Why operators end up with both
Telemetry without a plan is a filing cabinet. A plan without telemetry is a spreadsheet. The products are useful apart and coherent together.
The shared spacecraft registry
Every spacecraft is described once: its COSPAR identifier, its buses, the APIDs it emits, the parameters those APIDs carry and their units, the elevation masks it is flown against and the ground stations it can reach. Telemetry Hub resolves incoming packets against that description. Mission Control computes windows against it. A change to an APID map is a change in one place.
- One registry entry per spacecraft, versioned with a diff log
- APID maps that accept ranges and masks, not just fixed values
- Units declared at the parameter level, converted at query time
One clock across both products
Telemetry timestamps are not the moment Helion received a frame. They are the spacecraft clock value carried inside the frame, corrected by the offset Helion maintains per spacecraft and per station. The receive time is kept alongside it, never instead of it. When an operator compares two spacecraft against a thermal event, both timelines refer to the same instant.
- Spacecraft time preserved separately from station receive time
- Per-station clock offset measured continuously, not assumed
- Offsets visible in the audit log with the measurement that produced them