Integrating Smart Assembly Lines with Manufacturing Execution Systems (MES): A Practical Guide
- This architecture binds station-level PLC control to plant MES databases for part genealogy, process parameter locking and real-time yield reconciliation. Each relay carrier receives a laser-etched 2D matrix code; every measured process value is timestamped and linked to the unique identifier before transfer to the factory server.
- A fiber laser marks Data Matrix codes directly on relay bases or carrier trays at 120 parts per minute. The code stores batch ID, mold cavity number and raw material lot number. Vision verifies mark contrast and position tolerance ±0.15 mm before downstream assembly. Failed codes trigger Poka-Yoke interlock to block non-trackable units from entering the process flow.
- Three protocol tiers run concurrently across the production cell. Modbus TCP handles high-frequency register reads for servo position and analog sensor values. OPC UA delivers structured process data and secure session authentication between cell controller and MES. MQTT transmits lightweight event alarms and yield counters to the plant SCADA dashboard over low-bandwidth links.
- Each finished relay record carries a fixed payload: peak riveting force, force–displacement curve integral, resistance spot welding Joule value, 4‑wire Kelvin contact resistance, station cycle start and finish timestamps, and operator ID. Records are rejected if contact resistance exceeds 0.5 mΩ or riveting force falls outside the configured process window.
- Local edge controllers cache up to 72 hours of completed part records in non‑volatile storage. When uplink packet loss exceeds 15 % for longer than 3 s, the cell switches to offline buffering mode. All queued telemetry uploads resume automatically once TCP handshake recovers, without halting servo motion or part transfer.

| Parameter | Modbus TCP | OPC UA | MQTT |
|---|---|---|---|
| Typical Sampling Interval | 1–5 ms | 20–100 ms | 100–500 ms |
| Max Payload Size | 256 bytes | 64 kB | 256 bytes |
| Native Session Security | None | AES‑256, certificate authentication | Optional TLS |
| Suitable Data Type | Servo registers, analog sensor values | Structured process logs, recipe downloads | Alarms, yield counters, status events |
| Latency Under Load | Low | Medium | Low |
| Bandwidth Footprint | Medium | High | Very low |
| Support for Timestamped Traceability Records | Limited | Full native support | Partial |
| Edge Offline Buffer Compatibility | Requires custom logic | Built‑in session resumption | Lightweight queueing |
| Relative Integration Effort | Low | High | Medium |
| Common Deployment Role | Real‑time I/O telemetry | MES / recipe / traceability backbone | SCADA dashboard and alerting |