Implementation Methodology - Services Capability

Maintenance Strategy

A well structured Maintenance Strategy provides the framework and operating principles for the delivery of the maintenance function. In many cases, the maintenance strategy is the translation of legislative and company policy into practical guidelines and an approach that the maintenance team can implement. Without a formal maintenance strategy, the justification for maintenance is often poorly understood and consequently support for it is reduced.

Peacock Engineering have developed a proven Maintenance Strategy framework, and have Consultants with the maintenance background and experience to support organisations in the development of their own.

Business Process Definition

From the formalisation of the maintenance strategy, comes the development of a Business Process model. Peacock Engineering have established a generic maintenance process model that can be used as a starting point with clients to develop a speciofic process framework for their business. The definition of discrete business processes that combine to support the end-to-end delivery of maintenance is an essential pre-cursor to any systems implementation as it often explains and support "why you do what you do" ... creating the justification for system and data support to deliver the proces effectively.

Peacock Engineering have experienced consultants with many years experience of running business process development workshops and producing process documentation. Depending on the requirements of the client, this can vary from high-level process definition right through to detailed procedures and responsiblitry flow-charting.

KPI and Reporting Requirements Development

With the business process elements defined, it is then possible to establish process performance metrics and other reporting requirements needed to operate the processes effectively and to measure the contribution that they are making to the overall process.

Operational Implementation Planning

With any systems implementation, the success is invariably in the ability of the business to accomodate and embrace the change rather than in the inherent capability of the software. The operational planning has to be owned by teh business team, however Peacock Engineering have many years experience of complex system implementations and can support clients in the development of a robust change management plan.

Components of that plan would typically include:

• the review and updating of standard operating procedures
• development of more details processes and any non-system supported process elements
• preparation of a training plan in readiness for the introduction of new systems and processes

Functional Requirements Specification

With the business processes defined it is possible to use these as a framework for defining how the system will support those processes. This is typically captured in a Functional Requirements Specification. For this step in the implementation, the Peacock Engineering team bring together their broad understanding of Asset and Service Management with their deep understanding of the Tivoli Maximo application suite and any associated system components. By using the process definition as the basis for functional requirements specification it is possbile to link requirements back to tangible process and business requirements and in doing so justify (or not) the need for any system configuration and development.

Data Requirements Specification

As with the system functional requirements, Peacock Engineering would advocate the business process framework be used to support the data requirements defininition.