Parent Service Package: TM02
< < TM01.3 : TM02.1 : TM02.2 > >

TM02.1: Wide Area Wireless Communications

Use Wide Area Wireless communications to collect traffic information from participating vehicles.

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
Basic Vehicle Developer	Basic Vehicle	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.
Basic Vehicle Developer	Vehicle 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.
Payment Administration Center Developer	Payment 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.
Payment Administration Center 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.
Payment Administration Center 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.
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.
Traffic Management Center 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.
Transit Management Center 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.
Transit Management Center Developer	Transit 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.
Transit Management Center 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.
Transportation Information Center 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.
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.
Transportation Information Center Developer	Vehicle 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.
Vehicle 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.
Vehicle Developer	Vehicle	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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider System Developer	Wireless Communications Provider 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.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Basic Vehicle Installer	Basic Vehicle	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.
Basic Vehicle Owner	Basic Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Basic Vehicle Owner	Basic Vehicle 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.
Payment Administration Center Installer	Payment 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.
Payment Administration Center Owner	Payment Administration Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Payment Administration Center Owner	Payment 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.
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.
Transit Management Center Installer	Transit 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.
Transit Management Center Owner	Transit Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transit Management Center Owner	Transit 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.
Vehicle Installer	Vehicle	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.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle 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.
Wireless Communications Provider System Installer	Wireless Communications Provider 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.
Wireless Communications Provider System Owner	Wireless Communications Provider System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Wireless Communications Provider System Owner	Wireless Communications Provider 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.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Basic Vehicle Maintainer	Basic Vehicle	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.
Basic Vehicle Manager	Basic Vehicle	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.
Basic Vehicle Manager	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.
Basic Vehicle Owner	Basic Vehicle 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.
Basic Vehicle Owner	Basic Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Basic Vehicle Owner	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.
Basic Vehicle Owner	Driver	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Basic Vehicle Owner	Vehicle 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.
Basic Vehicle Owner	Vehicle 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.
Basic Vehicle Owner	Vehicle User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Basic Vehicle Supplier	Basic Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Driver	Basic Vehicle	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.
Driver	Vehicle	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.
Payment Administration Center Maintainer	Payment 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.
Payment Administration Center Manager	Payment 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.
Payment Administration Center Manager	Payment Administrator	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.
Payment Administration Center Owner	Payment 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.
Payment Administration Center Owner	Payment 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center 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.
Payment Administration Center Supplier	Payment 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.
Payment Administrator	Payment 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.
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	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.
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 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.
Traffic Management Center Owner	Transportation Information 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.
Traffic Management Center 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.
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.
Transit Management Center Maintainer	Transit 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.
Transit Management Center Manager	Transit 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.
Transit Management Center Manager	Transit 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center Owner	Transit 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.
Transit Management Center Owner	Transit 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center Supplier	Transit 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.
Transit Operations Personnel	Transit 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	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.
Transportation Information Center 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.
Transportation Information Center Owner	Traffic 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.
Transportation Information Center 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.
Transportation Information Center 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.
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 Owner	Vehicle 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.
Transportation Information Center Owner	Vehicle 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.
Transportation Information Center Owner	Vehicle User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
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.
Vehicle Maintainer	Vehicle	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.
Vehicle Manager	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.
Vehicle Manager	Vehicle	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.
Vehicle 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.
Vehicle 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.
Vehicle Owner	Transportation Information 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.
Vehicle 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.
Vehicle Owner	Vehicle 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.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Wireless Communications Provider System Maintainer	Wireless Communications Provider 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.
Wireless Communications Provider System Manager	Wireless Communications Provider 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.
Wireless Communications Provider System Manager	Wireless Communications Provider 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.
Wireless Communications Provider System Operator	Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider 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.
Wireless Communications Provider System Owner	Wireless Communications Provider 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.
Wireless Communications Provider System Owner	Wireless Communications Provider 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.
Wireless Communications Provider System Supplier	Wireless Communications Provider 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.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Traffic Management Center	TMC Situation Data Management	1.1.2.5	Process Vehicle Situation Data
Transportation Information Center	TIC Situation Data Management	6.2.1	Collect Misc Traveler Information
		6.2.2	Collect Traffic Data
		6.2.5	Collect Situation and Sensor Data From Vehicles
		6.5.8	Provide Operational Data for Other Centers
		6.5.9	Provide Traveler Alert Interface
		6.9	Manage Traveler Info Archive Data
Vehicle	Vehicle Basic Safety Communication	3.1.1	Produce Collision and Crash Avoidance Data
		3.1.3	Process Vehicle On-board Data
		3.1.4	Communicate with Remote Vehicles
		3.1.6	Provide Vehicle Acceleration and Deceleration Inputs
		3.2.3.2	Manage Platoon Following
		3.2.3.3	Process Data for Vehicle Actuators
		3.2.3.5.1	Process General Vehicle Sensor Data
		3.2.4	Process Sensor Data for Automatic Vehicle Operations
		6.7.1.3	Process Vehicle Location Data
		6.7.1.4	Update Vehicle Navigable Map Database
		6.7.3.2	Provide Driver Information Interface
	Vehicle Situation Data Monitoring	3.1.3	Process Vehicle On-board Data

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
Basic Vehicle	Vehicle	'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Payment Administration Center	Center	The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
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.
Transit Management Center	Center	The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
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.
Vehicle	Vehicle	This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Wireless Communications Provider System	Center	The 'Wireless Communications Provider System' represents the systems used by wireless communications providers to provide data and voice services that collectively serve billions of mobile users around the world. As they serve their customers, these providers collect location information from their mobile customers as they use communications services while they traverse the transportation network. This information may be shared with transportation providers, in aggregate and without personal information, to provide a rich data source that may be used in conjunction with other data to monitor transportation network use and performance. Use this physical object where the relationship with the communications provider is limited to use of service provider-derived transportation network performance data. Where wireless communications services are purchased and used to support wireless interfaces included in an ITS architecture, see 'ITS Communications Equipment', which can represent use of purchased communications services as part of an overall ITS communications network.

Includes Functional Objects:

Functional Object	Description	Physical Object
TIC Situation Data Management	'TIC Situation Data Management' manages connected vehicle situation data collection, quality controls, filtering, aggregation, and storage. Through this process, raw data reported by connected vehicles are transformed into information products that can be accessed and used to support transportation operations and traveler information.	Transportation Information Center
TMC Situation Data Management	'TMC Situation Data Management' collects, assimilates, and disseminates vehicle probe data collected from roadside short range communications equipment and centers controlling transit vehicles, toll collection points, and route-guided vehicles. It estimates traffic and road conditions based on the aggregated probe data and disseminates this information 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 Situation Data Monitoring	'Vehicle Situation Data Monitoring' is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this functional object supports collection of data for areas remote from RSEs or other communications infrastructure.	Vehicle

Includes Information Flows:

Information Flow	Description
comm-derived travel performance data	Data that can be used to derive travel time data and other transportation performance measures. Data provided may be raw IDs, locations, and timestamps, derived link travel times, speeds, or other data that has been collected and derived by a communications provider from its mobile customers.
host vehicle status	Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment.
road network conditions	Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
road network traffic situation data	Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions.
toll probe data	Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
transit probe data	Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
vehicle situation data	This flow represents vehicle snapshots that may be provided by the vehicle to support traffic and environmental conditions monitoring. Snapshots are collected by the vehicle for specific events (e.g., when a sensor exceeds a threshold) or periodically and reported based on control parameters when communications is available. Traffic-related data includes snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control events. Environmental data may include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected.
vehicle situation data parameters	A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval.

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
Basic Vehicle
Payment Administration Center	Low	Moderate	Low	Class 1
Traffic Management Center	Moderate	Moderate	Moderate	Class 2
Transit Management Center	Low	Moderate	Low	Class 1
Transportation Information Center	Moderate	Moderate	Moderate	Class 2
Vehicle	Moderate	Moderate	Moderate	Class 2
Wireless Communications Provider System	Not Applicable	Moderate	Low	Class 1

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
Basic Vehicle	Vehicle	host vehicle status	Low	Moderate	High
Basic Vehicle	Vehicle	host vehicle status	Unlikely that this includes any information that could be used against the originator.	This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly.	Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety.
Payment Administration Center	Traffic Management Center	toll probe data	Low	Moderate	Low
Payment Administration Center	Traffic Management Center	toll probe data	As this is aggregate information that will be used for a public information product, there is little reason to conceal it.	This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money.	There are many sources of traffic data, it is unlikely that this is the only one. While loss of this flow would degrade overall travel time quality, it would not eliminate that metric and would have a widespread but minor effect.
Payment Administration Center	Transportation Information Center	toll probe data	Low	Moderate	Low
Payment Administration Center	Transportation Information Center	toll probe data	As this is aggregate information that will be used for a public information product, there is little reason to conceal it.	This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money.	There are many sources of traffic data, it is unlikely that this is the only one. While loss of this flow would degrade overall travel time quality, it would not eliminate that metric and would have a widespread but minor effect.
Traffic Management Center	Transportation Information Center	road network conditions	Low	Moderate	Moderate
Traffic Management Center	Transportation Information Center	road network conditions	No harm should come from seeing this data, as it is eventually intended for public consumption.	While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally.	Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Transit Management Center	Traffic Management Center	transit probe data	Low	Moderate	Low
Transit Management Center	Traffic Management Center	transit probe data	As this is aggregate information that will be used for a public information product, there is little reason to conceal it.	This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money.	There are many sources of traffic data, it is unlikely that this is the only one. Loss of this flow may degrade overall travel time quality (unclear, as transit travel times are notoriously different from passenger vehicle travel times), it would not eliminate that metric and would have a widespread but minor effect.
Transit Management Center	Transportation Information Center	transit probe data	Low	Moderate	Low
Transit Management Center	Transportation Information Center	transit probe data	As this is aggregate information that will be used for a public information product, there is little reason to conceal it.	This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money.	There are many sources of traffic data, it is unlikely that this is the only one. Loss of this flow may degrade overall travel time quality (unclear, as transit travel times are notoriously different from passenger vehicle travel times), it would not eliminate that metric and would have a widespread but minor effect.
Transportation Information Center	Traffic Management Center	road network traffic situation data	Moderate	Moderate	Moderate
Transportation Information Center	Traffic Management Center	road network traffic situation data	The data this is based on is not encrypted, but aggregated messages may have more privacy implications than individual ones.	Should be limited effect if this data is incorrect or compromised, as there should be other mechanisms in place to validate it.	This information is used as supplemental information. It should operate correctly if not every single message is received.
Transportation Information Center	Vehicle	vehicle situation data parameters	Low	Moderate	Moderate
Transportation Information Center	Vehicle	vehicle situation data parameters	This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation.	Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data	Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not
Vehicle	Transportation Information Center	vehicle situation data	Moderate	Moderate	Low
Vehicle	Transportation Information Center	vehicle situation data	Might be able to link multiple snapshots together and compromise some element of driver/traveler privacy.	Event driven data can be used for various mobility monitoring applications, and as operational decisions may be made based on mobility conditions, this data's accuracy should be preserved or decisions may not align with real situations.	While desireable, in most application contexts the provision of a single vehicle's data through this flow is not critical.
Wireless Communications Provider System	Traffic Management Center	comm-derived travel performance data	Not Applicable	Moderate	Low
Wireless Communications Provider System	Traffic Management Center	comm-derived travel performance data	This data is intended for public use and is presumed to already be sanitized.	Data should be correct and available, but this is one of many sources of travel-time data. Installations not relying on this source as their primary means for acquiring travel time data could lower this to LOW.	Data should be correct and available, but this is one of many sources of travel-time data. Installations relying on this source as their primary means for acquiring travel time data should elevate this to MODERATE.
Wireless Communications Provider System	Transportation Information Center	comm-derived travel performance data	Not Applicable	Moderate	Low
Wireless Communications Provider System	Transportation Information Center	comm-derived travel performance data	This data is intended for public use and is presumed to already be sanitized.	Data should be correct and available, but this is one of many sources of travel-time data. Installations not relying on this source as their primary means for acquiring travel time data could lower this to LOW.	Data should be correct and available, but this is one of many sources of travel-time data. Installations relying on this source as their primary means for acquiring travel time data should elevate this to MODERATE.

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. 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.

System Requirements

No System Requirements