The configuration of a reactor programme, in a spreadsheet one person maintains.
The configuration moved into a typed model the client can be given a scoped view of, so the handover at the end of the assignment is an export rather than a migration.
- Ferrand Ingénierie
- 🧩Gabarits de mission
- Programme Estuaire
- 🗺️Configuration
- equipements312
- ecarts_ouverts11
- 📦Restitution client
- Programme Vaugris
EQP-0142 — Pompe de circulation primaire
- repere_client
- EST-PO-142
- statut_configuration*
- Figée
- indice
- C
- exigence_source*
- RCC-M · Partie B, §3.2
- visibilite_client*
- Partagé
- ecarts_ouverts
- 2
Pompe de circulation primaire, indice C figé à la revue de juin. Deux écarts restent ouverts côté fournisseur ; le client les voit en lecture sur sa branche, sans accéder aux autres programmes.
| Name | origine* | impact* | statut* |
|---|---|---|---|
| ECR-118 — Tolérance d'alignement d'arbre | Fournisseur | Majeur | En instruction |
| ECR-127 — Matière de garniture mécanique | Conception | Mineur | En instruction |
| ECR-092 — Épaisseur de calorifuge | Chantier | Mineur | Soldé |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The firm, the programmes and every figure are changed. The handover problem and the model are as they were.
The asset you are paid to produce is the one thing you cannot hand over cleanly.
One model, reused per programme, with a door for the client.
A reactor programme in one spreadsheet
Configuration management for the whole assignment lives in a file. It holds because the person who built it is still on the project.
A template, not a blank sheet
The configuration model is defined once and instantiated per assignment. A new programme starts structured.
The client cannot see it until the end
There is no safe way to give a client a live view of their own programme, so they get a report and wait.
The client sees their own branch, live
Scoped read access to their programme and nothing else. No report to assemble, no other client visible.
Every programme reinvents the structure
A new assignment starts from a blank sheet, or from a copy of the last spreadsheet, which is worse.
Handover is an export
At the end of the assignment the structure leaves with the data in it, in a shape the client's own tools can read.
The model belongs to the firm. The data belongs to the client.
- Ferrand Ingénierie
- 🧩Gabarits de mission
- Programme Estuaire
- 🗺️Configuration
- equipements312
- ecarts_ouverts11
- 📦Restitution client
- Programme Vaugris
EQP-0142 — Pompe de circulation primaire
- repere_client
- EST-PO-142
- statut_configuration*
- Figée
- indice
- C
- exigence_source*
- RCC-M · Partie B, §3.2
- visibilite_client*
- Partagé
- ecarts_ouverts
- 2
Pompe de circulation primaire, indice C figé à la revue de juin. Deux écarts restent ouverts côté fournisseur ; le client les voit en lecture sur sa branche, sans accéder aux autres programmes.
| Name | origine* | impact* | statut* |
|---|---|---|---|
| ECR-118 — Tolérance d'alignement d'arbre | Fournisseur | Majeur | En instruction |
| ECR-127 — Matière de garniture mécanique | Conception | Mineur | En instruction |
| ECR-092 — Épaisseur de calorifuge | Chantier | Mineur | Soldé |
What we modelled
From the standard down to the open deviation
The chain a client asks for at handover. Producing it used to mean reading the spreadsheet aloud.
Programmes on the same model
Three assignments, one structure. The right-hand column is computed, so a handover date is a fact rather than a hope.
| Programme | Équipements | Indice figé | Écarts ouverts |
|---|---|---|---|
| Estuaire | 312 | C | 11 |
| Vaugris | 188 | B | 4 |
| Mérens | 96 | A | 23 |
ƒ Écarts ouverts is computed by Koddex, not typed by anyone.
One equipment item, as the client sees it
Pompe de circulation primaire
EST-PO-142- repere_client
- EST-PO-142
- statut_configuration
- Figée
- exigence_source
- RCC-M · Partie B, §3.2
- ecarts_ouverts
- 2count(deviations.equipment == this AND status != closed)
What the graph computes
The number that decides whether a handover can happen. It used to be produced by reading a spreadsheet line by line.
Turns the end of an assignment into a threshold the client can watch approaching, rather than a surprise at the review.
A template per assignment, a scoped client view, and a handover that is an export.
The end of the assignment stopped being a migration.
| Before | After | |
|---|---|---|
| Where the configuration lives | A spreadsheet, one maintainer | A typed model, per programme |
| Starting a new assignment | Blank sheet, or a copy | An instantiated template |
| What the client sees | A report, at milestones | Their branch, live |
| Open deviations | Counted by reading | A computed column |
| Handover | A migration, at the end | A scoped export, any day |
“We need to get professional about this.”
Three things worth knowing before you defend this internally.
The client has to want the view
A live branch is only an advantage if the client uses it. Some prefer the milestone report, and that is a commercial conversation rather than a technical one.
One template will not fit every programme
Nuclear, oil and gas and equipment work do not carry the same attributes. The template is a starting point per family, not a single universal model.
Scoping is a decision, not a default
Deciding what a client may see of their own programme — and what stays the firm's method — has to be settled before the first share, by people.
Frequently asked questions
Who owns the data, the firm or the client?
The client owns their programme's data; the firm owns the model that structures it. That separation is what makes a handover an export rather than a negotiation, and it has to be agreed before the first assignment, not at the end of one.
Can a client see other clients?
No. Access is scoped to a programme branch by tag, so a client reads their own equipment, requirements and deviations and nothing else — including nothing of the firm's other assignments.
Does this work outside nuclear?
The pattern does — a contractor holding a client's structured data and having to hand it back is the same in oil and gas and in equipment work. The attributes differ, which is why the template is per family rather than universal.