We build a cyber digital twin of the facility from the first engineering documents, hold it against IEC 62443 and the law of the country where it will run, and let your CFO, COO, CTO and CISO ask what if while changing the design is still cheap. Our engineers run it with you through to handover.
Choose your project
The usual path
Designers work in drawings
P&IDs, network drawings and specifications are written by different teams, and nobody holds them as one system.
Suppliers read the spec once
Integrators and vendors meet the security requirements late, in different words, and prove them at the end.
Regulators arrive at handover
What the country requires is checked against the finished plant, when changing it is slowest and most expensive.
This is how most projects run, and it is why the first months of operation carry a list of things to fix. A model that exists from the first document changes the order of work.
Four seats, one model
The same model serves every executive. What changes is the question each one brings, and what each one takes out of the room.
CFO asks
What does each design option cost now, and what does it avoid later?
What the model shows
Design options compared on the same footing: what each requires, what it adds to the programme and what it would add if the same change came after construction began. Security is in the budget from the first design, not found at the end.
What you take away
A design choice recorded with its reasons, and a budget that already carries security.
What if, in the room
Each question is answered from the facility's own model, and the answer is kept with the decision.
How the model works
The twin reads the engineering documents as they are issued and turns each into a connected record of the facility, rather than a file in a folder. Requirements are attached to the parts they apply to.
Ingested
The cyber digital twin
Assets, zones, conduits, requirements and the paths between them, in one place.
Built on IEC 62443, with the other standards and national rules the project must meet.
Produced
Aligned to the requirements
IEC 62443 sets the structure: system requirements (62443-3-3), requirements on integrators and suppliers (62443-2-4) and on components (62443-4-2). Each requirement is tied to the zone, conduit or asset it governs, so a supplier sees exactly what applies to them.
The country's law.
Eigenia researches jurisdictions one by one, and every fact is sourced. The facility's requirements are read from that record, not from a generic checklist.
Where a requirement cannot be met.
The deviation is recorded for that facility with its reason and the control that stands in for it, so the question is answered once, in writing.
The engineers
Our engineers work as lead engineer and programme manager for the owner. They sit between designers, integrators and contractors, run the what-if sessions with your executives, and answer for the security of the whole system. Delivered by Eigenia and its partner network.
Lead IEC 62443 engineer
Writes the security requirements into the specification and owns the deviation register. Answers to the CISO and to the regulator.
Control engineer
Reviews the control system design and the supplier submittals against the model. Speaks for the CTO's question: does it hold together.
Industrial engineer
Knows how the process will run and fail. Tests the design against operating needs. Speaks for the COO.
Programme manager
Keeps designers, integrators and contractors aligned to the requirements, and protects the budget the CFO approved.
How an engagement runs
Requirements
set against the model and the country's law
Design reviews
and what-if sessions with the four executives
Supplier submittals
checked against their requirements
Factory and site tests
of the security functions
Handover
with the as-built model
At handover
Security functions have been tested at the factory and on site before you take the plant over. The twin goes with it, current to what was built, so operations start from a true record rather than a drawing set.
Why now
Eigenia has researched 226 of 249 jurisdictions, every fact sourced, with the dates that apply. A decision made on a model can be re-run when a rule or an assumption changes.
Where the equipment is a product in scope of the EU Cyber Resilience Act, its supplier is subject to the reporting duties from 11 September 2026 and to the regulation in full from 11 December 2027.
Every engagement starts from the facility's country, sector, type, supply chain and external pressures. The researched record for the country, and the origins of its parts and software, set what the work has to cover.
Send the country, the sector and the facility type. The enquiry form carries the service with it.
Eigenia does not set cookies. The only thing stored in your browser is one preference, saved in local storage, noting that you have seen this notice.