Vibration monitoring has one of the best documented returns in industrial maintenance, and the constraint today is attention rather than evidence. A program that reads its whole sensor population every day, and shows the reasoning behind each conclusion, turns that evidence into decisions a reliability team can defend.
The case for vibration monitoring was settled a long time ago. The United States Department of Energy, in its operations and maintenance best practices guide, reports that a working predictive maintenance program tends to return maintenance cost reductions of roughly a quarter to a third, downtime reductions in the range of thirty five to forty five percent, and a substantial fall in unexpected breakdowns. Reliability centred maintenance explains why those numbers hold, because most rotating equipment develops a fault across a detectable interval rather than failing without warning, and vibration is the earliest practical place to observe that development.
An experienced analyst reading a spectrum can separate imbalance from misalignment, catch an outer race defect while it is still weeks away from being audible, and give planning enough notice to order the part and book the window. The return on the entire program lives inside that notice period, which is why so many operations invested in sensors and in certified analysts to read them.
Wireless sensors changed the economics of gathering the data, and the analysis software built around them has served reliability teams well for years. A site that once walked a monthly route now receives readings from hundreds of measurement points every day, and each point carries several parameters across three axes. Trending all of it, comparing each parameter against its alert and alarm setpoints, and deciding what deserves a closer look is a significant daily exercise before any diagnosis actually begins.
Most reliability teams have the judgment they need and would welcome more hours in which to apply it. The opportunity is to point that judgment at the assets which genuinely warrant it, on the morning the data first suggests it, rather than at whichever machines someone had time to open.
Each night the fleet is reviewed to identify statistically significant vibration activity, to compare it against the trend, and to craft the suggested diagnosis with the recommended actions. Points are measured against the setpoints the program itself defined, exceptions are ranked by severity, and a short summary reaches the team ahead of the shift. An analyst opens a list of the few sensors that moved, with the reason each one appears and the evidence attached to it.
Thresholds come from the program's own configuration rather than from a vendor default, and the source of each threshold is stated beside it, so the team knows whether a flag reflects their own setpoint or a statistical band drawn from the machine's history.
Daily vibration brief · 312 points reviewed · 4 exceptions
Reaching a conclusion on a flagged sensor is careful work. The analyst opens the spectrum, compares the reading against the machine's own history, looks at the waveform and weighs several indicators together before committing to an interpretation. Lumina carries out that examination on the data before anyone asks, and presents the result in the terms a reliability team already works in. You get an analyst that does the digging and shows its work.
What the signature indicates on this machine, described plainly, such as imbalance, misalignment, looseness or a bearing defect at a particular stage.
Why that conclusion follows from the reading, for example dominance at running speed pointing toward imbalance rather than a bearing fault.
What to do about it and how soon, with the severity and the remaining notice period that justify the timing.
The measurements and thresholds the assessment relied upon, so an analyst can confirm the reasoning rather than take it on trust.
The saving is measured in analyst hours. Work that used to mean opening spectral plots and waveform captures one sensor at a time now starts from an answer with the evidence beside it, and the team spends its attention on the decision instead of on the retrieval.
Ask the analyst · Conveyor drive 3
Overall velocity reached 0.148 in/s against your configured fault level of 0.140, and the energy sits at 3.1x running speed with sidebands spaced at 1x. That pattern points to an outer race defect rather than imbalance, which would concentrate at running speed alone. Crest factor has risen from 2.4 to 4.6 over eleven weeks, which is consistent with early impacting.
Plan a bearing replacement at the next available window and confirm with an envelope measurement on the drive end. At the current rate of change the trend reaches your alarm level in roughly three weeks.
Lumina computes the engineering before anything is reasoned about. Severity zones under ISO 10816, bearing defect frequencies, harmonic orders, crest factor and projections toward a threshold are calculated by code that behaves consistently across assets and across days, and the reasoning layer then works from those computed results and cites them. We draw a hard line between the model and your logic, so the AI does the reasoning while the rules, thresholds and standards your experts spent years building live outside the model, owned by you. Change a rule and you change the behaviour, audit a rule and you audit the system, because that logic is your intellectual property. That line is the Separation of Logic from Reasoning.
The Dialogue Intelligence Framework structures the conversation between the spectrum, the trend history, the machine record and the questions the analyst is actually asking, so that a recommendation arrives grounded in the full context of the asset rather than in a single reading. When a value is missing, the system names the gap and asks for it, because a stated gap is worth far more to an engineer than a confident guess.
Lumina Cortex then carries what the team teaches it, building a living intelligence fabric across the organization. When a senior analyst corrects a bearing specification or records that a machine runs with a known characteristic, that knowledge shapes the next analysis and stays with the team afterward. The intelligence your people generate compounds over time instead of resetting with every report, and it does not retire when they do, which matters greatly in a field where so much expertise has traditionally left with the person holding it.
All of it runs where your data already lives. The analysis happens on your own device, so the full dataset is processed where it sits, and you choose how your data interacts with AI, from cloud assisted all the way to fully air gapped. Reliability teams keep their working data close to home while still gaining the benefit of modern reasoning.
Spectrum · defect frequency with sidebands, clear of the running speed harmonics
Trend · overall velocity against the levels this program configured
Hours return to diagnosis and away from retrieval, the reasoning behind each answer is visible and challengeable, and the judgment that used to reach a handful of machines each week now reaches the whole fleet every morning.
Coverage stops depending on who had time, exceptions are ranked against the program's own thresholds, and there is enough notice to order the part and book the window rather than react to a stoppage.
Planned work displaces unplanned work, the machine record is maintained by the engineers who know the assets, and every recommendation carries the evidence that makes it defensible in a planning meeting.
Production continuity improves as unplanned stops become less frequent, decisions can be audited long after they were made, and the expertise the organization paid to develop compounds inside it instead of leaving with the people who built it.
That is the whole ambition behind this work, which is to break down the silos of knowledge and combine the expertise across your organization into a single organizational intelligence, for the benefit of everyone in it. Vibration analysis is a natural place to begin, because the physics is well understood, the standards are mature, and the value of a few weeks of notice is easy for anyone to recognise.
Mining shows the stakes plainly, since a single conveyor drive can hold up an entire production chain, and the same approach applies wherever rotating equipment matters. You can read more in Lumina for mining and metals.
A 30-minute session on reading a large vibration program every day, covering the daily brief, the evidence behind each recommendation, and the machine record your team maintains.
No spam. Just new articles on industrial AI, data sovereignty, and the reasoning layer, sent when we publish.