< < SU04 : SU05 : SU06 > >

SU05: Location and Time

This service package identifies the external systems and interfaces that provide accurate location and time to intelligent transportation system devices and systems.

Relevant Regions: Australia, Canada, European Union, and United States

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.
Center Developer	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.
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	Personal 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	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.
Data Distribution System Developer	Data Distribution 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.
Field Developer	Field	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.
Location and Time Data Source Developer	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.
Location and Time Data Source 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.
Location and Time Data Source Developer	Field 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.
Location and Time Data Source Developer	Location and Time Data Source	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.
Location and Time Data Source Developer	Personal 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.
Location and Time Data Source 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.
Network Time Source Developer	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.
Network Time Source 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.
Network Time Source Developer	Data Distribution 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.
Network Time Source Developer	Field 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.
Network Time Source Developer	Network Time Source	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.
Network Time Source Developer	Service Monitor 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.
Personal Developer	Personal	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.
Position Corrections Source 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.
Position Corrections Source Developer	Position Corrections Source	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.
Service Monitor System Developer	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.
Service Monitor 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.
Service Monitor System Developer	Data Distribution 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.
Service Monitor System Developer	Field 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.
Service Monitor System Developer	Service Monitor 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.
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.

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.
Center Installer	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.
Center Owner	Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Center Owner	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.
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.
Data Distribution System Installer	Data Distribution 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.
Data Distribution System Owner	Data Distribution System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Data Distribution System Owner	Data Distribution 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.
Field Installer	Field	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.
Field Owner	Field Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Field Owner	Field 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.
Location and Time Data Source Installer	Location and Time Data Source	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.
Location and Time Data Source Owner	Location and Time Data Source Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Location and Time Data Source Owner	Location and Time Data Source 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.
Network Time Source Installer	Network Time Source	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.
Network Time Source Owner	Network Time Source Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Network Time Source Owner	Network Time Source 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 Installer	Personal	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 Owner	Personal Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Owner	Personal 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.
Position Corrections Source Installer	Position Corrections Source	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.
Position Corrections Source Owner	Position Corrections Source Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Position Corrections Source Owner	Position Corrections Source 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.
Service Monitor System Installer	Service Monitor 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.
Service Monitor System Owner	Service Monitor System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Service Monitor System Owner	Service Monitor 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.
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.

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 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	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.
Center Maintainer	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.
Center Manager	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.
Center Owner	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.
Center Owner	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.
Center Supplier	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.
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 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	Personal 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	Personal 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	Personal 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	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.
Connected Vehicle Roadside Equipment Owner	Vehicle 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	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.
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.
Data Distribution System Maintainer	Data Distribution 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.
Data Distribution System Manager	Data Distribution 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.
Data Distribution System Owner	Data Distribution 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.
Data Distribution System Owner	Data Distribution 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.
Data Distribution System Supplier	Data Distribution 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.
Field Maintainer	Field	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.
Field Manager	Field	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.
Field Owner	Field 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.
Field Owner	Field Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Field Supplier	Field Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Location and Time Data Source Maintainer	Location and Time Data Source	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.
Location and Time Data Source Manager	Location and Time Data Source	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.
Location and Time Data Source Owner	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.
Location and Time Data Source Owner	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.
Location and Time Data Source 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.
Location and Time Data Source 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.
Location and Time Data Source Owner	Field 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.
Location and Time Data Source Owner	Field User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Location and Time Data Source Owner	Location and Time Data Source 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.
Location and Time Data Source Owner	Location and Time Data Source Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Location and Time Data Source Owner	Personal 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.
Location and Time Data Source Owner	Personal User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Location and Time Data Source 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.
Location and Time Data Source 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.
Location and Time Data Source Supplier	Location and Time Data Source Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Network Time Source Maintainer	Network Time Source	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.
Network Time Source Manager	Network Time Source	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.
Network Time Source Owner	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.
Network Time Source Owner	Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Network Time Source Owner	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.
Network Time Source 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.
Network Time Source Owner	Connected Vehicle Roadside Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Network Time Source 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.
Network Time Source Owner	Data Distribution 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.
Network Time Source Owner	Data Distribution System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Network Time Source Owner	Data Distribution 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.
Network Time Source Owner	Field 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.
Network Time Source Owner	Field Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Network Time Source Owner	Field User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Network Time Source Owner	Network Time Source 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.
Network Time Source Owner	Network Time Source Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Network Time Source Owner	Service Monitor 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.
Network Time Source Owner	Service Monitor 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.
Network Time Source Owner	Service Monitor System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Network Time Source Owner	Service Monitor 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.
Network Time Source Supplier	Network Time Source Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Personal Maintainer	Personal	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 Manager	Personal	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 Owner	Personal 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 Owner	Personal 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 Supplier	Personal Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Position Corrections Source Maintainer	Position Corrections Source	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.
Position Corrections Source Manager	Position Corrections Source	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.
Position Corrections Source 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.
Position Corrections Source Owner	Connected Vehicle Roadside Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Position Corrections Source 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.
Position Corrections Source Owner	Position Corrections Source 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.
Position Corrections Source Owner	Position Corrections Source Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Position Corrections Source Supplier	Position Corrections Source Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Service Monitor System Maintainer	Service Monitor 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.
Service Monitor System Manager	Service Monitor 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.
Service Monitor System Manager	Service Monitor 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.
Service Monitor System Operator	Service Monitor 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.
Service Monitor System Owner	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.
Service Monitor System Owner	Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Service Monitor System Owner	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.
Service Monitor 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.
Service Monitor System Owner	Connected Vehicle Roadside Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Service Monitor 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.
Service Monitor System Owner	Data Distribution 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.
Service Monitor System Owner	Data Distribution System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Service Monitor System Owner	Data Distribution 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.
Service Monitor System Owner	Field 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.
Service Monitor System Owner	Field Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Service Monitor System Owner	Field User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Service Monitor System Owner	Service Monitor 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.
Service Monitor System Owner	Service Monitor 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.
Service Monitor System Supplier	Service Monitor 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.
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	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	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.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Center	Center Support Services	10.6.1.3	Support Center Location and Time Services
Connected Vehicle Roadside Equipment	RSE Position Correction Support	1.2.7.7	Process Vehicle Safety and Environmental Data for Output
Connected Vehicle Roadside Equipment	RSE Support Services	10.6.2.1	Support Roadway System Communications
Data Distribution System	DDS Support Services	10.6.1.4	Support Data Distribution Location and Time Services
Field	Field Time Management	10.6.2.2	Provide Field Data Sharing Services
Personal	Personal Location Determination	6.8.1.4	Update Traveler Navigable Map Database
Personal	Personal Location Determination	6.8.1.6	Process Personal Device Location Data
Service Monitor System	SM Time Synchronization	10.4.1	Maintain Time Synchronization
Service Monitor System	SM Time Synchronization	10.4.2	Provide Time Support Services Operator Interface
Vehicle	Vehicle Location Determination	6.7.1.3	Process Vehicle Location Data
Vehicle	Vehicle Location Determination	6.7.1.4	Update Vehicle Navigable Map Database

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.
Center	Center	This general physical object is used to model core capabilities that are common to any center.
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.
Data Distribution System	Support	The 'Data Distribution System' collects, processes, and distributes ITS data, connecting data producers with data consumers and facilitating data exchange.
Field	Field	This general physical object is used to model core capabilities that are common to any piece of field equipment.
Location and Time Data Source	ITS	The 'Location and Time Data Source' provides accurate position information. While a Global Positioning System (GPS) Receiver is the most common implementation, this physical object represents any technology that provides a position fix in three dimensions and time with sufficient accuracy.
Network Time Source	Support	The 'Network Time Source' represents the external time source the Connected Vehicle Service Monitor System uses as the basis for time. This is likely implemented as a Stratum-2 Network Time Server that is 2 steps removed from a basic time source (e.g., atomic clock).
Personal	Personal	The 'Personal' physical object is used to model core capabilities that are common to more than one physical object in the 'Personal' class. It provides the general executive, management, and utility functions that may be shared by different types of personal devices.
Position Corrections Source	Support	The 'Position Corrections Source' represents the external source of land-based position corrections that augment satellite-provided (e.g., GPS) positioning data.
Service Monitor System	Support	The 'Service Monitor System' represents one or more center-based systems that provide monitoring, management and control services necessary to other applications and/or devices operating within the Connected Vehicle Environment. These support services enable other applications to provide transportation services.
Service Monitor System Operator	Support	The 'Service Monitor System Operator' represents the person or people that monitor and manage the Service Monitor System.
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, 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.

Includes Functional Objects:

Functional Object	Description	Physical Object
Center Support Services	'Center Support Services' provides foundational functions that support data collection, management, location reference, timing, and data distribution. It maintains precise location and time information to support other services.	Center
DDS Support Services	'DDS Support Services' provides foundational functions that support data collection, management, timing, and data distribution. It coordinates with Support subsystems to maintain necessary registrations with respect to location and scope.	Data Distribution System
Field Time Management	'Field Time Management' provides foundational time keeping functionality that supports an accurate, synchronized time reference in ITS field equipment. It receives accurate time information from an external source and maintains a local time reference using an internal clock in between time synchronizations.	Field
Personal Location Determination	'Personal Location Determination' receives current location information and provides this information to other applications that use the location information to provide guidance and emergency notification services. It interfaces with and encapsulates positioning technology such as a GPS receiver that is embedded in the user's device.	Personal
RSE Position Correction Support	'RSE Position Correction Support' broadcasts differential positioning data to enable precise locations to be determined by passing vehicles, supporting Connected Vehicle applications that require highly accurate positioning. The differential positioning data may be calculated directly by a precisely located RSE that is operating as a reference station or received from an external reference station and relayed to passing vehicles.	Connected Vehicle Roadside Equipment
RSE Support Services	'RSE Support Services' provides foundational functions that support data collection, management, location reference, timing, and data distribution. It coordinates with Support subsystems to maintain necessary registrations with respect to location and scope. It maintains precise location and time information to support other services.	Connected Vehicle Roadside Equipment
SM Time Synchronization	'SM Time Synchronization' provides the functions necessary to receive accurate time from an external Network Time Server and provide that Coordinated Universal Time (UTC) as Time Local Form to other center systems and field devices.	Service Monitor System
Vehicle Location Determination	'Vehicle Location Determination' receives current location of the vehicle and provides this information to vehicle applications that use the location information to provide ITS services.	Vehicle

Includes Information Flows:

Information Flow	Description
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.
location and time	The current geographic location in three dimensions (latitude, longitude, elevation) and the current time.
location correction	Information provided to improve positional accuracy. These corrections allow a mobile GPS receiver, such as a GPS system in a connected vehicle, to achieve a greater absolute positional accuracy, compensating for errors that exist in satellite positioning.
position corrections	Ground based reference station positioning corrections
service monitor information presentation	Presentation of information to the System Monitoring Operator including current operational status of the System Monitoring function and the connected vehicle environment that is monitored.
service monitor operator input	User input from the SMS operator including requests to monitor current system operation and inputs to affect system operation.
time	Current time expressed in Universal Time Coordinated (UTC) format from a Stratum-2 time server.
time local form	Time local form includes UTC time synchronized with the external source in a format usable by connected vehicle center functions.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users;	Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
G. Promote efficient system management and operation;	Improve efficiency

Associated Objective Categories

Objective Category
Arterial Management: Traffic Monitoring and Data Collection
Arterial Management: Traffic Signal Management
Freeway Management: Transportation Management Centers
Safety: Vehicle Crashes and Fatalities
Transit Operations and Management: Demand Responsive Transit
Transit Operations and Management: Transit Signal Priority
Travel Weather Management: Signal Timing Plans

Associated Objectives and Performance Measures

Objective	Performance Measure
Decrease delay by X percent per year by increasing the use of queue jumping and automated vehicle location.	Travel time delay on routes with queue jumping and automated vehicle location in use.
Decrease system-wide signal delay on transit routes by X percent per year.	System-wide signalized stop delay on transit routes.
Field data collection is conducted either through floating car studies or other methods at least once every Y years on major signalized arterials and X years on minor signalized arterials.	Number of field data collection studies performed every Y and X years on major and minor signalized arterials, respectively.
Improve on-time pick-up of demand response transit passengers.	Demand response passenger pick-up on-time performance
Improve the operational efficiency of the demand response transit service in the region.	Operating expense per passenger mile
Improve the operational efficiency of the demand response transit service in the region.	Operating expense per passenger trip
Improve the operational efficiency of the demand response transit service in the region.	Passenger miles per vehicle
Improve the operational efficiency of the demand response transit service in the region.	Passenger trips per vehicle
Increase implementation of transit signal priority strategies on X number of routes (or X number of intersections) over the next Y years.	Number of transit routes/intersections equipped with transit signal priority capability.
Increase the hours of TMC operation and level of staffing by X percent by year Y.	Number of hours of TMC operation and number of staff serving the TMC.
Increase the number of intersections running in a coordinated, closed-loop, or adaptive system by X percent in Y years.	Number of intersections running in a coordinated, closed-loop, or adaptive system.
Increase the percent of regional transportation system monitored by the TMC for real-time performance.	Percent of regional transportation system monitored by the TMC for real-time performance.
Reduce crashes at intersections	Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections	Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections	Number of crashes and fatalities related to red-light running
Reduce crashes at railroad crossings	Number of crashes and fatalities at railroad crossings
Reduce crashes due to red-light running	Number of crashes and fatalities related to red-light running
Reduce crashes due to road weather conditions	Number of crashes and fatalities related to weather conditions
Reduce crashes due to unexpected congestion	Number of crashes and fatalities related to unexpected congestion
Reduce lane departure crashes	Number of crashes and fatalities related to inappropriate lane departure, crossing or merging
Reduce secondary crashes	Number of secondary crashes
Reduce the number of motorcyclist fatalities by X percent by year Y.	Number of motorcyclist fatalities
Reduce the number of pedestrian fatalities by X percent by year Y.	Number of pedestrian fatalities
Reduce the rate fatalities in the region by X percent by year Y.	Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the rate of severe injuries in the region by X percent by year Y.	Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y.	Total crashes per X VMT.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y.	Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y.	Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y.	Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y.	Total severe injuries per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y.	Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y.	Number of serious injuries
Special timing plans are available for use during freeway incidents, roadway construction activities, or other special events for X miles of arterials in the region by year Y.	Number of miles of arterials that have at least one special timing plan for incidents, construction, or events.
Special timing plans are available for use during inclement weather conditions for X miles of arterials in the region by year Y.	Number of miles of arterials that have at least one special timing plan for inclement weather events.
X percent of intersections in the region are equipped and operating with traffic signals that enable real-time monitoring and management of traffic flows by year Y.	Percent of intersections in the region equipped and operating with traffic signals that enable real-time monitoring and management of traffic flows.
X percent of major and minor arterials are equipped and operating with arterial link traffic data detection stations (appropriate technology) per Z distance by year Y.	Percent of major and minor arterials equipped and operating with arterial link traffic data detection stations (appropriate technology) per Z distance.
X percent of major and minor arterials are equipped and operating with closed circuit television (CCTV) cameras per Z distance by year Y.	Percent of major and minor arterials equipped and operating with closed circuit television (CCTV) cameras per Z distance.

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

Needs and Requirements

Need		Functional Object	Requirement
01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.	Center Support Services	01	The Center shall acquire time sync data from an external Stratum-2 time source.
		Center Support Services	02	The Center shall use the externally acquired time sync data to maintain its internal clocks.
		DDS Support Services	04	The data support center shall obtain time sync data from the other Center.
			05	The data support center shall acquire time sync data from an external Stratum-2 time source.
			08	The data support center shall use the externally acquired time sync data to maintain its internal clocks.
		Field Time Management	01	The roadway field element shall acquire time sync data from an external Stratum-2 time source.
			02	The roadway field element shall obtain time sync data from the System Monitor.
			03	The roadway field element shall obtain time and position data from its local location and time data source.
		Personal Location Determination	02	The Personal device shall obtain time and position data from its local location and time data source.
		Personal Location Determination	03	The Personal device shall make time and position data available to device applications.
		RSE Support Services	01	The field element shall obtain time and position data from its local location and time data source.
			03	The field element shall obtain time sync data from the Service Monitor.
			04	The field element shall acquire time sync data from an external Stratum-2 time source.
		SM Time Synchronization	01	The service monitor system shall use the externally acquired time sync data to maintain its internal clocks.
			02	The service monitor system shall provide time sync data to other Centers.
			03	The service monitor system shall provide time sync data to Connected Vehicle Roadway Equipment.
			04	The service monitor system shall provide time sync data to ITS Roadway Equipment.
			05	The service monitor system shall acquire time sync data from an external Stratum-2 time source.
		Vehicle Location Determination	05	The vehicle shall provide its location with lane-level accuracy to other on-board applications.
		Vehicle Location Determination	06	The vehicle shall provide its location with road-level accuracy to other on-board applications.
02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.	Field Time Management	03	The roadway field element shall obtain time and position data from its local location and time data source.
		Personal Location Determination	02	The Personal device shall obtain time and position data from its local location and time data source.
			03	The Personal device shall make time and position data available to device applications.
			04	The Personal device shall obtain position correction data from the Connected Vehicle Roadside Equipment.
			05	The Personal device shall apply position correction data to its base positional data.
		RSE Position Correction Support	01	The field element shall obtain position correction information from an external position correction source.
			02	The field element shall provide position correction information to proximate Vehicles.
			03	The field element shall provide position correction information to proximate Personal devices.
		RSE Support Services	01	The field element shall obtain time and position data from its local location and time data source.
		Vehicle Location Determination	01	The vehicle shall provide the vehicle's current location to other in-vehicle functions.
			02	The vehicle shall calculate the location from one or more data sources including positioning systems such as GPS, sensors that track vehicle movement, and maps used to determine the likely vehicle route.
			03	The vehicle shall obtain position correction data from the Connected Vehicle Roadside Equipment.
			04	The vehicle shall apply position correction data to its base positional data.
03	Vehicle Operators and PID users need their vehicles and devices to determine their current location.	Personal Location Determination	01	The Personal device shall determine the traveler's current location. It is intended for use by traveler personal navigation and guidance systems, as well as emergency notification systems.

Related Sources

Document Name	Version	Publication Date
Core System Concept of Operations (ConOps)	Final revE	10/24/2011
Core System System Architecture Document (SAD)	Final revC	10/14/2011
Vehicle Safety Communications Applications (VSC-A) Final Report	Final	9/1/2011
Vehicle-to-Infrastructure (V2I) Safety Applications Concept of Operation Document	Draft	8/10/2012

Security

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

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Basic Vehicle
Center	Low	Low	High	Class 5
Connected Vehicle Roadside Equipment	Low	High	High	Class 5
Data Distribution System	Not Applicable	Low	Moderate	Class 1
Field	Moderate	Moderate	High	Class 5
Location and Time Data Source	Moderate	High	High	Class 5
Network Time Source	Not Applicable	High	Moderate	Class 3
Personal	Moderate	Moderate	High	Class 5
Position Corrections Source	Not Applicable	High	High	Class 5
Service Monitor System	Not Applicable	High	Moderate	Class 3
Vehicle	Moderate	Moderate	High	Class 5

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.
Connected Vehicle Roadside Equipment	Personal	location correction	Not Applicable	High	High
Connected Vehicle Roadside Equipment	Personal	location correction	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location corrections message, could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	If locations corrections are not delivered, catastrophic consequences could result from incorrect locations data on the device that should have received the corrections. DISC: HIGH is a tall barrier for this flow.
Connected Vehicle Roadside Equipment	Vehicle	location correction	Not Applicable	High	High
Connected Vehicle Roadside Equipment	Vehicle	location correction	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location corrections message, could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	If locations corrections are not delivered, catastrophic consequences could result from incorrect locations data on the device that should have received the corrections. DISC: HIGH is a tall barrier for this flow.
Location and Time Data Source	Center	location and time	Low	High	High
Location and Time Data Source	Center	location and time	Time reference and location information for Center systems should be observable. There is no reason to obfuscate.	Location and time data is the basis for safety and a host of other applications.While a center-system is probably not in the critical decision path for safety-related applications, it is likely to be in the critical path for applications that have a significant effect on system wide applications of other types. Considering the wide-ranging impact a corruption in time and or location could have on those applications, a compromise in this flow could have major negative impacts.	If this information is not available, applications depending on this information will not function properly. Given the scope of center-based applications, this flow's availability is of paramount importance.
Location and Time Data Source	Connected Vehicle Roadside Equipment	location and time	Low	High	High
Location and Time Data Source	Connected Vehicle Roadside Equipment	location and time	Time reference and location information for Field devices should be observable. There is no reason to obfuscate.	Location and time data is the basis for safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident.	If this information is not available, applications depending on this information will not function properly.
Location and Time Data Source	Field	location and time	Moderate	High	High
Location and Time Data Source	Field	location and time	While time reference should be universally available, time reference coupled with vehicle location is tracking data. This flow is internal to a vehicle, but should probably be encrypted to discourage hacking and snooping on the vehicle bus. Thus MODERATE.	Location and time data is the basis for crash imminent safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident.	If this information is not available, crash imminent safety applications depending on this information will not function properly.
Location and Time Data Source	Personal	location and time	Moderate	High	High
Location and Time Data Source	Personal	location and time	While time reference should be universally available, time reference coupled with vehicle location is tracking data. This flow is internal to a vehicle, but should probably be encrypted to discourage hacking and snooping on the vehicle bus. Thus MODERATE.	Location and time data is the basis for crash imminent safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident.	If this information is not available, crash imminent safety applications depending on this information will not function properly.
Location and Time Data Source	Vehicle	location and time	Moderate	High	High
Location and Time Data Source	Vehicle	location and time	While time reference should be universally available, time reference coupled with vehicle location is tracking data. This flow is internal to a vehicle, but should probably be encrypted to discourage hacking and snooping on the vehicle bus. Thus MODERATE.	Location and time data is the basis for crash imminent safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident.	If this information is not available, crash imminent safety applications depending on this information will not function properly.
Network Time Source	Center	time	Not Applicable	High	Moderate
Network Time Source	Center	time	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Network Time Source	Connected Vehicle Roadside Equipment	time	Not Applicable	High	Moderate
Network Time Source	Connected Vehicle Roadside Equipment	time	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Network Time Source	Data Distribution System	time	Not Applicable	High	Moderate
Network Time Source	Data Distribution System	time	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Network Time Source	Field	time	Not Applicable	High	Moderate
Network Time Source	Field	time	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Network Time Source	Service Monitor System	time	Not Applicable	High	Moderate
Network Time Source	Service Monitor System	time	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Position Corrections Source	Connected Vehicle Roadside Equipment	position corrections	Not Applicable	High	High
Position Corrections Source	Connected Vehicle Roadside Equipment	position corrections	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location corrections message, could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	If locations corrections are not delivered, catastrophic consequences could result from incorrect locations data on the device that should have received the corrections. DISC: HIGH is a tall barrier for this flow.
Service Monitor System	Center	time local form	Not Applicable	High	Moderate
Service Monitor System	Center	time local form	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Service Monitor System	Connected Vehicle Roadside Equipment	time local form	Not Applicable	High	Moderate
Service Monitor System	Connected Vehicle Roadside Equipment	time local form	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Service Monitor System	Data Distribution System	time local form	Not Applicable	High	Moderate
Service Monitor System	Data Distribution System	time local form	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Service Monitor System	Field	time local form	Not Applicable	High	Moderate
Service Monitor System	Field	time local form	Time reference is intended to be univerally available.	Time must be highly coordinated for some applications. This support function must meet the highest requirement.	Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE.
Service Monitor System	Service Monitor System Operator	service monitor information presentation	Not Applicable	High	High
Service Monitor System	Service Monitor System Operator	service monitor information presentation	System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Service Monitor System Operator	Service Monitor System	service monitor operator input	Not Applicable	High	High
Service Monitor System Operator	Service Monitor System	service monitor operator input	System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.

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.

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	Service Monitor System

System Requirements

System Requirement		Need
001	The system shall acquire time sync data from an external Stratum-2 time source.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
002	The system shall use the externally acquired time sync data to maintain its internal clocks.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
003	The system shall obtain time sync data from the System Monitor.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
004	The system shall obtain position correction information from an external position correction source.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
005	The system shall provide position correction information to proximate Vehicles.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
006	The system shall provide position correction information to proximate Personal devices.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
007	The system shall obtain time sync data from the Service Monitor.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
008	The system shall obtain time sync data from the other Center.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
009	The system shall provide time sync data to other Centers.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
010	The system shall provide time sync data to Connected Vehicle Roadway Equipment.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
011	The system shall provide time sync data to ITS Roadway Equipment.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
012	The system shall determine the traveler's current location. It is intended for use by traveler personal navigation and guidance systems, as well as emergency notification systems.	03	Vehicle Operators and PID users need their vehicles and devices to determine their current location.
013	The system shall obtain time and position data from its local location and time data source.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
013		02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
014	The system shall make time and position data to device applications.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
014		02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
015	The system shall obtain position correction data from the Connected Vehicle Roadside Equipment.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
016	The system shall apply position correction data to its base positional data.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
018	The system shall provide the vehicle's current location to other in-vehicle functions.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
019	The system shall calculate the location from one or more data sources including positioning systems such as GPS, sensors that track vehicle movement, and maps used to determine the likely vehicle route.	02	Vehicle Operators, PID users and system operators need their devices to operate from a common geographic reference.
020	The system shall provide its location with lane-level accuracy to other on-board applications.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.
021	The system shall provide its location with road-level accuracy to other on-board applications.	01	System operators, vehicle operators, support system operators, PID users, maintenance personnel need their devices to operate on a common time base. Coordination of time between the internal systems that comprise the connected vehicle environment prevents internal synchronization errors and enables time sensitive interactions between all users.