Adding Stops to Runs

Users can enter a list of Fixed Route Stops that must be included in a Para run.

Before you begin

Runs must be open.

About this task

When stops are specified, the Para run only provides service to these stops.

Only trips that have matching Origins and Destinations can be included on the run. A violation will occur for any trip moved to the run (for example, through drag-and-drop) that does not have a matching Origin and Destination (SRST).

Schedule Server matches the longitude and latitude of stop addresses (instead of StopIds) defined in the run's stop restrictions to determine possible insertion points. This allows client addresses with matching longitude and latitude values to be used as stops when scheduling BSR (bus stop restriction) runs.

Procedure

  1. Search for and select a run.
  2. Click the Stop Restrictions tab.
  3. Double-click on the first empty Stop cell.
  4. Type a stop name or number, or use the ellipsis button (…) to find a stop.
    For example, type main to see stop names that start with Main St., or type /333 to select Stop ID 333.
    Bus stops can be used if they are marked as InService in Task > Bus Stops. Bus stops used elsewhere in the system cannot be deleted from Task > Bus Stops.
  5. Optional: Type a Time.
    Using a time forces the vehicle assigned to the run to service the stop at a specific time, whether or not a client is on the vehicle. If no time is specified, the vehicle can stop at the specified location at any time (or multiple times) during the run.
  6. Select the Stop Rules to be used:
    • Pickup
      Only pick-ups can be performed at the stop.
    • DropOff
      Only drop-offs can be performed at the stop.
    • Both
      Both pick-ups and drop-offs can be performed at the stop.
  7. Optional: Set the Stop Tolerance.
    • Select Yes if the defined tolerance values are applicable to the stop.
    • Select No if no tolerance is allowed.

    Tolerance properties determine the duration before and after the schedule time that clients can be picked up without incurring a violation. Tolerance properties are set by a system administrator in Tools > System Properties, on the Profile tab, under PASS Scheduling > Stop Tolerance - Early and PASS Scheduling > Stop Tolerance - Late.

  8. Optional: Right-click to click and perform any of the following on an available Stop row:
    • Insert a stop.
    • Copy selected stops.
    • Paste copied stops.
    • Paste copied stops after reversing their order (Reverse and Paste).
  9. Optional: Create stop order groupings:
    Stops will be serviced in the order that they are listed (Stop Order Number). A violation occurs for any trips moved to the run that do not follow the stop sequence (SRSQ). However, stops that can occur in any order within a part of the run can be grouped so that they have the same Stop Order Number.
    1. Use the CTRL key and click to select multiple stops (or use the SHIFT key to select stops currently in sequence).
    2. Right-click and click Merge Stop Group.
    3. To remove a stop from the group, select a stop in the group, right-click and click Split Stop Group.
      Note that splitting the stop from the group will affect how stops appear in Stop Order Number.

      For example, splitting out the first stop will assign it a new number and keep the rest of the grouping. Splitting out a stop in the middle of the grouping will create a group out of the stops previous to the split stop, assign a new Stop Order Number to the split stop, and create a group out of the stops following the split stop. Typically, grouped stops will not have Times assigned to them. This allows the schedule server to schedule the stops in the best order.

    If Tolerance is allowed, then the timespans defined in Tools > Properties, on the Profile tab, under PASS Scheduling > Stop Tolerance - Early and PASS Scheduling > Stop Tolerance - Late are respected for pick-ups and drop-offs within the stop group.

    If specific times are defined for stops in the stop group, they are respected.