Border and Port Administration Center --> Intermodal Terminal:
loading authorization
Definitions
loading authorization (Information Flow): Permission from the government for the goods to be loaded onto ship, secured safely, and made ready for transportation.
Border and Port Administration Center (Source Physical Object): 'Border and Port Administration Center' represents back-office systems and databases run by domestic and foreign governmental agencies responsible for the regulation of trade, and the enforcement of customs and immigration laws. These agencies include U.S. Department of Homeland Security (DHS) and its counterparts in Canada and Mexico. DHS includes components like Customs and Border Protection (CBP), Immigration and Customs Enforcement (ICE), and Transportation Security Administration (TSA). Other agencies include the Maritime Adiministration, Coast Guard, and Port Authorities for ports and secondary trade agencies (e.g., U.S. Food and Drug Administration, U.S. Department of Agriculture, other USDOT departments, etc.), and agencies from other trading nations. The systems they manage coordinate activities related to land border crossings and ports. These systems support import/export cargo processing and enforcement operations at the port of entry, including programs such as FAST, Automated Commercial Environment (ACE), Nexus (Canada), SENTRI (Mexico), and US-VISIT.
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:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
Port: Gov load - Secure Internet (ITS) (0)
-
Port: Gov load - OMG DDS (4)
-
Port: Gov load - Apache Kafka (4)
-
Port: Gov load - Eclipse Zenoh (5)
-
Port: Gov load - OASIS MQTT (10)
-
Port: Gov load - OASIS AMQP (21)
-
(None-Data) - Secure Internet (ITS) (43)
-
(None-Data) - OMG DDS (44)
-
(None-Data) - Apache Kafka (44)
-
(None-Data) - Eclipse Zenoh (45)
-
(None-Data) - OASIS MQTT (50)
-
(None-Data) - OASIS AMQP (61)
Selected Solution
Port: Gov load - OASIS MQTTSolution Description
|
ITS Application Entity
USDA PGA MS ![]() APHIS CORE ACE PGA Guide ![]() APHIS Supplemental ![]() |
Click gap icons for more info.
|
||
|
Mgmt
OASIS MQTT DMP ![]() |
Facilities
![]()
OASIS MQTT ![]() |
Security
![]()
|
|
|
TransNet
|
|||
|
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
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| 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 | Any information related to clearance, border control, cargo impoundment, release or related customs information should be protected from casual observation, as this information could be used against affected parties causing financial or legal harm. | Any information related to clearance, border control, cargo impoundment, release or related customs information needs to be correct and timely so as to not negatively impact the movement of goods, which could cause financial or legal harm. | Any information related to clearance, border control, cargo impoundment, release or related customs information needs to be correct and timely so as to not negatively impact the movement of goods, which could cause financial or legal harm. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |

