< < CF21.1 : CF22.1 : CF23.1 > >
CF22.1: International Border Coordination Implementation
This service package covers coordination and sharing of information between agencies to support expedited clearance, customs pre-processing, and border crossing inspections. This implementation is a holistic view of the CF22 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.
Origin:
Canada
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Border and Port Administration Center Maintainer | Border and Port Administration Center | Maintains |
| Border and Port Administration Center Manager | Border and Port Administration Center | Manages |
| Border and Port Administration Center Manager | Border Inspection Administration Center Operator | System Usage Agreement |
| Border and Port Administration Center Owner | Border and Port Administration Center Maintainer | System Maintenance Agreement |
| Border and Port Administration Center Owner | Border and Port Administration Center Manager | Operations Agreement |
| Border and Port Administration Center Owner | Border Inspection System Maintainer | Maintenance Data Exchange Agreement |
| Border and Port Administration Center Owner | Border Inspection System Operator | Application Usage Agreement |
| Border and Port Administration Center Owner | Border Inspection System Owner | Information Exchange Agreement |
| Border and Port Administration Center Owner | Border Inspection System User | Service Usage Agreement |
| Border and Port Administration Center Owner | Other Border and Port Administration Centers Maintainer | Maintenance Data Exchange Agreement |
| Border and Port Administration Center Owner | Other Border and Port Administration Centers Owner | Information Exchange Agreement |
| Border and Port Administration Center Owner | Other Border and Port Administration Centers User | Service Usage Agreement |
| Border and Port Administration Center Owner | Other Border Inspection Administration Center Operator | Application Usage Agreement |
| Border and Port Administration Center Supplier | Border and Port Administration Center Owner | Warranty |
| Border Inspection Administration Center Operator | Border and Port Administration Center | Operates |
| Border Inspection System Maintainer | Border Inspection System | Maintains |
| Border Inspection System Manager | Border Inspection System | Manages |
| Border Inspection System Manager | Border Inspection System Operator | System Usage Agreement |
| Border Inspection System Operator | Border Inspection System | Operates |
| Border Inspection System Owner | Border and Port Administration Center Maintainer | Maintenance Data Exchange Agreement |
| Border Inspection System Owner | Border and Port Administration Center Owner | Information Exchange Agreement |
| Border Inspection System Owner | Border and Port Administration Center User | Service Usage Agreement |
| Border Inspection System Owner | Border Inspection Administration Center Operator | Application Usage Agreement |
| Border Inspection System Owner | Border Inspection System Maintainer | System Maintenance Agreement |
| Border Inspection System Owner | Border Inspection System Manager | Operations Agreement |
| Border Inspection System Owner | Other Border Inspection System Operator | Application Usage Agreement |
| Border Inspection System Owner | Other Border Inspection Systems Maintainer | Maintenance Data Exchange Agreement |
| Border Inspection System Owner | Other Border Inspection Systems Owner | Information Exchange and Action Agreement |
| Border Inspection System Owner | Other Border Inspection Systems User | Service Usage Agreement |
| Border Inspection System Supplier | Border Inspection System Owner | Warranty |
| Other Border and Port Administration Centers Maintainer | Other Border and Port Administration Centers | Maintains |
| Other Border and Port Administration Centers Manager | Other Border and Port Administration Centers | Manages |
| Other Border and Port Administration Centers Manager | Other Border Inspection Administration Center Operator | System Usage Agreement |
| Other Border and Port Administration Centers Owner | Border and Port Administration Center Maintainer | Maintenance Data Exchange Agreement |
| Other Border and Port Administration Centers Owner | Border and Port Administration Center Owner | Information Exchange Agreement |
| Other Border and Port Administration Centers Owner | Border and Port Administration Center User | Service Usage Agreement |
| Other Border and Port Administration Centers Owner | Border Inspection Administration Center Operator | Application Usage Agreement |
| Other Border and Port Administration Centers Owner | Other Border and Port Administration Centers Maintainer | System Maintenance Agreement |
| Other Border and Port Administration Centers Owner | Other Border and Port Administration Centers Manager | Operations Agreement |
| Other Border and Port Administration Centers Supplier | Other Border and Port Administration Centers Owner | Warranty |
| Other Border Inspection Administration Center Operator | Other Border and Port Administration Centers | Operates |
| Other Border Inspection System Operator | Other Border Inspection Systems | Operates |
| Other Border Inspection Systems Maintainer | Other Border Inspection Systems | Maintains |
| Other Border Inspection Systems Manager | Other Border Inspection System Operator | System Usage Agreement |
| Other Border Inspection Systems Manager | Other Border Inspection Systems | Manages |
| Other Border Inspection Systems Owner | Border Inspection System Maintainer | Maintenance Data Exchange Agreement |
| Other Border Inspection Systems Owner | Border Inspection System Operator | Application Usage Agreement |
| Other Border Inspection Systems Owner | Border Inspection System Owner | Information Exchange and Action Agreement |
| Other Border Inspection Systems Owner | Border Inspection System User | Service Usage Agreement |
| Other Border Inspection Systems Owner | Other Border Inspection Systems Maintainer | System Maintenance Agreement |
| Other Border Inspection Systems Owner | Other Border Inspection Systems Manager | Operations Agreement |
| Other Border Inspection Systems Supplier | Other Border Inspection Systems Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Border and Port Administration Center | Center | '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 Administration, 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. |
| Border Inspection System | Field | '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. |
| Other Border and Port Administration Centers | Center | Representing another Border and Port Administration Center, 'Other Border and Port Administration Centers' is intended to provide a source and destination for information exchange between international border and port administration functions. It enables transportation management activities to be coordinated across international borders. |
| Other Border Inspection Systems | Field | Representing another set of Border Inspection Systems, 'Other Border Inspection Systems' is intended to provide a source and destination for information exchange between international border inspection functions. It enables traffic management activities to be coordinated across international borders.. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Border Inspection | 'Border Inspection' manages and supports primary and secondary inspections at the border crossing. | Border Inspection System |
| Border Inspection Administration | 'Border Inspection Administration' performs administrative functions relating to the inspection of goods and vehicles at the border. | Border and Port Administration Center |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| border field equipment data | Data such as camera images and radiation sensor data. |
| consolidated agency response | Electronic manifest data as well as commercial vehicle screening results. |
| expedited clearance information | Includes carrier ID, importer ID, broker ID, conveyance ID, driver ID, service options, and associated information that is used to support expedited border clearance. |
| inspection results | Report of results of border inspection on a particular load. |
| refusal of entry information | Information on loads, vehicles, or drivers who have been refused entry to the country. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; | Improve freight network |
Associated Objective Categories 
| Objective Category |
|---|
| Freight Management: Border Crossing |
Associated Objectives and Performance Measures 
Needs and Requirements
| Need | Functional Object | Requirement | ||
|---|---|---|---|---|
| 01 | Border Administration needs to exchange data with other Border Administrations in order to support international coordination for expedited border clearance programs, including credentials, applications, supporting information, and registration details. | Border Inspection Administration | 12 | The center shall provide other Border Administrations with expedited border clearance program data, including application and registration information. |
| 13 | The center shall provide other Border Administrations with credentials and inspection result information to support their inspections. | |||
| 14 | The center shall provide other Border Administrations with surveillance data to support their inspections. | |||
| 02 | Border Inspection Operations need to exchange data with other Border Inspection Operations in order to support coordination across international borders, including, inspection results, and surveillance data. | Border Inspection | 06 | The border field equipment shall provide surveillance data to other Border Inspection systems. |
Related Sources
| Document Name | Version | Publication Date |
|---|---|---|
| None |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Border and Port Administration Center | High | High | Moderate | Class 4 |
| Border Inspection System | High | High | Moderate | Class 4 |
| Other Border and Port Administration Centers | Moderate | Moderate | Moderate | Class 2 |
| Other Border Inspection Systems | Moderate | High | Moderate | Class 3 |
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Border and Port Administration Center | Border Inspection System | consolidated agency response | High | High | Moderate |
| This contains the full manifest of the cargo container, as well as the results of the vehicle screening. This data can be highly sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | This response directly determines whether or not the vehicle is cleared to cross the border. An incorrect message could lead to a vehicle which should not be allowed to cross the border ending up across the border. | The system must have an acknowledgement of a missed message. If a message is not received, it may lead to extra searches, as vehicles could not be automatically cleared. | |||
| Border and Port Administration Center | Other Border and Port Administration Centers | expedited clearance information | Moderate | Moderate | Moderate |
| Contains PII to support the application. | Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention. | Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention. | |||
| Border and Port Administration Center | Other Border and Port Administration Centers | inspection results | Moderate | Moderate | Low |
| 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. | |||
| Border Inspection System | Border and Port Administration Center | inspection results | Moderate | Moderate | Low |
| 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. | |||
| Border Inspection System | Other Border Inspection Systems | border field equipment data | Moderate | Moderate | Moderate |
| Could be used as remote monitoring feed for the border, and so should be obfuscated to prevent unauthorized remote viewing of border circumstances. Also, some of the data reported here may not be casually observable. | Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing. | Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing. | |||
| Border Inspection System | Other Border Inspection Systems | refusal of entry information | Moderate | High | Moderate |
| Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | Corruption, unavailability or unauthorized manipulation of this data could an error in border administration. | Corruption, unavailability or unauthorized manipulation of this data could an error in border administration. | |||
| Other Border and Port Administration Centers | Border and Port Administration Center | expedited clearance information | Moderate | Moderate | Moderate |
| Contains PII to support the application. | Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention. | Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention. | |||
| Other Border and Port Administration Centers | Border and Port Administration Center | inspection results | Moderate | Moderate | Low |
| 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. | |||
| Other Border Inspection Systems | Border Inspection System | border field equipment data | Moderate | Moderate | Moderate |
| Could be used as remote monitoring feed for the border, and so should be obfuscated to prevent unauthorized remote viewing of border circumstances. Also, some of the data reported here may not be casually observable. | Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing. | Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing. | |||
| Other Border Inspection Systems | Border Inspection System | refusal of entry information | Moderate | High | Moderate |
| Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | Corruption, unavailability or unauthorized manipulation of this data could an error in border administration. | Corruption, unavailability or unauthorized manipulation of this data could an error in border administration. | |||
Standards
The diagram here shows the primary standards associated with the physical objects and information flows in this service package. Click on the standard # to go to the page explaining that standard in more detail. The tables that follow the diagram list the standards associated with the information flows in this service package that should drive development decisions. Click on the standard name for more information from the Communications View about a particular standard, including the solutions and information flow triples associated with the standard and any gaps or overlaps. This table is based primarily on standards used in North America. For information concerning standards and communications solutions in other regions consult the Communications View.
This material should be considered 'draft for review' and may change separately from ARC-IT version revisions. The date on the diagram relates to the date of the physical service package diagram on which this is based; standards-related information should be considered up-to-date as of the 'last updated' date on this page.
Communication Standards: Standards associated with data, message or dialog definitions, communications protocols and management and security of data exchanges. All standards here are also illustrated in information flow triple communications view diagrams.
| Name | Title |
|---|---|
| Security Entity | |
| Secure Session Alternatives | Secure Session Alternatives |
| Management Entity | |
| Bundle: SNMPv3 MIB | SNMPv3 & Networking MIBs |
| Networking and Transport Layer | |
| Internet Transport Alternatives | Internet Transport Alternatives |
| IP Alternatives | Internet Protocol Alternative Set |
| Access Layer | |
| Internet Subnet Alternatives | Internet Subnet Alternatives |
Physical Standards: Standards associated with device physical, environmental or performance requirements.
No physical standards have been identified for this service package.
Service-Level Standards: Standards associated service package structure, messaging patterns, user needs, requirements or similar systems-engineering content that describe one or more use cases satisfied by the service package.
No service-level standards have been identified for this service package.
System Requirements
| No System Requirements |