8,000 rows · 8 columns

Factory sensor telemetry

Eight thousand readings from twelve machines across three sites, at ten-minute intervals, with drift, seasonal temperature, injected anomalies, and gaps where a gateway dropped offline.

What is in it, and what is wrong with it

There are two failure modes deliberately hidden in here: a slow bearing-wear drift on vibration_mm_s for two machines, and sharp single-reading spikes that are sensor glitches rather than real events. A good anomaly detector separates them. Timestamps are not evenly spaced — the gateway at site RIV drops out for stretches, so resampling before modelling is not optional.

Schema

ColumnTypeDescription
reading_attimestampReading time, UTC. Irregular spacing.
device_idstringMachine identifier, e.g. MCH-04.
sitecategoryNOR, RIV, or SLT.
temp_cfloatMachine temperature in Celsius.
humidity_pctfloatAmbient relative humidity.
vibration_mm_sfloatRMS vibration velocity.
rpmintegerSpindle speed.
statuscategoryok, warn, or fault.

First twelve rows

reading_atdevice_idsitetemp_chumidity_pctvibration_mm_srpmstatus
2023-01-01 00:10:00MCH-01NOR35.945.62.8591769ok
2023-01-01 00:20:00MCH-02RIV38.3743.73.2081846ok
2023-01-01 00:30:00MCH-03SLT37.49382.9381724ok
2023-01-01 00:40:00MCH-04NOR38.0933.12.4131919ok
2023-01-01 00:50:00MCH-05RIV36.01472.0461738ok
2023-01-01 01:00:00MCH-06SLT35.9844.92.0361819ok
2023-01-01 01:10:00MCH-07NOR37.2936.92.2661687ok
2023-01-01 01:20:00MCH-08RIV36.5537.92.6831810ok
2023-01-01 01:30:00MCH-09SLT36.36442.5081749ok
2023-01-01 01:40:00MCH-10NOR37.2642.32.2331788ok
2023-01-01 01:50:00MCH-11RIV37.8245.73.1271828ok
2023-01-01 02:00:00MCH-12SLT37.2834.22.7241939ok