IBM Maximo Asset Management System - A Process Driven Methodology

It is often the case that clients and implementers see Maximo as an IT driven project focusing primarily on the installation of the software and on the functionality delivered by it.

Over the last two decades Peacock Engineering have established a methodology that focuses on two key principals:

• The delivery of  digital asset management and service management excellence is dependent on clearly defined business process
• Those processes must be aligned to what is important to the business in order for them to be seen as valuable and therefore justify investment in systems to support them.

Business Process Definition

Rather than focus on the applications and functionality of Maximo, Peacock Engineering have developed a process model that breaks Digital Asset Management and/or Service Management into discrete, manageable and measurable process elements. These process elements can then be defined in detail and the support required from Maximo justified. Responsibilities for execution of the process can also be clearly understood. The simple illustration below contrasts the typical approach of taking the Maximo Work Order application with the Peacock approach of breaking the work management process into discrete processes. Peacock Engineering have develop this modular approach across the entire Asset and Service Management process. For each of the process elements, PEL have some generic process details, data requirements and a typical view of how the processes are supported by Maximo. The client specific requirements can then be built quickly and efficiently on this framework.

Linking Activity to Contribution

Increasingly, businesses are being driven to become more efficient and effective at what they do. The implementation of Enterprise Asset and Service Management solutions are seen as a means by which businesses can acheive this, however beyond including a few words and cost savings in the Capex approval document, it is not uncommon for business to lose sight of the broader business objectives as they become burried in application functionality and project plans.

Building on the process driven methodology outlined above, the Peacock Engineering methodology also drives the client to continually revisit the link beween activity and the contribution this makes to the business. In this way, the business is always able to explain "why they do what they do" ... this in turn provides the justification for system configuration, data collection. Understanding the link to contirbution also supports the determination of performance measures for the process elements. This diagram below illustrates the translation of what is important to the business into what the maintenance/service team need to do to support hte goals of the business.