When you're riding the bus or the train, an unexpected delay is the last thing you need. If transit agencies want to know how well they're doing and how they can improve service, they have to track how reliable their service is for riders.
But not all reliability metrics are created equal, writes TransitCenter. Some agencies track their performance in a way that's much less rider-friendly than others:
At the moment, the [New York] MTA and many other agencies tend to use indicators of success that reflect the concerns of the people who actually run subway or other systems. These include on-time performance and the average distance a train car travels between mechanical problems.
But those measurements might not actually indicate whether the agency is delivering good service to riders. For example, regarding subway delay, the MTA relies heavily on a performance metric known as “wait assessment,” defined as the percentage of train arrivals that cause passengers to wait at least 25 percent longer than expected.
Wait assessment has two major problems. First, it is not obvious what it means to have a “good” wait assessment score. If the A train has a wait assessment score of 85 percent, what does that mean for riders? Second, wait assessment is indifferent to how late a train is or how many riders are affected by its lateness. On a line with service every four minutes, a gap of six minutes between trains in the Bronx at 6 A.M. is equally as “bad” as a gap of 15 minutes between trains passing through Grand Central at rush hour.
TransitCenter says Boston's MBTA has adopted a metric more in line with international best practice, one that captures what matters to riders:
There is already a performance metric that does a much better job than wait assessment. It’s called excess wait time, or EWT for short.
EWT measures how much extra time passengers wait for a train or bus compared with the ideal scenario of every vehicle running at scheduled frequencies. This gives it major advantages over wait assessment.
For starters, EWT records delay in minutes rather than as a percentage, which captures the problem of delay for riders much more accurately and intuitively. As a result, long gaps in service that cause big rider delays are weighted more heavily than small delays. Additionally, EWT weights delay by the number of people affected, so a service problem during rush hour counts as a bigger negative than an equivalent service delay on Sunday morning.
Not only has Boston moved toward a more rider-centric metric, it's working on publishing the data in an open format. TransitCenter has supported the development of a data tool to assess the reliability of New York City's bus routes based on the EWT standard. The more agencies that collect this data, release it an open format, and use it to improve service, the better.
Elsewhere on the Network today: Greater Greater Washington reports the extension of the D.C. Streetcar may have dedicated lanes -- addressing a key shortcoming of the existing project. Bike Portland notes that drive-alone rates are falling in greater Portland, even in suburban areas. And The Political Environment considers whether Great Lakes states outside of Wisconsin will use their authority to stop a plan divert Lake Michigan water to a sprawling Milwaukee suburb.
