Collection and storage
OPC UA, MQTT, custom gRPC collectors and batch import feed a durable ingest path with edge buffering, quality and explicit gaps.
SPEC 02–03→
Platform
One lifecycle. One model. One platform.
OrdinateDB is a time-series data platform spanning collection, storage, context, calculations, events, visualisation and access. The boundaries below explain responsibilities, not product editions.
One lifecycle
From arriving signal to governed use.
Asset context
Streams relate to assets, equipment, units, metadata, hierarchies and relationships through stable, versioned identities.
SPEC 01→
Calculations and derived streams
Deterministic rules turn declared inputs into versioned outputs whose lineage remains queryable and replayable.
SPEC 05→
Events and episodes
Batches, downtime, shifts and campaigns become named spans of time connected to the assets and data they describe.
SPEC 07→
Visualisation and analysis
OrdinateDB visualisation uses model, quality and event context for live state, historical trends and generated displays.
SPEC 09→
APIs and integration
REST, streaming, gRPC ingestion and ordctl expose the same governed operations used by the product interfaces.
SPEC 13→
Why coherence matters
SPEC 01 · SPEC 13One identity survives every step.
A collector writes to a stable stream identity. The model relates that stream to an asset. Calculations, episodes, displays, permissions and API queries refer to the same identity, so context does not have to be rebuilt at every handoff.
one stream · one governed path
collectsource URI → stream UUID
contextualisestream UUID → asset attribute
derivedeclared inputs → versioned output
visualiseasset → model-driven display
accessprincipal → role → scoped data
Architecture
Unified at the core, distributed where operations require it.
See how local history, interrupted links, forwarding and public interfaces fit across edge, plant and business environments.
Explore Architecture →Product governance
Data, configuration and access retain their history.
Inspect versioned configuration, lineage, quality, permissions, calculation history and attributed audit records.
Explore Product governance →Read the concepts and source-derived API reference, then use the live demo when you are ready to inspect the product directly.