Parent Service Package: PT04
< < PT04.1 : PT04.2 : PT04.3 > >

PT04.2: Stop-Based Point-of-Sale

Fare payments are made at transit stations or stops.

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

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
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.
Financial Center Installer	Financial 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.
Financial Center Owner	Financial Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Financial Center Owner	Financial 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 Transit Management Centers Installer	Other Transit 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 Transit Management Centers Owner	Other Transit Management Centers Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Transit Management Centers Owner	Other Transit 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.
Payment Administration Center Installer	Payment Administration Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Payment Administration Center Owner	Payment Administration Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Payment Administration Center Owner	Payment Administration Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Payment Device Installer	Payment 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.
Payment Device Owner	Payment Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Payment Device Owner	Payment 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.
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.
Transit Management Center Installer	Transit Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transit Management Center Owner	Transit Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transit Management Center Owner	Transit Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Transit Vehicle OBE Installer	Transit Vehicle OBE	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transit Vehicle OBE Owner	Transit Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transit Vehicle OBE Owner	Transit Vehicle OBE Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Transportation Information Center Installer	Transportation Information Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transportation Information Center Owner	Transportation Information Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transportation Information Center Owner	Transportation Information Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Traveler Support Equipment Installer	Traveler Support 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.
Traveler Support Equipment Owner	Traveler Support Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traveler Support Equipment Owner	Traveler Support 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.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
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.
Financial Center Maintainer	Financial 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.
Financial Center Manager	Financial 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.
Financial Center Manager	Financial 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.
Financial Center Operator	Financial 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.
Financial Center Owner	Financial 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.
Financial Center Owner	Financial 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.
Financial Center Owner	Payment Administration Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Financial Center Owner	Payment Administration Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Financial Center Owner	Payment Administration Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Financial Center Owner	Payment Administrator	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.
Financial Center Owner	Transit 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.
Financial Center Owner	Transit 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.
Financial Center Owner	Transit 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.
Financial Center Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Financial Center Supplier	Financial 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 Transit Management Centers Maintainer	Other Transit 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 Transit Management Centers Manager	Other Transit 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 Transit Management Centers Manager	Other Transit 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 Transit Management Centers Operator	Other Transit 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 Transit Management Centers Owner	Other Transit 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 Transit Management Centers Owner	Other Transit 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 Transit Management Centers Owner	Transit 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 Transit Management Centers Owner	Transit 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 Transit Management Centers Owner	Transit 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 Transit Management Centers Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Other Transit Management Centers Supplier	Other Transit 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.
Payment Administration Center Maintainer	Payment Administration Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Payment Administration Center Manager	Payment Administration Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Payment Administration Center Manager	Payment Administrator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Payment Administration Center Owner	Payment Administration Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Payment Administration Center Owner	Payment Administration Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Payment Administration Center Owner	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.
Payment Administration Center Owner	Personal Information Device Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Payment Administration Center Owner	Personal Information Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Payment Administration Center Owner	Transit Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Payment Administration Center Owner	Transit 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.
Payment Administration Center Owner	Transit Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Payment Administration Center Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Payment Administration Center Owner	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.
Payment Administration Center Supplier	Payment Administration Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Payment Administrator	Payment Administration Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Payment Device Maintainer	Payment 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.
Payment Device Manager	Payment 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.
Payment 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.
Payment Device Owner	Payment 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.
Payment Device Owner	Payment 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.
Payment Device 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.
Payment Device Owner	Traveler Support 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.
Payment Device Owner	Traveler Support Equipment Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Payment Device Owner	Traveler Support 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.
Payment Device Supplier	Payment 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.
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	Payment Administration Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personal Information Device Owner	Payment Administration Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Payment Administration Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Owner	Payment Administrator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personal Information Device Owner	Personal Information Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Owner	Transit 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	Transit 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	Transit 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	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
TIC Operator	Transportation Information Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Transit Management Center Maintainer	Transit Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transit Management Center Manager	Transit Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transit Management Center Manager	Transit Operations Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Transit Management Center Owner	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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center 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.
Transit Management Center Owner	Financial Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transit Management Center Owner	Financial 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.
Transit Management Center Owner	Financial 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.
Transit Management Center Owner	Financial Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transit Management Center Owner	Other Transit 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.
Transit Management Center Owner	Other Transit 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.
Transit Management Center Owner	Other Transit 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.
Transit Management Center Owner	Other Transit 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.
Transit Management Center Owner	Payment Administration Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transit Management Center Owner	Payment Administration Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Transit Management Center Owner	Payment Administration Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transit Management Center Owner	Payment Administrator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Transit Management Center Owner	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.
Transit 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.
Transit 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.
Transit Management Center Owner	TIC Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Transit Management Center Owner	Transit Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transit Management Center Owner	Transit Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transit Management Center Owner	Transportation Information Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transit Management Center Owner	Transportation Information Center Owner	Information 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.
Transit Management Center Owner	Transportation Information Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transit Management Center 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.
Transit Management Center Owner	Traveler Support 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.
Transit Management Center Owner	Traveler Support Equipment 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.
Transit Management Center Owner	Traveler Support 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.
Transit Management Center Supplier	Transit Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Transit Operations Personnel	Transit Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Transit Vehicle OBE Maintainer	Transit Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transit Vehicle OBE Manager	Transit Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transit Vehicle OBE Manager	Transit Vehicle 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.
Transit Vehicle OBE Owner	Transit Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transit Vehicle OBE Owner	Transit Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transit Vehicle OBE Supplier	Transit Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Transit Vehicle Operator	Transit Vehicle OBE	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Transportation Information Center Maintainer	Transportation Information Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transportation Information Center Manager	TIC Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Transportation Information Center Manager	Transportation Information Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transportation Information Center Owner	Transit Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transportation Information Center Owner	Transit Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Transportation Information Center Owner	Transit Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transportation Information Center Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Transportation Information Center Owner	Transportation Information Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transportation Information Center Owner	Transportation Information Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transportation Information Center Supplier	Transportation Information Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traveler	Payment 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.
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.
Traveler	Traveler Support Equipment	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Traveler Support Equipment Maintainer	Traveler Support 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.
Traveler Support Equipment Manager	Traveler	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Traveler Support Equipment Manager	Traveler Support 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.
Traveler Support Equipment Owner	Payment 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.
Traveler Support Equipment Owner	Payment Device Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Traveler Support Equipment Owner	Payment 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.
Traveler Support Equipment Owner	Transit 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.
Traveler Support Equipment Owner	Transit 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.
Traveler Support Equipment Owner	Transit 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.
Traveler Support Equipment Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Traveler Support Equipment 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.
Traveler Support Equipment Owner	Traveler Support 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.
Traveler Support Equipment Owner	Traveler Support 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.
Traveler Support Equipment Supplier	Traveler Support 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.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Payment Administration Center	PAC Payment Administration	5.4.2	Process Violations for Tolls
		7.1.1.3	Manage Bad Toll Payment Data
		7.1.1.6	Collect Probe Data From Toll Transactions
		7.1.1.7	Update Toll Price Data
		7.1.1.8	Register for Advanced Toll Payment
		7.1.1.9	Manage Toll Processing
		7.1.8	Exchange Data with Other Payment Administration
		7.4.4.1	Process Electric Charging Payments
		7.6.1.2	Calculate Vehicle Road Use Payment Charges
		7.6.1.4	Manage Road Use Charging Price Data
		7.6.1.5	Manage Road Use Charges Processing
		7.6.5	Exchange Road Use Charging Data with Other Payment Administration
		7.6.6.1	Provide Road Use Charging Services User Interface
		7.6.8	Provide Road Use Charging Enforcement Interface
		7.7	Administer Multimodal Payments
Personal Information Device	Personal Interactive Traveler Information	6.8.1.1.1	Determine Personal Portable Device Guidance Method
		6.8.1.1.2	Provide Personal Portable Device Dynamic Guidance
		6.8.3.1	Get Traveler Personal Request
		6.8.3.2	Provide Traveler with Personal Travel Information
		6.8.3.3	Provide Traveler Personal Interface
		6.8.3.4	Update Traveler Personal Display Map Data
		6.8.3.5	Provide Traveler Transit Services Interface
		6.8.3.6	Provide Personal Safety Messages
		6.8.3.7	Manage Traveler Personal Social Media Interface
		7.5.3	Provide Personal Payment Device Interface
		7.6.6.3	Provide Road Use Charging Services Personal Interface
Transit Management Center	Transit Center Fare Management	4.2.1.5	Manage Transit Operational Data Store
		4.2.1.7	Provide Interface for Other Transit Management Data
		4.6.7	Manage Transit Vehicle Advanced Payments
		5.4.4	Process Fare Payment Violations
		5.4.5	Process Vehicle Fare Collection Violations
		5.4.7	Process Roadside Fare Collection Violations
		7.3.1.1	Register for Advanced Transit Fare Payment
		7.3.1.2	Determine Advanced Transit Fares
		7.3.1.3	Manage Transit Fare Financial Processing
		7.3.1.4	Check for Advanced Transit Fare Payment
		7.3.1.5	Bill Traveler for Transit Fare
		7.3.1.6	Collect Bad Transit Fare Payment Data
		7.3.1.7	Update Transit Fare Data
		7.3.3	Get Traveler Image for Violation
		7.4.1.5	Process Traveler Other Services Payments
Transit Vehicle OBE	Transit Vehicle On-Board Fare Management	4.6.1	Manage Transit Fare Billing on Vehicle
		4.6.2	Determine Traveler Needs on Vehicle
		4.6.3	Determine Transit Fare on Vehicle
		4.6.4	Provide Traveler Fare Payment Interface on Vehicle
		4.6.5	Update Transit Vehicle Fare Data
		4.6.6	Provide Transit Vehicle Fare Collection Data
		7.3.5	Provide Transit Vehicle Payment Device Interface
Transportation Information Center	TIC Data Collection	6.2.1	Collect Misc Traveler Information
		6.2.2	Collect Traffic Data
		6.2.3	Collect Transit Operations Data
		6.2.4	Collect Multimodal Data
		6.2.5	Collect Situation and Sensor Data From Vehicles
		6.2.6	Collect Emergency Traveler Data
		6.5.4	Process Travel Services Provider Data
		6.6.2.3	Provide Route Segment Data for Other Areas
		7.4.2	Collect Price Data for Traveler Information Use
Traveler Support Equipment	Traveler Fare Management	4.7.2.1	Detect Traveler at Roadside
		4.7.2.2	Determine Traveler Needs at Roadside
		4.7.2.3	Determine Transit Fare at Roadside
		4.7.2.4	Manage Transit Fare Billing at Roadside
		4.7.2.5	Provide Traveler Roadside Fare Interface
		4.7.2.6	Update Roadside Transit Fare Data
		4.7.2.7	Provide Transit Roadside Passenger Data
		7.3.4	Provide Remote Terminal Payment Device Interface
		7.5.2	Provide Traveler Roadside Payment Device Interface
		7.5.4	Provide Traveler Kiosk Payment Device Interface
		7.6.6.2	Provide Road Use Charging Services Kiosk Interface

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
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.
Financial Center	Center	The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object.
Other Transit Management Centers	Center	Representing another transit operations center, 'Other Transit Management Centers' is intended to provide a source and destination for information flows between peer transit management centers. It enables transit management activities to be coordinated across geographic boundaries or jurisdictions.
Payment Administration Center	Center	The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
Payment Device	Personal	The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
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.
Transit Management Center	Center	The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transit Operations Personnel	Center	'Transit Operations Personnel' represents the people that are responsible for fleet management, maintenance operations, and scheduling activities of the transit system. These different roles represent a variety of individuals in the transit industry. Within the transit industry the person responsible for fleet management is known by many names: Street Supervisor, Starter, Dispatcher, Supervisor, Traffic Controller, Transportation Coordinator. This person actively monitors, controls, and modifies the transit fleet routes and schedules on a day to day basis (dynamic scheduling). The modifications will take account of abnormal situations such as vehicle breakdown, vehicle delay, detours around work zones or incidents (detour management, connection protection, and service restoration), and other causes of route or schedule deviations. Transit operations personnel are also responsible for demand responsive transit operation and for managing emergency situations within the transit network such as silent alarms on board transit vehicles, or the remote disabling of the vehicle. In addition the Transit Operations Personnel may be responsible for assigning vehicle operators to routes, checking vehicle operators in and out, and managing transit stop issues. This object also represents the personnel in the transit garage that are responsible for maintenance of the transit fleets, including monitoring vehicle status, matching vehicles with operators, and maintenance checking of transit vehicles. Finally, it represents the people responsible for planning, development, and management of transit routes and schedules.
Transit Vehicle OBE	Vehicle	The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transit Vehicle Operator	Vehicle	The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.
Transportation Information Center	Center	The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Traveler	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.
Traveler Support Equipment	Field	'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms.

Includes Functional Objects:

Functional Object	Description	Physical Object
PAC Payment Administration	'PAC Payment Administration' provides administration and management of payments associated with electronic toll collection, parking payments, and other e-payments. It provides the back office functions that support enrollment, pricing, reduced fare eligibility, payment reconciliation with financial institutions, and violation notification to enforcement agencies. It also supports dynamic pricing to support demand management, allow/block-list management and token validation.	Payment Administration Center
Personal Interactive Traveler Information	'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones.	Personal Information Device
TIC Data Collection	'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, pathway information, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers.	Transportation Information Center
Transit Center Fare Management	'Transit Center Fare Management' manages fare collection and passenger load management at the transit center. It provides the back office functions that support transit fare collection, supporting payment reconciliation with links to financial institutions and enforcement agencies for fare violations. It collects data required to determine accurate ridership levels, establish fares, and distribute fare information. It loads fare data into the vehicle prior to the beginning of normal operations and unloads fare collection data from the vehicle at the close out of normal operations. It manages allow/block lists and performs token validation.	Transit Management Center
Transit Vehicle On-Board Fare Management	'Transit Vehicle On-board Fare Management' supports fare collection using a standard fare card or other non-monetary fare medium and detects payment violations, manages allow/block lists and performs token validation. Collected fare data are made available to the center.	Transit Vehicle OBE
Traveler Fare Management	'Traveler Fare Management' provides the capability for the traveler to access and use a common fare medium for transit fares, tolls, shared use, and/or parking lot charges using a public device at or near the point of service. It accepts a service request and means of payment or smart card, verifies eligibility, calculates the amount due, collects payment (or deducts balance if smart card), manages allow/block lists, performs token validation, and identifies payment problems. It may be implemented using a card reader/dispenser in a point of sale device that includes a communications interface to the financial infrastructure to support payment collection and reconciliation.	Traveler Support Equipment

Includes Information Flows:

Information Flow	Description
account updates	Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information.
actuate secure payment	Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction.
authorization request	Request to determine if a transportation user is authorized to use a particular transportation resource.
authorization response	Notification of status of authorization request.
fare collection data	Fare collection information including the summary of fare system data and financial payment transaction data.
fare management information	Transit fare information and transaction data used to manage transit fare processing.
payment device information	Traveler payment information such as card number and previous transactions.
payment device update	Information updated concerning traveler's personal data including name, address, user account information, trip records, and profile data.
payment methods	A list of valid payment methods.
payment methods financial institution	A list of valid payment methods accepted by a financial center.
payment request	Request for payment from financial institution or related financial service requests (e.g., balance inquiry)
payment violation notification	Notification to enforcement agency of a toll, parking, or transit fare payment violation.
registered secureIDs	Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service.
request for payment	Request to deduct cost of service from user's payment account.
service registry	Catalogue of products and values, access rights and related information.
settlement	Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges.
transit fare coordination	Fare and pricing information shared between local/regional transit organizations.
transit fare information	Information provided by transit management that supports fare payment transactions.
transit fare request	Request for fare information and transit fare payment.
transit operations personnel input	User input from transit operations personnel including instructions governing service availability, schedules, emergency response plans, transit personnel assignments, transit maintenance requirements, and other inputs that establish general system operating requirements and procedures.
transit operations status	Presentation of information to transit operations personnel including accumulated schedule and fare information, ridership and on-time performance information, emergency response plans, transit personnel information, maintenance records, and other information intended to support overall planning and management of a transit property.
transit vehicle operator display	Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services.
transit vehicle operator input	Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data.
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.
user account reports	Reports on services offered/provided and associated charges.
user account setup	Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.

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
Enforcement Center
Financial Center
Other Transit Management Centers
Payment Administration Center
Payment Device
Personal Information Device
Transit Management Center
Transit Vehicle OBE
Transportation Information Center
Traveler Support Equipment

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
Financial Center	Payment Administration Center	payment methods financial institution	Moderate	Moderate	Low
Financial Center	Payment Administration Center	payment methods financial institution	Payment methods should be widely disseminated and contain no information that could cause harm if exposed.	Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.	Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Financial Center	Transit Management Center	settlement	Moderate	Moderate	Moderate
Financial Center	Transit Management Center	settlement	This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Other Transit Management Centers	Transit Management Center	transit fare coordination	Low	Moderate	Moderate
Other Transit Management Centers	Transit Management Center	transit fare coordination	Does not contain any personal or confidential information.	While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally.
Payment Administration Center	Personal Information Device	registered secureIDs	High	High	Moderate
Payment Administration Center	Personal Information Device	registered secureIDs	These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services.	Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH.	Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Payment Administration Center	Personal Information Device	user account reports	High	High	Moderate
Payment Administration Center	Personal Information Device	user account reports	Contains user identification and transaction history, which if compromised could lead to identity or financial theft.	Payment history information, if corrupted, could lead the user to take action he or she should not take. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest.	There should be other mechanisms to retrieve this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Payment Administration Center	Transit Management Center	payment methods	Moderate	Moderate	Low
Payment Administration Center	Transit Management Center	payment methods	Payment methods should be widely disseminated and contain no information that could cause harm if exposed.	Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.	Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Payment Device	Traveler Support Equipment	actuate secure payment	Moderate	Moderate	High
Payment Device	Traveler Support Equipment	actuate secure payment	Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact.	Payment related information needs to be correct or the user may be inconvenienced or defrauded.	Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Payment Device	Traveler Support Equipment	payment device information	Moderate	Moderate	High
Payment Device	Traveler Support Equipment	payment device information	Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow.	Payment related information needs to be correct or the user may be inconvenienced or defrauded.	Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device	Payment Administration Center	user account setup	High	High	Moderate
Personal Information Device	Payment Administration Center	user account setup	Contains user identification and matching vehicle information, which if compromised could lead to identity theft or remote tracking.	Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest.	There should be other mechanisms to provide this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Personal Information Device	Transit Management Center	user account setup	High	High	Moderate
Personal Information Device	Transit Management Center	user account setup	Contains user identification and transaction history, which if compromised could lead to identity or financial theft.	Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest.	These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Transit Management Center	Enforcement Center	payment violation notification	Moderate	Moderate	Moderate
Transit Management Center	Enforcement Center	payment violation notification	Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual.	Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE.	More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.
Transit Management Center	Financial Center	payment request	Moderate	Moderate	Moderate
Transit Management Center	Financial Center	payment request	Contains account and related information that is personal and if compromised could financially impact the owner of the account.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Transit Management Center	Other Transit Management Centers	transit fare coordination	Low	Moderate	Moderate
Transit Management Center	Other Transit Management Centers	transit fare coordination	Does not contain any personal or confidential information.	While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally.
Transit Management Center	Payment Administration Center	account updates	Moderate	Moderate	Moderate
Transit Management Center	Payment Administration Center	account updates	Contains an identifier that can be linked to an account which is in turn likely linked to a person, and thus PII that should be protected.	Payment charge and similar information should be correct or it could lead to abuse or incorrect charges. Impact limited to individual accounts however.	These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Transit Management Center	Payment Administration Center	service registry	Low	Moderate	Moderate
Transit Management Center	Payment Administration Center	service registry	Much of this information will eventually be widely disseminated to transport users, though there seems little good reason to not obfuscate it.	Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect.	Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect.
Transit Management Center	Personal Information Device	registered secureIDs	High	High	Moderate
Transit Management Center	Personal Information Device	registered secureIDs	These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services.	Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH.	Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Transit Management Center	Personal Information Device	user account reports	High	High	Moderate
Transit Management Center	Personal Information Device	user account reports	Contains user identification and transaction history, which if compromised could lead to identity or financial theft.	Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest.	These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Transit Management Center	Transit Operations Personnel	transit operations status	Moderate	High	High
Transit Management Center	Transit Operations Personnel	transit operations status	Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available.	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.
Transit Management Center	Transportation Information Center	transit fare information	Low	High	Moderate
Transit Management Center	Transportation Information Center	transit fare information	Intended to be distributed to the traveling public.	Accuracy of this data is important for decision making purposes. Corruption of this data could lead to revenue loss and confusion.	While availability of this data is important for decision making, and there are usually multiple avenues for determining transit costs, the TIC may serve a great many users, so it should have higher priority for fare information than individual traveler equipment.
Transit Management Center	Traveler Support Equipment	authorization response	Moderate	Moderate	Moderate
Transit Management Center	Traveler Support Equipment	authorization response	While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Transit Management Center	Traveler Support Equipment	fare management information	High	Moderate	Moderate
Transit Management Center	Traveler Support Equipment	fare management information	May contain PII of the originator, including possible special needs and identity, which should be readable only by the intended recepient lest the originator's privacy be violated.	If this is compromised or corrupted, the user's needs may not be properly communicated or met. If this is forged, the transit provider may not collect the appropriate fare or provide the proper services.	If this is not available, the user may not receive transit services offered, and as with other transit services may ceases using the system. While the immediate impact is LOW, long term impact is MODERATE due to user confidence issues.
Transit Operations Personnel	Transit Management Center	transit operations personnel input	Moderate	High	High
Transit Operations Personnel	Transit Management Center	transit operations personnel input	Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available.	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.
Transit Vehicle OBE	Transit Vehicle Operator	transit vehicle operator display	Low	Moderate	Low
Transit Vehicle OBE	Transit Vehicle Operator	transit vehicle operator display	This should not include any sensitive information. It would be possible for a person standing behind the driver to observe the information transmitted.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. This entire application should not directly affect the drivers driving habits. The operator should still be slowing and stopping at yellow or red lights, along with observing all other driving regulations. DISC: Original V2I analysis classified this as LOW.	Even if the operator is not made aware of the signal preemption, the system should still operate correctly. The operator should be using the traffic lights to influence their decision about whether or not to stop, not the display.
Transit Vehicle Operator	Transit Vehicle OBE	transit vehicle operator input	Low	Moderate	Low
Transit Vehicle Operator	Transit Vehicle OBE	transit vehicle operator input	This information is transmitted through systems on board the Transit Vehicle. Even if the vehicle were compromised and these communications monitored, most of this information is directly observable.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this is compromised, it could result in an incorrect signal priority request, which has minimal impact. DISC: Original V2I analysis classified this as LOW.	A delay in reporting this may result in a signal priority request not going through, which has minimal impact.
Transportation Information Center	Transit Management Center	transit fare request	Low	Moderate	Low
Transportation Information Center	Transit Management Center	transit fare request	Response information will all be public eventually and the request flow betrays no intent not already implicit in the sender.	This information will be propagated to travelers. This will set their expectations and may be used to drive their decision making. Incorrect data will reduce confidence in the overall transportation system and could negatively impact individual travelers' transportation experience.	Most likely this flow will not need to operate often; as long as it does operate within a reasonable update time from when fares change, LOW is acceptable.
Traveler	Traveler Support Equipment	traveler input	Not Applicable	Moderate	Low
Traveler	Traveler Support Equipment	traveler input	Publicly available information, while not directly observable, is intended for widespread distribution	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.
Traveler Support Equipment	Payment Device	payment device update	Moderate	Moderate	High
Traveler Support Equipment	Payment Device	payment device update	Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow.	Payment related information needs to be correct or the user may be inconvenienced or defrauded.	Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Traveler Support Equipment	Payment Device	request for payment	Moderate	Moderate	High
Traveler Support Equipment	Payment Device	request for payment	Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow.	Payment related information needs to be correct or the user may be inconvenienced or defrauded.	Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Traveler Support Equipment	Transit Management Center	authorization request	Moderate	Moderate	Moderate
Traveler Support Equipment	Transit Management Center	authorization request	Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.	Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Traveler Support Equipment	Transit Management Center	fare collection data	Moderate	Moderate	Moderate
Traveler Support Equipment	Transit Management Center	fare collection data	Imagery of a traveler that has ostensibly violated a transit fare. If captured by an observer, could be used against the individual.	If corrupted, could make it difficult to identify the offender, costing money.	If unavailable, other mechanisms could still exist to provide payment. If no other mechanisms exist this would have to be HIGH.
Traveler Support Equipment	Traveler	traveler interface updates	Not Applicable	Moderate	Moderate
Traveler Support Equipment	Traveler	traveler interface updates	Publicly available information, while not directly observable, is intended for widespread distribution	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.

Standards

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

Name	Title	Physical Object
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	Payment Administration Center

System Requirements

No System Requirements