Border Inspection System --> Traffic Management Center:
border incident information

Definitions

border incident information (Information Flow): Notification of existence of incident in the vicinity of the border. Information would include expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided.

Border Inspection System (Source Physical Object): 'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events.

Traffic Management Center (Destination 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.

Included In

This Triple is in the following Service Packages:

• TM08: Traffic Incident Management System

This triple is associated with the following Functional Objects:

• Border Inspection
• TMC Incident Detection
• TMC Incident Dispatch Coordination

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

• border_inspection_traffic_incident

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - Secure Internet (ITS) (43)
• (None-Data) - Apache Kafka (44)
• (None-Data) - OMG DDS (44)
• (None-Data) - OASIS MQTT (50)
• (None-Data) - OASIS AMQP (61)

Selected Solution

(None-Data) - OASIS AMQP

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities Development needed OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	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