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.

« How far "Pull" concept should drive your Supply Chain Activities? | Main | Keeping up with Order Fill rate in a Reactive Supply Chain environment »

Why my EAM implementation is not giving me as I expected?

Enough has been written on this but mainly in context of ERP. There have been many reasons given- toppers are lack of training, lack of top management commitment, poor package fitment and, unrealistic expectation etc. While, most of these hold good for EAM packages as well but I see two other reasons which are also the major factors for EAMs; (i) Master Data Management (ii) ease of use.

EAMs are data eaters and that too quality data. I have seen some EAM implementations not living up to the expectations and the simple reason being the data which was fed during implementation was not usable, though the package was a good fit for the business processes. For example, a standard operating procedure (SOP) for a maintenance job. The SOPs provided by equipment manufactures come in many shapes & formats and varies in granularity. Modeling those in an EAM package is a tedious job and if not done with proper planning can make whole equipment's SOPs unusable. The most common reason I have seen is granularity of SOPs. Many implementations even have the data which goes into lowest level of operations/tasks, and which is not required to be reported into software; though those tasks may be required to execute. Implementation team should note that while it is good to have each & every operation details to be maintained in system library but they should also note that while maintenance users report the actual against these tasks, they should not be spending too much time entering data into software. I have seen instances where maintenance teams spending more time to enter the data than the time spent actually on machines. Hence there should be a fine balance between data granularity & actual requirements. 

Ease of use is another factor. EAM packages are mainly used by shop floor people who spent most of their time working with machines and then find some time to report data into packaged application later in the day. These folks are not very much computer savvy and are not expected to be super users for sophisticated softwares. They do not have lot of times as well to struggle with bulky navigation of complex packages. Hence an easy to use package, tailored screens, mobile devices, touch screens etc are to be used by EAM users to make the implementation successful and get more out of the package. The user interface, specially for shop floor folks, should be as simple as pressing few buttons on a hand-held device or a touch screen. Probably that is going to be the most emerging trends for future EAM packages.
Certainly, all other reasons which hold good for ERPs are relevant for EAM as well. Add if you have seen any other potential failure reasons for EAMs.

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