Planning

Mobile Smart Ticketing (MST)

RAIL DELIVERY GROUP LIMITED

This public procurement record has 2 releases in its history.

PlanningUpdate

13 Apr 2026 at 11:55

Planning

09 Apr 2026 at 07:35

Summary of the contracting process

The Rail Delivery Group Limited, based in London, United Kingdom, is progressing through the planning stage of a tender process titled "Mobile Smart Ticketing (MST)", centred around the development of digital-first ticketing for the rail industry. This initiative is part of the Utilities sector and involves the migration of physical ITSO media to a digital format, aiming to reduce costs and enhance customer experience. The preliminary market engagement notice was published on 13 April 2026, with an email contact deadline for stakeholders to express interest in participating by 21 May 2026. Geographical areas targeted include several UK regions such as UKC, UKD, UKE, UKF, UKG, UKH, and UKI through to UKK, with the contract period anticipated to commence on 1 June 2026, spanning until 31 May 2030, subject to possible renewal until 2034.

This tender presents substantial opportunities for businesses involved in railway traffic control software development services, notably those with capabilities in secure digital ticketing solutions, mobile wallet ecosystems, and scalable national deployments. Companies with expertise in API-driven integrations, high availability systems, and monitoring capabilities aligned to rail standards stand to benefit. Additionally, businesses focused on interoperability across technologies and cost-efficient fulfilment strategies could find significant growth potential through participation in this initiative. The MST project encourages collaboration with industry partners to forge innovative solutions and explore a centrally orchestrated fulfilment layer, revealing further business expansion avenues.

Find more tenders on our Open Data Platform.
How relevant is this notice?

Notice Title

Mobile Smart Ticketing (MST)

Notice Description

The rail industry is progressing toward digital-first ticketing to reduce cost of sale, improve customer experience, and enable flexible products such as season tickets, PAYG and a roadmap toward single and return tickets. The Mobile Smart Ticketing (MST) initiative (migrating physical ITSO media to a digital format) aims to enable secure, standards-based ticket fulfilment to mobile devices. Initial launch will centre on a pilot for Season tickets, followed by PAYG, and then expansion into singles and returns. In addition, current fulfilment methods for rail (e.g. barcode, physical smartcard, paper) are isolated today, with retailers and integrators required to support multiple fulfilment technologies, each with distinct standards and operational overhead. Mobile Smart Ticketing offers the potential for the following: * Elimination of the downsides of current plastic ITSO cards which have to be obtained and updated prior to travel; * Customers will no longer have to use a separate app to view journey history and product validity; * Improved gate line speeds - customers will benefit from features such as NFC reader functionality, removing the need to unlock devices or open apps to pass through gates; * Over-the-air cancellations will also deliver enhanced fraud protection to the industry. A national rail pilot is targeted for delivery by mid-end 2027, focusing on: * Limited geography and/or Train Operating Company (TOC) deployment; * Season ticket products as initial use case to prove the technology and proposition; * Expansion path to PAYG. Beyond the pilot, RDG in collaboration with industry partners (e.g., FTR Programme, TOCs, etc) will develop a scalable roadmap to deliver singles and returns. Alongside the Mobile Smart Ticketing initiative, there is an opportunity to explore whether a centralised fulfilment orchestration layer could: 1. Reduce complexity for retailers/integrators; 2. Standardise interfaces across fulfilment media; 3. Lower long-term cost of sale; 4. This is exploratory and not a defined requirement of the pilot. Requirements are as follows: Functional Requirements * Support secure mobile ticket fulfilment aligned to ITSO Version 2.1.5; * Enable season ticket products at launch; * Provide clear roadmap to PAYG and singles & returns enablement; * Support lifecycle management (issue, update, revoke, renew, replace, etc); * Enable inspection/validation in existing rail environments. Technical Requirements * Compatibility with secure element-based implementations (DESFire); * Integration with existing retailing and RDG back-office systems; * Scalable architecture for a national deployment; * Support for multiple mobile wallet ecosystems; * API-driven integration model. Operational Requirements * High availability and resilience; * 24/7 customer support and recovery mechanisms (lost device, change of device, re-provisioning); * Enhanced monitoring and reporting capabilities; * Security and compliance aligned to RSP rail standards. Commercial Requirements * Transparent pricing model (setup, per-transaction, ongoing OPEX, lifecycle costs); * Scalable commercial structure for national rollout with economies of scale; * Clarity on licensing and third-party dependencies. Strategic / Future Requirements * Potential flexibility to support additional fulfilment media; * Potential to integrate with a central fulfilment orchestration layer; * Interoperability across TOCs and geographies.

Planning Information

To receive a copy of the MST MOI / MEQ please email Sam Stevens: sam.stevens@raildeliverygroup.com

Publication & Lifecycle

Open Contracting ID
ocds-h6vhtk-067e73
Publication Source
Find A Tender Service
Latest Notice
https://www.find-tender.service.gov.uk/Notice/033252-2026
Current Stage
Planning
All Stages
Planning

Procurement Classification

Notice Type
UK2 - Preliminary Market Engagement Notice
Procurement Type
Standard
Procurement Category
Services
Procurement Method
Not Specified
Procurement Method Details
Not specified
Tender Suitability
Not specified
Awardee Scale
Not specified

Common Procurement Vocabulary (CPV)

CPV Divisions

72 - IT services: consulting, software development, Internet and support


CPV Codes

72212140 - Railway traffic control software development services

Notice Value(s)

Tender Value
Not specified
Lots Value
Not specified
Awards Value
Not specified
Contracts Value
Not specified

Notice Dates

Publication Date
13 Apr 20261 weeks ago
Submission Deadline
Not specified
Future Notice Date
21 May 20264 weeks to go
Award Date
Not specified
Contract Period
31 May 2026 - 31 May 2030 4-5 years
Recurrence
Not specified

Notice Status

Tender Status
Planning
Lots Status
Planning
Awards Status
Not Specified
Contracts Status
Not Specified

Contracting Authority (Buyer)

Main Buyer
RAIL DELIVERY GROUP LIMITED
Contact Name
Available with D3 Tenders Premium →
Contact Email
Available with D3 Tenders Premium →
Contact Phone
Available with D3 Tenders Premium →

Buyer Location

Locality
LONDON
Postcode
EC4V 3DS
Post Town
Central London
Country
England

Major Region (ITL 1)
TLI London
Basic Region (ITL 2)
TLI3 Inner London - West
Small Region (ITL 3)
TLI35 Westminster and City of London
Delivery Location
TLC North East (England), TLD North West (England), TLE Yorkshire and The Humber, TLF East Midlands (England), TLG West Midlands (England), TLH East (England), TLI London, TLJ South East (England), TLK South West (England)

Local Authority
City of London
Electoral Ward
Castle Baynard
Westminster Constituency
Cities of London and Westminster

Further Information

Notice Documents

Open Contracting Data Standard (OCDS)

View full OCDS Record for this contracting process

Download

The Open Contracting Data Standard (OCDS) is a framework designed to increase transparency and access to public procurement data in the public sector. It is widely used by governments and organisations worldwide to report on procurement processes and contracts.

{
    "tag": [
        "compiled"
    ],
    "id": "ocds-h6vhtk-067e73-2026-04-13T12:55:28+01:00",
    "date": "2026-04-13T12:55:28+01:00",
    "ocid": "ocds-h6vhtk-067e73",
    "initiationType": "tender",
    "parties": [
        {
            "id": "GB-COH-08176197",
            "name": "RAIL DELIVERY GROUP LIMITED",
            "identifier": {
                "scheme": "GB-COH",
                "id": "08176197"
            },
            "additionalIdentifiers": [
                {
                    "scheme": "GB-PPON",
                    "id": "PMXW-9895-MJXN"
                }
            ],
            "address": {
                "streetAddress": "First Floor North",
                "locality": "London",
                "postalCode": "EC4V 3DS",
                "country": "GB",
                "countryName": "United Kingdom",
                "region": "UKI31"
            },
            "contactPoint": {
                "email": "sam.stevens@raildeliverygroup.com",
                "name": "Sam Stevens"
            },
            "roles": [
                "buyer"
            ],
            "details": {
                "classifications": [
                    {
                        "id": "publicUndertaking",
                        "scheme": "UK_CA_TYPE",
                        "description": "Public undertaking"
                    }
                ]
            }
        }
    ],
    "buyer": {
        "id": "GB-COH-08176197",
        "name": "RAIL DELIVERY GROUP LIMITED"
    },
    "planning": {
        "milestones": [
            {
                "id": "engagement",
                "type": "engagement",
                "description": "To receive a copy of the MST MOI / MEQ please email Sam Stevens: sam.stevens@raildeliverygroup.com",
                "dueDate": "2026-05-21T23:59:59+01:00",
                "status": "scheduled"
            }
        ],
        "documents": [
            {
                "id": "032151-2026",
                "documentType": "marketEngagementNotice",
                "noticeType": "UK2",
                "description": "Preliminary market engagement notice on Find a Tender",
                "url": "https://www.find-tender.service.gov.uk/Notice/032151-2026",
                "datePublished": "2026-04-09T08:35:19+01:00",
                "format": "text/html"
            },
            {
                "id": "033252-2026",
                "documentType": "marketEngagementNotice",
                "noticeType": "UK2",
                "description": "Preliminary market engagement notice on Find a Tender",
                "url": "https://www.find-tender.service.gov.uk/Notice/033252-2026",
                "datePublished": "2026-04-13T12:55:28+01:00",
                "format": "text/html"
            }
        ]
    },
    "tender": {
        "id": "ocds-h6vhtk-067e73",
        "legalBasis": {
            "id": "2023/54",
            "scheme": "UKPGA",
            "uri": "https://www.legislation.gov.uk/ukpga/2023/54/contents"
        },
        "title": "Mobile Smart Ticketing (MST)",
        "description": "The rail industry is progressing toward digital-first ticketing to reduce cost of sale, improve customer experience, and enable flexible products such as season tickets, PAYG and a roadmap toward single and return tickets. The Mobile Smart Ticketing (MST) initiative (migrating physical ITSO media to a digital format) aims to enable secure, standards-based ticket fulfilment to mobile devices. Initial launch will centre on a pilot for Season tickets, followed by PAYG, and then expansion into singles and returns. In addition, current fulfilment methods for rail (e.g. barcode, physical smartcard, paper) are isolated today, with retailers and integrators required to support multiple fulfilment technologies, each with distinct standards and operational overhead. Mobile Smart Ticketing offers the potential for the following: * Elimination of the downsides of current plastic ITSO cards which have to be obtained and updated prior to travel; * Customers will no longer have to use a separate app to view journey history and product validity; * Improved gate line speeds - customers will benefit from features such as NFC reader functionality, removing the need to unlock devices or open apps to pass through gates; * Over-the-air cancellations will also deliver enhanced fraud protection to the industry. A national rail pilot is targeted for delivery by mid-end 2027, focusing on: * Limited geography and/or Train Operating Company (TOC) deployment; * Season ticket products as initial use case to prove the technology and proposition; * Expansion path to PAYG. Beyond the pilot, RDG in collaboration with industry partners (e.g., FTR Programme, TOCs, etc) will develop a scalable roadmap to deliver singles and returns. Alongside the Mobile Smart Ticketing initiative, there is an opportunity to explore whether a centralised fulfilment orchestration layer could: 1. Reduce complexity for retailers/integrators; 2. Standardise interfaces across fulfilment media; 3. Lower long-term cost of sale; 4. This is exploratory and not a defined requirement of the pilot. Requirements are as follows: Functional Requirements * Support secure mobile ticket fulfilment aligned to ITSO Version 2.1.5; * Enable season ticket products at launch; * Provide clear roadmap to PAYG and singles & returns enablement; * Support lifecycle management (issue, update, revoke, renew, replace, etc); * Enable inspection/validation in existing rail environments. Technical Requirements * Compatibility with secure element-based implementations (DESFire); * Integration with existing retailing and RDG back-office systems; * Scalable architecture for a national deployment; * Support for multiple mobile wallet ecosystems; * API-driven integration model. Operational Requirements * High availability and resilience; * 24/7 customer support and recovery mechanisms (lost device, change of device, re-provisioning); * Enhanced monitoring and reporting capabilities; * Security and compliance aligned to RSP rail standards. Commercial Requirements * Transparent pricing model (setup, per-transaction, ongoing OPEX, lifecycle costs); * Scalable commercial structure for national rollout with economies of scale; * Clarity on licensing and third-party dependencies. Strategic / Future Requirements * Potential flexibility to support additional fulfilment media; * Potential to integrate with a central fulfilment orchestration layer; * Interoperability across TOCs and geographies.",
        "items": [
            {
                "id": "1",
                "additionalClassifications": [
                    {
                        "scheme": "CPV",
                        "id": "72212140",
                        "description": "Railway traffic control software development services"
                    }
                ],
                "deliveryAddresses": [
                    {
                        "region": "UKC",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKD",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKE",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKF",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKG",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKH",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKI",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKJ",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKK",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKC",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKD",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKE",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKF",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKG",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKH",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKI",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKJ",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    },
                    {
                        "region": "UKK",
                        "country": "GB",
                        "countryName": "United Kingdom"
                    }
                ],
                "relatedLot": "1"
            }
        ],
        "mainProcurementCategory": "services",
        "specialRegime": [
            "utilities"
        ],
        "aboveThreshold": true,
        "lots": [
            {
                "id": "1",
                "contractPeriod": {
                    "startDate": "2026-06-01T00:00:00+01:00",
                    "endDate": "2030-05-31T23:59:59+01:00",
                    "maxExtentDate": "2034-05-31T23:59:59+01:00"
                },
                "hasRenewal": true,
                "status": "planning"
            }
        ],
        "status": "planning",
        "amendments": [
            {
                "id": "033252-2026",
                "description": "Added a note about how to receive the MST MOI/MEQ, and set the contact email address to Sam Stevens, rather than the generic procurement email address."
            }
        ]
    },
    "language": "en"
}