PLM vs EAM for MRO
Mary Gorczynski 1100006B54 firstname.lastname@example.org | | Tags:  government eam plm maximo mro arc-advisory-group
1 Comments | 9,735 Visits
Today's blog comes from David Turner.
First let's start with the definitions:
1. PLM - Product Lifecycle Management is the process of managing the entire lifecycle of a product from its conception, through design and manufacture, to service and disposal.
2. EAM - Enterprise Asset Management means the whole life optimal management of the physical assets of an organization to maximize value.
3. MRO - All actions which have the objective of retaining or restoring an item in or to a state in which it can perform its required function. The actions include the combination of all technical and corresponding administrative, managerial, and supervision actions.
Now the Question: Why should an organization use an asset management system (EAM) versus a Product Lifecycle Management (PLM) system?
PLM software is used by manufacturing and construction organizations and is designed from the ground up to support all aspects of design and manufacturing. EAM software is designed to support all aspects of maintaining physical assets. In recent years, PLM systems have added some MRO (maintenance repair and operations) capabilities to support manufacturing organizations that also provide aftermarket services to maintain equipment in the field. This is not the predominant solution for aftermarket service providers and most large aftermarket service operations choose to simply integrate EAM software to their PLM systems to support maintenance and logistics. This approach is even more widely adopted by aftermarket service providers that service more than one OEM brand of equipment (and therefore multiple PLM systems are considered).
Differences between PLM and EAM functionality
The most basic difference is simply that EAM (Maximo) is designed to support maintenance and repair while PLM is built to support manufacturing and construction. A few other core differences are outlined in the following table. Note hyperlinks are available to references in quotes.
Why Maximo is a better fit for MRO
1. Built to support maintenance and repair operations and is the market leader. There are no PLM vendors even considered in Gartner Magic Quadrants ARC Advisory market studies.
2. Readily integrates with existing business and engineering systems through it’s integration framework that supports old and new integration technologies (flat file to web services).
3. Provides a “platform” for continuous improvement and potential absorption of other stove-piped systems.
4. Multiple options for deploying on mobile devices, both connected and disconnected.
Why Maximo is a less costly solution than PLM software for MRO
1. Very flexible and configurable, allowing us to implement incrementally and achieve early results and returns on investment.
2. Vast partner network affording us reasonable implementation and support options. In other words, finding good Maximo technical talent is not difficult or expensive.
3. Does not require as much IT technical resources to implement as a PLM solution.
To gain a perspective from ARC Advisory Group, register for this "IBM EAM enables higher stakeholder value" whitepaper here.