Total productive maintenance: equipment condition as a production responsibility

The bargain underneath the pillars

The arrangement most plants inherit is clean and unproductive: production runs machines until they stop, maintenance repairs them, and each side blames the other. Equipment ownership dissolves in the gap. What this philosophy proposes is that the operator holds daily condition, within an agreed boundary, and reports deterioration early, while the specialists move up towards diagnosis, restoration and design-out work. Neither group usually wants this at first. Production sees added tasks in an already full shift; maintenance sees its purpose handed to amateurs. Naming both objections at the outset works better than presenting the change as self-evidently beneficial.

What the maintainer is being asked to give up

A skilled maintainer's standing often rests on being the only person who can coax a particular machine back into life. Asking them to teach that away, to write down what they know, and to spend their hours on repeat causes rather than heroic recoveries is a genuine loss of identity, and it is rarely acknowledged out loud. The compensating offer has to be real: better diagnostic tools, protected time to investigate recurring failures, a voice in specifying new equipment, and recognition that shifts from response speed towards failures prevented. Where that offer is missing, the training happens on paper and the knowledge stays put.

What the operator is actually taking on

Daily condition work is not free. It consumes shift minutes, it needs competence that has to be built and tested, and it obliges the operator to raise problems that will sometimes be inconvenient for their own output figures. If the plant simultaneously holds that operator to a volume target assuming none of this, the tasks get signed off without being performed, which is worse than never asking. The honest version allocates the time explicitly, defines exactly which tasks fall within the operator's authority, and treats a completed check sheet for work nobody did as a serious failure rather than a paperwork lapse.

Pillars are a menu, not an implementation plan

The published pillar structures are useful as a checklist of what eventually needs attention and dangerous as a launch plan, because a site that starts all of them together produces a steering group, a training matrix, several audits and no change in equipment condition. Sequencing beats coverage: restore basic condition on a small set of machines, prove the operator routines hold there, then extend. The pillars covering design and early equipment management pay off later and need a maintenance function with the capacity to think, which does not exist while that function is still firefighting daily.

Telling real progress from a well-documented programme

Programme artefacts, such as matrices, audit scores and certificates on the wall, are easy to produce and prove very little. Better evidence is behavioural: who notices a leak first, whether shift handover mentions equipment condition unprompted, whether the tag queue is shrinking or growing, and whether breakdowns are still surprises. Ask a maintainer whether they are called earlier than they used to be. Ask an operator to point out something on their machine that is not right; where this has taken hold they will find several without hesitating, and will know what has been done about each.

Frequently asked questions

Is this just preventive maintenance under a different name?

No, although the two overlap heavily. Scheduling and executing planned maintenance is a technical activity a maintenance department can run on its own. What this philosophy adds is the redistribution of responsibility: operators holding daily condition, specialists moving towards diagnosis and design-out, and equipment losses treated as a production problem with a production owner. A site can have a mature planned schedule and none of that ownership, which is precisely the situation the approach was invented to address.

Where does the time for operator condition work come from?

It has to be taken from planned output, explicitly, and then defended. Attempts to fit it into gaps fail because gaps belong to whoever needs them most that shift. Common arrangements include a fixed window at the start or end of shift, a longer block on a lighter day, or absorbing the work during changeovers. Whichever is chosen, the planning assumptions must be adjusted to match, or the first busy week will remove it permanently.

Can this work where maintenance is contracted out?

Partly, and the contract has to be written for it. An agreement paid for response and repair rewards failures; one that expects the contractor to train operators, attend condition reviews and pursue repeat causes rewards prevention instead. The daily operator routines are unaffected by who employs the maintainer. The difficulty is knowledge transfer and design-out work, which contractors have little incentive to perform unless the agreement requires it and somebody checks that it happened.