Glossary

KPI specification

A KPI specification is the formal definition of a metric, including its formula, scope, data source, and rules for use.

Industry Insight and Thought Leadership ISO 22400 Manufacturing KPIs for Modern Plants

A KPI specification is a documented definition of a key performance indicator that explains exactly what the metric measures, how it is calculated, what data it uses, and how it should be interpreted. It is used to make sure the same KPI is measured consistently across teams, systems, time periods, and reporting views.

In manufacturing and regulated operations, a KPI specification commonly includes the metric name, business purpose, formula, unit of measure, time basis, inclusion and exclusion rules, source systems, refresh frequency, and ownership. It may also define thresholds, targets, and drill-down dimensions, but it is not the performance result itself.

A KPI specification is not a dashboard, chart, or report. It is the underlying metric definition that allows dashboards, MES reports, ERP analytics, and quality reviews to use the same logic. For example, if a site tracks first pass yield, schedule attainment, or nonconformance rate, the KPI specification defines what counts in the numerator and denominator and which transactions or events are in scope.

What it usually includes

Metric name and plain-language definition
Formula or calculation logic
Unit of measure and reporting cadence
Scope, boundaries, and exclusions
Source data and system of record
Data quality or timing assumptions
Owner or steward responsible for maintaining the definition
Target, threshold, or alert criteria when applicable

Operational meaning

Operationally, KPI specifications are used when metrics are implemented in MES, ERP, historian, BI, or quality systems. They help align operators, supervisors, engineers, quality teams, and analysts on the same definition so that shift reviews, management reporting, and continuous improvement activities are based on comparable numbers.

They are also useful when integrating data across systems. If production counts come from MES, scrap events from quality records, and labor time from ERP, the KPI specification documents how those sources are combined and which timestamps, statuses, or transaction types are valid for the metric.

Common confusion

KPI specification is often confused with a KPI target or KPI dashboard. A target is the expected value or threshold for a metric. A dashboard is the visual presentation of one or more metrics. The KPI specification is the controlled definition behind both.

It can also be confused with a data definition or report requirement. Those are related, but a KPI specification focuses on the business meaning and calculation rules of the metric, not only the technical structure of the data or the layout of a report.

When a KPI definition changes in one system, you typically get a period where numbers no longer align across dashboards, plants, or functions. The impact depends on integration design, governance, and documentation. In regulated, long-lifecycle environments, uncoordinated KPI changes can break traceability, confuse root-cause analysis, and create audit exposure if not versioned and communicated.

Does ISO 22400 replace my existing OEE definitions?

ISO 22400 does not automatically replace your current OEE definitions. It provides standardized terminology and formulas you can choose to align with, but adoption is voluntary and must be managed through change control, impact assessment, and revalidation of KPIs, reports, and integrations in your existing MES/ERP/QMS landscape.

How is ISO 22400 different from traditional OEE guidelines?

ISO 22400 formalizes manufacturing KPIs (including OEE) with standard definitions, data structures, and calculation rules, while traditional OEE guidelines are typically plant- or vendor-specific conventions. ISO 22400 reduces ambiguity but only helps if your data model, MES/SCADA integration, and governance are aligned and validated. Brownfield coexistence and legacy reports often mean you must run both in parallel for a period.

How long does an ISO 22400 rollout typically take?

An ISO 22400 rollout can range from a few months to several years depending on scope, data readiness, and brownfield complexity. A focused pilot for a handful of KPIs might be live in 3–6 months, while a plant- or network-wide rollout across mixed MES/ERP stacks commonly extends to 18–36 months, including validation and change control.

Related Glossary

State-Based KPI

A performance metric that is calculated separately for defined equipment, line, or process states, such as running, idle, or down.