Department for Transport

Street Manager Beta to Live

Incomplete applications

Incomplete applications
5 SME, 3 large

Completed applications

Completed applications
4 SME, 2 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 6 January 2020
Deadline for asking questions Monday 13 January 2020 at 11:59pm GMT
Closing date for applications Monday 20 January 2020 at 11:59pm GMT


Opportunity attribute name Opportunity attribute value
Summary of the work The winning supplier will be required to:

• provide a multi-disciplinary team to continue developing, managing and supporting the Street Manager service.
Latest start date Tuesday 31 March 2020
Expected contract length 24 Months
Location London
Organisation the work is for Department for Transport
Budget range

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The new Street Manager service for planning and managing roadworks is going live on 1 April 2020. This is when all LAs, utility companies and contractors will be mandated via legislation to use it.

This contract is to take the service through continuous improvement and build of a backlog, transition into a fully Live Service as defined by GDS, provide service support and maintenance, and other services to users including invoicing.
Problem to be solved Current systems used for managing road works were developed in the 1990s. Street Manager is replacing these with a single service to plan and manage road works. It is for registered users from LAs and utility companies. Open data on works will be published. The service has been in Public Beta since 1 November 2019.

This contract is to deliver the service backlog, including open data; iterate the service;, support the continuous improvement of the service; and provide service support. The supplier will need to provide admin support to invoice users, onboard new users and manage user accounts. They will also need to pass the GDS Live Assessment.
Who the users are and what they need to do The users are:

• utility companies, including planners/schedulers, administrators, compliance officers;
• local highway authorities, including network managers, inspectors, permitting and noticing officers;
• contractors, including agents and supervisors, site managers;
• central and local government, including policy officers, analysts and statisticians, local politicians and councillors; and
• data customers.

They need to plan works; raise and approve street works permits; record reinstatements; carry out inspections; and monitor performance.
Early market engagement No early market engagement has taken place with suppliers for this requirement.
Any work that’s already been done Discovery was in 2017; Alpha in 2018; Beta since mid 2018; private Beta since May 2019; public Beta since 1 November 2019. All users will be using the service by March 2020.
Existing team The supplier will be working with the DfT colleagues in London, as well as user representatives from Local Authorities and utility companies. The core team is:

Sally Kendall – DfT Service Owner
Paul Chandler – DfT Product Owner
Anthony Ferguson – Senior Responsible Owner (London)
Toby Staton-Bevan – DfT Project Manager
Current phase Beta

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Albany House, Petty France, London, SW1H 9EA
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 London.

We are used to working with development teams based on other locations, using smart working tools such as Slack and Zoom.
Security clearance Baseline (BPSS).

Any role with System Administrator-levels of privileged system access will require SC Clearance. The same standards will apply to any contractor or sub-contract as part of the supply chain.

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.

Please note, a presentation may be required at stage 2 of the evaluation.

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 through GDS service assessments
  • 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 and providing service support.
  • Be able to deploy an effective multi-disciplinary team able to start work no later than 31 March 2020.
  • Demonstrable evidence of excellent planning, coordination, communication and project management (using Agile) skills.
  • Have demonstrable experience of delivering and supporting IT services that has thousands of users using Agile.
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.
  • An understanding of the policy and approach the government and the data community are taking with data and open data and of the benefits this provides

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

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-Live phase including how service support will be provided (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 - 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 and Utilities in using the new service (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%)
  • Experience of transparent and collaborative decision making (2.5%)
  • Experience of taking responsibility for their work and resolving problems effectively (2.5%)
  • Proposed approach for working remotely (and co-located where possible) as part of the DfT Project team. (2.5%)
Payment approach Fixed price
Additional assessment methods
  • Case study
  • Work history
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Can you advise whether there was a supplier involved in the development to date? Yes a supplier has been involved in the development stages.

More information can be found at:
2. Can you clarify the technology upon which Street Manager is based and whether any existing software provider is currently providing support and development services? Or is this fully developed and supported 'in house'? Street Manager is built on the following key technologies:

• NodeJS 12+ microservices
• AWS, terraform
• Kubernetes, kops
• PostgreSQL

An existing software provider is currently providing support and development services.
3. “This contract is to deliver the service backlog, including open data”, What does ‘open data’ mean in this context DfT plan to publish summary data on live and planned works via open data platforms.

This summary data will include, but not be limited to, the location, date, time and type of work. High level designs will be available from the start of the contract.
4. Is the contract deemed to be outside IR35? Yes this contract is outside of IR35.
5. "The supplier will need to provide admin support to invoice users, onboard new users and manage user accounts."

Is this functionality already present or is it within the backlog?
The approach, process and functionality for onboarding new users and user management is in place and will continue through the contract. Support to invoice users will need to be established from the start of the contract.
6. “This contract is to take the service through continuous improvement and build of a backlog”

Is there a well formed and reviewed backlog which the PO has crafted in place or will the supplier be expected to define the backlog? If the backlog needs to be defined has time and cost been included in the budget to enable this? Have all non-functional requirements been captured?
A mature backlog will be in place from contract start which includes functional and non-functional stories. This backlog will need to be maintained for functional and non-functional stories and further matured over the cause of the contract.
7. Will the supplier be expected to build upon / maintain the framework that has already been implemented? An architecture framework has been implemented and should be enhanced and maintained over the duration of the contract.