NMDOT Park and Ride Dispatch - Transit Management Functionality

Send Your Comments

Subsystem Description

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.

Functional Area: Transit Center Fixed-Route Operations

Management of fixed route transit operations. Planning, scheduling, and dispatch associated with fixed and flexible route transit services. Updates customer service operator systems, and provides current vehicle schedule adherence and optimum scenarios for schedule adjustment.

IDRequirementStatus
1The 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.Planned
3The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other emergency.Planned
4The center shall dispatch fixed route or flexible route transit vehiclesPlanned
5The center shall collect transit operational data for use in the generation of routes and schedules.Planned
9The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway conditions, asset restrictions, work plans, etc.Planned

Functional Area: Transit Center Information Services

Provide interactive traveler information to travelers (on-board transit vehicles, at stops/stations, using personal devices), traveler information service providers, media, and other transit organizations. Includes routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, yellow pages, and special events.

IDRequirementStatus
1The center shall provide travelers using public transportation with traffic and advisory information upon request. Such information may include transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, and special events.Planned
2The center shall provide transit information to the media including details of deviations from schedule of regular transit services.Planned
3The center shall exchange transit schedules, real-time arrival information, fare schedules, and general transit service information with other transit organizations to support transit traveler information systems.Planned
4The center shall provide transit service information to traveler information service providers including routes, schedules, schedule adherence, and fare information as well as transit service information during evacuation.Planned

Functional Area: Transit Center Multi-Modal Coordination

Coordinate schedules with other agencies and modes, including transit transfer cluster and transfer point information.

IDRequirementStatus
1The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and construction operations, parking management, and other surface or air transportation modes.Planned
2The center shall share transfer cluster and transfer point information with multimodal transportation service providers, other transit agencies, and traveler information service providers. A transfer cluster is a collection of stop points, stations, or terminals where transfers can be made conveniently.Planned

Functional Area: Transit Center Vehicle Tracking

Monitoring transit vehicle locations via interactions with on-board systems. Furnish users with real-time transit schedule information and maintain interface with digital map providers.

IDRequirementStatus
1The center shall monitor the locations of all transit vehicles within its network.Planned
2The center shall determine adherence of transit vehicles to their assigned schedule.Planned
4The center shall provide transit operational data to traveler information service providers.Planned

Functional Area: Transit Data Collection

Collection and storage of transit management data. For use by operations personnel or data archives in the region.

IDRequirementStatus
1The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc.Planned
2The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.Planned
3The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself.Planned
4The center shall be able to produce sample products of the data available.Planned