19.07.2013 Views

August 2005 - Library

August 2005 - Library

August 2005 - Library

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

24<br />

To achieve success in managing maintenance as a business requires the identification, development and implementation of core<br />

business processes that are fundamental to maintenance management in a cost effective manner. The concept of Business Centre d<br />

Maintenance has evolved to provide the framework for developing these core business processes in a comprehensive business<br />

focussed approach to maintenance management. In such a framework, the maintenance team needs to focus on the four<br />

fundamental principles of Business Centred Maintenance - those being:<br />

1. The Principle of Strategy<br />

2. The Principle of Resource Management<br />

3. The Principle of Information Management<br />

4. The Principle of Value-adding<br />

Although the development of a Business Centred Maintenance framework in a traditional management environment is possible, the<br />

successful implementation and management of it re q u i res a team with ‘business nous (understanding)’. And this is where an<br />

organisation faces a significant change process in order to move from the traditional reactive culture to the more proactive culture<br />

as this culture requires ‘business nous’. Without this shift or change in thinking to develop the necessary business nous within the<br />

maintenance team, maintenance will continue to stay in the traditional reactive environment.<br />

CHANGING THE MAINTENANCE TEAM ENVIRONMENT - AN OVERVIEW OF THE<br />

PROCESS<br />

In a manufacturing industry context, change is typically imposed on a team or an individual by an external force, whether it be a<br />

person who is external to the team or external to the organisation. In either situation, the maintenance team is forced to change<br />

without due consideration to the impact that this change will have on the individual or team itself.<br />

And it is due to this lack of consideration that organisations generally fail in changing the way the maintenance team operates, as<br />

the team is likely to see no need for change as “we have been doing it this way for years, so why change now”. Without this need<br />

being communicated to the team prior to implementing the change, there is no desire or urgency to change the normal way of<br />

delivering maintenance. So how does an organisation commence the change process and create this sense of urgency?<br />

Building Change<br />

Capability<br />

Appreciating<br />

Change<br />

Executing<br />

Change<br />

Mobilising<br />

Change<br />

Figure 2 - Change Management Cycle<br />

The first step in any maintenance improvement process, which will bring<br />

about change in the maintenance team, should be the clear appreciation that<br />

change is actually re q u i red. Once the need for change has been<br />

a p p reciated, the development and implementation of a successful change<br />

process that is specific to the organisation, can only occur with the buy-in<br />

and support from the majority of the maintenance team. In order to obtain<br />

this buy-in, the support of the maintenance team needs to be mobilised so<br />

that they believe in the need for change otherwise change success, if<br />

achieved, will only be temporary (refer to Figure 2).<br />

Once this team is mobilised with the support of senior management,<br />

the development and implementation of new business processes and systems for maintenance delivery that define the ‘new way<br />

of doing maintenance’ has to occur. Such processes and systems will require significant learning by the team members. Where<br />

gaps in the capability of the team exist and cannot be filled by existing team members, new members may have to be re c ru i t e d<br />

either internally or externally. Once this has occurred and the team roles and functions are clearly defined and resourced, support<br />

mechanisms (e.g. Computerised Maintenance Management Systems) needs to be available for all team members to assist them in<br />

completing their day-to-day activities in a cost effective and value adding manner. By putting the right re s o u rces and support<br />

mechanisms in place at an early stage, the change management process would have built and put in place the change capabilities<br />

needed to allow for sustainable improvements in a cost effective manner.<br />

APPRECIATING AND DETERMINING THE NEED FOR CHANGE<br />

Appreciating the need for change in a maintenance organisation involves determining:<br />

1. Whether a need for change exists.<br />

2. Whether the change needs to occur immediately or at some later date.<br />

3. What improvements / benefits this change brings to the organisation.<br />

4. How the change impacts people within the organisation.<br />

To determine the above four factors, a detailed review process of the status quo situation needs to occur in the form of a Maintenance<br />

E ffectiveness Review. A Maintenance Effectiveness Review consists of three separate gap analysis surveys used to determine the<br />

effectiveness of current maintenance management practices as it relates to best practice. This Review would be seen as the first<br />

step of the overall improvement / change process. For the status quo review to be a true indication of the current situation, the<br />

surveys need to focus on the following aspects of maintenance:<br />

1. Maintenance Management - developing an understanding of Maintenance Management in:<br />

• Resource Management<br />

• Information Management<br />

• Maintenance Support<br />

• Maintenance Planning and Scheduling<br />

• Preventative Maintenance Management<br />

2. Productions Perception of Maintenance Effectiveness<br />

• How maintenance effectiveness is perceived by the “customer”.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!