Who should own KPI governance in an ISO 22400 project?

In an ISO 22400 project, KPI governance should not sit with a single department. The most robust pattern in regulated, brownfield environments is a cross-functional KPI governance group, usually led by operations but with explicit, shared ownership across operations, quality, IT/OT, and finance.

Primary ownership: cross-functional KPI governance group

In practice, KPI governance is best owned by a formal KPI governance group or steering committee that reports into existing operational governance (for example, an operations excellence board or site leadership team). This group should be explicitly chartered for ISO 22400 metrics and aligned with existing management review structures.

Typical chair and members:

• Chair: Operations or manufacturing leadership (e.g., Plant Manager, Director of Operations, or VP Manufacturing), because ISO 22400 KPIs primarily describe manufacturing performance and are used to run the plant.
• Core members:
  • Quality (e.g., Site Quality Head or Quality Systems lead) to ensure KPI definitions, data usage, and change control align with QMS, validation expectations, and regulatory commitments.
  • IT/OT (e.g., MES architect, OT lead, or IT manufacturing systems lead) to own data lineage, integration design, system performance impact, and cybersecurity constraints.
  • Finance / Controlling to align KPI formulas and time-basis with financial reporting and avoid conflicting “truths” for utilization, OEE, or cost-related metrics.
  • Continuous Improvement / Industrial Engineering to ensure KPIs support realistic improvement programs and standardized work measurement.

This group owns the KPI framework and decisions, not the day-to-day measurement. Daily data collection and review typically remains within operations, line leadership, and existing MES/reporting teams.

What the KPI governance group should own

Regardless of organizational chart, someone must explicitly own these responsibilities. In a mature ISO 22400 initiative, the governance group should control:

• KPI catalog and scope
  • Selection of which ISO 22400 KPIs are in scope by plant/asset/area.
  • Standard naming, units, and aggregation levels across sites where feasible.
  • Clear mapping from ISO 22400 concepts to local terminology to avoid ambiguity.
• Definitions and calculation rules
  • Formal, versioned definitions of each KPI, including inclusions, exclusions, and timing.
  • Resolution of contentious edge cases (e.g., what counts as “planned downtime,” “rework,” or “microstop” in your context).
  • Alignment of formulas across MES, data lake/BI, and any local spreadsheets to avoid multiple versions of the same KPI.
• Data sources and lineage
  • Approved source systems and signals for each KPI: MES, historians, ERP, LIMS, QMS, PLC tags, etc.
  • Data lineage and transformation rules from raw signals to KPI-ready data.
  • Expectations for data quality checks, reconciliation, and exception handling.
• Change control and validation
  • Change process for KPI formulas, thresholds, and visualizations, integrated with existing IT and QMS change control.
  • Impact assessment for regulated contexts (e.g., whether a change affects validated reports, batch record content, or management review inputs).
  • Approval workflows and documentation for audits and internal traceability.
• Usage and behavior
  • Guidance on how KPIs should and should not be used (e.g., for tier meetings, incentive schemes, supplier reviews).
  • Alignment of KPI targets with realistic process capability and qualification constraints.
  • Training expectations so that supervisors and engineers interpret metrics consistently.

Why a single-owner model usually fails in regulated plants

It is tempting to assign KPI governance to a single function (e.g., IT, quality, or a central analytics team). In most ISO 22400 implementations in regulated, long-lifecycle environments, this creates problems:

• IT-only ownership often leads to technically correct dashboards that misrepresent actual operations because key edge cases, rework flows, and shop-floor realities are not captured. It can also conflict with quality and validation expectations.
• Quality-only ownership may bias toward audit-friendly metrics and document-heavy processes that slow operational updates and discourage iterative improvement.
• Operations-only ownership can optimize local decision-making but neglect data lineage, integration constraints, and alignment with corporate financial and regulatory reporting.
• Corporate analytics-only ownership risks creating a parallel “metrics universe” that diverges from what MES, ERP, and local plants actually use, undermining trust.

In brownfield environments with multiple MES, ERP, SCADA, and data lake solutions, a single function rarely has authority and context across all systems. Cross-functional governance is usually the only practical way to manage the tradeoffs among accuracy, usability, and compliance.

Fitting ISO 22400 KPI governance into brownfield reality

ISO 22400 projects almost always coexist with legacy metrics, site-specific dashboards, and long-qualified systems. Effective ownership should acknowledge that:

• Full replacement of existing KPIs is rarely feasible in the short term. Replacing long-standing metrics or reports can trigger revalidation, retraining, and re-baselining of improvement programs. The governance group should plan for coexistence and phased convergence.
• Site autonomy and corporate standards must be balanced. The governance group may define a core, standardized ISO 22400 KPI set, while allowing controlled local extensions with clear labeling and documentation.
• Integration debt is a constraint, not an afterthought. OT and IT representatives must be able to say “no” or “not yet” when a desired ISO 22400 metric would require unsafe changes to PLCs, impactful MES outages, or brittle data pipelines.
• Audit and regulatory expectations limit rapid changes. For plants where KPIs feed into management review, quality indicators, or batch release decisions, even “purely operational” metric changes can have regulated implications. Quality and regulatory affairs must be part of ownership.

Practical ownership pattern

A pragmatic approach many plants use for ISO 22400 KPI governance is:

1. Charter a KPI governance group under existing operational governance, with a written mandate covering scope: ISO 22400 mapping, KPI definitions, and system-of-record decisions.
2. Assign a single accountable leader (often a senior operations or manufacturing systems leader) who is responsible for convening the group and ensuring decisions are implemented, without owning all details personally.
3. Define RACI for KPI lifecycle steps (design, implementation, validation where applicable, deployment, change management), spanning operations, quality, IT/OT, and finance.
4. Embed KPI changes into standard change control so that KPI formula or source changes are treated like any other system change with risk assessment, testing or validation, and documented approvals.
5. Review ownership annually as plants, systems, and regulatory expectations evolve, updating responsibilities and membership.

In summary, KPI governance in an ISO 22400 project should be owned by a cross-functional governance group led by operations, with mandatory participation from quality, IT/OT, finance, and continuous improvement. Concentrating ownership in a single siloed function tends to fail in regulated, brownfield manufacturing environments.