The Shared-Use Mobility Center defines Mobility-as-a-Service (MaaS) as ”a practice that integrates the travel options available to a user and offers them in a single interface, with a single payment mechanism” [1]. MaaS is, in a simplistic form, a business model that allows multi-modal platform integration of transportation options. However, how the model is executed is still a point of debate, and recent failures of proposed systems throw MaaS further into doubt. In 2017, as a relatively new concept, there was much uncertainty in the core characteristics of MaaS [2]. This uncertainty continued through 2021 with no unified, agreed upon single definition of MaaS; pointing to an underestimation of what riders and users need and suggesting that an integrated trip planner may be enough to satisfy needs [3]. Currently, little progress has been made to unify MaaS as a concept and successfully launch a fully integrated system. Policy and regulatory barriers remain, and incorporating local characteristics will be crucial for MaaS to succeed [4].

In the US, cities like Pittsburgh [5], Minneapolis [6], and Tampa [7] have launched their pilot MaaS programs. These pilot programs, however, only included limited transport services, mainly due to difficulties with public private collaboration, funding, cyber security, and lack of attractiveness to transit users, auto users, and older populations [4].