Vehicle Operator SOP 021: Perform Revenue Service

Purpose 

This procedure provides information for vehicle operators for how to use the MDT during revenue service. This procedure assumes the schedule has been pushed to the in-vehicle CAD/AVL system. The process covers adherence to schedule, reporting schedule issues, communicating with Dispatch, using emergency alarms, fare collection, and various possible in-service events.   

Operational Impact and Metrics  

Operational Impact: The CAD/AVL system streamlines several common operator tasks during service and helps identify and address problems as routes are running and efficiently provide relief operators or replacement buses as necessary.  

Metrics: On-time performance, Vehicle capacity, Bus bunching on route 

Definitions  

Frequency

Continuous monitoring and communication with dispatch during revenue service 

Positions and Responsibilities 

Implementation of this SOP is primarily the responsibility of vehicle operators. Supervisory personnel should also be familiar with these procedures to best support operators. Dispatcher responsibilities for monitoring revenue service are covered in the S0P-012-01. 

Procedure 

• Log into the MDT with the correct Block / Run 
  1. Adhere to schedule as displayed on MDT 
     • MDT displays next 3 stops and times to depart
  2. Confirm Trip and Direction are correct/match schedule 
  3. Use Trip Select, if the scheduled service display on the MDT is incorrect
     • Menu> Trip Select> Touch piece of work/ trip to be performed
     • MDT auto- updates to correct trip
  4. Monitor your depart time for each next stop as displayed on the MDT 
  5. Adhere to the dwell time when you arrive at the next stop  
  6. Monitor MDT for time to depart prompts
  7. Repeat steps 1, 2, 3, 6 while in revenue service 

Reporting Schedule Data Issues  

1. Call dispatch to report the issue, location, and description:
2. Schedule issues could include: 
   • Announcements – missing or incorrect or too early or too late 
   • Head sign fails to update correctly ( inbound, outbound destinations)
   • Schedule data – incorrect stops or departure time issues

Communication to Dispatch 

1. Canned text messages 
   • For informational one-way communication press the ‘MSG’ button on the MDT 
   • Select by pressing the desired canned message from the list on the MDT 
   • Confirm the message was delivered by monitoring the ‘Status Bar’ 

Receiving Canned Messages from Dispatch 

1. View message in the INBOX 
2. Respond to Dispatch messages as requested, by type:
   • Respond Yes or No, as required
   • Respond Acknowledge, as required
   • No response needed 

Request to Talk – Voice Radio / Closed Mic System/ VoIP

1. For informational two-way communication press the RTT button on the MDT 
2. For emergency two-way communication press the PRTT button on the MDT 
   • Accident, medical emergency, etc.  
3. Pick up handset when prompted by MDT 
4. Receiving request to talk from dispatch   
   • Pick up handset when prompted by MDT 
   • Hang up when done

Emergency Covert Alarm/Silent Alarm 

Agencies should clearly define parameters for when to use emergency features and review with dispatch and vehicle operators.

1. Use during hostile situations (as defined by agency policy and practice) and for medical emergencies
2. Press Covert EA button 
3. Monitor for Dispatch acknowledgement  
   • MDT Time Stamp: When the colon stops blinking, dispatch received your alert 
   • When the colon disappears, dispatch is listening in (if covert mic is enabled)
4. Covertly describe the situation, if able to do so safely without putting anyone in danger

Video Tagging 

1. Use during hostile situations ( as defined by agency policy and practice)
2. Press the video tagging button 
3. Dispatch receives an event to indicate video is active  
   • Date, time, vehicle   
4. Managers, and others as assigned, can review the video to determine next steps, if any

Fare Collection (two options) 

1. Operator manually indicates receipt of fare on MDT or Farebox 
   • When at a stop, open the door and the fare screen will display 
   • Press fare buttons to accurately record ridership 
   • Close door and pull away, the screen will disappear  
2. Customer taps fare card on reader and MDT records fare automatically 

Driver Off/ Driver On 

Agencies define when to use Driver Off/ Driver On buttons on the MDT, as preferred

1. Driver Off/ Driver On Button  
   • If you need to notify dispatch that you're off the vehicle/out of service, click MENU then click Driver Off (Avail recommends closing the door completely when not in service to avoid boards) 
   • To go back into service, click MENU and press Driver On

Vehicle Capacity

1. Drop-off only mode (may not be applicable to all agencies) 
   • Call Dispatch to report the vehicle is full as dispatch can use Decision Support tools to put the vehicle in Discharge Mode, thus updating the head sign to alert ridership that the vehicle is full/ cannot receive additional passengers 
   • Proceed in a Discharge Only state until the bus has more seating capacity  
   • Alert dispatch when the vehicle is ready to resume normal service 

Detours

1. Scheduled Active Detour 
   • When you login to the vehicle, any scheduled detours for your run are sent automatically as a data message 
   • Review the message in the INBOX and let dispatch know if you have any questions 
   • At the last stop before detour is active, press Detour Upcoming to view a popup of turn by turn directions
2. Unscheduled Detour 
   • Inform dispatch if you have to deviate from your scheduled route due to unexpected road obstruction (traffic, construction, police activity) 
   • Adhere to detoured route until advised/ able to return to scheduled route 

Trip Select Function 

1. If you notice your trip or direction are incorrectly listed on the MDT, click MENU and then touch  Trip Select 
2. Select the correct trip from the list ( head sign, stops display and ADA announcements will update to correct piece of work) 
3. The MDT will update to display the correct stops  

APC Adjust Function  

1. Confirm APC counts match the vehicle onboard count (e.g. at a trip layover) confirm and/or adjust the onboard count 
2. Perform a visual check of onboard passenger count 
3. Tap APC adjust to validate the onboard count if necessary 
4. Enter the actual onboard count on the APC adjust screen 
5. Click Save

Transfer Connection Protection 

1. Initiating a TCP request 
   • Operator presses XFER button on MDT 
   • Operator selects the following information 
     • Route 
     • Direction 
     • Enter number of passengers to transfer
     • Indicate if passenger/s use a wheelchair 
   • Operator presses the send button 

Receiving Vehicle - TCP Request 

1. Operator monitors MDT for TCP requests 
2. Review incoming transfer information in INBOX
3. Wait for dispatcher instructions  

Supporting Documents

Related SOPs 

1. SP-001-01 Planner – Schedule Data Management and Implementation 
2. SP-020-01 Operation – Pull Out/Start of Shift 
3. SP-022-01 Operation – Pullin/End of Service 
4. SP-023-01 Operation – Reliefs 
5. SP-012-01 Dispatch – Route Monitoring & Operator Relief 
6. SP-031-01 Maintenance – Vehicle Health Monitoring 
7. SP-050-01 Road Supervision (Route Monitoring)