Building a data model for project-costing reporting

Problem

Project-costing reporting depends on bringing related financial and operational information into a form that can be analysed consistently. My role included building and maintaining a Power BI data model for project costing, margins, and operational KPI reporting.

Data

The work used internal business data. This public case study excludes source-system details, table and field names, screenshots, financial figures, and other identifying information.

Approach

I first needed to understand the reporting requirements and the data available to support project-level analysis. Requirements can evolve, so the model and reporting need to remain maintainable as user requests and source structures change.

I carried out data transformations and cleanup in Power BI Desktop, built the data model and dashboard, and configured dynamic row-level security using USERPRINCIPALNAME() for user-specific access. The public description stays at a high level; internal data sources, model design, role definitions, and access mapping are not shown.

Technology

Power BI data modelling and reporting.

Solution

The work contributed to a data model used to support project costing, margin reporting, and operational KPI reporting, with dynamic row-level security configured for user-specific access. No internal visuals, data, or model diagrams are included here.

Result

The model and reporting work are the deliverables described in this case study. No quantified business impact is claimed.

Learning

The experience strengthened my understanding that practical modelling involves more than connecting tables. Requirements, source discovery, transformations, ongoing maintenance, and access security all affect whether reporting remains useful and dependable.