Transit Vehicle OBE --> Transit Management Center:
demand response passenger and use data

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

demand response passenger and use data (Information Flow): Data collected on board a demand response vehicle relating to the picking up and discharging of passengers.

Transit Vehicle OBE (Source Physical Object): 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 Management Center (Destination Physical Object): 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.

Included In

This Triple is in the following Service Packages:

PT03: Dynamic Transit Operations

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

None

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - OASIS MQTT over Wireless

Solution Description

This solution is used within Australia and the U.S.. It combines standards associated with (None-Data) with those for OASIS MQTT over Wireless. The (None-Data) standards include an unspecified set of standards at the upper layers. The OASIS MQTT over Wireless standards include lower-layer standards that support data distribution of specific types of data over wireless links.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OASIS MQTT DMP	Facilities Development needed OASIS MQTT	Security IP Security Alternatives OASIS MQTT
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic	Value
Time Context	Recent
Spatial Context	Local
Acknowledgement	False
Cardinality	Unicast
Initiator	Source
Authenticable	True
Encrypt	True

Interoperability	Description
Local	In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Moderate	Moderate	Moderate
Basis	May include current operational data of the transit vehicle. A cyber-criminal should not generally have information related to the loading of vehicles.	Demand responses may not be serviced if this data is unavailable or corrupted.	Demand responses may not be serviced if this data is unavailable or corrupted.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Transit Vehicle OBE --> Transit Management Center:demand response passenger and use data