{"id":49812,"date":"2026-09-08T15:56:00","date_gmt":"2026-09-08T20:56:00","guid":{"rendered":"https:\/\/assetmanagementprofessionals.org\/?p=49812"},"modified":"2026-09-08T17:08:59","modified_gmt":"2026-09-08T22:08:59","slug":"why-uptime-elements-criticality-analysis-is-a-leadership-instrument-not-a-spreadsheet","status":"publish","type":"post","link":"https:\/\/assetmanagementprofessionals.org\/es\/news-articles\/why-uptime-elements-criticality-analysis-is-a-leadership-instrument-not-a-spreadsheet\/","title":{"rendered":"Why Uptime\u00ae Elements Criticality Analysis Is a Leadership Instrument, Not a Spreadsheet"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
By Terrence O'Hanlon, Creator, Uptime\u00ae Elements | For the Association of Asset Management Professionals<\/h6>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

You passed the exam. You know what the Ca tile stands for, you can recite the risk formula, and you have probably seen a criticality ranking or two in your career. So this article is not going to explain criticality analysis to you.<\/p>

It is going to ask a harder question: why do so many criticality rankings, built by people who know exactly what they are doing, end up as tabs in a spreadsheet that nobody opens?<\/strong><\/p>

I have watched it happen at world-class sites. The analysis was technically sound. The scoring was defensible. And within a quarter, the plant was scheduling work the way it always had \u2014 by squeaky wheel, by seniority, by whoever caught the maintenance manager in the hallway. The ranking existed. It just did not govern anything.<\/p>

The difference between a ranking that governs and a ranking that gathers dust is not the math. It is everything the Uptime\u00ae Elements framework wraps around the math. That is the case for doing criticality analysis the Uptime Elements way, and as a Certified Reliability Leader, you are the person positioned to make it.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The ranking is a decision, not a document\n\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A generic criticality analysis produces a document. An Uptime Elements criticality analysis produces an agreement.<\/p>

The REM Passport’s first instruction is not about scoring. It is about the room: operations, engineering, maintenance, quality, materials, and EH&S, together, agreeing on the criteria, the weights, and the scores. Agreement replaces individual perceptions. That sentence carries more weight than the formula does, because it changes what the ranking is<\/em>. A list built by the reliability engineer is the reliability engineer’s opinion, and opinions get overruled on Thursday afternoon. A list the plant built about itself is a decision, and decisions have standing.<\/p>

This is where the People and Culture at Work domain stops being an adjacent tile and starts being the mechanism. The framework’s research is blunt: sixty-nine percent of implementation failures trace to people and culture \u2014 awareness and trust, leadership, competency, empowerment \u2014 not to technical deficiency. A criticality ranking that dies in a quarter did not fail technically. It failed culturally, because nobody outside the department that built it ever trusted it. The cross-functional requirement is not procedural decoration. It is the framework pre-solving the sixty-nine percent problem before the first asset is scored.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"