Oshkosh Transit - Transit Management Functionality
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 Paratransit Operations
Management of demand response transit services, including paratransit. Planning and scheduling of these services. Supports automated vehicle dispatch and automatically updates customer service operator systems.
| ID | Requirement | Status |
|---|---|---|
| 1 | The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests may include traveler information service providers. | Planned |
| 2 | The center shall monitor the operational status of the demand response vehicles including status of passenger pick-up and drop-off. | Planned |
| 3 | The center shall generate demand response transit (including paratransit) routes and schedules based on such factors as parameters input by the system operator, what other demand responsive transit schedules have been planned, the availability and location of vehicles, the relevance of any fixed transit routes and schedules, road network information, and incident information. | Planned |
| 5 | The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway conditions, asset restrictions, work plans, etc. | Planned |
| 6 | The center shall disseminate up-to-date schedules and route information to other centers for demand responsive transit services (paratransit). | 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.
| ID | Requirement | Status |
|---|---|---|
| 1 | The center shall monitor the locations of all transit vehicles within its network. | Planned |
| 2 | The center shall determine adherence of transit vehicles to their assigned schedule. | Planned |
| 3 | The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for transit tracking and dispatch. | Planned |
| 4 | The 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.
| ID | Requirement | Status |
|---|---|---|
| 1 | The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc. | Planned |
| 2 | The 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 |
| 3 | The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself. | Planned |
| 4 | The center shall be able to produce sample products of the data available. | Planned |