Knowledge channel · OT-grade notes
Architecture decisions, failure modes we have seen in production, and the boring glue work that makes OEE dashboards, UNS rollouts, and MES actually survive the next turnover cycle.
We write for the person in the stand-up who has to explain why the historian is full, why Sparkplug matters, and why the ERP team should not poll the PLC. Start with the flagship piece—or skim the grid.
Topic law, edge buffering, and how to keep your historian honest when the broker blinks. Includes naming patterns we use when the second plant joins the mesh—without a six-week topic rename project.
Read the full guide →Named volumes, health checks that catch a half-dead gateway, and TLS at the reverse proxy—without treating containers like a science fair.
Open article →Reason-code depth, one clock for the line, and ERP handshake boundaries so finance stops fighting production over the same six minutes of downtime.
Open article →Three layers: I/O, equipment UDT, value stream. One gateway, many consumers—without dumping fifty thousand tags into SAP.
Open article →DMZ patterns, identity that fits OT, and what we still insist happens on-site when someone needs to touch the drive.
Open article →Tell us what you are trying to instrument—Ignition, UNS, MES, or the politics between OT and IT. We take requests from customers and partner integrators.