TfL Revenue Collection Services - Project Proteus 24412

Opportunity overview

Transport for London (TfL) through its trading arm Transport Trading Limited (TTL) are procuring the Proteus Contract for the revenue collection services which will require a supplier to take over, operate and maintain the TfL fare collection system; provide the associated revenue collection services; and, in partnership with TTL and TfL, develop, enhance and expand these to meet future needs.

Awarded to

Amounts belong to published awards or contracts. Where several suppliers share one value, it is labelled as shared and is not a supplier-specific allocation.

Classification

• CPV72000000 — IT services: consulting, software development, Internet and support
• CPV30144400 — Automatic fare collection
• CPV30200000 — Computer equipment and supplies
• CPV34980000 — Transport tickets
• CPV48000000 — Software package and information systems
• CPV50316000 — Maintenance and repair of ticket-issuing machinery
• CPV51000000 — Installation services (except software)
• CPV60200000 — Railway transport services

Lots

• Transport for London's (TfL's) ability to collect fares revenue is fundamental to its achieving and maintaining financial sustainability. Critical to achieving this objective is to ensure we are effectively collecting the revenue by ensuring the revenue collection system and services are available and reliable. The Proteus Contract will ensure that operating costs are efficient, economic, and sustainable; and deliver value for money and support the delivery of the TfL change and innovation programme. The revenue collection system (the System) supports the Mayor's Transport Strategy objective of making better use of technology to improve the public transport experience, by providing simple and effective payment options to customers. TfL, through TTL, owns and has made significant investments in the System. The contractor under the Proteus Contract will be required to take over the system and become responsible for its maintenance, operation, development, enhancement and expansion in order to and deliver excellent customer experience and respond to business needs. The System supports legacy magnetic stripe tickets, Oyster (the TfL closed-loop, proprietary smart card system), contactless payment cards and ITSO (the UK national smart card specification). Currently the System incorporates: • c. 8,500 buses; • c. 1,000 London Underground, Overground, DLR and National Rail stations; • c. 4,000 Oyster Ticket Stops; and • 7 TfL Visitor Centres. Customers can travel seamlessly between different modes of transport using smart cards, magnetic tickets or contactless. Oyster Pay As You Go (PAYG) balances can be topped-up and tickets purchased conveniently either via ticket machines in stations, at Oyster Ticket Stops, or via digital channels (web and app). The System's back office collects all transactions securely ensuring best-value charges are applied for PAYG travel and are presented to customers in a transparent manner. The main ticketing products are: • PAYG on Oyster and contactless. Customers are charged for each journey made and benefit from daily and weekly capping; • Season tickets on Oyster. These comprise bus and tram season tickets and Travelcard season tickets which are valid on buses and all rail services within the zones purchased; and • Singles and Day Travelcards, which are issued on magnetic ticket stock. Prior to the COVID-19 pandemic, each year the System supported around 4 billion journeys comprising: • 2.2 billion bus journeys; • 1.4 billion Tube journeys; • 0.3 billion journeys on TfL Rail and London Overground; • 0.1 billion journeys on DLR; • PAYG travel on Tram and River services and the London Cable Car (around 0.03bn journeys combined); and • approximately 0.5 billion journeys on National Rail services in London. The System comprises of five main elements: • Front Office Assets: Broadly, ticket gates, retail, and validation devices used by customers to purchase and validate travel products and access the transport network as well as associated network equipment to transmit data. In addition, revenue inspection devices. • Data Landing: A collection of IT equipment that passes data bi-directionally between the front office assets and the back office. • Back Office: A collection of IT equipment that manages the various smart card transactions, customer accounts, billing, and settlement processes. This is split into Oyster, contactless and ITSO systems. The contractor under the Proteus Contract will be responsible for all Oyster and ITSO system support and Levels 1 and 2 for contactless, while TfL undertake Level 3 support for that part of the System. • Digital Channels: The customer web and mobile app channels are operated by TfL and interface to the System back-office. • Retail System: Management of xPERT retail devices at Oyster Ticket Stops, management of the network of Oyster Ticket Stops, and Oyster card enablement and management of bulk ticket sales. The data landing and back-office systems are currently located in two Tier 3 data centres, one within the M25 motorway and one just outside of the M25. The contractor under the Proteus Contract will have responsibility for systems integration for the integrated revenue collection system and service. This responsibility includes but is not limited to; the operational and technical integration of modules of the System, the safe introduction of new or changed technologies and services, ongoing activities to identify and address obsolescence, and to manage faults and incidents as they should occur in day-to-day operation of the system. As systems integrator, the contractor under the Proteus Contract will be responsible for working with TfL as technical authority and with other TfL contractors and interfacing parties to ensure the performance of the services is maintained throughout the lifetime of the contract. As an example, wide area networking and data centre networking are operated and maintained by separate suppliers to TfL. The Proteus Contractor under the Proteus Contract will be the custodian of the System and will be responsible for performing preventative and reactive maintenance; for the management of the assets, obsolescence and refresh to ensure the continued reliable performance of the System; and its development, enhancement and expansion. During the life of the Proteus Contract, we anticipate that there will be a number of changes, the key planned changes expected to be delivered during the Proteus Contract term include: • Hina Rail Reader Rollout: The Hina Rail Readers will be manufactured, tested and be readily available for the Proteus Contractor to implement onto the rail estate; • Payment Account Reference (PAR): This is a unique identifier associated with a specific cardholder PAN and this change will follow-on from the Hina reader deployment and will involve the Proteus Contractor. This change will allow us to link mobile devices with the payment card, allowing the interchangeable use of payment devices; • Account Based Ticketing / FTP5: This is our programme that will make Oyster an account based system. Initially this is likely to be a proof of concept involving design and back-office development work which we will lead on. This change will involve significant upgrade to our retail assets, changes to the reader to support the new risk management models, changes to the RID software as well as decommissioning the legacy Oyster system; • Revenue Inspection Device (RID) Replacement and Enhancement: This is the replacement of the current handheld device for revenue inspection. It is expected to be a broadly like for like device upgrade to the android platform device. We expect the next device may need to additionally include the ability to check barcode tickets; • Cobalt: TfL are currently running a procurement to replace iBus, the on bus Automatic Vehicle Location system that is used for service control and driver communications, and which is the source of live bus arrivals data. This is expected to result in the replacement iBus2 system. Part of the scope of iBus2 is a driver console which will replace the bus Electronic Ticket Machine (ETM) now that paper tickets are no longer issued. To be ready for this, we are developing Project Cobalt, which will prepare the revenue collection system to support iBus2. The Cobalt project has several stages and will run in parallel to the Proteus Contract transition in line with the iBus2 delivery: o Firstly, Cobalt will decouple the reader from the ETM, allowing the reader to be entirely independent; o Secondly, it will create the interface between the bus reader and the iBus2 system; and o Finally, once iBus2 has been delivered, the ETMs will be removed from buses during the iBus2 deployment, will be decommissioned, along with the bus garage equipment that supports the ETMs and the data flows to them. It is expected that the Proteus Contractor will be responsible for the decommissioning work for both the ETMs and the bus garage equipment; and • Front-office and Back-office refresh: The front-office and back-office will require performance assurance activities throughout the term of the contract and these changes will be driven by the Proteus Contractor's performance assurance plans. The Proteus Contract will enable potential future revenue collection services (and the provision of associated systems and ancillary services), including, but not limited to, in relation to the following: supporting the DfT National Ticketing strategy/aspirations, Heathrow Express services, new emerging forms of mobility including micro-mobility, mobility as a service, new ticketing and fare payment solutions, and commercial utilisation of revenue collection data.Value not stated