Border Inspection Administration (Terminator*)

This terminator represents back-office systems and databases run by U.S. 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. Data is collected and disseminated to other government systems and users. 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.

Inputs/Outputs
Interfaces Diagram

Terminator Interfaces Diagram

This is a context diagram for the entity Border Inspection Administration Terminator that shows every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Inputs/Outputs: Architecture Flows* and Data Flows*

Archived Data Management Border Inspection Administration

archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*:
- tbia-archive_request
archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
- tbia-border_archive_status

Border Inspection Administration Archived Data Management

border information archive data (Architecture Flow*) - Border inspection activities data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
- fbia-border_archive_data

Border Inspection Administration Commercial Vehicle Administration

client verification request (Architecture Flow*) - Request for information such as commercial drivers license information and carrier safety status.
Data Flows*:
- fbia-border_client_request
pre-arrival notification (Architecture Flow*) - Identification of a vehicle or driver that is approaching a border crossing.
Data Flows*:
- fbia-border_prearrival_notice

Border Inspection Administration Fleet and Freight Management

clearance notification (Architecture Flow*) - Notification that cargo has been cleared through customs.
Data Flows*:
- fbia-fleet_border_clearance_status
client id (Architecture Flow*) - A common identification number that can be used by all BIFA agencies and organizations to reference the carrier.
Data Flows*:
- fbia-fleet_client_identification
expedited clearance information (Architecture Flow*) - Includes carrier ID, importer ID, broker ID, conveyance ID, driver ID, service options, and associated information that is used to support expedited border clearance.
Data Flows*:
- fbia-fleet_expedited_clearance_response
expedited clearance status (Architecture Flow*) - Status of expedited clearance registration.
Data Flows*:
- fbia-fleet_expedited_clearance_status
manifest receipt confirmation (Architecture Flow*) - Confirmation that a shippers manifest has been received.
Data Flows*:
- fbia-fleet_manifest_receipt

Commercial Vehicle Administration Border Inspection Administration

border clearance status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
Data Flows*:
- tbia-border_clearance_status
client verification information (Architecture Flow*) - Information about carriers who have made border credential applications such as commercial drivers license information and carrier safety status.
Data Flows*:
- tbia-border_client_information
screening results (Architecture Flow*) - Results of commercial vehicle screening event at a border crossing - reports clearance event data regarding action taken at border, including acceptance or override of system decision, and date/time stamp.
Data Flows*:
- tbia-border_screening_results

Fleet and Freight Management Border Inspection Administration

expedited clearance registration (Architecture Flow*) - Registration of the importer, carrier, conveyance, and driver, as applicable, for border clearance programs such as FAST, Customs Self Assessment (Canada), C-TPAT (US), PIP (Canada), ACI (Canada), and ACE (US). Includes electronic filing of forms and associated payment.
Data Flows*:
- tbia-fleet_expedited_clearance_request
manifest data (Architecture Flow*) - Identifies Port of Entry, date, and information on carrier and goods, origin, etc.
Data Flows*:
- tbia-fleet_manifest_data