A Confluence of Challenges – A Confluence of Change
Tuesday, March 15th, 2011By Mark Foss
My mornings begin early. I woke up at 3:15 a.m. and left home at 4:00 a.m.. Work begins at 5:00 a.m. There is no transit available when I have to head to work. I’m just glad I don’t commute during the regular rush hour. As I head for the freeway, I begin thinking about the coming day.
Work as a communications coordinator is multi-faceted but it also has a routine familiarity. We facilitate solutions for breakdowns, emergencies, blockages and personnel issues. We collect and manage information. However, the tools of our trade and our business processes are evolving.
Presently, King County’s Transit Control Center (TCC) sits at the confluence of three major projects. First, our old radio system and its related CAD/AVL software are slowly being replaced (see: CCS). Secondly, new radio system equipment(See: OBS) is being installed in about 1,400 buses. It’s a big job. As the radio system project unfolds, we will essentially be using two radio systems – the legacy system and the new one – until completion. Finally, we are continuing to perfect the RapidRide “A Line” in preparation for the opening of the “B Line” in October.
The roll-out of the radio system is progressing well but, as with most major projects, it takes time and hard work. A talented team of technical people, project managers and operational staff are working hard to make these projects a success. I work as the morning coordinator using the new communication system – currently used primarily on RapidRide A Line.
Service on the RapidRide uses headway times – a new approach for us – rather than by a fixed schedule. The RapidRide service is constantly monitored and evaluated. All three of these related projects are works in progress. Unfortunately, recent national news indicates that federal funding for future RapidRide lines could be in jeopardy.
My duties include observing and documenting technical problems as they arise. Occasionally, technical staff members are called at odd hours or work from home to keep the system operational. Progressively problems are being solved. Implementation isn’t simply “plug-and-play.” The fun part for me is observing and assisting the progress.
The new CAD/AVL system allows me a level of insight and control I haven’t had up to this point. The new system prevents a driver from logging into the system with an already active login. A flaw in the old system allows a driver to login with an already active Route-Run combination, thus “knocking out” another legitimate login. With the new system, no such problem exists. I can log an operator on to, or off of, the system directly from the control center. The AVL uses GPS to track a bus – even if it is off a scheduled route. Buses with the new system on board, have automated announcements, automated interior signage and roadside real-time information signs (RTIS) offering passengers information on the next bus. RapidRide passengers already benefit from these enhanced features.
Soon the new system will increasingly handle more service than RapidRide. The biggest challenge will be use of two radio systems, and two CAD/AVL systems, in the same fleet. Coach changes, road blockages and almost any other major issue, will probably have to flow through two radio systems. Documentation will be a collaborative result of Coordinators working different systems, while handling the same problem. The transition will test the limits of communication skills both inside and outside the department.
When the new radio system, CAD/AVL features and RTIS are fully implemented, long-standing business practices may also change. The potential for positive change is tremendous. Road-side real-time information signs can be changed from the Control Center, potentially offering a new communication link with passengers. Another new feature allows a coordinator to specify radio (or text) communication with buses in a given geographic area. Exactly how business current practices will change due to the new technology yet unclear.
Hopefully, new practices will unfold step by step like three projects above: plan, implement and evaluate. Customer expectations may also evolve with the new capabilities. I think the full potential of new onboard systems will only be realized through use, evaluation and course correction over several years. My hope is that once the hardware and software are all in place, and general business practices are established, a method continual process improvement will be implemented.
Finally, I arrive at work. My morning musings draw to an end. As I pull into the parking facility at work I think about the general process of change. Much of the transit industry seems to be driven by tradition and past practice. However, the pressure of new technology, financial adversity and public mood is forcing change. The impending retirement of the “baby-boomers” also suggests an undercurrent of succession issues – change with a potential loss of experienced leadership. Adaptability and the capacity to evolve – under constrained budgets – are extremely important for public transit to appeal to present and future riders.
The fun part for me will be helping the process move forward.
