You’ve got 400 assets and a four-person crew. The PM schedule treats them all about the same, monthly checks across the board, and it’s quietly drowning the team. The techs spend Tuesday greasing a backup fan that could sit dead for a month before anyone noticed, while the air handler keeping your server room cool gets the same single monthly glance as everything else. Then it fails on a Saturday and catches everyone off guard. It shouldn’t.
This isn’t a problem with your team’s effort. It’s that you’re treating every asset as equally important when they obviously aren’t. Some failures cost you a phone call; others cost you a shutdown. Asset criticality analysis is how you tell those apart and aim your limited hours where failure actually hurts.
Why you can’t PM everything equally
Equal attention sounds fair, but it’s expensive and it isn’t safe. You have a fixed number of labor hours, and spreading them evenly means the critical assets get less than they need while the trivial ones get more than they deserve. The grease you spent on a $200 backup fan is grease you didn’t spend on the compressor that shuts down production when it dies.
Spread your attention evenly and you’ve effectively set no priorities at all. Criticality analysis exists to make the priority explicit and defensible, so when you put the air handler on a tighter schedule and let the storage-room fan run to failure, that’s a decision you can explain rather than an accident of the calendar.
A simple scoring model: consequence times likelihood
You don’t need a consultant or a 50-page framework for this. Criticality is consequence multiplied by likelihood. How bad is it if this asset fails, and how likely is it to fail? Score each on a 1-to-5 scale, multiply, and you get a number from 1 to 25 that ranks your whole fleet.
Consequence asks what happens when this thing fails. Start with safety: does failure put someone at risk? Then production, where the question is whether the line stops or there’s a backup. Then the cost of the repair plus the downtime, and finally whether failure breaches a regulation or a contract. Take the worst dimension. A 5 on safety makes the asset a 5 no matter how the others land.
Likelihood asks how often it fails. Old equipment, hard-running equipment, and anything with a history of breakdowns scores high. New, lightly loaded, well-maintained equipment scores low. Your work-order history is the honest answer here, so pull the failure count from the last two years rather than guessing.
Multiply the two. A score of 20 to 25 is critical, roughly 9 to 19 is important, and below 9 is low priority. The exact cut lines are yours to set. What matters is that you now have a ranked list instead of a flat one.
How criticality drives PM frequency
The ranking isn’t an exercise; it sets your schedule. Critical assets get frequent, thorough PMs, because you want to catch wear long before the failure you’re paying to avoid. Important assets get a moderate schedule. Low-criticality assets get minimal PMs, or you run them to failure on purpose because the replacement costs less than the inspections would.
That last move feels wrong until you do the math. Running a cheap, non-critical asset to failure is often the right financial call, since the labor to inspect it over its life adds up to more than just replacing it when it dies. Criticality analysis gives you permission to stop maintaining the things that don’t earn it, which frees the hours for the things that do. It’s also what keeps deferred maintenance from being random: you defer the bottom of the list deliberately, instead of letting the top of it slip by accident.
How criticality drives spare stocking
The same ranking sorts your storeroom. Critical assets justify holding the spare on the shelf, even an expensive one, because the downtime while you wait on shipping costs more than the cash tied up in the part. For low-criticality assets, order-on-demand is fine and a day or two of waiting doesn’t hurt.
For each spare, ask what waiting would cost if the part failed. When the answer is a shutdown, stock it. When it’s a minor inconvenience, don’t. Your criticality scores answer that question for the whole fleet at once, rather than one panicked purchase order at a time.
A worked example
Take three assets in a small facility.
The server-room air handler would take down the whole IT operation if it failed, so consequence is a 5. It’s eight years old and has tripped twice in two years, so likelihood is a 4. Score: 20. Critical. It gets a monthly thorough PM, and the blower motor lives on the shelf.
The loading-dock door is annoying when it fails and it slows shipping, but it stops nothing critical, so consequence is a 3. It’s heavily used and fails maybe once a year, so likelihood is a 3. Score: 9. Important. It gets a quarterly PM with common spares stocked, though the motor stays order-on-demand.
The break-room exhaust fan just makes the room stuffy when it quits, so consequence is a 1. It’s new and rarely runs, so likelihood is a 1. Score: 1. Low priority, no PM, and you replace it when it dies.
Same facility, same crew, three completely different maintenance strategies, and each one backed by a number you can show anyone who asks.
But what about the gut-feel overrides?
Sometimes the score is wrong and the people on the floor know it. A formula can’t catch every nuance: a hidden single point of failure, a part that’s been discontinued and can’t be reordered, a unit that runs fine right up until it floods the basement. When a technician tells you an asset is more critical than its score, listen. The model is your starting point, not the verdict. Run the numbers, then let experienced judgment adjust the edge cases. A scoring model you override thoughtfully will serve you better than a gut feel with nothing behind it.
Making the ranking live where the work happens
A criticality ranking on a spreadsheet ages fast. The value shows up when the score lives on the asset record itself, so the PM schedule and the spare-parts decision flow from it automatically instead of from memory. TeamWork’s asset management lets you carry a criticality value on each asset and drive PM frequency from it, so the ranking actually shapes the daily schedule rather than sitting in a file someone made once and forgot.
For the broader context on where criticality fits, the asset management guide covers how the score connects to the rest of your maintenance strategy. You can start a 30-day free trial of TeamWork with no credit card and rank your own fleet before you touch the schedule.