Remaining useful life (RUL): report an interval, not one number
Learn how RUL is defined, what each of three common approaches needs as data, and how to report P10, P50 and P90 values with a worked trend calculation.
Sourced method notes, with the tools to try them.
Learn how RUL is defined, what each of three common approaches needs as data, and how to report P10, P50 and P90 values with a worked trend calculation.
Read flagged rows in a sensor table by their isolation score, understand what contamination does in the model, and see where the method misleads you.
Read correlated sensors through T² and SPE together rather than one statistic, interpret contribution plots, and learn where the method’s assumptions break.
After reading, you can compute frequency resolution for a vibration record, justify your window choice, and read spectral peaks as clues rather than diagnoses, using a worked example.
This article shows how envelope analysis pulls repeating impacts out of a high-frequency vibration band, how to calculate the four defect frequencies, and how to read the result step by step.
Learn what unlabelled sensor history can and cannot tell you, how to evaluate a detector without labels, and why operating modes need attention first.
Learn the predict and update steps, what the gain K means, and how a level-and-slope state yields a smoothed health indicator together with its rate of change.
Follow how CUSUM and EWMA accumulate small process shifts, work through a six-point example, and choose their parameters with false alarms in mind.
After reading, you can set a sampling rate from your analysis band, recognise a false low-frequency peak caused by aliasing, and see why slow PLC or SCADA logs fall short for spectra.
After reading, you can track a machine's broadband vibration against its own baseline and read the ISO 20816 zones in the right context, without treating a zone as a fault diagnosis.
Work through Cp and Cpk on a hypothetical example, see how centring changes the result, and learn the conditions that must hold before the indices can be interpreted.
Compute MTBF, MTTR and availability from a hypothetical record, then see why MTBF is not a lifetime and how the Weibull shape parameter β bears on scheduled replacement.
Before reading a PLC tag for AI, know where in the scan cycle the value was produced and which timestamp describes it.
A number read over Modbus is not an engineering value until address base, scale and word order are verified.
Do not leave an OPC UA connection at “it works”. Treat security mode, certificate trust and user authentication as separate decisions.
The series in a historian is not the series the sensor saw. Compression settings change what features and models learn.
Control charts have watched process drift for decades. Before proposing a machine learning model, look at what this simple method says.
Data from a vibration sensor cannot be interpreted without knowing which quantity it measures, which frequency range it sees and how it was mounted.
Alarm floods are solved with an alarm philosophy first, not a model. AI works better on an orderly alarm list.
MQTT carries messages but does not define a data model. Sparkplug fills that gap by standardizing topic names and payload structure.
A forecasting model does not earn its complexity unless it measurably beats a method as simple as “repeat the last value”.
Splitting a manual into arbitrary-length pieces makes the right answer get searched in the wrong context. Preserve headings, tables and revision information.
Why randomly splitting sensor rows can exaggerate real-world performance.
A starting architecture that separates reading, recommendations and control authority.
Turn a tag value into a usable observation with units, quality, timestamps and asset context.
Availability, performance and quality must use consistent production boundaries.
Connect sensor behavior to operating context, maintenance events and a false-alarm budget.
Track products, batches, lighting and label consistency before counting defect images.
Evaluate answers from engineering manuals with source relevance, device context and appropriate abstention.
Put the business decision, data owner, baseline and acceptance criteria in one place.
Compute locally with a small numerical kernel, explicit memory limits and reproducible checks.
Why a single accuracy percentage can hide failure on rare events.
Kutup moved its client-side machine learning into a 21 KB WebAssembly kernel written in C — no TensorFlow.js, no 50 MB model download. How it works and what it buys.
From historians to machine learning, time-series data powers industrial analytics. A practical guide to collection, quality, and the forecasting methods that actually work on plant data.
General chatbots hallucinate; industrial answers must be verifiable. This article describes the evidence-first design pattern: curated corpora, hybrid retrieval, constrained synthesis, and inspectable output.
Calibration is how a measurement earns trust. The fundamentals — zero, span, linearity, hysteresis, and uncertainty — every engineer should apply before relying on an instrument.
Semantic search matches meaning, not spelling. This article explains embeddings, vector similarity, and why hybrid keyword-plus-vector retrieval is the robust production pattern.
Process data is time-series data, and general-purpose databases handle it poorly. Historians are purpose-built for collecting, compressing, and serving millions of process values.
Decades after digital fieldbuses arrived, the 4–20 mA loop still dominates instrumentation. The reasons are practical, not nostalgic: wire break detection, distance, and noise immunity.
SCADA systems supervise and control geographically distributed assets. A practical breakdown of their five core layers and how they fit together.
IEC 62443 is the reference standard for industrial automation and control system security. Here is how its zone and conduit model translates into concrete network decisions.
Retrieval-augmented generation and fine-tuning solve different problems. Knowing which to use — and why most production systems need both — prevents expensive mistakes.
Three standards dominate industrial Ethernet. They share the same cables and switches — but their timing, topology, and engineering models differ in ways that matter.
Normalization is the discipline of designing relational schemas that stay consistent as data grows. A practical guide to the normal forms that matter for real systems.
PID is the workhorse of process control. Understand what each term actually does, how the controller responds, and what tuning really means before you touch a loop.
OPC UA is the modern standard for industrial data exchange — secure, information-rich, and platform-independent. Here is what it actually provides and how it fits your architecture.
Programmable logic controllers and distributed control systems both automate industrial processes — but they were designed for different problems. Here is how engineers choose between them.
Modbus remains the most widely supported industrial protocol in the world. This guide compares the serial RTU variant with the Ethernet TCP variant and explains when each belongs in your architecture.
No results. Try another term or clear the topic filter.