Care Quality Commission (CQC)

Delivery of Alpha and Beta Phases for CQC Digital Services

Incomplete applications

11
Incomplete applications
7 SME, 4 large

Completed applications

15
Completed applications
9 SME, 6 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 13 February 2017
Deadline for asking questions Monday 20 February 2017 at 11:59pm GMT
Closing date for applications Monday 27 February 2017 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Care Quality Commission requires a supplier to deliver Alpha and Beta Services. The Supplier must have specialist capability and experience in delivering digital services in line with Digital by Default Standards.
Latest start date Week-commencing 27th March 2017
Expected contract length 12-24 months
Location London
Organisation the work is for Care Quality Commission (CQC)
Budget range The budget range for one year is from zero commitment (£0) to £667,580 + VAT. The Contract will be used to deliver specific service outcomes and outputs by bringing in a Supplier with the relevant Digital expertise to deliver Alpha and Beta Services. It is estimated that the Contract will last for 1 year however with a provision to extend for a further year should additional Services be required. Payments anticipated to be in instalments based on output delivery throughout the Alpha and Beta phases of each project. More information on payment structure to be provided following the Shortlisting Stage.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done Care Quality Commission (CQC) completed discoveries in late 2016 in three different areas:
● Project A- Collecting information from adult social care providers to assess, monitor and improve the quality and safety of services.
● Project B- Receiving feedback on people’s care.
● Project C- CQC Intranet.
Therefore, we now require a specialist, agile team to work with us on the Alpha and Beta phases to develop new digital services which have been informed by the discoveries.
In the event any additional Discoveries are undertaken the services may be required to fulfil the relevant Alpha and Beta phases.
Problem to be solved ● Project A- Collecting information from adult social care providers to monitor and improve the quality of services:
The existing system does not meet the needs of the users (duplication of effort, clarity of the process, complexity of information asked).
● Project B- Receiving feedback on people’s care:
Our current channels to receive people’s experiences of care do not meet our users’ needs (anonymity, security and confidentiality of data).
● Project C-CQC Intranet: The CQC is reviewing the current service offering with the goal of creating an intranet which is easier to use, maintain and is accessible by all employees.
Who the users are and what they need to do The following user stories correspond to current projects:
●Project A- As an adult social care provider, I need to provide information about the quality of my service so that I am compliant with CQC regulations.
●Project B- As a health and social care service user, I want to give feedback on my care, so that I can enable the relevant authority to take appropriate action/response.
●Project C- As a CQC employee, I need to find up-to-date information and guidance, so that I can do my job efficiently.
The Supplier will need to consider these user needs at all times.
Early market engagement We have discussed with GDS, OGDs and other ALBs regarding successful, similar service delivery and Supplier interaction.
Any work that’s already been done Discoveries were completed in late 2016 and outputs will be provided to the successful supplier. Moreover, prospective suppliers have the opportunity to ask questions should they need more clarity on each project.
Since the end of Discoveries, CQC have focussed on getting our technical infrastructure ready for specialist teams to start developing our new digital services and continuously integrate with existing systems. A Technical Architecture review is currently in progress to assist in this readiness and on the potential solution architecture of these digital services.
Existing team Head of Digital Development, three Product Owners, colleagues from Data Management, and Systems & Applications whenever necessary as part of the enabling project team. There may be instances where the Supplier will be required to work with other CQC Suppliers, especially those running existing systems.
Current phase Alpha

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place 151 Buckingham Palace Road, London, SW1W 9SZ.
Working arrangements It is expected that the majority of time will need to be spent by the Supplier co-located at the Authority’s Head Office (151 Buckingham Palace Road, London, SW1W 9SZ). The Authority can account for some off-site working to be agreed. Anticipated standard working hours Monday to Friday.
Security clearance Must meet the Baseline Personnel Security Standard (BPSS) and CQC’s Data Security standards .

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions We are looking for a reliable and skilled delivery partner throughout Alpha and Beta phases. However, continuing to the Beta phase will depend on successfully passing GDS Alpha Service Assessment. The continuation of Services relating to an individual project may be terminated if the Assessment has not been passed.
The Supplier will be required to deliver the following outputs which must comply with GDS Service Standards:
Alpha:
● end-to-end working prototype that passes the GDS Service assessment for each project.

Beta:
● end-to-end working digital service that passes the GDS Service assessment for each project

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Have expertise in Agile delivery as outlined in the GDS Service Manual (2%)
  • Have experience of designing services that meet the GDS Service Standards and have passed the GDS Service Assessment (2%)
  • Have experience of designing prototypes from Discovery findings to meet user needs (2%)
  • Be highly experienced with using application programming interfaces (APIs) and representational state transfer (REST) web services (1.5%)
  • Have expertise in cloud technologies: design, planning. security, integration, whilst remaining Cloud provider agnostic (1.5%)
  • Have experience in using automated testing environments and continuous integration (1.5%)
  • Have the ability to provide up to three multi-disciplinary teams as per GDS Service Manual to client site for the duration of the project (1.5%)
Nice-to-have skills and experience
  • Experience in Oracle-based CRM systems (1%)
  • Experience of working with a national regulator (1%)
  • Experience of upskilling a traditional public sector environment into agile ways of working (1% )

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • Demonstrates Supplier’s previous experience in delivering an Alpha or Beta service that have passed GDS Service Assessment- 10%
  • Demonstrates Supplier’s previous experience in setting up a multi-disciplinary agile team for a government agency- 10%
  • Demonstrates Supplier’s previous experience in managing risks and dependencies- 10%
  • Demonstrates Supplier’s approach and methodology to delivering an Alpha for Project A mentioned above (including technical solution, team structure) addressing GDS Service Manual- 10%
  • Proposal Criteria to be assessed via Written Proposal.
Cultural fit criteria
  • Demonstrates Supplier’s proposition on delivering an Alpha for Project B mentioned above addressing GDS Service Manual with particular focus on research techniques with the users- (5%)
  • Demonstrates how the Supplier will work collaboratively with the host organisation and other suppliers towards successful delivery-with reference to previous examples (7.5%)
  • Demonstrates how the Supplier will upskill CQC and provide knowledge transfer to the Contracting Organisation- (7.5%)
  • Cultural Fit Criteria to be assessed via Presentation. Anticipated dates of presentation- 9th/10th March 2017
Payment approach Fixed price
Assessment methods
  • Written proposal
  • Presentation
Evaluation weighting

Technical competence

55%

Cultural fit

20%

Price

25%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Have you already made a selection for Oracle CRM or would consider other CRM solutions like MS Dynamics or Sales force? Oracle CRM is our current system. We presume all future digital services to consider issues of connectivity into the CRM, provided that Alpha proceeds to Beta.
2. Considering in an Alpha the aim would be to explore the user needs; can the nice to have criteria for: Experience in Oracle-based CRM systems (1%) be removed from the list of criteria. Oracle CRM is our current system. We presume all future digital services to consider issues of connectivity into the CRM, provided that Alpha proceeds to Beta. This is a nice-to-have criteria.
3. In order to achieve project cohesion, does CQC accept that some cross-fertilisation of project personnel across items A, B & C would be desirable? Yes. However, if any of the projects are conducted simultaneously we must ensure that there is sufficient coverage.
4. Was the Discovery phase carried out internally and are the results of the Discovery findings available? Discovery work was carried out by CQC, in collaboration with a Supplier following a Procurement exercise. The full output from the Discoveries will be shared with the successful Supplier.

As there is a character limit within the comments section, and an issue with how DOS creates hyperlinks, please copy and paste the following link into your browser to view a selection of our user stories:

https://docs.google.com/document/d/1qSxq2Aiz1Mz0zOJYRDK12yohztMtQmPehZYBi-EKgik/edit?usp=sharing
5. Given that CQC seeks an agile project, would fixed price quotes per sprint be acceptable? It is anticipated payment will be in instalments linked to the completion of deliverables such as sprints throughout each project however the exact and final structure will be shared following the shortlisting stage.
6. Will it be possible for shortlisted suppliers to ask any further clarification questions - once suppliers have been shortlisted? The timeline for Clarification questions will be in-line with Digital Outcome and Specialists (DOS) Guidance.
7. Has consideration yet been given to how the information in the map will be kept up-to-date, validated and moderated, or is this an area to be tackled in Alpha? Thank you for your question, however, we are not sure which map you are referring to and are unable to provide a response.
8. What level of integration (if any) is required with Departments’ Programme and Project Management tools/systems? We use only Jira, Trello and Slack to manage our projects, and there isn’t any other systems that need to be considered in relation to project management.
9. Has Discovery established any preferences for the technologies to be used (or does the Department have any in-house preferences that should be adopted)? We are currently evaluating Drupal 8 and Django as potential options, enabling extensibility with third-party systems. API-first approach enables fast-paced development outside of external deployment cycles.
10. In the event any additional Discoveries are undertaken the services may be required to fulfil the relevant Alpha and Beta phases.". Could you clarify the intent behind that please? Does it just mean that the scope of work may expand? The number of the Alphas/Betas required may increase dependent on emerging business need. Payment will reflect any increase in work.
11. What is the reason for grouping the 3 projects together in a single tender? Does this reflect your preference for a) a solution that covers all three aspects, b) a provider that can address all three projects, or is it just for procurement expediency? CQC are not looking for a solution that covers all three aspects. These are three priority projects and we want to address them through a single provider.
12. One of your criteria is to be highly experienced in APIs and REST web services - while this isn't a problem for us, are there particular systems you're expecting to integrate with (you've mentioned Oracle CRM) ? Oracle CRM is our current CRM system. We require any new services developed to have the flexibility to integrate with a range of internal and, possibly, external systems.
13. 'Have the ability to provide up to three multi-disciplinary teams as per GDS Service Manual to client site for the duration of the project (1.5%)' Further to my other question, would you prefer one supplier who could service all three projects, or would you equally welcome bids for some, but not all projects. We would like one bid for all projects.
14. Are alternative dates available for the cultural presentation if key personal are unavailable for the dates suggested (the week of 6th March)? Week commencing 6th March is the preferred option.
15. With respect to Project A, are you including any possible integration to automatically collect data from care management systems (including via Public API) or has that been excluded from the beta? We would seek to address these questions in the alpha stage and then develop in beta accordingly.
16. Can we ask for clarification on what the stated budget is expected to cover? For example, is £667k is for all 3 Alphas and Betas? In addition to this, can we ask how the specific estimations for the budget have been made? The £667,000 is to cover all three Alphas and Betas. We have modelled costs based on average time and resource estimated for each project.
17. is it expected that 1 supplier will work across all 3 projects, or would you look to appointment different suppliers? Single supplier.
18. To get a sense of the relative complexity of each project, please could CQC indicate what percentage of the maximum available budget range they would expect to be apportioned to each project (e.g. project 1 20%, project 2 50%, project 3 30% etc.)? CQC expect the supplier to allocate cost.
19. Besides Oracle CRM, does CQC have any preferred technologies/standards/tools that suppliers should align with? If so, please could this information be shared? Open standards. Drupal 7/8. Django. Trello, Slack, JIRA.
20. Given that this would be a fixed price engagement, have the Discoveries identified a clear Minimum Viable Product for each project and does CQC expect that no further Discovery work will need to be undertaken by the successful supplier? Yes, we have MVPs for each project and will require no further discovery work from the supplier.