ERP and MES integration: the data decisions manufacturers need first

The practical answer

ERP and MES integration should begin with ownership of records and the meaning of each status change. Decide which system controls orders, operations, quantities, and revisions, then define how updates move and how conflicts are resolved. Connecting APIs before agreeing on these rules can spread inconsistent data faster.

Which system owns each piece of information?

Map the records used in the selected workflow and identify the system allowed to change each field. Order status, production progress, and inventory availability may represent different business concepts even when their labels look similar. Ask the people who depend on those fields to define them.

Avoid a blanket policy of synchronizing everything in both directions. That can turn a local correction into a recurring conflict. Start with one-way ownership for each field and document the limited cases where a receiving system may propose a change.

What timing and failure rules should be defined?

Decide whether the workflow needs immediate updates, periodic batches, or a scheduled reconciliation. Tie that choice to the decision being made. A management report and an operational dispatch screen can have very different requirements for freshness and availability.

Specify what happens when a message arrives twice, arrives late, or refers to an older revision. Use identifiers and state checks so retrying a failed transfer does not create a second business action. Make unresolved records visible to an owner rather than hiding them in a technical log.

Define a stable identifier for each record and event.
Specify authoritative fields and allowed transitions.
Track source revision and update time.
Handle duplicates and out-of-order updates.
Provide a reconciliation view and responsible owner.

Where does the integration boundary sit?

NIST SP 800-82 addresses security for operational technology. Use that distinction when describing the project boundary: an integration that reads production records requires a different review from one that can alter equipment or process settings.

Keep the initial scope explicit in access permissions and implementation. If the objective is reporting, use the approved reporting interface and avoid unnecessary write authority. Any expansion should be reviewed with the people accountable for the affected business and plant systems.

Reference: NIST: Guide to Operational Technology Security, SP 800-82 Rev. 3

How do you roll out without losing visibility?

Compare the proposed integration output with existing records before allowing it to drive consequential work. Reconcile counts and statuses, inspect differences, and document why each difference occurred. Include a recovery exercise in which a source system is temporarily unavailable.

For a Tennessee manufacturer expanding to additional sites, reuse the integration pattern only after checking local definitions and revisions. Agentix scopes connected systems around the business handoff, so the deliverable includes reconciliation and operating responsibility alongside the connection itself.

Common questions

Does this integration require AI?

Often the core record transfer does not. Deterministic rules are appropriate for identifiers, state transitions, and reconciliation. AI may assist with interpreting unstructured notes or explaining exceptions, provided those tasks have their own controls.

Should every update happen in real time?

Only when the business decision requires it and the systems can support it reliably. Define acceptable delay, outage behavior, and recovery expectations before choosing a transport or update schedule.

Sources & editorial notes

Published by Agentix. Implementation recommendations are our analysis. Workflow examples describe proposed approaches, not completed client projects or measured results. Product documentation was checked September 30, 2026.

NIST: Guide to Operational Technology Security, SP 800-82 Rev. 3

Send corrections with a supporting source to hello@goagentix.com.

Put the guide to work

Agent ecosystems

Connect agents, applications, and people into a coherent operating process with shared context, defined ownership, and reliable handoffs between responsibilities.

Explore this service →Book an AI strategy call