Data & Analytics · CHG Global (World Balance Philippines)

Power BI Implementation & Unified Reporting

A Power BI implementation unifying SAP, Salesforce and spreadsheet data into one analytics platform, with standardized dashboards and user training.

Three sources unifiedMeasured Result
SKU and location reportingMeasured Result
Delivered without operational disruptionMeasured Result
Illustration: a database, a cloud and a spreadsheet feeding one dashboard of charts, with an analyst presenting it.
The project

What changed, and what came of it

The same client as the SAP HANA engagement. Reporting was assembled by hand from three systems that did not agree with each other. We consolidated them into a single analytics platform with standardized dashboards, so the argument moved from whose number is right to what the number means.

Before

Data was disconnected across systems, reporting was slow, and visibility across departments was limited. Teams built their own reports in spreadsheets, which meant the same question got different answers depending on who asked it and when. The requirement was to unify reporting and enable real-time analytics without disrupting daily operations.

What we built

We led a Power BI implementation integrating data from SAP, Salesforce and Excel into a centralized analytics platform, with standardized dashboards, optimized data models and training sessions to support adoption.

Measured Result
Three sources unified

SAP, Salesforce and Excel data consolidated into one analytics platform.

Measured Result
SKU and location reporting

Product-level performance, markdown and location sales analysis available from one place.

Measured Result
Delivered without operational disruption

Integration was read-only and refreshes scheduled so daily operations were unaffected.

Each outcome carries the label that describes what kind of claim it is. We never present a target as a measured result — see the Ledger and our claims policy.

The system

What the system does

  • Multi-source integrationSAP, Salesforce and spreadsheet sources brought into one platform.
  • Standardized dashboardsOne agreed definition per measure, presented consistently across departments.
  • Optimised data modelsModels built for query performance rather than mirroring source structures.
  • SKU performanceProduct-level performance and markdown analysis.
  • Location performanceSales performance by location.
  • User trainingTraining sessions run as part of delivery to support adoption.
Architecture

How it fits together

A layer-level view. We do not publish hostnames, addresses, credentials, firewall rules or topology detail for systems in production.

Presentation
Executive dashboardsDepartmental reportsSelf-service exploration
Semantic model
Standardized measuresOptimised data models
Integration
SAP extractSalesforce extractSpreadsheet ingestion
Sources
SAPSalesforceExcel
Security and rollout

How it is protected, and how it went live

Controls in the delivered system

Delivered under ITDC’s information security practices, which follow ISO/IEC 27001 and NIST guidance.
Role-based access so departments see the data their function requires.
Read-only integration with source systems; the platform does not write back.
Measure definitions held centrally rather than re-implemented per report.
Access to the underlying models separated from access to published dashboards.
Refresh schedules designed to avoid load on source systems during operating hours.

High-level controls only. Detailed security design is shared under NDA with the client organization, not published.

How it was rolled out

  1. Source assessmentThe three source systems assessed for structure, quality and refresh constraints.
  2. Model buildData models built and measures standardized with the business.
  3. Dashboard deliveryStandardized dashboards delivered by department.
  4. Training and adoptionTraining sessions run so the platform was used rather than merely delivered.
Questions

Frequently asked questions

Because each team built its own reports in spreadsheets, and each defined the measure slightly differently. The same question genuinely returned different answers depending on who was asked — which is a definition problem before it is a tooling problem.

SAP, Salesforce and spreadsheet data, brought into one Power BI platform with standardised dashboards and optimised data models behind them. The modelling is the durable part: it is what makes SKU and location performance comparable across sources rather than merely displayed together.

Yes, and it is not incidental. A dashboard nobody trusts or knows how to read is replaced by a spreadsheet within a quarter, which is exactly the situation the project existed to end. Adoption is the binding constraint on analytics work far more often than the technology is.

No. It sits above SAP and the other sources, which is what lets a single report span systems that do not otherwise talk to each other. Operational reporting inside SAP continues to serve the transactional questions it is designed for.

Let's talk

Planning a similar project?

Tell us the organization, the process and the constraint you are working against. We can help shape the architecture, the implementation approach and the next step.