Planned maintenance: criticality to verified return

Planned maintenance: criticality to verified return

Use asset function, failure history and deterioration evidence to decide what maintenance is needed. Distinguish tasks justified by time or condition from reactive work and repeated breakdown fixes. Plan the people, parts and access window before the task, then execute under the approved technical controls. Operations and maintenance should agree how correct function and readiness will be verified before return. Review whether the plan prevents important failures or simply creates more activity. Consistent failure and restoration definitions are needed before interpreting reliability measures. Operator observations provide useful evidence but do not replace specialist diagnosis or engineering acceptance criteria.

Follow the method

1. Review failure evidence
2. Plan justified work
3. Execute authorized work
4. Verify return
5. Review effectiveness

Challenge the plan before adding maintenance activity

Fictional packaging line: transfer unit M8 stops intermittently. A scheduled external clean/check was marked complete on day 1; similar interruptions were recorded on days 3 and 6. Planner Kira is asked to double the task frequency immediately. The failure mechanism and execution detail are not yet established.

Follow the method

1. Same failure?
2. Task appropriate?
3. Task executed?
4. Plan change?
5. Effective?

Completed maintenance, recurring loss

Use repeat-failure and task evidence to challenge a maintenance plan, define authorized work and verify both return to service and later effectiveness.

Fictional packaging line: transfer unit M8 stops intermittently. A scheduled external clean/check was marked complete on day 1; similar interruptions were recorded on days 3 and 6. Planner Kira is asked to double the task frequency immediately. The failure mechanism and execution detail are not yet established.

Role: Maintenance planner with the qualified technician, operator and asset owner.

Normal condition

A maintenance task has a justified purpose, required competence/resources and evidence that the required function was restored.

The gap

Task completion is recorded, but recurrence continues and the task’s relationship to the failure is unclear.

• This lesson plans evidence and responsibilities, not technical disassembly, adjustment or isolation steps.
• Calendar frequency and condition thresholds require asset-specific technical authority; none is prescribed by this exercise.

1. Connect failure to required function

   Kira records what M8 failed to do, under which operating conditions and how the interruption was identified. She compares event descriptions before assuming they share a cause.

   Why: Similar downtime labels may conceal different mechanisms.

   Evidence: A common failure definition and event identities are established.

2. Inspect the existing task’s purpose

   The technician explains which condition the clean/check is intended to detect or prevent and what execution evidence should exist. The team retrieves the actual task record rather than trusting the tick.

   Why: A completed activity can be unsuitable, incompletely executed or unrelated to the recurring failure.

   Evidence: The plan review distinguishes task suitability from execution uncertainty.

3. Prepare justified work

   The planner assigns technical investigation, appropriate access window, competence, parts/information and the return-verification requirement. Any task or interval change follows the responsible technical review.

   Why: Planning makes authorized work executable; adding frequency without a mechanism can add cost and disruption without preventing loss.

   Evidence: The work package names purpose, owner, prerequisites and acceptance evidence.

4. Verify return and review recurrence

   After authorized work, the asset owner accepts required function using the approved verification. The team then observes representative operating exposure and records recurrence separately from immediate return.

   Why: Passing a restart check is not evidence that the maintenance plan will prevent the failure over time.

   Evidence: Return-to-service record and later effectiveness review are distinct, linked records.

The record was complete but the task targeted another condition

Further fictional review confirms that the scheduled task was executed correctly, but its documented purpose does not address the interruption mechanism now supported by technical evidence.

Retain the completed-task record and revise the maintenance strategy through the technical owner. Do not label the technician noncompliant or simply repeat the irrelevant task faster.

Execution quality and task suitability are different explanations with different responses.

Link the supported failure mechanism to the proposed task and define how effectiveness will be reviewed.

Run a practice session

Materials

• M8 event and task cards
• Blank plan-review/work package
• Separate immediate and later verification headings

1. Clarify required function · 5 minutes

   Are these events actually the same failure?

2. Review task evidence · 7 minutes

   Does the tick prove suitability or execution?

3. Practice Q5 plan review · 9 minutes

   What evidence would justify changing the interval?

4. Debrief effectiveness · 5 minutes

   What can a restart test not establish?

Debrief

• If learners choose a repair, ask which supplied evidence justifies it.
• If they only request more data, require a named question, owner and record.

Write three competing explanations for recurrence and the evidence needed to distinguish them.

Transfer into the work

Owner: Maintenance technical owner and planner with the asset owner

Record: Failure history, task review, authorized work package and effectiveness record

Review: Before plan changes, at return acceptance and after representative exposure

Evidence: Failure mechanism, execution detail, restored function and recurrence behavior

Continue technical investigation and adjust the approved maintenance strategy; retain honest unresolved status.