Transit Management (Subsystem*)
The Transit Management Subsystem (TRMS) 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 subsystem's interfaces allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems. This subsystem receives special event and real-time incident data from the traffic management subsystem. It provides current transit operations data to other center subsystems. It interfaces with the Emergency Management Subsystem to allow coordinated use of transit vehicles to facilitate response to major emergencies or evacuations. The Transit Management Subsystem collects and stores accurate ridership levels and implements fare structures for use in electronic fare collection. It collects operational and maintenance data from transit vehicles, manages vehicle service histories, and assigns vehicle operators and maintenance personnel to vehicles and routes. The Transit Management Subsystem also provides the capability for automated planning and scheduling of public transit operations. The scheduling capability includes schedule writing, block building and runcutting. The subsystem furnishes travelers with real-time travel information, continuously updated schedules, schedule adherence information, transfer options, and transit routes and fares. In addition, the subsystem supports transit security features. This includes monitoring silent alarms, both passenger and operator initiated, on-board transit vehicles. It also includes the capability to support transit vehicle operator authentication and the capability to remotely disable a transit vehicle. The subsystem includes the capability to monitor for a transit vehicle being off the assigned route. The subsystem also includes the capability to alert operators and police to potential incidents identified by these security features.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Transit Center Connection Protection (Equipment Package*)
PSpecs: - Transit Center Fare Management (Equipment Package*)
PSpecs:- 4.2.3.5-Manage Transit Operational Data Store
- 4.2.3.7-Provide Interface for Other Transit Management Data
- 4.6.7-Manage Transit Vehicle Advanced Payments
- 5.4.4-Process Fare Payment Violations
- 5.4.5-Process Vehicle Fare Collection Violations
- 5.4.7-Process Roadside Fare Collection Violations
- 7.3.1.1-Register for Advanced Transit Fare Payment
- 7.3.1.2-Determine Advanced Transit Fares
- 7.3.1.3-Manage Transit Fare Financial Processing
- 7.3.1.4-Check for Advanced Transit Fare Payment
- 7.3.1.5-Bill Traveler for Transit Fare
- 7.3.1.6-Collect Bad Transit Fare Payment Data
- 7.3.1.7-Update Transit Fare Data
- 7.3.3-Get Traveler Image for Violation
- 7.4.1.5-Process Traveler Other Services Payments
- Transit Center Fixed-Route Operations (Equipment Package*)
PSpecs:- 4.1.4-Manage Transit Vehicle Deviations
- 4.1.6-Manage Transit Vehicle Operations
- 4.2.2-Provide Transit Plans Store Interface
- 4.2.3.1-Generate Transit Routes
- 4.2.3.2-Generate Transit Schedules
- 4.2.3.3-Produce Transit Service Data for External Use
- 4.2.3.4-Provide Transit Operations Personnel Interface for Services Generation
- 4.2.3.5-Manage Transit Operational Data Store
- 4.2.3.6-Produce Transit Service Data for Manage Transit Use
- Transit Center Information Services (Equipment Package*)
PSpecs: - Transit Center Multi-Modal Coordination (Equipment Package*)
PSpecs:- 4.1.4-Manage Transit Vehicle Deviations
- 4.1.5-Provide Transit Vehicle Status and Probe Information
- 4.1.6-Manage Transit Vehicle Operations
- 4.2.3.2-Generate Transit Schedules
- 4.2.3.3-Produce Transit Service Data for External Use
- 4.2.3.4-Provide Transit Operations Personnel Interface for Services Generation
- 4.2.3.7-Provide Interface for Other Transit Management Data
- 4.2.3.8-Provide Interface for Transit Service Raw Data
- Transit Center Paratransit Operations (Equipment Package*)
PSpecs:- 4.1.4-Manage Transit Vehicle Deviations
- 4.1.6-Manage Transit Vehicle Operations
- 4.2.1.1-Process Demand Responsive Transit Trip Request
- 4.2.1.2-Compute Demand Responsive Transit Vehicle Availability
- 4.2.1.3-Generate Demand Responsive Transit Schedule and Routes
- 4.2.1.4-Confirm Demand Responsive Transit Schedule and Route
- 4.2.3.3-Produce Transit Service Data for External Use
- 4.2.3.4-Provide Transit Operations Personnel Interface for Services Generation
- Transit Center Passenger Counting (Equipment Package*)
PSpecs: - Transit Center Security (Equipment Package*)
PSpecs:- 4.1.6-Manage Transit Vehicle Operations
- 4.2.3.7-Provide Interface for Other Transit Management Data
- 4.4.1-Provide Transit Security and Emergency Management
- 4.4.2-Coordinate Multiple Agency Responses to Transit Incidents
- 4.4.3-Generate Responses for Transit Incidents
- 4.4.4-Provide Transit Operations Personnel Security Interface
- Transit Center Signal Priority (Equipment Package*)
PSpecs: - Transit Center Vehicle Tracking (Equipment Package*)
PSpecs: - Transit Data Collection (Equipment Package*)
PSpecs:- 4.2.4-Manage Transit Archive Data
- Transit Environmental Monitoring (Equipment Package*)
PSpecs:- 4.1.6-Manage Transit Vehicle Operations
- Transit Evacuation Support (Equipment Package*)
PSpecs: - Transit Garage Maintenance (Equipment Package*)
PSpecs:- 4.1.5-Provide Transit Vehicle Status and Probe Information
- 4.1.6-Manage Transit Vehicle Operations
- 4.3.1-Monitor Transit Vehicle Condition
- 4.3.2-Generate Transit Vehicle Maintenance Schedules
- 4.3.3-Generate Technician Work Assignments
- 4.3.4-Monitor And Verify Maintenance Activity
- 4.3.5-Report Transit Vehicle Information
- 4.3.6-ManageTransit Vehicle Inventory
- 4.3.7-Manage Transit Vehicle Operations Data Store
- Transit Transportation Operations Data Collection (Equipment Package*)
PSpecs:- 4.1.6-Manage Transit Vehicle Operations
- Transit Vehicle Assignment (Equipment Package*)
PSpecs: - Transit Vehicle Operator Assignment (Equipment Package*)
PSpecs:- 4.5.1-Assess Transit Vehicle Operator Performance
- 4.5.2-Assess Transit Vehicle Operator Availability
- 4.5.3-Access Transit Vehicle Operator Cost Effectiveness
- 4.5.4-Assess Transit Vehicle Operator Eligibility
- 4.5.5-Generate Transit Vehicle Operator Route Assignments
- 4.5.6-Report Transit Vehicle Operator Information
- 4.5.7-Provide Transit Vehicle Operator Information Store Interface
Inputs/Outputs: Architecture Flows* and Data Flows*
Alerting and Advisory Systems
Transit Management
- alerts and advisories (Architecture Flow*) - Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system.
Data Flows*:
Archived Data Management
Transit Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*: - archived data products (Architecture Flow*) - Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
Data Flows*:
Emergency Management
Transit Management
- alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This flow may also identify specific information that should not be released to the public.
Data Flows*: - emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*: - emergency transit service request (Architecture Flow*) - Request to modify transit service and fare schedules to address emergencies, including requests for transit services to evacuate people from and/or deploy response agency personnel to an emergency scene. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of transit resources.
Data Flows*: - evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*: - threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*: - transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
Event Promoters
Transit Management
- event plans (Architecture Flow*) - Plans for major events possibly impacting traffic.
Data Flows*:
Financial Institution
Transit Management
- transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
Data Flows*:
Information Service Provider
Transit Management
- demand responsive transit request (Architecture Flow*) - Request for paratransit support.
Data Flows*: - selected routes (Architecture Flow*) - Routes selected based on route request criteria.
Data Flows*: - transit information request (Architecture Flow*) - Request for transit operations information including schedule and fare information. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*: - transit trip request (Architecture Flow*) - Request for a transit trip plan that is responsive to traveler requirements such as schedule, cost, or duration.
Data Flows*: - transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:
Maintenance and Construction Management
Transit Management
- current asset restrictions (Architecture Flow*) - Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
Data Flows*: - maint and constr work plans (Architecture Flow*) - Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
Data Flows*: - road weather information (Architecture Flow*) - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
Data Flows*: - roadway maintenance status (Architecture Flow*) - Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
Data Flows*: - work zone information (Architecture Flow*) - Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
Data Flows*:
Map Update Provider
Transit Management
- map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
Multimodal Transportation Service Provider
Transit Management
- multimodal service data (Architecture Flow*) - Multimodal transportation schedules and other service information.
Data Flows*: - service response (Architecture Flow*) - Multimodal (possibly non-roadway) transit provider services information and trip reservation confirmations.
Data Flows*:
Other Transit Management
Transit Management
- transit fare coordination (Architecture Flow*) - Fare and pricing information shared between local/regional transit organizations.
Data Flows*: - transit service coordination (Architecture Flow*) - Schedule coordination information shared between local/regional transit organizations.
Data Flows*: - transit traveler information coordination (Architecture Flow*) - Transit schedules, real-time arrival information, fare schedules, and general transit service information shared between transit organizations to support transit traveler information systems.
Data Flows*:
Parking Management
Transit Management
- parking information (Architecture Flow*) - General parking information and status, including current parking availability.
Data Flows*:
Personal Information Access
Transit Management
- transit information user request (Architecture Flow*) - Request for special transit routing, real-time schedule information, and availability information.
Data Flows*: - trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*:
Remote Traveler Support
Transit Management
- transit fare and passenger status (Architecture Flow*) - Information provided from the traveler location that supports fare payments, passenger data, and associated record-keeping.
Data Flows*: - transit information user request (Architecture Flow*) - Request for special transit routing, real-time schedule information, and availability information.
Data Flows*: - trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*:
Surface Transportation Weather Service
Transit Management
- transportation weather information (Architecture Flow*) - Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making.
Data Flows*:
Traffic Management
Transit Management
- incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - request transit information (Architecture Flow*) - Request for transit service information and current transit status.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic control priority status (Architecture Flow*) - Status of signal priority request functions at the roadside (e.g. enabled or disabled).
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*: - transit demand management request (Architecture Flow*) - Request to change the demand for transit facility use through pricing or other mechanisms.
Data Flows*:
Transit Management
Archived Data Management
- archived data product requests (Architecture Flow*) - A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
Data Flows*: - transit archive data (Architecture Flow*) - Data used to describe and monitor transit demand, fares, operations, and system performance. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Transit Management
Emergency Management
- alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*: - emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*: - emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
Data Flows*: - emergency transit service response (Architecture Flow*) - Response indicating changes to transit service, fares, and/or restrictions that will be made and status of transit resources to be deployed to support emergency response and/or evacuation.
Data Flows*: - transit emergency data (Architecture Flow*) - Initial notification of transit emergency at a transit stop or on transit vehicles and further coordination as additional details become available and the response is coordinated.
Data Flows*: - transit system status assessment (Architecture Flow*) - Assessment of damage sustained by the public transportation system including location and extent of the damage, current operational status including an estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
Transit Management
Enforcement Agency
- payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
Data Flows*:
Transit Management
Event Promoters
- event confirmation (Architecture Flow*) - Confirmation that special event details have been received and processed.
Data Flows*:
Transit Management
Financial Institution
- payment request (Architecture Flow*) - Request for payment from financial institution.
Data Flows*:
Transit Management
Information Service Provider
- demand responsive transit plan (Architecture Flow*) - Plan regarding overall demand responsive transit schedules and deployment.
Data Flows*: - emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
Data Flows*: - transit and fare schedules (Architecture Flow*) - Transit service information including routes, schedules, and fare information.
Data Flows*: - transit incident information (Architecture Flow*) - Information on transit incidents that impact transit services for public dissemination.
Data Flows*: - transit probe data (Architecture Flow*) - Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
Data Flows*: - transit request confirmation (Architecture Flow*) - Confirmation of a request for transit information or service.
Data Flows*: - transit schedule adherence information (Architecture Flow*) - Dynamic transit schedule adherence and transit vehicle location information.
Data Flows*: - transit trip plan (Architecture Flow*) - An origin-destination transit trip that may involve multiple modes and connections. (could use current trip plan that is PIAS to ISP, but since this is center to center a separate AF might be called for).
Data Flows*:
Transit Management
Maintenance and Construction Management
- work plan feedback (Architecture Flow*) - Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system.
Data Flows*:
Transit Management
Map Update Provider
- map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
Transit Management
Media
- transit incidents for media (Architecture Flow*) - Report of an incident impacting transit operations for public dissemination through the media.
Data Flows*: - transit information for media (Architecture Flow*) - Report of transit schedule deviations for public dissemination through the media.
Data Flows*:
Transit Management
Multimodal Transportation Service Provider
- service request (Architecture Flow*) - Request to multimodal (possibly non-roadway) transit provider for general services information and specific trip information or reservation.
Data Flows*: - transit multimodal information (Architecture Flow*) - Transit schedule information for coordination at modal interchange points.
Data Flows*:
Transit Management
Other Transit Management
- transit fare coordination (Architecture Flow*) - Fare and pricing information shared between local/regional transit organizations.
Data Flows*: - transit service coordination (Architecture Flow*) - Schedule coordination information shared between local/regional transit organizations.
Data Flows*: - transit traveler information coordination (Architecture Flow*) - Transit schedules, real-time arrival information, fare schedules, and general transit service information shared between transit organizations to support transit traveler information systems.
Data Flows*:
Transit Management
Parking Management
- parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
Transit Management
Personal Information Access
- personal transit information (Architecture Flow*) - General and personalized transit information for a particular fixed route, flexible route, or paratransit system.
Data Flows*: - trip plan (Architecture Flow*) - A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows*:
Transit Management
Remote Traveler Support
- transit fare information (Architecture Flow*) - Information provided by transit management that supports fare payment transactions and passenger data collection.
Data Flows*: - transit traveler information (Architecture Flow*) - Transit information prepared to support transit users and other travelers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information.
Data Flows*: - trip plan (Architecture Flow*) - A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows*:
Transit Management
Surface Transportation Weather Service
- transportation weather information request (Architecture Flow*) - A request for transportation weather information that may specify the area of interest (a geographic region, particular routes within a region, specific road segments), the type of information that is required, the desired spatial resolution of the information, and time horizon.
Data Flows*:
Transit Management
Traffic Management
- emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
Data Flows*: - traffic control priority request (Architecture Flow*) - Request for signal priority at one or more intersections along a particular route.
Data Flows*: - transit demand management response (Architecture Flow*) - Response to transit demand management change requests indicating level of compliance with request.
Data Flows*: - transit probe data (Architecture Flow*) - Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
Data Flows*: - transit system data (Architecture Flow*) - Current transit system operations information indicating current transit routes, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.
Data Flows*:
Transit Management
Transit Operations Personnel
- transit operations status (Architecture 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.
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
Transit Management
Transit Vehicle
- alarm acknowledge (Architecture Flow*) - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
Data Flows*: - bad tag list (Architecture Flow*) - List of invalid transit user tags which may have previously failed a fare payment transaction.
Data Flows*: - fare management information (Architecture Flow*) - Transit fare information and transaction data used to manage transit fare processing on the transit vehicle.
Data Flows*: - remote vehicle disable (Architecture Flow*) - Signal used to remotely disable a transit vehicle.
Data Flows*: - request for vehicle measures (Architecture Flow*) - Request for vehicle performance and maintenance data collected by onboard sensors.
Data Flows*: - transit schedule information (Architecture 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.
Data Flows*: - transit traveler information (Architecture Flow*) - Transit information prepared to support transit users and other travelers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information.
Data Flows*: - transit vehicle operator authentication update (Architecture Flow*) - Results of authentication process or update of on-board authentication database.
Data Flows*: - transit vehicle operator information (Architecture Flow*) - Transit service instructions, wide area alerts, traffic information, road conditions, and other information for both transit and paratransit operators.
Data Flows*:
Transit Management
Transit Vehicle Operator
- route assignment (Architecture Flow*) - Route assignment information for transit vehicle operator.
Data Flows*:
Transit Operations Personnel
Transit Management
- transit operations personnel inputs (Architecture Flow*) - User input from transit operations personnel including instructions governing service availability, schedules, emergency response plans, transit personnel assignments, transit maintenance requirements, and other inputs that establish general system operating requirements and procedures.
Data Flows*:- ftrop-alert_notification_status
- ftrop-approved_corrections
- ftrop-archive_commands
- ftrop-coordination_data
- ftrop-disable_transit_vehicle
- ftrop-emergency_plan_response
- ftrop-fare_updates
- ftrop-initiate_service_updates
- ftrop-media_parameter_request
- ftrop-media_parameter_updates
- ftrop-parking_information_request
- ftrop-passenger_loading_updates
- ftrop-planning_parameters
- ftrop-planning_parameters_update_request
- ftrop-request_fare_output
- ftrop-request_response_parameter_output
- ftrop-request_transit_vehicle_data
- ftrop-response_parameters
- ftrop-security_action
- ftrop-technician_information_request
- ftrop-technician_information_updates
- ftrop-trans_weather_info_request
- ftrop-transit_display_update_request
- ftrop-transit_operations_inputs
- ftrop-transit_services_output_request
- ftrop-transit_vehicle_inventory_input
- ftrop-transit_vehicle_maintenance_information_request
- ftrop-transit_vehicle_maintenance_specs
- ftrop-transit_vehicle_maintenance_updates
- ftrop-transit_vehicle_operator_information_request
- ftrop-transit_vehicle_operator_information_updates
- ftrop-transit_vehicle_operator_route_preferences
Transit Vehicle
Transit Management
- alarm notification (Architecture Flow*) - Notification of activation of an audible or silent alarm by a traveler in a public area or by a transit vehicle operator using an on-board device.
Data Flows*: - demand response passenger and use data (Architecture Flow*) - Data collected on board a demand response vehicle relating to the picking up and discharging of passengers.
Data Flows*: - fare collection data (Architecture Flow*) - Fare collection information including the summary of on-board fare system data and financial payment transaction data.
Data Flows*: - request for bad tag list (Architecture Flow*) - Request for list of bad vehicle tag IDs.
Data Flows*: - transit traveler request (Architecture Flow*) - Request by a Transit traveler to summon assistance, request transit information, or request any other transit services.
Data Flows*: - transit user information (Architecture Flow*) - Information about individual transit users boarding a transit vehicle, used to track a user's progress on a scheduled transit trip.
Data Flows*: - transit vehicle conditions (Architecture Flow*) - Operating conditions of transit vehicle (e.g., engine running, oil pressure, fuel level and usage).
Data Flows*: - transit vehicle loading data (Architecture Flow*) - Data collected on board the transit vehicle relating to passenger boarding and alighting.
Data Flows*: - transit vehicle location data (Architecture Flow*) - Current transit vehicle location and related operational conditions data provided by a transit vehicle.
Data Flows*: - transit vehicle operator authentication information (Architecture Flow*) - Information regarding on-board transit operator authentication
Data Flows*: - transit vehicle schedule performance (Architecture Flow*) - Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle.
Data Flows*:
Transit Vehicle Operator
Transit Management
- transit vehicle operator availability (Architecture Flow*) - Transit vehicle operator availability data that can be used to develop vehicle operator assignments and detailed operations schedules.
Data Flows*:
Weather Service
Transit Management
- weather information (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
Data Flows*:

