Transit Vehicle OBE --> Transit Management Center:
transit vehicle loading data

Definitions

transit vehicle loading data (Information Flow): Data collected on board the transit vehicle relating to passenger boarding and alighting.

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:

• PT07: Transit Passenger Counting
• PT17: Transit Connection Protection

This triple is associated with the following Functional Objects:

• Transit Center Passenger Counting
• Transit Vehicle Passenger Counting

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

• transit_vehicle_passenger_loading

This Triple has the following triple relationships:

Communication Solutions

• US: TCIP - Secure Wireless Internet (ITS) (15)
• (None-Data) - Secure Wireless Internet (EU) (32)
• Data for Distribution (TBD) - Apache Kafka over Wireless (36)
• Data for Distribution (TBD) - OMG DDS over Wireless (36)
• (None-Data) - OASIS MQTT over Wireless (42)
• Data for Distribution (TBD) - OASIS MQTT over Wireless (42)
• (None-Data) - OASIS AMQP over Wireless (45)
• Data for Distribution (TBD) - OASIS AMQP over Wireless (45)

Selected Solution

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities Development needed OASIS AMQP	Security IP Security Alternatives
	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

Security