Sign in

Blog · Board and management reporting · Manufacturing

Power BI maintenance dashboard: cost and downtime

A maintenance dashboard compares maintenance spending with scheduled and unscheduled downtime by site. Work through a US manufacturer's monthly export, the denominator choices, and the checks that make the comparison usable.

The short answerA Power BI maintenance dashboard compares maintenance expenses, planned stoppages, and unplanned downtime across sites for the same period. Start with work-order costs and asset event logs, reconcile spending to the ledger, and divide downtime by a defined scheduled-hours base. Read cost and reliability together before deciding where to investigate or invest.

A Power BI maintenance dashboard should compare site spending with downtime on the same asset and reporting-period basis; a maintenance dashboard in Power BI is useful only when those definitions agree. Show planned and unplanned stoppages separately, then reconcile the expense totals before ranking sites.

Microsoft defines a Power BI dashboard as a single page of visualizations, with related reports supplying detail. The business task here is deciding which maintenance exceptions deserve investigation. Covirage is not affiliated with Microsoft, the maker of Power BI.

Start with the maintenance records you already have

Consider a US components manufacturer reviewing September 2026 at Dayton, Ohio, and Tulsa, Oklahoma. The maintenance manager brings a work-order expense export, an asset downtime log, and the production calendar. Finance supplies the maintenance expense balance for the same month.

Keep the original records separate until their totals are checked. Expense records need a work-order ID, asset, site, posting date, expense category, and amount in USD. The event log needs an event ID, asset, start and end times, and a planned or unplanned classification. The calendar supplies the scheduled hours for those assets.

The shared reporting unit is the site and month. A work order can have several expense lines and several stoppages. Matching every expense line to every event first would multiply both amounts and hours. Summarize each source to the agreed reporting unit before comparing the results.

For this example, scheduled asset-hours include planned maintenance windows within scheduled shifts. They exclude shifts when the equipment was never scheduled to operate. Two assets scheduled simultaneously contribute their hours separately; these are asset-hours, not elapsed hours on the clock.

A worked comparison of maintenance expense and downtime

The following site totals come from the three exports. Planned spending means expenses classified to planned maintenance work; reactive spending means expenses classified to repairs. Neither column includes capital equipment purchases.

| Site | Planned spending (USD) | Reactive spending (USD) | Scheduled asset-hours | Planned downtime (hours) | Unplanned downtime (hours) | |---|---:|---:|---:|---:|---:|---:| | Dayton | 12,000 | 18,000 | 1,000 | 40 | 60 | | Tulsa | 8,000 | 12,000 | 800 | 24 | 16 | | Total | 20,000 | 30,000 | 1,800 | 64 | 76 |

Use these definitions throughout the page:

Maintenance expense = Planned spending + Reactive spending
Downtime percentage = (Planned downtime + Unplanned downtime) / Scheduled asset-hours
Maintenance cost per scheduled asset-hour = Maintenance expense / Scheduled asset-hours

Site Maintenance expense (USD) Total downtime (hours) Downtime Unplanned downtime Cost per scheduled asset-hour (USD)
Dayton 30,000 100 10.00% 6.00% 30.00
Tulsa 20,000 40 5.00% 2.00% 25.00
Total 50,000 140 7.78% 4.22% 27.78

Dayton's downtime is (40 + 60) / 1,000 = 10.00%. Tulsa's is (24 + 16) / 800 = 5.00%. The combined figure is 140 / 1,800 = 7.78%, using the underlying hours rather than averaging the site percentages. Displayed percentages and unit costs are rounded to two decimal places; calculations retain full precision.

This is a maintenance comparison, so it stops short of measuring overall equipment effectiveness. Use the separate OEE dashboard example when the decision also needs production speed and quality, and the operations dashboard example for operating cost and throughput.

Prove the totals before interpreting the charts

The spending check is 20,000 + 30,000 = 50,000, which must also equal 30,000 + 20,000 across sites. Finance then matches that amount to the included maintenance expense accounts. Investigate timing differences, unmatched work orders, and expenses assigned to an unknown site before publishing the comparison.

The hours check is 64 + 76 = 140. Each event must fall inside the reporting month and the scheduled asset window. When two events overlap on the same asset, count the shared interval once. Otherwise downtime can exceed the time equipment was available to stop.

For an Excel check, Microsoft's SUMIFS function adds amounts meeting multiple criteria. If expense amounts are in C, sites in A, and the reporting month in B, the Dayton subtotal is:

=SUMIFS(C2:C1000,A2:A1000,"Dayton",B2:B1000,"September 2026")

That formula assumes the month labels are standardized text and that the range contains only the agreed maintenance expenses. A broader dashboard examples page can help place the checked maintenance totals in the management review without expanding this page into every operating measure.

Change one input: less unplanned downtime at Dayton

Now change only Dayton's unplanned downtime from 60 to 40 hours. Keep scheduled hours, planned downtime, and spending unchanged. This is a sensitivity test, not a claim that fewer stoppages automatically reduce booked expense.

Measure Original Changed case
Dayton unplanned downtime (hours) 60 40
Dayton total downtime (hours) 100 80
Dayton downtime 10.00% 8.00%
Company total downtime (hours) 140 120
Company downtime 7.78% 6.67%
Company maintenance expense (USD) 50,000 50,000

The changed case proves itself: 40 planned Dayton hours + 40 unplanned Dayton hours + 40 Tulsa hours = 120. Dividing by the unchanged 1,800 scheduled hours gives 6.67%. The company recovers 20 asset-hours, while maintenance expense remains $50,000. The maintenance manager can investigate what supported the improvement; finance should not book savings from recovered time alone.

Where it goes wrong

  • Using different calendars. A site excluding planned stops from scheduled hours cannot be compared directly with one including them.
  • Double counting event time. Several work orders can describe one physical stoppage. Deduplicate the affected asset intervals.
  • Treating purchasing as expense. A parts purchase, a parts issue, and a maintenance expense posting may describe different stages. Agree which amount the page measures.
  • Inferring causation from a ranking. More spending and more downtime can reflect asset condition or workload. They do not prove the maintenance team caused the problem.

Assign the maintenance manager to explain the largest stoppages and the controller to resolve spending differences. Keep an explicit next action beside each exception. For the surrounding choice of reporting approach, see Power BI alternatives.

Compare your own maintenance export in Covirage

Bring a sample of your own maintenance expense file, downtime export, or Google Sheet with the period and scheduled-hours definitions. Covirage maps the columns, and its tools compute and check the site comparisons; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring your file.

See Covirage for industrial manufacturers for the manufacturing context.

Questions people ask

Which measures belong on a maintenance dashboard?

Include maintenance spending, planned and unplanned downtime, scheduled asset-hours, downtime percentage, and maintenance cost per scheduled asset-hour. Separate expense categories and keep asset scope visible. Add other measures only when they help the maintenance manager decide what action to take.

Should planned maintenance count as downtime?

It can, provided the dashboard labels it separately and defines the denominator. This example includes planned maintenance within scheduled asset-hours. If your production calendar excludes those stops instead, use that convention consistently and avoid comparing the resulting percentage directly with this one.

Does lower maintenance spending mean better performance?

Lower spending can reflect fewer failures, postponed work, or different accounting timing. Compare it with downtime, open work orders, and the assets covered. A spending reduction alone does not establish a reliability improvement or prove that equipment needs less attention.