From hand-built reports to one Microsoft Fabric data platform

Reports built by hand from 6 separate systems

CDD's information sat in 6 places: Paycor, Blackbaud, Setworks, Relias, When I Work and Excel. Reports were built by hand from exports and spreadsheets, so different teams could get different numbers for the same KPI. Executives and operations managers each needed their own view, and CDD wanted to run the platform itself after handover.

Built in layers, then handed over

1. 1
   Week 1

   KPI workshops

   Ran requirements and KPI workshops to agree the business rules and what each dashboard had to show.

2. 2

   Pipelines

   Built reusable Fabric Data Factory pipelines that pull from each system's API or exports, with incremental loads, monitoring and logging.

3. 3

   OneLake zones

   Organized OneLake into raw, curated and business-ready zones (bronze, silver and gold) feeding an enterprise data warehouse.

4. 4

   Shared models

   Built shared dimensions, semantic models and a data dictionary, so every report uses the same definitions.

5. 5

   Dashboards and handover

   Delivered the management and operational dashboards, tested and deployed them, then ran documentation and knowledge-transfer sessions.

One trusted source for finance, workforce and operations

CDD now has one governed source for finance, compliance, workforce, staffing and occupancy reporting, with KPI definitions every team shares. New systems can join through the same pipeline pattern without a redesign, and CDD's own team took over the pipelines, models and reports at handover.

• 6 systems feeding one governed platform
• KPI definitions every team shares
• Management and operational dashboards
• CDD's own team running it after handover

• Microsoft Fabric
• Data Factory
• OneLake
• Power BI
• Semantic models