WP1464: International reuse of Verify v2

Tender description

Summary of the work To investigate international interoperability of GOV.UK Verify and the potential to enable UK citizens to use their Verify accounts internationally. The team will be made up of 4 Developers and 4 Web Ops Engineers. Expected Contract Length six (6) months Latest start date Monday 13 November 2017 Why the Work is Being Done This work is to support building the capability of the UK's digital identity scheme on an international level. This work seeks to potentially enable international usage of GOV.UK Verify - for example a UK citizen using a Verify identity to access services abroad. This scheme of work is to scope the feasibility of potentially connecting Verify to the eIDAS framework and provide sizings and estimates for the next phase. This work needs to be completed by end of March 2018. Problem to Be Solved The ability for UK citizens to prove their identity using a UK digital identity, Verify, to access international services. Who Are the Users As a holder of a Verify account I need to prove my digital identity so that I can access an international service. Work Already Done A team in Verify is currently delivering the eIDAS core capability to enable people that hold a digital ID from other member states to prove their identify and use UK services that are on Verify. Existing Team Technologists as well as cross-functional colleagues in GOV.UK Verify Current Phase Not started Skills & Experience • Experience taking initiative to solve uncommon and difficult problems • Significant experience of developing modern web applications using Java • Experience with microservice architecture and 12-Factor applications • Experience of working with cloud environments, such as AWS, and infrastructure as code • Experience working with Public Key Infrastructure • Experience working in Agile environments and DevOps cultures • Ability to work independently and move in a fast-paced environment • Excellent communication skills • Experience in balancing the priorities of a delivery team against the needs of a wider programme and a product's stability Nice to Haves • Experience developing with SAML • Experience working in the public sector • Ruby experience Work Location Government Digital Service, The White Chapel Building, 10 Whitechapel High Street, London, E1 8QS Working Arrangments On site 5 days a week 9:00 - 5.30 Security Clearance SC Security Clearance is required to operate on this project. Must hold security clearance (SC) at start date of contract Additional T&Cs All expenses must be pre-agreed with between the parties and must comply with the Cabinet Office (CO) Travel and Subsistence (T&S) Policy. All vendors are obliged to provide sufficient guarantees to implement appropriate technical and organisational measures so that the processing meets the requirements of GDPR and ensures the protection of the rights of data subjects. For further information please see the Information Commissioner's Office website:https://ico.org.uk/for-organisations/data-protection-reform/overview-of-the-gdpr/ No. of Suppliers to Evaluate 3 Proposal Criteria • Your approach to onboarding your team to the projects • Your management of proposed flexible team resources • Your approach to defining technical architecture and software architecture in a context of legacy systems and a drive towards efficiency • Your approach to data privacy and security • How you've identified risks and dependencies and offered approaches to manage them • Proposal price Cultural Fit Criteria • Your approach to knowledge sharing with civil servants to support learning from this engagement. • Work as a team with our organisation and other suppliers • Transparent and collaborative when making decisions Payment Approach Time and materials Evaluation Weighting Technical competence 65% Cultural fit 15% Price 20% Questions from Suppliers 1. To deliver the scope of work (""To investigate international interoperability of GOV.UK Verify and the potential to enable UK citizens to use their Verify accounts internationally"") you would need a wider team than just however 4 developers and 4 web ops. Is there an existing team the 8 roles would sit in, or are you actually looking for a multi disciplinary team including BA/UR etc that can deliver all aspects of work against the scope? Yes, there is an existing team that the developers and webops will work with that will provide the non-technical roles. 2. You have stated "Must hold security clearance (SC) at start date of contract" . Our current experience is that new SC clearances and inter-departmental transfers of SC clearance are taking around 6 weeks. Given that your proposed start date is 13/11/2017 that would require any (non-incumbent) supplier to commence SC clearance requests by the end of September 2017. ie at the same time as this initial bid submission. Can you please clarify when you expect to award contracts and the amount of time that will be made available to the winning supplier to complete the SC clearance process post contract? The whole of the Supplier's team should have SC clearance before the latest start date 13 November. If not held by all of the Suppliers' team, then the Supplier is required to pay (estimated £64/person) and arrange security clearance themselves to become eligible and compliant to perform the contract. SC clearance can take from approximately eight to ten weeks.To arrange SC clearance please email gds-digital-buyer@digital.cabinet-office.gov.uk with your request for contact details, reference WP1464.Please note that the Supplier's contract would be terminated if SC clearance was not granted or held by their whole team. See: https://www.gov.uk/guidance/security-vetting-and-clearance