Availability × Performance × Quality
View the overall OEE result together with its three components so the source of the loss is visible.
MANUFACTURING KPI DASHBOARD
KPIs connected to the production events behind them.
ClearRivet combines live manufacturing KPIs with the underlying machine and downtime record so a low number can be investigated instead of simply reported.
WHY IT MATTERS
A dashboard should explain the number.
Manufacturing KPIs are most useful when definitions are consistent and the source events can be traced. ClearRivet is designed to preserve that connection from summary to machine history.
Actual versus target
Track units made, production rate and order progress against the configured target.
Time and reason
See stopped duration and the events or reasons contributing to Availability loss.
CLEARRIVET APPROACH
A dashboard should explain the number.
Manufacturing KPIs are most useful when definitions are consistent and the source events can be traced. ClearRivet is designed to preserve that connection from summary to machine history.
OEE
Availability
Performance
Quality
Actual production
Target production / rate
Run and downtime duration
Order progress and historical comparison
KPIs FOR DAILY PRODUCTION
Manufacturing KPIs are useful when the team can trace them back to the shift.
A KPI card should not be the end of the investigation. If OEE falls, production misses target or downtime rises, the next question is what happened on the machine. ClearRivet keeps summary KPIs connected to the underlying run/stop events, production counts, rate, order context and downtime reasons.
See the total result and the three components
Availability, Performance and Quality show whether the loss is primarily time, speed or good-output related rather than hiding everything inside one percentage.
Measure actual production against the target
Use count, rate and order progress to see whether the shift is delivering the quantity expected, not simply whether the machine is switched on.
Keep duration and reason beside the KPI
When Availability falls, supervisors can see the stop events and reason history contributing to the loss and decide which event needs attention.
FROM SHIFT TO TREND
Compare the KPI only after the definitions are consistent.
Plant dashboards become misleading when machines use different planned-time rules, rate targets or quality definitions. ClearRivet is designed around configured operating context so comparisons can be made with the definitions visible and understood.
For daily management, the practical sequence is simple: see what is off target, identify the component creating the gap, review the machine events behind it, then compare later periods to see whether the corrective action held.
COMMON QUESTIONS
Questions manufacturing teams ask.
How is Availability calculated?
Availability should be based on runtime divided by planned available production time, using the site’s configured production calendar and event logic.
How is Performance calculated?
Performance compares actual production output or rate against the configured ideal/target production capability for the relevant period.
How is Quality calculated?
Quality is based on good production divided by total production when quality quantities are available and recorded.
EXPLORE CLEARRIVET
Related production monitoring capabilities.
KPIs THAT DRIVE ACTION
A manufacturing KPI dashboard should show the number and the loss behind it.
OEE, output, target attainment and downtime totals are useful starting points, but the dashboard becomes more valuable when a team can move from the KPI into the event that changed it. If Availability falls, the next question is what stopped. If Performance falls, the next question is where speed or output was lost.
ClearRivet is designed to keep KPI views connected to production orders, machine events, downtime reasons and shift context so managers can investigate rather than simply observe.
SHOP-FLOOR SCREEN
Shared TV and Andon views should emphasise exceptions, not dashboard clutter.
On the shop floor, the priority is fast recognition: running or stopped, production versus target, active downtime, order progress and calls for help. A shared screen should make those conditions obvious enough for the team to respond without searching through reports.
See it. Then prove it.