A plant manager's morning usually starts with the same question: what happened on the line overnight, and is today's schedule still realistic? Too often the answer means pulling three different reports — one for downtime, one for maintenance status, one for output — before a clear picture emerges. Most plants track around 37 KPIs across their systems, yet high-performing operations limit their manager-level dashboard to the 8-12 that actually drive daily decisions. Book a free demo to see a dashboard built around those, not everything at once, on a single connected screen.
Why 37 KPIs Is the Wrong Target
The instinct when building a plant dashboard is to track everything the CMMS can measure. In practice, the industry average sits around 37 tracked KPIs per plant, but high-performing plants limit the manager-level scorecard to 8-12 metrics that map directly to daily decisions — everything else either belongs at operator level or gets reviewed monthly, not daily. A dashboard that shows everything shows nothing clearly.
The fix isn't collecting less data overall — it's being deliberate about which numbers earn a permanent spot on the screen a plant manager checks every morning.
A plant manager's dashboard sits squarely in the weekly tier — enough detail to spot trends, without the daily noise or the monthly strategic lag.
Breaking Down OEE: Where the Losses Actually Hide
OEE is widely treated as the single most important plant metric because it combines three separate loss categories into one number. Most manufacturers target 85% as world-class, with 60% considered typical and anything below 40% signalling a serious improvement opportunity. The formula is simple, but knowing which of the three factors is actually dragging your number down is where the real diagnostic value sits.
Chasing availability alone while performance or quality quietly slips is a common trap — the dashboard needs to show all three, not just the headline number.
MTBF and MTTR: The Two Numbers Behind Uptime
Availability — the first factor in OEE — is really the product of two underlying maintenance metrics: how often things break, and how fast they get fixed. Tracking these separately makes the diagnosis clearer than watching uptime alone.
A plant with high MTBF but slow MTTR has infrequent but disruptive failures. Low MTBF with fast MTTR points to frequent small issues a team has gotten efficient at fixing — a different problem entirely.
Turning Downtime Data Into Action, Not Just a Chart
A dashboard that shows downtime trending up is only half useful — the value is in connecting that trend to what's actually causing it and what work order addresses it. OxMaint pulls uptime, downtime cause codes, PM compliance and maintenance backlog into one live view, so a plant manager isn't reconciling separate reports before a shift meeting. Sign up free and connect your first line to see the picture start forming.
Expert Perspective: Building a Dashboard People Actually Use
KPIs that are published but never discussed are decoration, not management tools. A dashboard earns its place in daily operations by being reviewed on a set cadence — daily huddles for operational metrics, weekly reviews for reliability trends, monthly business reviews for cost and strategic numbers. Without that rhythm, even the best-designed dashboard ends up ignored on a screen nobody looks at.
What Good Downtime Data Actually Looks Like
Raw downtime hours tell you there's a problem. A useful downtime dashboard tells you which machine, which cause category, and how that compares to last week — turning a number into a decision. Cause-coded downtime, reviewed weekly against the maintenance backlog, is what actually shifts a plant from reactive firefighting to planned improvement. Sign up free and start coding your downtime causes to see the pattern emerge.
Once causes are visible, the highest bar on the chart is usually the clearest starting point for where maintenance attention should go next.
Getting a Live Dashboard Running
Standing up a connected uptime dashboard doesn't require ripping out existing systems. Start by connecting your CMMS work order and downtime data for your most critical line, get the core 8-12 metrics visible, and expand line by line from there. Sign up free and connect your critical line first before rolling it out further.
A dashboard only earns its place once it becomes part of how decisions actually get made — a fixture in the daily huddle, not a screen glanced at occasionally. Set a standing weekly review of the 8-12 core metrics, note what changed and why, and let that rhythm keep the dashboard relevant instead of decorative. Book a free demo to see this built around your own plant.
