Awarded to Cogworx

Start date: Tuesday 9 July 2019
Value: £30,000
Company size: SME

UK Export Finance

Service Design & Technical Architecture Service Discovery

9 Incomplete applications

6 SME, 3 large

12 Completed applications

10 SME, 2 large

• Published: Friday 3 May 2019
• Deadline for asking questions: Friday 10 May 2019 at 11:59pm GMT
• Closing date for applications: Friday 17 May 2019 at 11:59pm GMT

Overview

• Summary of the work: Talented team to undertake discovery work to help the service team understand how to develop an existing digital service to meet a public beta assessment against the GDS Service Standard.
• Latest start date: Monday 24 June 2019
• Expected contract length: 2-3 weeks
• Location: London
• Organisation the work is for: UK Export Finance
• Budget range: £30,000

About the work

• Why the work is being done: The Digital Trade Finance Project is enhancing UKEF's digital capabilities, and simultaneously setting a template for the way that the organisation will build and maintain digital services in the future. The service incorporates two existing online services (internal and external) The team have produced a high level plan for passing Public Beta Assessment. This procurement is acting on a GDS proposal that a short discovery takes place. The discovery will turn this high-level plan into a delivery plan of tangible activities the team can plan and deliver, focusing on all 18 aspects of a Public Beta Service Assessment.
• Problem to be solved: Work has taken place to align the Service with the governments approach to delivering digital services. ; However, the Service does not meet the governments standard for service delivery, nor does it currently meet accessibility standards.; To obtain GDS spend approvals and to bring the service in-line with the accessibility legal requirements a Public Beta Assessment needs to be undertaken and the standard met. Deliverables for this piece of work will include the definition a set of prioritised sprints with each sprint showing the problem statement the sprint is designed to solve, dependencies between sprints and the resources needed to deliver.
• Who the users are and what they need to do: Staff within partner banks with varying levels of experience of the system and its legal context, and UKEF internal staff. Estimated 7 and higher on the Digital Inclusion (for all users IT and web-based systems are essential parts of the job that they do).
• Any work that’s already been done: A high-level plan has been produced to take the service from its current position to a position where it is ready for a public beta assessment.
• Existing team: Service Owner, Product Manager, User Researcher, Delivery Manager, Business Analysts x2, Developers x4, QA analysts x2, Split into sub teams working on the internal and external facing elements of the service. The delivery attempts to be agile but is hampered by lack of continuous integration or automated testing.
• Current phase: Beta

Work setup

• Address where the work will take place: 1 Horse Guards Road London SW1A 2HQ
• Working arrangements: 5 days per week in the UKEF office.
• Security clearance: People need CTC (Counter-terrorism) clearance to work unaccompanied within 1 HGR. The short duration of this contract means that there will not be time to obtain this clearance, and so people will have to be accompanied during their visits to the UKEF office.

Additional information

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:
  • Have experience of helping a service meet the standards of a public beta assessment.
  • Have experience of auditing services to understand the gap between current position and work needed to meet assessment standard.
  • Have experience of mapping required resources to deliver against a roadmap of activity.
  • Be able to analyse the service design requirements of a public sector organisation and create a plan for how they could be met.
  • Be able to analyse the technical architecture of a service and identify ways that it should be enhanced to meet the Beta requirements of the GDS service standard.
  • Be able to analyse the content and UX of a Government or Financial Sector service and identify how it can be improved to meet user needs and meet agreed standards.
• Nice-to-have skills and experience:
  • • Have experience of working with Government Departments.
  • • Have experience of the financial sector.

How suppliers will be evaluated

• How many suppliers to evaluate: 3
• Proposal criteria:
  • Evidence of successful service design
  • Evidence of helping services meet accessibility standards
  • Evidence of helping services teams meet the GDS Service Standard at assessments
  • Evidence of implementing a successful Technical Architecture
• Cultural fit criteria:
  • Be extremely confident written and spoken communicators, able to engage senior leaders at short notice.
  • Be team players who can quickly integrate and add value.
  • Demonstrate good negotiation and influencing skills.
• Payment approach: Capped time and materials
• Assessment methods: Written proposal
• Evaluation weighting:

  Technical competence

  60%

  Cultural fit

  20%

  Price

  20%

Questions asked by suppliers

• 1. Would you be willing to consider 4 days per week in the UKEF office?: Yes.
• 2. What roles would you expect the supplier to provide?: Service designer, technical architect, and anything else the supplier recommends.
• 3. Is there an incumbent in this role?: It's not a role, it’s a discovery outcome. However, UKEF do not have service designers. We have had suppliers and contractors working on this service previously.
• 4. Is there an incumbent supplier who is currently working on this project for you, or has done so recently?: We have had suppliers and contractors working on this service previously.
• 5. Please advise whether the high level plan was produced for you by a third party supplier or by your own in-house staff.: The high level plan was produced by in-house staff and other government digital colleagues.
• 6. Can we see the beta assessment report?: The service hasn’t undertaken a public beta assessment yet.
• 7. Will the existing team be in place throughout the discovery process?: Yes.
• 8. Has any previous service discovery been conducted and if so what were the outcomes?: Other work has taken place, however it has not been focused on getting the service to a public beta standard.
• 9. Have you carried out a private BETA? Will the results be shared with us?: An assessment workshop has taken place. The results will be shared with the successful supplier.
• 10. Have you carried out a private Beta? and if so will this be made available before end of the bid phase?: An assessment workshop has taken place. The results will be shared with the successful supplier.