ZEKLAREnergy
EN / IT
BACK TO ZEKLAR ENERGY/energy/reactor-os
Operating System· nuclear

REACTOR OS

Operations intelligence for utilities and operators.

REACTOR OS is operations intelligence for utilities and operators: the plant operating system, where data, safety and real-time decisions converge. It unifies field signals, procedures and safety status into a single view for the control room. Built to run continuously on nuclear infrastructure, with reliability as a design constraint.

24/7 CONTINUOUS OPERATIONReal-time CONTROL-ROOM DECISIONS1 vista PLANT STATEADVISORY MODE · READ-ONLY24/7 CONTINUOUS OPERATIONReal-time CONTROL-ROOM DECISIONS1 vista PLANT STATEADVISORY MODE · READ-ONLY
01In figuresFIELD DATA
24/7
Continuous operation
Real-time
Control-room decisions
1 vista
Plant state
02The problem

Plant data without a single view

A plant generates data from SCADA, safety systems, maintenance and diagnostics, each with its own console. The operator has to assemble the picture under pressure, jumping between screens that do not talk to each other. You need an operating system that unifies real state into an informed decision.

03What it does04
01

Unified view

A single control view brings process, safety and maintenance signals into one coherent model.

02

Safety status

Safety margins and barriers monitored continuously, with alarms prioritized by severity.

03

Decision support

Operating procedures contextualized to plant state, to guide the response in real time.

04

Operational continuity

Redundant architecture and failover for uninterrupted operation through maintenance and faults.

04How it works04 STEPS
01

Integrate

REACTOR OS connects to SCADA, safety systems and FLUX nodes to gather plant state.

02

Correlate

Signals are correlated into a single model reflecting process, safety and assets.

03

Decide

Prioritized alarms and contextual procedures support the operator's response.

04

Record

Actions and events are archived in VAULT as operational history and an audit basis.

05Architecture

REACTOR OS is the plant operating system for utilities and operators: it unifies field signals, procedures and safety status into a single control-room view. The architecture is designed with reliability as a constraint: integration with SCADA and safety systems, correlation of signals into one model, decision support and a redundant architecture for continuous 24/7 operation.

01Signal integrationConnects to SCADA, safety systems, maintenance and in-situ FLUX nodes to gather plant state from sources that do not talk to each other.
02Unified plant modelSignals are correlated into a coherent model reflecting process, safety and assets, the basis for the single control-room view.
03Safety monitoringSafety margins and barriers monitored continuously, with alarms prioritized by severity to focus attention where it matters.
04Decision supportOperating procedures contextualized to plant state guide the operator's response in real time, with CORTEX diagnostics in support.
05Continuity and archiveRedundant architecture with failover for uninterrupted operation through maintenance and faults; actions and events archived in VAULT as history and an audit basis.
06Specifications
FormOS d'impianto (SW + HW + servizi)
DeploymentOn-prem sala controllo
IntegrationsSCADA, sistemi di sicurezza, FLUX
AvailabilityRidondanza + failover, 24/7
AlarmsPrioritizzati per gravità
ArchiveVAULT (storico + audit)
DiagnosticsCORTEX
StandardsIEC 61513, IEC 62645
07Deployment

On-prem in the control room

Installed on plant systems and connected to SCADA and safety systems; the single view runs in the control room on a redundant architecture.

Redundant high availability

Redundant nodes with automatic failover to guarantee uninterrupted operation through planned maintenance and hardware faults.

Air-gapped on safety network

Operation on a plant network isolated from corporate networks per IEC 62645, with updates delivered only through signed, verified media.

08Security & compliance

Verified boot and TPM

Nodes boot with secure boot and TPM 2.0; no unsigned software enters a system that governs the plant's safety status.

Network segregation

Separation between the safety network and corporate networks per IEC 62645/IEC 61513, with encrypted storage for the operational history.

RBAC and control-room audit

Commands and authorizations by role via AEGIS; every control-room action and event is tracked in VAULT as an immutable audit basis.

Certifications

ISO 27001-aligned management and design aligned to nuclear I&C standards (IEC 61513) and nuclear cybersecurity (IEC 62645).

09Integrations
PULSE as the fleet operations layerFLUX for in-situ edge dataVAULT for operational historyCORTEX for diagnostics and predictionExisting SCADA and safety systems
10FAQ

Does REACTOR OS replace SCADA and safety systems?

No. It connects to existing systems and unifies them into a coherent view as an operational layer; it does not replace qualified safety functions.

How does it guarantee continuous operation?

With a redundant architecture and automatic failover, so operation stays uninterrupted through planned maintenance and hardware faults.

How does it relate to PULSE and FLUX?

FLUX supplies in-situ edge data, PULSE is the fleet operations layer; REACTOR OS is the operating system of the individual plant in the control room.

How does it support the operator in an event?

With alarms prioritized by severity and procedures contextualized to the real state, guiding the response in real time instead of jumping between screens.

Are events kept traceable for audit?

Yes: actions and events are archived in VAULT as operational history and an immutable basis for reviews and regulatory inspections.

11The markGRID 64 · STROKE 5

The mark encodes the mechanism, not the sector: la cupola di contenimento, il nucleo, le barre di controllo.

44302216
12Other products · ZEKLAR Energy

ZEKLAR software technology 4.0/5.0

Let's talk
ZEKLAR · SOFTWARE THAT MAKES THE DIFFERENCE.
ZEKLAR · VAT L81419031T · info@zeklar.com© 2026