Decision Support SOP 0020

Purpose

This procedure provides information for your agency staff to ensure that day-of-service adjustments are accounted for in your ITS system for cancellations and/or additions.

Operational Impact and Metrics

• Accounting for service changes- cancellations or additions 
• Communications with effected vehicle operators, maintenance staff
• Communications with the Public - ridership awareness of changes
• Managing unscheduled deviations- entering system adjustments to account for service reductions and additions which feed into NTD reportable metrics

Definitions

Frequency

This procedure should be performed: daily as needed, as it is a day of service tool, meaning proactive response to service disruptions as they occur ensures a smoother transition

Positions and Responsibilities

Implementation of this procedure is the responsibility of:

• Dispatchers - as the primary staff monitoring vehicles in service and as managers of communications with vehicle operators
• Messaging to Public - review/customize message for myStop for service interruptions such as cancellations
• Example - https://youragency.myavail.rideralerts.com/ InfoPoint/

Procedure

This procedure describes the high-level steps involved:

• Right-click a vehicle from the Operations area, typically the Status tab or Map, and select Decision Support
• Select the action card needed for the adjustment (Replace Vehicle, Helper Vehicle, Discharge Only, Platoon Vehicle, Cancel Service)
• Enter related information: Based on Card Selection

Replace Vehicle

•  
  1. Enter vehicle Id to replace current vehicle on route
  2. Enter vehicle operator
  3. Create message for both vehicles to alert both of location for swap
  4. Enter incident information using dropdown menus
  5. Save
  6. May involve communicate to internal staff who enter system adjustments so they can account for reduced service, if applicable for NTD reporting
  7. Return to monitoring Operations

Helper Vehicle

•  
  1. Enter 2^nd vehicle to join current vehicle on route that is running late
  2. Enter 2^nd driver
  3. Create message for both vehicles to alert both of location start for 2^nd vehicle
  4. Enter related incident information using dropdown menus
  5. Save
  6. Communicate to internal staff who enter system adjustments so they can account for additional service for NTD reporting
  7. Return to monitoring Operations

Discharge Only

1.  
   1. Create message for vehicle on route to notify them of no pick ups, performing drop offs only
   2. Head sign adjustment occurs if configured - "bus full" - to inform riders 
      • Or manually update head sign using the overhead/ODK
      • Head sign codes on the ODK are preserved for the agency for cases when integration is limited
   3. Enter related incident information using the dropdown menus
   4. Save
   5. Return to monitoring Operations

Platoon Tripper  Platoon Vehicles work in unison with Discharge Only

•  
  1. Enter 2^nd vehicle to also service vehicle on route to better distribute ridership
  2. Enter 2^nd driver for 2^nd vehicle
  3. Create messages with location to begin service for 2^nd bus and to alert both drivers
  4. Enter incident information using dropdown menus
  5. Save
  6. Communicate to internal staff who enter system adjustments so they can account for additional tripper service for NTD reporting
  7. Public communications - If unable to assign a Platoon Vehicle, due to availability, and if your agency does no display ridership counts on myStop ( bus full, bus empty, etc.), it is best practice to inform your ridership 
  8. Return to monitoring Operations

Cancel Service

1.  
   1. Enter message for vehicle operator to inform them/ confirm cancellation
   2. Enter where service cancellation will occur- stop location
   3. Enter related incident information using dropdown menus
   4. Save
   5. Messaging to Public- myStop applications for service cancellations
   6. Example - https://youragency.myavail.rideralerts.com/ InfoPoint/
   7. Communicate to internal staff who enter system adjustments so they can account for reduced service for NTD reporting
   8. Return to monitoring Operations

TIPS:

• Accounting for service adjustments is important to be sure the data collected and reported on for NTD needs is correct 
• Entered service interruptions feed into your reportable miles and hours consumed for NTD needs 
• Built- in messaging is based on the 'vehicle’
• Create Public Messages to inform ridership of changes as needed
• Related incident information can be found on the Vehicle Incidents card
• Incidents are editable, based on permissions

Supporting Documents

Help Center Articles:

Decision Support Overview - A Day of Service Adjustment Tool

Public Messages Creation Tool

System Adjustments - Accounting for Service Deviations for NTD Reporting

Related SOPs:

Dispatch SOP#012-Route Monitoring, Vehicle Swaps, Vehicle Additions, Operator Reliefs