Reactive maintenance is a given thing, as assets will fail sooner or later. It is also a given thing that resolving reactive maintenance is expensive: it is neither planned nor predicted and in most cases involves high urgency. So having the basics in place to ensure a fast and efficient processing of reactive maintenance will definitely save cost and reduce the downtime of your assets. Moreover, it will make the users of those assets more productive and happier.
To establish a well performing reactive maintenance process, good communication with all stakeholders is key and this will ensure accurate, fast and first time execution of work. It starts with defining the stakeholders and determining their connection points and communication workflow.
A basic reactive maintenance process has at least three stakeholders:
- Reporter: the person or department that detects the asset failure and starts the process. This can be any building user or maintenance specialist.
- Classifier: the person or department that takes the call from the reporter, registers the call, validates priority, and passes the call to the right internal specialist or external supplier for resolving the asset failure.
- Executor: the person or supplier that executes the maintenance work and feeds the status back to the classifier.
Different tools and needs
It is important to validate these stakeholders carefully and to equip them with the right instructions, information, tools and systems to ensure a fast and efficient processing. These tools and needs differ per stakeholder.
- How can reporters communicate asset failure as easy and fast as possible? By paper, phone, email, using mobile apps or a self-service webpage, visiting a helpdesk or by any combination of these?
- What information is important for detecting a failure? For example, reporter name, location of failure, applicable asset, actual impact, priority.
- How can reporters track the status and progress of their call? By phone, email, self-service, in an automated process?
- How can classifiers register a reported call as easy as possible, validate the input from the reporter, and check on duplicate calls?
- How can classifiers analyse the impact of a call and determine the handling priority and the internal trades or external supplier needed for execution?
- How can classifiers inform internal or external suppliers about a maintenance job and how can they monitor the progress of execution?
- How can internal and external suppliers easily access their work backlog, see priorities, location details, asset to maintain and access information needed for fast execution?
- How can internal and external suppliers comply with health and safety regulations, register spent time and materials and easily close jobs?
- How are job status updates communicated to the classifiers and how is information about spent time, cost and materials shared and processed?
It is obvious that a fast and efficient processing of reactive maintenance is only possible when the asset and contract repository are in place and combined with extensive process automation for all stakeholders in one integrated workflow.