DjedCore

Architecture

Shared platform core

Keep reactor-specific rules out of the shared core. Every project uses one common data model, with separate, versioned project configurations.

  • Identity

    What each item, lot and serial number is.

  • Provenance

    Who made it, handled it and shipped it.

  • Evidence

    Certificates, inspections, tests, nonconformances and revisions, each with a scope.

  • Workforce

    People, their qualifications and validity dates.

  • Work packages

    What is installed, where, by when and under which conditions.

  • Dependencies

    Finish-to-start, start-to-start and finish-to-finish links, with lags.

  • Events

    The append-only, hash-chained record of every change.

  • Forecasting

    Ready-by-date probabilities with correlated supplier and activity factors.

Client layer · under NDA

Configuration templates

What each project configuration contains and the rules for building it are shared with clients under NDA.

How clients get access

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.

Email us contact@djedcore.com