Coral Thermal Telemetry Schema
An open schema defining what an instrumented liquid-cooled infrastructure pod measures, at what rate, in what units, with what semantics, and how the resulting data is structured. No comparable open schema exists for immersion or hybrid thermal systems, which is why fleet-level thermal data is currently unusable across vendors.
Coral publishes an open telemetry schema defining what an instrumented liquid-cooled infrastructure pod measures, at what rate, in what units, with what semantics, and how the resulting data is structured. No comparable open schema exists for immersion or hybrid thermal systems, which is why fleet-level thermal data is currently unusable across vendors.
Why a schema is the most important thing in this section
Whoever defines how a pod is measured owns every layer above it. A schema is boring, foundational, and it determines whether the next five years of fleet data are an asset or a pile of incompatible logs. It also creates a gravitational pull: any operator who adopts the schema becomes a candidate contributor to the shared dataset.
What the schema defines
Entity model. Measurement taxonomy. Units and precision. Sample rate classes. Quality flags. Event model. Fluid condition data model. Spatial thermal field representation. Control action logging. And a reference implementation.
Status
Version 1.0 is in preparation. Coral's current shipping instrumentation baseline covers seven parameter classes over Modbus TCP/IP: temperature logging, pump health, flow, pressure, oil level, oil leak detection and door interlock state. The schema extends this to the fluid condition and spatial thermal field layers described at Layer 7.
Request the specification document
A consulting engineer can design a Coral pod into a building without a sales conversation. Ask for the current interface document and the change log.