Lesson 5 of 20 · Chapter 5
Early Equipment Management and Design for Maintainability
Some machines fight you every day, however hard people work. The fight is usually not about effort or discipline: it was designed in, long before anyone pressed start. Early Equipment Management is the TPM pillar that stops a plant buying the same problems again. This lesson shows how the people who live with machines feed their experience into the design of the next one, how to test a design before it is built, and how to run a new line up to speed without inheriting ten years of workarounds.
Choose how you want to learn
You can change this any time. Every level does the same hands-on steps. Press Listen on any part to hear it read aloud.
- 1 · The machine that fights
- 2 · Four kinds of feedback
- 3 · Test it before it exists
- 4 · Ramp-up
- 5 · The New Line Bench
- 6 · Try it at work
- 7 · Your card
- 8 · Check yourself
Part 1
The machine that fights you was designed that way
You can clean, check and plan perfectly and still hear: “We keep doing the right things, but this machine fights us.”
Often the fight comes from design decisions: a filter behind three guards, an oil level you need a ladder and a torch to see, a part that only one person knows how to adjust.
Early Equipment Management fixes this at the start, by bringing the people who run and maintain machines into the design and buying of the next one. The earlier the question is asked, the cheaper the fix.
In the old wall model, equipment is designed or bought, installed on a project timeline, and handed to production with a short training session and a binder of manuals. The next line is then bought with the same blind spots, and the plant inherits another decade of avoidable loss.
Modern TPM treats maintenance feedback as a formal input to design and procurement. Operators, technicians and quality people take part in design reviews and in the factory and site acceptance tests, with checklists rooted in the six big losses.
“It is coming from design decisions that were baked into the equipment long before the first operator ever pressed start.”
“Modern TPM treats feedback as a formal input to design and procurement.”
“When they are asked after the line is producing and the schedule is tight, changes become politically and financially expensive, and the plant falls back into coping.”
Read the whole chapter free in the book reader.
When are the people who will live with the machine asked for their view? Move the point and see what happens to each fix.
Part 2
Four kinds of maintenance feedback
“We want a better machine” does not help a designer. Feedback has to be about losses, said plainly: what goes wrong, how often, and why.
The chapter sorts useful feedback into four kinds. Access: can people reach what they need to check and fix? Readability: can they see what normal looks like? Error-proofing and repeatability: can a changeover or restart be done the same way every time? Parts: are the parts that wear out standard and easy to get?
Small repeated phrases like “it’s hard to see” or “we can’t tell if it’s normal” are really design signals.
Each category points to a design response. Poor access is answered with humane access, not heroic training: external grease manifolds where safe, sight glasses people can read without contortion, hinged quick-release guards. Poor readability is answered with reference marks, built-in indicators and condition-monitoring points; the goal is not a fancy machine but a legible one.
Feedback should also include quality language, not only uptime language: if a process is sensitive to alignment, the design should provide alignment features and measurement access, so the machine produces good parts naturally.
“If a team says, “We want a better machine,” the conversation becomes subjective.”
“The design response is not heroic training; it is humane access.”
“Maintenance feedback often shows up as small repeated phrases: “We can’t tell if it’s normal,” “It’s hard to see,” “It drifts and then suddenly trips.” These phrases are design signals.”
Six things people say about a machine. Which kind of feedback is each one?
Part 3
Live with the machine before it exists
A digital twin is a computer model of the machine: its shape, how it moves, its controls and its sensors. With it, a team can “walk up” to the machine before it is built.
You can ask real questions: can I see the oil level without taking a guard off? Can I reach this filter? Moving a sensor or adding a door on the screen costs almost nothing. Doing it after installation costs a lot.
Every awkward spot will be dealt with one way or another: now, on purpose, in the model, or later, on the floor, by people finding a workaround.
Many organisations accidentally buy rituals: equipment that can technically run, followed by months of workarounds (the bracket someone taps, the sensor someone wipes daily, the first pallet someone holds). A virtual maintainability and restart review lets the team design legibility and repeatable starts in instead.
Connected to data from existing machines, the model can test warm-up sequences and interlocks before the real one arrives, and it becomes the baseline when it does. It also feeds the other pillars: exact inspection points and safe access for Autonomous Maintenance, and job plans with tolerances for Planned Maintenance before the first failure.
“Too many organizations inadvertently purchase rituals.”
“You can place a virtual operator at the machine and ask practical questions: Can I see the oil level in the sight glass without removing guarding?”
“That decision will happen either now, virtually and deliberately, or later, physically and informally.”
A virtual walkaround of a new filler. Decide what to do about each problem the model shows.
Part 4
Ramp-up is a capability milestone, not a volume race
When a new line starts up, everyone watches how much it makes. But output can rise just because people are pushing harder.
The real test is stability: fewer stops in the first hour, fewer adjustments, less time to the first good part. A line is ready when it can restart and return to normal without improvising.
So keep a startup loss register: write down every startup problem and deal with it. If you do not, the problem just becomes “how this line is.”
A defined warm-up (duration, conditions, verification points) is not a startup loss; an undefined one is. A return-to-baseline checklist should be used after every adjustment, short stop, changeover and maintenance job, and who does which check, operator or maintenance, must be designed rather than negotiated in the moment.
Ramp-up also exposes maintenance-induced variation (alignment, torque, lubrication done inconsistently) and missing basics like shadow boards and kitted change parts. A line in ramp-up cannot afford scavenger hunts; close the gaps immediately.
“It is a capability milestone: the process can produce at target rate, with target quality, reliably enough that schedules become credible and people stop living in recovery mode.”
“If it does not, the loss becomes “the personality of the line.””
“A defined warm-up is not a startup loss; an undefined warm-up is.”
Two new lines, eight weeks of ramp-up. Judge them first by output, then by stability. The numbers are an illustration.
Part 5
Turn early pain into permanent capability
Every problem on a new line is a chance. Restore it so the line runs. Stabilise it with a written standard so it does not come back. And improve the design so the reason it drifted is gone: move the sensor, add the shield, change the part.
Then write the lesson into the standards for the next machine you buy. That is how early pain turns into capability.
Restoring alone lets the line run, and the same startup problems return for years. Restoring and stabilising controls the symptom, but the design reason for the drift is still there. Only when the lessons from the line become design standards, checklists and acceptance criteria for future equipment does the plant stop inheriting the same losses.
The bench below walks one new line from design review to ramp-up. Every choice on it comes from the chapter; try getting all of them right but one.
“It is a phase to design, measure, and shorten, until the new asset behaves like what TPM has been aiming for all along: a system that returns to baseline predictably and produces good parts at rate without drama.”
The New Line Bench. One new asset, from design review to ramp-up.
Part 6
Try it where you work
Do these on a real machine: at work if you work with equipment, or at home on a car, washing machine, furnace or lawn mower if you do not. Tick each one when it is done. Safety first: look and clean only what you are allowed to touch, never reach into moving equipment, and follow your site’s lockout rules.
Part 7
Your “My Design Feedback” card
Turn one daily workaround into feedback a designer or buyer can act on. Nothing you type here leaves this device.
My Design Feedback
Global Sovereign University · Modern TPM, lesson 5
Four kinds of feedback
- Access: can people reach it?
- Readability: can they see normal?
- Error-proofing and repeatability: same start every time?
- Parts: standard and easy to get?
Ask early, when change is cheap. Judge ramp-up by stability, not volume. Keep a startup loss register.
Part 8
Check yourself
Six real situations. Pick what you would do. You will see why after each one.
Lesson 5 complete.
You can now turn daily workarounds into design feedback, sort it into the four kinds, test a design before it exists, and judge a new line by stability instead of volume. Next: Lesson 6, training, education and employee empowerment.
Modern Total Productive Maintenance (TPM) by Dr. Gene A Constant. This lesson comes from chapter five. Read the whole book free in the reader, or keep a copy.
Buy a copy — it funds a free seat
GSU is a 501(c)(3) nonprofit and book sales are its only income. A purchase is not a tax-deductible donation. This lesson is free and always will be.