Data Integrity

MQTT Historians Need Source Event Time, Not Arrival Time

Global – October 29, 2026 -- Historians that stamp MQTT messages with broker arrival time can display an old pressure reading as a new process condition, distorting aggregates, alarms and event order during outage replays.

Plain MQTT defines no process-time field

MQTT specifies only the transport of an application message. It prescribes no timestamp field, industrial clock model or time semantics. The publisher's application contract decides whether a payload carries a time, in what format and with what quality.

OPC UA's SourceTimestamp and ServerTimestamp concepts do not carry over to ordinary MQTT payloads. Broker receipt time and connector receipt time are useful operational observations, but they do not prove when a machine produced a measurement.

LabWare, Phizzle Launch Loop to Automate GxP Instrument Data Capture

Image
LabWare, Phizzle Launch Loop to Automate GxP Instrument Data Capture

Wilmington – October 29, 2026 -- LabWare and Phizzle have made LabWare Loop available by request to LabWare customers, with commercial availability planned for early 2027. The vendor-agnostic tool moves results from legacy and modern instruments directly into LabWare sample result records, replacing manual data handling with a verified chain of custody.

The workflow follows each GxP sample from sampling plan to result in a single auditable digital process. It supports 21 CFR Part 11, EU Annex 11 and ALCOA+ data integrity principles.

OPC UA Historians Should Store Source Time and Receipt Time

Image
OPC UA Historians Should Store Source Time and Receipt Time

Global – October 29, 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.

SourceTimestamp stays fixed as data passes through servers

The OPC UA specification defines SourceTimestamp as the time a data source applies to a value, ideally the last change of the value or status, generated as close to the source as possible. It does not change when the value passes through another OPC UA server. That makes it the best fit for sequence-of-events work, batch analysis and calculations tied to when the process changed.

Reconnected OPC UA Links Can Still Leave Historian Data Gaps

Image
Reconnected OPC UA Links Can Still Leave Historian Data Gaps

Global – October 29, 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.

In the common architecture of device or PLC, OPC UA server, collector and historian, the first step is to find which link failed. If the device or server stops producing values, the collector has nothing to recover unless the source keeps its own history. If the collector cannot reach the historian, a durable local buffer can protect messages it has already collected. Treating all three as a generic network outage leads to the wrong fix.

MQTT QoS 1 Suits Most Industrial Telemetry; Duplicates Need Handling

Image
MQTT QoS 1 Suits Most Industrial Telemetry; Duplicates Need Handling

Global – October 28, 2026 -- QoS 1 is the practical starting point for most industrial telemetry over MQTT, but none of the three QoS levels guarantees a complete historian, according to engineering guidance tied to the OASIS MQTT 5.0 standard.

QoS 1 reduces the risk of losing a message on an MQTT delivery hop. The receiving system must tolerate duplicates. QoS 0 fits replaceable readings where low overhead matters more than complete delivery. QoS 2 is reserved for flows where duplicate delivery on that hop is unacceptable and the extra protocol exchange is justified.

MQTT QoS covers one sender-receiver hop, not the whole pipeline

The OASIS MQTT 5.0 standard defines QoS for a single delivery flow. A device publishing to a broker is one flow. The broker sending to a subscribing collector is another, and it can use a different QoS depending on the original publication and the subscriber's granted maximum.

Breaker Launches Bot-Filtering Tool as 87% of Email Clicks Found Fake

Image
Breaker Launches Bot-Filtering Tool as 87% of Email Clicks Found Fake

Austin, Texas – October 05, 2026 -- Nonhuman sources generated 87.3% of all recorded click activity across 1.77 billion emails processed in the first quarter of 2026, according to data from Omeda, raising questions about the reliability of engagement metrics marketers use to evaluate campaigns and report results to sponsors. Even newsletters, which registered the lowest bot share among major high-volume email categories, still saw 82.4% of clicks attributed to automated activity rather than human readers.

Breaker, a B2B-focused newsletter platform, has launched RealClickTM alongside a Model Context Protocol (MCP) server and API designed to address distorted click data and unchecked AI access to marketing workflows.

121G Adds AI Anomaly Monitoring to 10Bridge Healthcare Data Platform

Image
121G Adds AI Anomaly Monitoring to 10Bridge Healthcare Data Platform

Carrollton, Ga. – September 23, 2026 -- 121G has added AI Process Anomaly Monitoring to its 10Bridge data acquisition and interoperability platform, giving healthcare organizations automated detection of irregular file and data processing behavior before it disrupts operations.

New tool flags data deviations before they cause integration failures

The capability continuously monitors jobs processed through 10Bridge, automatically identifying transactions, files, or data that fall outside typical processing patterns. When an anomaly surfaces, the system alerts designated users so they can investigate and resolve issues preemptively, rather than after a failure disrupts downstream systems.

ActBlue Forensic Review Finds 99.99% of $990M in Donations U.S.-Verified

Image
ActBlue Forensic Review Finds 99.99% of $990M in Donations U.S.-Verified

Boston – September 20, 2026 -- ActBlue said an independent forensic review of its 2023 contribution data found that 99.99% of nearly $990 million in political donations came from donors who provided a U.S. address or a valid U.S. passport number, directly rebutting Congressional Republican claims that the platform facilitated illegal foreign contributions.

Forensic audit shows foreign-address donations were rare and screened

Only 0.13% of all 2023 contribution dollars came from Americans living abroad, with 99.87% originating from donors listing domestic addresses, according to the review. ActBlue said its compliance policy required any donor entering a foreign address to supply a U.S. passport number before a contribution could be submitted, regardless of payment method.