European Traffic Management System (ERTMS) Early Works - Stage 2 (Develop) Support Services
Awarded
Key facts
- Closing date
- Not stated by the buyer
- Buyer's estimated value
- Not stated The buyer's own estimate, not income to you.
- Procedure
- Competitive flexible procedure
- Notice type
- Contract award notice (UK6)
Decision brief
Taken from the buyer's published notice (shown as written, shortened where long). Tenderpatch has not added to or interpreted it. Always read the official documents before bidding.
- How bids will be scored
- Not stated in the notice.
- Conditions of participation (what you must show)
- None published in the notice. They may be in the tender documents.
- Contract length and extensions
- Period not stated.
- How to submit
- Not stated in the notice.
- Tender documents
- No document links in the notice. Use the official notice link.
New to public tenders? Plain-English guide to this page
- Framework
- An agreement that sets terms for work the buyer may order later, often from several suppliers. The value shown usually covers the whole agreement, not one job.
- Open for bids / closing date
- You must submit by the closing date and time, normally through the buyer's own online portal. Late bids are normally refused.
- Clarification questions
- A deadline for asking the buyer questions about the tender. It is earlier than the closing date.
- Conditions of participation
- What the buyer asks suppliers to show before they can be considered, such as experience, insurance or accreditations.
- Bids are scored on
- How the buyer will compare bids, usually a split between price and quality. A 60/40 split in favour of quality means the cheapest bid will not necessarily win.
- Lots
- A tender can be split into parts. You can often bid for only the lots that suit you.
- Area (ITL)
- The buyer names an official statistical area for where the work is, not a street address. Check the tender documents for the actual sites.
- UK4 and other notice codes
- Official codes for the type of notice. A "tender notice" means bids are being invited.
General explanations written by Tenderpatch, not part of this notice.
Description
LSPH’s current TVM430 signalling system is reaching obsolescence, creating increasing operational, safety and resilience risks. Without intervention, system reliability and lifecycle issues are expected to significantly impact network performance from the 2030s. Stage 1 of the upgrade programme—delivered with SYSTRA—produced an Operational Context Document, a Technical Strategy with long- and short-list options, and a Strategic Outline Business Case (SOBC) in WebTAG format. This completed the Rail Network Enhancements Pipeline (RNEP) Stage 1: Determine. LSPH and its stakeholders are now progressing to RNEP Stage 2: Develop, requiring specialist external consultancy support throughout 2026. Stage 2 will resolve key strategic questions, including the preferred technology solution for replacing TVM430, the funding approach within the HS1 regulatory and concession framework, the suitability of innovative commercial models, strategic opportunities, and the project delivery and scope choices that minimise whole-life cost. Additional strategic issues may be identified collaboratively during the process. Summary of requirement: Stage 2 has an estimated duration of six months, extending if an option to complete on-site surveys is executed, and aims to evaluate a range of delivery options for introducing ERTMS on High Speed 1. The assessment will include but not be limited to benefits, costs, deliverability, and operational impacts. The objective is to secure full stakeholder agreement on a single, coherent project delivery strategy for ERTMS implementation. To complete Stage 2, the appointed consultant will deliver: • Confirmation of the preferred technical option, commercial delivery model, funding route, and integrated project delivery model. • Long-list and short-list optioneering across technical, commercial, and funding dimensions to determine the integrated delivery model. • A whole-life cost estimate for the integrated delivery model. • A delivery schedule through to entry into service and handover to maintenance. • A comprehensive RAID (Risks, Assumptions, Issues and Dependencies) register in the authority’s format. • All Deliverables from the Deliverables Register (to be provided). • Satisfy paragraphs A.6 to A.11 of the latest Rail Network Enhancements Pipeline guidance to enable progression to the next phase. Required Outcome: All relevant stakeholders support and agree to the implementation of a single, coherent project delivery strategy for ERTMS on High Speed 1.