AI Executive Office — CXO Assistant Platform (On-Premises)  ·  View 09 of 30  ·  3 · Structure

Integration Catalogue

Every way the platform touches another system, with protocol, cadence and direction — including the two it is allowed to write to.

Editable source SVG draw.io All views
Consumers Mattermost app Executive web Tenant console Audit export Superset Integration layer Kong Gateway north–south Airflow + dbt batch + CDC Kafka event in Camunda + Camel action out Edge collector DMZ reach Source and target systems ERP and finance Procurement Projects HR and CRM Supply chain Document estate Workflow engine Chat and email bot API HTTPS · SSE admin API signed same measures OData CDC REST r/w REST hourly nightly events delta crawl approved SMTP · webhook Integration Catalogue — Every Interface In and Out Application we own External / third party Interface / broker Queue / topic synchronous batch event / async Fourteen interfaces, four cadences. Mobile shares the web contract; the existing lake is registered as an external Iceberg catalogue rather than copied. Only procurement and the workflow engine are written to, and only after an approval. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Read integrations are pulled on a declared cadence rather than pushed. A source that pushes is welcome to, but the platform never depends on it, because a missing push is invisible and a missing pull is an alert
  • The existing lake is registered as an external Iceberg or Hive catalogue and queried in place rather than copied. Copying a customer's warehouse into the platform doubles the storage footprint and creates a second version of the truth
  • Writes exist on exactly two interfaces. Every other arrow out is a notification
  • MCP does not appear in this catalogue and that is deliberate: it is how the model reaches a tool, not how the platform reaches a source system. An MCP server still calls SAP over OData like anything else

Numbers

  • Fourteen interfaces at go-live; the prototype takes three (ERP/finance, procurement, projects)
  • Cadences: seconds (events), 15 minutes (finance CDC), hourly (projects), 4-hourly (documents), nightly (HR, CRM, market)
  • Each interface carries a freshness contract, and the answer states which one it used

Risks

  • Legacy public-sector ERPs frequently have no CDC capability. The fallback is a nightly full extract, which changes what "what changed since yesterday?" can honestly mean — and the answer must say so
  • The workflow engine write is the highest-blast-radius interface in the platform. It is the one with a dedicated connector identity and a re-check at execution time (view 20)
◀  Container Architecture All views Multi-Tenancy and Isolation  ▶
Solution Architecture v1.1 · fully on-premise, open source, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0909-integration-catalogue