Management dashboard projects at distribution companies tend to follow the same path. A BI tool is chosen, extraction jobs are built to pull data out of operational systems, a data warehouse is designed, and eventually a dashboard full of impressive charts appears. A few months later, two problems surface: the numbers on the dashboard stop matching the ones on the operational screens, and fewer and fewer people open it.
In this post we look at why it works better to produce management indicators from inside the operational data, to show each person only their own scope, and to deliver deviations to the people concerned without waiting for anyone to look at a dashboard.
The Hidden Cost of a Separate BI Layer
A separate BI tool brings a second copy of the data with it. Investment requests, preliminary projects, maintenance work orders and outages are created in the operational system; what the dashboard shows is a copy transferred at intervals. If a transfer runs late, or the meaning of a field changes, the two systems drift apart and meetings open with the question "which number is right?"
On top of that, every new indicator needs someone who understands both the operational system and the BI side. Metric definitions often end up buried in undocumented queries inside the BI tool, and the question of who calculates an indicator, and on what basis, goes unanswered.
Reading Data at the Source, and the Metric Catalog
The alternative is to produce indicators where the operational data lives. Then the "preliminary projects awaiting approval" figure on the dashboard and the figure on the preliminary project screen come from the same source, with no separate transfer and no separate reconciliation.
For this to work well, metrics have to be defined explicitly. A good metric catalog records what each indicator measures, which dimension it is broken down by, which filter limits it, its source and its unit. That way the definition belongs to the organization rather than to individuals.
Role-Based Scope: Everyone Sees Their Own Dashboard
At a distribution company, the general manager, a regional manager and a unit lead do not expect the same thing from a dashboard. Opening one dashboard to everyone carries two risks: data people are not authorized for becomes visible, and irrelevant cards drown out the indicator that matters.
The healthier approach is to tie the dashboard's scope to permissions. Users see only the provinces their department is authorized for, and the province and year filters work within that boundary. When each card is tied to its own permission, the same dashboard shows managers the full picture and regional teams their own area. Maintaining a single dashboard also saves each role from commissioning a dashboard project of its own.
Which Cards Answer a Management Question?
A dashboard with many cards is not necessarily a good dashboard. Each card should answer a concrete management question:
- Investment: What state are investment requests in, how is the trend moving, and how are they spread across districts?
- Projects: Which stages are projects waiting in, how many preliminary projects have been approved, and what is the drawing status?
- Customer applications: How are applications progressing?
- Maintenance: How are maintenance cost and average cost distributed by level, where do maintenance counts stand against the same month last year, and what does the monthly cost trend say?
Showing completion rates against the organization's own targets turns a card from a statistic into a performance indicator.
Why Waiting for Someone to Open the Dashboard Is Not Enough
Even the best-designed dashboard only works when it is opened. Managers' days fill up with meetings and field issues, and the habit of checking the dashboard fades over time. A deviation can sit visibly on a dashboard for weeks and keep growing until someone notices.
Material and tender processes are a good example. Financial progress falling behind physical progress, stock coverage dropping, or a tender group's total weight climbing higher than expected can be fixed with a simple correction when caught early. Caught late, it becomes a problem that moves the project schedule.
Threshold Monitoring and the Morning Summary: Let the Deviation Come to You
Here the logic is reversed: instead of the user going to the dashboard, the deviation comes to the user. Each monitoring rule gets a threshold, a list of recipients and the roles concerned. When a threshold is breached, an alert is raised and tracked as open or resolved, so follow-up on the same issue is not lost.
It also matters that alerts do not turn into a flood of individual emails. A single summary email at the start of the day does not scatter attention, and it makes clear what deserves priority that day. Managers know where things are drifting before they open the dashboard, over their morning coffee.
Conclusion: From Operational Data to a Management Dashboard with GeoEner Business Intelligence
GeoEner Business Intelligence is a metrics and indicators module built into GeoEner, with no need for a separate BI tool or data warehouse. Investment requests, preliminary projects, customer applications, maintenance work orders, outages and network inventory are read directly from the source, and each metric's key, category, source, unit and data strategy are visible in the Metric Catalog.
The 14-card overview dashboard filters by province and year, is limited to the provinces the user's department is authorized for, and ties each card to its own role permission. In the Monitoring Center, thresholds, recipients and roles are set for material financial and physical progress, stock coverage and total tender group weight; breaches are tracked as open or resolved, and a summary email goes to the people concerned every morning. Metric snapshots are taken every night and the monitoring evaluation runs every morning.
If you would like to see how you can follow management indicators straight from your own operational data, without adding a BI layer, get in touch and let us plan a demo.
