Digital Twin ERP and MES Integration with ISA-95

Q: How should a digital twin integrate with ERP and MES?

Treat the twin as a read model over systems that already own the facts. The ERP owns production orders, bills of materials, materials and cost. The MES owns dispatch, as-built genealogy and quality results. The historian owns process time series. The twin subscribes to events from each owner, composes them into a current view, and owns only derived facts such as predictions and simulations. When it needs to change something, it sends a command to the owning system and waits for that system to confirm through its normal events.

Q: What is ISA-95 and why does it matter for digital twins?

ISA-95, also published internationally as IEC 62264, is the standard for integrating enterprise business systems with manufacturing control systems. It defines a hierarchy in which level 4 covers business planning and logistics, typically the ERP, and level 3 covers manufacturing operations management, typically the MES. Part 2 specifies the information exchanged across the level 3 to level 4 interface, and Part 3 models the level 3 activities. A twin that respects those boundaries inherits decades of agreed vocabulary and avoids inventing its own conflicting model of orders and production.

Q: Should a digital twin write data back into SAP or the MES?

Not directly. Writing into ERP or MES databases bypasses their validation, audit trails and vendor support, and it makes the twin a second owner of the same fact. Instead, send commands through the owner's interface, such as an ISA-95 job command to the MES or a change request to a planner in the ERP. Carry an idempotency key, send through an outbox so retries are safe, and do not update the twin until the owner confirms. Anything that changes ERP orders or dates should require human approval.

Q: What is B2MML and should I use it?

B2MML is MESA International's XML implementation of the ISA-95 object models, covering things such as production schedules, production performance, equipment and material definitions. It gives ERP and MES integrations a standard schema instead of a bespoke format. If your MES and ERP integration layer support it, or the OPC UA ISA-95 Job Control companion specification, use the standard model. The adoption cost is real, but it pays back as soon as you add a second plant or a second MES vendor, because the twin does not need a new adapter dialect.

Q: How does OPC UA fit into a digital twin architecture?

OPC UA is the common way to read process values and equipment state from the control layer. Use OPC UA subscriptions through an edge gateway that publishes to your event backbone, rather than letting the twin connect to PLCs directly. Set sampling intervals to the decision you need: around 100ms can be reasonable for a fast process value feeding an anomaly model, while scheduling rarely needs faster than minutes. The OPC Foundation also publishes an ISA-95 Job Control companion specification for exchanging job orders and responses with the MES over OPC UA.

Q: Why do digital twin projects lose the trust of planners and operators?

Usually because the twin disagrees with the system people already trust. If the twin stores its own copy of order quantities, due dates or work-in-progress, it drifts after missed events, manual corrections and outages. The first time the twin contradicts SAP, planners stop using it. Prevent this by owning no borrowed facts, building state as a projection from owner events, showing new state only after the owner confirms a change, and running a scheduled reconciliation report that turns drift into a visible queue of defects with owners.

Q: What is the Asset Administration Shell and do I need it?

The Asset Administration Shell, specified by the Industrial Digital Twin Association, is a vendor-neutral way to describe an industrial asset and its data as a set of submodels. It is useful for multi-vendor and multi-site programmes because it gives every asset a standard digital description. You do not strictly need it to start. What you do need from day one is a governed asset identity map linking the ERP equipment number, the MES work centre and the OPC UA node for each asset, because most twin data problems are really identity problems.

Q: When should a manufacturer not build a digital twin?

When there is nothing trustworthy for the twin to compose. If execution data lives on paper and spreadsheets with no MES, or if ERP master data is unreliable, a twin will visualise bad data convincingly and erode trust. Digitise execution and clean master data first. Also avoid twins that write setpoints to PLCs unless they are engineered and certified as control systems. And avoid starting with a 3D visualisation; get ownership, identity and reconciliation right with a simple table view before investing in rendering.

Satyam Kumar

ブログに戻る

architecture

The Twin Is a Read Model, Not a System of Record: Integrating a Digital Twin With ERP and MES Using ISA-95 (2026)

By Satyam KumarOctober 2, 202611 min read

digital twin digital twin erp integration digital twin mes integration isa-95 iec 62264 manufacturing execution system sap mes integration opc ua b2mml asset administration shell industrial digital twin it ot integration manufacturing data architecture cqrs read model transactional outbox smart factory architecture

The Twin Is a Read Model, Not a System of Record: Integrating a Digital Twin With ERP and MES Using ISA-95 (2026)

Frequently Asked Questions

この記事を共有する

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

AI＆クラウドアーキテクト。数百万人にスケールするシステム構築を支援。

LinkedIn GitHub

The Twin Is a Read Model, Not a System of Record: Integrating a Digital Twin With ERP and MES Using ISA-95 (2026)

Frequently Asked Questions

この記事を共有する

Comments

Leave a comment