Anonymized engagement summary: Power BI weld quality and project-controls reporting, rebuilt on Microsoft Fabric, for an industrial construction contractor (2026)
Anonymized engagement summaryIndustrial construction contractor · 2026
Opening answer. An industrial construction contractor runs its weld quality (QA/QC) and project-controls reporting in Power BI. The reports draw on two outside systems, a weld-tracking system and a project-controls system, through an Azure Synapse data warehouse. In 2026 EPC Group:
- rebuilt and reconciled the Power BI reports on a warehouse connected end to end
- carried new fields through the weld data path
- moved both integrations from Azure Synapse to a Microsoft Fabric warehouse
- set up access and release management for the reporting team
This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.
Problem and scope
| Item | Scope |
|---|---|
| Organization | An industrial construction contractor |
| Situation | Weld, welder and inspection data from a weld-tracking system and budget data from a project-controls system, integrated through an Azure Synapse warehouse feeding Power BI. A legacy data warehouse was being phased out, a job-naming change was underway across the estate, and reports needed new fields |
| Workstreams | The two data integrations; the migration of both from Azure Synapse to Microsoft Fabric; the Power BI reporting estate on top of them |
| Reporting assets | Six built, migrated or rebuilt: a QA/QC report, an executive report, an audit report, a PMO weld dashboard, a weld-data report and a project control budget allocation report |
Not reported: user counts, data volumes, and any change in inspection or project-control outcomes attributable to the reporting.
Approach and artifacts
Fix the warehouse before the report. When the client asked for joint location on the reports, the field could not simply be added in Power BI. It was carried from the weld-tracking source through:
- the configuration query and staging
- the weld dimension
- the stored procedures and pipelines
- the reporting layer
A weld classification field went the same way. A new defect column followed later, through staging, the inspection fact table, stored procedures and pipelines, and was then replicated into Fabric.
Rebuild, then reconcile. The warehouse was connected end to end first. The weld, welder and inspection datasets were validated against source in sequence, and the QA/QC report was rebuilt: relationships, DAX logic, validation, then publish and functional checks. The executive report was then reconciled against the QA/QC report, and all three major reports were confirmed to match. Refresh failures were diagnosed and fixed in the same period. When the client raised discrepancies — inspection counts, combined versus classified welds, weld-inch totals — each was worked against the client's verified numbers and closed with the fix confirmed.
Synapse to Fabric without stopping the reports. The Fabric warehouse was provisioned. Both integrations' schemas and stored procedures were migrated, with staging, dimension and fact pipelines built and tested end to end. Fabric stored-procedure compatibility issues were resolved at each stage. Capacity was procured and assigned, and a target-state architecture covering both integrations and future sources was issued to the client. Changes made in Synapse during the transition were replicated into Fabric.
A third-party dependency, handled in the open. The project-controls integration needed view definitions that turned out to be encrypted and permission-restricted. EPC Group established that and re-raised the request with the client's vendor, and the definitions arrived later in the engagement. Once they did, five more control-budget tables were staged and new KPI columns were added to the control-budget fact table for the PMO.
Access and release management. A Power BI deployment pipeline was proposed and tested across three stages with a dedicated workspace. A service principal and security group were created for warehouse access, tested through Power BI and handed to the reporting team. When a weld dashboard went blank, the cause was traced to a pipeline failure, fixed, and documented in a root-cause analysis.
Work products delivered (EPC-reported):
- Written response to the client's year-end priorities (legacy warehouse phase-out, cost management, dashboard validation sequence)
- Control-budget dimensional model review with the PMO and Project Controls
- Rebuilt QA/QC, executive and audit reports; three-report reconciliation
- Fabric migration strategy, then the Fabric architecture issued to the client
- Fabric staging, dimension and fact pipelines, tested end to end
- Power BI delivery report; deployment-pipeline proposal
- Dashboard outage root-cause analysis; warehouse service principal and security group
- PMO weld dashboard layout approved after client review rounds; self-service sandbox walkthrough
What EPC Group delivered and what is not claimed
| Claim | Basis | Status |
|---|---|---|
| Six reporting assets built, migrated or rebuilt and validated against source | Delivery record | Delivered (EPC-reported) |
| The three major reports reconciled against one another and confirmed to match | EPC delivery record | Delivered (EPC-reported) |
| Both integrations built and tested end to end in a Fabric warehouse | EPC delivery record | Delivered (EPC-reported) |
| PMO weld dashboard layout approved by the client | Client correspondence on file (2026) | On file (EPC-reported) |
| Business outcomes such as fewer weld defects or faster reporting | Not reported | Not claimed |
Related services
Power BI consulting · Microsoft Fabric consulting · All case studies · Talk to a senior architect
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Related service: Enterprise Azure Analytics Platform
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2026-ANON-CONSTR-PBIFABRIC · Published under the anonymized-engagement rule.