The control plane
One living model of the enterprise, read from the estate itself, that powers the dashboards, the alerts, the impact analysis, the workflows and the investigation layer. Not a diagram: a queryable operational record.
Discover
Every entity, system, environment, dataset, data domain, integration and business process, with who owns it and how it connects. Registered by hand, imported from templates, or read by connectors — and every object carries its provenance: declared, imported, inferred or verified, with when it was last observed. Known and guessed are never confused.
Observe
Connectors read from the estate on a schedule you control and never write to it. A generic REST poller, CSV upload for estates the cloud cannot reach, a telemetry API for systems that push, and a contract that makes an enterprise connector a module rather than a project. A connector that cannot read says so on every screen that depends on it.
Health is composed from evidence — availability, reliability, interface success, timeliness, freshness, volume variance, schema stability, ownership, observation and dependency — up from systems and integrations to datasets, domains, processes, entities, acquisitions and the enterprise. Every state opens to what made it. A state nothing measured says unmeasured, never healthy. Thresholds are yours.
Understand
If this integration fails, what is affected? The model is traversed, not guessed: upstream and downstream, direct and transitive, the entities, processes, datasets and owners, with anything reached only by inference listed apart and never counted. An executive landing view answers the eight questions a board asks, each from something you can open.
The investigation layer answers plain questions — why did integration health fall this week? — by walking the same model, and every fact it states cites the evidence it read. How the AI is kept honest →
Control
A central exception register with severity, priority, impact, root cause, owner, SLA, escalation, evidence, comments, approval and closure. Workflow rules that raise, assign and escalate from the record: a critical integration failure becomes an incident with its owner told; a schema change becomes a review task for the data owner; a critical system with no owner becomes a governance task. Notifications in-app and by email.
Transform
Acquisitions as first-class objects on the same model: phase, Day-1 readiness, milestones and cutovers by workstream, integration health, fragmentation, risks. The acquisition module →