Who should own KPI definitions in an ISO 22400 program?

In an ISO 22400 program, no single function should unilaterally own KPI definitions. The most effective approach is a formal, cross functional governance group that is accountable for defining, approving, and changing KPI definitions, with clearly assigned roles inside that group.

Recommended ownership model

For regulated, brownfield environments, a practical split of responsibilities is:

• Executive sponsor (Operations or Plant leadership): Owns the overall KPI framework, priorities, and conflict resolution. Ensures KPIs support strategy, not just data availability.
• Process owners (Operations / Manufacturing Engineering / Maintenance): Own the operational meaning of each KPI (e.g., what counts as planned production time, what is valid downtime, how to treat changeovers or inspections). They drive usability and prevent definitions that are theoretically correct but operationally useless.
• Quality / QMS: Owns traceability, documentation, and change control of KPI definitions. They ensure that definitions, formulas, and data sources are version controlled, reviewed, and aligned with quality procedures and audit expectations.
• IT / OT / MES data stewards: Own the technical implementation of KPI definitions in MES, historians, data lakes, and reporting tools. They are responsible for data lineage, mapping to ISO 22400 structures, and ensuring that different systems calculate KPIs consistently.
• Finance / Controlling (where relevant): Validates that cost, efficiency, and utilization KPIs align with financial reporting and do not create conflicting “truths” between plant and corporate dashboards.

Why shared ownership is critical for ISO 22400

ISO 22400 provides standardized terminology and formula structures, but each plant still has to decide:

• How to classify and segment time (e.g., planned vs unplanned stops, changeovers, maintenance windows).
• Which equipment and value streams are in scope for each KPI.
• How to handle borderline cases (rework, test cycles, engineering trials, quality holds).
• How to align KPI definitions across MES, ERP, SCADA, and reporting tools.

If KPI ownership sits purely in IT, you risk technically consistent metrics that are operationally meaningless. If it sits purely in operations, you risk local optimizations, poor documentation, and divergence across sites. If it sits purely in quality, you may get good procedures but low adoption. A shared model with explicit governance responsibilities balances these risks.

Governance and change control expectations

In regulated and long lifecycle environments, KPI definition ownership must include structured governance, not just an informal committee. At minimum:

• Authoritative KPI catalog: A single, controlled list of ISO 22400 KPIs, including name, formula, inputs, exclusions, calculation level (machine, line, plant), and system of record.
• Formal approval workflow: Proposed new KPIs or definition changes are reviewed and approved by the governance group (operations, quality, IT/OT, and finance as needed), with documented rationale and impact.
• Version control and traceability: Each KPI definition has a version history that makes it clear when and why a change was made, which systems were impacted, and which periods are not comparable due to a definition change.
• Impact assessment and validation: Before changes go live, data stewards and process owners validate that the implementation matches the approved definition, and that reports, dashboards, and alerts behave as expected.
• Communication and training: Changes to KPI definitions are communicated to supervisors, engineers, and analysts so that performance trends are interpreted correctly.

Coexistence with existing systems in brownfield plants

In brownfield environments, KPI definition ownership is constrained by existing MES/SCADA, historians, ERP, and reporting tools, many of which embed their own KPI calculations. A realistic ownership approach acknowledges that:

• You often cannot replace all existing KPI logic in legacy systems without major validation, downtime, and requalification. Instead, you typically define a system of record for each KPI and document how other systems approximate or consume it.
• Different lines, plants, or vendors may use slightly different KPI formulas today. Ownership includes deciding whether to harmonize, and if so, over what time horizon and with what revalidation burden.
• Data integration and mapping efforts must be jointly owned by IT/OT and process owners so that ISO 22400 fields are populated correctly and consistently across interfaces.
• External reporting (to customers, regulators, or corporate) may already rely on specific definitions. Changing them can have audit and contractual implications that need quality and legal review.

Because full replacement of legacy KPI logic can be risky and expensive in regulated contexts, the governance group often prioritizes:

• Defining and documenting canonical ISO 22400-aligned KPIs first.
• Mapping current system outputs to those definitions, with clear notes where they differ.
• Gradually refactoring or consolidating KPI calculations as systems are upgraded or revalidated.

Practical steps to assign ownership

To establish ownership without reorganizing your entire structure:

1. Appoint an ISO 22400 KPI program lead (often from operations excellence or manufacturing engineering) who coordinates the work but does not own definitions alone.
2. Create a KPI governance charter that names the core group (operations, quality, IT/OT, finance) and spells out decision rights, approval workflows, and documentation expectations.
3. Start with a small, critical set of KPIs (e.g., availability, performance, quality rate, OEE, NPT) and assign specific process owners and data stewards to each.
4. Document the current state vs ISO 22400-aligned target state for each KPI, including where existing systems deviate.
5. Integrate KPI definition changes into existing change control processes (e.g., IT change management and QMS document control), so modifications are tracked like any other controlled change.

In summary, KPI definitions in an ISO 22400 program should be owned by a cross functional governance group with clear accountability: operations for practical meaning, quality for traceability and change control, IT/OT for data integrity and implementation, and finance for alignment with business reporting. The exact org chart matters less than having explicit roles, documented decisions, and disciplined change management across your existing systems.