Security and data
Our plant software advises. It never writes to your control or safety systems.
What we build for a plant reads its data and proposes. The plant’s own systems and people act. We hold no certification credential.
The boundary
Four rules for anything we connect to a plant
No write path to control or safety systems
What we build does not write to a PLC, a DCS or a safety instrumented system. The functional safety of a plant is governed by IEC 61511 and stays with the plant’s own systems and engineers. Optimisation sits above them, as advice.
Read-only connection to the plant
Where our software reads plant data, it does so read-only, through a site gateway that follows ISA/IEC 62443 zones and conduits.
A person decides
Recommendations reach operators as proposals with their evidence, and a person can overrule every one. A closed-loop feature would need its own safety case and the plant owner’s approval process, and none exists.
A proof is not a safety case
Where we prove a property of an algorithm, the proof covers that algorithm and the level it states. It does not replace a safety case or OT security, and we do not present it as one.
Certifications
What we hold, and what we do not
We hold no audit or certification credential. That includes ISO 27001 and IEC 62443, and any certification scheme for hydrogen or fuels. Where a standard shapes our design, as IEC 62443 zoning shapes how our software connects to a plant, we say it is a design rule and not a certification.
This website
What flexiana.com collects
The contact, newsletter and book-order forms store what you type, with your IP address and browser details, so we can answer you and stop abuse. The privacy notice says what else the site collects and lists every field.
Before you share data
Ask us what your security team will ask
Where your data would be held, who would operate the service, and how we would connect to your plant. Ask before you share anything, and we will answer in writing.