Neutronics, thermohydraulics and mechanics now read the same cardinal values from one model, and a change to any of them names every study it invalidates.

Diamètre actif retenu après l'itération de janvier. Toute révision de cette valeur invalide les études neutroniques et thermohydrauliques qui la référencent, et impose une revue mécanique du support de cuve.
| Name | metier* | etat_vis_a_vis_rev4* | criticite* |
|---|---|---|---|
| NEU-12 — Nappe de puissance à pleine charge | Neutronique | À rejouer | Critique |
| THE-05 — Marge d'ébullition nucléée | Thermohydraulique | À rejouer | Critique |
| MEC-21 — Support de cuve, tenue sismique | Mécanique | À revoir | Majeure |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The company, the reactor and every figure are changed. The three disciplines, the problem and the model are as they were.
Core geometry sits in a neutronics deck, in a thermohydraulic model and on a mechanical drawing. Each is right on the day it is written.
Core diameter is an object with a unit, a revision and an owner — not a cell in three files.
The value moves in one discipline. The other two carry on with the old one until somebody notices in a review, or does not.
Each discipline's study references the item. Where-used answers who depends on this value in one click.
Whatever holds this data has to sit in France or the EU. That requirement arrives before any discussion of features.
A new revision of the value flags every study built on the previous one, before anyone signs anything.


Diamètre actif retenu après l'itération de janvier. Toute révision de cette valeur invalide les études neutroniques et thermohydrauliques qui la référencent, et impose une revue mécanique du support de cuve.
| Name | metier* | etat_vis_a_vis_rev4* | criticite* |
|---|---|---|---|
| NEU-12 — Nappe de puissance à pleine charge | Neutronique | À rejouer | Critique |
| THE-05 — Marge d'ébullition nucléée | Thermohydraulique | À rejouer | Critique |
| MEC-21 — Support de cuve, tenue sismique | Mécanique | À revoir | Majeure |
Seven studies depend on the core diameter. The graph is the answer to a question that used to take a week of emails.
Typed columns on the left, computed on the right. Nobody maintains the dependency count by hand.
| Valeur | Propriétaire | Rév | Études dépendantes |
|---|---|---|---|
| Diamètre actif du cœur | Neutronique | 4 | 7 |
| Puissance thermique nominale | Neutronique | 6 | 11 |
| Débit primaire nominal | Thermohydraulique | 3 | 5 |
| Masse de la cuve | Mécanique | 2 | 4 |
ƒ Études dépendantes is computed by Koddex, not typed by anyone.
How many studies read this value. The number nobody could give before.
This is the cascade, made countable before a review rather than after it.
One value, referenced everywhere, with a revision that names what it invalidates.
| Before | After | |
|---|---|---|
| Where the value lives | The same value in three disciplines | One item, three references |
| Propagating a change | A change nobody downstream hears about | A revision that names what it invalidates |
| Answering “who depends on this?” | Who depends on this? A week of emails | Where-used, one click |
| Establishing consistency | Consistency argued in review | Consistency computed before it |
| Hosting | Hosting an open question | EU hosting, settled on day one |
“What we need is the flexibility of Excel with the consistency of a piece of software.”
It does not run the physics. Neutronics and thermohydraulic codes stay where they are; Koddex holds the values they agree on and the links between the studies.
It only works if each cardinal value has one named owner. Where two disciplines both claimed a value, that had to be settled by people before it could be modelled.
Modelling the first three values took a day. Bringing a whole reactor programme in is a matter of months, not an afternoon.
The customer's own term: a physical value that several disciplines depend on at once — core geometry, nominal thermal power, primary flow. They are few, and they are the ones that hurt when they drift.
No. The codes keep running where they run. What changes is that their inputs come from one referenced item rather than from a copy, and that a new revision of that item flags every study that used the old one.
In the EU, and on the customer's own infrastructure where a programme requires it. For this team the hosting question came before any discussion of features, which is normal in the sector.
The first three cardinal values and their dependent studies were modelled in a day. Usefulness arrives with the first cascading revision, not with the last import.