Traffic Management Center --> Transportation Information Center:
incident information for public

Definitions

incident information for public (Information Flow): Report of current desensitized incident information prepared for public dissemination.

Traffic Management Center (Source Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Included In

This Triple is in the following Service Packages:

• CVO09: Freight-Specific Dynamic Travel Planning
• PS08: Roadway Service Patrols
• PS14: Disaster Traveler Information
• TI01: Broadcast Traveler Information
• TI02: Personalized Traveler Information
• TI03: En-Route Guidance
• TI04: Trip Planning and Payment
• TM08: Traffic Incident Management System

This triple is associated with the following Functional Objects:

• TIC Data Collection
• TMC Incident Dispatch Coordination
• TMC Service Patrol Management

This Triple is described by the following Functional View Data Flows:

• planned_events
• traffic_incident_data

This Triple has the following triple relationships:

Communication Solutions

• EU: DATEX - DATEX Messaging (3)
• US: TMDD - NTCIP Messaging (13)
• (None-Data) - Secure Internet (ITS) (32)
• Data for Distribution (TBD) - Apache Kafka (36)
• Data for Distribution (TBD) - OMG DDS (36)
• (None-Data) - OASIS MQTT (42)
• Data for Distribution (TBD) - OASIS MQTT (42)
• Data for Distribution (TBD) - OASIS AMQP (45)

Selected Solution

EU: DATEX - DATEX Messaging

Solution Description

ITS Application Entity Bundle: DATEX			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB W3C WSDL 1.1	Facilities No Standard Needed	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security