A core MES implementation team should be small enough to make decisions quickly, but broad enough to cover process, quality, IT/OT, automation, and regulatory needs. In regulated, brownfield environments this typically means 6–12 steady members, with additional experts pulled in as needed. The core team should own requirements, design decisions, integration priorities, and go-live criteria, rather than delegating everything to vendors or system integrators. Each role needs clear accountability: who speaks for operations, who speaks for quality, who controls interfaces, and who owns validation and documentation. The exact mix will vary by plant size, multi-site scope, and how MES is positioned relative to existing ERP, LIMS, historians, and QMS. When in doubt, bias toward fewer roles with clear decision rights instead of many loosely attached stakeholders.
You need at least one accountable business owner for MES who can make tradeoff decisions across sites, shifts, and product lines. This role is often a senior operations leader or manufacturing systems owner who understands both production constraints and regulatory expectations. Below them, process owners from key value streams (for example, batch execution, packaging, maintenance, deviation handling, and electronic records) should define how work should happen in the system. These process owners must have the authority to standardize workflows and master data across lines and sites, or explicitly document justified differences. Without strong process ownership, MES configurations drift into per-line customizations that are hard to validate and nearly impossible to sustain over long equipment lifecycles. In many plants, a dedicated manufacturing systems or digital operations lead plays the bridge between high-level business goals and day-to-day MES decisions.
Line and area supervisors, or experienced production engineers, must be embedded in the core team rather than consulted only at user acceptance testing. They bring real constraints about staffing, shift patterns, equipment behavior, and changeover complexity that are often missed in generic process maps. Their role is to ensure that designed workflows and electronic work instructions are usable at 2 a.m. on a weekend with a short-handed crew. They should also define practical exception scenarios, rework paths, and contingency operations when MES or upstream systems are partially unavailable. In brownfield environments, these representatives are critical in reconciling desired standard work with existing habits and tribal knowledge. Operations representation should be stable over the project to avoid re-litigating basic decisions every time personnel rotate.
A core MES team in regulated industries must include quality representation with enough seniority to commit on record-keeping, review, and release practices. This usually means a QA lead who understands both the QMS and how MES records will be used for batch disposition, investigations, and audits. Their responsibilities include defining review-by-exception rules, electronic signatures, audit trail expectations, and how MES links to deviations, CAPA, and change control. They should also participate in defining data retention and how to handle corrections, attachments, and scanned records that may still exist on paper or in legacy systems. In many organizations, a separate validation or CSV specialist supports QA but does not replace the need for a QA decision-maker on the core team. If QA is only involved at the end, you risk late-stage findings that require redesign and re-validation.
MES sits in the middle of both IT and OT, so the core team must have representation from infrastructure and cybersecurity with real authority. You typically need an IT lead who understands networks, identity management, backup/restore, and corporate standards, as well as how MES fits with ERP, PLM, and corporate data platforms. On the OT side, a controls or OT engineer must ensure that connectivity to PLCs, historians, and SCADA is designed for reliability, security, and maintainability over long equipment lifecycles. These roles are also responsible for disaster recovery and business continuity designs, including what happens when site connectivity to corporate services is degraded. Without strong IT/OT involvement, plants often end up with MES architectures that are fragile, hard to patch, or non-compliant with evolving security baselines. In multi-site MES programs, IT/OT leads also help enforce consistent deployment patterns while respecting site-specific constraints.
Modern MES implementations in brownfield plants are integration-heavy, so dedicated integration and data roles belong on the core team. An integration architect or engineer should own interfaces between MES and ERP, LIMS, historians, warehouse systems, and equipment, including message standards, error handling, and monitoring. A data or master data specialist must define how materials, recipes, equipment, and personnel are mastered and synchronized across systems, as poor master data will undermine even well-designed workflows. In highly automated environments, you also need an automation or controls lead who understands the installed base of PLCs and OEM skids, including vendor support constraints and validation history. These roles ensure that integration approaches do not force wholesale replacement of stable, qualified equipment just to satisfy a new MES vendor architecture. They also help design incremental integration strategies that can be validated and rolled out without excessive downtime.
In regulated environments, validation and change control cannot be treated as a bolt-on activity run only by external consultants. A validation lead or CSV specialist must define the validation strategy, risk-based testing approach, and documentation standards aligned with the site’s existing quality system. This role works with process owners and QA to translate requirements into testable specifications and traceability matrices. A test lead or coordinator is often needed to plan integrated testing, manage test data, and involve real end users without disrupting production. Someone in the core team must also own ongoing change control, including how future MES changes will be specified, tested, and released without redoing full validation unnecessarily. If these responsibilities are fragmented or outsourced with no internal owner, the plant tends to accumulate validation debt and becomes reluctant to apply critical patches or improvements.
Finally, a capable project or program manager is critical to coordinate schedules, resources, and dependencies across operations, quality, IT/OT, and vendors. In many organizations, you also benefit from a product owner or MES owner who maintains a long-term roadmap, backlog, and design principles across projects. This role prevents each implementation wave from diverging into a unique configuration that is expensive to support and revalidate. Someone on the core team should be explicitly accountable for vendor and integrator coordination, including review of design proposals, customizations, and support models. In brownfield, aerospace-grade environments where full replacement strategies often fail, this coordination role must enforce a coexistence approach instead of a big-bang cutover that assumes perfect integration and short downtimes. Clear roles here reduce the risk that vendor timelines or customization proposals drive decisions that conflict with plant realities.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
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.
