I. Architecture Design for Master-Slave Deployment
Role Division: The SCADA industrial control computer functions as a local cache, storing real-time RC calibration operation data, while the MES server serves as the master data source, storing the complete RC calibration baseline archive and historical traceability data.
Advantages of Deployment: SCADA can maintain the execution of RC calibration tasks using its local cache, even in the event of a brief network outage in the workshop, thereby preventing data loss and production downtime.
II. Protocol Selection for Mainstream Synchronisation Communication
OPC UA Protocol: The most often employed solution, it supports cross-platform data interaction and facilitates real-time bidirectional synchronisation of RC calibration data with a latency of ≤100ms. It is an industrial-grade standard protocol.
MQTT Protocol: This protocol has been modified to accommodate weak network workshop scenarios. It utilises a lightweight message queue mechanism, supports breakpoint resumption, and automatically retransmits unsynchronised RC calibration data after network recovery.
Bidirectional Database Synchronisation: A synchronisation table for RC parameters is configured in both the SCADA and MES databases. Synchronisation operations are initiated automatically by database triggers in response to data modifications.
III. Configuration of the Core Synchronisation Rule
Real-time Data Synchronisation: The MES system is synchronised with the SCADA-collected real-time RC calibration data and temperature fluctuation data every 100ms to guarantee data real-time performance.
Benchmark Parameter Synchronisation: In the event that the MES updates the RC calibration benchmark parameters, they are promptly and automatically transmitted to the SCADA system, thereby guaranteeing that the judgement rules are identical on both sides and that there is no version deviation.
Breakpoint Resumption Mechanism: The system automatically compares the timestamps of the data on both sides and retransmits all RC calibration data from the interruption period to assure data integrity after network interruption recovery.
IV. Security and Verification Mechanism for Synchronisation
Cross-System Reconciliation Verification: Every morning, MES and SCADA automatically conduct a comprehensive reconciliation of RC calibration data. If the data on both sides is inconsistent, an anomaly alarm is immediately triggered.
Transmission Protection: The TLS 1.3 encryption protocol is employed during the synchronisation process, and all RC calibration data is digitally signed to prevent unauthorised tampering during transmission.
Hierarchical Access Control: The modification of synchronisation rules is restricted to administrator accounts. In order to prevent data inconsistencies that may result from inadvertent operations, ordinary maintenance personnel are not authorised to operate the synchronisation configuration.
