Review downtime Pareto

The Pareto for Downtime dashboard answers one question: where did the hours go? It ranks every downtime reason by the total time lost across your machines, so you can see the small number of causes responsible for most of your stoppages and act on them first. Downtime is any period a machine was stopped instead of producing. A Pareto is a chart that sorts those causes from largest to smallest and draws a running cumulative line on top, so the "vital few" reasons that make up most of the loss stand out from the "trivial many".

Use this dashboard when you are planning maintenance, running a continuous-improvement review, or preparing for a shift huddle and need a defensible, ranked list of what to fix. Every number is calculated on the server for the exact time range, machine, and reason you have in view, and the whole page is cross-filterable: click a reason or a machine and the entire dashboard narrows to it. Because the scope lives in the page address, a view you build is shareable , send the link and a colleague sees the same filtered picture.

Before you startCopy Anchor Link

You need a few things in place for this dashboard to show real numbers:

• Permission to open this dashboard. Any one of these permissions is enough: View OEE analytics (analytics.view_oee), View OEE events (oee_events.view), or View production jobs (production_jobs.view). OEE stands for Overall Equipment Effectiveness, Bulk's measure of how much of a machine's available time turned into good output. The built-in Dashboards, Dashboards viewer, Manager, Operator, Tablet user, Invoicing, Entity admin, and Super user roles already include one of them. If the page says you do not have access, it lists these same permissions. Grant any one of them. You do not need all three.
• OEE downtime tracking enabled on at least one asset type. An asset type is the template that defines a class of machine (for example "CNC press"). Downtime tracking is switched on per asset type. If no asset type has it enabled, the page shows "No downtime tracking configured" instead of a chart.
• Downtime reasons configured. Each reason (for example "Tool change" or "Material wait") carries an OEE loss category and a planned-or-unplanned setting. Reasons set to the planned-stop loss type count as Planned downtime; everything else counts as Unplanned. Events recorded without a reason are grouped as Uncategorized.
• Recorded downtime events. The rankings are built from actual downtime events logged against your assets. With tracking on but no events in the window, the dashboard shows a "No downtime this period" state.

Open the dashboardCopy Anchor Link

1. Open Dashboards. The picker is titled Open a dashboard.
2. Find Pareto for Downtime and double-click its card to open the dashboard.
3. Alternatively, single-click the card and use its confirmation bar to open it.
4. The dashboard opens without a sidebar. Use Back to dashboards in the top-right to return to the picker.

Set the scopeCopy Anchor Link

The page header shows Downtime, a time-range picker and a Machines picker. Every scope choice is written into the page address.

• Time range. Choose Today, Current week, Previous week, Current month, Last month, 7 days or 30 days. The default is 7 days.
• Machines. The picker defaults to All machines. Select one or several machines from the list grouped by production line.
• Chart filters. Click a named reason, line or machine to narrow the dashboard. Active filters appear as removable chips beneath the header.
• Clear all. Use this control to remove active machine, line and reason filters. It leaves the selected time range in place.

The current page has no separate Planned or Unplanned scope control. Loss Type, Category and Reason tabs change how the trend and comparisons are stacked.

Read the metricsCopy Anchor Link

The summary directly under the header has four figures:

• Total downtime is the stopped time summed across the scope.
• Efficiency is running time divided by running plus recorded downtime. It describes recorded time rather than the entire calendar window.
• Utilization is running time divided by the window duration multiplied by the number of machines in scope. The recorded running duration appears beneath its label.
• Top loss names the biggest reason by time and shows its share of total downtime.

Where a comparison is available, the first three figures show a change against the immediately prior equal-length window. Top loss shows its current share. A dash means a figure cannot be calculated.

Read the chartsCopy Anchor Link

Downtime reasons is the Pareto, headed "Ranked by time lost, cumulative share":

• Bars are sorted strictly from most to least time lost. A cumulative-percentage line climbs left to right, and a dashed reference line marks the 80% mark , the classic cutoff for the vital few.
• Colour encodes the configured loss type, such as Changeover/Setup, Waiting or Minor Stop. The legend above the chart names the types in view. Other / Uncategorized uses a neutral colour.
• Only the top reasons get their own bar; the long tail is folded into a single Other bar, and events with no reason collect in an Uncategorized bar. Neither is ever dropped, so the totals always add up.
• Hover any bar for its reason name, loss type, downtime, share, cumulative percent and event count. Click a named reason bar to filter the dashboard to it; click it again to clear the filter. In the resulting single-reason view, the cumulative line and 80% reference are hidden.

Downtime trend, headed Daily total, follows the reason chart as a separate panel. It stacks one bar per day across the window. Choose Loss Type, Category or Reason to change the stack, then hover a day for its total and series details.

Compare machinesCopy Anchor Link

Downtime by line compares production lines. Downtime by machine, headed with the machine count and an instruction to click a machine to filter, draws one horizontal bar per asset, stacked by the selected grouping and sorted by total downtime. Bar length is proportional to the busiest machine, so the worst offenders are obvious. Every machine is listed. Click a machine row to scope the whole dashboard to it.

Gotham housing review exampleCopy Anchor Link

Bruce Wayne opens Pareto for Downtime at Gotham Applied Sciences and leaves the scope on 7 days and All machines. The recorded Fixture Changeover and Waiting for Parts stops appear as two ranked reasons, with the corresponding day populated in the trend.

He clicks Fixture Changeover to narrow the view. A Reason chip appears, the chart becomes a single bar, and its tooltip shows the recorded duration and event count. He clears the filter before comparing causes again.

Bruce then selects 30 days and reviews Downtime by machine. The wider window includes the existing Tool Wear/Replacement stop at Gotham Machining Centre 1 alongside the housing benches. He can use the grouping tabs or click a row to investigate that machine, then share the filtered page link for a review.

What you can expectCopy Anchor Link

For any window, machine, type, and reason you choose, the dashboard returns a truthful, ranked picture of lost time: totalled headline metrics, a strict Pareto with a cumulative line, a daily stacked trend, and a per-machine comparison. Every filter recomputes the whole page.

Limitations and feature stateCopy Anchor Link

• This dashboard is available (generally released), not a beta.
• It is read-only. It visualizes downtime data but does not let you create or edit downtime events, reasons, or timers from here , corrections are made where the data originates.
• Rankings depend on setup: OEE downtime tracking must be enabled on an asset type, reasons must be configured, and events must be recorded. Missing any of these shows an empty or "no downtime" state rather than a chart.
• Every figure reflects the current scope. Changing the window, machine, type, or reason recomputes all metrics and charts , the totals are meant to move with your filters.
• Efficiency measures running time against running plus recorded downtime. Utilization measures running against the calendar window across machines. These are separate ratios and do not replace a full OEE score.
• 30-day and all-machine figures are complete. The dashboard reads the full analytics replica for the selected window rather than a capped sample.

TroubleshootingCopy Anchor Link

• "No downtime tracking configured." No asset type has OEE downtime tracking enabled, so there is nothing to rank. Enable tracking on the relevant asset type in settings, then return to the dashboard.
• "No downtime this period." Tracking is on and no filters are active, but no downtime was recorded in the window , a good result. Widen the time range to confirm, or check that reasons are being applied when stoppages happen.
• "No events match." Your filters exclude everything. Use Reset filters in the empty state, or remove a chip in the scope bar.
• The dashboard will not load at all. The access message lists every permission that would open it. Any one of View OEE analytics, View OEE events, or View production jobs is enough. Ask an administrator to grant one of those on a role, then sign in again.

Related guidanceCopy Anchor Link

• Review OEE assets , a per-machine timeline of running and downtime, complementary to this ranking.
• Review OEE people , the same lens applied to operators instead of machines.
• Review OEE timelines , the analytics home for the OEE asset and user timelines.
• Configure downtime reasons , define the reasons, categories, and planned settings that drive every bar here.
• Configure OEE dashboards , set up and manage OEE dashboards.
• Run production timers , how running and stopped time is captured on the shop floor.
• Dashboards , the full dashboard picker.