The use of the term mapping in this document refers only to the exercise of defining
the relationship between GIS and HxGN EAM attributes also referred to as data mapping.
This screen allows administrators to set up field mappings between GIS attributes for a given layer and HxGN EAM equipment field attributes. Even though the entry point for this function is not from the HxGN EAM application, the storage for the mappings is in the HxGN EAM database.
The GIS attribute lookup shows the list of fields available in the table of the selected layer. For this lookup field aliases are supported. The HxGN EAM Attribute lookup shows a list of fields in the HxGN EAM equipment table for which the user has permission including user defined fields, custom fields, and comments. If the boiler text for a user defined field has been changed in the HxGN EAM system, these aliases are not displayed in this lookup. You may link GIS related attributes to equipment attributes, including equipment user defined fields custom fields and comments. Since some attributes "are seen as" strictly maintenance related while other data may need to reside in both systems, users can choose whether this data is copied or moved to HxGN EAM and vice versa. Note that if custom fields or comments are used in field mappings these should be limited to a small number, perhaps 10 or less. Mapping too many custom fields can significantly slow synchronization performance.
These mapping will be used by the system, whenever features are created in GIS, to create the corresponding equipment automatically in HxGN EAM as well as when equipment is created in EAM to create corresponding features in GIS. The mapping function supports the use of hard coded values as well as concatenated sequenced values being pushed to HxGN EAM records. This allows more than one GIS attribute to be mapped to a single HxGN EAM attribute. When this mapping is used to create equipment, the values for each of the GIS attributes will be concatenated into a single HxGN EAM attribute.
However, the system enforces certain rules to maintain the integrity of the data in both systems. The following are mapping rules that will be enforced by the system when the record is submitted. If a rule is violated at submit time, the system will display the appropriate error message.
-
Do not allow duplicate GIS Attributes or HxGN EAM Attributes for multiple records that have different Owners.
-
If the Source field is ‘GIS’ or ‘Both,’ do not allow HxGN EAM Attribute, and Sequence to be duplicated for multiple records.
-
If the Source field is ‘HxGN EAM’ or ‘Both,’ do not allow GIS Attribute, and Sequence to be duplicated for multiple records.
-
If the Source is ‘HxGN EAM’ or ‘Both,’ do not allow HxGN EAM Attribute and Sequence to be duplicated for multiple records.
-
If Source = ‘GIS’ or ‘Both,’ do not allow GIS Attribute and Sequence to be duplicated for multiple records.
-
Do not allow Source, GIS Attribute or GIS Value, HxGN EAM Attribute or HxGN EAM Value to be duplicated for multiple records. Note that in addition to this scenario, if all the fields above match, except Source, and at least one of the matching records has its Source as ‘Both’ then these records will be considered duplicates as well.
See the Mapping data types section of this document for additional information.