north-central illinois intelligent ...north-central illinois intelligent transportation systems...

NORTH-CENTRAL ILLINOIS INTELLIGENT TRANSPORTATION SYSTEMS (ITS)

ARCHITECTURE

Prepared For: North-Central Illinois Intelligent Transportation Systems (ITS) Program

Wisconsin State Project ID: 5556-00-06 5556-00-09

5556-00-10 5556-00-11

Submitted To:

Wisconsin Department of Transportation (WisDOT) Transportation District 1 - Madison

Prepared By:

2801 International Lane, Suite 109 Madison, WI 53704 Ph: (608) 242-9220 Fax: (608) 242-9230 www.transcore.com

February, 2003

TABLE OF CONTENTS

EXECUTIVE SUMMARY............................................................................................................................... 1 1 INTRODUCTION .................................................................................................................................... 3

1.1 PROJECT OVERVIEW............................................................................................................................. 3 1.2 PURPOSE OF DOCUMENT..................................................................................................................... 3 1.3 REPORT FORMAT AND OUTLINE ......................................................................................................... 4

2 PROJECT DESCRIPTION...................................................................................................................... 5 2.1 REGION INFORMATION........................................................................................................................ 5 2.2 REGIONAL STAKEHOLDERS ................................................................................................................. 5 2.3 PROJECT CONCEPTS ............................................................................................................................. 7

3 DEVELOPMENT PROCESS .................................................................................................................. 8 3.1 STAKEHOLDER OUTREACH ................................................................................................................. 8 3.2 USER SERVICES ..................................................................................................................................... 9 3.3 MARKET PACKAGES ............................................................................................................................ 9 3.4 PROJECT CONCEPTS ............................................................................................................................. 9 3.5 ARCHITECTURE DESIGN .................................................................................................................... 10 3.6 NATIONAL STANDARDS .................................................................................................................... 10

4 USER SERVICES ASSESSMENT ....................................................................................................... 11 4.1 AGENCY INTERVIEWS ........................................................................................................................ 11 4.2 OVERVIEW OF USER SERVICES........................................................................................................... 11 4.3 MAPPING USER NEEDS TO USER SERVICES ...................................................................................... 17 4.4 REGIONAL ARCHITECTURE USER SERVICES ..................................................................................... 19

5 MARKET PACKAGES IDENTIFICATION/MAPPING ................................................................ 20 5.1 MARKET PACKAGES OVERVIEW ....................................................................................................... 20 5.2 MAPPING USER SERVICES TO MARKET PACKAGES ......................................................................... 22 5.3 IDENTIFIED MARKET PACKAGES FOR NORTH-CENTRAL ILLINOIS................................................. 24

6 PROJECT CONCEPTS .......................................................................................................................... 45 6.1 CRITICAL PROJECT CONCEPT DESCRIPTIONS................................................................................... 45 6.2 DEPLOYMENT SCHEDULE FOR PROJECT CONCEPTS ........................................................................ 85

7 SYSTEM ARCHITECTURE ................................................................................................................. 86 7.1 OVERVIEW OF THE PHYSICAL ARCHITECTURE ................................................................................ 86 7.2 OVERVIEW OF THE LOGICAL ARCHITECTURE .................................................................................. 90 7.3 OVERVIEW OF THE REGIONAL ITS ARCHITECTURE ........................................................................ 91 7.4 HIGH-LEVEL PHYSICAL ARCHITECTURE FOR NORTH-CENTRAL ILLINOIS .................................... 92 7.5 DEFINING THE REGIONAL SUBSYSTEMS ........................................................................................... 93 7.6 TYPICAL REGIONAL INTERCONNECTS AND DATA EXCHANGES .................................................... 97

8 NATIONAL ITS STANDARDS........................................................................................................ 109 8.1 STANDARDS DEVELOPMENT ORGANIZATIONS ............................................................................. 109 8.2 NTCIP STANDARDS ........................................................................................................................ 110

North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11

ITS Architecture Report

i

8.3 ITS STANDARDS LIFE CYCLE .......................................................................................................... 110 8.4 APPLICABLE ITS STANDARDS FOR THE NORTH-CENTRAL REGIONAL ARCHITECTURE ............. 110

9 SAMPLE AGENCY STAKEHOLDER INTERVIEW FORMS ..................................................... 113 10 LIST OF STAKEHOLDER AGENCIES INTERVIEWED ......................................................... 125 11 LIST OF ARCHITECTURE SUBSYSTEMS ................................................................................ 125 12 LIST OF ARCHITECTURE TERMINATORS ............................................................................ 129 13 BOONE COUNTY AGENCY ARCHITECTURES ..................................................................... 132

13.1 BOONE COUNTY 911 CENTER ..................................................................................................... 132 13.2 BOONE COUNTY HIGHWAY DEPARTMENT DISPATCH .............................................................. 134 13.3 CITY OF BELVIDERE DEPARTMENT OF PUBLIC WORKS .............................................................. 136 13.4 CITY OF BELVIDERE DISPATCH .................................................................................................... 138

14 DEKALB COUNTY AGENCY ARCHITECTURES ................................................................... 139 14.1 CITY OF DEKALB DEPARTMENT OF PUBLIC WORKS .................................................................. 139 14.2 CITY OF DEKALB DISPATCH ........................................................................................................ 141 14.3 CITY OF SYCAMORE DEPARTMENT OF PUBLIC WORKS ............................................................. 142 14.4 CITY OF SANDWICH DEPARTMENT OF PUBLIC WORKS ............................................................. 143 14.5 DEKALB COUNTY 911 CENTER ................................................................................................... 144 14.6 DEKALB COUNTY HIGHWAY DEPARTMENT DISPATCH............................................................ 146 14.7 NORTHERN ILLINOIS UNIVERSITY DISPATCH ............................................................................ 148 14.8 NORTHERN ILLINOIS UNIVERSITY PARKING .............................................................................. 149

15 OGLE COUNTY AGENCY ARCHITECTURES......................................................................... 150 15.1 OGLE COUNTY 911 CENTER ........................................................................................................ 150 15.2 OGLE COUNTY HIGHWAY DEPARTMENT DISPATCH................................................................. 152

16 WINNEBAGO COUNTY AGENCY ARCHITECTURES ......................................................... 154 16.1 CITY OF ROCKFORD DEPARTMENT OF PUBLIC WORKS ............................................................. 154 16.2 CITY OF ROCKFORD DISPATCH ................................................................................................... 156 16.3 CITY OF ROCKFORD MAINTENANCE DISPATCH ........................................................................ 157 16.4 CITY OF ROCKFORD PARKING ..................................................................................................... 159 16.5 ILLINOIS STATE POLICE – DISTRICT 16........................................................................................ 160 16.6 ROCKFORD MASS TRANSIT.......................................................................................................... 161 16.7 WINNEBAGO COUNTY 911 CENTER............................................................................................ 162 16.8 WINNEBAGO COUNTY HIGHWAY DEPARTMENT DISPATCH .................................................... 164

17 ILLINOIS DEPARTMENT OF TRANSPORTATION ARCHITECTURES .......................... 166 17.1 IDOT BOONE COUNTY HIGHWAY DEPARTMENT DISPATCH ................................................... 167 17.2 IDOT DEKALB COUNTY HIGHWAY DEPARTMENT DISPATCH................................................. 169 17.3 IDOT OGLE COUNTY HIGHWAY DEPARTMENT DISPATCH...................................................... 171 17.4 IDOT WINNEBAGO COUNTY HIGHWAY DEPARTMENT DISPATCH ......................................... 173 17.5 ILLINOIS DEPARTMENT OF TRANSPORTATION – DISTRICT 2 TRAFFIC MANAGEMENT AND MAINTENANCE CONTROL CENTER........................................................................................................... 175



ii

TABLE OF FIGURES Figure 2-1: North-Central Illinois - Boone, Winnebago, DeKalb, and Ogle Counties ...................................... 5 Figure 3-1: Architecture Development Process.................................................................................................. 8 Figure 4-1: North-Central Illinois ITS Program User Needs and Objectives................................................... 13 Figure 4-2: User Services Grouped by Service Bundles .................................................................................. 14 Figure 4-3: User Service Definitions Table...................................................................................................... 17 Figure 4-4: User Services Mapped to Stakeholder Needs ................................................................................ 18 Figure 4-5: List of Applicable User Services for Region ................................................................................. 19 Figure 5-1: National ITS Architecture Market Packages Grouped by Category.............................................. 22 Figure 5-2: Market Package to User Service Relationship............................................................................... 23 Figure 5-3: Identified Regional Market Packages ............................................................................................ 24 Figure 5-4: APTS01 - Transit Vehicle Tracking Market Package ................................................................... 25 Figure 5-5: APTS02 - Transit Fixed-Route Operations Market Package......................................................... 26 Figure 5-6: APTS03 - Demand Response Transit Operations Market Package............................................... 27 Figure 5-7: APTS04 - Transit Passenger and Fare Management Market Package .......................................... 27 Figure 5-8: APTS05 - Transit Security Market Package.................................................................................. 28 Figure 5-9: APTS06 - Transit Maintenance Market Package .......................................................................... 28 Figure 5-10: APTS07 - Multi-modal Coordination Market Package ............................................................... 29 Figure 5-11: APTS08 - Transit Traveler Information Market Package............................................................ 29 Figure 5-12: ATIS01 - Broadcast Traveler Information Market Package........................................................ 30 Figure 5-13: ATIS02 - Interactive Traveler Information Market Package....................................................... 31 Figure 5-14: ATIS05 - ISP Based Route Guidance Market Package ............................................................... 32 Figure 5-15: ATMS01 - Network Surveillance Market Package ..................................................................... 32 Figure 5-16: ATMS03 - Surface Street Control Market Package .................................................................... 33 Figure 5-17: ATMS04 - Freeway Control Market Package ............................................................................. 34 Figure 5-18: ATMS06 - Traffic Information Dissemination Market Package................................................. 34 Figure 5-19: ATMS07 - Regional Traffic Control Market Package ................................................................ 35 Figure 5-20: ATMS08 - Incident Management System Market Package ........................................................ 36 Figure 5-21: ATMS10 – Electronic Toll Collection Market Package.............................................................. 37 Figure 5-22: ATMS13 - Standard Railroad Grade Crossing Market Package ................................................. 38 Figure 5-23: ATMS14 - Advanced Railroad Grade Crossing Market Package .............................................. 38 Figure 5-24: ATMS16 - Parking Facility Management Market Package......................................................... 39 Figure 5-25: ATMS18 - Road Weather Information System Market Package ................................................ 40 Figure 5-26: ATMS19 - Regional Parking Management Market Package ...................................................... 40 Figure 5-27: CVO10 - HAZMAT Management Market Package.................................................................... 41 Figure 5-28: EM01 - Emergency Response Market Package........................................................................... 42 Figure 5-29: EM02 - Emergency Routing Market Package ............................................................................. 42 Figure 5-30: AD01 - ITS Data Mart Market Package ...................................................................................... 43 Figure 5-31: AD02 - ITS Data Warehouse Market Package............................................................................ 44 Figure 5-32: AD03 - ITS Virtual Data Warehouse Market Package................................................................ 44 Figure 6-1: High level Physical Architecture for Traffic Management and Maintenance Control Center

Project........................................................................................................................................................ 47 Figure 6-2: Interconnect Diagram for Traffic Management and Maintenance Control Center Project ........... 48 Figure 6-3: Agency Roles and Responsibilities for Traffic Management and Maintenance Control Center

Project........................................................................................................................................................ 49 Figure 6-4: Architecture Flow Diagram for the Traffic Management and Maintenance Control Center Project

................................................................................................................................................................... 50 Figure 6-5: Architecture Flow Diagram Definitions for the Traffic Management and Maintenance Control

Center Project ............................................................................................................................................ 51 Figure 6-6: Applicable ITS Standards for the Traffic Management and Maintenance Control Center Project52



iii

Figure 6-7: High Level Physical Architecture for the Interstate Traffic Monitoring and Traveler Information Project........................................................................................................................................................ 53

Figure 6-8: Interconnect Diagram for the Interstate Traffic Monitoring and Traveler Information Project .... 54 Figure 6-9: Agency Roles and Responsibilities for the Interstate Traffic Monitoring and Traveler Information

Project........................................................................................................................................................ 54 Figure 6-10: Architecture Flow Diagram for the Interstate Traffic Monitoring and Traveler Information

Project........................................................................................................................................................ 55 Figure 6-11: Architecture Flow Diagram Definitions for the Interstate Traffic Monitoring and Traveler

Information Project.................................................................................................................................... 56 Figure 6-12: Applicable ITS Standards for the Interstate Traffic Monitoring and Traveler Information Project

................................................................................................................................................................... 57 Figure 6-13: High Level Physical Architecture for the Advanced Signal Operations/Coordination & Surface

Street Traffic Monitoring Project .............................................................................................................. 58 Figure 6-14: Interconnect Diagram for the Advanced Signal Operations/Coordination & Surface Street

Traffic Monitoring Project ........................................................................................................................ 59 Figure 6-15: Agency Roles and Responsibilities for the Advanced Signal Operations/Coordination & Surface

Street Traffic Monitoring Project .............................................................................................................. 59 Figure 6-16: Architecture Flow Diagram for the Advanced Signal Operations/Coordination & Surface Street

Traffic Monitoring Project ........................................................................................................................ 60 Figure 6-17: Architecture Flow Diagram Definitions for the Advanced Signal Operations/Coordination &

Surface Street Traffic Monitoring Project ................................................................................................. 61 Figure 6-18: Architecture Flow Diagram Definitions for the Advanced Signal Operations/Coordination &

Surface Street Traffic Monitoring Project ................................................................................................. 62 Figure 6-19: High Level Physical Architecture for the Agency Data Sharing Project..................................... 63 Figure 6-20: Interconnect Diagram for the Agency Data Sharing Project ....................................................... 63 Figure 6-21: Agency Roles and Responsibilities for the Agency Data Sharing Project .................................. 64 Figure 6-22: Architecture Flow Diagram for the Agency Data Sharing Project .............................................. 65 Figure 6-23: Architecture Flow Diagram Definitions for the Agency Data Sharing Project ........................... 66 Figure 6-24: Applicable ITS Standards for the Agency Data Sharing Project................................................. 66 Figure 6-256-26: High Level Physical Architecture for the Winter Weather Maintenance Enhancement

Project........................................................................................................................................................ 67 Figure 6-27: Interconnect Diagram for the Winter Weather Maintenance Enhancement Project.................... 68 Figure 6-28: Agency Roles and Responsibilities for the Winter Weather Maintenance Enhancement Project68 Figure 6-29: Architecture Flow Diagram for the Winter Weather Maintenance Enhancement Project .......... 69 Figure 6-30: Architecture Flow Diagram Definitions for the Winter Weather Maintenance Enhancement

Project........................................................................................................................................................ 69 Figure 6-31: High Level Physical Architecture Diagram for the Arterial Dynamic Message Signs and

Dynamic Trailblazer Signing Project ........................................................................................................ 70 Figure 6-32: Interconnect Diagram for the Arterial Dynamic Message Signs and Dynamic Trailblazer

Signing Project .......................................................................................................................................... 71 Figure 6-33: Agency Roles and Responsibilities for the Arterial Dynamic Message Signs and Dynamic

Trailblazer Signing Project........................................................................................................................ 71 Figure 6-34: Interconnect Diagram for the Arterial Dynamic Message Signs and Dynamic Trailblazer

Signing Project .......................................................................................................................................... 72 Figure 6-35: Architecture Flow Diagram Definitions for the Arterial Dynamic Message Signs and Dynamic

Trailblazer Signing Project........................................................................................................................ 73 Figure 6-36: Applicable ITS Standards for the Arterial Dynamic Message Signs and Dynamic Trailblazer

Signing Project .......................................................................................................................................... 74 Figure 6-37: High Level Physical Architecture for the Construction Work Zone Safety, Traffic Monitoring,

and Traveler Information Project .............................................................................................................. 75



iv

Figure 6-38: Interconnect Diagram for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project.................................................................................................................................... 76

Figure 6-39: Agency Roles and Responsibilities for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project .............................................................................................................. 76

Figure 6-40: Interconnect Diagram for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project.................................................................................................................................... 77

Figure 6-41: Architecture Flow Diagram Definitions for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project .......................................................................................... 78

Figure 6-42: Applicable ITS Standards for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project ..................................................................................................................... 78

Figure 6-43: High Level Physical Architecture for the Advanced Rail Crossing Notification Project............ 79 Figure 6-44: High Level Physical Architecture for the Advanced Rail Crossing Notification Project............ 80 Figure 6-45: Agency Roles and Responsibilities for the Advanced Rail Crossing Notification Project ......... 80 Figure 6-46: Architecture Flow Diagram for the Advanced Rail Crossing Notification Project ..................... 80 Figure 6-47: Architecture Flow Diagram Definitions for the Advanced Rail Crossing Notification Project .. 81 Figure 6-48: Applicable ITS Standards for the Advanced Rail Crossing Notification Project ........................ 81 Figure 6-49: Architecture Flow Diagram for the Supplemental Emergency Vehicle Traffic Signal Preemption

Project........................................................................................................................................................ 82 Figure 6-50: High Level Physical Architecture Diagram for the Supplemental Emergency Vehicle Traffic

Signal Preemption Project ......................................................................................................................... 83 Figure 6-51: Agency Roles and Responsibilities for the Supplemental Emergency Vehicle Traffic Signal

Preemption Project .................................................................................................................................... 83 Figure 6-52: Architecture Flow Diagram for the Supplemental Emergency Vehicle Traffic Signal Preemption

Project........................................................................................................................................................ 83 Figure 6-53: Architecture Flow Diagram Definitions for the Supplemental Emergency Vehicle Traffic Signal

Preemption Project .................................................................................................................................... 84 Figure 6-54: Applicable ITS Standards for the Supplemental Emergency Vehicle Traffic Signal Preemption

Project........................................................................................................................................................ 84 Figure 6-55: Timeframe for Deployment of Regional Project Concepts ......................................................... 85 Figure 7-1: Physical Architecture Subsystems Classes .................................................................................... 88 Figure 7-2: Physical Architecture Sausage Diagram........................................................................................ 89 Figure 7-3: Physical Architecture “Interconnect” Diagram ............................................................................. 89 Figure 7-4: Physical Architecture “Architecture Flow” Diagram .................................................................... 90 Figure 7-5: Logical Architecture “Data Flow” Diagram.................................................................................. 91 Figure 7-6: Sausage Diagram with Applicable Regional Architecture Subsystems Highlighted .................... 92 Figure 7-7: Simplified Regional Interconnect Diagram ................................................................................... 98 Figure 7-8: Typical Emergency Management Interconnect Diagram .............................................................. 99 Figure 7-9: Typical Emergency Management Architecture Flow Diagram................................................... 100 Figure 7-10: Typical Traffic Management Interconnect Diagram ................................................................. 101 Figure 7-11: Typical Traffic Management Architecture Flow Diagram ........................................................ 102 Figure 7-12: Typical Maintenance Management Interconnect Diagram........................................................ 103 Figure 7-13: Typical Maintenance Management Architecture Flow Diagram............................................... 104 Figure 7-14: Typical Transit Management Interconnect Diagram ................................................................. 104 Figure 7-15: Typical Transit Management Architecture Flow Diagram........................................................ 105 Figure 7-16: Typical Parking Management Interconnect Diagram................................................................ 106 Figure 7-17: Typical Parking Management Architecture Flow Diagram....................................................... 106 Figure 7-18: Typical Information Service Provider Interconnect Diagram ................................................... 107 Figure 7-19: Typical Information Service Provider Architecture Flow Diagram .......................................... 107 Figure 7-20: Typical Archived Data Management Interconnect Diagram..................................................... 108 Figure 7-21: Typical Archived Data Management Architecture Flow Diagram............................................ 108 Figure 8-1: Lifecycle of ITS Standard Development ..................................................................................... 110 North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


v

Figure 8-2: Applicable Standards for North-Central Illinois Regional ITS Architecture .............................. 112 Figure 9-1: Outreach Interview Questionnaire - Commercial Vehicle Operations ........................................ 114 Figure 9-2: Outreach Interview Questionnaire - Emergency Management.................................................... 115 Figure 9-3: Outreach Interview Questionnaire - Freeway Management ........................................................ 116 Figure 9-4: Outreach Interview Questionnaire - Public Transportation ......................................................... 118 Figure 9-5: Outreach Interview Questionnaire - Traveler Information .......................................................... 120 Figure 9-6: Outreach Interview Questionnaire - Arterial Traffic Management ............................................. 121 Figure 9-7: Outreach Interview Questionnaire - Parking Management ......................................................... 123 Figure 9-8: Outreach Interview Questionnaire - Maintenance Operations..................................................... 124 Figure 11-1: Architecture Subsystems Table ................................................................................................. 126 Figure 11-2: Regional Architecture Subsystems Definitions Table ............................................................... 128 Figure 12-1: Architecture Terminators Table................................................................................................. 130 Figure 12-2: Regional Architecture Subsystems Definitions Table ............................................................... 131 Figure 13-1: Boone County 911 Center Interconnect Diagram...................................................................... 132 Figure 13-2: Boone County 911 Center Architecture Flow Diagram ............................................................ 133 Figure 13-3: Boone County Highway Department Dispatch Interconnect Diagram...................................... 134 Figure 13-4: Boone County Highway Department Dispatch Architecture Flow Diagram ............................ 135 Figure 13-5: City of Belvidere Department of Public Works Interconnect Diagram..................................... 136 Figure 13-6: City of Belvidere Department of Public Works Architecture Flow Diagram............................ 137 Figure 13-7: City of Belvidere Dispatch Interconnect Diagram .................................................................... 138 Figure 13-8: City of Belvidere Dispatch Architecture Flow Diagram ........................................................... 138 Figure 14-1: City of DeKalb Department of Public Works Interconnect Diagram........................................ 139 Figure 14-2: City of DeKalb Department of Public Works Architecture Flow Diagram............................... 140 Figure 14-3: City of DeKalb Dispatch Interconnect Diagram........................................................................ 141 Figure 14-4: City of DeKalb Dispatch Architecture Flow Diagram .............................................................. 141 Figure 14-5: City of Sycamore Department of Public Works Interconnect Diagram .................................... 142 Figure 14-6: City of Sycamore Department of Public Works Architecture Flow Diagram ........................... 142 Figure 14-7: City of Sandwich Department of Public Works Interconnect Diagram .................................... 143 Figure 14-8: City of Sandwich Department of Public Works Architecture Flow Diagram ........................... 143 Figure 14-9: DeKalb County 911 Center Interconnect Diagram.................................................................... 144 Figure 14-10: DeKalb County 911 Center Architecture Flow Diagram ........................................................ 145 Figure 14-11: DeKalb County Highway Department Dispatch Interconnect Diagram.................................. 146 Figure 14-12: DeKalb County Highway Department Dispatch Architecture Flow Diagram ........................ 147 Figure 14-13: Northern Illinois University Dispatch Interconnect Diagram.................................................. 148 Figure 14-14: Northern Illinois University Dispatch Architecture Flow Diagram ........................................ 148 Figure 14-15: Northern Illinois University Parking Interconnect Diagram ................................................... 149 Figure 14-16: Northern Illinois University Parking Architecture Flow Diagram .......................................... 149 Figure 15-1: Ogle County 911 Center Interconnect Diagram ........................................................................ 150 Figure 15-2: Ogle County 911 Center Architecture Flow Diagram ............................................................... 151 Figure 15-3: Ogle County Highway Department Dispatch Interconnect Diagram ........................................ 152 Figure 15-4: Ogle County Highway Department Dispatch Architecture Flow Diagram ............................... 153 Figure 16-1: City of Rockford Department of Public Works Interconnect Diagram ..................................... 154 Figure 16-2: City of Rockford Department of Public Works Architecture Flow Diagram............................ 155 Figure 16-3: City of Rockford Dispatch Interconnect Diagram..................................................................... 156 Figure 16-4: City of Rockford Dispatch Architecture Flow Diagram............................................................ 156 Figure 16-5: City of Rockford Maintenance Dispatch Interconnect Diagram ............................................... 157 Figure 16-6: City of Rockford Maintenance Dispatch Architecture Flow Diagram ...................................... 158 Figure 16-7: City of Rockford Parking Interconnect Diagram....................................................................... 159 Figure 16-8: City of Rockford Parking Architecture Flow Diagram ............................................................. 159 Figure 16-9: Illinois State Police – District 16 Interconnect Diagram ........................................................... 160 Figure 16-10: Illinois State Police – District 16Architecture Flow Diagram................................................. 160 North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


vi

Figure 16-11: Rockford Mass Transit Interconnect Diagram......................................................................... 161 Figure 16-12: Rockford Mass Transit Architecture Flow Diagram ............................................................... 161 Figure 16-13: Winnebago County 911 Center Interconnect Diagram............................................................ 162 Figure 16-14: Winnebago County 911 Center Architecture Flow Diagram .................................................. 163 Figure 16-15: Winnebago County Highway Department Dispatch Interconnect Diagram............................ 164 Figure 16-16: Winnebago County Highway Department Dispatch Architecture Flow Diagram .................. 165 Figure 17-1: IDOT Boone County Highway Department Dispatch Interconnect Diagram ........................... 167 Figure 17-2: IDOT Boone County Highway Department Dispatch Architecture Flow Diagram.................. 168 Figure 17-3: IDOT DeKalb County Highway Department Dispatch Interconnect Diagram ......................... 169 Figure 17-4: IDOT DeKalb County Highway Department Dispatch Architecture Flow Diagram................ 170 Figure 17-5: IDOT Ogle County Highway Department Dispatch Interconnect Diagram.............................. 171 Figure 17-6: IDOT Ogle County Highway Department Dispatch Architecture Flow Diagram..................... 172 Figure 17-7: IDOT Winnebago County Highway Department Dispatch Interconnect Diagram ................... 173 Figure 17-8: IDOT Winnebago County Highway Department Dispatch Architecture Flow Diagram......... 174 Figure 17-9: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control

Center and County Maintenance Agencies Interconnect Diagram.......................................................... 175 Figure 17-10: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and County Maintenance Agencies Architecture Flow Diagram ................................... 175 Figure 17-11: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Local Department of Public Works Offices Interconnection Diagram.................... 176 Figure 17-12: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Local Department of Public Works Offices Architecture Flow Diagram................ 176 Figure 17-13: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Emergency Management Agencies Interaction Diagram ........................................ 177 Figure 17-14: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Emergency Management Agencies Architecture Flow Diagram............................. 177 Figure 17-15: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and State Maintenance Agencies Interaction Diagram................................................... 178 Figure 17-16: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and State Maintenance Agencies Architecture Flow Diagram....................................... 178 Figure 17-17: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Transit Agencies Interconnect Diagram .................................................................. 179 Figure 17-18: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and Transit Agencies Architecture Flow Diagram ......................................................... 179 Figure 17-19: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and other Traffic Management Interconnect Diagram.................................................... 180 Figure 17-20: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center and other Traffic Management Architecture Flow Diagram .......................................... 180 Figure 17-21: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center - Generalized Operations Interconnect Diagram ............................................................ 181 Figure 17-22: Illinois Department of Transportation – District 2 Traffic Management and Maintenance

Control Center - Generalized Operations Architecture Flow Diagram ................................................... 181



vii

Executive Summary As the economy and population continue to expand in North-Central Illinois, demands on emergency management, traffic management, transit, maintenance and other agencies also expand. For decades, technology has rapidly enhanced the productivity and efficiency of many public services. Innovations in telecommunications, information technology, and sensor technology have lead to an increased use of tools, collectively called Intelligent Transportation Systems (ITS), to support various operational enhancements. While these tools can significantly improve services and productivity, considerable investment can be required. To optimize synergies between systems and reduce duplication of development efforts, planning for integration of systems can maximize investment, enhance agency relationships, and better serve the public. The planning exercise of establishing the framework is a process that is used to determine existing and future relationships between agencies and associated management systems on a regional basis. A comprehensive framework is commonly known as Regional ITS Architecture. The North-Central Illinois ITS Regional Architecture is comprised of stakeholder agencies contained within the four counties of Boone, Winnebago, DeKalb, and Ogle.

North-Central Illinois – Boone, Winnebago, DeKalb, and Ogle Counties The Regional Architecture was commissioned to look at the needs of the Illinois Transportation Department and local agencies and to identify how communications and data could be shared over a wide range of time horizons. The architecture process served as a planning tool and helped to bring about a thorough understanding of different stakeholder issues and clarify future opportunities to meet partner needs. Through the use of a Regional Architecture, enhanced interaction and integration of future technological infrastructure and resource sharing is anticipated.


1 ITS Architecture Report

As outlined by the U.S. Department of Transportation (USDOT), a regional architecture is also necessary to comply with the requirements of The Transportation Equity Act for the 21st Century (TEA-21). This requirement stipulates that all future ITS projects using federal funds must “conform” to the National ITS Architecture. The National ITS Architecture was developed by the USDOT to present a common framework for planning and integrating future intelligent transportation systems. This report contains a description of the project and how the regional architecture was developed. The primary report chapters are summarized as follows: Chapter 1: Introduction. This section includes a brief background on the need for a

North-Central Illinois ITS Architecture and the contents of the report. Chapter 2: Project Description. This section highlights information about the project

scope, including details on project stakeholders and characteristics of the region. Chapter 3: Development Process. This section details the efforts undertaken to develop

the regional architecture. Included with this chapter is information on outreach and design tasks.

Chapter 4: User Services Assessment. This section identifies how user needs were

recognized and summarizes the results. From the information collected on user needs, user services were also identified, as defined by the ITS National Architecture, and prioritized.

Chapter 5: Market Package Identification/Mapping. User services were used to identify

market packages. The different types of market packages identified are listed and explained.

Chapter 6: Project Concepts. Potential project concepts were developed and prioritized

by the stakeholders. This section identifies the highest priority concepts and gives a description of each including an overall project level schedule.

Chapter 7: System Architecture. The regional architecture is explained in detail. Typical

architecture flows and interconnects highlight how communication and data will be shared between various agencies.

Chapter 8: National ITS Standards. The standards that are applicable to the regional

architecture are highlighted along with a status of where they stand in the adoption process.

In addition to the main body of the report numerous appendices have been included. Several appendices include agency specific architecture diagrams.



1 Introduction

1.1 Project Overview As North-Central Illinois continues significant economic growth and development, the region is experiencing increased demand on transportation related infrastructure and resources. As the population continues to expand, demands on emergency management, traffic management, transit, maintenance and other agencies grow. In North-Central Illinois the response to this demand has ignited the desire to share information and improve the ability to communicate more effectively between agencies. In the past, sharing information was not always a priority. As such, past technology deployed was implemented with little thought as to how communication or information would be exchanged with other agency stakeholders (i.e., partner agencies, transportation system users, etc.). Future expansion or integration of existing or proposed software and hardware systems may be expensive and difficult but will most likely focus on the ability to share and exchange information between different agencies. With the development of the National Intelligent Transportation Systems (ITS) Architecture, a framework has been established to support future integration of a wide array of transportation related management systems. The process of establishing the framework, or architecture, is a planning exercise that is used to determine existing and future relationships between agencies and associated management systems on a regional basis and supports improved future information exchanges and communications. The North-Central Illinois ITS Regional Architecture is comprised of stakeholder agencies contained within the four counties of Boone, Winnebago, DeKalb, and Ogle. The Regional Architecture was commissioned to look at the needs of the Illinois Transportation Department and local agencies and to identify how communications and data could be shared over a wide range of time horizons. The architecture process served as a planning tool and helped to bring about a thorough understanding of different stakeholder issues and clarify future opportunities to meet partner needs. Through the use of Regional Architecture, enhanced interaction and integration of future technological infrastructure and resource sharing is anticipated. As outlined by the U.S. Department of Transportation (USDOT), a regional architecture is also necessary to comply with the requirements of The Transportation Equity Act for the 21st Century (TEA-21). This requirement stipulates that all future ITS projects using federal funds must “conform” to the National ITS Architecture. The National ITS Architecture was developed by the USDOT to present a common framework for planning and integrating future intelligent transportation systems. This project addresses both the desire for developing a long-term planning tool and the necessity of complying with the requirements of the federal mandate.

1.2 Purpose of Document On January 8, 2001 a Notice of Final Rule Making was issued implementing the requirements of Section 5206(e) of the Transportation Equity Act for the 21st Century (TEA-21). This section required federally funded ITS projects to conform to the National ITS Architecture. However, it recognized that not all elements of the National Architecture may be applicable for every



state, region or major metropolitan area, thus “Conformance with the National ITS Architecture is interpreted to mean the use of the National Architecture to develop a regional architecture, and the subsequent adherence of all ITS projects to that regional ITS architecture. This rule requires that the National ITS Architecture be used as a reference in developing a regional ITS architecture.”1 Thus, development of a “regional architecture” shows compliance with section 5206(e) and allows Federal funding for future ITS projects in North-Central Illinois. Apart from being required for Federal funding, a regional ITS architecture provides a useful planning reference as it gives insight into stakeholders needs during development and design phases of ITS projects. This documents represents the recommended Regional ITS Architecture for the North-Central Illinois Region.

1.3 Report Format and Outline This report contains a description of the project and how the regional architecture was developed. The primary report chapters are summarized as follows:

Chapter 2: Project Description. This section highlights information about the project scope, including details on project stakeholders and characteristics of the region. Chapter 3: Development Process. This section details the efforts undertaken to develop the regional architecture. Included with this chapter is information on outreach and design tasks. Chapter 4: User Services Assessment. This section identifies how user needs were recognized and summarizes the results. From the information collected on user needs, user services were also identified, as defined by the ITS National Architecture, and prioritized. Chapter 5: Market Package Identification/Mapping. User services were used to identify market packages. The different types of market packages identified are listed and explained. Chapter 6: Project Concepts. Potential project concepts were developed and prioritized by the stakeholders. This section identifies the highest priority concepts and gives a description of each, including an overall project level schedule. Chapter 7: System Architecture. The regional architecture is explained in detail. Typical architecture flows and interconnects highlight how communication and data will be shared between various agencies. Chapter 8: National ITS Standards. The standards that are applicable to the regional architecture are highlighted along with a status of where they stand in the adoption process.



1 January 8, 2001, U.S. Department of Transportation, Federal Highway Administration, 23 CFR Parts 655 and 940, FHWA Docket No. FHWA-99-5899 (http://www.its.dot.gov/aconform/archrule_final_1.htm)

2 Project Description The North-Central Illinois Regional ITS Architecture addresses issues surrounding existing and future planning of transportation related systems. It is intended to look at public and private agencies and address issues involving information and data sharing, system integration, and migration preparations. The project provides guidance to agencies on what data is currently being or will be generated in the future, who has interest in receiving the data, and how the data may be utilized to improve communications and operations.

2.1 Region Information The North-Central Illinois ITS Regional Architecture is comprised of stakeholder agencies contained within the four counties of Boone, Winnebago, DeKalb, and Ogle (Figure 2-1). Currently, approximately 1/2 Million individuals live and work within the region. The region includes over 2,193 sq. miles of land area and is home to many federal landmarks, historical sites, and state parks including Castle Rock State Park, White Pines and Lowden Parks. The region contains the City of Rockford, Illinois. Rockford is the 2nd largest city in Illinois and supports over 400,000 individuals within its metropolitan area. Significant attractions within the region are the many festivals held year round, including the Rockford Art Museum Festival, Scottish Highland Games, and the Festival of Lights.

Figure 2-1: North-Central Illinois - Boone, Winnebago, DeKalb, and Ogle Counties

2.2 Regional Stakeholders The identified regional stakeholders represent many different backgrounds and perform different transportation related functions. They are made up of public and private entities, which typically operate out of a control, dispatch, or other center of operations. Six categories of stakeholders identify roles and responsibilities of each regional stakeholder. The following briefly describes each category and lists the associated regional stakeholders.

Traffic Management: Agencies that operate roadway equipment and serve to improve transportation system operation efficiency and safety. Traffic management agencies typically coordinate the other agencies by relaying pertinent traffic conditions



and incidents and alerting the traveling public. Regional traffic management stakeholders include:

Illinois State Toll Highway Authority – Downers Grove Operations Area Illinois State Department of Transportation – District 2 City of Rockford Department of Public Works City of DeKalb Department of Public Works City of Sycamore Department of Public Works City of Sandwich Department of Public Works City of Belvidere Department of Public Works

Emergency Management: Agencies that operate in a public safety capacity, often coordinating efforts involving emergency response. Regional emergency management stakeholders include:

Illinois State Police – District 1 Illinois State Police – District 15 Illinois State Police – District 16 City of Rockford Dispatch City of Belvidere Dispatch City of DeKalb Dispatch Northern Illinois University Dispatch Boone County 911 Center DeKalb County 911 Center Ogle County 911 Center Winnebago County 911 Center

Information Service Provider: Agencies that collect and distribute transportation related information through various means to the traveling public, media, and other agencies required for operational purposes. Regional information service providers would include:

Illinois State Department of Transportation – District 1 Gateway Traveler Information Hub

Transit Management: Agencies that manage, operate, and maintain transit vehicle fleets and or coordinate other transportation service modes. Regional transit management stakeholders would include:

Rockford Mass Transit

Operations and Maintenance: Agencies that operate and manage maintenance vehicle fleets with responsibilities for emergency clean up, snow and ice removal, and annual upkeep of transportation facilities. Regional operations and maintenance stakeholders include:

IDOT Boone County Highway Department Dispatch IDOT DeKalb County Highway Department Dispatch IDOT Ogle County Highway Department Dispatch IDOT Winnebago County Highway Department Dispatch Boone County Highway Department Dispatch



DeKalb County Highway Department Dispatch Ogle County Highway Department Dispatch Winnebago County Highway Department Dispatch City of Rockford Maintenance Dispatch

Parking Management: Agencies operating and managing parking facilities supporting special events or general public parking needs. Regional parking management stakeholders include:

Northern Illinois University Parking City of DeKalb Parking City of Rockford Parking

Identification of each stakeholder’s function in the region further facilitates understanding and translation of agency needs into the regional architecture.

2.3 Project Concepts Development of a regional architecture incorporates near and long-term plans for facilitating data and information sharing between stakeholders. During the architecture development process, discussions with different agencies led to defining ideas or concepts for work that was determined to be critical to the region for the purpose of facilitating the sharing of data and information. Projects were then developed from each concept and further defined. The final result was to establish “project concepts” that comply with the completed regional architecture and address the stated critical needs of the stakeholders for the region. The final list of high priority project concepts identified by the stakeholders include the following:

Project 1: Traffic Management and Maintenance Control Center Project 2: Interstate Traffic Monitoring & Traveler Information Project 3: Advanced Signal Operations/Coordination & Surface Street Traffic

Monitoring Project 4: Agency Data Sharing Project 5: Winter Weather Maintenance Enhancements Project 6: Arterial Dynamic Message Signs & Dynamic Trailblazer Signing Project 7: Construction Work Zone Safety, Traffic Monitoring and Traveler

Information Project 8: Advanced Rail Crossing Notification System Project 9: Supplemental Emergency Vehicle Traffic Signal Preemption

A description of each project concept and its related architectures are presented in further detail in Chapter 6.0.



3 Development Process The process used to develop the Regional Architecture is illustrated in Figure 3-1. As shown, the development of the architecture starts with an outreach effort focused on determining existing and planned ITS deployments from input supplied by identified regional stakeholders. From that effort user needs were assessed and user services that could fill stakeholder needs were determined. Once user services were known, applicable market packages were identified along with critical project concepts. The information collected was then utilized to build a regional architecture that mapped market packages to user services and encompassed the critical project concepts. Finally, from the regional architecture, a list of National ITS standards necessary to deploy the architecture was identified.

Identify Relevant Market PackagesIdentify Relevant Market Packages

Inventory Existing Systems


Determine Current & Future Needs

and Services


and Services

Tailor Connections to Local Needs and

Conditions


Conditions

Review Individual Architecture FlowsReview Individual Architecture Flows

USER NEEDSUSER SERVICES


MARKET PACKAGESMARKET

PACKAGES

SYSTEM ARCHITECTURE

SYSTEM ARCHITECTURE

ITS STANDARDSITS STANDARDS

OUTREACHOUTREACH

Stak

ehol

der I

nput

Regional Architecture

Activity Process

Identify Relevant Market PackagesIdentify Relevant Market Packages




and Services


and Services


Conditions


Conditions

Review Individual Architecture FlowsReview Individual Architecture Flows



MARKET PACKAGESMARKET

PACKAGES

SYSTEM ARCHITECTURE

SYSTEM ARCHITECTURE

ITS STANDARDSITS STANDARDS

OUTREACHOUTREACH

Stak

ehol

der I

nput

Regional Architecture

Activity Process

Figure 3-1: Architecture Development Process

3.1 Stakeholder Outreach The outreach effort involved mainly one-on-one interviews with targeted stakeholders. The objectives of the interviews were to discuss the ITS program and how it might influence existing and planned system deployments. Over 50 stakeholder interviews were held, gathering information on each agency’s current and future information needs and what role the agency envisioned having with other local and regional partners. Information gathered was utilized for assessing user needs and how system integration may be handled in future system implementations between different agencies. Sample agency interview forms are presented in Chapter 9. Four workshops were also conducted to collectively discuss initial stakeholders needs and to review draft architecture diagrams (interconnect and architecture flow).



Identification of user needs was necessary for later development of a regional architecture that addressed both local and larger agency and transportation issues. Thus, individual agency interviews and larger workshop sessions helped to identify regional needs and future plans.

3.2 User Services The National ITS Architecture defines 31 different user services under seven service “bundles” or categories. The services represent the needs of users in a structured manner and provide a common language that can be used locally, regionally, or nationally to describe existing or desired functions. Service bundles identified by the stakeholders as needed or desired included the following:

Travel and Traffic Management Public Transportation Management Electronic Payment Emergency Management Information Management

Other bundles not currently recognized as needed by the targeted stakeholders included:

Advance Vehicle Safety Systems Commercial Vehicle Operations

A full description of these user services bundles and the individual user services are discussed in Section 4.0. User needs collected during outreach efforts were mapped to the 31 user services outlined by the National ITS Architecture. Once user services are identified, the process of associating appropriate market packages used in the development of an architecture can be completed.

3.3 Market Packages Market packages represent one or more equipment packages that work together to address a specific transportation service or need. The National ITS Architecture outlines a basic set of market packages intended to show how a system could be implemented to serve the needs of single or multiple agencies. The market packages are intended to indicate a representation of how market driven solutions might be assembled to address transportation related needs. Market packages, as defined in the National Architecture, are comprehensive solutions, which may not be necessary to implement in their entirety for a particular agency’s expressed need. Therefore, market packages are customized to more accurately portray the needs or services an agency desires. For the purpose of developing a regional architecture, user services direct what packages are applicable, and feedback from the stakeholders assists in customizing them to fit more tightly with desired needs.

3.4 Project Concepts Feedback collected from stakeholders is also used to identify near-term critical project concepts that should be considered prior to developing the regional architecture. As the regional architecture process unfolds, planned and future ITS projects emerge as critical or under development by differing stakeholders. Careful consideration of these projects insures



that they are accounted for in the architecture. There are currently 12 project concepts identified and accounted for in the regional architecture.

3.5 Architecture Design The regional architecture is developed based on the identification of appropriate market packages and critical project concepts. The architecture is a planning tool that depicts the potential for integration of various agency systems throughout the region and the data that is shared between them. The regional architecture design is based on the National ITS Architecture, but can be modified slightly to address issues not currently accounted for in the national model. In the current regional architecture a certain degree of modification was necessary to address regional concerns.

3.6 National Standards Once the regional architecture has been developed identification of applicable National ITS standards becomes necessary to insure integration of future systems. By recognizing these standards, agencies may be able to integrate existing facility deployments now with future system upgrades and expansions. To accomplish this task the appropriate standards are identified and presented to provide guidance as to which standards are appropriate for consideration based on the regional architecture.



4 User Services Assessment Stakeholder agencies were assessed through various means to ascertain what services they would require in order to fulfill existing and future needs. The bulk of the work was completed through interviews with the stakeholder agency’s managers and directors. Through the interview process concentration was made to isolate opinions and feedback from key Department heads, and gain insight on the future plans of the agency. In addition to the interviews, workshops were also held to build awareness and educate the stakeholders and policy makers on the value of ITS and how it could have a positive impact on their future plans and operations.

4.1 Agency Interviews Over 28 stakeholder agency interviews were held, gathering information on each agency’s current and future information needs and what role the agency envisioned having with other local and regional partners. Information gathered focused on the agency’s transportation related roles and priorities. Agencies were categorized as:

Commercial Vehicle Operation Emergency Management Freeway Management Public Transportation Traveler Information Arterial Traffic Management Parking Management Maintenance and Operation

Stakeholders ranged from local, county, and state departments, to private entities located in North-Central Illinois. The insight was utilized for assessing user needs and to determine what user services, as defined by the National ITS Architecture, were applicable. Samples of the forms used during the agency interview are presented in Chapter 9. A list of agencies that were interview is presented in Chapter 10.

4.2 Overview of User Services The National ITS Architecture currently defines 31 different user services. To develop the regional architecture, stakeholder needs were identified and associated with the various user services. Figure 4-1 highlights the common user identified needs.



Regional Stakeholder Needs

Objectives

1. Enhance Transportation Mobility and Accessibility

a. Improve accessibility and availability of travel information to tourists, commercial vehicle operators, emergency services, transit users, and other users of all transportation facilities.

b. Simplify scheduling and fee collection procedures for operators and users of intermodal and parking facilities.

c. Reduce the variability and number of actions necessary to use public transportation facilities.

2. Enhance Transportation Productivity

a. Reduce travel delay and increase the reliability and predictability of moving people and goods for all transportation users.

b. Reduce the operational costs to operators incurred from inefficient transportation facilities.

c. Reduce costs to users by improving the equity of fee collection. d. Reduce scheduling and processing delays and costs to users and

operators associated with the regulation of vehicles. e. Reduce the costs and improve the quality of data collection for

transportation system planning, use, operations, maintenance, and installations.

3. Improve Transportation Safety a. Improve the tracking of hazardous material movements, the response to and migration of the effects due to loss of containment incidents.

b. Reduce the number of motor vehicle collisions, associated injuries and fatalities.

c. Improve the average response of emergency services. d. Enhance personal security on all modes of transportation. e. Ensure responding personnel safety. f. Reduce crash severity. g. Support transportation facility modifications to support shift in driving

population (i.e., large population of older drivers) 4. Enhance the Quality and Efficiency of Transportation Travel

a. Reduce time delay costs associated with congestion. b. Optimize the operational efficiency of goods and people movement on

existing facilities. c. Increase average vehicle occupancy. d. Reduce rate of growth of vehicle miles traveled. e. Reduce time lost in intermodal interchange. f. Expand and improve the delivery of traveler information. g. Improve traffic management. h. Reduce delays, crashes, and congestion. i. Enhance special event traveler experiences. j. Reduce vehicle emissions. k. Enhance roadway maintenance including enhanced snow and ice

removal. 5. Develop a Transportation Management System that Most Effectively Supports the Optimal Deployment of Appropriate Technologies

a. Establish a framework for a Traffic Management System that: Advances the Illinois ITS Program and is compatible with the

National ITS Program. Advances the deployment and integration of technology.

b. Establish an ITS Architecture that: Is open and adaptable to meet future architecture needs. Is consistent with emerging national standards. Involves and unites a wide range of stakeholders in planning for

ITS. Supports flexibility in tailoring ITS deployment and operations to

local requirements. Achieves integration of ITS systems and components. Enables information sharing among stakeholders. Facilitates future, cost-effective ITS expansion.



Regional Stakeholder Needs

Objectives

Provides for future interoperability of key ITS services at a state, regional, and national level.

6. Support the Enhancement of Transportation Incident Management

a. Implement a sustainable system of interagency relationships and coordination

b. Improve the ability and reduce the amount of time to detect, verify, respond to, and remove traffic incidents

c. Identify supplemental funding resources d. Foster stakeholder / public awareness and support e. Improve the ability to identify, respond, remove and/or mitigate effects

of traffic incidents. 7. Support Enhanced Sharing of Information Among All Stakeholders

a. Encourage Center to Center information sharing Public Works Law Enforcement / Public Safety Traffic Management

b. Use technology to assist in the distribution of project related information c. Conduct productive, routine project meetings

Figure 4-1: North-Central Illinois ITS Program User Needs and Objectives

The National ITS Architecture has established seven categories or “Service Bundles” to assist in grouping the user services. Grouping various user services into bundles provides a way of associating services that contain common infrastructure elements or management components. Figure 4-2 illustrates how the 31 user services are grouped under the National ITS Architecture’s 7 service bundles. Furthermore, Figure 4-3 on the subsequent pages describes the 31 user services using definitions adopted from National ITS Architecture.



User Services Bundles USER SERVICE BUNDLE: TRAVEL AND TRAFFIC MANAGEMENT 1. Pre-Trip Travel Information 2. En-Route Driver Information 3. Route Guidance 4. Ride Matching And Reservation 5. Travel Services Information 6. Traffic Control 7. Incident Management 8. Travel Demand Management 9. Emissions Testing And Mitigation 10. Highway-Rail Intersection USER SERVICE BUNDLE: PUBLIC TRANSPORTATION MANAGEMENT 1. Public Transportation Management 2. En-Route Transit Information 3. Personalized Public Transit 4. Public Travel Safety USER SERVICE BUNDLE: ELECTRONIC PAYMENT 1. Electronic Payment Services USER SERVICE BUNDLE: COMMERCIAL VEHICLE OPERATIONS 1. Commercial Vehicle Electronic Clearance 2. Automated Roadside Safety Inspection 3. Onboard Safety Monitoring 4. Commercial Vehicle Administrative Processes 5. Hazardous Material Incident Response 6. Commercial Fleet Management USER SERVICE BUNDLE: EMERGENCY MANAGEMENT 1. Emergency Notification And Personal Safety 2. Emergency Vehicle Management USER SERVICE BUNDLE: ADVANCED VEHICLE SAFETY SYSTEMS 1. Longitudinal Collision Avoidance 2. Lateral Collision Avoidance 3. Intersection Collision Avoidance 4. Vision Enhancement For Crash Avoidance 5. Safety Readiness 6. Pre-Crash Restraint Deployment 7. Automated Vehicle Operation USER SERVICE BUNDLE: INFORMATION MANAGEMENT 1. Archived Data Function

Figure 4-2: User Services Grouped by Service Bundles



User Services Bundles USER SERVICE BUNDLE: TRAVEL AND TRAFFIC MANAGEMENT 1. Pre-Trip Travel Information Definition: Pre-Trip Travel Information (PTTI) assists travelers in making mode choices, travel time estimates, and route decisions prior to trip departure. Four major functions: (1) Available Services Information (2) Current Situation Information (3) Trip Planning Service (4) User Access 2. En-Route Driver Information Definition: En-Route Driver Information (DI) provides vehicle drivers with information, while en-route, which will allow alternative routes to be chosen for their destination. Two major functions: (1) Driver Advisory (2) In-vehicle Signing 3. Route Guidance Definition: Route Guidance provides travelers with directions to selected destinations. Four major functions: (1) Provide Directions (2) Static Mode (3) Real-Time Mode (4) User Interface 4. Ride Matching And Reservation Definition: Ride Matching and Reservation provides travel users with information on rideshare providers. Three major functions: (1) Rider Request (2) Transportation Provider Services (3) Information Processing (includes provider billing service) 5. Travel Services Information Definition: Traveler Services Information provides travelers with service and facility data for the purpose of assisting prior to embarking on a trip or after the traveler is underway. 6. Traffic Control Definition: Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions: (1) Traffic Flow Optimization (2) Traffic Surveillance (3) Control Function (4) Provide Information Includes control of network signal systems with eventual integration of freeway control. 7. Incident Management Definition: Incident Management identifies incidents, formulates response actions, and supports initiation and ongoing coordination of response actions. Six major functions: (1) Scheduled Planned Incidents (2) Identify Incidents (3) Formulate response Actions (4) Support Coordinated Implementation of Response Actions (5) Support Initialization of Response to Actions (6) Predict Hazardous Conditions 8. Travel Demand Management Definition: Travel Demand Management will generates and communicates management and control strategies to support and facilitate implementation of TDM programs, policies and regulations. Two major functions: (1) Increase Efficiency of Transportation System (2) Provide Wide Variety of Mobility Options 9. Emissions Testing And Mitigation Definition: The ETAM function provides state and local governments with the capability to enhance their air quality control strategies.



User Services Bundles 10. Highway-Rail Intersection Definition: The Highway-Rail Intersection (HRI) function is used to control highway and rail traffic in at-grade HRIs. Two sub-services: (1) Standard Speed Rail Subservice which is applicable to light rail transit, commuter rail and heavy rail trains with operational speeds up to 79 miles per hour (MPH) (2) High Speed Rail Subservice which is applicable to all passenger and freight trains with operational speeds from 80 to 125 MPH USER SERVICE BUNDLE: PUBLIC TRANSPORTATION MANAGEMENT 1. Public Transportation Management Definition: The use of technology to manage public transportation infrastructure and services. 2. En-Route Transit Information Definition: En-Route Transit Information provides travelers with real-time transit and high-occupancy vehicle information allowing travel alternatives to be chosen once the traveler is en-route. Three major functions: (1) Information Distribution (2) Information Receipt (3) Information Processing 3. Personalized Public Transit Definition: Personal public transit (para-transit) that uses technology to optimize fleet operations through efficient allocation of resources. 4. Public Travel Safety Definition: The Public Travel Security (PTS) function creates an environment of safety in public transportation. USER SERVICE BUNDLE: ELECTRONIC PAYMENT 1. Electronic Payment Services Definition: Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions: (1) Electronic Toll Collection (2) Electronic Fare Collection (3) Electronic Parking Payment (4) Electronic Payment Services Integration USER SERVICE BUNDLE: COMMERCIAL VEHICLE OPERATIONS 1. Commercial Vehicle Electronic Clearance Definition: Provides the capability to provide clearance to commercial vehicles at ports of entry, inspection stations, weigh stations and toll booths. 2. Automated Roadside Safety Inspection Definition: Provides the capability for each individual vehicle's or carrier's participation in the process to be on a voluntary safety inspection basis. 3. Onboard Safety Monitoring Definition: Provides monitoring and warnings of safety problems. Of primary importance is to inform the driver, as soon as possible, of any problem that has been detected. Of secondary importance is notifying the carrier of detected safety problems. Last in importance is the notification of appropriate enforcement agencies. 4. Commercial Vehicle Administrative Processes Definition: Consists of 3 subservices including Electronic Purchase Of Credentials, Automated Mileage and Fuel Reporting and Auditing, and International Border Electronic Clearance. 5. Hazardous Material Incident Response Definition: Supports efficient management during the notification and mitigation of HAZMAT incidents. 6. Commercial Fleet Management Definition: Consists of more efficient management of a vehicle fleet through sharing/integration of real-time transportation conditions information. USER SERVICE BUNDLE: EMERGENCY MANAGEMENT 1. Emergency Notification And Personal Safety Definition: provides for the faster notification to emergency services when travelers are involved in an incident. 2. Emergency Vehicle Management Definition: Consists of more efficient management of a vehicle fleet through sharing/integration of real-time transportation conditions information and/or utilization of supplemental traffic signal equipment. USER SERVICE BUNDLE: ADVANCED VEHICLE SAFETY SYSTEMS



User Services Bundles 1. Longitudinal Collision Avoidance Definition: Consists of technology that assists in minimizing the potential for head-on and rear-end vehicle collisions. 2. Lateral Collision Avoidance Definition: Consists of technology that assists in minimizing the potential for sideswipe and fixed object vehicle collisions. 3. Intersection Collision Avoidance Definition: Consists of technology that assists in minimizing the potential for intersection vehicle collisions. 4. Vision Enhancement For Crash Avoidance Definition: Consists of technology that assists motorists identify hazardous conditions that are typically not viewable. 5. Safety Readiness Definition: Consists of technology that advises motorists to take corrective actions when hazardous conditions are present. 6. Pre-Crash Restraint Deployment Definition: Consists of an automatic activation system that detects an impending collision with a moving or a stationary object prior to crash impact. 7. Automated Vehicle Operation Definition: Consists of completely or partially automated vehicles and supporting roadway infrastructure. USER SERVICE BUNDLE: INFORMATION MANAGEMENT 1. Archived Data Function Definition: The Archived Data User Service provides the historical data archive repositories and controls archiving functionality for all ITS data with five major functions: 1) Operational Data Control function to manage operations data integrity 2) Data Import and Verification function to acquire historical data from the Operational Data Control function 3) Automatic Data Historical Archive function for permanent data archiving 4) Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities 5) ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval

Figure 4-3: User Service Definitions Table

4.3 Mapping User Needs to User Services To facilitate the architecture development process, identification of applicable user services is necessary. Recognizing applicable user services leads to the identification of related Market Packages to support further refinement of the regional ITS Architecture. To identify what user services are applicable to the region, user needs, as expressed during the stakeholder interviews, must be mapped to the 31 different user services. For this purpose, each user need was reviewed and a determination made as to which user service(s) would address that need if the service was deployed. If a user service was identified as addressing a user need, it was mapped to that need. It is important to note that a user need may be addressed by more than one user service and, conversely, a user service may address more than a single user need. Figure 4-4 highlights the results of the mapping process with stakeholder needs previously shown in Figure 4-1: North-Central Illinois ITS Program User Needs and Objectives.



User Services Stakeholder Needs Match USER SERVICE BUNDLE: TRAVEL AND TRAFFIC MANAGEMENT

Pre-trip travel information 1a, 2a, 4a, 4f, 4i, 4j En-route driver Information 1a, 2a, 4a, 4i, 4j Route guidance 1a, 2a, 4a, 4i, 4j Ride matching and reservation 4c Travel services information Traffic control 2a, 2b, 4a, 4b, 4h, 4i, 4j Incident management 2a, 2b, 3a, 3c, 4a, 4h, 4i, 4j, 6a, 6b, 6e Travel demand management 2a Emissions testing and mitigation 4j Highway-rail Intersection 3b, 3f USER SERVICE BUNDLE: PUBLIC TRANSPORTATION MANAGEMENT

Public transportation management 1a, 1b, 1c, 2a, 2b, 4d, 4i En-route transit information 1a, 4i Personalized public transit 1a, 2a Public travel safety 3d, 4i USER SERVICE BUNDLE: ELECTRONIC PAYMENT

Electronic payment services 1b, 2b USER SERVICE BUNDLE: COMMERCIAL VEHICLE OPERATIONS

Commercial vehicle electronic clearance 1b, 2b, 4b Automated roadside safety inspection 2b, 3b Onboard safety monitoring 3b Commercial vehicle administrative processes 1b, 2b Hazardous material incident response 3a, 3c Commercial fleet management 1b, 2a, 2b, 3b USER SERVICE BUNDLE: EMERGENCY MANAGEMENT

Emergency notification and personal safety 3c, 3d, 3e Emergency vehicle management 3c, 2b USER SERVICE BUNDLE: ADVANCED VEHICLE SAFETY SYSTEMS

Longitudinal collision avoidance Lateral collision avoidance Intersection collision avoidance Vision enhancement for crash avoidance Safety readiness Pre-crash restraint deployment Automated vehicle operation USER SERVICE BUNDLE: INFORMATION MANAGEMENT

Archived data function 2e, 7a, 7b

Advanced Vehicle Safety Systems beyond scope of project. Automakers are primary

developer.

Figure 4-4: User Services Mapped to Stakeholder Needs



4.4 Regional Architecture User Services The mapping of users needs to user services aided in understanding which of the 31 user services are important for the region. Figure 4-5 shows the relevant regional user services and presents them grouped under their respective service bundle.

Applicable User Services USER SERVICE BUNDLE: TRAVEL AND TRAFFIC MANAGEMENT Pre-Trip Travel Information En-Route Driver Information Route Guidance Ride Matching And Reservation Traffic Control Incident Management Travel Demand Management Emissions Testing And Mitigation Highway-Rail Intersection

USER SERVICE BUNDLE: PUBLIC TRANSPORTATION MANAGEMENT Public Transportation Management En-Route Transit Information Personalized Public Transit Public Travel Safety USER SERVICE BUNDLE: ELECTRONIC PAYMENT Electronic Payment Services USER SERVICE BUNDLE: COMMERCIAL VEHICLE OPERATIONS Commercial Vehicle Electronic Clearance Automated Roadside Safety Inspection Onboard Safety Monitoring Commercial Vehicle Administrative Processes Hazardous Material Incident Response Commercial Fleet Management USER SERVICE BUNDLE: EMERGENCY MANAGEMENT Emergency Notification And Personal Safety Emergency Vehicle Management USER SERVICE BUNDLE: INFORMATION MANAGEMENT Archived Data Function

Figure 4-5: List of Applicable User Services for Region

As a result of the mapping process some user services were determined to be unnecessary, as they did not address any stated user need at this time. Examples of user services not applicable for the region include all services under the advanced vehicle safety systems user service bundle and the travel services information. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


5 Market Packages Identification/Mapping Market packages represent how real-world market forces influence the creation of common solutions for specific transportation needs. Market packages in the physical world are combinations of hardware, software, and service solutions developed and fueled by an industry need for a readily available and deployable solution. In the National ITS Architecture market packages are conceptual representations of solutions to different transportation industry needs. The market packages in the National Architecture represent a logical assembly of different transportation elements that are connected by data flows detailing where information is generated and how it is routed to address a specific need. The typical elements that comprise a market package represent centers, vehicles, travelers, and roadway components with interconnections showing communication paths and data exchanges between them. Since market packages under the National ITS Architecture are based on concepts of how market forces may respond to the needs of the transportation industry they are not intended to be rigid solutions but instead are guidelines, which can be customized to reflect specific requirements. The National ITS Architecture outlines 63 market packages designed to address needs or issues experienced now or foreseen as needed in the future. Samples of those needs where market packages have been created include transit vehicle tracking, freeway and surface street control, and incident management. Although market packages have been created to address specific issues they can be deployed independently or in combination. Thus, it is likely that in any given region several market packages could be envisioned as integrated and working in combination. As stated previously input collected from North-Central Illinois regional stakeholders, assisted in identifying user needs. Under the National ITS Architecture user services are directly tied to market packages. Thus, user services can be mapped to market packages that are understood as potential solutions to stakeholder needs. Furthermore, by identifying the applicable regional market packages through the mapping process, stakeholders gain additional insight into procurement requirements that will bring about better integration within the region.

5.1 Market Packages Overview As previously stated, there are currently 63 basic market packages defined in the National ITS Architecture. They are grouped under seven categories identifying their impact on more specific transportation industry segments. For reference, the seven categories used by the National ITS Architecture to group and classify market packages are:

Advanced Public Transportation Systems (APTS) Advanced Traveler Information Systems (ATIS) Advanced Traffic Management Systems (ATMS) Advance Vehicle Safety Systems (AVSS) Commercial Vehicle Operations (CVO) Emergency Management (EM) Archived Data Management (AD)

Figure 5-1 below identifies and associates the 63 market packages from the National Architecture with the appropriate category.



Market Package Market Package Name

ADVANCED PUBLIC TRANSPORTATION MANAGEMENT SYSTEMS (APTS) 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 APTS7 Multi-modal Coordination APTS8 Transit Traveler Information

ADVANCED TRAVLER INFORMATION SYSTEMS (ATIS) ATIS1 Broadcast Traveler Information ATIS2 Interactive Traveler Information ATIS3 Autonomous Route Guidance ATIS4 Dynamic Route Guidance ATIS5 ISP Based Route Guidance ATIS6 Integrated transportation Management/Route Guidance ATIS7 Yellow Pages and Reservation ATIS8 Dynamic Ridesharing ATIS9 In Vehicle Signing

ADVANCED TRAFFIC MANAGEMENT SYSTEMS (ATMS) ATMS1 Network Surveillance ATMS2 Probe Surveillance ATMS3 Surface Street Control ATMS4 Freeway Control ATMS5 HOV Lane Management ATMS6 Traffic Information Dissemination ATMS7 Regional Traffic Control ATMS8 Incident Management System ATMS9 Traffic Forecast and Demand Management

ATMS10 Electronic Toll Collection ATMS11 Emissions Monitoring and Management ATMS12 Virtual TMC and Smart Probe Data ATMS13 Standard Railroad Grade Crossing ATMS14 Advanced Railroad Grade Crossing ATMS15 Railroad Operations Coordination ATMS16 Parking Facility Management ATMS17 Reversible Lane Management ATMS18 Road Weather Information System ATMS19 Regional Parking Management

ADVANCED VEHICLE SAFETY SYSTEMS (AVSS) AVSS1 Vehicle Safety Monitoring AVSS2 Driver Safety Monitoring AVSS3 Longitudinal Safety Warning AVSS4 Lateral Safety Warning AVSS5 Intersection Safety Warning AVSS6 Pre-Crash Restraint Deployment AVSS7 Driver Visibility Improvement AVSS8 Advanced Vehicle Longitudinal Control AVSS9 Advanced Vehicle Lateral Control




AVSS10 Intersection Collision Avoidance AVSS11 Automated Highway System

COMMERCIAL VEHICLE OPERATIONS (CVO) CVO1 Fleet Administration CVO2 Freight Administration CVO3 Electronic Clearance CVO4 CV Administrative Processes CVO5 International Border Electronic Clearance CVO6 Weigh-In-Motion CVO7 Roadside CVO Safety CVO8 Onboard CVO Safety CVO9 CVO Fleet Maintenance

CVO10 HAZMAT Management EMERGENCY MANAGEMENT SYSTEMS (EM)

EM1 Emergency Response EM2 Emergency Routing EM3 Mayday Support

ARCHIVED DATA MANAGEMENT SYSTEMS (AD) AD1 ITS Data Mart AD2 ITS Data Warehouse AD3 ITS Virtual Data Warehouse

Figure 5-1: National ITS Architecture Market Packages Grouped by Category

5.2 Mapping User Services to Market Packages Previous documents generated for the National ITS Architecture have detailed the relationship between the 63 different market packages and 31 identified user services. In the development process used for the North-Central Illinois Regional Architecture stakeholder user services were mapped to applicable market packages. The process establishes the needed regional market packages that are later used to develop the regional system architecture (Chapter 7). Figure 5-2 indicates which market packages satisfy each user service.2



2 Adopted from Table 3-1: “Market Package to User Service Relationships”, National ITS Architecture Team, Market Packages: A Tool for Viewing, Accessing, and Utilizing the National ITS Architecture, Federal Highway Administration, U.S. Department of Transportation, Washington D.C., December 1999, page 81.

Market Packages 1.1

– Pr

e-Tr

ip T

rave

l Inf

orm

atio

n

1.2

– En

-Rou

te D

river

Info

rmat

ion

1.3

– Ro

ute

Gui

danc

e

1.4

– Ri

de M

atch

ing

and

Res

erva

tion

1.5

– Tr

avel

er S

ervi

ce In

form

atio

n

1.6

– Tr

affic

Con

trol

1.7

– In

cide

nt M

anag

emen

t

1.8

– Tr

avel

Dem

and

Man

agem

ent

1.9

– Em

issio

ns T

estin

g an

d M

itiga

tion

1.10

– H

ighw

ay –

Rai

l Int

erse

ctio

n

2.1

– Pu

blic

Tra

nspo

rtatio

n M

anag

emen

t

2.2

– En

-Rou

te T

rans

it In

form

atio

n

2.3

– Pe

rson

aliz

ed P

ublic

Tra

nsit

2.4

– Pu

blic

Tra

vel S

ecur

ity

3.1

– El

ectro

nic

Paym

ent S

ervi

ce

4.1

– Co

mm

erci

al V

ehic

le E

lect

roni

c C

lear

ance

4.2

– A

utom

ated

Roa

dsid

e Sa

fety

Insp

ectio

n

4.3

– O

n-B

oard

Saf

ety

Mon

itorin

g

4.4

– Co

mm

erci

al V

ehic

le A

dmin

istra

tive

Proc

ess

4.5

– H

azar

dous

Mat

eria

l Inc

iden

t Res

pons

e

4.6

– Co

mm

erci

al F

leet

Man

agem

ent

5.1

– Em

erge

ncy

Not

ifica

tion

and

Pers

onal

Sec

urity

5.2

– Em

erge

ncy

Veh

icle

Man

agem

ent

6.1

– Lo

ngitu

dina

l col

lisio

n A

void

ance

6.2

– La

tera

l Col

lisio

n A

void

ance

6.3

– In

ters

ectio

n C

ollis

ion

Avo

idan

ce

6.4

– V

ision

Enh

ance

men

t For

Cra

sh A

void

ance

6.5

– Sa

fety

Rea

dine

ss

6.6

– Pr

e-C

rash

Res

train

t Dep

loym

ent

6.7

– A

utom

ated

Veh

icle

Ope

ratio

n

7.1

– A

rchi

ved

Dat

a Fu

nctio

n

Network Surveillance • Probe Surveillance • Surface Street Control • • • Freeway Control • • • HOV Lane Management • • Traffic Information Dissemination • • Regional Traffic Control • Incident Management System • Traffic Forecast and Demand Management • • Electronic Toll Collection • • Emissions Monitoring and Management • Virtual TMC and Smart Probes • • Standard Railroad Grade Crossing • Advanced Railroad Grade Crossing • Railroad Operations Coordination • Parking Facility Management • • Reversible Lane Management • • Road Weather Information System • • •

AT

MS

Regional Parking Management • • Transit Vehicle Tracking • • • • Transit Fixed-Route Operations • • Demand Response Transit Operations • • • Transit Passenger and Fare Management • • Transit Security • • Transit Maintenance • Multi-modal Coordination • • •

APT

S

Transit Traveler Information • • • Broadcast Traveler Information • • • Interactive Traveler Information • • • • • • • Autonomous Route Guidance • • Dynamic Route Guidance • • • • • ISP Based Route Guidance • • • • Integrated Trans. Management/Route Guidance • • •

Yellow Pages and Reservation • • • • • • Dynamic Ride Sharing • • • • • • • •

AT

IS

In Vehicle Signing • • • Vehicle Safety Monitoring • • Driver Safety Monitoring • Longitudinal Safety Warning • • Lateral Safety Warning • • Intersection Safety Warning • • • Pre-Crash Restraint Deployment • •

AV

CSS

Driver Visibility Improvement • gFleet Administration • • Freight Administration • Electronic Clearance • • CV Administrative Processes • • International Border Electronic Clearance • • Weigh-In- Motion • Roadside CVO Safety • • On-Board CVO Safety • CVO Fleet Management • • •

CV

O

HAZMAT Management • • • Emergency Response • • Emergency Routing • • E

M

Mayday Support • • ITS Data Mart •ITS Data Warehouse •A

D

ITS Virtual Data Warehouse •

Figure 5-2: Market Package to User Service Relationship



5.3 Identified Market Packages for North-Central Illinois Through the mapping process, at least 29 of the 63 potential market packages are identified as potentially applicable to the North-Central Illinois region. Based on previous stakeholder needs, identified user services were used to select market packages that if deployed would satisfy the original stakeholders needs. Figure 5-3 highlights the market packages applicable to the North-Central Illinois regional architecture.


ADVANCED PUBLIC TRANSPORTATION MANAGEMENT SYSTEMS (APTS) 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 APTS7 Multi-modal Coordination APTS8 Transit Traveler Information

ADVANCED TRAVLER INFORMATION SYSTEMS (ATIS) ATIS1 Broadcast Traveler Information ATIS2 Interactive Traveler Information ATIS5 ISP Based Route Guidance

ADVANCED TRAFFIC MANAGEMENT SYSTEMS (ATMS) ATMS1 Network Surveillance ATMS3 Surface Street Control ATMS4 Freeway Control ATMS6 Traffic Information Dissemination ATMS7 Regional Traffic Control ATMS8 Incident Management System

ATMS10 Electronic Toll Collection ATMS13 Standard Railroad Grade Crossing ATMS14 Advanced Railroad Grade Crossing ATMS16 Parking Facility Management ATMS18 Road Weather Information System ATMS19 Regional Parking Management

COMMERCIAL VEHICLE OPERATIONS (CVO) CVO10 HAZMAT Management

EMERGENCY MANAGEMENT SYSTEMS (EM) EM1 Emergency Response EM2 Emergency Routing

ARCHIVED DATA MANAGEMENT SYSTEMS (AD) AD1 ITS Data Mart AD2 ITS Data Warehouse AD3 ITS Virtual Data Warehouse

Figure 5-3: Identified Regional Market Packages

Each of the market packages identified as applicable to the North-Central Illinois Regional Architecture are explained and illustrated below. Each has also been grouped, for additional reference, under their respective categories established by the National ITS Architecture.



5.3.1 Advanced Public Transportation System Market Packages Advance Public Transportation System (APTS) market packages address select needs and issues surrounding the public transportation industry. Issues such as locating, monitoring, operating, and maintaining vehicles are undertaken. There are eight market packages identified under the National ITS Architecture, all of which all apply to the North-Central Illinois Region. A description and diagram detail each package is shown below.

APTS01 - Transit Vehicle Tracking: This market package provides for an Automated Vehicle Location System to track the transit vehicle’s real time schedule adherence and updates the transit system’s schedule in real-time. Vehicle position may be determined either by the vehicle (e.g., through GPS) and relayed to the infrastructure or may be determined directly by the communications infrastructure. A two-way wireless communication link with the Transit Management Subsystem is used for relaying vehicle position and control measures. Fixed route transit systems may also employ beacons along the route to enable position determination and facilitate communications with each vehicle at fixed intervals. The Transit Management Subsystem processes this information, updates the transit schedule and makes real-time schedule information available to the Information Service Provider Subsystem via a wireline link.

TransitManagement

Transit Center Trackingand Dispatch

Transit Vehicle

On-board TripMonitoring

InformationService Provider

transit and fareschedules

transit informationrequest

transit vehiclelocation data

Vehicle

vehiclelocation

transit vehicle schedule performance

Vehicle LocationDetermination

Figure 5-4: APTS01 - Transit Vehicle Tracking Market Package

APTS02 - Transit Fixed-Route Operations: This market package performs automatic driver assignment and monitoring, as well as vehicle routing and scheduling for fixed-route services. This service uses the existing AVL database as a source for current schedule performance data, and is implemented through data processing and information display at the transit management subsystem. This data is exchanged using the existing wireline link to the information service provider where it is integrated with that from other transportation modes (e.g. rail, ferry, air) to provide the public with integrated and personalized dynamic schedules.



p

TransitManagement

Transit Center Fixed Route Operations

Transit Vehicle

On Board Fixed Route Schedule Management




driver instructions

traffic information

for transit

Transit Garage Operations

Transit Driver

route assignment

transit driver

availability

TrafficManagement

transit vehicleschedule performance

Figure 5-5: APTS02 - Transit Fixed-Route Operations Market Package

APTS03 - Demand Response Transit Operations: This market package performs automatic driver assignment and monitoring as well as vehicle routing and scheduling for demand response transit services. This package uses the existing AVL database to monitor current status of the transit fleet and supports allocation of these fleet resources to service incoming requests for transit service while also considering traffic conditions. The Transit Management Subsystem provides the necessary data processing and information display to assist the transit operator in making optimal use of the transit fleet. The Information Service Provider Subsystem may either be operated by the transit management center or be independently owned and operated by a separate service provider. In the first scenario, the traveler makes a direct request to a specific paratransit service. In the second scenario, a third party service provider determines the paratransit service is a viable means of satisfying a traveler’s request and uses wireline communications to make a reservation for the traveler.



TransitManagement

Transit Center Paratransit Operations

Transit Vehicle

On-Board ParatransitOperations


transit vehicle passenger and use data

driver instructions

Transit GarageOperations

selected routes

demand responsivetransit plan

traffic informationfor transit

Transit Driver

route assignment

transit driver

availability

TrafficManagement

InformationServiceProvider

demand responsivetransit request

transit information request

Figure 5-6: APTS03 - Demand Response Transit Operations Market Package

APTS04 - Transit Passenger and Fare Management: This market package allows for the management of passenger loading and fare payments onboard vehicles using electronic means. The payment instrument may be either a stored value or credit card. This package is implemented with sensors mounted on the vehicle to permit the driver and central operations to determine vehicle loads, and readers located either in the infrastructure or onboard the transit vehicle to allow fare payment. Data is processed, stored, and displayed on the transit vehicle and communicated as needed to the Transit Management Subsystem using existing wireless infrastructure.

Remote TravelerSupport

TransitManagement

Transit Center Fare and Load Mgmt

Transit Vehicle

On-Board TransitFare and Load Mgmt


transit requestconfirmation


transit vehicle passenger and use data

bad tag list

Remote TransitFare Management

transit farepayment

request

transit fare payment responses

PaymentInstrument

paymentrequest forpayment

FinancialInstitution

paymentrequest

transactionstatus

EnforcementAgency

violationnotification

payment

request for payment

fare and payment status

Figure 5-7: APTS04 - Transit Passenger and Fare Management Market Package

APTS05 - Transit Security:



This market package provides for the physical security of transit passengers. An onboard security system is deployed to perform surveillance and warn of potentially hazardous situations. Public areas (e.g. stops, park and ride lots, stations) are also

monitored. Information is communicated to the Transit Management Subsystem using the existing or emerging wireless (vehicle to center) or wireline (area to center) infrastructure. Security related information is also transmitted to the Emergency Management Subsystem when an emergency is identified that requires an external response. Incident information is communicated to the Information Service Provider.


TransitManagement

Transit Center Security

Transit Vehicle

On-Board TransitSecurityemergency

acknowledge

emergencynotification

emergencyacknowledge

emergencynotification

transitemergency

data

transitemergency coordinationdata

Secure Area Monitoring

secure area monitoring support


transitincident information

EmergencyManagement

secure areasurveillance data

Remote Mayday I/F

Figure 5-8: APTS05 - Transit Security Market Package

APTS06 - Transit Maintenance: This market package supports automatic maintenance scheduling and monitoring. Onboard condition sensors monitor critical system status and transmit critical status information to the Transit Management Subsystem. Hardware and software in the Transit Management Subsystem process this data and schedule maintenance activities.

Transit MaintenancePersonnel

maintenancestatus

transitworkschedule

TransitManagement

Transit Vehicle

On-board Maintenance

transit vehicleconditionsTransit Garage

Maintenance

Figure 5-9: APTS06 - Transit Maintenance Market Package

APTS07 - Multi-modal Coordination: This market package establishes two-way communications between multiple transit and traffic agencies to improve service coordination. Intermodal coordination between transit agencies can increase traveler convenience at transfer points and also improve operating efficiency. Coordination between traffic and transit management is intended to improve on-time performance of the transit system to the extent that this



can be accommodated without degrading overall performance of the traffic network. More limited local coordination between the transit vehicle and the individual intersection for signal priority is also supported by this package.

TrafficManagement

TransitManagement

Transit Center Multi-modal Coordination

Transit Vehicle

On-board TransitSignal Priority

transit vehicleschedule performance

TMC Multi-modalCoordination

Roadway

Roadside SignalPriority

localsignalpriorityrequest

trafficcontrol priorityrequest

signal control data

request forright-of- way

trafficcontrolprioritystatus

transitsystem

data

transit parking lot response

transit parkingcoordination

Other TransitManagement

TRMScoordination

ParkingManagement

Multimodal TransportationService Provider

transit multimodalinformation

Figure 5-10: APTS07 - Multi-modal Coordination Market Package

APTS08 - Transit Traveler Information: This market package provides transit users at transit stops and onboard transit vehicles with ready access to transit information. The information services include transit stop annunciation, imminent arrival signs, and real-time transit schedule displays that are of general interest to transit users. Systems that provide custom transit trip itineraries and other tailored transit information services are also represented by this market package.

transitinformation

userrequest

TransitManagement


Transit Vehicle

On-board TransitInformation Services

Transit CenterInformation Services

Remote TransitInformation Services

RemoteTraveler Support



transittraveler information

transit schedule information

transit travelerrequest

TransitUser

transituserinputs

transit traveler information

transituser

outputs

Figure 5-11: APTS08 - Transit Traveler Information Market Package

5.3.2 Advanced Traveler Information System Market Packages Markets packages under the Advanced Traveler Information Systems (ATIS) category work to supply travelers with information on existing traffic conditions, weather, construction, maintenance, and special events activities that could impact their travel plans. The information could be supplied in a variety of ways including television, hardware located along the roadway, or through an electronic mechanism. There are nine basic market packages identified under the National ITS Architecture, of which three apply to the North-Central Illinois Region and are highlighted below. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


ATIS01 - Broadcast Traveler Information: This market package provides the user with a basic set of ATIS services; its objective is early acceptance. It involves the collection of traffic conditions, advisories, general public transportation, toll and parking information, incident information, air quality and weather information, and the near real time dissemination of this information over a wide area through existing infrastructures and low cost user equipment (e.g., FM subcarrier, cellular data broadcast). Different from the market package ATMS6--Traffic Information Dissemination--which provides the more basic HAR and DMS information capabilities, ATIS1 provides the more sophisticated digital broadcast service. Successful deployment of this market package relies on availability of real-time traveler information from roadway instrumentation, probe vehicles or other sources.


Remote BasicInformation Reception

Vehicle

Basic VehicleReception

Personal InfoAccess

Personal BasicInformation Reception

broadcastinformation


TrafficManagement

TransitManagement


Basic InformationBroadcast

trafficinformation


request for traffic informationtransit information

request


EmergencyManagement

ParkingManagement

Media

WeatherService

weatherinformation

traveler information for media

incidentinformation

parkinginformation

Figure 5-12: ATIS01 - Broadcast Traveler Information Market Package

ATIS02 - Interactive Traveler Information: This market package provides tailored information in response to a traveler request. Both real-time interactive request/response systems and information systems that "push" a tailored stream of information to the traveler based on a submitted profile are supported. The traveler can obtain current information regarding traffic conditions, transit services, ride share/ride match, parking management, and pricing information. A range of two-way wide-area wireless and wireline communications systems may be used to support the required digital communications between traveler and the information service provider. A variety of interactive devices may be used by the traveler to access information prior to or during a trip including phone, kiosk, Personal Digital Assistant, personal computer, and a variety of in-vehicle devices. Successful deployment of this market package relies on availability of real-time transportation data from roadway instrumentation, probe vehicles or other means.



Personal InfoAccess


Vehicle

Personal InteractiveInformation Reception

Remote InteractiveInformation Reception

Interactive VehicleReception

TrafficManagement

TransitManagement


Interactive InfrastructureInformation

trafficinformation


request fortraffic information transit information

request

traveler information

travelerinformation

traveler requesttraveler request

travelerrequestMedia

traveler information

traveler informationfor media

ParkingManagement

parking information

WeatherService

weather information

EmergencyManagement

incidentinformation

Figure 5-13: ATIS02 - Interactive Traveler Information Market Package

ATIS05 - ISP Based Route Guidance: This market package offers the user advanced route planning and guidance, which is responsive to current conditions. Different than the Dynamic Route Guidance Market Package, this market package moves the route planning function from the user device to the information service provider. This approach simplifies the user equipment requirements and can provide the infrastructure better information on which to predict future traffic and appropriate control strategies to support basic route planning with minimal user equipment. The package includes both turn-by-turn route guidance as might be used in a vehicle, as well as pre-trip routes. The package includes two-way data communications and optionally also equips the vehicle with the databases, location determination capability, and display technology to support turn-by-turn route guidance.




Remote Interactive Information Reception

trip request

Personal InfoAccess

Location DataSource

Location DataSource

positionfix

positionfix

trip plan

trip plan

TrafficManagement

TransitManagement


Infrastructure ProvidedRoute Selection

trafficinformation transit and fare

schedules

request fortraffic information


Personal Location Determination

trip request

Vehicle

Vehicle Provider-BasedRoute Guidance

trip confirmationtrip confirmation

trip confirmation

trip request

Personal Provider-BasedRoute Guidance

Vehicle LocationDetermination

trip plan

Figure 5-14: ATIS05 - ISP Based Route Guidance Market Package

5.3.3 Advanced Traffic Management System Market Packages Advanced Traffic Management System (ATMS) market packages focus on roadway operations. Typically involved agencies include a traffic operations center that monitors roadway conditions and identifies breakdowns in traffic flow caused by planned or unplanned incidents and initiates responses necessary to moderate the impact to the traveling public. There are 19 basic market packages identified under the National ITS Architecture of which 12 apply to the North-Central Illinois Region and are highlighted below.

ATMS01 - Network Surveillance: This Market Package includes traffic detectors, environmental sensors, other surveillance equipment, the supporting field equipment, and wireline communications to transmit the collected data back to the Traffic Management Subsystem. The derived data can be used locally when traffic detectors are connected directly to a signal control system or remotely (e.g., when a CCTV system sends data back to the Traffic Management Subsystem). The data generated by this Market Package enables traffic managers to monitor traffic and road conditions, identify and verify incidents, detect faults in indicator operations, and collect census data for traffic strategy development and long range planning. The collected data can also be analyzed and made available to users and the Information Service Provider Subsystem.

TrafficManagement

Collect TrafficSurveillance

Roadway

Roadway BasicSurveillance


trafficinformation

request fortraffic information

traffic flow

sensor andsurveillance control

Traffic Maintenance

traffic images

Figure 5-15: ATMS01 - Network Surveillance Market Package



ATMS03 - Surface Street Control: This market package provides the central control and monitoring equipment, communication links, and the signal control equipment that support local surface street control and/or arterial traffic management. A range of traffic signal control systems are represented by this market package ranging from static pre-timed control systems to comprehensive traffic responsive systems that dynamically adjust control plans and strategies based on current traffic conditions and priority requests. Additionally, general advisory and traffic control information can be provided to the driver while en-route. This market package is generally an intra-jurisdictional package that does not rely on real-time communications between separate control systems to achieve area-wide traffic signal coordination. Systems that achieve coordination across jurisdictions by using a common time base or other strategies that do not require real time coordination would be represented by this package. This market package is consistent with typical urban traffic signal control systems.

TrafficManagement

TMC SignalControl

Roadway

RoadwaySignal Controls

signal control data

TrafficMaintenance

signal control status

traffic flow

request for right-of-way

traffic images

sensor and surveillance control

Driver

driverinformation

Figure 5-16: ATMS03 - Surface Street Control Market Package

ATMS04 - Freeway Control: This market package provides the communications and roadside equipment to support ramp control, lane controls, and interchange control for freeways. Coordination and integration of ramp meters are included as part of this market package. This package is consistent with typical urban traffic freeway control systems. This package incorporates the instrumentation included in the Network Surveillance Market Package to support freeway monitoring and adaptive strategies as an option. This market package also includes the capability to utilize surveillance information for detection of incidents. Typically, the processing would be performed at a traffic management center; however, developments might allow for point detection with roadway equipment. For example, a CCTV might include the capability to detect an incident based upon image changes. Additionally, this market package allows general advisory and traffic control information to be provided to the driver while en-route.



TrafficManagement

TMC FreewayManagement

Roadway

RoadwayFreeway Control

freeway control data

TrafficMaintenance

freeway control status

traffic flow

traffic images

Driver

driverinformation

sensor andsurveillance control

Figure 5-17: ATMS04 - Freeway Control Market Package

ATMS06 - Traffic Information Dissemination: This market package allows traffic information to be disseminated to drivers and vehicles using roadway equipment such as dynamic message signs or highway advisory radio. This package provides a tool that can be used to notify drivers of incidents; careful placement of the roadway equipment provides the information at points in the network where the drivers have recourse and can tailor their routes to account for the new information. This package also covers the equipment and interfaces that provide traffic information from a traffic management center to the media (for instance via a direct tie-in between a traffic management center and radio or television station computer systems), transit management center, emergency management center, and information service provider.

TrafficManagement

TMC Traffic InfoDissemination

Roadway

roadway informationsystem status Roadway Traffic Info

Dissemination

roadway informationsystem data


trafficinformation

Driver

driverinformation

Mediatraffic information

for media

Basic Vehicle

broadcastadvisories

EmergencyManagement

TransitManagement current

networkconditions

traffic informationfor transit

Figure 5-18: ATMS06 - Traffic Information Dissemination Market Package

ATMS07 - Regional Traffic Control: This market package advances the Surface Street Control and Freeway Control Market Packages by adding the communications links and integrated control strategies that enable integrated Inter-jurisdictional traffic control. This market package provides for the sharing of traffic information and control among traffic management centers to support a regional control strategy. The nature of optimization and extent of information and control sharing is determined through working arrangements



between jurisdictions. This package relies principally on roadside instrumentation supported by the Surface Street Control and Freeway Control Market Packages and adds hardware, software, and wireline communications capabilities to implement traffic management strategies, which are coordinated between allied traffic management centers. Several levels of coordination are supported from sharing of information through sharing of control between traffic management centers.

TrafficManagement

Roadway

freeway control data

freeway control status

signal control data

signal control status

TMC RegionalTraffic Control

Other TM

traffic flow

trafficcontrol

coordination

trafficinformationcoordination

Figure 5-19: ATMS07 - Regional Traffic Control Market Package

ATMS08 - Incident Management System: This market package manages both predicted and unexpected incidents so that the impact to the transportation network and traveler safety is minimized. Requisite incident detection capabilities are included in the freeway control market package and through regional coordination with other traffic management and emergency management centers, weather service entities, and event promoters supported by this market package. Information from these diverse sources are collected and correlated by this market package to detect and verify incidents and implement an appropriate response. This market package provides Traffic Management Subsystem equipment that supports traffic operations personnel in developing an appropriate response in coordination with emergency management and other incident response personnel to confirmed incidents. The response may include traffic control strategy modifications and presentation of information to affected travelers using the Traffic Information Dissemination market package. The same equipment assists the operator by monitoring incident status as the response unfolds. The coordination with emergency management might be through a CAD system or through other communication with emergency field personnel. The coordination can also extend to tow trucks and other field service personnel.



EmergencyManagement

TrafficManagement

TMC Incident DispatchCoord/Communication

Roadway

Other TM

trafficinformationcoordination

incident information

Emergency ResponseManagement

incident data



trafficinformation

roadway information system data

EmergencyVehicle

incidentstatus

TMC IncidentDetection

Roadway IncidentDetection

WeatherService

weatherinformation

loggedspecial vehicle

route

Construction &Maintenance

maintenance resource request

maintenance resource response

closure coordination

traffic images


OtherEM

incident report

EventPromoter

event plans

incidentresponse

coordination

incidentcommandinformation


Figure 5-20: ATMS08 - Incident Management System Market Package

ATMS10 - Electronic Toll Collection: This market package provides toll operators with the ability to collect tolls electronically and detect and process violators. Variations in the fees that are collected enables implementation of demand management strategies. Dedicated short-range communication between the roadway equipment and the vehicle is required as well as wireline interfaces between the toll collection equipment and transportation authorities and the financial infrastructure that supports fee collection. Vehicle tags of toll violators are read and electronically posted to vehicle owners. Standards, inter-agency coordination, and financial clearinghouse capabilities enable regional and, ultimately, national interoperability for these services. The population of toll tags and roadside readers that these systems utilize can also be used to collect road use statistics for highway authorities. This data can be collected as a natural by-product of the toll collection process or collected by separate readers that are dedicated to probe data collection.



TollAdministration

TollAdministration

Toll Collection

Toll PlazaToll Collection

Vehicle

Vehicle Toll/Parking Interface

tagdata

PaymentInstrument

paymentrequest forpayment

toll transactions

toll instructions


paymentrequest

transactionstatus

EnforcementAgency


tagupdate


toll datarequest

toll data

Figure 5-21: ATMS10 – Electronic Toll Collection Market Package

ATMS13 - Standard Railroad Grade Crossing: This market package manages highway traffic at highway-rail intersections (HRIs) where operational requirements do not dictate more advanced features (e.g., where rail operational speeds are less than 80 miles per hour). Both passive (e.g., the crossbuck sign) and active warning systems (e.g., flashing lights and gates) are supported. (Note that passive systems exercise only the single interface between the roadway subsystem and the driver in the architecture definition.) These traditional HRI warning systems may also be augmented with other standard traffic management devices. The warning systems are activated on notification by interfaced wayside equipment of an approaching train. The equipment at the HRI may also be interconnected with adjacent signalized intersections so that local control can be adapted to highway-rail intersection activities. Health monitoring of the HRI equipment and interfaces is performed; detected abnormalities are reported to both highway and railroad officials through wayside interfaces and interfaces to the traffic management subsystem. Similar interfaces and services are provided for other types of multimodal crossings (e.g., draw bridges).



TrafficManagement

HRI TrafficManagement

Roadway

Standard Rail Crossing

RailOperations

WaysideEquipment

hri status

Traffic

trafficcharacteristics

hri request

Pedestrians

Driver

crossingpermission

driverinformation

hri control data

hri advisories

trackstatus

hri operationalstatus

Figure 5-22: ATMS13 - Standard Railroad Grade Crossing Market Package

ATMS14 - Advanced Railroad Grade Crossing: This market package manages highway traffic at highway-rail intersections (HRIs) where operational requirements demand advanced features (e.g., where rail operational speeds are greater than 80 miles per hour). This market package includes all capabilities of the Standard Railroad Grade Crossing Market Package and augments these with additional safety features to mitigate the risks associated with higher rail speeds. The active warning systems supported by this market package include positive barrier systems, which preclude entrance into the intersection when the barriers are activated. Like the Standard Package, the HRI equipment is activated on notification by wayside interface equipment, which detects, or communicates with the approaching train. In this market package, the wayside interface equipment also provides additional information about the arriving train so that the train's direction of travel, its estimated time of arrival, and the estimated duration of closure may be derived. This enhanced information may be conveyed to the driver prior to, or in context with, warning system activation. This market package also includes additional detection capabilities, which enable it to detect an entrapped or otherwise immobilized vehicle within the HRI and provide an immediate notification to highway and railroad officials.

TrafficManagement

HRI TrafficManagement

RailOperations

WaysideEquipment

hri status

trackstatus

Traffic

trafficcharacteristics

hri request

Pedestrians

Driver

crossingpermission

driverinformation

hri operational

statusintersection blockage

notification Roadway

AdvancedRail Crossing

arriving traininformation

intersectionblockage

notification

hri control data

hri advisories

Figure 5-23: ATMS14 - Advanced Railroad Grade Crossing Market Package



ATMS16 - Parking Facility Management: This market package provides enhanced monitoring and management of parking facilities. The included equipment assists in the management of parking operations, coordinates with transportation authorities, and supports electronic collection of parking fees. This is performed by sensing and collecting current parking facilities status, sharing the data with information service providers and traffic operations, and automatic fee collection using short-range communications with the same in-vehicle equipment utilized for electronic toll collection.

Parking Management

Parking

ManagementVehicle

Vehicle Toll/Parking Interface


PaymentInstrument


tag update

tag data

transactionstatus

paymentrequest

EnforcementAgency


parkinginformation

request tag data

paymentrequest

forpayment

parking lot reservation confirmationParking Electronic

Payment

Parking Surveillance

Figure 5-24: ATMS16 - Parking Facility Management Market Package

ATMS18 - Road Weather Information System: This market package monitors current and forecasted road and weather conditions using a combination of weather service information and data collected from environmental sensors deployed on and about the roadway. The collected road weather information is monitored and analyzed to detect and forecast environmental hazards such as icy road conditions, dense fog, and approaching severe weather fronts. This information can be used to more effectively deploy road maintenance resources, issue general traveler advisories, and support location specific warnings to drivers using the Traffic Information Dissemination Market Package.



WeatherService

TrafficManagement

TMC Road WeatherMonitoring

Roadway

Roadway EnvironmentalMonitoring

Construction &Maintenance

RoadwayEnvironment

TrafficOperationsPersonnel

weatherinformation


maintenanceresourceresponse weather

conditions

environmental conditions

trafficoperator

inputs

trafficoperator

data

closurecoordination

Figure 5-25: ATMS18 - Road Weather Information System Market Package

ATMS19 - Regional Parking Management: This market package supports coordination between parking facilities to enable regional parking management strategies.

ParkingManagement

Parking Management

Parking Coordination

TransitManagement

parkingavailability

transit parking lot response

transit parkingcoordination

parking demand management request

TrafficManagement

OtherParking

parking coordination

Figure 5-26: ATMS19 - Regional Parking Management Market Package

5.3.4 Commercial Vehicle Operation Market Packages Commercial Vehicle Operation (CVO) market packages focus on the safety, operation, and administration of individual commercial vehicles and/or fleets. Through better management of vehicles improved safety, better information for planning, and decreased delays are possible. Typical needs addressed by the commercial vehicle market packages include administration of fleet and freight, clearance for height and border crossing, as well as safety systems. There are 10 market packages identified under the National ITS Architecture of which one applies to the North-Central Illinois Region and is highlighted below. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


CVO10 - HAZMAT Management: This market package supports maintenance of CVO fleet vehicles through close interface with onboard monitoring equipment and AVLS capabilities within the Fleet and Freight Management Subsystem. Records of vehicle mileage, repairs, and safety violations are maintained to assure safe vehicles on the highway.

CommercialVehicle

commercial vehicle measures

TrafficManagement

TMC Incident Dispatch Coordination

/Communication

Hazmatinformation

Vehicleemergency notification

incidentinformation

EmergencyManagement

Emergency ResponseManagement

Mayday Support

Fleet and FreightManagement

Fleet HAZMAT Management

CommercialVehicle

On-board CargoMonitoring

Vehicle Mayday I/F

CommercialVehicle

Administration

credentialapplication

electronic credentials

commercialvehicledatarequest

commercialvehicle

data

Basic Vehicle

basic vehiclemeasures

Figure 5-27: CVO10 - HAZMAT Management Market Package

5.3.5 Emergency Management Market Packages Emergency Management (EM) market packages typically serve the needs of law enforcement, fire, search and rescue, and HAZMAT operations. The packages also address coordination between the various agencies’ personnel, vehicles, and response plans. There are three basic market packages identified under the National ITS Architecture, of which two apply to the North-Central Illinois Region and are highlighted below.

EM01 - Emergency Response: This market package provides the computer-aided dispatch systems, emergency vehicle equipment, and wireless communications that enable safe and rapid deployment of appropriate resources to an emergency. Coordination between Emergency Management Subsystems supports emergency notification and coordinated response between agencies. Existing wide area wireless communications would be utilized between the Emergency Management Subsystem and an Emergency Vehicle to enable an incident command system to be established and supported at the emergency location. The Emergency Management Subsystem would include hardware and software for tracking the emergency vehicles. Public safety, traffic management, and many other allied agencies may each participate in the coordinated response managed by this package.



EmergencyManagement

Emergency Call-Tracking

EmergencyVehicle

On-board EV Incident Management

Communication

incident status

Emergency Response Management

emergency dispatch requests

Other EMincidentreport

TrafficManagement

resource request +remote surveillance control

current network conditions +resource deployment status

WeatherServices weather

information

Figure 5-28: EM01 - Emergency Response Market Package

EM02 - Emergency Routing: This market package supports dynamic routing of emergency vehicles and coordination with the Traffic Management Subsystem for special priority on the selected route(s). The Information Service Provider Subsystem supports routing for the emergency fleet based on real-time traffic conditions and the emergency routes assigned to other responding vehicles. In this market package, the Information Service Provider Subsystem would typically be integrated with the Emergency Management Subsystem in a public safety communications center. The Emergency Vehicle would also optionally be equipped with dedicated short-range communications for local signal preemption.

EmergencyManagement

EmergencyVehicle

emergency vehicletracking data

emergency trafficcontrol request

TrafficManagement

signal control data

On-Board EVEn Route Supportsuggested route

local signalpreemption request

Roadway

Roadside Signal Priority

Emergency Dispatch

request for right-of-way

current network conditions +emergency traffic control response

Vehicle Location Determination

Figure 5-29: EM02 - Emergency Routing Market Package

5.3.6 Archive Data Market Packages Archive Data (AD) market packages focus on the storage and distribution of vital operations information. There are three basic market packages identified under the National ITS Architecture ,of which all apply to the North-Central Illinois Region and are highlighted below.



AD01 - ITS Data Mart: This market package provides a focused archive that houses data collected and owned by a single agency, district, private sector provider, research institution, or other organization. This focused archive typically includes data covering a single transportation mode and one jurisdiction that is collected from an operational data store and archived for future use. It provides the basic data quality, data privacy, and meta-data management common to all ITS archives and provides general query and report access to archive data users.

Archived DataManagement

Government Reporting System Support

Archived Data Administrator

Archived Data User Systems

archiverequests +

archivestatus

archived data products archive management data

trafficarchivedata

archived data products requests

archive management data requests

TrafficManagement

Traffic Data Collection

ITS Data Repository

Any of the following ITS data source can be the source for an ITS Data Mart. The Traffic Management Subsystem is shown as an example.Data Sources:•Commercial Vehicle Administration•Emergency Management•Emissions Management •Information Service Provider•Parking Management•Roadway Subsystem•Toll Administration•Traffic Management•Transit Management

•Construction and Maintenance•Intermodal Freight Depot•Map Update Provider•Multimodal Transportation Service Provider•Other Data Sources•Weather Service

government reporting system data

GovernmentReportingSystems

Figure 5-30: AD01 - ITS Data Mart Market Package

AD02 - ITS Data Warehouse: This market package includes all the data collection and management capabilities provided by the ITS Data Mart, and adds the functionality and interface definitions that allow collection of data from multiple agencies and data sources spanning across modal and jurisdictional boundaries. It performs the additional transformations and provides the additional meta-data management features that are necessary so that all of this data can be managed in a single repository with consistent formats. The potential for large volumes of varied data suggests additional on-line analysis and data mining features that are also included in this market package in addition to the basic query and reporting user access features offered by the ITS Data Mart.




On-Line Analysisand Mining

ITS Data Repository

Government Reporting System Support

Traffic and RoadsideData Archival

TrafficManagement

TrafficData Collection

Toll Administration

Toll Data Collection

EmergencyManagement

Emergency Data Collection

EmissionsManagement

Emission Data Collection

ParkingManagement

ParkingData Collection

RoadwayRoadside

Data Collection

CommercialVehicle Adm.

CVData Collection

TransitManagement

TransitData Collection


WeatherService


IntermodalFreight Depot

Construction& Maintenance

Multimodal Transportation Service Provider

sensor & surveillance control

archive request confirmation +archived data products

archive management data

Other DataSources

archive analysis results

archive data product requests

archive management requests

Government ReportingSystems

government reportingdata receipt

weatherinfo.

intermodal freight archive data

multimodalarchive

data

transit archive data

emissions archive data

parking archive data

toll archive datatraffic archive data

commercial vehicle archive data

emergency archive data

roadside archive data

other data sourcearchive data

archive requests

archive requests

archive requests

archiverequests

archive requests

archive requests

archiverequests

Information ServiceProvider

Emergency Data Collection

travelerarchive data

archiverequests

construction &maintenance

Figure 5-31: AD02 - ITS Data Warehouse Market Package

AD03 - ITS Virtual Data Warehouse: This market package provides the same broad access to multimodal, multidimensional data from varied data sources as in the ITS Data Warehouse Market Package, but provides this access using enhanced interoperability between physically distributed ITS archives that are each locally managed. Requests for data that are satisfied by access to a single repository in the ITS Data Warehouse Market Package are parsed by the local archive and dynamically translated to requests to remote archives which relay the data necessary to satisfy the request.


ITS Data Repository

Virtual Data Warehouse Services



Other Archives

archivecoordination

archived data products

archived data products requests

archive management dataarchive management

data requests

Figure 5-32: AD03 - ITS Virtual Data Warehouse Market Package



6 Project Concepts Through stakeholder outreach various project ideas or concepts were identified as needed or desired for the North-Central Illinois Region. The majority of the projects concepts fall into the categories of improving communications, data sharing between agencies, utilizing new resources to increase operational efficiencies, and making administration and management improvements. Other projects focus on adding infrastructure improvements seen as needed to facilitate sharing information with the traveling public and improve traffic mobility. Ten project concepts were generated from stakeholder outreach efforts and identified as critical or “high-priority”. The high-priority project concepts fill needs or desires expressed by stakeholders and are considered likely candidates for future regional deployments due to strong support. Identification of the project concepts allowed for further refinement of the regional architecture by insuring that high-priority projects were taken into consideration and accounted for during the regional architecture’s development.

6.1 Critical Project Concept Descriptions In the following sections, descriptions and diagrams explain in detail the nine critical project concepts. Some of the information describing the projects uses architecture terms and definitions that are explained in greater detail in “System Architecture”, Chapter 7. The use of system architecture here helps to tie the project concepts to the regional system architecture and provides detail that better defines the function and characteristics of each project. The nine critical project concepts are:

Project 1: Traffic Management and Maintenance Control Center Project 2: Interstate Traffic Monitoring & Traveler Information Project 3: Advanced Signal Operations/Coordination & Surface Street Traffic

Monitoring Project 4: Agency Data Sharing Project 5: Winter Weather Maintenance Enhancements Project 6: Arterial Dynamic Message Signs & Dynamic Trailblazer Signing Project 7: Construction Work Zone Safety, Traffic Monitoring and Traveler

Information Project 8: Advanced Rail Crossing Notification System Project 9: Supplemental Emergency Vehicle Traffic Signal Preemption

The section that follows further explains each of the critical project concepts. Each section is broken into six parts, described below:

1. Description: A short explanation of the project concept in paragraph form. General details are given highlighting the project’s purpose and system function along with information on the project’s intended goals and benefits.

2. High-level Architecture: A high-level diagram graphically illustrating the

general system elements that comprise the project. Its purpose is to highlight the relationship between generic centers, roadway devices, vehicles, and travelers to show the types of groups and systems that would be involved with the project



when deployed. No information, at this point is provided on exact agencies, equipment, or data exchanges between them.

3. Interconnect Diagram: Agencies and equipment involved with the project are

identified here. The Diagram highlights the communication paths that will link the different agencies, equipment, and other resources involved with the project. The diagram does not distinguish which communication form or system will be used (i.e., wireless, fiber, etc.) nor does it indicate the information to be sent across the communication paths.

4. Architecture Flow Diagram: Here the information and data exchanged between

the different projects are first described. Also indicated here is the source and destination of the information utilized by the project.

5. Architecture Flow Definitions: Definitions for each flow used in the

Architecture Flow Diagram are presented.

6. Identified Applicable ITS Standards: Applicable National ITS standards that would facilitate project deployment and integration are presented in this section.

6.1.1 Project 1 - Traffic Management and Maintenance Control Center The Traffic Management and Maintenance Control Center (TMMCC) will serve as a critical component in enhancing operations and maintenance efficiency throughout IDOT District 2 in the future. Serving as the cornerstone, it is envisioned the TMMCC will support existing and planned services including: Interagency Coordination – The TMCC would become the primary focal point for coordinating interagency activities such as traffic incident clearance during major events, planning for and debriefing major freeway incidents, phone and radio communications with partner agencies, and sharing of real-time travel information. Maintenance Dispatch – The existing operations area in Dixon currently provides maintenance dispatch capabilities. Under the TMMCC, some of the dispatching functions may become more automated such as real-time maintenance / road and lane closure tracking, emergency repair tracking, and plowing coordination. Traffic Operations – It is envisioned that the TMMCC would serve as the center of traffic operations along Interstate and State Highways jurisdictionally controlled by IDOT. Traveler Information – The TMCC will serve as a local and regional point for distributing traveler information through the use of dynamic message signs (both portable and permanent), internet and an interface with the Gary –Chicago – Milwaukee (GCM) Gateway which currently provides aggregated multi-state travel information. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


6.1.1.1 High Level Physical Architecture: Figure 6-1 shows the high level physical architecture for the Traffic Management and Maintenance Control Center (TMMCC) project. It illustrates how the project links multiple subsystems to a centralized TMCC traffic management subsystem.

Figure 6-1: High level Physical Architecture for Traffic Management and

Maintenance Control Center Project

6.1.1.2 Interconnect Diagram: Figure 6-2 shows an interconnect diagram, highlighting the relationship between the different management agencies, the traffic management center in Dixon, and the roadway (subsystem) elements. The diagram is a high level view of data paths that reveals how information will be routed between different center and roadway subsystems. The current diagram shows roadside equipment, within the District, connected to the TMMCC, which functions as a focal point for operation activities and information exchange with the other agencies.



Archived Data Management_Illinois S...Archived Data Management

System-Dixon IL

Traffic Management_Illinois State De...Traffic Management and Maintenance

Control Center_Dixon

Traffic Management_City of Rockford...City of Rockford Traffic Engineering

Office

Traffic Management_Wisconsin State...Corridor Transportation Management

Center Madison

ISP_Illinois State Department of Tran...IDOT-Gateway Travelar Information

System

Traffic Management_Iowa State Dep...IowaDOT-District 5 Operations

Traffic Management_Illinois State Tol...ISTHA-Operations Downers Grove


Control Center_Dixon_Personnel


Control Center_Dixon_RoadsideEquipment

ExistingPlanned

Figure 6-2: Interconnect Diagram for Traffic Management and Maintenance Control Center Project

Figure 6-3 further identifies roles and responsibilities for the Traffic Management and Maintenance Control Center project.



Agency

Roles and Responsibilities

IDOT District 2 Traffic Management and Maintenance Control Center - Dixon

Primary control and operations of field equipment in District 2

Control and operate dynamic message signs (portable and permanent), detectors, and surveillance images

Process archive requests from the Archived Data Management System

Configure changes, provide information, display dynamic information, and adjust traffic control strategies per personnel command

Detection and verification of incidents Dispatch Maintenance Vehicles Monitor weather conditions Coordinate interagency activities Facilitate sharing of traffic information with

partner agencies Monitor and modify traffic signal operations

IDOT District 1 Gateway Traveler Information Hub

Routinely Poll IDOT TMMCC ITE equipment servers to provide information on GCM webpage.

WisDOT District 1 Corridor Transportation Management Center - Madison

Primary control and operations of field equipment in District 1 (Southwest Wisconsin)

Coordinate Traffic Management and Traveler Information Activities when incident has multi-state impacts.

ISTHA Operations Area – Downer’s Grove Primary control and operations of field equipment along the Illinois Tollway

Coordinate Traffic Management and Traveler Information Activities when incident has impacts on IDOT and other agency jurisdictions.

Iowa District 5 Operations Area - Fairfield Primary control and operations of field equipment in the Quad Cities area

Coordinate DMS messaging in Quad Cities Area (since some signs are located within Illinois)

City of Rockford Traffic Engineering Office Operates a significant amount of IDOT signals in the Rockford area

Coordinate Signal Operations with IDOT Share Video Image Detection System images with

TMMCC

Figure 6-3: Agency Roles and Responsibilities for Traffic Management and Maintenance Control Center Project

6.1.1.3 Architecture Flow Diagram: Figure 6-4 shows a sample architecture flow diagram highlighting the typical data exchanges between the Dixon traffic management center, a roadway subsystem, and other agency subsystems for the Traffic Management and Maintenance Control Center project.



Archived Data Management_Illinois State De...Archived Data Management System-Dixon IL

Traffic Management_Illinois State Department...Traffic Management and Maintenance Control

Center_Dixon

Traffic Management_City of Rockford_Depart...City of Rockford Traffic Engineering Office


Center Madison


System







archive requestsarchive status

traffic control coordinationtraffic information coordination


logged special vehicle routerequest for traffic information

road network usetraffic control coordination

traffic information coordinationtraffic control coordination

traffic information coordinationtraffic archive data

traffic information


traffic operator data

freeway control dataroadway information system data





traffic operator inputs

fault reportsfreeway control status

incident dataroadway information system status

traffic flowtraffic images

ExistingPlanned

Figure 6-4: Architecture Flow Diagram for the Traffic Management and Maintenance Control Center Project

6.1.1.4 Architecture Flow Definitions: Figure 6-5 contains the architecture flow definitions, which describe the data being exchanged between subsystems in the diagram above.



Architecture Flow

Definition

archive requests A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.

archive status Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.

fault reports Reports from field equipment (sensors, signals, signs, controllers, etc.) which indicate current operational status.

freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and other systems associated with freeway operations

freeway control status Current operational status and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and other control equipment associated with freeway operations.

incident data Data and imagery from the roadside supporting incident detection and verification. logged special vehicle route

Anticipated route information for special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governer's motorcade) that may require changes in traffic control strategy.

request for traffic information

Request for traffic information that specifies the region/route of interest, the desired effective time period, and other parameters that allow preparation of a tailored response. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.

road network use Aggregated route usage and associated travel data from clients for planning and analysis. roadway information system data

Information used to initialize, configure, and control roadside systems that provide driver information. This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.

roadway information system status

Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field equipment that provides dynamic information to the driver.


Information used to configure and control sensor and surveillance systems at the roadside.

traffic archive data Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.

traffic control coordination

Information transfers that enable remote monitoring and control of traffic management devices. This flow is intended to allow cooperative access to, and control of, field equipment during incidents and special events and during day-to-day operations. This flow also allows 24-hour centers to monitor and control assets of other centers during off-hours, allows system redundancies and fail-over capabilities to be established, and otherwise enables integrated traffic control strategies in a region.

traffic flow Raw and/or processed traffic detector information, which allows derivation of traffic flow variables (e.g., speed, volume and density measures).

traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.

traffic information Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw data, processed data, or some combination of both may be provided by this architecture flow.

traffic information coordination

Traffic information exchanged between TMC’s. Normally would include incidents, congestion data, traffic data, signal timing plans, and real-time signal control information.

traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of traffic control equipment, maintenance activity status, incident status, and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, and supports review of historical data and preparation for future traffic operations activities.

traffic operator inputs Traffic operations requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.

Figure 6-5: Architecture Flow Diagram Definitions for the Traffic Management and Maintenance Control Center Project



6.1.1.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-6 identifies applicable ITS standards that would support the deployment of the Traffic Management and Maintenance Control Center project. Organization

Standard Name

Document ID

AASHTO Simple Transportation Management Framework (STMF) NTCIP 1101 AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Dynamic Message Signs NTCIP 1203

AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather Information NTCIP 1204

AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices NTCIP 1206 AASHTO Ramp Meter Controller Objects NTCIP 1207 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Message Set for Weather Reports NTCIP 1301 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202

AASHTO Application Profile for Simple Transportation Management Framework (STMF) NTCIP 2301

AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304

AASHTO Application Profile for Common Object Request Broker Architecture (CORBA) NTCIP 2305

AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502

ITE Standard for Functional Level Traffic Management Data Dictionary (TMDD) ITE TM 1.03

ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01 SAE Data Dictionary for Advanced Traveler Information System (ATIS) SAE J2353 SAE Message Set for Advanced Traveler Information System (ATIS) SAE J2354 SAE Rules for Standardizing Street Names and Route IDs SAE J2529

SAE Messages for Handling Strings and Look-Up Tables in ATIS Standards SAE J2540

Figure 6-6: Applicable ITS Standards for the Traffic Management and Maintenance Control Center Project



6.1.2 Project 2 - Interstate Traffic Monitoring & Traveler Information The Interstate Traffic Monitoring and Traveler Information project is meant to facilitate quicker identification of incidents and provide critical traveler information along major freeway segments in Transportation District 2. Incidents will be identified through the use of traffic detectors located along I-39, and, in some cases, verified through the use of traffic condition cameras in the Rockford urban areas and other critical interchanges. When an incident has been verified, dynamic message signs (both portable and permanent) will provide important alerts to motorists. Once aware of an incident, a motorist may choose to alter their travel, thus saving time and reducing congestion caused by the incident. When no incidents are present signs may be used in conjunction with detectors to display travel times that assist motorists in planning their travel. 6.1.2.1 High Level Physical Architecture: Figure 6-7 shows the high level physical architecture for the Interstate Traffic Monitoring and Traveler Information project. It illustrates how the project will connect roadway subsystems that monitor and inform the traveling public with a traffic management subsystem that manages and operates the subsystem. Traffic data is archived for later use.

Travelers

Vehicles Roadside

Centers

Wide Area Wireless Communications

Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle

RemoteTravelerSupport

PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement

CommercialVehicleCheck

Wireline Communications

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



TrafficManagement

TrafficManagement

RoadwayRoadway

ArchivedData

Management

ArchivedData

Management

Wireline CommunicationsWireline Communications

Figure 6-7: High Level Physical Architecture for the Interstate Traffic Monitoring and

Traveler Information Project 6.1.2.2 Interconnect Diagram: Figure 6-8 shows the interconnect diagram, which shows the relationships between different traffic management centers (traffic management subsystems) and their respective roadside equipment (roadway subsystems). The diagram is a high level view of data paths that reveals how information is exchanged. The current diagram shows three traffic management agencies all connected by the Traffic Management and Maintenance Control Center in Dixon. Each agency has its own roadside equipment but will use the TMMCC as the center responsible for regional transportation coordination efforts.




Center Madison

Traffic Management_Wisconsin State...Corridor Transportation ManagementCenter Madison_Roadside Equipment




Traffic Management_Illinois State Tol...ISTHA-Operations DownersGrove_Roadside Equipment



Figure 6-8: Interconnect Diagram for the Interstate Traffic Monitoring and Traveler

Information Project

ExistingPlanned

Figure 6-9 further identifies roles and responsibilities for the Interstate Traffic Monitoring and Traveler Information project.

Agency


IDOT District 2 Traffic Management and Maintenance Control Center – Dixon


Control and operate dynamic message signs (portable and permanent), detectors, and surveillance images



Detection and verification of incidents WisDOT District 1 Corridor Transportation Management Center – Madison

Primary control and operations of field equipment in District 1 (Southwest Wisconsin)

Coordinate Traffic Management and Traveler Information Activities when incident has multi-state impacts.

Possibly share video and/or DMS control ISTHA Operations Area – Downers Grove Primary control and operations of field equipment

along the Illinois tollway Coordinate Traffic Management and Traveler

Information Activities when incident has impacts on IDOT and other agency jurisdictions

Possibly share video and/or DMS control

Figure 6-9: Agency Roles and Responsibilities for the Interstate Traffic Monitoring and Traveler Information Project

6.1.2.3 Architecture Flow Diagram:



Figure 6-10 shows a sample architecture flow diagram highlighting the typical data exchanges between the project traffic management subsystems and roadside equipment.

Traffic Management_Wisconsin State Department of Transportat...Corridor Transportation Management Center Madison

Traffic Management_Illinois State Department of Transportation...Traffic Management and Maintenance Control Center_Dixon

Traffic Management_Wisconsin State ...Corridor Transportation ManagementCenter Madison_Roadside Equipment

Traffic Management_Illinois State Toll Highway ...ISTHA-Operations Downers Grove

Traffic Management_Illinois State Toll Highway ...ISTHA-Operations Downers Grove_Roadside

Equipment

Traffic Management_Illinois State Depa...Traffic Management and Maintenance




sensor and surveillance controlfault reports

freeway control statusincident data

roadway information system statustraffic flow

traffic imagestraffic control coordination



sensor and surveillance controlfault reports



traffic images


sensor and surveillance controltraffic control coordination


traffic information coordinationfault reports



traffic images

Figure 6-10: Architecture Flow Diagram for the Interstate Traffic Monitoring and Traveler

Information Project

ExistingPlanned




Architecture Flow

Definition


freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and other systems associated with freeway operations.


incident data Data and imagery from the roadside supporting incident detection and verification.


Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio, beacon systems). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.





traffic control coordination


traffic flow Raw and/or processed traffic detector information which allows derivation of traffic flow variables (e.g., speed, volume and density measures).




Figure 6-11: Architecture Flow Diagram Definitions for the Interstate Traffic Monitoring and Traveler Information Project

6.1.2.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-12 identifies applicable ITS standards that would support the deployment of the Interstate Traffic Monitoring and Traveler Information Project.



Organization

Standard Name

Document ID

AASHTO Simple Transportation Management Framework (STMF) NTCIP 1101 AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Dynamic Message Signs NTCIP 1203

AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather Information NTCIP 1204

AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices NTCIP 1206 AASHTO Ramp Meter Controller Objects NTCIP 1207 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Message Set for Weather Reports NTCIP 1301 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202

AASHTO Application Profile for Simple Transportation Management Framework (STMF) NTCIP 2301

AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304

AASHTO Application Profile for Common Object Request Broker Architecture (CORBA) NTCIP 2305

AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502

ITE Standard for Functional Level Traffic Management Data Dictionary (TMDD) ITE TM 1.03

ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01 SAE Data Dictionary for Advanced Traveler Information System (ATIS) SAE J2353 SAE Message Set for Advanced Traveler Information System (ATIS) SAE J2354 SAE Rules for Standardizing Street Names and Route IDs SAE J2529

SAE Messages for Handling Strings and Look-Up Tables in ATIS Standards SAE J2540

Figure 6-12: Applicable ITS Standards for the Interstate Traffic Monitoring and Traveler Information Project

6.1.3 Project 3 - Advanced Signal Operations/Coordination & Surface Street Traffic

Monitoring To better support unplanned incidents along the freeway and major arterials, the Advanced Signal Operations/Coordination and Surface Street Traffic Monitoring project will enhance existing signal systems making them more responsive to actual traffic conditions. Under the project, signal systems located in Rockford and DeKalb would be upgraded from closed loop to responsive or adaptive. Components of the project include controller upgrades, installation of central servers / workstations, supplemental communications infrastructure and additional North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


traffic detection. Another key feature of the project includes providing a streamed video link between several video image detection (VIDS) units and the City of Rockford Traffic Engineering Office. Since several signals are operated and maintained by Rockford but owned by IDOT, it is envisioned that the streamed images would also be provided to the Traffic Management and Maintenance Control Center in Dixon. 6.1.3.1 High Level Physical Architecture: Figure 6-13 shows the high level physical architecture for the Advanced Signal Operations/Coordination and Surface Street Traffic Monitoring project. It illustrates how the project will connect roadway subsystems with a single traffic management subsystem.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



TrafficManagement

TrafficManagement

RoadwayRoadway


Figure 6-13: High Level Physical Architecture for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

6.1.3.2 Interconnect Diagram: Figure 6-14 shows the interconnect diagram, which highlights the relationships between the different agencies responsible for signal maintenance and operation. The diagram is a high level view of data communication paths between agencies. The current project would facilitate the sharing of traffic data and the response coordination. The project would support coordinated signal and traffic operations efforts between the City of DeKalb, City of Rockford, and the Illinois State Department of Transportation.



Traffic Management_City of DeKalb_...City of DeKalb Department of Public

Works


Works_Personnel


Works_Roadside Equipment


Office




Office_Personnel


Office_Roadside Equipment

ExistingPlanned

Figure 6-14: Interconnect Diagram for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

Figure 6-15 further identifies the roles and responsibilities for the Advanced Signal Operations/Coordination and Surface Street Traffic Monitoring project.

Agency


1. City of Rockford Department of Public Works 2. City of DeKalb Department of Public Works 3. IDOT District 2 Traffic Management and Maintenance Control Center - Dixon

Primary control and operations of field equipment along respective jurisdiction

Coordination and secondary control and operation of field equipment in adjacent jurisdictions

Detect and respond to equipment failure Command, operate, and configure sensor,

surveillance, and traffic signal controls Request real time data and archived data for

incident management and special event planning

Figure 6-15: Agency Roles and Responsibilities for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

6.1.3.3 Architecture Flow Diagram: Figure 6-16 shows a sample architecture flow diagram highlighting the typical data exchanges between the different city and state traffic management centers and roadside equipment.



Traffic Management_City of DeKalb_Department of Public WorksCity of DeKalb Department of Public Works


Works_Personnel



Traffic Management_City of Rockford_Department of Public WorksCity of Rockford Traffic Engineering Office




Office_Personnel




sensor and surveillance controlsignal control data




fault reportsincident data

signal control statustraffic flow







fault reportsincident data





ExistingPlanned

Figure 6-16: Architecture Flow Diagram for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

6.1.3.4 Architecture Flow Definitions: Figure 6-17 contains the following flow definitions, which describe the data being exchanged between subsystems in the diagram above.



Architecture Flow

Definition


incident data Data and imagery from the roadside supporting incident detection and verification.



signal control data Information used to configure and control traffic signal systems. signal control status Status of surface street signal controls. traffic control coordination






traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of traffic control equipment, maintenance activity status, incident status, and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, and supports review of historical data and preparation for future traffic operations activities.

traffic operator inputs Traffic operations requests for information, configuration changes, commands to adjust current traffic control strategies (e.g, adjust signal timing plans, change DMS messages), and other traffic operations data entry.

Figure 6-17: Architecture Flow Diagram Definitions for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

6.1.3.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-18 identifies applicable ITS standards that would support the deployment of the Advanced Signal Operations / Coordination and Surface Street Traffic Monitoring Project.



Organization

Document ID

Simple Transportation Management Framework (STMF) NTCIP 1101 Standard Name

AASHTO AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Dynamic Message Signs NTCIP 1203 AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather NTCIP 1204 AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices AASHTO Ramp Meter Controller Objects NTCIP 1207 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for Simple Transportation Management Framework NTCIP 2301 AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304 AASHTO Application Profile for Common Object Request Broker Architecture NTCIP 2305 AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502 ITE Standard for Functional Level Traffic Management Data Dictionary ITE TM 1.03 ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01

NTCIP 1206

Figure 6-18: Architecture Flow Diagram Definitions for the Advanced Signal Operations/Coordination & Surface Street Traffic Monitoring Project

6.1.4 Project 4 - Agency Data Sharing: By sharing traffic data and video from the Department with emergency response agencies, the Agency Data Sharing project facilitates improved coordination of resources during both planned and unplanned events. The project will be staged over several phases. The first focuses on sharing information from ITS devices positioned along the Interstate with a minimal number of public safety agencies (i.e., Winnebago County Sheriff’s Department, ISTHA and the media). In subsequent phases, traffic data will be shared between Illinois State Police Dispatch and other county public safety dispatch facilities. Later phases will see expansion of the service to encompass additional public safety and transportation-orientated agencies, some of which may not be critical, but could use the data to improve services. 6.1.4.1 High Level Physical Architecture: Figure 6-19 shows the high level physical architecture for the Agency Data Sharing project. It illustrates how the project will connect data from roadway subsystems to traffic management, emergency management, Toll, and Maintenance.



Figure 6-19: High Level Physical Architecture for the Agency Data Sharing Project

6.1.4.2 Interconnect Diagram: Figure 6-20 shows an interconnect diagram, which highlights the relationship between five different subsystems. Two of the five subsystems, those of traffic management and emergency management, are most likely to be part of an initial project deployment with others added in phases depending on funding and interest. The diagram shows how data and information would be exchanged if all subsystems were included.

O&M_County of Boone_IDOT Highw...Boone County IDOT Highway

Maintenance Dispatch

O&M_County of DeKalb_IDOT Highw...DeKalb County IDOT Highway




O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT Highway



Center Madison

O&M_County of Ogle_IDOT Highway...Ogle County IDOT Highway


EM_Illinois State Police_District 1Illinois State Police-District 1 Dispatch




EM_County of Winnebago_SheriffWinnebago County 911 Center

Media

ExistingPlanned Figure 6-20: Interconnect Diagram for the Agency Data Sharing Project



Figure 6-21 further identifies the roles and responsibilities for the Agency Data Sharing Project.

Agency


1. Winnebago County 911 Center 2. Illinois State Police Dispatch Centers (Districts 1, 15 and 16)

Receive and share information from other agencies involving planned and unplanned events, including crashes, construction, and special events.

Remotely operate sensors or surveillance equipment

IDOT District 2 Maintenance Facilities (in Ogle, Winnebago, DeKalb, and Boone Counties)

Respond to information received from other agencies and coordinate work zone closure, maintenance and response activities.

ISTHA Operations Area Downers Grove

Respond to information received from other agencies and coordinate work zone closure, maintenance and response activities.

Traffic Management and Maintenance Control Center - Dixon

Share information on local traffic conditions including incident data, traffic flow, and construction.

Allow access and control of traffic images with other agencies.

Receive and utilize data from dispatch centers and the media concerning incidents and traffic flow

Request current transportation information from the media, and dispatch centers.

WisDOT District 1 Corridor Transportation Management Center – Madison

Share information on Traffic Management and Traveler Information Activities when incident has multi-state impacts.

Share traveler information system data to ensure consistent information is share across state lines.

Local Media Receive and relay information to the public on planned incidents to improve their travel plans

Receive and relay information on unplanned events and incidents to minimize impact to motorists.

Provide information to public agencies that could have significant travel impacts.

Figure 6-21: Agency Roles and Responsibilities for the Agency Data Sharing Project

6.1.4.3 Architecture Flow Diagram: Figure 6-22 shows a “typical” architecture flow diagram highlighting the typical data exchanges between the project’s subsystems. Some agencies have been excluded to emphasize the types of information exchanges by removing duplicate information.



MediaTraffic Management_Illinois State Department of Transportation_Dist...

Traffic Management and Maintenance Control Center_Dixon

O&M_County of Ogle_IDOT Highway MaintenanceOgle County IDOT Highway Maintenance Dispatch




external reportsmedia information request

event and resource coordinationevent report

maintenance responsetraffic equip maintenance status

work zone closure status

traffic information for media

current network conditionsemergency traffic control response

incident informationincident information request

resource deployment statusmaintenance request

traffic equip statuswork zone closure coordination

maintenance requesttraffic equip status

work zone closure coordinationemergency traffic control request

incident informationincident response status

remote surveillance controlresource request




Figure 6-22: Architecture Flow Diagram for the Agency Data Sharing Project

ExistingPlanned6.1.4.4 Architecture Flow Definitions:

Figure 6-23 contains the architecture flow definitions, which describe the data being exchanged between subsystems in the diagram above.

Architecture Flow

Definition

current network conditions Current traffic information, road conditions, and camera images that can be used to locate and verify reported incidents, and plan and implement an appropriate response.

emergency traffic control request

Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, or request another special traffic control plan.

emergency traffic control response

Status of the special traffic signal control strategy implemented in response to the emergency traffic control request.

event report Report of an event including location, type, severity and other information necessary to initiate an appropriate maintenance response.

event and resource coordination

Planned and unplanned event response procedures, resource coordination, and current event response status that are shared between adjacent agencies to support a coordinated response.

external reports Traffic and incident information that is collected by the media through a variety of mechanisms (e.g., radio station call-in programs, air surveillance).

incident information Notification of existence of incident and expected severity, location, time and nature of incident.

incident information for media

Report of current desensitized incident information prepared for public dissemination through the media.

incident information request

Request for incident information, clearing time, severity. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.


Request for road maintenance resources that can be used in the diversion of traffic (cones, portable signs), clearance of an incident, and repair of ancillary damage.



Architecture Flow

Definition


Current status of maintenance resources included availability and deployment status.

media information request Request from the media for current transportation information.

remote surveillance control The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.

resource deployment status Status of traffic management center resource deployment identifying the resources available and their current deployment status.

resource request A request for traffic management resources to implement special traffic control measures, assist in clean up, verify an incident, etc. .

traffic equipment status Identification of field equipment requiring repair and known information about the associated faults.

traffic information for media

Report of current traffic conditions, incidents, maintenance activities and other traffic-related information prepared for public dissemination through the media.

work zone closure status Status of maintenance work zone closure. work zone closure coordination

Planned closure response procedures, resource coordination, and current event response status of maintenance work zone closure.

Figure 6-23: Architecture Flow Diagram Definitions for the Agency Data Sharing Project

6.1.4.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-24 identifies applicable ITS standards that would support the deployment of the Agency Data Sharing Project.

Organization

Standard Name

Document ID

AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304 AASHTO Application Profile for Common Object Request Broker Architecture NTCIP 2305 AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502 IEEE Standard for Public Safety IMMS for use by EMCs IEEE P1512.2 IEEE Standard for Emergency Management Data Dictionary IEEE P1512.a

IEEE Standard for Common Incident Management Message Sets (IMMS) for use by EMSs IEEE P1512-2000

ITE Standard for Functional Level Traffic Management Data Dictionary ITE TM 1.03 ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01 ITE TCIP - Spatial Representation (SP) Business Area Standard NTCIP 1405

Figure 6-24: Applicable ITS Standards for the Agency Data Sharing Project

6.1.5 Project 5 – Winter Weather Maintenance Enhancements The ability to better predict, respond to, and minimize winter weather impacts in North Central Illinois is critical to regional economic stability and growth. Winter weather maintenance enhancements have been grouped into the following areas:



Road and Weather Information Systems – Includes enhancing forecasting and other weather conditions (e.g., fog, snow white-out, etc.), capabilities of existing RWIS stations and providing additional sites in the region. Automated Bridge De-icing – Includes equipping high volume bridges with Automated Fixed Location Automated De-icings Systems (AFLADS). In addition to the core AFLADS, it is envisioned that Dynamic Message signs will be used to warn motorists of real-time bridge conditions (e.g., chemical being applied, wet pavement, etc.) Maintenance Snow and Ice Management Concept Vehicles - Incorporates automatic vehicle location technology (AVL) to monitor resources along with maintenance products to facilitate quicker response to rapidly changing winter conditions. Additional products such as traction measuring devices and advance salt spreaders would be used to minimize material cost by determining road surface conditions in real-time and adjusting the amount of material released. An initial project phase may involve a less “high-tech” solution by incorporating reader technology on each vehicle and each maintenance yard entrance to facilitate collection of critical operations data. 6.1.5.1 High Level Physical Architecture: Figure 6-256-26 shows the high level physical architecture for the Winter Weather Maintenance Enhancement project.

Figure 6-256-26: High Level Physical Architecture for the Winter Weather Maintenance

Enhancement Project

6.1.5.2 Interconnect Diagram: Figure 6-27 shows an interconnect diagram, which highlights the path along which data will travel from the roadway subsystems to the maintenance management subsystems and traffic management subsystem (TMMCC). Data on weather conditions will be collected by roadside equipment that will relay the information back to a maintenance dispatch center that in turn North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


provides operational instructions to its vehicles. Maintenance activities or status can be coordinated between highway dispatch centers or in response to requests generated by the TMMCC.




Maintenance Dispatch_Vehicles













O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT HighwayMaintenance Dispatch_Vehicles

ExistingPlanned

Figure 6-27: Interconnect Diagram for the Winter Weather Maintenance Enhancement Project

Figure 6-28 further identifies individual agency roles and responsibilities for the Winter Weather Maintenance Enhancement project.

Agency


1. Traffic Management and Maintenance Control Center - Dixon 2. IDOT Maintenance Facilities (in Ogle, Winnebago, DeKalb, and Boone Counties)

Primary control and operations of RWIS and AFLADS field equipment

Report current environment conditions (e.g., air temperature, wind speed, surface temperature) as measured by environmental sensors and communicated by supporting field equipment


Primary control of maintenance vehicles Coordination and joint operation of maintenance vehicles

and equipment in adjacent municipalities Determine driver availability, service instructions to

driver, and driver route assignment Perform maintenance on vehicles Record current status, location, and operating conditions

of maintenance vehicles Implement event response procedures Report event status, location, type, and severity to initiate

a coordinated maintenance response Manage maintenance operations via a system operator

having access data collected by sensors

Figure 6-28: Agency Roles and Responsibilities for the Winter Weather Maintenance Enhancement Project











Maintenance Dispatch_VehiclesOgle County IDOT Highway

Maintenance Dispatch_RoadsideEquipment

maintenance responseOM driver instructions

maintenance responseenvironmental conditions status

OM request for vehicle measuresOM vehicle conditions

OM vehicle location dataOM vehicle logging

maintenance requestmaintenance request

Figure 6-29: Architecture Flow Diagram for the Winter Weather Maintenance Enhancement

Project

ExistingPlannedFigure 6-30 contains the architecture flow definitions, which describe the data being

exchanged between subsystems in the diagram above.

6.1.5.4 Architecture Flow Definitions:

Architecture Flow

Definition

environmental conditions Current environment conditions (e.g., air temperature, wind speed, surface temperature) as measured by environmental sensors and communicated by supporting field equipment.





OM driver instructions Service instructions for maintenance vehicle drivers. OM request for vehicle measures

Request for vehicle performance and maintenance data collected by onboard sensors.

OM vehicle conditions Operating conditions of maintenance vehicle (e.g., mileage). OM vehicle location data Current vehicle location and related operational conditions data provided by a vehicle. OM work logging Orders for maintenance of maintenance vehicle or other maintenance equipment.

Figure 6-30: Architecture Flow Diagram Definitions for the Winter Weather Maintenance Enhancement Project.

6.1.5.5 Identification of Applicable ITS Standards The North-Central Illinois Regional Architecture expands on the National ITS Architecture by introducing Operations and Maintenance subsystems. However, unlike other subsystems identified in the National Architecture there are no existing or developing standards associated with the operations and maintenance elements. Work is currently being done to add operations and maintenance elements to the National ITS Architecture in the future and North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


at that time, there likely will be new standards recommended or modifications of existing standards to include the new elements. Hence there are no applicable standards identified here. 6.1.6 Project 6 - Arterial Dynamic Message Signs & Dynamic Trailblazer Signing The Arterial Dynamic Message Signs (DMS) and Dynamic Trailblazer Signing project is meant to assist motorists by providing them with alternate route signing and timely information on planned and unplanned incidents. Through using DMS and dynamic trailblazers on arterials, motorists are supported with real-time guidance along alternate routes during special events, construction, maintenance, or traffic incidents that impact travel. DMS can display information on a planned event location, alternate routes, estimated travel time, road construction, or an existing incident. Dynamic trailblazer signs change direction to “point out” an alternate way around these incidents. Supplemental dynamic signing along the currently planned alternate route that traverses Illinois and Wisconsin along Rte. 76 to the east of I-39 will help reduce the total amount of resources required to support rerouting of traffic. 6.1.6.1 High Level Physical Architecture: Figure 6-31 shows the high level physical architecture for the Arterial Dynamic Message Signs and Dynamic Trailblazer Signing project. It illustrates how the project will connect roadway subsystems with a single traffic management subsystem.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



TrafficManagement

TrafficManagement

RoadwayRoadway


Figure 6-31: High Level Physical Architecture Diagram for the Arterial Dynamic Message

Signs and Dynamic Trailblazer Signing Project

6.1.6.2 Interconnect Diagram:



Figure 6-32 shows an interconnect diagram, which highlights the relationship between the traffic management, maintenance, and the roadway subsystem elements. The diagram is a high level view of data paths that reveals how information will be routed between different subsystems. The current diagram shows that RWIS and pavement conditions monitoring equipment located along the roadway will relay data and information directly to a

management center in that Transportation District. The traffic management center shares road condition information between the various county agencies.

Traffic Management_City of Belvider...City of Belvidere Department of Public

Works




Office


Center Madison



Figure 6-32: Interconnect Diagram for the Arterial Dynamic Message Signs and Dynamic

Trailblazer Signing Project

ExistingPlannedFigure 6-33 further identifies the roles and responsibilities for the Arterial Dynamic Message

Signs and Dynamic Trailblazer Signing project.

Agency




Control and operate arterial dynamic message signs, and dynamic trailblazer signs, detectors, and surveillance images



Detection and verification of incidents Detect and respond to field equipment failure

1. City of Rockford Department of Public Works 2. City of Belvidere Department of Public Works

Secondary control and operations of field equipment in District 2 (long-term)

WisDOT District 1 Corridor Transportation Management Center - Madison

Share information on Traffic Management and Traveler Information Activities when incident has multi-state impacts.

Share traveler information system data to ensure consistent information is share across state lines

Figure 6-33: Agency Roles and Responsibilities for the Arterial Dynamic Message Signs and Dynamic Trailblazer Signing Project



6.1.6.3 Architecture Flow Diagram: Figure 6-34 shows an architecture flow diagram for the typical data exchanges between agency subsystems.

Traffic Management_City of Belvidere_Departm...City of Belvidere Department of Public Works

Traffic Management_Illinois State Department o...Traffic Management and Maintenance Control

Center_Dixon


Office


Center Madison














Figure 6-34: Interconnect Diagram for the Arterial Dynamic Message Signs and Dynamic

Trailblazer Signing Project

ExistingPlannedFigure 6-35 contains the architecture flow definitions, which describe the data being

exchanged between subsystems in the diagram above.

6.1.6.4 Architecture Flow Definitions:

6.1.6.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-36 identifies applicable ITS standards that would support the deployment of the Arterial Dynamic Message Signs and Dynamic Trailblazer Signing Project.



Architecture Flow

Definition




incident data Data and imagery from the roadside supporting incident detection and verification. roadway information system data






signal control data Information used to configure and control traffic signal systems. traffic control coordination Information transfers that enable remote monitoring and control of traffic management

devices. This flow is intended to allow cooperative access to, and control of, field equipment during incidents and special events and during day-to-day operations. This flow also allows 24-hour centers to monitor and control assets of other centers during off-hours, allows system redundancies and fail-over capabilities to be established, and otherwise enables integrated traffic control strategies in a region.





Figure 6-35: Architecture Flow Diagram Definitions for the Arterial Dynamic Message Signs and Dynamic Trailblazer Signing Project



Organization

Standard Name

Document ID

AASHTO Simple Transportation Management Framework (STMF) NTCIP 1101 AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Dynamic Message Signs NTCIP 1203 AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather NTCIP 1204 AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices NTCIP 1206 AASHTO Ramp Meter Controller Objects NTCIP 1207 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Message Set for Weather Reports NTCIP 1301 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for Simple Transportation Management Framework NTCIP 2301 AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304 AASHTO Application Profile for Common Object Request Broker Architecture NTCIP 2305 AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502 ITE Standard for Functional Level Traffic Management Data Dictionary ITE TM 1.03 ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01 SAE Data Dictionary for Advanced Traveler Information System (ATIS) SAE J2353 SAE Message Set for Advanced Traveler Information System (ATIS) SAE J2354 SAE Rules for Standardizing Street Names and Route IDs SAE J2529 SAE Messages for Handling Strings and Look-Up Tables in ATIS Standards SAE J2540

Figure 6-36: Applicable ITS Standards for the Arterial Dynamic Message Signs and Dynamic Trailblazer Signing Project

6.1.7 Project 7 - Construction Work Zone Safety, Traffic Monitoring and Traveler

Information The Construction Work Zone Safety, Traffic Monitoring and Traveler Information project is designed to monitor and detect fluctuations in traffic conditions influenced by construction activity or unplanned incidents. Many of the same roadside elements that support data collection, traffic monitoring, and broadcast activities for regional traffic management can be incorporated into the localized nature of construction work zones. Other strategies such as dynamic speed limits and changeable no passing zones can significantly improve safety within work zones. Traffic detector stations, portable dynamic message signs, closed circuit television cameras, and highway advisory radio all support a mobile traffic management center that can act as a stand alone facility with its own personnel, or route the data and control of roadside devices back to a stationary regional transportation management center. Many of the roadside elements are temporarily placed along the work zone and can be easily



moved to a new location. Because work zones tend to restrict movement of vehicles by reducing travel speeds and/or the number of travel lanes, an unplanned incident such as a crash or vehicle breakdown can severely cripple traffic flow. To minimize the impact of incidents, sharing traffic data with local emergency management agencies can assist them to respond more rapidly. 6.1.7.1 High Level Physical Architecture: Figure 6-37 shows the high level physical architecture that identifies which portions of the Regional ITS Architecture are being used for the Construction Work Zone Safety, Traffic Monitoring and Traveler Information project. The project includes connections between roadway subsystems, traffic management, and emergency management subsystems.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

ManagementDe

dica

ted

Shor

t Ran

geCo

mm

unic

atio

ns

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

ManagementDe

dica

ted

Shor

t Ran

geCo

mm

unic

atio

ns

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



TrafficManagement

TrafficManagement

RoadwayRoadway


EmergencyManagementEmergency

Management

Figure 6-37: High Level Physical Architecture for the Construction Work Zone Safety,

Traffic Monitoring, and Traveler Information Project

6.1.7.2 Interconnect Diagram: Figure 6-38 shows a typical interconnect diagram highlighting the relationship between agencies responsible for traffic operations and response in and surrounding work zones. The diagram is a high level view of data paths that reveals how information will be routed between the different subsystems. The current diagram shows a very simple data link between the roadway and TMMCC, which exchanges data with maintenance and emergency management agencies.



EM_County of Boone_Sheriff Depart...Boone County 911 Center







ExistingPlanned

Figure 6-38: Interconnect Diagram for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project

Figure 6-39 further identifies the roles and responsibilities for the Construction Work Zone Safety, Traffic Monitoring and Traveler Information project.

Agency



Coordination with Construction Unit to ensure equipment is positioned properly during staging.

Primary maintenance of Construction Work Zone Safety, Traffic Monitoring and Traveler Information field equipment


Primary operations of Construction Work Zone Safety, Traffic Monitoring and Traveler Information field equipment

Use Construction Work Zone Safety, Traffic Monitoring and Traveler Information to support Incident Management Activities

IDOT District 2 Construction Secondary operations of Construction Work Zone Safety, Traffic Monitoring and Traveler Information field equipment

County 911 Dispatch Centers (Boone, DeKalb, Ogle, and Winnebago Counties)

User of Construction Work Zone Safety, Traffic Monitoring and Traveler Information. Provide Back-up operations of Dynamic Message Signs

Figure 6-39: Agency Roles and Responsibilities for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project





Traffic Management_Illinois State Department of Transportation_Distri...Traffic Management and Maintenance Control Center_Dixon



Traffic Management_Illinois State Department of Transportation_Distri...Traffic Management and Maintenance Control Center_Dixon_Roadside

Equipment




work zone closure statuscurrent network conditions

emergency traffic control responseincident information

incident information requestresource deployment status


work zone closure coordinationfreeway control data

roadway information system datasensor and surveillance control




ExistingPlanned

Figure 6-40: Interconnect Diagram for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project


Architecture Flow

Definition

current network conditions Current traffic information, road conditions, and camera images that can be used to locate and verify reported incidents, and plan and implement an appropriate response.

emergency traffic control response

Status of the special traffic signal control strategy implemented in response to the emergency traffic control request.




incident data Data and imagery from the roadside supporting incident detection and verification. incident information Notification of existence of incident and expected severity, location, time and nature of

incident. incident information request

Request for incident information, clearing time, severity. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.

incident response status Status of the current incident response including traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides).





remote surveillance control The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.

resource deployment status Status of traffic management center resource deployment identifying the resources



Architecture Flow

Definition available and their current deployment status.

resource request A request for traffic management resources to implement special traffic control measures, assist in clean up, verify an incident, etc.







traffic equipment status Identification of field equipment requiring repair and known information about the associated faults.



work zone closure status Status of maintenance work zone closure. work zone closure coordination

Planned closure response procedures, resource coordination, and current event response status of maintenance work zone closure.

Figure 6-41: Architecture Flow Diagram Definitions for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project

6.1.7.5 Identification of Applicable ITS standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-42 identifies applicable ITS standards that would support the deployment of the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project.

Organization

Standard Name

Document ID

AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304 AASHTO Application Profile for Common Object Request Broker Architecture NTCIP 2305 AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502 ASTM ADMS Standard Guidelines ASTM AG ASTM ADMS Data Dictionary Specifications ASTM DD IEEE Standard for Public Safety IMMS for use by EMCs IEEE P1512.2 IEEE Standard for Emergency Management Data Dictionary IEEE P1512.a

IEEE Standard for Common Incident Management Message Sets (IMMS) for use by EMCs IEEE P1512-2000

ITE Standard for Functional Level Traffic Management Data Dictionary ITE TM 1.03 ITE Message Sets for External TMC Communication (MS/ETMCC) ITE TM 2.01 ITE TCIP - Spatial Representation (SP) Business Area Standard NTCIP 1405

Figure 6-42: Applicable ITS Standards for the Construction Work Zone Safety, Traffic Monitoring, and Traveler Information Project



6.1.8 Project 8. Advanced Rail Crossing Notification System North Central Illinois experiences a significant amount of rail traffic that is generated from the industrial areas of Chicago and Detroit. To enhance roadway safety, Advanced Rail Crossing Notification Systems are proposed for locations in DeKalb, Rochelle, and Rockford. Components of a typical advanced rail crossing notification system can detect and measure train detection, train travel direction, estimated time of arrival, estimated duration of closure, and entrapped vehicles. When integrated with other traveler information (dynamic message signs), traffic management (coordination with adjacent traffic signals) and emergency management systems (blocked vehicle alarm / notification), the components collectively provide significant safety and travel efficiency benefits. High Level Physical Architecture: Figure 6-43 shows the high level physical architecture for the Advanced Rail Crossing Notification project. It illustrates how the project will connect roadway subsystems (specifically equipment associated with rail crossings) and traffic management subsystems.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



TrafficManagement

TrafficManagement

RoadwayRoadway


Figure 6-43: High Level Physical Architecture for the Advanced Rail Crossing Notification

Project

6.1.8.1 Interconnect Diagram: Figure 6-44 shows a typical interconnect diagram, which highlights the relationship between agencies that would participate in Advanced Rail Crossing Notification project.




Works


Works_Roadside EquipmentRailroad Company Dispatch Centers

ExistingPlanned

Figure 6-44: High Level Physical Architecture for the Advanced Rail Crossing Notification Project

Figure 6-45 further identifies roles and responsibilities for the Advanced Rail Crossing Notification project.

Agency


Railroad Company Dispatch Centers Install, operate and maintain equipment Provide outputs to support modified operation of

adjacent traffic signals and traveler information devices Provide information to appropriate emergency

management agency when vehicle trapped alarm is activated

1. City of Rockford Department of Public Works 2. City of DeKalb Department of Public Works 3. IDOT District 2 Maintenance Facilities (in Ogle, Winnebago, DeKalb, and Boone Counties)

Install, operate, and maintain adjacent traffic signals and traveler information devices

Figure 6-45: Agency Roles and Responsibilities for the Advanced Rail Crossing Notification Project

6.1.8.2 Architecture Flow Diagram: Figure 6-46 shows a typical architecture flow diagram highlighting the typical data exchanges between the project’s subsystems. Some agencies have been excluded to emphasize the types of information exchanges by removing duplicate information.


Works

Railroad Company Dispatch CentersTraffic Management_City of DeKalb_...

City of DeKalb Department of PublicWorks_Roadside Equipment

hri advisorieshri control data

hri requesthri status

intersection blockage notification

ExistingPlanned

Figure 6-46: Architecture Flow Diagram for the Advanced Rail Crossing Notification Project




Architecture Flow

Definition

hri advisories Notification of Highway-Rail Intersection equipment failure, intersection blockage, or other condition requiring attention, and maintenance activities at or near highway rail intersections.

hri control data Data required for HRI information transmitted at railroad grade crossings and within railroad operations.

hri request A request for highway-rail intersection status or a specific control request intended to modify HRI operation.

hri status Status of the highway-rail intersection equipment including both the current state or mode of operation and the current equipment condition.

intersection blockage notification

Notification that a highway-rail intersection is obstructed and supporting information.

Figure 6-47: Architecture Flow Diagram Definitions for the Advanced Rail Crossing Notification Project

6.1.8.4 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-48 identifies applicable ITS standards that would support the deployment of the Advanced Rail Crossing Notification Project.

Organization

Standard Name

Document ID

AASHTO Simple Transportation Management Framework (STMF) NTCIP 1101 AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Dynamic Message Signs NTCIP 1203 AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather NTCIP 1204 AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices NTCIP 1206 AASHTO Ramp Meter Controller Objects NTCIP 1207 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for Simple Transportation Management Framework NTCIP 2301 AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 AASHTO Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304 AASHTO Application Profile for Common Object Request Broker Architecture NTCIP 2305 AASHTO Information Profile for DATEX NTCIP 2501 AASHTO Information Profile for CORBA NTCIP 2502

Figure 6-48: Applicable ITS Standards for the Advanced Rail Crossing Notification Project North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


6.1.9 Project 9 – Supplemental Emergency Vehicle Traffic Signal Preemption Supplemental emergency vehicle traffic signal preemption in North Central Illinois will support traffic incident management activities and the overall quality of service provided by local emergency service agencies. Emergency vehicle preemption equipment allows a signal to temporarily modify its timing when activated by either a transmitter mounted on an approaching vehicle or by a specific, predefined acoustical characteristic of a siren. While some intersections in North Central Illinois are already operating with preemption equipment, the project would include equipping all traffic signals on Illinois state routes with preemption apparatus. If optical preemption equipment is installed, it is assumed local agencies would be burdened with equipping each emergency vehicle with a transmitter. 6.1.9.1 High Level Physical Architecture: Figure 6-49 shows the high level physical architecture for the Supplemental Emergency Vehicle Traffic Signal Preemption project. It illustrates how the project will connect roadway subsystems (traffic signal preemption equipment) with a vehicle and traffic management subsystem.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Roadway


Roadway


VehicleVehicle

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

TrafficManagement


Figure 6-49: Architecture Flow Diagram for the Supplemental Emergency Vehicle Traffic

Signal Preemption Project

6.1.9.2 Interconnect Diagram: Figure 6-50 shows the interconnect diagram, which highlights the relationship between the different traffic management agencies (subsystems), the roadway (subsystem), and emergency vehicle elements. The diagram is a high level view of data paths that reveals how information will be routed between different subsystems. The current diagram simply indicates that roadside equipment, located in City of Sycamore, will connect to roadside equipment, which will use preemption to move emergency vehicles through a signalized intersection.



Traffic Management_City of Sycamor...City of Sycamore Department of Public

Works



Fire and EMS Vehicles

ExistingPlanned

Figure 6-50: High Level Physical Architecture Diagram for the Supplemental Emergency Vehicle Traffic Signal Preemption Project

Figure 6-51 further identifies roles and responsibilities for the Supplemental Emergency Vehicle Traffic Signal Preemption project.

Agency



Maintain emergency vehicle preemption equipment installed on IDOT operated signals

Local Department of Public Works (ex. City of Sycamore) Maintain emergency vehicle preemption equipment installed on Illinois State Routes operated signals

Fire and EMS Vehicles Exclusive user of emergency vehicle preemption equipment

Figure 6-51: Agency Roles and Responsibilities for the Supplemental Emergency Vehicle Traffic Signal Preemption Project

6.1.9.3 Architecture Flow Diagram: Figure 6-52 shows a sample architecture flow diagram highlighting the typical data exchanges between a traffic management center and a roadway subsystem for the Supplemental Emergency Vehicle Traffic Signal Preemption project.


Works



Fire and EMS Vehicles


fault reportsrequest for right-of-way


traffic imageslocal signal preemption request

ExistingPlanned

Figure 6-52: Architecture Flow Diagram for the Supplemental Emergency Vehicle Traffic Signal Preemption Project

6.1.9.4 Architecture Flow Definitions: Figure 6-53 contains the architecture flow definitions, which describe the data being exchanged between subsystems in the diagram above. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


Architecture Flow

Definition

fault reports Reports from field equipment (i.e. sensors, signals, signs, controllers, etc.) which indicate current operational status.

signal preemption request Direct control signal or message to a signalized intersection that results in preemption of the current control plan and grants right-of-way to the requesting vehicle

request for right-of-way Forwarded request from signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.

sensor and surveillance control Information used to configure and control sensor and surveillance systems at the roadside. signal control data Information used to configure and control traffic signal systems. signal control status Status of surface street signal controls. traffic flow Raw and/or processed traffic detector information which allows derivation of traffic flow variables

(e.g., speed, volume and density measures). traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use

in machine vision applications.

Figure 6-53: Architecture Flow Diagram Definitions for the Supplemental Emergency Vehicle Traffic Signal Preemption Project

6.1.9.5 Identification of Applicable ITS Standards ITS standards serve as a basis for supporting the initial deployment of a project concept and later its integration with the regional architecture and other deployed systems. Several standards have been developed by different organizations that support the deployment of the National ITS Architecture. Figure 6-54 identifies applicable ITS standards that would support the deployment of the Supplemental Emergency Vehicle Traffic Signal Preemption Project.

Organization

Standard Name

Document ID

AASHTO Simple Transportation Management Framework (STMF) NTCIP 1101 AASHTO Base Standard: Octet Encoding Rules (OER) NTCIP 1102 AASHTO Simple Transportation Management Protocol (STMP) NTCIP 1103 AASHTO Global Object Definitions NTCIP 1201 AASHTO Object Definitions for Actuated Traffic Signal Controller Units NTCIP 1202 AASHTO Object Definitions for Environmental Sensor Stations & Roadside Weather NTCIP 1204 AASHTO Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205 AASHTO Data Collection & Monitoring Devices NTCIP 1206 AASHTO Object Definitions for Video Switches NTCIP 1208 AASHTO Transportation System Sensor Objects NTCIP 1209 AASHTO Objects for Signal Systems Master NTCIP 1210 AASHTO Objects for Signal Control Priority NTCIP 1211 AASHTO Class B Profile NTCIP 2001 AASHTO Point to Multi-Point Protocol Using RS-232 Subnetwork Profile NTCIP 2101 AASHTO Subnet Profile for PMPP Over FSK modems NTCIP 2102 AASHTO Subnet Profile for Point-to-Point Protocol using RS 232 NTCIP 2103 AASHTO Subnet Profile for Ethernet NTCIP 2104 AASHTO Transportation Transport Profile NTCIP 2201 AASHTO Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202 AASHTO Application Profile for Simple Transportation Management Framework NTCIP 2301 AASHTO Application Profile for Trivial File Transfer Protocol NTCIP 2302 AASHTO Application Profile for File Transfer Protocol (FTP) NTCIP 2303 ASTM Standard Specification for 5.9 GHz Data Link Layer ASTM N/A ASTM Standard Specification for 5.9 GHz Physical Layer ASTM N/A

ASTM Specification for Dedicated Short Range Communication (DSRC) Data Link Layer: Medium Access and Logical Link Control ASTM PS 105-99

ASTM Specification for Dedicated Short Range Communication (DSRC) Physical Layer using Microwave in the 902-928 MHz ASTM PS 111-98

IEEE Security/Privacy of Vehicle/RS Communications including Smart Card Communications IEEE P1556

Figure 6-54: Applicable ITS Standards for the Supplemental Emergency Vehicle Traffic Signal Preemption Project



6.2 Deployment Schedule for Project Concepts Timeframe estimates for deployment of each project concept are presented in Figure 6-55. Based on feedback collected from stakeholders, a strong interest has been expressed to have the bulk of projects started within the next 12 to 24 months. However, based on the current budgetary and political environments these estimates will require re-evaluation. The majority of the projects, once started, would take between three and four years to design and deploy.

Project Concept 1 2 3 4 5 6 7 8 9 10Project 1: Traffic Management and Maintenance Control Center 1a. Phase 1 - Upgrade of Existing Dispatch Facility in Dixon 1b. Phase 2 - New Facility - Addition or Stand AloneProject 2: Interstate Traffic Monitoring & Traveler InformationProject 3: Advanced Signal Ops./Coord. & Surface Street Traffic MonitoringProject 4: Agency Data SharingProject 5: Winter Weather Maintenance Enhancements 5a. RWIS 5b. Automated Bridge De-Icing 5c.Maintenance Snow and Ice Management Concept Vehicles Project 6: Arterial Dynamic Message Signs & Dynamic Trailblazer SigningProject 7: Construction Work Zone Safety, Traffic Monitoring & Traveler Info.Project 8: Advanced Rail Crossing Notification SystemProject 9: Supplemental Emergency Vehicle Traffic Signal Preemption

Timeframe for Deployment (years)

Figure 6-55: Timeframe for Deployment of Regional Project Concepts



7 System Architecture A system or regional architecture serves the same function as the National ITS Architecture. Using the National Architecture as a model the regional architecture can be described as a tool that “…provides a common structure for the design of intelligent transportation systems. It is not a system design nor is it a design concept. What it does is define the framework around which multiple design approaches can be developed, each one specifically tailored to meet the individual needs of the user, while maintaining the benefits of a common architecture…”3 Using the National ITS Architecture to generate a regional model requires an understanding of the national architecture’s basic elements. General awareness of these elements further assists in the presentation of the information and a greater chance that information is applied. The National ITS Architecture is comprised of two architectures referred to as the physical and logical. The physical architecture piece of the National Architecture deals with the interaction of real-world elements such as an agency center, a traveler, roadside equipment, or a vehicle. Conversely, the logical architecture defines the processes that carry out different ITS functions by establishing the data being exchanged and the form the data will take. Both the logical and physical architectures serve as mechanisms to describe the interaction of various elements in the architecture, and are beneficial in different ways. A physical architecture is easier to comprehend since it deals with tangible and more widely understood transportation elements such as a vehicle, equipment, a roadway, or dispatch center and establishes how those elements can be connected to form a system. The logical architecture deals with processes and functions typically hidden from view, but required to perform some action such as a database query. The North-Central Illinois Regional ITS Architecture is essentially a high-level physical architecture. The regional architecture shown will illustrate the interconnection between different regional centers, vehicles, roadside equipment, and travelers along with the data that is exchanged between them. Although a logical architecture is not presented as part of the regional architecture, elements of the logical architecture are present in the physical architecture’s “architecture flows”.

7.1 Overview of the Physical Architecture The Physical Architecture, as mentioned, is part of the National ITS Architecture and is used to portray real-world transportation facilities and infrastructure elements. The Physical Architecture uses a set of 19 subsystems, which represent and describe different transportation elements. The physical architecture also details the interaction between those elements. The Physical Architecture is referenced as a “high-level view” of the National Architecture, since it deals with “physical” elements and not the function or data exchanges behind the operation of those elements, which is performed under the Logical Architecture. The Physical



3 Lockheed Martin Federal System, Odetics Intelligent Transportation Systems Division, National ITS Architecture: Executive Summary, Federal Highway Administration, U.S. Department of Transportation, Washington D.C., December 1999, page 3.

Architecture serves as a way to define how agencies, roadside equipment, travelers, and vehicles are connected and how basic information is shared between them. There are three components that make up the Physical Architecture, they are:

Subsystems Terminators Flow

There are also three diagrams typically used to illustrate how information is shared between components in the physical architecture and are referenced as:

“Sausage Diagram” Interconnect Flow Diagram Architecture Flow Diagram

Each physical architecture element and diagram is explained in the following sections to generate an understanding of how they portray actual transportation infrastructure elements and the interaction between those elements. 7.1.1 Subsystems Under the National ITS Architecture the physical architecture contains facilities and infrastructure elements that are grouped into four classes of “subsystems”. The four classes of subsystems are identified as centers, roadside, vehicles, and travelers. Each class is described below using the definition adopted from the National ITS Architecture. Center Subsystems: Subsystems that provide management, administrative, and support functions for the transportation system. The center subsystems each communicate with other centers to enable coordination between modes and across jurisdictions. The nine center subsystems are Traffic Management, Transit Management, Commercial Vehicle Administration, Archived Data Management, Emissions Management, Toll Administration, Emergency Management, Information Service Provider, and Fleet and Freight Management. One of four general subsystem classes defined in the National ITS Architecture.4 Roadside Subsystems: Intelligent infrastructure distributed along the transportation network which perform surveillance, information provision, and plan execution control functions and whose operation is governed by center subsystems. Direct interface to vehicle subsystems exist. One of four general subsystem classes defined in the National ITS Architecture.5 Vehicle Subsystems: Covers ITS related elements on vehicle platforms. Vehicle subsystems include general driver information and safety systems applicable to all vehicle types. Three fleet vehicle subsystems (Transit, Emergency, and Commercial Vehicles) add ITS capabilities unique to these special vehicle types. One of four general subsystem classes defined in the National ITS Architecture.6 Traveler Subsystems: Equipment used by travelers to access ITS services pre-trip and en-route. This includes elements that are owned and operated by the traveler as well as elements that are owned by



4 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Center Subsystem 5 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Roadside Subsystem 6 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Vehicle Subsystem

transportation and information providers. One of four general subsystem classes defined in the National ITS Architecture.7

TravelerSubsystem

VehiclesSubsystem

Roadside Subsystem

CenterSubsystem

TravelerSubsystem

VehiclesSubsystem

Roadside Subsystem

CenterSubsystem

Figure 7-1: Physical Architecture Subsystems Classes

Nineteen different subsystems are organized under each of the four classes and defined under the National ITS Architecture. Each of the 19 subsystems corresponds to real-world elements such as a transit management facility, traffic controller, vehicle, or motorist. Chapter 11 contains a listing of the different physical architecture subsystems, specifies which are applicable to the regional architecture, and defines them. 7.1.2 Terminators Terminators represent the limits of the National ITS Architecture. In the physical architecture terminators function as boundaries for information exchanged. Typically, terminators only interact with a single subsystem and to not link together multiple system elements similar to subsystems. There are four categories of terminators. These categories are environment, human, other system, and system. Chapter 12 contains tables listing the different terminators, and points out and defines those that are applicable to the North-Central Illinois Regional ITS Architecture. 7.1.3 Sausage Diagram The “Sausage Diagram” is considered the top-level interconnect diagram for the National ITS Architecture. It illustrates how different subsystems connect and the communication methods that facilitate the data exchanges between them. As a top-level diagram it only shows the interconnection between different subsystems and does not provide specific details on the exact information and data exchanged.



7 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Traveler Subsystem

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Access

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Figure 7-2: Physical Architecture Sausage Diagram

7.1.4 Interconnect Flow Diagram The interconnect flow diagram highlights the communication interaction between multiple subsystems or between a subsystem and terminators. The diagram details communication paths between the architecture elements showing how information is routed. The type of communications system reflected by the interconnect flow can be one of four types that include wireline, wide area wireless, dedicated short range, or vehicle to vehicle. Additional communications types such as human and physical/environmental interfaces can also be represented by interconnect flows.

Subsystem Subsystem TerminatorTraffic ManagementCenter

Transit Dispatch Center

Traffic OperationsPersonnel

SubsystemSubsystem SubsystemSubsystem TerminatorTerminatorTraffic ManagementCenter


Traffic OperationsPersonnel

Figure 7-3: Physical Architecture “Interconnect” Diagram

7.1.5 Architecture Flow Diagram The architecture flow diagram further elaborates on the information provided by the interconnect flow diagram. Whereas the interconnect diagram indicates the communication path between elements, the architecture flow diagram details the information exchanged on that path. Typically a single interconnect flow represents one or more architecture flows which detail the type and direction information exchanges on the interconnect take between subsystems or terminators in the system.



SubsystemSubsystem SubsystemSubsystemTraffic ManagementCenter


Traffic Information for TransitRequest Transit Information

Transit System DataDemand Mgmt. Response

Figure 7-4: Physical Architecture “Architecture Flow” Diagram

7.2 Overview of the Logical Architecture Another architecture contained within the National ITS Architecture is referred to as the Logical Architecture. The Logical Architecture describes the functionality of an ITS system and details how user services are supported. It establishes the processes that execute the functionality and the information distributed between those processes. The Logical Architecture, like the physical architecture, does not mandate a particular technology for implementation, rather it allows for flexibility in system deployment. The Logical Architecture uses the following elements to define and illustrate system functionality:

Processes Process Specifications Data Flows Data Dictionary Entries Data Flow Diagram

The North-Central Illinois Regional ITS Architecture is a physical architecture, however, the various physical architecture elements can be further decomposed to develop a logical architecture. Thus, reviews of the elements that comprise a logical architecture are presented for reference. 7.2.1 Processes A process is a function or activity that is needed to support an ITS User Service. It is utilized in the logical architecture to represent high-level general actions and also more detailed functions. An example of how processes are used to represent general and specific functions can be demonstrated by looking at the general process “Manage Traffic” in the National ITS Architecture. The “Manage Traffic” process identified can be further broken down into the following more detailed processes:

“Provide Traffic Surveillance” “Manage Incidents” “Provide Device Control” “Manage Emissions” “Manage Travel Demand” “Manage Highway Rail Intersections”

Each of the additional processes can be further broken down until you reach “primitive processes”, which represent not only the lowest level process, but also represent the most specific or detail function. North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


7.2.2 Process Specification Process specification is the most detailed processes defined by the logical architecture. It contains a description, list of functional requirements, and a set of inputs and outputs. Process specification generally is referred to as “Pspec”. 7.2.3 Data Flow Data flows represent information exchanged between processes in the logical architecture. Data flows indicate the type and direction information travels between processes. Combinations of data flows are also used to define architecture flows deployed in the physical architecture. Individual data flows are generally defined in a data dictionary entry. 7.2.4 Data Dictionary Entries A data dictionary is used in the logical architecture to describe a data flow’s characteristics. A data dictionary entry (DDE) contains a description of the data flow and highlights additional lower level data elements that are part of that flow. Lower level data elements are also defined by separate DDEs. 7.2.5 Data Flow Diagram The data flow diagram illustrates the processes and data exchanges in a logical architecture. The diagram consists of four elements each with a unique symbol. The functions or processes in the diagram are represented by circles and perform different architecture tasks. Lines with arrows indicate the movement of information or data between diagram elements and represent data flows. “Data at rest” in the system is represented by parallel lines and are referred to as data stores. The last diagram element is a terminator, which is represented by a rectangle and depicts an endpoint or boundary for the architecture. Figure 7-5 models a typical data flow diagram.

Process1

Process3

Process2

Terminator

Data_Flow1

Data_Flow2

Data_Flow3

Data_Flow4

Data_Store

Process1

Process3

Process2

Terminator

Data_Flow1

Data_Flow2

Data_Flow3

Data_Flow4

Data_Store

Figure 7-5: Logical Architecture “Data Flow” Diagram

7.3 Overview of the Regional ITS Architecture The North-Central Illinois Regional ITS Architecture is a physical architecture. The architecture provides a high-level view illustrating how regional agencies, vehicles, and



infrastructure, might be integrated through systems deployed in the future. The architecture is based on the recommendations of different stakeholder agencies that participated in the architecture’s development. The regional architecture starts by representing different regional agencies and transportation elements as subsystems. All subsystems used with one exception were previously established and defined by the National ITS Architecture. Only one new subsystem was created, thus expanding upon the existing national architecture. The additional subsystem is used to represent operations and maintenance centers in North-Central Illinois and is referred to as the Operations and Maintenance subsystem. Based on information collected through agency interviews and workshops, associated user services and market packages were identified for each stakeholder. This stakeholder information was further used during the process of assembling the regional architecture. Specialized software was utilized during the architecture assemble process and, as such, most of the diagrams presented are reproductions of the original software’s generated diagrams.

7.4 High-Level Physical Architecture for North-Central Illinois The National ITS Architecture uses the “sausage diagram” to illustrate the relationship of various architecture elements at a high-level. The high-level diagram functions as a starting point for discussion as to what elements comprise the North-Central Illinois Regional Architecture by first isolating only the elements which are applicable. Figure 7-6 shows the typical sausage diagram with applicable elements highlighted.

Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement



Travelers

Vehicles Roadside

Centers


Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

CommercialVehicle

Administration

ArchivedData

Management

Dedi

cate

d Sh

ort R

ange

Com

mun

icat

ions

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle


PersonalInformation

Acce ss

TollAdministration

EmergencyManagement

TrafficManagement

Fleet andFreight

Management

TransitManagement

EmissionsManagement

InformationService

Provider

Roadway

Toll Collection

ParkingManagement


Wireline CommunicationsWide Area Wireless Communications

Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

ArchivedData

Management

Ded

icat

ed S

hort

Ran

geC

omm

unic

atio

ns

Vehicle

TransitVehicle

EmergencyVehicle


EmergencyManagement

TransitManagement

InformationService

Provider

Roadway

ParkingManagement

Wireline CommunicationsWide Area Wireless Communications

Vehi

cle

to V

ehic

le C

omm

unic

atio

ns

ArchivedData

Management

Ded

icat

ed S

hort

Ran

geC

omm

unic

atio

ns

Vehicle

TransitVehicle

EmergencyVehicle


EmergencyManagement

TrafficManagement

TrafficManagement

InformationService

Provider

Roadway

ParkingManagement


MaintenanceManagementMaintenanceManagement

Physical Architecture Expanded

VehicleVehicle

TransitManagementPersonal

InformationAccess

PersonalInformation

Access

Wide Area Wireless CommunicationsWide Area Wireless Communications Wireline CommunicationsWireline Communications

Toll CollectionToll Collection

TollAdministration

TollAdministration

Figure 7-6: Sausage Diagram with Applicable Regional Architecture Subsystems

Highlighted



Figure 7-6 also shows an addition to the established center subsystems identified by the National Architecture. The additional center subsystem was created as part of the North-Central Illinois Regional Architecture. In North-Central Illinois, as in other parts of the State, the Department of Transportation relies on county maintenance forces to maintain freeways and state trunk highways. As a result, county maintenance facilities typically operate as an established “center of operations” with responsibilities for handling both state and county needs. There is currently no operations and maintenance subsystem defined by the National Architecture. However, there has been discussion and recent work in this area with the possibility that such a subsystem may be added to the National ITS Architecture in the future. To facilitate including operations and maintenance stakeholders in the regional architecture the Maintenance Management subsystem was created.

7.5 Defining the Regional Subsystems There are 12 subsystems identified as part of the North-Central Illinois Regional ITS Architecture. Six of the subsystems are classified as “Center” and can be directly associated with agency stakeholders in the region. Of the other remaining seven only the parking management subsystem can also be directly associated to agency stakeholders in the region. The other six subsystems represent roadside equipment, vehicles, or traveler support elements that interact with or are controlled by the other seven but can not be directly associated with any specific agency. The following briefly describes each of the subsystems used in the North-Central Illinois Regional ITS Architecture and identifies associated stakeholder agencies involved or groups benefited by each subsystem.

Traffic Management: The Traffic Management Subsystem operates within a traffic management center or other fixed location. This subsystem communicates with the Roadway Subsystem to monitor and manage traffic flow. Incidents are detected and verified and incident information is provided to the Emergency Management Subsystem, travelers (through Roadway Subsystem Highway Advisory Radio and Dynamic Message Signs), and to third party providers. … The subsystem communicates with other Traffic Management Subsystems to coordinate traffic information and control strategies in neighboring jurisdictions. 8 Associated regional traffic management stakeholders include:


Emergency Management: The Emergency Management Subsystem operates in various emergency centers supporting public safety including police and fire stations, search and rescue



8 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Traffic Management Subsystem

special detachments, and HAZMAT response teams. This subsystem interfaces with other Emergency Management Subsystems to support coordinated emergency response involving multiple agencies. 9 Associated regional emergency management stakeholders include:


Information Service Provider: This subsystem collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The subsystem can play several different roles in an integrated ITS. In one role, the ISP provides a general data warehousing function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other ISPs. In this information redistribution role, the ISP provides a bridge between the various transportation systems that produce the information and the other ISPs and their subscribers that use the information. The second role of an ISP is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, real time traffic condition and transit schedule information, yellow pages information, ride matching information, and parking information. 10 Associated regional information service providers would include:

Illinois State Department of Transportation – District 1 Gateway Traveler Information Hub

Transit Management: The transit management subsystem manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, and paratransit services. 11 Associated regional transit management stakeholders would include:



9 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Emergency Management Subsystem 10 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Information Service Provider Subsystem 11 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Transit Management Subsystem

Rockford Mass Transit Operations and Maintenance: The Operations and Maintenance Subsystem manages maintenance vehicle fleets and coordinates with other transportation services. It provides operations, maintenance, and management functions for the local or state government infrastructure. It has a central dispatch and garage management system and supports communication between maintenance Departments and other entities such as emergency response services and traffic management systems. Associated regional operations and maintenance stakeholders include:

IDOT Boone County Highway Department Dispatch IDOT DeKalb County Highway Department Dispatch IDOT Ogle County Highway Department Dispatch IDOT Winnebago County Highway Department Dispatch Boone County Highway Department Dispatch DeKalb County Highway Department Dispatch Ogle County Highway Department Dispatch Winnebago County Highway Department Dispatch City of Rockford Maintenance Dispatch

Archived Data Management: The Archived Data Management Subsystem collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. 12 Associated regional archived data management stakeholders would include:

Illinois State Department of Transportation – District 2 Roadway: This subsystem includes the equipment distributed on and along the roadway which monitors and controls traffic. Equipment includes highway advisory radios, dynamic message signs, cellular call boxes, CCTV cameras and video image processing systems for incident detection and verification, vehicle detectors, traffic signals, grade crossing warning systems, and freeway ramp metering systems. This subsystem also provides the capability for emissions and environmental condition monitoring including weather sensors, pavement icing sensors, fog etc. 13 Associated regional roadway stakeholders would include:

Illinois State Department of Transportation – District 2 Parking Management: The Parking Management Subsystem provides electronic monitoring and management of parking facilities. It supports a DSRC communications link to the Vehicle Subsystem that allows electronic collection of parking fees. It also includes the instrumentation,



12 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Archived Data Management Subsystem 13 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Roadway Subsystem

signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. 14 Associated regional parking management stakeholders include:

Northern Illinois University Parking City of DeKalb Parking City of Rockford Parking

Personal Information Access: This subsystem provides the capability for travelers to receive formatted traffic advisories from their homes, place of work, major trip generation sites, personal portable devices, and over multiple types of electronic media. These capabilities shall also provide basic routing information and allow users to select those transportation modes that allow them to avoid congestion, or more advanced capabilities to allow users to specify those transportation parameters that are unique to their individual needs and receive travel information. 15

Associated regional personal information access stakeholders would include:

Illinois State Department of Transportation – District 2 Transit Agencies

Remote Traveler Support: This subsystem provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes, and at major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access.16 Associated regional remote traveler support beneficiaries would include:

Traveling public

Emergency Vehicle Subsystem: This subsystem resides in an emergency vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient emergency response. The Emergency Vehicle Subsystem includes two-way communications to support coordinated response to emergencies in accordance with an associated Emergency Management Subsystem. Emergency vehicles are equipped with automated vehicle location capability for monitoring by vehicle tracking and fleet management functions in the Emergency Management Subsystem. Using these capabilities, the appropriate emergency vehicle to respond to each emergency is determined. Route guidance capabilities within the vehicle enable safe and efficient routing to the emergency. In addition, the emergency vehicle may be equipped to support signal preemption through communications with the roadside subsystem.17



14 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Parking Management Subsystem 15 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Personal Information Access Subsystem 16 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Remote Traveler Support Subsystem 17 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Emergency Vehicle Subsystem

Associated regional emergency vehicle beneficiaries would include:

Emergency Management Agencies Transit Vehicle Subsystem: This subsystem resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The Transit Vehicle Subsystem collects accurate ridership levels and supports electronic fare collection. An optional traffic signal prioritization function communicates with the roadside subsystem to improve on-schedule performance. Automated vehicle location functions enhance the information available to the Transit Management Subsystem enabling more efficient operations. Onboard sensors support transit vehicle maintenance. The Transit Vehicle Subsystem also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares.18 Associated regional transit vehicle beneficiaries would include:

Transit Agencies Vehicle: This subsystem resides in an automobile and provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel by personal automobile.19 Associated regional vehicle beneficiaries would include:

Traveling public

7.6 Typical Regional Interconnects and Data Exchanges There were approximately 32 stakeholder agencies associated with the development of the North-Central Illinois Regional ITS Architecture, resulting in each agency having its own physical architecture that fits into the larger regional plan. Of those agency architectures many have multiple subsystems and terminators. The final result is a regional architecture for North-Central Illinois, which contains over 500 physical architecture elements excluding interconnects and architecture flows. Due to the number of architecture elements it is not practical to present the entire regional architecture here. However, by presenting several “typical” agency architectures a picture of the larger plan is generated. To provide an understanding of how the stakeholder agencies are connected, a simplified regional interconnect diagram (Figure 7-7) was developed placing the agencies into groups for reference.



18 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Transit Vehicle Subsystem 19 USDOT, National ITS Architecture, Version 3.0, Physical Architecture, Vehicle Subsystem

A

Traffic Management and MaintenanceControl Center

Dixon

Traffic Management_Illinois StateDepartment of Transportation_District 2

Gateway Traveler Information HubSchaumburg

ISP_Illinois State Department ofTransportation_District 1

Archived Data Management SystemDixon

Archived Data Management_IllinoisState Department of

Transportation_District 2

ISTHA Operations AreaDowners Grove

Traffic Management_Illinois State TollHighway Authority_Traffic Engineering

Winnebago County 911 CenterRockford

EM_County of Dane_Public SafetyCommunications

All Other DeKalb County Police/Fire/EMS

EM_County of DeKalb_Police/Fire/EMS

Boone County 911 CenterBelvidere

EM_County of Boone_SheriffDepartment

Ogle County 911 CenterOregon

EM_County of Ogle_Sheriff Department

DeKalb County 911 CenterDeKalb

EM_County of DeKalb_SheriffDepartment

All Other Boone County Police/Fire/EMS

EM_County of Boone_Police/Fire/EMS

ll Ogle County Police/Fire/EMS

EM_County of Ogle_Police/Fire/EMS

DeKalb Dispatch Center

EM_City of DeKalb_Police/Fire/EMS

Northern Illinois University DispatchCenterDeKalb

EM_Northern Illinois University_Police

Rockford Dispatch Center

EM_City of Rockford_Police/Fire/EMS

Belvidere Dispatch Center

EM_City of Belvidere_Police/Fire/EMS

Winnebago County Highway DepartmentDispatchRockford

O&M_County of Winnebago_HighwayDepartment

Boone County Highway DepartmentDispatchBelvidere

O&M_County of Boone_HighwayDepartment

Ogle County Highway DepartmentDispatchOregon

O&M_County of Ogle_HighwayDepartment

DeKalb County Highway DepartmentDispatchDeKalb

O&M_County of DeKalb_HighwayDepartment

City of Rockford Traffic EngineeringOffice

Traffic Management_City ofRockford_Department of Public Works

City of DeKalb Department of PublicWorks Office

Traffic Management_City ofDeKalb_Department of Public Works

Winnebago County Highway DepartmentDispatchRockford

Traffic Management_County ofWInnebago_Highway Department

DeKalb County Highway DepartmentDispatchDeKalb

Traffic Management_County ofDeKalb_Highway Department

Northern Illinois University ParkingFacilities

Parking Managerment_Northern IllinoisUniversity_Parking

City of Rockford Parking Facilities

Parking Managerment_City ofRockford_Parking

City of DeKalb Parking Facilities

Parking Managerment_City ofDeKalb_Parking

All Other Winnebago CountyMaintenance/Public Works Departments

O&M_County ofWinnebago_Maintenance Departments

Rockford Mass Transit District DispatchArea

Transit Management_City ofRockford_Rockford Mass Transit District

Dispatch CenterPecatonica

EM_State of Illinois State Police_District16

Operations AreaFairfield

Traffic Management_Iowa StateDepartment of Transportation_District 5

City of Rockford Maintenance DispatchCenter

O&M_City of Rockford_MaintenanceDepartment

Adjacent County Highway DepartmentsInterconnectedAdjacent 911 Centers Interconnected

NORTHCENTRAL ILLINOIS ORGANIZATIONAL ITS ARCHITECTURE

Dispatch CenterSterling


Dispatch CenterDowner's Grove


All Other Winnebago County Police/Fire/EMS

EM_County of Winnebago_Police/Fire/EMS

Corridor Transportation ManagementCenter

Madison

Traffic Management_Wisconsin StateDepartment of Transportation_District 1

IDOT Maintenance Facilities (in Ogle,WInnebago, DeKalb, and Boone

Counties)

O&M_Illinois State Department ofTransportation _District 2

City of Sycamore Department of PublicWorks Office

Traffic Management_City ofSycamore_Department of Public Works

City of Sandwich Department of PublicWorks Office

Traffic Management_City ofSandwich_Department of Public Works

City of Belvidere Department of PublicWorks Office

Traffic Management_City ofBelvidere_Department of Public Works

Figure 7-7: Simplified Regional Interconnect Diagram



There are seven types or groups of stakeholder agencies identified in Figure 7-7. The groups identified are labeled as:

Emergency Management Traffic Management Operations and Maintenance Transit Management Parking Management Information Service Provider Archived Data Management

The regional architecture is represented by set of typical stakeholder agency architectures. Each agency architecture contains a brief description highlighting its role in the region, an interconnect diagram showing the communications channels between different architecture elements, and an architecture flow diagram detailing the information being exchanged between the architecture elements. 7.6.1 Typical Emergency Management Architecture Emergency management agencies represent local, county, or State Departments such as law enforcement, fire, or safety organizations. The typical emergency management agency physical architecture illustrates a chain of command. The command structure shows local emergency management agencies connected to a broader county Department (such as a county 911 center), which then coordinates activities with state and other adjacent counties emergency management agencies. Figure 7-8 shows a typical emergency management interconnect diagram, here represented by Boone County 911 Center.

EM_County of Boone_Police/Fire/EMSAll Other Boone County

Police/Fire/EMS


EM_City of Belvidere_Police/Fire/EMSBelvidere Dispatch Center

EM_County of Boone_Sheriff Depart...Boone County 911 Center_Personnel

O&M_County of Boone_Highway De...Boone County Highway Department

Dispatch




Works

EM_County of DeKalb_Sheriff Depart...DeKalb County 911 Center


MediaTraffic Management_Illinois State De...Traffic Management and Maintenance



ExistingPlanned

Figure 7-8: Typical Emergency Management Interconnect Diagram



Regional emergency management stakeholder agencies include:


Figure 7-9 is a typical architecture flow diagram for an emergency management agency. It details the information exchanged including its path and direction. Boone County 911 Center continues as an example.


Police/Fire/EMS

EM_County of Boone_Sheriff DepartmentBoone County 911 Center


MediaEM_County of Boone_Sheriff Department

Boone County 911 Center_Personnel





Dispatch




Works

Traffic Management_Illinois State Department of Transportation_District 2Traffic Management and Maintenance Control Center_Dixon

incident reportincident response coordination





emergency operations status




incident information for maintenancerequest request for maintenance


emergency traffic control requestincident information

incident response statusremote surveillance control

resource requestemergency traffic control request



emergency operations request

maintenance deployment status

maintenance deployment statuscurrent network conditions





media information request



resource deployment status


ExistingPlanned

Figure 7-9: Typical Emergency Management Architecture Flow Diagram



7.6.2 Typical Traffic Management Architecture Traffic management agencies consist of local city and State Departments. The typical traffic management physical architecture shows the agency to be acting as a hub receiving information from varying sources including parking structures, event promoters, and other traffic management agencies. That information is used in coordinating field equipment and hardware accordingly. Figure 7-10 shows a typical traffic management interconnect diagram, here represented by the City of Belvidere Traffic Engineer Office.



Works


Works_Personnel





Figure 7-10: Typical Traffic Management Interconnect Diagram

Regional traffic management stakeholders include:


Figure 7-11 is a typical architecture flow diagram for a traffic management agency. It details the information exchanged including its path and direction. City of Belvidere Traffic Engineering Office continues as an example.




Traffic Management_City of Belvidere_Department of Public WorksCity of Belvidere Department of Public Works


Works_Personnel







resource requestcurrent network conditions




freeway control datahri control data

hri requestsensor and surveillance control

signal control datatraffic control coordination




hri statusintersection blockage notification

request for right-of-waysignal control status



ExistingPlanned Figure 7-11: Typical Traffic Management Architecture Flow Diagram

7.6.3 Typical Maintenance Management Architecture Maintenance management agencies are comprised of local city and county Departments. The typical maintenance management architecture shows the agency to be coordinating activities locally and with adjacent agencies. Thus, major events that require a regional response coincide with improved efficiency. Figure 7-12 shows a typical maintenance management interconnect diagram, here represented by the Ogle County Highway Department.



O&M_County of DeKalb_Highway De...DeKalb County Highway Department

Dispatch

O&M_County of Ogle_Highway Depa...Ogle County Highway Department

Dispatch

EM_County of Ogle_Sheriff Departm...Ogle County 911 Center


Dispatch_Driver


Dispatch_Fleet Manager


Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles





O&M_County of Winnebago_Highwa...Winnebago County Highway

Department Dispatch

ExistingPlanned Figure 7-12: Typical Maintenance Management Interconnect Diagram

Regional maintenance stakeholders include:

IDOT Boone County Highway Department Dispatch IDOT DeKalb County Highway Department Dispatch IDOT Ogle County Highway Department Dispatch IDOT Winnebago County Highway Department Dispatch Boone County Highway Department Dispatch DeKalb County Highway Department Dispatch Ogle County Highway Department Dispatch Winnebago County Highway Department Dispatch City of Rockford Maintenance Dispatch

Figure 7-13 is a typical architecture flow diagram, for a maintenance management agency. It details the information exchanged including its path and direction. Ogle County Highway Department continues as an example.




Dispatch

O&M_County of Ogle_Highway DepartmentOgle County Highway Department Dispatch


O&M_County of Ogle_Highway DepartmentOgle County Highway Department Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles



O&M_County of Winnebago_Highway DepartmentWinnebago County Highway Department Dispatch





work zone closure coordination






OM route assignmentOM operations planning data

OM operator displayOM work schedule

OM driver instructionsevent and resource coordination

event report



work zone closure statusmaintenance response

traffic equip maintenance statuswork zone closure status

OM driver availabilityOM fleet manager inputs

OM operator management data

OM maintenance status





work zone closure coordinationevent and resource coordination

event reportmaintenance request


ExistingPlanned Figure 7-13: Typical Maintenance Management Architecture Flow Diagram

7.6.4 Typical Transit Management Architecture Only one transit management agency is represented in the regional architecture. The transit agency is responsible for bus and para-transit activities within a localized area. However, during the architecture development process there was an expressed desire to coordinate future operations with the Traffic Management and Maintenance Control Center. As a result, the typical agency architecture represents this desire and illustrates how that coordination is facilitated. Figure 7-14 shows a typical transit management interconnect diagram, here represented by the Rockford Mass Transit Authority.

Transit Management_City of Rockfor...Rockford Mass Transit District Dispatch

Area


Area_Kiosks


Area_Personnel




Figure 7-14: Typical Transit Management Interconnect Diagram



Regional transit management stakeholders include:

Rockford Mass Transit Figure 7-15 is a typical architecture flow diagram, for a transit management agency. It details the information exchanged including its path and direction. Rockford Mass Transit Authority continues as an example.

Transit Management_City of Rockford_TransitRockford Mass Transit District Dispatch Area


Traffic Management_Illinois State Department of Transp...Traffic Management and Maintenance Control

Center_Dixon


Area_Kiosks


Area_Personnel

transit emergency data

traffic control priority requesttransit demand management response

transit system dataemergency acknowledge

secure area monitoring supporttransit fare payment responses

transit traveler informationtransit operations planning data

transit operator displayemergency notification

secure area surveillance datatransit fare payment requests

transit information user requesttransit fleet manager inputs

transit operator management datarequest transit information

traffic control priority statustraffic information for transit

transit demand management request

transit emergency coordination data

Figure 7-15: Typical Transit Management Architecture Flow Diagram

7.6.5 Typical Parking Management Architecture During the outreach phase there was an expressed desire for future coordination between parking management facilities within a county region. The regional architecture reflects this desire. Figure 7-16 shows a typical parking management interconnect diagram, here represented by the City of DeKalb Parking Structures.




Works

Parking Management_City of DeKalb...City of DeKalb Parking Structures

Parking Management_City of DeKalb...City of DeKalb Parking

Structures_Enforcement

Parking Management_City of DeKalb...City of DeKalb ParkingStructures_Financial

Parking Management_City of DeKalb...City of DeKalb ParkingStructures_Operators

EM_Northern Illinois University_PoliceNorthern Illinois University Dispatch

Center

Figure 7-16: Typical Parking Management Interconnect Diagram

Regional parking management stakeholders include:

Northern Illinois University Parking City of DeKalb Parking

City of Rockford Parking

Figure 7-17 is a typical architecture flow diagram, for a parking management agency. It details the information exchanged including its path and direction. DeKalb Parking Structures continues as an example.


Works



Center

Parking Management_City of DeKalb...City of DeKalb Parking

Structures_Enforcement

Parking Management_City of DeKalb...City of DeKalb ParkingStructures_Financial

Parking Management_City of DeKalb...City of DeKalb ParkingStructures_Operators

parking demand management requestparking instructions


violation notificationpayment request

parking statusparking availability

parking demand management response

transaction status

parking operator inputsrequest for performance data


Figure 7-17: Typical Parking Management Architecture Flow Diagram

7.6.6 Typical Information Service Provider Architecture Currently there is increasing demand to bring information on traffic conditions in a timely manner to those that operate, maintain, or simply use the regional transportation system in a



daily capacity. For that purpose the Illinois Department of Transportation has expressed interest in the development of a Traffic Management and Maintenance Center that handles the collection and distribution of transportation and event related information to interested parties. The TMMC would help collect information to distribute to local agencies and groups outside of the four county region. Figure 7-18 shows the typical information service provider interconnects diagram, here represented by the Traffic Management and Maintenance Center.


System





ExistingPlanned

Figure 7-18: Typical Information Service Provider Interconnect Diagram

Regional parking management stakeholders include:

Illinois State Toll Highway Authority – Downers Grove Operations Area Illinois State Department of Transportation – District 2 IDOT – Gateway Traveler Information System

Figure 7-19 is a typical architecture flow diagram for the Traffic Management and Maintenance Center. It details the information exchanged including its path and direction.


System

Traffic Management_Illinois State Department o...Traffic Management and Maintenance Control

Center_Dixon

Traffic Management_Illinois State Toll Highway ...ISTHA-Operations Downers Grove


fare and price informationlogged special vehicle route

request for traffic informationroad network use

fare and price informationrequest for traffic information


request fare and price informationtraffic information





ExistingPlanned

Figure 7-19: Typical Information Service Provider Architecture Flow Diagram North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


7.6.7 Typical Archived Data Management Architecture With the emerging interest in integrating various transportation systems, there also emerges a need to archive data. Archived data would initially be accessible by traffic management agencies, and later would expand to provide access to law enforcement or other public safety agencies. Figure 7-20 shows a typical archived data management interconnect diagram, here represented by the Illinois Department of Transportation Archived Data Management System.


System-Dixon IL



ExistingPlanned

Figure 7-20: Typical Archived Data Management Interconnect Diagram

Figure 7-21 is a typical architecture flow diagram, for the IDOT Archived Data Management system. It details the expected information exchanged with the data management system.


System-Dixon IL




traffic archive data

ExistingPlanned

Figure 7-21: Typical Archived Data Management Architecture Flow Diagram



8 National ITS Standards ITS Standards are fundamental to the establishment of an open ITS environment that achieves the goals originally envisioned by the U.S. Department of Transportation. Standards facilitate deployment of interoperable systems at local, regional, and national levels without impeding innovation as technology advances and new approaches evolve. Standards help create competition, better products, and lower prices. The example that best exhibits this is the telecommunications and computer industries. The openness of the ITS Architecture standards allow considerable latitude in the selection of technologies for use in systems, and also urges manufactures to continually improve their products and develop new ones. ITS standards:

Facilitate interoperability of basic functionality Promote system integration May be linked to federal funding in the future

Standards can be applied to the different elements of intelligent transportation systems:

ITS Standards Communication standards Data standards Message set standards Equipment Standards Software Standards

8.1 Standards Development Organizations The U.S. Department of Transportation's ITS Joint Program Office is supporting SDOs (Standards Development Organizations) with an extensive, multi-year program of accelerated standards development to facilitate successful ITS deployment. The program is supporting and accelerating the ITS consensus-based volunteer standards processes that are under way in the U.S. The following is a list of the current standard development organizations working on developing ITS standards:

American National Standards Institute (ANSI) American Society for Testing and Materials (ASTM) Electronic Industries Alliance (EIA) Institute of Electrical and Electronics Engineers (IEEE) Institute of Transportation Engineers (ITE) Society of Automotive Engineers (SAE) National Transportation Communications for ITS Protocol (NTCIP)

NTCIP is a joint product of the National Electronics Manufacturers Association (NEMA), the American Association of State Highway and Transportation Officials (AASHTO), and the Institute of Transportation Engineers (ITE).



8.2 NTCIP Standards NTCIP is a family of standards that provides both the rules for communicating (called protocols) and the vocabulary (called objects) necessary to allow electronic traffic control equipment from different manufacturers to operate with each other as a system. NTCIP is the first set of standards for the transportation industry that allows traffic control systems to be built using a "mix and match" approach with equipment from different manufacturers. Therefore, NTCIP standards reduce the need for reliance on specific equipment vendors and customized one-of-a-kind software. To assure both manufacturer and user community support, NTCIP is jointly developed by NEMA, AASHTO, and ITE.

8.3 ITS Standards Life Cycle An ITS standard undergoes several steps prior to formal adoption. The process typically can take one to five years. Figure 8-1 illustrates the Life Cycle of ITS Standards, which are generally broken into four categories: Standard Development, Standard Testing, ITS Product Development, Standard Adoption.

Figure 8-1: Lifecycle of ITS Standard Development

8.4 Applicable ITS Standards for the North-Central Regional Architecture Looking at the ITS Standards as a foundation for building the systems identified in the regional architecture, Figure 8-2 highlights the applicable standards for the North-Central Illinois Region ITS Architecture and indicates its status. Status is defined in Figure 8-2 as the following:

Published – (P) Standards that are available for purchase Approved – (A) Standards that have passed all necessary ballots and have been approved by a standards

development organization, but not yet published. In Balloting – (IB) Standards that are being voted upon by a committee or working group, or are

undergoing other SDO procedures Under Development – (UD) Standards that are being written, but are not yet ready for a formal ballot



SDO Std.

Number Standard Title Applicable to

Region Status

AASHTO 8003 NTCIP - Profiles - Framework and Classification of Profiles NA AASHTO 1207 NTCIP - Object Definitions for Ramp Meter Control YES A AASHTO 1208 NTCIP – Object Definitions for Video Switches YES UD AASHTO 1205 NTCIP - Object Definitions for Closed Circuit Television Camera Control YES IB AASHTO 2002 NTCIP – Class A and Class C Profile NA AASHTO TS 3.HAR NTCIP – Object Definitions for Highway Advisory Radio (HAR) NA AASHTO 2303 NTCIP - File Transfer Protocol - Application Profile YES A AASHTO 1204 NTCIP - Object Definitions for Environmental Sensor Stations YES P AASHTO 2302 NTCIP - Trivial File Transfer Protocol - Application Profile YES A AASHTO 2305 NTCIP - Application Profile - CORBA YES UD AASHTO 2304 NTCIP - Application Profile - Data Exchange (DATEX) YES IB AASHTO 1103 NTCIP - Simple Transportation Management Protocol (STMP) YES UD AASHTO 1102 NTCIP - Octet Encoding Rules YES IB AASHTO TS 3.1 NTCIP – Overview NA AASHTO 1101 NTCIP - Simple Transportation Management Framework (STMF) YES P AASHTO 2001 NTCIP - Class B Profile YES P AASHTO 1201 NTCIP - Global Object Definitions YES P AASHTO 1202 NTCIP - Object Definitions for Actuated Traffic Signal Controller Units YES P AASHTO 1203 NTCIP - Object Definitions for Dynamic Message Signs YES P AASHTO 2104 NTCIP - Subnetwork Profile for Ethernet YES IB AASHTO 2103 NTCIP - Subnetwork Profile for Point to Point using RS 232 YES UD AASHTO 2101 NTCIP - Point-to-Multipoint Protocol/RS232 Subnetwork Profile YES A AASHTO 1209 NTCIP - Object Definitions for Transportation Sensor Systems YES UD AASHTO 1206 NTCIP - Data Collection & Monitoring Devices YES UD AASHTO 2301 NTCIP - STMF Application Profile YES A AASHTO 2202 NTCIP - Internet (TCP/IP & UDP/IP ) Transport Profiles YES A

ITE TM 1.03 Standard for Functional Level Traffic Management Data Dictionary (TMDD) YES IB ITE ITE-9603-1 ATC Application Program Interface (API) NA ITE ITE-9603-2 ATC Cabinet NA ITE ITE-9603-3 Advanced Transportation Controller (ATC) NA ITE TM 2.01 Message Set for External TMC Communication (MS/ETMCC) YES IB ITE 1407 TCIP - Control Center (CC) Objects YES A ITE 1401 TCIP - Common Public Transportation (CPT) Objects YES P ITE 1408 TCIP - Fare Collection (FC)Objects YES A ITE 1400 TCIP - Framework NA ITE 1402 TCIP - Incident Management (IM) Objects YES P ITE 1406 TCIP - Onboard (OB) Objects YES A ITE 1403 TCIP - Passenger Information (PI) Objects YES P ITE 1404 TCIP - Scheduling/Runcutting (SCH) Objects YES P ITE 1405 TCIP - Spatial Representation (SP) Objects YES P ITE TS3.TM TCIP - Traffic Management (TM) Objects YES UD

ANSI TS284 Commercial Vehicle Safety Reports NA ANSI TS285 Commercial Vehicle Safety and Credentials Information Exchange NA ANSI TS286 Commercial Vehicle Credential NA ASTM PS111-98 Standard Specification for DSRC - Physical Layer 902-928 MHz YES P ASTM PS105-99 Standard Specification for DSRC - Data Link Layer YES P ASTM DSRC at 5.9 GHz NA FHWA Draft Specification for DSRC for Commercial Vehicles NA

EIA/CEA EIA-794 Data Radio Channel (DARC) System YES P EIA/CEA EIA-795 Subcarrier Traffic Information (STIC) System YES P

IEEE 1512 Standard for Common Incident Management Message Set (IMMS) for use by EMCs

YES P

IEEE SH94633- Survey of Communications Technologies NA



SDO Std.

Number Standard Title Applicable to

Region Status

94638 IEEE ITSPP#6-A ITS Data Dictionaries Guidelines NA IEEE 1404 Guide for Microwave Communications System Development NA IEEE P1454 Recommended Practice for Selection and Installation of Fiber Optic Cable in ITS

Environments NA

IEEE 1455 Message Sets for DSRC ETTM & CVO YES P IEEE 1488 Standard for Message Set Template for ITS NA IEEE 1489 Standard for Data Dictionaries for Intelligent Transportation Systems NA SAE J1663 Truth-in-Labeling Standard for Navigation Map Databases NA SAE J1708 Serial Data Comm. Between MicroComputer and Heavy Duty Vehicle

Applications NA

SAE J1760 ITS Data Bus Data Security Services Recommended Practice NA SAE J1761 ITS Terms and Definitions Information Report NA SAE J1763 A Conceptual ITS Architecture: An ATIS Perspective - Information Report NA SAE J1764 ISP-Vehicle Location Referencing Standard YES P SAE J2256 In-Vehicle Navigation System Communication Device Message Set Information

Report NA

SAE J2313 Onboard Land Vehicle Mayday Reporting Interface NA SAE J2352 Mayday Industry Survey Information Report NA SAE J2353 Advanced Traveler Information System (ATIS) Data Dictionary YES P SAE J2354 Advanced Traveler Information System (ATIS) Message Set YES P SAE J2355 ITS Data Bus Reference Architecture Information Report NA SAE J2364 Standard for Navigation and Route Guidance Function Accessibility While

Driving NA

SAE J2365 Standard for Navigation and Route Guidance Man-Machine Interface Transactions

NA

SAE J2366 ITS Data Bus Protocol - Link Layer Recommended Practice (J2366-2) NA SAE J2366/1 ITS Data Bus Protocol - Physical Layer Recommended Practice (J2366-1) NA SAE J2366/4 ITS Data Bus Protocol - Thin Transport Layer Recommended Practice NA SAE J2366/7 ITS Data Bus Protocol - Application Layer Recommended Practice NA SAE J2367 ITS Data Bus Gateway Recommended Practice NA SAE J2368 ITS Data Bus Conformance Test Recommended Practice NA SAE J2369 Standards for ATIS Message Sets Delivered Over Bandwidth Restricted Media YES P SAE J2372 Field Test Analysis Information Report NA SAE J2373 Stakeholder's Workshop Information Report NA SAE J2374 National Location Referencing Information Report NA SAE J2395 ITS In-Vehicle Message Priority NA SAE J2396 Measurement of Driver Visual Behavior Using Video Based Methods (Def. &

Meas.) NA

SAE J2399 Adaptive Cruise Control: Operating Characteristics and User Interface NA SAE J2400 Forward Collision Warning: Operating Characteristics and User Interface NA

Figure 8-2: Applicable Standards for North-Central Illinois Regional ITS Architecture



9 Sample Agency Stakeholder Interview Forms Agency Stakeholder interview forms were utilized during the outreach and user needs assessment portion of the Regional Architecture Project. Agencies were categorized into eight different types and separate sheets were created for each category. The eight different categories were:

1. Commercial Vehicle Operations 2. Emergency Management 3. Freeway Management 4. Public Transportation 5. Traveler Information 6. Arterial Traffic Management 7. Parking Management 8. Maintenance Operations

The eight different interview forms used for the project are reproduced on the following pages.



Commercial Vehicle Operations

1. Commercial Vehicle Operations Stakeholder Name: ____________________

2. Commercial Vehicle Operations Management Center Name: ____________________

3. Does your State/Regional CV Administrative Center perform (or plan to perform) electronic credential administrative services?

4. Does your project/region have (or plan to have) roadside inspection facilities?

5. Inspection Facility Name: ____________________

6. CVO Inspector Name: ____________________

7. Does your State/Regional CV Administrative Center perform (or plan to perform)

dispatching related to Inspection services? List dispatch duties: ____________________________________________

8. Commercial Vehicle Name: ____________________

9. Does your inspection facility perform (or plan to perform) electronic screening?

10. Does your inspection facility exchange (or plan to exchange) safety information?

11. Does your inspection facility involve (or plan to involve) an international border?

12. Do you perform (or plan to perform) a high speed Weigh-In-Motion service?

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

INTERVIEW INFORMATION

Interview Date: __________ Interviewee Name: ____________________ Interviewee Title: ____________________ Address: _____________________________ City: ____________________ Phone: _______________ Fax: _______________ email: ____________________ Interviewer Name: ____________________

SSoouutthhwweesstt WWiissccoonnssiinn // NNoorrtthh CCeennttrraall IIlllliinnooiiss IInntteelllliiggeenntt TTrraannssppoorrttaattiioonn SSyysstteemmss ((IITTSS)) PPrrooggrraamm

OUTREACH ITS ARCHITECTURE RELATED QUESTIONS Commercial Vehicle Operations

1. Commercial Vehicle Operations Stakeholder Name: ____________________

2. Commercial Vehicle Operations Management Center Name: ____________________

3. Does your State/Regional CV Administrative Center perform (or plan to perform) electronic credential administrative services?

4. Does your project/region have (or plan to have) roadside inspection facilities?

5. Inspection Facility Name: ____________________

6. CVO Inspector Name: ____________________

7. Does your State/Regional CV Administrative Center perform (or plan to perform)

dispatching related to Inspection services? List dispatch duties: ____________________________________________

8. Commercial Vehicle Name: ____________________

9. Does your inspection facility perform (or plan to perform) electronic screening?

10. Does your inspection facility exchange (or plan to exchange) safety information?

11. Does your inspection facility involve (or plan to involve) an international border?

12. Do you perform (or plan to perform) a high speed Weigh-In-Motion service?

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________




OUTREACH ITS ARCHITECTURE RELATED QUESTIONS

Figure 9-1: Outreach Interview Questionnaire - Commercial Vehicle Operations



Emergency Management 1. Emergency Management Stakeholder Name: ____________________ 2. Emergency Management Center Name: ____________________ 3. Emergency Management Personnel Name: ____________________ 4. What agencies do you provide dispatch services to? ________________________________

__________________________________________________________________________________ __________________________________________________________________________________

5. Provide description of existing radio infrastructure. _________________________________

__________________________________________________________________________________ __________________________________________________________________________________

6. Provide description of future radio infrastructure. _________________________________

__________________________________________________________________________________ __________________________________________________________________________________

7. Does the center currently perform (or plan to perform) computer-aided dispatch of

emergency vehicles? 8. Does the center currently perform (or plan to perform) automatic vehicle location of

emergency vehicles? 9. Emergency Vehicle Names: ____________________ Quantity: _____

Description of Emergency Vehicles: _______________________________________________ 10. Does the center receive (or plan to receive) incident data from an arterial, freeway, or transit

center? 11. Does the center send (or plan to send) incident data to an arterial, freeway, or transit center? 12. Does the center have (or plan to have) preemption lights for signalized intersections or ramp

meters?

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________




OUTREACH ITS ARCHITECTURE RELATED QUESTIONS Emergency Management 1. Emergency Management Stakeholder Name: ____________________ 2. Emergency Management Center Name: ____________________ 3. Emergency Management Personnel Name: ____________________ 4. What agencies do you provide dispatch services to? ________________________________

__________________________________________________________________________________ __________________________________________________________________________________

5. Provide description of existing radio infrastructure. _________________________________

__________________________________________________________________________________ __________________________________________________________________________________

6. Provide description of future radio infrastructure. _________________________________

__________________________________________________________________________________ __________________________________________________________________________________

7. Does the center currently perform (or plan to perform) computer-aided dispatch of

emergency vehicles? 8. Does the center currently perform (or plan to perform) automatic vehicle location of

emergency vehicles? 9. Emergency Vehicle Names: ____________________ Quantity: _____

Description of Emergency Vehicles: _______________________________________________ 10. Does the center receive (or plan to receive) incident data from an arterial, freeway, or transit

center? 11. Does the center send (or plan to send) incident data to an arterial, freeway, or transit center? 12. Does the center have (or plan to have) preemption lights for signalized intersections or ramp

meters?

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________





Figure 9-2: Outreach Interview Questionnaire - Emergency Management



Freeway Management

1. Freeway Management Stakeholder Name: ____________________

2. Freeway Management Operations Area Name: ____________________

3. Freeway Management Personnel Name: ____________________

4. Are any of your freeways managed by the Freeway Management Operations Area currently under (or are there plans to add) electronic surveillance using real-time traffic data collection technologies?

Indicate what types of technologies are used (check all that apply):

5. Loop Detectors Existing Planned 6. Closed Circuit Television Existing Planned 7. Vehicle Probe Readers Existing Planned 8. Other (e.g., radar) ____________________ Existing Planned

9. Does your Freeway Management Operations Area have (or plan to add) environmental sensor stations to monitor the environmental conditions?

10. Does your Freeway Management Operations Area currently distribute (or are there

plans to distribute) information to travelers directly using roadside infrastructure on the freeways?

Indicate what types of technologies are used (check all that apply):

11. Variable Message Signs (VMS) -- permanent or portable Existing Planned 12. Highway Advisory Radio (HAR) Existing Planned 13. In-vehicle Signing Existing Planned 14. Other ____________________ Existing Planned

15. Does your Freeway Management Operations Area operate (or plan to add) ramp meters

on freeway entrances?

Indicate what types of technologies are used (check all that apply): 16. Preemption for emergency vehicles Existing Planned 17. Priority for transit vehicles Existing Planned

18. Does your Freeway Management Operations Area operate (or plan to add) lane control devices (e.g., changeable overhead directional arrows) on the freeways?

19. Does your Freeway Management Operations Area disseminate (or plan to disseminate)

freeway travel times, speeds, and conditions information to the public?

Indicate what types of technologies are used (check all that apply): 20. Internet Web Page Existing Planned 21. Pagers or Personal Data Assistants Existing Planned 22. Kiosks Existing Planned 23. e-mail or other direct PC communications Existing Planned



Figure 9-3: Outreach Interview Questionnaire - Freeway Management



26. Other ____________________ Existing Planned

27. Does your Freeway Management Operations Area detect and verify (or plan to detect and verify) incidents?

28. Does your Freeway Management Operations Area share (or plan to share) traffic data with another Freeway Management Center or Arterial Management Center?

29. Does your Freeway Management Operations Area manage (or plan to manage) HOV lanes?

Other Comments: ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


Interview Date: __________Interviewee Name: ____________________ Interviewee Title: ____________________Address: _____________________________ City: ____________________Phone: _______________ Fax: _______________ email: ____________________Interviewer Name: ____________________


27. Does your Freeway Management Operations Area detect and verify (or plan to detect and verify) incidents?

28. Does your Freeway Management Operations Area share (or plan to share) traffic data with another Freeway Management Center or Arterial Management Center?

29. Does your Freeway Management Operations Area manage (or plan to manage) HOV lanes?

Other Comments: ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________



Figure 9-3: Outreach Interview Questionnaire - Freeway Management – CONT’D



Public Transportation

1. Public Transportation Stakeholder Name: ____________________

2. Public Transportation Center Name: ____________________

3. Public Transportation Personnel Name: ____________________

4. Does your Public Transportation Center manage (or plan to manage) transit vehicles?

5a. Public Transportation Vehicle Name: ____________________ Quantity: _____ Description of Transit Vehicles: __________________________________________________

Indicate what types of technologies are used (check all that apply): a. Fixed Route Existing Planned b. Rail Existing Planned c. Demand Response Existing Planned

5b. Public Transportation Vehicle Name: ____________________ Quantity: _____

Description of Transit Vehicles: __________________________________________________


5c. Public Transportation Vehicle Name: ____________________ Quantity: _____

Description of Transit Vehicles: __________________________________________________


6. Does your transit element provide (or plan to provide) monitoring of transit vehicles (e.g., engine conditions, passenger counting, etc.)?

7. Do you have (or plan to have) an Automated Vehicle Location (AVL) System?

8. Does your agency have (or plan to have) an electronic display (or automated audio output) of transit real time or static information at transit stops or kiosks?

9. Does your agency have (or plan to have) on board security monitoring systems or does it monitor (or plan to monitor) public areas (e.g., stops, park & ride lots, stations)?



Figure 9-4: Outreach Interview Questionnaire - Public Transportation



10. Does your Public Transportation Center directly or indirectly (i.e., thru another agency/organization) disseminate (or plan to disseminate) info to the public?

Indicate what types of technologies are used (check all that apply): a. Internet Web Page Existing Planned b. Pagers or Personal Data Assistants Existing Planned c. Kiosks Existing Planned d. e-mail or other direct PC communications Existing Planned e. Display/Audio in Transit Vehicles Existing Planned f. TV (interactive or dedicated Cable) Existing Planned g. Other ____________________ Existing Planned

11. Does your transit element share (or plan to share) transit data with a Freeway Management Center or Arterial Management Center?

12. Does your transit element have (or plan to have) a fully operational Electronic Fare Payment System (other than registering fare boxes)?

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________



Figure 9-4: Outreach Interview Questionnaire - Public Transportation – CONT’D



Traveler Information

1. Traveler Information Stakeholder Name: ____________________

2. Traveler Information Operations Area Name: ____________________

3. Traveler Information Personnel Name: ____________________

4. Does your Regional Traveler Information Operations Area use (or plan to use) different technologies to distribute traveler information to the public?

Indicate what types of technologies are used (check all that apply): 5. Internet Web Page Existing Planned 6. Pagers or Personal Data Assistants Existing Planned 7. Kiosks Existing Planned 8. e-mail or other direct PC communications Existing Planned 9. In-Vehicle Navigation Systems Existing Planned 10. TV (interactive or dedicated Cable) Existing Planned 11. Other ____________________ Existing Planned

12. Does your Regional Traveler Information Operations Area have (or plan to have) the

capability to provide any of the following information: broadcast data, personalized data, route guidance, or yellow pages information?

Indicate what types of information are provided (check all that apply): 1. Broadcast of Static or Real-Time Traffic or Transit information Existing Planned 2. Personalized provision of Traffic or Transit information to users Existing Planned 3. Route Guidance (either pre-trip or enroute) Existing Planned 4. Yellow Pages Information or Reservation Existing Planned

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________





Figure 9-5: Outreach Interview Questionnaire - Traveler Information



Arterial Traffic Management 1. Arterial Traffic Management Stakeholder Name: ____________________ 2. Arterial Traffic Management Operations Area Name: ____________________ 3. Arterial or Traffic Management Personnel Name: ____________________ 4. Does your Arterial Traffic Management Operations Area control (or plan to control)

signalized intersections?

Indicate what types of technologies are used (check all that apply): 5. Closed Loop or Centralized Control Existing Planned 6. Real-Time traffic adaptive control (e.g., SCOOT/SCATS) Existing Planned 7. Signal Preemption for emergency vehicles Existing Planned 8. Signal Priority for Transit Vehicles Existing Planned

9. Does your Arterial Traffic Management Operations Area deploy (or plan to deploy)

electronic surveillance using real-time traffic data collection technologies?

Indicate what types of technologies are used (check all that apply): 10. Loop Detectors that provide volume and speed data at mid-block locations (this

excludes actuators on intersection approaches) Existing Planned 11. CCTV Cameras Existing Planned 12. Probe Readers to estimate travel times on arterials Existing Planned 13. Other Existing Planned

14. Does your Arterial Traffic Management Operations Area distribute (or plan to distribute)

information to travelers directly using roadside media infrastructure on the arterials

Indicate what types of technologies are used (check all that apply): 15. Variable Message Signs on mainline streets Existing Planned 16. Highway Advisory Radio (HAR) Existing Planned 17. Variable Message Signs controlling parking access Existing Planned 18. In-Vehicle Signing transmitter locations Existing Planned 19. Other ____________________ Existing Planned

20. Do you have signalized intersections operated by the Arterial Management Operations Area

within 200 feet of a highway-rail intersection that currently (or are planned to) adjust signal timing in response to train crossing to avoid vehicle entrapment, or are interconnected with active crossing devices?

21. Does your agency deploy (or plan to deploy) technologies associated with highway-rail

intersections?

Indicate what types of technologies are used (check all that apply): 22. Video Surveillance Existing Planned 23. Electronic Surveillance other than video Existing Planned 24. Ability to predict train arrivals electronically Existing Planned



Figure 9-6: Outreach Interview Questionnaire - Arterial Traffic Management




27. Does your Arterial Traffic Management Operations Area have (or plan to add)environmental sensor stations to monitor the environmental conditions?

28. Does your Arterial Traffic Management Operations Area provide (or plan to provide) surface street travel times, speeds, and conditions information to the public?

Indicate what types of technologies are used (check all that apply):29. Internet Web Page Existing Planned30. Pagers or Personal Data Assistants Existing Planned31. Kiosks Existing Planned32. e-mail or other direct PC communications Existing Planned33. In-Vehicle Navigation Systems Existing Planned34. TV (interactive or dedicated Cable) Existing Planned35. Other ____________________ Existing Planned

36. Does your Arterial Traffic Management Operations Area detect and verify (or plan to detect and verify) incidents?

37. Does your Arterial Traffic Management Operations Area share (or plan to sh are) traffic data with another Freeway Management Center or Arterial Management Center?

Other Comments: ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________




27. Does your Arterial Traffic Management Operations Area have (or plan to add)environmental sensor stations to monitor the environmental conditions?

28. Does your Arterial Traffic Management Operations Area provide (or plan to provide) surface street travel times, speeds, and conditions information to the public?

Indicate what types of technologies are used (check all that apply):29. Internet Web Page Existing Planned30. Pagers or Personal Data Assistants Existing Planned31. Kiosks Existing Planned32. e-mail or other direct PC communications Existing Planned33. In-Vehicle Navigation Systems Existing Planned34. TV (interactive or dedicated Cable) Existing Planned35. Other ____________________ Existing Planned

36. Does your Arterial Traffic Management Operations Area detect and verify (or plan to detect and verify) incidents?

37. Does your Arterial Traffic Management Operations Area share (or plan to sh are) traffic data with another Freeway Management Center or Arterial Management Center?

Other Comments: ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________



Figure 9-6: Outreach Interview Questionnaire - Arterial Traffic Management – CONT’D



Parking Management 1. Parking Management Stakeholder Name: ____________________ 2. Parking Management Center Name: ____________________

3. Parking Management Personnel Name: ____________________

4. How many Parking Structures are under your management? _____

Description of Parking Structures (location and capacity):____________________________ ______________________________________________________________________________ ______________________________________________________________________________ 5. Does your Parking Management Center monitor (or plan to monitor) parking availability

(i.e., number of spaces)? 6. Does your Parking Management Center disseminate (or plan to disseminate) parking

availability and costs to the public?

Indicate what types of technologies are used (check all that apply): 7. Internet Web Page Existing Planned 8. Dynamic Message Signs Existing Planned 9. In-Vehicle Navigation Systems Existing Planned 10. Other ____________________ Existing Planned

Other Comments: ____________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________





Figure 9-7: Outreach Interview Questionnaire - Parking Management



Maintenance Operations

1. Maintenance Operations Stakeholder Name: ____________________

2. Maintenance Operations Area Name: ____________________

3. Maintenance Operations Personnel Name: ____________________

4. Does your Maintenance Operations Area manage (or plan to manage) maintenance vehicles (Snow Plows, Construction, etc.)?

5. Maintenance Vehicle Name: ____________________ Quantity: _____ a. Description of Maintenance Vehicles:

_____________________________________________

Maintenance Vehicle Name: ____________________ Quantity: _____

b. Description of Maintenance Vehicles: _____________________________________________

Maintenance Vehicle Name: ____________________ Quantity: _____ c. Description of Maintenance Vehicles:

_____________________________________________

6. Does your maintenance operations element provide (or plan to provide) monitoring of the maintenance vehicles (e.g., engine, sensors for salt/sand distribution or environmental probes on vehicles)?

7. Do you have (or plan to have) an Automated Vehicle Location (AVL) System?

8. Does your Maintenance Operations Center directly or indirectly (i.e., thru another agency/organization) disseminate (or plan to disseminate) info to the public?

Indicate what types of technologies are used (check all that apply): 9. Internet Web Page Existing Planned 10. Pagers or Personal Data Assistants Existing Planned 11. Kiosks Existing Planned 12. e-mail or other direct PC communications Existing Planned 13. Display/Audio in Transit Vehicles Existing Planned 14. TV (interactive or dedicated Cable) Existing Planned 15. Other ____________________ Existing Planned

16. Does your maintenance element share (or plan to share) maintenance data (e.g., winter road conditions, construction activity) with a Freeway Management Center or Arterial Management Center?

Other Comments: ______________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________


Interview Date: __________ Interviewee Name: ____________________ Interviewee Title: ____________________ Address: _____________________________ City: ____________________



Figure 9-8: Outreach Interview Questionnaire - Maintenance Operations



10 List of Stakeholder Agencies Interviewed The following lists stakeholder agencies that were interviewed for the North-Central Regional ITS Architecture.

1. Illinois State Toll Highway Authority – Downers Grove Operations Area 2. Illinois State Department of Transportation – District 2 3. City of Rockford Department of Public Works 4. City of DeKalb Department of Public Works 5. City of Sycamore Department of Public Works 6. City of Sandwich Department of Public Works 7. City of Belvidere Department of Public Works 8. Illinois State Police – District 1 9. Illinois State Police – District 15 10. Illinois State Police – District 16 11. City of Rockford Dispatch 12. City of Belvidere Dispatch 13. City of DeKalb Dispatch 14. Northern Illinois University Dispatch 15. Boone County 911 Center 16. DeKalb County 911 Center 17. Ogle County 911 Center 18. Winnebago County 911 Center 19. Illinois State Department of Transportation – District 1 Gateway Traveler Information Hub 20. Rockford Mass Transit 21. IDOT Boone County Highway Department Dispatch 22. IDOT DeKalb County Highway Department Dispatch 23. IDOT Ogle County Highway Department Dispatch 24. IDOT Winnebago County Highway Department Dispatch 25. Boone County Highway Department Dispatch 26. DeKalb County Highway Department Dispatch 27. Ogle County Highway Department Dispatch 28. Winnebago County Highway Department Dispatch 29. City of Rockford Maintenance Dispatch 30. Northern Illinois University Parking 31. City of DeKalb Parking 32. City of Rockford Parking

11 List of Architecture Subsystems The following two tables contain a list of different physical architecture subsystems that are part of the National ITS Architecture. Figure 11-1 lists subsystems and which are applicable to the regional architecture.



Subsystem Applicable to Regional Architecture

CENTER SUBSYSTEMS 1. Archived Data Management Subsystem Yes 2. Commercial Vehicle Administration No 3. Emergency Management Yes 4. Emissions Management No 5. Fleet and Freight Management No 6. Information Service Provider Yes 7. Toll Administration No 8. Traffic Management Yes 9. Transit Management Yes ROADSIDE SUBSYSTEMS 10. Commercial Vehicle Check No 11. Parking Management Yes 12. Roadway Subsystem Yes 13. Toll Collection No TRAVELER SUBSYSTEMS 14. Personal Information Access Yes 15. Remote Traveler Support Yes TRAVELER SUBSYSTEMS 16. Commercial Vehicle Subsystem No 17. Emergency Vehicle Subsystem Yes 18. Transit Vehicle Subsystem Yes 19. Vehicle Yes

Figure 11-1: Architecture Subsystems Table

Figure 11-2 (shown below) provides definitions for each of the applicable regional architecture subsystems. It continues across the ensuing two pages.

Subsystem Definition CENTER SUBSYSTEMS 1. Archived Data Management Subsystem

The Archived Data Management Subsystem collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. The data received is formatted, tagged with attributes that define the data source, conditions under which it was collected, data transformations, and other information (i.e. meta data) necessary to interpret the data. The subsystem can fuse ITS generated data with data from non-ITS sources and other archives to generate information products utilizing data from multiple functional areas, modes, and jurisdictions. The subsystem prepares data products that can serve as inputs to Federal, State, and local data reporting systems. This subsystem may be implemented in many different ways. It may reside within an operational center and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct center that collects data from multiple agencies and sources and provides a general data warehouse service for a region.

3. Emergency Management

The Emergency Management Subsystem operates in various emergency centers supporting public safety including police and fire stations, search and rescue special detachments, and HAZMAT response teams. This subsystem interfaces with other Emergency Management Subsystems to support coordinated emergency response involving multiple agencies. The subsystem creates, stores, and utilizes emergency response plans to facilitate coordinated response. The subsystem tracks and manages emergency vehicle fleets using automated vehicle location technology and two way communications with the vehicle fleet. Real-time traffic information received from the other center subsystems is used to further aide the emergency dispatcher in selecting the emergency vehicle(s) and routes that will provide the most timely response. Interface with the Traffic Management Subsystem allows strategic coordination in tailoring traffic control to support en-route emergency vehicles. Interface with the Transit Management Subsystem allows coordinated use of transit vehicles to facilitate response to major emergencies.



Subsystem Definition 6. Information Service Provider

This subsystem collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The subsystem can play several different roles in an integrated ITS. In one role, the ISP provides a general data warehousing function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other ISPs. In this information redistribution role, the ISP provides a bridge between the various transportation systems that produce the information and the other ISPs and their subscribers that use the information. The second role of an ISP is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, real time traffic condition and transit schedule information, yellow pages information, ridematching information, and parking information. The subsystem also provides the capability to provide specific directions to travelers by receiving origin and destination requests from travelers, generating route plans, and returning the calculated plans to the users. In addition to general route planning for travelers, the ISP also supports specialized route planning for vehicle fleets. In this third role, the ISP function may be dedicated to, or even embedded within, the dispatch system. Reservation services are also provided in advanced implementations. The information is provided to the traveler through the Personal Information Access Subsystem, Remote Traveler Support Subsystem, and various Vehicle Subsystems through available communications links. Both basic one-way (broadcast) and personalized two-way information provision is supported. The subsystem provides the capability for an informational infrastructure to connect providers and consumers, and gather that market information needed to assist in the planning of service improvements and in maintenance of operations.

8. Traffic Management

The Traffic Management Subsystem operates within a traffic management center or other fixed location. This subsystem communicates with the Roadway Subsystem to monitor and manage traffic flow. Incidents are detected and verified and incident information is provided to the Emergency Management Subsystem, travelers (through Roadway Subsystem Highway Advisory Radio and Dynamic Message Signs), and to third party providers. The subsystem supports HOV lane management and coordination, road pricing, and other demand management policies that can alleviate congestion and influence mode selection. The subsystem monitors and manages maintenance work and disseminates maintenance work schedules and road closures. The subsystem also manages reversible lane facilities, and processes probe vehicle information. The subsystem communicates with other Traffic Management Subsystems to coordinate traffic information and control strategies in neighboring jurisdictions. It also coordinates with rail operations to support safer and more efficient highway traffic management at highway-rail intersections. Finally, the Traffic Management Subsystem provides the capabilities to exercise control over those devices utilized for AHS traffic and vehicle control.

9. Transit Management

The transit management subsystem manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, and paratransit services. The subsystem's interfaces allow for communication between transit Departments and with other operating entities such as emergency response services and traffic management systems. This subsystem receives special event and real-time incident data from the traffic management subsystem. It provides current transit operations data to other center subsystems. The Transit Management Subsystem collects and stores accurate ridership levels and implements corresponding fare structures. It collects operational and maintenance data from transit vehicles, manages vehicle service histories, and assigns drivers and maintenance personnel to vehicles and routes. The Transit Management Subsystem also provides the capability for automated planning and scheduling of public transit operations. It furnishes travelers with real-time travel information, continuously updated schedules, schedule adherence information, transfer options, and transit routes and fares. In addition, the monitoring of key transit locations with both video and audio systems is provided with automatic alerting of operators and police of potential incidents including support for traveler activated alarms.

ROADSIDE SUBSYSTEMS 11. Parking Management

The Parking Management Subsystem provides electronic monitoring and management of parking facilities. It supports a DSRC communications link to the Vehicle Subsystem that allows electronic collection of parking fees. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. This portion of the subsystem functionality must be located in the parking facility where it can monitor, classify, and share information with customers and their vehicles. The subsystem also interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region. Note that the latter functionality may be located in a back office, remote from the parking facility.

12. Roadway Subsystem

This subsystem includes the equipment distributed on and along the roadway which monitors and controls traffic. Equipment includes highway advisory radios, dynamic message signs, cellular call boxes, CCTV cameras and video image processing systems for incident detection and verification, vehicle detectors, traffic signals, grade crossing warning systems, and freeway ramp metering systems. This subsystem also provides the capability for emissions and environmental condition monitoring including weather sensors, pavement icing sensors, fog etc. HOV lane management and reversible lane management functions are also available. In advanced implementations, this subsystem supports automated vehicle safety systems by safely controlling access to and egress from an Automated Highway System through monitoring of, and communications with, AHS vehicles. Intersection collision avoidance functions are provided by determining the probability of a collision in the intersection and sending appropriate warnings and/or control actions to the approaching vehicles.

TRAVELER SUBSYSTEMS



Subsystem Definition 14. Personal Information Access

This subsystem provides the capability for travelers to receive formatted traffic advisories from their homes, place of work, major trip generation sites, personal portable devices, and over multiple types of electronic media. These capabilities shall also provide basic routing information and allow users to select those transportation modes that allow them to avoid congestion, or more advanced capabilities to allow users to specify those transportation parameters that are unique to their individual needs and receive travel information. This subsystem shall provide capabilities to receive route planning from the infrastructure at fixed locations such as in their homes, their place of work, and at mobile locations such as from personal portable devices and in the vehicle or perform the route planning process at a mobile information access location. This subsystem shall also provide the capability to initiate a distress signal and cancel a prior issued manual request for help.

15. Remote Traveler Support

This subsystem provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes, and at major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops, simple displays providing schedule information and imminent arrival signals can be provided. This basic information may be extended to include multi-modal information including traffic conditions and transit schedules along with yellow pages information to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. In addition to traveler information provision, this subsystem also supports public safety monitoring using CCTV cameras or other surveillance equipment and emergency notification within these public areas. Fare card maintenance, and other features which enhance traveler convenience may also be provided at the discretion of the deploying agency.

TRAVELER SUBSYSTEMS 17. Emergency Vehicle Subsystem

This subsystem resides in an emergency vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient emergency response. The Emergency Vehicle Subsystem includes two-way communications to support coordinated response to emergencies in accordance with an associated Emergency Management Subsystem. Emergency vehicles are equipped with automated vehicle location capability for monitoring by vehicle tracking and fleet management functions in the Emergency Management Subsystem. Using these capabilities, the appropriate emergency vehicle to respond to each emergency is determined. Route guidance capabilities within the vehicle enable safe and efficient routing to the emergency. In addition, the emergency vehicle may be equipped to support signal preemption through communications with the roadside subsystem.

18. Transit Vehicle Subsystem

This subsystem resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The Transit Vehicle Subsystem collects accurate ridership levels and supports electronic fare collection. An optional traffic signal prioritization function communicates with the roadside subsystem to improve on-schedule performance. Automated vehicle location functions enhance the information available to the Transit Management Subsystem enabling more efficient operations. Onboard sensors support transit vehicle maintenance. The Transit Vehicle Subsystem also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares.

19. Vehicle This subsystem resides in an automobile and provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel by personal automobile. Information services provide the driver with current travel conditions and the availability of services along the route and at the destination. Both one-way and two-way communications options support a spectrum of information services from low-cost broadcast services to advanced, pay for use personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. Initial collision avoidance functions provide “vigilant co-pilot” driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain safe headway. Ultimately, this subsystem supports completely automated vehicle operation through advanced communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems. Pre-crash safety systems are deployed and emergency notification messages are issued when unavoidable collisions do occur.

Figure 11-2: Regional Architecture Subsystems Definitions Table



12 List of Architecture Terminators The following two tables contain a list of different architecture terminators that are part of the National ITS Architecture. Figure 12-1 lists terminators and indicates which are applicable to the regional architecture. Figure 12-2 provides definitions for each of the applicable regional terminators.



Terminators Currently in Regional

Architecture? ENVIRONMENT TERMINATORS 1. Environment No 2. Potential Obstacles No 3. Roadway No 4. Roadway Environment Yes 5. Secure Area Environment No 6. Traffic No 7. Vehicle Characteristics No HUMAN TERMINATORS 8. Archived Data Administrator No 9. Commercial Vehicle Driver No 10. Commercial Vehicle Manager No 11. CVO Inspector No 12. Driver No 13. Emergency Personnel Yes 14. Emergency System Operator Yes 15. ISP Operator Yes 16. Parking Operator Yes 17. Pedestrians No 18. Toll Administrator No 19. Toll Operator No 20. Traffic Operations Personnel Yes 21. Transit Driver Yes 22. Yes 23. Transit Maintenance Personnel No 24. Transit System Operators Yes 25. Transit User No 26. Traveler No OTHER SYSTEM TERMINATORS 27. Other Archives No 28. Other CVAS No 29. Other EM No 30. Other ISP No 31. Other Parking No 32. Other TM Yes 33. Other TRM No 34. Other Vehicle No SYSTEM TERMINATORS 35. Archived Data User Systems No 36. Basic Vehicle No 37. Commercial Vehicle No 38. Construction and Maintenance No 39. CVO Information Requestor No 40. DMV No 41. Emergency Telecommunications System No 42. Enforcement Agency Yes 43. Event Promoters Yes 44. Financial Institution Yes 45. Government Administrators No 46. Government Reporting Systems No 47. Intermodal Freight Depot No 48. Intermodal Freight Shipper No 49. Location Data Source No 50. Map Update Provider No 51. Media Yes 52. Multimodal Crossings No 53. Multimodal Transportation Service Provider No 54. Other Data Sources No 55. Payment Instrument Yes 56. Rail Operations No 57. Transit Vehicle No 58. Wayside Equipment No 59. Weather Service No

Transit Fleet Manager

Figure 12-1: Architecture Terminators Table



Terminator Definition ENVIRONMENT TERMINATORS 4. Roadway Environment

This terminator represents the physical conditions surrounding the roadway itself. These may include emissions, fog, ice, snow, rain, etc. which will influence the way in which a vehicle can be safely operated on the roadway.

HUMAN TERMINATORS 13. Emergency Personnel

This terminator represents personnel that are responsible for police, fire, emergency medical services, towing, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle Subsystem during dispatch to the incident site, but often work independently of the Emergency Vehicle Subsystem while providing their incident response services. Emergency personnel may include an Officer in Charge (OIC) and a crew. When managing an incident following standard Incident Command System practices, the on-site emergency personnel form an organizational structure under the auspices of an Incident Commander.

14. Emergency System Operator

This terminator represents the human entity that monitors all ITS emergency requests, (including those from the E911 Operator) and sets up pre-defined responses to be executed by an emergency management system. The operator may also override predefined responses where it is observed that they are not achieving the desired result. This terminator includes dispatchers who manage an emergency fleet (police, fire, ambulance, HAZMAT, etc.) or higher order emergency managers who provide response coordination during emergencies.

15. ISP Operator This terminator is the human entity that may be physically present at the ISP to monitor the operational status of the facility and provide human interface capabilities to travelers and other ISP subsystems.

16. Parking Operator

This terminator is the human entity that may be physically present at the parking lot facility to monitor the operational status of the facility.

20. Traffic Operations Personnel

This terminator represents the human entity that directly interfaces with vehicle traffic operations. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems to accomplish ITS services. They provide operator data and command inputs to direct systems' operations to varying degrees depending on the type of system and the deployment scenario. All functionality associated with these services that might be automated in the course of ITS deployment is modeled as internal to the architecture.

21. Transit Driver This terminator represents the human entity that is a special form of the Driver terminator that receives and provides additional information that is specific to Transit (including demand responsive transit) operations. This information will not be received by other types of Driver. The Transit Driver terminator operates the Transit Vehicle terminator and represents random route drivers, flexible fixed route drivers and fixed route drivers. The fixed route drivers require minimal information such as run times and passenger loading. The flex fixed and random route drivers require additional information such as dynamically changing routes.

22. Transit Fleet Manager

This terminator represents the human entity that is responsible for planning the operation of transit fleets, including monitoring and controlling the transit fleet route schedules and the transit fleet maintenance schedules. This comprises planning routes and schedules for either daily use or for special occasions as distinct from making day to day variations to schedules and routes.

24. Transit System Operator

This terminator represents the human entities that are responsible for all aspects of the Transit subsystem operation including planning and management. They actively monitor, control, and modify the transit fleet routes and schedules on a day to day basis. The modifications will be to take account of abnormal situations such as vehicle breakdown, vehicle delay, etc. These personnel may also be responsible for demand responsive transit operation and for managing emergency situations within the transit network.

OTHER SYSTEM TERMINATORS 32. Other TM Representing another Traffic Management center, system or subsystem, this terminator is intended to provide a source

and destination for ITS data flows between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas. In the Physical Architecture this terminator is a reciprocal Traffic Management Subsystem (TMS).

SYSTEM TERMINATORS 42. Enforcement Agency

This terminator represents an external entity which receives reports of violations detected by various ITS facilities, e.g. individual vehicle emissions, toll violations, CVO violations, etc.

43. Event Promoters

This terminator represents external Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area.

44. Financial Institution

This terminator represents the organization that handles all electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are subsumed by this entity.

51. Media This terminator represents the information systems that provide traffic reports, travel conditions, and other transportation-related news services to the traveling public through radio, TV, and other media. Traffic and travel advisory information that are collected by ITS are provided to this terminator. It is also a source for traffic flow information, incident and special event information, and other events which may have implications for the transportation system.

55. Payment Instrument

This terminator represents the entity that enables the actual transfer of funds from the user of a service to the provider of the service. This terminator can be as abstract as an account number in the Logical Architecture, or as real as the electronic tag in the Physical architecture.

Figure 12-2: Regional Architecture Subsystems Definitions Table



13 Boone County Agency Architectures The following are Boone County agency architectures. The following agencies have interconnect and architecture flow diagrams on the following pages:

1. Boone County 911 Center 2. Boone County Highway Department Dispatch 3. City of Belvidere Department of Public Works 4. City of Belvidere Dispatch

13.1 Boone County 911 Center


Police/Fire/EMS



EM_County of Boone_Sheriff Depart...Boone County 911 Center_Personnel


Dispatch




Works






ExistingPlanned

Figure 13-1: Boone County 911 Center Interconnect Diagram




Police/Fire/EMS



MediaEM_County of Boone_Sheriff Department

Boone County 911 Center_Personnel





Dispatch




Works


















emergency operations request


maintenance deployment statuscurrent network conditions










ExistingPlanned

Figure 13-2: Boone County 911 Center Architecture Flow Diagram



13.2 Boone County Highway Department Dispatch



Dispatch


Dispatch_Driver



Boone County Highway DepartmentDispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles




Dispatch




Department Dispatch

ExistingPlanned

Figure 13-3: Boone County Highway Department Dispatch Interconnect Diagram




O&M_County of Boone_Highway DepartmentBoone County Highway Department Dispatch

Boone County Highway Department Dispatch_OperatorsO&M_County of Boone_Highway De...Boone County Highway Department

Dispatch_Driver




Dispatch_Personnel


Dispatch_Vehicles




Dispatch





OM operator displaymaintenance deployment status

OM route assignment

OM operations planning data

OM work schedule


event report

equipment maintenance statusevent and resource coordination

event reportmaintenance response





equipment maintenance statusmaintenance response


OM driver availability

OM fleet manager inputs








traffic equipment statuswork zone closure coordination






ExistingPlanned

Figure 13-4: Boone County Highway Department Dispatch Architecture Flow Diagram



13.3 City of Belvidere Department of Public Works



Works


Works_Personnel





ExistingPlanned

Figure 13-5: City of Belvidere Department of Public Works Interconnect Diagram




Traffic Management_City of Belvidere_Department of Public WorksCity of Belvidere Department of Public Works


Works_Personnel













signal control datatraffic control coordination








ExistingPlanned

Figure 13-6: City of Belvidere Department of Public Works Architecture Flow Diagram



13.4 City of Belvidere Dispatch


EM_City of Belvidere_Police/Fire/EMSBelvidere Dispatch Center_Personnel

EM_County of Boone_Sheriff Depart...Boone County 911 Center Media

ExistingPlanned

Figure 13-7: City of Belvidere Dispatch Interconnect Diagram


MediaEM_City of Belvidere_Police/Fire/EMSBelvidere Dispatch Center_Personnel


incident information for mediaemergency operations status


emergency operations requestincident report

incident response coordinationmedia information request

ExistingPlanned

Figure 13-8: City of Belvidere Dispatch Architecture Flow Diagram



14 DeKalb County Agency Architectures The following are DeKalb County agency architectures. The following agencies have interconnect and architecture flow diagrams on the following pages:

1. City of DeKalb Department of Public Works 2. City of DeKalb Dispatch 3. City of Sycamore Department of Public Works 4. City of Sandwich Department of Public Works 5. DeKalb County 911 Center 6. DeKalb County Highway Department Dispatch 7. Northern Illinois University Dispatch 8. Northern Illinois University Parking

14.1 City of DeKalb Department of Public Works


Works


Works_Personnel





Office


Parking Management_Northern Illinoi...Northern Illinois University Parking

FacilitiesRailroad Company Dispatch Centers



ExistingPlanned

Figure 14-1: City of DeKalb Department of Public Works Interconnect Diagram




Railroad Company Dispatch Centers

EM_County of DeKalb_Sheriff DepartmentDeKalb County 911 Center



Facilities


Works_Personnel




Office



hri advisories



resource deployment statusparking demand management request

parking instructions





signal control data








parking availabilityparking demand management response




resource request


railroad advisoriesrailroad schedules


ExistingPlanned

Figure 14-2: City of DeKalb Department of Public Works Architecture Flow Diagram



14.2 City of DeKalb Dispatch


EM_City of DeKalb_Police/Fire/EMSDeKalb Dispatch Center

EM_City of DeKalb_Police/Fire/EMSDeKalb Dispatch Center_Personnel Media

ExistingPlanned

Figure 14-3: City of DeKalb Dispatch Interconnect Diagram EM_County of DeKalb_Sheriff Depart...

DeKalb County 911 Center


MediaEM_City of DeKalb_Police/Fire/EMSDeKalb Dispatch Center_Personnel


incident information for mediaemergency operations status


emergency operations requestmedia information request

ExistingPlanned Figure 14-4: City of DeKalb Dispatch Architecture Flow Diagram



14.3 City of Sycamore Department of Public Works


Works


Works_Personnel






Figure 14-5: City of Sycamore Department of Public Works Interconnect Diagram

Traffic Management_City of Sycamore_Department of Publi...City of Sycamore Department of Public Works



Works_Personnel

Traffic Management_City of Sycamore_Department of Publi...City of Sycamore Department of Public Works_Roadside

Equipment












traffic imagesemergency traffic control request




Figure 14-6: City of Sycamore Department of Public Works Architecture Flow Diagram



14.4 City of Sandwich Department of Public Works

Traffic Management_City of Sandwic...City of Sandwich Department of Public

Works


Works_Personnel






Figure 14-7: City of Sandwich Department of Public Works Interconnect Diagram

Traffic Management_City of Sandwich_Department of Public...City of Sandwich Department of Public Works



Works_Personnel

Traffic Management_City of Sandwich_Department of Public...City of Sandwich Department of Public Works_Roadside

Equipment












traffic imagesemergency traffic control request




Figure 14-8: City of Sandwich Department of Public Works Architecture Flow Diagram



14.5 DeKalb County 911 Center

EM_County of DeKalb_Police/Fire/E...All DeKalb County Police/Fire/EMS




Works


Works


Works

EM_County of DeKalb_Sheriff Depart...DeKalb County 911 Center_Personnel


Dispatch




EM_Illinois State Police_District 1Illinois State Police-District 1 Dispatch Media


Center




ExistingPlanned

Figure 14-9: DeKalb County 911 Center Interconnect Diagram



EM_County of DeKalb_Police/Fire/E...All DeKalb County Police/Fire/EMS

EM_County of DeKalb_Sheriff DepartmentDeKalb County 911 Center




Works


Works

Media


EM_County of DeKalb_Sheriff Depart...DeKalb County 911 Center_Personnel



EM_Northern Illinois University_PoliceNorthern Illinois University Dispatch Center


Dispatch









resource deployment statuscurrent network conditions















incident information for maintenanceincident response status

remote surveillance controlrequest request for maintenance

resource requestincident information for maintenance

request request for maintenanceemergency traffic control request





resource request






emergency operations requestcurrent network conditions


incident information requestmaintenance deployment status

resource deployment statusmaintenance deployment status









ExistingPlanned

Figure 14-10: DeKalb County 911 Center Architecture Flow Diagram



14.6 DeKalb County Highway Department Dispatch


Dispatch


Dispatch



Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles




Dispatch



ExistingPlanned

Figure 14-11: DeKalb County Highway Department Dispatch Interconnect Diagram




O&M_County of DeKalb_Highway DepartmentDeKalb County Highway Department Dispatch


O&M_County of DeKalb_Highway DepartmentDeKalb County Highway Department Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles




Dispatch












resource deployment statusevent and resource coordination


traffic equip statustraffic equipment status




OM driver instructions






work zone closure coordinationmaintenance response

traffic control coordinationtraffic equip maintenance status

traffic information coordinationwork zone closure status











work zone closure statusmaintenance request

traffic control coordinationtraffic equip status

traffic information coordinationwork zone closure coordination

ExistingPlanned

Figure 14-12: DeKalb County Highway Department Dispatch Architecture Flow Diagram



14.7 Northern Illinois University Dispatch



Center

Parking Management_City of Rockfor...City of Rockford Parking Structures



Center_Personnel


Facilities

Figure 14-13: Northern Illinois University Dispatch Interconnect Diagram



Center




Center_Personnel


Facilities

parking coordinationparking coordination





parking coordinationemergency operations request


Figure 14-14: Northern Illinois University Dispatch Architecture Flow Diagram



14.8 Northern Illinois University Parking


Works


Facilities


Center


Facilities_Enforcement


Facilities_Financial


Facilities_Operators

Figure 14-15: Northern Illinois University Parking Interconnect Diagram

Traffic Management_City of DeKalb_...

City of DeKalb Department of PublicWorks


Facilities


Center


Facilities_Enforcement


Facilities_Financial


Facilities_Operators






transaction status


Figure 14-16: Northern Illinois University Parking Architecture Flow Diagram



15 Ogle County Agency Architectures The following are Ogle County agency architectures. The following agencies have interconnect and architecture flow diagrams on the following pages:

1. Ogle County 911 Center 2. Ogle County Highway Department Dispatch

15.1 Ogle County 911 Center

EM_County of Ogle_Police/Fire/EMSAll Ogle County Police/Fire/EMS




MediaEM_County of Ogle_Sheriff Departm...

Ogle County 911 Center_Personnel


Dispatch






ExistingPlanned

Figure 15-1: Ogle County 911 Center Interconnect Diagram



EM_County of Ogle_Police/Fire/EMSAll Ogle County Police/Fire/EMS

EM_County of Ogle_Sheriff DepartmentOgle County 911 Center



Media

EM_County of Ogle_Sheriff Departm...Ogle County 911 Center_Personnel



Dispatch







media information requestincident information for media










resource requestemergency operations request

maintenance deployment statusmaintenance deployment status





ExistingPlanned

Figure 15-2: Ogle County 911 Center Architecture Flow Diagram



15.2 Ogle County Highway Department Dispatch


Dispatch


Dispatch



Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles






Department Dispatch

ExistingPlanned

Figure 15-3: Ogle County Highway Department Dispatch Interconnect Diagram




Dispatch



O&M_County of Ogle_Highway DepartmentOgle County Highway Department Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles

















event report



work zone closure statusmaintenance response












ExistingPlanned

Figure 15-4: Ogle County Highway Department Dispatch Architecture Flow Diagram



16 Winnebago County Agency Architectures The following are Winnebago County agency architectures. The following agencies have interconnect and architecture flow diagrams on the following pages:

1. City of Rockford Department of Public Works 2. City of Rockford Dispatch 3. City of Rockford Maintenance Dispatch 4. City of Rockford Parking 5. Illinois State Police – District 16 6. Rockford Mass Transit 7. Winnebago County 911 Center 8. Winnebago County Highway Department Dispatch

16.1 City of Rockford Department of Public Works


Works


Office

O&M_City of Rockford_Maintenance ...City of Rockford Maintenance Dispatch



Office_Personnel



Railroad Company Dispatch CentersTraffic Management_Illinois State De...Traffic Management and Maintenance



ExistingPlanned

Figure 16-1: City of Rockford Department of Public Works Interconnect Diagram




Works




Railroad Company Dispatch Centers



Office_Personnel









hri advisories



resource deployment statusmaintenance request






hri requestroadway information system data





hri statusincident data



railroad advisoriesrailroad schedules




resource request

ExistingPlanned

Figure 16-2: City of Rockford Department of Public Works Architecture Flow Diagram



16.2 City of Rockford Dispatch

Media

EM_City of Rockford_Police/Fire/EMSRockford Dispatch Center

EM_City of Rockford_Police/Fire/EMSRockford Dispatch Center_Personnel


ExistingPlanned

Figure 16-3: City of Rockford Dispatch Interconnect Diagram

Media


EM_City of Rockford_Police/Fire/EMSRockford Dispatch Center_Personnel


media information requestincident information for media

emergency operations statusincident report

incident response coordinationemergency operations request


ExistingPlanned

Figure 16-4: City of Rockford Dispatch Architecture Flow Diagram



16.3 City of Rockford Maintenance Dispatch


O&M_City of Rockford_Maintenance ...City of Rockford Maintenance

Dispatch_Driver




Dispatch_Operators


Dispatch_Personnel


Dispatch_Vehicles


Office



ExistingPlanned

Figure 16-5: City of Rockford Maintenance Dispatch Interconnect Diagram



O&M_City of Rockford_Maintenance DepartmentCity of Rockford Maintenance Dispatch


Dispatch_Driver




Dispatch_Operators

O&M_City of Rockford_Maintenance DepartmentCity of Rockford Maintenance Dispatch_Personnel


Dispatch_Vehicles


Office

Traffic Management_Illinois State Department of ...Traffic Management and Maintenance Control

Center_Dixon



OM driver instructionsmaintenance response





OM operator management dataOM maintenance status




work zone closure coordinationmaintenance request


ExistingPlanned

Figure 16-6: City of Rockford Maintenance Dispatch Architecture Flow Diagram



16.4 City of Rockford Parking


Parking Management_City of Rockfor...City of Rockford ParkingStructures_Enforcement

Parking Management_City of Rockfor...City of Rockford Parking

Structures_Financial


Structures_Operators


Office


Center

Figure 16-7: City of Rockford Parking Interconnect Diagram



Center

Parking Management_City of Rockfor...City of Rockford ParkingStructures_Enforcement


Structures_Financial


Structures_Operators


Office





transaction status




Figure 16-8: City of Rockford Parking Architecture Flow Diagram



16.5 Illinois State Police – District 16 EM_County of Boone_Sheriff Depart...

Boone County 911 Center



EM_Illinois State Police_District 16Illinois State Police-District 16

Dispatch_Personnel

MediaEM_County of Winnebago_Sheriff

Winnebago County 911 Center

Figure 16-9: Illinois State Police – District 16 Interconnect Diagram

EM_County of Boone_Sheriff Depart...

Boone County 911 Center



Media


EM_Illinois State Police_District 16Illinois State Police-District 16

Dispatch_Personnel







emergency operations statusemergency operations request



Figure 1 -1 : Illinois State Police – District 16Architecture Flow Diagram 6 0



16.6 Rockford Mass Transit


Area


Area_Kiosks


Area_Personnel




Figure 16-11: Rockford Mass Transit Interconnect Diagram



Traffic Management_Illinois State Department of Transp...Traffic Management and Maintenance Control

Center_Dixon


Area_Kiosks


Area_Personnel



transit system dataemergency acknowledge

secure area monitoring supporttransit fare payment responses

transit traveler informationtransit operations planning data

transit operator displayemergency notification

secure area surveillance datatransit fare payment requests

transit information user requesttransit fleet manager inputs

transit operator management datarequest transit information



transit emergency coordination data Figure 16-12: Rockford Mass Transit Architecture Flow Diagram



16.7 Winnebago County 911 Center

EM_County of Winnebago_Police/Fir...All Other Winnebago County

Police/Fire/EMS




Office

EM_Illinois State Police_District 16Illinois State Police-District 16 Dispatch Media




Area



EM_County of Winnebago_SheriffWinnebago County 911

Center_Personnel


Department Dispatch



ExistingPlanned

Figure 16-13: Winnebago County 911 Center Interconnect Diagram



EM_County of Winnebago_Police/Fir...All Other Winnebago County

Police/Fire/EMS





Media






EM_County of Winnebago_SheriffWinnebago County 911

Center_Personnel


Department Dispatch















resource deployment statusincident information for media










resource request







transit emergency coordination data

emergency operations requestcurrent network conditions



resource deployment statusmaintenance deployment status

ExistingPlanned

Figure 16-14: Winnebago County 911 Center Architecture Flow Diagram



16.8 Winnebago County Highway Department Dispatch


Dispatch


Department Dispatch


Dispatch




O&M_County of Winnebago_Highwa...Winnebago County HighwayDepartment Dispatch_Driver


Department Dispatch_Fleet Manager


Department Dispatch_Operators


Department Dispatch_Personnel


Department Dispatch_Vehicles



ExistingPlanned

Figure 16-15: Winnebago County Highway Department Dispatch Interconnect Diagram






Dispatch




O&M_County of Winnebago_Highway DepartmentWinnebago County Highway Department Dispatch_Driver


Department Dispatch_Fleet Manager


Department Dispatch_Operators


Department Dispatch_Personnel


Department Dispatch_Vehicles









maintenance requesttraffic control coordination

traffic equip statustraffic information coordination








resource deployment statusevent and resource coordination











maintenance responsetraffic control coordination

traffic equip maintenance statustraffic information coordination

work zone closure statusOM driver availability

OM fleet manager inputs








ExistingPlanned

Figure 16-16: Winnebago County Highway Department Dispatch Architecture Flow Diagram



17 Illinois Department of Transportation Architectures The following are Illinois Department of Transportation architectures. The following agencies have interconnect and architecture flow diagrams on the following pages:

1. IDOT Boone County Highway Department Dispatch 2. IDOT DeKalb County Highway Department Dispatch 3. IDOT Ogle County Highway Department Dispatch 4. IDOT Winnebago County Highway Department Dispatch 5. Illinois Department of Transportation – District 2 Traffic Management and

Maintenance Control Center Interaction with County Maintenance Agencies Interaction with Local Department of Public Works Offices Interaction with Emergency Management Agencies Interaction with State Maintenance Agencies Interaction with Transit Agencies Interaction with other Traffic Management Agencies Generalized Operations



17.1 IDOT Boone County Highway Department Dispatch


O&M_County of Boone_IDOT Highway MaintenanceBoone County IDOT Highway Maintenance Dispatch


Dispatch

O&M_County of Boone_IDOT Highway MaintenanceBoone County IDOT Highway Maintenance

Dispatch_Driver


Maintenance Dispatch_Fleet Manager


Maintenance Dispatch_Operators


Maintenance Dispatch_Personnel


Dispatch_Vehicles



























ExistingPlanned

Figure 17-1: IDOT Boone County Highway Department Dispatch Interconnect Diagram




O&M_County of Boone_IDOT Highway MaintenanceBoone County IDOT Highway Maintenance Dispatch


Dispatch


Dispatch_Driver








Dispatch_Vehicles



























ExistingPlanned

Figure 17-2: IDOT Boone County Highway Department Dispatch Architecture Flow Diagram



17.2 IDOT DeKalb County Highway Department Dispatch







Dispatch

O&M_County of DeKalb_IDOT Highw...DeKalb County IDOT HighwayMaintenance Dispatch_Driver













ExistingPlanned

Figure 17-3: IDOT DeKalb County Highway Department Dispatch Interconnect Diagram





O&M_County of DeKalb_IDOT Highway MaintenanceDeKalb County IDOT Highway Maintenance Dispatch



Dispatch

O&M_County of DeKalb_IDOT Highway MaintenanceDeKalb County IDOT Highway Maintenance Dispatch_Driver











Traffic Management_Illinois State Department of Transportation_D...Traffic Management and Maintenance Control Center_Dixon






maintenance deployment statusevent and resource coordination

event report




OM route assignmentOM route assignment






OM driver availabilityOM driver availability








ExistingPlanned

Figure 17-4: IDOT DeKalb County Highway Department Dispatch Architecture Flow Diagram



17.3 IDOT Ogle County Highway Department Dispatch







Dispatch


Maintenance Dispatch_Driver




Maintenance Dispatch_OperatorsOgle County IDOT Highway

Maintenance Dispatch_RoadsideEquipment







ExistingPlanned

Figure 17-5: IDOT Ogle County Highway Department Dispatch Interconnect Diagram








Dispatch

O&M_County of Ogle_IDOT Highway MaintenanceOgle County IDOT Highway Maintenance

Dispatch_Driver





O&M_County of Ogle_IDOT Highway MaintenanceOgle County IDOT Highway Maintenance

Dispatch_Vehicles





Ogle County IDOT HighwayMaintenance Dispatch_Roadside

Equipment








OM operator display







environmental conditions status






ExistingPlanned

Figure 17-6: IDOT Ogle County Highway Department Dispatch Architecture Flow Diagram



17.4 IDOT Winnebago County Highway Department Dispatch











Department Dispatch


Maintenance Dispatch_Driver



O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT HighwayMaintenance Dispatch_Operators

O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT HighwayMaintenance Dispatch_Personnel


ExistingPlanned

Figure 17-7: IDOT Winnebago County Highway Department Dispatch Interconnect Diagram





O&M_County of Winnebago_IDOT Highway MaintenanceWinnebago County IDOT Highway Maintenance Dispatch



Traffic Management_Illinois State Department of Transportation_D...Traffic Management and Maintenance Control Center_Dixon



Department Dispatch

O&M_County of Winnebago_IDOT Highway MaintenanceWinnebago County IDOT Highway Maintenance Dispatch_Driver



O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT HighwayMaintenance Dispatch_Operators

O&M_County of Winnebago_IDOT Hi...Winnebago County IDOT HighwayMaintenance Dispatch_Personnel










maintenance deployment statusevent and resource coordination

event reportevent and resource coordination

event report






OM driver instructionsmaintenance response







ExistingPlanned

Figure 17-8: IDOT Winnebago County Highway Department Dispatch Architecture Flow Diagram



17.5 Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center

17.5.1 Interaction with County Maintenance Agencies


Dispatch


Dispatch




Department Dispatch


Dispatch

Figure 17-9: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and County Maintenance Agencies Interconnect Diagram


O&M_County of DeKalb_Highway DepartmentDeKalb County Highway Department Dispatch










equipment maintenance statusmaintenance response





































ExistingPlanned

Figure 17-10: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and County Maintenance Agencies Architecture Flow

Diagram North-Central Illinois ITS Architecture & Transportation Management System Preliminary Engineering State ID 5556-00-06/09/10/11


17.5.2 Interaction with Local Department of Public Works Offices


Works




Works


Office


Works


Works

Figure 17-11: Illinois Department of Transportation – District 2 Traffic Management and

Maintenance Control Center and Local Department of Public Works Offices Interconnection Diagram


Works

Traffic Management_Illinois State Departm...Traffic Management and Maintenance


Traffic Management_City of DeKalb_Depart...City of DeKalb Department of Public Works


Office


Works


Works













Figure 17-12: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and Local Department of Public Works Offices Architecture

Flow Diagram



17.5.3 Interaction with Emergency Management Agencies







Figure 17-13: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and Emergency Management Agencies Interaction Diagram

EM_County of Boone_Sheriff Department

Boone County 911 CenterEM_County of DeKalb_Sheriff Department

DeKalb County 911 CenterEM_County of Winnebago_Sheriff

Winnebago County 911 Center







resource requestincident report

incident response coordinationincident report

incident response coordinationemergency traffic control request







resource request



resource deployment statuscurrent network conditions








resource deployment statusincident report

incident response coordinationincident report

incident response coordinationemergency traffic control request




Maintenance Control Center and Emergency Management Agencies Architecture Flow Diagram



17.5.4 Interaction with State Maintenance Agencies












Maintenance Control Center and State Maintenance Agencies Interaction Diagram

O&M_County of Boone_IDOT Highway Mainten...Boone County IDOT Highway Maintenance

Dispatch

O&M_County of DeKalb_IDOT Highway MaintenanceDeKalb County IDOT Highway Maintenance Dispatch



Traffic Management_Illinois State Department of Transportation_Dist...Traffic Management and Maintenance Control Center_Dixon

O&M_County of Ogle_IDOT Highway Maintena...Ogle County IDOT Highway Maintenance

Dispatch




work zone closure statusevent and resource coordination









work zone closure coordinationmaintenance request









ExistingPlanned

Figure 17-16: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and State Maintenance Agencies Architecture Flow Diagram



17.5.5 Interaction with Transit Agencies


Area



ExistingPlanned

Figure 17-17: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and Transit Agencies Interconnect Diagram


Area




transit system datarequest transit information



ExistingPlanned

Figure 17-18: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and Transit Agencies Architecture Flow Diagram



17.5.6 Interaction with other Traffic Management Agencies


Center Madison




System




Maintenance Control Center and other Traffic Management Interconnect Diagram


Center Madison

Traffic Management_Illinois State Department of Transportation...Traffic Management and Maintenance Control Center_Dixon

ISP_Illinois State Department of Transportation_Planning and Pr...IDOT-Gateway Travelar Information System








fare and price informationrequest for traffic information







request fare and price informationtraffic control coordination

traffic informationtraffic information coordination

Figure 17-20: Illinois Department of Transportation – District 2 Traffic Management and Maintenance Control Center and other Traffic Management Architecture Flow Diagram



17.5.7 Generalized Operations


System-Dixon IL








Maintenance Control Center - Generalized Operations Interconnect Diagram

Archived Data Management_Illinois State De...Archived Data Management System-Dixon IL

Traffic Management_Illinois State Department...Traffic Management and Maintenance Control

Center_Dixon

Media






external reportsmedia information request

traffic information for mediatraffic archive data






incident datarequest for right-of-way

roadway information system statussignal control status



Maintenance Control Center - Generalized Operations Architecture Flow Diagram



north-central illinois intelligent ...north-central illinois intelligent transportation systems...

Documents