Industry · 05 / Jet engines

Idle to afterburn, every spool on record.

Vibration spectra at 20 kHz, EGT, shaft speeds and borescope video — one record from the test cell to the wing.

20 kHz
vibration at full rate, never decimated
In sync
spectra beside borescope video
Cell → wing
one record across the engine’s life
01 · Phloem for propulsion

The test cell, readable.

High-rate vibration means nothing in isolation. Phloem keeps it next to temperatures, speeds and video, on one playhead.

Spectra with context

A vibration signature lines up with EGT, N1 and the borescope frame from the same instant.

Trend across builds

Compare runs across engine builds and hours. Watch a bearing signature develop over months, not fail in a day.

Evidence for certification

Structured test reports traceable to raw channels, assembled from the run itself.

02 · Lifecycle

One platform, from first prototype to fleet.

The record built in development carries into validation and operations — nothing starts from scratch.

01

Develop

  • Rig and core tests on the same timeline as full-engine runs — live at the bench from the first spool-up.
  • Compare builds channel by channel across the campaign.
  • Correlate performance shifts with hardware changes.
02

Validate

  • Run acceptance tests as codified, repeatable suites.
  • Flag out-of-family vibration the moment it appears.
  • Generate traceable evidence for review in minutes.
03

Operate

  • Ingest on-wing and overhaul-shop data into the same record.
  • Trend health per serial number across the fleet.
  • Catch wear early by watching signatures drift.
03 · One timeline

What a run looks like in Phloem.

A cell run as it lands: vibration, EGT, shaft speed and borescope video, already on one playhead.

Cell 3 · Run 212 cell · recordingcloud · in sync BUILD 9 · LIVE
28:14elapsed
9,204Kmessages
8streams
24.1 GBon disk
T+00:00T+01:00T+02:00T+03:00T+04:00
vibe/vib/spectral_x 20 kHz
temp/engine/egt_c 712 °C
speed/engine/n1_pct 96 %
video/cam/borescope 30 fps
At the cell

The cell records to a local spool from the first spool-up — no cloud dependency mid-run. Every run syncs into the engine’s one record afterwards.

CELL 3 local spool · full rate syncs between runs CLOUD one record · every run
04 · Ecosystem

Native to the test cell.

First-class ingest for the formats, protocols and buses this work already runs on — and the wider ecosystem behind them.

protocolModbus
formatMCAP
dataInfluxDB
vizGrafana
analysisMATLAB
dataParquet

And anything else with an SDK, a topic, or a recorded log.

05 · Outcomes

What teams get back.

Full-rate
Forever queryable

Twenty-kilohertz vibration stays at twenty kilohertz — the microsecond events that matter don’t get averaged away.

Months
Of signature history

A developing bearing signature is visible across every run of every build, in one query.

06 · End of run

Engines that tell you before they fail.

The signature is always in the data. Keep every run, at full rate, in one place — and hear it early.