Ownership of KPI definitions in a manufacturing organization is shared, but not ambiguous. The pattern that works in regulated, brownfield environments is:
- Business ownership for what is measured and why.
- Cross-functional governance for the formal KPI catalog and change control.
- Data/IT/OT stewardship for how KPIs are technically defined and calculated.
1. Business owners: accountable for the KPI itself
Each KPI should have a clear business owner who is accountable for its relevance and performance. Typically:
- Manufacturing / Operations leadership: OEE, throughput, NPT, schedule adherence, capacity utilization.
- Quality leadership: defect rates, right-first-time, complaint rates, recall metrics, CAPA timeliness.
- Supply chain / planning: on-time delivery, forecast accuracy, inventory turns.
- Maintenance / engineering: MTBF, MTTR, planned vs unplanned downtime.
These owners decide which KPIs matter, set targets, and are accountable for actions when KPIs miss plan. They do not unilaterally change definitions or calculations once deployed, because that undermines comparability, auditability, and trust.
2. Cross-functional governance: owns the KPI catalog and definitions
In regulated and long-lifecycle environments, the effective pattern is a cross-functional KPI governance group that owns the official KPI catalog and definitions. This is typically a subset of an existing steering body such as an Operational Excellence council, data governance board, or site leadership team.
This group should:
- Maintain a controlled registry of KPIs, including purpose, owner, data sources, calculation logic, and known limitations.
- Approve any new KPI that will be used for management decisions, regulatory reporting, or customer-facing metrics.
- Approve and document changes to definitions (e.g., how downtime is classified, what counts as a defect, how scrap is valued).
- Ensure alignment across plants where a KPI is claimed to be global or comparable.
- Coordinate communication and training when definitions change.
Membership should include at least:
- Operations leadership
- Quality / Regulatory representation
- Finance / controlling (for cost and productivity metrics)
- IT / OT or data engineering
- Engineering / maintenance, where equipment- and asset-based KPIs are involved
This group is where tradeoffs and conflicts get resolved. For example, if one plant wants to redefine OEE to look better on paper, the governance group can reject or localize that change and preserve global comparability.
3. IT/OT & data teams: stewards of technical implementation
IT, OT, and data engineering teams should not own KPI business meaning, but they must own the technical implementation of the definitions:
- Designing and maintaining data models in MES, historians, data lakes, and BI tools so that KPI logic is consistent.
- Implementing calculations and aggregations in a controlled layer (e.g., semantic model, KPI engine) rather than ad-hoc in every report.
- Managing data lineage and traceability, including documenting which systems feed each KPI.
- Ensuring access control so that only authorized roles can modify KPI logic in production systems.
In a brownfield stack, these teams also own the practical compromises: for example, when legacy equipment cannot provide ideal signals, they document the approximation and its impact on KPI accuracy.
4. Quality & regulatory functions: guardrails and traceability
Quality, regulatory, or compliance functions rarely own all KPIs, but they should own the guardrails around KPIs that affect regulated outputs, release decisions, or complaint handling. They typically:
- Review and approve KPI definitions that are used in batch release, product disposition, or regulatory reports.
- Ensure KPI definitions are under document control with change history and impact assessment.
- Verify that critical KPI calculations in validated systems follow appropriate validation and revalidation processes when modified.
- Confirm that KPI changes do not silently weaken specs, acceptance criteria, or surveillance obligations.
They do not guarantee compliance outcomes, but they make sure KPI changes follow the same discipline as changes to other controlled procedures and tools.
5. Why KPI ownership and definition control matter
If ownership and governance are unclear, typical failure modes include:
- Multiple truths: OEE or COPQ calculated differently by plant, system, or team, making comparisons and global decisions unreliable.
- Untraceable changes: definitions slowly drift as local teams tweak reports, with no record of when or why the KPI “moved.”
- Audit exposure: regulators or customers see conflicting numbers for the same metric, and you cannot show a controlled process for definitions.
- Lost baseline: when definitions change, historical trends become hard to interpret and improvement claims cannot be substantiated.
These issues are amplified in environments with long equipment lifecycles and mixed MES/ERP/QMS stacks, where replacing systems to fix KPI confusion is rarely practical due to qualification burden, validation cost, and downtime risk. Making ownership and governance explicit is usually far lower risk than a full system replacement.
6. Practical pattern for brownfield environments
For existing plants with entrenched systems and ad-hoc KPIs, a pragmatic approach is:
- Assign named owners for each critical KPI (operations, quality, maintenance, supply chain, finance).
- Create a simple KPI catalog in a controlled repository listing definition, owner, data sources, and calculation logic.
- Stand up a small governance group to approve new KPIs and changes.
- Standardize only the most important KPIs first (e.g., OEE, NPT, key quality rates) instead of trying to harmonize everything at once.
- Push technical logic into a shared layer (e.g., data warehouse semantic model) and slowly retire conflicting logic in local spreadsheets and reports.
This approach respects existing systems and minimizes disruption while still clarifying who owns KPI definitions and how they are controlled.
