Batch Optimization Known Issues
The following are the known issues in Batch Optimization.
Recursive Events Issue
Recursive events created in Lightning mode are not considered during scheduling. ServiceMax recommends that you create recursive events in Classic mode.
Territory Unassignment Issue
When you change or remove the territory of a technician who has scheduled work orders, Batch Optimization does not recognize the change or removal of the territory.
For example, technician Tina belongs to the NY territory. On the dispatch process job run on 11/03.2020, a work order is assigned to Tina for 11/05/2020. Tina was moved to NJ territory on 11/04/2020. Schedule Optimization does not recognize this change and reschedules the work order that is assigned to Tina for 11/05/2020.
In such a case, you must manually unassign the work orders.
Dispatch Process Job Run Time Limitation
The scheduled time for the job run for the dispatch process should not be the same as the start time of the associated territories' business hours. For example, if the territory's business hours start at 8:00 AM, the job run should not be scheduled at 8:00 AM.
ServiceMax recommends that you set the dispatch process job run time to a time before the start time of the associated territories' business hours. This ensures that the dispatch process job run schedules all the work orders marked for the current day.
Consider the following examples:
• If the dispatch process territory's Business Hours start at 8:00 AM and the dispatch process job run is scheduled before 8:00 AM (for example, at 7:45 AM), this job run schedules all the work orders marked for the current day.
• If the dispatch process territory's Business Hours start at 8:00 AM and the dispatch process job run is scheduled after 8:00 AM (for example, at 8:15 AM), this job run does not schedule the work orders marked for the current day. It only schedules the work orders marked for the next day.