Forbach & Partners DE Book a call

From vibration to alert: our system's processing chain according to ISO 13374

Between the raw signal on the spindle housing and the alert in the dashboard there are five clearly separated steps. Each one is traceable, and every threshold is stated openly.

An alert such as "Outer race bearing damage suspected" is the end of a long calculation. If people are to trust it, they need to know how it comes about. This article describes the processing chain from vibration to alert in our system, step by step: from the measurement window through features, spectrum and envelope to the assessment against the learned baseline and the inspection recommendation in plain language. Along the way we state the starting values the system works with today and say which of them are still being calibrated on the test rig.

Five of the six stages according to ISO 13374

The ISO 13374 series of standards describes how data is processed in condition monitoring. It divides the path into stages: data acquisition, data manipulation, state detection, health assessment, diagnosis and recommendation. We have adopted this structure because it enforces a clean separation. Each stage has a clear input, a clear output and a fixed location: either the edge box on the machine or the platform in the data centre in Germany.

1 Acquiresensor andspeed 2 Preparewindow, filter,envelope 3 Detectfeatures,bearing lines 4 Assessbaseline,confirmation 5 Advisefinding andinspection Edge box on the machine Platform (Germany) Only features are transmitted, no raw signal
The processing chain according to ISO 13374. The computationally intensive stages run on the machine; the assessment against the learned baseline runs on the platform.

This split is deliberate. A raw signal with sampling rates in the kilohertz range is large. Features are small. The edge box therefore calculates stages one to three itself and sends only the result. The platform, in turn, knows the history of every machine and can judge whether a value is unusual for exactly this spindle. How the edge box is built is described in the article The edge box on the machine.

Step 1: The measurement window at constant speed

The edge box records the signal from the vibration sensor on the spindle housing in short windows. By default, a window is one second long and one is recorded every ten seconds. Both can be set per measuring point. In parallel, the edge box reads the spindle speed from the CNC control, read-only via OPC UA.

Not every window is evaluated. The edge box checks the speed immediately before and after the window. Only if both values are above 300 rpm and differ by no more than 2 % does the window go into the calculation. Run-ups, braking and standstill are therefore excluded. The reason is simple: bearing frequencies are proportional to speed. If the speed changes during the measurement, the lines in the spectrum smear, and the window can no longer be compared cleanly with the baseline.

Step 2: Features, orders and envelope

From every valid window, the edge box calculates a fixed set of features. The names of these features are part of our data contract and are versioned. This keeps it traceable which calculation produced a stored value.

FeatureDomainWhat it represents
RMSTime domainTotal energy of the vibration
Peak valueTime domainLargest excursion in the window
Crest factorTime domainPeak value divided by RMS, rises with impacts
KurtosisTime domainMeasure of impulsiveness
1st and 2nd orderOrder spectrumVibration once and twice per revolution
Envelope amplitudesEnvelope spectrumEnergy at BPFO, BPFI, 2 × BSF and FTF

The time-domain features are explained in detail in the article RMS, crest factor and kurtosis. For frequency analysis, the window is weighted with a Hann window and converted into an amplitude spectrum. The frequency axis is then divided by the rotational frequency. This produces the order spectrum: order 1 is the vibration once per revolution, typical of unbalance; order 2 often points to alignment or mounting problems. The search uses a tolerance of at least 0.05 orders. More on this in the article Order analysis and unbalance.

For the bearings we use envelope analysis. A band-pass filter cuts out the frequency range around a structural resonance, the Hilbert transform provides the envelope, and its spectrum shows how many times per second impacts occur. The band has to be determined for each measuring point, for example with a tap test. There is no standard band for all machines. The fundamentals are described in the article Detecting rolling bearing damage early.

Step 3: Searching for the bearing frequencies

From the bearing geometry given in the datasheet and the measured speed, the edge box calculates the four fault frequencies. It then searches the envelope spectrum for lines at these positions. Fixed rules apply:

  • Tolerance: real bearings slip. The search therefore covers a band of ±2 % around the calculated frequency, but at least 1.5 line spacings wide.
  • Comparison with the noise floor: every line found is compared with the local noise floor. The noise floor is taken as the median of the amplitudes around the line. The median is insensitive to the very lines we are looking for.
  • Fundamental and harmonics: the fundamental frequency and its multiples up to the third are checked. Damage only counts as seen when the fundamental itself is at least 10 dB above the noise floor and at least one harmonic is too. A multiple on its own is not enough, because multiples of different damage types can overlap.
  • Rolling element at 2 × BSF: a defective rolling element touches both raceways once per rotation about its own axis. The clearer line is therefore usually at twice the rolling element frequency.
  • Sidebands: for each fault frequency, the edge box checks whether there are lines next to it spaced at the rotational frequency. This is typical of inner race damage, which passes through the load zone with the shaft.

The result is not an opaque overall score, but a series of findings of the kind "Outer race: line at the expected frequency, two multiples, so many dB above the noise floor". If there are several candidates, the one with the most multiples found and the greater distance from the noise floor wins. The 10 dB is a starting value, not a value from a standard. It is being calibrated with measurements on the test rig.

Step 4: Assessment against the learned baseline

Whether a feature is high depends on the spindle. Installation, age, sensor position and machining shape the base level. The platform therefore compares every new value with the learned baseline, i.e. the normal state of exactly this machine, at exactly this measuring point and in the same speed range. By default, the speed ranges are rounded to 100 rpm, so that only like is compared with like.

The baseline is built from at least 20 measurements in a known healthy condition. For each feature, the platform stores the median and a robust spread. The deviation of a new measurement is calculated as follows:

Deviation = (value − median) / spread only increases count Spread = maximum of 1.4826 · MAD (90th percentile − median) / 1.2816 5 % of the median

MAD is the median absolute deviation from the median. With the factor 1.4826 it corresponds to the standard deviation for normally distributed data, but is insensitive to individual outliers in the learning phase. The second formula handles skewed distributions, as are usual for spectral amplitudes. The lower bound of 5 % of the median prevents a very quiet machine from reporting the smallest changes as an alarm. Why we take this route rather than fixed thresholds is explained in the article 3-sigma alarms or a learned baseline. How the learning phase works in operation is described in Learning the baseline.

Persistence: confirmed first, then reported

The largest deviation across all features determines the level of a single measurement. The starting values are:

Starting values, not from a standard, calibrated on the test rig
LevelDeviation fromMeaning in the alert
Normalbelow 4within the range of the baseline
Noticeable4keep an eye on it, no immediate action needed
Warning8schedule an inspection at the next opportunity
Alarm15inspect promptly, increased risk of failure

A single measurement, however, does not yet trigger anything. A level is only reported once it has been reached in three consecutive measurements. More precisely: the reported level is the lowest of the last three. An impact during a tool change or a knock during clamping therefore does not produce an alarm. In addition, a new alert is only raised when the confirmed level rises. If a spindle stays at "Warning", it is not reported again with every measurement.

What the starting values mean

The thresholds 4, 8 and 15, the 10 dB for the bearing lines and the three confirmations come neither from a standard nor from a manufacturer. They are deliberately chosen starting values that can be set per installation. Synthetic signals have shown that the calculation is correct. How early real damage is detected will only be shown by the test rig and feedback from operation.

Step 5: From deviation to a plain-language recommendation

The last stage translates numbers into an alert a maintenance engineer can work with. Every alert consists of five parts: title, location, urgency, inspection instruction and explanation. The title depends on the strongest finding. If the edge box has identified a bearing component in the envelope spectrum, or if an envelope amplitude has risen the most, it reads something like "Outer race bearing damage suspected (spindle bearing)". If the first order has risen the most, it says "Unbalance suspected". If crest factor or kurtosis have risen, the alert points to impulsive vibration and possible incipient bearing damage.

The location states machine, measuring point and speed. The inspection instruction says what to do on site, for example: check running noise, bearing temperature and lubrication, discuss the finding with the spindle service provider. If unbalance is suspected: check the tool and workholding for unbalance, contamination and seating. The explanation names up to three features with reading, normal value, factor and deviation, plus, where applicable, the distance of the bearing line from the noise floor in dB. It ends with the note that the finding has been confirmed over several measurements.

What the alert deliberately does not contain: an estimated remaining running time. Our rule for alert texts is to say what was measured and what to inspect. A figure in days would be invented without reliable damage data for your spindle. What the alert looks like in the dashboard is shown in the article Alerts with an explanation. Which machines are suitable is set out on the page Spindle monitoring for CNC machining centres.

Frequently asked questions

How is an alarm generated in condition monitoring of a CNC spindle?

In our system, in five of the six stages of ISO 13374 (we deliberately make no day-exact prognosis): the edge box records vibration windows at constant speed, calculates features and searches the envelope spectrum for bearing frequencies. The platform compares the features with the machine's learned baseline. An alert is only raised when a level persists for three measurements in a row.

Why does a single impact during a tool change not trigger an alarm?

Because a level is only reported once it has been reached in three consecutive measurements. A one-off outlier remains visible in the database but does not produce an alert.

Are the alarm thresholds taken from a standard such as ISO 10816?

No. Standards such as ISO 10816 or ISO 20816 assess whole classes of machines and are too coarse for early bearing damage. Our thresholds refer to the deviation from the baseline of the individual spindle. The values 4, 8 and 15 are starting values that are calibrated on the test rig.

Is raw vibration data transferred to the cloud?

No. The edge box calculates the features at the machine and transmits only these. Details on transmission and storage are on the page Data security.

Does the system predict when the spindle will fail?

No. The alert states the finding, the size of the deviation and an inspection recommendation with urgency. A remaining running time to the day cannot be credibly given without damage data for the specific spindle.

Sascha P. Forbach

About the author

Sascha P. Forbach is the founder of Forbach & Partners and the software architect of its spindle monitoring system. For twelve years he has advised manufacturers on process quality and machine availability. About us

Next step

Can your control be connected? You will know in 20 minutes.