Mobility as a Service (MaaS) is a technological transformation happening right now in the world of transportation. It’s a model which responds to the changing needs of people living and working in cities and towns.

By 2030, 60% of the world’s population is expected to be living in urban centres, so particularly in these areas, the demand for transit is continuously growing. This growth places an ever-increasing strain on the limited road space available, bringing congestion and poorer air quality, as well as more pressure on public transport already full to capacity.

MaaS seeks to deliver a solution to these problems. Broadly, it follows the transformative trend of empowering the consumer, giving them a greater amount of choice.
More choice = more convenience!

Accessed from a smartphone app or accessible web interface, MaaS enables users to easily book and purchase end-to-end journeys across multiple modes of transport. This requires the integration of routing data, booking functionality, e-ticketing and payment systems, as well as real-time traffic and service disruption alerts, into a single, user-friendly platform.

The success of MaaS implementation therefore absolutely depends on the co-operation of stakeholders; local authorities, transport providers in both public and private sectors, transport and infrastructure planners, and payment processors. In order for the eco-system to work, all actors must work in partnership.

The MaaS platform provider must give its users access to a full range of transport operators, their assets and services, and the ability to map, book and pay-for their journey in a single transaction (either in the form of a service subscription or pay-as-you-go).

Data is at the heart of MaaS. The model is enabled by data, each part requiring a level of interoperability to allow the necessary flow of information (usually via API gateways) and choices available to the user, updated in real-time. Much of the data is drawn from different sources into a single platform to provide the information needed. Some examples of the types of data needed at the various stages in the MaaS user journey are noted in the 2018 Parliamentary Report on MaaS:

• PLAN: routes, transport mode options, feasibility of travel, journey segment durations, availability, facilities, stations & stops, pricing.
• BOOK: pricing, availability, subscription status, e-ticketing, payment.
• TRAVEL: real-time traffic/service disruption alerts, service crowding, GPS tracking.
• POST-TRAVEL: recording of journey durations, journey feedback, compensation processing.

Collecting usage data from consumers of MaaS will also help stakeholders to match network and asset demand and supply, and optimise the network correctly based upon these new insights.

Because of this, Data Provider(s), acting as brokers to fulfil the data and information sharing needs of these stakeholders, will play an intrinsic role in the MaaS ecosystems of the future. The 2018 Parliamentary Report on Mobility as a Service recommends data sharing amongst stakeholders be heartily encouraged, else risk that schemes will never breakout of pilot stages and become successful.