Showing posts with label service disruption. Show all posts
Showing posts with label service disruption. Show all posts

Thursday, April 30, 2009

We Asked Metro ...

What they're specifically doing to prevent delays, and they answered.

Metro does not see the current amount of delays as requiring any kind of crisis response program. Makes you wonder where they've been for the past three days.
Instead, WMATA relies on "preventative maintenance," wrote a spokesman for WMATA in an email exchange.
“We never stop looking for ways to improve service and to decrease disruptions,” they wrote.
Every rail car is inspected daily for wear and tear, they wrote, adding that any areas of concern are repaired immediately. More detailed inspections are also performed on a regular basis, they wrote. Metro also inspects the tracks regularly and performs track maintenance nearly every weekend, according to the spokesman.
“Not all disruptions are attributable to car performance,” they wrote. “Many offloads can be attributed to door problems, and I think we all know that many door problems are caused by people who try to hold them open.”
The spokesman said that the percentage of trains per day that need to be offloaded is about half a percent and that of all the “door movements” per day, 99.999 percent are successful.
“Of course, the important train is the one you’re on at the time,” they said. “If that train is running one of the .5 percent of the trips not completed, it inconveniences as many as 1,000 people. It is a big deal, to you and to us.”
WMATA makes some good points. We tend to remember the suck-o-ramas, not the times when Metro worked.
And we've seen with our own eyes the impatient a-hole who pried the door open rather than wait another few minutes for the next train. We wonder, though, how often it's the passengers' fault. We asked, and WMATA doesn't keep data on that. Perhaps they should.
Also, despite a lot of evidence to the contrary, DC doesn't have a monopoly of jerks who pry open train doors. We've seen it in other cities, and while it may be amusing to see, it doesn't cause the trains to go out of service. We think WMATA needs to look into some more robust doors.
Given the recent spate of "switch" issues, perhaps WMATA could review it's track inspection procedures. But just don't use any of that track equipment the derails, please.
We also don't think WMATA is taking into account the ripple effects of door problems and breakdowns. We think 1,000 is a low estimate for the number of people affected by a rush hour breakdown. And if our Twittercaps are any indication, people react quite viscerally to a Metro malfunction.
WMATA doesn't seem to think it has an image problem, and this is disheartening. We fear that because of Metro's performance, more people will think like this:
@jiwest Why oh why is the Orange line so sporadic? I think I've had quite enough of no-car city life, thank you very much.
More cars is exactly what we don't need.
More on doors to come.

Other news:
Metro discusses budget woes on Capitol Hill (WTOP)
Great John Kelly piece in WaPo we can all relate to
Another Metro stop in Bethesda? (Gazette)
Major work to begin on 14th St. bridge (DC Examiner)


Photo: sudama

add to del.icio.us Add to Blinkslist add to furl Digg it add to ma.gnolia Stumble It! add to simpy seed the vine TailRank post to facebook

Tuesday, April 28, 2009

All Lines Appear To Suck Equally

Over the past six weeks, we've been documenting Metro's "disruption" reports. Granted, they're often cryptic and don't give an indication of the ripple effects one disruption can cause. Still, it's good WMATA reports them.
We've unscientifically documented 232 disruptions that appear to be serious enough to cause ripple effects and leave people thinking Metro sucks. We leave out reports like "train delayed because of door problem" because it sounds like that train was able, in the end, to move people. We also omit sick passenger issues since those aren't Metro's fault.
232 disruptions over 30 work days is an ugly record of disservice in our opinion. It's almost 8 per day.
That said, your odds of being victim to a Metro meltdown, you might think, vary depending on the line you're on. Here's the ugliness broken down by line:

Red Line: 90 disruptions (39%)*
Orange Line: 61 disruptions (26%)
Green Line: 32 disruptions (14%)
Blue Line: 31 disruptions (13%)
Yellow Line: 14 disruptions (6%)

But ... these numbers are startlingly in line with the percentage of Metro's deployed cars each line utilizes. These are from 2008 (page 12),

Red Line: 34% of cars
Orange Line: 24% of cars
Blue Line: 17% of cars
Green Line: 16% of cars
Yellow Line: 7% of cars

Basically, it appears all the lines have about an equal chance of ruining your day. Yeah, the Red Line gets a lot of the glory, but its screw ups are pretty much par for the course.

Metro's own Jan. 2009 findings about "on-time performance" ranked the Red Line first. Metro's measurements include only peak-service times.

Red Line: 95%
Orange Line: 93%
Yellow Line: 93%
Blue Line: 91%
Green Line: 90%


* Percentages are rounded


Tweet of the day:
@theKyleBogucki escalators were down in the metro, i watched a man stand on the bottom reading a news paper for at least 15 second before he noticed

Other news:
Metro Transit Police arrest suspects for breaking into cars at Branch Avenue

add to del.icio.us Add to Blinkslist add to furl Digg it add to ma.gnolia Stumble It! add to simpy seed the vine TailRank post to facebook

Friday, April 10, 2009

The Week That was April 1-7


Well, Metro doesn’t seem to want to get the April 7 data up on its site despite issuing a press release about how many people rode on April 9. The SIXTH most on a weekday E-VER! OMG! Wait til the WaPo gets a hold of that info! Major headline! It’s as if record ridership was the sole measure of success. Seriously?
As much as we’d hoped April would indeed be “No Delay” month, for the four work days (April 1-6) there were 26 disruptions of a serious enough nature that they probably pissed a lot of people off. If you want to see a complete list, click here. We’ve posted entire lists before, and frankly, they’re just too long. Since we’re missing April 7, we’ll add the average over the past month to the 26 and surmise that Metro probably had 34 disruptions last week. No sign of unsucking. UPDATE: There were 11 disruptions on April 7.
As we said, over the past month, Metro has averaged almost eight disruptions a day on workdays. For the cherry blossom related events (April 4-5), it was 4.5/day. At first we thought “wow” Metro stepped it up for the big event. They must have deployed only top flight drivers who can remember if they’re on 4, 6 or 8-car trains.
What do you think? Does Metro provide a better level of service for big events? If so, why can’t they do that normally?
Interesting factoid: Over the inauguration (Jan. 19-20), Metro averaged 10.5 disruptions/day.
But on the bright side, Metro didn’t derail for the last two big events either! How about a press release on that, WMATA?

Past weeks: here, here and here.

More MetroFAIL on WaPo
Load this up on your iPod


add to del.icio.us Add to Blinkslist add to furl Digg it add to ma.gnolia Stumble It! add to simpy seed the vine TailRank post to facebook
 
Creative Commons License
This work is licensed under a
Creative Commons Attribution-Noncommercial 3.0 Unported License.
Site Meter