Parent Service Package: PS04
< < PS03.7 : PS04.1 : PS05.1 > >

PS04.1: Mayday Notification Implementation

This 'implementation' is a holistic view of the PS04 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
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.
Emergency Management Center Developer	Emergency 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.
Emergency Management Center Developer	Other Emergency Management Centers Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Emergency Management Center Developer	Personal Information Device Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Emergency Management 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.
Enforcement Center Developer	Enforcement Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other Emergency Management Centers Developer	Emergency 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.
Other Emergency Management Centers Developer	Other Emergency Management Centers	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other PIDs Developer	Other PIDs	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other PIDs Developer	Personal Information Device Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Other Vehicles Developer	Other Vehicles	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other Vehicles 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.
Personal Information Device Developer	Emergency 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.
Personal Information Device Developer	Other PIDs Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Personal Information Device Developer	Personal Information Device	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle Developer	Basic 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	Emergency 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.
Vehicle Developer	Enforcement 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	Other Vehicles 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.

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.
Emergency Management Center Installer	Emergency 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.
Emergency Management Center Owner	Emergency Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Emergency Management Center Owner	Emergency 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.
Enforcement Center Installer	Enforcement Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Enforcement Center Owner	Enforcement Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Enforcement Center Owner	Enforcement Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other Emergency Management Centers Installer	Other Emergency Management Centers	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other Emergency Management Centers Owner	Other Emergency Management Centers Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Emergency Management Centers Owner	Other Emergency Management Centers Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other PIDs Installer	Other PIDs	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other PIDs Owner	Other PIDs Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other PIDs Owner	Other PIDs Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other Vehicles Installer	Other Vehicles	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other Vehicles Owner	Other Vehicles Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Vehicles Owner	Other Vehicles Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Personal Information Device Installer	Personal Information Device	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Personal Information Device Owner	Personal Information Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Information Device Owner	Personal Information Device Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
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 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.
Emergency Management Center Maintainer	Emergency 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.
Emergency Management Center Manager	Emergency 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.
Emergency Management Center Manager	Emergency 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.
Emergency Management 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.
Emergency Management Center Owner	Emergency 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.
Emergency Management Center Owner	Emergency 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.
Emergency Management Center Owner	Other Emergency Management Centers Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Emergency Management Center Owner	Other Emergency Management Centers 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.
Emergency Management Center Owner	Other Emergency Management Centers Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Emergency Management Center Owner	Other Emergency Management Centers User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Emergency Management Center Owner	Personal Information Device Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Emergency Management Center Owner	Personal Information Device Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Emergency Management Center Owner	Personal Information Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Emergency Management Center Owner	Traveler	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.
Emergency Management 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.
Emergency Management 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.
Emergency Management 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.
Emergency Management Center Supplier	Emergency 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.
Emergency System Operator	Emergency 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.
Enforcement Center Maintainer	Enforcement Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Enforcement Center Manager	Enforcement Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Enforcement Center Manager	Enforcement Center Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Enforcement Center Operator	Enforcement 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.
Enforcement Center Owner	Enforcement Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Enforcement Center Owner	Enforcement Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Enforcement Center Supplier	Enforcement Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other Emergency Management Centers Maintainer	Other Emergency Management Centers	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other Emergency Management Centers Manager	Other Emergency Management Centers	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other Emergency Management Centers Manager	Other Emergency Management Centers 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.
Other Emergency Management Centers Operator	Other Emergency Management Centers	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.
Other Emergency Management Centers Owner	Emergency 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.
Other Emergency Management Centers Owner	Emergency 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.
Other Emergency Management Centers Owner	Emergency 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.
Other Emergency Management Centers Owner	Emergency 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.
Other Emergency Management Centers Owner	Other Emergency Management Centers Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other Emergency Management Centers Owner	Other Emergency Management Centers Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Emergency Management Centers Supplier	Other Emergency Management Centers Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other PIDs Maintainer	Other PIDs	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other PIDs Manager	Other PIDs	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other PIDs Manager	Other PIDs 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.
Other PIDs Operator	Other PIDs	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.
Other PIDs Owner	Other PIDs Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other PIDs Owner	Other PIDs Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other PIDs Owner	Personal Information Device Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Other PIDs Owner	Personal Information Device Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Other PIDs Owner	Personal Information Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Other PIDs Owner	Traveler	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.
Other PIDs Supplier	Other PIDs Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other Vehicle OBEs Operator	Other Vehicles	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.
Other Vehicles Maintainer	Other Vehicles	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other Vehicles Manager	Other Vehicle OBEs 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.
Other Vehicles Manager	Other Vehicles	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other Vehicles 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.
Other Vehicles Owner	Driver	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Other Vehicles Owner	Other Vehicles Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other Vehicles Owner	Other Vehicles Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Vehicles 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.
Other Vehicles 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.
Other Vehicles 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.
Other Vehicles Supplier	Other Vehicles 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 Information Device Maintainer	Personal Information Device	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Personal Information Device Manager	Personal Information Device	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Personal Information Device Manager	Traveler	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Personal Information Device Owner	Emergency 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.
Personal Information Device Owner	Emergency Management Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Emergency 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.
Personal Information Device Owner	Emergency 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.
Personal Information Device Owner	Other PIDs Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personal Information Device Owner	Other PIDs Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personal Information Device Owner	Other PIDs Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Other PIDs User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Owner	Personal Information Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traveler	Personal Information Device	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
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	Basic 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.
Vehicle Owner	Basic 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.
Vehicle Owner	Basic 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.
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.
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.
Vehicle Owner	Emergency 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.
Vehicle Owner	Emergency 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.
Vehicle Owner	Emergency 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.
Vehicle Owner	Emergency 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.
Vehicle Owner	Enforcement 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	Enforcement Center Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Vehicle Owner	Enforcement Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Vehicle Owner	Enforcement 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	Other Vehicle OBEs 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	Other Vehicle OBEs Operator	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Vehicle Owner	Other Vehicles 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	Other Vehicles 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.
Vehicle Owner	Other Vehicles 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.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Emergency Management Center	Emergency Call-Taking	5.1.1.1	Coordinate Emergency Inputs
		5.1.1.3	Collect Incident And Event Data
		5.1.2	Determine Coordinated Response Plan
		5.1.3	Communicate Emergency Status
		5.1.4	Manage Emergency Response
		5.2	Provide Operator Interface for Emergency Data
	Emergency Notification Support	5.1.2	Determine Coordinated Response Plan
		5.1.3	Communicate Emergency Status
		5.1.6	Process Mayday Messages
		5.2	Provide Operator Interface for Emergency Data
Personal Information Device	Personal Emergency Notification	6.8.1.5	Provide Traveler Emergency Message Interface
		6.8.2.1	Build Traveler Personal Security Message
		6.8.2.2	Provide Traveler Emergency Communications Function
Vehicle	Vehicle Emergency Notification	3.1.3	Process Vehicle On-board Data
		3.3.1	Provide Communications Function
		3.3.2	Build Automatic Collision Notification Message
		6.7.2.1	Build Driver Personal Security Message
		6.7.2.2	Provide Driver In-vehicle Communications Function

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.
Driver	Vehicle	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Emergency Management Center	Center	The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
Emergency System Operator	Center	'Emergency System Operator' represents the public safety personnel that monitor emergency requests, (including those from the E911 Operator) and set up pre-defined responses to be executed by an emergency management system. The operator may also override predefined responses where it is observed that they are not achieving the desired result. This also includes dispatchers who manage an emergency fleet (police, fire, ambulance, HAZMAT, etc.) or higher order emergency managers who provide response coordination during emergencies.
Enforcement Center	Center	The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Other Emergency Management Centers	Center	'Other Emergency Management Centers' provides a source and destination for information flows between various communications centers operated by public safety agencies, emergency management agencies, other allied agencies, and private companies that participate in coordinated management of transportation-related incidents, including disasters. The interface represented by this object enables emergency management activities to be coordinated across jurisdictional boundaries and between functional areas, supporting requirements for general networks connecting many allied agencies. It also supports interface to other allied agencies like utility companies that also participate in the coordinated response to selected highway-related incidents.
Other PIDs	Personal	'Other PIDs' represents other personal information devices (PIDs) that are communicating with the device. This includes all connected personal information devices that support wireless short-range communications, including those used by pedestrians, cyclists, and other vulnerable road users (VRUs). This object provides a source and destination for information transfers between connected personal devices. The host device, represented by the Personal Information Device physical object, sends information to, and receives information from the Other PIDs to model all connected personal-to-personal (P2P) communications in ARC-IT.
Other Vehicles	Vehicle	'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.
Personal Information Device	Personal	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Traveler	Personal	The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
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.

Includes Functional Objects:

Functional Object	Description	Physical Object
Emergency Call-Taking	'Emergency Call-Taking' supports the emergency call-taker, collecting available information about the caller and the reported emergency, and forwarding this information to other objects that formulate and manage the emergency response. It receives 9-1-1, 7-digit local access, and motorist call-box calls and interfaces to other agencies to assist in the verification and assessment of the emergency and to forward the emergency information to the appropriate response agency.	Emergency Management Center
Emergency Notification Support	'Emergency Notification Support' receives emergency notification messages from vehicles or personal handheld devices, determines an appropriate response, and either uses internal resources or contacts a local agency to provide that response. The nature of the emergency is determined based on the information in the received message as well as other inputs. This object effectively serves as an interface between automated collision notification systems and the local public safety answering point for messages that require a public safety response. This capability depends on an up-to-date registry of public safety answering points/response agencies by coverage area, the type of emergency, and hours of service.	Emergency Management Center
Personal Emergency Notification	'Personal Emergency Notification' provides the capability for travelers to report an emergency or activate a panic button to summon assistance. The personal mayday capability is provided by a portable device such as a smart phone.	Personal Information Device
Vehicle Emergency Notification	'Vehicle Emergency Notification' provides the capability for drivers or collision detection sensors to report an emergency and summon assistance. It gathers data from on-board collision detection sensors, provides a mechanism for the driver to summon assistance, and includes a communications capability to report the collision including indicators of collision severity, the number of passengers involved, and information about the vehicle that may affect the response.	Vehicle

Includes Information Flows:

Information Flow	Description
driver input	Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver input information	Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
driver update information	Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
driver updates	Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
emergency acknowledge	Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
emergency data request	A request for additional information or a control command issued by the emergency response agency in response to an emergency request for assistance from a traveler.
emergency notification	An emergency request for assistance that is automatically initiated by a vehicle or manually initiated by a vehicle occupant or a traveler (vulnerable road user) with a personal information device. The request includes call-back number, date, time, location, pre-event vehicle heading, vehicle make, model, model year, and fuel type, and crash severity indicators. Crash severity indicators include: airbags deployed, number of impacts, crash delta velocity, principle direction of force, and rollover indication. In addition, seatbelt restraint use, number of occupants, occupant location, and intrusion may be included. For commercial vehicles, this flow may also include freight equipment type (box, flatbed, trailer, container, etc.), type of cargo (refrigerated, non-perishable, liquid, etc.), hazardous material data, quantity of cargo, and cargo permits as applicable (hazmat, special routing permissions).
emergency notification relay	The relay of a previously received emergency notification. This relay enables a connected vehicle or an equipped personal information device (PID) that is passing within radio range of a vehicle or PID in need of assistance to store the notification and then forward it to a public safety agency when communications is available. Multiple relays may be necessary in remote areas with infrequent traffic and spotty communications coverage. The relay includes all of the information included in the original emergency notification (see 'emergency notification') and relay-specific data that can be used to manage the relay. Relay-specific data may include the date and time of original emergency notification receipt and the number of times the message has been relayed.
emergency operations input	Emergency operator input supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
emergency operations status	Presentation of information to the operator including emergency operations data, supporting a range of emergency operating positions including call taker, dispatch, emergency operations, security monitoring, and various other operations and communications center operator positions.
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.
incident report	Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response.
request for service	Driver inputs that summon an emergency response, request a financial transaction, or initiate other services.
traveler input	User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates	Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.
vehicle incident record	Data that has been recorded during an incident.

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
Emergency Management Center
Enforcement Center
Other Emergency Management Centers
Other PIDs
Other Vehicles
Personal Information Device
Vehicle

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	driver input information	Moderate	High	High
Basic Vehicle	Vehicle	driver input information	Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise.	Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation.	Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation.
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.
Driver	Vehicle	driver input	Moderate	High	High
Driver	Vehicle	driver input	Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy.	Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner	Commands must always be able to be given or the driver has no control.
Driver	Vehicle	request for service	Moderate	High	High
Driver	Vehicle	request for service	This request implies a declaration of intent, which if observed could provide leverage over the driver.	Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner	Commands must always be able to be given or the driver has no control.
Emergency Management Center	Emergency System Operator	emergency operations status	Moderate	High	High
Emergency Management Center	Emergency System Operator	emergency operations status	Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity.	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.
Emergency Management Center	Other Emergency Management Centers	incident report	High	Moderate	Moderate
Emergency Management Center	Other Emergency Management Centers	incident report	This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE.	Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate.	A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Emergency Management Center	Personal Information Device	emergency acknowledge	Low	Moderate	Low
Emergency Management Center	Personal Information Device	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Emergency Management Center	Vehicle	emergency acknowledge	Low	Moderate	Low
Emergency Management Center	Vehicle	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Emergency Management Center	Vehicle	emergency data request	Moderate	Moderate	Moderate
Emergency Management Center	Vehicle	emergency data request	This request is a response to an emergency outreach from the Vehicle OBE. If a hostile third party observed this information they might use it in the commission of a crime.	An incorrect message may mislead the originator of the emergency request and/or invalidate the request, which which could affect the emergency response scenario.	Given that this is part of the mayday chain of events, it should have some priority over other flows. Probably not HIGH, as even without this a physical response will be issued.
Emergency System Operator	Emergency Management Center	emergency operations input	Moderate	High	High
Emergency System Operator	Emergency Management Center	emergency operations input	Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity.	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.
Other Emergency Management Centers	Emergency Management Center	incident report	High	Moderate	Moderate
Other Emergency Management Centers	Emergency Management Center	incident report	This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE.	Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate.	A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Other PIDs	Personal Information Device	emergency acknowledge	Low	Moderate	Low
Other PIDs	Personal Information Device	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Other PIDs	Personal Information Device	emergency notification	Moderate	High	Moderate
Other PIDs	Personal Information Device	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other PIDs	Personal Information Device	emergency notification relay	Moderate	High	Moderate
Other PIDs	Personal Information Device	emergency notification relay	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other Vehicles	Vehicle	emergency acknowledge	Low	Moderate	Low
Other Vehicles	Vehicle	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Other Vehicles	Vehicle	emergency notification	Moderate	High	Moderate
Other Vehicles	Vehicle	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other Vehicles	Vehicle	emergency notification relay	Moderate	High	Moderate
Other Vehicles	Vehicle	emergency notification relay	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device	Emergency Management Center	emergency notification	Moderate	High	Moderate
Personal Information Device	Emergency Management Center	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device	Other PIDs	emergency acknowledge	Low	Moderate	Low
Personal Information Device	Other PIDs	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Personal Information Device	Other PIDs	emergency notification	Moderate	High	Moderate
Personal Information Device	Other PIDs	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device	Other PIDs	emergency notification relay	Moderate	High	Moderate
Personal Information Device	Other PIDs	emergency notification relay	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device	Traveler	traveler interface updates	Not Applicable	Moderate	Moderate
Personal Information Device	Traveler	traveler interface updates	Personalized data that includes directions and guidance for an individual, but eventually evident anyway.	Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral.	Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Traveler	Personal Information Device	traveler input	Not Applicable	Moderate	Low
Traveler	Personal Information Device	traveler input	This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it.	While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans.	Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Vehicle	Basic Vehicle	driver update information	Low	Moderate	Moderate
Vehicle	Basic Vehicle	driver update information	This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW.	Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.	Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.
Vehicle	Driver	driver updates	Not Applicable	Moderate	Moderate
Vehicle	Driver	driver updates	This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the driver, then the system has not operated correctly.
Vehicle	Emergency Management Center	emergency notification	Moderate	High	Moderate
Vehicle	Emergency Management Center	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle	Emergency Management Center	emergency notification relay	Moderate	High	Moderate
Vehicle	Emergency Management Center	emergency notification relay	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle	Enforcement Center	vehicle incident record	Moderate	Moderate	Low
Vehicle	Enforcement Center	vehicle incident record	Any information relevant to legal authorities should be considered need-to-know only.	Any information relevant to legal authorities should be provided intact, or the originator may be negatively impacted.	There should be other ways for this data to be exchanged.
Vehicle	Other Vehicles	emergency acknowledge	Low	Moderate	Low
Vehicle	Other Vehicles	emergency acknowledge	As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information.	An incorrect message may mislead the originator of the emergency request, which could affect his behavior	If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Vehicle	Other Vehicles	emergency notification	Moderate	High	Moderate
Vehicle	Other Vehicles	emergency notification	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle	Other Vehicles	emergency notification relay	Moderate	High	Moderate
Vehicle	Other Vehicles	emergency notification relay	Emergency notification flows intended for centers can include PII, so they should be obfuscated.	Emergency notification has a time-critical and life-saving and property saving component.	Ideally HIGH, but there are altenative mechanisms for emergency notifications, so 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