Associated tabs - HxGN EAM - 12.1.1 - Feature Briefs - Hexagon

HxGN EAM Optimized Scheduler Dispatching

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
12.1.1

Ensure that you can see the records you created earlier that should be displayed on these tabs based on the header record organization. If you would like to limit the records on these tabs (for example, by Department) that will be sent to the OS based on the selected setup record, create a new dataspy on each tab to show these records. Make sure to include the following required fields, at a minimum, for each dataspy on the tabs. These fields contain the minimum data that the Constraint Optimizer needs to process each type of record:

  • WO Activities - Work Order, Activity, People Required, Hours Remaining, Calculated Priority, Equip. Location X, and Equip. Location Y (see WO equipment (A/S/P) to see where the values of these two location fields come from).

  • Crews - Crew, Organization, Starting X Coordinate, and Starting Y Coordinate.

  • Shifts - Shift

  • Employees - Employee, Organization, Starting X Coordinate, and Starting Y Coordinate.

  • Make sure you have a dataspy created on each of these tabs that shows the records you expect to be exported to the Constraint Optimizer as part of the selected Optimized Scheduler Setup record. If you do not see records you expect (or at all) first check any ‘where’ clause on the Dataspy, then make sure the records are setup as described elsewhere in this document.

  • The Dataspies created on these tabs will be selected on the setup record header to specify records to be sent to the Constraint Optimizer for that setup record. The dataspy does not need to be the default dataspy on its related tab to be used on the header.

  • Any dataspy created on these tabs must be a Global Dataspy. This is done so that any administrator working with this screen can see all Dataspies creating for this screen.

  • There must be at least one record on the WO Activities tab and at least one record on either the Crews or Employees tab to receive at least one dispatching record back from the Constraint Optimizer (remember, you are not required to use Shifts).

  • The WO Activities, Crews, and Employees grid definitions do not filter out records with invalid or missing location data. Records with missing or invalid locations will be displayed; however, the Optimized Scheduler job will fail when trying to process the setup record whose tabs contain missing or invalid location data. Make sure any WO equipment, Crews and Employees that will be used in this integration have valid location data.

  • WO activities dataspy - Be sure to specify in the dataspy for this grid the date range for which WO activities will be sent. You do not want WO activities that are scheduled to start 6 months from now being sent to the OS for dispatching today. This date range is based on a filter condition for Activity Start Date. So, if you want to dispatch all WO activities that start in the next week then set the filter condition to Activity Start Date >= +7.

    • A new field has been added to the list of filterable fields in the Edit Dataspy pop-up. The field is called "Undispatched WO Activities". It is a checkbox and it’s default value is unselected. Therefore, the default dataspy WILL show WO activities that are currently dispatched. Each time the Constraint Optimizer integration runs, any activities that are currently dispatched, but not completed, will be re-dispatched. If you do NOT want this to occur, you must change the dataspy by selecting this checkbox so that only undispatched WO activities show in the grid.

  • WO Type Authorization and Department Security are not enforced on these tabs. If the record’s organization is valid for the header record’s organization, then it will be displayed.