Typical message flow for Advanced Maintenance Planning - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Integrating with Infor ION
Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1

The follow diagram shows a typical message flow for Advanced Maintenance Planning integration process.

  1. HxGN EAM and ERP synchronizes master data used in the integrated, including the following:

    • Resources or Constrained Resources are production resources in the ERP. In HxGN EAM, they are related to equipment on which HxGN EAM performs maintenance operations.

    • Priority Code, carried in CodeDefinition, is to synchronize the priority measurement indicators between HxGN EAM and the ERP.

  2. When HxGN EAM releases a work order that requires downtime for a piece of equipment, HxGN EAM creates an approved Production Request for the resource that is linked to the equipment. HxGN EAM also publishes the production request in a ProcessProductionOrder message, although the production order, which is of type Maintenance Task, does not specify a finished good item.

  3. The ERP receives the ProcessProductionOrder message and creates a resource schedule requirement for the resource indicated in the production order message.

  4. The ERP resource scheduler plans the actual period for the production order originated in HxGN EAM to be performed, by changing the status of the production order to Firm. This triggers a message of SyncProductionOrder.

  5. HxGN EAM subscribes to SyncProductionOrder messages and detects that a production order linked to its production request is in Firm status. HxGN EAM updates the actual work order schedule with the schedule from the SyncProductionOrder message.

  6. The user performs the maintenance task and closes the work order in HxGN EAM. That causes HxGN EAM to send another ProcessProductionOrder message to request changing the Production Order status in the ERP to Completed.

  7. Either system can request the cancellation of a production order originated from an HxGN EAM production request, through the ProcessProductionOrder or SyncProductionOrder message.