Regulatory Compliance System

Descriptions

A full requirements specification has been produced detailing ECL stakeholders requirements. Due to a strict word limit a very brief extract is reproduced here: Users: 850 named users Duration: Minimum two year contract initially Location: All venues that ECL provides services from Non-functional requirements •Suppliers should have an understanding of and compliance with; regulations, guidance and legislation relevant to ECL •Suppliers should be certified against the Cyber Essentials Plus scheme •Suppliers should be certified against ISO27001. The certification body must be recognised by UKAS or be an international body recognised by UKAS •Suppliers must be proactively developing the system to ensure it stays current in the future. •Suppliers must be able to prove financial stability •Suppliers must be able to provide at least two reference sites that can be visited by key members of ECL’s team •Suppliers must be able to provide appropriate professional services and on-going support •Suppliers must be able to provide appropriate 1st, 2nd and 3rd line support either directly or in conjunction with Essex County Council •Suppliers must enter into a Data Processing Agreement with ECL or relevant clauses must be in the Terms and Conditions •Mobile devices can only be Samsung Android Knox or Windows Phone 8.1 / Windows 8.1 Functional requirements Split into 14 sub sections. MoSCoW prioritisation is used to indicate the level of importance stakeholders attach to each aspect of the specification. Sub section headings are reproduced here: •Security •Electronic forms •Workflow •Learning and development •HR •Document control •Policies and procedures •Incident reporting and customer engagement (comments, compliments and complaints) •Risk register •Audits •Asset management •Integration •Technical infrastructure •Service continuity / business continuity