Impact of SLA Fields in Batch Optimization
The following table lists the scenarios in which SLA field values impact scheduling Batch 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
|
Error Text Updated in the Skipped WorkOrders File
|
|---|---|---|---|---|
|
20/06/2023 10:00 AM
|
22/06/2023 2:00 PM
|
No
|
PST and PET are in the past.
|
|
|
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.
|
|
|
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.
|
PST is out of the horizon and PET is null, skipping this WO.
|
|
Null
|
20/06/2023 10:00 AM
|
No
|
PST is Null and PET is in the past.
|
PST is NULL and PET is out of the horizon, skipping this WO.
|
|
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.
|
|
|
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.
• The OptiMax Error Text and OptiMax Status fields are not updated in the work order. Instead, the status and the error are updated in the Skipped WorkOrders files during the job run in the corresponding batch job records for the work orders not considered for scheduling. For more information, see Managing Skipped Work Orders.
|