Data Collection and Integration
What the exam tests
This domain tests how MES acquires and contextualizes plant data: PLC and SCADA integration, OPC UA, MQTT, REST, historians, barcode/RFID, time synchronization, and message reliability.
Core rules
- PLCs provide control-level signals; SCADA supervises equipment; historians store time-series data; MES adds order, material, personnel, and quality context.
- OPC UA provides structured, secure, bidirectional interoperability. MQTT is lightweight publish/subscribe and suits event and telemetry transport. REST is common for business-system integration but is not a plant-floor fieldbus.
- B2MML is an XML implementation of ISA-95 message content for ERP-to-MES integration.
- Timestamps need a common time base and time zone. A correct value with the wrong timestamp can be attributed to the wrong shift or order.
- Integration should be idempotent where duplicate messages are possible, and store-and-forward protects against network outages.
Worked example
A filling line sends a completion event at 22:58 local time, but the MES server stores UTC and the shift boundary is 23:00 local. If the integration applies the wrong offset, the event lands in the next shift. The fix is to standardize on UTC in transport, convert at presentation, and include the source timestamp plus receipt timestamp. Reasoning: shift attribution depends on time context as much as quantity.
Traps
- Assuming more frequent polling always improves accuracy; it can add load without adding events.
- Losing context by storing a tag value without equipment, order, or lot identifiers.
- Ignoring duplicate delivery and creating double production confirmations.
- Mixing local time and UTC across historians and MES.