Route Ladder SOP 0018

Purpose

This procedure provides information for your agency staff to ensure that after importing schedule data into ETMS, each route has be updated on the Routes card to include important values for public visibility purposes and for tracking on time performance and possible issues in Operations.

Operational Impact and Metrics

1. Route color designation is an important visual aid for the public and Operations
2. Headway routes monitoring requires setting up thresholds for Operations alerts
3. OTP thresholds and Off Route alerts are enabled so Operations is aware of OTP and off route issues

Definitions

Frequency

This procedure should be performed when deploying new schedules and when adding new routes

1. Both types of updates require a major deployment using the import tool

Positions and Responsibilities

Implementation of this procedure is the responsibility of Planners & Schedulers- whoever manages the digital schedule and related attributes for the agency.

Procedure

This procedure describes the high-level steps involved:

1. Data entries should be made on two tabs on the Routes card

   • Passenger Info - default tab
   • Operations Info - secondary tab

   
   Passenger Info Tab

   1. Text and route trace color are required entries 
      1. Add background color
   2. Add text color
   3. Visible to Public - Slider defaults to ‘Visible’. Only use to hide routes on active schedule but not in service (Special Service).
   4. Mode of Service - Use dropdown menu to add mode, if using commuter bus, bus rapid transit (BRT), etc. and it’s included in your schedule data.
   5. Type of Service - Use dropdown menu to add service type, if using contracted service, and it’s included in your schedule data.
       

2. Optional fields:

   1. Sort Order - Allows you to prioritize routes with high ridership at top of list for online visibility ease
   2. GTFS URL - Your myStop applications
   3. Route Abbreviation
      • GTFS Long Name
   4. GTFS Description

   
   Operation Info Tab

   1. Set the Early Threshold (minutes) - Enter deviation expectation for Operations alerts (0 is standard or 1)
   2. Set the Late Threshold (minutes) - Enter deviation expectation for Operations alerts (5 is standard)
   3. Add the Overcapacity Threshold %
   4. External Volume During Quiet Hours % - Optional
   5. Add the Ridership Source - Farebox or APCs
      • Fareset Ids
   6. Visible to Dispatch - Toggle defaults to ‘Yes’
   7. Monitor for Headway - Used to alert dispatch of bunching/ gapping issues for headway routes
   8. Bunching Threshold % - Used for headway routes
   9. Gapping Threshold % - Used for headway routes
   10. Off Route - Toggle should indicate ‘Yes’ to allow monitoring alerts in Operations
       • Distance Threshold (# feet away from trace/scheduled road that triggers ‘off route’ alert)
          
3. Save all updates made
    
   • Updates become active after all other schedule data attributes have been managed and saved

Ask these Questions

1. Are the routes visually appealing/easy to interpret and use for riders who use your online tools to plan trips?
   • Are the route colors high contrast?
     • Avoid similar colors for trace and text
     • Example: grey trace, white text/light green trace, white text
   • Are the routes prioritized as you prefer?
     • Are the routes used the most near the top of the list for easy ridership visibility?
2. Does the service information match your publicly visible agency site?
   • Review and update your publicly visible schedule if conflicts display.

Supporting Documents

Deploying a Schedule: Schedule Data Import Process 
Route Attributes: Managing Route Attributes Using the Routes Card
Visibility Tips: Marketing Tips for Routes & myStop

Related SOPs

Planner SOP#001: Schedule Data Management and Implementation
Planner SOP#002: Planning & Daily Schedule Analysis