Greater Greater Washington. The Washington, DC area is great. But it could be greater.

Posts about Service Disruption

Transit


Metro closing Red Line for 8 months to accelerate repairs

This article was posted as an April Fool's joke.

Metro will suspend all service on the Red Line for the next 8 months to allow repair crews to finish work on the line more quickly. Shuttle buses will replace trains between Shady Grove and Glenmont.


Photo by ElvertBarnes on Flickr.

According to Metro spokesman Stan Dessel, Metro is tired of the constant weekend track work. "Frankly, we're just as sick of the slow trickle of repairs as the customers are. We decided it would simply be faster to just fix everything at once," Dessel said.

Dessel said customers should also consider alternative commuting methods, like driving. Customers who drive or take the shuttle buses should expect to add an additional 60-120 minutes to their travel time.

Riders from Shady Grove can also drive to Vienna and take the Orange Line.

Governors Bob McDonnell and Martin O'Malley announced plans to spend $10 billion to build a new freeway across the Potomac River in order to accommodate the Metro riders, but added that funding is too scarce to contribute more to speed up the Metro repairs. "We think this is the best way to use our state transportation dollars to help commuters," said Virginia Secretary of Transportation Sean Proaughton.

In addition, MARC will add new service on the Brunswick Line. CSX announced that it would allow MARC to run more trains and actually tell its dispatchers to give priority to passenger trains on the line, as opposed to previous times when they claimed to have done so but dispatchers did not actually follow through.

Metro is launching a new public relations campaign around the closure, called "Red Line: Deal With It." Customers will see construction walls at Red Line station entrances with slogans like, "8 Months Isn't So Bad, Is It?" and "No More Delays. No More Red Line."

Organizers of large national events are also being informed. A national tea party convention has already modified its website to inform attendees driving to the region from points north on I-95 to take the Beltway to Vienna instead of driving to Glenmont or using any other station.

Metro will suspend all work on other lines, including Silver Line construction, in order to complete the work in 8 months. "We hope that by the time the Red Line reopens, we'll only have to single-track twice a month," said WMATA CEO Richard Snarles.

Dessel said Metro is working with Mayor Gray to hire thousands of unemployed District residents to help with the 24-hour repairs. The program is part of a new employment program called "One City, One Line."

A social media component of the program, called "Metro Fast Forward," will equip track workers with helmet video cameras and editing software so that they can produce videos of the work in real time.

This concept has actually been in the works for over a year. Previous WMATA spokesperson Lisa Dystone planned not to tell riders about the closure, arguing that nobody would notice. However, Michael Perkins noticed an obscure footnote in a WMATA Board presentation and encouraged officials to mount a larger campaign to inform riders.

Some have already criticized Metro's plan. The critical blog DeCrapify DC Metro said 8 months is far longer than needed to finish the work. Another blog and popular Twitter account, WTF WMATA, wrote that customers deserve better treatment and vowed to hold Metro accountable.

How will you adjust to the Red Line closing? Let us know in the comments.

Transit


Metro opens doors, closes data

Metro used to publish lists of service disruptions online, but soon after I published a post analyzing the data, Metro stopped posting new reports and eventually removed the entire archive. Is this good customer relations?


Photo by Marcin Wichary on Flickr.

Metro officials say that the reports require a lot of staff time, but they already have internal reports that show the same information, just in a more technical way. Metro could, and should, still release those reports to interested members of the press or transit aficionados who can interpret them for the public.

If Metro's performance is getting better, then posting these reports would help advocates write reports or articles about that fact, and boost public confidence in the work CEO Richard Sarles and his team are doing. If the performance is not getting better, then we should be having a public conversation with WMATA officials about what it would take to get improvements, or when the current repair schedule will start to bear fruit.

Here's an example service disruption from a report I received from a WMATA insider:

TRAIN GOES TO B4 AT POINT OF POWER, HAVE TO CUT OUT ATP TO MOVE, NOT DISPATCHED, K08, CMD, ATCC, 918
Other reports are a little simpler to understand:
NO ALL DOORS CLOSED CUSTOMER POSSIBLY HOLDING THE DOORS
A lot of this message wouldn't make sense to the vast majority of commuters. WMATA could still post these with a glossary that helps decode even this cryptic report, though there is the possibility that customers would see them and be confused, or call in to customer service about it.

Instead of posting these, WMATA created a "Vital Signs" report, which lists a few high-level metrics like overall rail on-time performance. But one number for rail on-time performance hides a lot of important information. A train can be late up to half the headway and still count as on time, meaning that when trains run every 20 minutes, trains could still be 10 minutes late or early. It doesn't include performance during planned track work, and other factors.

Today, WMATA's approach to public information seems to be to release only a few conclusions, not any deeper information. When the Riders' Advisory Council or others have asked for more, they've been told that it's the job of staff, and nobody else, to analyze data and tell the public and press what to believe about the issues.

But to many riders, this isn't satisfying. WMATA officials say they're aggressively fixing problems, but will those fixes actually lead to better performance, and when? So far, the agency has just cut the on-time performance target from 95% to 90%. It's never met its goal for the frequency equipment breaks down ("mean time before failure") since the data have been reported, and does not appear to be improving.

It's no secret that WMATA's reputation as a reliable transit service is tarnished by frequent service delays and offloads. If Metro begins to publish these reports again, customers could decipher the differences in service disruptions that are the fault of customer behavior like blocking doors, sick passengers, or police activity, and those that are due to maintenance issues like brake, track control circuit, or door problems.

Compare this to San Francisco and Chicago, two transit agencies that have longer histories of reporting service data.

Chicago reports number of rail delays of 10 minutes or more, percentage of track that is affected by a slow zone restriction, miles between rail vehicle defects, percentage of the rail fleet unavailable for service, and percentage of customer complaints not closed out within 14 days.

San Francisco reports how closely they're meeting the schedule (similar to WMATA), how the headways match up against the plan (more useful to customers for frequent routes), the amount of service, late pull-outs, overcrowded vehicles, the number of unexcused absences, mean distance between failures for trains, vacancy rates for service-critical positions, and the complaint resolution rate within 14 days.

San Francisco and Chicago implemented better performance reporting as part of an effort to regain the public trust after a long decline in service. Metro should do the same in a concerted effort to truly move Metro Forward.

Transit


Metro suffers complete blackout

Metro suffered a complete system failure last night around 11:30 pm. The failures were so extensive that all communications, including track circuits, were out of service.


Photo by Make Lemons on Flickr.

Customers on Twitter were reporting that rail operators had to leave and walk to the next station to get permission to move. WMATA's website was down, no communication came over any of the alert systems.

Former DCRA tweeter Mike Rupert wrote in the Local Gov blog that he thinks the complete lack of communication killed months of goodwill.

This wasn't Metro's only problem yesterday. In the morning, a cracked rail forced single-tracking between Van Ness and Friendship Heights, and then one train single-tracking stopped for 15 minutes due to door problems, forcing long delays for all riders trying to traverse the area.

With Metro's 30-plus year old system and a long backlog of deferred maintenance needs, some problems are going to crop up, but many riders and the Riders' Advisory Council have repeatedly faulted inadequate communication during crises.

Meanwhile, while Metro has launched a detailed campaign to explain its need for maintenance work, it has been tight-lipped about more specifics, such as timelines and costs for various aspects. Riders frustrated by multiple overlapping outages of lines, escalators and more may well tire of just hearing entreaties to be patient for a period of years, with little more to reassure them that the delays are leading to actual change.

Were you stuck in either of yesterday's problems? Looking constructively, what level and type of communication do you think Metro needs to achieve?

Transit


Weekend station closures will become common on Metro

Metro released a complete calendar yesterday for all their major trackwork over the next 12 months. It relies much more heavily on closing stations and connecting them with shuttle buses, rather than single-tracking.


Photo by DCist on Flickr.

WMATA believes the closures and bus bridges will affect most passengers less than single-tracking and will allow them to get vital work done faster. Many of the closures allow installing new "track circuit modules" that prevent the electronic systems from losing indication of trains, as happened in the Fort Totten crash, or "guarded #8" switches which guard against trains derailing as they change tracks.

The first of this work, coming this weekend, is related to the Silver Line. The Orange Line will be closed between East Falls Church and West Falls Church stations to enable crews to work on the connection between the Silver and Orange Lines.

While closing stations and forcing passengers to use a bus may be disruptive for those passing through the work zone, they actually worked quite smoothly last time, Metro used them, on Memorial Day weekend. Many readers reported using them.

Metro also carried more passengers that weekend than the previous year, even with the shuttles. Metro spokesperson Dan Stessel said that over the Memorial Day weekend in 2010, Metro carried around 70,300 riders on the Blue and Orange Lines between Federal Center SW and Minnesota Avenue and Benning Road.

This year, the line was closed so that the interlocking at Eastern Market could be replaced. Passengers had to ride shuttle buses between Federal Center SW and Minnesota Avenue and Benning Road. Despite that, Metro carried 84,600 riders on the bus bridge.

It appears that the line closure and bus bridge did not deter riders from taking Metro. Hopefully, as closed segments and shuttle buses become a regular sight on Metro, they will continue to run as smoothly.

Transit


Savvy Metro riders always have a Plan B

This morning, a bomb threat caused Metro to close its Rockville and Shady Grove stations during the morning rush. Many riders were delayed or stranded while Metro worked to recover.


Photo by nevermindtheend on Flickr.

These unexpected closures are, luckily, few and far in between. But by learning all your options, you can be prepared for them.

Metro was able to establish shuttle bus service relatively quickly, but hastily set up bus bridges are often disorganized, hard to find, and slow. Your best option may be to take a regularly scheduled bus service.

If your station were to be unexpectedly closed, would you know which bus would get you around the closure? If you're a regular transit rider, you might want to have that piece of information handy.

Let's take Rockville, for example. With that section of the Red Line closed, riders had several options to get around the closure.

Perhaps the best alternative would be Ride On route 46, which would take riders as far as Medical Center. Route 46 runs on Rockville Pike, parallel to the Red Line. It runs every 15 minutes, and covers the distance from Rockville to Twinbrook, the next open station on the Red Line, in only 10 minutes.

The "Q" Metrobuses are another alternative. They run every 10-15 minutes during rush hour between Rockville and Wheaton along Veirs Mill Road.

Rockville also has a stop on MARC's Brunswick Line. Since this closure happened during the morning rush, riders had the chance to board the last few inbound trains of the day. These commuter trains take riders to Silver Spring and Union Station.

Riders who knew about these regularly scheduled buses/trains may have been able to get around the closure even before Metro's bus bridge was set up. Knowing your alternatives can save you lots of time and frustration.

If you haven't done so already, take the time today to find alternate transit options to/from your home and work stations. You never know when something could cause a closure. If you know your choices, you don't have to be at the mercy of crowded bus bridges and overburdened station managers.


Photo by strangelibrarian on Flickr.
Your Plan B might be as simple as walking a few blocks to a nearby station. Or perhaps it could involve Capital Bikeshare. In many cases, you will likely need to have a bus route in mind as an alternate. If so, on your way home tonight, stop by the station manager's kiosk and pick up a bus schedule for your backup route or print if off of Metro's website.

It would be great if Metro could get some alternate routes out via twitter and email during these closures, though their communications department is likely pretty busy during unforeseen closures. So don't wait. Be proactive and find your Plan B today.

Transit


More weekend closures, less single-tracking for Metrorail

To save time and money, Metro is revising the way they do some track work. Instead of single-tracking through work zones, Metro will now close whole line segments more often.


Photo by ElvertBarnes on Flickr.

When BART was being designed, a 1971 article in the IEEE Transactions on Industry and General Applications described its system for avoiding shutdowns by single-tracking:

The BART system will provide service at 90-s intervals during peak demand periods, extending to as long as 15-min intervals during the low-demand early morning hours. At no time will service be discontinued; by the use of carefully placed crossovers and the control of trains in a reverse running mode, maintenance work on the roadbed can be performed without serious disruption of the service.

But in 1971 BART had yet to open, and the Metrorail system had only broken ground two years earlier. Operating experience in the years since has shown that while single-tracking may preserve service, it does so at the expense of lengthened headways and disruptions along the entire length of the line.

Today, taking this experience into account, WMATA has announced a new approach to weekend track work on the Metrorail system, in which entire sections of lines will be closed and replaced with buses.

Single-tracking doesn't just disrupt riders in the work area itself; it slows down the entire line, and affects riders throughout the Metrorail system.

WMATA's new approach to track work will preserve service on the open portions of lines, and avoid the follow-on effects which usually occur when trains are single-tracking.

Closing lines to speed repairs is, by itself, nothing new. In 2006, London Underground elected to close the Waterloo & City Line in its entirety for five months, in order to avoid a projected 70 weekend closures necessary to complete the major overhaul of the line.

Because of the complete closure, weekday riders who would have been spared disruption under a program of weekend closures instead had to take alternate routes. But because the complete closure was more efficient, the work was done (and the disruption ended) in 5 months, rather than in more than a year for weekend closures alone.

New York City's MTA has also been examining partial line closures as an alternative to frequent evening and weekend disruption. No decision has been made yet, but MTA Chairman Jay Walder seems to think it's a strategy that's proven itself in London, and which may prove viable in New York as well.

So, how well will this strategy work for Metrorail? At the extremities of lines, complete closures will probably be superior to single-tracking. Work will go faster with no trains running through the work areas, and the unaffected parts of the line won't have to contend with the bottleneck caused by single-tracking. In the core of the network, though, where ridership levels are high even on weekends, shuttle buses may end up swamped with passengers, leading to delays for riders traveling through the closed areas.

In the end, riders will face disruption whether trains are single-tracking or replaced with shuttle busesbut in this case, replacing trains with shuttle buses means a faster end to the work, and a quicker return to normalcy.

Transit


Track work will disrupt Metro rides this weekend

This weekend, Metro will be closing another section of the Blue/Orange subway downtown. The Red Line will also lose service on the ends, and all lines will close early at night.


Graphic by the author.

Starting tonight, Metro will close the Blue and Orange lines between Metro Center and L'Enfant Plaza. Metro Center and L'Enfant Plaza will still have Blue and Orange Line trains, but Federal Triangle and Smithsonian will be closed. They'll reopen on Tuesday morning.

All riders should keep in mind that the last train on all lines will depart 20 minutes earlier than usual throughout the weekend.

Like all line closures, Metro will be providing free shuttle bus service around the closure. These buses typically can't handle the number of passengers that exit the stations in large clumps as trains are offloaded. So passengers generally are forced to wait for a bus they can fit on.

This delay and being forced to exit the system and wait on a street corner in the elements is a major, though necessary, hassle.

Metro could reduce demand for shuttles by letting riders know how close Federal Triangle is to Metro Center and Archives and how close Smithsonian is to L'Enfant Plaza. They've done this in the past for major events, by encouraging riders not to change lines, and instead walk from the nearest station.

For those continuing longer distances, since each separate section of the Blue and Orange Lines connects to other Metro lines, many riders may well choose to avoid the shuttle buses and simply take the Green/Yellow and Red lines around the closure.

Unfortunately, the Green, Yellow, and Red lines will be operating typical weekend frequencies. The Red Line will be the most frequent, despite 2 different work projects on either end of the line. Red trains will be coming through Metro Center every 7-8 minutes, but the more frequent service will only be between Grosvenor and New York Avenue.

This means passengers will risk a long wait at 2 transfer stations if they attempt to take Metro around the work zone. If Metro could run a few more trains, they could make this easier, though that would also cost money they don't really have.

Running more frequent Red Line service at least between Farragut North and New York Avenue could virtually eliminate the wait for passengers transferring at Metro Center and Gallery Place. And wait times on the Green and Yellow lines between L'Enfant and Gallery Place could be alleviated by adding special Blue Line trains from Franconia-Springfield to Mount Vernon Square. Or as a cheaper option, just running shuttle trains from Pentagon City to Mount Vernon Square.

While beefing up Metro service on the unaffected lines would make getting around the closure easier, it would probably not completely eliminate the need for shuttles. Some passengers may want or need direct service to Federal Triangle or Smithsonian.

Metro officials did not respond to our inquiry about beefing up rail service as an alternative or plans to communicate about nearby stations.

If you have to travel around this closure, a choice between the bus shuttle and a hop on the Red and Green lines is likely to be a crapshoot.

Transit


Metro trackwork announcements take tentative step forward

WMATA has been working recently to improve the way it communicates track work to riders. On Monday it released the February track work schedule for weeknights and weekends in a revised, simpler format.


Photo by Dan Dan The Binary Man on Flickr.

It's a good sign that the agency is willing to rethink how it communicates with riders. Still, out on the rails, some confusion still remains.

First, according to reader Matt, who wrote earlier this week:

I ride [the Red Line] predominantly after the morning peak, and during all of last week as well as today, Red Line trains have been singletracking between Friendship Heights and Medical Center. In-station signs and messages indicate that this is scheduled maintenance and that "there is no delay." [Yet] I can't really find any information on this scheduled maintenance.

Metro has recently been working to announce track work for the entire month at the beginning of each month. Yet in January several other track work projects were announced throughout the month. The work Matt is referring to in particular was announced on January 25 and is scheduled to last until February 11.

If the work is lasting so far into February, why didn't the agency reiterate that it would be doing mid-day work on the Red Line in its press release on Monday? The title, "February's planned work on all lines to improve safety and reliability," certainly indicates that it should contain all of the month's maintenance work.

Of course, there is no reason to re-announce every maintenance project at arbitrary intervals with respect to when they started, but if WMATA wants to establish a precedent of giving customers a full outlook of trackwork for a month, it needs to be sure to include all projects, not just those that begin in that particular month.

Supplement, don't replace:
These new full-month charts are good step in the right direction on the part of Metro's communications department. Metro is ecognizing that it needs to communicate the minimally necessary information to the vast majority of its customers without getting bogged down in unnecessary details.

Simplification is a great thing, no doubt, but it appears that Metro is creating a false choice between simplicity and more information, replacing the information-laden press releases with the new, simplified chart, rather than supplementing them.

Metro's new format for monthly scheduled maintenance is definitely simpler to understand than the text-heavy press releases of the past. But, it no longer includes the amount of information the old format did. The agency should continue to announce each project in detail, at the same time it explores ways to compile the projects into a simpler format, not do one at the expense of the other.

The general work description, and ultimate benefit columns are a very good idea for customers who don't care that WEE-Z bonds are being replaced or new light bulbs are being installed, but ultimately want to know what the benefit to them will be. But some of the vague benefit descriptions will inevitably beg the question "what does that mean?" from a fair number of customers.

Improving the trackwork "calendar":
The format, too, leaves something to be desired. WMATA could make the charts available as a simple webpage. Although the PDF format is nearly universally accessible these days, it is still a barrier to some. In a webpage format, the data can be entered in XML that would allow it to be accessed by developers who want to incorporate it into apps.

A webpage could also be easily programmed so that users can sort the projects by line, date, or any other category for that matter. Additionally, in a webpage the colored rail line dots can have alternative text attributes assigned to them for people with screen readers, which is not always possible in Acrobat.

This is particularly important because currently people with visual impairments will not be able to tell which lines are affected by each project. While some would recognize, for instance, that Takoma and Forest Glen are on the Red Line, not all necessarily would, particularly if they are not end stations. A transit agency should always build communications tools that don't make any assumptions about its users' knowledge or familiarity.

The most logical way to communicate scheduled disruptions to Metro riders is in a calendar format. That is, after all, why we created our Scheduled Service Disruption Calendar that can be accessed from any page in the sidebar. It is in no way perfect, but it operates on the open Google Calendar platform so that people can import the feeds to their own calendar programs and allows riders to view all disruptions or show only those on lines that are relevant to them.

Finally, Metro needs to improve the way this information is accessed on its website. Scheduled disruptions should be available from the front page. As far as I can tell, the only way to access track work schedules is to find the press release in the News archive. Metro has a calendar page, that includes a "Track Work" category, but none of the track work is actually in the database. Even if it were, this "calendar" is still only in a list format and is not exportable to any other platform.

Delayed trains or delayed people?
Reader Matt raises another point in his e-mail which indicates a larger problem with the way WMATA handles and communicates maintenance-related disruptions.

The indication that there is no delay is very misleading. Over the 6 days I have experienced this singletracking, 3 of the days I have had to wait more than 10 minutes for a train, with today requiring a wait of approximately 18 minutes. This is certainly much more than normal - and it shows with a much more full platform. The extra 5-15 minutes is not a major delay, but it does matter.
Though I can only speculate, it would appear that by "no delays," Metro is indicating that trains are moving through the single track area on the schedule that was established during the maintenance plan.

This is a symptom of Metro's often operating more like a logistics company than a person-oriented transit agency. Saying that there are no delays during single tracking indicates that WMATA treats delays with respect to moving trains through the system rather than moving people.

While a train may be maintaining the established schedule during track work times, this will still manifest itself as a delay to the customer standing on the platform at one of the affected stations. Matt is right that Metro should communicate this to its customers.

Make no mistake, the new track maintenance format is a very good sign from Metro's communications office under Sarles' leadership, because it shows that they're willing and able to be creative in how they communicate information to the public. When talking to Lisa Farbstein, WMATA's director of media relations, on Wednesday at the blogger roundtable, she said she hopes this new format is only the first iteration and that they'll continue to improve it over time. We hope they'll consider some of our recommendations.

Metro still has a long way to go until they have created a truly transparent operation that fully communicates with its customers, but, with developments like PlanItMetro and these new trackwork calendars, they are making serious efforts to improve in this area.

DC Maryland Virginia Arlington Alexandria Montgomery Prince George's Fairfax Charles Prince William Loudoun Howard Anne Arundel Frederick Tysons Corner Baltimore Falls Church Fairfax City
CC BY-NC