Architecture Scope
The scope of the Regional ITS Architecture can be described in terms of: 1) the size of the region and jurisdictions covered (geographic scope), 2) the planning or time horizon, and 3) the variety of transportation services that are covered. This scope is defined in the context of adjacent and overlapping Regional ITS Architectures.
Description
This 2018 Arizona Statewide ITS Architecture is an update to the 2013 Arizona Statewide ITS Architecture owned by Arizona Department of Transportation (ADOT). There are three existing ITS architectures within the State; this Statewide ITS Architecture and two regional ITS architectures. The two regional ITS architectures are the Maricopa Association of Governments (MAG) Regional ITS Architecture, June 2013, and Pima Association of Government's (PAG) Tucson Metropolitan Region Intelligent Transportation Systems Strategic Deployment Plan for the 21st Century, July 2004. This Statewide Architecture interacts with these two regional architectures but is separate and focuses on the ADOT-owned ITS elements and all other ITS elements outside of the two regional architectures.
The Statewide Transportation Planning strategy used to develop this ITS Architecture represents multimodal transportation that supports the vision laid out in Building a Quality Arizona (BQAZ) combined with What Moves You Arizona (Arizona's Long-Range Transportation Plan). The Statewide ITS Architecture adopts the goals and strategies from these plans.
In addition to the MAG and PAG ITS Regional Architectures, ADOT shares operations and data with surrounding states to varying degrees. Therefore, this Arizona Statewide ITS Architecture considers the surrounding states as stakeholders and their ITS architectures as related:
� 2010 California Statewide ITS Architecture Update
� 2012 New Mexico Statewide ITS Architecture Update
� 2013 Southern Nevada Regional ITS Architecture Update
� Utah Statewide ITS Architecture
Time Frame
10 years
Geographic Scope
The geographic scope includes the entire State of Arizona extending south to Mexico and to the bordering States of California, New Mexico, Utah, and Nevada. This geographic scope includes all ADOT-owned ITS elements throughout the State and all other governmental agency ITS elements outside the MAG and PAG regions.
Service Scope
This ITS Architecture covers a broad spectrum of ITS related services including: Commercial Vehicle Operations, Data Management, Maintenance and Construction, Parking Management, Public Safety, Public Transportation, Connected Vehicle Support, Sustainable Travel, Traffic Management, Traveler Information, Vehicle Safety, and Weather.
Related Architectures
| Related Architecture | Description |
|---|---|
| 2004 Tucson Metropolitan Region ITS Strategic Deployment Plan for the 21st Century | The Pima Association of Governments (PAG), the metropolitan planning organization for the Tucson region and its ITS stakeholders have created a regional ITS plan to serve as a guide enabling local jurisdictions to plan future projects to integrate with existing and other planned projects belonging to neighboring jurisdictions, ultimately serving the region as a whole. It has been developed in conformance with precepts of the National ITS Architecture and the recently issued ITS Rulemaking by USDOT, helping to position the region for future federal funding opportunities. |
| 2007 New Mexico Statewide Architecture | The New Mexico Statewide ITS Architecture is a roadmap for transportation systems integration in the State of New Mexico over the next 20 years. The New Mexico Statewide ITS Architecture has been developed through a cooperative effort by the region's transportation agencies, led by New Mexico Department of Transportation (NMDOT), covering all surface transportation modes and all roads in the state. The New Mexico Statewide ITS Architecture was initially developed from existing documentation for the State, a general understanding of the transportation systems in New Mexico, and from information gathered from regional and state government websites. An initial Statewide ITS Architecture was developed and was elaborated on through extensive stakeholder input gathered through a series of stakeholder workshops, from review with individual stakeholders, and from comments received during the review period. The New Mexico Statewide ITS Architecture represents a shared vision of how each agency's systems will work together in the future, sharing information and resources to provide a safer, more efficient, and more effective transportation system for travelers in the state. The architecture is an important new tool that will be used by: � Planning agencies and organizations to better reflect integration opportunities and operational needs into the transportation planning process. � Operating and implementing agencies to recognize and plan for transportation integration opportunities in the Region. � Other organizations and individuals that use the transportation system in the Region. The architecture provides an overarching framework that spans all of these organizations and individual transportation projects. Using the architecture, each transportation project can be viewed as an element of the overall transportation system, providing visibility into the relationship between individual transportation projects and ways to cost-effectively build an integrated transportation system over time. |
| 2010 California Statewide ITS Architecture and System Plan | The 2010 update to the California Statewide ITS Architecture included a literature review, review of goals and objectives of stakeholders, updating stakeholder lists; documenting actual inventory (service systems in place, or planned), interviews and face-to face meetings with stakeholders, and mapping (linking of inventory) to Architecture system elements. |
| 2013 MAG Regional ITS Architecture Update | The first comprehensive ITS Strategic Plan for the Phoenix metropolitan region was developed by Maricopa Association of Governments (MAG) in 2001. This Plan included the very first definition of the Regional ITS Architecture (RIA). Since ITS is closely linked to system management and operations, as a natural next step, MAG developed the Regional Concept of Transportation Operations (RCTO) in 2003, which was a high level transportation operations plan for the region. These important planning developments resulted in significant new additions and improvements to the region's ITS infrastructure and transportation operations. As such, MAG led the development of the RIA update to account for the growth in systems throughout the region, and to ensure consistency and conformance with the programs, standards, and guidelines provided through the FHWA Rule 940 and FTA Policy on Architecture Conformity and Standards, as well as through the National ITS Architecture. This updated RIA: � Reflects all existing ITS-related infrastructure in the MAG Region as well infrastructure and connectivity that are programmed and planned for future projects; � Accurately reflects any changes and modifications that have been made to the National ITS Architecture since the 2012 MAG ITS Strategic Plan; � Serves as the key reference for any ITS infrastructure development in the MAG region by MAG member agencies, and provides detailed information on how an ITS project can be broken into smaller functional pieces. A very important goal for MAG with this RIA is to provide its members with a tool for project development and integration; � Includes a plan and process for maintaining and updating the RIA on a regular basis, so that it will remain current and valid and serve as a valuable tool to support ongoing project development and implementation by MAG member agencies; and � Complies with Rule 23 CFR 511 by including existing and planned systems and interfaces that monitor travel and traffic conditions and providing that information to travelers and users of traveler information. The MAG ITS Architecture was updated in 2013 to reflect enhancements of the region's systems that changed the functionality for some agencies. The most notable changes are in updated METRO Light Rail and Valley Metro functionality, the addition of ITS services in some cities that were previously planned, and added future functionality with Integrated Corridor Management strategies and additions to the website based on newly defined 2015-2017 TIP projects. This update also reflects the latest version 7.0.5.2 of Turbo Architecture and the National ITS Architecture Version 7.0. |
| 2013 Southern Nevada Regional ITS Architecture | The Southern Nevada ITS Architecture (SNVArch) region is represented in population and transportation-related activity by the Las Vegas Metropolitan area. The southern region includes the local cities which own ITS infrastructure on arterial roadways and the RTC Freeway Arterial System of Transportation (FAST) system which owns and operates ITS infrastructure on highways and freeways and also operates the arterial network infrastructure within the region from the FAST Traffic Management Center (TMC). FAST is designed to monitor and control traffic. The traffic control component of the system consists of freeway and arterial management. Traffic control requires detection of traffic conditions through the use of video image detection and inductive loop detection. Visual verification of conditions is possible through closed-circuit television cameras. Traffic control is achieved through the use of traffic signals, ramp meters, dynamic message signs, and lane use control signals. FAST is a partnership of 5 major local stakeholders in addition to NDOT. RTC and NDOT pay for the primary costs of operation of FAST. The RTC of Southern Nevada and its RTC FAST TMC, the City of Henderson, the City of North Las Vegas, the City of Las Vegas, the City of Mesquite, Boulder City and Clark County are the primary jurisdictions reflected in the 2013 Southern Nevada Regional ITS Architecture. |
| Utah Statewide ITS Architecture | Arizona DOT will share operations and data with surrounding states, to varying degrees. Utah's Statewide ITS Architectures either includes Arizona Statewide as an element or, they will be asked to include an interconnect and reflect this in their statewide architectures. |