CVO21: International Border Electronic Clearance
This service package provides for automated clearance at international border crossings. It augments the Electronic Clearance service package by allowing interface with border administration and border inspection related functions. This service package processes the entry documentation for vehicle, cargo, and driver, checks compliance with import/export and immigration regulations, handles duty fee processing, and reports the results of the crossing event to manage release of commercial vehicle, cargo, and driver across an international border. It interfaces with administrative systems used by customs and border protection, immigration, carriers, and service providers (e.g., brokers) and inspection systems at international border crossings to generate, process, and store entry documentation.
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 | Commercial Vehicle 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 Administration Center Developer | Fleet and Freight Management 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 Administration Center Developer | Freight Distribution and Logistics 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 Administration Center Developer | Intermodal Customer 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 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 | Commercial Vehicle 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 | Commercial Vehicle Check Equipment 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 | Commercial Vehicle OBE 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 | Freight Equipment 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. |
Commercial Vehicle Administration Center 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. |
Commercial Vehicle Administration Center Developer | Commercial Vehicle 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. |
Commercial Vehicle Administration Center Developer | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle Administration Center Developer | Fleet and Freight Management 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. |
Commercial Vehicle Administration Center Developer | Intermodal Customer 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. |
Commercial Vehicle Administration Center Developer | Other CV 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. |
Commercial Vehicle Check Equipment Developer | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Developer | Commercial Vehicle Check Equipment | 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. |
Commercial Vehicle Check Equipment Developer | Commercial Vehicle OBE 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. |
Commercial Vehicle Check Equipment Developer | Freight Equipment 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. |
Commercial Vehicle OBE 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. |
Commercial Vehicle OBE Developer | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle OBE Developer | Commercial Vehicle OBE | 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. |
Enforcement Center Developer | Commercial Vehicle Check Equipment 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. |
Enforcement Center Developer | Enforcement 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. |
Fleet and Freight Management Center 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. |
Fleet and Freight Management Center Developer | Commercial Vehicle OBE 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. |
Fleet and Freight Management Center Developer | Fleet and Freight Management 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. |
Freight Distribution and Logistics Center 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. |
Freight Distribution and Logistics Center Developer | Freight Distribution and Logistics 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. |
Freight Equipment 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. |
Freight Equipment Developer | Commercial Vehicle Check Equipment 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. |
Freight Equipment Developer | Commercial Vehicle OBE 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. |
Freight Equipment Developer | Freight Equipment | 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. |
Intermodal Customer 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. |
Intermodal Customer System Developer | Commercial Vehicle OBE 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. |
Intermodal Customer System Developer | Intermodal Customer 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. |
Other CV Administration Centers Developer | Commercial Vehicle 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 CV Administration Centers Developer | Other CV 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. |
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. |
Commercial Vehicle Administration Center Installer | Commercial Vehicle 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. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Installer | Installation Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Installer | Commercial Vehicle Check Equipment | 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment Installer | Installation Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle OBE Installer | Commercial Vehicle OBE | 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. |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Installer | Installation Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE 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. |
Enforcement Center Installer | Enforcement 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. |
Enforcement Center Owner | Enforcement Center Installer | Installation Agreement |
Enforcement Center Owner | Enforcement 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. |
Fleet and Freight Management Center Installer | Fleet and Freight Management 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. |
Fleet and Freight Management Center Owner | Fleet and Freight Management Center Installer | Installation Agreement |
Fleet and Freight Management Center Owner | Fleet and Freight Management 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. |
Freight Distribution and Logistics Center Installer | Freight Distribution and Logistics 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. |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics Center Installer | Installation Agreement |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics 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. |
Freight Equipment Installer | Freight Equipment | 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. |
Freight Equipment Owner | Freight Equipment Installer | Installation Agreement |
Freight Equipment Owner | Freight Equipment 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. |
Intermodal Customer System Installer | Intermodal Customer 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. |
Intermodal Customer System Owner | Intermodal Customer System Installer | Installation Agreement |
Intermodal Customer System Owner | Intermodal Customer 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 CV Administration Centers Installer | Other CV 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 CV Administration Centers Owner | Other CV Administration Centers Installer | Installation Agreement |
Other CV Administration Centers Owner | Other CV 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. |
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 | Commercial Vehicle 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 Administration Center Owner | Commercial Vehicle 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. |
Border Inspection Administration Center Owner | Commercial Vehicle 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 Administration Center Owner | Fleet and Freight Management 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 Administration Center Owner | Fleet and Freight Management 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. |
Border Inspection Administration Center Owner | Fleet and Freight Management 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 Administration Center Owner | Freight Distribution and Logistics 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 Administration Center Owner | Freight Distribution and Logistics 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. |
Border Inspection Administration Center Owner | Freight Distribution and Logistics 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 Administration Center Owner | Intermodal Customer 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 | Intermodal Customer System 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 | Intermodal Customer 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 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 | Commercial Vehicle 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 | Commercial Vehicle 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 | Commercial Vehicle 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 | Commercial Vehicle Check Equipment 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 | Commercial Vehicle Check Equipment 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 | Commercial Vehicle Check Equipment 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 | Commercial Vehicle Driver | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Border Inspection System Owner | Commercial Vehicle Inspector | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Border Inspection System Owner | Commercial Vehicle OBE 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 | Commercial Vehicle OBE 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 | Commercial Vehicle OBE 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 | Freight Equipment 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 | Freight Equipment 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 | Freight Equipment 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. |
Commercial Vehicle Administration Center Maintainer | Commercial Vehicle 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. |
Commercial Vehicle Administration Center Manager | Commercial Vehicle 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. |
Commercial Vehicle Administration Center 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. |
Commercial Vehicle Administration Center 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. |
Commercial Vehicle Administration Center 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. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle 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. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle 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. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Inspector | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management 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. |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management Center Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management 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. |
Commercial Vehicle Administration Center Owner | Intermodal Customer 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. |
Commercial Vehicle Administration Center Owner | Intermodal Customer System Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Commercial Vehicle Administration Center Owner | Intermodal Customer 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. |
Commercial Vehicle Administration Center Owner | Other CV 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. |
Commercial Vehicle Administration Center Owner | Other CV 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. |
Commercial Vehicle Administration Center Owner | Other CV 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. |
Commercial Vehicle Administration Center Supplier | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Maintainer | Commercial Vehicle Check Equipment | 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. |
Commercial Vehicle Check Equipment Manager | Commercial Vehicle Check Equipment | 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. |
Commercial Vehicle Check Equipment Manager | Commercial Vehicle Inspector | System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Driver | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE 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. |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Commercial Vehicle Check Equipment Owner | Freight Equipment 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. |
Commercial Vehicle Check Equipment Owner | Freight Equipment 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. |
Commercial Vehicle Check Equipment Owner | Freight Equipment User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Commercial Vehicle Check Equipment Supplier | Commercial Vehicle Check Equipment Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Commercial Vehicle Driver | Commercial Vehicle OBE | Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel. |
Commercial Vehicle Inspector | Commercial Vehicle Check Equipment | Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel. |
Commercial Vehicle OBE Maintainer | Commercial Vehicle OBE | 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. |
Commercial Vehicle OBE Manager | Commercial Vehicle Driver | System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system. |
Commercial Vehicle OBE Manager | Commercial Vehicle OBE | 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. |
Commercial Vehicle OBE 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. |
Commercial Vehicle OBE Owner | Border Inspection System Owner | Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Commercial Vehicle OBE 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. |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment 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. |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment Owner | Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Commercial Vehicle OBE Owner | Commercial Vehicle Inspector | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Commercial Vehicle OBE Owner | Commercial Vehicle Inspector | Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE 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. |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Commercial Vehicle OBE Supplier | Commercial Vehicle OBE Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Enforcement Center Maintainer | Enforcement 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. |
Enforcement Center Manager | Enforcement 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. |
Enforcement Center Owner | Commercial Vehicle Check Equipment 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. |
Enforcement Center Owner | Commercial Vehicle Check Equipment Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Enforcement Center Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Enforcement Center Owner | Commercial Vehicle Inspector | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Enforcement Center Owner | Enforcement 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. |
Enforcement Center Owner | Enforcement 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. |
Enforcement Center Supplier | Enforcement 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. |
Fleet and Freight Management Center Maintainer | Fleet and Freight Management 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. |
Fleet and Freight Management Center Manager | Fleet and Freight Management 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. |
Fleet and Freight Management Center 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. |
Fleet and Freight Management Center 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. |
Fleet and Freight Management Center 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. |
Fleet and Freight Management Center Owner | Commercial Vehicle Driver | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE 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. |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Fleet and Freight Management Center Owner | Fleet and Freight Management 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. |
Fleet and Freight Management Center Owner | Fleet and Freight Management 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. |
Fleet and Freight Management Center Supplier | Fleet and Freight Management 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. |
Freight Distribution and Logistics Center Maintainer | Freight Distribution and Logistics 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. |
Freight Distribution and Logistics Center Manager | Freight Distribution and Logistics 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. |
Freight Distribution and Logistics Center 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. |
Freight Distribution and Logistics Center 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. |
Freight Distribution and Logistics Center 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. |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics 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. |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics 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. |
Freight Distribution and Logistics Center Supplier | Freight Distribution and Logistics 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. |
Freight Equipment Maintainer | Freight Equipment | 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. |
Freight Equipment Manager | Freight Equipment | 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. |
Freight Equipment 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. |
Freight Equipment Owner | Border Inspection System Owner | Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Freight Equipment 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. |
Freight Equipment Owner | Commercial Vehicle Check Equipment 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. |
Freight Equipment Owner | Commercial Vehicle Check Equipment Owner | Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Freight Equipment Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Freight Equipment Owner | Commercial Vehicle Driver | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Freight Equipment Owner | Commercial Vehicle Driver | Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
Freight Equipment Owner | Commercial Vehicle Inspector | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Freight Equipment Owner | Commercial Vehicle Inspector | Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
Freight Equipment Owner | Commercial Vehicle OBE 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. |
Freight Equipment Owner | Commercial Vehicle OBE Owner | Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Freight Equipment Owner | Commercial Vehicle OBE User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Freight Equipment Owner | Freight Equipment 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. |
Freight Equipment Owner | Freight Equipment Manager | Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
Freight Equipment Supplier | Freight Equipment Owner | Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem. |
Intermodal Customer System Maintainer | Intermodal Customer 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. |
Intermodal Customer System Manager | Intermodal Customer 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. |
Intermodal Customer 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. |
Intermodal Customer System 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. |
Intermodal Customer 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. |
Intermodal Customer System Owner | Commercial Vehicle Driver | Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Intermodal Customer System Owner | Commercial Vehicle OBE 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. |
Intermodal Customer System Owner | Commercial Vehicle OBE Owner | Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Intermodal Customer System Owner | Commercial Vehicle OBE User | Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage. |
Intermodal Customer System Owner | Intermodal Customer 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. |
Intermodal Customer System Owner | Intermodal Customer 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. |
Intermodal Customer System Supplier | Intermodal Customer 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 CV Administration Centers Maintainer | Other CV 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 CV Administration Centers Manager | Other CV 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 CV Administration Centers Owner | Commercial Vehicle 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 CV Administration Centers Owner | Commercial Vehicle 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 CV Administration Centers Owner | Commercial Vehicle 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 CV Administration Centers Owner | Other CV 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 CV Administration Centers Owner | Other CV 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 CV Administration Centers Supplier | Other CV 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. |
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. |
Commercial Vehicle Administration Center | Center | The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely. |
Commercial Vehicle Check Equipment | Field | 'Commercial Vehicle Check Equipment' supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. Commercial Vehicle Check Equipment also provides supplemental inspection services such as expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program. |
Commercial Vehicle Driver | Vehicle | The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations. |
Commercial Vehicle Inspector | Field | The people who perform regulatory inspection of Commercial Vehicles in the field. CVO Inspectors support roadside inspection, weighing, and checking of credentials either through automated preclearance or manual methods. The Commercial Vehicle Inspector is an inspection and enforcement arm of regulatory agencies with frequent direct interface with Commercial Vehicles and their Drivers. |
Commercial Vehicle OBE | Vehicle | The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles. |
Enforcement Center | Center | The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc. |
Fleet and Freight Management Center | Center | The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. |
Freight Distribution and Logistics Center | Center | The 'Freight Distribution and Logistics Center' provides intermodal logistics support and support for the efficient distribution of freight across transport systems and modes. This can include consolidation arrangements, warehousing, and consignor-to-consignee intermodal shipping arrangements. These capabilities may be provided as part of intermodal fleet management activities or can be provided by an independent logistics specialist. |
Freight Equipment | Vehicle | 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment. |
Intermodal Customer System | Center | The 'Intermodal Customer System' represents organizations that engage in the shipment of freight, either originator (consigner or shipper) or recipient of the cargo shipment. They enable the movement of goods on routes that require the use of other modes of transportation such as heavy rail, air, sea, etc. The Intermodal Customer System includes those personnel responsible for the movement of freight across international borders. |
Other CV Administration Centers | Center | 'Other CV Administration Centers' is intended to provide a source and destination for information flows between peer (e.g. inter-regional) commercial vehicle administration centers. It enables commercial vehicle administration activities to be coordinated across different jurisdictional areas. It encompasses all functions associated with commercial vehicle safety, registration, and operating authority for non-U.S. based commercial motor vehicle carriers. The agencies represented herein may include Federal, state, provincial, and local regulatory entities outside the U.S. |
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 |
CV On-Board Electronic Screening Support | 'CV On-Board Electronic Screening Support' exchanges information with roadside facilities, providing information such as driver, vehicle, and carrier identification to roadside facilities that can be used to support electronic screening. Pass/pull-in messages are received and presented to the commercial vehicle driver and screening events are recorded. Additional information, including trip records (e.g., border clearance information), safety inspection records, cargo information, and driver status information may also be collected, stored, and made available to the roadside facility. | Commercial Vehicle OBE |
CVAC Information Exchange | 'CVAC Information Exchange' supports the exchange of safety, credentials, permit data, and other data concerning the operation of commercial vehicles among jurisdictions. The object also supports the exchange of safety (e.g., driver logs), credentials, permit, and operations data between systems (for example, an administrative center and the roadside check facilities) within a single jurisdiction. Data are collected from multiple authoritative sources and packaged into snapshots (top-level summary and critical status information) and profiles (detailed and historical data). Data is made available to fleet operators and other information requestors on request or based on subscriptions established by the requestor. | Commercial Vehicle Administration Center |
CVAC International Administration | 'CVAC International Administration' generates and processes the entry documentation necessary to obtain release of vehicle, cargo, and driver across an international border, report the results of the crossing event, and handle duty fee processing. It interfaces with the systems used by customs and border protection, immigration, carriers, and service providers (e.g., brokers) to generate, process, and store entry documentation. | Commercial Vehicle Administration Center |
CVCE Electronic Screening | 'CVCE Electronic Screening' supports electronic credentials and safety screening of commercial vehicles at mainline speeds. It processes the data from the commercial vehicles along with accessed database information to determine whether a pull-in message is needed. It may also generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities. | Commercial Vehicle Check Equipment |
CVCE International Border Crossing | 'CVCE International Border Crossing' checks compliance with import/export and immigration regulations to manage release of commercial vehicle, cargo, and driver across an international border. It includes interfaces to the equipment at international border crossings operated by government agencies such as Customs and Border Protection. | Commercial Vehicle Check Equipment |
FDLC Freight Services | 'FDLC Freight Services" provides the core freight distribution and logistics center functionality, including management and coordination of intermodal shipping arrangements, including load consolidation and warehousing services. | Freight Distribution and Logistics Center |
Freight Administration and Management | 'Freight Administration and Management' manages the movement of freight from source to destination. It interfaces to intermodal customers to setup and schedule transportation and coordinates with intermodal terminals and freight consolidation stations to coordinate the shipment. It coordinates with the appropriate government agencies to expedite the movement of trucks, their drivers, and their cargo across international borders. The application monitors the status of the freight and freight equipment (container, trailer, or chassis) and monitors freight location and compares it against the planned route. | Fleet and Freight Management Center |
Freight Equipment Monitoring | 'Freight Equipment Monitoring' includes the on-board devices used to monitor intermodal freight equipment. These devices provide freight equipment location and status of the freight, container, or chassis equipment. | Freight Equipment |
Includes Information Flows:
Information Flow | Description |
---|---|
arrival notification | Notification of arrival (and departure) of a motor vehicle at the inspection station. |
border agency clearance results | Notification regarding the granting of permission for commercial freight shipment to enter the U.S. |
border clearance data | Trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events. |
border clearance data request | Request for trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events. |
border clearance event | Reports clearance event data regarding action taken at border, including acceptance or override of system decision, and date/time stamp |
border clearance event records | Aggregate port clearance event data regarding action taken at border, including acceptance or override of system decisions, and date/time stamps. |
border clearance status | 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 those results become available. |
border pass/pull-in | Command to commercial vehicle to pull into or bypass border inspection station |
border security input | Information regarding security related events occurring at the border. |
clearance notification | Notification that cargo has been cleared through customs. |
client verification information | Information about carriers who have made border credential applications such as commercial drivers license information and carrier safety status. |
client verification request | Request for information such as commercial drivers license information and carrier safety status. |
consolidated agency response | Electronic manifest data as well as commercial vehicle screening results. |
container manifest | Official statement of the cargo held in a container. |
container seal interrogation | Customs inspection of the electronic seal on a container to verify the container has not been opened or tampered with; requires proper authentication. |
container seal status | The status of an electronic seal on a container, indicating sealing time, location, and authority, and any openings or tampering. |
credentials status information | Credentials information such as registration, licensing, insurance, check flags, and electronic screening enrollment data. A unique identifier is included. Corresponds to the credentials portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
cv driver input | This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information. |
CVC override mode | This flow represents the tactile or auditory interface with ITS equipment containing the manual override of automated pass/pull-in decisions generated by the Commercial Vehicle Check station. |
CVO inspector information | This flow represents the visual or auditory interface with ITS equipment containing credential, safety, and preclearance information and instructions to the commercial vehicle inspector. |
CVO pass/pull-in message | This flow represents the visual or auditory interface with ITS equipment containing a message sent to commercial vehicle driver indicating whether to bypass or requesting pull in to inspection/verification stop along with inspection results (e. g., LED indicator on transponder or variable message sign). |
electronic lock data | Notification to roadside (via transponder) of the presence and status of electronic cargo locks. |
electronic lock data request | Request from roadside for data regarding presence and status of electronic cargo locks. |
freight equipment information | Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, temperature, humidity, power, battery levels, brake wear data, and bill of lading/information regarding the cargo/content. |
information on violators | Information on violators provided by a law enforcement agency. May include information about commercial vehicle violations or other kinds of violations associated with the particular entity. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown. |
inspection results | Report of results of border inspection on a particular load. |
manifest data | Identifies Port of Entry, date, and information on carrier and goods, origin, etc. |
manifest receipt confirmation | Confirmation that a shippers manifest has been received. |
pre-arrival notification | Identification of a vehicle or driver that is approaching a border crossing. |
request tag data | Request for tag information including tag id and associated data. |
safety status information | Safety information such as safety ratings, security ratings or flags, inspection summaries, and violation summaries. A unique identifier is included. Corresponds to the safety and security portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
screening results | 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. |
tag data | Unique tag ID and related vehicle information. |
transportation border clearance assessment | Includes directions for commercial driver to proceed to nearest vehicle weigh and inspection station for further review if required. |
trip declaration identifiers | Specific identifiers extracted from notification containing information regarding pending commercial freight shipment into the U.S. Includes carrier, vehicle, and driver identification data. |
trip identification number | The unique trip load number for a specific cross-border shipment. |
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 |
Freight Management: Customer Satisfaction |
Freight Management: Travel Time Delay |
Freight Management: Travel Time Reliability |
Associated Objectives and Performance Measures 

Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. | Border Inspection Administration | 03 | The center shall provide the collected border activities statistics data to archived data and planning systems. |
04 | The center shall collect information on Port of Entry, date, and other information on carrier and goods. | |||
CV On-Board Electronic Screening Support | 03 | The commercial vehicle shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, including border crossings. | ||
CVAC Information Exchange | 01 | The center shall exchange information with roadside check facilities, including credentials and credentials status information, safety status information, daily site activity data, driver records, and citations. | ||
CVAC International Administration | 04 | The center shall receive and store border clearance event data from the roadside check facilities that are located near border crossings. | ||
CVCE International Border Crossing | 02 | The roadside check facility equipment at a border crossing shall receive the inspection results from the border inspection system to be used to screen the incoming commercial vehicles once they have cleared the border agency's inspection area. | ||
06 | The roadside check facility equipment at a border crossing shall send clearance event data regarding action taken at a border to the commercial vehicle administration center and to the commercial vehicle. This may include a date/time stamped acceptance or override of system decisions whether to allow release of the vehicle and its cargo. | |||
Freight Administration and Management | 07 | The center shall support the submission of cargo manifest data to the appropriate government border inspection administration system. | ||
Freight Equipment Monitoring | 03 | The onboard freight device shall provide freight equipment location and status of the freight, container, or chassis equipment. | ||
02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. | Border Inspection Administration | 02 | The center shall process cargo manifest data from freight distribution and logistics centers to clear cargo for crossing the border. |
05 | The center shall collect border inspection results from the field. | |||
06 | The center shall provide fleet and freight management centers with the results of the clearance processing, including the updated manifest. | |||
CVCE Electronic Screening | 05 | The roadside check facility equipment shall provide an interface to inspectors in the field to allow them to monitor and if necessary override the pull-in decisions made by the system. | ||
FDLC Freight Services | 07 | The center shall receive the notification that cargo has been cleared through customs. | ||
08 | The center shall identify information on carrier and goods origin, port of entry and date. | |||
03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. | Border Inspection | 03 | The border field equipment shall provide border security-related information occurring at the border to transportation centers. |
Border Inspection Administration | 07 | The center shall provide the appropriate commercial vehicle administration center with the arrivals of freight and commercial vehicles crossing a border. | ||
CVAC Information Exchange | 02 | The center shall exchange safety and credentials data among other commercial vehicle administration centers, including border clearance status, credentials information, credentials status information, driver records, accident reports, permit information, and safety status information. | ||
CVAC International Administration | 01 | The center shall receive domestic transportation and declaration information from Border Inspection Administration Agencies such as U.S. Bureau of Immigration and Customs Enforcement (ICE), the U.S. Bureau of Customs and Border Protection (CBP), and their counterparts in Canada and Mexico. | ||
02 | The center shall provide an assessment regarding a commercial vehicle and driver at a border crossing. The assessment or clearance data will be forwarded on to the appropriate regulatory agencies and roadside check facilities operating at the border crossing. | |||
03 | The center shall provide border clearance status concerning commercial vehicles and their shipments to the roadside check facilities, the commercial vehicle fleet and freight management centers, intermodal freight shippers, other commercial vehicle administration centers, and border inspection administration centers. | |||
FDLC Freight Services | 09 | The center shall provide information on the carrier and goods, origin, port of entry, and date. | ||
Freight Administration and Management | 03 | The center shall coordinate the shipment of cargo using freight equipment with intermodal freight depots. Information to be coordinated includes information regarding a freight transportation booking and the assigned driver and vehicle scheduled to transport the freight along with cargo movement logs, routing information, and cargo ID. | ||
07 | The center shall support the submission of cargo manifest data to the appropriate government border inspection administration system. | |||
11 | The center shall collect the border crossing clearance status of commercial freight shipment scheduled to enter the U.S, from commercial vehicle administration systems. | |||
04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. | Border Inspection Administration | 08 | The center shall exchange border manifest data with the border crossing field equipment. |
CV On-Board Electronic Screening Support | 01 | The commercial vehicle shall receive electronic screening (pass/pull-in) messages from the roadside check facilities and present them to the driver in either audible or visual forms. | ||
02 | The commercial vehicle shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo status, hazmat identifiers, out of service status, vehicle axle weight, vehicle weight, and time. | |||
04 | The commercial vehicle shall support an interface to a commercial vehicle driver that is also acting in the role of a commercial vehicle fleet manager to set up routes, pay necessary taxes, obtain proper credentials, and write the identifiers to the electronic tag for the driver, vehicle, and carrier. | |||
CVCE Electronic Screening | 01 | The roadside electronic screening equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. | ||
07 | The roadside electronic screening equipment shall request and input electronic screening data from the commercial vehicle's electronic tag data. | |||
08 | The roadside check facility equipment shall collect safety data from the commercial vehicle and its freight equipment. | |||
09 | The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, enforcement agencies, and the inspector. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc. | |||
CVCE International Border Crossing | 01 | The roadside check facility equipment at a border crossing shall receive the border agency clearance results, transportation border clearance assessments, and trip declaration identifiers from the commercial vehicle administration center to be used to screen the incoming commercial vehicles. | ||
03 | The roadside check facility equipment at a border crossing shall request and input the tag data from approaching commercial vehicles to determine the identity of the vehicle along with its carrier, driver, and a trip identity. | |||
04 | The roadside check facility equipment at a border crossing shall request and input the border clearance data from approaching commercial vehicles to compare against the data received from the center concerning compliance with import/export and immigration regulations. | |||
05 | The roadside check facility equipment at a border crossing shall request and input the electronic cargo lock data from approaching commercial vehicles to compare against the data received from the center. | |||
06 | The roadside check facility equipment at a border crossing shall send clearance event data regarding action taken at a border to the commercial vehicle administration center and to the commercial vehicle. This may include a date/time stamped acceptance or override of system decisions whether to allow release of the vehicle and its cargo. | |||
Freight Administration and Management | 04 | The center shall track the progress of freight equipment as it moves from source to destination based on inputs from the commercial vehicles, the freight equipment, intermodal freight depots, shippers, and commercial vehicle administration centers that provide border clearance status information. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 | |
Border Information Flow Architecture | 5/16/2012 |
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 |
Commercial Vehicle Administration Center | High | High | Moderate | Class 4 |
Commercial Vehicle Check Equipment | High | High | Moderate | Class 4 |
Commercial Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
Enforcement Center | High | Moderate | Low | Class 4 |
Fleet and Freight Management Center | High | High | Moderate | Class 4 |
Freight Distribution and Logistics Center | Moderate | High | Moderate | Class 3 |
Freight Equipment | Moderate | Moderate | Moderate | Class 2 |
Intermodal Customer System | High | High | Moderate | Class 4 |
Other CV Administration Centers | High | High | Moderate | Class 4 |
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 | Border Inspection System | manifest data | 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 lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | Corruption, unavailability or unauthorized manipulation of this data could lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | |||
Border Inspection Administration Center | Commercial Vehicle Administration Center | client verification request | Moderate | Moderate | Moderate |
May include PII, and prompts a response flow that does include PII. | Request needs to be correct, or the wrong data may be sent. | MODERATE assumes this flow is part of a real-time request-response suppporting border clearance. If not real-time or near-real time, this could be LOW. | |||
Border Inspection Administration Center | Commercial Vehicle Administration Center | pre-arrival notification | Moderate | High | Moderate |
Includes vehicle and/or operator identifier which is PII by nature. Disclosure of this information could enable vehicle tracking, at least at the border, which would be useful for competitive businesses and actors bent on criminal activity against the vehicle/carrier in question. | Since this is used for electronic clearance purposes, any modification would deny a rightful crossing or enable a fraudulent one, both of which have significant consequences. Given that the vehicle could have all manner of contents, rated HIGH because of the potential for smuggling high value or dangerous goods. | Electronic clearance might not function without this flow, justifying MODERATE.This will be an inconvenience, but not denial of service, since alternative mechanisms exist to facilitate border crossing. | |||
Border Inspection Administration Center | Fleet and Freight Management Center | clearance notification | Moderate | Moderate | Moderate |
This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for logistic specialists to know, however, they will also be receiving similar information from other sources. A false message here may cause confusions, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Border Inspection Administration Center | Fleet and Freight Management Center | manifest receipt confirmation | High | Moderate | Moderate |
May contain PII of driver, vehicle and/or cargo, location and destination. This is personal and also competitive. Compromise of this information could lead to leverage or business advantage, and if consistent could have a large impact on targeted carriers. Even if not, setting to equal origination flow 'manifest data' | Corruption, unavailability or unauthorized manipulation of this data could lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | Corruption, unavailability or unauthorized manipulation of this data could lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | |||
Border Inspection Administration Center | Freight Distribution and Logistics Center | clearance notification | Moderate | Moderate | Moderate |
This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for logistic specialists to know, however, they will also be receiving similar information from other sources. A false message here may cause confusions, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Border Inspection Administration Center | Intermodal Customer System | clearance notification | Moderate | Moderate | Moderate |
This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for cargo originators or recipients to know, however, they will also be receiving similar information from other sources. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Border Inspection System | Border Inspection Administration Center | border security input | Moderate | Moderate | Low |
Since this is describing events that already occurred it is possible that someone could observe these by sitting at the border and watching. However some things in this may be slightly sensitive in nature and should not be completely visible to anyone. If this flow could carry instructions to be acted on at a later point (e.g. "Suspicious traveler, pull over down the road and investigate"), this could potentially be HIGH because it is potentially national security related information; however, it is not clear from the CVRIA description whether or not this will be the case. | 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 | Commercial Vehicle Administration Center | arrival notification | Low | Moderate | Low |
This information can be directly observed at the border. | This information could affect how the CVAC responds to a request on a vehicle 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 | Commercial Vehicle Check Equipment | inspection results | Moderate | Moderate | Low |
This could contain information on what is in a particular load. As such it could be used by a malicious individual to determine which vehicles are a greater target then the rest. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This is an informational message and as such any errors in it should not affect anything. If this has higher integrity though then it will be more likely to be useful. DISC: Original V2I analysis classified this as LOW. | 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 | Commercial Vehicle OBE | border pass/pull-in | Not Applicable | High | Moderate |
This is directly observable data. | This message is directly acted upon. It should not be possible to spoof a border inspection station bypass. | The system should know if these messages are not received. If the messages are not received, the system should fail safely, with the border agents performing additional inspections. | |||
Border Inspection System | Commercial Vehicle OBE | clearance notification | Moderate | Moderate | Moderate |
This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for logistic specialists to know, however, they will also be receiving similar information from other sources. A false message here may cause confusions, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Border Inspection System | Commercial Vehicle OBE | request tag data | Not Applicable | Moderate | Low |
This request is sent to all vehicles entering the border, and does not contain any sensitive information. | This needs to verify that it is coming from a valid sender. | If this request is not received, the system will not broadcast its tag data. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Border Inspection System | Freight Equipment | container seal interrogation | Low | Moderate | Low |
The presence of electronic locks will most likely be observable by looking at the cargo doors and the other information is not sensitive in nature. | The container seal status returned after this interrogation will not have a HIGH integrity, as such is interrogation does not require a HIGH integrity. If the integrity of the container seal status is somehow possible to raise to a HIGH, then this could also have a HIGH integrity. | If this interrogation is not received, the system will not broadcast its Container Seal Status. However, there are multiple chances for this data to be transmitted and received. Additionally, if this information is never received the vehicle will be handled in the same way that it was prior to the implementation of this system. | |||
Border Inspection System | Freight Equipment | request tag data | Not Applicable | Moderate | Low |
This request is sent to all vehicles entering the border, and does not contain any sensitive information. | This needs to verify that it is coming from a valid sender. | If this request is not received, the system will not broadcast its tag data. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle Administration Center | Border Inspection Administration Center | border clearance status | High | High | Moderate |
This includes information regarding what is being shipped across the border, which contains highly sensitive information. This also includes data regarding clearance results, which is also sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | This information is used later in the decision process. Future trips across the border take past data into account. Incorrect data here may lead to incorrect decisions made regarding letting something across the border. | This is all recent data, it is not acted upon immediately. This system should operate correctly with a few missed messages. It is necessary for the sender to know if the message was received. | |||
Commercial Vehicle Administration Center | Border Inspection Administration Center | client verification information | Moderate | Moderate | Moderate |
Contains carrier and operator PII, which if observed by a hostile third party could be used in anti-competitive or identity-related criminal activities. | Since this is used as part of the border clearance process, it must be timely and accurate to avoid delays for the subject operator. | Since this is used as part of the border clearance process, it must be timely and accurate to avoid delays for the subject operator. | |||
Commercial Vehicle Administration Center | Border Inspection Administration Center | screening results | Moderate | Moderate | Low |
This could contain information on what is in a particular load. As such it could be used by a malicious individual to determine which vehicles are a greater target then the rest. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This is an informational message and as such any errors in it should not affect anything. If this has higher integrity though then it will be more likely to be useful. | 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. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | border agency clearance results | Low | High | Moderate |
This information is observable by seeing if the freight shipment enters the U.S. It should only contain the result of the analysis, and should not contain sensitive information. | If this message is incorrect or altered, it could have a significant economic impact. This message is one requirement to determine if a freight shipment is allowed to enter the U.S. | This message is used to determine whether or not a freight shipment can cross the border. If this message is not received, the recipient must be aware, so that they can request the result again. A slightly delay will not have a significant impact on the border crossing. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | transportation border clearance assessment | Moderate | High | Moderate |
In general, the result of this assessment will be clearly indicated by a vehicle being allowed through, or told to stop. However, if a vehicle that will be stopped is able to learn about it in advance, they could attempt to flee. | An incorrect message indicating to check a vehicle that doesn't need to be checked would simply lead to wasted unnecessary inspections, however, an incorrect message claiming that a vehicle does not need an inspection could lead to a vehicle containing contraband not being inspected. | 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. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | trip declaration identifiers | Moderate | Moderate | Moderate |
These identifiers are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted identifiers will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles through the CVCE. | |||
Commercial Vehicle Administration Center | Fleet and Freight Management Center | border clearance status | High | Moderate | Moderate |
This includes information regarding what is being shipped across the border, which contains highly sensitive information. This also includes data regarding clearance results, which is also sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for fleet-fright managers to know, however, they will also be receiving similar information from other sources. A false message here may cause confusion, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Commercial Vehicle Administration Center | Intermodal Customer System | border clearance status | High | Moderate | Moderate |
This includes information regarding what is being shipped across the border, which contains highly sensitive information. This also includes data regarding clearance results, which is also sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for cargo originators or recipients to know, however, they will also be receiving similar information from other sources. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | border clearance status | High | Moderate | Moderate |
This includes information regarding what is being shipped across the border, which contains highly sensitive information. This also includes data regarding clearance results, which is also sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for cargo originators or recipients to know, however, they will also be receiving similar information from other sources. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | credentials status information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | safety status information | Moderate | Moderate | Moderate |
Credentials data are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted credentials data will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles administered through equipment managed by other CVAC. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | border clearance event records | Moderate | Moderate | Moderate |
While the data contained within this flow could be directly observed, this flow effectively aggregates many single observations, and as such observing this flow proxies observing many individual flows. Since mass border clearance information could indicate trends or, if penetrated could be used along with other information in illicit tracking activities, this compromise of this flow could have significant impact. | This data is not directly effecting any decisions made in the system. It may be used in an aggregate to influence future decisions, but any inaccuracies should not have a significant affect. | The system must have an acknowledgement of a missed message. It is not acted upon in real time, but the CVAC should receive all records at some point. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Driver | CVO pass/pull-in message | Not Applicable | High | High |
This interface is also directly observable. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. If roadside mechanisms are not existant, then this would be HIGH. | Data should be available as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. If roadside mechanisms are not existant, then this would be HIGH. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Inspector | CVO inspector information | Not Applicable | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive reasons. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | border clearance data request | Moderate | Moderate | Low |
May not have an identity but does include an identifier that can be related to vehicle movement, and so should be protected from observation. | If the data in this request is incorrect, the vehicle may have difficulty in the border crossing or be incorrectly cleared. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | border clearance event | Moderate | Moderate | Low |
May not have an identity but does include an identifier that can be related to vehicle movement, and so should be protected from observation. | If this data is incorrect, the vehicle may have difficulty in the border crossing or be incorrectly cleared. | If this data is missing, the vehicle will be inconvenienced in the border crossing, which will slow down border crossings for other vehicles as well; however, the clearance could always be communicated manually and the issue solved on a vehicle-by-vehicle basis. Busy crossings may elevate this to MODERATE. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | border pass/pull-in | Not Applicable | High | Moderate |
This is directly observable data. | This message is directly acted upon. It should not be possible to spoof a border inspection station bypass. | The system should know if these messages are not received. If the messages are not received, the system should fail safely, with the border agents performing additional inspections. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | clearance notification | Moderate | Moderate | Moderate |
This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for logistic specialists to know, however, they will also be receiving similar information from other sources. A false message here may cause confusions, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | electronic lock data request | Low | Moderate | Low |
This request is sent to all vehicles entering the border, and does not contain any sensitive information. | This needs to verify that it is coming from a valid sender. | If this request is not received, the system will not broadcast its Electronic Lock Data. However, there are multiple chances for this data to be transmitted and received. Additionally, if this information is never received the vehicle will be handled in the same way that it was prior to the implementation of this system. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | request tag data | Not Applicable | Moderate | Low |
This request is sent to all vehicles entering the border, and does not contain any sensitive information. | This needs to verify that it is coming from a valid sender. | If this request is not received, the system will not broadcast its tag data. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle Check Equipment | Freight Equipment | request tag data | Not Applicable | Moderate | Low |
This request is sent to all vehicles entering the border, and does not contain any sensitive information. | This needs to verify that it is coming from a valid sender. | If this request is not received, the system will not broadcast its tag data. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle Driver | Commercial Vehicle OBE | cv driver input | Moderate | Moderate | Moderate |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive and physical security reasons. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. | Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH. | |||
Commercial Vehicle Inspector | Commercial Vehicle Check Equipment | CVC override mode | Not Applicable | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive reasons. | Overrides must be correct and available or it would be possible for a vehicle that the inspector wants to see to pass through uninspected, which could have a safety impact. | Overrides must be correct and available or it would be possible for a vehicle that the inspector wants to see to pass through uninspected, which could have a safety impact. | |||
Commercial Vehicle OBE | Border Inspection System | tag data | Low | Moderate | Low |
This is broadcast data. | False data here could lead to a misclassification of the vehicle. If it was an accidental error, it would be easy to correct. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | border clearance data | Moderate | Moderate | Moderate |
May not have an identity but does include an identifier that can be related to vehicle movement, and so should be protected from observation. | This data is being reported by the vehicles attempting to cross the border, all the data reported by them should be verified before being trusted. Considering that, the integrity could never be a HIGH. However if this data is incorrect often, it will be of little use to the system. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | electronic lock data | Low | Moderate | Low |
The presence of electronic locks will most likely be observable by looking at the cargo doors. | This data is being reported by the vehicles attempting to cross the border, all the data reported by them should be verified before being trusted. Considering that, the integrity could never be a HIGH. However if this data is incorrect often, it will be of little use to the system. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | tag data | Low | Moderate | Low |
This is broadcast data. | False data here could lead to a misclassification of the vehicle. If it was an accidental error, it would be easy to correct. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Commercial Vehicle OBE | Commercial Vehicle Driver | CVO pass/pull-in message | Not Applicable | Moderate | Moderate |
This interface is also directly observable. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. | Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH. | |||
Enforcement Center | Commercial Vehicle Check Equipment | information on violators | High | Moderate | Low |
Contains PII and violation information, that if disclosed to parties other than the destination could provide leverage (business or personal) over the commercial vehicle. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | This flow does not need to be real-time as there will be a backup (manual) mechanism, and buffering or batch uploads would also suffice. | |||
Fleet and Freight Management Center | Border Inspection Administration Center | manifest data | 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 lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | Corruption, unavailability or unauthorized manipulation of this data could lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | trip identification number | Moderate | Moderate | Low |
Trip number may be associated with other flows, which if observed would indicate a vehicle's routing, which if viewed by an attacker could be used against the operator in the commission of a crime. | May be used in other flows, so needs to be accuate. | Likely a significant period of time over which the flow may be instantiated before it impacts operations. | |||
Freight Distribution and Logistics Center | Border Inspection Administration Center | manifest data | 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 lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | Corruption, unavailability or unauthorized manipulation of this data could lead to border clearance delays, greatly impacting the individual vehicles involved. Depending on the volume of vehicles at the border crossing, this could be MODERATE. | |||
Freight Equipment | Border Inspection System | container manifest | Moderate | Moderate | Low |
The contents of a freight container may not necessarily be something that should be made public. If it is known that a container is carrying high value objects, it may be the target of theft. | Due to the nature of this information, it is impossible to be certain that what it states is true, thus it cannot have a HIGH integrity. However, it should be as accurate as possible. | If the vehicle is not pre-approved it will be handled by border security. Therefore, it is not clear that there is any security risk from failures of availability; more availability allows the operator to benefit from the processing efficiency gains associated with this application but any level of availability is acceptable from a security point of view. | |||
Freight Equipment | Border Inspection System | container seal status | Moderate | Moderate | Moderate |
Possibly competetive information. If available in aggregate or large scale to actors with competing interests to the actors legitimately involved with the container, information as to where the container is and is projected to be at different times could be abused to the actor's advantage.For high value containers, this may be HIGH. | Due to the nature of this information, it is impossible to be certain that what it states is true, thus it cannot have a HIGH integrity. However, it should be as accurate as possible. | Would be nice to make this HIGH considering the safety implications in case of HAZMAT containers, but considering the context of an incident, HIGH is likely impractical for this wireless signal in a vehicular environment. | |||
Freight Equipment | Border Inspection System | tag data | Low | Moderate | Low |
This is broadcast data. | False data here could lead to a misclassification of the vehicle. If it was an accidental error, it would be easy to correct. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Freight Equipment | Commercial Vehicle Check Equipment | tag data | Low | Moderate | Low |
This is broadcast data. | False data here could lead to a misclassification of the vehicle. If it was an accidental error, it would be easy to correct. | If this data is missing, the system cannot make a decision about how to handle that vehicle. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security. | |||
Freight Equipment | Commercial Vehicle OBE | freight equipment information | Moderate | Moderate | Moderate |
Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | On-board data exchanges, should be at least MODERATE so that on-board systems can fulfill their functions. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | |||
Intermodal Customer System | Border Inspection Administration Center | manifest data | Moderate | Moderate | 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. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Intermodal Customer System | Commercial Vehicle OBE | trip identification number | Moderate | Moderate | Low |
Trip number may be associated with other flows, which if observed would indicate a vehicle's routing, which if viewed by an attacker could be used against the operator in the commission of a crime. | May be used in other flows, so needs to be accuate. | Likely a significant period of time over which the flow may be instantiated before it impacts operations. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | border clearance status | High | Moderate | Moderate |
This includes information regarding what is being shipped across the border, which contains highly sensitive information. This also includes data regarding clearance results, which is also sensitive. This flow contains information about a significant number of shipments, which increases the value of this data. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for cargo originators or recipients to know, however, they will also be receiving similar information from other sources. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | credentials status information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles.. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | safety status information | Moderate | Moderate | Moderate |
Credentials data are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted credentials data will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles through the CVCE. |
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 process cargo manifest data from freight distribution and logistics centers to clear cargo for crossing the border. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
002 | The system shall provide the collected border activities statistics data to archived data and planning systems. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
003 | The system shall collect information on Port of Entry, date, and other information on carrier and goods. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
004 | The system shall collect border inspection results from the field. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
005 | The system shall provide fleet and freight management centers with the results of the clearance processing, including the updated manifest. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
006 | The system shall provide the appropriate commercial vehicle administration center with the arrivals of freight and commercial vehicles crossing a border. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
007 | The system shall exchange border manifest data with the border crossing field equipment. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
008 | The system shall exchange information with roadside check facilities, including credentials and credentials status information, safety status information, daily site activity data, driver records, and citations. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
009 | The system shall exchange safety and credentials data among other commercial vehicle administration centers, including border clearance status, credentials information, credentials status information, driver records, accident reports, permit information, and safety status information. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
010 | The system shall receive domestic transportation and declaration information from Border Inspection Administration Agencies such as U.S. Bureau of Immigration and Customs Enforcement (ICE), the U.S. Bureau of Customs and Border Protection (CBP), and their counterparts in Canada and Mexico. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
011 | The system shall provide an assessment regarding a commercial vehicle and driver at a border crossing. The assessment or clearance data will be forwarded on to the appropriate regulatory agencies and roadside check facilities operating at the border crossing. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
012 | The system shall provide border clearance status concerning commercial vehicles and their shipments to the roadside check facilities, the commercial vehicle fleet and freight management centers, intermodal freight shippers, other commercial vehicle administration centers, and border inspection administration centers. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
013 | The system shall receive and store border clearance event data from the roadside check facilities that are located near border crossings. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
014 | The system shall receive the notification that cargo has been cleared through customs. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
015 | The system shall identify information on carrier and goods origin, port of entry and date. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
016 | The system shall provide information on the carrier and goods, origin, port of entry, and date. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
017 | The system shall coordinate the shipment of cargo using freight equipment with intermodal freight depots. Information to be coordinated includes information regarding a freight transportation booking and the assigned driver and vehicle scheduled to transport the freight along with cargo movement logs, routing information, and cargo ID. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
018 | The system shall track the progress of freight equipment as it moves from source to destination based on inputs from the commercial vehicles, the freight equipment, intermodal freight depots, shippers, and commercial vehicle administration centers that provide border clearance status information. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
019 | The system shall support the submission of cargo manifest data to the appropriate government border inspection administration system. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. | ||
020 | The system shall collect the border crossing clearance status of commercial freight shipment scheduled to enter the U.S, from commercial vehicle administration systems. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
021 | The system shall provide border security-related information occurring at the border to transportation centers. | 03 | Commercial Vehicle Administration and Border Administration need to exchange commercial vehicle records with other agencies and stakeholders along a border including credentials, status of the credentials, and records of fuel tax payments. |
022 | The system shall provide an interface to inspectors in the field to allow them to monitor and if necessary override the pull-in decisions made by the system. | 02 | Commercial Vehicle Administration and Border Administration need to be able to verify that vehicles, freight equipment, cargo, and drivers coming into the country are admissible and comply with federal laws and regulations. |
023 | The system shall collect safety data from the commercial vehicle and its freight equipment. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
024 | The system shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, enforcement agencies, and the inspector. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
025 | The system shall receive the border agency clearance results, transportation border clearance assessments, and trip declaration identifiers from the commercial vehicle administration center to be used to screen the incoming commercial vehicles. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
026 | The system shall receive the inspection results from the border inspection system to be used to screen the incoming commercial vehicles once they have cleared the border agency's inspection area. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
027 | The system shall request and input the tag data from approaching commercial vehicles to determine the identity of the vehicle along with its carrier, driver, and a trip identity. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
028 | The system shall request and input the border clearance data from approaching commercial vehicles to compare against the data received from the center concerning compliance with import/export and immigration regulations. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
029 | The system shall request and input the electronic cargo lock data from approaching commercial vehicles to compare against the data received from the center. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
030 | The system shall send clearance event data regarding action taken at a border to the commercial vehicle administration center and to the commercial vehicle. This may include a date/time stamped acceptance or override of system decisions whether to allow release of the vehicle and its cargo. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. | ||
031 | The system shall receive electronic screening (pass/pull-in) messages from the roadside check facilities and present them to the driver in either audible or visual forms. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
032 | The system shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo status, hazmat identifiers, out of service status, vehicle axle weight, vehicle weight, and time. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
033 | The system shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, including border crossings. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |
034 | The system shall support an interface to a commercial vehicle driver that is also acting in the role of a commercial vehicle fleet manager to set up routes, pay necessary taxes, obtain proper credentials, and write the identifiers to the electronic tag for the driver, vehicle, and carrier. | 04 | Commercial Vehicle Administration and Border Administration need to provide electronic communications with commercial vehicles to support security inspections and weigh-in-motion detection. |
035 | The system shall provide freight equipment location and status of the freight, container, or chassis equipment. | 01 | Commercial Vehicle Administration and Border Administration need to collect transportation related data, including border crossing data to support planning and research activities that span land border crossings. |