Crown Marketplace Foundation

Tender description

Why the Work is Being Done Public sector users access multiple CCS commercial agreements (CCS-CA) to buy common goods and services. Currently, this is a manual, paper based process which is complex and hard to use. These need to be turned into digital services that allow users to access these CAs online and via a self-service guided user journey. There are five CAs identified for digitisation and this work will form the foundation of a platform to support more CCS-CAs in the near future. Problem to Be Solved CCS requires an initial team to support the building of a platform based on a series of CCS-CA’s that have common repeatable elements and similar user needs. Each CCS-CA requires a consistent user experience and approach to delivery across the user journeys to be delivered as separate MVPs for each CCS-CA. The timelines for public betas are: Facilities Management 09/11/18, Management Consultancy 26/11/18, Legal Services 26/11/18, Agency Supply Teachers 29/10/18, Apprenticeship Training Service 27/11/18. Who Are the Users The primary user will have limited or no knowledge of a CCS-CA or how to use it. This user will however have personal experience of online shopping. User research has highlighted confusion when choosing which CCS-CA is appropriate, how to run a procurement and then select a supplier. The user needs to: find the right CCS-CA, be guided through the buying journey, filter results, shortlist suppliers, find local suppliers and compare supplier services. The user will require assistance choosing the appropriate mechanism to buy the most cost effective and compliant way. Early Market Engagement CCS has run a full test phase to fully understand the core service needs of our end-users, their buying habits, procurement methods and the end-to-end expectation of the service. A full evaluation of the capabilities of SaaS solutions has been conducted and work has been undertaken with GDS to design and understand both architectural and services designs. These findings have been incorporated into the service documentation that will be made available to shortlisted suppliers upon completion of a Non Disclosure Agreement. Work Already Done Discovery and user needs have been gathered for all the agreements and architectural designs. The Alpha is currently in the process of testing both wireframes and business requirements and will be available to the successful supplier. Link to architecture decisions: https://github.com/Crown-Commercial-Service/CCS-Architecture-Decision-Records/tree/TDDA-2018-07-09 Existing Team The existing team includes commercial subject matter experts, technical architects, technical and business operations, analysts and user researchers. There are also key interactions with GDS teams. CCS has a number of third party delivery partners which the successful supplier would be expected to work closely and co-operate with. Current Phase Alpha Work Location The Supplier will work in a mix of premises (including their own) in mixed teams with the client and other suppliers. The Supplier will travel as required to work and to attend key meetings, stakeholder engagement events etc. at the client's premises in London at 45 – 59 Kingsway, Holborn WC2B 6TE or other locations. The team and locations will be agreed during sprint planning meetings and may include CCS and other team members working from the suppliers office. Any expenses must be pre-agreed and must comply with the CCS Travel and Subsistence Policy. Working Arrangments The Supplier will be working within a development team that consists of a Product Owner and Delivery Manager. Other CCS roles may be added from time to time, including technical, design and operations colleagues. It will be a truly mixed team between the supplier and other suppliers and CCS staff. They will need to work closely with GDS to understand how the to keep the service architecture and design in step with the Digital Marketplace. The supplier will need to work within NCSC Cloud Security Principles. Security Clearance Some CTC cleared personnel would be an advantage and we can sponsor the application. Additional T&Cs Any expenses must be pre-agreed and must comply with the CCS Travel and Subsistence Policy. The Supplier must comply with the Digital Service Standard. The Suppler is to develop the service in line with the Cloud Security Principles, the Security Design Principles and the Bulk Data guidance. Skills & Experience Confirm you have built a microservice systems to at least public beta in the past 2 years using Java, Javascript, Ruby or Python, ideally in a complex multi-user environment. 2% Confirm you have at least 12 months experience operating microservice software. Describe how this was gained, ideally in an environment covering incidents, high resilience, logging and disputes. 2% Confirm you have 2 years experience building public cloud architectures using a script based 'architecture as code' approach and describe how this experience was gained. 2% Confirm you have 2 years experience operating in Continuous Integration environments shared with multiple teams, ideally with third parties and describe how this experience was gained. 2% Confirm you have 2 years experience performing user research and using that data to inform their build and describe how this experience was gained. 2% Confirm you have 2 years experience of working with mixed supplier and customer teams and describe how this experience was gained. 2% Confirm you have 2 years experience of iterative delivery starting with an MVP and continuously adding value and describe how this experience was gained. 2% Confirm you have 2 years experience building WCAG 2.0 level 2 (or equivalent) accessible web applications and describe how this experience was gained. 2% Nice to Haves Describe your experience in building AWS based architectures, the more AWS services the better. 2% Describe your experience in Docker, ideally in an orchestrated technology such as Kubernetes or AWS ECS. 1% Describe your experience in Terraform, ideally for a complete service architecture including pipeline. 1% Describe your experience in Python, ideally in a web application. 1% Describe your experience in Salesforce data integration and how this was gained. 1% Describe your experience working in a way similar to Government Design standards, including external assessment based governance. 2% Describe your experience in Government OFFICIAL security standards or similar. 1% No. of Suppliers to Evaluate 5 Proposal Criteria Summary: Describe your overall approach to delivering our outcome,how you will plan, build and manage the project including risks/learnings you feel are important for successful delivery. 6% Architecture: Outline your approach for multiple MVPs, using common records services (parties, agreements, catalogues, user needs, tasks) and other services (sector specific services, user registration and authentication). 6% MVPs: Outline your approach to delivering a user journey based on microservices within a task-list, e.g. user finds, selects suppliers and compares services. Detailed example will be provided. 6% Team: Describe your team and roles to support the multiple MVPs together with how they will work mixed with civil servants and other suppliers on a shared platform. 5% Working together: Describe how you will work so you can meet your commitments, whilst stories prioritisation and certain design and technology elements are not under your direct control. 6% Value: Outline your approach to delivering a platform with several CCS-CAs, each delivered as an MVP to its own dates and user groups, developing minimal but extensible platform components. 6% Cultural Fit Criteria Present what your approach to measuring quality of code would be when working within a multi-supplier and customer team. 4% Present how you meet the needs of different stakeholders with conflicting demands, working on multiple MVP’s with different time scales and how you will manage and report resource usage. 4% Present how you will work with other suppliers and CCS teams to maintain delivery timelines where collaboration may introduce outside dependencies or pressures. 4% Present your approach to sharing learning, feedback and technical solutions within teams and how you communicate this with non-technical stakeholders. 4% Present how you will document, share and then handing over an MVP to another team which could be another supplier and/or the CCS operations team. 4% Payment Approach Capped time and materials Assessment Method Written proposal Presentation Evaluation Weighting Technical competence 60% Cultural fit 20% Price 20% Questions from Suppliers Budget range £750k - £900k