Crown Commercial Service
Report Management Information - Beta and Live
1 Incomplete application
0 SME, 1 large
4 Completed applications
4 SME, 0 large
Important dates
- Published
- Wednesday 25 July 2018
- Deadline for asking questions
- Wednesday 1 August 2018 at 11:59pm GMT
- Closing date for applications
- Wednesday 8 August 2018 at 11:59pm GMT
Overview
- Summary of the work
-
CCS requires a team to continue to build a beta service and move to live by March2019. The Report Management Information service will take its first transactions in August and the new service will roll-out to suppliers in phases thereafter.
The supplier will provide service support whilst it's transitioned in-house - Latest start date
- Wednesday 26 September 2018
- Expected contract length
- 7 month contract with the option to extend for a period of up to 5 months
- Location
- London
- Organisation the work is for
- Crown Commercial Service
- Budget range
- Up to £320,000
About the work
- Why the work is being done
- We are changing the way suppliers report their spend to CCS, following on from the work completed in Discovery and Alpha, we are seeking a delivery partner to continue this development into Beta and Live.
- Problem to be solved
-
Completion of the existing prioritized product backlog to ensure the service continues to meet user needs through private beta. On-going development of the service, product roadmap and backlog through to passing the Live service assessment.
Work will include phased migration of around 7000 users from the old service to the new service and continued onboarding of new users. The old service is planned for closure in April 2019. - Who the users are and what they need to do
-
- Suppliers who need to submit monthly returns. Suppliers may be micro-businesses, SMEs or large companies
- CCS staff who provide support and assistance to suppliers submitting returns.
- CCS staff who manage performance of existing frameworks and development of new frameworks
- CCS staff who need to need to perform audits and due diligence
- Other CCS systems that need to pull data from a management reporting tool - Early market engagement
- A roadmap/backlog will be shared with the shortlisted suppliers.
- Any work that’s already been done
-
We have been working with dxw since February on prototyping and developing an MVP product. The service is due to go into private beta on 1 August 2018 with a small number of suppliers.
The outcome for alpha: https://www.digitalmarketplace.service.gov.uk/digital-outcomes-and-specialists/opportunities/6012
The architecture decisions for the project:
https://github.com/Crown-Commercial-Service/DataSubmissionService-ADRs - Existing team
-
CCS Team made up of:
Senior Delivery Manager
Technical Architect
Supplier team made up of:
Delivery Manager,
Product Manager,
User Researcher,
Content Designer,
2 Developers,
Designer,
Ops support - Current phase
- Beta
Work setup
- Address where the work will take place
-
Onsite work for a minimum of three days a week at CCS’ offices at Civil Aviation House, Kingsway London.
Regular travel to Norwich (and occasional travel to Liverpool) will be required. - Working arrangements
-
Onsite work for a minimum of three days a week.
Regular travel to Norwich (and occasional travel to Liverpool) will be required.
Any expenses must be pre-agreed and must comply with the CCS Travel and Subsistence Policy. - Security clearance
- CTC is required. Crown Commercial Service will sponsor clearance process.
Additional information
- Additional terms and conditions
Skills and experience
Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.
- Essential skills and experience
-
- Experience of taking an MVP and transitioning it to a live service with a focus on user needs - Please detail what you did, when and the outcomes - 5%
- Experience working on agile projects within multidisciplinary teams, as outlined in Government Service Design Manual and Digital Service Standard - Please detail what you did, when and outcomes - 1%
- Experience iteratively designing&prototyping service changes, testing with users and turning research data into clear findings to inform an improvements backlog - Detail what you did, when and outcomes - 2%
- Experience in developing secure services and how to pragmatically mitigate risks - Please detail what you did, when and the outcomes - 1%
- Experience of building scalable infrastructure using Terraform, Amazon Web Services, Elastic Container Service and Docker - Please detail what you did, when and the outcomes - 2%
- Experience developing applications using Javascript, Ruby-on-Rails and Python and the GOV.UK frontend toolkits - Please detail what you did, when and the outcomes - 2%
- Experience developing and managing serverless applications using AWS Lambda - Please detail what you did, when and the outcomes - 5%
- Nice-to-have skills and experience
-
- Experience migrating users from a legacy service to a new service, including strong stakeholder management skills - Please detail what you did, when and the outcomes - 1%
- Experience of transferring knowledge to internal staff - Please detail what you did, when and the outcomes - 1%
How suppliers will be evaluated
- How many suppliers to evaluate
- 5
- Proposal criteria
-
- Outcome Delivery: Describe your overall approach to delivering our outcome, how you will plan, build and manage the project including risks/learnings that are important for successful delivery. 10%
- Team structure: Describe your team set up (including roles) and how you would adapt the team to changing priorities during the course of beta and transition to live - 10%
- Understanding user needs: Detail how you will ensure user needs are understood and met in the development and delivery of the service 5%
- Knowledge Transfer: How will you ensure CCS staff are ready to take on operational control and support upon completion of the work. 5%
- Architecture:How will you develop (and continue to develop and iterate) the service in line with the architecture decisions outlined here: https://github.com/Crown-Commercial-Service/DataSubmissionService-ADRs 5%
- Delivery Plan: Provide a delivery plan to deliver within the stated time frames - 5%
- Price: Provide an outline of your costs to meet the outcome within the timeline - NOTE: this will be evaluated using the Price weighting, and submitted with written proposals
- Cultural fit criteria
-
- NOTE: Cultural Fit Criteria will be assessed during Supplier Presentations
- Demonstrate your ability to deliver in an open, collaborate, agile way according to the principles outlined in the Government Service Design Manual - 5%
- Demonstrate your ability to work and communicate with clients / team members with low technical expertise - 5%
- Demonstrate your ability to deliver outcomes, applying an agile methodology, in non-agile environments and successfully bridging the two worlds - 5%
- Demonstrate how you will deliver simplicity (e.g. do less but better, explaining complex issues in a clear, simple way, break down and prioritise complex issues) - 5%
- Payment approach
- Capped time and materials
- Assessment methods
-
- Written proposal
- Presentation
- Evaluation weighting
-
Technical competence
60%Cultural fit
20%Price
20%
Questions asked by suppliers
-
1. 7367/1 - 01/08/2018 14:14
Will CSS be recruiting user research participants for usability testing and ongoing research? - Yes, we have access to a user research coordinator in the team who helps find research participants and book research sessions.
-
2. 7367/2 - 01/08/2018 14:15
Does this budget include any expenses for user research, or is there a separate budget for this? - Expenses for travel are covered as part of the wider contract. There is budget for accessibility testing and assisted digital research.
-
3. 7367/3 - 01/08/2018 14:18
You mention that the "The supplier will provide service support whilst it's transitioned in-house". Can you tell us more about the team who will be taking over support for the service and their capability? - CCS has internal teams that support existing systems. They will be taking on responsibility for supporting various digital services including Report MI. This support role will include handling enquiries, managing virtual infrastructure and incident management.
-
4. 7367/4 - 01/08/2018 14:18
Do you anticipate that any other roles will be needed to support the migration/roll-out? For example, stakeholder engagement or comms? - We expect suppliers at proposal stage to suggest the roles they feel are required to successfully deliver a large scale migration alongside ongoing development work.