September 28, 2022
Swiftly has been in the fixed route public transit game since, well, before Swiftly. One of our co-founders and my brilliant colleague, Mike Smith, spent decades in the transit software world fine tuning prediction models for hundreds of agencies around the world. He started Swiftly with a goal to deliver the absolute best predictive information for passengers - and we’ve done just that.
Our prediction algorithms leverage a variety of historical data as well as truly real-time vehicle location information. We iterate continuously on our prediction engine to reduce error and ensure passengers catch their ride.
And yet, there’s much more to great transit predictions than just accuracy.
You can hear best practices and new strategies for connecting with passengers in our recorded webinar, "Connect with passengers: Building passenger trust with 'real' real-time information," featuring speakers from Transit, IBI, and Swiftly.
Generating truly great real-time passenger information requires quite a bit more than predicting the predictable. It necessitates understanding the unpredictable, too.
We all know that transit doesn’t run in a vacuum. Life happens all around transit operations - operators don’t log into their onboard mobile devices, water main lines break and force detours, delivery trucks double park and slow corridors, and staff need unanticipated sick leave.
Similarly, riders don’t always search for information on an agency’s website or dedicated mobile app. They may have their own preferred third-party trip planning app, or they might rely on an SMS service or digital signage at stops.
So, while we pride ourselves on our extremely accurate real-time passenger predictions, we know that communicating service changes and getting information into people’s hands is just as important. Beyond the measurable accuracy of predictions, here are other key elements of great passenger info:
Predictions are ETAs for when a vehicle will arrive at your stop. But, what about all those vehicles that won’t? Service that isn’t running is just as important as the service that is.
Swiftly’s data engine can include cancellations, whether trips are canceled in the Swiftly dashboard or even in another system and fed in via GTFS-RT or Swiftly APIs.
And it’s a good thing it does: Cancellations account for the majority of Service Adjustments in Swiftly, and “reduced service” or “no service” make up more than 50% of Service Alerts reasons that flow through the system.
Knowing when service is explicitly canceled empowers riders to better plan their trips and builds trust with agencies; leaving riders to guess does the opposite.
Scrutinizing prediction accuracy is a worthy area of focus for any transit authority. As studies have shown, better ETAs reduce perceived wait time and can increase ridership. Yet prediction accuracy is really only a part of the story when it comes to communicating effectively with transit riders.
Real time passenger information must take into account the unpredictable: an AVL feed failing, vehicles that aren’t logged into an onboard system such as a CAD/AVL, and cancellations across different software systems. If we only focus on prediction accuracy, we can get caught up in looking at a fraction of the fleet instead of the holistic picture of service that passengers really care about.
See how Swiftly can improve service reliability, passenger information, and operational efficiency at your agency with an in-depth demo.