Remaining Useful Life Without Run-to-Failure Data
You don't need a graveyard of failed bearings to forecast a repair, and the number on the dashboard was never the point.
Field Notes · Author
Andrus Nõmm leads Zoniax OÜ in Tallinn, Estonia, where the team instruments processing plants with ruggedized sensors, edge telemetry, and learning models.
You don't need a graveyard of failed bearings to forecast a repair, and the number on the dashboard was never the point.
Brussels just put AI on both sides of the plant firewall. Read from the control room, the EU's new Cyber-AI Action Plan is part threat model, part toolkit.
A heat pump's economics live or die on two signals the boiler house has never logged: the temperature each duty truly needs, and the shape of the load across the day.
Deployment is day one for an industrial model, not the finish line: how drift, retraining, and ownership decide whether it survives its second year.
ENISA just shipped a five-domain maturity model for the Cyber Resilience Act, and read against a real processing line it works less like a scorecard than a gap list.
The digital omnibus pushed high-risk AI obligations out to December 2027, but the machinery regulation still lands in January 2027, and that gap is where the work sits.
Five claims plant teams hear about MPC, from vendors and skeptics alike, checked against the control-engineering record.
The revised Industrial Emissions Directive asks large plants to prove their water, energy and materials performance, and the number it wants is a ratio most sites can't yet defend.
From 11 September 2026, the maker of every connected industrial device owes Europe an early warning within 24 hours of an exploited flaw - and the plant is usually where that flaw is seen first.
A plant-floor method for baselining, attributing, and pricing industrial AI value before the dashboards outrun the returns.
An anomaly score tells you something changed. Getting to what changed first is a separate, harder problem in correlation, direction, and disciplined alarms.
A field note on putting a language model in the rack: the hardware, the memory-bandwidth wall, the heat, and why the box never closes a control loop.
The first international standard for managing AI is a management system, not a model test - and for a plant that distinction is the whole point.
How a sensor-to-model control loop trims the biggest power load in an activated-sludge plant without risking the permit.
An AI copilot is a useful reference librarian for operators, not an engineer - here's where it earns its keep and where it has to be fenced out.
What the OPC Foundation's Field eXchange profile actually standardizes between controllers, the TSN and Ethernet-APL wires underneath, and where it isn't ready yet.
How infrared inspection turns invisible heat into lead time before a connection fails.
How years of plant tag history move out of the historian into an open, queryable lakehouse, walked layer by layer from sensor to served model.
How to turn historian energy and throughput data into a supplier-specific Scope 3 footprint an auditor will accept.
Why cell plants still scrap 15-30% of early output, and how inline measurement and cell genealogy move defect detection from the gate back to the coater.
Industry 4.0's standardized digital twin was optional for a decade. EU product law just made it a market-access requirement.
How one MQTT broker, the Sparkplug state model, and an ISA-95 topic tree replace a plant's point-to-point integration sprawl.
Who counts as a deployer, when plant AI is high-risk, and the deadlines that land on the factory floor.
Six claims that ride in on the agentic AI procurement deck, and why each one breaks against a deterministic control room.
Who owns the data your machines produce, who may see it, and how to keep it trustworthy from the sensor to the boardroom.
Why specific energy consumption is the metric that actually exposes plant efficiency, and how to benchmark it without lying to yourself.
Five things vendors and managers get wrong about cold chain temperature monitoring, and what actually catches an excursion in time.
Where machine vision, soft sensors, and predictive maintenance actually have to run on a regulated production line.
Telling a synchronized twin from a dashboard, and a four-line test for whether a process plant should build one.
Cameras grade scrap by sight, but it takes spectroscopy to read the copper that wrecks a heat, and a control loop to act before the grab closes.
How the EU's NIS2 directive turns into concrete OT controls on a processing plant floor, built in the order that actually works.
Continuous emissions monitoring isn't one technology. Pick extractive, in-situ, or predictive on accuracy, latency, availability, and who maintains it.
Choosing, validating, and maintaining inferential sensors that survive their first feedstock change.
How to cut a processing plant into zones and conduits, set a security level for each, and build a boundary that actually holds.
Why squeezing the burn on a plant that runs on garbage is a control problem you fight every shift, not a setting you dial in once.
A vision cell sees what a tired inspector misses, but only if the engineering and the claims around it are honest.
Where the hot end's energy, yield, and quality really trade off, and the instrumentation that holds the line.
How instrumented return lines turn over-cautious clean-in-place cycles into measured ones, without ever shipping a failed clean.
Fixed alarm limits catch the gross excursion and miss the early drift. Here's how learned anomaly detection scores raw sensor streams, and why the threshold, not the model, is the hard part.
How the standard maps the plant-to-business seam, what it actually standardizes, and where real integrations slip.
Reliability metrics are only as honest as the failure definition and the timestamps behind them. Four claims worth dismantling.
Two ways to store plant data, compared by storage cost, query, integration, and fit - and how to tell which one your operation actually needs.
Stop deciding edge-versus-cloud plant-wide. Decide it per workload, on latency, bandwidth, reliability, and who maintains it.
Overall equipment effectiveness travels to a continuous plant only if you stop counting parts and start measuring flow, loss, and the constraint.
A working engineer's comparison of the three protocols that run plant networks, scored on the criteria that actually decide a deployment.