Business requirements - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

HxGN EAM to EAM Synchronization

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1
  • Each node needs the ability to operate on an EAM instance at the node which will be the main point of entry for employees at the node location so the node location can operate when disconnected from satellite.

  • Each node instance would be an org specific to that node.

  • Each org would then be replicated to a Root instance which would contain all node orgs into a single instance for access by the Root.

  • All integrations would happen at the root level.

  • Root wants to be able to create WOs, assets, POs in any organization.

  • Root will be able to control certain information where it is only changed at the Root level. (This may include code tables, etc. to be defined during requirements gathering) OK, that would mean HW master data that would be read-only access for the rig.

  • All information updated through integration or manual entry at the Root has to be synchronized at the node level.

  • All nodes need the ability to view QOH for identified parts and assets from any node or alternate warehouses. This could be all parts or assets. Nodes may have need to request parts or assets from other nodes. Ability to make a warehouse pingable or non-pingable ("Pinging" is the visibility of inventory on other facilities and shore based warehouses).

  • Root instance would serve as disaster recovery for nodes should something happen to a node instance. This goal may not be achieved this way as IDM documents, ION flows, triggers and non-transactional data may be lost. This may need to be approached from the DB backup perspective.