Other Border Inspection Administration Centers --> Border Inspection Administration Center:
This triple is bi-directional. See also
Border Inspection Administration Center --> Other Border Inspection Administration Centers: inspection results
inspection results (Information Flow): Report of results of border inspection on a particular load.
Other Border Inspection Administration Centers (Source Physical Object): Representing another Border Inspection Administration Center, 'Other Border Inspection Administration Centers' is intended to provide a source and destination for information exchange between international border administration functions. It enables traffic management activities to be coordinated across international borders.
Border Inspection Administration Center (Destination Physical Object): 'Border Inspection 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 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 the border crossings. These systems support import/export cargo processing and enforcement operations at the border, including programs such as FAST, Automated Commercial Environment (ACE), Nexus (Canada), SENTRI (Mexico), and US-VISIT.
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Communication SolutionsNo communications solutions identified.
|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).|
|Information Flow Security|
|Basis||This information should be protected as much as possible, however the disclosure of this information will not have a significant impact on those involved.||This information could affect how the BIAC responds to a request on a person in the future. As such this information should be relatively secure; however mistakes in the information do not have a major impact on anything.||This information requires an acknowledgment of receipt, but if a message is missed it could be sent again at a later time without any impact on the rest of the system.|