Cloud history drifts when values are dated by when they were sent. How CATIM Nimbus keeps each value's own time from the controller to an industrial cloud platform.
The controller's own health belongs on the Unified Namespace beside its data: the same values through MQTT and i3X, every service's status in one subscription, and the unit's own facts through the same API.
An integrator's customer should meet the integrator's brand on every screen, and a rebrand should never break the software that reads the data. How CATIM Nimbus carries someone else's brand without a custom build.
The EU Cyber Resilience Act asks for outcomes, not mechanisms. What those outcomes mean for the controller inside a machine, the questions a machine builder should ask of it, and the principles behind CATIM Nimbus.
Shared logins and per-device user lists turn every hire and leaver into a visit to every controller. How we design identity by role - units that know roles, not people - and how an integrator hands a site to its owner cleanly.
Many plants keep their control network off the internet. The questions IT asks of a new controller, and how CATIM Nimbus answers them: nothing on the internet calls in, trust made on site, and the one thing the site provides - the right time.
Staff who click past browser warnings every day will click past the one that matters. How an edge controller earns the browser's trust: its own key, a certificate signed by the authority you choose, and one root installed once.
