Data Lag Eliminated
2-hour morning data preparation window replaced with a live dashboard refreshing every 15 minutes from the TMS SQL database - managers see current state, not this morning's snapshot.
Case study
Real-Time Fleet and Delivery Visibility: Power BI Operations Dashboard for a Regional Logistics Operator
A regional logistics company started every day two hours behind - operations managers rebuilt their daily briefing from five Excel files before they could make any decisions. We replaced the manual process with a live Power BI dashboard that refreshes from the TMS database every 15 minutes.
Daily Ops Prep Hours Saved
2 hours per day of manual report assembly across 5 Excel files eliminated - operations manager and two regional coordinators recover 6 staff-hours daily.
Excel Reports Consolidated
5 separate daily Excel reports - fleet utilisation, delivery performance, driver KPIs, customer SLA status, and exception log - replaced by a single Power BI dashboard with drill-down.
Fleet Utilisation Visibility
Fleet utilisation rate visible for the first time as a real-time metric - previously calculated weekly from a manual asset log. Now live and filterable by vehicle type and region.
Delivery Exceptions Escalated
Automated Power BI alerts fire when delivery exception rate crosses threshold - operations manager notified before the customer calls, not after the end-of-day report.
First-Year ROI
220% - daily ops preparation time recovered, exception response time improved, and one major customer SLA penalty avoided by catching a delivery pattern issue 3 days earlier than the old process would have.
The Operation Before the Dashboard
This regional logistics operator runs a fleet of 60+ vehicles across three distribution hubs serving retail and manufacturing customers on contracted SLA delivery windows. Every morning, the operations manager and two regional coordinators spent the first two hours of their day building a picture of where things stood.
Five Excel files were involved: a fleet utilisation tracker updated from the vehicle management system, a delivery performance report pulled from the TMS, a driver KPI sheet maintained by the team leaders, a customer SLA status file updated by the commercial team, and a delivery exception log compiled from driver notes and customer calls.
The five files were produced by different people at different times. The earliest was ready at 7:30am. The last was sometimes still being updated at 10am. Operations decisions made at the 8am briefing were made on yesterday's data.
What We Built
We deployed a Power BI dashboard connected directly to the TMS SQL Server database via DirectQuery. The dashboard auto-refreshes every 15 minutes in Power BI Service, giving the operations team live fleet and delivery data without any manual file preparation.
The dashboard has four pages: an operations overview, a fleet utilisation deep-dive, a delivery performance analysis, and a driver KPI scorecard. Each page is designed for a specific role - the operations overview is the 8am briefing in one screen; the fleet page is for the fleet manager; the driver scorecard is for team leaders.
Row-level security limits what each user sees. Drivers access their personal KPIs via the Power BI mobile app. Regional coordinators see their hub's data. The operations director sees the full fleet.
We ran a metric definition workshop before writing a single DAX measure. The biggest obstacle was not the technical build - it was agreeing what "on-time" meant across five previously independent definitions. The workshop produced a documented KPI dictionary that now governs all reporting across the business.
Dashboard Capabilities
Live Operations Overview
Real-time summary of active jobs, vehicles in transit, current delivery exception rate, and SLA compliance - refreshed every 15 minutes from TMS SQL database.
Fleet Utilisation Analysis
Fleet utilisation by vehicle type, route, and hub. Idle time, kilometres per day, and load factor visible at individual vehicle level. First time this data has been consolidated in one view.
Delivery Performance Tracking
On-time delivery rate by customer, route, and driver against SLA windows. Period trend charts show performance trajectory - enabling proactive customer conversations rather than reactive ones.
Driver KPI Scorecard
Per-driver view of jobs completed, on-time rate, average load, and customer feedback score. Accessible via Power BI mobile app. Row-level security limits each driver to their own data.
Automated Exception Alerts
Power BI Data Alerts fire when exception rate crosses the defined threshold - email notification to operations manager and regional coordinators before end of day, not after.
Customer SLA Compliance View
Per-customer SLA performance against contracted windows. Commercial team uses this page for contract review meetings - same data, no manual preparation.
After Go-Live: What Changed
The 8am operations briefing now runs from one screen. Everyone in the room sees the same live data. The two-hour morning preparation window no longer exists - the dashboard is ready when the first person arrives.
Three months after deployment, the dashboard flagged a delivery performance pattern on one regional route that was trending toward SLA breach. The operations team adjusted the route plan before the breach occurred and before the customer noticed the trend. Under the old process, the same pattern would have appeared in the weekly Excel analysis - after the breach had already happened and a penalty conversation had started.
The daily ops admin role was redeployed to exception resolution and customer communication rather than report assembly. The operations manager uses the recovered two hours for forward planning.
“We used to make decisions at the 8am briefing based on yesterday's numbers. Now the dashboard is live and everyone in the room is looking at the same thing. The first time we caught a delivery pattern going wrong before it hit the customer - and avoided a penalty - that paid for the whole project.
Tech Stack
Power BI Service - cloud-hosted dashboard with 15-minute scheduled refresh and automated Data Alerts
DirectQuery - live SQL Server connection to TMS database; no import cache, no stale data
DAX measures - KPI calculations including on-time delivery, utilisation rate, and exception flag logic
Row-level security - role-based data filtering; drivers see personal KPIs, managers see full fleet
Power BI mobile app - driver-facing scorecard accessible on-the-go without desktop access
KPI dictionary - documented metric definitions agreed across operations, commercial, and CS teams
Frequently Asked Questions
How does Power BI connect to the operational data in real time?
We configured a DirectQuery connection from Power BI to the SQL Server database that the TMS writes to. DirectQuery means Power BI reads the current database state every time a dashboard element is loaded - there is no import cache to refresh. For this client, the dashboard auto-refreshes every 15 minutes via a scheduled dataset refresh in Power BI Service. Critical KPIs like active jobs in transit and delivery exceptions update without the operations manager clicking anything.
What was involved in migrating the existing Excel reporting into Power BI?
The main work was not moving the data - it was defining consistent metric definitions. Five Excel files produced five slightly different versions of "on-time delivery." One measured against scheduled departure, another against promised delivery time, another against a customer SLA window. We ran a metric definition workshop with the operations, commercial, and customer service leads to agree one definition for each KPI. That agreement was the hardest part. The Power BI build itself took about three weeks once the definitions were locked.
Can drivers or field staff see their own performance in the dashboard?
Yes - we built a driver-level view with row-level security so each driver sees only their own KPIs: jobs completed, on-time rate, average load, and customer feedback scores. Driver dashboards are accessed via the Power BI mobile app. Regional managers see their full team; the operations director sees the whole fleet. No separate report needed - same dashboard, different data scope based on the user's login.
How does the delivery exception escalation work?
Power BI Alerts are configured on the delivery exception count measure. When exceptions cross a threshold - currently set at 5% of active jobs - Power BI sends an email alert to the operations manager and the relevant regional coordinator. The alert includes the current exception count and a link directly to the exceptions drill-down page in the dashboard. This replaced the end-of-day exception report that the operations admin used to compile manually.
Next step
Want similar results in your operations?
Book an Automation Opportunity Assessment. We map workflows and scope a practical build plan.
- No Onsite Visit Required
- No Technical Specification Required
- Assessment Before Commitment
- Clear Scope Before Work Begins
Questions before you book? Speak with our team at +1 385 386 3860
