Department for Transport – Office for Low Emission Vehicles (OLEV)

Discovery Phase – National Chargepoint Registry (NCR) 2.0

Incomplete applications

Incomplete applications
3 SME, 2 large

Completed applications

Completed applications
16 SME, 8 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Friday 6 April 2018
Deadline for asking questions Friday 13 April 2018 at 11:59pm GMT
Closing date for applications Friday 20 April 2018 at 11:59pm GMT


Opportunity attribute name Opportunity attribute value
Summary of the work The winning supplier will :
• Undertake a Discovery Phase to determine:
 specific user needs;
 how best to meet user needs; assessing;
 recent legislation (AFID/AEVB); and
 continuation of NCR:
• either in current/new form; and
• how best funded – either by OLEV or private sector.
Latest start date Monday 4 June 2018
Expected contract length up to 6 weeks
Location London
Organisation the work is for Department for Transport – Office for Low Emission Vehicles (OLEV)
Budget range Capped at £60,000

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The NCR is a database of publicly-available chargepoints for electric vehicles in the UK established in 2011. The database is freely open for those who wish to use the database, either by individual data users (e.g. electric vehicle drivers) or by business data users for their products (e.g. mapping smartphone apps, satellite navigation and route planning). The NCR management contract expires 30 April 2018 and OLEV requires the discovery of what the NCR users (current and future) needs, how best can these needs be met, and so determine whether to re-procure the NCR contract in its present or different form.
Problem to be solved OLEV’s policy objective, for the NCR, is to support electric vehicle uptake and address a perceived lack of chargepoint infrastructure by highlighting the presence of chargepoints across the UK. The NCR does not currently hold data on all the UK’s publicly-available chargepoints as network operators are not fully providing data. However, new legislative measures (The Alternative Fuels Infrastructure Regulations 2017 and the Automated and Electric Vehicles Bill) will require full data provision. The problem is how to best meet OLEV’s policy objective (as stated above) through effective working with data providers and users in complying with the legislative measures.
Who the users are and what they need to do Discovery will engage with a wide range of stakeholders to assess their needs:
• Data providers (usually chargepoint hosts or network operators) who need to be able to provide chargepoint data to the NCR (or otherwise); and
• Data users (individuals or businesses) who need to be able to download chargepoint information from the NCR (or otherwise) in a standard format.

We want to assess the best methods to facilitate these needs.

Additionally, we want to assess whether there is a need to provide a website to allow user access to chargepoint information from the NCR with a map interface.
Early market engagement An NCR Stakeholder Event was held in December 2017, engaging both data providers and users in separate sessions. Invitations were sent using direct contact and mailing lists and the event was promoted through Twitter and the NCR website with an online sign-up for the wider public.

Following introductions to the background and purpose, 8 key questions were posed and an online audience participation tool was used to collect views. After the event, further input was invited through an online survey posing the same questions and the results of both the direct engagement and the survey were compiled into a final report.

The event was supported and overseen by OLEV to ensure impartiality, and attracted approximately 50 delegates over the two sessions. Feedback on the day confirmed that the event was useful, even-handed and constructive. The benefit of having a single and definitive repository of information on public charge points was widely accepted, and some known issues with the current NCR in relation to accuracy, extent of coverage and integration with existing systems were identified as key weaknesses that need to be addressed.

A full report with event details and a transcription of all responses can be found at: .
Any work that’s already been done The NCR currently comprises of two components:
• A database (where the chargepoint information is held) []; and
• A website [] (including a map interface) that accesses the database.

Current regulations and legislation, in Parliament, for provision of user information on chargepoint infrastructure:
• consultation & response to the earlier proposed transposition of European Union Alternative Fuels Infrastructure Directive (AFID) ( [sections 1.65-1.68, particularly 1.67, on User Information]
• Regulations at
• Automated and Electric Vehicles Bill (AEVB) ( in place of the Modern Transport Bill [Part 2 section 11 on Information for users of public charging points]
Existing team The supplier will be working with the OLEV colleagues at Department for Transport in London. The team will be:
• Deputy Head of OLEV as Product Owner;
• Head of Infrastructure Team as Senior Responsible Owner; and
• Member of Infrastructure Team as Service Manager.
Current phase Not started

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Primarily at supplier’s own offices and, when necessary, at the Department for Transport’s office in Great Minster House,33 Horseferry Road, London, SW1P 4DR for meetings. Also it is envisaged that visits to users at their work locations will be required to see how they work in the real world.
Working arrangements The supplier is expected to engage closely with OLEV and external stakeholders (e.g. other HMG stakeholders, IT Security, internal Developers) on a frequent basis to fully meet the requirements. This is a full-time, 5 days a week arrangement based at supplier’s own offices and at DfT’s office to produce the relevant supporting documentation and develop the solution and product proposals. There are no expenses allowances associated with this work. Any ad-hoc or overseas expenses will require prior approval from DfT and will be treated on a case-by-case basis in compliance with DfT Expenses policy (available at full-proposal-stage).
Security clearance Preference is that supplier’s staff already have current Baseline Personnel Security Standard (BPSS) clearance.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions N/A

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
  • Demonstrable evidence of excellent planning, communication and project management skills
  • Demonstrable evidence of co-ordination and allocation of project resources
  • Demonstrable evidence of risk identification and mitigations
  • Demonstrable experience of quality assurance of project delivery
  • Demonstrable evidence of conducting and documenting user research, and iterating project work accordingly
  • Demonstrable evidence of working in an Agile way
Nice-to-have skills and experience Demonstrable evidence of knowledge of the plug-in vehicle industry including charging infrastructure challenges and strategies

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • Approach and methodology (weighting 10%)
  • Estimated timeframes for the work in the form of a Project Plan (weighting 10%)
  • Team structure for this project in the form of a Resource Allocation Plan (weighting 10%)
  • How risks and dependencies have been identified and approaches offered to manage them in the form of a Risk Register (weighting 10%)
  • How the proposed solution meets user needs (weighting 10%)
  • How the proposed solution meets OLEV’s policy objective (weighting 10%)
Cultural fit criteria
  • Experience of individuals successfully working with diverse stakeholders (such as Government Digital Service [GDS]), our organisation and/or other public/private sector customers (weighting 5%)
  • Experience of successfully working as a team with diverse stakeholders (such as GDS), our organisation and/or other public/private sector customers (weighting 5%)
  • Evidence of strategic thinking striving to deliver best possible solution/concept possible (weighting 10%)
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Work history
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. In the nice-to-have skills you have asked for "Demonstrable evidence of knowledge of the plug-in vehicle industry including charging infrastructure challenges and strategies". Most suppliers would struggle to have this evidence. Are you expecting suppliers to contact in someone with this knowledge in order to apply for this project? The ‘nice-to-have skill’ to be able to “Demonstrable evidence of knowledge of the plug-in vehicle industry including charging infrastructure challenges and strategies” is not essential and it is not necessary to buy in someone with this knowledge.
2. What is determining the length (6 weeks) for this Discovery project? 6 weeks seems too short for a large Discovery project like this. Especially when trying to engage with users and booking in to visit them and invite them to workshops. GDS allows up to 8 weeks for a discovery and we would even allow up to 3 months for a Discovery project of this size. This is not a large scale Discovery and it has been judged to be deliverable within the suggested period of 6 weeks.
3. Please could you confirm if you have users ready to participate in research activities? E.g workshops, user interviews. If users haven't been engaged it'll be difficult to complete this discovery within 6 weeks. We have not specifically arranged/selected any stakeholders for participation, however we have available a list of data users and data providers to the NCR. It has been judged to be deliverable within the suggested period of 6 weeks.
4. In the question about ‘evidence of project management’, what kind of methodology are you referring to? Does the process need to comply to the GDS Service Standard? We are seeking evidence of delivering and managing projects, particularly in the Digital space. Use of Agile methodology is preferable but not essential criteria for assessing this question. Compliance with GDS Service standards is essential.
5. Will any work on the NCR service be subject to GDS service assessments? Yes, Discovery outputs could potentially necessitate subsequent Alpha, Beta, Live phases and therefore we would expect all work to be subject to GDS service assessments.
6. In the question about ‘evidence of quality assurance’, does this relate to coding standards (e.g. testing code) or the way the project is managed? It seems unusual to focus on QA in a discovery project. This question relates to Project Management and successful delivery with appropriate governance and quality assurance. Not seeking to assess coding standards.
7. Will there be space in DfT offices for an integrated co-located team to work an collaborate? Space is not available on a full-time basis. User Researcher(s) will meet to work/collaborate with the OLEV team members (principally the Service Manager) as required/available.
8. Will the OLEV team be able to help with their contacts to recruit participants for research? Some help can be provided but there should not be sole dependency on OLEV having to recruit participants as it is expected that User Researcher(s) will suggest innovative ways to recruit participants for research
9. What will be the availability of OLEV team members (days per week)? The Service Manager will be available as required by agreement. Availability of other OLEV team members would be subject to an agreed project resource plan and wherever possible OLEV colleagues would be available.
10. Who developed and/or is maintaining the current NCR platform? The NCR was developed by previous incumbent, Next Green Car, and is maintained by the current incumbent, Cenex.
11. Will the provider get access to analytics and data related to the current NCR platform? Yes – the User Researcher(s) will meet with the current NCR managers at which information about the current NCR platform will be available.