Factory Floor Event-Driven MES Integration Architecture

Role: Lead Enterprise Integration Architect specializing in industrial automation systems and event-driven architectures.

Context

• Shop-floor MES core: {{mes_core_system}}
• Enterprise ERP backend: {{erp_backend_system}}
• Event broker backbone: {{event_broker_technology}}
• Critical manufacturing transactions: {{critical_transaction_types}}
• Business continuity targets: {{failover_rpo_rto}}
• Cybersecurity framework: {{cybersecurity_compliance_standard}}

Task

Author a comprehensive event-driven integration architecture specification that decouples {{mes_core_system}} and {{erp_backend_system}} via {{event_broker_technology}}, ensuring real-time consistency for {{critical_transaction_types}} compliant with {{cybersecurity_compliance_standard}}.

Method

1. Analyze transaction lifecycles for {{critical_transaction_types}} to identify producers, consumers, and idempotency keys.
2. Design partitioned topic topologies and schema registry governance rules inside {{event_broker_technology}}.
3. Architect the transactional outbox pattern on {{mes_core_system}} to guarantee exactly-once message delivery semantics.
4. Define dead-letter queue (DLQ) routing, automated retry policies, and human-in-the-loop manual reconciliation consoles.
5. Design stateful stream processing logic for order dispatching, material consumption recording, and work-in-progress reconciliation.
6. Formulate network segmentation, mutual authentication, and fine-grained ACLs satisfying {{cybersecurity_compliance_standard}}.
7. Detail cross-region replication and split-brain resolution protocols ensuring {{failover_rpo_rto}} commitments.

Constraints

• MUST enforce idempotent consumers across all services consuming from {{event_broker_technology}}.
• MUST NOT permit synchronous blocking HTTP/RPC calls between {{mes_core_system}} and {{erp_backend_system}} in runtime paths.
• Message schemas MUST enforce backward and forward compatibility via an enforced schema registry.
• Outbox polling latency MUST NOT exceed 100 milliseconds for safety-critical execution events.

Output format

Deliver an integration architecture specification structured as follows:

1. Executive Architecture Summary & Data Flow Matrix
2. Event Topology & Topic Partitioning Design (configured for {{event_broker_technology}})
3. Outbox Pattern & Reliable Delivery Specification
4. Idempotency & Error Handling (DLQ, Poison Pill Mitigation)
5. Security, Access Control & {{cybersecurity_compliance_standard}} Compliance
6. High Availability, Disaster Recovery & RPO/RTO Metrics Ensure length is between 800 and 1200 words.

Self-review

• Confirm that every transaction in {{critical_transaction_types}} is mapped to a concrete event payload schema.
• Verify that failover strategies strictly align with {{failover_rpo_rto}} limits.
• Ensure zero synchronous point-to-point coupling between the MES and ERP layers.