Skip to main content

Anonymized engagement summary: urgent fix of segment-level backlog errors in a 27-table CARR/ARR Power BI model for a healthcare technology company (2025)

Anonymized engagement summaryHealthcare technology company · 2025

Opening answer. In 2025 a healthcare technology company engaged EPC Group for an urgent Power BI fix. The company's contracted and annual recurring revenue (CARR/ARR) model had started showing wrong backlog values by product segment after a dashboard update earlier that year, while the total backlog stayed correct. The engagement traces the likely cause to:

  • complex relationships across 27 tables
  • reliance on many measures
  • possible formula inconsistencies

The scope is to find the root cause, fix the DAX and relationships, prevent a repeat, document the fix and hand it over to the company's own 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

ItemScope
OrganizationA healthcare technology company
SymptomAfter a dashboard update, backlog values by product segment were wrong while the total backlog was right
Suspected causeComplex relationships across a 27-table model, many dependent measures, possible formula inconsistencies
UrgencyTime-sensitive; subject-matter experts assigned to the backlog issue first
Fix scopeTroubleshoot and fix the segmentation errors; review and optimize the DAX so results hold across product segments; remove unnecessary relationships in the 27-table model; add measures that prevent future calculation breakdowns
Reporting scopeA root-cause analysis; best-practice recommendations for data modelling and calculations; a view on restructuring for performance, automation and self-service; the feasibility of moving the backlog calculations to Microsoft Fabric, and of Copilot for Power BI later
Hand-overReal-time walkthroughs and documentation for the company's IT staff on the changes and how to maintain the model; activity reports
FlexibilityRemaining time usable for further Power BI support — dashboard enhancements, report optimization and data-model work

Not reported: the specific defect found, how long the fix took, and whether the Fabric recommendation was taken up.

Approach and artifacts

Totals right, segments wrong, is a model problem. When a grand total reconciles but its breakdown does not, the arithmetic is usually fine and the filter path is not. The engagement therefore starts with the relationships and measures, not the visuals:

  • an in-depth assessment of the CARR/ARR backlog calculations
  • the root cause of the segment-level discrepancy
  • the table relationships and data structure, looking for simplification

Fix, then make it hard to break again. Corrected DAX and simplified relationships come with measures intended to stop the same breakdown recurring. A root-cause report records what failed and what was changed, so the finance team is not dependent on memory the next time the model is touched.

Advice alongside the fix. The Microsoft Fabric and Copilot for Power BI recommendations are given as advice alongside the work, so the urgent fix gets the time it needs.

What EPC Group delivered and what is not claimed

ClaimBasisStatus
The company contracted EPC Group to diagnose and fix the CARR/ARR backlog errorsEPC engagement recordContracted (EPC-reported)
The defect was fixed, a root-cause report issued, or knowledge transfer heldNot reportedNot claimed

Related services

Power BI consulting · All case studies · Talk to a senior architect

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Related service: Power BI Admin & Governance Support Services

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2025-ANON-HTECH-PBIRESCUE · Published under the anonymized-engagement rule.

AI assistant — not a human