PT02: Transit Fixed-Route Operations
This service package performs automated dispatch and system monitoring for fixed-route and flexible-route transit services. This service performs scheduling activities including the creation of schedules, blocks and runs, as well as operator assignment. This service monitors the transit vehicle trip performance against the schedule and provides information displays at the Transit Management Center.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
| Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
| Maint and Constr Management Center Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Transit Management Center Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Transit Management Center User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Transit Operations Personnel | Application Usage Agreement |
| Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
| Traffic Management Center Maintainer | Traffic Management Center | Maintains |
| Traffic Management Center Manager | Traffic Management Center | Manages |
| Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
| Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
| Traffic Management Center Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | Transit Management Center Owner | Information Provision Agreement |
| Traffic Management Center Owner | Transit Management Center User | Service Usage Agreement |
| Traffic Management Center Owner | Transit Operations Personnel | Application Usage Agreement |
| Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
| Transit Management Center Maintainer | Transit Management Center | Maintains |
| Transit Management Center Manager | Transit Management Center | Manages |
| Transit Management Center Manager | Transit Operations Personnel | System Usage Agreement |
| Transit Management Center Owner | Transit Management Center Maintainer | System Maintenance Agreement |
| Transit Management Center Owner | Transit Management Center Manager | Operations Agreement |
| Transit Management Center Owner | Transit Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
| Transit Management Center Owner | Transit Vehicle OBE Owner | Information Provision Agreement |
| Transit Management Center Owner | Transit Vehicle OBE User | Service Usage Agreement |
| Transit Management Center Owner | Transit Vehicle Operator | Application Usage Agreement |
| Transit Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Transit Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
| Transit Management Center Owner | Transportation Information Center User | Service Usage Agreement |
| Transit Management Center Supplier | Transit Management Center Owner | Warranty |
| Transit Operations Personnel | Transit Management Center | Operates |
| Transit Vehicle OBE Maintainer | Transit Vehicle OBE | Maintains |
| Transit Vehicle OBE Manager | Transit Vehicle OBE | Manages |
| Transit Vehicle OBE Manager | Transit Vehicle Operator | System Usage Agreement |
| Transit Vehicle OBE Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
| Transit Vehicle OBE Owner | Transit Management Center Owner | Expectation of Data Provision |
| Transit Vehicle OBE Owner | Transit Management Center User | Service Usage Agreement |
| Transit Vehicle OBE Owner | Transit Operations Personnel | Application Usage Agreement |
| Transit Vehicle OBE Owner | Transit Operations Personnel | Vehicle Operating Agreement |
| Transit Vehicle OBE Owner | Transit Vehicle OBE Maintainer | System Maintenance Agreement |
| Transit Vehicle OBE Owner | Transit Vehicle OBE Manager | Operations Agreement |
| Transit Vehicle OBE Supplier | Transit Vehicle OBE Owner | Warranty |
| Transit Vehicle Operator | Transit Vehicle OBE | Operates |
| Transportation Information Center Maintainer | Transportation Information Center | Maintains |
| Transportation Information Center Manager | Transportation Information Center | Manages |
| Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
| Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
| Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
| Transit Management Center | Center | 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 | Center | '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. |
| Transit Vehicle OBE | Vehicle | 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 Vehicle Operator | Vehicle | 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. |
| Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Transit Center Fixed-Route Operations | 'Transit Center Fixed-Route Operations' manages fixed route transit operations. It supports creation of schedules, blocks and runs for fixed and flexible route transit services. It allows fixed-route and flexible-route transit services to disseminate schedules and automatically updates customer service operator systems with the most current schedule information. It also supports automated dispatch of transit vehicles. Current vehicle schedule adherence and optimum scenarios for schedule adjustment are also provided. It also receives and processes transit vehicle loading data. | Transit Management Center |
| Transit Center Operator Assignment | 'Transit Center Operator Assignment' automates and supports the assignment of transit vehicle operators to runs. It assigns operators to runs in a fair manner while minimizing labor and overtime services, considering operator preferences and qualifications, and automatically tracking and validating the number of work hours performed by each individual operator. It also provides an exception handling process for the operator assignment function to generate supplemental operator assignments when required by changes during the operating day. | Transit Management Center |
| Transit Center Vehicle Assignment | 'Transit Center Vehicle Assignment' assigns individual transit vehicles to vehicle blocks and downloads this information to the transit vehicle. It also provides an exception handling process for the vehicle assignment function to generate new, supplemental vehicle assignments when required by changes during the operating day. It provides an inventory management function for the transit facility which stores functional attributes about each of the vehicles owned by the transit operator. These attributes permit the planning and assignment functions to match vehicles with routes based on suitability for the types of service required by the particular routes. | Transit Management Center |
| Transit Vehicle Schedule Management | 'Transit Vehicle Schedule Management' monitors schedule performance and identifies corrective actions when a deviation is detected. It provides two-way communication between the transit vehicle and center, enabling the center to communicate with the vehicle operator and monitor on-board systems. | Transit Vehicle OBE |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| current infrastructure restrictions | 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. |
| incident information | 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. |
| road network conditions | 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 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. |
| roadway maintenance status | Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status). |
| route assignment | Route assignment information for transit vehicle operator. |
| traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. |
| traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. |
| transit and fare schedules | Transit service information including routes, schedules, and fare information. This also includes on-demand service information. |
| transit operations personnel input | 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. |
| transit operations status | 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 schedule adherence information | Dynamic transit schedule adherence and transit vehicle location information. |
| transit schedule information | 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 vehicle operator availability | Transit vehicle operator availability data that can be used to develop vehicle operator assignments and detailed operations schedules. |
| transit vehicle operator display | Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services. |
| transit vehicle operator information | Transit service instructions, wide area alerts, traffic information, road conditions, and other information for both transit and paratransit operators. |
| transit vehicle operator input | 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 schedule performance | Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle. |
| work zone information | 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. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
| F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
| G. Promote efficient system management and operation; | Improve efficiency |
| I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; | Improve resiliency and reliability |
| J. Enhance travel and tourism. | Support travel and tourism |
Associated Objective Categories 
Associated Objectives and Performance Measures
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.
Needs and Requirements
| Need | Functional Object | Requirement | ||
|---|---|---|---|---|
| 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. | Transit Center Fixed-Route Operations | 01 | The center shall generate transit routes and schedules based on such factors as parameters input by the system operator, road network conditions, incident information, operational data on current routes and schedules, and digitized map data. |
| 02 | The center shall provide the interface to the system operator to control the generation of new routes and schedules (transit services) including the ability to review and update the parameters used by the routes and schedules generation processes and to initiate these processes | |||
| 03 | The center shall generate special routes and schedules to support an incident, disaster, evacuation, or other emergency. | |||
| 05 | The center shall collect transit operational data for use in the generation of routes and schedules. | |||
| 11 | The center shall provide an interface to the archive data repository to enable the operator to retrieve historical operating data for use in planning transit routes and schedules. | |||
| 02 | Transit Operations needs to be able to disseminate transit schedules for fixed route or flexible route transit routes to traveler information centers. | Transit Center Fixed-Route Operations | 07 | The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large numbers of vehicles. |
| 08 | The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the premature termination of some services, etc. | |||
| 10 | The center shall disseminate up-to-date schedules and route information to other centers for fixed and flexible route services. | |||
| Transit Vehicle Schedule Management | 07 | The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations that would then lead to schedule corrective actions. | ||
| 03 | Transit Operations needs to be able to dispatch transit vehicles for fixed route or flexible route runs. | Transit Center Fixed-Route Operations | 04 | The center shall dispatch fixed route or flexible route transit vehicles. |
| 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. | Transit Center Operator Assignment | 01 | The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies. |
| 02 | The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated hours, plus health and vacation commitments. | |||
| 03 | The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority, and transit vehicle availability. | |||
| 04 | The center shall provide an interface through which the transit vehicle operator information can be maintained - either from the transit vehicle operator, center personnel, or other functions. | |||
| 05 | The center shall generate supplemental vehicle operator assignments as required due to change events that occur during the operating day. | |||
| Transit Center Vehicle Assignment | 01 | The center shall assign individual transit vehicles to transit blocks. | ||
| 02 | The center shall download vehicle assignments to the transit vehicle prior to the start of the day's operations. | |||
| 03 | The center shall provide an exception handling process for the vehicle assignment function. This process shall generate new supplemental vehicle assignments as required due to change events which occur during the operating day. | |||
| 04 | The center shall provide an inventory management function for the transit facility that stores functional attributes about each vehicle owned by the transit operator. The functional attributes permit the planning and assignment functions to match vehicles with routes based on suitability for the types of service required by the particular routes. | |||
| 05 | The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment planning. | |||
| 06 | The center shall provide transit operations personnel with the capability to update transit vehicle assignments and receive reports on transit vehicle inventory status. | |||
| Transit Vehicle Schedule Management | 01 | The transit vehicle shall receive a vehicle assignment including transit route information, transit service instructions, traffic information, road conditions, and other information for the operator. | ||
| 08 | The transit vehicle shall notify the transit center of vehicle location and operational status as the vehicle exits and returns to the transit facility to support future vehicle assignments. | |||
| 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. | Transit Center Fixed-Route Operations | 06 | The center shall provide instructions or corrective actions to the transit vehicle operators based upon operational needs. |
| 13 | The center shall monitor transit vehicle schedule adherence in order to manage transit vehicle operations. | |||
| Transit Vehicle Schedule Management | 02 | The transit vehicle shall use the route information and its current location to determine the deviation from the predetermined schedule. | ||
| 03 | The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops. | |||
| 04 | The transit vehicle shall determine scenarios to correct the schedule deviation. | |||
| 05 | The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle operator if the deviation is small, or the transit vehicle is operating in an urban area. | |||
| 06 | The transit vehicle shall send the schedule deviation and estimated arrival time information to the center. | |||
| 06 | Transit Operations need to have real time information about the road network in order to increase the effectiveness of operations for fixed route or flexible route transit. | Transit Center Fixed-Route Operations | 09 | The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway conditions, asset restrictions, work plans, etc. |
| 12 | The center shall receive information from Traffic Operations concerning road network conditions, incidents, and other impacts to the road network. | |||
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Maint and Constr Management Center | Low | High | Moderate | Class 3 |
| Traffic Management Center | High | Moderate | Moderate | Class 4 |
| Transit Management Center | High | High | Moderate | Class 4 |
| Transit Vehicle OBE | Low | Moderate | Moderate | Class 1 |
| Transportation Information Center | Low | Low | Moderate | Class 1 |
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Maint and Constr Management Center | Transit Management Center | current infrastructure restrictions | Low | High | Moderate |
| Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. | Map data including restriction data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. | Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH. | |||
| Maint and Constr Management Center | Transit Management Center | roadway maintenance status | Low | Moderate | Moderate |
| Roadway maintenance status data is distributed to a host of places including travelers, so there is no justification for obfuscation. | Road maintenance data needs to be accurate and available so that the Transit Management Center can make appropriate decisions, such as revised bus routing. Inappropriate decisions may significantly affect traffic and individual travel experiences. | Road maintenance data needs to be accurate and available so that the Transit Management Center can make appropriate decisions, such as revised bus routing. Inappropriate decisions may significantly affect traffic and individual travel experiences. | |||
| Maint and Constr Management Center | Transit Management Center | work zone information | Low | Moderate | Moderate |
| Eventually intended for public distribution, so no need to obfuscate. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. | |||
| Traffic Management Center | Transit Management Center | incident information | High | Moderate | Moderate |
| This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the TMC should be able to know if the EMC has received a message. | |||
| Traffic Management Center | Transit Management Center | road network conditions | Low | Moderate | Moderate |
| No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
| Traffic Management Center | Transit Management Center | traffic image meta data | Low | Moderate | Moderate |
| Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
| Traffic Management Center | Transit Management Center | traffic images | Low | Moderate | Moderate |
| Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While availability of imagery is useful for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally, though it could be LOW. | |||
| Transit Management Center | Transit Operations Personnel | transit operations status | Moderate | High | High |
| 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. | |||
| Transit Management Center | Transit Vehicle OBE | transit schedule information | Low | Moderate | Moderate |
| 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. | |||
| Transit Management Center | Transit Vehicle OBE | transit vehicle operator information | Low | Moderate | Moderate |
| While specifically relevant for transit operations, does not contain any information that would not be disseminated to other channels including the public. | The transit vehicle operator will rely on this information to make decisions. Unavailable, Inaccurate or corrupted data will lead to difficulties maintaining vehicle performance (schedule adherence, etc.) | The transit vehicle operator will rely on this information to make decisions. Unavailable, Inaccurate or corrupted data will lead to difficulties maintaining vehicle performance (schedule adherence, etc.) | |||
| Transit Management Center | Transit Vehicle Operator | route assignment | Moderate | High | High |
| 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. | |||
| Transit Management Center | Transportation Information Center | transit and fare schedules | Low | Moderate | Moderate |
| Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally, though it could be LOW depending on the level of projected updates. | |||
| Transit Management Center | Transportation Information Center | transit schedule adherence information | Low | Moderate | Moderate |
| Eventually intended for public consumption, so no need to obfuscate. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | |||
| Transit Operations Personnel | Transit Management Center | transit operations personnel input | Moderate | High | High |
| 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. | |||
| Transit Vehicle OBE | Transit Management Center | transit vehicle schedule performance | Low | Moderate | Low |
| This information is directly observable, and in most instances it is made publically available. | This information may be used to influence the decision about whether or not to make a traffic control priority request on behalf of the transit vehicle. If it is incorrect it may cause the transit management center to send out incorrect traffic control priority requests, which may delay traffic. | There should not be any catastrophic failures caused if this data is occasionally missing. | |||
| Transit Vehicle OBE | Transit Vehicle Operator | transit vehicle operator display | Low | Moderate | Low |
| This should not include any sensitive information. It would be possible for a person standing behind the driver to observe the information transmitted. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This entire application should not directly affect the drivers driving habits. The operator should still be slowing and stopping at yellow or red lights, along with observing all other driving regulations. DISC: Original V2I analysis classified this as LOW. | Even if the operator is not made aware of the signal preemption, the system should still operate correctly. The operator should be using the traffic lights to influence their decision about whether or not to stop, not the display. | |||
| Transit Vehicle Operator | Transit Management Center | transit vehicle operator availability | Moderate | Moderate | Moderate |
| PII by definition, including when an operator may be working and when he may not. | Will be used to make operator assignments; if this data is corrupted or not available those assignments may be made in error. | Will be used to make operator assignments; if this data is corrupted or not available those assignments may be made in error or not include those operators for whom the flow was interrupted. | |||
| Transit Vehicle Operator | Transit Vehicle OBE | transit vehicle operator input | Low | Moderate | Low |
| 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. | |||
Standards
Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
System Requirements
| System Requirement | Need | ||
|---|---|---|---|
| 001 | The system shall generate transit routes and schedules based on such factors as parameters input by the system operator, road network conditions, incident information, operational data on current routes and schedules, and digitized map data. | 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. |
| 002 | The system shall provide the interface to the system operator to control the generation of new routes and schedules (transit services) including the ability to review and update the parameters used by the routes and schedules generation processes and to i | 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. |
| 003 | The system shall generate special routes and schedules to support an incident, disaster, evacuation, or other emergency. | 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. |
| 004 | The system shall dispatch fixed route or flexible route transit vehicles. | 03 | Transit Operations needs to be able to dispatch transit vehicles for fixed route or flexible route runs. |
| 005 | The system shall collect transit operational data for use in the generation of routes and schedules. | 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. |
| 006 | The system shall provide instructions or corrective actions to the transit vehicle operators based upon operational needs. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 007 | The system shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large numbers of vehicles. | 02 | Transit Operations needs to be able to disseminate transit schedules for fixed route or flexible route transit routes to traveler information centers. |
| 008 | The system shall generate the necessary corrective actions which may involve more than the vehicles concerned and more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the premature termina | 02 | Transit Operations needs to be able to disseminate transit schedules for fixed route or flexible route transit routes to traveler information centers. |
| 009 | The system shall exchange information with Maintenance and Construction Operations concerning work zones, roadway conditions, asset restrictions, work plans, etc. | 06 | Transit Operations need to have real time information about the road network in order to increase the effectiveness of operations for fixed route or flexible route transit. |
| 010 | The system shall disseminate up-to-date schedules and route information to other centers for fixed and flexible route services. | 02 | Transit Operations needs to be able to disseminate transit schedules for fixed route or flexible route transit routes to traveler information centers. |
| 011 | The system shall provide an interface to the archive data repository to enable the operator to retrieve historical operating data for use in planning transit routes and schedules. | 01 | Transit Operations needs to be able to create and update schedules for fixed route or flexible route transit routes in order to plan transit operations. |
| 012 | The system shall receive information from Traffic Operations concerning road network conditions, incidents, and other impacts to the road network. | 06 | Transit Operations need to have real time information about the road network in order to increase the effectiveness of operations for fixed route or flexible route transit. |
| 013 | The system shall monitor transit vehicle schedule adherence in order to manage transit vehicle operations. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 014 | The system shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing the transit vehi | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 015 | The system shall assess the transit vehicle operator's availability based on previous work assignments, accumulated hours, plus health and vacation commitments. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 016 | The system shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority, and transit vehicle availability. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 017 | The system shall provide an interface through which the transit vehicle operator information can be maintained - either from the transit vehicle operator, center personnel, or other functions. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 018 | The system shall generate supplemental vehicle operator assignments as required due to change events that occur during the operating day. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 019 | The system shall assign individual transit vehicles to transit blocks. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 020 | The system shall download vehicle assignments to the transit vehicle prior to the start of the day's operations. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 021 | The system shall provide an exception handling process for the vehicle assignment function. This process shall generate new supplemental vehicle assignments as required due to change events which occur during the operating day. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 022 | The system shall provide an inventory management function for the transit facility that stores functional attributes about each vehicle owned by the transit operator. The functional attributes permit the planning and assignment functions to match vehicle | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 023 | The system shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment planning. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 024 | The system shall provide transit operations personnel with the capability to update transit vehicle assignments and receive reports on transit vehicle inventory status. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 025 | The system shall receive a vehicle assignment including transit route information, transit service instructions, traffic information, road conditions, and other information for the operator. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |
| 026 | The system shall use the route information and its current location to determine the deviation from the predetermined schedule. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 027 | The system shall calculate the estimated times of arrival (ETA) at transit stops. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 028 | The system shall determine scenarios to correct the schedule deviation. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 029 | The system shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle operator if the deviation is small, or the transit vehicle is operating in an urban area. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 030 | The system shall send the schedule deviation and estimated arrival time information to the center. | 05 | Transit Operations need to be able to monitor transit vehicle schedule adherence in order to manage fixed route or flexible route transit operations. |
| 031 | The system shall support the operations of a flexible route service. This may include requests for route deviations that would then lead to schedule corrective actions. | 02 | Transit Operations needs to be able to disseminate transit schedules for fixed route or flexible route transit routes to traveler information centers. |
| 032 | The system shall notify the transit center of vehicle location and operational status as the vehicle exits and returns to the transit facility to support future vehicle assignments. | 04 | Transit Operations need to be able to schedule blocks (vehicle assignments) and runs (operator assignments) for fixed route or flexible route transit operations. |