Manufacturing
Line and OEE telemetry, quality-gate state, and downtime analytics on one engine — line-rate ingest with constant-time current state.
The problem
Why this is hard today
A production line emits a continuous stream of machine, sensor, and quality-gate events, and the questions that matter are immediate: which cells are down, which lines are below OEE target, which gate just started failing.
The common stack routes telemetry into a historian, current state into a cache, and analytics into a warehouse — three systems whose disagreement shows up as a plant dashboard that trails the line it monitors.
The fit is one engine that ingests line telemetry at line rate, maintains per-cell and per-line current state as O(1) reads, and computes OEE and downtime rollups continuously in the same SQL.
Where NYXDB fits
Use-case journeys
Machine & sensor ingest
Absorb bursty line-telemetry streams durably, with backpressure instead of data loss.
IoT & telemetryPlant observability
Continuous transforms turn raw events into live per-cell OEE and downtime tables.
Observability & logsDowntime time series
High-rate ingest and windowed downsampling of line metrics for trend analysis.
Time seriesArchitecture
How NYXDB fits the plant floor
Machine and quality events append durably at line rate under the memory governor; keyed tables hold the latest state per cell and line; continuous transforms maintain the OEE and downtime tables dashboards read as ordinary tables.
- 01
Line-rate ingest
Shard-owned, lock-free write paths, WAL-backed, governed under pressure.
- 02
Cell & line state
Keyed tables keep the latest per (cell, metric) — O(1) reads.
- 03
OEE rollups
tumble/hop windows maintained continuously by transforms (ADR-080).
- 04
Live streams
STREAM SELECT pushes state and OEE deltas to plant dashboards as they commit.
Real SQL
Representative queries
SELECT line_id, oee, target_oeeFROM line_stateWHERE oee < target_oee;Every statement follows the engine’s own test SQL shapes. See the SQL reference for full syntax.
Capabilities
What you get
Line-rate ingest
Lock-free shard-owned write paths.
O(1) cell state
Latest reading per cell, instantly.
Windowed OEE
tumble/hop maintained continuously.
Edge to cloud
One 154MB image runs on the floor or in the datacenter.
Proof
Measured on the vetted benchmark lane
durable line-telemetry ingest, single core
1M-row batches, best durable mode
vetted table
View benchmark12.45M rows/sin-memory columnar append ceiling
narrow 4-column rows
vetted table
View benchmark268nsper-cell state count, flat 1k–16k keys
O(1) maintained counter
vetted table
View benchmarkMeasured on AMD EPYC 9554P 64-Core Processor (64t), 1505GB RAM, 6x NVMe — measured on server-class hardware. Release build, median of 5 (re-captured stragglers: median of 3), commit-pinned (7945ae33, 2026-07-09). Ingest figures are engine-side. See the full benchmark suite.
Learn more