Minnesota Statewide Architecture - MnDOT

Minnesota Statewide Architecture

December, 2001

Developed for:

Minnesota Department of Transportation

Office of Advanced Transportation Systems

Submitted By:

I

Table of Contents Minnesota System Inventory .................................................................................................... 1

Minnesota’s Market Packages................................................................................................ 15 Network Surveillance (ATMS01) ........................................................................................................ 15 Surface Street Control (ATMS03) ....................................................................................................... 16 Freeway Control (ATMS04) ................................................................................................................ 18 HOV Lane Management (ATMS05).................................................................................................... 19 Traffic Information Dissemination (ATMS06) .................................................................................... 20 Regional Traffic Control (ATMS07) ................................................................................................... 21 Incident Management System (ATMS08) ........................................................................................... 22 Traffic Forecast and Demand Management (ATMS09)....................................................................... 24 Virtual TMC and Smart Probe Data (ATMS12) .................................................................................. 25 Standard Railroad Grade Crossing (ATMS13) .................................................................................... 25 Advanced Railroad Grade Crossing (ATMS14) .................................................................................. 27 Parking Facility Management (ATMS16)............................................................................................ 28 Reversible Lane Management (ATMS17) ........................................................................................... 29 Road Weather Information System (ATMS18) ................................................................................... 30 Regional Parking Management (ATMS19) ......................................................................................... 31 Transit Vehicle Tracking (APTS1) ...................................................................................................... 31 Transit Fixed-Route Operations (APTS2)............................................................................................ 32 Demand Response Transit Operations (APTS3).................................................................................. 33 Transit Passenger and Fare Management (APTS4).............................................................................. 34 Transit Security (APTS5)..................................................................................................................... 35 Multi-modal Coordination (APTS7) .................................................................................................... 36 Broadcast Traveler Information (ATIS1)............................................................................................. 37 Interactive Traveler Information (ATIS2)............................................................................................ 38 ITS Data Mart (AD1) ........................................................................................................................... 39 ITS Data Warehouse (AD2)................................................................................................................. 40 Fleet Administration (CVO01)............................................................................................................. 41 CV Administrative Processes (CVO04)............................................................................................... 42 HAZMAT Management (CVO10)....................................................................................................... 43 Emergency Response (EM1)................................................................................................................ 44 Emergency Routing (EM2) .................................................................................................................. 45 Mayday Support (EM3) ....................................................................................................................... 46 Compliance Management..................................................................................................................... 47

Minnesota Statewide Architecture ......................................................................................... 48 System Interconnections ...................................................................................................................... 48 System Interfaces and Information Exchanges .................................................................................... 48 Potential Standards............................................................................................................................... 49

How to Use the Statewide Architecture ................................................................................. 51

Appendix A – System Interconnect Tables............................................................................ 52

Appendix B – Information Exchange Tables ........................................................................ 65

II

List of Tables Table 1. Minnesota System Inventory _____________________________________________________ 2 Table 2. Standards Information Sources ___________________________________________________ 50 Table A1. Account Management Providers ________________________________________________ 53 Table A2. Broadcast Information Providers ________________________________________________ 53 Table A3. Local Signal Center __________________________________________________________ 53 Table A4. Local Signal Center Roadside Equipment _________________________________________ 54 Table A5. Demand Responsive Transit Center______________________________________________ 54 Table A6. Demand Responsive Transit Vehicle _____________________________________________ 54 Table A7. Division of Emergency Management Center _______________________________________ 54 Table A8. Event Promoters_____________________________________________________________ 55 Table A9. National Weather Service _____________________________________________________ 55 Table A10. Map Update Providers _______________________________________________________ 55 Table A11. Department of Motor Vehicles_________________________________________________ 55 Table A12. Regional Traffic Management Center ___________________________________________ 56 Table A13. Metro TMC Roadside Equipment ______________________________________________ 56 Table A14. Metro TMC _______________________________________________________________ 56 Table A15. Inter-jurisdictional Traffic Management System ___________________________________ 57 Table A16. State Patrol Dispatch Centers__________________________________________________ 57 Table A17. Minnesota Emergency Management Vehicle______________________________________ 57 Table A18. Maintenance Dispatch Center _________________________________________________ 57 Table A19. Electrical Services Center ____________________________________________________ 58 Table A20. Maintenance Dispatch Center Vehicle___________________________________________ 58 Table A21. TOCC____________________________________________________________________ 58 Table A22. TOCC Roadside Equipment___________________________________________________ 58 Table A23. Metro Transit Management Center _____________________________________________ 59 Table A24. Metro Transit Management Vehicles____________________________________________ 59 Table A25. Road Weather Information Center ______________________________________________ 59 Table A26. RWIS Roadside Equipment ___________________________________________________ 59 Table A27. Truck Center ______________________________________________________________ 59 Table A28. Traveler Information Center __________________________________________________ 60 Table A29. Parking Management Center __________________________________________________ 60 Table A30. Parking Management Roadside Equipment _______________________________________ 60 Table A31. Metro Traffic Engineering Center ______________________________________________ 60 Table A32. Metro Traffic Engineering Roadside Equipment ___________________________________ 61 Table A33. Emergency Management Vehicle ______________________________________________ 61 Table A34. Local Emergency Management Center __________________________________________ 61 Table A35. Inter-Jurisdictional MnCARS _________________________________________________ 62 Table A36. Local Transit Management Center______________________________________________ 62 Table A37. Local Transit Management Vehicles ____________________________________________ 62 Table A38. Traveler Information Kiosk ___________________________________________________ 62 Table A39. Greater Minnesota State Patrol ________________________________________________ 62 Table A40. DTN _____________________________________________________________________ 63 Table A41. Mayday Service Provider_____________________________________________________ 63 Table A42. Mayday Vehicle ____________________________________________________________ 63 Table A43. Inter-Jurisdictional Emergency Management System _______________________________ 63 Table A44. In Vehicle Signing System____________________________________________________ 63 Table A45. In Vehicle Signing Roadside Equipment _________________________________________ 63 Table A46. Data Center _______________________________________________________________ 64 Table A47. Compliance Management Roadside Equipment ___________________________________ 64 Table B1. Account Management Providers Information Exchanges _____________________________ 66 Table B2 Broadcast Information Providers Information Exchanges ______________________________ 66 Table B3. Local Signal Center Information Exchanges _______________________________________ 68

III

Table B4. Local Signal Center Roadside Equipment Information Exchanges_______________________ 72 Table B5. Demand Responsive Transit Center Information Exchanges___________________________ 73 Table B6. Demand Responsive Transit Vehicle Information Exchanges __________________________ 74 Table B7. Division of Emergency Management Center Information Exchanges ____________________ 75 Table B8. Event Promoters Information Exchanges__________________________________________ 77 Table B9. National Weather Service Information Exchanges __________________________________ 78 Table B10. Map Update Providers Information Exchanges ____________________________________ 79 Table B11. Department of Motor Vehicles Information Exchanges______________________________ 79 Table B12. Regional Traffic Management Center Information Exchanges ________________________ 79 Table B13. Metro TMC Roadside Equipment Information Exchanges ___________________________ 84 Table B14. Metro TMC Information Exchanges ____________________________________________ 86 Table B15. Inter-jurisdictional Traffic Management System Information Exchanges ________________ 92 Table B16. State Patrol Dispatch Centers Information Exchanges_______________________________ 92 Table B17. Minnesota Emergency Management Vehicle Information Exchanges___________________ 97 Table B18. Maintenance Dispatch Center Information Exchanges ______________________________ 98 Table B19. Electrical Services Center Information Exchanges ________________________________ 102 Table B20. Maintenance Dispatch Center Vehicle Information Exchanges_______________________ 103 Table B21. TOCC Information Exchanges________________________________________________ 103 Table B22. TOCC Roadside Equipment Information Exchanges _______________________________ 109 Table B23. Metro Transit Management Center Information Exchanges _________________________ 110 Table B24. Metro Transit Management Vehicles Information Exchanges________________________ 113 Table B25. Road Weather Information Center Information Exchanges __________________________ 114 Table B26. RWIS Roadside Equipment Information Exchanges _______________________________ 115 Table B27. Truck Center Information Exchanges __________________________________________ 115 Table B28. Traveler Information Center Information Exchanges ______________________________ 116 Table B29. Parking Management Center Information Exchanges ______________________________ 118 Table B30. Parking Management Roadside Equipment Information Exchanges ___________________ 118 Table B31. Metro Traffic Engineering Center Information Exchanges __________________________ 118 Table B32. Metro Traffic Engineering Roadside Equipment Information Exchanges _______________ 121 Table B33. Emergency Management Vehicle Information Exchanges __________________________ 122 Table B34. Local Emergency Management Center Information Exchanges ______________________ 122 Table B35. Inter-Jurisdictional MnCARS Information Exchanges _____________________________ 125 Table B36. Local Transit Management Center Information Exchanges__________________________ 126 Table B37. Local Transit Management Vehicles Information Exchanges ________________________ 127 Table B38. Traveler Information Kiosk Information Exchanges _______________________________ 127 Table B39. Greater Minnesota State Patrol Information Exchanges ____________________________ 127 Table B40. DTN Information Exchanges _________________________________________________ 131 Table B41. Mayday Service Provider Information Exchanges_________________________________ 131 Table B42. Mayday Vehicle Information Exchanges ________________________________________ 131 Table B43. Inter-Jurisdictional Emergency Management System Information Exchanges ___________ 132 Table B44. In Vehicle Signing System Information Exchanges________________________________ 134 Table B45. In Vehicle Signing Roadside Equipment Information Exchanges _____________________ 134 Table B46. Data Center Information Exchanges ___________________________________________ 134 Table B47. Compliance Management Roadside Equipment Information Exchanges _______________ 136

1

MINNESOTA SYSTEM INVENTORY

When developing a statewide architecture it is important have a good understanding on which stakeholders, systems, and projects are going to be interacting within the state of Minnesota. It is also important to establish agreements among the stakeholders who will be exchanging data to promote integration throughout the state.

Several systems and projects will need to interface among each other to help facilitate integration within the state of Minnesota. In order for this goal to be achieved, a system inventory is required to identify all ITS projects and systems that are being used or planned that aids in managing traffic conditions within the state of Minnesota. The system inventory for the Minnesota Statewide Architecture is presented in Table 1. This table identifies and describes the systems and stakeholders that are responsible for operations and management of their respective systems. This table will allow the Minnesota Department of Transportation (Mn/DOT) to understand the capabilities that exist within the state and what interfaces are currently being supported or need to be accommodated in the future.

Table 1 also maps each system to one or more National ITS Architecture elements. This mapping places the regional systems and stakeholders within the context of the National ITS Architecture which will facilitate the examination of integration opportunities. For systems that were not addressed by the National ITS Architecture, a user defined entity was created to ensure they are incorporated in the Minnesota Statewide Architecture. The reader should note that the column for System Name shows specific systems names in some cases and generalizes system names in other cases. This naming convention was used for the following reasons:

1. The National ITS Architecture focuses on the functions that are being performed by any given system. Since there are several agencies/systems that are performing similar functions, some system names were generalized and lump into a single category. For example every agency that operates traffic signals were not given their own grouping they have similar functionality. Similar examples exist for Traveler Information Centers, Local Emergency Management Centers, etc.

2. To ensure that the statewide architecture is kept at a manageable level.

2

Table 1. Minnesota System Inventory

Group System Name Description of System Status Subsystem & Terminators

Associated Stakeholder

1 Account Management Providers

Account Management Providers Provide invoicing and payment tracking services for private companies or public agencies. Examples of the Account Management Provider include: Service Billing Companies and Credit Card Companies

Existing Financial Institution (Term)

Account Management Providers

2 Broadcast Information Providers

Broadcast Information Providers Privately owned component that collects travel-related information from the public sector and private information sources, and broadcasts that information to its customers via a variety of user interface equipment (e.g.; radio, television). Examples of the Broadcast Information Provider include: AM/FM Radio Stations KTSP and KBEM, Television Stations and WCCO, Cable Companies, and Paging Companies

Existing Media (Term)

Local Media Networks

Greater Minnesota Cable TV Providers

Provide video feeds to the cable TV companies via satellite. The project will use data generated from Mn/CARS.

Planned See Others Greater Minnesota Cable Networks

Duluth Media Outlets Official station for weather/school closures/traffic information for Duluth.

Existing See others Duluth Media Outlets

3 Local Signal Center City of St. Paul Signal Center Public controlled component that is used to manage roadside equipment (e.g., traffic signal controllers and loop detectors) and communicate traffic related data to other traffic management centers. This center can also be a place for the inter-jurisdictional traffic system.

Existing Traffic Management

Archive Data Mgmt

City of St. Paul

Local Signal Center(s) Public controlled centers that manage local traffic signals. The agencies shown here have similar functionality therefore there is no reason to separate each agency. The local agencies that are in this category are for the twin cities and for Greater Minnesota. These centers can also be a place for the integrated corridor traffic management system. Note, some local signals centers currently being integrated are specifically listed in this document

Existing See Others Local Signal Operation Agencies

Cities and Counties

City of Minneapolis Signal Center

Public controlled component that is used to manage roadside equipment (e.g., traffic signal controllers and loop detectors) and communicate traffic related data to other traffic

Existing See Others City of Minneapolis

3



management centers. This center can also be a place for the inter-jurisdictional traffic system. The Adaptive Signal Control Integration (AUSCI) is operated from this center.

City of St. Cloud Signal Center This system manages traffic operations in the St. Cloud area. Existing See other City of St. Cloud

City of Duluth Signal Center Responsible for maintenance and operations of the traffic signals in the Duluth Area.

Existing See Others City of Duluth

Stearns County Signal Center This agency is responsible for some of the traffic signals in the St. Cloud Metro area.

Existing See Others Stearns County

City of Sauk Rapids Signal Center

This agency is responsible for some of the traffic signals in the St. Cloud Metro area.

Existing See Others City of Sauk Rapids

City of Mankato Signal Center This center is responsible for the traffic operations in the Mankato area.

Existing See Others Mn/DOT District 7

City of Rochester Signal Operations Center

System is responsible for the traffic operations in the Rochester area.

Existing See Others City of Rochester

Mankato High Water Warning System

Mn/DOT has a high water warning device on Highway 59/60 near Worthington that automatically detects a rise in water level and issues and alert based on commands from the City of Mankato signal center. This system will be represented by showing the City of Mankato roadside equipment sending data to the City of Mankato signal center.

Existing See Other Mn/DOT District 7

Moorhead Advance Train Detection

This system tracks train movement through Fargo-Moorhead areas and uses this information to reduce traffic delay and improve emergency response. This system will be represented by showing the City of Moorhead roadside equipment sending data to the City of Moorhead.

Planned

See Others

Mn/DOT’s OATS, City of Moorhead, City of Fargo

4 Local Signal Center

Roadside Equipment

City of St. Paul Roadside Equipment

Public controlled component that consists of signs, signals and surveillance equipment used for the control and management of traffic. Detecting and collecting data about traffic conditions is also performed by this component. Examples of the Centralized Roadside Equipment include: Traffic Signals, Loop Detectors, Surveillance Cameras, Local Intersection Controllers, Signal Priority/Pre-emption Equipment, Portable Workzone system, Portable Traffic Management System, Railroad Crossing Detectors, Dynamic Message Signs.

Existing Roadway Subsystem City of St. Paul

Local Signal Center(s) Roadside Equipment

Traffic signals and loop detectors that belong to the Local Signal Centers.


4



Cities and Counties

City of Minneapolis Roadside Equipment

Public controlled component that consists of signs, signals and surveillance equipment used for the control and management of traffic. Detecting and collecting data about traffic conditions is also performed by this component. Examples of the Centralized Roadside Equipment include: Traffic Signals, Loop Detectors, Surveillance Cameras, Local Intersection Controllers, Signal Priority/Pre-emption Equipment, Portable Workzone system, Portable Traffic Management System, Railroad Crossing Detectors, Dynamic Message Signs.

Existing See Others City of Minneapolis

City of Duluth Roadside Equipment

Traffic signal controllers and detectors. Existing See Others City of Duluth

City of St. Cloud Roadside Equipment

ITS equipment on the roadside that is controlled by City of St. Cloud.

Existing See Others City of St. Cloud

Stearns County Roadside Equipment

ITS equipment on the roadside that is controlled by Stearns County TOC including some equipment in the St. Cloud jurisdiction.

Existing See Others Stearns County

City of Sauk Rapids Roadside Equipment

Traffic signal controllers and detectors. Existing See Others City of Sauk Rapids

City of Mankato Roadside Equipment

This system also collects pavement data regarding weather through RWIS and AWOS (already represented in inventory).


City of Rochester Roadside Equipment

ITS equipment on the roadside that is controlled by City of Rochester.

Existing See Others City of Rochester

Moorhead Advance Train Detection Roadside Equipment

This is where information from the Moorhead system are displayed

Planned See Others City of Moorhead, City of Fargo

Mankato High Water Warning System

Mn/DOT has a high water warning device on Highway 59/60 near Worthington that automatically detects a rise in water level and issues and alert based on commands from the City of Mankato signal center. This system will be represented by showing the City of Mankato roadside equipment sending data to the City of Mankato signal center.


5 Demand Responsive Transit Center

Demand Responsive Transit Center(s)

Publicly controlled component that is used to manage demand responsive transit systems, which reside outside of the jurisdiction of the Regional ITS Management Center. Demand responsive transit systems provide door-to-door

Existing Transit Management

Local Paratransit Agencies

5



transit service for paratransit and elderly individuals that are unable to use the standard public transit services. Examples of the Demand Responsive Transit Center include: Metro Mobility, Metro Mobility Contracted Operators, Plymouth Dial-A-Ride, ZIPS (Rochester), STRIDE (Duluth), Specialized Service Program (St. Cloud).

6 Demand Responsive Transit Vehicle

Demand Responsive Transit Center Vehicle(s)

This entity represents vehicles for the follow organizations: Metro Mobility, Metro Mobility Contracted Operators, Plymouth Dial-A-Ride, ZIPS (Rochester), STRIDE (Duluth), Specialized Service Program (St. Cloud).

Existing Transit Vehicle Subsystem

Vehicle

Local Paratransit Agencies

MTC Specialized Service Vehicles

MTC Specialized Service program provides demand response, driver-assisted complementary paratransit services for persons with disabilities.

Existing See Others St. Cloud Metropolitan Transit Commission

7 Division of Emergency Management Center

Division of Emergency Management Center

Public controlled component that is used to manage and coordinate Minnesota emergency resources during large-scale disasters. This center will utilize mobile communication centers to provide state level guidance during disaster recovery periods. Examples of the Division of Emergency Management Center include: Department of Public Safety (Division of Emergency Management Office) and Division of Emergency Management Mobile Center.

Existing Emergency Management Department of Public Safety

8 Event Promoters Event Promoters Agencies that provide information to, or receive information from, Minnesota public agencies and private companies providing ITS services.

Existing Event Promoters (Term) Local Event Promoters

9 National Weather Service National Weather Service Agencies that provide information to, or receive information from, Minnesota public agencies and private companies providing ITS services.

Existing Weather Service (Term) National Weather Service

10 Map Update Providers Map Providers Agencies that provide information to, or receive information from, Minnesota public agencies and private companies providing ITS services.

Existing Map Update Provider (Term)

Map Update Providers

11 Department of Motor Vehicles

Department of Motor Vehicles Agencies that provide information to, or receive information from, Minnesota public agencies and private companies providing ITS services.

Existing DMV (Term) DMV

12 Regional Traffic Management Center

Regional Traffic Management Center (RTMC)

The RTMC that is planned will co-locate the Metro Freeway Operations, Metro Traffic Engineering, and the metro state patrol dispatch. Emergency management, traffic management, dispatching and information service provider

bili i ill ll b h d i hi

Planned Traffic Management

Emergency Management

Information Service

Mn/DOT Metro Division

Minnesota State Patrol

6



capabilities will all be housed in this center. Provider

Archived Data Mgmt

13 Metro TMC Roadside

Equipment

Metro TMC Roadside Equipment

Publicly controlled component that is used to control and collect data of continuous traffic flow for freeways. In addition, TMC Roadside Equipment monitors the flow of traffic and detects incidents due to alterations in traffic flow or by use of video surveillance equipment. Traffic flow may be adjusted by use of alternate ramp timing plans or by use of dynamic message sign to alert the traveler of impending traffic conditions and identification of alternate route opportunities. TMC roadside equipment components are connected to and operated by the Mn/DOT Metro Division. Examples of the TMC Roadside Equipment include: Ramp Meters, Loop Detectors, Surveillance Cameras, Highway Advisory Radio Signs, Portable Workzone System, Portable Traffic Management System, Dynamic Message Signs.

Existing Roadway Subsystem Mn/DOT Metro Division

14 Metro Traffic Management Center (TMC)

Metro Traffic Management Center (TMC)

Public controlled component that is used to manage continuous traffic flow and provide appropriate information to the freeway travelers and other Traffic Management Centers. TMC uses ramp metering, CCTV, DMS, traveler information systems, and highway helper to monitor and manage traffic conditions. This center can also be a place for the inter-jurisdictional traffic system. The ISP portion www.dot.state.mn.us/tmc/trafficinfo web site has been developed by Mn/DOT's Metro Division. It provide road conditions incident icons. It is hosted on Mn/DOT's web server and utilizes TMC loop detector, incident detection reports and cameras.


Information Service Provider


Archive Data Management


15 Inter-jurisdictional Traffic Management System

Integrated Corridor Traffic Management (ICTM) System

This system is operated by metro freeway operations and has capabilities of traffic control and coordination. This is an example of inter-jurisdictional system.


Archive Data Mgmt


16 State Patrol Dispatch Centers

State Patrol Dispatch Centers Manages Minnesota State Patrol resources and communicates incident data and resource requests to other public and private agencies. Emergency vehicle components are connected to and operated by the State Patrol Dispatch Center. Examples of the State Patrol Dispatch Center include: Waters Edge (Metro Region) State Patrol Dispatch Center, Other Regional State Patrol Dispatch Centers, and Mobile Command/Communication Center. This center is responsible for dispatching state patrol vehicles in the twin cities areas.

Existing Emergency Management

Traffic management

Archive Mgmt


7



17 Minnesota Emergency Management Vehicle

Minnesota Emergency Management Vehicles

(State Patrol Vehicles)

Collection of vehicles that are utilized for responding to incidents and emergencies. Examples of the State Patrol and Incident Dispatch Emergency Vehicles include: State Patrol Vehicles, City/County/Local Police Vehicles, Ambulances, Fire Vehicles, Tow Vehicles, Highway Helper Vehicles, HAZMAT Vehicles, Emergency Mobile Communication Vehicles.

Existing Emergency Vehicle Subsystem

Vehicle


Greater Minnesota State Patrol Vehicles

State patrol vehicles that are dispatched to support safe and efficient emergency response. For the Greater Minnesota area.

Existing Same others Minnesota State Patrol

18 Maintenance Dispatch Center

Maintenance Dispatch Center(s) Public controlled components that are used for planned incidents (i.e.; road maintenance, snow plowing) and unplanned incidents (i.e., debris on roadway). They provide plans and resources required to resolve an incident where traffic is involved. Also, they provide an incident detection service by using some of the equipment used for their normal operations. These centers communicate with various vehicle components and equipment components utilized in the resolution of incidents. Examples of the Maintenance Dispatch Center include: Waters Edge (Mn/DOT Metro Region) and Other Regional Maintenance Dispatch Centers. This center is a representation of the maintenance dispatch centers for the twin cities and for greater Minnesota. The maintenance dispatch centers for greater Minnesota will be co-located in the TOCC. This will be better served with the release of version 4.0 of the architecture which will address maintenance activities and vehicles.


Traffic Management


Mn/DOT District Offices


19 Electrical Services Center Electrical Services Center This center is responsible for traffic signal maintenance. Information is received from Metro Traffic Engineering and Metro Freeway Operations.

Existing Construction and Maintenance (Term)

Mn/DOT Electrical Services

20 Maintenance Dispatch Center Vehicle

Maintenance Dispatch Center Vehicles

A collection of maintenance vehicles that are utilized to support road maintenance. Examples of the Maintenance Vehicle include: Snow Plow trucks, Salt/Sand Trucks, and Road Repair Trucks. This will be better served with the release of version 4.0 of the architecture which will address maintenance activities and vehicles.


Vehicle



Mn/DOT District 1 Snow Plows Responsible for plowing the roads and salt/sand distribution. Existing See others Mn/DOT District 1

8



This system will be represented by showing the Maintenance Dispatch Center sending commands to their snow plow vehicles and receiving status regarding treated roads.

21 Transportation Operation Communication Centers (TOCC)

Transportation Operation Communication Centers (TOCC)

These centers will be staffed by the State Patrol and supported by Mn/DOT monitor, control, and coordinate resources throughout Greater Minnesota. These centers are currently located in Duluth and St. Cloud and are planned to be located in Brainerd, Detroit Lakes, Mankato, Marshall, Rochester, Thief River Falls, and Virginia. The TOCCs will provide 24-hour, 7-day per week traffic monitoring and management. The TOCC will serve as a regional information collection and dissemination hub and provide information regarding road/weather conditions, construction, construction activity and detours, events, incidents, alternative modes, tourist and travel services.

Existing

and

Planned

Traffic Management



Archive Data Mgmt



Mn/DOT District 1 Traffic Operation Center

Responsible for some CMS and traffic signals in the Duluth area. This an example of a TOCC.

Existing See Others


I-90 Gate System This is a rural interstate transportation system to monitor, manage traffic, provide traveler information and enhance safety.

Planned See Others Mn/DOT District 7,

Mn/DOT Maintenance, City of Mankato

22 TOCC Roadside Equipment

TOCC Roadside Equipment ITS equipment on the roadside that is controlled by operators in the TOCC. The equipment in use are CCTV, DMS, portable traffic management devices, road condition and traffic volume devices.

Existing Roadway Subsystem Mn/DOT District Offices


Mn/DOT District 1 Roadside Equipment

ITS equipment on the roadway that is controlled by Mn/DOT District 1. This an example of a TOCC roadside equipment.

Existing See Others Mn/DOT District Offices

Local Signal Center(s) Roadside Equipment

Traffic signals and loop detectors that belong to the Local Signal Centers.


Cities and Counties

Mn/DOT District 1 Tunnel Alarm System

Monitors carbon monoxide levels, fire and fan and generator operation and communications and power from commands from Mn/DOT District 1 TOCC. This system will be represented by showing the Mn/DOT District 1 roadside equipment sending data to the Mn/DOT District 1 TOCC.

Existing User Defined Mn/DOT District 1

I-90 Gate Roadside Equipment This is the actual gates that prevents vehicles from entering a Planned See Others Mn/DOT District 7,

9



roadway segment. Mn/DOT Maintenance, City of Mankato

23 Metro Transit Management Center

Metro Transit Management Center(s)

Publicly controlled component that is used to manage transit systems outside of the jurisdiction of the Regional Traffic Management Center. Examples of the Transit Management Center include: Southwest Transit, Minnesota Valley Transit, Plymouth Metrolink, and School Bus Fleet Companies and DARTS.

Existing Transit Management

Emergency Mgmt


Twin Cities Transit Agencies

Rideshare Center Manages carpool and vanpool operations. Examples of the Rideshare Center include: Minnesota Rideshare for Twin Cities, Minnesota Rideshare for St. Cloud, and Minnesota Rideshare for Duluth.

Existing See Others Local Car/Vanpool Agencies

Metropolitan Council Transit Operations and Metro Mobility

Public transit transportation for the twin cities area. Existing See Others MCTO

24 Metro Transit Management Vehicles

Metro Transit Center Vehicles These transit vehicles are dispatched by the Metro Transit Center.

Existing Transit Vehicle Subsystem

Vehicle

Metro Transit

25 Road Weather Information Center(RWIS)

Road Weather Information System (RWIS)

Used to collect data about weather, and weather-related road surface conditions, on Mn/DOT roadways. Road Weather Roadside Equipment components are connected to and operated by the University of North Dakota.



Archived Data Mgmt

University of North Dakota

University of Minnesota Supplies R/WIS data on their website to Mn/DOT District 1 traffic.

Existing See Others University of Minnesota

26 RWIS Roadside Equipment

RWIS Roadside Equipment R/WIS or Road/Weather Information Systems / Sensors have been deployed throughout Minnesota to allow better management of maintenance and construction resources.

Existing Roadway Subsystem Mn/DOT Office of Maintenance

Mankato Automated Weather Observation Systems (AWOS)

Provide real-time weather information to Mn/DOT and to the aviation community.


27 Truck Center Truck Center Collects and distributes planned event information (i.e., road maintenance) and unplanned event information (i.e., road surface conditions). It is also responsible for granting trucking permits for oversized and overweight vehicles and provides route plans for oversized and overweight vehicles based on

Existing Commercial Vehicle Administration

Information Service Provider (ISP)

Mn/DOT Office of Motor Carrier Services

10



route plans for oversized and overweight vehicles based on information it receives from MnCARS. Examples of the Truck Center include: (Mn/DOT Metro Region Truck Center) and Other Regional Truck Centers.

28 Traveler Information

Center

Minnesota Office of Tourism Promotes tourism and travel through the Travel Partners Kiosk System.

Existing Information Service Provider

Traffic Management

Mn/DOT

TripUSA Website www.TripUSA.com web site has been implemented which provides statewide road conditions and weather forecasts/reports on a route segment by route segment basis.

Existing See Others Castle Rock

Smartraveler Website and #211 www.Smartraveler.com web site has been developed. This site provide current freeway traffic conditions and travel times in the Twin Cities Metro Area. #211 cell phone access to Metro traffic, incidents and travel times and utilizes the same Mn/DOT information as www.smartraveler.com.

Existing See Others SmartRoute Systems/(Westwood One)

#SAFE #SAFE (#7233) cell phone statewide access to route specific road and weather conditions. #SAFE is planned to be converted to 5-1-1

Existing See Others University of North Dakota

5-1-1 Statewide access to route specific road and weather conditions. This system is expected to replace the #SAFE system.

Planned See Others University of North Dakota

29 Parking Management Center

Metropolitan Airport Parking System

Provides parking availability information. Planned Traffic Management

Parking Management


Metropolitan Airport Commission

Parking Management Center This center manages parking facilities in Down Town Minneapolis/St. Paul Area and also distributes information on parking conditions

Existing See Others City of Minneapolis, Parking Facility owners

30 Parking Management Roadside Equipment

Parking Management Roadside equipment

This is the roadside equipment where parking information are displayed.

Existing Roadway Subsystem

Parking Operator (Term)

City of Minneapolis

31 Metro Traffic Engineering Center

Metro Traffic Engineering Monitors and manages traffic signals in the twin city area. They also use CCTV and DMS to monitor roadways and inform motorist of problems. When the RTMC is in place, this division will be co-located there.


Archive Data Mgmt


11



32 Metro Traffic Engineering Roadside Equipment

Metro Traffic Engineering Roadside Equipment

Traffic signals, detectors, ITS equipment on the roadside that are controlled by the Metro Traffic Engineering.

Existing Roadway Subsystem Mn/DOT Metro Division

33 Emergency Management Vehicle

Highway Helper Vehicles These vehicles are dispatch by the Maintenance Dispatch Center(s).


Vehicle


34 Local Emergency Management Center

Metro Local Police Centers This entity represents local police jurisdictions that are located in the metro area.


Metro Local Police Agencies

Metro Local Fire Centers This entity represents local fire jurisdictions that are located in the metro area.

Existing See Others Metro Local Fire Agencies

St. Louis County 911 Center Receives land line 911 calls and dispatches public safety agencies except State Patrol. St. Louis County has radios to monitor Duluth Police, Fire EMS and St. Louis County Sheriff.

Existing See Others St. Louis County

Greater Minnesota Local Fire Local fire departments that supports safe and efficient emergency response.

Existing See Others Greater Minnesota Local Fire Agencies

Greater Minnesota Local Police Local police departments that supports safe and efficient emergency response.

Existing See Others Greater Minnesota Local Police Agencies

St. Louis County Sheriff Center The sheriff department that supports safe and efficient emergency response.

Existing See Others St. Louis County Sheriff

Duluth Emergency Services Provides Ambulance/EMT services Existing See Others Duluth

35 Inter Jurisdictional

MnCARS

MnCARS Mn/CARS or Minnesota Condition Acquisition and Reporting System is scheduled for statewide activation by the end of 2000. It provides route specific road conditions, delays, detours, and closures. Mn/CARS is maintained by the Office of Maintenance but data is input throughout Mn/DOT at the District Offices and eventually at the State Patrol Dispatch District Offices or the TOCC's. Collects and distributes planned event information (i.e., road maintenance) and unplanned event information (i.e., road surface conditions).

Existing Information Service Provider

Mn/DOT Office of Maintenance


36 IVI Vehicles IVI Vehicles System aids drivers of snow plows in maintaining desired lane position and avoid collisions with obstacles during periods of low visibility. Similar systems are planned for ambulances and police cars.

Existing

and

Planned

Vehicle (User defined) Mn/DOT District Offices

Mn/DOT Office of Maintenance

12



Mn/DOT Office of Advanced Transportation

System

37 Criminal Justice Information Systems

TOCC Criminal Justice Information System (CJIS)

This is a database system that houses criminal information regarding motorist for Minnesota State Police to utilize.

Planned CJIS (User defined) Mn/DOT District Offices


38 Local Transit Management Center

Duluth Transit Authority Center Provides transit service in the Duluth area. Existing Transit Management

Duluth Transit Authority

St. Cloud MTC Provides for public transportation in the St. Cloud area. Existing See others St. Cloud Metropolitan Transit Commission

Mankato Transit Center Provides for public transportation in the Mankato area. Existing See others Heartland Express

City of Rochester Transit Center Provides transit service in the City of Rochester. Existing See Others City of Rochester

Rural Transit System This system provides for transit scheduling and dispatching for rural transit agencies (e.g., southwest translink).

Existing See Other Mn/DOT District Offices

Mn/DOT Office of Transit

Rural Transit Agencies

39 Local Transit Management Vehicles

St. Cloud MTC Transit Vehicles Transit vehicles that are dispatched by the St. Cloud MTC. Existing Transit Vehicle Subsystem

Vehicle

City of St. Cloud

Duluth Transit Authority Vehicles

Duluth transit vehicles that are dispatched by Transit Authority.

Existing See Others Duluth Transit Authority

Mankato Transit Vehicles Transit vehicles that are dispatched by the Mankato Transit Center.

Existing See Others

Heartland Express

City of Rochester Transit Vehicles

City of Rochester transit vehicles that are being dispatched. Existing See Other City of Rochester

Rural Transit Vehicles These vehicles are dispatched by operators in the TOCC Center. Where the communication system will support mobile data terminals, vehicles will be equipped with the terminals and a vehicle location and tracking component. This will provide real-time vehicle location with route and schedule adherence.

Existing See Others Mn/DOT District Offices

Mn/DOT Office of Transit

Rural Transit Agencies

40 Traveler Information Scenic Byways Kiosk Provides travel information through interactive kiosks. The Existing Remote Traveler Support Minnesota Office of Tourism

13



Kiosk kiosks are operated and maintained by Mn/DOT and the Minnesota Office of Tourism.

Mankato Kiosks System Provides traveler information for the Mankato area. Existing See Others Castle Rock

Orion Parking Garage Monitors This system will utilize monitors at several entrances to parking garages to provide transportation information to the public.

Planned See Others


41 Greater Minnesota State Patrol

Greater Minnesota State Patrol Greater Minnesota state patrol that supports safe and efficient emergency response. For the Greater Minnesota area. This is an example of a TOCC subsystem.


Archived Data Mgmt


42 DTN DTN Weather Information System (for Mankato)

Provides weather information to the City of Mankato. Existing Weather Service (Term) DTN

43 Mayday Service Provider Mayday System Mayday System can provide data to the State Patrol and emergency hospitals in the Twin Cities and Greater Minnesota.


Mn/DOT

44 Mayday Vehicle Mayday Vehicle These are vehicles equipped with Mayday systems Existing Vehicle Emergency Hospitals

Fire Departments


45 Inter-jurisdictional Emergency Management System

Orion CAD 911 System This system will be put in by the Minnesota State Police for the Twin Cities.

Planned Emergency Management

Archived Data Management


46 Local Roadway Maintenance System

Atkinson Bridge De-icing System

This system sprays chemicals on the bridge due to ice conditions that may form based on commands from the City of Duluth signal center. This is a an example of a de-icing system. This system will be represented by showing the City of Duluth roadside equipment sending data to the City of Duluth signal center.

Existing Atkinson Bridge De-icing System (User Defined)

City of Duluth

47 In Vehicle Signing System In-Vehicle Signing System Provides Information to school buses on railroad crossings and train presence for the City of Glencoe. This system will be represented by showing the City of Glencoe roadside equipment sending data to the school bus drivers.

Existing Vehicle Mn/DOT’s Office of Advance Transportation

Systems (OATS)

Mn/DOT’s Office of Fright and Railroad and Waterways

14



(OFRW)

48 In Vehicle Roadside Equipment

In Vehicle Roadside Equipment This is the In Vehicle Signing equipment by the roadside Existing Roadway Subsystem Mn/DOT’s Office of Fright and Railroad and Waterways

(OFRW

49 Data Center Records Center This center collects and archives all ITS and other data for Mn/DOT

Existing Archived Data Management

Office of Administrative Services

Transportation Information System (TIS)

TIS is a data based that is managed by the Office of Transportation Data Services. This office performs traffic forecasting for Mn/DOT and all the road log information (e.g., traffic and accident) is stored in a TIS data base.

Existing See Others Office of Transportation Data Services

50 Compliance Management Compliance Management System

Supports equipment on the roadside to detect red-light violation, railroad gate crossing infringements, speed compliance, and HOV lane use monitoring. This system will be represented by showing the compliance roadside equipment sending data to the local and state patrol.

Planned User Defined Minnesota State Patrol


The reader should note that the column for System Name shows specific systems names in some cases and generalizes system names in other cases. This naming convention was used for the following reasons: 1. The National ITS Architecture focuses on the functions that are being performed by any given system. Since there are several agencies/systems that are performing similar functions, some system

names were generalized and lump into a single category. For example every agency that operates traffic signals were not given their own grouping they have similar functionality. Similar examples exist for Traveler Information Centers, Local Emergency Management Centers, etc.

2. To ensure that the statewide architecture is kept at a manageable level.

15

MINNESOTA’S MARKET PACKAGES

The system inventory described who the players are for the Minnesota statewide architecture and what their responsibilities are for maintaining the transportation system. The next step in the development of a statewide architecture is to associate the systems identified in the system inventory with Market Packages. Market Packages are slices of the Physical Architecture that describe a particular transportation service that an agency or system is currently providing or has a desire to provide in the future. By associating the inventory with Market Packages, one will be able to obtain an initial insight as to which projects or systems are currently interacting or should be interacting with the state of Minnesota. The National ITS Architecture has identified a total of 63 Market Packages, however 32 were selected for Minnesota’s statewide architecture plus an additional Minnesota defined market package (Compliance Management). This section identifies the systems that are or will be involved in each of the selected market packages.

The next section will describe the following:

• Identification of the selected Market Package, • Definition of the Market Package, • Diagram of the Market Package, • Status of the services described as (existing or planned), and • Systems associated with the Market Package.

The reader should view each of the selected Market Packages as pieces of a puzzle of the statewide architecture. When all the Market Packages are combined they form an uncustomized statewide architecture.

Network Surveillance (ATMS01)

This market package includes traffic detectors, other surveillance equipment, the supporting field equipment, and wireline communications to transmit the collected data back to the Traffic Management Subsystem (agencies that were mapped to this category in the system inventory). The derived data can be used locally such as 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 (agencies that were mapped to this category in the system inventory).

16

ATMS01 - Network Surveillance

TrafficManagement

Collect TrafficSurveillance

Roadway

Roadway BasicSurveillance

InformationService Provider

trafficinformation

request fortraffic information

traffic flow

sensor andsurveillance control

Traffic Maintenance

traffic images

The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram.

The following systems identified in the inventory providing this transportation service are existing unless planned has been specified.

• Inter-Jurisdictional Traffic Management System • Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment (Existing and Planned) • Maintenance Dispatch Center • Metro TMC • Metro TMC Roadside Equipment • Metro Traffic Engineering Center • Metro Traffic Engineering Roadside Equipment • TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

Surface Street Control (ATMS03)

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

17

package ranging from static pre-timed control systems to fully 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.

ATMS03 - Surface Street Control

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



• Inter-Jurisdictional Traffic Management System • Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment (Existing and Planned) • Metro Traffic Engineering Center • Metro Traffic Engineering Roadside Equipment • Regional Traffic Management Center (Planned) • TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

18

Freeway Control (ATMS04)

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.

ATMS04 - Freeway Control

TrafficManagement

TMC FreewayManagement

Roadway

RoadwayFreeway Control

freeway control data

TrafficMaintenance

freeway control status

traffic flow

traffic images

Driver

driverinformation

sensor andsurveillance control



• Metro TMC • Metro TMC Roadside Equipment • Regional Traffic Management Center (Planned)

19

• TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

HOV Lane Management (ATMS05)

This market package manages HOV lanes by coordinating freeway ramp meters and connector signals with HOV lane usage signals. Preferential treatment is given to HOV lanes using special bypasses, reserved lanes, and exclusive rights-of-way that may vary by time of day. Vehicle occupancy detectors may be installed to verify HOV compliance and to notify enforcement agencies of violations.

ATMS05 - HOV Lane Management

TrafficManagement

TMC HOV Lane Management

Roadwayfreeway control data

Roadway HOV Control

HOV data

traffic flow

EnforcementAgency

violationnotification




20

Traffic Information Dissemination (ATMS06)

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.

ATMS06 Traffic Information Dissemination

TrafficManagement

TMC Traffic InfoDissemination

Roadway

roadway informationsystem status Roadway Traffic Info

Dissemination

roadway informationsystem data

InformationServiceProvider

trafficinformation

Driver

driverinformation

Mediatraffic information

for media

Basic Vehicle

broadcastadvisories

EmergencyManagement

TransitManagement current

networkconditions

traffic informationfor transit



• Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment (Existing and Planned) • Maintenance Dispatch Center • Metro TMC • Metro TMC Roadside Equipment

21

• Metro Traffic Engineering Center • Metro Traffic Engineering Roadside Equipment • Parking Management Center (Existing and Planned) • Parking Management Roadside Equipment • Regional Traffic Management Center (Planned) • TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

Regional Traffic Control (ATMS07)

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 Interjurisdictional 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.

ATM S07 - Regional Traffic Control

TrafficM anagement

Roadway



signal control data


TMC RegionalTraffic Control

Other TM

traffic flow

trafficcontrol

coordination

trafficinformationcoordination


22


• Inter-Jurisdictional Traffic Management System • Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment (Existing and Planned) • Metro Traffic Engineering Center • Metro Traffic Engineering Roadside Equipment

Incident Management System (ATMS08)

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 the 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.

23

ATMS08 - Incident Management System

EmergencyManagement

TrafficManagement

TMC Incident DispatchCoord/Communication

Roadway

Other TM


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




• Division of Emergency Management Center • DTN • Emergency Management Vehicle • Event Promoters • Greater Minnesota State Patrol • Inter-Jurisdictional Emergency Management System • Inter-Jurisdictional Traffic Management System • Local Emergency Management Center • Local Signal Center (Existing and Planned) • Maintenance Dispatch Center • Metro TMC • Metro Traffic Engineering Center • Minnesota Emergency Management Vehicle • National Weather Service • Regional Traffic Management Center (Planned) • Road Weather Information Center • State Patrol Dispatch Centers

24

• TOCC (Existing and Planned) • Traveler Information Center (Existing and Planned)

Traffic Forecast and Demand Management (ATMS09)

This market package includes advanced algorithms, processing, and mass storage capabilities that support historical evaluation, real-time assessment, and forecast of the roadway network performance. This includes the prediction of travel demand patterns to support better link travel time forecasts. The source data would come from the Traffic Management Subsystem itself as well as other traffic management centers and forecasted traffic loads derived from route plans supplied by the Information Service Provider Subsystem (systems identified in the inventory). In addition to short term forecasts, this market package provides longer range forecasts that can be used in transportation planning. This market package provides data that supports the implementation of TDM programs, and policies managing both traffic and the environment.

ATMS09 - Traffic Forecast and Demand Management

TrafficManagement

TMC Traffic NetworkPerformance Evaluation


Other TM


Event Promoters

eventplans

trafficinformation

traffic flowRoadway

TMC Toll/ParkingCoordination

ParkingManagement

TransitManagement

TollAdministration

parking demand management response

parking demand management request

toll demand management response

toll demand management request

transit demandmanagement

response

transit demand management request



• Metro TMC • Metro Traffic Engineering Center • Regional Traffic Management Center (Planned)

25

Virtual TMC and Smart Probe Data (ATMS12)

This market package provides for special requirements of rural road systems. Instead of a central TMC, the traffic management is distributed over a very wide area (e.g., a whole state or collection of states). Each locality has the capability of accessing available information for assessment of road conditions.

ATMS12 - Virtual TMC and Smart Probe Data

In-Vehicle SigningSystem

Vehicle

Roadway

Roadway Environment

Roadway

Automated RoadSigning

Roadway Probe Beacons

Smart Probe

roadway informationsystem data

vehicle probe data

vehicle signage data

vehicle probe data

roadwaycharacteristics

TrafficManagement

weatherconditions



• Road Weather Information Center • RWIS Roadside Equipment • TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

Standard Railroad Grade Crossing (ATMS13)

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

26

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.

ATMS13 - Standard Railroad Grade Crossing

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



• Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment • Metro Traffic Engineering Center • Metro Traffic Engineering Roadside Equipment

27

Advanced Railroad Grade Crossing (ATMS14)

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 from 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, additional information about the arriving train is also provided by the wayside interface equipment 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.

ATMS14 - Advanced Railroad Grade Crossing

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


28


• In Vehicle Signing System • In Vehicle Signing Roadside Equipment • Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment

Parking Facility Management (ATMS16)

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.

ATMS16 - Parking Facility Management

Parking Management

Parking

ManagementVehicle

Vehicle Toll/Parking Interface

FinancialInstitution

PaymentInstrument


tag update

tag data

transactionstatus

paymentrequest

EnforcementAgency


parkinginformation

request tag data

paymentrequest

forpayment

parking lot reservation

confirmationParking ElectronicPayment

Parking Surveillance



• Parking Management Center (Existing and Planned) • Parking Management Roadside Equipment

29

Reversible Lane Management (ATMS17)

This market package provides for the management of reversible lane facilities. In addition to standard surveillance capabilities, this market package includes sensory functions that detect wrong-way vehicles and other special surveillance capabilities that mitigate safety hazards associated with reversible lanes. The package includes the field equipment, physical lane access controls, and associated control electronics that manage and control these special lanes. This market package also includes the equipment used to electronically reconfigure intersections and manage right-of-way to address dynamic demand changes and special events.

ATMS17 - Reversible Lane Management

Traffic

Management

TMC ReversibleLane Management

TrafficOperationsPersonnel

Roadway

Roadway ReversibleLanes

traffic flow

incident data




signal control data

trafficoperator

inputs

trafficoperator

data

reversible lane status




30

Road Weather Information System (ATMS18)

This market package monitors current and forecast 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.

ATMS18 - Road Weather Information System

WeatherService

TrafficManagement

TMC Road WeatherMonitoring

Roadway

Roadway EnvironmentalMonitoring

Construction &Maintenance

RoadwayEnvironment

TrafficOperationsPersonnel

weatherinformation


maintenanceresourceresponse weather

conditions

environmental conditions

trafficoperator

inputs

trafficoperator

data

closurecoordination



• Local Signal Center (Existing and Planned) • Local Signal Center Roadside Equipment • National Weather Service • Road Weather Information Center • RWIS Roadside Equipment • TOCC (Existing and Planned) • TOCC Roadside Equipment (Existing and Planned)

31

Regional Parking Management (ATMS19)

This market package supports coordination between parking facilities to enable regional parking management strategies.

ATMS19 - Regional Parking Management

ParkingManagement

Parking Management

Parking Coordination

TransitManagement

parkingavailability

transit parking lot response

transit parkingcoordination

parking demand management request

TrafficManagement

OtherParking

parking coordination


The Parking Management Center is the only system identified from the inventory that is providing this transportation service. The system status is existing and planned.

Transit Vehicle Tracking (APTS1)

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.

32

APTS1 - Transit Vehicle Tracking

TransitManagement

Transit Center Trackingand Dispatch

Transit Vehicle

On-board TripMonitoring


transit and fareschedules

transit informationrequest

transit vehiclelocation data

Vehicle

vehiclelocation

transit vehicle schedule performance

Vehicle LocationDetermination


The following systems identified in the inventory providing this transportation service are existing.

• Local Transit Management Center • Local Transit Management Vehicles • Metro Transit Management Center • Metro Transit Management Vehicles

Transit Fixed-Route Operations (APTS2)

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 to provide the public with integrated and personalized dynamic schedules.

33

APTS2 - Transit Fixed-Route Operations

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



• Local Transit Management Center • Metro Transit Management Center

Demand Response Transit Operations (APTS3)

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 be either be operated by 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 request and uses wireline communications to make a reservation for the traveler.

34

APTS3 - Demand Response Transit Operations

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


demand responsivetransit request

transit information request



• Demand Responsive Transit Center • Demand Responsive Transit Vehicle

Transit Passenger and Fare Management (APTS4)

This market package allows for the management of passenger loading and fare payments on-board 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 on-board 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.

35

Remote TravelerSupport

TransitManagement

Transit Center Fare and Load Mgmt

Transit Vehicle

On-Board TransitFare and Load Mgmt


transit requestconfirmation



bad tag list

Remote TransitFare Management

transit farepayment

request

transit fare payment responses

PaymentInstrument

paymentrequest forpayment


paymentrequest

transactionstatus

EnforcementAgency


payment

request for payment

fare and payment status

APTS4 Transit Passenger and Fare Management



• Local Transit Management Center • Local Transit Management Vehicle

Transit Security (APTS5)

This market package provides for the physical security of transit passengers. An on-board 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.

36

APTS5 - Transit Security


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



• Local Transit Management Center • Metro Transit Management Center

Multi-modal Coordination (APTS7)

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.

37

APTS7 - Multi-Modal Coordination

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



• Local Signal Center (Existing and Planned) • Local Transit Management Center • Metro TMC • Metro Traffic Engineering Center • Metro Transit Management Center • TOCC (Existing and Planned)

Broadcast Traveler Information (ATIS1) 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.

38

ATIS1 - Broadcast Traveler Information


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


The Broadcast Information Providers is the only system identified from the inventory that is providing this transportation service. The system status is existing.

Interactive Traveler Information (ATIS2)

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 a trip or en-route to include 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.

39

ATIS2 - Interactive Traveler Information

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



• Traveler Information Center (Existing and Planned) • Traveler Information Kiosk

ITS Data Mart (AD1)

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.

40

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

AD1 - ITS Data Mart


The Data Center is the only system identified in the inventory providing this transportation service. The system status is existing.

ITS Data Warehouse (AD2)

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 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.

41

Archived DataManagement

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

Archived Data User Systems

WeatherService

Archived Data Administrator

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

AD2 - ITS Data Warehouse


The Data Center is the only system identified in the inventory providing this transportation service. The system status is existing.

Fleet Administration (CVO01)

This market package keeps track of vehicle location, itineraries, and fuel usage at the Fleet and Freight Management Subsystem using a cell based or satellite data link and the pre-existing wireless infrastructure. The vehicle has a processor to interface to its sensor (e.g., fuel gauge) and to the cellular data link. The Fleet and Freight Management Subsystem can provide the vehicle with dispatch instructions, and can process and respond to requests for assistance and general information from the vehicle via the cellular data link. The market package also provides the Fleet Manager with connectivity to intermodal transportation providers using the existing wireline infrastructure.

42

CVO01 - Fleet Administration

Fleet and FreightManagement

Fleet Administration

CommercialVehicle

On-board Trip Monitoring

fleet to driver update

driver and vehicle information

CommercialVehicle Driver

CVO driverinitialization

Fleet Maintenance Management alerts,

messages

route plan

route request


vehiclelocation

Vehicle

Vehicle Location Determination

CommercialVehicle Manager

fleet status fleet managerinquiry

log information


The Truck Center is the only system identified in the inventory providing this transportation service. The system status is existing.

CV Administrative Processes (CVO04)

This market package provides for electronic application, processing, fee collection, issuance, and distribution of CVO credential and tax filing. Through this process, carriers, drivers, and vehicles may be enrolled in the electronic clearance program provided by a separate market package which allows commercial vehicles to be screened at mainline speeds at commercial vehicle check points. Through this enrollment process, current profile databases are maintained in the Commercial Vehicle Administration Subsystem and snapshots of this database are made available to the commercial vehicle check facilities at the roadside to support the electronic clearance process.

43

CVO04 - CV Administrative Processes

Fleet andFreight Management

Fleet Credentials and Taxes Management

and Reporting

Other CVAS

electronic credentialsCommercial Vehicle

Administration.Credentials and Taxes

Administration credential application

CVASinformationexchange


paymentrequest

transactionstatus

PaymentInstrument

paymentrequest forpayment

compliance review report

CV Information Exchange



• Account Management Providers • Department of Motor Vehicles • Truck Center

HAZMAT Management (CVO10)

This market package integrates incident management capabilities with commercial vehicle tracking to assure effective treatment of HAZMAT material and incidents. HAZMAT tracking is performed by the Fleet and Freight Management Subsystem. The Emergency Management subsystem is notified by the Commercial Vehicle if an incident occurs and coordinates the response. The response is tailored based on information that is provided as part of the original incident notification or derived from supplemental information provided by the Fleet and Freight Management Subsystem. The latter information can be provided prior to the beginning of the trip or gathered following the incident depending on the selected policy and implementation.

44

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

CVO10 - HAZMAT Management



• Metro TMC • Regional Traffic Management Center (Planned) • TOCC (Existing and Planned) • Truck Center

Emergency Response (EM1)

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.

45

EM1 - Emergency Response

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



• Division of Emergency Management Center • Emergency Management Vehicle • Greater Minnesota State Patrol • Local Emergency Management Center • Maintenance Dispatch Center • Regional Traffic Management Center (Planned) • State Patrol Dispatch Centers • TOCC (Existing and Planned)

Emergency Routing (EM2) 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.

46

EM2 - Emergency Routing

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




• Greater Minnesota State Patrol • Inter-Jurisdictional Emergency Management System (Planned) • Local Emergency Management Center • Maintenance Dispatch Center • Regional Traffic Management Center (Planned) • State Patrol Dispatch Centers • TOCC (Existing and Planned)

Mayday Support (EM3)

This package allows the user (driver or non-driver) to initiate a request for emergency assistance and enables the Emergency Management Subsystem to locate the user and determine the appropriate response. The Emergency Management Subsystem may be operated by the public sector or by a private sector provider. The request from the traveler needing assistance may be manually initiated or automated and linked to vehicle sensors. The data is sent to the Emergency Management subsystem using wide area wireless communications with voice as an option. Providing user location implies either a location technology within the user device or location determination within the communications infrastructure.

47

EM3 - Mayday Support

EmergencyManagement

Mayday Support

Vehicle

Vehicle Mayday I/F

Personal Inform.Access

Personal Mayday I/F


Remote Mayday I/F

Other EM

emergency notification

emergency acknowledge





incidentreport


Personal Location Determination

Vehicle Safety Monitoring System



• Greater Minnesota State Patrol • Mayday Vehicle • State Patrol Dispatch Centers

Compliance Management

In the case of the Minneapolis/St. Paul Metropolitan Area, the existing Market Packages in the National ITS Architecture did not satisfy the specific need for enforcement of traffic infractions. As such, a new Market Package (Compliance Management) was developed to strictly address this concern. The Compliance Management package is defined as follows: This package allows enforcement agencies to use the Roadway Subsystem to support equipment packages to detect red-light violation, railroad gate crossing infringements, speed compliance, and HOV lane use monitoring. This package enables the Emergency Management Subsystem to detect the violation and respond immediately, or to activate warning systems that alert drivers to their offense. The detection may be automatically linked to roadside equipment allowing for red-light detection, speed violation systems, and violation of HOV lane use. The data from the Roadway Subsystem may be sent to the Emergency Management subsystem using wireless communications with the

48

violator or vehicle owner. Notification of the offense may be transmitted to process for compliance management actions, communications, and/or enforcement. In other cases where the law prohibits such action by enforcement agencies, compliance management may consist of roadway technologies, for example, that will sense excessive speeds and triggers a message board, warning the violator of the speeding infraction.


• Compliance Roadside Equipment • Metro Local Police Centers • State Patrol Dispatch Centers

MINNESOTA STATEWIDE ARCHITECTURE

The following sections will illustrate Minnesota’s Statewide Architecture. The architecture is based on the inventory and the transportation services identified in the previous sections. Minnesota’s statewide architecture is represented by a series of tables. The information exchanges between stakeholders are identified in the statewide architecture. This documentation will allow agencies to examine the existing and planned interfaces they have among each other and work together to reach agreements on implementation of certain interfaces.

System Interconnections

System interconnections describe which agencies are currently exchanging information or have plans to exchange information in the future. The interconnections between the various systems, which were defined in Table 1 of the system inventory, are shown in Appendix A. Appendix A is a listing of tables of the various interconnects for each system identified in Minnesota’s statewide architecture. Each table has three columns (elements, elements and status). The element columns represent an agency or system that is either sending or receiving information to/from another agency or system (e.g., Table A2. Broadcast Information Providers) Table A2 shows that Broadcast Information Providers is exchanging information with the Demand Transit Responsive Center. This information exchange is existing and can be bi-directional.

System Interconnects are the starting point for stakeholders to become familiar with the overall environment in which they operate. Once stakeholders are in agreement with the system interconnects, they can then further explore these interconnections for their information content. The information content of system interconnects is described in the next section.

System Interfaces and Information Exchanges

In order to explore the next level of detail in the Minnesota’s Statewide Architecture, one needs to examine the information exchange between the systems interconnects. At the information exchange level, it is evident what information is shared between the system interconnects identified in Appendix A. The information content of the interconnects is captured in Appendix B. Appendix B is a listing of tables that illustrates the information exchanges among the systems in the Minnesota Statewide Architecture. Each table has five columns, which are described below:

• Source Element – the point in which the data is being collected and sent from. • Flow Name – the name of the information flow carrying the content information.

49

• Flow Description – description of the information contents of the flow name. • Destination Element – the receiver of the data from the source element. • Flow Status – indication of the flow name being existing information exchange or an

exchange that is planned at a later date.

Elements not defined by the National ITS Architecture are identified with an (*) because they are local functions that are important to Mn/DOT.

Potential Standards

For each information exchange between system interconnects identified in Appendix B, there are potential standards that can be examined to aid in deploying system interfaces. In order to view the potential standards for Minnesota’s Statewide Architecture, the standards report must be printed from the Microsoft Access Database. The report is not included here because it is more of an implementation concern whereas regional or statewide architectures are more of a planning concern.

Once the standards report is printed, there will be five columns used to describe the output. These are:

• Source Element – the point in which the data is being collected and sent from. • Destination Element – the receiver of the data from the source element. • Flow Name – description of the information contents of the flow name. • Standard Doc ID – the identification number of the standard document describing a

communications protocol, message set or data dictionary. • Standard Title – the name of the standards document that describes a communications

protocol, message set or data dictionary.

One might wonder how to use the information in the standards reports. Stakeholders should come together to agree upon which standards to implement for the chosen system interfaces identified in Appendix B. For example on the first page of the Standards Report, media information request is being sent from the Broadcast Information Provider to the Metro TMC. This interface shows nine potential standards that can be implemented. Stakeholders need to agree on which ones to deploy. One should also note that interrelationships exist among the various standards, and deployers may need to select more than one standard from the list of choices. For example if DATEX is the protocol of choice, the stakeholders might want to investigate the following standards for the media information request:

• Standard for Emergency Management Data Dictionary • Standard for Common Incident Management Message • Base Standard: Octet Encoding Rules (OER) • Subnet Profile for Ethernet • Internet (TCP/IP and UDP/IP) Transport Profile • Application Profile for Data Exchange ASN.1 (DATEX) • Information Profile for DATEX

Keep in mind that a suite of ITS Standards is needed to fully standardize the communications protocol, message sets and data elements. The goal is to end up with a protocol, message sets, and data dictionaries that all work together. Also future design decisions should take the chosen standards into account.

Standards are an essential part of system integration. Several ITS standards activities are currently in development by the Standard Development Organizations (SDO). These standards address particular interfaces identified in the National ITS Architecture.

50

In ITS, standards development activities have been allocated to the following organizations:

• AASHTO (American Association of State Highway and Transportation Officials) • ANSI (American National Standards Institute) • ASTM (American Society for Testing and Materials) • IEEE (Institute of Electrical and Electronics Engineers) • ITE (Institute of Transportation Engineers) • NEMA (National Electrical Manufacturers Association) • SAE (Society of Automotive Engineers)

Although each standards activity is allocated to a single SDO, it should be noted that many of the standards efforts are collaborative between multiple SDOs (e.g., NTCIP Joint Steering Committee is comprised of representatives from AASHTO, ITE and NEMA).

For the Minnesota Statewide Architecture, the applicable standards are being developed by five standards development organizations: AASHTO, ASTM, ITE, IEEE, and SAE. Table 2 lists the web sites of the SDO home pages (e.g., IEEE) as well as specific ITS Standards efforts (e.g., TMDD). Note: The ITS Standards specific internet addresses may change in the future.

Table 2. Standards Information Sources

Standard Development Organizations (SDO) Home Page

ITS Standards Specific Sites

AASHTO (www.aashto.org) NTCIP website (www.ntcip.org) *

ASTM (www.astm.org) Select the link for standardization news

IEEE (stdsbbs.ieee.org) Standards Coordinating Committee on ITS (grouper.ieee.org/groups/scc32/index.html)

ITE (www.ite.org) Traffic Management Data Dictionary and Message Sets for External Traffic Management Center Communications

(www.ite.org/tmdd/)

SAE (www.sae.org) www.sae.org/TECHCMTE/gits.htm * - Website also has an NTCIP guide that presents a framework on how NTCIP standards work

There are several excellent resources about ITS standards on the World Wide Web. The ITS America Standards Home Page (www.itsa.org/standards.html) provides access to standards information relating to all aspects of ITS. It also contains links to the organizations involved and, where possible, provides rapid access to published standards documents. The U.S. DOT Joint Program Office Standards site (www.its.dot.gov/standard/standard.htm) provides current status on the standards acceleration program.

The identified web site links may change from time-to-time. A current set of links to these sites will be maintained on the National ITS Architecture website at www.iteris.com/itsarch.

http://stdsbbs.ieee.org/

http://www.sae.org/TECHCMTE/gits.htm

51

HOW TO USE THE STATEWIDE ARCHITECTURE

It is recommended that stakeholders should use this document in the following manner. If a stakeholder wanted to see how they are represented in Minnesota’s Statewide Architecture, they would start with the system inventory and locate their system (e.g., Metro TMC). In order to see how Metro TMC is associated with other systems, the stakeholder should refer to the respective system interconnect table. In this example, Metro TMC system interconnect table is Table A14. The system interconnects show that Metro TMC is sharing data with specific traffic and public safety organizations. In some cases general organizations may have been defined that contain similar interfaces in order to reduce complexity (e.g., local signal centers). The system interconnects also shows which organizations need to have discussions and potential agreements in place if enhancements are to the Metro TMC. Once the appropriate stakeholders have been identified, they can discuss the existing and planned information exchanges and determine how to implement certain interfaces. The information exchange tables will provide insight into the interfaces. In this example, Table B14 focuses on the Metro TMC information exchanges. Table B14 shows that incident and traffic information from transportation and public safety organizations is being used to provide congestion information to motorist and also used to coordinate incident responses. Stakeholders can then view the Minnesota Standards Reports and make decisions on which standards to investigate and potentially implement.

52

APPENDIX A – SYSTEM INTERCONNECT TABLES

53

Table A1. Account Management Providers

Element Element Status

Account Management Providers Demand Responsive Transit Center Planned

Account Management Providers Truck Center Existing

Table A2. Broadcast Information Providers


Broadcast Information Providers Demand Responsive Transit Center Existing

Broadcast Information Providers Division of Emergency Management Center Existing

Broadcast Information Providers Greater Minnesota State Patrol Existing

Broadcast Information Providers Local Emergency Management Center Existing

Broadcast Information Providers Local Signal Center Existing

Broadcast Information Providers Local Transit Management Center Existing

Broadcast Information Providers Metro TMC Existing

Broadcast Information Providers Metro Traffic Engineering Center Existing

Broadcast Information Providers Metro Transit Management Center Existing

Broadcast Information Providers Regional Traffic Management Center Planned

Broadcast Information Providers State Patrol Dispatch Centers Existing

Broadcast Information Providers TOCC Existing

Broadcast Information Providers Traveler Information Center Existing

Table A3. Local Signal Center


Broadcast Information Providers Local Signal Center Existing

Division of Emergency Management Center Local Signal Center Planned

DTN Local Signal Center Existing

Event Promoters Local Signal Center Existing

Inter-jurisdictional Traffic Management System Local Signal Center Planned

Local Emergency Management Center Local Signal Center Existing

Local Signal Center Local Signal Center_Roadside Equipment Existing

Local Signal Center Metro TMC Planned

Local Signal Center Metro Traffic Engineering Center Planned

Local Signal Center Metro Transit Management Center Planned

Local Signal Center National Weather Service Existing

Local Signal Center Parking Management Center Existing

Local Signal Center Regional Traffic Management Center Planned

Local Signal Center TOCC Planned

Local Signal Center Traveler Information Center Planned

54

Table A4. Local Signal Center Roadside Equipment


Local Signal Center Local Signal Center_Roadside Equipment Existing

Table A5. Demand Responsive Transit Center


Account Management Providers Demand Responsive Transit Center Planned

Broadcast Information Providers Demand Responsive Transit Center Existing

Demand Responsive Transit Center Demand Responsive Transit Vehicle Existing

Demand Responsive Transit Center Division of Emergency Management Center Planned

Demand Responsive Transit Center Local Emergency Management Center Planned

Demand Responsive Transit Center Local Transit Management Center Planned

Demand Responsive Transit Center Metro Transit Management Center Existing

Table A6. Demand Responsive Transit Vehicle


Demand Responsive Transit Center Demand Responsive Transit Vehicle Existing

Table A7. Division of Emergency Management Center


Broadcast Information Providers Division of Emergency Management Center Existing

Demand Responsive Transit Center Division of Emergency Management Center Planned

Division of Emergency Management Center Greater Minnesota State Patrol Existing

Division of Emergency Management Center Local Emergency Management Center Existing

Division of Emergency Management Center Local Signal Center Planned

Division of Emergency Management Center Maintenance Dispatch Center Planned

Division of Emergency Management Center Metro TMC Planned

Division of Emergency Management Center Metro Traffic Engineering Center Planned

Division of Emergency Management Center Metro Transit Management Center Planned

Division of Emergency Management Center National Weather Service Existing

Division of Emergency Management Center Regional Traffic Management Center Planned

Division of Emergency Management Center State Patrol Dispatch Centers Existing

Division of Emergency Management Center TOCC Planned

55

Table A8. Event Promoters


Event Promoters Greater Minnesota State Patrol Existing

Event Promoters Local Emergency Management Center Existing

Event Promoters Local Signal Center Existing

Event Promoters Metro TMC Existing

Event Promoters Metro Traffic Engineering Center Existing

Event Promoters Regional Traffic Management Center Planned

Event Promoters State Patrol Dispatch Centers Existing

Event Promoters TOCC Existing

Event Promoters Traveler Information Center Existing

Table A9. National Weather Service


Division of Emergency Management Center National Weather Service Existing

Greater Minnesota State Patrol National Weather Service Existing

Local Emergency Management Center National Weather Service Planned

Local Signal Center National Weather Service Existing

Local Transit Management Center National Weather Service Existing

Maintenance Dispatch Center National Weather Service Existing

Metro TMC National Weather Service Existing

Metro Traffic Engineering Center National Weather Service Existing

National Weather Service Regional Traffic Management Center Planned

National Weather Service State Patrol Dispatch Centers Existing

National Weather Service TOCC Existing

National Weather Service Traveler Information Center Existing

National Weather Service Truck Center Existing

Table A10. Map Update Providers


Map Update Providers Traveler Information Center Planned

Table A11. Department of Motor Vehicles


Department of Motor Vehicles Truck Center Existing

56

Table A12. Regional Traffic Management Center


Broadcast Information Providers Regional Traffic Management Center Planned

Data Center Regional Traffic Management Center Planned

Division of Emergency Management Center Regional Traffic Management Center Planned

Electrical Services Center Regional Traffic Management Center Planned

Emergency Management Vehicle Regional Traffic Management Center Planned

Event Promoters Regional Traffic Management Center Planned

Local Signal Center Regional Traffic Management Center Planned

Maintenance Dispatch Center Regional Traffic Management Center Planned

Metro TMC_Roadside Equipment Regional Traffic Management Center Planned

National Weather Service Regional Traffic Management Center Planned

Regional Traffic Management Center Road Weather Information Center Planned

Regional Traffic Management Center State Patrol Dispatch Centers Planned

Regional Traffic Management Center TOCC Planned

Regional Traffic Management Center Traveler Information Center Planned

Table A13. Metro TMC Roadside Equipment


Metro TMC Metro TMC_Roadside Equipment Existing

Metro TMC_Roadside Equipment Regional Traffic Management Center Planned

Table A14. Metro TMC


Broadcast Information Providers Metro TMC Existing

Data Center Metro TMC Planned

Division of Emergency Management Center Metro TMC Planned

Electrical Services Center Metro TMC Existing

Emergency Management Vehicle Metro TMC Existing

Event Promoters Metro TMC Existing

Inter-jurisdictional Traffic Management System Metro TMC Existing

Local Signal Center Metro TMC Planned

Maintenance Dispatch Center Metro TMC Existing

Metro TMC Metro TMC_Roadside Equipment Existing

Metro TMC Metro Traffic Engineering Center Existing

Metro TMC National Weather Service Existing

Metro TMC Road Weather Information Center Existing

Metro TMC State Patrol Dispatch Centers Planned

Metro TMC TOCC Existing

57


Metro TMC Traveler Information Center Planned

Table A15. Inter-jurisdictional Traffic Management System


Inter-jurisdictional Traffic Management System Local Signal Center Planned

Inter-jurisdictional Traffic Management System Metro TMC Existing

Inter-jurisdictional Traffic Management System Metro Traffic Engineering Center Existing

Table A16. State Patrol Dispatch Centers


Broadcast Information Providers State Patrol Dispatch Centers Existing

Compliance Management Roadside Equipment State Patrol Dispatch Centers Planned

Division of Emergency Management Center State Patrol Dispatch Centers Existing

Event Promoters State Patrol Dispatch Centers Existing

Greater Minnesota State Patrol State Patrol Dispatch Centers Existing

Inter-Jurisdictional Emergency Management System State Patrol Dispatch Centers Planned

Local Emergency Management Center State Patrol Dispatch Centers Planned

Metro TMC State Patrol Dispatch Centers Planned

Minnesota Emergency Management Vehicle State Patrol Dispatch Centers Existing

National Weather Service State Patrol Dispatch Centers Existing

Regional Traffic Management Center State Patrol Dispatch Centers Planned

Table A17. Minnesota Emergency Management Vehicle

Element Element

Greater Minnesota State Patrol Minnesota Emergency Management Vehicle

Minnesota Emergency Management Vehicle State Patrol Dispatch Centers

Table A18. Maintenance Dispatch Center


Division of Emergency Management Center Maintenance Dispatch Center Planned

Emergency Management Vehicle Maintenance Dispatch Center Existing

Inter-Jurisdictional MnCARS Maintenance Dispatch Center Existing

Maintenance Dispatch Center Maintenance Dispatch Center_Vehicle Existing

Maintenance Dispatch Center Metro TMC Existing

Maintenance Dispatch Center National Weather Service Existing

Maintenance Dispatch Center Regional Traffic Management Center Planned

58


Maintenance Dispatch Center TOCC Existing

Table A19. Electrical Services Center


Electrical Services Center Metro TMC Existing

Electrical Services Center Metro Traffic Engineering Center Existing

Electrical Services Center Regional Traffic Management Center Planned

Table A20. Maintenance Dispatch Center Vehicle


Maintenance Dispatch Center Maintenance Dispatch Center_Vehicle Existing

Table A21. TOCC


Broadcast Information Providers TOCC Existing

Data Center TOCC Planned

Division of Emergency Management Center TOCC Planned

Event Promoters TOCC Existing

Greater Minnesota State Patrol TOCC Existing

Inter-Jurisdictional MnCARS TOCC Existing

Local Emergency Management Center TOCC Existing

Local Signal Center TOCC Planned

Local Transit Management Center TOCC Planned

Maintenance Dispatch Center TOCC Existing

Metro TMC TOCC Existing

Metro Transit Management Center TOCC Planned

National Weather Service TOCC Existing

Regional Traffic Management Center TOCC Planned

Road Weather Information Center TOCC Planned

TOCC TOCC_Roadside Equipment Existing

TOCC Traveler Information Center Existing

Table A22. TOCC Roadside Equipment


TOCC TOCC_Roadside Equipment Existing

59

Table A23. Metro Transit Management Center


Broadcast Information Providers Metro Transit Management Center Existing

Demand Responsive Transit Center Metro Transit Management Center Existing

Division of Emergency Management Center Metro Transit Management Center Planned

Local Emergency Management Center Metro Transit Management Center Existing

Local Signal Center Metro Transit Management Center Planned

Local Transit Management Center Metro Transit Management Center Planned

Metro Transit Management Center Metro Transit Management Vehicles Existing

Metro Transit Management Center TOCC Planned

Metro Transit Management Center Traveler Information Center Planned

Table A24. Metro Transit Management Vehicles


Metro Transit Management Center Metro Transit Management Vehicles Existing

Table A25. Road Weather Information Center


Data Center Road Weather Information Center Existing

Metro TMC Road Weather Information Center Existing

Regional Traffic Management Center Road Weather Information Center Planned

Road Weather Information Center RWIS_Roadside Equipment Existing

Road Weather Information Center TOCC Planned

Road Weather Information Center Traveler Information Center Existing

Table A26. RWIS Roadside Equipment


Road Weather Information Center RWIS_Roadside Equipment Existing

Table A27. Truck Center


Account Management Providers Truck Center Existing

Department of Motor Vehicles Truck Center Existing

National Weather Service Truck Center Existing

60

Table A28. Traveler Information Center


Broadcast Information Providers Traveler Information Center Existing

Event Promoters Traveler Information Center Existing

Greater Minnesota State Patrol Traveler Information Center Planned

Local Emergency Management Center Traveler Information Center Planned

Local Signal Center Traveler Information Center Planned

Map Update Providers Traveler Information Center Planned

Metro TMC Traveler Information Center Planned

Metro Traffic Engineering Center Traveler Information Center Planned

Metro Transit Management Center Traveler Information Center Planned

National Weather Service Traveler Information Center Existing

Parking Management Center Traveler Information Center Existing

Regional Traffic Management Center Traveler Information Center Planned

Road Weather Information Center Traveler Information Center Existing

TOCC Traveler Information Center Existing

Traveler Information Center Traveler Information Kiosk Existing

Table A29. Parking Management Center


Local Signal Center Parking Management Center Existing

Parking Management Center Parking Management_Roadside Equipment Existing

Parking Management Center Traveler Information Center Existing

Table A30. Parking Management Roadside Equipment


Parking Management Center Parking Management_Roadside Equipment Existing

Table A31. Metro Traffic Engineering Center


Broadcast Information Providers Metro Traffic Engineering Center Existing

Data Center Metro Traffic Engineering Center Planned

Division of Emergency Management Center Metro Traffic Engineering Center Planned

Electrical Services Center Metro Traffic Engineering Center Existing

Event Promoters Metro Traffic Engineering Center Existing

Inter-jurisdictional Traffic Management System Metro Traffic Engineering Center Existing

Local Emergency Management Center Metro Traffic Engineering Center Existing

Local Signal Center Metro Traffic Engineering Center Planned

61


Metro TMC Metro Traffic Engineering Center Existing

Metro Traffic Engineering Center Metro Traffic Engineering_Roadside Equipment Existing

Metro Traffic Engineering Center National Weather Service Existing

Metro Traffic Engineering Center Traveler Information Center Planned

Table A32. Metro Traffic Engineering Roadside Equipment


Metro Traffic Engineering Center Metro Traffic Engineering_Roadside Equipment Existing

Table A33. Emergency Management Vehicle


Emergency Management Vehicle Maintenance Dispatch Center Existing

Emergency Management Vehicle Metro TMC Existing

Emergency Management Vehicle Regional Traffic Management Center Planned

Table A34. Local Emergency Management Center


Broadcast Information Providers Local Emergency Management Center Existing

Compliance Management Roadside Equipment Local Emergency Management Center Planned

Demand Responsive Transit Center Local Emergency Management Center Planned

Division of Emergency Management Center Local Emergency Management Center Existing

Event Promoters Local Emergency Management Center Existing

Greater Minnesota State Patrol Local Emergency Management Center Existing

Inter-Jurisdictional Emergency Management System Local Emergency Management Center Planned

Local Emergency Management Center Local Signal Center Existing

Local Emergency Management Center Local Transit Management Center Planned

Local Emergency Management Center Mayday Vehicle Existing

Local Emergency Management Center Metro Traffic Engineering Center Existing

Local Emergency Management Center Metro Transit Management Center Existing

Local Emergency Management Center National Weather Service Planned

Local Emergency Management Center State Patrol Dispatch Centers Planned

Local Emergency Management Center TOCC Existing

Local Emergency Management Center Traveler Information Center Planned

62

Table A35. Inter-Jurisdictional MnCARS


Data Center Inter-Jurisdictional MnCARS Planned

Inter-Jurisdictional MnCARS Maintenance Dispatch Center Existing

Inter-Jurisdictional MnCARS TOCC Existing

Table A36. Local Transit Management Center


Broadcast Information Providers Local Transit Management Center Existing

Demand Responsive Transit Center Local Transit Management Center Planned

Local Emergency Management Center Local Transit Management Center Planned

Local Transit Management Center Local Transit Management_Vehicles Existing

Local Transit Management Center Metro Transit Management Center Planned

Local Transit Management Center National Weather Service Existing

Local Transit Management Center TOCC Planned

Table A37. Local Transit Management Vehicles


Local Transit Management Center Local Transit Management_Vehicles Existing

Table A38. Traveler Information Kiosk


Traveler Information Center Traveler Information Kiosk Existing

Table A39. Greater Minnesota State Patrol


Broadcast Information Providers Greater Minnesota State Patrol Existing

Compliance Management Roadside Equipment Greater Minnesota State Patrol Planned

Division of Emergency Management Center Greater Minnesota State Patrol Existing

Event Promoters Greater Minnesota State Patrol Existing

Greater Minnesota State Patrol Inter-Jurisdictional Emergency Management System Existing

Greater Minnesota State Patrol Local Emergency Management Center Existing

Greater Minnesota State Patrol Mayday Vehicle Existing

Greater Minnesota State Patrol Minnesota Emergency Management Vehicle Existing

Greater Minnesota State Patrol National Weather Service Existing

Greater Minnesota State Patrol State Patrol Dispatch Centers Existing

Greater Minnesota State Patrol TOCC Existing

63


Greater Minnesota State Patrol Traveler Information Center Planned

Table A40. DTN


DTN Local Signal Center Existing

Table A41. Mayday Service Provider


Mayday Service Provider Mayday Vehicle Existing

Table A42. Mayday Vehicle


Greater Minnesota State Patrol Mayday Vehicle Existing

Local Emergency Management Center Mayday Vehicle Existing

Mayday Service Provider Mayday Vehicle Existing

Table A43. Inter-Jurisdictional Emergency Management System


Greater Minnesota State Patrol Inter-Jurisdictional Emergency Management System Existing

Inter-Jurisdictional Emergency Management System Local Emergency Management Center Planned

Inter-Jurisdictional Emergency Management System State Patrol Dispatch Centers Planned

Table A44. In Vehicle Signing System


In Vehicle Signing System In Vehicle Signing_Roadside Equipment Planned

Table A45. In Vehicle Signing Roadside Equipment


In Vehicle Signing System In Vehicle Signing_Roadside Equipment Planned

64

Table A46. Data Center


Data Center Inter-Jurisdictional MnCARS Planned

Data Center Metro TMC Planned

Data Center Metro Traffic Engineering Center Planned

Data Center Regional Traffic Management Center Planned

Data Center Road Weather Information Center Existing

Data Center TOCC Planned

Table A47. Compliance Management Roadside Equipment


Compliance Management Roadside Equipment Greater Minnesota State Patrol Planned

Compliance Management Roadside Equipment Local Emergency Management Center Planned

Compliance Management Roadside Equipment State Patrol Dispatch Centers Planned

65

APPENDIX B – INFORMATION EXCHANGE TABLES

66

Table B1. Account Management Providers Information Exchanges

SourceElement FlowName FlowDescription DestinationElement FlowStatus

Account Management

Providers

transaction status Response to transaction request. Normally dealing with a request for payment.

Truck Center Existing

Demand Responsive Transit Center

payment request Request for payment from financial institution. Account Management

Providers

Planned

Truck Center payment request Request for payment from financial institution. Account Management

Providers

Existing

Table B2 Broadcast Information Providers Information Exchanges


Broadcast Information Providers

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).

Local Signal Center Existing




Metro TMC Existing




Metro Traffic Engineering Center

Existing




Regional Traffic Management Center

Planned




TOCC Existing




Traveler Information Center

Existing


media information request

Request from the media for current transportation information. Local Signal Center Existing



Request from the media for current transportation information. Metro TMC Existing



Request from the media for current transportation information. Metro Traffic Engineering Center

Existing



Request from the media for current transportation information. Regional Traffic Management Center

Planned



Request from the media for current transportation information. TOCC Existing



Request from the media for current transportation information. Traveler Information Center

Existing


transit incidents for media

Report of an incident impacting transit operations for public dissemination through the media.


Existing

67



transit information for media

Report of transit schedule deviations for public dissemination through the media.


Planned

Division of Emergency

Management Center

incident information for media

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


Existing

Greater Minnesota State Patrol




Existing

Local Emergency Management Center




Existing

Local Signal Center traffic information for media

Report of current traffic conditions, incidents, maintenance activities and other traffic-related information prepared for public

dissemination through the media.


Existing

Local Transit Management Center




Existing





Planned

Metro TMC incident information for media



Existing

Metro TMC traffic information for media




Existing

Metro TMC traveler information for media

General traveler information regarding incidents, unusual traffic conditions, transit issues, or other advisory information that has

been desensitized and provided to the media.


Existing


traffic information for media




Existing

Metro Transit Management Center




Existing





Existing





Existing






Existing





Planned






Planned






Planned

State Patrol Dispatch incident information for Report of current desensitized incident information prepared for Broadcast Existing

68

SourceElement FlowName FlowDescription DestinationElement FlowStatus Centers media public dissemination through the media. Information

Providers

TOCC incident information for media



Existing

TOCC traffic information for media




Existing

TOCC traveler information for media




Existing






Planned






Existing

Table B3. Local Signal Center Information Exchanges








Request from the media for current transportation information. Local Signal Center Existing


Management Center

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).

Local Signal Center Planned

DTN weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity,

precipitation, visibility, light conditions, etc.).


Event Promoters event plans Plans for major events possibly impacting traffic. Local Signal Center Existing

Inter-jurisdictional Traffic Management

System

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.



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.



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






Local Signal Center commands to spray chemicals*

Instructions to maintenance vehicle operators to spray chemicals on the roadway system.

Local Signal Center_Roadside

Existing

69

SourceElement FlowName FlowDescription DestinationElement FlowStatus Equipment

Local Signal Center 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.

Metro TMC Planned

Local Signal Center emergency traffic control response

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


Existing




Planned

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


Equipment

Planned

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


Equipment

Planned

Local Signal Center ice levels on bridge request*

Request for reports describing ice conditions on the bridge. Local Signal Center_Roadside

Equipment

Existing

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


Management Center

Planned



Existing


Metro TMC Planned



Planned



Planned


TOCC Planned

Local Signal Center 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.


Existing




Metro TMC Planned





Planned





Planned




TOCC Planned

Local Signal Center parking instructions Information that allows local parking facilities to be managed to support regional traffic management objectives.

Parking Management Center

Existing

Local Signal Center roadway information system data

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.


Equipment

Existing

70


Local Signal Center sensor and surveillance control

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


Equipment

Existing

Local Signal Center signal control data Information used to configure and control traffic signal systems. Local Signal Center_Roadside

Equipment

Existing

Local Signal Center traffic control priority status

Status of signal priority request functions at the roadside (e.g. enabled or disabled).


Planned

Local Signal Center 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.

Metro TMC Planned




Planned




Planned



TOCC Planned




Planned

Local Signal Center 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.


Planned





Planned




TOCC Planned





Planned

Local Signal Center traffic information for media




Existing

Local Signal Center traffic information for transit

Current and forecasted traffic information and incident information.


Planned


Equipment

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



Equipment

flood warning alert* Issues an alert to MnDOT regarding high water levels. Local Signal Center Existing


Equipment

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

condition.


Local Signal ice levels on bridge* Reports describing ice conditions on the bridge. Local Signal Center Existing

71

SourceElement FlowName FlowDescription DestinationElement FlowStatus Center_Roadside

Equipment


Equipment

intersection blockage notification

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



Equipment

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.



Equipment

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.



Equipment

signal control status Status of surface street signal controls. Local Signal Center Existing


Equipment

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

density measures).



Equipment

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

applications.


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


Metro TMC incident response status Status of the current incident response including traffic management strategies implemented at the site (e.g., closures,



Metro TMC 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.


Metro TMC road network use Aggregated route usage and associated travel data from clients for planning and analysis.


Metro TMC traffic information coordination





traffic information coordination














request for traffic information






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



traffic control priority request

Request for signal priority at one or more intersections along a particular route.


72



transit system data Current transit system operations information indicating current transit routes, the level of service on each route, and the progress

of individual vehicles along their routes for use in forecasting demand and estimating current transportation network

performance.


National Weather Service

weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity,

















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


TOCC 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.


TOCC request for traffic information





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


TOCC traffic information coordination










Table B4. Local Signal Center Roadside Equipment Information Exchanges


Local Signal Center commands to spray chemicals*

Instructions to maintenance vehicle operators to spray chemicals on the roadway system.


Equipment

Existing

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


Equipment

Planned

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


Equipment

Planned

Local Signal Center ice levels on bridge request*

Request for reports describing ice conditions on the bridge. Local Signal Center_Roadside

Equipment

Existing

73


Local Signal Center roadway information system data





Equipment

Existing

Local Signal Center sensor and surveillance control



Equipment

Existing

Local Signal Center signal control data Information used to configure and control traffic signal systems. Local Signal Center_Roadside

Equipment

Existing


Equipment




Equipment

flood warning alert* Issues an alert to MnDOT regarding high water levels. Local Signal Center Existing


Equipment


condition.



Equipment

ice levels on bridge* Reports describing ice conditions on the bridge. Local Signal Center Existing


Equipment

intersection blockage notification

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



Equipment

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.



Equipment





Equipment

signal control status Status of surface street signal controls. Local Signal Center Existing


Equipment


density measures).



Equipment


applications.


Table B5. Demand Responsive Transit Center Information Exchanges



demand responsive transit plan

Plan regarding overall demand responsive transit schedules and deployment.


Planned


driver instructions Transit service instructions for both transit and paratransit drivers. Demand Responsive Transit Vehicle

Existing


payment request Request for payment from financial institution. Account Management

Providers

Planned

74



transit and fare schedules Specific transit and fare schedule information including schedule adherence.


Planned


transit emergency data Initial notification of transit emergency at a transit stop or on transit vehicles and further coordination as additional details

become available and the response is coordinated.


Management Center

Planned





Planned


transit incident information

Information on transit incidents that impact transit services for public dissemination.


Planned





Existing





Planned


transit request confirmation

Confirmation of a request for transit information or service. Metro Transit Management Center

Planned


TRMS coord Coordination information between local/regional transit organizations including schedule, on-time information and

ridership.


Planned



ridership.


Planned

Demand Responsive Transit Vehicle


Data collected on board the transit vehicle pertaining to availability and/or passenger count.


Existing


demand responsive transit request

Request for paratransit support. Demand Responsive Transit Center

Existing


transit emergency coordination data

Data exchanged between centers dealing with a transit-related incident.


Existing



Request for transit operations information including schedule and fare information. The request can be a subscription that initiates as-needed information updates as well as a one-time request for

information.


Existing



ridership.


Existing

Table B6. Demand Responsive Transit Vehicle Information Exchanges



driver instructions Transit service instructions for both transit and paratransit drivers. Demand Responsive Transit Vehicle

Existing

Demand Responsive Transit Vehicle




Existing

75

Table B7. Division of Emergency Management Center Information Exchanges






Management Center

Planned


Management Center




Existing


Management Center

incident response coordination

Incident response procedures, resource coordination, and current incident response status that are shared between allied response agencies to support a coordinated response to incidents. This

flow also coordinates a positive hand off of responsibility for all or part of an incident response between agencies.


Existing


Management Center





Planned


Management Center




Maintenance Dispatch Center

Planned


Management Center




Metro TMC Planned


Management Center





Planned


Management Center





Planned


Management Center




State Patrol Dispatch Centers

Existing


Management Center




TOCC Planned


Management Center





Management Center



Metro TMC Planned


Management Center




Planned

Division of incident response status Status of the current incident response including traffic Regional Traffic Planned

76

SourceElement FlowName FlowDescription DestinationElement FlowStatus Emergency

Management Center management strategies implemented at the site (e.g., closures,

diversions, traffic signal control overrides). Management Center


Management Center




Existing


Management Center



TOCC Planned


Management Center

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


Existing


incident report Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate

incident response.


Management Center

Existing






Management Center

Existing



incident response.


Management Center

Existing






Management Center

Existing



Management Center

Planned




Management Center

Planned



incident response.


Management Center

Planned






Management Center

Planned



Management Center

Planned

Metro TMC incident report Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate

incident response.


Management Center

Planned

Metro TMC incident response coordination




Management Center

Planned




Management Center

Planned




Existing

77

SourceElement FlowName FlowDescription DestinationElement FlowStatus precipitation, visibility, light conditions, etc.). Management Center




Management Center

Planned



incident response.


Management Center

Planned






Management Center

Planned




Management Center

Existing



incident response.


Management Center

Existing






Management Center

Existing


resource deployment status

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

status.


Management Center

Existing



Management Center

Planned

TOCC incident report Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate

incident response.


Management Center

Planned

TOCC incident response coordination




Management Center

Planned

Table B8. Event Promoters Information Exchanges


Event Promoters event plans Plans for major events possibly impacting traffic. Greater Minnesota State Patrol

Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Local Emergency Management Center

Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Local Signal Center Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Metro TMC Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Metro Traffic Engineering Center

Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Regional Traffic Management Center

Planned

Event Promoters event plans Plans for major events possibly impacting traffic. State Patrol Dispatch Centers

Existing

78


Event Promoters event plans Plans for major events possibly impacting traffic. TOCC Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Traveler Information Center

Existing


event confirmation Confirmation that special event details have been received and processed.

Event Promoters Planned




Metro TMC event confirmation Confirmation that special event details have been received and processed.











TOCC event confirmation Confirmation that special event details have been received and processed.


Table B9. National Weather Service Information Exchanges






Management Center

Existing





Existing





Planned









Existing





Existing




Metro TMC Existing





Existing





Planned





Existing

National Weather weather information Accumulated forecasted and current weather data (e.g., TOCC Existing

79

SourceElement FlowName FlowDescription DestinationElement FlowStatus Service temperature, pressure, wind speed, wind direction, humidity,






Existing





Table B10. Map Update Providers Information Exchanges



map updates Map update which could include a new underlying static or real-time map or map layer(s) update.


Planned


map update request Request for a map update which could include a new underlying map or map layer updates.


Planned

Table B11. Department of Motor Vehicles Information Exchanges


Department of Motor Vehicles

registration Registered owner of vehicle and associated vehicle information. Truck Center Existing

Truck Center license request Request supporting registration data based on license plate read during violation.


Planned

Table B12. Regional Traffic Management Center Information Exchanges






Planned



Request from the media for current transportation information. Regional Traffic Management Center

Planned

Data Center archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and

satisfy user data requests.


Planned

Data Center 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.


Planned

Data Center 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.


Planned


Management Center





Planned

Division of incident response status Status of the current incident response including traffic Regional Traffic Planned

80

SourceElement FlowName FlowDescription DestinationElement FlowStatus Emergency

Management Center management strategies implemented at the site (e.g., closures,

diversions, traffic signal control overrides). Management Center

Electrical Services Center

work zone status Status of maintenance work zone. Regional Traffic Management Center

Planned


Vehicle

incident status Information gathered at the incident site that more completely characterizes the incident and provides current incident response

status.


Planned

Event Promoters event plans Plans for major events possibly impacting traffic. Regional Traffic Management Center

Planned



Planned





Planned




Planned





Planned


emergency traffic control response



Planned




Planned


incident information request




Planned



incident response.


Planned






Planned





Planned


remote surveillance control




Planned




status.


Planned




Planned


traffic information Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw



Planned






Planned

Metro emissions data Emissions data and associated imagery collected by roadside Regional Traffic Planned

81

SourceElement FlowName FlowDescription DestinationElement FlowStatus TMC_Roadside

Equipment equipment. Management Center

Metro TMC_Roadside

Equipment

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


Planned

Metro TMC_Roadside

Equipment



Planned

Metro TMC_Roadside

Equipment

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.


Planned

Metro TMC_Roadside

Equipment

hov data Current HOV lane information including both standard traffic flow measures and information regarding vehicle occupancy in

HOV lanes.


Planned

Metro TMC_Roadside

Equipment


condition.


Planned

Metro TMC_Roadside

Equipment

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


Planned

Metro TMC_Roadside

Equipment

roadside archive data A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any

other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any

identified sensor faults.


Planned

Metro TMC_Roadside

Equipment




Planned

Metro TMC_Roadside

Equipment


density measures).


Planned

Metro TMC_Roadside

Equipment


applications.


Planned





Planned


archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned


closure coordination Coordination between subsystems regarding construction and maintenance closure times and durations.


Planned


current network conditions




Planned


emergency archive data Logged incident information that characterizes the identified incidents and provides a record of the corresponding incident

response. Content may include a catalog of available information, the actual information to be archived, and associated

meta data that describes the archived information.

Data Center Planned



Emergency vehicle dispatch instructions including incident location and available information concerning the incident.


Vehicle

Planned





Planned

82






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.

Metro TMC_Roadside

Equipment

Planned




Management Center

Planned







Planned




Planned



TOCC Planned




Planned





Planned






Planned






Planned





TOCC Planned



incident response.


Management Center

Planned



incident response.


Planned



incident response.


Planned



incident response.

TOCC Planned






Management Center

Planned






Planned





Planned

83

SourceElement FlowName FlowDescription DestinationElement FlowStatus flow also coordinates a positive hand off of responsibility for all

or part of an incident response between agencies.





Planned



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.


Planned










status.


Planned




Planned




Planned






Metro TMC_Roadside

Equipment

Planned




Metro TMC_Roadside

Equipment

Planned


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.

Data Center Planned


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


Planned





Planned











Planned





TOCC Planned






Planned


traveler archive data Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler

payment transaction data. Content may include a catalog of available information, the actual information to be archived, and

Data Center Planned

84

SourceElement FlowName FlowDescription DestinationElement FlowStatus associated meta data that describes the archived information.






Planned

Road Weather Information Center




Planned




Planned






Planned



incident response.


Planned






Planned





Planned




Planned



Planned

TOCC incident information request




Planned


incident response.


Planned






Planned

Table B13. Metro TMC Roadside Equipment Information Exchanges


Metro TMC freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and


Metro TMC_Roadside

Equipment

Existing

Metro TMC roadway information system data




Metro TMC_Roadside

Equipment

Existing

Metro TMC sensor and surveillance control


Metro TMC_Roadside

Equipment

Existing

85


Metro TMC_Roadside

Equipment

emissions data Emissions data and associated imagery collected by roadside equipment.


Planned

Metro TMC_Roadside

Equipment



Planned

Metro TMC_Roadside

Equipment


Metro TMC Existing

Metro TMC_Roadside

Equipment



Planned

Metro TMC_Roadside

Equipment


Metro TMC Existing

Metro TMC_Roadside

Equipment



Planned

Metro TMC_Roadside

Equipment


HOV lanes.

Metro TMC Existing

Metro TMC_Roadside

Equipment


HOV lanes.


Planned

Metro TMC_Roadside

Equipment


condition.


Planned

Metro TMC_Roadside

Equipment


Metro TMC Existing

Metro TMC_Roadside

Equipment



Planned

Metro TMC_Roadside

Equipment

roadside archive data A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any

other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any

identified sensor faults.


Planned

Metro TMC_Roadside

Equipment



Metro TMC Existing

Metro TMC_Roadside

Equipment




Planned

Metro TMC_Roadside

Equipment


density measures).

Metro TMC Existing

Metro TMC_Roadside

Equipment


density measures).


Planned

Metro TMC_Roadside

Equipment


applications.

Metro TMC Existing

Metro TMC_Roadside



Planned

86

SourceElement FlowName FlowDescription DestinationElement FlowStatus Equipment applications.


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


Metro TMC_Roadside

Equipment

Planned






Metro TMC_Roadside

Equipment

Planned




Metro TMC_Roadside

Equipment

Planned

Table B14. Metro TMC Information Exchanges





Metro TMC Existing



Request from the media for current transportation information. Metro TMC Existing



Metro TMC Planned




Metro TMC Planned



Metro TMC Planned


Management Center




Metro TMC Planned


Management Center



Metro TMC Planned


work zone status Status of maintenance work zone. Metro TMC Existing


Vehicle

emergency dispatch response

Request for additional emergency dispatch information (e.g., a suggested route) and provision of en-route status.

Metro TMC Existing


Vehicle

emergency vehicle tracking data

The current location and operating status of the emergency vehicle.

Metro TMC Planned


Vehicle

incident command request

Request for resources, commands for relay to other allied response agencies, and other requests that reflect local command

of an evolving incident response.

Metro TMC Existing

87



Vehicle


status.

Metro TMC Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Metro TMC Existing


System


Metro TMC Existing


System




Metro TMC Existing


System



Metro TMC Existing

Local Signal Center current network conditions



Metro TMC Planned


Metro TMC Planned




Metro TMC Planned



Metro TMC Planned



Metro TMC Existing





Metro TMC Existing



incident response.

Metro TMC Existing





Metro TMC Existing




Metro TMC Existing





Metro TMC Existing




status.

Metro TMC Existing



Metro TMC Existing




Metro TMC Existing

Maintenance traffic information Traffic information exchanged between TMC’s. Normally would Metro TMC Existing

88

SourceElement FlowName FlowDescription DestinationElement FlowStatus Dispatch Center coordination include incidents, congestion data, traffic data, signal timing


Metro TMC archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned

Metro TMC closure coordination Coordination between subsystems regarding construction and maintenance closure times and durations.


Existing

Metro TMC emergency archive data Logged incident information that characterizes the identified incidents and provides a record of the corresponding incident



Data Center Planned

Metro TMC event confirmation Confirmation that special event details have been received and processed.


Metro TMC freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and


Metro TMC_Roadside

Equipment

Existing



Management Center

Planned



System

Existing





Existing



Existing



Planned


TOCC Existing



Planned

Metro TMC incident information for media



Existing

Metro TMC incident information request




Existing





Planned




TOCC Existing


incident response.


Management Center

Planned


incident response.


Existing

Metro TMC incident report Report of an identified incident including incident location, type, State Patrol Dispatch Planned

89

SourceElement FlowName FlowDescription DestinationElement FlowStatus severity and other information necessary to initiate an appropriate

incident response. Centers


incident response.

TOCC Existing





Management Center

Planned





Existing





Planned







Existing




Existing




Planned

Metro TMC maintenance resource request




Existing






System

Existing











Existing

Metro TMC resource deployment status


status.


Existing

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


Existing



Planned

90




System

Existing





Planned

Metro TMC roadway information system data




Metro TMC_Roadside

Equipment

Existing

Metro TMC sensor and surveillance control


Metro TMC_Roadside

Equipment

Existing

Metro TMC 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


Data Center Planned

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


Existing

Metro TMC traffic information Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw



Planned









Existing





Existing

Metro TMC traffic information for media




Existing

Metro TMC traveler information for media




Existing

Metro TMC_Roadside

Equipment


Metro TMC Existing

Metro TMC_Roadside

Equipment


Metro TMC Existing

Metro TMC_Roadside

Equipment


HOV lanes.

Metro TMC Existing

Metro TMC_Roadside

Equipment


Metro TMC Existing

91


Metro TMC_Roadside

Equipment



Metro TMC Existing

Metro TMC_Roadside

Equipment


density measures).

Metro TMC Existing

Metro TMC_Roadside

Equipment


applications.

Metro TMC Existing



Metro TMC Existing





Metro TMC Existing




Metro TMC Existing





Metro TMC Existing




Metro TMC Existing




Metro TMC Existing



Metro TMC Planned





Metro TMC Planned



incident response.

Metro TMC Planned





Metro TMC Planned




Metro TMC Planned


Metro TMC Existing




Metro TMC Existing


incident response.

Metro TMC Existing





Metro TMC Planned

92

Table B15. Inter-jurisdictional Traffic Management System Information Exchanges



System


Metro TMC Existing


System




Metro TMC Existing


System








System







Existing


System



Metro TMC Existing



System

Existing






System

Existing



System

Existing








System

Existing

Table B16. State Patrol Dispatch Centers Information Exchanges



Roadside Equipment

speed violation* Detection of violation is sent to the emergency management subsystem for enforcement.


Planned


violation of HOV lane use*

Detection of violation of HOV lane use is sent to the emergency management subsystem for enforcement.


Planned

93

SourceElement FlowName FlowDescription DestinationElement FlowStatus Roadside Equipment


Management Center





Existing


Management Center




Existing


Management Center



Existing

Event Promoters event plans Plans for major events possibly impacting traffic. State Patrol Dispatch Centers

Existing




Existing



incident response.


Existing






Existing





Existing




Existing

Inter-Jurisdictional Emergency

Management System




Planned


Management System

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




Planned


Management System

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



Planned


Management System





Planned


Management System



Planned


Management System





Planned


Management System




Planned

94





Planned



incident response.


Planned






Planned





Planned



Planned





Planned


incident response.


Planned





Planned




Planned



Planned

Minnesota Emergency

Management Vehicle




Existing

Minnesota Emergency

Management Vehicle




Planned

Minnesota Emergency

Management Vehicle





Existing

Minnesota Emergency

Management Vehicle


status.


Existing





Existing


current network conditions




Planned





Planned

95





Planned






Planned



incident response.


Planned






Planned




Planned





Management System

Planned






Management System

Planned





Management System

Planned






Management System

Planned




Minnesota Emergency

Management Vehicle

Existing





incident command information

Information that supports local management of an incident. It includes resource deployment status, hazardous material

information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency personnel

in the field to implement an effective, safe incident response.

Minnesota Emergency

Management Vehicle

Existing




Management Center

Existing




Existing




Management System

Planned




Planned



Metro TMC Planned

96





Planned





Existing






Existing






Planned





Metro TMC Planned






Planned



incident response.


Management Center

Existing



incident response.


Existing



incident response.


Planned



incident response.

Metro TMC Planned



incident response.


Planned






Management Center

Existing






Existing






Management System

Planned






Planned





Metro TMC Planned

97







Planned




Metro TMC Planned





Planned




status.


Management Center

Existing




status.


Existing




Planned


suggested route Suggested route for a dispatched emergency vehicle that may reflect current network conditions and the additional routing options available to en-route emergency vehicles that are not

available to the general public.

Minnesota Emergency

Management Vehicle

Existing

Table B17. Minnesota Emergency Management Vehicle Information Exchanges





Minnesota Emergency

Management Vehicle

Existing






Minnesota Emergency

Management Vehicle

Existing




Minnesota Emergency

Management Vehicle

Existing

Minnesota Emergency

Management Vehicle




Existing

Minnesota Emergency

Management Vehicle




Existing

Minnesota Emergency

Management Vehicle




Planned

Minnesota Emergency

Management Vehicle




Planned

98


Minnesota Emergency

Management Vehicle





Existing

Minnesota Emergency

Management Vehicle





Existing

Minnesota Emergency

Management Vehicle


status.


Existing

Minnesota Emergency

Management Vehicle


status.


Existing




Minnesota Emergency

Management Vehicle

Existing






Minnesota Emergency

Management Vehicle

Existing




Minnesota Emergency

Management Vehicle

Existing

Table B18. Maintenance Dispatch Center Information Exchanges



Management Center





Planned


Vehicle




Existing


Vehicle




Planned


Vehicle


status.


Existing

Inter-Jurisdictional MnCARS





Existing







Existing

Maintenance emergency dispatch Emergency vehicle dispatch instructions including incident Emergency Existing

99

SourceElement FlowName FlowDescription DestinationElement FlowStatus Dispatch Center requests location and available information concerning the incident. Management

Vehicle




Maintenance Dispatch

Center_Vehicle

Existing





Planned







Center_Vehicle

Existing




Management Center

Planned




Existing



Metro TMC Existing




Planned



TOCC Planned





Metro TMC Existing






Planned





TOCC Planned



incident response.


Management Center

Planned



incident response.

Metro TMC Existing



incident response.


Planned



incident response.

TOCC Planned






Management Center

Planned





Metro TMC Existing

Maintenance incident response Incident response procedures, resource coordination, and current Regional Traffic Planned

100

SourceElement FlowName FlowDescription DestinationElement FlowStatus Dispatch Center coordination incident response status that are shared between allied response

agencies to support a coordinated response to incidents. This flow also coordinates a positive hand off of responsibility for all


Management Center





TOCC Planned




Metro TMC Existing





Planned




TOCC Planned





Metro TMC Existing






Planned





TOCC Planned




status.

Metro TMC Existing




status.


Planned




status.

TOCC Planned



Metro TMC Existing




Planned



TOCC Planned


snow plow instructions* Instructions to snow plow operators regarding which roads n Maintenance Dispatch

Center_Vehicle

Existing





Existing




Metro TMC Existing



data, processed data, or some combination of both may be


Planned

101

SourceElement FlowName FlowDescription DestinationElement FlowStatus provided by this architecture flow.




TOCC Planned





Metro TMC Existing






Planned





TOCC Planned


Center_Vehicle

snow plowing status* Information describing which roads have been plowed. Maintenance Dispatch Center

Existing



Existing





Existing


incident response.


Existing





Existing




Existing

Metro TMC resource deployment status


status.


Existing



Existing





Existing





Existing




Planned






Planned



incident response.


Planned





Planned

102

SourceElement FlowName FlowDescription DestinationElement FlowStatus flow also coordinates a positive hand off of responsibility for all






Planned




status.


Planned




Planned






Planned



Existing





Existing


incident response.


Existing





Existing

TOCC incident response status Status of the current incident response including traffic management strategies implemented at the site (e.g., closures,



Existing

TOCC resource deployment status


status.


Existing

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


Existing





Existing

Table B19. Electrical Services Center Information Exchanges



work zone status Status of maintenance work zone. Metro TMC Existing


work zone status Status of maintenance work zone. Metro Traffic Engineering Center

Existing


work zone status Status of maintenance work zone. Regional Traffic Management Center

Planned

Metro TMC closure coordination Coordination between subsystems regarding construction and maintenance closure times and durations.


Existing

Metro TMC maintenance resource request




Existing

Metro TMC traffic equipment status Identification of field equipment requiring repair and known Electrical Services Existing

103

SourceElement FlowName FlowDescription DestinationElement FlowStatus information about the associated faults. Center




Existing






Existing




Existing




Planned






Planned




Planned

Table B20. Maintenance Dispatch Center Vehicle Information Exchanges






Center_Vehicle

Existing







Center_Vehicle

Existing


snow plow instructions* Instructions to snow plow operators regarding which roads n Maintenance Dispatch

Center_Vehicle

Existing


Center_Vehicle

snow plowing status* Information describing which roads have been plowed. Maintenance Dispatch Center

Existing

Table B21. TOCC Information Exchanges





TOCC Existing



Request from the media for current transportation information. TOCC Existing



TOCC Planned




TOCC Planned

Data Center archive status Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided

TOCC Planned

104

SourceElement FlowName FlowDescription DestinationElement FlowStatus appears valid. If an error has been detected, the offending data



Management Center




TOCC Planned


Management Center



TOCC Planned

Event Promoters event plans Plans for major events possibly impacting traffic. TOCC Existing



TOCC Planned



incident response.

TOCC Planned





TOCC Planned




TOCC Planned





TOCC Existing


logged special vehicle route

Anticipated route information for special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor’s motorcade) that

may require changes in traffic control strategy.

TOCC Planned






TOCC Existing


TOCC Planned




TOCC Planned



TOCC Planned




TOCC Planned




performance.

TOCC Planned



TOCC Planned




TOCC Planned

105

SourceElement FlowName FlowDescription DestinationElement FlowStatus updates as well as a one-time request for information.



incident response.

TOCC Planned





TOCC Planned




TOCC Planned





TOCC Planned




status.

TOCC Planned



TOCC Planned




TOCC Planned





TOCC Planned


TOCC Existing




TOCC Existing


incident response.

TOCC Existing



TOCC Planned





TOCC Planned





TOCC Planned




performance.

TOCC Planned




TOCC Existing



TOCC Planned

106






TOCC Planned



incident response.

TOCC Planned





TOCC Planned




TOCC Planned

TOCC archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned

TOCC current network conditions




Planned

TOCC emergency archive data Logged incident information that characterizes the identified incidents and provides a record of the corresponding incident



Data Center Planned

TOCC event confirmation Confirmation that special event details have been received and processed.


TOCC freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and


TOCC_Roadside Equipment

Existing

TOCC gate command controls* Commands to control the gate system of I-90. TOCC_Roadside Equipment

Existing



Management Center

Planned



Planned



Existing





Existing


Metro TMC Existing



Planned



Planned



Existing

TOCC incident information for media



Existing

107






Planned





Existing




Metro TMC Existing





Planned





Planned


incident response.


Management Center

Planned


incident response.


Planned


incident response.


Existing


incident response.

Metro TMC Existing


incident response.


Planned





Management Center

Planned





Planned





Existing

TOCC incident response status Status of the current incident response including traffic management strategies implemented at the site (e.g., closures,



Existing

TOCC motorist criminal information*

This flow makes available criminal information regarding motorist for Minnesota State Police to utilize.


Existing




Existing

TOCC remote surveillance control




108


TOCC request for traffic information





TOCC request transit information

Request for transit service information and current transit status. Metro Transit Management Center

Planned

TOCC resource deployment status


status.


Existing

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


Existing

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


TOCC roadway information system data





Existing

TOCC sensor and surveillance control



Existing

TOCC signal control data Information used to configure and control traffic signal systems. TOCC_Roadside Equipment

Existing

TOCC 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


Data Center Planned

TOCC traffic information Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw



Existing




Existing









Existing

TOCC traffic information for media




Existing

TOCC traffic information for transit



Planned




Planned

TOCC transit information request


information.


Planned

109


TOCC traveler information for media




Existing


carbon monoxide levels* Reports describing carbon monoxide levels. TOCC Existing



TOCC Existing



TOCC Existing




TOCC Existing


signal control status Status of surface street signal controls. TOCC Existing



density measures).

TOCC Existing



applications.

TOCC Planned





TOCC Planned

Table B22. TOCC Roadside Equipment Information Exchanges


TOCC freeway control data Control commands and operating parameters for ramp meters, dynamic message signs, mainline metering/lane controls and



Existing

TOCC gate command controls* Commands to control the gate system of I-90. TOCC_Roadside Equipment

Existing

TOCC roadway information system data





Existing

TOCC sensor and surveillance control



Existing

TOCC signal control data Information used to configure and control traffic signal systems. TOCC_Roadside Equipment

Existing


carbon monoxide levels* Reports describing carbon monoxide levels. TOCC Existing



TOCC Existing



TOCC Existing



Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field

TOCC Existing

110

SourceElement FlowName FlowDescription DestinationElement FlowStatus equipment that provides dynamic information to the driver.


signal control status Status of surface street signal controls. TOCC Existing



density measures).

TOCC Existing



applications.

TOCC Planned

Table B23. Metro Transit Management Center Information Exchanges



demand responsive transit plan

Plan regarding overall demand responsive transit schedules and deployment.


Planned




Planned





Planned



Confirmation of a request for transit information or service. Metro Transit Management Center

Planned



ridership.


Planned


Management Center





Planned




Existing



incident response.


Existing




Planned



Planned





Planned

Local Signal Center traffic control priority status

Status of signal priority request functions at the roadside (e.g. enabled or disabled).


Planned




Planned

Local Signal Center traffic information for transit



Planned



ridership.


Planned

111



bad tag list List of invalid transit user tags which may have previously failed a fare payment transaction.

Metro Transit Management

Vehicles

Planned


broadcast information General broadcast information that contains link travel times, incidents, advisories, transit services and a myriad of other

traveler information.


Vehicles

Existing


demand responsive transit request

Request for paratransit support. Demand Responsive Transit Center

Existing


driver instructions Transit service instructions for both transit and paratransit drivers. Metro Transit Management

Vehicles

Existing


emergency acknowledge Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.


Vehicles

Existing


emergency data request A request for additional information or a control command issued by the emergency response agency in response to an emergency

request for assistance from a traveler.


Vehicles

Existing








fare management information

Transit fare information and transaction data used to manage transit fare processing on the transit vehicle.


Vehicles

Planned






TOCC Planned





Existing





TOCC Planned





TOCC Planned








request for vehicle measures

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


Vehicles

Planned


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



traffic control priority request

Request for signal priority at one or more intersections along a particular route.





Planned

112






Existing





Planned





Existing





Existing




information.


Existing



Confirmation of a request for transit information or service. Traveler Information Center

Planned


transit schedule information

Current and projected transit schedule adherence. Metro Transit Management

Vehicles

Planned




performance.





performance.

TOCC Planned




performance.


Planned






Existing



ridership.


Existing



ridership.


Planned


Vehicles

emergency notification An emergency request for assistance originated by a traveler using an in-vehicle, public access, or personal device. Sufficient

information is provided so that the recipient can determine the location of the emergency as a minimum. Additional information identifying the requestor and requesting device and the nature and severity of the emergency may also be provided (and required) by

some systems.


Existing


Vehicles

fare and payment status Current fare collection information including the operational status of the fare collection equipment and financial payment

transaction data.


Planned


Vehicles

request for bad tag list Request for list of bad vehicle tag IDs. Metro Transit Management Center

Planned

113



Vehicles

transit vehicle conditions Operating conditions of transit vehicle (e.g., mileage). Metro Transit Management Center

Planned


Vehicles

transit vehicle location data

Current transit vehicle location and related operational conditions data provided by a transit vehicle.


Planned


Vehicles




Existing


Vehicles


Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle.


Existing



Planned





Planned

TOCC request transit information


Planned




Planned

TOCC transit information request


information.


Planned






Planned


request fare and price information

Requests for current fare and price information from a service provider that can be used to augment the traffic manager's overall

view of current transportation network status.


Planned


request transit information


Planned

Table B24. Metro Transit Management Vehicles Information Exchanges





Vehicles

Planned


broadcast information General broadcast information that contains link travel times, incidents, advisories, transit services and a myriad of other

traveler information.


Vehicles

Existing


driver instructions Transit service instructions for both transit and paratransit drivers. Metro Transit Management

Vehicles

Existing




Vehicles

Existing





Vehicles

Existing

Metro Transit fare management Transit fare information and transaction data used to manage Metro Transit Planned

114

SourceElement FlowName FlowDescription DestinationElement FlowStatus Management Center information transit fare processing on the transit vehicle. Management

Vehicles


request for vehicle measures

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


Vehicles

Planned


transit schedule information

Current and projected transit schedule adherence. Metro Transit Management

Vehicles

Planned


Vehicles

emergency notification An emergency request for assistance originated by a traveler using an in-vehicle, public access, or personal device. Sufficient


some systems.


Existing


Vehicles


transaction data.


Planned


Vehicles

request for bad tag list Request for list of bad vehicle tag IDs. Metro Transit Management Center

Planned


Vehicles

transit vehicle conditions Operating conditions of transit vehicle (e.g., mileage). Metro Transit Management Center

Planned


Vehicles




Planned


Vehicles




Existing


Vehicles




Existing

Table B25. Road Weather Information Center Information Exchanges





Planned





Existing




Existing




Data Center Planned




RWIS_Roadside Equipment

Existing

Road Weather traffic information Current and forecasted traffic information, road and weather Metro TMC Existing

115

SourceElement FlowName FlowDescription DestinationElement FlowStatus Information Center conditions, incident information, and pricing data. Either raw






Planned




TOCC Planned





Existing




Existing

Table B26. RWIS Roadside Equipment Information Exchanges






Existing




Existing

Table B27. Truck Center Information Exchanges


Account Management

Providers

transaction status Response to transaction request. Normally dealing with a request for payment.



registration Registered owner of vehicle and associated vehicle information. Truck Center Existing





Truck Center license request Request supporting registration data based on license plate read during violation.


Planned

Truck Center payment request Request for payment from financial institution. Account Management

Providers

Existing

116

Table B28. Traveler Information Center Information Exchanges






Existing



Request from the media for current transportation information. Traveler Information Center

Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Traveler Information Center

Existing




Planned




Planned




Planned





Planned


map updates Map update which could include a new underlying static or real-time map or map layer(s) update.


Planned



Planned

Metro TMC traffic information Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw



Planned





Planned




Planned





Planned



Confirmation of a request for transit information or service. Traveler Information Center

Planned




performance.


Planned





Existing


parking availability Current parking lot occupancy, parking availability, and cost information.


Existing


parking information General parking information and current parking availability. Traveler Information Center

Existing




Planned

117






Planned





Existing



Existing




Existing





Metro TMC Planned






Planned






Planned





TOCC Planned


map update request Request for a map update which could include a new underlying map or map layer updates.


Planned


request fare and price information

Requests for current fare and price information from a service provider that can be used to augment the traffic manager's overall

view of current transportation network status.


Planned













Planned


request transit information


Planned






Planned


traveler information Traveler information comprised of traffic status, advisories, incidents, payment information and many other travel-related data

updates and confirmations.

Traveler Information Kiosk

Existing






Existing


traveler request Request by a traveler to summon assistance, request information, make a reservation, or initiate any other traveler service.


Existing

118

Table B29. Parking Management Center Information Exchanges


Local Signal Center parking instructions

Information that allows local parking facilities to be managed to support regional traffic management objectives.


Existing


parking availability

Current parking lot occupancy, parking availability, and cost information.


Existing


parking information

General parking information and current parking availability. Traveler Information Center

Existing


parking status Parking lot operational status. Parking Management_Roadside

Equipment

Existing


sensor and surveillance

control


Parking Management_Roadside

Equipment

Existing


Equipment

parking operator inputs

Local parking operator inputs that query current status and control the operation of the parking management system.


Existing

Table B30. Parking Management Roadside Equipment Information Exchanges



parking status Parking lot operational status. Parking Management_Roadside

Equipment

Existing



control



Equipment

Existing


Equipment

parking operator inputs

Local parking operator inputs that query current status and control the operation of the parking management system.


Existing

Table B31. Metro Traffic Engineering Center Information Exchanges



external reports

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



Existing


media information

request

Request from the media for current transportation information. Metro Traffic Engineering Center

Existing

Data Center archive coordination

Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and



Planned

Data Center 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




Planned




Planned

Division of Emergency incident Status of the current incident response including traffic Metro Traffic Planned

119

SourceElement FlowName FlowDescription DestinationElement FlowStatus Management Center response

status management strategies implemented at the site (e.g., closures,

diversions, traffic signal control overrides). Engineering Center


work zone status

Status of maintenance work zone. Metro Traffic Engineering Center

Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Metro Traffic Engineering Center

Existing


System







Existing


emergency traffic control

request





Planned



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


Existing


incident response

status

Status of the current incident response including traffic management strategies implemented at the site (e.g., closures,



Existing


resource request

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


Existing





Planned

Metro TMC incident information



Existing

Metro TMC incident response

status

Status of the current incident response including traffic management strategies implemented at the site (e.g., closures,



Existing

Metro TMC request for traffic

information





Existing

Metro TMC road network use

Aggregated route usage and associated travel data from clients for planning and analysis.


Planned





Existing


archive coordination

Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned


closure coordination

Coordination between subsystems regarding construction and maintenance closure times and durations.


Existing


event confirmation

Confirmation that special event details have been received and processed.





Division of Emergency Management Center

Planned

Metro Traffic incident Notification of existence of incident and expected severity, Local Emergency Existing

120

SourceElement FlowName FlowDescription DestinationElement FlowStatus Engineering Center information location, time and nature of incident. Management Center




Metro TMC Existing



request




Existing



request



Metro TMC Existing






Existing






Metro Traffic Engineering_Roadside

Equipment

Existing



control



Equipment

Existing


signal control data

Information used to configure and control traffic signal systems. Metro Traffic Engineering_Roadside

Equipment

Existing


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


Data Center Planned








System

Existing


traffic equipment

status

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


Existing


traffic information

Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw


Metro TMC Existing


traffic information

Current and forecasted traffic information, road and weather conditions, incident information, and pricing data. Either raw



Planned










Metro TMC Existing






Existing

121



Equipment



Existing


Equipment

roadway information

system status



Existing


Equipment


Status of surface street signal controls. Metro Traffic Engineering Center

Existing


Equipment


density measures).


Existing


Equipment


applications.


Planned


weather information

Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity,



Existing


request for traffic

information





Planned

Table B32. Metro Traffic Engineering Roadside Equipment Information Exchanges








Equipment

Existing



control



Equipment

Existing


signal control data

Information used to configure and control traffic signal systems. Metro Traffic Engineering_Roadside

Equipment

Existing


Equipment



Existing


Equipment

roadway information

system status



Existing


Equipment


Status of surface street signal controls. Metro Traffic Engineering Center

Existing


Equipment


density measures).


Existing


Equipment


applications.


Planned

122

Table B33. Emergency Management Vehicle Information Exchanges



Vehicle




Existing


Vehicle



Metro TMC Existing


Vehicle




Planned


Vehicle



Metro TMC Planned


Vehicle




Metro TMC Existing


Vehicle


status.


Existing


Vehicle


status.

Metro TMC Existing


Vehicle


status.


Planned





Vehicle

Existing





Vehicle

Planned

Table B34. Local Emergency Management Center Information Exchanges



Roadside Equipment

railroad gate crossing infringements*

Detection of railroad gate crossing infringements is sent to the emergency management subsystem for enforcement.


Planned


Roadside Equipment

red-light violation* Detection of red-light violation is sent to the emergency management subsystem for enforcement.


Planned





Planned


Management Center





Planned

Event Promoters event plans Plans for major events possibly impacting traffic. Local Emergency Management Center

Existing

123




incident response.


Existing






Existing


Management System





Planned



Mayday Vehicle Existing













Planned










Existing




Existing




Planned




Planned





Existing



incident response.


Management Center

Existing



incident response.


Existing



incident response.


Existing



incident response.


Planned

Local Emergency incident response Incident response procedures, resource coordination, and current Division of Existing

124

SourceElement FlowName FlowDescription DestinationElement FlowStatus Management Center coordination incident response status that are shared between allied response

agencies to support a coordinated response to incidents. This flow also coordinates a positive hand off of responsibility for all


Emergency Management Center






Existing






Management System

Planned






Planned









Existing





Planned




Existing





Planned




Existing



Existing





Existing





Planned




Existing






Existing





Planned




Planned






Planned

125




incident response.


Planned






Planned




Existing

Table B35. Inter-Jurisdictional MnCARS Information Exchanges






Planned




Planned






Existing





TOCC Existing


logged special vehicle route

Anticipated route information for special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor’s motorcade) that

may require changes in traffic control strategy.

TOCC Planned







Existing






TOCC Existing




Existing





Existing



Existing




Existing

126

Table B36. Local Transit Management Center Information Exchanges




ridership.


Planned





Planned



Local Transit Managment_Vehicles

Planned





Planned





Planned





Existing





Planned




performance.

TOCC Planned



ridership.


Planned

Local Transit Managment_Vehicle

s


transaction data.


Planned


s

request for bad tag list Request for list of bad vehicle tag IDs. Local Transit Management Center

Planned


s




Planned


s




Existing


s




Existing



ridership.


Planned





Existing




Planned

127

Table B37. Local Transit Management Vehicles Information Exchanges





Planned





Planned


fare and payment status

Current fare collection information including the operational status of the fare collection equipment and financial payment

transaction data.


Planned


request for bad tag list

Request for list of bad vehicle tag IDs. Local Transit Management Center

Planned





Planned


transit vehicle passenger and use

data



Existing


transit vehicle schedule

performance



Existing

Table B38. Traveler Information Kiosk Information Exchanges



traveler information Traveler information comprised of traffic status, advisories, incidents, payment information and many other travel-related data

updates and confirmations.


Existing


traveler request Request by a traveler to summon assistance, request information, make a reservation, or initiate any other traveler service.


Existing

Table B39. Greater Minnesota State Patrol Information Exchanges



Roadside Equipment



Planned


Roadside Equipment




Planned


Management Center





Existing

Event Promoters event plans Plans for major events possibly impacting traffic. Greater Minnesota State Patrol

Existing





Management System

Planned





Management System

Planned

128

SourceElement FlowName FlowDescription DestinationElement FlowStatus initiate a one-time response from the recipient.





Management System

Planned









Management System

Planned




Minnesota Emergency

Management Vehicle

Existing









Minnesota Emergency

Management Vehicle

Existing




Existing



TOCC Planned




Planned





Existing



incident response.


Management Center

Existing



incident response.


Existing



incident response.


Existing



incident response.

TOCC Planned






Management Center

Existing






Management System

Existing



Incident response procedures, resource coordination, and current incident response status that are shared between allied response


Existing

129

SourceElement FlowName FlowDescription DestinationElement FlowStatus agencies to support a coordinated response to incidents. This







Existing





TOCC Planned





Existing




TOCC Planned




Existing




Minnesota Emergency

Management Vehicle

Existing


Management System





Planned


Management System




Planned


Management System





Planned


Management System


incident response.


Planned


Management System





Planned



incident response.


Existing






Existing

Mayday Vehicle emergency notification An emergency request for assistance originated by a traveler using an in-vehicle, public access, or personal device. Sufficient

information is provided so that the recipient can determine the


Planned

130

SourceElement FlowName FlowDescription DestinationElement FlowStatus location of the emergency as a minimum. Additional information identifying the requestor and requesting device and the nature and severity of the emergency may also be provided (and required) by

some systems.

Minnesota Emergency

Management Vehicle




Existing

Minnesota Emergency

Management Vehicle




Planned

Minnesota Emergency

Management Vehicle





Existing

Minnesota Emergency

Management Vehicle


status.


Existing





Existing




Existing






Existing



incident response.


Existing






Existing




status.


Existing

TOCC current network conditions




Planned



Planned





Planned


incident response.


Planned





Planned




Existing

131

Table B40. DTN Information Exchanges


DTN weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity,



Table B41. Mayday Service Provider Information Exchanges


Mayday Service Provider









some systems.


Existing

Table B42. Mayday Vehicle Information Exchanges

















some systems.


Planned



some systems.


Existing

132

Table B43. Inter-Jurisdictional Emergency Management System Information Exchanges






Management System

Planned






Management System

Planned





Management System

Planned






Management System

Planned






Management System

Existing


Management System




Planned


Management System





Planned


Management System





Planned


Management System




Planned


Management System




Planned


Management System





Planned


Management System





Planned


Management System



Planned

133



Management System


incident response.


Planned


Management System





Planned


Management System





Planned


Management System





Planned


Management System




Planned






Management System

Planned





Management System

Planned






Management System

Planned





Management System

Planned






Management System

Planned




Management System

Planned






Management System

Planned

134

Table B44. In Vehicle Signing System Information Exchanges


In Vehicle Signing_Roadside

Equipment

driver information General advisory and traffic control information provided to the driver while en-route.

In Vehicle Signing System

Planned

Table B45. In Vehicle Signing Roadside Equipment Information Exchanges


In Vehicle Signing_Roadside

Equipment

driver information General advisory and traffic control information provided to the driver while en-route.

In Vehicle Signing System

Planned

Table B46. Data Center Information Exchanges




Metro TMC Planned




Planned




Planned




Planned



TOCC Planned





Planned




Metro TMC Planned





Planned





Planned


request can be a general subscription intended to initiate a


Existing

135

SourceElement FlowName FlowDescription DestinationElement FlowStatus continuous or regular data stream or a specific request intended to





TOCC Planned




Planned



Metro TMC Planned




Planned




Planned




Existing



TOCC Planned

Metro TMC archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned

Metro TMC emergency archive data Logged incident information that characterizes the identified incidents and provides a record of the corresponding incident



Data Center Planned

Metro TMC 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


Data Center Planned




Data Center Planned




Data Center Planned




Data Center Planned



response. Content may include a catalog of available

Data Center Planned

136

SourceElement FlowName FlowDescription DestinationElement FlowStatus information, the actual information to be archived, and associated





Data Center Planned


traveler archive data Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler

payment transaction data. Content may include a catalog of available information, the actual information to be archived, and

associated meta data that describes the archived information.

Data Center Planned




Data Center Planned

TOCC archive coordination Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and


Data Center Planned

TOCC emergency archive data Logged incident information that characterizes the identified incidents and provides a record of the corresponding incident



Data Center Planned

TOCC 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


Data Center Planned

Table B47. Compliance Management Roadside Equipment Information Exchanges



Roadside Equipment

railroad gate crossing infringements*

Detection of railroad gate crossing infringements is sent to the emergency management subsystem for enforcement.


Planned


Roadside Equipment

red-light violation* Detection of red-light violation is sent to the emergency management subsystem for enforcement.


Planned


Roadside Equipment



Planned


Roadside Equipment



Planned


Roadside Equipment




Planned


Roadside Equipment




Planned

Date post:	13-Apr-2022
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

Minnesota Statewide Architecture - MnDOT

Documents