Who should be on a manufacturing KPI council?

A manufacturing KPI council should include the people who own the process, the data, and the consequences of acting on the metric. In most plants, that means a small cross-functional group with enough authority to define KPIs, resolve conflicts, approve changes, and enforce governance.

A practical council usually includes:

• Operations leadership to represent throughput, schedule adherence, labor utilization, and shift-level execution reality.
• Quality leadership to ensure metrics do not hide rework, escapes, NCR volume, or other quality impacts.
• Manufacturing or industrial engineering to define how process changes, routings, cycle times, and standards affect KPI meaning.
• Maintenance or asset reliability if uptime, downtime, OEE, or constraint equipment performance is in scope.
• Supply chain or materials planning when shortages, kit readiness, supplier performance, or queue time materially affect output.
• Finance to align KPI definitions with cost, inventory, margin, and valuation impacts without letting accounting logic distort shop-floor truth.
• IT, MES, ERP, or data owners to manage source-system definitions, integration dependencies, master data issues, and reporting controls.
• Site or business leadership sponsor to break ties, set priorities, and make decisions stick.

Depending on scope, you may also need representation from program management, continuous improvement, regulatory or compliance functions, and EHS. Not every stakeholder needs a permanent seat, but the council should be able to pull them in when definitions or changes affect their domain.

What matters more than headcount

The council should not be a large committee that debates dashboards without owning outcomes. A good manufacturing KPI council has three characteristics:

• Decision rights over KPI definitions, thresholds, ownership, and retirement.
• Data accountability for source systems, calculation logic, timing, and exceptions.
• Change control so metric definitions do not drift quietly between sites, shifts, or reports.

If those controls are missing, the same KPI name often ends up meaning different things in ERP, MES, spreadsheets, and management reviews. That is common in brownfield environments and is one reason KPI programs lose credibility.

Who should chair it

Usually, the chair should come from operations or operational excellence, with formal participation from quality and IT or data governance. If the council is chaired only by IT, it may become a reporting exercise. If it is chaired only by operations, data lineage and system constraints may be ignored. The balance matters.

How big should it be

Smaller is usually better. Five to nine core members is often enough, with named alternates and ad hoc subject matter experts. Larger groups can work for enterprise standardization, but they tend to slow definition changes and make ownership less clear.

What the council is actually responsible for

In practice, the council should govern:

• KPI definitions and formulas
• Inclusion and exclusion rules
• System of record for each input
• Data latency and refresh expectations
• Exception handling and manual overrides
• Approval of new KPIs and retirement of low-value ones
• Cross-site comparability limits
• Versioning, traceability, and change history

That last point matters in regulated and long-lifecycle operations. If a KPI drives action, escalation, incentives, or quality decisions, you need traceability around how it is defined and when it changed. A dashboard without governance is not the same as a controlled performance system.

Brownfield reality

If your plant runs mixed ERP, MES, QMS, historians, spreadsheets, and manual logs, the council should explicitly include people who understand those seams. Do not assume KPI standardization is just a BI problem. In many facilities, differences in routing design, transaction discipline, machine connectivity, and operator workarounds will limit how consistent a KPI can be across lines or sites.

That is also why full replacement is usually not the first answer. Replacing legacy systems to harmonize KPIs often fails or stalls because of validation effort, qualification burden, integration complexity, downtime risk, and the need to preserve traceability across long equipment lifecycles. In most cases, the KPI council needs to work with coexistence, not wish it away.

Bottom line

The right council is cross-functional, small enough to act, and senior enough to enforce standards. At minimum, include operations, quality, engineering, IT or data ownership, and an executive sponsor. Add maintenance, supply chain, finance, and program leadership when those functions materially shape the KPI or the decisions made from it.