IT services: consulting, software development, Internet and support

Tender description

TfL is seeking to appoint a provider to develop a system capable of ingesting data from micromobility operators in London to provide TfL and participating London boroughs with near real time (up to 1 minute latency) visibility of activity across London and informative analytics. Such a system will support network performance optimisation and long-term transport planning decisions in London. The provider’s system shall be developed in compliance with the mobility data specification or General Bikeshare Feed Specification and enable 2-way data sharing between micro mobility operators and TfL and London boroughs. Over the course of the pilot, the provider shall support TfL’s ongoing relationship with operators and ensure that TfL and boroughs have access to the data they need as data needs evolve. This contract is for a provider to deliver an 18-month data-sharing pilot between micromobility operators in London and TfL, with several London boroughs participating as users. Summary of requirements: — develop application programming interface (APIs) to enable 2-way data sharing between micromobility operators and TfL/London borough users, — solution must be able to ingest as near as possible to real-time data and share this with TfL/boroughs within 1 minute of receiving the data, — required data from operators: —— locations of all dockless micromobility hire vehicles; —— unique vehicle identifiers; —— vehicle type for each vehicle; —— propulsion type for each vehicle; —— vehicle status (available for hire/out of service); —— journey start data; —— journey end data; — develop a front-end dashboard displaying this data to users. Users shall be provided with secure, role-based access and shall be able to filter historic and real-time data by: —— operator; —— vehicle type; —— propulsion type; —— borough; —— time; —— any other categories as request by TfL/boroughs over the course of the contract. — data can be downloaded and stored by TfL and boroughs as needed for analytical purposes, — TfL and London boroughs able to communicate with operators and supply operational information (e.g. network availability information and policy updates), — the solution should be scalable and come with the option of adding further standard features or developing customised features, — the provider shall support TfL in onboarding boroughs to the pilot and providing technical support to all users throughout the pilot, — the provider shall support TfL’s ongoing relationship with operators and ensure that TfL and boroughs have access to the data they need as data needs evolve, — the provider should use a standard data format such as mobility data specification (MDS) or General Bikeshare Feed Specification (GBFS), — the provider’s solution should be compatible with a range of devices, including desktops, laptops, tablets and smartphones, — the provider shall provide training to TfL and borough users at the start of the contract, as new users are added and as required for any new features, updates or other changes, — compliance with the requirements of the General Data Protection Regulation (GDPR) and the Data Protection Act 2018 or any amendment or re-enactment from time to time or national replacement of such legislation, — ‘Data minimisation’: the provider will need to work with TfL in defining the specific scope of data collected from operators and aligning this with clear purposes of use, to ensure collection of the minimum data required.