Data services

Tender description

Data as a Service — Journey Time Data (DaaS-JTD) is the first new and improved data source to be procured as part of the data roadmap project within TfL's SITS programme (details of which can be found within the SITS DaaS-JTD Market Brochure to be provided with SQ). The primary objective of the DaaS-JTD procurement is for TfL to acquire a real-time data feed (within 3 minutes of the end of each 5 minute interval as a minimum) of full point-to-point vehicular journey time data, mapped to a major road junction geography defined by TfL as the CORN. In addition, TfL is seeking options for mode split (between cars, freight, etc.) and, where beneficial, for a secondary enriched dataset. All data will be delivered to TfL's architecture via an API connection. Service delivery will be phased as follows: 1) Implementation services (circa 90-days); 2) Data services (following successful delivery of implementation service) — 24 months. TfL is seeking to award a single contract for the services. Through DaaS-JTD, TfL is seeking a full point-to-point vehicular journey time dataset, delivered as close to real time as possible (but within 3 minutes of the end of each 5 minute interval as a minimum). The data received from DaaS-JTD will provide a journey time view of the London road network within the Common Operational Road Network (CORN) as defined by TfL and further explained in the DaaS-JTD Market Brochure. The data will be provided for all vehicle classes/modes combined (with options for modal split) and will be geographically and temporally comprehensive. It will act as a critical base data layer for TfL and will be used to support and validate existing data and future datasets. DaaS-JTD is part of the Data Roadmap project within the SITS programme. Through DaaS-JTD, TfL is looking to procure a dataset that: 1) Covers the CORN in its entirety; 2) Is snapped to a GIS definition of the road network provided by TfL based on OS Highways; 3) Is delivered via an API into TfL’s wider SITS architecture; 4) Provides a feed of the required data in as close to real-time as possible (but within 3 minutes of the end of each 5 minute interval as a minimum); and 5) Offers innovative options, including for modal split (between cars, freight, private hire vehicles, etc.) and a delayed secondary feed of enriched data (including all processing, patching, etc.) where beneficial. Key delivery constraints for this procurement are that no new on-street infrastructure shall be installed (either by TfL or the service provider) to capture or transmit data and no service provider data platform is required as TfL expects to perform analysis and fusion of the raw data with other internal datasets. The procurement and delivery of DaaS-JTD will be undertaken in 3 stages: 1) Tender process – historical datasets (representing the real-time data provision for a designated period) will be provided by each bidder and evaluated alongside details of how the required services will be provided and the price for those services to select a Service Provider to work with; 2) Implementation phase – TfL will work with the successful bidder, leading a 3-month period for implementation and testing of the solution to ensure that the data is being delivered as required; and 3) Ongoing provision of data services – subject to successful completion of the implementation phase, the successful bidder will commence a 2-year data services provision period (which may be extended at TfL’s discretion for up to an additional 2-years). The indicative contract value provided in Section II.1.5) and Section II.2.6) assumes a maximum contract value of 1 500 000 GBP which covers the value of all potential spend that could go through the contract over the whole contract term including the full contract extension provisions, the delivery of any options and any future service enhancements. This value has been increased from that originally identified in the earlier PIN to allow the opportunity for provision of further granularity in the datasets during the life of the contract. Tenderers should read the supporting procurement documentation released with this contract notice, which details the requirements and the commercial contracting principles. TfL will welcome all tenderer solutions that can meet the requirements and deliver within the constraints set out in the procurement documents.