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

PM03.2: Direct Payment Using WAW

Wide area wireless communications is used to communicate directly with back-office systems to pay for parking.

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

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

Enterprise

Development Stage Roles and Relationships
(hide)

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

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.
Light Vehicle OBE Installer	Light Vehicle OBE	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Light Vehicle OBE Owner	Light Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Light Vehicle OBE Owner	Light Vehicle OBE Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Parking Management Center Installer	Parking 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.
Parking Management Center Owner	Parking Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Parking Management Center Owner	Parking 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.
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.

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	Parking 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	Parking 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	Parking 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	Parking Manager	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.
Light Vehicle Driver	Light Vehicle OBE	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Light Vehicle OBE Maintainer	Light Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Light Vehicle OBE Manager	Light Vehicle Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Light Vehicle OBE Manager	Light Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Light Vehicle OBE Owner	Light Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Light Vehicle OBE Owner	Light Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Light Vehicle OBE Supplier	Light Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Maint and Constr Field Personnel	Personal Information Device	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Parking Management Center Maintainer	Parking 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.
Parking Management Center Manager	Parking 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.
Parking Management Center Manager	Parking Manager	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.
Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking Management Center Owner	Maint and Constr Field Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Parking Management Center Owner	Parking 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.
Parking Management Center Owner	Parking 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.
Parking 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.
Parking 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.
Parking 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.
Parking Management Center Supplier	Parking 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.
Parking Manager	Parking 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.
Personal Information Device Maintainer	Personal Information Device	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Personal Information Device Manager	Maint and Constr Field Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Personal Information Device Manager	Personal Information Device	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Personal Information Device Owner	Parking 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	Parking 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	Parking 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	Parking Manager	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personal Information Device Owner	Personal Information Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Parking Management Center	Parking Account and Fee Management	5.4.3	Process Parking Lot Violations
		7.2.1.3	Collect Bad Charge Payment Data
		7.2.1.4	Check for Advanced Parking Lot Payment
		7.2.1.6	Manage Parking Lot Financial Processing
		7.2.1.7	Update Parking Lot Data
		7.2.1.8	Register for Advanced Parking Lot Payment
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

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.
Light Vehicle Driver	Vehicle	The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle.
Light Vehicle OBE	Vehicle	The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Parking Management Center	Center	The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Parking Manager	Center	'Parking Manager' is the human operator that supports back office operations for one or more parking areas.
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.

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
Parking Account and Fee Management	'Parking Account and Fee Management' manages parking fare collection at the Parking Management Center. It provides the back office functions that support control of field parking management systems, supporting payment reconciliation with links to financial institutions. It loads fee data into field systems when those systems are initialized or whenever such information is modified.	Parking Management 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

Includes Information Flows:

Information Flow	Description
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.
light vehicle driver input	Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
light vehicle driver updates	Information provided to the light vehicle driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
parking manager input	Input from the parking manager to query current status and control back office operations for a parking management system.
parking status	Presentation of information to the parking manager including operational status and transaction reports. This includes aggregated status for parking areas as well as status for back office operations.
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.
settlement	Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges.
traveler payment information	Information provided for payment of road use charges, tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.
traveler payment request	Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement.
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	Moderate	Moderate	Moderate	Class 2
Financial Center	Moderate	Moderate	Moderate	Class 2
Light Vehicle OBE
Parking Management Center	High	High	High	Class 5
Personal Information Device	High	High	High	Class 5

In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Financial Center	Parking Management Center	settlement	Moderate	Moderate	Moderate
Financial Center	Parking 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.
Light Vehicle Driver	Light Vehicle OBE	light vehicle driver input	Moderate	High	High
Light Vehicle Driver	Light Vehicle OBE	light vehicle driver input	Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy.	Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner	Commands must always be able to be given or the driver has no control.
Light Vehicle OBE	Light Vehicle Driver	light vehicle driver updates	Not Applicable	Moderate	Moderate
Light Vehicle OBE	Light Vehicle Driver	light vehicle driver updates	This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the driver, then the system has not operated correctly.
Parking Management Center	Enforcement Center	payment violation notification	Moderate	Moderate	Moderate
Parking 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.
Parking Management Center	Financial Center	payment request	Moderate	Moderate	Moderate
Parking 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.
Parking Management Center	Parking Manager	parking status	Moderate	High	High
Parking Management Center	Parking Manager	parking 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.
Parking Management Center	Personal Information Device	traveler payment request	Moderate	Moderate	Moderate
Parking Management Center	Personal Information Device	traveler payment request	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.
Parking Management Center	Personal Information Device	user account reports	High	High	Moderate
Parking 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.
Parking Manager	Parking Management Center	parking manager input	Moderate	High	High
Parking Manager	Parking Management Center	parking manager 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.
Personal Information Device	Parking Management Center	actuate secure payment	Moderate	Moderate	High
Personal Information Device	Parking Management Center	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.
Personal Information Device	Parking Management Center	traveler payment information	High	High	Moderate
Personal Information Device	Parking Management Center	traveler payment information	Contains personal information, potentially including identity, payment information such as account numbers and location. All of this information is personal in nature and acceptable only for the intended destination to receive, as any 3rd party observation could lead to identity theft/compromise and/or payment method theft/compromise.	This is information is used to process payment and/or detect fraud. Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action.	This is information is used to process payment . Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. Availability constrained to MODERATE the fact that alternative mechanisms and compromises exist to ameliorate not completing the flow.
Personal Information Device	Parking Management Center	user account setup	High	High	Moderate
Personal Information Device	Parking 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.

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