Enterprise Asset Management (EAM) tools allow managers, especially in companies with a high number of dispersed assets, to have a broad view of the asset life cycle and its relationship to operations.
These tools go far beyond a simple Maintenance Manager (GMAO/CMMS) and can include in their analysis financial issues such as full cost of the asset (CAPEX+OPEX), depreciation, repair costs versus replacement costs, calculation of the cost of ownership of the assets, etc.
In summary, the objective of an M&A is to manage assets throughout their life cycle by optimizing operational efficiency to obtain the highest possible return on investment.
The implementation of this type of solution is not only based on technology: it is about optimising critical processes, together with the end user, to achieve significant savings in operations and costs. The operational management of the asset involves a series of coordination difficulties, which can be solved with agile processes, supported by workflows and detached from the accounting rigidity inherent in the asset and the services involved.
Phases of MEA implementation
The implementation of an EAM tool does not have to be a long-term project and, if done correctly, has a rapid return on investment.
A phased project approach depending on the business processes contemplated in the scope allows the delivery of a complete, turnkey service, with strict compliance in time and form, thus guaranteeing the final result and the achievement of the client’s business objectives.
Beyond the mere implementation of the technological solution, which we will see later, the implementation of the EAM must ensure that both the software and the processes and data are aligned with the objectives and needs of the company in a given context.
How can this level of customisation be achieved for the client and at the same time be implemented quickly and efficiently? The use of a modular and sectorised solution, such as Retain, allows the maximum optimisation of the implementation process following 3 levels of configuration.
On the first level, the EAM has a complete suite of applications and generic tools, as well as a centralised database and various connectors.
On this basis, the second level incorporates sector customisations adapted to different generic business models.
Finally, for each client a customised solution is configured based on the sectorial solution that best suits their needs, incorporating the necessary customisations and developments until the optimum solution is achieved.
EAM implementation methodology
This type of EAM configuration also allows for a phased implementation capable of supporting a continuous improvement process throughout the life of the project.
Phase 1: Contrast and decisions
- A contrast is made based on the analysis of the customer’s current processes and the standard functional coverage of the MES against the customer’s current requirements and technology.
- Review of the client’s current technology and incorporation of best practices.
- Preparation of detailed documentation of functional requirements.
Phase 2: Parameterisation of the solutions
- The EAM sectorial solution that best adapts to the scope defined by the client’s requirements is implemented.
- On this configuration, a customised construction is made, including the necessary customisations and developments to implement the new processes that respond to the defined requirements.
- Creation of a prototype to validate the most critical scenarios and the functional tests of the developments made.
- Data loading, including the migration of pre-existing data and the collection and improvement of data from other applications.
- Strict compliance with quality standards.
Phase 3: Continuous improvement
The implementation of the EAM must incorporate business intelligence tools that allow us to have a measure of the efficiency of the system through various KPIs set in phase 1.
Based on these efficiency measures, we will be able to compare them with the objective indicators or with the system’s own history, allowing us to make adjustments to the processes in a cycle of continuous improvement until maximum efficiency is obtained in the operation.
Conclusions. Implementation of Retain EAM
The methodological approach is fundamental to achieving the objectives of the project. At Retain, the implementation methodology specifies how we develop our model in a given context, adapted to each business and its characteristics.
If you want to know more about Retain, contact us and an expert will contact you to design the solution that best suits the characteristics of your company.