Tableau and Power BI: administration, migration, and the semantic layer.

What this covers

Two platforms, run as one estate rather than two separate tool choices:

• Tableau Server administration — sites, projects, permissions, and extract refresh schedules, run as a managed platform rather than a collection of individually published workbooks.
• Tableau Online administration — the same discipline where the platform is hosted rather than self-managed.
• Migration — consolidating scattered Desktop-only workbooks onto a managed Server or Online site, or moving between sites, without losing the calculations and permissions that took years to accumulate.
• The semantic layer — data source definitions, calculated fields and row-level security defined once, upstream of the workbook, so two dashboards built by two different people still agree.
• Power BI — semantic models and row-level security on the same modelled warehouse, where Power BI is the tool your team already knows.
• SQL Server — as the warehouse or mart storage both tools read from.

company delivery history · founder-asserted · 18 Aug 2026

We are not a Tableau or Power BI reseller. You hold the licences directly — with Tableau and with Microsoft — and we administer, migrate and build on top of what you already have.

Scorecards and KPI reporting

Once a model exists, publishing an agreed set of measures on a schedule is the last mile of this work, not a separate practice — scorecards, performance metrics and KPI reporting sit on top of the same warehouse and the same definitions as everything else on this page.

company delivery history · founder-asserted · 18 Aug 2026

How a number gets from a source system to a scorecard

The diagram above is the summary. Here is the same path, spelled out:

1. Source systems. ERP, POS, inventory, or whatever systems of record the operation actually runs on — the same sources a reconciliation or a warehouse project reads from.
2. Extract. A scheduled pull, not a manual export somebody remembers to run.
3. Modelled warehouse. The same warehouse layer this silo builds for any reporting project — one set of definitions, not a parallel copy built inside the BI tool.
4. Tableau Server. Reads the model, publishes and refreshes workbooks against it, and enforces permissions and row-level security at the platform level.
5. Tableau Online. The same administration model, hosted rather than self-managed.
6. Power BI. Reads the same modelled warehouse, where Power BI is the tool your team already knows — not a second, disagreeing model.
7. Scorecard and KPI set. Published on a schedule, with the definitions agreed once in the model rather than argued over in the meeting where the number gets shown.

The BI layer — Tableau or Power BI — reads that model. It does not write back to the source systems, and it is not where the definitions live.

Access to a client's Tableau or Power BI tenant during this work follows the same standard we hold ourselves to everywhere else — named individual accounts, least privilege, and logged, time-bound elevation. See Trust & Security.

This is one part of Data Engineering & Analytics.