ISA-95 MES Integration: SAP ERP & Rockwell FactoryTalk

Key Takeaways

• ISA-95 standardizes ERP↔MES interfaces using object models (ProductionRequest, ProductionPerformance, Part Genealogy) and B2MML XML for reliable exchange.
• Architect SAP ERP → SAP MII → B2MML → Rockwell FactoryTalk (MES) with asynchronous messaging, canonical models, and delivery guarantees for order dispatch and genealogy.
• Map SAP process orders/BOM to ISA-95 SegmentRequirement and ProductionSchedule objects; return ProductionPerformance messages for yields and lot traceability.
• Mitigate temporal mismatch and data mapping errors with message queuing (Kafka/MQ), schema validation, and pilot-by-line rollouts.
• Validate end-to-end with B2MML conformance tests, OPC UA connectivity checks, and SAP BAPI/RFC reconciliation to ensure inventory and quality integrity.

Introduction

Integrating SAP ERP with Rockwell FactoryTalk under ISA-95 delivers a deterministic, auditable path for production orders, part genealogy, and performance feedback. The ISA-95 object model and B2MML message schemas reduce bespoke code and provide a repeatable blueprint for enterprises. This post presents an architected integration pattern, object mappings, messaging guarantees, common pitfalls, and a practical rollout checklist based on industry implementations and standards.

For a primer on ISA-95 concepts, see our internal knowledge overview: /knowledge/isa-95-integration

High-level architecture

Implement a layered architecture that preserves concerns and enforces ISA-95 semantics:

• SAP ERP (Level 4): Plans production, issues process orders, maintains master data (BOM, routing).
• Integration Layer: SAP MII or middleware (transformations, orchestration, B2MML generation). Provide delivery guarantees (MQ/Kafka).
• MES (Level 3): Rockwell FactoryTalk ProductionCentre / Plex — consumes ProductionRequest, performs execution, records genealogy and yields.
• OT Interface (Levels 0–2): PLCs, SCADA, and OPC UA gateways provide real-time signals and serial number capture.

Sequence:

1. SAP creates process order → SAP MII transforms to B2MML ProductionSchedule / ProductionRequest.
2. Middleware posts to MES webservice or message queue; MES acknowledges and reserves line capacity.
3. MES executes; captures serials, operations, and quality events; returns B2MML ProductionPerformance.
4. MII maps performance to SAP BAPIs/RFCs (e.g., goods receipt, confirmation, inventory adjustments).

Key platform links: /platforms/sap and /platforms/rockwell-automation

ISA-95 object mappings and message flow

Use ISA-95 Parts 2 and 5 objects consistently to ensure traceability.

• ProductionRequest / ProductionSchedule

  • Source: SAP process order / planned order
  • Contains: Part ID, operation sequence, planned start/finish, required resources, BOM reference
  • Transformation: SAP MII -> B2MML ProductionSchedule/ProductionRequest (validate against B2MML schema)

• ProductionPerformance

  • Source: MES execution events
  • Contains: actual quantities, yield, scrap, runtimes, operator ID, timestamps
  • Usage: Update SAP via BAPI/RFC (e.g., PI_PROD or goods receipt processes)

• Part Genealogy (ISA-95 Part 4)

  • Source: MES serialized production and parent-child relationships
  • Contains: serialized part IDs, lot numbers, process step lineage
  • Usage: Feed back to SAP for traceability, warranty, and compliance reporting

Reference: ISA-95 standard documentation (ISA) and B2MML patterns: https://www.isa.org/standards-and-publications/isa-95-standard and https://www.symestic.com/en-us/blog/mes/isa95

Integration pattern: SAP MII + B2MML + FactoryTalk

Recommended pattern components and rationale:

• SAP MII (or equivalent middleware) for canonical model transformations, transaction orchestration, and B2MML emission. SAP lacks native ISA-95 messaging, so MII provides the required mapping and queuing features (see SAP community guidance: https://community.sap.com/t5/additional-blog-posts-by-members/integration-of-sap-erp-and-mes-via-mii-12-0-using-isa-95-standard-in/ba-p/12888459).
• B2MML as the canonical XML interchange format reduces custom field drift and accelerates validation.
• Rockwell FactoryTalk (ProductionCentre/Plex) natively consumes ISA-95/B2MML patterns or can accept via its API/OPC UA adapters. Rockwell documentation outlines MES capabilities and recommended Level 3 practices: https://www.rockwellautomation.com/content/dam/plex/documents/pdf/mes/WhatIsMES_Feb2025.pdf
• Message broker (Kafka, RabbitMQ) for asynchronous decoupling between ERP and MES, handling burst loads and temporal mismatches.

Typical message flows:

• Synchronous for scheduling queries and status checks.
• Asynchronous for production execution events and heavy telemetry, using guaranteed delivery.

Comparison: Integration approaches

| Attribute | SAP MII + B2MML (Canonical) | Direct SAP IDoc/RFC | OPC UA Gateway + MES | |----------:|----------------------------|---------------------|----------------------| | Standard compliance | High (ISA-95/B2MML) | Low-medium | Medium (depends on mapping) | | Development overhead | Moderate | High (custom mappings) | Low–Moderate | | Temporal resolution | Good (async + transformation) | Tight but brittle | Good for OT data | | Genealogy support | Native (B2MML Part 4) | Requires custom extensions | MES-dependent | | Scalability | High with MQ/Kafka | Limited by RFC throughput | High for telemetry |

Common pitfalls and mitigations

• Temporal mismatch: ERP schedules operate on minutes/hours; MES requires second-level events. Mitigate with async brokers (Kafka), backpressure controls, and local buffering in MES.
• Schema drift: Custom SAP fields cause B2MML parse errors. Mitigate by enforcing a canonical data dictionary and schema validation step in MII.
• Delivery guarantees: RPC-style calls can fail under load. Use message queuing with durable topics and idempotent consumers.
• Legacy OT connectivity: Older PLCs require OPC UA/DA gateways; validate signal mapping and time synchronization across systems.
• Security and compliance: Secure middleware endpoints with TLS, OAuth or client certificates; enforce RBAC for both SAP and MES APIs.

Testing, validation, and rollout

• Unit: Validate B2MML production messages against ISA-95 Part 5 schemas.
• Integration: End-to-end tests that create SAP process orders and verify ProductionPerformance reconciliation in SAP inventory and quality records.
• Pilot: Start with a single line/plant; iterate template for BOM, routing, and resource models.
• Performance: Load-test with synthetic orders to validate broker throughput and worst-case reconciliation times.
• Traceability: Run reverse genealogy queries from finished serialized unit back to raw material lots.

External references for patterns and industry results:

• Symestic ISA-95 overview: https://www.symestic.com/en-us/blog/mes/isa95
• SAP MII integration guidance: https://community.sap.com/t5/additional-blog-posts-by-members/integration-of-sap-erp-and-mes-via-mii-12-0-using-isa-95-standard-in/ba-p/12888459
• Rockwell MES overview: https://www.rockwellautomation.com/content/dam/plex/documents/pdf/mes/WhatIsMES_Feb2025.pdf
• Industry trend analysis: https://www.bowdark.com/blog/isa95-and-americas-digital-manufacturing-transformation

Security and compliance considerations

• Network segmentation: Enforce DMZ pattern for middleware; separate ERP, MES, and OT zones.
• Authentication: Use mutual TLS for service-to-service calls; consider OAuth/JWT for REST APIs.
• Data residency: Ensure serialized genealogy payloads comply with industry regulations (food, pharma).
• Audit trails: Preserve message IDs, timestamps, and checksums in MII and MES. Maintain immutable logs for recall scenarios.

Example implementation checklist

• Define canonical ISA-95 object dictionary (ProductionRequest, ProductionPerformance, SegmentRequirement).
• Implement SAP MII transforms and B2MML schema validation pipelines.
• Configure durable messaging (Kafka/RabbitMQ) with retry and dead-letter handling.
• Map SAP BAPIs/RFCs for confirmations and inventory updates.
• Configure FactoryTalk to ingest B2MML messages or accept via its API and expose genealogy services.
• Conduct pilot, performance, and compliance tests.

Key Benefits by use case

• Automotive: Faster order dispatch and reduced integration work (up to 60% less in documented cases) through B2MML canonical flows (see SAP/Rockwell case literature).
• Batch/process: Combine ISA-95 with ISA-88 recipes for repeatable batch execution.
• Recall readiness: End-to-end genealogy enables rapid isolation of affected lots.

Next Steps

To implement an ISA-95-compliant SAP↔FactoryTalk integration, our recommended services:

• /services/plc-programming — for OT connectivity and serial capture
• /services/scada-hmi-development — for supervisory integration and OPC UA gateway work
• /services/industrial-robotics — where robotics cells must be coordinated within MES workflows

Contact our team to build a pilot integration architecture, validate B2MML mappings, and execute a phased rollout aligned with ISA-95 compliance and your production KPIs.