Minnesota Department of Transportation

511 Travel Info

Transit in Minnesota

Wadena County Transit but

Request for Information

Regional Mobility as a Service Platform

The Office of Transit and Active Transportation (OTAT) in support of its Greater Minnesota Shared Mobility Program is seeking information on how an interested contractor could help build all or part of a Regional Mobility as a Service Platform (MaaS).

The purpose of this RFI is to solicit feedback from technology experts and other stakeholders on the building of a Regional MaaS.   OTAT is exploring piloting a Regional MaaS in partnership with select Greater Minnesota transit agencies and private shared mobility service providers as a proof of concept to build a statewide platform. The MaaS platform would allow residents and visitors to plan trips, purchase and redeem fare/tickets, and receive real time updates on trip status on public transit and private sector shared mobility providers. In addition, vehicle routing, projected and real world trip data, and ridership information generated by this platform will be used to assist local, regional, and state planners and policymakers on transit service changes and public policy changes to improve service delivery and operational efficiency.

MnDOT’s Office of Transit and Active Transportation has received the following questions regarding the RFI from potential request respondents.

April 14, 2020
Question: Is that 11:59 AM or PM that the document is due?  I am assuming PM.
MnDOT Response: Yes.

April 15, 2020
Question: I see that the submission deadline is 4th May.  However, I couldn't find an email address to submit our documentation - should I send this completed RFI directly to you?  Or is there another email address?
MnDOT Response:  Yes. RFI submissions should come to me [elliott.mcfadden@state.mn.us].

Question: Please clarify when submittals to MnDOT for the RFI for Regional Mobility as a Service Platform are due.
Page 1 states “All proposals must be received at the address listed above on or before 3:00 P.M. Central Time on June 16, 2020.”
Section 4.2 states “Written information regarding this request are due no later than 11:59:59 CST, May 4, 2020.”
MnDOT Response: The State Register has lists all the published requests for all state agencies in Minnesota. Page 1 is a different request.
Our RFI starts on page 33 of the PDF of the Register. 11:59:59 on May 4, 2020 is the deadline.

April 21, 2020
Question: I am inquiring about the due date for your Regional Mobility as a Service Platform RFI. Is the due date June 16th or May 4th? Can you also please clarify if the due date for questions is May 1st? I came across this RFI in the Minnesota State Register document. Is there a standalone RFI document?
MnDOT Response: The question regarding the RFI due has been answered on our RFI question response page in the response from April 15, 2020. Regarding the May 1 date, that is the deadline to submit any clarifying questions to MnDOT that a potential responders to the RFI has about the RFI. Currently the RFI is only published in the State Register, Volume 44, Number 42 dated April 13, 2020. Our MaaS RFI begins on page 1181 of the this volume of the Register (page 33 of the PDF online.)

April 27, 2020
Question: I'm writing to ask if you can add me to your mailing list for changes for the Minnesota DOT - Office of Transit and Active Transportation (OTAT) Request for Information (RFI) for Regional Mobility as a Service Platform.
MnDOT Response: Thank you for reaching out to us. All updates on the RFI are posted on MnDOT’s Transit page. We are not planning to send any updates via e-mail list at this time.

 

April 30, 2020
Questions from vendor:

  1. By regional MaaS we assume you mean Urban, Sub-Urban, rural and intra-Urban?
  2. Will the MaaS Platform be open to private MaaS Operators to provide commercial MaaS services to their subscriber base (Whim, Mobility-X, etc.)
  3. Are you looking to own the platform or would you be looking to reduce the CAPEX and look for a SaaS model?
  4. What elements of regulation at OTAT looking to impose on MSPs to help control the holistic transport management network? Are you looking to limit the areas and times MSP can operate in order to protect public transport services?
  5. What do you envisage the process for onboarding, managing and offboarding private MSPs and MOs on the platform?
  6. Who would be responsible for the management of financial risk?
  7. Are OTAT anticipating the ability to generate revenue from the model via fees and subscription services, or are they looking to make this cost neutral?
  8. Are OTAT anticipating having one public agency MaaS App or will multiple apps have access to the platform?

MnDOT response:

  1. Yes, the regional MaaS will include a variety of community types in a spectrum from urban to rural.
  2. The RFI is our opportunity to understand how technology might solve the problem we are trying to solve: build a platform that allows residents and visitors the ability to plan, book, and track trips across all shared mobility services in the covered region. OTAT would like to see a solution that provides as much use as is feasible of data standards and interoperability to allow the consumer functionality of the MaaS platform to be available in as many consumer platforms as possible, not just the agency MaaS consumer app. We are asking companies in this space to respond with their recommendations of the best models to achieve this and how their technology would play a role.
  3. The RFI is our opportunity to understand how technology might solve the problem we are trying to solve: build a platform that allows residents and visitors the ability to plan, book, and track trips across all shared mobility services in the covered region. In addition, we want this solution to allow easier analysis of trip data to improve overall level of service for non-SOV options. OTAT has not yet determined the desired ownership model for this project. We are asking companies in this space to respond with their recommendations of the best models to achieve this and how their technology would play a role.
  4. OTAT is looking to build a technology platform that facilitates the planning, booking, and trip tracking of all participating shared mobility providers. Regulation of such services would remain the purview of existing regulatory bodies relevant to each service. While data from the platform may help inform policy makers as they set or change policies, regulating service providers will not be in the scope of this project.
  5. We are looking for solutions that incorporate data standards and interoperability to facilitate onboarding and management. In that light, we are asking companies in this space to respond with their recommendations of the best models to achieve this and how their technology would play a role.
  6. Mobility service providers would remain financially liable for the delivery of services as they currently are outside the MaaS platform. Within the scope of planning, booking, and trip tracking, we are asking companies in this space to respond with their recommendations of the best models of financial risk that balances the lowest possible risk to MnDOT with what is feasible in the current market place.
  7. OTAT is asking companies in this space to respond with their recommendations of the best models to achieve our goal of building a regional MaaS as a proof of concept for a statewide MaaS platform. These models could include revenue sharing, revenue concession in exchange for service (revenue neutral), or an investment from MnDOT in the building and ongoing management of services. Responses should identify which option or options they would recommend for this project. OTAT will use these responses to better understand the advantages and disadvantages of each approach and whether they are economically feasible in the existing marketplace and funding sources.
  8. While the development of an agency MaaS consumer app is part of the planned scope of this project, OTAT would like to see the consumer facing functionality of the MaaS platform be as interoperable as possible for other MaaS consumer applications and mobility service providers who wish to add this functionality to their customer applications.

Questions from vendor:

  1. Is it possible to grant an extension for the deadline in order for us to provide a more comprehensive response?
  2. Are you able to share estimated budget information you will have for this project? 

MnDOT response:

  1. We are not planning to extend the RFI response deadline at this time. OTAT is exploring timely funding opportunities for this project and will need the information by the May 4, 2020 deadline to help inform how we wish to proceed.
  2. The RFI is our opportunity to understand how technology might solve the problem we are trying to solve: build a platform that allows residents and visitors the ability to plan, book, and track trips across all shared mobility services in the covered region. In addition, we want this solution to allow easier analysis of trip data to improve overall level of service for non-SOV options. We are asking companies in this space to respond with their recommendations of the best models and scope to achieve this and how their technology would play a role.