A waste-focused MES initiative needs a small core leadership team with clear accountability for scope, decisions, and tradeoffs. Typically this includes a project sponsor from operations, a project or program manager, and a solution owner (often from manufacturing engineering or operations excellence). The sponsor should own the business case and be able to resolve cross-functional conflicts about priorities, metrics, and downtime windows. The project or program manager coordinates timelines, risk management, and alignment with other site or enterprise initiatives to avoid conflicting upgrades or shutdowns. The solution owner is responsible for how waste-reduction requirements translate into MES functionality, data structures, and operational procedures across lines and plants.
Operations representation is critical because waste is often driven by scheduling, staffing, material handling, and line management decisions, not only machine performance. You need production managers or supervisors who understand real bottlenecks, daily workarounds, and how current KPIs are calculated and used. At least one experienced operator from key lines should be involved in workshops and design reviews to validate that proposed MES screens, alerts, and data capture steps are practical under real cycle-time and staffing constraints. In regulated environments, operations leaders must also ensure that changes to work instructions, logbooks (electronic or paper), and shift handover practices are controlled and documented. Without credible frontline input, MES waste tracking often adds administrative burden without actually reducing downtime, scrap, or rework.
Manufacturing engineers and continuous improvement (CI) practitioners are usually the primary owners of how waste is defined, measured, and reduced. You need process engineers who understand cycle times, routings, tooling constraints, and known failure modes, and can specify what should be captured in MES (e.g., scrap codes, rework paths, microstops, and changeover classifications). CI or lean specialists can align MES configuration with existing problem-solving methods such as 5‑Whys, A3s, or value stream maps, and ensure that waste categories match how the organization already talks about losses. This group should also define how MES data will be used in root cause analysis, kaizen events, and daily management routines, rather than assuming that more data automatically drives better decisions. In brownfield plants, they must account for legacy routings, homegrown spreadsheets, and tribal knowledge that may conflict with the MES “ideal” process.
Quality must be involved early because waste-related changes often intersect with nonconformance handling, traceability, and release decisions. Quality engineers or quality systems owners should define how scrap, rework, holds, and deviations will be recorded in MES and how these data flows interact with QMS records. They need to ensure that any changes to sampling plans, inspections, or digital signatures are validated and controlled under existing quality procedures. In highly regulated environments, a quality representative will also help determine what requires formal validation, what evidence needs to be retained, and how MES changes may impact audit trails. If quality is not part of the team, you risk building waste dashboards that contradict official quality metrics or that bypass required review and approval steps, creating compliance and data integrity issues.
IT and OT roles are essential because waste-focused MES projects depend on reliable data from machines, historians, PLCs, and upstream systems like ERP or LIMS. You need MES technical experts and system integrators who understand the current architecture, interfaces, and vendor constraints, and who can realistically assess what can be automated versus what must remain manual. OT engineers or controls specialists must validate that proposed data capture (e.g., downtime reasons, counts, speeds) is technically feasible on existing equipment without compromising safety systems or causing unplanned downtime. IT representatives are needed to handle infrastructure, cybersecurity, access control, and alignment with enterprise standards, especially when MES changes touch user management or cloud integrations. A data engineer or analyst can help define data models, ensure that loss categories and event logs are usable for analysis, and highlight integration debt that may limit real-time analytics.
Waste-focused MES projects often depend on credible cost and savings estimates to stay funded and prioritized. A finance or cost-accounting representative should help define how scrap, rework, and downtime costs are calculated, and how MES data will tie into standard costing or variance reporting. Without this role, you can end up with conflicting “savings” numbers between CI teams, operations reporting, and corporate finance. Supply chain or planning representatives may also be needed if waste data will influence material planning, safety stocks, or delivery commitments. These roles ensure that waste metrics captured in MES are not just technically accurate, but also meaningful in the context of inventory, service levels, and contractual obligations.
For regulated environments, you need clear ownership of validation and change control from the outset. This often includes a validation engineer or CSV specialist responsible for defining the validation strategy, risk assessments, and testing requirements for MES changes that affect electronic records, signatures, or traceability. A change control coordinator or configuration manager can ensure that MES changes are properly requested, reviewed, approved, and documented within existing change control processes. Governance roles may also include a steering committee or architecture board that reviews the project’s impact on other systems such as ERP, PLM, and QMS, and avoids uncoordinated customizations that are hard to maintain. Without these functions, even well-designed waste features can fail during audits or become too fragile to sustain over long equipment lifecycles.
In brownfield plants with multiple legacy systems, the same person may wear several hats, but the underlying responsibilities still need to be covered. For example, a senior manufacturing engineer might act as both solution owner and CI lead, while an experienced OT engineer covers both controls and MES integration duties. Multi-site programs may require site-level champions who translate corporate MES and waste definitions into local processes while feeding back constraints related to local equipment, unions, or regulatory regimes. Each site should still assign named individuals for operations, quality, IT/OT, and engineering roles, even if project resources are tight. The key is not to achieve a perfect org chart, but to ensure that process ownership, system ownership, data ownership, and compliance ownership are all explicitly represented and coordinated.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
