Global – October 27, 2026 -- Industrial historians that store an OPC UA value and timestamp without the accompanying 32-bit StatusCode can pass stale, substituted, or Bad readings into averages, alarm reviews, and production calculations as ordinary process measurements.

Global – October 27, 2026 -- The right OPC UA collection rate is the slowest configuration that still preserves the process behavior needed for operations and historical analysis, and it is set across five separate stages rather than one "scan rate." Device updates, server sampling, subscription publishing, filtering and historian storage each have their own timing. Treating them as one setting can add load without adding information, or hide a pressure transient the historian was expected to explain.

Global – October 27, 2026 -- An OPC UA NodeId tells a client which node to read, but not which pump, line or measurement that node represents in the plant. Reliable mapping therefore keeps source identity, browse path, equipment identity and user-facing label connected but stored as separate fields.

Global – October 27, 2026 -- The taosX gRPC interface in TDengine TSDB Enterprise is unencrypted by default, so teams collecting OPC UA data across network zones must explicitly enable and verify TLS, according to TDengine's security documentation. The point is part of a wider OT/IT integration checklist: a working OPC UA client beside the server proves only that the endpoint and credentials work locally, not that the same path should be opened from an enterprise historian into the control network.