Processing rules for defining equipment records within Esri

See the list of processing rules followed when HxGN EAM equipment records are automatically created for GIS features you have created within Esri:

Note: Contact your system administrator for more information regarding these processing rules.
Processing rules
A GIS feature must reside within a layer that contains the GISOBJID attribute before you can create a corresponding equipment record.
Equipment records are created based on the field mappings defined for the feature’s layer. If a field mapping has not been defined, the field is populated based on the GIS profile defined on the user’s default preference record for the layer.
Note: If a field mapping for an attribute exists, the equipment field is always populated based on the data of the attribute, even if the attribute value is empty and the GIS profile value contains data.
  • Field mappings are not defined for Layer, Location X, and Location Y. The equipment records are created based on an implied mapping where GIS is the owner and the data is automatically mapped to the Layer, Location X, and Location Y fields in HxGN EAM.
  • If a feature is a line or polygon feature, the HxGN EAM Location X and Location Y are populated based on the feature’s center point.
If more than one GIS attribute is mapped to a single HxGN EAM field, the data is concatenated into the single field based on the Sequence and Delimiter values on the mapping record.

Likewise, if a GIS attribute that contains concatenated data is mapped into more than one HxGN EAM field, the data is parsed based on the Sequence and Delimiter values on the mapping record.
The equipment is automatically defined as an Asset record if a field mapping does not exist for the equipment type.
The equipment code of the equipment record is assigned based on any existing field mapping. If a feature attribute is mapped to the equipment code field, the equipment code is assigned based on the field mapping even if the AUTOANUM installation parameter is set to Yes.

If no field mapping exists for the equipment code, an equipment code is automatically generated even if AUTOANUM is set to No.
The following HxGN EAM fields can be unique per HxGN EAM organization:
  • Class
  • Location
  • Position
  • Parent
  • PO
  • Part

This organization may or may not be the same organization of the equipment record.

If there is a mapping record for Class, Location, Position, Parent, PO, or Part, these must also get populated: the organization of Class, Location, Position, Parent, PO, or Part. If you map data into these fields, you must also map the organization field for each of them.

If a field mapping does not exist for the organization of Class, Location, Position, Parent, PO, or Part, the information is populated based on the following:
  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to a single organization:

    The organization is copied.

  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to multiple organizations:

    An attempt is made to populate the organization based on the GIS profile defined on the user’s default preference record for the layer.

  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to multiple organizations and there is not a default GIS profile:

    An attempt is made to populate the organization based on the organization of the equipment record.