Home > Architecture > User Services >

2.1 Public Transportation Management (User Service*)

The Public Transportation Management user service automates the operations, planning and management functions of public transit systems. It provides real-time computer analysis of vehicles and facilities to improve transit operations and maintenance. It monitors the location of transit vehicles, identifies deviations from the schedule, and offers potential solutions to dispatchers and operators. This service will help maintain transportation schedules and assure transfer connections from vehicle to vehicle and between modes and can be coupled with traffic control services to facilitate quick response to service delays. Information regarding passenger loading, vehicle running times, accumulated miles and hours and vehicle maintenance will help improve service and provide managers with a wealth of information on which to base decisions. Service schedulers will have timely data to adjust trips. Personnel management will be enhanced with the automatic recording and verification of operating and maintenance task performance. Security of transit personnel will be enhanced through providing access management of transit vehicles.

---

User Service Requirements*:

2.1.0	ITS shall include a Public Transportation Management (PTM) function.
	PSpecs*: 1.2.7.14 , 10 , 10 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 , 4.2.2 , 4.2.3.1 , 4.2.3.2 , 4.2.3.4 , 4.2.3.5 , 4.2.3.7 , 4.2.3.8 , 4.2.3.9 , 4.2.5 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7 , 4.4.1 , 4.4.4 , 4.5.1 , 4.5.2 , 4.5.3 , 4.5.4 , 4.5.5 , 4.5.6 , 4.5.7 , 4.6.6 , 5.1.7.3.5 , 5.1.7.3.6 , 6.2.3 , 6.5.8
2.1.1	PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities.
	PSpecs*: 1.2.7.14 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 , 4.2.3.7 , 4.4.4 , 4.6.6 , 6.2.3
2.1.1.1	To enable the automation of the vehicle and facilities operations OVF shall provide the capability to gather the needed data to include, but not be limited to, the following:
	PSpecs*: 4.1.1 , 4.1.3 , 4.1.5 , 4.1.6 , 4.6.6
2.1.1.1(a)	Vehicle passenger loading by bus stop and trip segment.
	PSpecs*: 4.1.1 , 4.1.6 , 4.6.6
2.1.1.1(b)	Bus running times between time points.
	PSpecs*: 4.1.1 , 4.1.6
2.1.1.1(c)	Fare collection by fare category.
	PSpecs*: 4.6.6
2.1.1.1(d)	Drive-line operating condition.
	PSpecs*: 4.1.1 , 4.1.3
2.1.1.1(e)	Mileage accumulated by individual buses.
	PSpecs*: 4.1.1 , 4.1.6
2.1.1.1(f)	Real-time vehicle location reports.
	PSpecs*: 4.1.3
2.1.1.2	OVF shall include a Command and Control (CC) capability.
	PSpecs*: 1.2.7.14 , 4.1.2 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.8 , 4.2.3.7 , 4.4.4
2.1.1.2.1	CC shall provide the capability for real-time Vehicle Command and Control (VCC).
	PSpecs*: 4.1.2 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.8 , 4.2.3.7 , 4.4.4
2.1.1.2.1.1	VCC shall provide the capability to compare received information with predetermined operating condition specifications and note any deviations.
	PSpecs*: 4.1.2 , 4.1.6
2.1.1.2.1.2	VCC shall provide the capability to transmit noted deviations to central control.
	PSpecs*: 4.1.5
2.1.1.2.1.3	VCC shall provide the capability to display any noted deviations.
	PSpecs*: 4.1.2 , 4.1.5
2.1.1.2.1.4	VCC shall provide the capability to automatically issue corrective instructions to the operator including, but not limited to, the following:
	PSpecs*: 4.1.2 , 4.1.4 , 4.1.8 , 4.2.3.7
2.1.1.2.1.4(a)	Route corrections.
	PSpecs*: 4.1.2 , 4.1.8
2.1.1.2.1.4(b)	Changes in stops.
	PSpecs*: 4.1.2 , 4.1.8
2.1.1.2.1.4(c)	Changes in wait time at a transfer stop.
	PSpecs*: 4.1.8 , 4.2.3.7
2.1.1.2.2	When CC detects a vehicle(s) has deviated from schedule it shall provide the capability to automatically determine the optimum scenario for returning the vehicle or fleet to schedule.
	PSpecs*: 4.1.2 , 4.1.4 , 4.1.8
2.1.1.2.3	CC shall include an integrated traffic control capability that provides traffic signal preemption when required for schedule adjustment to Transit Vehicles at traffic signals (i.e., centralized or distributed).
	PSpecs*: 1.2.7.14 , 4.1.2 , 4.1.4 , 4.1.8
2.1.1.2.4	CC shall include the capability for its computational capabilities to be located either on-vehicle and/or at remote locations.
	PSpecs*: 4.1.2 , 4.1.4 , 4.1.6 , 4.1.8
2.1.1.2.5	CC shall include the capability of exchanging information with other public transit systems regarding coordination of transfers between public transit system routes.
	PSpecs*: 4.1.8 , 4.2.3.7
2.1.2	PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
	PSpecs*: 4.1.3 , 4.1.6 , 4.1.7 , 4.2.2 , 4.2.3.1 , 4.2.3.2 , 4.2.3.4 , 4.2.3.5 , 4.2.3.8 , 4.2.3.9 , 4.2.5 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.7 , 4.4.4 , 6.2.3 , 6.5.8
2.1.2.1	The PSS shall include a Planning capability.
	PSpecs*: 4.2.2 , 4.2.3.1 , 4.2.3.2 , 4.2.3.4 , 4.2.3.5 , 4.2.3.8 , 4.2.3.9 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.7 , 4.4.4
2.1.2.1.1	PSS Planning shall be performed off-line from stored data that were collected in real-time.
	PSpecs*: 4.2.2 , 4.2.3.2 , 4.2.3.4 , 4.2.3.5 , 4.2.3.8
2.1.2.1.2	PSS Planning shall include processing of the data in a manner that will permit improvements in routes and services.
	PSpecs*: 4.2.3.4 , 4.2.3.9 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.7 , 4.4.4
2.1.2.2	The PSS shall include a Schedule Generation capability.
	PSpecs*: 4.1.3 , 4.1.6 , 4.1.7 , 4.2.3.2 , 4.2.3.4 , 4.2.3.8 , 4.2.3.9 , 4.2.5 , 6.2.3 , 6.5.8
2.1.2.2.1	The PSS Schedule Generation function shall collect data for schedule generation including, but not limited to, the following:
	PSpecs*: 4.1.3 , 4.1.6 , 4.2.3.2 , 6.2.3 , 6.5.8
2.1.2.2.1(a)	Route segment running-time.
	PSpecs*: 4.1.3
2.1.2.2.1(b)	Passenger loading at each stop.
	PSpecs*: 4.1.3
2.1.2.2.1(c)	Revenue information.
	PSpecs*: 4.1.6
2.1.2.2.2	The PSS Schedule Generation function shall use the collected data in the automatic or semiautomatic development of transportation system schedules.
	PSpecs*: 4.2.3.2 , 4.2.3.4 , 4.2.3.8 , 4.2.3.9
2.1.2.2.3	The PSS Schedule Generation function shall provide the capability to print schedules.
	PSpecs*: 4.2.3.2
2.1.2.2.4	The PSS Schedule Generation function shall provide the capability to disseminate schedules to, but not be limited to, the following:
	PSpecs*: 4.1.7 , 4.2.3.4
2.1.2.2.4(a)	Kiosks.
	PSpecs*: 4.2.3.4
2.1.2.2.4(b)	Transportation Management Centers.
	PSpecs*: 4.2.3.4
2.1.2.2.5	The PSS Schedule Generation function shall provide the capability to automatically update the customer service operator system with the most current schedule and schedule adherence information.
	PSpecs*: 4.2.3.2 , 6.2.3
2.1.2.2.6	The PSS Schedule Generation function shall provide the capability to generate vehicle schedules (block schedules) and vehicle operator schedules (run schedules).
	PSpecs*: 4.2.3.2 , 4.2.5
2.1.3	PTM shall include a Personnel Management (PM) function to facilitate the management of operator, and maintenance personnel.
	PSpecs*: 4.1.6 , 4.3.2 , 4.3.3 , 4.3.7 , 4.5.1 , 4.5.2 , 4.5.3 , 4.5.4 , 4.5.5 , 4.5.6 , 4.5.7 , 5.1.7.3.5 , 5.1.7.3.6
2.1.3.1	PM shall include a Maintenance Personnel Management (MPM) function.
	PSpecs*: 4.3.2 , 4.3.3 , 4.3.7
2.1.3.1.1	MPM shall automatically ensure that proper service personnel are provided information for vehicle maintenance activities.
	PSpecs*: 4.3.2 , 4.3.3 , 4.3.7
2.1.3.1.2	MPM shall automatically assign service technicians by skill level to work on individual vehicles.
	PSpecs*: 4.3.2 , 4.3.3 , 4.3.7
2.1.3.2	PM shall include an Operator Personnel Management (OPM) function.
	PSpecs*: 4.1.6 , 4.5.1 , 4.5.2 , 4.5.3 , 4.5.4 , 4.5.5 , 4.5.6 , 4.5.7 , 5.1.7.3.5 , 5.1.7.3.6
2.1.3.2.1	OPM shall automatically generate assignments of individual vehicle operators to runs produced by the Schedule Generation function.
	PSpecs*: 4.5.2 , 4.5.6 , 4.5.7
2.1.3.2.2	OPM shall assign vehicle operators to runs in a fair manner while minimizing labor and overtime costs.
	PSpecs*: 4.5.2 , 4.5.3 , 4.5.4 , 4.5.5 , 4.5.6 , 4.5.7
2.1.3.2.3	In generating fair vehicle operator assignments, OPM shall include factors relating to operators' preferences and qualifications to include, but not be limited to, the following:
	PSpecs*: 4.1.6 , 4.5.2 , 4.5.5 , 4.5.6 , 4.5.7
2.1.3.2.3(a)	Seniority.
	PSpecs*: 4.5.5
2.1.3.2.3(b)	Operator schedule preference.
	PSpecs*: 4.1.6
2.1.3.2.3(c)	Garage assignment.
	PSpecs*: 4.5.5
2.1.3.2.3(d)	Vehicle qualification.
	PSpecs*: 4.5.5
2.1.3.2.3(e)	Other factors contained in negotiated labor agreements.
	PSpecs*: 4.5.2 , 4.5.5
2.1.3.2.4	OPM shall automatically track and validate the number of work hours performed by each individual vehicle operator.
	PSpecs*: 4.5.1 , 4.5.2 , 4.5.3 , 4.5.4 , 4.5.6 , 4.5.7
2.1.3.2.5	OPM shall provide the capability for authentication of vehicle operators prior to operating a transit bus or rail vehicle.
	PSpecs*: 4.1.6 , 5.1.7.3.5 , 5.1.7.3.6
2.1.3.2.6	OPM shall provide an exception handling capability to provide for replacement vehicle operators in the event of operator unavailability due to operator absence, vehicle incident, or vehicle mechanical problem.
	PSpecs*: 4.5.5
2.1.4	PTM shall include a Communications function.
	PSpecs*: 10 , 10 , 4.4.1 , 4.4.4
2.1.4.1	PTM Communications shall provide the capability to establish two-way voice communication between vehicle operators and the central facility.
	PSpecs*: 4.4.4
2.1.4.2	PTM Communications shall provide the capability for two-way data communications between individual vehicles and the control facility (e.g., sensor data and bus position).
	PSpecs*: 4.4.1
2.1.4.3	OVF Communications shall provide the capability to send information from individual facilities to a central facility for processing and analysis.
	PSpecs*: 4.4.1
2.1.4.4	As support for responding to the detection of an on-board emergency, the OVF Communications shall provide dispatchers with the capability to inform the following:
	PSpecs*: 4.4.1 , 4.4.4
2.1.4.4(a)	Police.
	PSpecs*: 4.4.1
2.1.4.4(b)	Fire department.
	PSpecs*: 4.4.1
2.1.4.4(c)	Paramedic.
	PSpecs*: 4.4.1
2.1.4.4(d)	Vehicle operator (initiation of silent or audible alarm notification).
	PSpecs*: 4.4.1 , 4.4.4
2.1.4.5	PTM shall use an open vehicle communication network standard for all on-board electronic equipment.
	PSpecs*: 10 , 10
2.1.5	PTM shall include a Vehicle Management (VM) function to facilitate the management of Public Transit Vehicles (PTVs).
	PSpecs*: 4.1.1 , 4.1.6 , 4.2.5 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7
2.1.5.1	VM shall include a Maintenance Vehicle Management (MVM) function.
	PSpecs*: 4.1.1 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7
2.1.5.1.1	MVM shall automatically track vehicle miles on each vehicle in real-time.
	PSpecs*: 4.1.1
2.1.5.1.2	MVM shall use vehicle mileage data to automatically generate preventative maintenance schedules for each specific vehicle.
	PSpecs*: 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7
2.1.5.1.3	MVM shall automatically generate maintenance and repair schedules based on other significant maintenance indicator data, including vehicle operator notations of fault conditions.
	PSpecs*: 4.3.1
2.1.5.1.4	MVM shall provide the capability to record and verify that maintenance work was performed.
	PSpecs*: 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7
2.1.5.2	VM shall include an Operational Vehicle Management (OVM) function.
	PSpecs*: 4.1.6 , 4.2.5 , 4.3.2 , 4.3.6
2.1.5.2.1	OVM shall automatically generate assignments of individual vehicles to blocks produced by the Schedule Generation function.
	PSpecs*: 4.2.5 , 4.3.2
2.1.5.2.2	Vehicles shall be assigned to blocks based on available inventory, suitability to provide the service required by the block, and operational in-service status.
	PSpecs*: 4.2.5 , 4.3.2 , 4.3.6
2.1.5.2.3	OVM shall provide a dispatch control function to initialize vehicles and vehicle operators for the start of the operating day, control exit and return to transit facility, and maintain real-time awareness of returning vehicles approach to transit facility.
	PSpecs*: 4.1.6
2.1.5.2.4	OVM shall provide an exception handling capability to provide recovery from vehicle incidents or mechanical problems.
	PSpecs*: 4.2.5
2.1.5.2.5	OVM shall provide a vehicle inventory management function.
	PSpecs*: 4.2.5 , 4.3.6