Maintenance Strategy

Condition-Based Maintenance

Maintenance triggered when sensor or inspection data shows an asset has crossed a defined condition threshold, rather than acting on a fixed calendar.

A — Hard / technicalTacticalStrategic

Condition-based maintenance without a defined action threshold is not a maintenance strategy. It's a dashboard someone occasionally glances at.

Why this service exists

For high-value or high-consequence-of-failure assets, acting on genuine condition rather than a generic calendar interval avoids both unnecessary intervention (replacing something that's fine) and missed intervention (a fixed interval that's too long for this specific asset's actual duty cycle).

What the service covers

  • Condition monitoring (vibration, thermal, oil analysis, electrical signature).
  • Threshold definition and review.
  • Triggered intervention against defined thresholds.

Assets and objects

  • Concentrated on high-value, high-consequence assets — major HVAC plant, lifts, critical electrical infrastructure — rather than applied uniformly, since monitoring infrastructure has a real cost that only pays off where consequence of failure justifies it.

Who takes part

  • Condition-monitoring specialistRequired

    Mandatory for threshold design and interpretation.

  • Maintenance techniciansRequired

    Execute triggered work.

  • FM asset managerSituational

    Oversees strategy and investment.

What the service needs

  • Sensor/monitoring data.
  • Asset criticality and failure-mode data.
  • Historical condition trends.

How delivery runs

  1. 01Identify assets where condition-based strategy genuinely earns its monitoring cost — not a default applied everywhere.
  2. 02Install and maintain monitoring infrastructure (vibration sensors, thermal imaging cycles, oil analysis sampling).
  3. 03Define explicit action thresholds before monitoring begins, not retrospectively.
  4. 04Trigger and execute intervention when thresholds are crossed.
  5. 05Review and refine thresholds against actual failure data over time.

What is delivered

  • Condition trend data.
  • Triggered work orders.
  • Threshold-review records.

From output to outcome

Output

Monitored assets with triggered interventions.

Outcome

Maintenance effort concentrated exactly where and when it's needed.

Organisational effect

The efficiency case for condition-based maintenance over blanket PPM, realised only when the threshold-and-response discipline is actually followed, not merely when sensors are installed.

Where it gets tense

  • Condition data collected and visualised without any defined action threshold attached — this is precisely that failure mode occurring at the asset level.

Strategic, tactical, operational

Strategic

Condition-based monitoring investment should be justified against consequence-of-failure, not applied as a blanket technology upgrade.

Tactical

Who owns the authority to act when a threshold is crossed needs to be explicit before deployment — this is the asset-level instance of the platform's decision governance principle.

Operational

Sensor calibration drift over time can silently invalidate thresholds if not periodically re-verified.

Performance indicators

  • Percentage of monitored assets with defined action thresholds

    Low percentages indicate monitoring without management.

  • Time from threshold breach to intervention

    Shows response discipline.

  • Avoided-failure count where estimable

    Direct evidence of value.

Risks

  • For critical infrastructure, an unactioned threshold breach can itself become a liability issue if it's later shown the organisation had the data and didn't act on it.

Statutory context

Condition-based maintenance itself is not statutorily mandated, but where applied to statutory assets it must supplement, not replace, the legal minimum inspection regime.

Sourcing options

  • Single service

    Monitoring technology often vendor-supplied/leased.

  • Bundled

    Intervention work typically sourced through the same contract as the underlying asset's general maintenance.

Technology and data

  • Vibration analysis.
  • Thermal imaging.
  • Oil analysis.
  • IoT sensor networks, increasingly feeding predictive-maintenance modelling layers.

Competencies required

  • Condition-monitoring interpretation.
  • Threshold design.
  • Statistical trend analysis.

Common mistakes

  • Installing monitoring technology without defining what action a given reading should trigger.
  • Conflating condition-based with predictive maintenance.

Connections

Knowledge domains
  • Data Science
  • IoT
  • Maintenance Engineering
To index
Standards and guidance
  • None universal
To index
Terms
  • Condition-based maintenance
To index

Adjacent services

Last reviewed: 2026-08-23

Classified using market terminology (hard / soft / enabling), nuanced against EN 15221-8:2025 and ISO 41011:2024.

Services Atlas