Transit Management Center --> Transit Vehicle OBE:
transit schedule information
Definitions
transit schedule information (Information Flow): Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board.
Transit Management Center (Source 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.
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
- PT06: Transit Fleet Management
- PT09: Transit Signal Priority
- PT10: Intermittent Bus Lanes
- PT14: Multi-modal Coordination
This triple is associated with the following Functional Objects:
- Transit Center Fixed-Route Operations
- Transit Center Multi-Modal Coordination
- Transit Center Priority Management
- Transit Center Vehicle Assignment
- Transit Vehicle Schedule Management
- Transit Vehicle Signal Priority
This Triple is described by the following Functional View Data Flows:
- schedule_change_for_connection_protection
- signal_priority_rules
- transit_services_for_corrections
- transit_services_for_eta
- transit_vehicle_assignment_for_vehicle
- transit_vehicle_service_enable
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: NeTEx - Secure Wireless Internet (EU) (3)
- US: GTFS static - Secure Wireless Internet (ITS) (7)
- 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)
- Data for Distribution (TBD) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
CEN 16614-2 CEN 16614-3 CEN 12896-1 CEN 12896-2 CEN 12896-3 CEN 12896-5 CEN 12896-6 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
CEN 16614-1 |
Security
|
|
TransNet
|
|||
Access
|
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 | Destination |
Authenticable | True |
Encrypt | False |
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 | Low | Moderate | Moderate | |
Basis | This information is not sensitive. It is generally made public, to support transit system functionality. | This data contains the vehicle assignment. It should be accurate, and not easily modified. However, the bus drivers will have some knowledge about what a reasonable configuration is, and should be able to notice any unusual configurations, such as all busses being a #27. | This information is necessary for the TSP to work correctly. A few missed messages will not have a large impact. The Transit Management Center needs to know if the TV OBE does not receive the message, so it can resend it. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |