Asset criticality: interruption, alternatives, and uncertainty
5 min read
Lesson objectives
- Rank assets from consequence, likelihood, and fallback data; show how one changed fact alters priority; separate escalation from repair authority.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
An expensive asset can be low in criticality if its loss produces little service disruption; a small pump can be decisive when it is the only one serving an occupied area. Criticality is not a permanent attribute of a device name. It is a judgment about the consequence of losing its function in a stated service context, the possibility of failure over a defined decision horizon, and the practical ability to continue with an alternative. Start with the asset's function: what does it enable, for whom, and when? Trace its dependencies to see whether loss stops a whole service or a limited part. Instead of merely asking whether a machine is important, ask what its absence would cause now and for a specified period. An air unit serving an empty hall today has a different service consequence during a crowded event, although its location and purchase price are unchanged.
For this exercise we use an explicit internal matrix, not an international mandatory scoring standard. Consequence is 1 when service continues with modest inconvenience, 2 when service is degraded and action is needed during the day, and 3 when a core purpose is interrupted or a safety exposure appears. Likelihood is 1 for rare failure supported by a trustworthy record, 2 for plausible failure, and 3 for recurrent failures or clear warning indicators. Their product begins a discussion; multiplying ordinal labels does not measure a true financial cost. Record the time horizon and the evidence behind the likelihood. Do not score missing knowledge as 1. With no failure history, write ‘uncertain’ and request verification or an early review. Next test fallback: does it exist, was it tested, and how long does service transfer take? An untested standby machine is not assured continuity.
Criticality informs maintenance planning, spare parts, and response arrangements. It does not authorize the specialist to repair equipment immediately. A high-consequence asset may justify earlier specialist inspection, a parts check, and prepared communications. It never removes work-permit or safety requirements. Identify the decision owner where shutdown or expenditure needs higher approval. If the register conflicts with the site, keep the ranking provisional and link the data exception. An exact-looking score derived from a duplicate asset or a nonexistent fallback misleads. A different order may be defensible if consequence, likelihood, and fallback definitions are clear and applied consistently before seeing the desired result.
Review criticality when service, users, fallback capability, or failure evidence changes; there is little value in recalculating it each morning without new information. Preserve the assumptions that supported a prior ranking so the team can understand why it was reasonable at the time. When a counterexample emerges, identify the changed driver first: consequence, likelihood, or fallback reliability. Then reorder work and resources. Asset criticality alone cannot set every incident's priority. An immediate slip exposure involving a low-cost item may outrank preventive work on a high-criticality asset. The asset register supplies identity, location, function, and history; the service card supplies the effect of the current incident. Professional judgment combines both, then checks the result against observed conditions and delegated authority.
Lesson summary
Rank assets from consequence, likelihood, and fallback data; show how one changed fact alters priority; separate escalation from repair authority.