Map layers and HxGN EAM equipment screens - HxGN EAM - Version 12.0.1 - Feature Briefs

HxGN EAM GIS

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

Deciding which map layers will be integrated. It is not necessary to integrate all layers with HxGN EAM for proper implementation. It is recommended to integrate only the layers that will be tracked as equipment in HxGN EAM. This should be determined before any features or equipment are created and synchronized. Often it is helpful to create classes of equipment in HxGN EAM that correspond to features types in GIS. For example, all equipment in HxGN EAM mapped to features in the Streetlights layer in GIS could be in an equipment class of Streetlights. You may also choose to make a copy of the asset screen in HxGN EAM and name it according to the equipment type or class. For example, a copy of the asset screen could be called Streetlights and have a filter that displays only equipment with class of Streetlights. Use the Field Filter setup screen to achieve this. In this way, it is possible to hide the class field on the appropriate screen and set its default value to the correct class. You might also limit access to this screen to only the users who will be planning and performing maintenance on Streetlights. Organizing it in a thoughtful way that makes sense can help manage your HxGN EAM data more effectively.

Once it is determined whether all layers should be integrated or not, another key decision is to decide if all layers should be visible in HxGN EAM. Displaying fewer layers per map usually results in better performance of the map screens in HxGN EAM. It may be determined that the map can be loaded initially with fewer layers visible by default. Layer display can be managed either in ArcMap, ArcGIS Pro, or in HxGN EAM map screens. Using the map controls in HxGN EAM, layers can be enabled or disabled as needed. These preferences are then saved and tracked per user. This gives control of layer visibility depending on the job function or preference of each individual user.

In many cases, even greater flexibility is needed so HxGN EAM provides the ability to assign different maps to various users.

See the Configuring multiple maps section for further information on limiting certain map data to only relevant users for that data.

Another decision is whether the equipment will be created in HxGN EAM first or will features be created in GIS first? Before creating HxGN EAM equipment, consider the customer needs and what makes sense in their environment. It is wise to decide the best way to set up the equipment in HxGN EAM before creating any data in GIS or creating any HxGN EAM data from GIS features. It may be helpful to review Asset Management and Understanding equipment in the HxGN EAM User Guide before creating equipment records. Once the equipment is created in HxGN EAM, you will need to create data mapping for the fields to be tracked in HxGN EAM to fields in the GIS layer tables. When creating data mappings, use the Source field to determine which system owns the data on the initial creation of records. Use the Owner field to determine which system owns the data for future synchronization of specific feature attributes after the initial creation.

Most customers utilizing HxGN EAM and GIS integration prefer HxGN EAM track the actual physical work required to install a new feature in a certain area. Since the feature does not yet exist in HxGN EAM, a work order is created against a similar equipment or parent equipment. Paperwork with the details of the new feature is passed to the GIS analyst who will then create the new feature on the GIS map. Once the feature is created and approved, synchronization is run to create the corresponding equipment in HxGN EAM. Once the record exists in the two systems, the equipment on the installation work order can be updated to the new equipment.