DVDP width=

Europe's leading event for sustainable urban mobility kicks off a new version.

Extensive research into existing specifications and standards on the market is the basis for the TOMP working group to release the TOMP-API 1.4. In the meantime, the TOMP API has gained recognition at national, European and international level and has become an important standard. And despite that, it was time for a new release that reflects both the changes in the mobility sector and the continued emergence of shared mobility and new modes of transport.

Policy conference

The annual POLIS conference in Brussels, within walking distance of the European Parliament, offers cities and regions the opportunity to showcase their transport performance to a large audience of mobility experts, practitioners and decision-makers. The perfect place to present the international cooperation between members of the TOMP working group. An in-depth analysis during the preparation for the 'deep dive' sessions during the POLIS conference on data, standards and specifications form the basis of this new version.

(Text continues below the photo)
TOMP API version 1.4 release

The latest release of TOMP-API includes the 'one-stop booking process' for both public transport and private-public mobility that can significantly reduce implementation costs. In addition, the full attention to the 'last mile' with a scooter, shared bicycle or traveling further from a station with a (shared) bus that stops on the corner of the street or even in front of the door. For example, extra information about the connection can be added to a booking. 

plan, book and pay

The eye-catcher is better interoperability and integration with other specifications and standards that describe the current mobility offer, such as NeTEX, GTFS, APDS and GBFS. TOMP-API 1.4 offers better support for planning, booking and paying for a taxi. The support of passenger characteristics (CROW ) forms the basis for efficient use in target group transport. In short, the latest release of TOMP-API is better for all modes of transport and provides a better user experience for travelers.

Read also  NTM working with data standards Mobility as a Service
(Text continues below the photo)
Better support for planning, booking and payment.

about TOMP-WG

Started three years ago as a project of the Ministry of Infrastructure and Water Management to support the roll-out of Mobility-as-a-Service (MaaS). TOMP-WG quickly became the place where Carriers – TO or Transport Operator and MaaS Providers MP – data aggregators, data producers, public or private sector entities and other non-profit organizations can collaborate. The TOMP-WG (Transport Operator, MaaS Provider – Working Group) is a joint initiative to create a standardized language through an API.

(Text continues below the photo)
Members of the TOMP working group during a boat trip in Ghent offered by Pitane Mobility.

The social added value of a uniform data standard for MaaS is well known. This findings from a research of Ecorys, an international research and consultancy agency, show that the TOMP API represents added value for society. This added value is visible, among other things, in the form of efficiency benefits for carriers and MDVs, and a better travel experience for citizens. The TOMP API also contributes – indirectly via MaaS – to achieving the social policy objectives. 

In the long term, there will also be a business motive for (partial) carriers to invest in the TOMP API. At the same time, there is not (yet) a convincing business case for carriers to start using the TOMP API immediately. This conclusion corresponds with the observation that (partial) carriers active on the market do not (yet) use the TOMP API on a large scale. Preconditions are a strong increase in the use of MaaS and guaranteeing the user-friendliness of the TOMP API. 

Read also  NTM working with data standards Mobility as a Service
Related articles:
Maas newspaper
Print Friendly, PDF & Email