Setting up Constraint Optimizer records - 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

This integration will not necessarily send all the EAM data discussed in the previous sections. You will create Optimized Scheduler Setup records to define what data will be sent.

Create a setup record to specify the EAM dispatching data that should be sent to the Constraint Optimizer for dispatching purposes.

The header will contain the following:

Components

Description

Organization

(specific only) to control which data can be sent as part of the selected setup record.

Dataspies

Define the records to be sent with the selected setup record. There are four Dataspies (WO Activities, Crews, Employees, and Shifts).

Frequency

Specifies how often the selected setup record will be processed by the Optimized Scheduler job.

Use Road Distance

If selected, the Constraint Optimizer will use actual road distances between WO activities to determine dispatching results. Else, straight-line distance will be used.

Do not select the Active check box, or populate Next Evaluation Date, or select Dataspies when first saving the setup record. Data on the associated tab is required first (see Associated tabs for details).

After creating the necessary Dataspies on the associated tab, return to the header and do the following:

  1. Select a dataspy for the WO Activities Dataspy, Crews Dataspy, Employees Dataspy, and Shifts Dataspy fields. These selected Dataspies determine the specific data that will be sent to the Constraint Optimizer when the selected setup record is processed by the Optimized Scheduler job.

  2. Select the Active check box.

  3. Populate Next Evaluation Date.

The Optimized Scheduler Setup record is now ready to be processed by the Optimized Scheduler job during its next run.

See Run Optimized Scheduler Job section for more details as each Optimized Scheduler Setup record is processed by the job.

  • This new screen will be delivered in the R5 menu: Work > Setup.

  • If crews/employees will be dispatched at different frequencies, etc. based on Department or Organization, then create a separate setup record for each. In the case of Departments, the Organization on the setup header may the same; however, a dataspy should be created on the appropriate tabs to filter for the specific Department. This is just one example of the need for multiple setup records.

  • A Crew dataspy does not need to be created on the Crews tab for the selected record for it to be available in the Crews dataspy on the selected record. Any dataspy created on a setup record will be available for selection on all other setup records. The same holds true for WO Activities, Employees, and Shifts Dataspies.

  • Click the Test Optimized Scheduler Connection button to ensure that the cloud operations team has successfully established the necessary integration points between EAM and the Constraint Optimizer.

  • Click the Run Optimized Scheduler button to run the Optimized Scheduler job for the selected Optimized Scheduler Setup record only (manual run button). This contrasts with the Optimized Scheduler job processing all active Optimized Scheduler Setup records each time it runs.

    The following must be true before any information will be sent to the Constraint Optimizer. See Run Optimized Scheduler Job section for details of behavior after the below validations have passed:

    • The minimum required fields for each associated tab must be present in its dataspy selected on the record view (see Optimized Scheduler Setup > Associated Tabs section for details of required fields).

    • There must be at least one Crew or individual Employee displayed on its related tab for the dataspy selected on the record view. The Crew or Employee must also have a valid location (see appropriate section in this document for details).

    • There must be at least one WO activity displayed on its tab for the dataspy selected on the record view. The WO must also have a valid location (see appropriate section in this document for details).

    • All Crews and Employees displayed on its tab for the dataspy selected must either all be on a Shift for the system date or all must not be on a Shift for the system date. There cannot be a mixture.

  • If any of the validations mentioned above fail, the system will stop processing the record, no records will be sent to the Constraint Optimizer, and no records will be returned from the Constraint Optimizer. The error condition will be displayed in the Error field for the Optimized Scheduler Setup record. Clicking the Run Optimized Scheduler button will run the job for the selected record and can therefore cause these same errors to be populated to the Errors field.

  • If all validations mentioned above pass, the records will be sent to the Constraint Optimizer; however, some WO activities may not get dispatched for various reasons. We call these errors as well. These are WO activity specific errors and they will be populated into the Optimized Scheduler Dispatch Errors field on the Activities page for Work Orders after results are received from the Constraint Optimizer.

    Examples of these errors include:

    • No qualified crews were available.

    • Crews had no available time.

    • No crews with enough employees were found for the activity.

      These are just example messages for real situations that will occur.