CVO22: International Border Coordination
This service package covers coordination and sharing of information between agencies to support expedited clearance, customs pre-processing, and border crossing inspections.
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
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Border Inspection Administration Center Developer | Border Inspection Administration Center | Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role. |
Border Inspection Administration Center Developer | Border Inspection System Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Border Inspection Administration Center Developer | Other Border Inspection Administration Centers Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Border Inspection System Developer | Border Inspection Administration Center Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Border Inspection System Developer | Border Inspection System | Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role. |
Border Inspection System Developer | Other Border Inspection Systems Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Other Border Inspection Administration Centers Developer | Border Inspection Administration Center Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Other Border Inspection Administration Centers Developer | Other Border Inspection Administration Centers | Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role. |
Other Border Inspection Systems Developer | Border Inspection System Developer | Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Other Border Inspection Systems Developer | Other Border Inspection Systems | Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role. |
Installation Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Border Inspection Administration Center Installer | Border Inspection Administration Center | Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation. |
Border Inspection Administration Center Owner | Border Inspection Administration Center Installer | Installation Agreement |
Border Inspection Administration Center Owner | Border Inspection Administration Center Verifier | Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design. |
Border Inspection System Installer | Border Inspection System | Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation. |
Border Inspection System Owner | Border Inspection System Installer | Installation Agreement |
Border Inspection System Owner | Border Inspection System Verifier | Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design. |
Other Border Inspection Administration Centers Installer | Other Border Inspection Administration Centers | Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation. |
Other Border Inspection Administration Centers Owner | Other Border Inspection Administration Centers Installer | Installation Agreement |
Other Border Inspection Administration Centers Owner | Other Border Inspection Administration Centers Verifier | Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design. |
Other Border Inspection Systems Installer | Other Border Inspection Systems | Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation. |
Other Border Inspection Systems Owner | Other Border Inspection Systems Installer | Installation Agreement |
Other Border Inspection Systems Owner | Other Border Inspection Systems Verifier | Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design. |
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Border Inspection Administration Center Maintainer | Border Inspection Administration Center | Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state. |
Border Inspection Administration Center Manager | Border Inspection Administration Center | Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context. |
Border Inspection Administration Center Owner | Border Inspection Administration Center Maintainer | System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system. |
Border Inspection Administration Center Owner | Border Inspection Administration Center Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Border Inspection Administration Center Owner | Border Inspection System Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Border Inspection Administration Center Owner | Border Inspection System Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Border Inspection Administration Center Owner | Border Inspection System User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Border Inspection Administration Center Owner | Other Border Inspection Administration Centers Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Border Inspection Administration Center Owner | Other Border Inspection Administration Centers Owner | Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. |
Border Inspection Administration Center Owner | Other Border Inspection Administration Centers User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Border Inspection Administration Center Supplier | Border Inspection Administration Center Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Border Inspection System Maintainer | Border Inspection System | Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state. |
Border Inspection System Manager | Border Inspection System | Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context. |
Border Inspection System Owner | Border Inspection Administration Center Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Border Inspection System Owner | Border Inspection Administration Center Owner | Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
Border Inspection System Owner | Border Inspection Administration Center User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Border Inspection System Owner | Border Inspection System Maintainer | System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system. |
Border Inspection System Owner | Border Inspection System Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Border Inspection System Owner | Other Border Inspection Systems Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Border Inspection System Owner | Other Border Inspection Systems Owner | Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
Border Inspection System Owner | Other Border Inspection Systems User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Border Inspection System Supplier | Border Inspection System Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Other Border Inspection Administration Centers Maintainer | Other Border Inspection Administration Centers | Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state. |
Other Border Inspection Administration Centers Manager | Other Border Inspection Administration Centers | Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context. |
Other Border Inspection Administration Centers Owner | Border Inspection Administration Center Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Other Border Inspection Administration Centers Owner | Border Inspection Administration Center Owner | Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. |
Other Border Inspection Administration Centers Owner | Border Inspection Administration Center User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Other Border Inspection Administration Centers Owner | Other Border Inspection Administration Centers Maintainer | System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system. |
Other Border Inspection Administration Centers Owner | Other Border Inspection Administration Centers Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Other Border Inspection Administration Centers Supplier | Other Border Inspection Administration Centers Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Other Border Inspection Systems Maintainer | Other Border Inspection Systems | Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state. |
Other Border Inspection Systems Manager | Other Border Inspection Systems | Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context. |
Other Border Inspection Systems Owner | Border Inspection System Maintainer | Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Other Border Inspection Systems Owner | Border Inspection System Owner | Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
Other Border Inspection Systems Owner | Border Inspection System User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Other Border Inspection Systems Owner | Other Border Inspection Systems Maintainer | System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system. |
Other Border Inspection Systems Owner | Other Border Inspection Systems Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Other Border Inspection Systems Supplier | Other Border Inspection Systems Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
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 Inspection Administration Center | Center | '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. |
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 Inspection Administration Centers | Center | 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. |
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 Inspection 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 

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.
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 |
---|---|---|
ITS User Services Document | 1/1/2005 | |
ITS Architecture for Canada - Version 3 |
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 Inspection Administration Center | High | High | Moderate | Class 4 |
Border Inspection System | High | High | Moderate | Class 4 |
Other Border Inspection 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 Inspection 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 Inspection Administration Center | Other Border Inspection 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 Inspection Administration Center | Other Border Inspection 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 Inspection 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 Inspection Administration Centers | Border Inspection 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 Inspection Administration Centers | Border Inspection 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
Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall provide other Border Administrations with expedited border clearance program data, including application and registration information. | 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. |
002 | The system shall provide other Border Administrations with credentials and inspection result information to support their inspections. | 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. |
003 | The system shall provide other Border Administrations with surveillance data to support their inspections. | 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. |
004 | The system shall provide surveillance data to other Border Inspection systems. | 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. |