Glossary

Real-Time Dashboard

A live visual display of current operational data, metrics, and alerts from connected manufacturing or business systems.

Core Aerospace Operations Execution Performance Visibility (OEE, NPT, Shift Variance)Operational Excellence

A real-time dashboard is a visual interface that displays current or near-current data from one or more systems so users can monitor operations as conditions change. In manufacturing, it commonly brings together metrics, status indicators, alarms, and trends from sources such as MES, ERP, SCADA, historians, quality systems, maintenance systems, or IoT platforms.

The term usually refers to the presentation layer, not the underlying data source, analytics model, or control system itself. A dashboard may show machine states, production counts, downtime, yield, work order progress, quality events, or inventory status, but it does not by itself execute production, store all source data, or replace operator procedures.

How it is used in operations

In industrial and regulated environments, a real-time dashboard is commonly used to give operators, supervisors, engineers, and managers a shared view of what is happening now. Depending on the audience, it may present:

equipment or line status
throughput, cycle time, and schedule attainment
OEE-related measures and downtime signals
quality exceptions, holds, or nonconformance counts
material flow, WIP, or shortage indicators
alerts that need review or escalation

Some dashboards update continuously, while others refresh on a short interval. In practice, “real-time” often means data is available with minimal delay, not necessarily instant at the millisecond level.

What it includes and excludes

A real-time dashboard commonly includes live KPIs, status widgets, charts, trend views, and alert summaries. It may also support drill-down into underlying events or records.

It does not necessarily include closed-loop control, automated decision-making, historical reporting, or root cause analysis. Those functions may exist in connected systems, but they are separate from the dashboard itself.

Common confusion

Dashboard vs. report: A dashboard is used for ongoing visibility into current conditions. A report is usually a static or scheduled output focused on a defined time period.

Dashboard vs. HMI: An HMI is typically designed for direct interaction with equipment or a process. A dashboard is usually for monitoring and coordination across assets, lines, sites, or business functions.

Dashboard vs. historian or BI platform: A historian stores time-series process data, and a BI platform supports broader analytics and reporting. A dashboard may use data from either, but is not the same thing.

Manufacturing example

A plant supervisor might use a real-time dashboard to see current line output, active downtime reasons, open quality holds, and whether work orders are on pace for the shift.

ISO 22400 does not mandate a single "official" Overall Equipment Effectiveness (OEE) formula. It standardizes terminology and gives reference models and example calculations for availability, performance, and quality, but leaves room for plant-specific definitions. In regulated, brownfield environments, you must explicitly define and document your chosen OEE variant, validate calculations, and manage changes under configuration control.

How many data points are needed for a meaningful capability study?

There is no single universal minimum. In practice, about 25 to 30 rational subgroup averages, or roughly 100 to 125 individual observations, is a common starting point for a preliminary capability study. More data is usually needed when the process is unstable, mixed across setups or lots, measured poorly, or run at low volume.

How many KPI categories should a manufacturing organization define?

There is no fixed correct number. Most manufacturing organizations should limit KPI categories to a small, governed set, often about 4 to 8, so reporting stays usable and ownership stays clear. The right count depends on operating model, data quality, regulatory traceability needs, and how well metrics can be maintained across MES, ERP, QMS, and legacy systems.

Why is standardized KPI terminology important for multi-site aerospace manufacturers?

Standardized KPI terminology lets multi-site aerospace manufacturers compare performance accurately, avoid false conclusions, and maintain audit-ready traceability. Without clear, shared definitions for metrics like OEE, NPT, and COPQ, plants optimize against different scoreboards, masking risk, hiding capacity constraints, and undermining quality and compliance initiatives.

Related Glossary