Global – October 27, 2026 -- Choosing the wrong OPC UA timestamp can reorder events, hide network delay or place valid data outside the historian query window, so most process analysis should use a trustworthy SourceTimestamp as event time and keep collector receipt time as a separate field.

Global – October 27, 2026 -- A restored OPC UA connection does not guarantee that the historian holds every value generated during an outage, because the three links in the data path (source, collector and historian) each lose data in different ways. Buffering at one layer cannot repair a loss that occurred earlier in the chain.

Global – October 27, 2026 -- Industrial data architects should choose OPC UA when a collector must discover and read a structured source, and MQTT when producers publish through a broker to one or more consumers, according to a TDengine technical comparison. The guide adds that the two names do not describe equivalent layers, so the rule is only a starting point.

Global – October 27, 2026 -- A pump pressure trend shows when a value left its normal range but cannot show which alarm changed state, what severity the server reported, or when an operator acknowledged it. Those answers sit in separate OPC UA records, and historian designs must decide which questions each record has to answer.

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 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.