• The Recommended slots are displayed at the beginning of the table. However, you can sort the table by date. The Recommended slots mean that those slots are recommended regarding route suitability and cost factor.

• One slot is displayed per technician per day, when there is no non WO event or manually scheduled event is present in the route. If a non WO event or manually scheduled event is present in the route, then two slots are displayed for that technician, one slot before the event and another after the event.

• Two slots are displayed if the event is present in the route, and if the service duration and travel time can be accommodated within the available time before and after the event.

• Slots are displayed for all the technicians in the territory for the span of the dispatch horizon days.

• The Start Date and End Date values are the dispatch horizon start and end dates by default. You can change the date range. If you change the date range, the updated open slots table is displayed only when you click Run.

• If the dispatch horizon is more than 30 days, Propose Times displays slots for the first 15 days only. The date picker fields are also updated to reflect the first 15 days. You must manually change the date range to reflect the rest of the date range within the dispatch horizon and click Run to view the open slots for the rest of the dispatch horizon.

• Poor slots are not displayed by default. Click the Show Poor Slots checkbox to display poor slots. You can only view poor slots and not book one. If you try to book a poor slot, an error message is displayed informing you that you cannot book the slot because it is a poor one. You can only view the poor slots' information as a reference.

• If the technician for whom you have booked the arrival window becomes unavailable, the work order is rescheduled to another available technician for the same arrival window. The fixed arrival window is honored, even though the assigned technician may change.

• The work orders booked with the Propose Time option honor the time window, but they can start anytime within the window. For example, if the arrival window is 8 AM-9 AM, the work order start time can be 8.15 AM.

• Batch Optimization can change the scheduled time of the work order booked via Propose Time to any time within the selected window.

• The following are honored for work orders booked using the Propose Time option:

◦ Technician efficiency

◦ Preferred/mandatory/prohibited technician for the work order

• If any scheduling-related fields of a work order booked using the Propose Time option are updated before the Batch Optimization job run, the updated values are considered during optimization.

• The Batch job runs containing only the proposed time-booked work orders fail. This is because the propose time-booked work orders are fixed events, and the optimizer can optimize a set of work orders during a job run only when there is at least one work order that is qualified for the Optimized Batch that is not a fixed work order.

• When no technician in the territory is available in the Propose time Booked slots, the Propose time booked WO is marked as Bad event by the server and it overlaps with another WO by the optimizer.

• The following features are not supported when using the Propose Time option:

◦ Capacity reservation

◦ Overnight stay