Parent Service Package: TM23
< < TM23.1 : TM23.2 : TM24.1 > >

TM23.2: C-ITS Communications

Short range communications is used to share border-related information with travelers.

Relevant Regions:

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 and Port Administration Center Developer	Border and Port 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 and Port 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 and Port Administration Center Developer	Personal Information Device 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 and Port 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	Connected Vehicle Roadside 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	Light 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	Traffic 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 System Developer	Transportation Information 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.
Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Developer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Developer	Light 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.
Connected Vehicle Roadside Equipment Developer	Traffic 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.
Light 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.
Light Vehicle OBE Developer	Connected Vehicle Roadside 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.
Light Vehicle OBE Developer	Light 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.
Personal Information Device Developer	Border and Port 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.
Personal Information Device Developer	Personal Information Device	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.
Traffic Management Center Developer	Traffic 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.
Transportation Information Center Developer	Transportation Information 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.
Traveler Card 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.
Traveler Card Developer	Light 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.
Traveler Card Developer	Traveler Card	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 and Port Administration Center Installer	Border and Port 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 and Port Administration Center Owner	Border and Port Administration Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Border and Port Administration Center Owner	Border and Port 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 (hide) An agreement whereupon one party installs a system on behalf of a second party.
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.
Connected Vehicle Roadside Equipment Installer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Light Vehicle OBE Installer	Light 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.
Light Vehicle OBE Owner	Light Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Light Vehicle OBE Owner	Light 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.
Personal Information Device Installer	Personal Information Device	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.
Personal Information Device Owner	Personal Information Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Information Device Owner	Personal Information Device 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.
Traffic Management Center Installer	Traffic 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.
Traffic Management Center Owner	Traffic Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traffic Management Center Owner	Traffic 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.
Transportation Information Center Installer	Transportation Information 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.
Transportation Information Center Owner	Transportation Information Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transportation Information Center Owner	Transportation Information 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.
Traveler Card Installer	Traveler Card	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.
Traveler Card Owner	Traveler Card Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traveler Card Owner	Traveler Card 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 and Port Administration Center Maintainer	Border and Port 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 and Port Administration Center Manager	Border and Port 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 and Port Administration Center Manager	Border Inspection Administration Center Operator	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.
Border and Port Administration Center Owner	Border and Port 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 and Port Administration Center Owner	Border and Port 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 and Port 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 and Port Administration Center Owner	Border Inspection System Operator	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 and Port Administration Center Owner	Border Inspection 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 and Port 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 and Port Administration Center Owner	Maint and Constr Field Personnel	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 and Port Administration Center Owner	Personal Information Device 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 and Port Administration Center Owner	Personal Information Device 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 and Port Administration Center Owner	Personal Information Device 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 and Port Administration Center Supplier	Border and Port 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 Administration Center Operator	Border and Port Administration Center	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.
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 Manager	Border Inspection System Operator	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.
Border Inspection System Operator	Border Inspection System	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.
Border Inspection System Owner	Border and Port 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 and Port 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 System Owner	Border and Port 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 Administration Center Operator	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	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	Connected Vehicle Roadside 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	Connected Vehicle Roadside Equipment Operator	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	Connected Vehicle Roadside 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	Connected Vehicle Roadside 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	Light 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	Light 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	Light Vehicle OBE Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Border Inspection System Owner	Light 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	TIC Operator	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	Traffic 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 System Owner	Traffic Management Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Border Inspection System Owner	Traffic 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 System Owner	Traffic Operations Personnel	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	Transportation Information 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	Transportation Information Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Border Inspection System Owner	Transportation Information 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 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.
Connected Vehicle Roadside Equipment Maintainer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside Equipment Operator	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.
Connected Vehicle Roadside Equipment Operator	Connected Vehicle Roadside 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.
Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Border Inspection System Operator	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.
Connected Vehicle Roadside Equipment Owner	Border Inspection System Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Light 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.
Connected Vehicle Roadside Equipment Owner	Light 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.
Connected Vehicle Roadside Equipment Owner	Light Vehicle OBE Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Connected Vehicle Roadside Equipment Owner	Light 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.
Connected Vehicle Roadside Equipment Owner	Traffic 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.
Connected Vehicle Roadside Equipment Owner	Traffic Management Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Connected Vehicle Roadside Equipment Owner	Traffic 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.
Connected Vehicle Roadside Equipment Owner	Traffic Operations Personnel	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.
Connected Vehicle Roadside Equipment Supplier	Connected Vehicle Roadside 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.
Light Vehicle Driver	Light 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.
Light Vehicle OBE Maintainer	Light 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.
Light Vehicle OBE Manager	Light 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.
Light Vehicle OBE Manager	Light 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.
Light 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.
Light Vehicle OBE Owner	Border Inspection System Operator	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.
Light 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.
Light 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.
Light Vehicle OBE Owner	Connected Vehicle Roadside 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.
Light Vehicle OBE Owner	Connected Vehicle Roadside Equipment Operator	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.
Light Vehicle OBE Owner	Connected Vehicle Roadside 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.
Light Vehicle OBE Owner	Connected Vehicle Roadside 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.
Light Vehicle OBE Owner	Light 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.
Light Vehicle OBE Owner	Light 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.
Light Vehicle OBE Supplier	Light 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.
Maint and Constr Field Personnel	Personal Information Device	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.
Personal Information Device Maintainer	Personal Information Device	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.
Personal Information Device Manager	Maint and Constr Field Personnel	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.
Personal Information Device Manager	Personal Information Device	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.
Personal Information Device Owner	Border and Port 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.
Personal Information Device Owner	Border and Port 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.
Personal Information Device Owner	Border and Port 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.
Personal Information Device Owner	Border Inspection Administration Center Operator	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.
Personal Information Device Owner	Personal Information Device 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.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
TIC Operator	Transportation Information Center	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.
Traffic Management Center Maintainer	Traffic 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.
Traffic Management Center Manager	Traffic 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.
Traffic Management Center Manager	Traffic Operations Personnel	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.
Traffic Management Center Owner	Traffic 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.
Traffic Management Center Owner	Traffic 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.
Traffic Management Center Supplier	Traffic 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.
Traffic Operations Personnel	Traffic Management Center	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.
Transportation Information Center Maintainer	Transportation Information 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.
Transportation Information Center Manager	TIC Operator	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.
Transportation Information Center Manager	Transportation Information 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.
Transportation Information Center Owner	Transportation Information 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.
Transportation Information Center Owner	Transportation Information 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.
Transportation Information Center Supplier	Transportation Information 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.
Traveler	Traveler Card	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.
Traveler Card Maintainer	Traveler Card	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.
Traveler Card Manager	Traveler	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.
Traveler Card Manager	Traveler Card	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.
Traveler Card 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.
Traveler Card Owner	Border Inspection System Operator	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.
Traveler Card 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.
Traveler Card 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.
Traveler Card Owner	Light 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.
Traveler Card Owner	Light 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.
Traveler Card Owner	Light 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.
Traveler Card Owner	Light 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.
Traveler Card Owner	Traveler Card 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.
Traveler Card Owner	Traveler Card Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Traveler Card Supplier	Traveler Card 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 Object	Functional Object	PSpec Number	PSpec Name
Border and Port Administration Center	Border Inspection Administration	2.8.4.1	Manage Registration For Border Inspection
		2.8.4.2	Perform Border Inspection Pre-Processing
		2.8.4.3	Manage Border Inspection
Border Inspection System	Border Inspection	2.8.4.4	Perform Border Inspection
Border Inspection System	Border Inspection	2.8.4.5	Manage Border Area Security and Traffic
Connected Vehicle Roadside Equipment	RSE Border Management	1.1.2.6	Process Collected Vehicle Safety Data
		1.1.6	Collect Vehicle Traffic Surveillance Data
		2.3.9	Process Commercial Vehicle Roadside Messages
		2.8.4.6	Exchange Border Clearance Roadside Information
	RSE Traveler Information Communications	1.1.1.6	Collect Vehicle Roadside Safety Data
		1.1.2.6	Process Collected Vehicle Safety Data
		1.2.7.4	Process In-vehicle Signage Data
		1.2.7.7	Process Vehicle Safety and Environmental Data for Output
		1.5.10	Collect Vehicle Emissions Messages
		2.8.4.6	Exchange Border Clearance Roadside Information
		6.7.3.3	Provide Short Range Traveler Information
		9.2.3.8	Collect Connected Vehicle Field Equipment Status
		9.3.3.5	Manage Speeds at Roadside
Light Vehicle OBE	Light Vehicle Border Crossing Support	6.7.5.1	Get Light Vehicle Driver Personal Request
		6.7.5.2	Provide Light Vehicle Driver with Personal Travel Information
		6.7.5.3	Provide Light Vehicle Driver Information Interface
Personal Information Device	Personal Trip Planning and Route Guidance	6.8.1.1.1	Determine Personal Portable Device Guidance Method
		6.8.1.1.2	Provide Personal Portable Device Dynamic Guidance
		6.8.1.1.3	Provide Personal Portable Device Autonomous Guidance
		6.8.1.2	Provide Personal Portable Device Guidance Interface
		6.8.3.1	Get Traveler Personal Request
		6.8.3.2	Provide Traveler with Personal Travel Information
		6.8.3.3	Provide Traveler Personal Interface
		6.8.3.5	Provide Traveler Transit Services Interface
		7.5.3	Provide Personal Payment Device Interface
Traffic Management Center	TMC Basic Surveillance	1.1.2.1	Process Traffic Data for Storage
		1.1.2.2	Process Traffic Data
		1.1.2.3	Update Data Source Static Data
		1.1.2.5	Process Vehicle Situation Data
		1.1.2.8	Process Roadway Environmental Data
		1.1.3	Generate Predictive Traffic Model
		1.1.4.1	Retrieve Traffic Data
		1.1.4.2	Provide Traffic Operations Personnel Traffic Data Interface
		1.1.5	Exchange Data with Other Traffic Centers
		1.2.6.1	Maintain Traffic and Sensor Static Data
		1.2.8	Collect Traffic Field Equipment Fault Data
		1.3.1.1	Analyze Traffic Data for Incidents
		1.3.2.1	Store Possible Incident Data
		1.3.2.5	Provide Current Incidents Store Interface
		1.3.2.6	Manage Traffic Routing
		1.3.4.2	Provide Traffic Operations Personnel Incident Interface
		1.3.4.5	Process Video Data
Transportation Information Center	TIC Data Collection	6.2.1	Collect Misc Traveler Information
		6.2.2	Collect Traffic Data
		6.2.3	Collect Transit Operations Data
		6.2.4	Collect Multimodal Data
		6.2.5	Collect Situation and Sensor Data From Vehicles
		6.2.6	Collect Emergency Traveler Data
		6.5.4	Process Travel Services Provider Data
		6.6.2.3	Provide Route Segment Data for Other Areas
		7.4.2	Collect Price Data for Traveler Information Use

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
Border and Port Administration Center	Center	'Border and Port Administration Center' represents back-office systems and databases run by domestic and foreign governmental agencies responsible for the regulation of trade, and the enforcement of customs and immigration laws. These agencies include U.S. Department of Homeland Security (DHS) and its counterparts in Canada and Mexico. DHS includes components like Customs and Border Protection (CBP), Immigration and Customs Enforcement (ICE), and Transportation Security Administration (TSA). Other agencies include the Maritime Adiministration, Coast Guard, and Port Authorities for ports and secondary trade agencies (e.g., U.S. Food and Drug Administration, U.S. Department of Agriculture, other USDOT departments, etc.), and agencies from other trading nations. The systems they manage coordinate activities related to land border crossings and ports. These systems support import/export cargo processing and enforcement operations at the port of entry, including programs such as FAST, Automated Commercial Environment (ACE), Nexus (Canada), SENTRI (Mexico), and US-VISIT.
Border Inspection System	Field	'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events.
Connected Vehicle Roadside Equipment	Field	'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Light Vehicle Driver	Vehicle	The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle.
Light Vehicle OBE	Vehicle	The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Personal Information Device	Personal	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Traffic Management Center	Center	The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transportation Information Center	Center	The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Traveler Card	Personal	The 'Traveler Card' stores traveler identification information, including biometric information, that can be used in trusted traveler programs to expedite clearance through security checkpoints at borders or security-critical areas.

Includes Functional Objects:

Functional Object	Description	Physical Object
Border Inspection	'Border Inspection' manages and supports primary and secondary inspections at the border crossing.	Border Inspection System
Border Inspection Administration	'Border Inspection Administration' performs administrative functions relating to the inspection of goods and vehicles at the border.	Border and Port Administration Center
Light Vehicle Border Crossing Support	'Vehicle Border Crossing Support' uses connected vehicle technology to exchange traveler credentials with border systems to support expedited clearance through international borders.	Light Vehicle OBE
Personal Trip Planning and Route Guidance	'Personal Trip Planning and Route Guidance' provides a personalized trip plan to the traveler. The trip plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. Coordination may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including systems that provide a basic trip plan to the traveler as well as more sophisticated systems that can provide transition by transition guidance to the traveler along a multi-modal route with transfers. Devices represented by this functional object include desktop computers at home, work, or at major trip generation sites, plus personal devices such as tablets and smart phones.	Personal Information Device
RSE Border Management	'RSE Border Management' supports border operations, providing functions that measure border wait times and provide wait times and other traveler information to approaching vehicles. Short range communications with vehicles and associated equipment supports collection of traveler, vehicle, and cargo information and credentials.	Connected Vehicle Roadside Equipment
RSE Traveler Information Communications	'RSE Traveler Information Communications' includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles.	Connected Vehicle Roadside Equipment
TIC Data Collection	'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, pathway information, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers.	Transportation Information Center
TMC Basic Surveillance	'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers.	Traffic Management Center
Vehicle Basic Safety Communication	'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc.	Vehicle
Vehicle Traveler Information Reception	'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information.	Vehicle

Includes Information Flows:

Information Flow	Description
border card data	Personal identification data from ID cards used by travelers at border crossings.
border crossing status information	Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border
border security input	Information regarding security related events occurring at the border.
border wait times data	Measure of current, actual, or predicted wait time at border. Measurement provided by vehicle type, lane, and type of lane (e.g., NEXUS vs. regular).
expedited traveler registration	Application for expedited traveler programs, such as NEXUS, Global Entry, Viajero Confiable, etc. Includes electronic filing of forms and associated payment. Applications for commercial vehicle driver may be completed through CVO services (see 'expedited clearance registration' flow).
expedited traveler registration status	Status of expedited traveler registration.
light vehicle driver input	Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
light vehicle driver updates	Information provided to the light vehicle driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
local border wait times	Current border wait time calculated by the RSE based on data collected from passing connected vehicles.
local traveler information	Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information.
traveler border clearance status	Information indicating whether border clearance has been granted and instructions if additional processing is required.
traveler credentials	Traveler identification, including trusted traveler program information, if applicable.
traveler personal information	This flow includes biometric and other data to allow recognition of travelers.
vehicle location and motion for surveillance	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle signage data	In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings).
vehicle signage local data	Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need		Functional Object	Requirement

Related Sources

Document Name	Version	Publication Date
None

Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Border and Port Administration Center
Border Inspection System
Connected Vehicle Roadside Equipment
Light Vehicle OBE
Personal Information Device
Traffic Management Center
Transportation Information Center
Traveler Card

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
Source	Destination	Information Flow	Basis	Basis	Basis
Border and Port Administration Center	Border Inspection System	traveler personal information	Moderate	High	Moderate
Border and Port Administration Center	Border Inspection System	traveler personal information	This flow includes PII of travelers. If it also includes the necessary challenge questions and response to impersonate that individual, it could be classified as a HIGH.	False data here could allow someone to impersonate someone else. This may lead to an unauthorized person entering the country.	The system must have an acknowledgement of a missed message. If this data is not received, the traveler will have to identify themselves through the traditional methods, such as a passport.
Border and Port Administration Center	Personal Information Device	expedited traveler registration status	Moderate	Moderate	Moderate
Border and Port Administration Center	Personal Information Device	expedited traveler registration status	Contains PII to support the application.	Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention.	Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention.
Border Inspection System	Border and Port Administration Center	border security input	Moderate	Moderate	Low
Border Inspection System	Border and Port Administration Center	border security input	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	Connected Vehicle Roadside Equipment	vehicle signage local data	Low	Moderate	Moderate
Border Inspection System	Connected Vehicle Roadside Equipment	vehicle signage local data	This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone.	These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means.	These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues.
Border Inspection System	Light Vehicle OBE	traveler border clearance status	Low	High	Moderate
Border Inspection System	Light Vehicle OBE	traveler border clearance status	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	Traffic Management Center	border wait times data	Not Applicable	Moderate	Low
Border Inspection System	Traffic Management Center	border wait times data	This is directly observable data.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this information is used to determine how thoroughly to investigate passing vehicles (ie. When it is busy vehicles are subject to less thorough inspection) this flow could be bumped up to a MEDIUM. DISC: Original V2I analysis classified this as LOW.	If this information is not fully up to date, or is missing, the system can still operate properly.
Border Inspection System	Transportation Information Center	border crossing status information	Low	Moderate	Low
Border Inspection System	Transportation Information Center	border crossing status information	This is all public information which is mostly available through public information channels.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. A flaw in this information will not cause much, if any harm. A higher integrity will allow this information to be of more use, but is not required for security reasons. DISC: Original V2I analysis classified this as LOW.	Without this information there will not be any direct problem. A higher availability will allow this information to be more useful; however it is not a requirement.
Connected Vehicle Roadside Equipment	Border Inspection System	local border wait times	Not Applicable	Moderate	Low
Connected Vehicle Roadside Equipment	Border Inspection System	local border wait times	This is directly observable data.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this information is used to determine how thoroughly to investigate passing vehicles (ie. When it is busy vehicles are subject to less thorough inspection) this flow could be bumped up to a MEDIUM. DISC: Original V2I analysis classified this as LOW.	If this information is not fully up to date, or is missing, the system can still operate properly.
Connected Vehicle Roadside Equipment	Traffic Management Center	local border wait times	Not Applicable	Moderate	Low
Connected Vehicle Roadside Equipment	Traffic Management Center	local border wait times	This is directly observable data	If this information is used to determine how thoroughly to investigate passing vehicles (ie. When it is busy vehicles are subject to less thorough inspection) this flow could be bumped up to a MEDIUM.	If this information is not fully up to date, or is missing, the system can still operate properly.
Light Vehicle Driver	Light Vehicle OBE	light vehicle driver input	Moderate	High	High
Light Vehicle Driver	Light Vehicle OBE	light vehicle driver input	Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy.	Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner	Commands must always be able to be given or the driver has no control.
Light Vehicle OBE	Border Inspection System	traveler credentials	High	Moderate	Moderate
Light Vehicle OBE	Border Inspection System	traveler credentials	This contains sensitive information on multiple individuals that could potentially be used to impersonate them or steal their identity. If anyone other than the intended parties can view this information it could lead to a large financial cost for many individuals.	The identity reported by this transmission might not actually be the individual in the vehicle. If a border officer can add information that gets sent to the BIS, then the integrity requirement could potentially be raised to HIGH as this flow might be used to make law enforcement decisions involving the use of force. We assume that if this information is added it is added at the BIS rather than the RSE, so this integrity requirement on this flow is MEDIUM.	Assuming it is still possible to validate travelers in the way that is currently possible this is acceptable as a MEDIUM. If when this system is down, the border cannot process any individuals then this would need to be a HIGH because completely shutting down the border could cause significant financial problems.
Light Vehicle OBE	Light Vehicle Driver	light vehicle driver updates	Not Applicable	Moderate	Moderate
Light Vehicle OBE	Light Vehicle Driver	light vehicle driver updates	This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the driver, then the system has not operated correctly.
Personal Information Device	Border and Port Administration Center	expedited traveler registration	Moderate	Moderate	Moderate
Personal Information Device	Border and Port Administration Center	expedited traveler registration	Contains PII to support the application.	Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention.	Must be accurate and timely or the border clearance will not be expedited and will not function without other intervention.
Traveler Card	Border Inspection System	border card data	High	Moderate	High
Traveler Card	Border Inspection System	border card data	This data contains all of the information needed to identify a traveler. If a criminal was able to view this data, it could be used to impersonate the traveler.	The identity reported by this transmission might not actually be the individual in the vehicle. As such there is no way that this could have HIGH integrity, and is why other sources must be used to ensure that this individual is who they are claiming to be.	If the traveler card data was not delivered to the RSE by Vehicle OBE this will be the last chance for the card to be validated. If it fails, the traveler will likely be turned away from the border and not be allowed to cross. This would be equivalent to arriving at the border today without a passport, however it would be the system’s fault, not the user’s. Since there is no alternate way for an individual to prove their identity, this could break the whole system and should not happen.
Traveler Card	Light Vehicle OBE	border card data	High	Moderate	High
Traveler Card	Light Vehicle OBE	border card data	This data contains all of the information needed to identify a traveler. If a criminal was able to view this data, it could be used to impersonate the traveler.	The identity reported by this transmission might not actually be the individual in the vehicle. As such there is no way that this could have HIGH integrity, and is why other sources must be used to ensure that this individual is who they are claiming to be.	If the traveler card data was not delivered to the RSE by Vehicle OBE this will be the last chance for the card to be validated. If it fails, the traveler will likely be turned away from the border and not be allowed to cross. This would be equivalent to arriving at the border today without a passport, however it would be the system’s fault, not the user’s. Since there is no alternate way for an individual to prove their identity, this could break the whole system and should not happen.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

Name	Title	Physical Object
CTI 4001 RSU	Roadside Unit (RSU) Standard	Connected Vehicle Roadside Equipment
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	Traffic Management Center

System Requirements

No System Requirements