Print Friendly, PDF & Email
DVDP width=

In addition to the legal agreements, there is also a standard for the 'technical' connection between the parties: the TOMP API.

The success of MaaS, Mobility as a Service, depends on good services for people traveling by train, bicycle or shared transport. Smooth cooperation between governments, MaaS providers and mobility providers is a must for this. That is why the five largest municipalities in the Netherlands, several bicycle and scooter operators and MaaS platforms recently published a new version of the model contract.OpenWheels Model Partner Agreementlaunched, the National Access Point for Mobility Data reports.


Until recently, Maas providers made separate agreements with mobility providers for agreements on mobility. This meant a lot of work and a lot of time, at the expense of the customer's service. Agreements had therefore already been made in a number of large cities for two-wheelers, such as shared bicycles and shared scooters. These agreements were laid down in the 'Open Bike II' model contract.


In the spirit of 'Open Bike II', there was a strong need to continue the cooperation around the standard contract and to broaden it to shared cars and taxis, the four-wheelers. 42 mobility organizations have recently contributed to expanding and standardizing the cooperation agreements within 'OpenWheels'. Including: Donkey Republic, MaaS Global, Gayio, Cargaroo, Sustainable-emotion, Turnn, Nazza, Urbee, HTM, I&W, ANWB, TCA, Tier, 9292, Greenwheels, Mywheels, Automicle and Radiuz.

The structure of 'OpenWheels' has remained the same as the previous model contract. Various themes, such as liability, have been further developed and improved. In addition, each individual appendix has been expanded with its own sample text. The new version provides the legal connection between mobility providers and MaaS providers.

Read also  Government employees: green light for more sustainable travel and cycling is rewarded

technical agreements

In addition to the legal agreements, there is also a standard for the 'technical' connection between the parties: the TOMP API. To plan, book and pay for a trip in a MaaS app, a lot of data has to be exchanged. The TOMP API enables this to be done in the same way with the same language between all MaaS providers and mobility providers. This standard is an open source and standardized interface (link) between mobility providers and MaaS providers. By means of the legal (OpenWheels) and technical (TOMP-API) connection, the parties involved want to make MaaS as efficient as possible.


NTM, it National Access Point Mobility Data, will support the technical MaaS standards from January 1, 2023. The National Access Point for Mobility Data is the place where governments and market parties can publish, find and use mobility data. This concerns data on roads, public transport, parking, waterways, shared mobility and other relevant data in the field of mobility. 

Related articles:
Calendar pack