2026-08-14 · product
Adaptive routing now honors safety interlocks natively
The routing engine now evaluates every candidate re-route against the active interlock chain before committing to it. A re-route that would move material into a guarded zone is rejected at the reasoning stage — it never reaches the write path, and the operator is notified instead. This closes the last gap between "adaptive" and "safe," and it means the recovery envelope can be widened without widening the safety envelope.
safety interlocks · adaptive routing
2026-06-30 · integration
OPC-UA information model for cognitive process automation, v1.0
We published the first version of the information model CognitioFlow uses to read plant state as typed, addressable objects rather than a flat register map. The model names the process objects the reasoning layer actually cares about — work-cells, diverters, process variables, interlocks — so a reasoning decision can reference "diverter D3 is blocked" instead of "register 40117 == 1." The full companion spec is available through sales.
OPC-UA · information model
2026-05-11 · field trial
Modbus TCP brownfield bridge enters field trial
The bridge that folds legacy Modbus instruments into the reasoning loop is now in field trial. It maps holding registers into the same process model the rest of the system uses, so a fifteen-year-old flow meter contributes to the same decision as a modern drive. The point of the trial is the boring part: whether the mapping stays stable across reboots and firmware quirks — which is exactly where brownfield integrations usually fail.
Modbus TCP · brownfield
2026-03-19 · essay
Why exception handling, not speed, sets the recovery time
A faster line that stops for every deviation is still a stopped line. We wrote up why the metric that matters in automation is recovery time — the interval from deviation to resumption — and why it's almost never the headline number on the spec sheet. The recovery path is what cognitive automation shortens; raw throughput is downstream of it.
OEE · recovery time
2026-01-27 · standards
CognitioFlow joins the PROFINET and EtherNet/IP conformance track
We started the conformance process for our PROFINET and EtherNet/IP interfaces. Conformance matters for one reason: a cognitive layer is only as trustworthy as the fieldbus it rides on. If the I/O timing is wrong, the reasoning is moot. We'll share the results — pass or fail — as they come back from the test labs.
PROFINET · EtherNet/IP