A Power BI production dashboard for output against plan
A Power BI production dashboard shows what the plant made, what it planned to make and where the two differ. Supervisors see their line and shift, planners see orders at risk, and managers see the week at a glance. The model reads from your production system and lives in your own Microsoft tenant, built by a small team.
- Output against plan
- Orders at risk
- Shift-by-shift view
Last updated
What does a Power BI production dashboard show?
The morning meeting on most shop floors asks three things. Did we hit yesterday's plan? If not, why? And what stands in the way today? Too often the answers come from a whiteboard and memory.
A production page brings the records to that meeting. It lists planned and actual quantity per line and shift. Gaps appear in color, and each gap links to the downtime and scrap logged in the same hours.
Planners read it differently. They care about orders rather than shifts. So a second page lists open production orders with quantity completed, quantity remaining and the due date. Then late orders surface before the customer calls.

Output measures for the daily production meeting
Six measures cover quantity, time and waste for most discrete and process plants.
Output against plan
Compare good units made with planned units for the same line and period, in units and as a gap.
Schedule attainment
Divide orders or quantities finished as scheduled by those scheduled. It shows how well the plan held.
Throughput
Count good units per hour of run time, so lines of different shift length compare fairly.
Cycle time
Measure the time to finish one unit or one order from start to end. Then compare it with the standard.
Scrap quantity
Sum units and material lost, split by reason. Because scrap consumes capacity, it belongs beside output.
Work in progress
Count units started but unfinished at each step. A growing pile shows where the flow stalls.
Where does production data for Power BI come from?
The ERP or manufacturing system holds the production orders: item, planned quantity, start date and due date. It also holds the reported output, usually as confirmations or receipts against each order. Those two tables form the heart of the model.
Shift detail often lives elsewhere. Some plants capture hourly counts in a floor system, while others use operator entries. We bring that in as a separate fact table at line and hour grain, and relate it to the same product, line and date tables. If supervisors need counts within minutes rather than after a refresh, see power bi real-time dashboards.
A shift calendar completes the picture. Night shifts cross midnight, so a calendar date alone puts half the shift on the wrong day. Therefore we add a production date and a shift key to every record during data preparation. After that, daily totals match what supervisors expect.
Mistakes in a Power BI production dashboard
These six faults cause most disagreements at the morning meeting.
- Splitting a night shift across two calendar days
- Comparing actuals with a plan someone changed afterwards
- Counting scrapped units as output
- Mixing units of measure across products in one total
- Reporting by posting date instead of production date
- Showing totals only, with no route to the order
How we build a Power BI production dashboard
Supervisors and planners join the demos, because they will use the pages daily.
Walk the process
First we learn how orders flow through your lines and where output gets reported.
Model orders and output
We load orders, confirmations and shift counts, add the shift calendar and relate everything in a star shape.
Check against the floor
Next we compare several days of figures with supervisors' own records and fix any mismatch.
Design for meeting and planning
Finally we build the shift page and the order page, then hand over the file with notes.
Production reporting in Power BI: common questions
Can a Power BI production dashboard read from our ERP?
In most cases, yes. Many ERP systems sit on a database Power BI can query, and some have a documented connector. Others need an API or a scheduled export. We confirm the route against Microsoft's connector list and your vendor's documentation. An on-premises database also needs a data gateway, which Microsoft provides.
How often should production data refresh in Power BI?
It depends on who reads the page. A refresh before each shift meeting suits most supervisors. Planners may want several refreshes through the day. The service supports scheduled refresh, with limits that depend on the license. For minute-by-minute screens, the floor system itself remains the right tool.
Can the page show several plants together?
Yes. A plant table lets leaders compare sites or open one. However, plants often use different item codes and shift patterns. So we first map products and calendars to a shared structure. Row-level security can then limit each plant manager to their own site while leaders see all of them.
Is this the same as an OEE report?
No, although they share data. A production page centers on quantity against plan and on orders. An effectiveness report centers on time losses per machine. Many plants want both. Because the two use the same machine, product and date tables, they can live in one model and link to each other.
How does an engagement begin?
With a free 30-minute assessment. We then send a written scope with fixed contents, and you decide. Power BI Agency is a division of Sataware Technologies, independent of Microsoft. We deliver online, reply within 2 hours and do not resell licenses.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.