Delineate the boundaries between ArcGIS and EAM

[Hussam_AlJabri]

Hey Freinds,

I would like to discuss the evolving nature of ArcGIS as it transforms into an Enterprise platform, encompassing various functions that overlap with other systems such as EAM, serving as a system of records or asset registry.

I am seeking guidance on how to effectively delineate the boundaries between these systems and harness their full potential capabilities. This is particularly relevant for organizations embarking on the development of systems and networks from scratch.

Thank you for your valuable insights.

[BrianBerube_GIS · Accepted solution]

Hi @Hussam_AlJabri ,

This is a common question for those embarking on this same or similar journey. A few questions to consider as you embark on developing systems and networks from scratch in general with the ArcGIS System are: 

1.) Identify ways your organization will benefit from integrating key systems with your enterprise GIS.

2.) Understand the integration methods, tools, and capabilities ArcGIS and your other enterprise systems provide so you can choose the best approach for your integration.

3.) Add context and transform business data into information that enables people to make more informed decisions.

Finally, we have available a reference architecture white paper called Architecting the ArcGIS System: Best Practices here: https://www.esri.com/content/dam/esrisites/en-us/media/technical-papers/architecting-the-arcgis-syst...  (I've also attached to my reply) I would suggest reading this to understand all best practices related to the ArcGIS System, however, there is a specific section on Page 12 regarding Integration considerations which contains the 3 questions I've mentioned above and additional context for you or others to consider. 

[Hussam_AlJabri]

Thanks for sharing your insights. I have read the doc you shared and find it useful now.

Do you know where I can get robust use cases where the GIS geo-enabling the other enterprise systems?

[robertopepato_bizpoke]

I've been working with the integration of enterprise EAM and GIS systems for some years and I have noticed implementations in both ways: GIS as the system of records/asset registry and the other way around.

Depending on a number of factors, sometimes EAM is used as the system of records/asset registry and integration loads/updates assets into GIS by using coordinates previously captured and stored in EAM; and sometimes GIS is used as the system of records/asset registry and integration loads/updates
data into EAM periodically. IMO, the "right" way depends on, as I said, organization context and a number of factors.

I believe that, no matter the chosen pattern for integration, combining functionality from both systems can create powerful solutions:

* One can think of GIS to add value and save money on maintenance planning and dispatching, among many other possibilities;

* EAM, on the other hand, can handle financial and operational aspects of maintenance (track asset inventory, preventive maintenance, emergency maintenance, and so on).

Regards,