Schedule Violations

Accessibility Violation.

Schedule Server supports accessibility masks on FX runs at the stop, line, and vehicle levels.

Bookings and clients can be associated with accessibility masks (that is, a set of accessibility requirements). It is possible for accessibility types to be categorized as applying to a stop, line, or vehicle, rather than all three.

Schedule Server enforces accessibility requirements and offers FX solutions that satisfy applicable requirements at the stop, line and vehicle levels. This violation occurs if a trip is dragged and dropped onto a run such that any of the accessibility requirements is not met.

The PASS user interface for supporting booking and client specific accessibility requirements is not available at this time, nor does the InfoServer utilize the Accessibility Type categorization (by stop, line or vehicle). The PASS > SchedSrv > Enable Accessibility Mask switch can be used to enable and disable this functionality.

A trip is scheduled later than its RL drop-off time less its appointment time buffer.

The appointment time buffer is set in Tools > System Properties, on the Profile tab, under PASS Scheduling > Appointment Time Buffer.

This violation occurs if a break is scheduled with a passenger still on board OR a break actually begins either before the earliest time or after the latest time specified for the break to start.

This violation occurs when manually inserted breaks for Break and Lunch types that fall outside the auto break rules are flagged with a BrR violation when auto break logic is enabled.

This violation occurs if the run is backtracking. For example, the vehicle leaves the mall, drives to perform a pick-up and then drives back to the mall to perform the drop-off.

The capacity of the run has been violated, meaning that there are too many passengers on board to transport.

This violation occurs when a booking requiring a co-driver is scheduled to a run without a co-driver.

This violation occurs if the client has more than one trip with schedule times that overlap.

This violation occurs when a client trip has been placed on a run for a provider that is not included in the client’s list of valid providers (defined in Client Registration on the Providers tab).

This violation occurs if a provider has already met the allotted costing quota during a time interval and additional passenger with this space type is scheduled on to a run.

For more information, refer to the PASS-CT System Administrator and User Guide.

This violation occurs when the minimum/maximum time set between one client’s drop-off and their next pick-up is violated.

For example, if the passenger's duration of stay has been violated by five minutes, the system shows the DUR + (the amount of time that has been violated).

This violation occurs if a driver or co-driver marked with an inactive status type (in Task > Employees, on the Status tab) has been assigned to a run.

This violation only applies to Para runs.

This violation occurs when the events are out of sequence, meaning that a passenger is dropped off before being picked up. Usually, this is caused by manually dragging and dropping trips in a schedule.

This violation occurs when an escort is not available.

This violation occurs when a dedicated escort is not present at all times required for a passenger.

This violation occurs when a general escort is not present at all times required for a passenger.

Estimated Time Variance Threshold Exceeded.

Use of this violation requires that the PASS Scheduling/Allowed Estimated Time Variance context property is enabled.

This violation applies to any case where two passengers, or a passenger and driver are on a vehicle at the same time in violation of a schedule rule.

This violation occurs when a Fixed Route stop time has been violated. (FLEX only)

This violation occurs when estimated times are manually adjusted. The trip is frozen so that no further adjustments take place.

This violation occurs when a run has been frozen, which prevents same day insertions on a run operated by a new driver.

This violation occurs when a client travels past the requested stop, so he or she is labeled a hostage on board.

Location Capacity Violation.

This violation occurs when there are too many vehicles with overlapping times at a location for the curbside capacity.

Location Capacity allows you to define the maximum number of vehicles allowed at one location at the same time. For any location, the capacity can be defined by time of day and day of week. The capacity considers the number of vehicles and not the vehicle types or run capacities. The Schedule Server identifies a violation if too many vehicles have overlapping arrive/depart times at the location.

The Schedule Server arranges certain trips (based on capacity type, space type or mobility aids) in such sequences that the drop-off occurs immediately after the pick-up (last in/first out). This arrangement prevents situations where, for example, a passenger on a stretcher is moved out of a vehicle temporarily to allow other passengers to be picked up or dropped off.

This violation occurs when a mobility aid that a client requires is not provided by the vehicle. This only applies to mobility aids that must be provided by the transit property as opposed to ones that clients provides themselves. For example, stretchers and stair climbers.

This violation is predominantly associated with mobility aids requiring garage pick-up or driver assist.

This violation occurs when a non-group member is scheduled on a run at the same time as an exclusive group.

This violation occurs when the passenger is on-board the vehicle beyond the On-Board Time tolerance.

This violation typically occurs when events are placed out of sequence and trip events are placed before a pull-out event or after a pull-in event.

Used mainly in Europe.

Used mainly in Europe.

This violation occurs when a trips violates a provider restriction.

For example, a booking is assigned to a different provider than that which is assigned to its scheduled run.

This violation occurs when an incorrect passenger type is on board.

This violation occurs for runs that are going to a restricted location while they have clients or employees not authorized to access that location. R violations are incurred on the event at which unauthorized passengers are included.

A client or employee not marked as allowed at a restricted location is assigned to a run during a period of time where the run will perform an event at that restricted location.

To avoid R violations, passengers with restricted access privileges should be picked up before passengers without restricted access privileges and dropped off after passengers without restricted access privileges.

This violation occurs when a run travels into polygons that conflict with the polygon rules of the Para Service Area Route to which it is assigned.

This violation occurs when the requested trip time has been moved earlier than its tolerances.

This violation occurs when the requested trip time has been moved later than its tolerances.

The run is operating more hours than specified (the length of the run is in excess).

This violation occurs when runs pulls out earlier than its tolerances.

This violation occurs when a runs pulls in later than its tolerances.

This violation occurs when a run violates a polygon boundary, meaning that the run is outside of the defined service area.

This violation occurs when a pick-up or drop-off is in violation of a Para Service Area Rule.

This violation occurs when a scheduled trip time is earlier than the Schedule Early Tolerance.

This violation occurs when an event is in violation of a paraservice. (ParaServiceId needed by booking is not provided by this run.)

This violation occurs when a scheduled trip time is later than the Schedule Late tolerances.

Stop Restriction Sequence.

The stop sequence defined for the run in Task > Runs on the Stop Restrictions tab is not followed.

The trip includes an Origin or Destination that does not match the stops defined in Task > Runs on the Stop Restrictions tab for the run.

This violation occurs when a pick-up at the transfer point is late.

This violation occurs when a booking is manually placed on a run of an invalid mode type.

This violation occurs when the drop-off at the transfer point is late.

This violation occurs if a pick-up is placed on a run with an assigned vehicle type that is not compatible with the booking or the Schedule Server’s VehicleTypeExclusions list.

This violation occurs when a client is required to walk too far to a bus stop in a FLEX/Fixed solution.