In most regulated industrial environments, ERP is the system of record for work order creation, planning, and financial status, while MES is the system of record for executing and documenting the work. The ERP work order typically defines the what, how many, when, and which customer or project, while MES governs the how, who, where, and detailed as-built history. Trying to make ERP the single authoritative source for all work order data forces it into a role it is not designed for, especially around real-time execution and traceability. Conversely, pushing planning and financial ownership into MES often collides with existing finance, MRP, and supply chain processes embedded in ERP. The more regulated and integrated the plant, the more costly and risky it is to overturn this division of responsibility.
A pragmatic pattern is to treat ERP as authoritative for work order identity (number), type, planned quantity, due date, BOM, and route header, while MES is authoritative for operation-level execution, labor and machine time detail, actual yields, and nonconformance records. In this pattern, work orders are created and scheduled in ERP, then released and enriched in MES with the detailed routing steps, work instructions, and data collections required for regulated traceability. MES returns summarized execution results and key status back to ERP (completed quantity, scrap quantity, closure status, and possibly summarized labor), preserving financial integrity. The system of record is thus split by data domain, not by whole object: ERP holds the authoritative work order header; MES holds the authoritative execution ledger underneath it.
Putting work order system-of-record status fully into MES can look appealing for operational control, but it tends to conflict with how procurement, inventory, and finance are implemented in ERP. Many ERPs assume that work orders originate there to drive MRP, capacity planning, and cost collection; bypassing that can break established reporting and audit trails. In regulated environments, rewriting those ERP-centric processes and then revalidating them across all integrated systems is a substantial effort, not just a configuration change. Plants with long-lived assets and complex product structures (aerospace, defense, medical devices) often find that decoupling ERP from work order ownership introduces more long-term risk than it removes. MES can still be the de facto operational “source of truth” for what really happened on the shop floor, even when ERP remains the legal and financial system of record for the work order entity.
Trying to keep ERP as the authoritative source for every work order detail usually leads to poor fit for real-time execution and compliance traceability. ERP systems are not optimized to capture per-unit measurements, tool usage, signatures, rework paths, or complex electronic batch records in a way that is usable at the station level. Pushing operators to work primarily in ERP screens often results in workarounds, shadow spreadsheets, or paper logs, which undermine the very data integrity the single-system approach is supposed to protect. Retrofitting ERP to capture MES-level detail usually means heavy customization that is hard to validate, expensive to maintain, and brittle when vendors update the platform. Over time, this can create more integration debt and validation overhead than a clean ERP–MES split with clearly defined interfaces and responsibilities.
In brownfield environments with existing ERP, legacy MES or custom shop-floor systems, and constrained downtime, a full realignment of system-of-record boundaries is rarely practical. Most plants cannot afford to halt production while they rip out existing integrations, requalify new interfaces, and retrain staff across finance, operations, and quality. Interfaces between ERP and MES are often point-to-point, fragile, and poorly documented, so changing which system is authoritative for work orders can expose hidden assumptions in dozens of reports and workflows. In aerospace-grade or similar contexts, any substantial change to work order ownership also brings a validation and qualification burden, with corresponding documentation and audit exposure. As a result, many successful programs adopt an incremental approach: first stabilize the current split, then refine data ownership field by field rather than attempting a big-bang switch.
Instead of declaring ERP or MES as the system of record globally, it is safer to define ownership at the attribute level. For example, the work order number, order type, and planned quantity might be ERP-owned, while operation start/end times, actual equipment used, and parameter measurements are MES-owned. This should be documented in a data responsibility matrix that is under change control and linked to interface specifications and validation evidence. Audit trails in both systems must make it clear which attributes can be changed where and under what authorization. In regulated contexts, this also means aligning e-signature, time-stamping, and user-account management across systems so that records can be reconciled and defended during inspections.
Choosing where work order system-of-record boundaries sit involves tradeoffs between financial integrity, real-time control, traceability depth, and cost of change. Plants with strong corporate ERP standards and centralized finance will usually favor ERP as the header system of record, with MES owning granular execution history. Highly automated greenfield plants, or those with MES tightly integrated into planning, may push more planning responsibility into MES, but this is less common in heavily regulated, multi-site enterprises. Key decision criteria include: how MRP and costing are implemented today, how painful it would be to revalidate changed processes, and how dependent upstream and downstream systems are on the current work order data model. Making these tradeoffs explicit—and documenting why specific attributes are owned by ERP versus MES—is usually more important than aiming for a doctrinal “one system of record” answer.
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.
