SLA Fields' Impact in Real-time Optimization
The following table lists the scenarios in which SLA field values impact scheduling Real-time Optimization.
Current dispatch horizon time window: 26/06/2023 10 AM to 30/06/2023 6 PM
|
PST Specified in the Work Order
|
PET Specified in the Work Order
|
Work Order Considered for Scheduling?
|
Reason
|
OptiMax Error Text Field Update
|
OptiMax Status Field Update
|
|---|---|---|---|---|---|
|
20/06/2023 10:00 AM
|
22/06/2023 2:00 PM
|
No
|
PST and PET are in the past.
|
Both PST and PET are before the horizon dates. Hence skipping this WO from scheduling.
|
OPT_SKIPPED
|
|
24/06/2023 11:00 AM
|
28/06/2023 3:00 PM
|
Yes
|
PET is within the scheduling horizon.
|
||
|
02/07/2023 11:00 AM
|
03/07/2023 3:00 PM
|
No
|
PST and PET are in the future.
|
As both PST and PET are beyond the Horizon dates, skipping this WO from scheduling.
|
OPT_SKIPPED
|
|
25/06/2023 2:00 PM
|
04/07/2923 10:00 AM
|
Yes
|
PST and PET are such that current scheduling dates are covered.
|
||
|
27/06/2023 11:00 AM
|
29/06/2023 10:00 AM
|
Yes
|
PST and PET are within the current scheduling horizon.
|
||
|
25/06/2023 2:00 PM
|
Null
|
Yes
|
PET is Null, so PET is considered as the current scheduling horizon end date by default.
|
||
|
28/06/2023 10:00 AM
|
Null
|
Yes
|
PST is within the scheduling horizon.
|
||
|
02/07/2023 11:00 AM
|
Null
|
No
|
PST is in the future and PET Is Null.
|
As PST is out of the Horizon and PET is null, skipping this WO from scheduling.
|
OPT_SKIPPED
|
|
Null
|
20/06/2023 10:00 AM
|
No
|
PST is Null and PET is in the past.
|
As PST is NULL and PET is out of Horizon, skipping this WO from scheduling.
|
OPT_SKIPPED
|
|
Null
|
29/06/2023 3:00 PM
|
Yes
|
PET is within the scheduling horizon.
|
||
|
Null
|
02/07/2023 11:00 AM
|
Yes
|
PST is Null, so PST is considered as the current scheduling horizon start date by default.
|
||
|
27/06/2023 10:00 AM
|
02/07/2023 11:00 AM
|
Yes
|
PST is within the scheduling horizon.
|
||
|
Null
|
26/06/2023 6:00 PM
|
Yes
|
PET is within the scheduling horizon.
|
||
|
30/06/2023 10:00 AM
|
Null
|
Yes
|
PST is within the scheduling horizon.
|
||
|
26/06/2023 10:00 AM
|
30/06/2023 6:00 PM
|
Yes
|
PST and PET are within the current scheduling horizon.
|
||
|
28/06/2023 5:00 PM
|
30/06/2023 6:00 PM
|
Yes
|
PST and PET are within the current scheduling horizon.
|
||
|
26/06/2023 10:00 AM
|
28/06/2023 5:00 PM
|
Yes
|
PST and PET are within the current scheduling Horizon.
|
||
|
26/06/2023 10:00 AM
|
26/06/2023 2:00 PM
|
Yes
|
PST and PET are within the current scheduling horizon.
|
||
|
30/06/2023 12:00 PM
|
30/06/2023 6:00 PM
|
Yes
|
PST and PET are within the current scheduling horizon.
|
||
|
26/06/2023 10:00 PM
|
27/06/2023 6:00 AM
|
No
|
PST and PET do not have valid working hours.
|
Skipping this WO as it does not have valid access hours.
|
OPT_ERROR
|
|
26/06/2023 10:00 PM
|
27/06/2023 2:00 PM
|
Yes
|
PET is within the scheduling horizon.
|
||
|
Null
|
Null
|
Yes
|
Current scheduling PST and PET are considered by default.
|
 |
The dispatch horizon time window is calculated in business days and not calendar days. If the specified dispatch horizon in the dispatch process is five days, the next five business days are considered as the dispatch horizon. If there are holidays or weekends within that time window, those days are not considered.
|