The device is described once. Each site attaches its own validation evidence to it, so a divergence between sites becomes visible instead of becoming a finding.

Trois sites ont validé contre la révision 5 de la spécification. Le quatrième a validé contre la révision 4, avant la modification du protocole d'étalonnage. L'écart est visible ici, pas en audit.
| Name | revision_validee* | essais* | statut* |
|---|---|---|---|
| Site A — Ligne pilote | Révision 5 | Complets | Validé |
| Site C — Production série | Révision 5 | Complets | Validé |
| Site D — Sous-traitance | Révision 4 | Partiels | À rejouer |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The organisation, the device, the sites and every figure are changed. The multi-site problem and the model are as they were.
Each site keeps its own file. Nobody holds a view across the four without asking four people.
Specification, configuration and intended use live on the device item, not in each site's copy of them.
Two sites validating against different revisions of the same specification is normal until an auditor notices.
Validation records attach to the device with the site as an attribute, so local rigour is preserved and made comparable.
Trials, certifications and post-market evidence sit in separate documents per site rather than on the device.
Which sites validated against which revision is a value, visible before an audit rather than during one.


Trois sites ont validé contre la révision 5 de la spécification. Le quatrième a validé contre la révision 4, avant la modification du protocole d'étalonnage. L'écart est visible ici, pas en audit.
| Name | revision_validee* | essais* | statut* |
|---|---|---|---|
| Site A — Ligne pilote | Révision 5 | Complets | Validé |
| Site C — Production série | Révision 5 | Complets | Validé |
| Site D — Sous-traitance | Révision 4 | Partiels | À rejouer |
The view nobody had: which site validated against which revision, on one screen.
Four sites against one specification revision. The right-hand column is computed, so nobody has to compare four files.
| Site | Révision validée | Essais | Écart |
|---|---|---|---|
| Site A — Ligne pilote | 5 | Complets | Aucun |
| Site B — Assemblage | 5 | Complets | Aucun |
| Site C — Production série | 5 | Complets | Aucun |
| Site D — Sous-traitance | 4 | Partiels | 1 révision |
ƒ Écart is computed by Koddex, not typed by anyone.
The divergence that used to surface during an audit, available before one.
Makes approving a specification revision a decision with a named cost across the network.
One device description, per-site evidence, and divergence as a value rather than a finding.
| Before | After | |
|---|---|---|
| The device description | One copy per site | One item, four branches |
| Divergence between sites | Found by an auditor | A computed column |
| Local rigour | Preserved, and invisible | Preserved, and comparable |
| Approving a spec revision | A document change | A named list of sites to re-validate |
| A view across the network | Ask four people | One screen |
Making divergence visible does not resolve it. The first weeks surface disagreements that four separate files had been quietly absorbing.
Trials and tests happen where they happen. Koddex holds which revision each site validated against and what evidence it produced.
Past validations are referenced rather than re-keyed. The computed divergence is meaningful from the revision you start at, not retroactively.
No — that was the condition. Each site still produces its own validation evidence, with its own people and its own protocols. What changes is that all of it hangs off one device description, so the four can be compared without four requests.
The sites still validated against the previous revision are named immediately. Approving a revision therefore carries a visible cost across the network, which is precisely the information that used to arrive late.
It shows up most sharply there, because an auditor crossing sites is exactly who finds the divergence. But any organisation validating one device in more than one place has the same problem the rest of the year.