Maintenance Risk Agent
Says which asset fails next, and which service is causing failures
4 of 16 assets are high risk, and 63% of all assets are past their service interval.
16 assets, 22 failures in the last 12 months, 10 assets overdue for service.
Main compressor K1, Passenger lift L2, Forklift F-12 are high risk: overdue, failing repeatedly or old, and ranked first because of how critical they are.
3 critical asset(s) already carry 3 or more risk points: Main compressor K1, Passenger lift L2, Chiller CH-3.
Points: overdue 2 (3 beyond 1.5 times the interval), 3+ failures 2, 2 failures 1, age 10+ 1; priority is points times criticality. These are rules over your figures, not a failure probability.
Priority score, highest first
- Main compressor K118
- Passenger lift L218
- Forklift F-1210
- Chiller CH-39
- Packaging line P46
- Air handler A-66
- Wrapper W-26
- Boiler B-16
Assets by risk level
- High25%
- Medium44%
- Low31%
Assets, highest priority first
| Asset | Age | Failures | Days since service | Interval | Points |
|---|---|---|---|---|---|
| Main compressor K1 · High | 11 | 4 | 420 (Far overdue) | 180 | 6 |
| Passenger lift L2 · High | 14 | 3 | 400 (Far overdue) | 180 | 6 |
| Forklift F-12 · High | 8 | 3 | 210 (Far overdue) | 120 | 5 |
| Chiller CH-3 · Medium | 9 | 2 | 250 (Overdue) | 180 | 3 |
| Packaging line P4 · Medium | 7 | 1 | 160 (Far overdue) | 90 | 3 |
| Air handler A-6 · Medium | 10 | 1 | 400 (Overdue) | 365 | 3 |
| Wrapper W-2 · Medium | 9 | 2 | 100 (Overdue) | 90 | 3 |
| Boiler B-1 · Medium | 12 | 2 | 330 () | 365 | 2 |
| Sprinkler pump SP-1 · Medium | 8 | 0 | 190 (Overdue) | 180 | 2 |
| Dock leveller D-3 · High | 15 | 2 | 280 (Far overdue) | 180 | 5 |
| Generator G-1 · Low | 13 | 1 | 340 () | 365 | 1 |
| Conveyor C-7 · Medium | 5 | 1 | 95 (Overdue) | 90 | 2 |
What to do this week
- Service Main compressor K1, Passenger lift L2 this week: they top the priority list.
- Bring the 10 overdue assets back inside their interval, critical ones first.
- Review replacement for Main compressor K1, Passenger lift L2: old, failing repeatedly and overdue, so repair is unlikely to hold.
Do
- Service in order of priority score, not in order of due date.
Don't
- Don't read points as a failure forecast: they say where to look first.
How to improve
- Add repair cost and downtime per failure so the next report can price the risk.
- Add failure causes so the next report can separate wear from misuse and missed service.
Demo
Overview
Preventive maintenance intervals come from a manufacturer's recommendation written for an average machine in average conditions. The asset in front of you is not average — it runs harder or barely at all, in dust or damp, operated by people with different habits. The same interval is simultaneously too frequent for half the fleet, servicing things that did not need it, and too slow for the other half, which fails between services.
The evidence to correct this is already in the work order history and nobody reads it. Every organisation running assets has years of records showing what broke, when, after how many hours, and what was done just before it broke. That last one is the finding nobody looks for: failures clustering shortly after a service is not coincidence, it is induced failure, and it means the maintenance itself is causing downtime.
Two more patterns hide in the same data. The same fault fixed four times on one asset means the fix is wrong, not that the asset is unreliable. And an asset whose maintenance cost has passed what it is worth to keep is a replacement decision nobody makes, because no single line item ever looks large.
This agent reports all four, with the evidence and the confidence behind each. It schedules nothing and touches no maintenance system, and it never makes a safety determination.
Benefits
Failures prevented rather than attended
Which is the whole point of preventive maintenance.
Servicing that stops being wasted
Half a fleet is usually serviced more often than it needs.
Replacement decisions with evidence
Rather than when something finally dies.
What it does
Finds induced failures
Breakdowns clustering shortly after a service. Not coincidence — the maintenance itself is causing downtime, and nobody looks for it.
Corrects intervals to actual use
The manual describes an average machine. Yours runs harder, or barely at all, in conditions it never mentions.
Catches the fault fixed four times
A repeat failure means the fix was wrong, not that the asset is unreliable. Different problem, different action.
Names the asset past its economic life
Maintenance cost against replacement value. No single work order ever looks large enough to trigger the question.
States confidence per finding
Some assets have hundreds of records and some have nine. The report says which is which.
Schedules nothing
No work order is raised, changed or closed, and no safety determination is ever made.
What this changes
What this changes about your week
- It takes over
- Reading years of work orders to find what fails next and why.
- Done today by
- Nobody. Intervals come from the manufacturer's manual instead.
- How often
- Never, which is why intervals never change.
- Typical manual effort
- Correlating every failure against usage, service history and the fleet baseline.
Why Field Services in particular. Failures clustering shortly after a service means the maintenance is causing downtime — the one pattern nobody looks for, because it inverts the assumption the whole schedule rests on.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Maintenance Risk Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-opus-5 with automatic fallback
- 3Toolsextract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Requirements
Integrations
No integrations required.
Before you start
- Work order history: asset, date, fault, action taken, cost, downtime
- Asset register with running hours or usage, and replacement value
- Current maintenance intervals
- Requires the All-Access plan or higher
Use cases
Annual maintenance planning
Intervals set from your own history rather than the manual.
A rising downtime trend
Whether it is age, intervals, or the servicing itself.
Capital planning
Which assets have passed the point of being worth repairing.
After acquiring a fleet
What the records say about what you just bought.
Pricing
All-Access
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Does it schedule maintenance?
No. It raises, changes and closes nothing, and has no access to a maintenance system. It reports what the history shows.
Does it make safety decisions?
Never. Where a pattern touches a safety-critical system it escalates immediately to a person. It gives no safety determination of any kind, in any circumstance.
How much history does it need?
More is better and it tells you when there is not enough. A prediction from nine work orders is reported as low confidence rather than presented alongside one drawn from four hundred.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent