At this point a more than legitimate question arises: does the three arrows diagram allow us to talk about MaaS?
The answer is yes; the three arrows diagram allows it, but on one condition (necessary but not sufficient): that the transport services present consist of more than a single mode. This is because a product serving the end user must intrinsically contain many – ideally all – of the available mode of transport on any given territory. MaaS means having a holistic view of mobility.
In the event that the three arrows diagram remains unimodal, the horizontal arrow at the top cannot be called MaaS, but will have other names: “app of a public transport agency”, “e-commerce of a single operator”, “FlixBus app” just to give some examples. There is nothing wrong with these products, on the contrary, they respond to specific needs of digital users and, if implemented artfully, they can give rise to projects with particularly interesting results. But MaaS is another thing: without multimodality one cannot speak of MaaS.
What is seen in the first part of this article, that is the construction of the three arrows diagram, refers to a single mode of transport (whatever it is). In this second part we talk about MaaS, or the integration of multiple transport services that are put into the system for the end user. Let’s make an analogy to better understand this difference. In the first part of the article the parallel is with an e-commerce of a single manufacturer (suppose, for example, of shoes), in the second part, that of MaaS, the analogy is with a marketplace – think about Amazon – in which the products of several suppliers are harmonized, as well as items and services belonging to different categories (shoes of each brand and model, but also sweaters, hats, books, watches, appliances, etc.). MaaS means all types of bus services (urban, suburban, etc.) but also metro, train, parking, bike sharing, micro mobility and so on and so forth.