Transit Management Center --> Transit Operations Personnel:
transit operations status
Definitions
transit operations status (Information Flow): Presentation of information to transit operations personnel including accumulated schedule and fare information, ridership and on-time performance information, emergency response plans, transit personnel information, maintenance records, and other information intended to support overall planning and management of a transit property.
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 Operations Personnel (Destination Physical Object): 'Transit Operations Personnel' represents the people that are responsible for fleet management, maintenance operations, and scheduling activities of the transit system. These different roles represent a variety of individuals in the transit industry. Within the transit industry the person responsible for fleet management is known by many names: Street Supervisor, Starter, Dispatcher, Supervisor, Traffic Controller, Transportation Coordinator. This person actively monitors, controls, and modifies the transit fleet routes and schedules on a day to day basis (dynamic scheduling). The modifications will take account of abnormal situations such as vehicle breakdown, vehicle delay, detours around work zones or incidents (detour management, connection protection, and service restoration), and other causes of route or schedule deviations. Transit operations personnel are also responsible for demand responsive transit operation and for managing emergency situations within the transit network such as silent alarms on board transit vehicles, or the remote disabling of the vehicle. In addition the Transit Operations Personnel may be responsible for assigning vehicle operators to routes, checking vehicle operators in and out, and managing transit stop issues. This object also represents the personnel in the transit garage that are responsible for maintenance of the transit fleets, including monitoring vehicle status, matching vehicles with operators, and maintenance checking of transit vehicles. Finally, it represents the people responsible for planning, development, and management of transit routes and schedules.
Included In
This Triple is in the following Service Packages:
- PS10: Wide-Area Alert
- PS11: Early Warning System
- PS12: Disaster Response and Recovery
- PS13: Evacuation and Reentry Management
- PT01: Transit Vehicle Tracking
- PT02: Transit Fixed-Route Operations
- PT03: Dynamic Transit Operations
- PT04: Transit Fare Collection Management
- PT05: Transit Security
- PT06: Transit Fleet Management
- PT07: Transit Passenger Counting
- PT08: Transit Traveler Information
- PT09: Transit Signal Priority
- PT14: Multi-modal Coordination
- PT17: Transit Connection Protection
This triple is associated with the following Functional Objects:
- Transit Center Connection Protection
- Transit Center Fare Management
- Transit Center Fixed-Route Operations
- Transit Center Information Services
- Transit Center Multi-Modal Coordination
- Transit Center Operator Assignment
- Transit Center Paratransit Operations
- Transit Center Passenger Counting
- Transit Center Priority Management
- Transit Center Security
- Transit Center Vehicle Assignment
- Transit Center Vehicle Tracking
- Transit Evacuation Support
- Transit Garage Maintenance
This Triple is described by the following Functional View Data Flows:
- ttrop-archive_status
- ttrop-coordination_request
- ttrop-emergency_plan_response
- ttrop-emergency_request
- ttrop-infrastructure_integrity_status
- ttrop-media_parameters
- ttrop-parameters
- ttrop-paratransit_service
- ttrop-parking_information
- ttrop-passenger_loading_error
- ttrop-potential_incidents_alarm
- ttrop-proposed_corrections
- ttrop-response_parameter_output
- ttrop-technician_information
- ttrop-traffic_and_maint_and_const_data
- ttrop-transaction_reports
- ttrop-transit_fare_output
- ttrop-transit_operations_information
- ttrop-transit_services_output
- ttrop-transit_vehicle_data
- ttrop-transit_vehicle_disable_status
- ttrop-transit_vehicle_inventory
- ttrop-transit_vehicle_maintenance_information
- ttrop-transit_vehicle_operator_information
- ttrop-transp_information_for_transit_operations
- ttrop-weather_information
- ttrop-wide_area_alert_notification
- ttrop-work_schedule
This Triple has the following triple relationships:
| None |
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 | Moderate | High | High | |
| Basis | 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. | |