Bay Region. Final Regional ITS Architecture. Michigan Department of Transportation Regional ITS Architectures and Deployment Plans

Transcription

1 Michigan Department of Transportation Regional ITS Architectures and Deployment Plans Bay Region Final Regional ITS Architecture Prepared by: In association with: January 31, Copyright 2008 by Kimley-Horn and Associates, Inc. All rights reserved.

2 TABLE OF CONTENTS FINAL REGIONAL ITS ARCHITECTURE REPORT BAY REGION 1. INTRODUCTION Project Overview Document Overview Assessment The Bay Region Geographic Overview Transportation Infrastructure Bay Region ITS Plans Stakeholders REGIONAL ITS ARCHITECTURE DEVELOPMENT PROCESS CUSTOMIZATION OF THE NATIONAL ITS ARCHITECTURE FOR THE BAY REGION Systems Inventory Regional Needs Element Customization Subsystems and Terminators ITS Inventory by Stakeholder Top Level Regional System Interconnect Diagram Market Packages Selection and Prioritization of Regional Market Packages Customized Market Packages Regional ITS Needs and Customized Market Packages Architecture Interfaces Element Connections Data Flows Between Elements APPLICATION OF THE REGIONAL ITS ARCHITECTURE Functional Requirements Standards Operational Concepts Potential Agreements Phases of Implementation USE AND MAINTENANCE PLAN FOR THE REGIONAL ITS ARCHITECTURE Process for Determining Architecture Conformity Maintenance Process Procedure for Submitting ITS Architecture Changes Between Scheduled Updates...50 APPENDIX A NATIONAL ITS ARCHITECTURE MARKET PACKAGE DEFINITIONS APPENDIX B CUSTOMIZED MARKET PACKAGES APPENDIX C ELEMENT FUNCTIONAL REQUIREMENTS APPENDIX D STAKEHOLDER DATABASE APPENDIX E ARCHITECTURE CONFORMANCE AND MAINTENANCE DOCUMENTATION FORM i Final Regional ITS Architecture

3 TABLE OF CONTENTS FINAL REGIONAL ITS ARCHITECTURE REPORT BAY REGION LIST OF FIGURES Figure 1 - Bay Regional Boundaries...4 Figure 2 - Bay Regional ITS Architecture and Deployment Plan Development Process...7 Figure 3 - National ITS Architecture Physical Subsystem Interconnect Diagram...11 Figure 4 - Bay Regional System Interconnect Diagram...24 Figure 5 - Example Market Package Diagram: ATMS03 Surface Street Control...27 Figure 6 - Example Interconnect Diagram: Public Safety Vehicles...30 Figure 7 - Example Flow Diagram: EM01-1 Michigan State Police...31 Figure 8 - Example Emergency Routing Diagram: EM02 Public Safety...32 Figure 9 - Example Two Element Flow Diagram...33 Figure 10 - Example Emergency Context Flow Diagram: Traveler Information Database...34 Figure 11 - Process for Documenting Architecture Performance...52 LIST OF TABLES Table 1 - Summary of Architecture Assessment Categories...2 Table 2 - Bay Stakeholder Agencies and Contacts...6 Table 3 - Bay Region Stakeholder Descriptions...12 Table 4 - Bay Region Inventory of ITS Elements...13 Table 5 - Bay Region Market Package Prioritization by Functional Area...26 Table 6 - Regional ITS Needs and Corresponding Market Packages...28 Table 7 - Bay Region Applicable ITS Standards...36 Table 8 - Bay Region Stakeholder Roles and Responsibilities...39 Table 9 - Bay Region Potential Agreements...46 Table 10 - Regional ITS Architecture and Deployment Plan Maintenance Summary...50 ii Final Regional ITS Architecture

4 LIST OF ACRONYMS AASHTO AD AHS AMBER ANSI APTS ATIS ATMS AVL AVSS CCTV CJIC CRC CVISN CVO DCM DMS DNR DPW DSRC EM EMS EOC FHWA FTA HAR HAZMAT HRI American Association of State Highway and Transportation Officials Archived Data Automated Highway System America s Missing: Broadcast Emergency Response American National Standards Institute Advanced Public Transportation Systems Advanced Travel Information System Advanced Traffic Management System Automated Vehicle Location Advanced Vehicle Safety System Closed Circuit Television Criminal Justice Information Center County Road Commission Commercial Vehicle Information Systems and Networks Commercial Vehicle Operations Data Collection and Monitoring Dynamic Message Sign Department of Natural Resources Department of Public Works Dedicated Short Range Communication Emergency Management Emergency Medical Services Emergency Operations Center Federal Highway Administration Federal Transit Administration Highway Advisory Radio Hazardous Materials Highway Rail Intersection iii Final Regional ITS Architecture

5 LIST OF ACRONYMS IDAS IEEE IMMS ISO ISP ITE ITS MAC MC MDT MITSC MOU MSP NEMA NOAA NTCIP NWS RWIS SAE ITS Deployment Analysis Software Institute of Electrical and Electronics Engineers Incident Management Message Sets International Standards Organization Information Service Provider Institute of Transportation Engineers Intelligent Transportation System Medium Access Control Maintenance and Construction Michigan Department of Transportation Mobile Data Terminal Michigan Intelligent Transportation Systems Center Memorandum of Understanding Michigan State Police National Emergency Management Association National Oceanic and Atmospheric Administration National Transportation Communications for ITS Protocol National Weather Service Roadway Weather Information System Society of Automotive Engineers SAFETEA-LU Safe, Accountable, Flexible, Efficient Transportation Equity Act A Legacy for Users SDO STMF TCP/IP TEA-21 TIP TMC Standards Development Organization Simple Transportation Management Framework Transmission Control Protocol/Internet Protocol Transportation Equity Act for the 21st Century Transportation Improvement Program Transportation Management Center iv Final Regional ITS Architecture

6 LIST OF ACRONYMS TOC TSC UDP/IP USDOT VIVDS XML Traffic Operations Center Transportation Service Centers User Datagram Protocol/Internet Protocol United States Department of Transportation Vehicle Imaging Video Detection Systems Extensible Mark-up Language v Final Regional ITS Architecture

7 1. INTRODUCTION 1.1 Project Overview Development of a regional intelligent transportation system (ITS) architecture is one of the most important steps in planning for and implementing ITS in a region. ITS architectures provide a framework for implementing ITS projects, encourage interoperability and resource sharing among agencies, identify applicable standards to apply to projects, and allow for cohesive longrange planning among regional stakeholders. The ITS architecture allows stakeholders to plan for what they want their system to look like in the long-term, and then break out the system into smaller, more modular pieces that can be implemented over time as funding permits. ITS architectures satisfy the conformity requirements first established in the Transportation Equity Act for the 21 st Century (TEA-21) highway bill and continued in the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) bill passed in In response to Section 5206(e) of TEA-21, the Federal Highway Administration (FHWA) issued a final rule and the Federal Transit Administration (FTA) issued a final policy that required regions implementing any ITS projects using federal funds to have an ITS architecture in place by April After this date, any ITS projects must show conformance with their regional ITS architecture in order to be eligible for funding from FHWA or FTA. Regions that had not yet deployed ITS were given four years to develop an ITS architecture after their first ITS project proceeded to final design. In November 2006, the Michigan Department of Transportation () began development of the Bay Regional ITS Architecture. The Regional ITS Architecture has the same geographic boundaries of the Bay Region. The Regional ITS Architecture focuses on a 20-year vision of ITS for the Bay Region. In addition, a separate ITS Deployment Plan was developed to identify and prioritize specific ITS projects recommended for the Region in order to implement the ITS architecture. The ITS Deployment Analysis Software (IDAS) was utilized to evaluate and prioritize the list of ITS projects outlined for the Bay Region. The ITS Architecture and the ITS Deployment Plan were both developed with significant input from local, state, and federal officials. A series of four workshops were held to solicit input from stakeholders and ensure that the plans reflected the unique needs of the Region. Copies of the draft reports were provided to all stakeholders. The Regional ITS Architecture and Deployment Plan developed reflects an accurate snapshot of existing ITS deployments and future ITS plans in the Region. Needs and priorities of the Region will change over time and in order to remain effective this plan should be periodically reviewed and updated. 1.2 Document Overview The Bay Regional ITS Architecture report is organized into five key sections: Section 1 Introduction This section provides an overview of the National ITS Architecture requirements, the Bay Regional ITS Architecture, and the key features and stakeholders in the Bay Region. Section 2 Regional ITS Architecture Development Process An overview of the key steps involved in developing the ITS architecture for the Bay Region is provided in this section. It includes a discussion of stakeholder involvement, architecture workshops, and the architecture development process. 1 Final Regional ITS Architecture

8 Section 3 Customization of the National ITS Architecture for the Bay Region This section contains a summary of regional needs and details the customization of the National ITS Architecture to meet the ITS vision for the Bay Region. The market packages that were selected for the Region are included in this section and interconnects are presented, including the sausage diagram showing the relationships of the key subsystems and elements in the Region. Section 4 Application of the Regional ITS Architecture Functional requirements and standards that apply to the Region, as indicated by the Regional ITS Architecture, are presented in Section 4. Operational concepts identifying stakeholder roles and responsibilities have been prepared and potential agreements to support the sharing of data and resources have been identified. Section 5 Use and Maintenance Plan for the Regional ITS Architecture A use and maintenance plan will be developed for the Bay Regional ITS Architecture and included in this section in the Final Document. The plan will outline the procedure for updating the ITS architecture over time. The Bay Regional ITS Architecture also contains five appendices: Appendix A National ITS Architecture Market Package Definitions; Appendix B Customized Market Packages; Appendix C Element Functional Requirements; Appendix D Stakeholder Database; and Appendix E Architecture Maintenance Documentation Form. 1.3 Assessment The Final Draft of the Bay Region ITS Architecture and Deployment Plan has been assessed based on twelve items derived from both the April 8, 2001 USDOT ITS Architecture and Standards Conformity Rule/Policy and from the architecture development process described in the Regional ITS Architecture Guidance Document. A listing of these items is shown in Table 1. Table 1 - Summary of Architecture Assessment Categories Content Criteria Architecture Implementation Criteria 1. Architecture Scope 8. Implementation Plan (use) 2. Stakeholder Identification 9. Maintenance Plan 3. System Inventory 10. Agreements 4. Needs and Services 11. Standards Identification 5. Operational Concept 12. Project Sequencing 6. Functional Requirements 7. Interfaces/Flows 2 Final Regional ITS Architecture

9 1.4 The Bay Region Geographic Overview The Bay Region is defined by the boundary of Lake Huron and Saginaw Bay to the east, the North Region to the north, the Grand Region to the west, and the University and Metro Region to the south, as shown in Figure 1. The Region encompasses all of the 13 counties of the Bay Region of Michigan. The largest cities within the geographical boundaries of the Bay Region include Flint, Saginaw, Bay City, Midland, and Mt. Pleasant. When developing the stakeholder group, the project team coordinated with to invite the appropriate townships, cities, counties, State and Federal agencies, and area transit providers. The Bay-Metro Transit Authority, Flint-Mass Transportation Authority, and the Saginaw Transit Authority Regional Services are the primary transit providers that operate within the regional boundaries. The Bay-Metro Transit Authority provides fixed route and paratransit services within Bay County. The Flint-Mass Transportation Authority operates fixed route and paratransit services in and near Genesee County. The Saginaw Transit Authority Regional Services operates fixed route and paratransit for the urbanized Saginaw area. Table 2 in Section identifies the stakeholders that participated in the process. When developing the architecture, a 20-year vision for ITS in the Region was documented. In the ITS Deployment Plan, the 20-year time frame will be broken down into smaller time periods to prioritize and sequence the projects. The naming convention used for elements in the Bay Regional ITS Architecture is consistent with the naming convention that was used in the Grand, North, Superior, and Southwest Regions and the Statewide ITS Architecture. This consistency provides seamless connections to those other architectures without requiring that they be specifically called out. Statewide initiatives, such as statewide commercial vehicle operations and the 511 traveler information service, are referenced in the Regional ITS Architecture, but will be addressed in further detail in the Statewide ITS Architecture Transportation Infrastructure As illustrated in Figure 1, the Region is connected by several State and Federal highways. The primary roadway facilities include I-75, I-69, US 127, US 10, and M-46. I-75 is the only interstate in Michigan that runs north-south north of Flint. I-75 connects Detroit with Lansing and continues north through Saginaw, Bay City, and on to Grayling in the North Region. I-69 runs east-west through the southern portion of the Bay Region. It connects Lansing in the University Region with Flint and continues east to Port Huron on the Lake Huron coastline in the Metro Region. US 127 is one of the major north-south roadways that connects Lansing in the University Region with Mt. Pleasant. US 127 continues north of Mt. Pleasant, running parallel with I-75 until they intersect just south of Grayling in the North Region. US 10 runs east-west through the Bay Region from US 127 on the west side to Midland and Bay City. M-46 is another east-west route that connects the Grand Region with Saginaw and continues east to Port Sanilac on the Lake Huron coastline. 3 Final Regional ITS Architecture

10 1/31/2008 Figure 1 - Bay Regional Boundaries

11 1.4.3 Bay Region ITS Plans The Bay Region began the development of a Regional ITS Architecture in 2006 when contracted with a consultant to develop several regional ITS architectures and deployment plans in the State of Michigan. Version 5.1 of the National ITS Architecture was used in the architecture development. It is important to recognize the initial deployment of ITS infrastructure in a region because as of April 2005, in order for a region to receive funding for ITS projects from the Highway Trust Fund, the United States Department of Transportation (USDOT) requires that the region have an ITS architecture developed. This requirement only applies to regions with existing ITS infrastructure deployed. For regions that do not have any ITS infrastructure deployed, the USDOT requires that they have an ITS architecture within four years of their first ITS project entering final design. The Bay Region includes Genesee County, which approved a Regional ITS Architecture in December Genesee County has several deployments and those existing and planned ITS components are included in the Bay Region ITS Regional Architecture. The Bay Region also has several ITS components deployed outside of Genesee County. Examples of implementations in the Region include closed loop signal systems, portable dynamic message signs (DMS), and weigh-in-motion sensors. As the Bay Region pursues funding opportunities for proposed projects, it will be necessary to show that a project fits within the ITS architecture developed for the Region Stakeholders Due to the fact that ITS often transcends traditional transportation infrastructure, it is important to involve non-traditional stakeholders in the architecture development and visioning process. Input from these stakeholders, both public and private, is a critical part of defining the interfaces, integration needs, and overall vision for ITS in a region. Table 2 contains a listing of stakeholders in the Bay Region who have participated in the project workshops or provided input to the study team as to the needs and issues that should be considered as part of the Regional ITS Architecture. Other stakeholders that were invited to participate but were not able to attend were provided minutes of workshops and copies of reports to encourage their participation as much as possible. Appendix D contains a copy of the stakeholder database and workshop attendance records. 5 Final Regional ITS Architecture

12 Table 2 - Bay Stakeholder Agencies and Contacts Stakeholder Agency Address Contact Bay City Area Transportation Study (BCATS) Center Avenue Bay County Bay City, Michigan Bay County Road Commission 2600 East Beaver Road Kawkawlin, Michigan Bay Metro Transit 1510 North Johnson Street Bay City, Michigan Bay Metro Transit 1510 North Johnson Street Bay City, Michigan ECMPDR (Regional Planning Commission) 3144 Davenport Avenue, Suite 200 Saginaw, Michigan FHWA - HAD -MT 400 Seventh Street, SW Washington, DC FHWA - Michigan 315 West Allegan, Suite 201 Lansing, Michigan Genesee County Metropolitan Planning 1101 Beach Street Commission Flint, Michigan Genesee County Road Commission 211 West Oakley Street Flint, Michigan Genesee County Road Commission 211 West Oakley Street Flint, Michigan Genesee County Road Commission 211 West Oakley Street Flint, Michigan Gratiot County Road Commission 214 East Center Street Ithaca, Michigan Programs, - Lansing 425 West Ottawa Lansing, Michigan Bay City TSC 2590 E. Wilder Road Bay City, Michigan Bay Region 55 East Morley Drive Saginaw, Michigan Bay Region 55 East Morley Drive Saginaw, Michigan Bay Region 55 East Morley Drive Saginaw, Michigan Bay Region 55 East Morley Drive Saginaw, Michigan Cass City TSC 6867 East Cass City Road Cass City, Michigan Central Maintenance 6333 Old Lansing Road Lansing, Michigan Davison TSC 9495 East Potter Road Davison, Michigan ITS Program Office 425 W. Ottowa Street, Mail Code B235 Lansing, Michigan Metro Region West Nine Mile Road Southfield, Michigan Metro Region West Nine Mile Road Southfield, Michigan MT. Pleasant TSC 1212 Corporate Drive Mt. Pleasant, Michigan Planning 425 W. Ottowa Street, Mail Code B235 Lansing, Michigan Saginaw County MPO 111 South Michigan Avenue Saginaw, Michigan Saginaw County Road Commission 3020 Sheridan Avenue Saginaw, Michigan Saginaw Metropolitan Area Transportation 615 Court Street Study (SMATS) and SCMPC Saginaw, Michigan Saginaw Transit Authority Regional Services 301 East Genesee, Suite 500 Saginaw, Michigan Tuscola County Road Commission 1733 Mertz Road Caro, Michigan Dave Engelhardt James Lillo Eric Sprague Glenn Cardinali Anamika Laad Tim Crothers Morrie Hoevel Sharon Gregory Kenneth Johnson Christina Michael Bonnie Wood Ray Welke Jim D'Lamater Louis Taylor Wendy Cloutier Steve Palmer Linda Burchell Jay Reithel Doug Wilson Tim Croze David Thorp Greg Krueger Collin Castle Michelle Mueller Terry Palmer Dave Schade Doug Bell Bill Miller Phil Grimaldi Bill Wright Michelle Zawerucha 5 Final Regional ITS Architecture

13 2. REGIONAL ITS ARCHITECTURE DEVELOPMENT PROCESS Development of the Regional ITS Architecture and Deployment Plan for the Bay Region relied heavily on stakeholder input to ensure that the architecture reflected local needs. A series of four workshops was held with stakeholders to gather input, and draft documents were made available to stakeholders for review and comment. The process followed for the Bay Region was designed to ensure that stakeholders could provide input and review for the development of the Region s ITS Architecture and Deployment Plan. Figure 2 illustrates the process followed. Kick-off Workshop and ITS Needs System Inventory ITS Architecture Workshop and ITS Architecture Development ITS Deployment Plan Workshop and ITS Deployment Plan Development Comment Resolution Workshop and Final Report Figure 2 - Bay Regional ITS Architecture and Deployment Plan Development Process A total of four workshops with stakeholders over a period of eleven months were used to develop the Bay Regional ITS Architecture and Deployment Plan. These workshops included: Kick-Off Workshop December 7, 2006; Regional ITS Architecture Development Workshop January 18, 2007; ITS Deployment Plan Workshop August 3, 2007; and Comment Resolution Workshop December 5, Key components of the process are described below: Task 1 Kick-Off Workshop and ITS Needs: A stakeholder group was identified that included representatives from regional transportation, transit, and emergency management/public safety agencies. The group was invited to the project Kick-Off Workshop where ITS needs for the Region were identified. Task 2 System Inventory: Collecting information for the system inventory began at the Kick-Off Workshop through discussions with the stakeholders to determine existing and planned ITS elements in the Region. After the Kick-Off Workshop, follow-up calls were conducted with several local stakeholders to gather additional input. Task 3 ITS Architecture Workshop and ITS Architecture Development: The purpose of the Regional ITS Architecture Workshop was to review the system inventory with stakeholders and develop the Bay Regional ITS Architecture. Training on the National ITS Architecture was integrated into the workshop so that key elements of the architecture, such as market packages, could be explained prior to 7 Final Regional ITS Architecture

14 the selection and editing of these elements. The result of the Regional ITS Architecture Workshop was an ITS Architecture for the Bay Region that included a system inventory, interconnect diagram, customized market packages, and relevant ITS standards. Following the workshop, a Draft Regional ITS Architecture document was prepared and sent to stakeholders for review and comment. Task 4 ITS Deployment Plan Workshop and ITS Deployment Plan Development: A draft project listing for the Region will be presented to stakeholders at the Regional ITS Deployment Plan Workshop. Stakeholders will be asked to provide input on the recommended projects, responsible agencies, associated costs, and deployment timeframe. Following the workshop, a Draft Regional ITS Deployment Plan document was prepared and sent to stakeholders for review and comment Task 5 Comment Resolution Workshop and Final Report: A Comment Resolution Workshop was held with stakeholders to review the Draft Regional ITS Architecture and the Draft Regional ITS Deployment Plan. Next steps for the Region were also discussed. Comments were incorporated and a final Regional ITS Architecture and Regional ITS Deployment Plan were developed. 8 Final Regional ITS Architecture

15 3. CUSTOMIZATION OF THE NATIONAL ITS ARCHITECTURE FOR THE BAY REGION 3.1 Systems Inventory An important initial step in the architecture development process is to establish an inventory of existing ITS elements. At the Kick-Off Workshop and through subsequent discussions with agency representatives, Bay Region stakeholders provided the team with information about existing and planned systems that would play a role in the Region s ITS architecture. The National ITS Architecture has eight groups of ITS service areas., planned, and future systems in the Region were identified in the following service areas: Traffic Management includes the Michigan Intelligent Transportation Systems Center (MITSC) located in Detroit as well as other existing and future TMCs and traffic operations centers (TOCs), detection systems, closed circuit television (CCTV) cameras, fixed and portable dynamic message signs, and other related technologies. Emergency Management includes emergency operations/management centers, improved information sharing among traffic and emergency services, automated vehicle location (AVL) on emergency vehicles, traffic signal preemption for emergency vehicles, and wide-area alerts. Maintenance and Construction Management includes work zone management, roadway maintenance and construction information, winter maintenance, and road weather detection systems. Public Transportation Management includes transit and paratransit AVL, dispatch systems, transit travel information systems, electronic fare collection, and transit security. Commercial Vehicle Operations includes coordination with Commercial Vehicle Information Systems and Networks (CVISN) efforts, and hazardous material (HAZMAT) management Traveler Information includes broadcast traveler information such as 511, traveler information kiosks, and highway advisory radio (HAR). Archived Data Management includes electronic data management and archiving systems. Vehicle Safety includes collision avoidance and automated highway systems. 3.2 Regional Needs Needs from the Region were identified by Stakeholders at the Kick-Off Workshop held in December of The needs identified provided guidance for determining which market packages should be included in the architecture. Stakeholders identified ITS needs for the Bay Region in the following areas: Traffic management; Emergency management; Maintenance and construction management; Public transportation management; Commercial vehicle operations; Traveler information; and Archived data management. 9 Final Regional ITS Architecture

16 Section contains additional information about the specific needs identified and relates those needs to the market packages that document the corresponding ITS service. 3.3 Element Customization The inventory and needs documented at the Kick-Off Workshop are the starting point for developing an ITS architecture for the Bay Region. These ITS systems and components are used to customize the National ITS Architecture and create the architecture for the Bay Region. When developing customized elements, the stakeholder group agreed not to create individual traffic, maintenance, and emergency management elements for all of the individual cities within the Bay Region. The smaller communities in the Region were documented as part of the local agency elements. This documentation allows the communities to be included in the Regional ITS Architecture, and therefore eligible to use federal monies on potential future ITS deployments Subsystems and Terminators Each identified system or component in the Bay Region ITS inventory was mapped to a subsystem or terminator in the National ITS Architecture. Subsystems and terminators are the entities that represent systems in ITS. Subsystems are the highest level building blocks of the physical architecture, and the National ITS Architecture groups them into four major classes: Centers, Field, Vehicles, and Travelers. Each of these major classes includes various components that represent a set of transportation functions (or processes). Each set of functions is grouped under one agency, jurisdiction, or location, and correspond to physical elements such as: traffic operations centers, traffic signals, or vehicles. Figure 3 shows the National ITS Architecture subsystems. This figure, also known as the sausage diagram, is a standard interconnect diagram, showing the relationships of the various subsystems within the architecture. A customized interconnect diagram for the Bay Region is shown in Figure 4. Communication functions between the subsystems are represented in the ovals. Fixed-point to fixed-point communications include not only twisted pair and fiber optic technologies, but also wireless technologies such as microwave and spread spectrum. Terminators are the people, systems, other facilities, and environmental conditions outside of ITS that need to communicate or interface with ITS subsystems. Terminators help define the boundaries of the National ITS Architecture as well as a regional system. Examples of terminators include: drivers, weather information providers, and information service providers. 10 Final Regional ITS Architecture

17 Travelers Remote Traveler Support Personal Information Access Traffic Management Information Service Provider Emergency Management Emissions Management Centers Toll Administration Transit Management Commercial Vehicle Administration Fleet and Freight Management Maintenance & Construction Management Archived Data Management Wide Area Wireless (Mobile) Communications Vehicle to Vehicle Communications Vehicle Emergency Vehicle Vehicles Commercial Vehicle Transit Vehicle Maint & Const Vehicle Dedicated Short Range Communications Fixed-Point to Fixed-Point Communications Roadway Field Security Monitoring Toll Collection Parking Management Commercial Vehicle Check Terminators Figure 3 - National ITS Architecture Physical Subsystem Interconnect Diagram ITS Inventory by Stakeholder Each stakeholder is associated with one or more systems or elements (subsystems and terminators) that make up the transportation system in the Bay Region. A listing of stakeholders as identified in the architecture can be found in Table 3 along with a description of the stakeholder. For example, rather than individually documenting each of the smaller local agencies in the Region, a single stakeholder was created for local agencies which represents the counties, cities, and towns not specifically called out in the architecture. Table 4 sorts the inventory by stakeholder so that each stakeholder can easily identify and review all of the architecture elements associated with their agency. The table includes the status of the element. In many cases, an element classified as existing might still need to be enhanced to attain the service level desired by the Region. 11 Final Regional ITS Architecture

18 Table 3 - Bay Region Stakeholder Descriptions Stakeholder Bay Metro Transit Authority Department of Homeland Security DNR Financial Institution Flint-Mass Transportation Authority Media MSP NOAA Other Agencies Other Elements Private Information Service Provider Private Operators Private Transportation Providers Rail Operators Regional Demand Response Transit Providers Saginaw Transit Authority Regional Services System Users Stakeholder Description Transit provider that operates fixed route and paratransit in Bay County. The Department of Homeland Security is responsible for coordinating with multiple agencies to secure the nation's borders and protect the infrastructure and citizens. Michigan Department of Natural Resources is responsible for the operations and maintenance of all Parks and Recreation facilities including infrastructure components on those properties. DNR utilizes some technologies to provide information to visitors at Parks and Recreation facilities. Banks involved in the transfer of funds for fare collection as well as for other fee based transportation services. Can handle the exchange of money for transit electronic fare collection or toll collection. Transit provider that operates fixed route and paratransit in and near Genesee County. Local government includes municipalities, counties, and townships and covers all departments within those agencies that deal with traffic, public safety, emergency management, public works and school transportation agencies. Local Agencies include: Bay City, Bay CRC, City of Burton, City of Clio, City of Davison, City of Fenton, City of Flint, City of Flushing, City of Grand Blanc, City of Linden, City of Midland, City of Montrose, City of Mount Morris, City of Mt. Pleasant, City of Saginaw, City of Swartz Creek, Genesee CRC, Gratiot CRC, Isabella CRC, Midland CRC, Saginaw CRC. The Michigan Department of Transportation is responsible for the planning, design, construction, maintenance and operation for all aspects of a comprehensive integrated transportation system in the State of Michigan. Some of these roles are achieved through contract services with local agencies and private entities. Local media outlets. This can include television stations, newspapers, radio stations and their associated websites. Michigan State Police is the state law enforcement agency that enforces traffic safety laws as well as commercial vehicle regulations. National Oceanic and Atmospheric Administration gathers weather information and issues severe weather warnings. This stakeholder represents a wide variety of agencies. The associated elements are groups of agencies or providers that do not have a primary stakeholder agency. Other elements include potential obstacles, roadway environment and other vehicles. Private sector business responsible for the gathering and distribution of traveler information. This service is typically provided on a subscription basis. Private Operators manage privately owned resources that interconnect with public sector elements and sub-systems of the Regional Architecture. Private transportation service providers such as taxis and shuttle services. Companies that operate trains and/or are responsible for the maintenance and operations of railroad tracks. Transit providers in the Bay region aside from Bay Metro Transit Authority, Flint- Mass Transportation Authority and Saginaw Transit Authority Regional Services that operate paratransit service in the region. The agencies include Caro Area Transit Authority, Midland Dial-A-Ride and Greater Lapeer Transit Authority. Transit provider that operates fixed route and paratransit for urbanized Saginaw area. All of the users of the transportation system. 12 Final Regional ITS Architecture

19 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status Bay Metro Transit Bay Metro Transit Authority CCTV Surveillance CCTV surveillance at the Bay Metro Transit Authority Authority Center. Department of Homeland Security Bay Metro Transit Authority Data Archive Bay Metro Transit Authority Dispatch Center Bay Metro Transit Authority Electronic Fare Payment Card Bay Metro Transit Authority Kiosks The transit data archive for the Bay Metro Transit Authority. Used by FTA and Office of Public Transportation. Transit dispatch center responsible for the tracking, scheduling and dispatching of fixed route and paratransit vehicles operated by Bay Metro Transit Authority. Medium for collection of transit fares electronically. Kiosks for dissemination of transit traveler information. Kiosks can also be used for the purchase and recharging of electronic fare payment cards. Bay Metro Transit Authority Vehicles Transit Vehicles owned by Bay Metro Transit Authority. Bay Metro Transit Authority Website Department of Homeland Security Website with information about fares and schedules. At this time the website is static. Responsible for coordinating with multiple agencies to secure the nation's borders and protect the infrastructure and citizens. DNR DNR Weather Stations Department of Natural Resources field equipment that collects weather data such as temperature and visibility. Financial Institution Flint-Mass Transportation Authority Financial Service Provider Service Agency Flint-Mass Transportation Authority CCTV Surveillance Flint-Mass Transportation Authority Data Archive Flint-Mass Transportation Authority Dispatch Center Handles exchange of money for transit electronic payment collection. Agency responsible for payment of transit fares for medical transportation as part of government subsidized medical care. This includes Medicare and VA programs. CCTV surveillance at the Flint-Mass Transportation Authority Center. The transit data archive for the Flint-Mass Transportation Authority. Used by FTA and Office of Public Transportation. Transit dispatch center responsible for the tracking, scheduling and dispatching of fixed route and paratransit vehicles operated by Flint-Mass Transportation Authority. 13 Final Regional ITS Architecture

20 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status Flint-Mass Transportation Authority (continued) Flint-Mass Transportation Authority Electronic Fare Payment Card Flint-Mass Transportation Authority Kiosks Flint-Mass Transportation Authority Vehicles Flint-Mass Transportation Authority Website Bay City Drawbridge Control Equipment Bay City Drawbridge Notification Equipment City of Flint 911 County 911 Dispatch County Road Commission County Road Commission Equipment Repair County Road Commission Maintenance Vehicles Fenton Police Department Medium for collection of transit fares electronically. Kiosks for dissemination of transit traveler information. Kiosks can also be used for the purchase and recharging of electronic fare payment cards. Transit Vehicles owned by Flint-Mass Transportation Authority. Website with information about fares and schedules. At this time the website is static. Roadside equipment located on Bay City drawbridges that close approaching roadways or stop traffic prior to the drawbridge opening to waterway traffic. Roadside equipment located on Bay City drawbridges that send notifications when the drawbridge is open for waterway traffic. 911 Dispatch for the City of Flint. Central Dispatch is responsible for the dispatch of all Flint public safety vehicles (police and fire). Central Dispatch is responsible for the dispatch of all public safety vehicles (police and fire). After hours Central Dispatch will also dispatch the Street Department on-call emergency responder. Counties included are Clare, Gladwin, Arenac, Isabella, Midland, Bay, Gratiot, Saginaw, Huron, Tuscola, Sanilac, Genesee and Lapeer. Contract agency managed by a county that oversees road maintenance and snow removal on local and facilities. Facility responsible for maintenance of County Road Commission vehicles. County Road Commission vehicles used in maintenance operations. Municipal police responsible for enforcement within the City of Fenton. Airports Municipal and county owned airports. 14 Final Regional ITS Architecture

21 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status CCTV Cameras Roadside equipment on local routes used for traffic (continued) condition monitoring and management of incidents. DPW Contract agency managed by a local municipality that oversees road maintenance and snow removal on local and facilities. DPW Vehicles Local Government vehicles used in maintenance operations. Field Sensors Parking Management System Public Safety Vehicles Ride Sharing Program Speed Monitoring Equipment TOC Traffic Signals Roadway equipment on local routes used to detect vehicle volumes and/or speeds. This information is used in the operation of the traffic signal system and collected by the TOC. System operated by a local agency that monitors available vehicle parking at key parking facilities. Local law enforcement, fire and EMS vehicles. Includes the ITS equipment installed on the cruisers (AVL, MDTs, etc.). System used for matching riders with similar origins and destinations to promote carpooling. Speed monitoring equipment owned and operated by a local agency. Includes radar, lidar, etc. Local Traffic Operations Center responsible for municipal signal system operations. Multiple traffic signals interconnected and operated by a. Website Website for the Local Agencies. Local Emergency Operations Center Bay City Drawbridge Management Center Maintenance and Construction Field Personnel Animal Crossing Detection Central command and control facility responsible for carrying out the principles of emergency preparedness and emergency management, or disaster management functions at a strategic level in an emergency situation. Central facility that monitors vehicle and waterway traffic and controls drawbridge traffic in Bay City. field forces that operate and maintain facilities. Roadside equipment that monitors roadway for animal activity that could impact traffic. 15 Final Regional ITS Architecture

22 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status (continued) Animal Crossing Warning System In-vehicle and roadside equipment that can notify drivers about possible animal activity. Anti-Icing Field Equipment Bay Region Commercial Vehicle Parking Management System Bay Region Maintenance Management System Bay Region Office Bay Region Transportation Service Centers CCTV Cameras Commercial Vehicle Permitting System DMS Drawbridge Control Equipment Drawbridge Management Center Drawbridge Notification Equipment ESS Roadside equipment located along routes that collects weather data such as temperature and visibility. System operated on routes that monitors available commercial vehicle parking at rest areas and other key locations. Central system used to track and plan maintenance on Bay Region vehicles. The Bay Region Office serves as a data collection and dissemination point for traffic information in the Bay Region. This includes coordination with other agencies such as public safety, emergency management, and transit. field office that oversees road construction and maintenance on facilities. Most maintenance and snow removal in this region is achieved through contract agencies. Roadside equipment located on local roadways used for traffic condition monitoring and management of incidents. system for tracking and monitoring oversize and overweight permits for commercial vehicles. Roadside equipment on routes used to share traveler information with motorists through dynamic messaging. Roadside equipment located on drawbridges that close approaching roadways or stop traffic prior to the drawbridge opening to waterway traffic. Management of the waterways used by boats and ferries and the roadways used by vehicles. Roadside equipment located on drawbridges that send notifications when the drawbridge is open for waterway traffic. Environmental sensor stations located on routes that collect information about the roadways such as temperature and moisture levels. 16 Final Regional ITS Architecture

23 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status (continued) Field Sensors Roadway equipment located on roadways used to detect vehicle volumes and/or speeds. This information is used in the operation of the traffic signal system and collected by the TOC. field sensors include VIVDS and any other vehicle detection. Frost Tube Sensors Grand Traverse County TOC Maintenance Vehicles Roadside equipment located along routes that collect data from frost tube sensors. Transportation operations center located in the North Region for Grand Traverse County. It will be a joint facility with, Grand Traverse County, and Traverse City. Will include the freeway management system in the North Region as well as rural ITS deployments and municipal traffic operations. Michigan Department of Transportation vehicles used in maintenance operations. MI Drive Website Website for Michigan Department of Transportation. North Region TMC Office of Communications Planning Division Data Warehouse Roadside Equipment for AHS Roadside Intersection Collision Avoidance Equipment Roadside Signing Equipment Security Monitoring Field Equipment Service Patrol Dispatch traffic management center located in the North Region. Michigan Department of Transportation responsible for the dissemination of traffic information to the media and public. Archive that contains historical traffic data such as volume and speed information. Equipment located along routes that allows communication between roadside devices and vehicles. Equipment located along routes that communicates between multiple roadside devices and vehicles to alert of unsafe travel conditions or conditions conducive to crashes. Equipment located along routes that provide data through dynamic messaging or in-vehicle messaging. Roadside equipment located on routes that is used for monitoring key infrastructure elements from damage or attacks. These elements include structures such as bridges or dams. Provides efficient use of resources to assist motorists in need on facilities. 17 Final Regional ITS Architecture

24 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status (continued) Service Patrol Vehicles Fully equipped vehicles that provide motorist assistance to vehicles in need on facilities. Speed Monitoring Equipment Speed monitoring equipment owned and operated by the Michigan Department of Transportation. Includes radar, lidar, etc. Statewide TMC - Lansing traffic management center located in Lansing. Superior Region TMC Traffic Signals Traveler Information Database Traveler Information Kiosks traffic management center located in the Superior Region. Multiple traffic signals interconnected and operated by. maintained database for collecting and disseminating road condition data about construction and maintenance activities, incidents, and special events. Interactive kiosks that provides users the ability to request and received transportation information. Weigh-in-Motion In-road equipment that monitors vehicle weights. West Michigan TMC Work Zone Safety Monitoring Equipment Co-located traffic management center in Traverse City. Responsible for the operation of the ITS equipment located in Traverse City and the surrounding areas in the North Region. Portable ITS equipment that can be used in work zones to more efficiently manage traffic and provide traveler information. Includes CCTV, vehicle detection, and/or DMS. Michigan 511 System 511 Traveler information system central server. Michigan 511 Voice Response System MITSC Other Region TSC s Michigan 511 Interactive Voice Response system. This is the customer interface component of the 511 system. traffic management center located in the Metro Region. Local Transportation Service Centers outside of the Bay Region that oversee the operations and maintenance on facilities. Media Local Print and Broadcast Media Local media that provide traffic or incident information to the public. 18 Final Regional ITS Architecture

25 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status MSP CJIC Database Criminal Justice Information Center Database stores criminal justice data and can be accessed by multiple agencies. NOAA Other Agencies Michigan Intelligence Operations Center (MIOC) MSP District 3 - Saginaw MSP Headquarters - East Lansing MSP Motor Carrier Division Michigan Intelligence Operations Center. Provides 24-hour statewide information sharing among local, state, and federal public safety agencies and private sector organizations in order to facilitate the collection, analysis, and dissemination of intelligence relevant to terrorism and public safety. Michigan State Police dispatch for the Bay Region. Provides call-taking and dispatch for public safety agencies. Michigan State Police headquarters that oversees operations of MSP. Responsible for monitoring commercial vehicle regulations on routes. MSP Office of Highway Safety Planning Manages crash data for routes. MSP Toll Free Winter Road Conditions Phone Number MSP Vehicles MSP Winter Travel Advisory Website National Weather Service NWS Weather Stations MBS International Airport Multimodal Transportation Service Provider Winter weather information operated from November through March to share winter weather conditions as received. Public Safety vehicles owned and operated by Michigan State Police. Includes the ITS equipment installed on the cruisers (AVL, MDTs, etc.). Traveler Information website operated by Michigan State Police for dissemination of winter weather advisories. Provides official US weather, marine, fire and aviation forecasts, warnings, meteorological products, climate forecasts, and information about meteorology. National Weather Service Field equipment that collects weather data such as temperature and visibility. Midland Bay City Saginaw International Airport is a municipal airport. Tri-owned by three municipalities. Agency that offers services across multiple transportation modes. 19 Final Regional ITS Architecture

26 Table 4 - Bay Region Inventory of ITS Elements Stakeholder Element Name Element Description Status Other Elements Private Concierge Provider Private entities that provides customized services to the (continued) traveler. This service is usually subscription based. Private Information Service Provider Private Operators Private Transportation Providers School Transportation Agencies Agencies responsible for operating school bus fleets. Potential Obstacles Roadway Environment Private Sector ISP Private Sector Traveler Information Services Contractor Smart Work Zone Equipment Private Fleet Management Systems Private Fleet Operators Private Parking Operator Private Transportation Providers Obstacles that could interfere with the safe operation of vehicles. All objects and conditions in the vicinity of the traveler that can affect the operations of the traveler. Private entities that collect and disseminate traffic information. Website sponsored by a private entity. Often this information is provided through a subscription. Smart Work Zone Equipment owned by private contractor. Portable ITS equipment that can be used in work zones to more efficiently manage traffic and provide traveler information. Includes CCTV, vehicle detection, and/or DMS. A way to track and manage the contents private commercial vehicle fleets carry. Private companies that proactively manage and operate their fleet routing. Includes reactions to incidents and possible delays. System operated on private property that monitors available commercial vehicle parking. Private providers of transportation services in the Region such as taxis and intercity bus services. Rail Operators Rail Operator Wayside Equipment Equipment located along the tracks including railroad crossing gates, bells, and lights as well as the interface to the traffic signal controller indicating the presence of a train. Regional Demand Response Transit Providers Regional Demand Response Transit Providers CCTV Surveillance Regional Demand Response Transit Providers Data Archive CCTV surveillance at the Regional Demand Response Transit Providers Center. The transit data archive for the Regional Demand Response Transit Providers. Used by FTA and Office of Public Transportation. 20 Final Regional ITS Architecture