MaaS Tender Tip #1

MaaS Tender Tip #1: Clearly define the roles of your stakeholders

If you work for a city and you’re interested in launching a new MaaS network, there are many different things to consider before you start sending out requests for tenders, such as: 

What types of MaaS solutions are out there? How can you transform a mobility-as-a-service network from a theoretical project into a tangible, product-based service that people actually want to use? Which stakeholders should be included in your MaaS networks, and what roles should they be allowed to play?  

Before your tender is written, the proverbial floodgates have been opened and the bids start pouring in, it’s helpful to have a clear answer to the above questions. We’ve tapped into our expert network and asked our experienced team to compile a list of essential tips for cities looking to launch their own private-public MaaS network. Without further ado, here’s MaaS tender tip #1.

MaaS Tender Tip #1: Clearly define the roles of your stakeholders

The stakeholders in any MaaS network can be divided into four main groups, with few exceptions: you (the city), your tech or software provider, MSPs, and third parties. 

The City

Cities are the backbone of MaaS systems. The role of the city is to own and oversee the entire MaaS platform; you’re the one who had the idea of simplifying and streamlining your mobility system to provide a valuable service to your citizens, after all. 

Cities should manage: 

  • Data. Cities should own all the data generated by a MaaS platform. This lets cities keep the responsibility of improving and enhancing the mobility network, assuring equitable MaaS growth, and making smart, data-informed decisions. 
  • Contractual relationships. You’re the unbiased project managers helping to organize this MaaS network; contracts should lie within your realm of responsibility.
  • Physical infrastructure. You have it, maintain it, expand upon it as necessary and own this topic. This includes the building of new mobility hubs and universal charging stations.
  • End user (people!) relationships. Who understands the people living in a city better than the city itself? The city is best positioned to manage promotions, advertising and user implementation and acquisition strategies. 

The Tech Provider

Some cities like to try and build their own tech team in-house. Their attempts are often unsuccessful. That’s for the simple reason that while they’re working on so many other aspects of building a MaaS platform, cities don’t have the time and resources to develop a capable tech team. That’s where your MaaS tech/software provider should step up and assist you. 

  • Platform setup and configuration. It’s your provider’s job to create flexible, modular platform architecture that can handle any integration. They should build a white-label app and brand it with your city’s logos and colors – your users need a seamless, stylish app to engage with your mobility platform. 
  • Journey and route planning. Tech providers should offer a multimodal routing engine tailored to the city’s specific needs. This also includes real-time journey planning that offers optimal routes according to traffic conditions and other factors, including maps.
  • Back office management. Cities obviously want to measure the success of their mobility platforms, and to do that, they need the help of strong back office tools that can handle customer service requests, provide solid analytics, and deal with fraud detection and GDPR rules. 
  • Testing, training and maintenance. One of your tech provider’s most vital tasks is managing platform operations. That means everything from testing the platform pre-launch, to training team members on how to use the platform, to fixing bugs and maintaining the platform long after your users are cruising around town on it. 

The MSPs

MSPs, aka mobility service providers, are the kick scooters, shared cars, taxis, bicycles and any other shareable, privately owned vehicles that want to be integrated onto your platform. These companies should manage:

  • Technical integration. MSPs are responsible for a smooth integration and opening their APIs.  
  • Commercial terms. MSPs should be willing to integrate deeply into your platform, meaning their services should be bookable and payable through your new app.
  • Operations, maintenance and branding. MSPs manage the locations and upkeep of their vehicles and of course continue to promote and maintain their own brand reputation.

Other Third Parties

Last but most certainly not least, other “third parties” are crucial components of any MaaS platform. They have their own highly specific topics to focus on:  

  • Single-sign on (SSO) functions. This authentication service provides a seamless, easy login process.
  • Payment service providers. PSPs enable payment structures across all vehicle and mobility types, from purchasing bus tickets to paying for scooter rides. 
  • Ticketing providers. No ticketing providers, no in-app digital tickets for your users!
  • Document/ID verification. To validate driver’s licenses for car and moped sharing or rentals, you’ll need to integrate a dedicated document verification service into your platform. 

    That’s it – the four main categories of stakeholders and their uniquely important roles have been clearly defined. That’s a great first step towards writing an excellent MaaS tender.

    Stay tuned to our blog and social channels as we share more on our MaaS tender tip series in the weeks to come. (Next up: defining your mobility offering!)

    For more information on how we help cities launch and grow mobility networks, get in touch or check out our webpage.