Manufacturing & Industrial Technology

TDengine Guide: Historian Data Needs Context Before AI Training

Image
TDengine Guide: Historian Data Needs Context Before AI Training

Global – October 27, 2026 -- A historian export of tags and timestamps is rarely a training-ready dataset for Industrial AI, according to TDengine guidance that tells engineers to establish what each measurement means, when it happened, which asset produced it and whether it is reliable before data reaches an external model-training workflow.

Engineers define the pump decision before selecting data

For a centrifugal pump, the guiding question is whether a reliability engineer should review the pump given its recent operating signals. That differs from asking a model to declare the cause of a failure. Records created after a maintenance decision must not become inputs, because they would not exist when the model makes its prediction.

WEMAG Turns 90 With 200+ Staff, 5 Million Articles, Robotics Push

Image
WEMAG Turns 90 With 200+ Staff, 5 Million Articles, Robotics Push

Fulda – October 27, 2026 -- WEMAG, the family-run tool and machinery distributor from Fulda, is marking its 90th anniversary in 2026 with more than 200 employees, six locations in Germany and a range of roughly five million articles, and is now investing in robotic order picking and automated logistics.

Merchant Adolf Ruland founded WEMAG Werkzeug- und Maschinengesellschaft on May 5, 1936. WEMAG GmbH & Co. KG is now run by the fourth generation. Helmut Schaus, the founder's son-in-law, took over management in 1948, followed by his son Joachim Schaus in 1972. Christopher Schaus joined in 2004, entered management in 2010 and received the symbolic company key from his father in 2018.

Alfa Laval Q3 Orders Surge 36% to SEK 23.2 Billion

LUND, Sweden – October 27, 2026 -- Alfa Laval's third-quarter order intake rose 36 percent to SEK 23.2 billion (17.1), with organic growth of 33 percent, while the company guided to somewhat lower demand in the fourth quarter.

Sales grow 8 percent as margin narrows to 18.1 percent

Net sales increased 8 percent to SEK 18,596 million (17,244), up 6 percent organically. Adjusted EBITA rose 6 percent to SEK 3,364 million (3,180). The adjusted EBITA margin slipped to 18.1 percent from 18.4 percent a year earlier.

Result after financial items reached SEK 3,050 million (2,967). Net income fell to SEK 2,262 million (2,303), and earnings per share declined to SEK 5.40 (5.53).

Operating cash flow climbs to SEK 3.4 billion

Cash flow from operating activities reached SEK 3,373 million, up from SEK 2,206 million in the prior-year quarter.

IGZ Adds AI-Driven Pick by Robot to LUKE Family for SAP EWM

Image
IGZ Adds AI-Driven Pick by Robot to LUKE Family for SAP EWM

Germany – October 27, 2026 -- IGZ Ingenieurgesellschaft für logistische Informationssysteme mbH is offering Pick by Robot, a plug-in robotics solution in its LUKE family that automates single-item picking directly within SAP EWM and runs 24/7.

AI image processing drives item recognition in round-the-clock operation

The system relies on AI- and deep-learning-based image processing for item recognition. IGZ says this delivers reliable identification and high process reliability across continuous operation.

Integrated tool changer widens the range of handled items

A built-in tool changer expands the spectrum of articles the robot can process. IGZ cites this as the source of the solution's flexibility.

OPC UA Connection Test Proves Only Part of Historian Data Path

Image
OPC UA Connection Test Proves Only Part of Historian Data Path

Global – October 27, 2026 -- A successful OPC UA connection check shows only that a client can reach the endpoint. It does not prove the intended nodes are readable, monitored, mapped or written to the historian, according to a five-step troubleshooting workflow for industrial data pipelines.

The method starts with one known, changing point, traced from the OPC UA server to one expected historian table. Large tag lists hide the first failure.

OPC UA vs MQTT: Match the Protocol to the Plant Data Role

Image
OPC UA vs MQTT: Match the Protocol to the Plant Data Role

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.

OPC UA preserves equipment context that MQTT leaves to the architect

OPC UA is a family of specifications covering Client/Server services, information modeling, Alarms and Conditions, Historical Access and PubSub. A server can organize measurements under equipment objects, attach engineering units and ranges, and expose status, timestamps and methods. A client can browse that address space instead of encoding meaning in topic strings.

Not every server delivers a rich model, however. Some expose flat tag lists, incomplete metadata or vendor-specific structures.

OPC UA Historians Need Alarm Records, Not Just Tag History

Image
OPC UA Historians Need Alarm Records, Not Just Tag History

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.

Tag history stores values, not alarm lifecycles

An OPC UA client collects a variable through a monitored item. When DataChange criteria are met, the server sends a DataValue that the historian can store with source timestamp, server timestamp, and StatusCode, depending on the collector mapping. Sampling, deadbands, queues, and timestamp selection determine how much process behavior survives.

Slowest OPC UA Rate That Preserves Process Behavior Is Right

Image
Slowest OPC UA Rate That Preserves Process Behavior Is Right

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.

Server sampling cannot beat the source update rate

A PLC may update a temperature every 500 milliseconds while the OPC UA server refreshes its internal value once per second. A client request to sample every 100 milliseconds then re-reads the same value or detects changes no sooner than the server exposes them.

OPC UA Mapping: Keep NodeId, Asset Key and Display Name Separate

Image
OPC UA Mapping: Keep NodeId, Asset Key and Display Name Separate

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.

Namespace indexes can change between sessions, so URIs must be stored

A NodeId such as ns=4;s=Pump01.DischargePressure uses 4 as an index into the session's NamespaceArray. The OPC UA specification allows that index to change in a later session. A stored ns=4 string without its namespace URI can point to the wrong namespace after the server's table changes. Mappings should retain the endpoint, namespace URI, identifier type and identifier, and resolve the current index at connection time.

TDengine taosX gRPC Is Unencrypted by Default in OT-IT Links

Image
TDengine taosX gRPC Is Unencrypted by Default in OT-IT Links

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.

Zones and flows come before collector placement

Segmentation protects more than confidentiality. OPC UA protocol security provides application authentication, message integrity and confidentiality, while network controls provide routing boundaries, firewall policy, inspection and isolation. Neither replaces the other: an encrypted session can still cross an overbroad firewall rule, end on a compromised collector, or run under an over-privileged account.