Lesson

Right-size your procurements and start your pilots at a manageable scale to minimize risk, suggests Florida DOT.

Florida DOT's evaluation report of a mobile ticketing app pilot offers suggestions and recommendations based off of its experiences.


06/01/2018
Tallahassee; Florida; United States


Background (Show)

Lesson Learned

The report summarized lessons learned during the deployment and offered recommendations for future operations.
  • Start small. The pilot was intentionally limited to include only a small subset of StarMetro's user base. This enabled the pilot to avoid any possible bugs in the application that might overwhelm the agency's limited customer service response and tech support ability.
  • Be flexible with the test plan. In order to gauge user adoption rates, it was decided during the testing period to add participants who expressed interest in the app, even if they had not pre-registered and filled out a pre-survey.
  • Commit to the pilot. The evaluation recommends conducting an initial pilot as part of a commitment to a permanent deployment, rather than as a temporary test. This avoids discontinuing services to customers that have grown accustomed to it, which may be unpopular with riders.
  • Be ready to deal with unexpected glitches. StarMetro found that its free WiFi points interacted in unexpected ways with the pilot technology. For example, the "captive portal" requiring agreement with Terms of Service inadvertently served to make Token Transit less secure, as it was easier to bypass security mechanisms when the app could not connect to the internet.
  • Right-size your procurement. The use of an "off the shelf" fare payment app allowed StarMetro to choose an app that had already been thoroughly tested. FDOT's report concluded that this likely led to an overall smoother experience than an in-house app might have had. The off-the-shelf option also worked particularly well for StarMetro as it is a relatively small transit agency with no unusual circumstances or fare structures that might necessitate a bespoke solution.
  • Consider technical needs when writing proposals. Survey results indicated that users strongly preferred seeing information within a single app. FDOT's report recommended that agencies require APIs and deep links in proposal responses, as these allow greater flexibility in integration.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

Mobile Fare Payment Technology Phase II: Final Report

Author: Hendricks, S.; S. Barbeau; A. Joslin; and C. Brakewood

Published By: Florida DOT Freight Logistics and Passenger Operations Transit Office

Source Date: 06/01/2018

URL: https://fdotwww.blob.core.windows.net/sitefinity/docs/default-source/content/transit/documents/bdv25-two-943-63-mobile-fare-payment-final-report.pdf?sfvrsn=4db2282a_0

Lesson Contacts

Lesson Analyst:

Ned Schweikert
Noblis
edward.schweikert
@noblis.org


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson ID: 2020-00955