Transit Vehicle Operator --> Transit Vehicle OBE:
transit vehicle operator input
Definitions
transit vehicle operator input (Information Flow): 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.
Transit Vehicle Operator (Source Physical Object): 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.
Transit Vehicle OBE (Destination 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.
Included In
This Triple is in the following Service Packages:
- PT02: Transit Fixed-Route Operations
- PT03: Dynamic Transit Operations
- PT04: Transit Fare Collection Management
- PT05: Transit Security
- PT06: Transit Fleet Management
- PT09: Transit Signal Priority
- PT10: Intermittent Bus Lanes
- PT11: Transit Pedestrian Indication
- PT12: Transit Vehicle at Station/Stop Warnings
- PT13: Vehicle Turning Right in Front of a Transit Vehicle
- PT15: Transit Stop Request
- PT17: Transit Connection Protection
- VS04: V2V Special Vehicle Alert
This triple is associated with the following Functional Objects:
- Transit Vehicle On-Board Connection Protection
- Transit Vehicle On-Board Fare Management
- Transit Vehicle On-Board Information Services
- Transit Vehicle On-Board Paratransit Operations
- Transit Vehicle Pedestrian Safety
- Transit Vehicle Schedule Management
- Transit Vehicle Security
- Transit Vehicle Signal Priority
- Transit Vehicle V2V Safety
This Triple is described by the following Functional View Data Flows:
- ftvo-fare_transaction_mode_set_up
- ftvo-paratransit_status
- ftvo-request_batch_mode_data_transfer
- ftvo-request_logon_authentication
- ftvo-secure_transit_vehicle_emergency_request
- ftvo-secure_transit_vehicle_surveillance_control
- ftvo-transit_service_status
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Transit Vehicle OBE | Transit Vehicle Operator | transit vehicle operator display |
Communication Solutions
No communications solutions identified.Characteristics
None defined |
Interoperability | Description |
---|---|
Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Low | |
Basis | 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. |