"We Need to Capture Every Equipment Stop in the Plant”
I hear this opening line sometimes.
I work closely with maintenance and reliability teams, and many conversations start with the same goal: track everything. In some cases, teams want to monitor hundreds of assets, sometimes more than 500 pieces of equipment across a single plant.
The intent is good. Better visibility, better decisions.
But very early on, we try to redirect the conversation away from pure downtime tracking and toward production loss accounting. From a business perspective, this shift matters far more than most organizations realize.
Process Reliability vs. Equipment Reliability
In the early stages of improvement, process reliability almost always delivers more value than equipment reliability.
That doesn’t mean equipment failures don’t matter. They absolutely do. Parts, labor, consumables, and contractor costs add up quickly. Minor failures today can easily become major production losses tomorrow if left unresolved.
The challenge is that resources (time, people, and capital) are always limited. We don’t get to fix everything at once.
When that’s the case, the highest return comes from understanding where production was actually lost, not simply where equipment stopped.
Why Production Loss Accounting Changes Mindsets
Production loss accounting answers questions that downtime data alone often cannot:
- How much potential production was actually lost?
- Which events truly constrained plant throughput?
- Where did the greatest economic damage occur?
This perspective forces prioritization based on impact, not activity.
Traditional equipment downtime data, on the other hand, often treats all stops as equal, even when many had no effect on final output. This is especially true in systems with redundancy or standby equipment, where a failure may look serious in a CMMS report but had zero impact on production.
The Question Many Plants Still Can’t Answer
Despite increasingly sophisticated systems, many operations still struggle with a very basic daily question:
“What caused us to lose production today?”
Until that question can be answered clearly and consistently, adding more assets, more tags, and more data rarely moves the needle.
A Practical Sequence That Maximizes Value
When resources are constrained, and they always are, the priority should be clear:
- Identify the events that caused the greatest production loss
- Stabilize and control those constraints
- Then expand into detailed equipment reliability to harden the system
Once this foundation is in place, expanding asset coverage makes sense. At that point, additional data reinforces a system that already delivers value.
This Isn’t Anti-Maintenance or Anti-Data
This approach isn’t about doing less maintenance.
It isn’t about avoiding data.
It’s about sequencing the work to maximize impact.
Reliability that doesn’t translate into throughput, margin, or capacity… is just activity… not results.
