The AMPA Regional ITS Architecture AMPA Regional ITS Architecture Update. Final Architecture Document. Submitted By:

Transcription

1 The AMPA Regional ITS Architecture AMPA Regional ITS Architecture Update Final Architecture Document November 2016 Submitted By: Consensus Systems Technologies Corporation 301 East 87th Street, Ste. 7A New York, NY USA

2 Table of Contents Table of Contents... ii Table of Figures... iv List of Tables... iv Revision History... v 1. Introduction Purpose Document Overview--Update Scope of the Architecture AMPA Regional ITS Architecture Development Process Process to Create the 2007 Update to the Architecture Kickoff Meeting Create Initial Architecture Update Stakeholder Outreach Meeting Draft Architecture Update Architecture Review Meeting Draft Architecture Update Architecture Documentation Deliver Final Architecture Products Architecture Update Process Requirements of the Final FHWA Rule and FTA Policy on Architecture Specific Requirements of the Final FHWA Rule or FTA Policy How the Final Rule and FTA Policy Requirements are Met ITS Architecture Concepts Identification of Stakeholders Champion Regional Stakeholders Operational Concepts Systems Inventory Systems by Stakeholder Systems by Architecture Entity Needs and Services Needs Identification Services Comparison of Needs and Services Interfaces and Information Exchanges Top Level Regional System Interconnect Diagram Customized Service packages Regional Architecture Information Flows Functional Requirements Standards Discussion of Key Standards for the Region Reference to the Detailed Standards information on the Web Site Project Sequencing Process for Selecting Projects Page ii

3 10.2. How to Use the Recommended Project Sequencing Agreements Types of Agreements Agreements Potential Agreements Using the AMPA Regional ITS Architecture Using the AMPA Regional ITS Architecture in the Planning Process Operational Strategies Identified for the AMPA Strategy Evaluation and Prioritization Metropolitan Transportation Plan Issues/Challenges Using the AMPA Regional ITS Architecture for Programming Architecture Use in the MRCOG Transportation Programming Process Architecture Use in Organization Capital Planning Architecture Use to Identify and Define Projects Challenges Using the AMPA Regional ITS Architecture in Project Definition Issues/Challenges Maintaining the Architecture Timetable for Periodic/Event Maintenance Ongoing Monitoring/Reporting Log Locally Funded Projects Not Identified in the Normal Planning Process Event-Driven Updates ITS Architecture Addendum Architecture Baseline Roles and Responsibilities for Maintenance Definitions Stakeholders Maintenance Working Group Responsible Agency Maintenance Manager Change Management Process Identify Change Evaluate and Review the Change Request Update Baseline Update of the Turbo Architecture Database Notify Stakeholders Appendix A: Acronyms Appendix B: Comments and Disposition Appendix C: Maintenance Request Form Page iii

4 Table of Figures Figure 1: AMPA Planning Area Boundary... 3 Figure 2: AMPA Regional ITS Architecture Development Process... 5 Figure 3: Information flows Figure 4: Example of a National ITS Architecture service package Figure 5: Example of AMPA Regional ITS Architecture customized service package.. 14 Figure 6: AMPA Regional System Interconnect Diagram Figure 7: Example Customized Service Package Figure 8: Example of Element Detail showing Interfaces Figure 9: Example of Architecture Flows Between Elements Figure 10: Example of Interface Figure 11: Example of standards mapping page Figure 12: Example Service package: APTS2- Transit Fixed Route Operations for City of Albuquerque Transit Figure 13: ITS Architecture and the Transportation Planning Process Figure 14: Supporting the Transportation Planning Processes Figure 15: ITS Project Programming/Budgeting/Capital Planning Figure 16: MRCOG TIP Development Flow Char (with ITS Subcommittee Participation Noted) Figure 17: ITS Corridors/Priority Corridors Map Figure 18: Mapping of ITS Infrastructure Figure 19: Project Implementation Process Figure 20: MRCOG TIP Development Flow Chart (with ITS Subcommittee Participation Noted) Figure 21. Change Management Process List of Tables Table 1. Mapping of Requirements to Architecture Outputs Table 2. Stakeholders Table 3. Stakeholder Roles and Responsibilities Table 4. Inventory sorted by Stakeholder Table 5: Summary of Transportation Needs/Priorities Table 6: Summary of High Priority Transportation Needs Table 7: Selected Regional Services (Service packages) Table 8: Mapping of Needs to Services Table 9: Applicable ITS Standards Table 10: AMPA ITS Projects Table 11: Types of Institutional Agreements Table 12: Institutional Agreements Table 13: Potential Institutional Agreements Table 14: Regional Project Development Process Relation to FHWA System Engineering Process Table 15: Systems Engineering Requirements supported by AMPA Regional ITS Architecture Page iv

5 Revision History Filename Version Date Author Comment AMPA Regional ITS Architecture /27/07 T. Harris/ B. Eisenhart Initial Release of Architecture Update AMPA Regional ITS Architecture Update-Draft AMPA Regional ITS Architecture Update-V2 2.x 9/30/16 B Eisenhart Revisions based on comments received /10/16 B Eisenhart Final Cleanup

6 Draft 1. Introduction The AMPA Regional Intelligent Transportation Systems (ITS) Architecture is a roadmap for transportation systems integration in the Albuquerque Metropolitan Planning Area (AMPA) over the next 20 years. The architecture has been developed through a cooperative effort by the AMPA s transportation agencies, covering all modes and all roads. The 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 region, and the state. The architecture is an important tool that will be used by: Operating Agencies to recognize and plan for transportation integration opportunities in the AMPA as well as the larger state. Planning Agencies to better reflect integration opportunities and operational needs into the transportation planning process. Other organizations and individuals that use the transportation system in the AMPA as well as the larger state. 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. The architecture also is coordinated with the New Mexico Statewide ITS Architecture to ensure consistency at those jurisdictional and operational points where AMPA based operations coincide and/or integrate with statewide planning and operations Purpose The AMPA Regional ITS Architecture represents a consensus blueprint for ITS Investments in the AMPA region. The AMPA Regional ITS Architecture starts by identifying the potential ITS agencies (stakeholders) within the region, or in the adjoining regions or the state in general. It goes on to define possible integration opportunities between agencies within the region and adjoining regions and identifies how cooperation between the agencies in the deployment of ITS systems can be used to satisfy transportation needs. The architecture can be used to efficiently structure implementations of ITS technologies. By creating a long range plan for the implementation of these systems and technologies, agencies can: Prepare for future expansion Leverage funding Identify standard interfaces

7 In addition to structuring implementations of ITS technologies, the AMPA Regional ITS Architecture allows the region to comply with the FHWA Rule/FTA Policy on Architecture and Standards. The FHWA Final Rule, 23 CFR 940, (and corresponding FTA policy) to implement Section 5206(e) of the TEA-21 requires that ITS projects funded through the Highway Trust Fund conform to the National ITS Architecture and applicable standards. The Rule/Policy requires that the National ITS Architecture be used to develop a local implementation of the National ITS Architecture, which is defined as a regional ITS architecture. This update of the AMPA Regional ITS Architecture will bring the regional architecture into full compliance with this Rule/Policy, which will facilitate the approval of federal funds to support ITS projects in the region Document Overview--Update This document is organized into thirteen main sections and six Appendices. Section 1 provides introductory information on the project, this document, and discusses the scope of the architecture. Section 2 describes the process used to develop the AMPA Regional ITS architecture. Section 3 gives a brief introduction and overview of the National ITS Architecture, and how it relates to this regional ITS architecture. The stakeholders are identified in Section 4, while their systems are inventoried in Section 5. The needs addressed by ITS and the services used to address those needs are covered in Section 6. The interfaces and information exchanges are described in Section 7. The definition of functional requirements for the elements of the architecture is described in Section 8. A discussion of ITS standards applicable to the region is provided in Section 9. A listing of planned ITS projects in the region, along with sequencing of these projects, are described in Section 10. A discussion of Agreements is provided in Section 11. Finally, Section 12 provides guidance on using the regional ITS architecture and Section 13 presents the architecture maintenance plan. The Appendices include a list of Acronyms (Appendix A), a summary of comments received and how the comments were addressed (Appendix B), and the Maintenance Change Request Form (Appendix C) Scope of the Architecture The geographic scope of the architecture is the entire AMPA boundary, which is shown graphically in Figure 1. The AMPA region covers Bernalillo County, Sandoval County, Valencia County, and portions of Torrance County. There are two other regional ITS architecture that borders the AMPA Regional ITS Architecture: the New Mexico Statewide ITS Architecture, last updated in 2012, and the Santa Fe Regional ITS Architecture, last updated in The New Mexico Statewide ITS Architecture provides a general expression of systems in the state, while the AMPA architecture provides specific examples of the systems within the AMPA region. For example, the Statewide ITS Architecture describes interfaces to the element MPO/RPO Traffic Database, while the AMPA architecture describes a specific example of this for the region, MRCOG Data Warehouse. Due to the geographic expansion of AMPA, the northern border of AMPA is approaching the southern boundary of the Santa Fe architecture. Page 2

8 Figure 1: AMPA Planning Area Boundary As mentioned in the introduction, the timeframe considered for the AMPA Regional ITS Architecture is a 20-year outlook for ITS activities in the region. This means that the architecture addresses existing ITS systems as well as those planned for development over the next 20 years. The regional ITS architecture represents a snapshot of the currently anticipated ITS and other projects based on information gathered from stakeholders, and research from agency websites or published agency documents. As such, the architecture will require regular updates to ensure that it maintains accurate representation for the region. Page 3

9 The architecture covers services across a broad range of ITS, including traffic management, maintenance and construction operations, incident management, emergency services, transit management, traveler information, archived data management, and electronic payment. Page 4

10 2. AMPA Regional ITS Architecture Development Process This update of the AMPA Regional ITS Architecture is the second major update following its original development in The sections below discuss the 2007 update and this current 2016 Update 2.1. Process to Create the 2007 Update to the Architecture Development of the AMPA Regional ITS Architecture relied heavily on stakeholder input to ensure that the ITS architecture reflected local and regional needs and plans. The development process used is illustrated in Figure 2. Kick-off Meeting Create Initial Architecture Update Review Architecture in two-day stakeholder meeting Update Architecture Definition-1 Architecture Review Meeting Update Architecture Definition-2 Architecture Documentation Deliver Final Architecture Products Figure 2: AMPA Regional ITS Architecture Development Process The following process steps were used to develop the ITS architecture: Conduct a kickoff meeting to present the development process to stakeholders and gather initial information on architecture scope and needs. Create an initial architecture update focusing on ITS elements and a draft set of customized ITS Services to be provided. Conduct stakeholder outreach through a two day workshop. Create of a complete updated architecture definition for review (web based). Allow stakeholder review of the draft regional ITS architecture and conduct additional stakeholder review through individual stakeholder interactions and through a one-day architecture review workshop. Finalize the ITS architecture based on review comments. Develop and deliver a draft Architecture document Following comments deliver the final architecture products. Page 5

11 Kickoff Meeting A wide array of stakeholders across all aspects of surface transportation in the region, were invited to a one day kick-off meeting that was held on June 7, This meeting was a kickoff of the New Mexico Statewide ITS Architecture development effort as well as the AMPA Regional ITS Architecture update. A key overall objective of the meeting was that the resultant regional ITS architecture update should be a consensus architecture, that is, each of the participants understands and agrees to the ITS elements and specific information exchanges between the ITS elements identified in the architecture that they participated in defining. (This is not to say that the resulting ITS Architecture has credible funding identified that would lead to full deployment. The ITS architecture only identifies the current set of ITS elements and interfaces that the stakeholders agree to. funding processes will continue to be used to decide how to allocate limited resources for ITS elements and interfaces for deployment.) The meeting also incorporated an overview or training in the National ITS Architecture and regional ITS architectures, and a discussion of the scope of the architecture, so that stakeholders would understand and more fully participate in the ITS architecture development process. The morning of the kick-off meeting focused on understanding ITS and what an ITS Architecture is, and the development approach for the Statewide ITS Architecture. During the late-morning and afternoon of the kick-off meeting, the focus shifted from the Statewide ITS Architecture to the AMPA Regional ITS Architecture and the scope associated with the AMPA region. To round out the afternoon, there was a brief discussion about the development of an ITS Strategic Plan for the state of New Mexico Create Initial Architecture Update An updated set of ITS elements, services and interconnections were created beginning with the original AMPA regional ITS architecture. The Turbo Architecture file from the original architecture was converted to the current version of Turbo Architecture (3.1), which is based on Version 5.1 of the National ITS Architecture. The previous architecture, plus existing and planned ITS projects from the Metropolitan Area ITS Implementation Plan (2003) were used to establish an initial list of services that the elements of the architecture would provide. For each existing or future ITS service operating or expected in the region, the service package diagram (the collection of ITS elements, equipment packages, and functions that work together to perform a specific ITS service see Section 3 for details on the National ITS Architecture) for that service from the National ITS Architecture was edited so that each National ITS Architecture subsystem or terminator was associated with the local stakeholder element name. In some cases, multiple instances of the service package were developed where the service had more than one instance in the region. This would be the case if there were multiple agencies performing the same service within the state. This set of customized service packages using the draft elements created previously, was created in preparation for stakeholder outreach so that each could be reviewed and further customized based on actual operating procedures (or theories) for each agency. Page 6

12 Stakeholder Outreach Meeting A two-day workshop was held at NMDOT District 3 Office on July 24 and 25, In the first part of the workshop, stakeholders were asked to participate in identifying and defining their ITS needs while reviewing and revising their draft inventory and the inventory of fellow stakeholders. The second part of the workshops was spent reviewing the customized service package diagrams, adding or deleting diagrams, elements, and interconnections when necessary Draft Architecture Update-1 Following the stakeholder workshop, the customized service packages were revised and a draft architecture was created. Using the customized service package diagrams (as modified during and post the workshop), the Turbo Architecture database was updated, built, and utilized to create a draft ITS architecture. This involved the following activities: Updating the ITS inventory (and stakeholders when necessary) Revising the customized service packages Development of a draft Operational Concept Creating a Turbo Architecture database that represents the sum of all of the customized service packages. In addition to creating the Turbo Architecture database and the customized set of service package diagrams, a high level Architecture Interconnect Diagram (AID, also known as a Sausage Diagram) of all the elements in the ITS architecture was created. A draft of this architecture document was created. There was also a hypertext version of the complete Turbo Architecture database that was created and placed on a generally accessible website ( and has also been made available and incorporated onto the NMDOT project website. This website describes each element of the ITS architecture and all of their interconnections with other elements. The website was developed using additional software tools that go beyond the basic Turbo Architecture software. Stakeholders were notified by (collected at the kick-off meeting, the stakeholder meetings and through independent research on the internet) that a review period for the AMPA Regional ITS Architecture had commenced, and feedback was solicited. Stakeholders were encouraged to review the regional ITS architecture on the website, and were encouraged to provide feedback electronically from the website. Comments received during the course of this project are summarized and maintained in a database. These stakeholders comments, as well as comments generated during the QC process, and their corresponding dispositions are summarized in Appendix B Architecture Review Meeting In addition to the stakeholder website review, a review of architecture material was held on September 18 and 20, During both meetings, stakeholders reviewed comments generated during the review period, and reviewed the changes to any of the customized service Page 7

13 package diagrams that were a direct result of the comments. In addition, the meeting covered discussions of service package prioritization and the identification of regional projects Draft Architecture Update-2 Following the stakeholder meeting, the architecture parts were again updated, and additional architecture elements, such as project list, list of agreements, and functional requirements were developed. These updates resulted from comments received during the meeting, or from outstanding comments from the MRCOG, liaisons or from s from the project website Architecture Documentation A draft Architecture document was created. This document, along with an updated web site, forms a complete description of the AMPA Regional ITS Architecture that is compliant with the architecture and standards Rule Deliver Final Architecture Products Following a comment period on the document and revised website, a final architecture document and final updated website will be developed as the final deliverables on the architecture Architecture Update Process The update of the AMPA Regional ITS Architecture followed a process similar to that used in the development of the original architecture, but with less extensive stakeholder interactions. The following five steps were performed Conduct Stakeholder Interviews Key stakeholder representatives were interviewed via telephone to understand what changes have taken place since the architecture was developed. The interviews focused on projects containing ITS services (using the project list from the original architecture as a starting point). Interviews were conducted with representatives of NMDOT, Bernalillo County, City of Albuquerque, City of Rio Rancho, Rio Metro, and ABQ Ride. The notes from the interviews were used as the starting point for development of the draft update architecture Develop a Draft ITS Architecture Update The first step to updating the ITS Architecture was updating it to Version 7.1 of the National ITS Architecture. This included updating service package names, subsystem names, and flows. Using the information collected during the stakeholder interviews, the architecture material was updated, including Stakeholders, Elements (Inventory), Customized Service Package diagrams of all services List of planned ITS Projects List of existing and planned agreements Page 8

14 Hold Stakeholder Workshop A one day stakeholder workshop was held on January 26, 2016 to review the draft architecture with key regional stakeholders. The objectives of the workshop were to: Provide training for regional stakeholders on ITS architecture what it is and how to use it. Review the draft ITS architecture in order to get concurrence from the stakeholders that it represents their existing and planned ITS deployments. The review covered stakeholders, inventory, services, interfaces (as shown in the customized service package diagrams), projects and agreements. Provide discussion of use of the architecture Develop Updated Draft ITS Architecture Following the workshop, a complete update of the architecture was created including the following baseline outputs: Turbo Architecture File Regional ITS Architecture Document ITS Strategic Plan Document Customized Service Package Diagrams Hyperlinked website containing the architecture details Develop Final ITS Architecture Following the receipt of comments, a webinar was held to review the comments received, Then a final set of architecture update products were created. The final updated baseline is available on the website and also provided to MRCOG and NMDOT on DVD. Turbo Architecture file and Customized Service Package file were also provided. Two copies of all final outputs were provided on DVD Requirements of the Final FHWA Rule and FTA Policy on Architecture Specific Requirements of the Final FHWA Rule or FTA Policy The FHWA Final Rule (23CFR 940) and FTA Policy on Intelligent Transportation System Architecture and Standards, which took effect on April 8, 2001, defines a set of requirements that regional or statewide ITS architectures should meet. The following is a list of specific requirements from the FHWA Rule/FTA Policy: A description of the region (scope) Identification of participating agencies and their systems (inventory) Operations concepts Agreements required for implementation System functional requirements Interface requirements Page 9

15 Identification of ITS Standards AMPA Regional ITS Architecture Sequence of projects required for implementation Develop a Process for maintaining your regional ITS Architecture How the Final Rule and FTA Policy Requirements are Met Table 1 shows how the requirements of the rule are met by the outputs developed for the AMPA Regional ITS Architecture: Table 1. Mapping of Requirements to Architecture Outputs Regional ITS Architecture Requirements Description of region Identification of participating agencies and other stakeholders An operational concept that identifies the roles and responsibilities of participating agencies and stakeholders A list of any agreements (existing or new) required for operations System functional requirements; Interface requirements and information exchanges with planned and existing systems and subsystems Identification of ITS standards supporting regional and national interoperability The sequence of projects required for implementation Develop and implement procedures and responsibilities for maintaining the architecture as needs evolve within the region. Where Requirements documented Geographic definition, identification of services and a timeframe are given in Section 1 of this document. Listing of stakeholders and their definitions is given in Section 4 of this document. An inventory of the elements operated by the stakeholders is contained in Section 5 of this document. The same information is also available in the hyperlinked web site and in the Turbo Architecture database. The operational concept is defined in Section 4 of this document. The discussion of existing and needed new agreements is given in Section 11 of this document. The functional requirements of the ITS systems are described in an overview in Section 8 of this document, are presented in detail l in the hyperlinked web site and in the Turbo Architecture database. The Interfaces and information flows are described in an overview in Section 7 of this document, and are described in detail in the hyperlinked web site and in the Turbo Architecture database. The identification of standards for ITS in the AMPA region is contained in Section 9 of this document. Projects, and their sequencing, are covered in Section 10 of this document. The Maintenance Plan is contained in Section 13 of this document. Page 10

16 3. ITS Architecture Concepts The AMPA Regional ITS Architecture is an example of a Regional ITS Architecture, which has been defined by FHWA Rule 940 as a regional framework for ensuring institutional agreement and technical integration for implementation of ITS projects. Regional ITS architectures, including the AMPA Regional ITS Architecture, are developed in order to provide a guide for the integration of transportation systems. The architecture is based upon the US National ITS Architecture Version 7.1. A complete description of this architecture can be found at The AMPA Regional ITS Architecture uses a set of common concepts or terms drawn from the National ITS Architecture to describe the parts of the AMPA region. This section will provide a description of the most common concepts or terms as an aid to the understanding the remainder of the document. What are some of the main parts of an ITS architecture? They are made of the following: Organizations Systems operated Services provided Functions performed Information exchanged The organizations that operate systems in the region covered by the architecture are referred to as stakeholders. These are public agencies, private organizations or the traveling public with a vested interest, or a "stake" in one or more transportation elements within a Regional ITS Architecture. The systems operated by the stakeholders are referred to as elements. In the AMPA Regional ITS Architecture the elements represent actual systems, such as City of Albuquerque Traffic Operations Center. An element may also represent field devices, for example the element NMDOT Traffic Signals. A more thorough discussion of the architecture elements is contained in Section 5. As mentioned above, the AMPA Regional ITS Architecture is based upon the National ITS Architecture which contains general terms for these systems (elements). Since these National ITS Architecture terms show up repeatedly in later discussion they will be defined here. The National ITS Architecture uses two terms to describe the systems that make up an architecture. They are: Subsystems, which represent the primary systems described by the architectures. For example the TMC element mentioned above represents a regional ITS architecture example of the Traffic Management Subsystem defined in the National ITS Architectures. The National ITS Architecture has 22 subsystems defined. Terminators, which represent systems that are on the boundary of the architecture. In general only interfaces to the terminators are described in the national architectures. An Page 11

17 example of a terminator from the National ITS Architecture is the Weather Service. The National ITS Architecture has 79 terminators defined. As a part of developing a regional ITS architecture, each element of the region is mapped to the subsystems and/or terminators that most closely define the functions of the element. This mapping allows the regional version to use the details associated with the subsystems and terminators in the National ITS Architecture. As an example, the element in the AMPA Regional ITS Architecture called National Weather Service is mapped to the National ITS Architecture terminator Weather Service. The information exchanged between elements (in the AMPA Regional ITS Architecture) or between subsystems and terminators in the National ITS Architecture is described by information flows or architecture flows. There are hundreds of these flows defined in the National ITS Architecture, and it is this information that is used to create the interface definitions in the AMPA Regional ITS Architecture. For example, in Figure 3 the top two boxes show an interface between two subsystems, with its information flows defining the exchange of information. A corresponding interface in the AMPA Regional ITS Architecture is shown in the bottom two boxes. Figure 3: Information flows By mapping the AMPA Regional ITS Architecture elements (e.g. City of Rio Rancho Traffic Operations Center) to National ITS Architecture subsystems (or terminators) (e.g. Traffic Management Subsystem), the interfaces defined in the National ITS architecture can be used as the basis for defining the interfaces in the AMPA Regional ITS Architecture. Page 12

18 The next key concept used by the architectures is that of service packages. These represent slices of an architecture that provide a transportation service. In the National ITS architecture, these service packages are combinations of subsystems and information flows that are used to provide the service. An example of a National ITS Architecture service package is shown in Figure 4. This shows the subsystems and information flows (some of which go to terminators) that perform the collection and distribution of traffic flow and traffic images used to monitor a road network. In the development of the AMPA Regional ITS Architecture, a set of customized service packages were created that define the elements and interfaces used to provide the transportation services in the AMPA Region. Figure 4: Example of a National ITS Architecture service package Figure 5 shows one of the customized service packages within the AMPA Regional ITS Architecture (in this case for the City of Albuquerque Traffic Operations Center). This diagram shows how the City of Albuquerque might implement this service. There are two types of interfaces shown in the customized service package: Traffic Management Center to Roadside Equipment and Traffic management Center to Information Service Provider Page 13

19 Figure 5: Example of AMPA Regional ITS Architecture customized service package Notice that the customized service package includes only some of the interfaces that were in the National ITS Architecture service package. It does not include interfaces to personnel or a map update provider element. Elements mapping to these are not included in the AMPA Regional ITS Architecture. One final concept to mention relates to the functions performed by the elements in the architecture. The National ITS Architecture has the concept of an equipment package, which defines a piece of a subsystem (within the service package) that performs a specific function. For example, in Figure 4, Collect Traffic Surveillance (identified by the white box within the Traffic Management Subsystem) is a function (or equipment package) that is performed by the Traffic Management Subsystem when performing the Network Monitoring Transportation Service. In the AMPA Regional ITS Architecture functions have been identified for the key elements from a mapping of equipment packages to elements using a mapping of equipment packages to each element. For example, the City of Albuquerque Traffic Operations Center (shown in Figure 5) will implement the Collect Traffic Surveillance equipment package (shown in Figure 4 as functionality in the Traffic Management Subsystem). Further information regarding how functions are defined for each element is found in Section 8 on Functional Requirements. Page 14

20 4. Identification of Stakeholders 4.1. Champion In order to successfully develop a Regional ITS Architecture for the AMPA Region, it is necessary to have a champion who can lead the effort from the agency s viewpoint. This individual, or group of individuals, should have the following skills/capabilities: They must have a vision for interconnectivity, partnership and regional integration. They must have knowledge of the local and regional ITS systems and projects. They must understand what a regional ITS architecture is and how to use it most effectively in the planning process. They must be a consensus builder or facilitator, and They must have executive level access to resources in order to gain the support of various regional or statewide agencies. The Champion for the development of the AMPA Regional ITS Architecture is Mid-Region Council of Governments staff. The champion is supported by the ITS (Sub-Committee) Committee of the Transportation Coordinating Committee (TCC) comprised of representatives of key stakeholders within the region. A designated MRCOG planning staff person will continue to champion the use and maintenance of the AMPA Regional ITS Architecture (along with input and consensus from the ITS Subcommittee) beyond the timeframe of this development effort Regional Stakeholders Stakeholder coordination and involvement is one of the key elements to the development of a regional ITS architecture. Because ITS often transcends traditional transportation infrastructure, it is important to consider a range of stakeholders beyond the traditional traffic, transit, and maintenance areas. In addition, it is important to consider stakeholders at a regional level in adjoining regions of the state. The AMPA Regional ITS Architecture includes a wide range of stakeholders. Many of these stakeholders, along with various other agencies, were present at one of the stakeholder meetings described in section 2 above. The following is a list of agencies/participants who were either present during the architecture development workshop and provided their input during the workshop, or who were contacted specifically by the development team for their inputs on the AMPA Regional ITS Architecture: <TBD-finish update> Bernalillo County Department of Public Works City of Albuquerque Department of Municipal Development (Traffic and Construction Services) City of Albuquerque Transit (ABQRIDE) City of Rio Rancho public works FHWA Page 15

21 Mid-Region Council of Governments (MRCOG) New Mexico DPS, Motor Transportation Division NM DPS NM Office of Emergency Management NMDOT District 3 and the ITS Bureau Rio Metro The AMPA Regional ITS Architecture is defined by a set of elements (or systems), each of which is owned (or operated or maintained) by a stakeholder. The above listing includes all the agencies that attended stakeholder meetings. Most, but not all of them own, operate, or maintain elements in the architecture. (An example of an agency that does not is FHWA, whose role in the AMPA Regional ITS Architecture is approval of the ITS Architecture and approval of projects for funding by the federal government that are represented therein.) Table 2 provides a listing of the full range of stakeholders assigned to elements in the AMPA Regional ITS Architecture. The table provides a name and description of the agency, department, or organization represented by the stakeholder. Table 2. Stakeholders Stakeholder Name Stakeholder Description Albuquerque RTMC Represents major stakeholders with seats at the Albuquerque RTMC. Archive Data Users Bernalillo County Users (and their systems) of general archive data. County government agencies for Bernalillo County. Responsible for the County's website, tourism, convention and visitor's bureau, the County's Office of Emergency Management, etc. Bernalillo County Fire Department The fire and emergency response agency for Bernalillo County. Includes the Bernalillo County fire and EMS. Bernalillo County Public Safety A stakeholder group representing both the Bernalillo County Sheriffs Office and the Bernalillo County Fire Department. Bernalillo County Public Works Division The Bernalillo County department responsible for the maintenance, construction, and traffic operations of county roads. Bernalillo County Sheriffs Office Bernalillo County/City of Albuquerque The Bernalillo County office that dispatches the Bernalillo County Sheriff vehicles to incidents on the County's roads. This stakeholder represents Bernalillo County and the City of Albuquerque. It implies joint ownership in the elements it is the stakeholder for. Page 16

22 Stakeholder Name City of Albuquerque City of Albuquerque Aviation Department City of Albuquerque Department of Municipal Development City of Albuquerque Environmental Health Department City of Albuquerque Fire Department City of Albuquerque Police Department City of Albuquerque Public Safety City of Albuquerque Transit Department City of Rio Rancho City of Rio Rancho Fire Department City of Rio Rancho Police Department City of Rio Rancho Public Works Contract Transport Companies Stakeholder Description Municipal government agencies in the City of Albuquerque. Responsible for the City's website, department of commerce, convention and visitor's bureau, the City's Office of Emergency Management, etc. City of Albuquerque department responsible for the operation of Albuquerque International Airport. City of Albuquerque department responsible for traffic operations as well as maintenance and construction activities (including roadway maintenance and signal maintenance) throughout the City. The department is also responsible for the installation and maintenance of traffic signals, street lights, flashing beacons, signs, markings, and the permit parking program for the City. City of Albuquerque department responsible for emissions inspections and testing. City of Albuquerque department responsible for fire and EMS dispatch and response. City of Albuquerque department responsible for police dispatch and response. A stakeholder group representing both the City of Albuquerque Police Department and the City of Albuquerque Fire Department. City of Albuquerque department responsible for transit operations (ABQ RIDE) throughout the City. Municipal government for the City of Rio Rancho. Responsible for the City's website, department of commerce, convention and visitor's bureau, etc. City of Rio Rancho Fire Department, which is also responsible for the City of Rio Rancho EOC. Represents the Police Department for the City of Rio Rancho. City of Rio Rancho department responsible for maintenance, construction, and traffic operations throughout the City. Emergency medical service providers that offer ambulance services and medical transports. Page 17

23 Stakeholder Name Financial Institution Independent School Districts Kirtland AFB Local Media Local Transit Agencies Mid Region Council of Governments Municipal Public Safety Municipalities New Mexico Department of Information Technology New Mexico Department of Public Safety - DPS Stakeholder Description Financial and banking institutions that play a role in the transfer of funds for fare collection as well as for other fee based transportation services. Public school districts. The districts have been included for their role in providing "fixed route" transit services and in supporting emergency evacuations with their fleet of school buses. Kirtland Air Force Base, located in Albuquerque, NM. Represents both print (newspaper) and broadcast (TV, radio) news media. Represents local transit agencies that operate in the Region that are not specifically called out by this architecture (e.g. JFSA - Jewish Family Service of Albuquerque, SECA - Statewide Employees Commuter Association, etc.). MRCOG is the Metropolitan Planning Organization (MPO) for the Albuquerque Metropolitan Planning Area (AMPA). The MPO is responsible for carrying out the metropolitan transportation planning process which includes developing transportation plans and programs including the MTP and TIP. In addition, MRCOG includes the ITS Subcommittee which, along with NMDOT and FHWA, maintains the AMPA regional ITS Architecture. In addition, MRCOG maintains the Consolidated Traffic Counts Database and Travel Time Database in support of MRCOG Planning functions including travel demand forecasting and the Congestion Management Process (CMP). Represents local or municipal public safety (fire/ems districts and municipal police) that are not explicitly represented in the architecture. This includes dispatch functions, PSAPs (public safety answering points), etc. operated at the municipal level (in the future these may be regional in nature). Represents the municipalities or villages located within the Region that are not specifically called out by the ITS architecture. This includes the Villages of Los Ranchos, Corrales, and Los Lunas and the Town of Bernalillo. The mission of the Department of Information Technology is to provide costeffective and efficient enterprise products, services and solutions within a secure and reliable environment for our customers through leadership, strategic planning, standards and policy, architecture and oversight. New Mexico Department of Public Safety includes the State Police and the Motor Transport Division. Page 18

24 Stakeholder Name New Mexico Department of Veterans Services New Mexico National Guard NMDOT - New Mexico Department of Transportation NMDOT District 3 NOAA Other Counties Private Commercial Carriers Private HAZMAT Providers Private Sector Traveler Information Service Providers Private Tow/Wrecker Providers Private Traffic Data Provider Private Weather Information Provider Public/Private Utilities Rail Operators Regional Airports Stakeholder Description Represents the New Mexico Department of Veterans Services. The National Guard for the State of New Mexico. The Statewide stakeholder for the New Mexico Department of Transportation. Represents the District 3 offices of the New Mexico Department of Transportation, located in Albuquerque, New Mexico. National Oceanic and Atmospheric Administration (includes the National Weather Service). Represents the government agencies in adjacent counties to the AMPA geographic region. Private owners of commercial vehicles that carry good throughout the state. Private responders to HAZMAT incidents. They are secondary responders to incidents. Local, regional and national information service providers that provide travel information to the traveling public (both subscription service and general broadcast information). Includes internet sites, service bureaus, etc. Private companies that provide tow or wrecker services for the Region. Private companies that provide traffic data based on sensors they place at the roadside, or based on probe measurement data. Weather information providers that provide regional weather information to regional agencies. Public or private utility companies that operate within the Region. Operators of private rail systems (e.g. BNSF, Amtrak, etc.), including passenger and freight. Represents the regional airports that are within the Region. Page 19

25 Stakeholder Name Regional Event Coordinators Regional Medical Centers Regional Parking Management Providers Regional Public Safety Agencies Regional Transit Providers Rio Metro Regional Transit District Sandia Labs Sandoval County Sandoval County Fire Department Sandoval County Public Works Sandoval County Sheriff Travelers Stakeholder Description This entity supports the information exchange/coordination with various special event activities to include the Balloon Fiesta and the State Fair. It also includes groups that promote events, such as a Chamber of Commerce or Visitor's Bureau. Agencies that own hospitals and trauma centers. Includes the personnel and equipment to operate Life Flight systems. This stakeholder represents all of the agencies that provide parking management within the Region. This stakeholder is a stakeholder group representing all public safety agencies within the Region. This stakeholder is a stakeholder group representing all the Region's transit agencies and transit operators. The Rio Metro Regional Transit District is the primary regional transit provider for Bernalillo, Sandoval and Valencia counties, offering transit service between municipalities and across county lines. Rio Metro manages the New Mexico Rail Runner Express commuter rail and operates and/or funds select bus routes in the three-county area. Rio Metro s services also provide links to other statewide destinations and transportation markets including Santa Fe, Taos, and Socorro. The agency's top priority is providing service that enables customers to access regional destinations, a critical transportation need since tens of thousands of trips occur each day between different towns, cities, Tribal areas, and counties in the service area. Represents the controlling body of Sandia Labs County government for Sandoval County. Responsible for the County's website, tourism, convention and visitor's bureau, etc. The fire and emergency response agency for Sandoval County. Includes the Sandoval County fire and EMS. The Sandoval County department responsible for the maintenance, construction, and traffic operations of county roads. The Sandoval County office that dispatches the Sandoval County Sheriff's vehicles to incidents on the County's roads. Traveling public accessing various modes of transportation, including surface street, air, rail/transit, and non-motorized. Page 20

26 Stakeholder Name Tribal Governments University of New Mexico Stakeholder Description Represents the Indian reservations or Pueblos within the Region, or just outside the boundaries of the Region. Includes Isleta, Laguna, Santa Ana, Zia, and all Navajo reservations. The University of New Mexico. Includes all departments of the University, including the UNM events department and the UNM Police Department. The stakeholders listed in Table 2 represent a mix of specific agencies or organizations and generic names used to represent a variety of stakeholders. An example of a specific agency or organization from the architecture is City of Albuquerque Transit Department, which represents the City of Albuquerque department responsible for transit operations (ABQ RIDE) throughout the City. An example of a generic stakeholder name would be Municipalities, which represents all of the departments or agencies (police, fire, EMS, traffic, maintenance and construction, etc.) at the municipal level. Another example of a general stakeholder in the architecture definition is Tribal Government, which would represent the government of pueblos such as Isleta, Laguna, and Santa Ana Pueblos Operational Concepts An Operational Concept documents each stakeholder s current and future roles and responsibilities in the operation of the regional ITS system. The operational concept documents these roles and responsibilities across a range of transportation services. The services covered by the AMPA Regional ITS Architecture are: Traffic Signal Control: the development of signaling systems that react to changing traffic conditions and provide coordinated intersection timing over a corridor, an area, or multiple jurisdictions. Highway Management: the development of systems to monitor freeway (or tollway) traffic flow and roadway conditions, and provide strategies such as ramp metering or lane access control to improve the flow of traffic on the freeway. Includes systems to provide information to travelers on the roadway. Incident Management: the development of systems to provide rapid and effective response to incidents. Includes systems to detect and verify incidents, along with coordinated agency response to the incidents. Transit Management: the development of systems to more efficiently manage fleets of transit vehicles or transit rail. Includes systems to provide transit traveler information both pre-trip and during the trip as well as electronic fare payment systems used on transit vehicles. Page 21

27 Traveler Information: the development of systems to provide static and real time transportation information to travelers. Emergency Management: the development of systems to provide emergency call taking, public safety dispatch, and emergency operations center operations. Maintenance and Construction Management: the development of systems to manage the maintenance of roadways in the region, including winter snow and ice clearance. Includes the managing of construction operations. Archive Data Management: the development of systems to collect transportation data for use in non-operational purposes (e.g. planning and research). Electronic Payment: the development of systems for performing electronic toll collection (this concept is covered in various other transportation services). Cooperative Vehicle Safety System: the development of vehicle to infrastructure (V2I) or vehicle to vehicle (V2V) communications to support applications that improve safety and mobility. Table 3 identifies the roles and responsibilities of key stakeholders for the specified range of transportation services. Transportation Service Traffic Signal Control Table 3. Stakeholder Roles and Responsibilities Stakeholder City of Albuquerque Department of Municipal Development Roles/ Responsibilities Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on City streets. Operate traffic signal systems on City owned streets, including traffic signals, sensor systems (CCTV), and right of way requests. Provide traffic information reports to regional information service providers, private information service providers, and the NMDOT Advanced Traveler Information System. Provide traffic information to regional agencies including transit, emergency management, maintenance and construction, and the media. Provide traffic information to travelers through City's DMS. Coordinate traffic information and control with other municipal and county TOCs, the Regional TOC, and the Statewide TMC. Coordinate HRI signal adjustments with private Rail Operators and NMDOT. Operate reversible lane signals and controls on City streets and bridges. Page 22

28 Transportation Service Stakeholder City of Rio Rancho Municipalities Roles/ Responsibilities Provide security monitoring of critical infrastructure for the City. Provide transit signal priority for regional fixed route transit vehicles. Provide emergency signal preemption for the City's Fire and EMS vehicles. Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on City streets. Operate traffic signal systems on City owned streets, including traffic signals, sensor systems (CCTV), and right of way requests. Provide traffic information reports to regional information service providers, private information service providers, and the NMRoads. Provide traffic information to regional agencies including transit, emergency management, maintenance and construction, and the media. Provide traffic information to travelers through City's DMS. Coordinate traffic information and control with other municipal and county TOCs, the Regional TOC, and the Statewide TMC. Coordinate HRI signal adjustments with private Rail Operators and NMDOT. Operate reversible lane signals and controls on City streets and bridges. Provide security monitoring of critical infrastructure for the City. Provide transit signal priority for regional fixed route transit vehicles. Provide emergency signal preemption for the City's Fire and EMS vehicles. Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on municipal streets. Operate traffic signal systems on municipality owned streets, including traffic signals, sensor systems, and right of way requests. Provide traffic information reports to regional information service providers, private information service providers, and the NMRoads. Provide traffic information to regional agencies including transit, emergency management, maintenance and construction, and the media. Provide traffic information to travelers through municipality DMS. Page 23

29 Transportation Service Stakeholder Bernalillo County Public Works Division NMDOT Roles/ Responsibilities Coordinate traffic information and control with other municipal and county TOCs, the Regional TOC, and the Statewide TMC. Coordinate HRI signal adjustments with private Rail Operators and NMDOT. Operate reversible lane signals and controls on municipal streets and bridges. Provide security monitoring of critical infrastructure for the municipality. Provide emergency signal preemption for the municipality's Fire and EMS vehicles. Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on county roads. Operate traffic signal systems on county owned streets, including traffic signals, sensor systems, and right of way requests. Provide traffic information reports to regional information service providers, private information service providers, and the NMRoads. Provide traffic information to regional agencies including transit, emergency management, maintenance and construction, and the media. Provide traffic information to travelers through County DMS. Coordinate traffic information and control with other municipal and county TOCs, the Regional TOC, and the Statewide TMC. Coordinate HRI signal adjustments with private Rail Operators. Operate reversible lane signals and controls on County streets and bridges. Provide emergency signal preemption for the County Fire and EMS vehicles. Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on State owned arterials. Operate traffic signal systems on State owned arterials, including traffic signals, sensor systems, and right of way requests. Provide traffic information reports to regional information service providers, private information service providers, and the NMRoads. Page 24

30 Transportation Service Highway Management Stakeholder NMDOT Roles/ Responsibilities Provide traffic information to regional agencies including transit, emergency management, maintenance and construction, and the media. Provide traffic information to travelers through State owned DMS. Coordinate traffic information and control with municipal and county TOCs and with other NMDOT TOCs/TMC. Coordinate HRI signal adjustments with private Rail Operators and NMDOT. Operate reversible lane signals and controls on NMDOT arterials, highways, and bridges. Operate roadway closure devices in NMDOT arterials and highways and alert emergency management agencies, maintenance and construction agencies, and public and private information service providers of the road closure. Provide security monitoring of critical infrastructure for the State. Operate network monitoring equipment (CCTV Cameras, field sensors, etc.) on State owned highways. Operate ramp metering devices and lane control equipment on State owned highways. Provide traffic information reports to regional information service providers, private information service providers, and the NMRoads. Provide traffic information reports to regional information service providers, private information service providers, and NMRoads. Coordinate rail schedules and adjustments for high speed rail intersections with private rail operators and Rio Metro. Operate roadway closure devices in NMDOT arterials and highways and alert emergency management agencies, maintenance and construction agencies, and public and private information service providers of the road closure. Provide security monitoring of critical infrastructure for the State. Coordinate traffic information and traffic control with other regional TMCs. Coordinate traffic information other State's regional TMCs or Statewide TMC. Page 25

31 Transportation Service Incident/Emergency Management Stakeholder City of Albuquerque Department of Municipal Development City of Rio Rancho Municipalities Bernalillo County Public Works Division NMDOT Roles/ Responsibilities Perform network monitoring for detection and verification of incidents on City owned streets. Provide incident information to the City's emergency responders through the 911/Emergency Communications Center and directly to other regional emergency responders. Coordinate maintenance resources for incident response with the City's Maintenance Department. Perform network monitoring for detection and verification of incidents on City owned streets. Provide incident information to the City's emergency responders through the Public Safety Communications Center and directly to other regional emergency responders. Coordinate maintenance resources for incident response with the City's Public Infrastructure Department. Perform network monitoring for detection and verification of incidents on municipality owned streets. Provide incident information to the municipality's emergency responders, including the Municipality's Police and Fire Departments and other regional emergency responders. Coordinate maintenance resources for incident response with the Municipality's Public Works Department. Perform network monitoring for detection and verification of incidents on County owned streets. Provide incident information to the County's emergency responders through the 911/Sheriff Communications Center and directly to other regional emergency responders. Coordinate maintenance resources for incident response with the County's Public Works Department. Perform network monitoring for detection and verification of incidents on State owned highways and arterials. Provide incident information to travelers via traffic information devices on highways (e.g. DMS, NMROADS, etc). Provide incident information to the City's emergency responders through the 911/Emergency Communications Center and directly to regional emergency responders, including the State Police, County Sheriff, County Fire and EMS, and City Police, Fire and EMS. Page 26

32 Transportation Service Stakeholder New Mexico Department of Public Safety - DPS Roles/ Responsibilities Coordinate maintenance resources for incident response with the State's Maintenance and Construction Dispatch the NMDOT D3 HELP Courtesy Patrol vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Coordinate incident response with the state police and regional public safety providers. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Dispatch the NMDOT D3 HELP Courtesy Patrol vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Detect HAZMAT spills of leaks at monitoring stations. Report threat information to regional emergency management agencies, traffic agencies, and maintenance agencies. Provide local signal preemption to County public safety vehicles. Receive Amber Alert and other Wide Area Alert information from state police and post alert information on NMDOT DMS/DMS/DMS. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems, the media, and on the NMDOT website. Dispatch State Police vehicles for incidents on the Region's highways. Coordinate incident response with other public safety agencies (police, fire, EMS, sheriff, etc.) as well as with NMDOT. Perform incident detection and verification for the highways within the region, and provide this information to traffic and other public safety agencies. Coordinate maintenance resources in response to incidents on state highways with regional maintenance providers. Coordinate an incident response with regional rail operations for incidents involving rail. Page 27

33 Transportation Service Stakeholder Roles/ Responsibilities Dispatch State Police vehicles (and track their location) as well as coordinate with all other public safety agencies within the Region. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function Coordinate with regional hospitals for care facility status. Receive local signal preemption from the municipalities within the Region. Receive and respond to threat information from the state agency, City or municipality TOC regarding critical infrastructure. Generate Amber Alerts and distribute them to regional emergency management agencies, transit agencies, traffic agencies, and the media. Generate and coordinate wide area alerts and distribute them to regional emergency management agencies, transit agencies, traffic agencies, regional information service providers, and the media. Plan and coordinate region wide emergency plans, evacuation and reentry plans, and disaster management plans dealing with HAZMAT incidents. Provide regional traffic, transit, emergency management, and maintenance operations with disaster information to disseminate to the traveling public. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Operate the New Mexico Statewide EOC. City of Albuquerque Public Safety Department Receive emergency calls for incidents within the City. Coordinate public safety resources for incident response with the City's TOC. Coordinate incident response with all City public safety agencies (police, fire and EMS). Dispatch the City's police vehicles (and track their location), fire vehicles and EMS vehicles as well as coordinate with all other public safety agencies within the region. Page 28

34 Transportation Service Stakeholder City of Rio Rancho Public Safety Department Roles/ Responsibilities Perform incident detection and verification for the streets within the City, and provide this information to the City's TOC. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate maintenance resources in response to incident with the City. Coordinate with ambulance services in response to incidents within the City. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Coordinate with regional hospitals for care facility status as well as patient care and status Receive local signal preemption from the City of Albuquerque. Receive and respond to threat information from the City's TOC regarding critical infrastructure. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Responding to transit emergencies/alarms on-board transit vehicles or at regional transit facilities. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Receive emergency calls for incidents within the City. Coordinate public safety resources for incident response with the City's TOC. Coordinate incident response with all City public safety agencies (police, fire and EMS). Dispatch the City's police vehicles (and track their location), fire vehicles and EMS vehicles as well as coordinate with all other public safety agencies within the region. Page 29

35 Transportation Service Stakeholder Roles/ Responsibilities Perform incident detection and verification for the streets within the City, and provide this information to the City's TOC. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate maintenance resources in response to incident with the City. Coordinate with ambulance services in response to incidents within the City. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Coordinate with regional hospitals for care facility status as well as patient care and status. Receive local signal preemption from the City of Albuquerque. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Operate the City's EOC. Municipal Police Departments Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Responding to transit emergencies/alarms on-board transit vehicles or at regional transit facilities. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Receive emergency calls for incidents within the municipalities. Coordinate public safety resources for incident response with the municipality's TOC. Dispatch the municipality's police vehicles and coordinate with the municipality's fire departments (as well as coordinate with all other public safety agencies within the region) for incidents. Page 30

36 Transportation Service Stakeholder Roles/ Responsibilities Perform incident detection and verification for the streets within the municipalities, and provide this information to the municipality TOCs. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate maintenance resources in response to incident with the municipality. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Coordinate with regional hospitals for care facility status Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Operate the Municipal EOCs. Municipal Fire Departments Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Responding to transit emergencies/alarms on-board transit vehicles or at regional transit facilities. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Coordinate public safety resources for incident response with the municipality's TOC. Dispatch the municipality's fire and EMS vehicles and coordinate with the municipality's police department (as well as coordinate with all other public safety agencies within the region) for incidents. Perform incident detection and verification for the streets within the municipalities, and provide this information to the municipality TOCs. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate with ambulance services in response to incidents within the City. Coordinate maintenance resources in response to incident with the municipality. Page 31

37 Transportation Service Stakeholder Bernalillo County Public Safety Roles/ Responsibilities Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Coordinate with regional hospitals for care facility status as well as patient care and status. Receive local signal preemption from the municipalities within the Region. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Responding to transit emergencies/alarms on-board transit vehicles or at regional transit facilities. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Receive emergency calls for incidents within the county. Dispatch the County's sheriff vehicles (and track their location) and fire and EMS vehicles as well as coordinate with all other public safety agencies within the region. Perform incident detection and verification for the streets within the county, and provide this information to the regional TMCs. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate maintenance resources in response to incident with the County. Provide evacuation, incident, and transportation system status information to regional public information systems. Coordinate with regional hospitals for patient care and status. Receive local signal preemption from County signals. Perform incident detection and verification for streets within the counties of the Region. Receive Amber Alert and other Wide Area Alert information from state police. Page 32

38 Transportation Service Stakeholder Sandoval County Roles/ Responsibilities Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Operate the County EOC. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Receive emergency calls for incidents within the county. Dispatch the County's sheriff vehicles (and track their location) and fire and EMS vehicles as well as coordinate with all other public safety agencies within the region. Perform incident detection and verification for the streets within the county, and provide this information to the regional TMCs. Coordinate an incident response with regional rail operations for incidents involving rail. Coordinate maintenance resources in response to incident with the County. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Coordinate with regional hospitals for patient care and status. Receive local signal preemption from NMDOT signals. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Operate the County's EOC. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans Provide evacuation, incident, and transportation system status information to regional public information systems. Page 33

39 Transportation Service Stakeholder University of New Mexico New Mexico General Services Department New Mexico National Guard Roles/ Responsibilities Dispatch the University of New Mexico's campus police vehicles. Perform incident detection and verification on the UNM campus and the streets surrounding the campus, and provide this information to the regional TMCs. Coordinate incident response with the regional public safety providers. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information from the Statewide EOC and the Regional EOCs. Operate the University's EOC. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Provide evacuation, incident, and transportation system status information to regional public information systems. Dispatch the forest service and other public department vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information the Statewide EOC. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Page 34

40 Transportation Service Stakeholder Tribal Public Safety Contract Transport Providers (Ambulance Services) Roles/ Responsibilities Dispatch the New Mexico National Guard vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information the Statewide EOC. Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Dispatch the private ambulances and other EMS vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Receive Amber Alert and other Wide Area Alert information from state police. Coordinate with regional hospitals for patient care and status. Perform incident detection and verification for streets within the Tribal boundaries. Aid in the coordination of region wide emergency plans, evacuation and reentry plans, and disaster management plans. Participates in the incident response, coordination, and reporting of the Regional Communications Network in a coordination effort only (no dispatch function). Dispatch the private ambulances and other EMS vehicles (and track their location) and coordinate with all other public safety agencies and communications centers within the Region. Coordinates with regional medical centers regarding the status of the care facility as well as the patient status enroute to the medical center. Receive Amber Alert and other Wide Area Alert information from state police. Receive Wide Area Alert information the Statewide EOC and all other regional and municipal EOCs. Page 35

41 Transportation Service Transit Management Stakeholder City of Albuquerque Transit Department City of Rio Rancho Roles/ Responsibilities Receive early warning information and threat information from the statewide EOC and/or the department of homeland security. Track vehicle location and evaluate schedule performance on all agency fixed route transit vehicles, light rail vehicles, and paratransit vehicles. Provide transit schedule and fare information to the agency's transit information center, the NMRoads, regional traveler information providers, and private sector traveler information service providers. Provide fixed route bus service or the City and outlying areas (on agreement). Provide demand response (paratransit) bus service for the agency defined service area, with the ability to provide a demand response transit plan from the agency's transit information center. Provide transit passenger electronic fare payment on all agency fixed route, and demand response vehicles. Provide transit security on all agency transit vehicles and at transit transfer centers through silent alarms, sensors, and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle condition reports on all agency fixed route, and demand response vehicles. Obtain traffic signal priority for designated fixed route transit vehicles from the cities within the agency's service area through the cities field equipment. Coordinate transit service with other regional transit providers, as well as regional intermodal terminals and regional airports. Provide transit traveler information to the agency website, private sector traveler information services, and the NMRoads, as well as making it available on all transit information kiosks. Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Track vehicle location and evaluate schedule performance on all agency paratransit vehicles. Provide transit schedule and fare information to the agency's website, the NMRoads, and private sector traveler information service providers. Page 36

42 Transportation Service Stakeholder Local Transit Roles/ Responsibilities Provide demand response (paratransit) bus service for the agency defined service area, with the ability to provide a demand response transit plan from the agency's transit information center. Provide transit passenger electronic fare payment on all agency paratransit vehicles. Provide transit security on all agency paratransit vehicles through silent alarms, sensors, and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle condition reports on all agency paratransit vehicles. Coordinate transit service with other regional transit providers, as well as regional intermodal terminals and regional airports. Provide transit traveler information to the agency website, private sector traveler information services, and the NMRoads, as well as making it available on all transit information kiosks. Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Track vehicle location and evaluate schedule performance on all agency transit vehicles. Provide transit schedule and fare information to the agency's website, the NMRoads, and private sector traveler information service providers. Provide fixed route bus service for the agency defined service area. Provide demand response (paratransit) bus service for the agency defined service area, with the ability to provide a demand response transit plan from the agency's transit information center. Provide transit passenger electronic fare payment on all transit vehicles. Provide transit security on all agency transit vehicles through silent alarms and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle condition reports on all agency transit vehicles. Coordinate transit service with other regional transit providers, as well as regional intermodal terminals and regional airports. Page 37

43 Transportation Service Stakeholder Roles/ Responsibilities Provide transit traveler information to the agency website, private sector traveler information services, and the NMRoads, as well as making it available on all transit information kiosks. Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Independent School Districts Track vehicle location and evaluate schedule performance on all school district buses. Provide school bus schedule and route information to the school district website. Provide fixed route school bus service for the cities, municipalities, and counties within the Region. Provide transit security on all transit vehicles through silent alarms and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle conditions reports on all Independent School District buses. Page 38

44 Transportation Service Stakeholder Rio Metro Roles/ Responsibilities Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Track vehicle location and evaluate schedule performance on all Rio Metro transit vehicles. Track rail vehicle location and provide positive train control for rail vehicle operations Provide transit schedule and fare information to the Rio Metro website, the NMRoads, and private sector traveler information service providers. Provide fixed route transit service for the defined service area Provide Rail Runner service between the City of Albuquerque and cities north (Santa Fe) and South (Belen). University of New Mexico Provide demand response bus service for the agency defined service area, with the ability to provide a demand response transit plan from the agency's transit information center. Provide transit passenger electronic fare payment on all agency transit vehicles. Provide transit security on all agency transit and rail vehicles through silent alarms and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle conditions reports on all Rio Metro transit vehicles. Coordinate transit service with other regional transit providers, as well as regional intermodal terminals and regional airports. Provide transit traveler information to the agency website, private sector traveler information services, and the NMRoads, as well as making it available on all transit information kiosks. Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Track vehicle location and evaluate schedule performance on all UNM courtesy shuttles. Provide transit schedule and fare information to the UNM website and to private sector traveler information service providers. Provide fixed route bus service for the university and the surrounding area. Page 39

45 Transportation Service Traveler Information Stakeholder NMDOT Roles/ Responsibilities Provide transit passenger electronic fare payment on all courtesy shuttles. Provide transit security on all agency transit vehicles through silent alarms and monitoring systems. Provide automated transit maintenance scheduling through automated vehicle condition reports on all agency courtesy shuttles. Coordinate transit service with other regional transit providers, as well as regional intermodal terminals and regional airports. Coordinate emergency plans with Municipal, County, and Statewide EOCs and provide emergency transit services for evacuations, fires, and disasters (including re-entry). Operate NMROADS. Collect traffic, maintenance and construction information, and transit schedule and fare information from regional providers. Provide traffic, maintenance and construction and transit information to the media, private travelers, and various traveler information services (including the agency website). Private Traveler Information Service Providers City of Albuquerque Department of Municipal Development City of Rio Rancho Coordinate and share traveler information with all other traveler information providers within the region. Provide traveler information to private travelers (in vehicle, personal computing device, or kiosk) upon request. Provide traveler information to the media. Collect traffic, incident, transit schedule, road maintenance and weather information and provide it to the media and private travelers. Coordinate and share traveler information with all other traveler information providers within the region. Collect traffic, maintenance and construction information, and transit schedule and fare information from regional providers. Provide traffic, maintenance and construction and transit information to the media, private travelers, and various traveler information services (including the agency website). Collect traffic, maintenance and construction information, and transit schedule and fare information from regional providers. Page 40

46 Transportation Service Maintenance and Construction Management Stakeholder Bernalillo County Sandoval County City of Albuquerque Department of Municipal Development Roles/ Responsibilities Provide traffic, maintenance and construction and transit information to the media, private travelers, and various traveler information services (including the agency website). Collect traffic, maintenance and construction information, and transit schedule and fare information from regional providers. Provide traffic, maintenance and construction and transit information to the media, private travelers, and various traveler information services (including the agency website). Collect traffic, maintenance and construction information, and transit schedule and fare information from regional providers. Provide traffic, maintenance and construction and transit information to the media, private travelers, and various traveler information services (including the agency website). Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Collect road weather information with agency field equipment and distribute it to regional traffic, maintenance and transit agencies as well as the national weather service and the media. Provide road weather information to regional emergency management providers, regional traffic agencies, regional transit agencies, and regional public information services. Provide winter road maintenance for all City streets and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic center. Provide maintenance of streets within the city, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, City public safety agencies, and to travelers (through ISPs). Dispatch City maintenance vehicles. Page 41

47 Transportation Service Stakeholder City of Rio Rancho Department of Public Infrastructure Roles/ Responsibilities Provide maintenance to all field equipment owned and operated by the City. Manage work zones on all City maintenance and construction activities, as well as monitors work zone safety with agency field devices and vehicles. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Collect road weather information with agency field equipment and distribute it to regional traffic, maintenance and transit agencies as well as the national weather service and the media. Provide road weather information to regional emergency management providers, regional traffic agencies, regional transit agencies, and regional public information services. Provide winter road maintenance for all City streets and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic center. Provide maintenance of streets within the city, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, City public safety agencies, and to travelers (through ISPs). Dispatch City maintenance vehicles. Provide maintenance to all field equipment owned and operated by the City. Manage work zones on City streets. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Page 42

48 Transportation Service Stakeholder Municipalities Bernalillo County Public Works Division Roles/ Responsibilities Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Provide winter road maintenance for all municipal streets and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic center. Provide maintenance of streets within the municipalities, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, municipal public safety agencies, and to travelers (through ISPs). Dispatch municipal maintenance vehicles. Provide maintenance to all field equipment owned and operated by the municipalities. Manage work zones on municipal streets. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Page 43

49 Transportation Service Stakeholder Sandoval County Public Works Roles/ Responsibilities Collect road weather information with agency field equipment and distribute it to regional traffic, maintenance and transit agencies as well as the national weather service and the media. Provide road weather information to regional emergency management providers, regional traffic agencies, regional transit agencies, and regional public information services. Provide winter road maintenance for all County roads and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic center. Provide maintenance of streets within the counties, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, municipal public safety agencies, and to travelers (through ISPs). Dispatch County maintenance vehicles. Provide maintenance to all field equipment owned and operated by the Counties. Manage work zones on all County maintenance and construction activities, as well as monitors work zone safety with agency field devices and vehicles. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Provide winter road maintenance for all County roads and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic center. Page 44

50 Transportation Service Stakeholder NMDOT District 3 Roles/ Responsibilities Provide maintenance of streets within the County, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, municipal public safety agencies, and to travelers (through ISPs). Dispatch County maintenance vehicles. Provide maintenance to all field equipment owned and operated by the Counties. Manage work zones on County roads. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Receive a request for maintenance resources for incident response from regional emergency management agencies. Coordinate maintenance resources for incidents with other regional maintenance providers. Receive vehicle location information from agency maintenance and construction vehicles. Receive vehicle maintenance conditions from agency maintenance and construction vehicles and coordinate fleet maintenance with agency equipment repair facility/garage. Collect road weather information with agency field equipment and distribute it to regional traffic, maintenance and transit agencies as well as the national weather service and the media. Provide road weather information to regional emergency management providers, regional traffic agencies, regional transit agencies, and regional public information services. Provide automated roadway treatment on agency owned roads or bridges. Provide winter road maintenance for all agency arterials and highways and provide roadway maintenance status information to regional public safety agencies, regional transit agencies, and the agency's traffic centers. Provide maintenance of state highways within the region, including pavement maintenance and all construction activities. Provide maintenance status to regional transit agencies, regional emergency management agencies, and to travelers (through ISPs). Page 45

51 Transportation Service Archived Data Management Stakeholder City of Albuquerque Public Works Traffic Bernalillo County Public Works Division NMDOT Mid Region Council of Governments Roles/ Responsibilities Dispatch agency maintenance vehicles. Provide maintenance to all field equipment owned and operated by the agency. Manage work zones on all agency maintenance and construction activities, as well as monitors work zone safety with agency field devices and vehicles. Coordinates maintenance and construction activities with other regional maintenance and construction agencies. Distributes maintenance and construction plans and work zone information to regional information service providers, regional traffic operations, emergency operations, rail operations, and the media. Collect and archive traffic information from City, bike, and pedestrian-count devices and from the City's TOC. Coordinate with MRCOG's Consolidated Traffic Counts Database and NMDOT's historical database. Collect and archive traffic information from County, bike, and pedestrian-count devices and from the County's TOC. Coordinate with MRCOG's Consolidated Traffic Counts Database and NMDOT's historical database. Coordinate with NMDOTs Statewide Crash Information System for regional and statewide crash records. Collect and archive emergency safety and crash information from regional emergency management providers. Collect and archive transit information about transit services within the Region. Coordinate with other regional traffic databases. Collect and archive maintenance and construction information from the agency's maintenance garage and regional maintenance departments. Collect and archive traffic, bike, and pedestrian-count information from regional traffic management providers for planning purposes. Collect and archive bike and pedestrian count information as part of the Consolidated Traffic Counts program Collect and archive traffic count information from the MRCOG's own field equipment. Coordinate with other regional traffic databases. Function as a data warehouse for emergency archive information, maintenance and construction information, and other traffic information. Page 46

52 Transportation Service Stakeholder Roles/ Responsibilities As the MPO, perform applicable Regional Emissions Analysis per EPA requirements under the National Ambient Air Quality Standards (NAAQS) to ensure transportation plans comply with SIP and regional emissions budgets for identified pollutants. Page 47

53 5. Systems Inventory The AMPA Regional ITS Architecture inventory is a list of elements that represent all existing and planned ITS systems in the region as well as non-its systems that provide information to or get information from the ITS systems. These elements are owned, operated, or maintained by stakeholder agencies, companies, or groups (defined in the previous section). The focus of the inventory is on those systems that support, or may support, interfaces that cross stakeholder boundaries (e.g. public to private interfaces). The vast majority of the inventory represents ITS systems within the AMPA Region, but the inventory does contain some elements that represent systems in adjoining regions or those that are statewide in nature. An example of an element that is statewide in nature (and more completely described in the New Mexico Statewide ITS Architecture) would be NMDOT Signal Lab, which represents the statewide center responsible for operating traffic signals for NMDOT. The significance of having NMDOT Signal Lab in the AMPA Regional ITS Architecture is because it would interface with the NMDOT Traffic Signals" specific to the AMPA region. Each element in the inventory is described by a name, the associated stakeholder, a description, general status (e.g. existing or planned), and the associated subsystems or terminators from the National ITS Architecture that the elements is mapped to for modeling purposes Systems by Stakeholder Table 4 sorts the inventory by stakeholder so that each stakeholder can easily identify all the elements that are defined in the architecture. For each element in the inventory, the table provides an element description and an indication of whether the element exists or is planned. The majority of elements in the inventory represent a specific existing or planned system. Some examples of specific systems are the Bernalillo County Traffic Operations Center or the City of Albuquerque Traffic Operations Center. Some of the elements represent sets of devices, rather than a single specific system or device. An example of this type of element is the element NMDOT CCTV. This element represents all of the CCTV that are, or will be, operated by NMDOT in the region. The element describes the type of field device, not the specific number of devices. A third type of element in the inventory is a generic element that represents all of the systems of a certain type in the region. An example of this type of element is Municipal ITS Field Equipment which not only represents various ITS field devices, it also represents all of the ITS components either deployed or planned at the municipal level. These generic elements have been created for two primary reasons. First, they represent elements with similar types of interfaces. So, from a standardization standpoint, describing how one of the major elements in the region (e.g. the City of Albuquerque TOC) interfaces with various public safety dispatch functions would be the same. Second, describing many systems with a single element helps keep the architecture from growing too large. Page 48

54 Table 4. Inventory sorted by Stakeholder Stakeholder Element Name Element Description Status Albuquerque RTMC Albuquerque RTMC Represents the Regional Traffic Management Center (RTMC) for the Planned Albuquerque metro area. The RTMC is jointly operated by regional traffic and public safety agencies. Archive Data Users Archive Data Users Any user of archive data products from any Regional archive management system. This may include individual users, computer applications, or modeling systems utilizing the archived data. Bernalillo County Bernalillo County Asset The asset management system for the County of Bernalillo. Planned Management System Bernalillo County Bernalillo County Emergency The emergency operations center (EOC) for Bernalillo County. Operations Center (EOC) Bernalillo County Bernalillo County Public Information System The office that provides the official interface between Bernalillo County traffic and public works departments and interests outside the departments such as the media. Bernalillo County Bernalillo County Traffic Planning System The archive system for Bernalillo County that uses traffic and traveler information as well as accident data for planning purposes. This function is maintained in the Bernalillo County Infrastructure Planning and Geo Resources section of Public Works. Bernalillo County Bernalillo County Website Transportation information website for Bernalillo County. In the future will include real-time construction, work zone, special event, incident, and traffic information. Bernalillo County Fire Bernalillo County Fire and EMS Fire and EMS vehicles owned and operated by Bernalillo County. Onboard Department Vehicles ITS systems may include mobile data terminals (MDTs), AVL, cameras, etc. Bernalillo County Public Safety Bernalillo County Public Works Division Bernalillo County Public Works Division Bernalillo County 911/ Sheriff Communications Center Bernalillo County CCTV Bernalillo County DMS The communication center that serves as the public safety answering point and the dispatch function for both the Bernalillo County Sheriff's department and the Bernalillo County Fire and EMS. Closed circuit television (CCTV) cameras owned and operated by Bernalillo County. Dynamic message signs owned and operated by Bernalillo County. Includes portable message signs for maintenance and construction activities or emergency conditions/warnings. Page 49

55 Stakeholder Element Name Element Description Status Bernalillo County Public Bernalillo County Field Sensors Traffic and vehicle sensors owned and operated by Bernalillo County. Works Division Bernalillo County Public Bernalillo County Fleet The equipment repair facility for Bernalillo County. Handles maintenance Works Division Management Facility and construction vehicles and equipment. Bernalillo County Public Works Division Bernalillo County ITS Field Equipment Field equipment owned and operated by Bernalillo County. Includes all other ITS field equipment that isn't specifically called out in the architecture (e.g. RWIS, Flood Gates, etc.). Bernalillo County Public Works Division Bernalillo County Public Works Division Bernalillo County Public Works Division Bernalillo County Public Works Division Bernalillo County Public Works Division Bernalillo County Sheriffs Office Bernalillo County Public Works Dispatch Bernalillo County Public Works Vehicles Bernalillo County Storage Facility Bernalillo County Traffic Operations Center Bernalillo County Traffic Signals Bernalillo County Sheriff Vehicles The maintenance and construction division for Bernalillo County. Operates as the dispatch function for Bernalillo County's maintenance and construction vehicles as well as snow plows. Maintenance and construction vehicles owned and operated by Bernalillo County (includes snow plows). May include AVL and MDTs onboard vehicles. The storage facility for maintenance and construction operations (e.g. gravel, dirt, extra vehicles, etc,) for Bernalillo County. The traffic operations center located for Bernalillo County that controls the traffic signal systems and other field equipment owned by Bernalillo County. Traffic signal systems owned and operated by Bernalillo County. May include preemption capabilities, video detection, pedestrian signals, etc. Sheriff vehicles owned and operated by the Bernalillo County Sheriff's Department. Onboard ITS systems may include mobile data terminals (MDTs), AVL, cameras, etc. The parking management system at the Mesa Del Sol amphitheater. Bernalillo County/City of Albuquerque Mesa Del Sol Amphitheater Parking System Planned City of Albuquerque City of Albuquerque Convention The City of Albuquerque Department of Tourism responsible for attracting and Visitors Bureau various travelers, conventions, etc. to the City of Albuquerque. City of Albuquerque City of Albuquerque Public The office that provides the official interface between the City of Information System Albuquerque traffic and maintenance departments and interests outside the departments such as the media. City of Albuquerque City of Albuquerque Smart Parking Management system for the City of Albuquerque. Planned Parking System City of Albuquerque City of Albuquerque Toll The department at the City of Albuquerque responsible for the collection of Planned Authority tolls at area river crossings. City of Albuquerque City of Albuquerque Toll Plazas Toll plazas at the City of Albuquerque's tolled river crossings. Planned Page 50

56 Stakeholder Element Name Element Description Status City of Albuquerque City of Albuquerque Website Transportation information website for the City of Albuquerque. In the future will include real-time construction, work zone, special event, incident, and traffic information. City of Albuquerque Albuquerque International The international airport that serves the Albuquerque area. Aviation Department Sunport City of Albuquerque Albuquerque International The parking management system that operates at the Albuquerque Planned Aviation Department Sunport Parking System International Airport. City of Albuquerque Department of Municipal Development City of Albuquerque Asset Management System The asset management system for the City of Albuquerque. Planned City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque CCTV Closed circuit television (CCTV) cameras owned and operated by the City of Albuquerque. Planned City of Albuquerque CV RSE City of Albuquerque connected vehicle roadside equipment Planned City of Albuquerque DMS City of Albuquerque Field Sensors City of Albuquerque Fleet Management Facility City of Albuquerque ITS Field Equipment City of Albuquerque Maintenance and Construction Vehicles Dynamic message signs owned and operated by the City of Albuquerque. May be shared resources with the NMDOT and Homeland Security. Traffic and vehicle sensors owned and operated by the City of Albuquerque. The equipment repair facility for the City of Albuquerque. Handles maintenance and construction vehicles and equipment. Field equipment owned and operated by the City of Albuquerque that is not expressly identified in this architecture (e.g. VIVDS, Flood Gates, security monitoring field equipment, etc.). Maintenance and construction vehicles owned and operated by the City of Albuquerque. Includes maintenance, construction, snow plows, etc. ITS technologies onboard vehicles may include AVL system, MDTs, etc. Planned Planned Planned Page 51

57 Stakeholder Element Name Element Description Status City of Albuquerque Department of Municipal Development City of Albuquerque Maintenance Dispatch The maintenance and construction division for the City of Albuquerque. Operates as the dispatch function for the City of Albuquerque public works (maintenance, construction, snow plows, etc.) vehicles. City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Department of Municipal Development City of Albuquerque Environmental Health Department City of Albuquerque Environmental Health Department City of Albuquerque Fire Department City of Albuquerque Police Department City of Albuquerque RWIS City of Albuquerque Storage Facility City of Albuquerque Traffic Operations Center City of Albuquerque Traffic Planning System City of Albuquerque Traffic Signal Shop City of Albuquerque Traffic Signals City of Albuquerque Emissions Monitoring Systems City of Albuquerque Environmental Health ITS Field Equipment City of Albuquerque Fire and EMS Vehicles City of Albuquerque Emergency Operations Center (EOC) Road Weather Information System (RWIS) operated and maintained by the City of Albuquerque. The storage facility for maintenance and construction operations (e.g. gravel, dirt, extra vehicles, etc.) for the City of Albuquerque. The traffic operations center located in the City of Albuquerque that controls the traffic signal systems and other field equipment owned by the City of Albuquerque. The archive system for the City of Albuquerque that collects traffic and traveler information as well as accident data for planning purposes. Traffic signal shop that repairs and replaces traffic signals and other ITS field equipment for the City of Albuquerque. Traffic signal systems owned and operated by the City of Albuquerque. May include preemption capabilities, video detection, pedestrian signals, etc. These are the air quality monitoring systems for the City of Albuquerque and the City's Environmental Health Department. This is the administrative part of the air quality collection system. Field equipment owned and operated by the City of Albuquerque, the Environmental Health department that is responsible for air quality monitoring for the City. Fire and EMS vehicles owned and operated by the City of Albuquerque. ITS technologies on-board fire and EMS vehicles may include mobile data terminals (MDTs), AVL, signal preemption devices, etc. Also includes HAZMAT vehicles dispatched within the City limits. The emergency operations center (EOC) for the City of Albuquerque. Planned Page 52

58 Stakeholder Element Name Element Description Status City of Albuquerque Police Department City of Albuquerque Police Department Emergency Response Vehicles Police vehicles owned and operated by the City of Albuquerque. ITS technologies on-board cruisers may include mobile data terminals (MDTs), AVL, etc. City of Albuquerque Public Safety City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque Transit Department City of Albuquerque 911/Emergency Communications Center ABQ RIDE Fixed Route Dispatch System ABQ RIDE Fixed Route Transit Vehicles ABQ RIDE Paratransit Dispatch System ABQ RIDE Paratransit Vehicles Alvarado Transportation Center City of Albuquerque Station/Stop Security Monitoring Equipment City of Albuquerque Station/Stop Traveler Information Equipment City of Albuquerque Transit Information Center City of Albuquerque Transit Kiosks City of Albuquerque Transit Parking Facilities The public safety answering point and dispatch function for the City of Albuquerque Police and Fire Departments. This is intended to be the new Emergency center located on the west side of town. Computerized dispatch and system for the City of Albuquerque fixed route transit service. Fixed route transit vehicles owned and operated by the City of Albuquerque Transit Division. ITS technologies on vehicles may include AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.). Includes vehicles designated as D-Ride vehicles and Rapid Ride transit vehicles. Computerized dispatch and scheduling system for the City of Albuquerque paratransit service. Paratransit and demand response vehicles owned and operated by the City of Albuquerque Transit Division. ITS technologies on vehicles may include AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.). The multimodal transportation center in downtown Albuquerque. Connections for the City's bus service and rail runner are available. The surveillance systems and emergency notification systems that can be used to improve security in transit terminals and other public areas. Represents stop or station equipment that provide traveler information to transit riders, such as kiosks and message boards. This element represents transit information centers or kiosks located around the City of Albuquerque. Transit kiosks owned and operated by the City of Albuquerque. May include an opportunity to purchase a transit card, request trip information, or display notices on LED displays. Parking facilities that are owned and operated by the City of Albuquerque. These systems may be at City parking lots close to transit centers, or at the transit center itself. Planned Planned Planned Page 53

59 Stakeholder Element Name Element Description Status City of Albuquerque City of Albuquerque Transit The payment card used specifically for the City of Albuquerque transit rides. Planned Transit Department Payment Card May be obtained at the City's transit kiosks or transit centers. City of Albuquerque City of Albuquerque Transit The transit website for the City of Albuquerque transit department (ABQ Transit Department Website RIDE). Website has schedule and fare information, bus pass purchase locations, trip planning, etc. City of Albuquerque Transit Department Regional Payment Instrument Future payment instrument used for transit and other electronic systems. Planned City of Rio Rancho City of Rio Rancho Public Information System The office provides the official interface between the City of Rio Rancho traffic and maintenance departments and interests outside the departments such as the media. The archive system for the City of Rio Rancho that collects traffic and traveler information as well as accident data for planning purposes. City of Rio Rancho City of Rio Rancho Traffic Planning System City of Rio Rancho City of Rio Rancho Website Transportation information website for the City of Rio Rancho. In the future will include real-time construction, work zone, special event, incident, and traffic information. City of Rio Rancho Fire Department City of Rio Rancho Fire Department City of Rio Rancho Police Department City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Emergency Operations Center (EOC) City of Rio Rancho Fire and EMS Vehicles City of Rio Rancho Police Vehicles The emergency operations center (EOC) for the City of Rio Rancho. Fire and EMS vehicles owned and operated by the City of Rio Rancho. ITS technologies on-board fire and EMS vehicles may include mobile data terminals (MDTs), AVL, signal preemption devices, etc. Also includes HAZMAT vehicles dispatched within the City limits. Police vehicles owned and operated by the City of Rio Rancho. ITS technologies on-board cruisers may include mobile data terminals (MDTs), AVL, etc. The asset management system for the City of Rio Rancho. Planned Planned City of Rio Rancho Asset Planned Management System City of Rio Rancho CCTV Closed circuit television (CCTV) cameras owned and operated by the City of Planned Rio Rancho. City of Rio Rancho DMS Dynamic message signs owned and operated by the City of Rio Rancho. May be a shared resource with the City of Albuquerque and/or the NMDOT. City of Rio Rancho Field Sensors Traffic and vehicle sensors owned and operated by the City of Rio Rancho. Planned Page 54

60 Stakeholder Element Name Element Description Status City of Rio Rancho Public City of Rio Rancho Fleet The equipment repair facility for the City of Rio Rancho. Handles Works Maintenance Facility maintenance and construction vehicles and equipment. City of Rio Rancho Public City of Rio Rancho Flood Flood Monitoring devices deployed near Rio Rancho roadways. Planned Works Monitoring Devices City of Rio Rancho Public City of Rio Rancho ITS Field Field equipment owned and operated by the City of Rio Rancho that is not Planned Works Equipment expressly identified in this architecture (e.g. Permanent counting stations, security monitoring field equipment, etc.). City of Rio Rancho Public Works City of Rio Rancho O and M Yard The storage facility for maintenance and construction operations (e.g. gravel, dirt, extra vehicles, etc.) for the City of Rio Rancho. City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Public Works City of Rio Rancho Public Works Contract Transport Companies City of Rio Rancho Public Infrastructure Dispatch City of Rio Rancho Public Infrastructure Fleet City of Rio Rancho RWIS City of Rio Rancho Traffic Operations Center City of Rio Rancho Traffic Signals Private Ambulance Provider Dispatch The maintenance and construction division for the City of Rio Rancho. Operates as the dispatch function for the City of Rio Rancho's maintenance and construction vehicles. Maintenance and construction vehicles for the City of Rio Rancho. May also include snow plow or any other vehicle utilized by the DPW. Road Weather Information System (RWIS) operated and maintained by the City of Rio Rancho. The traffic operations center located in Rio Rancho that controls the traffic signal systems and other field equipment owned by the City of Rio Rancho. Traffic signal systems owned and operated by the City of Rio Rancho. Includes signal preemption capabilities for emergency vehicles. This covers the private ambulance dispatch systems that serve the Albuquerque region. This includes Superior Ambulance and Albuquerque Ambulance. The private vehicles owned and operated by private ambulance providers within the Region. Contract Transport Companies Private Ambulance Provider Vehicles Financial Institution Financial Institution Represents the financial institutions the regional transit agencies will use as part of electronic fare payment systems. Independent School Independent School District The buses owned and operated by the various independent school districts. Districts Buses ITS equipment installed on district buses may include AVL, MDTs and security Independent School Districts Independent School District Dispatch monitoring equipment (CCTV, silent alarms, etc.) Dispatch function for each of the Independent School Districts. Includes radio communication with school buses. Planned Page 55

61 Stakeholder Element Name Element Description Status Kirtland AFB Kirtland AFB Emergency This element represents the emergency management functions of Kirkland Services AFB that may need to coordinate with public agencies (traffic and emergency management). Local Media Local Print and Broadcast Includes the local newspapers and the local TV and radio stations Media Local Transit Agencies Local Transit Dispatch The dispatch function for local transit agencies are not specifically called out in the Architecture. May have an automated dispatch or CAD system in the future. Local Transit Agencies Local Transit Vehicles Fixed route and demand response transit vehicles owned and operated by local transit agencies. The ITS applications on local transit vehicles may Include AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.). Local Transit Agencies Local Transit Website The transit website for the local transit agencies operating within the Region. Websites may include vanpooling forms, information in finding a vanpool, and information regarding the board of directors, demand response transit plans, etc. Mid Region Council of MRCOG Data Warehouse The data warehouse for MRCOG. Allows virtual access points into other Governments archives through one portal. Mid Region Council of Governments MRCOG Probe Vehicles Probe vehicles utilized by MRCOG to collect travel time and speed data, etc. Mid Region Council of Governments Mid Region Council of Governments Mid Region Council of Governments Mid Region Council of Governments Municipal Public Safety MRCOG Consolidated Traffic Monitoring Program The traffic count archive for MRCOG. Collects traffic, bike, and pedestrian count information from its constituent cities as well as its own count equipment. MRCOG ITS field sensors Traffic and vehicle sensors owned and operated by the MRCOG Regional Electric Charging Stations Regional Ridesharing Center Municipal Fire and EMS Vehicles Regional Electric Charging Stations include public charging stations that support consumers, workplace charging stations, and fleet charging stations. Ridesharing Center supporting Connected Vehicle Dynamic Ridesharing application. Fire and EMS vehicles owned and operated by local fire districts that are not explicitly called out in the architecture. Planned Planned Page 56

62 Stakeholder Element Name Element Description Status Municipal Public Safety Municipal Fire Dispatch This element represents the smaller fire districts in the Albuquerque Metropolitan Area that are not explicitly represented in the architecture inventory. Examples include the Fire Departments for the villages of Tijeras and Albuquerque Los Ranchos. Municipal Public Safety Municipal Police Dispatch Represents local or municipal police department dispatch systems that are not explicitly represented in the architecture inventory. Municipal Public Safety Municipal Police Vehicles Police vehicles that are owned and operated by the municipal police departments that are not explicitly called out in the architecture. Municipalities Municipal Asset Management The asset management system for the municipalities within the Region. Planned System Municipalities Municipal Emergency The emergency operations centers for the municipalities within the Region. Planned Operations Centers (EOC) Primary responsibility is to monitor local capabilities and request state support when needed. Municipalities Municipal Equipment Repair Equipment Repair Facilities operated at the municipal level. Handles Planned Facility maintenance and construction vehicles and equipment. Municipalities Municipal ITS Field Equipment Represents ITS roadway devices that are owned and operated by municipalities. These devices include loop detectors, DMSs, pre-emption devices, flood detection devices, CCTV cameras and RWIS. Planned Municipalities Municipalities Municipalities Municipal Public Information System Municipal Public Works Dispatch Municipal Public Works Vehicles The office and systems for municipalities that provide the official interface between municipal traffic and maintenance departments and interests outside the departments (e.g. the media). The maintenance and construction division for municipalities. Operates as the dispatch function for the municipalities' maintenance and construction vehicles as well as snow plows. Maintenance and construction vehicles owned and operated by municipalities (includes snow plows). May include AVL and MDTs onboard vehicles. Municipalities Municipal Storage Facility The storage facility for maintenance and construction operations (e.g. gravel, dirt, extra vehicles, etc.) for the municipalities. Municipalities Municipal Traffic Operations Operation of traffic signal systems by municipalities. This includes the Center Villages of Los Ranchos, Corrales, and Los Lunas and the Town of Bernalillo. Planned Planned Planned Page 57

63 Stakeholder Element Name Element Description Status Municipalities Municipal Websites The general information website for municipalities. In the future will include Planned real-time construction, work zone, special event, incident, and traffic information, and tourism information. New Mexico Department of Information Technology New Mexico State Radio Communications Bureau (RCB) State communications dispatch for DPS, Fire/ Rescue statewide, NMDOT, Forest Service, EMS, and hospitals. Also known as Santa Fe Control. Own communications infrastructure in state New Mexico Department of Public Safety - DPS New Mexico Department of Public Safety - DPS New Mexico Department of Public Safety - DPS New Mexico Department of Public Safety - DPS New Mexico Department of Public Safety - DPS New Mexico Department of Public Safety - DPS New Mexico Department of Veterans Services New Mexico National Guard NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation New Mexico Statewide Emergency Operations Center (EOC) NM DPS Alert Coordinator NM DPS District Dispatch Center NM DPS Vehicles NM Motor Transport Division (MTD) District Offices NM Motor Transport Division (MTD) Response Vehicles New Mexico Veterans Transit Portal New Mexico National Guard Command System New Mexico Statewide Transit Information Portal NMDOT Automatic Traffic Recording Devices The statewide emergency operations center located in Albuquerque. The origination point for Amber Alerts and other wide area alerts throughout the State. The district dispatch center for the NM DPS (State Police). May have an integrated CAD system. There are 12 districts, all of which have their own dispatch center (except D12). Emergency vehicles that are owned and operated by the NM DPS (State Police). ITS applications installed on the police vehicles may include AVL, MDTs, maintenance scheduling equipment, etc. The MTD district offices which dispatch commercial vehicle enforcement personnel The MTD response vehicles within the NM DPS that handle commercial vehicle incidents, enforcements, etc. This transit portal collects transit information from regional information to provide trip planning services for New Mexico veterans. The National Guard Command and Deployment system for the State of New Mexico. They would assist in emergency management, particularly as it relates to disasters or evacuations. This potential future system would gather static and/or real-time transit information data from transit agencies throughout New Mexico. The portal would then provide a single location to access transit information in New Mexico. Traffic recording devices that are owned and operated by NMDOT. Planned Planned Page 58

64 Stakeholder Element Name Element Description Status NMDOT - New Mexico NMDOT CCTV Closed Circuit Television Cameras (CCTV) owned and operated by NMDOT. Department of Transportation Includes the CCTV for AMTMS. NMDOT - New Mexico NMDOT Connected Vehicle RSE Represents connected vehicle roadside equipment operated by NMDOT. Planned Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT DMS Dynamic message signs owned and operated by NMDOT. NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT Field Sensors NMDOT Highway Maintenance Management System (HMMS) NMDOT Historical Traffic Database NMDOT Lane Controls Traffic and vehicle sensors owned and operated by NMDOT. Includes vehicle detection systems (video, microwave, acoustic, etc.) and traffic counting systems. The maintenance archive management system for NMDOT. Specifically, this system aids NMDOT in determining appropriate maintenance activities as well as archiving various maintenance activities (for date, location, type of activity, labor, equipment used, materials used, etc.). The archive data management system for traffic operations and traffic information for the NMDOT Albuquerque District. Lane control devices owned and operated by NMDOT. These include lane control signals on bridges. Planned Planned NMDOT Other District TOCs Traffic Management Centers in other NMDOT Districts. NMDOT Park and Ride Dispatch NMDOT Park and Ride Facilities The dispatch function for the NMDOT Park and Ride shuttles. May have a CAD system in the future. Park and ride facilities that are owned and operated by NMDOT. Systems at the park and ride facility may include gates, barriers, parking fare equipment, etc. Also includes security equipment to monitor the parking facilities and the shelters or kiosks at park and ride locations. Planned Page 59

65 Stakeholder Element Name Element Description Status NMDOT - New Mexico Department of Transportation NMDOT Park and Ride Shuttle Buses The shuttles that are owned and operated by the NMDOT Park and Ride services. In the future these shuttles may have CAD systems, MDTs and security monitoring equipment (CCTV, silent alarms, etc.) NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT Patrol Yard NMDOT Ramp Metering Devices NMDOT Rest Area/Visitor Center/Truck Stop/Service Plaza Kiosks NMDOT Road Closure Gates NMDOT Roadway Treatment Devices NMDOT RWIS NMDOT Signal Lab NMDOT Smart Roadside Lighting NMDOT Statewide Crash Information System Storage facility/yard owned, operated, and used by the New Mexico Department of Transportation. Ramp metering devices that are owned and operated by NMDOT. This represents the rest areas and visitor centers with varied amenities that are existing or planned by NMDOT. Tourist information, emergency evacuation information, and general traffic information could be provided in the future. This element represents automated road closure gates owned and operated by NMDOT used for the remote closure of roads. Intended to be for areas where ice or snow or other adverse weather conditions exist on a frequent basis and that cause hazardous conditions for motorists (e.g. canyon roads, etc.). Roadway treatment devices (anti-icing equipment, sensors, etc.) owned and operated by NMDOT to treat roads (usually ice, snow, etc.). Road weather information systems that are owned and operated by NMDOT. The NMDOT Signal Lab manages traffic signal systems statewide that are owned and operated by NMDOT. Represents Smart Roadside Lighting equipment operated by NMDOT. Statewide database of vehicle crash records. Input to system provided by elements within the architecture. Planned Planned Planned Planned Planned Page 60

66 Stakeholder Element Name Element Description Status NMDOT - New Mexico Department of Transportation NMDOT Statewide Pavement Management System Statewide database for pavement management. Input into system provided by elements in the Region. Aids in planning for the life of pavement and funding requirements for resurfacing (based on historical evidence). NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT - New Mexico Department of Transportation NMDOT Statewide TMC NMDOT TIMS NMDOT Toll Authority NMDOT Transportation Management Center located in Albuquerque. Currently controls the ITS field equipment for District 3 as well as ITS equipment in other Districts. Also dispatches motorist assistance patrols in the Albuquerque area The NMDOT Transportation Information Management System (TIMS) manages transportation infrastructure, inventory, attributes, and assets in a geospatial context. It is the core system used to report to FHWA. The NMDOT division responsible for collecting tolls at NMDOT bridge crossings within the Region. Planned NMDOT Toll Plazas Toll plazas at NMDOT river crossings. Planned NMDOT Traffic Data Collection System NMDOT Traffic Safety Division Data System The traffic data collection system (sensors, etc.) that are owned and operated by NMDOT. Regional database that collects traffic safety and incident information. NMDOT Traffic Signals Traffic signal systems owned and operated by NMDOT. NMDOT VMT Road User Payment System Represents a future system that would manage a VMT road user payment system for NMDOT roadways. Planned NMDOT Work Zone Equipment Work zone monitoring and alerting equipment owned by NMDOT. Planned Page 61

67 Stakeholder Element Name Element Description Status NMDOT - New Mexico NMRoads Web based traveler information application Department of Transportation NMDOT New Mexico Department of Transportation NMRoads Admin Traveler information portal managed by NMDOT that provides static and real-time information on traffic conditions, road conditions, weather conditions, road construction information and transit related information. The website also provides access to current CCTV images and DMS signage. NMRoads has a larger role as an operating environment where info is input and output between ITS centers, even allowing device control for remote devices, creating a web-based operational system. NMDOT New Mexico Department of Transportation NMDOT New Mexico Department of Transportation NMDOT District 3 Other NMDOT District Maintenance Dispatch NMDOT Maintenance dispatch function in neighboring districts. Other NMDOT Field Devices Represents NMDOT field devices interfaced with other NMDOT field devices. NMDOT District 3 Equipment Repair Facility The SHOP The maintenance shop for all roadside equipment owned and operated by NMDOT. Also provides maintenance to NMDOT vehicles. NMDOT District 3 NMDOT District 3 ITS Field This element represents any or all ITS field equipment (roadside) that is not Equipment specifically called out in the architecture. NMDOT District 3 NMDOT District 3 Maintenance Maintenance and construction vehicles for the NMDOT Albuquerque District. and Construction Vehicles NMDOT District 3 NMDOT District 3 HELP Trucks Motorist assistance patrols for response to stranded motorists/vehicles and provides emergency traffic control to incident responders NMDOT District 3 NMDOT District 3 Maintenance Office in charge of maintenance and construction operations for the NMDOT Office Albuquerque District. NMDOT District 3 NMDOT District 3 Maintenance NMDOT maintenance sections for the Albuquerque Region. Dispatches Units Dispatch maintenance vehicles and equipment for maintaining road and ITS NMDOT District 3 NMDOT District 3 Pavement Management System equipment owned by NMDOT. District Pavement Management System to assist in storing, retrieving, analyzing and reporting information to help with pavement-related decisionmaking processes. Planned Page 62

68 Stakeholder Element Name Element Description Status NMDOT District 3 NMDOT District 3 Public The public transportation management archive for NMDOT District 3. Transportation Management System (PTMS) NMDOT District 3 NMDOT District 3 Security Security equipment owned and operated by NMDOT. Generally used for Planned Monitoring Field Equipment monitoring bridges, roads, etc. for homeland security measures. NMDOT District 3 NMDOT Smart Work Zone Represents Smart Work Zone Systems operated by NMDOT. These systems System are associated with distinct projects. NOAA National Weather Service Service for national, regional, and local weather information. Other Counties Other County Public Safety This element represents the connection to other States, including County Communications Centers (Sheriff and Fire), and Local (municipal police and fire departments) law enforcement, fire, and EMS call taker and dispatch centers. Communication between these centers uses a mesh topology - any emergency management center can communicate directly with any other emergency management center. Note that this element also represents interfaces to emergency management centers in jurisdictions adjacent to the region that also coordinate during major incidents. Other Counties Other County TOC Traffic operations centers in other counties that may coordinate with county traffic operations centers called out in the architecture. Planned Private Commercial Carriers Private HAZMAT Providers Private HAZMAT Providers Private Sector Traveler Information Service Providers Private Tow/Wrecker Providers Commercial Vehicles This represents ITS equipment in privately owned commercial vehicles. This classification applies to all such vehicles ranging from small panel vans used in local pick-up and delivery services to large, multi-axle tractor trailer rigs operating on long haul routes. Private HAZMAT Response Second responders to incidents, as determined by the first responder to an Providers incident. Responsible for regional HAZMAT mitigation and clean-up activities. Private HAZMAT Vehicles Private HAZMAT vehicles that operate as second responders to incidents. Private Sector Traveler Information Services Private Tow/Wrecker Dispatch Private traveler information providers serving the region. This element could, in the future, provide support to the National Traveler Information 511 number since it collects information from a broad array of operating centers. Could also include a website. Dispatch function for privately owned tow or wrecker service. Based on a rotation list. Page 63

69 Stakeholder Element Name Element Description Status Private Tow/Wrecker Private Tow/Wrecker Vehicles This element represents possible ITS equipment inside tow or wrecker Providers vehicles. Private Traffic Data Private Data Systems Private provider systems that measure or calculate roadway speeds. Provider Private Weather Private Weather Information Private weather services that provide regional and local weather information. Information Provider Provider Private Weather Private Weather Support Private collection of road weather data and provision of data to NMDOT Planned Information Provider Services System through web based access. Public/Private Utilities Public/Private Utilities Public or private utility companies that operate within the Region. This includes Albuquerque and Bernalillo County Water and Utility Authority, PNM, etc. Rail Operators Rail Operations Centers The dispatch centers for major railroads in the region (e.g. BNSF, Amtrak, etc.). Rail Operators Rail Operators Wayside The rail operated equipment at highway rail intersections. Interconnect with Equipment the region's traffic control departments. Regional Airports Regional Airports Regional Airports that are owned and operated by the local municipalities where they reside. Regional Event Special Event Coordinators Promoters and sponsors of special events. They coordinate with traffic and Coordinators emergency providers. Includes Balloon Fiesta coordinators, State Fair coordinators, Journal Pavilion coordinators, Mesa Del Sol coordinators, etc. Regional Medical Centers Lifeguard Air Rescue Dispatch Represents the private air evacuation/rescue service that provides transport from remote locations to area hospitals. Regional Medical Centers Regional Medical Centers Medical centers that are located within the region (hospitals). Includes the University of New Mexico Hospital. Regional Parking Regional Parking Management This network represents the coordination between all parking management Planned Management Providers Network facilities within the region. Regional Public Safety Agencies Regional Emergency Communications Network Regional public safety communications network. Planned Regional Transit Providers Rio Metro Regional Transit District Regional Transit Kiosks Rail Runner On-Board PTC Equipment Kiosks located throughout the state (at visitor centers, local PIOs, etc.) that dispense regional fare cards and provide transit fare and schedule information to transit users. Positive Train Control equipment on Rail Runner trains. Planned Planned Page 64

70 Stakeholder Element Name Element Description Status Rio Metro Regional Rail Runner The operations and dispatch function for the Rail Runner commuter rail Transit District Operations/Dispatch system. Rio Metro Regional Rail Runner Station Traveler Represents station equipment that provide traveler information to transit Transit District Information Equipment riders, such as kiosks and message boards. Rio Metro Regional Rail Runner Transit Parking The parking facilities at Rail Runner stations. May have the ability for Planned Transit District Facilities automatic payment of parking fees, making parking reservations, etc. Rio Metro Regional Rail Runner Transit Rail Vehicles Commuter rail cars owned and operated jointly by NMDOT and Rio Metro. Transit District ITS applications on the vehicles may include AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.) Rio Metro Regional Transit District Rail Runner Wayside Equipment The wayside or rail operated equipment owned and operated by Rio Metro at highway rail intersections for the Rail Runner. Rio Metro Regional Transit District Rio Metro Regional Transit District Rio Metro Regional Transit District Rio Metro Regional Transit District Rio Metro Regional Transit District Rio Metro Regional Transit District Rio Metro Demand Response Vehicles Rio Metro Operations Center Rio Metro Station/Stop Security Monitoring Equipment Rio Metro Station/Stop Traveler Information Equipment Rio Metro Transit Vehicles Rio Metro Transit Website Demand response vehicles owned and operated by the Rio Metro Regional Transit District. ITS technologies on vehicles may include AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.). This represents paratransit operations centers for Rio Metro Regional Transit District. The surveillance systems and emergency notification systems that can be used to improve security in transit terminals and other public areas. Represents stop or station equipment that provide traveler information to transit riders, such as kiosks and message boards. Demand response transit vehicles owned and operated by Rio Metro. Includes ITS applications including MDTs, AVL, and security monitoring equipment (CCTV, silent alarms, etc.). The website for Rio Metro. May be used for schedule and fare information, road network conditions, and even to request a demand response transit plan, while online. Sandia Labs Sandia Labs This element represents the emergency management functions of Sandia Labs. Sandoval County Sandoval County Asset The asset management system for the County of Sandoval. Management System Sandoval County Sandoval County Emergency The Sandoval County emergency operations center (EOC). Operations Center (EOC) Planned Planned Planned Page 65

71 Stakeholder Element Name Element Description Status Sandoval County Sandoval County Public The office provides the official interface between Sandoval County traffic and Information System public works departments and interests outside the departments such as the media. Sandoval County Sandoval County Regional The regional communication center that serves as the dispatch function for Dispatch Center the Sandoval County sheriff, fire and EMS vehicles. Sandoval County Sandoval County Website Transportation information website for Sandoval County. In the future will include real-time construction, work zone, special event, incident, and traffic information. Sandoval County Fire Sandoval County Fire and EMS Fire and EMS vehicles owned and operated by Sandoval County. Onboard ITS Department Vehicles systems may include mobile data terminals (MDTs), AVL, cameras, etc. Sandoval County Public Sandoval County Equipment The equipment repair facility for Sandoval County. Handles maintenance and Planned Works Repair Facility construction vehicles and equipment. Sandoval County Public Works Sandoval County ITS Field Equipment Field equipment owned and operated by Sandoval County. May include traffic signal systems (with preemption capabilities, traffic sensors, DMS, etc. Planned Sandoval County Public Works Sandoval County Public Works Sandoval County Public Works Sandoval County Sheriff Sandoval County Public Works Dispatch Sandoval County Public Works Vehicles Sandoval County Storage Facility Sandoval County Sheriff Vehicles The maintenance and construction division for Sandoval County. Operates as the dispatch function for Bernalillo County's maintenance and construction vehicles as well as snow plows. Maintenance and construction vehicles owned and operated by Sandoval County (includes snow plows). May include AVL and MDTs onboard vehicles. The storage facility for maintenance and construction operations (e.g. gravel, dirt, extra vehicles, etc.) for Sandoval County. Sheriff vehicles owned and operated by the Sandoval County Sheriff's Department. Onboard ITS systems may include mobile data terminals (MDTs), AVL, cameras, etc. Travelers Connected Vehicle OBE On Board Equipment in Connected Vehicles Planned Travelers Personal Information Device Devices used to interface with connected vehicle applications. Planned Travelers Private Travelers Personal Includes personal and office computers, pagers, and handheld devices used Computing Devices by travelers to receive ITS information. Travelers Private Vehicles Vehicles owned by travelers. Tribal Governments Tribal Public Safety Dispatch This element represents the law enforcement, fire, and EMS call taker and dispatch centers on Indian reservations. Includes the Zia, Santa Ana, Laguna, Isleta, and Tohajiilee Navajo Indian reservations. Page 66

72 Stakeholder Element Name Element Description Status Tribal Governments Tribal Road Maintenance Represents the public works or maintenance and construction functions of Planned the Tribal governments. In some cases this function is contracted to private companies Tribal Governments Tribal Transportation Represents the traffic operations function for the tribal governments. Planned Operations University of New Mexico UNM Courtesy Shuttles Transit vehicles owned and operated by the University of New Mexico. Include the ITS equipment installed on shuttles including AVL, MDTs and security monitoring equipment (CCTV, silent alarms, etc.) University of New Mexico UNM Emergency Operations The emergency operations center (EOC) for the University of New Mexico. Center (EOC) University of New Mexico UNM Events Office The event office at the University of New Mexico that coordinates with regional traffic systems for large events (football games, etc.). University of New Mexico UNM Police Dispatch The police dispatch for the University Police Department. University of New Mexico UNM Police Vehicles Police vehicles owned and operated by the University of New Mexico. Includes the ITS equipment installed on the cruisers (AVL, MDTs, etc.). University of New Mexico UNM Transportation Services The dispatch function for the University of New Mexico transit section. May Dispatch include CAD systems for dispatch and communications. University of New Mexico Wheres My Bus Where's My Bus? is an application that provides real-time transit information for ABQ Rides and UNM transit services. In the near future, the application will be expanded and renamed Where's My Transit? to include Rio Metro and NM Rail Runner Express real-time transit information. University of New Mexico Wheres My Transit Where's My Transit? (WMT) is an application that provides real-time transit information for New Mexico transit riders via a website and mobile application. Currently, the application is known as Where's My Bus? and provides real-time information for ABQ Rides and UNM transit services. In the near future, the application will be expanded and renamed Where's My Transit? to include Rio Metro and NM Rail Runner Express real-time transit information. Planned Page 67

73 5.2. Systems by Architecture Entity Each element in the AMPA Regional ITS Architecture inventory is mapped to one or more entities from the National ITS Architecture. In version 7.1 of the National ITS Architecture (on which this architecture is based) there are 101 entities defined. These 22 subsystems and 79 terminators describe a wide array of systems that provide ITS services, or interface with systems that provide ITS services. The mapping of AMPA Regional ITS Architecture elements to National ITS Architecture entities has two primary benefits. First, it allows the full set of information flows contained in the National ITS Architecture to be used in the description of AMPA Regional ITS Architecture interfaces. Secondly, it allows the elements of the AMPA Regional ITS Architecture to be grouped by like entity. Table 5 provides just such a sorting of inventory elements by entity. This table allows the users of the architecture to immediately identify all the elements that have functions relating to transit management, or traffic management, or any other subsystem or terminator defined by the National ITS Architecture. A list of the elements in the AMPA Regional ITS Architecture sorted by entity can be found on the AMPA Regional Architecture web page by selecting the Inventory by Entity button on the left side menu bar. This list on the web page allows the users of the architecture to immediately identify all the elements that have functions relating to transit management, or traffic management, or any other subsystem or terminator defined by the National ITS Architecture. The AMPA Regional ITS Architecture inventory contains the following number of elements mapped to different types of entities: Archived Data Management: 12 Emergency Management: 33 (including some transit elements that are mapped to emergency management because of the transit security service described in a later section) Information Service Providers: 24 Maintenance and Construction Management: 18 Traffic Management: 9 Transit Management: 9 Page 68

74 6. Needs and Services 6.1. Needs Identification Transportation needs identify the transportation problems that can be solved by ITS services. They also represent a link to transportation planning efforts that define the strategies used to address transportation problems. These strategies involve capital improvements as well as operational improvements and coordination opportunities among stakeholders. ITS solutions usually involve services that improve the efficiency, scope, or safety of operations. The initial set of user needs described below was developed from information collected as part of the New Mexico Statewide ITS Architecture development effort and customized based upon the AMPA stakeholder meetings. Table 5 below, shows an X where the level of regional priority was determined for the user need specified. Some user need prioritizations show specific references to public services ( fire/ems and police). This is done to show the prioritization difference between different public safety agencies. There are also several instances where a priority differs in urban areas vs. rural areas. These cases are identified in the table. Table 5: Summary of Transportation Needs/Priorities Need Area Specific ITS Need High Medium Low Not a Need Incident Management Traffic Management Need improved incident management and coordination within departments and among stakeholders Need to reduce delays due to crashes Need to reduce the incidence of secondary crashes from incidents Need to improve traffic congestion mitigation Need to reduce congestion on river crossings Need to provide early warning of poor visibility conditions (dust, snow, etc.) Need traffic signal interconnect and coordination to improve mobility Need traffic signal preemption for emergency vehicles Need advanced warning of flash flood areas Need to enhance communications and information sharing between regional agencies X X x X X X X Fire/EMS X X X Police Page 69

75 Need Area Specific ITS Need High Medium Low Not a Need Emergency Management Public Transportation Need to address speed differentials on controlled access roads (road geometry and vehicle density) Need to interconnect with neighboring regions Need to know travel times on major routes Need to know delays or travel times on major routes Need to implement parking management systems Need to alert drivers of speeding (automated alert systems) Need to improve emergency notification/dispatch and response times Need to improve traffic safety Need to expand remote traveler support services (information plus roadside assistance) Need to have callboxes throughout the region Need improved tracking of emergency vehicles Need to improve/enhance rural traveler service (inter-city) Need to improve urban traveler service Need to improve transit coordination among city/county/tribal governments Need better communication with transit customers Need to encourage major employers to implement transit use incentives. Need identified as part of TDM and CMS strategies Need automated maintenance system for transit fleets Need to improve efficiency of demandresponsive transit (enhanced information) Need to improve schedule operations for fixed-route transit vehicles X X X X X X X X Urban X X X X X X X X X X Rural X Page 70

76 Need Area Specific ITS Need High Medium Low Not a Need Maintenance Operations Traveler Information Information Management Other Need interactive ITS services (transitrelated) Need to improve vehicle routing and detours/information Need advanced and up-to-date road closure and construction zone information Need to reduce delays due to accidents or construction Need to know locations for snow plow dispatch Need better snow and ice monitoring Need to improve work zone safety (alert drivers of wrong-way movements) Need improved wind monitoring Need improved dust monitoring Need real-time roadway and traffic conditions information for recurring and non-recurring conditions Need real-time information about weather conditions/location Need easier access to traveler services information (locations, types of services, etc.) Need special event traffic information Need to have traveler information accessible at employment sites Need more accessible and comprehensive tourist information Need more ITS education Need park-and-ride information Need to reduce the number of animalvehicle collisions Need to expand communications services (e.g. cellular coverage) X X X X X X X X X X X X X X X X X X X During the discussion on user needs, discussion was generated on which potential stakeholders would be influenced by each of the user needs. Where no discussion was held, the architecture team was able to make a determination as to the agencies that would most likely be influenced by the user need. Page 71

77 For simplicity, the needs summary below identifies high priority needs and maps these to stakeholder groups. The seven groups whose needs were considered are: NMDOT Public Safety (Police, Fire, EMS, Emergency Management) Municipal (primarily traffic and public works)- City of Albuquerque, City of Rio Rancho County (primarily traffic and public works)- Bernalillo County Transit- ABQ Ride/ Rio Metro Planning (MPO/RPO)- MRCOG Private Sector Towing Table 6 provides a summary of the high priority transportation needs along with the group(s) for which these needs are high priority. Table 6: Summary of High Priority Transportation Needs Need Area Specific ITS Need Group Incident Management Need improved incident management and coordination within departments and among stakeholders NMDOT, Public Safety, Municipal, County, Private Sector Towing Need to reduce delays due to crashes NMDOT, Public Safety, Municipal, County, Private Sector Towing Need to reduce the incidence of secondary crashes from incidents NMDOT, Public Safety, Municipal, County Traffic Management Emergency Management Need to improve traffic congestion mitigation Need to reduce congestion on river crossings Need traffic signal interconnect and coordination to improve mobility Need traffic signal priority/preemption for emergency vehicles Need to enhance communications and information sharing between regional agencies Need to know travel times on major routes Need to improve emergency notification/dispatch and response times NMDOT, Municipal, County NMDOT, Municipal, County NMDOT, Municipal, County NMDOT, Public Safety, Municipal, County NMDOT, Public Safety, Municipal, County NMDOT, Municipal, County Public Safety (plus NMDOT, Municipal, County to support improved notification times on traffic related emergencies) Page 72

78 Need Area Specific ITS Need Group Need to improve traffic safety NMDOT, Public Safety, Municipal, County Public Transportation Maintenance Operations Traveler Information Information Management Need to improve urban traveler service Need to improve transit coordination among city/county/tribal governments Need better communication with transit customers Need to improve schedule operations for fixedroute transit vehicles Need interactive ITS services (transit-related) Need to reduce delays due to accidents or construction Need to improve work zone safety (alert drivers of wrong-way movements) Need real-time roadway and traffic conditions information for recurring and non-recurring conditions Need real-time information about weather conditions/location Need improved access to traffic count data Need more ITS education Need park-and-ride information Transit Transit Transit Transit Transit NMDOT, Municipal, County NMDOT, Municipal, County NMDOT, Municipal, County NMDOT, Municipal, County Planning Planning, NMDOT, Municipal, County NMDOT, Municipal, County 6.2. Services The ITS systems in the region currently provide a wide array of transportation services and that list will grow as more systems are developed or upgraded. The current and planned services can be described by the set of service packages that are shown in Table 7. This set of services is a subset of the services contained in the National ITS Architecture, and represent all of the selected services (service packages) based on information gathered at stakeholder meetings, needs assessments, and review of planning documents. Each of the service packages is currently implemented, or planned for implementation by one or more stakeholders in the region. For those services where one or more stakeholders have already implemented it, the status is set to existing. Table 7 identifies, for each service package, the status (existing or planned). Table 7: Selected Regional Services (Service packages) Service package Service package Name Status Page 73

79 Service package Service package Name Status AD1 ITS Data Mart AD2 ITS Data Warehouse APTS1 Transit Vehicle Tracking APTS2 Transit Fixed-Route Operations APTS3 Demand Response Transit Operations APTS4 Transit Passenger and Fare Management APTS5 Transit Security APTS6 Transit Maintenance Planned APTS7 Multi-modal Coordination Planned APTS8 Transit Traveler Information APTS9 Transit Signal Priority Planned APTS10 Transit Passenger Counting APTS11 Multimodal Connection Protection Planned ATIS1 Broadcast Traveler Information ATIS2 Interactive Traveler Information ATMS01 Network Surveillance (Monitoring) ATMS02 Probe Surveillance ATMS03 Surface Street Control ATMS04 Traffic Metering Planned ATMS05 HOV Lane Management Planned ATMS06 Traffic Information Dissemination ATMS07 Regional Traffic Control Planned ATMS08 Traffic Incident Management System ATMS10 Electronic Toll Collection Planned ATMS11 Emissions Monitoring and Management Planned ATMS12 Roadside Lighting System Control Planned ATMS13 Standard Railroad Grade Crossing Planned ATMS15 Railroad Operations Coordination Planned ATMS16 Parking Facility Management Planned ATMS17 Regional Parking Management Planned ATMS18 Reversible Lane Management Planned ATMS19 Speed Warning and Enforcement Planned ATMS21 Roadway Closure Management Planned ATMS25 VMT Road User Payment Planned Page 74

80 Service package Service package Name Status EM01 Emergency Call-Taking and Dispatch EM02 Emergency Routing EM04 Roadway Service Patrols EM05 Transportation Infrastructure Protection Planned EM06 Wide-Area Alert Planned EM08 Disaster Response and Recovery Planned EM09 Evacuation and Reentry Management Planned EM10 Disaster Traveler Information Planned MC01 Maintenance and Construction Vehicle and Equipment Tracking Planned MC02 Maintenance and Construction Vehicle Maintenance Planned MC03 Road Weather Data Collection MC04 Weather Information Processing and Distribution MC05 Roadway Automated Treatment Planned MC06 Winter Maintenance Planned MC07 Roadway Maintenance and Construction Planned MC08 Work Zone Management MC09 Work Zone Safety Monitoring Planned MC10 Maintenance and Construction Activity Coordination Planned Incident Management, identified as ATMS08 in the above table, is one of the key services that is planned throughout the region. Although it is technically called Traffic Incident Management, and identified numerically in the National ITS Architecture as ATMS08, a broader view of this service includes several service packages, including: ATMS03 Surface Street Control ATMS04 Freeway Control ATMS06 Information Dissemination ATMS07 Regional Traffic Control ATMS08 Traffic Incident Management EM1 Emergency Call-Taking and Dispatch EM2 Emergency Routing As indicated by Table 7 above, all of these services are identified as existing or planned for the AMPA Regional ITS Architecture. Page 75

81 6.3. Comparison of Needs and Services The priority needs identified in Section 6.1 will be addressed by the ITS services described in Section 6.2. Table 8 provides a mapping of the priority needs to ITS services identified in the previous section. Table 8: Mapping of Needs to Services Need Area Specific ITS Need ITS Service Addressing Need Service package Incident Management Need improved incident management and coordination Traffic Incident Management Emergency Response ATMS08 EM1 Emergency Routing EM2 Need to reduce delays due to crashes Traffic Incident Management Roadway Maintenance and Construction ATMS08 MC07 Work Zone Management MC08 Need to reduce the incidence of secondary crashes from incidents Traffic Incident Management Traffic Information Dissemination ATMS08 ATMS06 Traffic Management Need to improve traffic congestion mitigation Network Surveillance Surface Street Control ATMS01 ATMS03 Freeway Control ATMS04 Traffic Information Dissemination ATMS06 Regional Traffic Control ATMS07 Traffic Incident Management ATMS08 Need to reduce congestion on river crossings Network Surveillance Surface Street Control ATMS01 ATMS03 Traffic Information Dissemination ATMS06 Regional Traffic Control ATMS07 Traffic Incident Management ATMS08 Need to provide early warning of poor visibility conditions (dust, snow, etc.) Traffic Information Dissemination Weather Information Processing and Distribution ATMS06 MC04 Need traffic signal interconnect and coordination to improve mobility Surface Street Control Regional Traffic Control ATMS03 ATMS07 Page 76

82 Need Area Specific ITS Need ITS Service Addressing Need Service package Need traffic signal priority/preemption for emergency vehicles Emergency Routing EM02 Emergency Management Need advanced warning of flash flood areas Need to integrate ITS with existing infrastructure (address as a network) Need to enhance communications and information sharing between regional agencies Need to address speed differentials on Interstates Need to interconnect with neighboring regions Need to know travel times on major routes Need to implement parking management systems Need to alert drivers of speeding (automated alert systems) Need to improve emergency notification/dispatch and response times Traffic Information Dissemination Roadway Closure Management N/A Traffic Information Dissemination Traffic Incident Management Emergency Response Emergency Routing Freeway Control Regional Traffic Control Network Surveillance Parking Facility Management Speed Monitoring Traffic Incident Management Emergency Response Emergency Routing ATMS06 ATMS21 N/A ATMS06 ATMS08 EM01 EM02 ATMS04 ATMS07 ATMS01 ATMS16 ATMS19 ATMS08 EM01 EM02 Need to improve traffic safety Network Surveillance ATMS01 Need to expand remote traveler support services (information plus roadside assistance) Need improved tracking of emergency vehicles Surface Street Control Freeway Control Traffic Information Dissemination Traffic Incident Management Mayday Support Emergency Routing ATMS03 ATMS04 ATMS06 ATMS08 EM03 EM02 Page 77

83 Need Area Specific ITS Need ITS Service Addressing Need Service package Public Transportation Maintenance Operations Need to improve/enhance rural traveler service (inter-city) Need to improve urban traveler service Need to improve transit coordination among city/county/tribal governments Need better communication with transit customers Need to encourage major employers to implement transit use incentives Need automated maintenance system for transit fleets Need to improve efficiency of demand-responsive transit (enhanced information) Need to improve schedule operations for fixed-route transit vehicles Need interactive ITS services (transit-related) Need to improve vehicle routing and detours/information Need advanced and up-to-date road closure and construction zone information Transit Fixed-Route Operations Demand Response Transit Operations Transit Fixed-Route Operations Demand Response Transit Operations Multi-modal Coordination Transit Passenger and Fare Management Transit Traveler Information N/A Transit Maintenance Demand Response Transit Operations Transit Traveler Information Transit Fixed-Route Operations Transit Passenger and Fare Management Transit Traveler Information Surface Street Control Traffic Information Dissemination Roadway Maintenance and Construction Work Zone Management Traffic Information Dissemination Roadway Closure Management Winter Maintenance Roadway Maintenance and Construction APTS02 APTS03 APTS02 APTS03 APTS07 APTS04 APTS08 N/A APTS06 APTS03 APTS08 APTS02 APTS09 APTS04 APTS08 ATMS03 ATMS06 MC07 MC08 ATMS06 ATMS21 MC06 MC07 Need to reduce delays due to Traffic Incident Management ATMS08 Page 78

84 Need Area Specific ITS Need ITS Service Addressing Need Service package Traveler Information Information Management accidents or construction Need to know locations for snow plow dispatch Need better snow and ice monitoring Need to improve work zone safety (alert drivers of wrong-way movements) Roadway Maintenance and Construction Work Zone Management Weather Information Processing and Distribution Winter Maintenance Road Weather Data Collection Work Zone Safety Monitoring MC07 MC08 MC04 MC06 MC03 MC09 Need improved wind monitoring Road Weather Data Collection MC03 Need improved dust monitoring Road Weather Data Collection MC03 Need real-time roadway and traffic conditions information Need real-time information about weather conditions/location Need easier access to traveler services information (locations, types of services, etc.) Need special event traffic information Need to have traveler information accessible at employment sites Need improved access to traffic count data Network Surveillance Traffic Information Dissemination Broadcast Traveler Information Traffic Information Dissemination Road Weather Data Collection Weather Information Processing and Distribution Broadcast Traveler Information Network Surveillance Traffic Information Dissemination Traffic Incident Management Broadcast Traveler Information Broadcast Traveler Information ITS Data Mart Need more ITS education N/A N/A ATMS01 ATMS06 ATIS1 ATMS06 MC03 MC04 ATIS1 ATMS01 ATMS06 ATMS08 ATIS1 ATIS1 AD1 Need park-and-ride information ITS Data Mart AD1 Transit Fixed-Route Operations Transit Traveler Information APTS02 APTS08 Page 79

85 Need Area Specific ITS Need ITS Service Addressing Need Service package Other Need to reduce the number of animal-vehicle collisions N/A Need to expand cellular coverage N/A N/A N/A Page 80

86 7. Interfaces and Information Exchanges 7.1. Top Level Regional System Interconnect Diagram A system interconnect diagram, or sausage diagram, shows the systems and primary types of interconnections in the region. The National ITS Architecture interconnect diagram has been customized for the AMPA Region based on the information gathered from the stakeholders and system inventory. Figure 6 on the following pages summarize the existing and planned ITS elements for the state in the context of a physical interconnect. Elements (and their primary associated National ITS Architecture entity) are called out in the boxes surrounding the main interconnect diagram. In the center of the figure, the rectangles represent the subsystems of the National ITS Architecture. The AMPA Regional ITS Architecture has elements that map to 19 of the 22 possible subsystems of the National ITS Architecture. In addition, the AMPA Regional ITS Architecture has elements that map to 18 terminators of the National ITS Architecture. These terminators are shown on the right side (in yellow) of the diagrams below. Terminators include entities such as Care Facilities (which maps to Regional Medical Centers). The diagram also identifies the three basic types of communications used to interconnect the elements of the architecture. These communications types are defined as: Fixed point to fixed point Communications: A communications link serving stationary sources. It may be implemented using a variety of public or private communications networks that may physically include wireless (e.g., microwave) as well as wireline infrastructure. Both dedicated and shared communications resources may be used. Wide Area Wireless Communications: A communications link that provides communications via a wireless device between a user and an infrastructure-based system. Both broadcast (one-way) and interactive (two-way) communications services are grouped into wide-area wireless communications. These links support a range of services including real-time traveler information and various forms of fleet communications. Dedicated Short Range Communications: A wireless communications channel used for close-proximity communications between vehicles and the immediate infrastructure. It supports location-specific communications for ITS capabilities such as toll collection, transit vehicle management, driver information, automated commercial vehicle operations, and pre-emption or priority. Page 81

87 Draft Page 93

88 Draft Figure 6: AMPA Regional System Interconnect Diagram Page 94

89 7.2. Customized Service packages The service packages identified in the National ITS Architecture (see Section 3) have been customized to reflect the unique systems and connections within the AMPA region, as well as connections just outside of the region (e.g. other counties). Each service package can be shown graphically, with the service package name, the entity from the National ITS Architecture and the specific AMPA elements associated with the entity. In addition the service packages show the information flows that are exchanged (or will be exchanged) between elements. Figure 7 is an example of an ATMS service package for Surface Street Control that has been customized for the City of Albuquerque. This service package shows the two subsystems, Traffic Management and Roadway, and the associated elements. Information flows (called architecture flows in the National ITS Architecture) between the subsystems indicate what information is being shared. The service packages that were customized for the AMPA Regional ITS Architecture are shown in Appendix D. These service packages can also be found on the AMPA Regional Architecture web page by selecting the Service packages by Functional Area button on the left side menu bar. Under the Service package by Functional Area tab, service packages are grouped by functional areas (e.g. Traffic Management, Maintenance and Construction, and Public Transportation). Each set of customized service packages (based on the functional area) can be viewed by clicking on the Service package Diagram icon under each area heading. It is important to note that while the service package table on the web page shows all of the service packages from the National ITS Architecture, only those selected for the state are included in the diagrams. The selected service packages on the web page also are highlighted in the web page table with bold print and are indicated as existing or planned. Page 96

90 Figure 7: Example Customized Service Package 7.3. Regional Architecture Information Flows While it is important to identify the various systems and stakeholders as part of the AMPA Regional ITS Architecture, a primary purpose of the architecture is to identify the connectivity between transportation systems in the region. The interconnect (sausage) diagrams shown previously in Figure 6 showed the high level relationships of the elements in the region. The service packages from the National ITS Architecture represent services that can be deployed as an integrated capability, and the customized service package diagrams show the information flows between the subsystems and terminators (elements within the region) that are most important to the operation of the service packages. How these systems interface with each other is an integral part of the overall architecture. There are 229 different elements identified as part of the AMPA Regional ITS Architecture. These elements include City, County and Regional traffic operations centers, transit centers, transit vehicles, public safety dispatch centers, media outlets, and others essentially all of the existing and planned physical components that contribute to the region s intelligent transportation system. Interfaces have been defined for each element in the architecture. For example, the City of Rio Rancho Traffic Operations Center has planned interfaces with 51 other Page 97

91 elements in the region ranging from field equipment to transit centers. Some of the interfaces are far less complex. For example the Alvarado Transportation Center has interfaces with only four other elements in the architecture. The AMPA Regional ITS Architecture defines a total of 1381 interfaces from one element to another. Elements and their interfaces are accessible via the AMPA Regional ITS Architecture web page ( by clicking on the Inventory pulldown at the top, and selecting Inventory. On the web page, elements are listed alphabetically in the column on the left, and the description of each element appears on the right. By clicking on (selecting) an element, the element detail page comes up where the user can view the element definition, who the stakeholder is, the current status of the element, and the other elements with which the selected element interfaces with. Figure 8 below is an example of a portion of the element detail page for the City of Albuquerque Traffic Operations Center. Figure 8: Example of Element Detail showing Interfaces By clicking on (selecting) an element that interfaces with the City of Albuquerque Traffic Operations Center, more detailed information about the particular interface is pulled up (e.g. architecture flows). Architecture flows between elements define specific information that is exchanged by the elements. Each architecture flow has a direction, name and definition. Most of the architecture flows match ones from the National ITS Architecture (the mapping of Page 98

92 elements to National ITS Architecture entities allowed the developers to match the architecture flows to the appropriate interfaces). In some cases, new user defined flows have been created for interfaces or connections that are not expressed in the National ITS Architecture (NOTE: User defined flows have a _ud at the end of the flow name to indicate they are user defined). These architecture flows define the interface requirements between the various elements in the region. The AMPA Regional ITS Architecture defines 5198 triplets (a source element, architecture flow and destination element) throughout the region. An example of architecture flows between two elements is shown in Figure 9. In this interface, the architecture flows that go between the City of Albuquerque 911/Emergency Communications Center and the City of Albuquerque Traffic Operations Center are shown. Although both of these elements are existing, the architecture flows on this interface are shown as planned (indicated by the (P) after each flow). This signifies that these elements do not currently share data communications (since the architecture flows are all shown as planned). Each of the individual element interfaces can be accessed on the AMPA Regional ITS Architecture web page by following the instructions listed previously. Specifically, the user can click on the ITS Inventory button, select the element whose interfaces they are reviewing in order to bring up the element detail page. Once on the element detail page, scrolling down to the Interfaces and clicking on (selecting) an interfacing element, more detailed information about the particular interface is pulled up (e.g. architecture flows). Once you have selected the interfacing element, a screen should appear that is similar to the diagram shown in Figure 9 (which shows a simple interconnect diagram and a list of all the architecture flows on the interface). Selecting any of the architecture flows will provide a definition, and any standards associated with that architecture flow are noted. Page 99

93 Figure 9: Example of Architecture Flows Between Elements Page 100

94 8. Functional Requirements Functional requirements are a description of the functions or activities that are currently performed by the ITS elements or that are planned to be performed in the future. For the AMPA Regional ITS Architecture, these functions have been developed by using the functional assignments underlying the National ITS Architecture. In the National ITS Architecture, a Service Package is defined by subsystems, equipment packages, and architecture flows, which operate together to perform a particular transportation service. Equipment Packages represent pieces of a subsystem that perform a single function. (Further descriptions of these National ITS Architecture concepts are in Section 3.) Note: there are no equipment packages defined for the Terminators of the National ITS Architecture since they represent systems on the boundary of the architecture and, therefore, do not have functional descriptions within the architecture. Hence any element mapped only to a National ITS Architecture terminator- e.g. National Weather Service- will not have functions assigned to it. To consider an example of this mapping beginning with service packages, the Surface Street Control (ATMS03) service package is composed of three Traffic Management Subsystem equipment packages, Collect Traffic Surveillance, TMC Signal Control and Traffic Equipment Maintenance, and four Roadway Subsystem equipment packages, Field Management Stations Operations, Roadway Basic Surveillance, Roadway Signal Control and Roadway Equipment Coordination. The definitions of these seven equipment packages, copied from version 7.1 of the National ITS Architecture, are: Collect Traffic Surveillance This equipment package remotely monitors and controls traffic sensors and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. TMC Signal Control This equipment package provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management subsystem and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. Traffic Equipment Maintenance This equipment package monitors the operational status of field equipment and detects failures. It presents field equipment status to Traffic Operations Personnel and reports failures to the Maintenance and Construction Management Subsystem. The equipment package tracks the repair or replacement of the failed equipment. The entire range of ITS field equipment may be monitored by this equipment package including sensors (traffic, infrastructure, environmental, security, speed, etc.) and devices (highway advisory radio, dynamic message signs, automated Page 101

95 roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security surveillance equipment, etc.). Field Management Stations Operations This equipment package supports direct communications between field management stations and the local field equipment under their control. Roadway Basic Surveillance This equipment package monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. Roadway Signal Controls This equipment package includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, signal heads, detectors, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. This equipment package represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. Roadway Equipment Coordination This equipment package supports direct communications between field equipment. It includes field elements that control and send data to other field elements. This includes coordination between remote sensors and field devices (e.g., Dynamic Message Signs) and coordination between the field devices themselves (e.g., direct coordination between traffic controllers that are controlling adjacent intersections.). The approach used in the AMPA Regional ITS Architecture was to begin with the mapping of equipment packages to element s service packages within the architecture as an initial definition of the functions being performed by each element. Then, this mapping is tailored, or customized, in the Turbo Architecture tool to provide a more accurate picture of the functions performed by each element. The Turbo Architecture tool also contains a detailed mapping of functional requirements (written as shall statements) to each equipment package. This mapping to functional requirements has been customized for each element, selecting only those requirements that are appropriate given the definition and connectivity of the element. In some cases the functional requirement has been customized to better reflect the functions of the element. This detailed mapping of functional requirements to elements is contained in the Turbo Architecture database. A mapping of equipment packages to the elements is provided in tabular form in Appendix B. The mapping of elements to the functional areas (equipment packages) is provided on the hyperlinked web site version of the architecture. The detail page for each element (which is accessed by clicking on the hyperlinked element name within the Inventory, Inventory by Stakeholder or Inventory by Entity tabs under the Inventory Pulldown) has a list of the Page 102

96 functional areas (equipment packages) assigned to the element. Sometimes the user may need to scroll down to see the equipment packages. For example, the City of Rio Rancho Traffic Operations Center element has the following functional areas assigned to it: Collect Traffic Surveillance TMC Incident Detection TMC Incident Dispatch Coordination/Communication TMC Multimodal Coordination TMC Probe Information Collection TMC Regional Traffic Management TMC Reversible Lane Management TMC Environmental Monitoring TMC Signal Control TMC Traffic Information Dissemination Traffic Equipment Maintenance Traffic Data Collection MCM Environmental Information Processing MCM Environmental Information Collection TMC Evacuation Support This represents a first level of detail that can be obtained in the hyperlinked web site in connection with functionality. The additional level of detail, or detailed functional requirements, can be accessed by clicking on any of the equipment packages associated with the element under review. Using the above example, viewing the City of Rio Rancho Traffic Operations Center element detail page the user can see the equipment packages listed above. If the user were to select one of the equipment packages (all listed as hyperlinks), the equipment package detail page would appear. This page lists the detailed functional requirements that have been customized for the AMPA Regional ITS Architecture as well as providing a full description of what this equipment package contains and a listing of all element that are associated with this equipment package. Page 103

97 9. Standards The following subsections provide a discussion of ITS standards potentially applicable in the region and how to identify the standards that might be applicable on a specific interface within the architecture Discussion of Key Standards for the Region ITS standards establish a common way in which devices connect and communicate with one another. This allows transportation agencies to implement systems that cost-effectively exchange pertinent data and accommodate equipment replacement, system upgrades, and system expansion. Standards benefit the traveling public by providing products that will function consistently and reliably throughout the region. ITS standards contribute to a safer and more efficient transportation system, facilitate regional interoperability, and promote an innovative and competitive market for transportation products and services. The use of ITS standards is very important to project development in the region. Table 9 Identifies the ITS standards that are potentially applicable to the region. This table was created by taking the standards information available in the Turbo Architecture database (which identifies standards applicable to each architecture flow) and taking the total set of standards that result from all of the selected flows. The table provides the status of the standards effort as of April 2015 (the most recent update of the information). The table lists the abbreviation of Standards Development Organization (SDO) in the first column, the name of the standard in the second column and the number of the standard in the third column. Regular updates of SDO activities will help ensure that the latest standards are utilized. The SDOs involved in the development of ITS standards that are listed in the table include: American Association of State Highway and Transportation Officials (AASHTO) American National Standards Institute (ANSI) American Public Transportation Association (APTA) American Society for Testing and Materials (ASTM) Institute of Electrical and Electronics Engineers (IEEE) Institute of Transportation Engineers (ITE) National Equipment Manufacturers Association (NEMA) Society of Automotive Engineers (SAE) Table 9: Applicable ITS Standards SDO Standard Title Document ID AASHTO/ITE Traffic Management Data Dictionary (TMDD) and Message ITE TMDD Sets for External Traffic Management Center Communications (MS/ETMCC) AASHTO/ITE/NEMA Data Element Definitions for Transportation Sensor Systems NTCIP 1209 Page 104

98 SDO Standard Title Document ID (TSS) AASHTO/ITE/NEMA Field Management Stations (FMS) Part 1: Object Definitions NTCIP 1210 for Signal System Masters AASHTO/ITE/NEMA Global Object Definitions NTCIP 1201 AASHTO/ITE/NEMA NTCIP Center-to-Center Standards Group NTCIP C2C AASHTO/ITE/NEMA NTCIP Center-to-Field Standards Group NTCIP C2F AASHTO/ITE/NEMA Object Definitions for Actuated Traffic Signal Controller (ASC) NTCIP 1202 Units AASHTO/ITE/NEMA Object Definitions for Closed Circuit Television (CCTV) Camera NTCIP 1205 Control AASHTO/ITE/NEMA Object Definitions for Closed Circuit Television (CCTV) NTCIP 1208 Switching AASHTO/ITE/NEMA Object Definitions for Conflict Monitor Units (CMU) NTCIP 1214 AASHTO/ITE/NEMA Object Definitions for Data Collection and Monitoring (DCM) NTCIP 1206 Devices AASHTO/ITE/NEMA Object Definitions for Dynamic Message Signs (DMS) NTCIP 1203 AASHTO/ITE/NEMA Object Definitions for Electrical and Lighting Management NTCIP 1213 Systems (ELMS) AASHTO/ITE/NEMA Object Definitions for Environmental Sensor Stations (ESS) NTCIP 1204 AASHTO/ITE/NEMA Object Definitions for Signal Control and Prioritization (SCP) NTCIP 1211 APTA Standard for Transit Communications Interface Profiles APTA TCIP-S ASTM Dedicated Short Range Communication at 915 MHz Standards DSRC 915MHz Group ASTM Standard Practice for Metadata to Support Archived Data ASTM E Management Systems ASTM Standard Specifications for Archiving ITS-Generated Traffic ASTM E Monitoring Data ASTM/IEEE/SAE Dedicated Short Range Communication at 5.9 GHz Standards DSRC 5GHz Group IEEE Incident Management Standards Group IEEE IM IEEE SAE SAE SAE Standard for Message Sets for Vehicle/Roadside Communications Advanced Traveler Information Systems (ATIS) General Use Standards Group Dedicated Short Range Communications (DSRC) Message Set Dictionary Dedicated Short Range Communication (DSRC) Common Performance Requirements IEEE ATIS General Use SAE J2735 SAE J2945 NTCIP C2F: NTCIP Center-to-Field Standards Group Table 9 above specifies the NTCIP Center-to-Field (NTCIP C2F) Group of Standards, which addresses the communications protocols between a center and the ITS field devices it manages. The family includes the communications profiles that cover the interfaces between a Page 105

99 traffic management center and dynamic message signs, ramp meters, environmental sensors, or CCTVs under its control. These protocols are common across all Center-to-Field interfaces in the National ITS Architecture, and rather than repeat the entire list for each architecture flow, we have created this summary entry the NTCIP C2F Group of communications standards. The vocabulary (objects) is specific to the actual architecture flow in the National ITS Architecture and is therefore mapped to the corresponding Data Object standard. (In the example above, the Object Definitions for Dynamic Message Signs standard would be mapped to the specific control and data flows between the Traffic Management Subsystem and the Roadway DMS equipment). In order to satisfy a wide spectrum of system and regional communications requirements, Center-to-Field ITS deployments should each implement the combinations of the following NTCIP C2F communications protocols that best meet their needs. This Group includes the following Standards Activities: NTCIP 1101: Simple Transportation Management Framework (STMF) NTCIP 1102: Base Standard: Octet Encoding Rules (OER) NTCIP 1103: Simple Transportation Management Protocol (STMP) NTCIP 2101: Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2102: Subnet Profile for PMPP Over FSK modems NTCIP 2103: Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2104: Subnet Profile for Ethernet NTCIP 2201: Transportation Transport Profile NTCIP 2202: Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2301: Application Profile for Simple Transportation Management Framework (STMF) NTCIP 2302: Application Profile for Trivial File Transfer Protocol NTCIP 2303: Application Profile for File Transfer Protocol (FTP) NTCIP C2C: NTCIP Center-to-Center Standards Group Table 9 above specifies the NTCIP Center-to-Center (NTCIP C2C) Group of Standards, which address the communications protocols between two centers (e.g. two traffic management centers exchanging information to facilitate regional coordination of traffic signals). Some of the communication protocols covered by this family are DATEX-ASN, XML, and FTP. These protocols are common across all Center-to-Center interfaces in the National ITS Architecture, and rather than repeat the entire list for each architecture flow, we have created this summary entry the NTCIP C2C Group of communications standards. Page 106

100 The standards that describe the vocabulary (data elements and messages) are mapped to specific architecture flows rather than the entire set of NTCIP C2C interfaces. In the regional traffic coordination example above, the Traffic Management Data Dictionary and the Message Set for External TMC Communications standards would be mapped to the specific flows between two Traffic Management Subsystems. In order to satisfy a wide spectrum of system and regional communications requirements, Center-to-Center ITS deployments should each implement the combinations of the following NTCIP C2C communications protocols that best meet their needs. This Group includes the following Standards Activities: NTCIP 1102: Base Standard: Octet Encoding Rules (OER) NTCIP 2104: Subnet Profile for Ethernet NTCIP 2202: Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2303: Application Profile for File Transfer Protocol (FTP) NTCIP 2304: Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2306: Application Profiles for XML Message Encoding and Transport in ITS Center to Center Communications 9.2. Reference to the Detailed Standards information on the Web Site The previous section provides a general discussion of the standards environment in the region. However the architecture does contain a far more detailed standards view, one that maps applicable standards to the individual information flows that goes from one element to another. This detailed information is contained in the hyperlinked web site and can be accessed through the links to the architecture flows shown as part of each interface. Each element description page has a set of links that describe the information flowing to and from the element to other elements of the architecture. Selecting any of these interface links brings the user an interface page. For example, the interface between the NMDOT Statewide TMC and the NMDOT DMS (dynamic message signs) is shown in Figure 10. There is one information flow going to the DMS element and two coming back from it. Selecting one of the flows provides information regarding the flow and gives a list of ITS standards that are applicable to the flow. An example, for the roadway information system data flow, is shown in Figure 11. Figure 10: Example of Interface Page 107

101 Figure 11: Example of standards mapping page Page 108

102 10. Project Sequencing The incorporation of the AMPA Regional ITS Architecture into the planning process in the past few years has yielded projects that are linked to the ITS architecture. Through the deployment of projects produced from the metropolitan transportation planning process at the MRCOG, and the programming mechanism of the Transportation Improvement Program (TIP), the services supported in the AMPA Regional ITS Architecture will be implemented and made a reality in the transportation system. Project implementation completes the evolution from: transportation needs to services, to functional descriptions in the regional ITS architecture, to project identification in the planning process and to project definition and deployment. The overarching goal of the AMPA Regional ITS Architecture development process is that this evolution takes place with the maximum amount of integration knowledge possible, so as to efficiently and economically implement the ITS systems required to serve the transportation community and users. MRCOG is the designated metropolitan planning organization in the AMPA and is responsible for facilitating the prioritization and programming for all projects in the AMPA through the development of the 20-year Metropolitan Transportation Plan (MTP), and its near-term Transportation Improvement Program (TIP), the latter being a subset of the Statewide Transportation Improvement Program (STIP). Further planning/congestion mitigation guidance is included in the Congestion Management Process (a requirement for the MRCOG/MPO and discussed in Section 12 of this document). The MRCOG s ITS Subcommittee is the committee responsible for the evaluation of all projects considered for federal, state, and local transportation funding and submitted for inclusion into the TIP. The ITS Subcommittee is comprised of member agency ITS stakeholders, however, it is important to note that not all ITS projects are funded through this process, such as those involving emergency services, universities, the towing industry, etc. Although these groups are ITS Stakeholders, they are not public sector transportation and/or transit service providers and therefore are not members of the MRCOG. Where known, projects from these stakeholders have been included in the ITS Architecture in order to fully integrate ITS services to meet the regional mobility goals identified for the AMPA and beyond the AMPA. While many projects do not have a strong dependency on other projects, in some cases dependencies or relationships exist between systems and projects so that an order can be identified for deployment. Given the importance of integration of ITS for stakeholder agencies within the AMPA, and the dependencies of one system on another or one project on another, it is critical to view the entire transportation system at a high functional level. The AMPA Regional ITS Architecture provides this view point and aids in understanding the relationships between the ITS systems in the region Process for Selecting Projects A two-step process was used to select projects for the update of the AMPA Regional ITS Architecture: Page 109

103 Review of the local and regional transportation programs including (but not limited to) the AMPA s FY2016 FY2021 TIP and FY2016-FY2021 TIP and associated MTP, local agency Capitol Improvement Plans (CIPs), and other non-mrcog stakeholder plans. Gather Stakeholder feedback through outreach workshops, offline discussions, meetings and s, and Consider Service package Prioritization (which is covered in Section 6.2). The AMPA Regional ITS Architecture was created based on the needs for the region over the next 20 years. This ITS architecture identifies which systems (operated by agencies in the AMPA region or adjacent to the AMPA region) should be interfaced to maximize integration opportunities throughout the region. There were also TIP projects that did not identify ITS in the project description, but were viewed as potentially having an ITS component identified on the TIP Project Submittal Form C and reviewed by the ITS Subcommittee as referenced above as part of the TIP development process (e.g. signal coordination or signal preemption for an intersection improvement). In these situations, stakeholders were asked to provide feedback regarding the likelihood of ITS being incidental to the TIP project. Where these projects were likely to have ITS components (e.g. signals, DMS, CCTV, etc.), they have been included in the project list. The second step in the process (after identifying which projects were ITS related) was to obtain stakeholder feedback on the proposed ITS projects and their prioritization. Input from stakeholders was used and later refined to establish which projects were allocated to the short term (0-5 years) and long term (over 5 years). Obtaining stakeholder feedback was necessary for the following reasons: Ensure the ITS Project was consistent with stakeholder needs. Establish an estimated timeline or priority for ITS Project deployment and denoting a general order for project implementation. Understand the relationship and traceability between ITS projects and the AMPA Regional ITS Architecture (through customized service package prioritization). Projects listed as part of the regional TIP process were identified as short term projects based on the implied relatively short timeframe of the related TIP. A majority of this process was accomplished through interviews with stakeholders and at the stakeholder workshop. During the architecture review workshop held in February 2016, a draft list of projects was presented and input from the stakeholders was incorporated into the project list. During the workshop, comments were received from stakeholders regarding ITS project names, timeframes, funding sources, responsible agencies and programmed projects. In addition, stakeholders were able to identify additional sources where the analysts could find ITS projects that have been planned for the state. The results of the workshop and various stakeholder inputs after the workshop are provided in Table 10. The information included in each of the project functional areas is as follows: Page 110

104 Project Name and Location. The name and location of the proposed ITS project. Source. The ITS related document or input from which the project was identified. Description. The description of the project or services to be provided. Lead Agency. The primary agency or stakeholder responsible for the initiation, implementation, and maintenance of the ITS project and its components TIP Number. Funding is identified through the TIP programming process and is based on federal, state, and local sources as presented by the lead agency. Primary sources of ITS funding in the AMPA (MPO) include, but are not limited to CMAQ, NHPP, STPU/S, IM, state, and local amounts. Service packages. Maps the proposed ITS project to a transportation service (customized service package) identified in the AMPA Regional ITS Architecture, which reflects traceability from ITS project to the AMPA Regional ITS Architecture. It is important to note that if there are one or more customized service packages listed in this column then it is included as part of the regional ITS architecture. Priority. Indicates the estimated timeframe for an ITS project to be deployed. It is estimated that short-term projects will be implemented in 0-5 years; and long-term projects will be implemented in over 5 years. Page 111

105 Table 10: AMPA ITS Projects Project Name Location Description Lead Agency TIP Number Service Package Priority ABQ PD Communications ABQ EM-10 Short Everbridge ABQ Ride Connected Vehicle Intermittent Bus Lanes ABQ Ride Connected Vehicle Transit Signal Priority ABQ Ride Fare Collection System Upgrade ABQ Ride Technology Upgrade ABQ ABQ Upgrade reverse communications to the Everbridge system. This project will also include E911 upgrades. The overall goal of this project is to allow reverse communications for specific regions. Implement a connected vehicle transit application on Intermittent Bus Lanes Implement a connected vehicle version of transit signal priority on selected routes ABQ PD Communicatio ns ABQ Ride AVSS12-11 Long ABQ Ride APTS09-6 Long ABQ Upgrade to fare collection system to employ new technologies to improve efficiency of operations ABQ Ride APTS04-1 Long ABQ Transit Technology Upgrade project will upgrade ABQ ABQ Ride APTS05-1 Short RIDE servers to a virtual environment, as well as upgrading security equipment. ABQ Ride Transit ABQ Implement a connection protection system on ABQ ABQ Ride APTS11-1 Long Connection Protection Ride routes ABQ Ride Connected ABQ Implement a connected vehicle transit safety ABQ Ride AVSS12-06 Long Vehicle Safety Application application to provide a warning to the transit vehicle driver of pedestrians crossing in front of the vehicle. Statewide Transit Traveler ABQ Consolidation of transit passenger information across ABQ Ride, ATIS01-16 Long Information System the state NMDOT Travel Demand ABQ Coordination with NMDOT to provide comparative ABQ Ride, ATIS01-12 Long Management transit and road travel times on regional DMS to NMDOT provide travelers with travel alternatives. Bernalillo County Develop connection between County TMC and City Bernalillo ATMS07-1 Long Interconnect to City of ABQ TMC to get access to city cameras. County Bernalillo County Bernalillo Installing additional CCTV cameras on county roads. Bernalillo ATMS01-4 Short Surveillance Expansion County County Bernalillo County Traffic Bernalillo Install additional adaptive systems on Bridge Blvd and Bernalillo ATMS03-4 Long Page 112

106 Project Name Location Description Lead Agency TIP Number Service Package Priority Signal System Upgrade County Tramway Blvd. County City of ABQ ITS ABQ Add 69 PTZ Cameras, upgrade controllers, and City of ABQ A ATMS01-1, ATMS03- Short development- Phase XVI replace video detection equipment 1 City of ABQ ITS ABQ This phase includes additional Fiber, 37 CCTVs, City of ABQ A ATMS01-1, ATMS03- Short development-phase XVII upgrade of 37 controllers, and addition of 3 count stations 1 City of ABQ Surveillance ABQ Upgrade surveillance equipment in the city. City of ABQ ATMS01-1 Long system upgrade City of ABQ Traffic Signal ABQ Upgrade signal controller systems in the city. City of ABQ ATMS03-1 Long System Upgrade City of Rio Rancho Flood NM528 Deploy flood monitoring systems on NM528 City of Rio MC03-2 Long Monitoring City of Rio Rancho NM528 Reconstruction City of Rio Rancho Northern Blvd surveillance City of Rio Rancho Public Safety interconnect City of Rio Rancho Signal Preemption Upgrade City of Rio Rancho Signal System Wireless Upgrade City of Rio Rancho Southern Blvd Reconstruct City of Rio Rancho Surveillance Expansion City of Rio Rancho Travel Time Calculation MRCOG Travel and Traffic Measurement NM528 from Ridgecrest to Northern Blvd City of Rio Rancho City of Rio Rancho City of Rio Rancho Southern Blvd City of Rio Rancho NM528 AMPA Wide Reconstruction includes adding CCTV and Bluetooth travel time monitoring device Add Cameras and Bluetooth devices during Northern Blvd reconstruction. Add connection from City of Rio Rancho TMC to 911 center and city EOC. Upgrade of signal preemption for fire/ems. Upgrade to GPS capable Wireless connection to traffic signals (communication expansion to more traffic signals). Includes fiber replacement and additional CCTV Additional Cameras and Bluetooth on Broadmore Expand Bluetooth on NM528 in the City ( to calculate travel time and speed) This project will increase travel and traffic measurement functionality to support the Consolidated Traffic Monitoring Program. Rancho City of Rio Rancho ATMS01-2 Short City of Rio Rancho ATMS01-2 Short City of Rio ATMS08-2, EM08-6 Short Rancho City of Rio EM02-04 Long Rancho City of Rio ATMS03-2, MC07-3 Long Rancho City of Rio A ATMS01-2 Short Rancho City of Rio ATMS01-2, ATMS02- Long Rancho 3, MC07-3 City of Rio ATMS03-2 Short Rancho MRCOG A AD1-4, AD2-1, AD2-2 Short Page 113

107 Project Name Location Description Lead Agency TIP Number Service Package Priority Electric Charging Station Management Regionwide The Electric Charging Station Management application provides an exchange of information between vehicle and charging station to manage the Municipalities AVSS12-7 Long ITS Incident Management & Signal Oper. Enhancements Albuquerque Regional TMC NMDOT Adaptive Traffic Signal Systems NMDOT CV Curve Speed Warning NMDOT CV Intelligent Traffic Signal System NMDOT CV Pedestrian in Signalized Crosswalk Warning AMPA Wide NM6, NM45 Regionwide Regionwide Regionwide charging operation. The purpose of this project is to develop inter-agency ITS and signal/operational improvements in support of Incident Mgmt on the River Crossings and select CMP Corridors within the AMPA Develop Regional TMC to provide joint operations capability with, City of ABQ, County, Public Safety, and Transit Install adaptive traffic signal systems on NM6 in Valencia and NM45 (Coors Blvd) The Connected Vehicle curve speed warning application allows connected vehicles to receive information that it is approaching a curve along with the recommended speed for the curve. The Connected Vehicle Intelligent Traffic Signal System (ISIG) application uses both vehicle location and movement information from connected vehicles as well as infrastructure measurement of nonequipped vehicles to improve the operations of traffic signal control systems. The application utilizes the vehicle information to adjust signal timing for an intersection or group of intersections in order to improve traffic flow, including allowing platoon flow through the intersection. The Connected Vehicle Pedestrian in Signalized Crosswalk Warning application provides to the connected vehicle information from the infrastructure that indicates the possible presence of pedestrians in a crosswalk at a signalized MRCOG A ATMS01, ATMS03, ATMS06, ATMS08 Short NMDOT A AD1, AD2, ATMS01, ATMS04, ATMS05, ATMS06, ATMS07, ATMS08 Short NMDOT ATMS03-5 Short NMDOT AVSS12-12 Long NMDOT AVSS12-9 Long NMDOT AVSS12-14 Long Page 114

108 Project Name Location Description Lead Agency TIP Number Service Package Priority intersection. NMDOT CV Pedestrian Regionwide The Pedestrian Mobility application will integrate NMDOT AVSS12-10 Long Mobility traffic and pedestrian information from roadside or intersection detectors and new forms of data from wirelessly connected, pedestrian (or bicyclist) carried mobile devices (nomadic devices) to request dynamic pedestrian signals or to inform pedestrians when to cross and how to remain aligned with the crosswalk based on real-time Signal Phase and Timing (SpaT) and MAP information NMDOT CV Queue Warning Regionwide The Connected Vehicle Queue Warning (Q-WARN) application utilizes connected vehicle technologies, including vehicle-to-infrastructure (V2I) and vehicleto-vehicle (V2V) communications, to enable vehicles within the queue event to automatically broadcast their queued status information (e.g., rapid deceleration, disabled status, lane location) to nearby upstream vehicles and to infrastructure-based central entities (such as the TMC). NMDOT AVSS12-4 Long NMDOT CV Railroad Crossing Violation Warning NMDOT CV Reduced Speed Zone Warning NMDOT CV Restricted Lane Warning Regionwide Regionwide Regionwide The Railroad Crossing Violation Warning (RCVW) application will alert and/or warn drivers who are approaching an at-grade railroad crossing if they are on a crash-imminent trajectory to collide with a crossing or approaching train. The Reduced Speed Zone Warning Connected Vehicle application provides connected vehicles which are approaching a reduced speed zone with information on the zone s posted speed limit and/or if the configuration of the roadway is altered (e.g., lane closures, lane shifts). The Connected Vehicle Restricted Lane Warnings application provides the connected vehicle with restriction information about the travel lanes, such as NMDOT AVSS12-15 Long NMDOT AVSS12-1 Long NMDOT AVSS12-16 Long Page 115

109 Project Name Location Description Lead Agency TIP Number Service Package Priority if the lane is restricted to high occupancy vehicles (HOV), transit, or public safety vehicles only or has defined eco-lane criteria. A connected vehicle can use this information to determine if the vehicle is in a in a lane that has lane restrictions. NMDOT CV Road Weather Motorist Alert NMDOT CV Speed Harmonization NMDOT CV Spot Weather Impact Warning NMDOT CV Traveler Information NMDOT CV Variable Speed Limits for Weather Responsive Traffic Management Regionwide Regionwide Regionwide Regionwide Regionwide The Road Weather Motorist Alert and Warning application provides the capability of collecting road weather data from connected vehicles and using that data to develop short term warnings or advisories that can be provided to individual motorists. The Connected Vehicle Speed Harmonization application determines speed recommendations based on traffic conditions and weather information. The speed recommendations can be regulatory (e.g. variable speed limits) or advisory. The purpose of speed harmonization is to change traffic speed on links that approach areas of traffic congestion, bottlenecks, incidents, special events, and other conditions that affect flow. The Spot Weather Impact Warning (SWIW) Connected Vehicle application will alert drivers to unsafe conditions or road closure at specific points on the downstream roadway as a result of weatherrelated impacts, which include, but are not limited to high winds, flood conditions, ice, or fog. This project is a combination of several Connected Vehicle Traveler Information related applications including those for weather related traveler information. The Connected Vehicle Variable Speed Limits for Weather-Responsive Traffic Management application uses road weather information from connected vehicles as well as current and historical data from NMDOT AVSS12-19 Long NMDOT AVSS12-8 Long NMDOT AVSS12-2 Long NMDOT AVSS12-20 Long NMDOT AVSS12-18 Long Page 116

110 Project Name Location Description Lead Agency TIP Number Service Package Priority multiple sources to determine the appropriate current safe speed. NMDOT CV Vehicle Data for Traffic Operations NMDOT CV Work Zone Warning NMDOT Device Installation FY 16 NMDOT Device Installation FY20 NMDOT DMS Installation FY15 Regionwide Regionwide Regionwide Regionwide Regionwide The Vehicle Data for Traffic Operations (VDTO) application uses probe data information obtained from vehicles in the network to support traffic operations, including incident detection and the implementation of localized operational strategies. The Connected Vehicle Work Zone Warning application provides information about the conditions that exist in a work zone to vehicles that are approaching the work zone NMDOT Device Installation in FY16 DMS Installations I-40 WB at Carnuel I-25 Frontage NB at Candelaria NM 528 NB at US 550 connection CCTV PDN at 2 nd St Lomas at I-40 DMS Installation Central WB at I-25 MLK WB at I-25 I-25 SB frontage at Menaul Central EB at I-25 Roy EB at I-25 Rio Bravo EB at I-25 Bridge EB at I-25 CCTV Installation Tramway at PDN RWIS Installation I-40 in Tijeras Canyon DMS Installations on I-25 and I-40 in FY15 Montano EB at I-25 NMDOT AVSS12-5 Long NMDOT AVSS12-3 Long NMDOT A ATMS01-5, ATMS06-8 NMDOT ATMS01-5, ATMS06-8, MC03-6 Short Short NMDOT A ATMS06-8 Short Page 117

111 Project Name Location Description Lead Agency TIP Number Service Package Priority Comanche EB and WB at I-25 University NB at I-40 Lomas WB and EB at I-25 frontage Osuna EB at I-25 San Mateo WB at I-25 NMDOT DMS Installation FY17 NMDOT DMS Installation FY18 NMDOT Expand Probe Data Collection NMDOT Fiber Extension FY16 NMDOT Fiber Extension FY17 NMDOT Freeway Lane Management NMDOT I-25 Fiber Expansion NMDOT Improved AVL on Motorist Assist NMDOT Maintenance Systems Upgrades Regionwide Regionwide Regionwide NMDOT DMS Installation FY17 Carlisle NB and SB at I-40 MLK EB at I-25 NMDOT DMS Installation FY18 Lead WB at I-25 Ceasar Chavez WB at I-25 Coal EB at I-25 Tramway at Tramway Terrace 337 NB at I-25 Receive additional third party data to provide travel times on arterials Fiber extension from Rio Puerco to the Bernalillo/Cibola Cty line Supports DMS and CCTV deployments NMDOT A ATMS06-8 Short NMDOT A ATMS06-8 Short NMDOT ATMS02-3 Short NMDOT A ATMS01-5, ATMS08-6, ATMS02-3 Fiber extension from NM 6 to Belen NMDOT ATMS01-5, ATMS08-6, ATMS02-3 Short Regionwide Add lane management and control capabilities on NMDOT ATMS04-1 Long interstates I-25 Fiber extension from NM 6 to Belen along I-25- NMDOT ATMS01-5, ATMS08- Short including DMSs and cameras 6 Regionwide Upgrade AVL system on Motorist Assist vehicles to NMDOT EM04-1 Short provide more frequent location updates Regionwide Upgrade maintenance back end systems to provide NMDOT MC06-6, MC07-11 Long improved resource allocation, high net backend (hook into Visala), and resource inventory controls NMDOT Maintenance Regionwide Equipping maintenance vehicles with onboard NMDOT MC06-6 Long Vehicle Upgrades intelligence to quantify conditions. NMDOT Pretrip Planner Regionwide Through NMROADS provide pre trip travel planning NMDOT Short Short Page 118

112 Project Name Location Description Lead Agency TIP Number Service Package Priority capability NMDOT Smart Workzone Regionwide Deploy smart workzone systems including mobile NMDOT MC08-6 Short Systems DMS, mobile CCTV, queue detection, dynamic merges. NMDOT Traffic Data Regionwide Expand counting capabilities through additional NMDOT AD1-5 Short Collection Expansion devices and use of third party data NMDOT Trailblazer Regionwide Deploy additional Trailblazer signs NMDOT MC08-6 Short Deployment RailRunner Positive Train Regionwide Incorporate Positive Train Control capability to Rio Metro APTS01-6 Long Control RailRunner Rio Metro Buses APC Regionwide Deploy Automated Passenger Counters on Rio Metro Rio Metro APTS10-1 Short Rio Metro Real time Bus Location Regionwide buses. Make Rio Metro real Time bus locations available to users through Where s my bus and Where s my transit apps. Rio Metro APTS08-2 Short Page 119

113 10.2. How to Use the Recommended Project Sequencing The ITS project table ( Table 10 above) can be used as an input for the Transportation Improvement Plan (TIP) and Metropolitan Transportation Plan (MTP) for MRCOG and the Strategic/Long Range Plan for other organizations for planning purposes (as described in Section 12). The planning process allocates ITS project funding in coordination with other transportation projects. As displayed in Table 10, projects are classified as short or long-term timeframes. Some of these projects are drawn directly from the current TIP, while the long term projects could be used to support long range transportation plan update. The key question stakeholders may ask is, Now that we have a comprehensive list of ITS projects separated by timeframes, how do I use the projects to address the needs described in Section 6.1? To answer this question, stakeholders should focus on the following concepts: Why is this Important. Stakeholders should remember the reasons for going through the process of creating sequenced ITS projects. Ultimately they want to deploy projects that support the needs expressed in their ITS Architecture. Who s in Charge? Stakeholders should consider identifying a person or group that is responsible for managing how ITS Projects get deployed. This person or group would be aware of the big picture by familiarizing themselves with all of the planned activities and ensure integration opportunities are maximized in project deployments. Systematic Process. Stakeholders should ensure that projects are managed in a systematic manner. Funding Allocation. Stakeholders should ensure funding is allocated appropriately to support projects that have dependencies or synergies to be utilized. This is important if there are future projects that will depend on a short term or current project. The short term or current project must be funded appropriately to support the accommodation of known future project features or interfaces, thus avoiding redesign for future project accommodation. Project List Management. Stakeholders should prioritize projects within their common timeframes based on the aforementioned concepts. It is important for short-term projects to be reviewed by stakeholders prior to being transitioned into the TIP. A member of the ITS Subcommittee, or a group of members, should be responsible for removing projects from the regional list once implemented. Although project lists may reflect a single project, projects are typically broken into multiple phases and are implemented in an incremental manner. For example, many ITS projects are partially deployed as part of larger construction projects. A project s scope might involve interfacing with ten agencies and funding constraints may require agencies to be interconnected one at a time. In this situation, a project might by implemented in five years, if two agencies are being interconnected per year. If a project is partially 120

114 implemented due to unforeseen circumstances (e.g. limited funding received), then the list manager should update the project to reflect the remaining components that need to be implemented. The key point for project list management is projects will be implemented in an incremental manner, therefore the members of the ITS Subcommittee designated as the list manager(s) should keep accurate records of the incremental process and meet with stakeholders to determine how funding should be reallocated. Desired Outcome. Stakeholders should remember the desired outcome, which is to deploy projects to maximize integration opportunities throughout the AMPA. Therefore, when projects are transitioned into the project development phase, stakeholders should always be aware of other project deployment activities (even if the other activities require a project to be deployed at a different time). This mindset will require stakeholders to be flexible in developing interfaces what will allow for future expansion based on overall regional needs. An important issue to remember is when a project it to be implemented, stakeholders should convene to determine the specific details for deploying a project (e.g. how many phases will be required for this project and which components of service packages are allocated to a particular phase?). Table 10 (and the corresponding project page on the website) can be used as a guide as to which agencies/systems, services and interfaces to consider during the discussion and design phase of project implementation. 121

115 11. Agreements There are several types of arrangements associated with the interfaces included when deploying ITS projects within the state. The identification of institutional agreements required is crucial to the development of consensus architecture. This section documents the agreements associated with the AMPA Regional ITS Architecture, whether planned or existing Types of Agreements There are several types of arrangements associated with the interfaces included when deploying ITS projects within the AMPA region, and throughout the state. Data exchanges between systems require agreements on the transmission protocol and data formats to ensure compatibility. Coordinating field device operations owned by different agencies requires defined procedures for submitting message requests and rules governing when such requests can be honored. Such coordination can be done with informal arrangements such as a Memorandum of Understanding (MOU). Sharing control of field devices operated by different agencies, on the other hand, involves more liability issues, which requires more formal agreements. Coordinated incident response may also require formal agreements, but also requires group training of personnel from various agencies. While all interfaces involve agreements for data compatibility, agreements for procedure and operation as well as training can also be critical elements to optimizing the benefits of the architecture. Table 11 identifies types of potential agreements that could be used by agencies in the region.. It is recognized, however, that a specific agreement mechanism used among stakeholders may be different between them (for example the nature and limitations associated with a MOU might vary between stakeholders). This should be taken into consideration when identifying and pursuing the proper agreement mechanism. Type of Agreement Handshake Agreement Memorandum of Understanding Table 11: Types of Institutional Agreements Description Early agreement between one or more partners Not recommended for long term operations. Initial agreement used to provide minimal detail and usually demonstrating a general consensus. Used to expand a more detailed agreement like an Interagency Agreement which may be broad in scope but contains all of the standard contract clauses required by a specific agency. May serve as a means to modify a much broader Master Funding Agreement, allowing the master agreement to cover various ITS projects throughout the region and the MOUs to specify the scope and differences between the projects. 122

116 Type of Agreement Interagency Agreement Intergovernmental Agreement Operational Agreement Funding Agreement Description Between public agencies (e.g., transit authorities, cities, counties, etc.) for operations, services or funding Documents responsibility, functions and liability, at a minimum. Between governmental agencies (e.g., Agreements between universities and State DOT, MPOs and State DOT, etc.) Between any agency involved in funding, operating, maintaining or using the right-of-way of another public or private agency. Identifies respective responsibilities for all activities associated with shared systems being operated and/or maintained. Documents the funding arrangements for ITS projects (and other projects) Includes at a minimum standard funding clauses, detailed scope, services to be performed, detailed project budgets, etc. Master Agreements Standard contract and/or legal verbiage for a specific agency and serving as a master agreement by which all business is done. These agreements can be found in the legal department of many public agencies. Allows states, cities, transit agencies, and other public agencies that do business with the same agencies over and over (e.g., cities and counties) to have one Master Agreement that uses smaller agreements (e.g., MOUs, Scope-of-Work and Budget Modifications, Funding Agreements, Project Agreements, etc.) to modify or expand the boundaries of the larger agreement to include more specific language. In addition to the agreements noted above, one element that must be considered is data ownership. The type of agreement used to address this issue may vary depending upon agencies involved Agreements The identification of institutional agreements, along with if these agreements exist or need to be formulated, is a key output of this Plan and should be updated periodically as part of the overall Statewide ITS Architecture. During the stakeholder workshops held in Albuquerque throughout the course of this project, stakeholders identified a variety of agreements that currently exist in the state. In addition, the idea of formulating additional institutional agreements was discussed in great detail. From these meetings, and additional discussions with stakeholders who were unable to attend the workshops, a list of existing agreements throughout the AMPA Region was compiled. It is represented in Table 12 below. Table 12: Institutional Agreements Agencies Type of Agreement Reason NMDOT Counties Operational Agreement or MOU NMDOT provides field equipment for counties. The counties are responsible for power 123

117 Agencies Type of Agreement Reason NMDOT Media MOU NMDOT allows the use of Department video feeds on media broadcasts with limitations of use associated with concerns over privacy and public sensibilities City of Albuquerque City of Rio Rancho NMDOT City of Rio Rancho NMDOT NMDOT City of Albuquerque City of Albuquerque City of Rio Rancho City of Rio Rancho NMDOT City of Albuquerque City of Albuquerque City of Rio Rancho Counties Counties Town of Bernalillo Town of Bernalillo City of Albuquerque City of Rio Rancho City of Rio Rancho Operational Agreement or MOU Operational Agreement or MOU Operational Agreement Operational Agreement Operational Agreement Operational Agreement MOU The City of Albuquerque provides maintenance to ITS field equipment. Counties are responsible for power. The City of Rio Rancho provides maintenance to ITS field equipment. Counties are responsible for power. NMDOT provides field equipment (RWIS) for the Town of Bernalillo. The town provides the power. The City of Rio Rancho provides maintenance to ITS field equipment (RWIS). The town is responsible for power. Operation of NMDOT signals (based on geographic location). Operation of NMDOT signals (based on geographic location). Mutual Aid agreements for Fire/EMS. Counties MOU Mutual Aid agreements for Fire/EMS. City of Albuquerque MOU Mutual Aid agreements for Fire/EMS. Counties MOU Mutual Aid agreements for Fire/EMS. City of Albuquerque All Regional Stakeholders City of Albuquerque City of Rio Rancho Operational Agreement MOU Interagency Agreement Interagency Agreement NMDOT MRCOG Intergovernmental Agreement Rio Metro City of Albuquerque Sandoval County City of Rio Rancho MOU MOU Shared control over NMDOT CCTV. The ability for the COA Police Department to issue an Amber Alert. The City of Albuquerque Police dispatch maintenance and construction vehicles after hours. The City of Rio Rancho Police dispatch public infrastructure fleet vehicles after hours. Operation and maintenance of Rail Runner. For the City of Rio Rancho to provide paratransit services throughout the county. Provide fixed route service in the City of Rio Rancho. 124

118 Agencies Type of Agreement Reason City of Rio Rancho City of Rio Rancho Sandoval County Tribal Governments MOU MOU MRCOG NMDOT Intergovernmental Agreement MRCOG NMDOT Intergovernmental Agreement MRCOG City of Albuquerque City of Rio Rancho City of Rio Rancho City of Rio Rancho Member agencies, NMDOT, and FHWA City of Albuquerque Sandoval County Bernalillo County City of Albuquerque Intergovernmental Agreement Interagency Agreement MOU MOU MOU Regional Dispatch of Emergency Vehicles. Regional Dispatch of Emergency Vehicles. House the Statewide TMC in the MRCOG building. Data sharing agreement. MRCOG Traffic counting responsibilities Roadway, vehicle, and non-motorized vehicle counting and archiving responsibilities. Signal priority for ABQ Rapid Ride throughout the City. Signal Preemption for fire and EMS vehicles. Signal Preemption for fire and EMS vehicles. Signal Preemption for fire and EMS vehicles Potential Agreements For each customized service package developed in the architecture, potential institutional agreements can be identified. Agreements are identified on the basis of information being shared across institutional boundaries. Instances that involve the sharing of information wholly within one institution do not require an agreement. For example, Figure 12 illustrates transit fixed route operations for the City of Albuquerque Transit (ABQ RIDE). Taking a look at the right side of the diagram, the ABQ RIDE dispatch system is sharing information with the ABQ RIDE fixed route transit vehicles and other high capacity transit vehicles as well as the City of Albuquerque transit website. Since the ABQ RIDE dispatch system is sharing information to the ABQ RIDE s fixed route vehicles (and other high capacity vehicles) and the City of Albuquerque s website, no institutional agreements are necessary because the sharing of information is between elements under the same institutional entity. Taking a look at the left side of the diagram (and a few interfaces on the right as well) yields a different institutional relationship. The ABQ RIDE dispatch system could collect road network conditions about the roadways managed by Bernalillo County, the City of Rio Rancho, and NMDOT. Since the ABQ RIDE dispatch system is receiving information from other agency traffic operations centers, institutional agreements may be necessary (no agreement necessary for the City s own TOC). Simply put, Bernalillo County (Bernalillo County Traffic Operations Center), the City of Rio Rancho (City of Rio Rancho Traffic Operations Center), and NMDOT (NMDOT Statewide TMC) would agree to share road network conditions with the City of Albuquerque (ABQ RIDE). The same application of this theory would also apply to the 125

119 maintenance and construction elements as well as the additional information service providers as identified in the figure. Also, this particular example shows a unidirectional flow of information, but it is quite common for there to be information going in both directions that would be subject to an agreement. Figure 12: Example Service package: APTS2- Transit Fixed Route Operations for City of Albuquerque Transit Each service package identified in the AMPA Regional ITS Architecture and selected as a high priority service package was analyzed using the same methodology as described above. Table 13 documents the results of this analysis and identifies where institutional agreements are needed and what the purpose of the agreement are (i.e. the information that is being shared that would require an agreement). The table is sorted by Priority Service, or the transportation service where the agreement has been identified. The Potential Parties to Agreement identified the institutional entities that might share information, generally starting with the source entity or entities. The Purpose column gives a short description of the information being shared. It is important to note that the entities listed in the following table have not been identified in this table as a source or destination for the information being shared, nor does this 126

120 table contain the status of any institutional agreements. This table is intended to identify the possible agreements between entities. Therefore, this table should be used as a starting point when identifying or pursuing agreements between entities. Table 13: Potential Institutional Agreements Priority Service Potential Parties to Agreement Purpose Archive Data Emergency Management MRCOG, NMDOT, the City of Albuquerque, the City of Rio Rancho, Bernalillo County, Sandoval County, Tribal Governments. MRCOG, NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, Kirtland AFB, Municipalities, Sandia Labs, Tribal Governments, UNM NMDOT, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, MRCOG, and UNM Bernalillo County, City of Albuquerque, City of Rio Rancho, Kirtland AFB, Municipalities, NM State Police, NMDOT, Sandia Labs, Sandoval County, Tribal Governments and UNM Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NM State Police, Private Ambulance Providers and Sandoval County Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NM State Police, Sandoval County, Tribal Governments and UNM City of Albuquerque and City of Albuquerque Public Safety City of Albuquerque and Bernalillo County Sheriff and Fire/EMS City of Albuquerque and City of Rio Rancho Public Safety City of Albuquerque and NM State Police City of Rio Rancho and City of Rio Rancho Public Safety Bernalillo County and City of Albuquerque Public Safety Bernalillo County and City of Rio Rancho Public Safety Providing traffic archive data Archive coordination Providing emergency archive information Sharing transit archive information Coordinating incident response Coordinate patient and care facility status Provide care facility status Provide signal preemption Provide signal preemption Provide signal preemption Provide signal preemption Provide signal preemption Provide signal preemption Provide signal preemption 127

121 Priority Service Potential Parties to Agreement Purpose Bernalillo County and Bernalillo County Public Safety NMDOT, Bernalillo County Public Safety and Sandoval County Public Safety NM State Police, Regional Public Safety Agencies, Regional Transit Agencies, Regional Traffic Agencies and NMDOT NM State Police and City of Albuquerque City of Albuquerque, Regional Public Safety Agencies, Regional Transit Agencies, Regional Traffic Agencies and NMDOT NM State Police, Regional Public Safety Agencies and NMDOT City of Albuquerque, City of Rio Rancho, Bernalillo County, Kirtland AFB, NM National Guard, NM State Police, NMDOT, Sandia Labs, Sandoval County and UNM City of Albuquerque, Independent School Districts, Local Transit, Rio Metro Regional Transit District, NMDOT, MRCOG and UNM City of Rio Rancho, City of Albuquerque, Bernalillo County, Sandoval County, Municipalities, NM National Guard and Tribal Governments City of Rio Rancho, City of Albuquerque, Independent School Districts, Local Transit, Rio Metro Regional Transit District, NMDOT and MRCOG Municipalities, City of Rio Rancho, Bernalillo County, NM National Guard, NM State Police, Sandoval County and Tribal Governments Municipalities, Independent School Districts, Local Transit, Rio Metro Regional Transit District, NMDOT and MRCOG Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NM National Guard, Sandoval County and Tribal Governments Bernalillo County, City of Albuquerque, City of Rio Rancho, Independent School Districts, Local Transit, Rio Metro Regional Transit District, NMDOT and MRCOG Provide signal preemption Provide signal preemption Provide Amber Alert information Coordinate Amber Alert information Provide Amber Alert information Coordinating emergency plans for disasters Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry 128

122 Priority Service Potential Parties to Agreement Purpose Roadway Service Patrols Traffic Incident Management Sandoval County, City of Rio Rancho, Bernalillo County, Municipalities, NM National Guard, NM State Police and Tribal Governments Sandoval County, City of Rio Rancho, Independent School Districts, Local Transit, MidRTD, NMDOT and MRCOG UNM, City of Albuquerque, Bernalillo County, Kirtland AFB, Municipalities, NM State Police and Sandia Labs UNM, City of Albuquerque, Independent School Districts, Rio Metro Regional Transit District, NMDOT, MRCOG and UNM (Transit) NMDOT, City of Albuquerque, Bernalillo County and NM State Police City of Albuquerque, City of Rio Rancho, Bernalillo County, Kirtland AFB, NM State Police, NMDOT, Sandia Labs, Sandoval County and UNM City of Rio Rancho, City of Albuquerque, Bernalillo County, Municipalities, Sandoval County and Tribal Governments Municipalities, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County and Tribal Governments Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NM State Police, Sandoval County and Tribal Governments NMDOT, City of Rio Rancho, Bernalillo County, Kirtland AFB, Municipalities, RCB, Sandia Labs, Sandoval County and Tribal Governments NMDOT, City of Albuquerque and NM State Police Special Events Coordinators, UNM, City of Albuquerque, City of Rio Rancho, Bernalillo County, NMDOT and municipalities. City of Albuquerque, Bernalillo County, Kirtland AFB, NM State Police, Sandia Labs and UNM. City of Rio Rancho, Municipalities, Bernalillo County, Sandoval County and Tribal Governments Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry Coordinating emergency plans for disasters, evacuations and reentry Coordinate transit emergency plans for evacuations and reentry Providing an incident report Sharing incident data and emergency resources Sharing incident data and emergency resources Sharing incident data and emergency resources Sharing incident data and emergency resources Sharing incident data and emergency resources Sharing incident data, emergency resources and video images Sharing event plans Sharing incident data and coordinating maintenance and construction resources Sharing incident data and coordinating maintenance and construction resources 129

123 Priority Service Potential Parties to Agreement Purpose Traffic Management Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NM State Police and Tribal Governments NMDOT, Bernalillo County, City of Albuquerque, Municipalities, NM State Police, Sandoval County and Tribal Governments Sandoval County and Municipalities Private Rail Operations, City of Albuquerque, City of Rio Rancho, Bernalillo County, Municipalities, Sandoval County and Tribal Governments Private Rail Operations, City of Albuquerque, City of Rio Rancho, Bernalillo County, Municipalities, NMDOT and Tribal Governments City of Albuquerque, City of Rio Rancho, Bernalillo County, Municipalities, NMDOT and Private Sector Traveler Information Services NMDOT and the Media NMDOT, City of Albuquerque, City of Rio Rancho, Local Transit and MidRTD NMDOT, NM State Police and Private Ambulance Providers NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County and Municipalities Financial Institutions, City of Albuquerque, NMDOT, Albuquerque International Sunport and Mesa del Sol City of Albuquerque, NMDOT and Bernalillo County NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, Municipalities, and Private Sector Traveler Information Services NMDOT, MRCOG, City of Albuquerque, City of Rio Rancho, Local Transit Agencies and MidRTD Albuquerque International Sunport, NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Municipalities, and Private Sector Traveler Information Services Sharing incident data and coordinating maintenance and construction resources Sharing incident data and coordinating maintenance and construction resources Provide emergency dispatches Sharing incident data and providing incident response Obtain HRI advisories Sharing road network conditions Sharing traveler information Sharing road network conditions Sharing road network conditions Traffic information and control coordination Payment reconciliation for parking Sharing parking lot information Sharing parking lot information Sharing parking lot information Sharing parking lot information 130

124 Priority Service Potential Parties to Agreement Purpose Mesa del Sol, NMDOT, City of Albuquerque, Bernalillo County, MidRTD and Private Sector Traveler Information Services NMDOT and NM State Police Sharing parking lot information Sharing road network conditions, road closure information emergency traffic control information Transit Management Traveler Information NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County and Municipalities NMDOT and Private Sector Traveler Information Services NMDOT, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, Bernalillo County, Tribal Governments, Local Transit Agencies NMDOT, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, Bernalillo County, Sandoval County, Tribal Governments, Local Transit Agencies NMDOT, Private Sector Traveler Information Services, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, Local Transit Agencies NMDOT, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, Local Transit Agencies, UNM, and Financial Institutions NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, Tribal Governments, UNM, NM State Police NMDOT, City of Albuquerque, City of Rio Rancho, Rio Metro Regional Transit District, Local Transit Agencies, UNM City of Albuquerque, City of Rio Rancho City of Albuquerque Transit Department, City of Albuquerque Department of Municipal Development NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, and Sandoval County City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, other NMDOT Districts and municipalities Sharing road network conditions and emergency traffic control information Sharing roadway information system status for road closures Sharing road network conditions Sharing roadway maintenance status and work zone information Sharing transit schedule and fare information Completing electronic payment transactions Sharing transit emergency data Transit service coordination Providing signal priority Providing signal priority Sharing traveler information with the media Providing maintenance and construction and work zone information to NMDOT 131

125 Priority Service Potential Parties to Agreement Purpose Maintenance and Construction Management City of Albuquerque, City of Rio Rancho, Bernalillo County and municipalities City of Albuquerque, City of Rio Rancho, Local Transit, Rio Metro Regional Transit District and UNM City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, municipalities and private section traveler information services City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, Tribal Governments, Municipalities, NMDOT and other NMDOT Districts. Sandoval County and the City of Rio Rancho Sandoval County and the City of Rio Rancho City of Rio Rancho and Sandoval County City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, Tribal Governments, Municipalities, NMDOT and Public Utilities. City of Albuquerque, Local Transit, MidRTD, NMDOT, MRCOG and UNM. City of Albuquerque, Kirtland AFB, NM State Police, NMDOT, Sandia Labs and UNM. City of Rio Rancho, City of Albuquerque, Local Transit, MidRTD, NMDOT and MRCOG City of Rio Rancho, Bernalillo County, Sandoval County and Tribal Governments Municipalities, Local Transit, MidRTD, NMDOT and MRCOG Municipalities, City of Rio Rancho, Municipalities, Bernalillo County, Sandoval County and Tribal Governments Bernalillo County, Local Transit, Rio Metro Regional Transit District and NMDOT Bernalillo County, City of Albuquerque, City of Rio Rancho, Sandoval County and Tribal Governments Providing road network conditions to NMDOT Providing transit fare and schedule information to NMDOT ISP Coordination Share roadway maintenance status Provide field device status Provide maintenance resources Provide field equipment status and road network conditions Coordinate maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans 132

126 Priority Service Potential Parties to Agreement Purpose Weather Distribution Sandoval County, City of Rio Rancho, Local Transit, Rio Metro Regional Transit District and NMDOT Sandoval County, Bernalillo County, City of Rio Rancho and Tribal Governments NMDOT and Private Sector Traveler Information Services NMDOT, Bernalillo County, City of Albuquerque, City of Rio Rancho, Kirtland AFB, Municipalities, NM State Police, Sandoval County and Tribal Governments NMDOT, City of Albuquerque, City of Rio Rancho, Local Transit, Rio Metro Regional Transit District and MRCOG NOAA, Private Weather Information Providers, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County and NMDOT City of Albuquerque, City of Rio Rancho, Bernalillo County, NMDOT, Kirtland AFB, NM State Police, Sandia Labs, UNM, Local Transit, Rio Metro Regional Transit District, MRCOG and Private Traveler Information Systems City of Rio Rancho, City of Albuquerque, Bernalillo County, Sandoval County, Municipalities, Tribal Governments, Local Transit, Rio Metro Regional Transit District, NMDOT, MRCOG and Private Traveler Information Systems Bernalillo County, City of Albuquerque, City of Rio Rancho, Municipalities, NMDOT, Tribal Governments, Local Transit, MidRTD, MRCOG and Private Traveler Information Systems Sandoval County, City of Rio Rancho, Municipalities, NMDOT, Tribal Governments, Local Transit, Rio Metro Regional Transit District, MRCOG and Private Traveler Information Systems NMDOT, City of Albuquerque, City of Rio Rancho, Bernalillo County, Sandoval County, NM State Police, RCB, Local Transit, Rio Metro Regional Transit District, MRCOG and Private Traveler Information Systems Provide maintenance and construction work plans Provide maintenance and construction work plans Provide maintenance and construction work plans and current asset restrictions Provide maintenance and construction work plans Provide maintenance and construction work plans Sharing weather information Sharing road weather information Sharing road weather information Sharing road weather information Sharing road weather information Sharing road weather information 133

127 134

128 12. Using the AMPA Regional ITS Architecture The AMPA Regional ITS Architecture has been created, in part, to be used as a key reference in the transportation planning process. This will ensure all proposed ITS projects are consistent with the regional ITS architecture and additional integration opportunities are considered, leading to more efficient implementations. Planning processes are used to identify projects whose implementation will respond to regional needs. These projects are placed in programming documents such as a Transportation Improvement Program (TIP) in order to secure funding for the projects. A Congestion Management Process (CMP) is used to identify congestion mitigation strategies and prioritize projects. The coordinated development of these documents is one of the responsibilities outlined in 23 CFR, Part 450 for MPO s and the MRCOG. It should be noted that the ITS architecture can play a critical support role in this process, providing the level of stakeholder input that facilitates the integration of ITS into the larger regional transportation program. Once funded, the projects are implemented. The Regional ITS Architecture supports all three of these major steps planning, programming, and implementation An important part of developing an ITS Architecture is identifying the best approach to using it in the aforementioned MPO s transportation planning and programming process. An ITS Architecture provides guidance for planning ITS projects within a region. It also provides information that can be used in the initial stages of project definition and development. This section presents the approach for integrating the AMPA Regional ITS Architecture in MRCOG s transportation planning/programming process and leveraging the ITS Architecture for project definition. The approach facilitates and provides a mechanism for the projects identified in this document or in the Metropolitan Transportation Plan (MTP) and Transportation Improvement Program (TIP) to be planned and deployed in an orderly and integrated fashion. The primary objective of the ITS Architecture is integration. The integration of transportation systems to share information and coordinate activities provides significant benefits over the operation of systems in a stovepiped fashion. The AMPA Regional ITS Architecture illustrates the information to be exchanged between transportation systems to meet the transportation needs of the stakeholders in the region (addressed in Section 6.1). The ITS Architecture links the needs to ITS Services and then to the ITS projects that address them. The ITS Architecture was developed with these objectives in mind through the definition of ITS Services or Service Packages. By defining the ITS Architecture with services that address the needs, projects can be defined through the planning process using the architecture that addresses these needs through deployment Using the AMPA Regional ITS Architecture in the Planning Process One of the most important outcomes of the AMPA Regional ITS Architecture is that it will be used to plan and deploy ITS across the region. To do this, the ITS Architecture must be integrated into the regional planning process. As a result of integrating the ITS Architecture into 135

129 the planning process, the architecture will link the needs of the regions with the ITS deployments in the field. MRCOG is the designated metropolitan planning organization in the AMPA and is responsible for facilitating the prioritization and programming for all projects in the AMPA through the development of the 20-year Metropolitan Transportation Plan (MTP), and its near-term Transportation Improvement Program (TIP), the latter being a subset of the Statewide Transportation Improvement Program (STIP). The member agencies of the AMPA, represented by the Metropolitan Transportation Board (MTB) with its contributing committee structure, has designed the process consistent with federal rules to ensure that all transportation projects included on the federal transportation system are implemented consistent with the region s mobility goals, and are consistent with all federal, state, and local rules as applicable to providing a safe and efficient transportation system. All local municipalities and counties in the AMPA including the NMDOT are members of the MRCOG. In order to facilitate the connection between the Regional ITS Architecture and the local transportation program (TIP and MTP) the MTB has adopted the AMPA Regional ITS Architecture as part of the official set of planning documents for the region. Consideration of the architecture in the TIP program development process has been implemented at MRCOG. The process has been tailored to acknowledge the inclusion of ITS, specifically on a project by project basis; this has particular relevance in three primary areas to ensure consistency with the Regional ITS Architecture, support of Systems Engineering Certifications, and identification of specific ITS strategies included in the Congestion Management Process and its Project Prioritization Process which ranks the projects and favors those with ITS strategies that improve the region s mobility goals. The goal of the planning process is to make quality, informed decisions pertaining to the investment of public funds for regional transportation systems and services. Using the regional ITS architecture to support these planning activities is an important step in the mainstreaming of ITS into the traditional decision-making of planners and other transportation professionals. Once an architecture is complete, it can feed detailed ITS-specific information back into the planning process. Figure 13 below shows some of the key steps in MRCOG s transportation planning process and the ITS Architecture interrelation. These steps will be elaborated on in following sections. The process is driven by a regional vision and set of goals. These drive transportation improvement strategies that are a mix of capital improvements and operational improvements. The planning organizations evaluate and prioritize the various strategies, and the resulting output is a document called the Metropolitan Transportation Plan (MTP). This plan is the key output of long range planning. This document contains the following: MTP goals and objectives. The plan contains four goal areas and a set of objectives defined for each goal. Evaluation of growth and development scenarios for the region 136

130 Trend and Preferred alternatives (based on above evaluation) with a set of financially-constrained planned projects and efforts in the following general areas: o o o o o o o Bicycle/Pedestrian System Transit Roadways Intelligent Transportation Systems (ITS)/Transportation Systems Management Safety Non Capital Actions Intermodal/Multimodal Summary Discussion of Regional Challenges, Needs, and Strategies for the region and some of the transportation initiatives that might meet these challenges The Transportation Improvement Program (TIP) The Metropolitan Transportation Plan includes the key output of the Programming function the TIP. Once a project is programmed then project development can begin. All of these steps occur with a variety of critical factors and inputs as shown in the figure. As shown in the figure, a regional ITS architecture may support each step in this process. 137

131 Long Range Planning Regional Vision & Goals Regional ITS Architecture Alternate Improvement Strategies Operational Capital Evaluation & Prioritization of Strategies Development of Long-Range Transportation Plan Development of Transportation Improvement Program Project Development System Operation Budgets Figure 13: ITS Architecture and the Transportation Planning Process Critical Factors & Inputs Title VI Public Involvement Environmental Issues Economic Development Feedback The MTP is the expression of AMPA s long-range approach to planning and implementing the multimodal transportation system. It is the policy forum for balancing transportation investments among modes, geographic areas, and institutions. How can a Regional ITS Architecture support the transportation planning process? In the following basic ways that will be expanded upon below: The services described in the regional ITS Architecture can provide the basis for operational strategies that can be used to improve the transportation system to meet the region s vision and goals. The regional ITS architecture can be used to support evaluation and prioritization of strategies in two ways. The first is through the definition in the architecture of archiving and data collection systems that support collecting the data needed for evaluation. The second is through the detailed definition of ITS projects and their sequencing that can be used to support prioritization efforts. The definition of an integrated transportation system described by the regional ITS architecture can support the ITS elements of the MTP. 138

132 The process of developing and maintaining a regional ITS architecture can help to enhance the linkage between operations and planning through closer involvement of a wider array of stakeholders from both of these areas of transportation. Additionally, the Statewide ITS Architecture is formally adopted by MRCOG. This serves to emphasize the continuity of the Regional ITS Architecture to the regions outside of the AMPA and also encourages rigor in the architecture maintenance process (described in Section 13). The discussion below focuses on supporting the MPO transportation planning process, but the architecture can also be used to support the other planning processes used by agencies in the region (e.g. public safety agencies). As shown in Figure 14, agencies that do not use federal funds (or operate through the MPO planning process) will still have some form of long range plan and capital plan whose development can be supported by the regional ITS architecture. Other Agency Planning Process MPO Planning Process ITS Architecture ITS Related Projects ITS Related Projects goals, objectives, policies Strategic / Long Range Plan Long Range Metropolitan Transportation Plan Capital Plan / Budget Transportation Improvement Program (TIP) Funded ITS Related Projects Figure 14: Supporting the Transportation Planning Processes The challenge for achieving integration across planned ITS projects in the regions is to know how they fit together and interact or depend on each other. The regional ITS architecture can be leveraged to bridge the MPO processes to other agencies planning processes that do not use federal funding. If all the processes are using the same reference point, the regional ITS architecture, then project integration can start in the planning phase Operational Strategies Identified for the AMPA The AMPA planning process in the 2040 Metropolitan Transportation Plan begins with a set of goals and objectives which are given as: Mobility/Moving People 139

133 o o o Maintain Infrastructure Manage Congestion and Enhance Operations Expand Multi-Modal Options Economic Vitality o o o o Support Efficient Freight Movement Promote Development in Activity Centers and Key Corridors Enhance the Flow of Goods and Services Ensure Affordable Housing and Transportation Options Environmental Resiliency o Improve Air Quality Active Places o Improve Access to Employment Sites, Services, and Recreational Opportunities o Provide Safe and Healthy Travel Options These goals and their objectives are integrated into the project planning process, including the Congestion Management Process (CMP), and are carried through the project-ranking and prioritization activities included in the MTP and TIP development process shown in Figure 13, the strategies are primarily capital improvements or operational improvements. One can see how the Regional ITS Architecture can provide an array of potential operational improvements through the services that are defined in it. Strategies that have traditional transportation projects as their primary solution, may add ITS elements or services as a part of the overall strategy solution. For example, to reduce congestion, a corridor is planned for widening. This project could also include incorporation of ITS elements and services to better manage the upgraded corridor. This was identified as ITS Mainstreaming in the ITS Implementation Plan and is the most widely implemented form of ITS deployment currently used in the AMPA. The use of the architecture to support the definition of implementation strategies is assisted by the definition of needs and their mapping to ITS services given in Section Strategy Evaluation and Prioritization Transportation planners use a variety of tools to evaluate and prioritize the various strategies for transportation improvement. Collection of data about the transportation system is a key input to support the evaluation. Several ITS services, described in the regional ITS architecture can support this data collection, providing the planning organization the ability to measure nonrecurring congestion, travel times and travel time reliability, and other aspects of system performance and service reliability across all modes. 140

134 The AMPA Regional ITS Architecture provides a guide for the archiving of transportation data including the collection of data from various ITS operational systems. These archiving capabilities revolve around regional examples of the National ITS Architecture entity, Archived Data Management Subsystem (such as the MRCOG Data Warehouse). Furthermore the AMPA Regional ITS Architecture has examples of ITS services such as ITS Data Mart (collection of historical data from a single source) and ITS Data Warehouse (collection of historical data from multiple aspects of transportation). These examples of data archiving services describe connections and information that can be useful to planners in performing their evaluation and prioritization efforts. While the automation of data collection for archiving is usually a future activity (or project), the discussions that occur during the development of the regional ITS architecture often present additional opportunities for data sharing that can occur immediately even before projects for the automation of data sharing are implemented. This sharing of data between operations and planning, as well as the coordination that occurs in the development of the Regional ITS Architecture are examples of linkages between Planning and Operations. The concept of linkage between these two disciplines figures prominently in the FHWA Planning for Operations effort (see A complete treatment of these opportunities is included in the FHWA publication: Opportunities for Linking Planning and Operations. This publication can be found at Regional ITS Architecture outputs, specifically the project sequencing output may also be useful to planning staff as an aid to evaluation and prioritization of strategies and most importantly, the programming of the TIP. The architecture provides a short-term and long-term, multi-modal view of the ITS systems in the region. It provides the details of the transportation services and functions that can be provided by the stakeholders via ITS projects. The Regional ITS Architecture also illustrates the interfaces necessary between transportation systems to meet the transportation needs of the state. Finally it translates these details to the definition of a set of projects to be implemented. These projects are grouped by timeframe (e.g. short term, medium term, long term). Key to its usefulness for the strategy evaluation and prioritization (as well as for the MTP as discussed below) is that this list of projects goes well beyond the short term projects that get included in the TIP and STIP (see Section 12.2 for a discussion of how the architecture can be used in developing this program element.) The project sequencing contains information for each project that may be useful to the evaluation or prioritization of the projects including: Stakeholders Cost Mapping to ITS Services Note that this project sequencing is not a replacement for prioritization that is the function of the TIP, but rather, an input to the process by which projects are prioritized. In some cases, prioritization may already have occurred and be reflected in the project sequencing outputs. 141

135 The AMPA Regional ITS Architecture provides a guide for how ITS projects can be deployed to satisfy the goals and objectives defined as part of the planning process. The architecture provides the details on how ITS can be deployed to meet and satisfy the strategies and transportation services identified for the region. These details may include the interfaces, the operational concepts and agreements necessary to implement the strategies and transportation services. With these details, ITS projects can be more clearly defined, funded, and implemented to satisfy the regional goals Metropolitan Transportation Plan One of the primary motives for ITS, and the regional ITS architecture, is the need for more effective management of existing transportation infrastructure. Many regions can no longer rely on adding capacity to keep pace with increasing demand. Instead, they are relying on more effective, integrated management of the existing infrastructure. Recognizing this need, many regions are beginning to include a section of the plan on Management and Operations, which can be defined as an integrated approach to optimize the performance of existing infrastructure through the implementation of multimodal, intermodal, and often cross-jurisdictional systems, services, and projects. The recently passed law, FAST Act, emphasizes the need to include Management and Operations in each region s Long Range Plan. According to the legislation (Section 6001 (i)) metropolitan planning areas must include operational and management strategies to improve the performance of existing transportation facilities to relieve vehicular congestion and maximize the safety and mobility of people and goods. The statewide ITS architecture can provide the technical underpinning to this portion of the MTP. One of the primary purposes of the Regional ITS Architecture is to define how an integrated transportation system (of ITS elements) might evolve in a region. To do this, the architecture describes elements (e.g. various ITS assets) that are interconnected to provide operations and management of the transportation system. The architecture development and maintenance process provides an accessible way for transportation planners to become more focused on integrated management and operations. Operations practitioners have a vision for how this integrated transportation system might evolve, and express this via the details of the architecture. In the development of the AMPA MTP, some of the outputs of the regional ITS architecture can be of use in the plan update. The outputs and some indication of their use are: ITS Projects from the Regional ITS Architecture can provide an input to the Development of Preferred Alternatives and Future Challenges section (as well as the TIP, which is incorporated into the MTP). Customized Service packages from the AMPA Regional ITS Architecture offer service-oriented slices of the architecture that facilitate project definition with an understanding of integration necessary to deliver specific services. The service packages provide planners with insight into the ITS elements to include in a project, which will make the project as comprehensive as possible. They also provide sample Implementation Strategies that include ITS to address long range objectives. 142

136 Issues/Challenges One issue to address in using the architecture to support planning is coordination of ITS project planning between the federally funded projects and the non-federally funded projects. The nonfederally funded projects may not be part of the MTP (and TIP). The ITS Architecture contains systems and projects that are both federally and non-federally funded. The ITS Architecture provides a common reference point for all stakeholders to gain insight into the integration of the systems in the region to create an understanding of the regional systems and ITS Services being pursued Using the AMPA Regional ITS Architecture for Programming Regional and statewide programming and agency capital planning (a.k.a. budgeting) involve identifying and prioritizing ITS projects, resulting in funded projects. These processes are shown in Figure 15. Figure 15: ITS Project Programming/Budgeting/Capital Planning Using the regional ITS architecture to define an ITS project links the needs of the region identified in the architecture with the ITS deployed in the field. In the region, ITS projects are deployed by many organizations including NMDOT, transit agencies, and many local agencies and authorities. If projects of the various organizations are defined from the same reference point, the AMPA Regional ITS Architecture, then coordination begins in the initial planning and funding phase. ITS projects in the region may be funded by a variety of sources. ITS projects that are funded with federal funds are programmed through the MRCOG planning process with input from member transportation agencies in the region. All organizations in a region, whether they use federal funds to deploy ITS or not, perform short term planning via their capital planning (i.e. budgeting) process. 143

137 Architecture Use in the MRCOG Transportation Programming Process The Transportation Improvement Program (TIP) is a phased, multiyear, intermodal program of transportation projects that is consistent with the MTP. Like the MTP, the TIP is the financiallyconstrained mechanism that assigns federal funding to a prioritized list of specific projects to be constructed over a several-year period (six years for the AMPA TIP) after the programs approval. It can be considered the project implementation mechanism of the MTP. Integrating the ITS architecture and periodic maintenance activity into the ongoing planning and programming activities provides the best opportunity to capture and monitor ITS project development among member and nonmember entities. It is crucial that all those involved in the project planning and development stages (planners, managers, engineers, etc.) coordinate with those involved in latter final design/project implementation stages so that ITS Elements are consistent for the project, cradle to grave. This coordination will also ensure that any changes in project scope occurring during project development may be reflected back to the MPO and Architecture Maintenance activities accordingly. Figure 16 below shows the TIP development and process flow chart for the AMPA. Areas where the ITS Subcommittee and ITS project review is included are identified in red. The Architecture Maintenance activity is closely tied to this process, and will be explained the following chapter. Figure 16: MRCOG TIP Development Flow Char (with ITS Subcommittee Participation Noted) 144

138 Resources for Use in ITS Planning and Programming Primarily through the ITS Subcommittee, resources have been developed or available in other processes to assist agencies in the planning and programming of ITS within the AMPA, summarized below. ITS System and Priority Corridors Map The ITS Subcommittee maintains the ITS System/Priority Corridors Map (Figure 18). This map shows the broad set of roadways within the AMPA identified for ITS deployments, with a subset of prioritized corridors and is intended for use in the transportation and planning process. The map has been distributed to all member agencies with development review and roadway planning and project development responsibilities and is part of the MRCOG system maps in the MTP. It is integrated into the CMP and the Project Prioritization Process (PPP), and is used specifically in project planning and programming in support of identifying project-level ITS Strategies and deployment gaps. Proposed projects in the TIP and MTP are given priority through the programming process if located along one of these corridors. To compliment the map, more detailed resources are available through the MRCOG s ITS Subcommittee and the ITS Deployment data in GIS. 145

139 Figure 17: ITS Corridors/Priority Corridors Map 146

140 ITS Infrastructure in GIS AMPA Regional ITS Architecture As part of the ITS Architecture Maintenance activity, the ITS Subcommittee maintains a Geodatabase of ITS Infrastructure based on existing/near-term project development conducted and reported by each of the stakeholders. This is product is available online to member agencies that establishes a visual and spatial query and summary-enabled representation of ITS deployment within the AMPA, and serves a crucial role in the planning processes at MRCOG (Figure 18). The GIS allows for the ITS deployment data to be integrated in the GIS with other data sources, such as crash rates, congested roadways, planned projects from the TIP and MTP, and it plays a crucial role in the development of the TIP program and the aforementioned PPP project evaluation tool. Figure 18: Mapping of ITS Infrastructure Transportation Project Planning and Agency Development Review The planning process for transportation projects within local jurisdictions typically follows a sequence whereby project proposals are carried through a series of review stages by department to ensure that all project requirements are identified and/or met prior to final approval. This review presents an excellent opportunity for staff to identify ITS project opportunities, particularly on non-its roadway projects or projects within the roadway right of way that may not be included in other ITS project review. This practice is referred to as ITS project mainstreaming, and has expanded the scope of incremental ITS project development tremendously. Project examples include typical roadway maintenance activities, widening, and projects within or in proximity of the roadway right of way such that if identified early enough in the process can include ITS elements such as the inclusion of fiber/telemetry, thereby presenting a cost saving opportunity. The key is to identify these opportunities at critical stages of the development review process and for staff to have correct ITS reference and planning 147

141 materials, such as the ITS Corridors Map mentioned above. Since this effort has been initiated, numerous opportunities for including ITS elements on non-its projects have been identified, resulting in additional ITS deployment done in an extremely cost-effective manner. Congestion Management Process ITS strategies are identified in the Congestion Management Process Toolbox as one approach to mitigate congestion on the transportation system; the CMP Project Prioritization Process matrix identifies additional points when a project includes ITS elements. Along with the ITS Subcommittee, the Congestion Management Process group is part of the MRCOG monthly meeting structure. Coordination of this group and the ITS Subcommittee is maximized through shared representation at both committees, thereby resulting in direct communication and project level cooperation between the groups. In addition, the ITS Corridor Profiles initiated in FY2011 focus on top-ranked CMP corridors for use by the CMP Committee in their congestion analysis and corridor mitigation strategy evaluation. Those products are available on the MRCOG ITS webpage Architecture Use in Organization Capital Planning All agencies including MRCOG, NMDOT, transit agencies, local municipalities, etc. use a budgeting process to allocate funds to projects. The AMPA Regional ITS Architecture includes the existing and planned elements of all stakeholders and how they are or will be interfaced with other ITS elements in the state. Therefore, all organizations can use the architecture to define ITS projects, as defined below, and feed them into their budgeting process. Many ITS improvements are implemented as part of larger capital improvement projects, aka the CIP. As traditional capital projects are defined and programmed, it is important to identify the associated opportunities for efficient ITS implementation. The AMPA Regional ITS Architecture is a record of the ITS implementation planned by each agency that can be used to identify these opportunities. Most agencies in the AMPA have developed policies to review each capital project to determine if ITS measures should be included before the project moves forward. One important consideration with these locally-funded ITS projects is the consideration of the Systems Engineering Process (discussed in the next section) that is necessary in order to integrate with the larger federally-funded ITS system. Without System Engineering, the project s ability to integrate with other deployments is at risk Architecture Use to Identify and Define Projects A regional ITS architecture includes a sequence of projects. Projects from the architecture should feed into the programming and/or capital planning processes. ITS projects are taken directly from the plan and submitted for funding (with Federal or other funds.) As the projects defined in a regional ITS architecture are sequenced and have defined characteristics, organizations can use the architecture to define ITS projects to be submitted for funding from any source. 148

142 To obtain funding, a project sponsor must define a proposed ITS project. The information contained in the AMPA Regional ITS Architecture can be used to define projects with more detail in order to better scope them and establish project budget requirements. Some potential ways a regional ITS architecture can be used to define an ITS project include: Review the list of stakeholders to identify those that should be involved with the project and those that are or may be impacted. Use the stakeholder roles and responsibilities defined in the operational concept to clearly define the roles and responsibilities of the stakeholders involved in the project. Review the relevant service(s) (i.e. service package(s)) to identify elements potentially directly or indirectly associated with the project and recognizing potential partners to share development costs, material and/or labor, facilities, etc. Use the defined interfaces between ITS elements (in the customized service packages) to identify current and future integration opportunities. Utilize the sequence of projects to gain insight into the timelines and dependencies of a project with others including identifying opportunities to coordinate with capital projects. Apply the project description of the project sequencing including costs, technical feasibility, potential institutional issues and readiness to clearly define the project. Gain a thorough understanding of the elements and interfaces included in a project to more accurately estimate project budgets Challenges One critical issue is the coordination of Federally and non-federally funded projects in the state. In many regions, non-federally funded projects are generally not included in the TIP. However, the MRCOG has a very robust project development process which, for the most part, captures all of the locally-funded transportation projects. The main consideration here is that these locally-funded projects are often developed in-house by each agency and without the collaborative process administered at MRCOG, and therefore, may not be identified early on by the ITS Subcommittee. It is imperative that the stakeholders do proper diligence with their CIP efforts to notify the ITS Subcommittee of the project development activity. The Statewide ITS Architecture contains all ITS elements and projects within the scope of the architecture irrespective of funding source. As the AMPA Regional ITS Architecture enables understanding and coordination of all ITS related projects for all stakeholders in the region, stakeholders can benefit from using an ITS Architecture to plan, program, and deploy all ITS projects not just those that are Federal funded and therefore, must meet the Rule/Policy requirements. 149

143 12.3. Using the AMPA Regional ITS Architecture in Project Definition Projects that emerge from the planning process can benefit from the use of the AMPA Regional ITS Architecture in their definition and development. Project implementation should follow a systems engineering process. The ITS Architecture is most effective in the early phases of systems engineering processes. Figure 19 shows a typical project implementation process for deploying ITS projects. Transportation Planning Process Funded ITS Related Project Project Implementation Process Concept Operations & of Operations Maintenance High Level Requirements System Verification Detailed Requirements High Level Subsystem Design Verification Detailed Integration & Design Test Implementation Figure 19: Project Implementation Process The project implementation process shown in Figure 19 is a Systems Engineering process. It is a process that can be used to systematically deploy ITS while reducing the risks associated with 150

144 deployments. The Systems Engineering process is more than just steps in systems design and implementation; it is a life-cycle process. The process recognizes that many projects are deployed incrementally and expand over time. US DOT Rule 940 requires that the systems engineering process be used for ITS projects that are funded with federal funds. Applying the System Engineering process to ITS project development is a key requirement that must be addressed by stakeholders using federal funds. FHWA Rule 940/FTA Policy contains a set of requirements that apply to ITS projects. The Rule indicates that a Project Systems Engineering Analysis (PSEA) be created. The requirements for the PSEA, summarized below, state: a) All ITS projects funded with highway trust funds shall be based on a systems engineering analysis. b) The analysis should be on a scale commensurate with the project scope. c) The systems engineering analysis shall include, at a minimum: 1. Portions of the Regional ITS Architecture Being Implemented 2. Participating Agencies Roles and Responsibilities 3. Requirements Definitions 4. Analysis of Alternative System Configuration and Technology Options 5. Procurement Options 6. Applicable ITS Standards and Testing Procedures 7. Procedures and Resources Necessary for Operations and Management of the System. To support development of the PSEA, NMDOT has created an ITS Project Checklist ( that provides a relatively easy and straight forward way to meet these requirements. The form, at the link above is also accompanied by an online training presentation specifically designed for planners, project development engineers, and project managers (se reference above). The checklist provides for project name, description, and contact information, and leads the respondent through a series of specific project related questions where detailed project information, procurement methods, and phasing is identified. Other queries associate the project to the regional Architecture and market packages, as well as the stages included in the Systems Engineering V Diagram. The form allows for the attachment of all applicable service packages diagrams which can be obtained directly from the AMPA website or in later years from the appendices included in the Regional Architecture Addendum explained later in this document. The following are some key references that stakeholders can access to assist in using this process: General Resources FHWA Systems Engineering Website (ops.fhwa.dot.gov/int_its_deployment/sys_eng.htm) 151

145 Training Publications AMPA Regional ITS Architecture International Council on Systems Engineering ( Systems Engineering: An Introduction for Planners, Project Development Engineers and Project Managers Systems Engineering Training on NMDOT website: 415_NTPCommentsv2_1.ppt Advanced Systems Engineering for Advanced Transportation Projects (CITE - Building Quality Intelligent Transportation Systems through Systems Engineering (FHWA-OP ): Systems Engineering Guidebook for ITS (FHWA California Division/Caltrans): Systems Engineering for Intelligent Transportation Systems, An Introduction for Transportation Professionals: There are similarities between the systems engineering process defined in Figure 19 and the project development process followed by agencies in the region. A typical agency project development process is as follows: Project Selection Authorization to Proceed Project Definition o o o Purpose and Need Project Scoping Conceptual Design Project Design o o o Preliminary Plan Development Semi-Final Plan Development Final Plan Development Construction o Testing Operation and Maintenance 152

146 Table 14 shows the relationship the NMDOT project development process has to the FHWA system engineering process. Table 14: Regional Project Development Process Relation to FHWA System Engineering Process NMDOT Project Development Process Relation Systems Engineering Process Project Definition Purpose and Need Project Scoping Conceptual Design Project Design Preliminary Plan Development Semi-Final Plan Development Final Plan Development Construction Testing => => => => Concept of Operations High Level Requirements Detailed Requirements High Level Design Detailed Design Implementation Integration & Test Subsystem Verification System Verification Operation and Maintenance => Operations & Maintenance As shown by the highlights in Figure 19 and in Tables 14 and 15, the AMPA Regional ITS Architecture can be used to support development of the concept of operations, requirements and high level design in the systems engineering process. In deployment of an ITS related project, the ITS Architecture should be used as the starting point for developing a project concept of operations (not to be confused with an Architecture s Operational Concepts that define the roles and responsibilities of the Architecture s stakeholders). The concept of operations shows at a high level how the systems involved in a project operate in conjunction with the other systems of the region. According to the NHI course Introduction to Systems Engineering for Advanced Transportation, a Concept of Operations includes the following information: Identification of stakeholders, Development of a vision for the project, Description of where the system(s) will be used, Description of organizational procedures or practices appropriate to the system(s), definition of critical performance parameters associated with the systems(s), Description of the utilization environment (conditions under which various parts of the system(s) will be used), 153

147 Definition of performance measures used to evaluate the effectiveness of the system(s), Considerations of life cycle expectations, and Conditions under which the system(s) must operate (e.g. environmental conditions). The customized service package diagrams tailored by the regional stakeholders can also assist in definition of requirements for ITS systems involved in a specific project. The ITS Architecture contains high level functional requirements for all ITS elements in the region. These high level requirements can be the starting point for developing more detailed requirements. The ITS Architecture can support high level system design. The ITS architecture can be used by system designers to identify the ITS standards that are applicable for the interfaces included in the architecture. Additional resources identified above, i.e. the ITS Corridors and the existing ITS Infrastructure map should be utilized to show the overall integration among adjacent agencies of the intended ITS Service being pursued. While the above discussion relates the architecture to the general system engineering process, Rule 940 does have a specific set of system engineering analysis requirements that apply to all ITS projects that use funds from the Highway Trust Fund. The required system engineering analysis steps are: Identification of portions of the regional ITS architecture being implemented (or if a regional ITS architecture does not exist, the applicable portions of the National ITS Architecture) in this case the statewide ITS architecture; Identification of participating agencies roles and responsibilities; Requirements definitions; Analysis of alternative system configurations and technology options to meet requirements; Procurement options; Identification of applicable ITS standards and testing procedures; and Procedures and resources necessary for operations and management of the system. The AMPA Regional ITS Architecture provides inputs to a number of these steps as shown in Table 15. Table 15: Systems Engineering Requirements supported by AMPA Regional ITS Architecture Systems Engineering Requirements Identification of portions of the regional ITS architecture being implemented Identification of participating agencies roles and responsibilities (this relates to the Concept of Operations described earlier. AMPA Regional ITS Architecture Output Mapping project to the elements and interfaces of the regional ITS architecture Use Operational Concept as a starting point 154

148 Systems Engineering Requirements Requirements definitions Identification of applicable ITS standards and testing procedures AMPA Regional ITS Architecture Output Use Functional Requirements as a starting point. Use regional architecture standards outputs as a starting point for the standards definition. How do you show compliance with the rule requirements? NMDOT has developed an ITS Project Checklist ( which can be used to document how a specific project addresses the requirements. A Systems Engineering project certification is required by NMDOT and FHWA for all projects to ensure they follow this process. This certification plays not only a crucial role in ensuring the ITS project is developed in a thorough and robust manner consistent with the Regional Architecture, it provides a crucial link to the maintenance process explained the next chapter. Therefore, NMDOT will notify the Maintenance Manager of certifications via , and this record of project activity will serve as a monitoring mechanism for ITS project tracking as part of the Maintenance Plan duties at MRCOG Issues/Challenges One of the challenges of using the ITS Architecture and the System s Engineering process in the implementation of a project is educating stakeholders about the benefits of the process and the process itself. The systems engineering process is not a new process to many organizations. It may not be called the systems engineering process, but various stakeholders processes may map to the systems engineering process very well (as shown in Table 17). Making these types of linkages between processes makes it easier to incorporate the ITS Architecture as a tool in the process. Another challenge is engaging a broader stakeholder base on a project when the ITS Architecture indicates that possibility. The entire activity of seeking integration opportunities is more institutional than technical. There will be instances where getting more stakeholders involved in a project will increase its complexity or cross jurisdictional boundaries that may not have been considered in the initial scope. It is important to explore these integration opportunities so that, at the very least, they are accounted for and supported in the project design even though they may not be implemented with that specific project. The ultimate goal is to make ITS deployment as economical as possible. One way this can be accomplished is by deploying projects across institutional boundaries where different stakeholders get benefit from the ITS deployment. 155

149 13. Maintaining the Architecture The AMPA Regional ITS Architecture is not a static set of outputs. It must change as plans change, ITS projects are implemented, and the ITS needs and services evolve in the region. Fortunately, project development procedures for the NMDOT and the MRCOG include assurances that any project using the highway trust fund with federal or state funding are developed consistent with applicable FHWA/USDOT ITS requirements per 23 CFR Rule 940 on Intelligent Transportation Systems as well as 23 CFR pertaining to the Congestion Management Process applicable in Transportation Management Areas. These include: MRCOG s TIP and MTP Project Development Processes, the CMP and the Project Prioritization Process, and the ITS Subcommittee s monthly review of project development and implementation activities NMDOT project certification for Systems Engineering NMDOT s Location Study Procedures (updated in 2015) that require each project, regardless of project type, consider the presence and condition of ITS infrastructure and related equipment, as well as include applicable ITS architecture review. This provides an additional assurance that ITS Project development activity using non-local funds will be consistent with the architecture. These project development support mechanisms provide a high level of assurance that all projects will be developed consistent with the applicable ITS architecture, however, since they only apply to federal and state-funded projects, there is risk that locally funded projects could proceed without reference to the architecture. Therefore, a robust maintenance plan is necessary. This section describes the maintenance plan for maintaining the AMPA Regional ITS Architecture, and covers the following four key areas: Who will be involved in the maintenance of the architecture? When will the architecture be updated? What will be maintained? How it will be maintained (i.e. what configuration control process will be used)? The AMPA Regional ITS Architecture is created as a consensus view of what ITS systems the stakeholders in the state have currently implemented and what systems they plan to implement in the future. The AMPA Regional ITS Architecture will need to be updated to reflect changes resulting from project implementation or resulting from the planning process itself. Types of changes may include: Changes for Project Definition. When actually defined, a project may add, subtract or modify elements, interfaces, or information flows from the AMPA Regional ITS Architecture. Because the AMPA Regional ITS Architecture is meant to describe the current (as well as future) regional implementation of ITS, it must be updated to correctly reflect how the developed projects integrate into the state, or specific regions. Also, once projects are implemented, interfaces that were shown in the architecture as planned should now be changed to existing. 156

150 Projects are completed. At each update of the architecture, those projects completed can be removed from Turbo Architecture (and the document) and the current set of planned projects updated. Changes for Project Addition/Deletion. Occasionally a project will be added or deleted through the planning process and some aspects of the AMPA Regional ITS Architecture that are associated with the project may be expanded, changed or removed. Changes in Project Priority. Due to funding constraints, or other considerations, the planned project sequencing may change. Delaying a project may have a ripple effect on other projects that depend on it. Raising the priority for a project s implementation may impact the priority of other projects that are dependent upon it. Changes in Regional Needs. Transportation planning is done to address regional needs. Over time these needs can change and the corresponding aspects of the AMPA Regional ITS Architecture that addresses these needs may need to be updated. Changes in other Regional/Statewide ITS Architectures. Changes made in New Mexico Statewide ITS Architecture can affect the AMPA Regional ITS Architecture, necessitating changes to maintain consistency between the architectures. New Stakeholder: When new stakeholders come to the table, the AMPA Regional ITS Architecture will need be updated to reflect their place in the regional view of ITS elements, interfaces, and information flows. Changes or Evolution in ITS Standards applicable to ITS Projects in AMPA: The architecture maps ITS standards to interfaces (and hence to projects). Over time, this mapping will need to be updated as standards release new versions, or as new standards are developed and matured. Finally, the National ITS Architecture may be expanded and updated from time to time to include new user services or better define how existing elements satisfy the user services. These changes should also be considered as the AMPA Regional ITS Architecture is updated. The National ITS Architecture may have expanded to include a user service that has been discussed in a region, but not been included in the AMPA Regional ITS Architecture, or been included in only a very cursory manner Timetable for Periodic/Event Maintenance How often will the AMPA Regional ITS Architecture be modified or updated? What events or timetable will be used for making updates or changes to the architecture? The basic approach to updating the architecture is Periodic Maintenance; reviewing and revising the architecture at intervals related to recurring activities in the MRCOG transportation planning process. Eventdriven updates will be accommodated in the unlikely situation that they might be needed. 157

151 It has proven most pragmatic that the architecture be maintained coincident with agency projectsubmittals as part of the ongoing TIP and/or MTP project development cycles (2 years and 4 years, alternatively). These recurring activities are open to all member agencies in the AMPA, and provide the best opportunity to review ITS plans and submittals in the context of the entire system of projects for the region. All agency ITS project submittals are included, which allows ITS projects to be considered among all other projects, including other roadway projects (non- ITS) that may afford ITS Mainstreaming opportunities, i.e., incorporating ITS elements not necessarily part of their original scope. Extra effort will need to be made to reach out to those stakeholders not part of the MRCOG Transportation Planning Process, such as first responders. The Maintenance Manager will coordinate this effort with the MRCOG stakeholders present at the ITS Subcommittee. In addition, the MRCOG s CMP and the Project Prioritization Process include incentives (additional points) for any project with ITS elements as well as for those projects that specifically address ITS infrastructure, strategies, or ITS Service system gaps resulting from incomplete or phased deployment. This new approach at MRCOG focuses on ITS and provides further attention to the need for coordinated ITS deployment especially during project development as with the TIP and MTP, and the incentive has a tendency to encourage adjustments in project scope, resulting in additional ITS elements for non-its projects as opportunities present. The periodic update of the architecture will be developed during the TIP or MTP development process, and will involve the primary components of: Architecture Addendum, minor revisions, tied to TIP/MTP project evaluation and development cycle (2 years) Baseline Update, larger scale, more comprehensive, performed if deemed necessary. The process will utilize the fully integrated plan development cycle as shown in Figure 20 below, which stresses the relationship between the project funding program of the TIP/MTP and the project and plan guidance included in the Regional Architecture. Projects included in these plans/programs are associated with ITS Services identified in the architecture and provide a direct link between what is envisioned in the architecture and what is actually funded in the transportation plan. Both will be finalized once the transportation programs are approved and the project lists are solidified, which will ensure the architecture reflects the proper level of approved project programming. 158

152 Figure 20: MRCOG TIP Development Flow Chart (with ITS Subcommittee Participation Noted) Based on a monitoring of regional activity and need, a comprehensive architecture review should be considered every four years, and should be performed prior to the update of the TIP or MTP. The review is necessary to ensure that the architecture continues to accurately represent the regional view of ITS Systems. An update may include adding new stakeholders, reviewing transportation needs and services for the region, updating the status of projects, and reflecting new goals and strategies, as appropriate. Operational concepts, system functional requirements, project sequencing, ITS standards, and the list of agency agreements may also be updated at this time. If no significant changes are noted, then the architecture update can remain on the regular 2-year TIP/MTP project cycle and the Architecture Addendum process Ongoing Monitoring/Reporting Log Within the maintenance cycles of the architecture, all ITS project activity in the AMPA will be monitored through the ITS Subcommittee. Several processes will be utilized to support this monitoring, including the notification to the Maintenance Manager of all projects pursuing the aforementioned Systems Engineering Certification by the NMDOT ITS Bureau. Project updates at the ITS Subcommittee will also provide interim project information that will be evaluated for inclusion in the architecture accordingly. If necessary, the Maintenance Manager will contact the key stakeholders, via , written correspondence, or by telephone, and 159