Two ways of building, one pile of documents, and a supplier at the other end of an email.
Suppliers now write into the same structure the customer reads, seeing only their own branch, with aggregation happening on its own instead of on somebody's Tuesday.
- Vireo Industries
- Programme Cadence
- 🧩Modèles
- 🏭Nomenclature production
- pieces_usinees42
- non_conformites7
- Fournisseurs
- 📐Spécifications client
PRT-118 — Carter de réducteur
- reference_client
- CAD-4471-B
- mode*
- Build to print
- matiere
- EN-AW 7075 T651
- fournisseur*
- Atelier Sévigné (partagé)
- statut_ppap*
- Soumis
- non_conformites_12m
- 3
Carter usiné sur plan client, révision B. Le fournisseur renseigne ses relevés dimensionnels et ses non-conformités directement sur cette branche ; les coûts et les sources alternatives ne lui sont pas visibles.
| Name | origine* | gravite* | statut* |
|---|---|---|---|
| NC-2026-041 — Planéité hors tolérance | Fournisseur | Majeure | Clôturée |
| NC-2026-052 — Rugosité alésage | Fournisseur | Mineure | Clôturée |
| NC-2026-067 — Dureté après traitement | Interne | Critique | En cours |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The company, the parts and every figure are changed. The two build modes, the supplier problem and the model are as they were.
Everything the company knows is in a file, and everyone outside it gets a copy.
One tree, and a door cut into it for each supplier.
Excel, Word, PDF — including for non-conformities
Documents, standards requirements and non-conformity tracking all live in files. Counting NCs for a period means opening them.
Both modes on one structure
A part carries its drawing, its customer requirement, or both. The mode becomes an attribute, not a second filing system.
Build to spec and build to print at once
One line works from the customer's drawing, the next from the customer's requirement. Different documents, same part numbers.
Access by tag, not by export
A supplier sees the branch they work on and its acceptance criteria. Cost, alternates and other customers stay invisible.
Suppliers reachable only by email
Every exchange is a PDF out and a re-entry back in. Nobody can see a supplier's current state without asking for it.
Aggregation stops being a task
What the supplier writes is already in the graph, so non-conformities per period and per supplier are a query, not an afternoon.
The supplier is not a recipient. They are a writer with a narrow key.
- Vireo Industries
- Programme Cadence
- 🧩Modèles
- 🏭Nomenclature production
- pieces_usinees42
- non_conformites7
- Fournisseurs
- 📐Spécifications client
PRT-118 — Carter de réducteur
- reference_client
- CAD-4471-B
- mode*
- Build to print
- matiere
- EN-AW 7075 T651
- fournisseur*
- Atelier Sévigné (partagé)
- statut_ppap*
- Soumis
- non_conformites_12m
- 3
Carter usiné sur plan client, révision B. Le fournisseur renseigne ses relevés dimensionnels et ses non-conformités directement sur cette branche ; les coûts et les sources alternatives ne lui sont pas visibles.
| Name | origine* | gravite* | statut* |
|---|---|---|---|
| NC-2026-041 — Planéité hors tolérance | Fournisseur | Majeure | Clôturée |
| NC-2026-052 — Rugosité alésage | Fournisseur | Mineure | Clôturée |
| NC-2026-067 — Dureté après traitement | Interne | Critique | En cours |
What we modelled
From the customer spec down to the supplier's record
The supplier writes at the bottom of this chain. Everything above aggregates without anyone re-typing it.
Non-conformities, by supplier and period
The question the quality team could not answer without opening files. The right-hand column is computed.
| Fournisseur | Pièces | Mode | NC sur 12 mois |
|---|---|---|---|
| Atelier Sévigné | 18 | Build to print | 3 |
| Mécanique Vantour | 11 | Build to spec | 1 |
| Traitements Lorin | 6 | Build to print | 5 |
| Fonderie Ambel | 7 | Build to spec | 0 |
ƒ NC sur 12 mois is computed by Koddex, not typed by anyone.
One part, as the supplier sees it
Carter de réducteur
PRT-118- reference_client
- CAD-4471-B
- matiere
- EN-AW 7075 T651
- statut_ppap
- Soumis
- non_conformites_12m
- 3count(nc.part == this AND nc.date > now-12m)
What the graph computes
The figure the quality team had no autonomous way to produce, now readable per part and per supplier.
A customer spec revision names its parts, so the workload of a change is estimated before it is accepted.
A door into the graph for each supplier, and aggregation that happens on its own.
The ecosystem stopped being a mailing list.
| Before | After | |
|---|---|---|
| Reaching a supplier | A PDF out, a re-entry back | They write in the branch |
| What they can see | Whatever the export contained | Their branch, by tag |
| Two build modes | Two filing systems | One attribute on the part |
| Non-conformities per period | Open the files and count | A computed column |
| Cost of a spec change | Estimated after accepting it | Named before |
Three things worth knowing before you defend this internally.
Suppliers have to show up
A scoped door only helps if the supplier walks through it. Teams used to Excel need a champion on both sides, which is the slow part of any rollout.
It is not a CAD system
Drawings stay where they are made. Koddex holds the part, its requirement, its records and the links — not the geometry.
Historical non-conformities do not migrate themselves
The computed counts start from what is in the graph. Back-loading years of spreadsheet history is a decision with a cost attached.
Frequently asked questions
What does a supplier actually see?
The branch they work on: the part, the requirement it must satisfy, the acceptance criteria and their own records. Cost, alternative sources, other customers and the rest of the programme are filtered out by tag, not by a manual export.
How do build to spec and build to print coexist?
As an attribute on the part rather than as two structures. A build-to-print part points at a customer drawing; a build-to-spec part points at a customer requirement. Both sit in the same tree and roll up the same way.
Can our customers' systems read this?
Yes — the API mirrors the model, so a customer or partner tool exchanges structured data rather than documents. That is what removes the re-entry at both ends.