Council storm-response briefing #2: Metro’s “bottleneck” explained

Now, our second report (more to come) on the Seattle City Council‘s second day of briefings on December snowstorm response: This time, we focus on what the council heard from, and asked, Metro director Kevin Desmond. Biggest revelation – It’s clear now where the bus system’s customer-communication system broke down – there’s a major bottleneck. More about that in a moment. First, Desmond opened by stating the obvious: “This was the most severe weather, snow emergency in Metro’s history … We appreciate our customers’ patience and understand their frustration. Nobody likes to wait by the curb for a long time, for a bus that may or may not show up or may pass by because it’s crowded.” His bottom line: Metro has a snow plan, but it had to go out the window because it was written for a less-severe, shorter-duration situation. It’s an “80 percent” (service) plan, but he says Metro needs a “50 percent” plan, one that can be pro-actively put into effect with enough time to warn customers. That observation was just the beginning – read on:

Another difference he noted about the December “snow event” – it affected the “entire county” rather than separate areas as is more often the case, given the capricious weather around here. “The full-county effect taxed our resources significantly … That morning (December 18th), our entire articulated fleet and the trolley network [buses using overhead electric wires] began to fail.” And, unfortunately, he pointed out, those types of buses – which just don’t do well in snow – comprise half of Metro’s 1,400-bus fleet (Desmond said that number includes 100 deployed for Sound Transit). That day, he said, at one point, more than 200 buses were stuck, and Metro managers “had to create an ad-hoc 50 percent service plan we hadn’t pre-established or pre-planned” – basically, they made it up on the spot, but couldn’t even keep to that plan because of changing conditions. In addition to the bus fleet’s inability to handle the snow and ice, he described unplowed roads as a major obstacle, since, particularly within Seattle city limits, Metro operates many of its routes on “secondary and tertiary streets.” Coordinating with 39 “jurisdictions,” he said, also provided a challenge, particularly regarding coordinating which routes need to be kept open.

Last but by no means least on his list of major challenges, customer/public communication. He didn’t try to sugarcoat this one, saying, “It’s going to continue to be a problem in these events” because of “structural” issues.

The main one, as he described it, involves Metro’s Radio Control Center. This is where everything comes in from the field by radio – but he says they have only four radio channels, and that means a huge bottleneck in this kind of event, when “there’s a tremendous amount of information trying to flow from field to service coordinators.” He says a plan is in the works to increase the amount of radio channels. He also mentioned what we reported here during the storm — Metro has a GPS system coming next year so that buses can be tracked in real time using that technology, rather than the current system, which involves tracking them as they pass certain route points – and therefore falls completely off the rails as soon as routes are deviated from.

At that point, Councilmember Sally Clark asked, “What if the radio system went down?” Desmond indicated there’s no “well-developed alternative plan” — most drivers carry cell phones, he said, so they might be usable in a situation like that. But, he retorted, “This is a weather plan, not a disaster plan.” Clark fired right back, “Some people called it a disaster.”

Then, for the second consecutive day, Council President Richard Conlin brought up the method of communication that WSB’ers used quite effectively throughout the storm, when those formal communications channels failed: “There’s another network we’re missing,” he said, “the emerging electronic communication. For example, if you went to the [Seattle neighborhood] blog sites, you would have seen a lot of bus information [communicated during the storm]. If the funneling issue is the constraint, maybe decentralization would help.”

Desmond didn’t disagree, but did express some concern about “collect(ing) that in a coherent way,” while acknowleding “customers certainly want that instant information” — information he says is just not available now because “we have everybody calling in on radios, and that gets jammed up.”

West Seattle-residing City Councilmember Tom Rasmussen said the lack of real-time communication capability could even be life-threatening: “I find it quite alarming. When we hear of major disasters, like 9/11 or Katrina, it’s the lack of communication and lack of capacity of systems that causes so much injury and death … Metro may be one of the systems we rely on, but if we don’t have good communication systems, we’re really stuck and everyone’s left on their own. This has to be something that all the jurisdictions work with you on.”

Within “18 months,” Desmond reiterated, “we will have a significantly enhanced system … this is 30 or 40 million dollars in technology that’s coming.” In the shorter term, though, he acknowledged that there are steps that Metro could take – crosstraining people so more can be added in various roles in that Radio Control Center, and improving the Metro website: “We are still struggling with how to get information from the Control Center into our website and keep it updated on a routine basis.” And he agreed that “unpublished route” was a phrase that didn’t help much of anyone when it appeared online: “We were making up routes kind of on the fly – The website works well for the basic snow plan as currently written, does NOT work well for what happened. … We need to improve our website; I think it does not do justice to what our consumers need.”

Before his section of the briefing concluded, he noted that the King County Council plans its own set of hearings – the first one next Monday – at which Metro will make an even more detailed presentation regarding what happened, why, and what could be done to fix it.

(As noted earlier, this is our second report on today’s three-hour City Council storm-response briefing; the first one, with more on the road-clearing challenges, is here; our report on yesterday’s shorter briefing is here. We plan at least two more reports on today’s briefing – next one, what Seattle Public Utilities had to say about the trash/recycling/yard-waste pickup problems.)

6 Replies to "Council storm-response briefing #2: Metro's "bottleneck" explained"

  • datamuse January 6, 2009 (3:29 pm)

    Four channels? That’s it?? Wow. (Just for contrast, I think Bumbershoot operates with three times that number.)

  • seattlemarty January 6, 2009 (3:48 pm)

    “It’s going to continue to be a problem in these events” because of “structural” issues.

    ARRGGHH

    If I ever responded that way to my customers (or boss for that matter) I’d be asked if O wanted to reconsider my statement and if I didn’t I’d lose both my contract with my customer and my job. It must be nice to live in a bubble where you get to say problems can’t be fixed.

  • JayDee January 6, 2009 (7:19 pm)

    Here is my METRO “50% plan” for Alki and Admiral (Well mainly the 51/56/37 routes):
    1) Convince the city to plow Alki Ave and Admiral, from the West Seattle Bridge, to 63rd and Alki.
    2) Convince the City to plow the western route of the 51 route–It isn’t that challenging if there isn’t 3-4 inches of ice on-top.
    3) Run shorty buses on reduced schedules if you must, and service all three of these routes. This will allow people to catch all three routes with luck.
    4) Don’t run the 56 down the west side of Admiral, or back up Admiral–in bad conditions, the drivers shouldn’t stop on the hills anyway, and if the 37 is running, those partway up the hill can hike to the the beach.
    5) Those closer to the top can take the 51. Metro should put little snowflakes on the stops the bus should make in the snow to alert the horiz. challenged.
    6) Use the newfangled GPS devices to track the buses. Have someone at METRO assigned to monitor them. When a 56 starts dropping people off at the Chelan Cafe for 3-mile walks home, have the base call the bus and ask why, or if he sees a 56 taking a scenic tour of Delridge, again, ask why. If there is a real reason for the detour, then the observer should e-mail WSB. WSB can then alert us via whatever.

    Grace’s comment that we only have to walk 4 blocks is not true if you live on Alki Ave nearer Duwamish Head–Try 8 blocks, and a 500 foot elevation gain. Even 4 blocks downhill/uphill isn’t for the those less able. This plan makes sense, and even more sense if the city actually plows the streets, salt or no.

  • JayDee January 6, 2009 (7:20 pm)

    BTW, the 56 would loop somehow at California/Admiral and go back eastbound.

  • LyndaB January 6, 2009 (8:07 pm)

    wow, lack of communication that’s a “new” one. geez, if we had a WSB in my workplace, that would be fabulous. it’s way better than the ‘”grapevine news” we have but i digress. does anyone remember a bill gates/microsoft idea way back when where there would be information kiosks through out the city? sounds like a good idea. i wrote an email suggestion to metro about having reader boards at the street level so you can get up to date information. for instance, when the tunnel was closed (at one point) you don’t end up waiting for a bus that has returned to the tunnel route instead of street level.

    i guess metro does need to come up with a disaster plan. it’s not a bad idea. it will take some major planning. we all have good ideas to contribute here!

  • sam January 6, 2009 (9:57 pm)

    did Metro ever explain the literal bottleneck?

    scenario: you wait for an hour and half and then some for a bus. it shows up, full, and swears there’s more right behind. sure enough a couple more roll through, and then that’s the last of that route for over an hour.

    this happened on more than one occasion with the 120 so it’s almost like they meant to do it, and I was wondering why.

Sorry, comment time is over.