Purpose
This procedure provides information for dispatchers, or other appropriate transit agency staff, to best use the CAD/AVL system for common items occurring at pull-in or at the end of a shift or service. This procedure assumes the schedule has been pushed to the on-board CAD/AVL system (See S0P-001-01). The process covers monitoring and managing operator scheduled and actual pull-in times, operator log out, post-trip inspections, yard location, and event recording.
Operational Impact and Metrics
Operational Impact: The CAD/AVL system streamlines several common pull-in dispatch tasks and helps identify and address problems to improve on-time performance. By having access to yard maps, operator information, vehicle status information, and various monitoring alerts, dispatchers can make appropriate adjustments to achieve on time pull-in.
Metrics: On-time pull-in %
Definitions
| ITS | Intelligent Transportation Systems |
| CAD/AVL | Computer-Aided Dispatch and Automatic Vehicle Location |
| Block | All the trips run by a vehicle |
| MDT | Mobile Data Terminal |
Frequency
For all scheduled pull-ins and at end of each shift
Positions and Responsibilities
Implementation of this SOP is primarily the responsibility of dispatchers, or whomever transit agency staff are directly responsible for assigning drivers to buses, assigning buses to routes, and successful pull out from the operations side. Supervisory personnel should be familiar with these procedures to support the dispatchers. Bus operators responsibilities at Pull-in / End of Service are covered in the parallel S0P-022-01.
Procedure
- Pull-in/end of service
- Monitor scheduled pull-in times
- Monitor post-trip inspection status (if required)
- Monitor operator log-out
- Confirm current location of vehicles on yard map, update if necessary
- Unless vehicle locations are managed by maintenance hostlers
- Confirm you have responded to and logged all communications and events during your shift
- These are valuable alerts about system use- vehicle level
- Data files away to operational reports for later review as needed
Supporting Documents
Related SOPs