ZEKLAREnergy
EN / IT
Software· nuclear

CADENCE

The nuclear-tailored common data environment for the construction site.

CADENCE is the common data environment built for the nuclear construction site: it synchronizes resources, data and activities across partners and disciplines. Designers, EPCs and suppliers work on the same up-to-date data, so site decisions start from reality and not from disconnected copies.

1 DATA ENVIRONMENT FOR ALL PARTNERS−35% REWORK FROM SUPERSEDED REVISIONS100% HANDOVERS TRACKEDADVISORY MODE · READ-ONLY1 DATA ENVIRONMENT FOR ALL PARTNERS−35% REWORK FROM SUPERSEDED REVISIONS100% HANDOVERS TRACKEDADVISORY MODE · READ-ONLY
01In figuresFIELD DATA
1
data environment for all partners
−35%
rework from superseded revisions
100%
handovers tracked
02The problem

On site every partner has its own truth.

A nuclear EPC project involves dozens of companies, each with its own tools and its own copies of the documents. When the design changes, information arrives late and misaligned: work proceeds on a superseded revision and the nonconformity is discovered after the fact.

03What it does04
01

Shared data in real time

All partners read the same approved revision: when it changes, it changes for everyone at the same moment.

02

Cross-discipline coordination

Civil, mechanical, electrical and I&C share a single reference model, with clashes visible before installation.

03

Synchronized activities

Sequences, resources and constraints are tied to design data: an upstream delay propagates visibly downstream.

04

Deliverable register

Every handover between partners is tracked with status, approval and owner, without email exchanges.

04How it works04 STEPS
01

Federate

Connect data from designers, EPCs and suppliers into one common environment.

02

Coordinate

Align disciplines and activities on a single reference model.

03

Release

Publish approved revisions to all partners at the same time.

04

Record

Capture the as-built and return real site data to the archive.

05Architecture

CADENCE is a federated common data environment compliant with ISO 19650: designer, EPC and supplier data are connected into a shared reference model, with controlled publishing of approved revisions and as-built capture into VAULT.

01Data federationConnects the systems of dozens of partners without replacing them, exposing a single shared approved revision; models enter via open BIM formats (IFC, BCF).
02Coordination modelCivil, mechanical, electrical and I&C share a reference model with clash detection before installation.
03Release engineApproved revisions are published to all partners at once, with ISO 19650 states (WIP, shared, published, archived) and a deliverable register.
04As-built captureReal site data is recorded and returned to VAULT as certified configuration; supplied components are traced into LEDGER.
06Specifications
CDE standardISO 19650
BIM formatsIFC, BCF
Discipline coordinationCivile, meccanico, elettrico, I&C
Clash detectionPre-posa, sul modello federato
Deliverable registerStato, approvazione, responsabile
Concurrent partnersDecine di aziende federate
Access controlRBAC per partner e disciplina
Suite integrationsFORGE, VAULT, LEDGER
07Deployment

Cloud

Managed CDE on sovereign cloud, ideal for distributed multi-partner EPC projects: each company accesses its own perimeter with isolation and defined data residency.

On-premise

Deployment in the general contractor's data center with partner federation via secure connectors; the reference model stays under the customer's control.

Air-gapped

Isolated CDE for construction on classified sites: revision exchange via verified media between partner perimeters, without direct external connectivity.

08Security & compliance

Revision control

Only revisions approved through the ISO 19650 flow are published to partners: the risk of building on a superseded version is eliminated.

Partner isolation

RBAC by partner and discipline ensures each company sees only the data within its remit, with an immutable audit trail of every handover and access.

Handover traceability

Every handover between partners is recorded with status, approval and owner, replacing email exchange with verifiable, ISO 27001-aligned evidence.

As-built integrity

Site data returned to VAULT is signed and bound to the design revision, so the certified configuration verifiably reflects the real plant.

09Integrations
FORGE: design models and revisionsVAULT: certified as-built archiveLEDGER: qualification and traceability of supplied componentsBIM exchange formats (IFC, BCF)CDE standards (ISO 19650)
10FAQ

Must every partner adopt the same tools?

No. CADENCE federates existing systems via open BIM formats (IFC, BCF): partners keep their own tools and share a single approved revision.

How is building on superseded revisions avoided?

Publishing follows ISO 19650 states: when a revision is approved, it replaces the previous one for all partners at once, with a tracked notification.

Are supplied components linked to their qualification?

Yes. Every installed component is traced into LEDGER, which holds its qualification, certificates and chain of custody, keeping site and compliance consistent.

Where does as-built data go at project close?

The as-built is returned to VAULT as the plant's certified configuration, available for operations with PULSE across the full service life.

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