This opportunity is closed for applications

The deadline was Friday 24 July 2020
Department for Transport

Traffic Regulation Order Data Model (TRO-DM) Alpha/Beta

9 Incomplete applications

8 SME, 1 large

10 Completed applications

4 SME, 6 large

Important dates

Published
Friday 10 July 2020
Deadline for asking questions
Friday 17 July 2020 at 11:59pm GMT
Closing date for applications
Friday 24 July 2020 at 11:59pm GMT

Overview

Summary of the work
An Alpha study to develop a TRO data publication and distribution system by:

further validation of TRO-DM and reviewing its scope

assessing deployment options – including existing market capabilities and costs/benefits

prototyping to validate preferred options

developing necessary technical and service planning artefacts

recommending Beta designpass GDS assessment
Latest start date
Tuesday 1 September 2020
Expected contract length
Alpha - 4 months, there is no commitment for Beta at this stage.
Location
No specific location, eg they can work remotely
Organisation the work is for
Department for Transport
Budget range
£250k - (Alpha)

About the work

Why the work is being done
The DfT’s ‘Future of Mobility: Urban Strategy’ prioritises a regulatory framework that evolves with transport technology and advocates data sharing to improve the transport system. Traffic Regulation Orders (TROs) are made under the Road Traffic Regulation Act 1984 and set and enforce rules for the use of a road (speed limits, loading and unloading restrictions, parking bays and restrictions etc). The legal procedures for making TROs are paper based, process heavy, costly and TRO data provision is inconsistent and non-standardised. TRO digitisation would support new services, digital mapping, and the digital infrastructure for connected and automated vehicles.
Problem to be solved
Local authorities should be able to publish standardised and open TRO data for anyone to access, use and share. The DfT has procured the draft TRO-DM (UML format) to provide consistent and digital data. A further technical solution is required – developing a TRO data publication/distribution system which is flexible, open and usable and built on this model. This system will be determined by iterative testing, optioneering (supported by cost benefit analysis/market testing), and prototyping. The TRO-DM scope needs to be reviewed to consider sharing data at earlier TRO process stages, data licensing and the relationship with international data development.
Who the users are and what they need to do
The main users are highway authorities who have powers to make TROs, but applicants from utility/construction companies apply for temporary orders and special event organisers apply for special event orders. Interested parties, including members of the public, need to access information on the changes being made.
Sat-nav and digital map providers are key data customers who need to report changes to the road network, including road closures, to road users digitally and in real-time.
The DfT is the national policy holder and will need to consider a revised regulatory framework to ensure local authorities comply with the technical solution.
Early market engagement
The DfT commissioned TRO Discovery (https://www.geoplace.co.uk/downloads/TRO-Discovery-Summary-Report.pdf) reported in 2019 and had input from 200 individuals from 90+ organisations. From surveys undertaken, the Discovery estimated that c15,000 TROs and 40,000 Temporary TROs are produced annually.

The TRO Policy Alpha project was completed 2020 and the report has not yet been published (we hope to make available to shortlisted suppliers during this procurement). The ambition is to create a new legislative process that will meet the current and future needs of the wide range of users that interact with the TRO regime.
Any work that’s already been done
The draft DataModel for TROs was commissioned by the DfT as a key output of the Discovery – a free resource compatible with the international TRO landscape (see: BPA_TRO_Data_Model_User_Guidance.pdf). DfT acknowledge that this earlier work has not supplied the technical artefacts (such as JSON/XML schema, API definitions) and service management definition required for the deployment of a recommended option.

This model has been validated by eight local authorities and the three main market operators involved in providing TRO-linked data, but requires further validation, review and potential revision supporting publication of TRO data at several stages of the TRO development process.
Existing team
TRO-DM Alpha is being developed jointly between the Smarter Traffic Management team in the Traffic and Technology division of DfT and project consultants Harrod Booth Consulting who are retained and paid for by DfT.
Current phase
Alpha

Work setup

Address where the work will take place
In accordance with COVID Safe Working Guidance the work should be conducted at the supplier’s own site or remote working locations.

If necessary, also Department for Transport, Great Minster House, 33 Horseferry Road, London; Windsor House, Victoria Street, London; and supplier’s own premises.
Working arrangements
To be discussed.
Security clearance
DfT require BPSS clearance.

Additional information

Additional terms and conditions
Additional terms and conditions (Optional) (100 Words)
All output will be owned by the Department for Transport, which may share it under a suitable Open Licence. All material/outputs derived from the contract shall be the intellectual property of the Department for Transport.

Tenderers shall note the DfTc 'Digital Service Architecture - Principles and Standards’ which is available at:
https://drive.google.com/file/d/12GZIM8EcyRk1FgOjy3xiSNdQT5GDvTAq/view?usp=sharing

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 data Alpha project delivery with an Agile approach that is relevant to this specification
  • Experience of designing and implementing data management based on a web workflow [data architects
  • Evidence of successful delivery of data Alpha project of equivalent complexity
  • Evidence of successful completion of an alpha GDS assessment in an equivalent complex data project
Nice-to-have skills and experience
  • Experience in developing transport data standards
  • Experience in road transport legislation

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
5
Proposal criteria
  • Approach and methodology
  • Technical solution
  • Value for money
  • Team structure
Cultural fit criteria
  • Work as a team with our organisation and other suppliers
  • Be transparent and collaborative when making decisions
  • Share knowledge and experience with other team members
Payment approach
Capped time and materials
Additional assessment methods
  • Case study
  • Work history
  • Presentation
Evaluation weighting

Technical competence

70%

Cultural fit

10%

Price

20%

Questions asked by suppliers

1. Who’s in the incumbent and how long they have been the incumbent?
DfT do not have an incumbent supplier, however, Buchanan Computing and Harrod Booth Consulting have both assisted DfT in validating the draft TRO data model.
2. Who's on the panel?
DfT are yet to agree the panel.
3. Is there is an incumbent on this project who might have supported you on a similar project in the past?
DfT do not have an incumbent supplier for this Project, however, Buchanan Computing and Harrod Booth Consulting have both assisted DfT in validating the draft TRO data model.
4. Please can you confirm the scope of the procurement will cover a subsequent Beta (subject to successful Alpha and scope agreement)?
This procurement does have scope to continue with the successful supplier through to the Beta Phase of the Project, however DfT are not obligated to do so.
5. Please can you clarify the requirement of "Experience of designing and implementing data management based on a web workflow data architects"?
By this we mean that there should be evidence of experience and success in designing and implementation of data management systems and data exchange mechanisms using internet and web-based technologies and solutions. It is expected that the evidence will demonstrate the contribution of experienced data architects in design and deploying systems comparable in complexity to that expected for TRO data publication and exchange.
6. How will DfT evaluate the Essential & Nice to Have Questions? Will the Nice to Have's questions be used as part of the total score or only to differentiate between suppliers that have identical Essential Scores and then to get to a short list of 5 suppliers?
The Nice to Have's questions will be used as part of the total score.
7. Can you confirm whether question 2 – it appears to be missing a closing bracket and possibly additional text after ‘[data architects'
Question 2 is only missing a closing bracket, i can confirm no text is missing.
8. Can you clarify the difference between questions 3 and 4 – both appear to ask for the same evidence, namely evidence of the completion of an [GDS] Alpha in a data project of equivalent complexity. Is this the case / intent?
Question 3 requires the bidder to provide evidence of delivering a data Alpha project of equivalent complexity to DfT’s Traffic Regulation Order Data Model.

Question 4 requires the bidder to provide evidence of completing a GDS Alpha assessment for a digital data project.