Insights

MaaS: what Mobility as a Service means for sharing operators

Bus, train and shared vehicles in one app: what MaaS actually is, which levels of integration exist – and what connecting to a transport association delivers in practice.

Roland Kainbacher – Porträt Roland Kainbacher 8 min
Illustration: Anbindung an Mobility as a Service

Mobility as a Service, or MaaS, describes the idea of bringing different transport offers together in one application: bus, train, rental bike, carsharing and taxi not as separate worlds each with its own app and account, but as one continuous journey. Search, book, pay – in one place.

Why this matters for sharing operators

A carsharing service does not compete with the bus. It competes with the second car. And that only becomes dispensable when the combination of public transport and shared vehicles works reliably in everyday life – including for the trip the bus is not suited for.

For you as an operator that means two things: you reach people who would never download your own app. And you become part of an offer that public authorities actively support, because it matches their goals.

The levels of integration

MaaS is not a state but a scale. Literature usually distinguishes five levels:

  • Level 0 – no integration. Every provider on their own, own app, own account.
  • Level 1 – information. One app shows which offers exist and where. Booking happens with the provider.
  • Level 2 – booking and payment. The journey is booked and paid in one app, across providers.
  • Level 3 – offer integration. Packages and subscriptions bundling several modes – a monthly fee including carsharing kilometres, for instance.
  • Level 4 – societal goals. Offers are steered politically to shift traffic.

Most real projects sit between level 1 and 2. Even that makes a noticeable difference to the visibility of a regional service.

An example from Vorarlberg

For our partner caruso carsharing we implemented the connection to the Vorarlberg transport association. New and existing customers can register for the annual public transport ticket and for caruso at the same time. That annual ticket doubles as the chip card used to lock and unlock the vehicles.

This is a good example of what MaaS means in practice: not a grand platform, but connecting two existing offers so that one step disappears for the user. Anyone who already holds the annual ticket needs neither a second card nor a second registration.

Black caruso carsharing vehicle in front of an ÖBB commuter train with VMOBIL branding
Car sharing at the station: anyone holding the annual ticket unlocks the vehicle with the same card. Photo: Verkehrsverbund Vorarlberg

How the integration works technically

For a sharing service to appear in someone else's app, three things have to flow:

  • Locations and availability. Where are vehicles, which are free, what type are they? Open formats have become established here, GBFS in bike sharing for example.
  • Booking. The reservation is created from within the other app. The TOMP API is the most common standard between operators and MaaS platforms.
  • Identity and billing. Who is this person, are they allowed to drive, and who issues the invoice? Usually the most demanding part.

Through the Zemtu interface, locations, availability, rates and trip data can be read and user accounts synchronised. If you offer carsharing as an additional service, you can also arrange for your customers to receive a single monthly invoice covering everything.

What to watch out for

MaaS brings reach, but it changes your position. Three points to settle beforehand:

  • Customer relationship. When booking runs through another app, that app knows your customers – and you may not, directly. Clarify which data you receive.
  • Pricing authority. Who sets the price users see, and who carries a platform's discounts?
  • Liability. Who is responsible when someone books through the platform who would never have been approved by you?

Our position

We consider MaaS to be right – shared mobility only becomes an alternative to owning a car when it connects with public transport. We build the integrations our partners need and take part in projects heading that way. What we do not do: push our customers into a platform that takes the customer relationship away from them.

[Editorial note: this needs the concrete MaaS projects Zemtu is currently involved in and which standards are already implemented – TOMP API, GBFS, others. Please verify before further use.]