Traffic Management Center --> Intermodal Terminal:
intermodal freight traffic information

Definitions

intermodal freight traffic information (Information Flow): Information on traffic conditions affecting the depot including information concerning any special traffic control accommodations or restrictions for commercial vehicles.

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.

Intermodal Terminal (Destination Physical Object): The 'Intermodal Terminal' represents the terminal areas corresponding to modal change points. This includes interfaces between roadway freight transportation and air, rail, and/or water shipping modes. The basic unit of cargo handled by the Intermodal Terminal physical object is the container; less-than-container load handling is typically handled at a different facility (i.e., Freight Consolidation Station). The Intermodal Terminal can include electronic gate control for entrance and exit from the facility, automated guidance of vehicles within the facility, alerting appropriate parties of container arrivals and departures, and inventory and location of temporarily stored containers.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

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

This Triple has the following triple relationships:

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Apache Kafka

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for Apache Kafka. The (None-Data) standards include an unspecified set of standards at the upper layers. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity
Mind the gapMind the gap

Development needed
Click gap icons for more info.

Mgmt

Apache Zookeeper
Facilities
Mind the gapMind the gapMind the gap

Development needed
Apache Kafka
Apache Zookeeper
Security

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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

Characteristic Value
Time Context Recent
Spatial Context Regional
Acknowledgement True
Cardinality Unicast
Initiator Destination
Authenticable True
Encrypt True


Interoperability Description
Regional Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Moderate Moderate Moderate
Basis While this likely does not contain any private or competitive data, it may contain a large bundle of freight movement information, that if observed by a hostile third party, would provide a snapshot that enabled that attacker to identify targets without needing to be physically present. CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact.


Security Characteristics Value
Authenticable True
Encrypt True