Failure data and condition monitoring for reliability engineers
Every closed work order carries a failure code, so the Pareto and MTBF figures you work from are built on real jobs. Sensor readings, limits and alarms feed a health score, and condition-based PM turns a reading into a work order.
Reliability / Failure Pareto
Plant 1 failures, last 12 months
Corrective work orders by failure code
- MTBF, CNC line
- 412 h
- MTTR, CNC line
- 3.6 h
- PM compliance
- 94%
- Open alarms
- 4
| Failure code | Work orders | Downtime | Top asset |
|---|---|---|---|
| Bearing wear | 31 | 118 h | CNC-04 |
| Hydraulic leak | 24 | 86 h | PR-02 |
| Belt failure | 18 | 41 h | AC-02 |
| Sensor fault | 15 | 22 h | RB-02 |
| Electrical trip | 12 | 37 h | LT-01 |
Repeat failure
- CNC-04 has had 4 bearing failures in 12 months.
- Spindle vibration limit was crossed again on Tuesday.
What changes for you
Failure data you can trust
Technicians close every corrective job with a problem, cause and remedy code. The Pareto and the worst-MTBF list are built from those jobs, so the analysis starts from what actually happened.
Failure codes on work ordersProblem, cause and remedy codesFailure ParetoRecurring failure alerts
MTBF and MTTR for every asset
Each asset shows its availability, MTBF, MTTR and downtime history. You can compare similar machines across plants and pick the ones worth a deeper look.
Asset reliability reportMTTR and downtime from real repair timesPM compliance
Sensor limits turn into alarms and work
Readings arrive through the sensor API and are classified against the limits you set. Out-of-limit readings raise alarms, and condition-based PM creates the work order.
Sensor data APIOut-of-spec readings flagged on arrivalSensor alarms with acknowledge and shelveCondition-based work orders from sensor alarms
Health scores explain themselves
Each asset’s 0 to 100 score lists the readings, corrective jobs and overdue work behind it. You can see why a machine moved from green to amber before deciding what to do.
Asset health score with reasonsAsset health score with reasonsLive condition tiles on the plant floor view
Critical spares are tied to the assets they protect
The criticality register links spare parts to assets and shows where a single supplier puts uptime at risk. You set min and max levels on the parts that matter most.
Spare parts criticality registerCritical spare stock policyMin/max and reorder point settings
Related
Common questions
How does sensor data get into VenturusEAM?
Readings post to the sensor API with an API key, one at a time or in batches. Each reading is checked for quality, stored with its history and classified against the asset’s limits.
Can preventive maintenance run on a condition?
Yes. A PM schedule can trigger on a sensor condition, a meter reading, the calendar or a floating interval from the last completion.
Are failure codes configurable?
Yes. You define problem, cause and remedy codes for your equipment, and technicians pick from them when they close a job. VenturusAI can suggest a code from the request text for the planner to confirm.
Can I export the failure data for my own analysis?
Yes. Every grid exports to a spreadsheet, and the asset API returns records for your own tools.
The plant never stops. Neither does the record.
Bring an asset list and a month of work orders. We will load them and walk through your own plant in VenturusEAM, from the purchase order to the depreciation run.