Dataracity
Construction · USA · Microsoft Fabric

Unifying six disconnected systems into one governed analytics platform

Six siloed systems unified into a single governed Fabric platform — consistent KPIs, reliable reporting, and issues caught before users see them.

IndustryConstruction
Company201–500 employees
CountryUnited States
FrameworkSTEAM
Results
6Systems unifiedFinance, projects, timesheets, budgets, operations
100+KPIs built into the modelConsistent across every report
1Enterprise semantic modelOne shared version of the truth
0Manual reconciliations by designCleansed and reconciled in the platform
Software used
Microsoft FabricAnalytics platformSQLTransformation logicPower BIReporting and self-service
Related services
The migration, move by move

Six systems in, one governed platform out.

Seven moves took finance, projects, timesheets, budgets, and operations from six disconnected systems to a single Fabric platform the whole business reports from. Follow the pipe.

Scroll to run the migration
Where it startedSix disconnected systems
01
01The challenge · Six systems, six truths

Every department reported off its own extract.

Six independent systems covered finance, project management, timesheets, budgets, and operations, and each department reported off its own extract. There was no central version of the truth for project or financial KPIs.

Six systems, no shared modelEach department on its own extractsNo agreed figures for project or financial KPIs
Before · six independent systemsFragmented
Finance
Project management
Timesheets
Budgets
Operations
Reporting extracts
Six copies of the numbers, none authoritative

Each system produced its own extract. No central version of the truth.

02
02The context · What it cost the business

Failures went unexplained and reconciliation went by hand.

Data issues and refresh failures happened often with no visibility into root cause, and the gaps between systems were closed by hand. Business users couldn’t self-serve, and leadership had no single view of project performance, burn rate, or budget health.

Refresh failures with no root-cause visibilityManual reconciliations across systemsNo leadership view of burn rate or budget health
Before · what it costNo visibility
Refresh failuresno root cause
Cross-system reconciliationmanual
Business self-serviceblocked
Burn rate and budget healthno single view

Failures were discovered downstream, and the gaps were closed by hand.

03
03The approach · Governed foundation

One governed architecture across ingestion, cleansing, and business logic.

The analytics foundation was rebuilt on Microsoft Fabric using our STEAM framework — a governed medallion architecture across ingestion, cleansing, and gold-layer business logic, ingesting and unifying all six systems in one place.

Medallion architecture: ingest, cleanse, serveBusiness logic held in the gold layerAll six systems landing in one platform
Approach · governed medallion on FabricSTEAM-aligned
Ingest
Six sources landedFinance, projects, timesheets, budgets, operations
Cleanse
Conformed and reconciledStructured transformations with quality checks
Gold
Business logicEnterprise model behind every report
Governance applied across the whole platform, not per report

Ingestion, cleansing, and business logic separated — all six systems in one place.

04
04The approach · The enterprise model

A central star schema every report is built on.

A centralized star schema became the enterprise model for reporting, with over 100 KPIs defined directly in it — so projects, budgets, hours, and financials are measured the same way everywhere.

Central star schema as the enterprise model100+ KPIs defined once, reused everywhereProjects, budgets, hours, and financials reconciled
Approach · central star schemaOne model
FactProjects · budgets · hours · financials
ProjectCost codeCalendarEmployeeClientDepartment

Over 100 KPIs defined once and reused everywhere.

05
05The approach · Trust in the numbers

Structured transformations, with checks and lineage you can follow.

Transformation logic was structured and instrumented — quality checks at each step and transparent lineage from source system to report, so any figure can be traced back to where it came from.

Quality checks built into each transformationTransparent lineage, source to reportReconciled data across all six systems
Approach · quality and lineageTraceable
01SourceSix systems, as captured
02TransformStructured SQL logic
03CheckQuality rules per step
04PublishReconciled, lineage intact
Transparent lineage end to end

Any figure can be traced back to the system it came from.

06
06The approach · Observability and alerting

The BI team hears about failures before users do.

Run statistics, row counts, and loading dashboards made pipeline health visible, and automated alerts notify the BI team of failures, delays, and anomalies before users notice them.

Run statistics, row counts, load dashboardsAutomated alerts on failures, delays, anomaliesIssues visible before users notice
Approach · operational observabilityAlerting on
Run statistics per pipelinetracked
Row counts on every loadchecked
Loading dashboards for the BI teamlive
Alerts on failures, delays, anomaliesautomated

Issues surface early — troubleshooting starts before a ticket is raised.

07
07The solution · Handed to the business

A clean semantic model analysts can build on themselves.

A governed semantic model was exposed to analysts and business teams, designed for self-service rather than extract requests — removing manual Excel work and reducing dependency on IT.

Clean semantic model for analystsManual Excel work removedReduced dependency on IT
Solution · governed self-serviceHanded over
Model
Clean semantic layerExposed to analysts and business teams
Excel
Manual work removedNo more extract-and-rebuild cycles
IT
Dependency reducedReporting no longer queued behind IT

Analysts build their own reporting on a model the business trusts.

Where it landedOne governed Fabric platform
Building an enterprise-grade business intelligence platform is no small undertaking, and finding a partner who can match both the technical complexity and the operational reality of your business is even harder. Dataracity did both. They navigated integration challenges across six disparate systems without losing sight of the bigger picture, and their command of the Microsoft stack meant we weren't spending cycles educating them on fundamentals. What set them apart was the strategic layer they brought — they weren't just executing tasks, they were thinking alongside me about what this platform needed to do long-term. We now have end-to-end operational metrics with clarity we've never had before — leadership can directly connect that data to P&L performance in real time. I would recommend Dataracity without hesitation.
Arthur L. Burris Jr.Arthur L. Burris Jr.Director, Enterprise Architecture, BI & Process Innovation
The people who built it

Team responsible.

A small delivery team, named and accountable from kickoff to go-live.

  • Luke Matthews, Co-Founder, Head of Project Delivery & Data Architecture at Dataracity

    Luke Matthews

    Co-Founder, Head of Project Delivery & Data Architecture

  • Amanda Buthelezi, Co-Founder, Project Lead (BI & Data Strategy) at Dataracity

    Amanda Buthelezi

    Co-Founder, Project Lead (BI & Data Strategy)

  • Boris Keckarovski, Data Engineer & Business Intelligence Consultant at Dataracity

    Boris Keckarovski

    Data Engineer & Business Intelligence Consultant

  • Filip Bukvić, Business Intelligence Consultant at Dataracity

    Filip Bukvić

    Business Intelligence Consultant

How the STEAM framework shapes a buildOur delivery framework, end to end
How many systems are you reporting from?

One governed model beats six sets of numbers.

Bring us your systems and the KPIs that never agree. We'll map the unified architecture, the enterprise model, and the path to self-service in one conversation.

30 minutes No obligation Microsoft Fabric partners