The Infosys global supply chain management blog enables leaner supply chains through process and IT related interventions. Discuss the latest trends and solutions across the supply chain management landscape.

« Catch Me If You Can.... the continuing evolution of catch weight items | Main | Product Allocation Planning - Managing supply constraints »

Role of EAM Packages in Smart Grid - Part 2

This is in continuation of my previous blog on Role of EAM packages in Smart Grid.

This note of mine is focused on debate of ownership issues of Asset Register - where asset date to be kept - EAM system or GIS or both based on data classification.

To arrive on conclusion, let's understand what kind of data is stored in EAM and GIS systems. GIS generally stores coordinates, spatial attributes of an asset while EAM is more about physical characteristics of the asset. But at the same time, both the systems, more or less, are capable of storing, managing and handling all the information - spatial or physical attributes.

Let's also consider what are the end-user's needs from these systems - GIS systems are mainly to view the asset by its location, position, and travel route graphically. Users would like to use EAM systems to know about the physical characteristics of the assets - in both offline and online mode. Many times, users working at asset's location would also like to see multiple types of information - Asset's relationship/dependency on other assets in nearby area, its subassembly, previous work done on the asset etc. To see all this information, users would like to see the entire information in one system and would not like to switch between applications.

Considering the about two facts, it is reasonable to assume that while there is some data which is best managed in GIS and some in EAM, but at the same time, user experience should also be considered before deciding about the data ownership.

So, my view is that data to be shared by these two systems - GIS managing the network connectivity and EAM managing the physical attributes but the important consideration should that data should be made available in the system where user wants it. While there are lots of integration options available to seamlessly exchange the data between any two systems, data duplication to be kept minimum to avoid data quality issues.


Praveen, convergence is impacting all industries and technologies rapidly, so I anticipate there will increasingly be situations where the more expensive and critical assets themselves get instrumented and business services provide the analysis or reporting that users require - these services can access systems of record and some information directly from the assets.

Thanks for the comments.
Yes, Your comments are fully aligned with my thoughts. I had written a note on this topic few months ago. You may want to read that:

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter