PT EN
Back to site

Use Case — Governed BI over Multiple Sources

Scenario

An executive board needs reliable dashboards that cross-reference data from a transactional Postgres, recurring spreadsheets and a relationship graph — without each analyst creating their own copy of the data in an isolated tool.

Flow on the platform

  1. Register the connections once. The administrator (or the analyst, depending on permission) registers each source in the central connection manager — see Connections. Credentials stay in the vault; the same connection is reused by all flows.
  2. Let the catalog do the work. When the connection is created, automatic cataloging (ACOC) scans schemas, collects quality metrics and publishes the datasets to the Knowledge Catalog — nothing stays "off the radar" of governance (Data Governance).
  3. Prepare the semantic model. In DATTA Prep, the analyst combines the sources (joins, filters, calculated columns) without writing code — see DATTA Prep. For advanced logic, the DATTAX language covers measures and transformations.
  4. Build and publish dashboards. In DATTA BI, the analyst assembles the visuals with cross-filter and drilldown — see DATTA BI — and publishes to the team's workspace in Panels. Scheduled refresh keeps the data up to date (Refresh Scheduler).
  5. Explore beyond the dashboard. Ad-hoc questions in natural language go through the Intelligent Query Layer, which translates them into federated SQL with safety — see SIQL.

Outcome

  • A single truth: connections, datasets and models cataloged and governed, with end-to-end lineage.
  • Dashboards with a unified visual identity, responsive and with automatic refresh — no exporting CSV to an external tool.
  • New questions do not require a new BI project: natural language over the same governed model.