PASS Scheduling System Properties

Table 1. PASS Scheduling System Properties
Property	Description
PASS Scheduling > Weekly Activate Inactive Drivers & Vehicles	If PASS is not integrated with OPS, this switch allows inactive drivers and vehicles to be activated.
PASS Scheduling > Actual coordinates affect times	Specifies whether the Schedule Server should recalculate the actual time of an event after it receives the time posted by the MDT Server. For example, if a drop-off is scheduled for 15:30 but is performed at 15:25, the Schedule Server uses the time of 15:25 in recalculating the time between the arrive time and the next event. The change readjusts the schedule of succeeding events.
PASS Scheduling > Actual times affect times	Specifies whether AVL positions influence the calculation of the estimated times (ETA, EstTime, ETD). When set to No, only actual times typed by the user cause an update of the subsequent estimated times. When this property is set to Yes, all AVL positions reported by the vehicle affect the schedule. The Schedule Server should be restarted after changing this property value.
PASS Scheduling > Allowed Estimated Time Variance	How much time the estimated time can be after the scheduled early time. The default value is 15 minutes.
PASS Scheduling > Allowed Estimated Time Variance - Enable for Taxi Pickup	Whether to enable use of the Taxi Pickup violation. The default value is No.
PASS Scheduling > Appointment Time Buffer	Minimum amount of time before the trip's drop-off RL time that the trip must be scheduled.
PASS Scheduling > Arrive Should Set	Records the time when a trip is marked Arrived in the Schedule Editor. ActualArriveTime Schedule Editor shows, in both the actual arrival (Act Arr) column and the estimated arrival column (Est), the current time when a trip is marked Arrived. EstTime Schedule Editor shows the current time in the Est column when a trip is marked Arrived. Both Estimated arrive time is updated by the actual arrive time. Default Actual arrival time and estimated arrival time are updated for pickups and only the actual arrival time is updated for drop-offs .
PASS Scheduling > Arrived or Performed Events Can be Moved	Specifies whether events that have been marked as Arrived or Performed can be moved (for example, via drag-and-drop), and whether events can be moved before other events that have already been marked as Arrived or Performed.
PASS Scheduling > Auto Layover	Specifies whether automatic layover break events are created for live same-day inserts.
PASS Scheduling > Auto Layover Offset	Sets an auto layover event time to the current time plus a number of minutes to account for the delay in dispatching the insert that originally caused the auto layover. (Use a negative value to subtract minutes). The default value for the offset is +5 minutes.
PASS Scheduling > Average speed	Average speed used when calculating time and distance. Each additional factor is calculated using this speed as the base. When setting this speed, consider whether the system is rural or urban.
PASS Scheduling > Backtrack Ratio	A floating number multiplied by the farthest distance from the point of origin that clients reach during their trips. Leave the backtrack ratio set at the default. When set to 0, this feature is turned off.
PASS Scheduling > Backtrack Threshold	Minimum distance that clients are allowed to stray from their points of origin before near backtracking is activated. (Zigzagging is allowed within a small area.) When set to 0, this feature is turned off.
PASS Scheduling > Booking Activate: Check client eligibility dates	Specifies whether to activates subscription bookings only if the date of the booking complies with the Eligible From/Eligible To date fields in both the Certification and Funding Source tabs of the Clients screen.
PASS Scheduling > Breaks > Autobreaks > Lock Autobreaks Removes Rule	Specifies whether to remove the autobreak rule from the daily run if the Lock Autobreaks switch is enabled (in the Schedule Server application, click View > Switches, then in the Switches tab, expand PASS > SchedSrv > Autobreaks > Lock Autobreaks).
PASS Scheduling > Breaks > Autobreaks > Locked Break Type	Type of break (in the list of user-defined user breaks) that the Lock Autobreak process inserts into runs. To do this, type the code for the break type corresponding to the codes shown in the Insert Break dialog box. The original break type is used as the default for this property, and also if an invalid selection is made. This property is not used for an autobreak rule if the Primary Break Type is set for the autobreak rule in Auto Driver Break Rules.
PASS Scheduling > Breaks > Default Break Length	Default break length if a break length is not specified in the Schedule Editor. If no break length is specified here either, the break length defaults to 15 minutes. Break lengths specified in the User Breaks properties override the default specified here.
PASS Scheduling > Breaks > User Breaks (User Break 0 to User Break 39)	Specifies a list of forty user-definable breaks (0 through 39). Select a break to see the break code associated with it. For example, if you select User Break 0, the code shown on the left frame is B0. The break code is shown in the Schedule Editor. To specify break lengths, type a comma followed by a value from 1 to 999 (which represents the default number of minutes) after the break name. The length specified here overrides the Default Break Length property.
PASS Scheduling > Bulk Scheduling > Match to Date Based Schedules (Default = false)	Used with Bulk runs (for PASS-ED school bus runs). Prevents users from batching template trips. The default setting is False, meaning that if a user attempts to batch a template schedule, a warning appears and the batch process is canceled. For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Bulk Scheduling > Max OBT	Used with Bulk runs (for PASS-ED school bus runs). For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Bulk Scheduling > Minimize distance or travel time rule	Used with Bulk runs (for PASS-ED school bus runs). For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Bulk Scheduling > Sets: Default Batch Parameter	Used with Bulk runs (for PASS-ED school bus runs). For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Bulk Scheduling > Sets: Default Batch Violation	Used with Bulk runs (for PASS-ED school bus runs). For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Bulk Scheduling > Update Master Stop After Saving Solution	Used with Bulk runs (for PASS-ED school bus runs). For more information, contact a Trapeze Customer Care representative.
PASS Scheduling > Capacity Type Swapping > Swap Between Garages	Specifies whether the Schedule Server can swap capacity types between two runs that originate from different garages.
PASS Scheduling > Capacity Type Swapping > Swap Between Providers	Specifies whether the Schedule Server can swap capacity types between two runs that are from different providers.
PASS Scheduling > Clear Provider Cost Adjustment	Specifies whether to show credited amounts in client records if a client has canceled a trip.
PASS Scheduling > Co-Driver Space Type	Space type used by the co-driver on a run. If the run has a co-driver assigned and the co-driver space type is specified, the capacity of the run is reduced by one space at the time of the run pull-out.
PASS Scheduling > Default Space Type for Employees
PASS Scheduling > Dispatch : Lock future days and templates	Specifies whether to prevent users from performing dispatching activities for any other date except the current date.
PASS Scheduling > Distance Calc. Method	Method used to calculate distances for scheduling. This property is set to Triangulation by default. Choosing the Triangulation method produces the fastest response time from the system but Street Routing offers the most accurate results. Point to Point Calculates the shortest distance between two points. (This method does not take into account streets or landmarks between the two points.) Triangulation Calculates distance between points by drawing straight lines and right angles (for example, using only East-West and North-South lines.) This method is most frequently used at sites and gives a more accurate calculation of the distance that a vehicle travels compared to the Straight method. Street Routing Calculates distance by finding the shortest route along existing streets. Note: With street routing, if an origin or destination is not directly on a street, the system projects the location to the nearest road. If the projected location is on a dead-end street that cannot be used in a route, the system projects the location to the next closest street. To restrict the distance within which the system searches for streets when projecting origin or destination locations, set the Map > StreetRouter > Max Distance To Street property in Trapeze6. Barrier Restriction By taking into account barriers such as rivers, mountains, and other obstructions, this method calculates distance based on routes that circumnavigate common barriers. Before the Schedule Server uses the Barrier method for Distance Calculation, you must define your barriers.
PASS Scheduling > Enforce Client Providers	Specifies whether provider scheduling options should be limited to those defined in the client profile. Yes Schedule Server will only allow clients on runs that have no provider or on runs that have a provider from the list of client providers found in Client Registration (on the Providers tab). For example, when creating a trip in Trip Booking or when rescheduling a client trip in the Schedule Booking Wizard. Other provider runs will not be searched, even when allowing provider violations (found in Tools > System Properties, on the Profile tab, under PASS Scheduling > Sets: Violations). If a client trip has been placed on a run for a provider that is not included in the client’s list of valid providers, a CPR violation is created. If you decide to allow CPR violations, after setting the property, restart Schedule Server. No All available Providers are shown. The default is No.
PASS Scheduling > Escort Job Class Id	Job class ID used by Schedule Server to filter available escorts when scheduling trips.
PASS Scheduling > EvOrder: Max Value	Maximum value to be used in event ordering. This value is used in determining MDT events and incidents. If an event order value changes, it is considered to be an incident. (This property is normally set at 20000000.) Note: EvOrder properties are related to MDTs. Do not alter the default settings; they affect the event order sent to the MDT.
PASS Scheduling > EvOrder: Min Separation	Minimum difference of sequential order. If it is lower than this number, the system reorders the events, creating incidents. (This property is normally set at 2048.) Note: EvOrder properties are related to MDTs. Do not alter the default settings; they affect the event order sent to the MDT.
PASS Scheduling > EvOrder: Normal Separation	Difference of sequential order for a normal sequential event. (This property is normally set at 1024.) Note: EvOrder properties are related to MDTs. Do not alter the default settings; they affect the event order sent to the MDT.
PASS Scheduling > Exclude Pulls from "Mark All"	Specifies whether to exclude pull-ins and pull-outs from the Mark All function. Dispatchers are alerted about pull-ins/pull-outs that are approaching overdue status on the Incidents tab in the Dispatch screen; they can manually dispatch the pull-ins/pull-outs when they occur.
PASS Scheduling > Fast-Costing Violation Set	Violation set that the Schedule Server is to use when fast-costing all of the solutions. The default violation set is used when calculating the final costing of each solution.
PASS Scheduling > Flag Stop Booking Sub Type	Subtype used in trip booking for flag stops.
PASS Scheduling > Flashback Threshold	Limit of flashback captures to instances when the weight of the selected solution exceeds the weight of the best solution by more than the threshold specified here.
PASS Scheduling > Force fast-cost when street routing	Specifies whether fast costing is to be always used when the distance calculation method is street routing, regardless of the Use Fast Costing option in the Schedule Parameters dialog box. The value of FCost Depth in the parameters dialog box is still taken into account in this case. If the site uses street routing, set this property to Yes to hasten solution times. If set to No, the use of fast costing is controlled by the setting in the Schedule Parameters dialog box.
PASS Scheduling > Hide inactive schedule types	Specifies whether to hide inactive schedule types wherever the Schedule Type list exists in the following screens and dialog boxes: Date Intervals dialog box Schedule Editor Schedule list in the Select Schedules dialog box Select Schedule Range dialog box in Trip Administration Main screen Monitor Runs Trip Administration Set Schedule Mode dialog box (press F3 or click File > Set Mode)
PASS Scheduling > Incident EstTime Threshold	Specifies what is shown in the Dispatch screen in New Events. Incidents are created for Sent Events whose Estimated Time changes by an amount greater than or equal to this property’s value. If set to 15 minutes, an incident appears when an Est Time changes by 15 minutes or more. The recommended setting is 23h if the site is using MDTs.
PASS Scheduling > Incidents for today only	Specifies whether to show incidents for the current day.
PASS Scheduling > Incidents: Create for Nodes	(Flex only) Specifies whether to show incidents that occur when there are changes to nodes.
PASS Scheduling > Incidents: Create for No-shows	Specifies whether to create an incident when a trip is marked as No-show. Select Yes only when a driver is required to request that a trip is marked as a no-show or when the dispatcher is responsible for monitoring no-shows. Select No if the driver determines that a trip is a no-show. This property setting depends on the site’s policy.
PASS Scheduling > Incidents: Create for Re-ordered	Specifies whether to create an incident when a trip is reordered (if EvOrder changes). Select Yes if the site uses MDTs.
PASS Scheduling > Incidents: Create for Stops	Specifies whether to create incidents for stops on the Dispatch screen. This is related to stop time changes for Flex routes. Choose No.
PASS Scheduling > > Incidents: Write TT to Msg. Center	Allows the Schedule Server to write a message to the MDT Center when a transfer violation occurs.
PASS Scheduling > Late Cancellation Threshold(minutes)	Designates a booking as a Late Cancellation if the schedule time of the booking is equal to or less than the threshold (in minutes). For example, if this property is set at 60 and the user attempts to cancel a booking that is set to occur within the hour, the following message appears: `This trip qualifies for automated Late Cancellation. Do you want to proceed?` Choose Yes to designate the booking as a late cancellation. Choose No to allow the user to select a cancel code.
PASS Scheduling > Max Hostage Time	Allows you to set the maximum time that the client is allowed to be on board the vehicle while it is stopped. For example, waiting for another pick-up. Once the client’s time on board the vehicle exceeds the maximum hostage time, the system flags this trip as an HO violation. Max Hostage time is also used for OBT calculations when PASS > SchedSrv > Enable New OBT Calculation server switch is set to ON.
PASS Scheduling > Max OBT w/o Transfers	Maximum on-board time a passenger is allowed to be on board a vehicle without a transferring to another vehicle. An OB violation is incurred once this time has been reached.
PASS Scheduling > Max OBT with Transfers	(Used with FLEX) Maximum on-board a passenger is allowed to be on board a vehicle, including trips with transfers. An OB violation is incurred once this time has been reached.
PASS Scheduling > Max Transfer Layover	Maximum wait time at a transfer point (for example, 20 minutes). When this value is exceeded, a TL violations is incurred.
PASS Scheduling > Max Trips Unscheduled at once	Maximum number of trips in a single day that may be unscheduled at one time in the Trip Administration and Schedule Editor screens.
PASS Scheduling > Max Walking Distance	Maximum walking distance allowed between a client’s origin or destination and a bus stop for FX or FLEX solutions. When searching for solutions, the Schedule Server compares the Max Walking Distance parameter in the solution set used for the booking with this global Max Walking Distance property, and then uses the lesser of the two values.
PASS Scheduling > Min. Duration of Stay	Specifies whether to enforce the global minimum duration of the stay property if it is greater than a booking minimum duration. Therefore, the minimum duration of stay of a booking is the greater of the booking minimum duration and the global minimum duration.
PASS Scheduling > Minimum Transfer Layover	Minimum amount of time that must occur between a transfer drop-off and the subsequent transfer pick-up. The default for this parameter is 0. If this parameter is violated (the amount of time between transfer drop-off and pick-up is less than the minimum), a TL violation occurs. This is the same violation that occurs when Maximum Transfer Layover is exceeded.
PASS Scheduling > MobAid Garage Pickup Restriction	Restricts mobility aid garage pick-ups and drop-offs to occur only at the run's pull-out garage. If set to No, mobility aid pick-ups can occur at any garage.
PASS Scheduling > Multimodal Flex Scheduling > Allow flex on garage deadhead	(Used for scheduling Flex runs in the FLEX module.) Specifies whether vehicles can deviate off route between the garage and the first fixed stop or between the last fixed stop and the return to the garage.
PASS Scheduling > Multimodal Flex Scheduling > Auto Create Daily Runs	(Used for scheduling Flex runs in the FLEX module.) Specifies whether the Schedule Server should automatically create daily FLEX and FX runs directly from the FX tables even if the run does not have a master run record in PASS. The Schedule Server must be started if when this property is first enabled.
PASS Scheduling > Multimodal FX Scheduling > Bus Stop search radius	Bus Stop search radius defines the search radius for accessible bus stops by checking for bus stops around a pick-up and drop-off point.
PASS Scheduling > Multimodal Flex Scheduling > Fixed stop late tolerance	(Used for scheduling Flex runs in the FLEX module.) Specifies how late a run is allowed to be at a fixed stop.
PASS Scheduling > Multimodal Flex Scheduling > Flex if zero slack	(Used for scheduling Flex runs in the FLEX module.) If set to Yes, the FLEX algorithm allows route deviation regardless of the slack value. The deviation may or may not result in the FLEX bus arriving late at that node (how late depends on other properties). If it is set to No, the FLEX algorithm does not allow route deviation from the fixed path between the node with zero slack and the previous node. It only allows deviation if the slack is greater than zero.
PASS Scheduling > Multimodal Flex Scheduling > Ignore late at non-node FX Stop	(Used for scheduling Flex runs in the FLEX module.) If set to Yes, lateness is computed only at nodes (that is, published time points) and not at intermediate fixed stops.
PASS Scheduling > Multimodal FX Scheduling > Ignore violations	(Applies to PASS-IPA and Bus Stop Restriction runs.) If set to Yes, no violations are applied to the fixed route portion of multimodal trips. (Note that, currently, TL (Transfer Late) violations may still appear on Fixed Route portions of trips.)
PASS Scheduling > Multimodal FX Scheduling > Ignore violations for fixed portions of scheduling solutions	(Applies to PASS-IPA and Bus Stop Restriction runs.) If set to Yes, no violations are applied to the fixed route portion of multimodal trips. (Note that, currently, TL (Transfer Late) violations may still appear on Fixed Route portions of trips.)
PASS Scheduling > Multimodal Flex Scheduling > Min Stop25Stop Dev. Dist	(Used for scheduling Flex runs in the FLEX module.) Minimum distance separation that two sequential stop events must have for a client deviation to be allowed to be inserted in between the events. If the minimum distance is not reached, a client deviation is allowed only if the two stop times are different by at least the number of minutes specified by the Min Stop2Stop Dev. Time property. Deviations that are not allowed incur ES violations.
PASS Scheduling > Multimodal Flex Scheduling > Min Stop25Stop Dev. Time	(Used for scheduling Flex runs in the FLEX module.) Minimum time separation that two sequential stop events that fail the Min Stop2Stop Dev Dis rule must have to allow a client deviation to be inserted in between the events.
PASS Scheduling > Multimodal Flex Scheduling > Transfer Point Late Tolerance	(Used for scheduling Flex runs in the FLEX module.) Amount of time that a FLEX vehicle can arrive late at a transfer node before it is considered a violation.
PASS Scheduling > Multimodal FX Scheduling > Apply Dwell Time	Specifies whether to add passenger dwell times to pick-up and drop-off estimate times for events at fixed stops. If set to No, passenger dwell times are not applied to FX runs. By default, this feature is disabled because FX routes already have average dwell times added to their schedules.
PASS Scheduling > Multimodal FX Scheduling > Auto Create Daily Runs	Specifies whether the Schedule Server can automatically create daily FX runs directly from the FX tables, even though the run does not have a master run record in PASS.
PASS Scheduling > Multimodal FX Scheduling > Enable Saving Trips to Fixed Route Solution	If set to Yes, users can save to fixed route solutions. If set to No, users cannot save to fixed route solutions. The default setting is Yes.
PASS Scheduling > Multimodal FX Scheduling > Only Search for Alternative Transport Solutions if No Fixed Route Solution Exists	If set to Yes, Schedule Server searches for solutions in fixed route runs. If solutions are found, only those fixed route options are available. If solutions are not found, Schedule Server searches for solutions on any run type. If set to No, there is no change in Schedule Server's search behavior. The default setting is No.
PASS Scheduling > Multimodal FX Scheduling > Require ParaMasterLine For Activation	Specifies whether the Schedule Server can automatically create FX runs only for runs that have an entry in the ParaMasterLine table. If set to No, any applicable LineIdConst can be used to auto-create a run, regardless of whether there is an entry in the ParaMasterLine table. This property is used only when FX Scheduling > Auto Create Daily Runs is set to Yes.
PASS Scheduling > OBT Factors based on ReqTime	Specifies whether the Schedule Server should consider request times for OBT factors rather than an arbitrary standard time (that is, midnight). For example, setting this property to Yes and using a Req time of 8:00 A.M. bases the OBT factor on the expected trip time of a trip taken at 8:00 A.M. (even if the trip is booked for and takes place at 10:00 A.M.) Setting this property to No bases the OBT factor on the expected trip time at midnight. Trapeze recommends setting this property to Yes. The property is set to Yes by default.
PASS Scheduling > Perform Should Set	Records the time when a trip is marked as Performed in Schedule Editor and contains the following options: Actual Depart Time Actual time a trip is marked Performed in both the actual departure (Act D) column and the estimated column (Est). Est Time Updates the Est column, which is the only column that shows the actual time when a trip is marked as Performed. Both Updates the actual and estimated times in their columns. Default Updates the ETA column for pick-up events and updates the ETD column for drop-off events. Note: Trapeze recommends this option.
PASS Scheduling > Planning Mode - allow automatic scheduling	Specifies whether automatic scheduling is allowed when planning mode is used. Yes Automatically scheduled trips are allowed in batch scheduling and automated scheduling appears in solution searches. No No automatic scheduling is allowed.
PASS Scheduling > Polygon types > ADA	Polygon type for all ADA polygons.
PASS Scheduling > Polygon types > Booking polygon	Polygon type that is saved when a new booking is created. If no polygon type is specified, the system does not save a polygon when a booking is created. Both a booking polygon and a jurisdiction polygon can be saved for each origin and destination. See the description of Jurisdiction polygons.
PASS Scheduling > Polygon types > Ferry	Polygon type for ferries.
PASS Scheduling > Polygon types > Jurisdiction polygons	Default jurisdiction polygon type. The type defines the boundary that can be applied to a client record, location record, or trip booking recorded. The type that is used is based on your jurisdictions.
PASS Scheduling > Polygon types > Para Service Area	Polygon type used in the Para Service Area Route screen and the Para Service Area Rules screen.
PASS Scheduling > Polygon types > Service area	Polygon type that defines the service area.
PASS Scheduling > Polygon types > Service Parameter	Service parameter polygon type. This is used in rare instances in the fare type Depends On logic.
PASS Scheduling > Polygon types > Speed Zone	Speed zone polygon type. Set this property to <none> if you are not using speed zone polygons. Polygon types are created as ancillary data. When you set this property and grant permission for the Trapeze4 > Employees > Speed Zone permission key, the Speed Zone tab in Employees is enabled.
PASS Scheduling > Publish Events	These properties must be configured for the PASS Real Time Views application. You must also set these properties for the Dispatch Manager screen.
PASS Scheduling > Publish Events Host	These properties must be configured for the PASS Real Time Views application. You must also set these properties for Dispatch Manager.
PASS Scheduling > Publish Events Port	These properties must be configured for the PASS Real Time Views application. You must also set these properties for Dispatch Manager.
PASS Scheduling > Resequence on Arrive	If Yes is selected, when events are marked as arrived, they are moved before non-arrived events on the run and are ordered by their actual arrival time.
PASS Scheduling > Resequence on Perform	If Yes is selected, when events are marked as performed, they are moved before non-performed events on the run and are ordered by their actual departure times.
PASS Scheduling > Reset Locked EstTime on Reorder	Specifies whether to remove the locked time (a manually typed time) and let the system reorder estimated times based on real-time scheduling activities.
PASS Scheduling > Run Optimizer Parameter Set	Parameter set the Run Optimizer uses during a batch schedule process. If this property is not set, the parameter set chosen for the batch is used.
PASS Scheduling > Run Optimizer Violation Set	Violation set the Run Optimizer uses during a batch schedule process. If this property is not set, the violation set chosen for the batch is used.
PASS Scheduling > Same Day PickUp Constraint	Specifies whether to impose a time restriction on scheduling a same-day trip. The time restriction is defined in the Same Day PickUp Constraint Offset property.
PASS Scheduling > Same Day Pickup Constraint Offset	Minimum time in advance that a same day trip can be booked. Note: The Same Day Pick Up Constraint property must be set to Yes to use this property.
PASS Scheduling > Same geo - graduated bonus	Specifies whether to award same-geo case bonuses if all conditions are satisfied within a defined time window.
PASS Scheduling > Same Geo - windows (minutes)	Time window in minutes to check for same-geo cases.
PASS Scheduling > Schedule Type - Active Live	Schedule type used for this property. This property is always set to Live.
PASS Scheduling > Schedule Type - Active Template	Schedule type used for this property. This property is always set to Template.
PASS Scheduling > Sets: Default Batch Parameter	Default file used to define batch parameters for batch scheduling. These parameters may also be adjusted manually when batching.
PASS Scheduling > Sets: Default Batch Violation	Default file used to define batch violations. These violations may also be adjusted manually when batching.
PASS Scheduling > Sets: Default Flag Stop Parameter	Default parameter set to be used for flag stops.
PASS Scheduling > Sets: Default Flag Stop Violation	Default violation set to be used for flag stops.
PASS Scheduling > Sets: Default Parameter	Default file used to define the parameter for finding solutions during single insert scheduling in the Schedule Wizard.
PASS Scheduling > Sets: Default Violation	Default file used to define the violation set used by the Schedule Wizard during single insert scheduling.
PASS Scheduling > Sets: Parameters	Allows for editing of scheduling parameters. Click Edit to show the Solution Parameters dialog box.
PASS Scheduling > Sets: Violations	Allows for editing of scheduling violations. Click Edit to show the Allowable Violations dialog box.
PASS Scheduling > Stamp Provider on Save	Specifies whether to switch to a new provider in the Provider field in Trip Booking when the provider is selected via a run in the Schedule Booking Wizard.
PASS Scheduling > Stop Tolerance - Early	Defines the maximum amount of time before a specified stop time that the run is allowed to use the stop.
PASS Scheduling > Stop Tolerance - Late	Defines the maximum amount of time after a specified stop time that the run is allowed to use the stop.
PASS Scheduling > Stamp Transfer Subtype on Save	Specifies whether the subtype is updated when a trip is scheduled as a transfer.
PASS Scheduling > Sync Neg with Sch times	Specifies whether to synchronize negotiated times with scheduled times. Trapeze recommends selecting Yes (prompt) from the list.
PASS Scheduling > Sync Neg/Sch with Req times	Specifies whether to synchronize the schedule and negotiated times with the Requested time. Trapeze recommends selecting Yes (prompt) from the list.
PASS Scheduling > Sync Sch with Neg times	Specifies whether to synchronize the scheduled time with the negotiated time. Trapeze recommends selecting Yes (no prompt) from the list.
PASS Scheduling > Tolerance - Apply to Dropoff	Specifies whether to activate the use of early and late tolerances to be used with the requested drop-off time in the Scheduling Wizard. When set to No, the Dropoff Early/Dropoff Late window is only applied on the drop-off ReqTime for the purpose of the initial solution search (this is expanded if SearchW is also set to be checked). When the solution is saved the Dropoff Early/Dropoff Late window is removed (and a SchTime window is not set on drop-off). This provides some tolerance on the drop-off EstTime when SearchW is unchecked but doesn't allow the suggested solution to be at any time of the day. Trapeze recommends selecting No.
PASS Scheduling > Tolerance - Dropoff Early	Earliest time, from the scheduled drop-off time, that a client can be dropped off.
PASS Scheduling > Tolerance - Dropoff Late	Latest time, from the scheduled drop-off time, that a client can be dropped off.
PASS Scheduling > Tolerance - Pickup Early	Earliest time, from the scheduled trip pick-up, when a client can be picked up.
PASS Scheduling > Tolerance - Pickup Late	Latest time, from the scheduled trip pick-up, when a client can be picked up.

PASS Scheduling > Weekly Activate Inactive Drivers & Vehicles

If PASS is not integrated with OPS, this switch allows inactive drivers and vehicles to be activated.

PASS Scheduling > Actual coordinates affect times

Specifies whether the Schedule Server should recalculate the actual time of an event after it receives the time posted by the MDT Server. For example, if a drop-off is scheduled for 15:30 but is performed at 15:25, the Schedule Server uses the time of 15:25 in recalculating the time between the arrive time and the next event. The change readjusts the schedule of succeeding events.

PASS Scheduling > Actual times affect times

Specifies whether AVL positions influence the calculation of the estimated times (ETA, EstTime, ETD). When set to No, only actual times typed by the user cause an update of the subsequent estimated times. When this property is set to Yes, all AVL positions reported by the vehicle affect the schedule. The Schedule Server should be restarted after changing this property value.

PASS Scheduling > Allowed Estimated Time Variance

How much time the estimated time can be after the scheduled early time.

The default value is 15 minutes.

PASS Scheduling > Allowed Estimated Time Variance - Enable for Taxi Pickup

Whether to enable use of the Taxi Pickup violation.

The default value is No.

PASS Scheduling > Appointment Time Buffer

Minimum amount of time before the trip's drop-off RL time that the trip must be scheduled.

PASS Scheduling > Arrive Should Set

Records the time when a trip is marked Arrived in the Schedule Editor.

ActualArriveTime: Schedule Editor shows, in both the actual arrival (Act Arr) column and the estimated arrival column (Est), the current time when a trip is marked Arrived.
EstTime: Schedule Editor shows the current time in the Est column when a trip is marked Arrived.
Both: Estimated arrive time is updated by the actual arrive time.
Default: Actual arrival time and estimated arrival time are updated for pickups and only the actual arrival time is updated for drop-offs .

PASS Scheduling > Arrived or Performed Events Can be Moved

Specifies whether events that have been marked as Arrived or Performed can be moved (for example, via drag-and-drop), and whether events can be moved before other events that have already been marked as Arrived or Performed.

PASS Scheduling > Auto Layover

Specifies whether automatic layover break events are created for live same-day inserts.

PASS Scheduling > Auto Layover Offset

Sets an auto layover event time to the current time plus a number of minutes to account for the delay in dispatching the insert that originally caused the auto layover. (Use a negative value to subtract minutes). The default value for the offset is +5 minutes.

PASS Scheduling > Average speed

Average speed used when calculating time and distance. Each additional factor is calculated using this speed as the base. When setting this speed, consider whether the system is rural or urban.

PASS Scheduling > Backtrack Ratio

A floating number multiplied by the farthest distance from the point of origin that clients reach during their trips. Leave the backtrack ratio set at the default. When set to 0, this feature is turned off.

PASS Scheduling > Backtrack Threshold

Minimum distance that clients are allowed to stray from their points of origin before near backtracking is activated. (Zigzagging is allowed within a small area.) When set to 0, this feature is turned off.

PASS Scheduling > Booking Activate: Check client eligibility dates

Specifies whether to activates subscription bookings only if the date of the booking complies with the Eligible From/Eligible To date fields in both the Certification and Funding Source tabs of the Clients screen.

PASS Scheduling > Breaks > Autobreaks > Lock Autobreaks Removes Rule

Specifies whether to remove the autobreak rule from the daily run if the Lock Autobreaks switch is enabled (in the Schedule Server application, click View > Switches, then in the Switches tab, expand PASS > SchedSrv > Autobreaks > Lock Autobreaks).

PASS Scheduling > Breaks > Autobreaks > Locked Break Type

Type of break (in the list of user-defined user breaks) that the Lock Autobreak process inserts into runs.

To do this, type the code for the break type corresponding to the codes shown in the Insert Break dialog box.

The original break type is used as the default for this property, and also if an invalid selection is made.

This property is not used for an autobreak rule if the Primary Break Type is set for the autobreak rule in Auto Driver Break Rules.

PASS Scheduling > Breaks > Default Break Length

Default break length if a break length is not specified in the Schedule Editor.

If no break length is specified here either, the break length defaults to 15 minutes.

Break lengths specified in the User Breaks properties override the default specified here.

PASS Scheduling > Breaks > User Breaks (User Break 0 to User Break 39)

Specifies a list of forty user-definable breaks (0 through 39).

Select a break to see the break code associated with it.

For example, if you select User Break 0, the code shown on the left frame is B0. The break code is shown in the Schedule Editor.

To specify break lengths, type a comma followed by a value from 1 to 999 (which represents the default number of minutes) after the break name.

The length specified here overrides the Default Break Length property.

PASS Scheduling > Bulk Scheduling > Match to Date Based Schedules (Default = false)

Used with Bulk runs (for PASS-ED school bus runs). Prevents users from batching template trips.

The default setting is False, meaning that if a user attempts to batch a template schedule, a warning appears and the batch process is canceled.