Consider reconfiguring and integrating existing roadway management IT systems whenever possible to save costs associated with implementing new systems.
Phoenix’s experiences with integrating roadway management IT systems.
Made Public Date
09/16/2005

27

Phoenix
Arizona
United States
TwitterLinkedInFacebook
Identifier
2005-00054

Phoenix's Roadway Closure and Restriction System

Background

The Phoenix, Arizona Metropolitan Model Deployment was one of four cities included in the Metropolitan Model Deployment Initiative (MMDI). The initiative was set forth in 1996 to create model deployments of ITS infrastructure and integration. One of the goals of the MMDI was to disseminate information on the lessons learned from the deployments to assist other cities which may be considering using and/or integrating ITS.

The goals of Phoenix's Metropolitan Model Deployment effort — called "AZTech" — are to provide improved safety and regional mobility through enhanced traffic management and regional, multimodal traveler information. The Roadway Closure and Restriction System (RCRS) is a method by which improved regional traveler information can be gathered and disseminated. The intent of this report is to present a project description and lessons learned from the Roadway Closure and Restriction System, one of the 15 projects deployed as part of AZTech. The main lesson learned relating to the RCRS is that agencies should consider reconfiguring and integrating existing roadway management IT systems whenever possible to save costs associated with implementing new systems.

Lessons Learned

Determine if the desired scope and range of traveler information can be generated by upgrading and integrating existing traffic management IT systems.

In Phoenix’s case, because the new system was an upgrade of an existing system, the development costs were lower than what would be seen for a newly deployed system. The other costs were shared among the other 15 model deployment projects, eight planned additional Traffic Operations Centers, and two Fire Dispatch Centers. These server costs were shared because it is the core component that integrates all of the transportation information systems.

Engage regional stakeholders in examining system integration options and potential solutions.

This project required a high level of communication and coordination among the different districts within the Arizona Department of Transportation and with several local partners.

The Roadway Closure and Restriction System is linked to other systems through the AZTech server. Each jurisdiction that is linked to the server can update its road-way and highway closure information. Once information is manually input into the system, the server relays it to the web site, kiosks, and the toll-free telephone system. Other freeway information, such as incidents and lane closures, is relayed in parallel with the closure and restriction information.

The local municipalities in Phoenix were able to share infrastructure, which led to equipment cost-sharing. To reach the shared information phase of integration, several jurisdictions in Phoenix were forced to disband institutional barriers and increase inter-jurisdictional communication. Thus, the outcome involves a more regional approach to traveler information reporting.

Phoenix's Roadway Closure and Restriction System

Phoenix's Roadway Closure and Restriction System
Publication Sort Date
10/01/2000
Author
Steve Gordon, Jeff Trombly
Publisher
ITS JPO
Other Reference Number
FHWA-OP-01-036

(Our website has many links to other organizations. While we offer these electronic linkages for your convenience in accessing transportation-related information, please be aware that when you exit our website, the privacy and accessibility policies stated on our website may not be the same as that on other websites.)

Focus Areas Taxonomy: