Care Quality Commission (CQC)

Delivery of Alpha and Beta Phases for CQC Digital Services. Re-advertisement

Incomplete applications

20
Incomplete applications
12 SME, 8 large

Completed applications

17
Completed applications
11 SME, 6 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 20 March 2017
Deadline for asking questions Monday 27 March 2017 at 11:59pm GMT
Closing date for applications Monday 3 April 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 w/c 8th May 2017
Expected contract length 12 months with an option to extend for a further 12 months should this be required
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 outcomes and outputs by bringing in a Supplier with the expertise to deliver the Services. It is estimated the Contract will last for 1 year with a provision to extend for a further year should additional Services be required. Fixed price Agreement based on delivery of outputs. Payments likely to be in two instalments within both Alpha and Beta phases of each project. More information on payment structure to be provided following Shortlisting to inform Price Submission.

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 service quality: The existing system does not meet user needs (duplication of effort, clarity of the process, complexity of information asked) or integrate with core systems.

Project B- Receiving feedback on people’s care: Our current channels to receive people’s experiences of care do not meet user needs (anonymity, security and confidentiality of data) or integrate with core systems.

Project C-CQC Intranet: 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 completed late 2016; outputs will be provided to the successful supplier.

Since the Discoveries, CQC has focussed on getting our technical infrastructure ready for specialist teams to start developing the new digital services and continuously integrate with existing systems. CQC has significant legacy Drupal assets and are considering either Drupal or Django as potential future technology options.
A Technical review has been undertaken and a prospective architecture designed - this is based around a number of independently deployable services that expose and consume RESTful APIs to deliver required business outcomes. Several PoCs are being built to test architecture feasibility.
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 our 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 which will be appended to the final Contract with the successful Supplier.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions At the end of Alpha CQC will decide whether the Services relating to each Project (A,B&C) will proceed to Beta and the Contract/Services relating to an individual Project may be terminated at this point. Progression to Beta will also depend on the Alpha successfully passing GDS Service Assessment. Each individual Alpha and Beta will be detailed as a Statement-of-Works appended to the Contract.
Payment will be linked to completion of the following outputs (split by instalments)-see GDS Service Standards for detailed outputs:
-Alpha- end-to-end working prototype passing GDS Service Assessment.
-Beta- end-to-end working digital service passing GDS Service Assessment.

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 experience of delivering digital services using Agile techniques (as defined in the GDS Service Manual) that meet the GDS Service Standards and have passed GDS Service Assessments (2%)
  • Have experience of rapid development of prototypes from Discovery findings to meet user needs (1%)
  • Be highly experienced in designing, building and consuming application programming interfaces (APIs) and representational state transfer (REST) web services (1.5%)
  • Can demonstrate the benefits of using cloud technologies and have experience in design, planning, security and integration, whilst remaining cloud provider agnostic (1%)
  • Have experience in delivering services in a continuous integration environment and using automated testing frameworks (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%)
  • Have demonstrable experience in developing reusable forms based data collection modules incorporating workflow logic in Drupal or Django (2%)
  • Have demonstrable experience in integrating Drupal or Django with IDAM/SSO systems such as Okta, ideally exploiting existing reusable components (2%)
  • Have demonstrable experience in integrating Drupal or Django with Oracle-based CRM systems, ideally exploiting existing reusable components (1%)
Nice-to-have skills and experience
  • Experience of working with a national regulator with a clear understanding of the implications (0.5%)
  • Experience of upskilling a traditional public sector environment into agile ways of working leading to a transformational change in working methods (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 approach and methodology to delivering a successful Alpha and Beta for specifically Project A mentioned above (including technical solution and team structure) addressing GDS Service Manual- (15%)
  • Demonstrates architectural blueprint for a service that minimises bespoke coding and addresses problem with reference to component services and APIs- (10%)
  • Demonstrates Supplier’s previous experience and proposed approach in delivering an Alpha and Beta service that passes GDS Service Assessment- (5%)
  • Demonstrates Supplier’s previous experience and proposed approach in setting up a multi-disciplinary agile team for a government agency - (5%)
  • Demonstrates Supplier’s previous experience in and proposed approach to managing risks and dependencies- (5%)
  • Proposal Criteria to be assessed via Written Proposal.
Cultural fit criteria
  • Demonstrates Supplier’s proposition on delivering a successful Alpha and Beta for Project B mentioned above addressing GDS Service Manual (with focus on technological capability and approach) - (10%)
  • Demonstrates how the Supplier will work collaboratively with the host organisation and other suppliers towards successful delivery - with reference to previous examples (5%)
  • Demonstrates how the Supplier will upskill and provide knowledge transfer to CQC - (5%)
  • Cultural Fit Criteria to be assessed via Presentation at CQC Head Office. Anticipated dates of presentation- 20th/21st/24th April 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. Additional information: Although the full output from the Discoveries will be provided to the successful Supplier, please click on the following to view a selection of our User Stories: https://docs.google.com/document/d/1qSxq2Aiz1Mz0zOJYRDK12yohztMtQmPehZYBi-EKgik/edit?usp=sharing
2. Can you confirm if you are after a single team for 1 year, running the work sequentially, or looking for 3 teams running projects in parallel for about 3-4 months. The suggested budget is unlikely to cover 3 teams for 12 months. The working assumption is that projects will be delivered in a staggered fashion, beginning with Provider Information Returns (Project A), with some overlap to enable development and learning from one project to be used within the subsequent projects. However, we would wish to work with the supplier to determine whether work can be brought forward as we progress, without losing the benefit of learning. This would enable us to deliver benefits in a shorter timeline. It is important that any partner has the flexibility to work under either scenario.
3. Is the particular reason to why this opportunity has been re-advertised? More is now known around CQC’s potential technology landscape which has enabled clearer technical criteria to be defined. These criteria will help us ensure we reach a better outcome from the procurement. The decision was made to re-advertise on this basis.
4. We note that this is a Re-advertisement from a previous opportunity in February 2017. Can you confirm why the previous advertisement did not successfully lead to a selection? More is now known around CQC’s potential technology landscape which has enabled clearer technical criteria to be defined. These criteria will help us ensure we reach a better outcome from the procurement. The decision was made to re-advertise on this basis.
5. Can you say why you are re-advertising this work? More is now known around CQC’s potential technology landscape which has enabled clearer technical criteria to be defined. These criteria will help us ensure we reach a better outcome from the procurement. The decision was made to re-advertise on this basis.
6. CQC states that “current channels … do not meet user needs (anonymity, security and confidentiality of data) or integrate with core systems”. Will there be an opportunity, within the agile framework, to evaluate CQC’s proposed architecture against required elements of the solution e.g. anonymity, masking, data governance? The proposed architecture doesn't specify any particular level of anonymity, security and data governance, though CQC would need the delivered solution to meet the required levels which will be defined in conjunction with our information security team and GDS security guidelines. We would anticipate that a chosen supplier would work to help define solutions given need.
7. Does CQC intend to take responsibility for the maintenance of data quality and integrity given the need for data governance, update and write-back to CQC core systems (administered by third parties) arising from the new inputs? Yes
8. Projects are often held up between Alpha and Beta phase by the need to get further funding approval. Can you confirm that the funding of up to £667,580 +VAT has been approved and is now committed to this work should the Alphas prove the need for Beta development? We have approval for the entire funding envelope and budget allocated. However, we will still be subject to GDS approvals for the move from Alpha to Beta.
9. This is an re-advertisement (as stated), can you please shed some light on why this was re-advertised? Are the questions that where answered on the original submission still valid? More is now known around CQC’s potential technology landscape which has enabled clearer technical criteria to be defined. These criteria will help us ensure we reach a better outcome from the procurement. The decision was made to re-advertise on this basis. Only response submissions for this re-advertisement will be evaluated and considered.
10. Is direct interrogation of Oracle databases now out of scope? If so, how is it intended to provide information for the review process? If in scope, have the licensing implications been addressed by CQC? (The supplier cannot as we have not been told precisely what systems we should integrate with.) We envisage that Integration with our Oracle-based CRM will be through APIs, but we will take on board advice from suppliers based on their experience. CQC will manage any licence costs or implications.
11. May suppliers reference indirect web service integration credentials between Drupal and Oracle? Our experience indicates that direct integration is not achievable; would require Oracle participation in the coding; and will have licensing implications We envisage that Integration with our Oracle-based CRM will be through APIs, but we will take on board advice from suppliers based on their experience. CQC will manage any licence costs or implications.
12. The configuration of your existing team makes us believe that you intend to control the workflow. Is that right, please? Since you are asking the potential supplier to commit to delivery within a fixed period of time and a fixed budget, how do you intend to address potential delays caused by traditional management approaches on your side, please? How will the responsibility be distributed? For example, your Product Owners not receiving in real-time the information needed to progress with development. Are you able to give to the potential contractor full authority over delivery matters, please? We want the supplier to have experience of upskilling a traditional public sector environment into agile ways of working leading to a transformational change in working methods. Your response should demonstrate how you will work collaboratively with CQC towards successful delivery. Working with our Product Managers the Supplier will manage the workflow. CQC will work with the supplier to manage scope and time within budget.
13. Does CQC consider this work to be in or out of scope of IR35? CQC considers this request for Alpha and Beta Services to be out of scope of IR35. Payment will be based on deliverables and outputs which will be communicated following the short-listing stage.
14. Although CQC describes its Drupal assets as 'legacy', should suppliers understand that CQC now considers Drupal (Django or equivalent) as strategic to the collection and review of these new inputs to its valuable data and intelligence assets? We have a series of Drupal 7 assets (public website, provider portal). We are looking at how best to develop CQC’s assets and retain an open mind as to whether Drupal 8 or Django form the best solution for future core services. Both present significant benefits and the combination of service provider capability and their proposed architectural plans for use of either Drupal or Django will inform CQCs choice of Supplier.
15. Does CQC consider this work to be in or out of scope of IR35? In addition to the response provided CQC would like to make clear the following practices for Digital projects will be in place:

• The terms of engagement are centred around specific deliverables and outcomes through a specific project.
• The skills being sought are not currently available in CQC
• Suppliers can substitute resources should they need
• CQC requires only the need for a team to be collocated. For the majority of the time the most efficient cost effective way for that to occur is on premises, however, considerations will be made for work to be carried out elsewhere.