Solutions

Asset Reliability

Preventive maintenance is not automatically good maintenance. Too little causes failures. Inspecting too often, carrying tasks nobody needs and running the wrong intervals costs money and capacity just as easily. Asset Reliability combines two parts. Asset Events puts everything that happened to an asset on one timeline. PM Plan Review checks whether the preventive plan is doing what it was built to do. Together they show which plans need attention now, instead of waiting for the review cycle or for the next breakdown.

Annual subscription · Asset Events + PM Plan Review

01 · Everything that happened to one asset
02 · Which assets are worth looking at

WHAT IT IS

Reviewing one PM plan properly takes about 40 minutes.

Multiply that by a full portfolio and the intended three-year review cycle stops being realistic. What actually gets reviewed is the bad actors, the critical assets, and the plans where something already went wrong.

That is a reasonable way to spend limited time, but it says nothing about the rest of the portfolio. Unnecessary tasks, intervals that no longer match the failure behaviour and inspections that have not produced a finding in years sit just as comfortably in plans nobody has looked at.

Asset Reliability makes the plans that probably need a review surface by themselves — based on what actually happened to the asset. The question shifts from "whose turn is it in the cycle" to "which plan is showing that something is off".

HOW IT WORKS

From what happened, to what changes, to whether it helped.

  1. Put the asset history on one timeline

    Preventive work, corrective work, breakdowns, priorities, costs and follow-up work land on a single timeline per asset. Notable events come up for review: unusually high costs, recurring failures, duplicate workorders, PM executed late or skipped, corrective work shortly after a preventive task, large gaps between estimated and actual hours, and low-priority work that later became a breakdown.

  2. Judge the events, do not just count them

    Every event can be marked. Was this preventable — the PM was not performed on time, the interval should have been shorter, or there was no PM plan at all? Was it possibly over-inspected? Was the due date or the planned date not honoured? Or is it a data issue: a duplicate workorder, or hours booked on the wrong tag number, which should be excluded before it distorts the bad-actor analysis. Those judgements are stored, so patterns can be trended instead of re-argued every year.

  3. Hold the plan against what the asset actually did

    Which assets have no PM plan at all, whether the right plan is attached, whether preventive work is executed on time, how often tasks are skipped or deferred, how often a preventive task produces corrective follow-up, whether estimated hours match reality, and whether inspections structurally return nothing.

  4. Set an action and check whether it worked

    Shorten or extend an interval, remove a task, add prevention that is missing, rewrite a task text, correct the estimated hours, change the criticality of an asset. Each action has an owner, a status and a result — and the effect shows up in the asset events that follow.

WHAT YOU SEE

Six views on whether maintenance is working.

  • The asset timeline

    Everything that happened to one asset in one place — preventive and corrective work, breakdowns, costs, priorities and follow-up work, in the order it occurred.

  • Events worth a second look

    Recurring failures, duplicate workorders, corrective work shortly after a PM task, inspections without findings, deviating costs, hours that keep missing the estimate, and intervals that look too short or too long.

  • Avoidable versus unavoidable

    Planned-versus-unplanned tells you how much unplanned work there was, not which part of it could have been prevented. Here every event is judged: was PM late, was a task missing, was the interval too long, was the problem already visible, did low-priority work sit too long?

  • Coverage of the PM portfolio

    Which assets are in a preventive plan, which are not, and whether the plan attached to an asset is the right one.

  • Whether a plan is doing anything

    Execution on time, skipped and deferred tasks, corrective follow-up per plan, estimated against actual hours, and inspections that have not led to an action in years.

  • Whether the change worked

    After an adjustment: fewer breakdowns, less follow-up work, fewer inspections without findings, lower costs, critical work executed on time more often, and a smaller share of unplanned work classified as avoidable.

HOW YOU START

Three things to set up.

  1. Connect your ERP export — workorder history, PM plans, costs and hours, read-only.
  2. Agree which event patterns get flagged and which classifications your engineers use.
  3. Start with the assets and plans that surface first, not with the full portfolio at once.

PRACTICAL

Pricing model, data, and setup time.

  • Pricing

    €12,000 / year

  • Data source

    ERP export (read-only) — workorder history, PM plans, costs and hours

  • Setup time

    2 to 4 weeks

  • Audience

    Reliability engineers, maintenance engineers, asset owners

Talk to us