DjedCore
EN
Get started

Software

Evidence traceability software. Installed on your own systems.

DjedCore software traces every item on a nuclear project through eight layers of traceability and checks nine readiness gates for each work package, so you see what is ready, what is blocked and why. It is modular, licensed per organisation and runs on your own devices.

In development. Pilot licences are available to early partners. Screens and examples use synthetic data.

01

Licensed software, not a hosted service

  • Installed on your devices

    The application and its data stay inside your organisation. Nothing is sent to DjedCore.

  • Modular licence

    A licence key activates the modules, users and term you agree. Add modules later without reinstalling.

  • Technical support from us

    Installation help, updates and resolution of software issues.

  • Your QA system stays in charge

    DjedCore does not regulate, approve or hold your work or your documents. The software supports decisions; your QA system remains the record of authority.

02 / L1 → L8

Eight layers of traceability

Each layer is the source of requirements for the one below it. When a layer changes, the software shows every item, record and work package affected further down.

  1. L8Evidence records
  2. L7Inspection and test plans
  3. L6Specifications and issued-for-construction drawings
  4. L5Codes and standards
  5. L4Design basis
  6. L3EPC contract
  7. L2Licence and licence conditions
  8. L1Law and regulation

03 / Three frameworks, three questions

Six layers, eight layers, nine gates. Each answers a different question.

  1. E1 → E6

    Six evidence layers

    Can this item be accepted for this use?

    DjedCore's evidence model for a single component: identity, provenance, requirements, quality evidence, physical status and acceptance.

  2. L1 → L8

    Eight layers of traceability

    Where does each requirement come from?

    The regulatory hierarchy, from law and licence down to the evidence record.

  3. MAT → REG

    Nine readiness gates

    Can this work package proceed?

    Material, engineering, quality, workforce, equipment, work area, prerequisite work, permit and regulatory conditions.

The six layers are a DjedCore framework, not an industry standard. Applicable acceptance criteria and authorised review remain decisive.

04

Nine readiness gates

A work package is Ready when every mandatory gate is satisfied or formally waived. Otherwise it is Blocked, with one reason for each open gate. Blocked is derived from the gates, so it can never disagree with them.

  1. MAT

    Material

    Every required item is Released and allocated to this package.

  2. ENG

    Engineering

    Every referenced document is at an issued-for-construction revision, with no open change notice.

  3. QA

    Quality

    All preceding hold points are cleared and no open nonconformance affects the tags in scope.

  4. WRK

    Workforce

    Enough people with valid qualifications are assigned for the planned dates.

  5. EQP

    Equipment and tools

    Cranes, tools and calibrated test equipment are booked and in calibration.

  6. ARE

    Work area

    The area is released for this type of work and access is clear.

  7. PRE

    Prerequisite work

    Every predecessor work package meets its dependency rule.

  8. PER

    Permit

    Work, hot-work, lifting or radiological permits are approved.

  9. REG

    Regulatory

    A regulator or owner hold or witness point is released, or a licence condition is met.

05

Try it: one work package, nine gates

Pick a work package to see why it is ready or blocked.

Synthetic example data

Blocked · 2 open gates

  • MATMaterialOpenP-201 received but not released: material certificate missing
  • ENGEngineeringSatisfied
  • QAQualityOpenHold point HP-07 not cleared
  • WRKWorkforceSatisfied
  • EQPEquipment and toolsSatisfied
  • AREWork areaSatisfied
  • PREPrerequisite workSatisfied
  • PERPermitSatisfied
  • REGRegulatorySatisfied

06

Modules and availability

License the modules your project needs. Each module carries its own status, and new modules are added to an existing licence without reinstalling.

  1. M1

    Traceability layers

    Links every item to the eight layers of traceability, from law and licence conditions to the evidence record.

    In development

  2. M2

    Readiness gates

    Checks nine readiness gates for every work package and gives one reason for each open gate.

    In development

  3. M3

    Evidence data model

    Keeps identity, provenance, requirements, quality evidence, physical status and acceptance as six separate evidence layers.

    In development

  4. M4

    Change impact

    Designed to update every readiness decision that depends on a changed document, nonconformance or qualification, and to keep the history of the change.

    In development

  5. M5

    Tamper-evident record

    Every change is kept as a hash-chained event. If anyone edits history, it shows.

    In development

  6. M6

    Readiness forecasting

    Readiness dates given as ranges with a confidence level, not as single promises.

    Planned

  7. M7

    Evidence package export

    Scoped, verifiable packages for owners, auditors and regulators.

    In design

  8. M8

    Reactor-family configurations

    Versioned rule sets for large reactors and SMRs on top of the shared core.

    In development

07

Built for software qualification

Nuclear organisations often have to qualify the software they use. Each DjedCore release is planned to ship with:

  • A unique version identifier and release notes
  • A verification and validation summary
  • A user manual and an installation guide
  • A defined support and maintenance policy
  • Known limitations, stated plainly

08

Deployment

  • Desktop installation on devices your organisation manages
  • One organisation per licence; no shared multi-tenant service
  • Imports from your existing QA, document-control and scheduling exports
  • Reactor-family rules in versioned configurations

Roadmap

  1. V1

    Construction to operating licence: one project, from EPC contract signature to operational readiness.

  2. V2

    Operation on the same records: fuel load, start-up, maintenance and outages.

  3. Later

    Several projects and fleets, and research on supply-chain resilience.

09 / Licence-holder layer

How does it work in practice?

How the layers are linked, checked and kept consistent is part of the licensed software and is explained to licence holders. Tell us about your project and we will walk you through it.

Ask us how it works

10

Go deeper

Have a licence file, a supplier or a work package you are worried about?

Send a short description. We reply within two working days and sign your NDA before any document changes hands.

Get started Email us contact@djedcore.com