Department for Transport, on behalf of 207 Local Authorities in England, Wales, Scotland and NI.

Blue Badge Service - Beta Phase

Incomplete applications

8
Incomplete applications
3 SME, 5 large

Completed applications

14
Completed applications
5 SME, 9 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 5 February 2018
Deadline for asking questions Monday 12 February 2018 at 11:59pm GMT
Closing date for applications Monday 19 February 2018 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work The winning supplier will be required to provide a multi-disciplinary team to take the online application form, Local Authority interface and the single system of record through beta and in to live.
Latest start date Monday 9 April 2018
Expected contract length 10 Months
Location London
Organisation the work is for Department for Transport, on behalf of 207 Local Authorities in England, Wales, Scotland and NI.
Budget range Capped at £2,670,000

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The current Blue Badge service is ending in December 2018. A new online application form, Local Authority interface and single system of record needs to be in place by January 2019. Discovery and Alpha phases are complete. This contract is to take forward a Beta phase and transition in to a Live Service.
Problem to be solved There are circa 3 million Blue Badge holders in the UK. Permits can last up to 3 years. Around 1 million applications are made per annum. This figure consists of new applications and reapplications.

207 Local Authorities throughout the UK administer this scheme. Citizens can apply for a Blue Badge either in person or online. The contract for the current online application, Local Authority interface and single system of record ends in December 2018.

The supplier will:
-take the findings from the Discovery and Alpha phases into Beta
-build a new service
-transition to a Live Service by January 2019.
Who the users are and what they need to do As a citizen
I need to complete the application process online
So that the application process is quick and efficient

As a local authority administrator
I need to be able to manage and issue Blue Badges in my area
So that I can provide a service to citizens

As a local authority enforcement officer
I need to check the validity of a badge
So that I know whether to take action or not
Early market engagement No early market engagement has taken place with suppliers for this requirement.
Any work that’s already been done The Discovery and Alpha phases have already been completed. The GDS Alpha Assessment was passed in January 2018. We are now ready to move in to the Beta phase. The Live service needs to be in place by January 2019.
Existing team The supplier will be working with the DfT colleagues in London and DfT colleagues in Swansea, as well as leads from various Local Authorities. The core team is:

Keith Hughes – DfT Head of Parking & Blue Badge Policy (London)
Anthony Ferguson – Senior Responsible Owner (London)
Daniel Fyfield – Service Manager (Swansea)
Adam Griffiths – Product Owner (Swansea)
Current phase Alpha

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Great Minster House, 33 Horseferry Road, London, SW1P 4DR

DVLA, Longview Road, Morriston, Swansea SA6 7JL

You will also be required to visit various Local Authorities throughout the UK.
Working arrangements We expect a full time engagement from delivery teams to meet the required outcomes.

We expect this to be a full time, 5 day per week basis (Monday to Friday). We value co-location, therefore we do expect face to face dialogue, in the spirit of the service standard, on a weekly basis.

Show and Tells will be conducted in either London or Swansea.
Security clearance BPSS

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions Standard Framework and Call Off Terms and Conditions. Any expenses shall be submitted in line with DfT standard T&S policy.

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
  • Demonstrate understanding and ability to deliver digital services/products to the Government Digital Service standards
  • Demonstrate experience in iteratively improving and successfully taking complex, high volume transactional digital services from public beta through to Live service
  • Demonstrate a successful approach to completion of required Security Health Check, Penetration Testing, Service Readiness, and release reviews as part of quality and acceptance tests
  • Demonstrable experience of transitioning a multi-faceted and complex service from one service model to another
  • Be able to deploy an effective multi-disciplinary team able to start work no later than 9th April 2018.
  • Proven track record of delivering projects at speed with clearly identified deliverables and timescales
  • Demonstrable evidence of excellent planning, coordination, communication and project management skills.
  • Have demonstrable experience of delivering IT services that has millions of users.
  • Must have significant UX and user testing credentials
  • Proven experience delivering projects using the agile project management methodology
Nice-to-have skills and experience
  • Experience of working with Central Government agencies
  • Experience of working with the Local Authority network
  • Demonstrable evidence where innovative solutions have been applied to assist in project delivery
  • Demonstrable evidence of adhering with Customers’ relevant policies and standards
  • Demonstrable evidence of successfully managing and assisting in delivering IT projects within public sector organisations
  • Demonstrable experience of utilising Open source technologies to affect change

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • Proposed methodology and approach to taking forward the Beta phase including how the findings from the Discovery and Alpha phases will be adopted (20%)
  • Proposed team structure, including details of resource, positions and responsibilities throughout Beta. (including CVs of key members) (10%)
  • Ability to meet the timeframe for Beta to live (10%)
  • Proposed methodology and approach to service transition from Beta to Live, and how you will work with the incumbent supplier to achieve this. (15%)
  • Proposed approach to working with Local Authorities in adopting the new service, and how support and guidance will be provided during transition (10%)
  • How you have identified risks and dependencies and offered approaches to manage them (5%)
Cultural fit criteria
  • Experience of working as a team with our organisation and other stakeholders and suppliers (2.5%)
  • Evidence where status quo has been challenged resulting in an improved final outcome (2.5%)
  • Demonstrable evidence of working with clients with low technical expertise (2.5%)
  • Proposed approach for working remotely (and co-located where possible) as part of the DfT Project team. (2.5%)
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Presentation
Evaluation weighting

Technical competence

70%

Cultural fit

10%

Price

20%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Will DfT share the outputs of Alpha Phase with potential bidders? Yes, please follow this link to the final Show & Tell https://docs.google.com/document/d/13DQaLswZ7i5h5SwucboU5VJ103fxrgTHd9G9UJmByVs/edit?usp=sharing
2. Does DfT have more detailed information for potential bidders regarding the Beta requirements? Yes, please follow this link to the Additional Information document https://docs.google.com/document/d/1WXSQaFRbAsVxSi-9GlBKKQsmgYa3-7MOA1ea__90k5I/edit?usp=sharing
3. a) Can you please confirm whether a supplier has been working with DFT to complete Discovery and Alpha Activities and b) whether that supplier will be bidding for this opportunity or otherwise involved in any ongoing activity? a) Yes, a supplier was procured through Digital Outcomes & Specialists Framework Lot 2 in August 2017 to conduct the Blue Badge Service: Discovery / Alpha.

b) The Department’s Blue Badge Service: Beta Phase opportunity is open to all suppliers on the Digital Outcomes & Specialists Lot 2 (Find a team to provide an outcome). The Department has no valid reason to ask the provider of Discover/Alpha Phases, if they will be bidding for the Beta Phase opportunity.
4. Which software development technologies have been used during the Alpha Phase? Does the authority have a preference for a particular technology stack? Please email rob.thomas@dft.gsi.gov.uk for access to the Technology Stack document.
The Government technology code of practice should be followed where possible. Link: https://www.gov.uk/government/publications/technology-code-of-practice/technology-code-of-practice
5. Please can you confirm the name of the supplier(s) who undertook Discovery and Alpha phases? As published on Contracts Finder, the contract for the Discovery and Alpha Phases was awarded to Valtech UK Ltd.
6. Please can you provide details of the work done to date? What was delivered in Alpha? Where were the outcomes or points identified from the GDS assessment to take forward in Beta? Please see the answers provided to clarification questions 1 and 2.
7. Who is the supplier supporting the legacy Blue Badge solution? As published on Contracts Finder, the provider of the current Blue Badge Service is Northgate Public Services.
8. Which software development technologies have been used during the Alpha Phase? Does the authority have a preference for a particular technology stack? Please email rob.thomas@dft.gsi.gov.uk for access to the Technology Stack document. The Government technology code of practice should be followed where possible. Link: https://www.gov.uk/government/publications/technology-code-of-practice/technology-code-of-practice
9. This is a correction (incorrect link provided) to the response provided to Q1 (above). Question was

1. Will DfT share the outputs of Alpha Phase with potential bidders?
Yes, please follow this link to the Additional Information document https://docs.google.com/document/d/1WXSQaFRbAsVxSi-9GlBKKQsmgYa3-7MOA1ea__90k5I/edit?usp=sharing
10. This is a correction (incorrect link provided) to the response provided to Q2 (above). Question was:

Does DfT have more detailed information for potential bidders regarding the Beta requirements?
Yes, please follow this link to the final Show & Tell https://docs.google.com/document/d/13DQaLswZ7i5h5SwucboU5VJ103fxrgTHd9G9UJmByVs/edit?usp=sharing
11. We were wondering if you could kindly provide us with access to the Technology Stack document and to the Alpha/Discovery Prototypes for the above referenced opportunity. As per previous response regarding the Technology Stack information, further details can be obtained by emailing Rob.thomas@dft.gsi.gov.uk or Jason.thrupp@dft.gsi.gov.uk

Information pertaining to the Alpha prototypes can be obtained via the same route
12. Please can you confirm some of the following clarifications: Was the discovery/alpha carried out by the DfT or a 3rd party? If 3rd party, is the 3rd party allowed to participate in this procurement? Was a COTS product or platform used for alpha/beta? If yes, what is the product? The Discovery and Alpha phases were carried out between DfT and Valtech. Any supplier signed up to the DOS Framework can bid for the Beta contract.

We have yet to undertake Beta. For Alpha we developed a Prototype therefore no build has yet taken place.
13. How long did the Alpha phase last, and how much was the total cost spent on Alpha? The Alpha phase lasted 10 weeks and cost approximately £260k.
14. Will you make available all the Discovery and Alpha outputs prior to the ITT, including any requirements/user stories backlog (such as in JIRA or another tool)? Please see the answers provided to clarification questions 1 and 2. The Alpha S&T document includes the outputs, requirements and user stories. All available information will be handed to the successful bidder once the contract has been awarded.
15. There will be hosting costs for deploying on Gov UK Paas - will these be covered separately by the department or are they to be included in this BETA in which case can the Department state what they will be Any hosting costs will be covered separately by the Department.
16. The details say that 'This contract is to take forward a Beta phase and transition in to a Live Service' can you clarify if this contract is for the Beta phase as far as public Beta and a Beta assessment or also includes work to take the service up to and through a Live assessment This contract is for the Beta and the Beta assessment only. The Live Service provider will be responsible for taking forward the Live Service assessment. However, this contract will require the Beta supplier to undertake activities to enable the service to go live.
17. Presumably the budget range capped at £2,670,000 is based on a business case. Please can the department provide the business case. If the business case is not available please can the department provide the detail behind this estimated budget. The Business Case is not available for cascade. The Beta cost is based on DfT’s projected Beta team and the different rates associated with the DOS Framework.
18. Would you please be able to share the following:
a) The technology stack document
b) Access to the prototype
c) Full size images of the User Journey (show and tell slide 12)
d) Full size / legible image of the Beta backlog (show and tell slide 23)
Please see Q&A #11. Further details can be obtained by emailing Rob.thomas@dft.gsi.gov.uk
19. Are the technologies in the technology stack document mandatory for Beta phase or can they be replaced by suitable equivalents in line with the government technology code of practice? The technologies in the Technology Stack document are Alpha recommendations only.
20. It states the latest start date is 9th April, can we ask what the procurement timetable is expected to be between 19th Feb and 9th April in order to award the contract? Evaluation of Initial Proposals is anticipated to be completed on 28th February 2018 with notifications being sent to all Tenderer’s shortly after. The deadline for Full Proposal from shortlisted Tenderer’s is anticipated to be on 19th March 2018. Notification of the outcome is anticipated to be sent to the shortlisted Tenderer’s on 29th March 2018.
21. Can we ask how price will be assessed? Yes. Price will be assessed in line with the weightings set in the opportunity advert. Price has a 20% weighting overall. The lowest tender price will receive the full 20% weighting available, with subsequent higher tender prices receiving a proportion of the 20% weighting available. For more information on the scoring mechanism that must be used, please read the Supplier Guidance Document available here https://www.gov.uk/guidance/digital-outcomes-and-specialists-suppliers-guide
22. For the skills and experience questions, are you asking suppliers to provide their organisational experience in these topics? Yes
23. In regards to 'Demonstrable evidence of adhering with Customers’ relevant policies and standards' can you just give examples of which types of policy and standards this refers to? Tenderers should provide examples of where they have worked on previous projects and there has been a need to align their work to meet the customer’s internal policies and/or standard, for example Data Sharing, IT Security.