Structural Ontology
Assets, spaces, topology, live state, telemetry bindings, and the relationships that describe the operational world.
Operational Context
Industrial AI needs a model of the world it operates in.
DanaOS connects what exists, what is happening, what experts know, and why a condition matters to the business.
The DanaOS architecture
Four layers. One runtime.
Vendor extensionsHoneywell BMS · Experionover verticals
Vertical packsBuilding · Industrial · Semi · Mining · Oil & Gas · Maritime · Gridcompose, don’t fork
Cross-vertical foundationsspatial · process-flow · equipment · enterprisethe non-forking tier · governed modules
Substrate runtimegoverned agents · two-tier ontology · sovereignty
Vertical packs compose shared foundations — they don't fork them. The runtime never changes per domain.
Cognitive Ontology
Procedures, causality, judgment, computations, models or simulations, methods, and validation logic.
Enterprise facet
Economic meaning—cost, production, risk, and compliance—tags every relevant entity, condition, and action.
A two-tier ontology — Structural (what’s there) and Cognitive (what to do) — plus an Enterprise facet that tags every entity and action with its economic meaning (cost, production, risk, compliance).
DanaOS represents this architecture; some capabilities remain in development.
DanaOS integrates your existing sensors and operational systems; it is not a sensor platform.
From condition to consequence
Context turns signals into decisions.
- PerceiveRead state through governed bindings to existing sensors and systems.
- ContextualizeResolve identity, relationships, topology, and constraints.
- ReasonApply the Cognitive Ontology with computations, models or simulations, and expert methods.
- Act and verifyRecommend or act through explicit authority, then confirm the outcome.