Define the sensitivity of an asset and its criticality

Rank assets by consequence of failure, and tune how much monitoring noise each one generates.

Criticality tells Handhaaf how much a failure hurts — safety, production, cost — so priority, monitoring coverage and escalation all follow the ranking. Sensitivity controls how readily an asset surfaces warnings.

• Set asset criticality

• Fill in the following fields
• Criticality — the consequence band. A-critical assets get the tightest thresholds, first-priority work and spare coverage.
• Description — what this band means on your site, so everyone applies it consistently.
• Assets — the assets that belong to this category. You can assign in bulk by site or asset group.

When creating or editing a criticality category, scroll to the sensitivity slider. It controls how readily assets in that band generate warnings and recommendations.

• Set insight sensitivity
• Lower sensitivity — fewer, higher-confidence insights for that asset group.
• Higher sensitivity — earlier detection, at the cost of more noise.

Sensitivity should reflect how critical the asset is to operations and how quickly the team needs to be notified of changes in performance.