Running Optimizer Scheduler driver (job) - HxGN EAM - Version 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Optimized Scheduler Dispatching
Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1

The Optimized Scheduler job can be called to run in two ways:

  1. The job itself runs at its pre-scheduled time. When this occurs, the job will process all Optimized Scheduler Setup records that are ‘Active’ and whose Next Evaluation Date is in the past.

  2. The Run Optimized Scheduler button is clicked from an Optimized Scheduler Setup record. When this occurs, the job will process ONLY the selected Optimized Scheduler Setup record.

Regardless of how the job is initiated, it will process each Optimized Scheduler Setup record as follows:

  1. EAM will perform the four validations mentioned in the Optimized Scheduler Setup section. If they all pass, the following steps will be performed. Else, the Error field on the Optimized Scheduler Setup record will be populated with the appropriate error.

    1. Set the Optimized Scheduler Status to Processing.

    2. Populate/update Last Evaluation Date and Next Evaluation Date.

    3. Clear existing errors in the Error field for the Optimized Scheduler Setup record.

    4. EAM will send the records associated to each dataspy selected on the Optimized Scheduler Setup record header to the Constraint Optimizer for processing.

    5. Once a response is received by EAM from the Constraint Optimizer, the system will do the following for each Optimized Scheduler Setup record for which a response was received:

      1. Populate/update Last Optimized Scheduler Process Date.

      2. Set Optimized Scheduler Setup Status = Complete.

    6. Do the following for each WO activity successfully dispatched:

      1. Create a dispatch labor record (see Dispatch Labor for Work Order screen):

      • The Crew or Employee dispatched should be populated and the Dispatch Date should be set to the system date.

      • The Sequence should be populated as well for all dispatch records. The Sequence is relevant for each Crew or Employee and specifies the order in which each WO activity should be performed based on the Constraint Optimizer’s dispatching algorithm. The only place where Sequence can be viewed in the View/Delete Dispatch Labor Popup that is available when right-clicking a Crew or Employee on the GIS Map WO Dispatching screen.

      • If there are existing dispatch records for the WO activity, then these records will be deleted prior to adding the new dispatching records i.e. the WO activity will get re-dispatched each time the job runs until the activity is complete.

      1. Update the WO activity successfully dispatched as follows:

      • Update activity Assignment Status to indicate that it is dispatched for each activity. Value in org. option ACTDISST will be used.

      • Clear existing dispatch errors currently in the Optimized Scheduler Dispatch Errors field (errors populated the last time the WO activity was processed).

    7. Do the following for each WO activity that could not be dispatched:

      1. Enter one or more error messages into the Optimized Scheduler Dispatch Errors field (new in this release). Examples of errors might be "no qualified crew available" or "not enough availability to dispatch the WO activity". These exact errors are just examples, but they are real conditions that could cause a WO activity not to be dispatched.

      2. Also, change activity Assignment Status back to its default value if the current Assignment Status matches the value in the ACTDISST org option.

  • Assuming all other criteria are met, the Constraint Optimizer will dispatch a WO activity if it can be started prior to the end of the shift. The Constraint Optimizer does not consider if the work can be finished on the same shift when dispatching.

  • Any records whose Status = Processing (Constraint Optimizer is currently processing the related records, but has not sent a response back to EAM) AND it has been processing for more than 1 hour after the Next Evaluation Date, then the job will re-process the setup record. For example, if the Optimized Scheduler Setup record runs Daily at 3 P.M and the Next Evaluation Date = Mar. 5, 2021 3:00 P.M. the process will start at that time. When the process starts, the system will reset the Next Evaluation Date to Mar. 6, 2021 3:00 P.M. If the process that started on Mar. 5th has NOT received a response by the next scheduled evaluation date (i.e. Mar. 6, 2021 3:00 P.M.), the system will attempt to re-send the data to the Constraint Optimizer.

  • Vehicles that are associated to the Crews displayed for the selected Crew Dataspy will have their qualifications sent to the Constraint Optimizer, along with crew employee qualifications for dispatching purposes.

  • The Constraint Optimizer will only return results to EAM if at least one WO activity can be successfully dispatched. Else, no results will be returned. So, if you are testing this integration with only a few WO activities (or just one) and all of those activities cannot be dispatched for one reason or another (i.e. no crews qualified, no crews with enough employees, etc.), then these WO activity level errors will not be written into the activities themselves in this case. Instead, the Optimized Scheduler Setup record will remain in Processing status until the Next Evaluation Date, then run again.

  • In a subsequent release or patch, we plan to download the crew or employee’s WO activity dispatching Sequence to the Mobile Transit app. The crew and/or employee will have visibility to this information from their mobile device.