Knowledge Resources

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.