No maintenance strategy?
Not having a maintenance strategy is the simplest “strategy” to have for asset maintenance. The absence of a strategy eliminates the need to plan ahead for maintenance.
Unplanned, reactive maintenance is the most likely type of maintenance that will occur. Despite the fact that no strategy exists, most types of maintenance tasks are still possible. For example:
- Unplanned, reactive maintenance will occur any time the asset breaks down.
- Preventative maintenance may occur when the operator (or someone else) decides to do it. This may include lubrication or cleaning. However, this maintenance is unstructured and does not occur according to a formalized schedule or due to a trigger.
- Predictive monitoring may also occur. For example, a bathroom sink may be subject to condition monitoring every time it is used. The user may notice a decrease in flow rate, and initiate preventive repairs for the sink.
A “no maintenance strategy” may be suitable for homes and home workshops. Owned equipment may never have had any planning for maintenance strategy. When the equipment is non-critical and does not pose any safety risk, this strategy may be ideal.
A “no maintenance strategy” approach is unsuitable in most other situations. The risk of equipment unavailability, or safety issues should prompt some level of thought about a maintenance strategy.
Triggers used for “no maintenance strategy” maintenance
Many triggers can be used for this type of “no maintenance strategy” maintenance. These, however, are all characterized by an unstructured and unplanned approach.
Breakdown is the most likely trigger for maintenance. If the asset is required and not working, then maintenance will be required.
Time may also be used as a trigger. “I haven’t lubricated the machine for a long time” could be a trigger for maintenance.
An event could be used. A news report of a fire being caused by a similar asset may trigger a maintenance inspection.
A usage trigger may initiate work. A counter ticking over to a significant milestone (say 100 hours) may initiate maintenance by the user if they want to. Importantly, this would not be pre-planned.
Condition may also be used. The example of the bathroom sink beginning to run slowly is an example of this trigger.