SLA Fields' Impact in Long-Term Planning
When an LTP dispatch process job exists in the org along with Batch or Real-Time Optimization dispatch process jobs, the dispatch horizons of both the dispatch processes impact the scheduling.
LTP job schedules the work order when it is within its dispatch horizon.
When the same work order falls within the Batch/RTO dispatch horizon, the work order is considered for scheduling again, to further optimize the schedule.
The following table lists the scenarios in which SLA field values impact the work order scheduling when both LTP and Batch dispatch process jobs are actively running.
Consider the following scenario:
Current batch horizon time window: 26/06/2023 10 AM to 30/06/2023 6 PM
Current LTP horizon time window: 01/07/2023 10 AM to 05/07/2023 6 PM
PST Specified in the Work Order
PET Specified in the Work Order
Batch Scheduling
LTP Scheduling
Comments
Work Order Considered for Scheduling?
Reason
Work Order Considered for Scheduling?
Reason
26/06/2023 10:00 AM
27/06/2023 6:00 PM
Yes
PST and PET are within the batch scheduling horizon.
No
PST and PET are in the past.
28/06/2023 11:00 AM
03/07/2023 3:00 PM
No
Yes
PET falls within the horizon.
07/07/2023 11:00 AM
08/07/2023 6:00 PM
No
PST and PET are in the future.
No
PST and PET are in the future.
28/06/2023 12:00 PM
08/07/2023 6:00 PM
Yes
PST is within the batch scheduling horizon.
Yes
PST and PET are such that current scheduling dates are covered.
In such cases
when the PST and PET overlap both the batch and LTP horizons, whichever job runs first schedules the work order.
02/07/2023 2:00 PM
05/07/2023 6:00 PM
No
PST is outside the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
27/06/2023 1:00 PM
Null
Yes
PST is within the batch scheduling horizon.
No
Both PST and PET are mandatory.
03/07/2023 11:00 AM
Null
No
PST is outside the scheduling horizon.
No
Both PST and PET are mandatory.
10/07/2023 10:00 AM
Null
No
PST is outside the scheduling horizon.
No
Both PST and PET are mandatory.
Null
13/06/2023 1:00 PM
No
PET is in the past.
No
Both PST and PET are mandatory.
04/07/2023 6:00 PM
Null
No
As PST is outside the batch horizon and PET is null it is skipped.
No
Both PST and PET are mandatory.
Null
12/07/2023 10:00 AM
Yes
PST is null, so the current scheduling PST is considered.
No
Both PST and PET are mandatory.
01/07/2023 10:00 AM
09/07/2023 6:00 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are such that current scheduling dates are covered.
Null
01/07/2023 8:00 PM
Yes
PST is null, so the current scheduling PST is considered.
No
Both PST and PET are mandatory.
05/07/2023 10:00 AM
Null
No
PET is null and PST is outside the scheduling horizon.
No
Both PST and PET are mandatory.
01/07/2023 10:00 AM
05/07/2023 9:30 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
03/07/2023 12:00 PM
05/07/2023 9:30 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
01/07/2023 10:00 AM
04/07/2023 12:30 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
01/07/2023 10:00 AM
01/07/2023 8:30 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
05/07/2023 10:00 AM
05/07/2023 5:00 PM
No
PST and PET are not within the scheduling horizon.
Yes
PST and PET are within the scheduling horizon.
01/07/2023 11:30 PM
02/07/2023 7:00 AM
No
PST and PET are not within the scheduling horizon.
No
PST and PET hours are not valid.
02/07/2023 11:00 PM
03/07/2023 11:00 AM
No
PST and PET are not within the scheduling horizon.
Yes
PET is within the horizon and falls under scheduling horizon valid hours.
Null
Null
Yes
The current scheduling horizon start and end date are considered as the PST and PET values.
No
Both PST and PET are mandatory.
* 
The dispatch horizon time window is calculated in business days and not calendar days. If the specified dispatch horizon in the dispatch process is 5 days, the next 5 business days are considered as the dispatch horizon. If there are holidays or weekends within that time window, those days are not considered.
If the OptiMax Error Text and OptiMax Status fields are not updated in the work order, the status is updated in the Skipped WorkOrders files during the job run. For more information, see Managing Skipped Work Orders.
Was this helpful?