← Thinking
Series
The operating model
A ten-part argument that moves from what an asset is — through work, lifecycle, production, budgets and shutdowns — to a connected operating model and the evidence behind it.
10 parts
- 01The asset register is not the asset systemAn asset register records identity and hierarchy. An asset system should also represent operating state — usage, condition, life forecasts, maintenance demand and the economics of keeping the asset.
- 02The work order is not the maintenance systemThe work order is one transaction inside a larger model of evidence, assessment, decision, execution, condition, history and future maintenance demand.
- 03One work model may not fit every assetCommon asset, work, people and cost structures are worth sharing — but roads, structures, fixed plant and shutdowns identify, schedule and forecast work differently enough that one universal work-order workflow rarely fits them all.
- 04Production consumes asset lifeMaintenance forecasting becomes more useful when production demand, utilisation and component life are treated as parts of the same model.
- 05Maintenance budgets should describe the future, not just the pastHistorical expenditure is a useful baseline, but maintenance demand comes from what assets are expected to do next — so a budget should also carry a forward view of commitments, forecast work, resource limits and expected outturn.
- 06Should operations have a ledger?Finance preserves movements and derives a position from them. Operations accumulates hours, cost, commitments, life consumption and risk across scattered systems — a ledger-like layer could record those movements and explain where an asset, shutdown or site stands and why.
- 07A shutdown is an operating eventA major shutdown is not just a large maintenance job — it is a temporary operating state where production, maintenance, contractors, procurement, isolation and commissioning converge on a constrained window, and it deserves to be modelled as a first-class operating event.
- 08Resource planning starts before the work orderMuch of tomorrow's maintenance demand is already visible in today's condition, production plan and lifecycle forecast — so labour, skills, parts, contractors and workshop capacity can be forecast and constraint-tested long before the work order exists.
- 09Health is a position, not a traffic lightA single health score hides more than it shows. Treating asset or entity health as a multidimensional, time-phased operational position — condition, lifecycle, cost, production exposure, resource readiness, risk — keeps the traffic light connected to evidence and decisions.
- 10From maintenance records to operating evidenceReliable records are essential, but maintenance data earns its value when history becomes evidence — inputs to a continuously evolving, explainable understanding of where each entity stands and what will happen next.