Explainable, hardware-agnostic predictive maintenance. Bluestream PdM ingests any existing sensor over OPC UA / Modbus / MQTT / I²C, predicts remaining useful life against reliability standards, and pushes a criticality-ranked, failure-mode-labelled work order into your CMMS.
The difference is that every number traces back to a standard: an ISO 14224 failure mode, an OREDA base rate, a position on the P–F curve, and a NORSOK Z-008 criticality — so a reliability engineer and an auditor both accept the call.
The idea in three moves
Most predictive-maintenance tools force a trade-off: a proprietary sensor you're locked into, a black-box score no engineer trusts, or an offline reliability spreadsheet with no live data. Bluestream refuses the trade-off — ingest, reason, act.
Any existing sensor or PLC over OPC UA, Modbus, MQTT or I²C. No proprietary hardware, no rip-and-replace.
Predictions anchored in OREDA reliability data and ISO 14224 failure modes — a credible answer from day one, not after months of training.
Every finding becomes a criticality-ranked, failure-mode-labelled job in your CMMS — the loop closes.
1 · Open on what needs attention
The dashboard doesn't greet you with a wall of gauges. It opens on a single ranked queue — what to act on first — sorted by severity, then criticality, then how much lead time is left. Healthy assets collapse out of the way.
Needs action
ranked by severity · criticality · lead timevib_rms ›
winding_temp ›
You start with the two or three assets that actually need you today — the antidote to alert fatigue, the number-one reason maintenance teams end up tuning predictive tools out.
2 · Lead with the conclusion
Click an asset and the first thing you see isn't a spectrum plot — it's a plain-language verdict: what's wrong, whether it was caught early, and what to do. Anyone on the team knows the situation in one sentence.
winding_temp is trending toward its limit — predicted ~8d of lead time, caught early at P.
Recommended check cooling, load and connections; plan a winding inspection · est. repair ~3.3h.
An alert becomes a decision. The failure mode is named in a public standard — ISO 14224 code OHE — so the finding is auditable and travels with the asset, rather than living in a proprietary label.
3 · Show your work
Under the verdict sits the reasoning, assembled end-to-end. A signal becomes a failure mode, checked against an industry base rate, placed on the P–F curve, and turned into a remaining-life estimate with honest uncertainty.
Why we're saying this
P–F curve — you are here
Remaining life
~8dYou see remaining life as an honest range (P10–P90), and exactly where the asset sits on its failure curve — not a single number you can't interrogate.
ISO 14224 names the failure mode, OREDA supplies the population base rate and repair effort, the P–F interval frames the lead time, and NORSOK Z-008 sets the criticality that ranks it.
Reading the P10–P90 band. The remaining-life figure isn't a single date — it is the 10th, 50th and 90th percentiles of the predicted days-to-failure. P50 (~8 days) is the median, the most likely time to failure; P10 (~6 days) is the conservative end you plan the work by — only a 10 % chance it fails sooner; and P90 (~11 days) is the optimistic end, by which failure is nearly certain. The band narrows as live data accumulates. See Predictive Maintenance & RUL for how the band is built, and Weibull’s B10 life for the population version of the same idea.
4 · One tap to a work order
"Create work order" opens a job that already knows why it exists — pre-filled with the asset, failure mode, criticality, remaining life, and the OREDA repair estimate — plus a checklist scoped to the specific failure mode. Print it for the technician, or push it to the CMMS.
OHE — Overheating · ISO 14224
C3 · NORSOK Z-008 · plan within 5 days
RUL ~8d · ~43% through P–F · repair ~3.3h (OREDA)
The same maintenance intelligence behind the Work Instruction Generator in our Toolbox builds the checklist — each step tied to the failure mode, with acceptance checks and hazard callouts.
Under the hood: what makes the answers trustworthy
The platform is deliberately built so that nothing on screen is a black box. Six design choices carry that promise:
A small edge service normalizes OPC UA / Modbus / MQTT / I²C into one contract — so any sensor, new or installed, feeds the same pipeline.
An OREDA population failure-rate prior gives a credible remaining-life estimate on day one, then sharpens with live trend as evidence accumulates.
A close-coupled pump's body and its motor driver draw on separate OREDA records — the granularity ISO 14224 defines and other tools flatten.
Each prediction cites a failure mode, a base rate, and a P–F position — an audit-grade rationale, not a post-hoc gloss on a black box.
Findings become work orders in Microsoft Dynamics 365 or your CMMS, ranked by NORSOK criticality and hours-to-limit.
Every alert links to plain-English explainers of the standard behind it — you're reading one now.
The through-line: every number on the screen can be traced to a reliability standard. That is what lets Bluestream be explainable and hardware-agnostic at once — the combination the rest of the market leaves open.