Key takeaways
Short answer: Criticality and priority are two ranking concepts in maintenance that are often blurred, but one describes an asset and the other a job. Criticality is how important an asset is to the operation — how badly its failure would hurt production, safety, or cost. Priority is how urgently a specific work order should be done compared with other jobs. Criticality is a fixed property of the asset; priority is a property of the task, set when the work is triaged. Criticality strongly informs priority, but they are distinct. For where jobs get triaged, see work order vs work request.
Criticality is a measure of how important an asset is to the operation — essentially, how much it would hurt if that asset failed. It is assessed by consequence: an asset whose failure would stop production, endanger safety, breach compliance, or cost a great deal is highly critical; one whose failure is easily absorbed (a redundant unit, a non-essential machine) is low-criticality. Criticality is a relatively stable property of the asset itself, derived from its role in the operation, not from any particular moment or job. It is usually established through a criticality analysis that ranks assets by failure consequence, and it underpins a great deal of maintenance strategy — which assets deserve the most attention, the best monitoring, the largest spares holding. Criticality answers a strategic question: which assets matter most?
Priority is a measure of how urgently a specific work order should be done relative to the other work competing for maintenance resources. It is assigned to a job, usually when a work request is triaged into a work order, and it determines the order in which work gets scheduled and done. Priority is dynamic and job-specific: the same asset can generate a high-priority job (an urgent failure stopping the line now) and a low-priority one (a minor cosmetic issue that can wait), and priority shifts with circumstances. Priority answers a tactical, scheduling question: of all the work waiting, what should we do first? It is about urgency and sequencing of tasks, not the inherent importance of assets — though, as we will see, the two are connected.
The clean distinction: criticality is a property of the asset (how important it is), priority is a property of the job (how urgent it is). They answer different questions — criticality asks which assets matter most strategically, priority asks which jobs to do first tactically. They also behave differently: criticality is relatively fixed (it changes only if the asset's role changes), while priority is dynamic (it depends on the specific situation and shifts as circumstances change). Confusing them muddles maintenance decisions — treating a job's urgency as if it were the asset's importance, or the reverse, leads to mis-prioritized work. A critical asset does not make every job on it urgent, and an urgent job can arise on a non-critical asset. The two are related but distinct dimensions.
Two assets, two jobs. Asset A is a critical production machine whose failure stops the whole line; Asset B is a redundant backup pump whose failure no one would notice immediately. Now the jobs. On critical Asset A, a routine lubrication task is due — important asset, but the job itself is not urgent, so it is a high-criticality asset with a modest-priority job. On non-critical Asset B, a seal has just failed and is leaking — low-criticality asset, but the job has some urgency. Meanwhile, if critical Asset A actually fails and stops the line, that job is both high-criticality and top-priority. The point: criticality (the asset's importance) and priority (the job's urgency) are separate axes. A smart triage reads both — a job on a critical asset usually deserves elevated priority, but the asset's criticality and the job's urgency are still two different things being combined.
Though distinct, the two are designed to work together: criticality is one of the main inputs to setting priority. When a work order is triaged, a good prioritization scheme combines the urgency of the specific job with the criticality of the asset it is on — a job on a highly critical asset is generally bumped up, because the consequence of leaving it undone is greater. This is how the strategic and tactical layers connect: criticality analysis establishes, in advance, which assets matter most, and that ranking then feeds into the moment-to-moment priority decisions, ensuring that work on the assets most important to the operation tends to get done first. Without criticality feeding priority, triage becomes purely reactive — whatever shouts loudest gets done — rather than weighted toward the assets whose failure would hurt most. Criticality gives priority its strategic backbone.
Criticality and priority together direct maintenance effort toward what most protects the availability factor of OEE. Criticality identifies the assets whose failure would most damage availability — exactly where reliability effort should concentrate, the logic behind reliability-centered maintenance. Priority then ensures the most urgent jobs on those assets get done first, so the work that prevents the biggest availability losses happens promptly. Used together, they focus a maintenance team's limited time on the assets and jobs that most shift downtime from unplanned to planned and shrink the six big losses. Maintenance that ignores criticality and priority spreads effort evenly and protects OEE less than maintenance that concentrates it where failure hurts most.
Fabrico provides the OEE and downtime data that makes both criticality and priority evidence-based. Its loss breakdown reveals which assets actually cause the most lost OEE — grounding criticality assessment in real consequence rather than assumption — and tying work orders to that data helps ensure the most urgent jobs on the most critical assets rise to the top of the queue. It turns criticality and priority from static judgments into a data-driven focus on the work that most protects availability. Book a demo to focus maintenance where it most protects OEE.
Criticality is how important an asset is to the operation — the consequence if it fails. Priority is how urgently a specific work order should be done relative to others. Criticality is a property of the asset; priority is a property of the job. Criticality informs priority but is not the same.
No. Criticality describes an asset's importance and is relatively fixed; priority describes a job's urgency and is dynamic. The same critical asset can have both urgent and non-urgent jobs, and an urgent job can arise on a non-critical asset. They are distinct dimensions.
Through a criticality analysis that ranks assets by the consequence of their failure — impact on production, safety, compliance, and cost. An asset whose failure stops the line or endangers safety is highly critical; a redundant or non-essential asset is low-criticality.
Criticality is a key input to setting priority. A good triage combines the urgency of the specific job with the criticality of the asset, so jobs on highly critical assets are generally elevated. This gives priority decisions a strategic backbone rather than being purely reactive.
Together they focus maintenance on what most protects availability. Criticality identifies the assets whose failure would most damage OEE, and priority ensures the most urgent jobs on them get done first, shifting downtime from unplanned to planned where it matters most.
Вход
Блог
