Reliability measured from your own work orders and sensors
VenturusEAM calculates mean time between failures, repair time, availability and maintenance spend from the work orders your crew closes and the costs posted to your ledger. Sensor readings arrive through one API, are checked against limits for the machine’s class, and feed a health score that says why an asset is in trouble.
21 capabilities on this page’s part of the platform
Reliability / Asset reliability
Asset reliability, last 12 months
Plant 1 · Corrective work by asset
- Fleet MTBF
- 41 days
- Availability
- 97.8%
- PM compliance
- 93%
- Corrective spend
- $64,180
| Asset | Corrective jobs | MTBF | Spend | Health |
|---|---|---|---|---|
| CNC-04 · VMC | 9 | 38 days | $18,420 | 48 |
| PR-02 · Press | 7 | 49 days | $14,960 | 57 |
| RB-02 · Weld robot | 5 | 68 days | $11,305 | 71 |
| AC-02 · Compressor | 4 | 84 days | $7,880 | 82 |
| LT-01 · Lathe | 3 | 112 days | $5,215 | 88 |
| QC-01 · CMM | 2 | 161 days | $2,940 | 94 |
VenturusAIWhy CNC-04 scores 48
- Spindle vibration read critical on 3 days this week: minus 24.
- Three corrective work orders in 90 days, including WO-24817: minus 18. One overdue PM: minus 10.
Where the downtime money goes
The failure Pareto ranks your failure codes by how often they occur and by what they cost, with cost read from posted labor and parts net of returns. The asset reliability report puts corrective count, MTBF and spend side by side for every asset, and the dashboard lists the assets that fail most often.
Failure Pareto
Rank failure codes by how often they occur and by what they cost, for any date range, to see which few drive most of the downtime spend.
Asset reliability report
For every asset, see corrective work count, mean time between failures and maintenance spend over a date range you choose.
Worst assets by MTBF
The dashboard lists the assets that fail most often, with their MTBF and corrective job count.
Availability, repair time and PM compliance
Availability and mean time to repair come from when work actually started and finished on each work order. OEE is calculated per work center from production counts and downtime, and the home dashboard shows backlog, maintenance cost, PM compliance and MTBF for the sites you can see.
MTTR and downtime from real repair times
Mean time to repair and downtime hours are measured from when work actually started and finished.
PM compliance
The share of PM work orders completed within seven days of their scheduled date.
Maintenance KPIs on the home dashboard
The home dashboard shows open, overdue and in-progress work, backlog by priority, maintenance cost this month and year, PM compliance and MTBF.
Asset availability
Availability is the share of the period an asset was not down for maintenance, per asset and across the fleet.
OEE by work center
Overall equipment effectiveness calculated for each work center from production counts and downtime.
Sensor readings checked as they arrive
Gateways and historians post up to 1,000 readings per call to one REST endpoint, with a quality code and source on every reading. Each one is checked against the warning and critical limits a reliability engineer sets for the equipment class, stored with the asset and rolled up by minute, hour and day for trend charts.
Sensor data API
Gateways and historians send sensor readings to Venturus through one REST endpoint, up to 1,000 readings per call.
Out-of-spec readings flagged on arrival
Every incoming reading is checked against warning and critical limits for its equipment class and marked normal, warning or critical.
Latest values and reading history by API
Read the latest value of every sensor on an asset, or the recent history of one sensor, through the same API.
Sensor data quality codes
Each reading carries its quality code, OPC quality byte, source and zone, so bad or uncertain data is not mistaken for a real reading.
Common industrial sensor types
Temperature, vibration, pressure, current, speed, flow, power, voltage, run hours, cycles and humidity are supported out of the box.
Sensor limits screen
Reliability engineers set warning and critical limits for each equipment class and sensor on screen.
Sensor reading history
Every sensor reading is kept in the database alongside the asset, so history is there for trends and investigations.
Sensor trend rollups by minute, hour and day
Readings are rolled up into minute, hour and day averages with min, max and out-of-spec counts for fast trend charts.
Alarms and health scores on the plant floor
Out-of-limit readings raise alarms that operators acknowledge, shelve for a set time with a reason, or clear, and emergency alarms can never be suppressed. Every machine on the plant floor view shows its latest values in green, amber or red next to a health score that is refreshed on a schedule.
Sensor alarms with acknowledge and shelve
Out-of-limit readings raise alarms that operators acknowledge, shelve for a set time with a reason, or clear.
Live condition tiles on the plant floor view
Each machine on the plant floor view shows its latest sensor values colored by limit, plus its health score.
Asset health score with reasons
Each asset gets a 0 to 100 health score from recent out-of-spec readings, corrective work and overdue work, with the reasons shown.
Health scores refreshed on a schedule
Health scores are recomputed regularly from live data rather than once at load.
Spares that protect uptime
The spare parts criticality register shows which spares protect which assets, with criticality, reorder point and safety stock on each. A critical spare with a single supplier is flagged as a supply risk before it becomes a week of downtime.
Spare parts criticality register
See which spare parts protect which assets, how critical each is, and where a single supplier puts uptime at risk.
VenturusAI
VenturusAI scores asset health and shows its working
Each asset starts at 100 and loses points for out-of-spec readings in the last 7 days, corrective work in the last 90 days and overdue work orders. The breakdown is kept with the score, so a reliability engineer sees why an asset is red and decides which machines to inspect or plan work on.
How VenturusAI worksAsset health score with reasons
The system scores asset health and shows the penalties behind it. Reliability and maintenance staff decide which assets to inspect or plan work on.
Related
Common questions
How is MTBF calculated?
MTBF is the average gap between completed corrective work orders on an asset over the date range you choose, and it needs at least two jobs in the window. Fleet averages for MTBF and availability sit at the top of the report.
How do sensor readings get into VenturusEAM?
Gateways and historians send readings to one REST endpoint, up to 1,000 per call, using a sign-in or a company API key. Readings bridged from MQTT or OPC UA gateways keep their OPC quality byte, source and zone.
Is the health score a black box?
No. The score is a fixed formula: points come off for sensor breaches, repeat corrective work and overdue work, and the screen shows each deduction. Green is 80 and above, amber 60 to 79 and red below 60.
Where does the maintenance spend in the reports come from?
From the ledger. Spend is the labor and parts debits posted against each asset’s work orders, minus returns, so the reliability reports and your books agree.
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.