The Status Problem at the Company Line
When a brand owner or OEM relies on a contract manufacturer, production status may not live in one system. MES sits at the edge of operational technology and information technology and must interact with enterprise applications and OT data sources depending on the organizational solution landscape. Across company boundaries, that interaction becomes a governance challenge as well as a technical one.
The right question is not "how do we get more data" but rather: which production events need to cross the company boundary, at what cadence, and with whose confirmation?
Why the Gap Persists
MES can interact with ERP to get production and purchase order information, master data about parts and products, inventory availability, and bill of materials. MES would also report back to ERP for the status of orders, actual material and labor consumption during production, and machine status. That exchange design varies based on the systems MES interacts with.
The core tension is that granular internal data from ERP, MES, and QMS is typically not shared with external parties because it contains proprietary manufacturing details that protect intellectual property. A contract manufacturer has legitimate reasons to keep its process parameters, machine configurations, and labor routing private. The OEM has a legitimate need to know whether its order is on track. What information should cross the boundary, in what form, and who is accountable for its accuracy are questions that require deliberate design to answer.
Defining Useful Events Before Choosing a Mechanism
Not every MES event belongs in the OEM's planning system. Organizations can selectively extract and transform internal activities into shareable supply chain event data, filtering out proprietary manufacturing details to protect intellectual property.
Order start and completion confirmations allow the OEM to update its schedule and customer commitments. If the partner's MES records a material shortage or a substitution against the OEM's bill of materials, that event may affect the OEM's inventory position and quality record. If PLM is present, MES can interact with it to get a detailed bill of process, work instructions, and in some cases the bill of materials. MES would also report to PLM about process execution information, non-conformances, and BOM variations.
Shipment readiness may be a natural starting point for agreement because both parties share an interest in accurate delivery timing. Events that may warrant staying internal include machine-level cycle times, internal labor routing, process parameters, and detailed work instructions. Supply chain event information encapsulated inside traceability records such as Make, Assemble, Store, Ship, and Receive records represents pedigree information that can be shared without exposing internal process detail. Distinguishing pedigree information from internal process data is a practical way to scope the initial partner conversation.
Cadence and Confirmation
Event selection answers what crosses the boundary. Cadence and confirmation answer when and with whose authority.
Cadence should match the decision it supports. A material shortage signal or quality hold may need near-real-time notification because the response window is short. Shipment readiness needs to arrive before the OEM's transportation booking cutoff, which is a specific operational deadline. Ask what decision each event enables and how quickly that decision must be made; the answer sets the required update frequency.
Transmission and confirmation are related but distinct questions. A status update from the partner's system tells the OEM what was recorded, but it does not always tell the OEM whether a human has reviewed and accepted that status. Ask whether a system-generated signal is sufficient for a given event type, or whether a named acknowledgment from the partner's production or quality team is required. Who is responsible for validating an incoming signal before it updates the OEM's schedule is also a question that should be assigned deliberately rather than discovered during an exception.
Approaches and Their Tradeoffs
Structured file exchange. The partner exports a defined set of status records on a scheduled basis, and the OEM imports them into its planning system or a staging layer. Latency is the primary tradeoff: a daily file does not support real-time exception management, and file format errors can delay the entire batch.
Portal-based status entry. The OEM provides a web portal where the partner's production team enters status updates against specific orders. This approach keeps integration requirements on the partner's side minimal, but update frequency and accuracy depend on the partner's operational discipline and staffing.
Direct MES-to-ERP integration. MES can interact with ERP to get production and purchase order information, master data about parts and products, inventory availability, and bill of materials. MES would also report back to ERP for order status, actual material and labor consumption, and machine status. The design for this pattern varies based on the systems MES interacts with. Before committing to this approach, ask whether the partner's MES can reliably expose the required events. Also ask whether the OEM's integration layer can maintain the connection over time. The gap between what a partner's MES can theoretically expose and what it can reliably maintain in production can be significant.
Event-based traceability records. Rather than integrating MES directly to ERP, the partner publishes defined supply chain events to a shared traceability layer. Supply chain event information encapsulated inside traceability records such as Make, Assemble, Store, Ship, and Receive records represents pedigree information that can be shared without exposing internal process detail.
No single approach is universally correct. A partner with a modern MES and an API-capable integration layer may support direct event publishing. A smaller partner running a legacy system may only support structured file exports or manual portal entry. Metrotechs recommends evaluating each partner's actual system capabilities before committing to an integration pattern.
Separating Visibility from Production Control
Visibility without defined exception ownership can move the status-chasing problem from phone calls to dashboards without resolving it.
A well-designed visibility architecture serves both parties by defining a narrow, agreed set of shareable events. Organizations can selectively extract and transform internal activities into shareable supply chain event data, filtering out proprietary manufacturing details to protect intellectual property. That selective extraction is both a technical mechanism and a governance commitment.
A Practical Sequence for Getting Started
-
List the decisions that currently depend on manual status checks. For each one, identify the specific production event that would make the check unnecessary.
-
Scope the shareable event set with the partner. For each candidate event, ask whether it represents pedigree information the partner can share, or internal process detail that should stay private. This classification shapes the data model and the partner conversation.
-
Ask specifically what the partner's system can expose. What events does the MES record, what can it export or publish, and what integration interfaces are available?
-
Define cadence by decision type, not by technical convenience. Match the update frequency to the response window the OEM actually needs. Defaulting to real-time for everything raises integration cost and partner resistance without proportional operating benefit.
-
Assign a named owner for cross-boundary record validation. Before any data feed goes live, define who on the OEM side is responsible for reviewing incoming status signals, flagging discrepancies, and escalating exceptions.