The drawing is approved, the order is released, and nothing connects the two.
Design revisions, manufacturing orders and the team's day-to-day work now hang off the same items, so a change in development reaches the shop floor without a person carrying it.
- Halvane Medical
- Ligne Ostéo
- 🧩Modèles
- 🧱Nomenclature
- 🏭Ordres de fabrication
- ordres_ouverts23
- 📐Plans & modèles
OF-2026-0418 — Vis corticale Ø3,5
- reference_piece
- OST-VC-035
- revision_lancee*
- Plan OST-VC-035 · indice D
- revision_courante*
- Indice E
- quantite
- 1 200
- statut*
- En cours
- ecart_de_revision
- 1 indice
Ordre lancé sur l'indice D. L'indice E a été approuvé depuis, avec une modification de congé de tête. L'écart est signalé avant que le lot ne parte : soit l'ordre est relancé, soit la dérogation est tracée.
| Name | statut_ordre* | ecart* | action* |
|---|---|---|---|
| OF-2026-0418 — Vis corticale Ø3,5 | En cours | 1 indice | À arbitrer |
| OF-2026-0402 — Vis corticale Ø3,5 | Clôturé | 1 indice | Tracé |
| OF-2026-0431 — Vis corticale Ø4,0 | Planifié | Aucun | Aucune |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The company, the device and every figure are changed. The three systems, the silo and the model are as they were.
Three tools, each right about its own part, none of them talking.
The part is the anchor. Orders, revisions and tasks hang off it.
An ERP that does not know the revision
Manufacturing orders reference a part number. Which drawing revision that number means today is somewhere else.
One item, three views
Design, production and planning read the same part from their own angle instead of holding three records of it.
An EPDM nobody outside design opens
Drawing and model revisions are managed properly, and production never sees them without being told.
The order carries its revision
A manufacturing order references the exact revision it was released against, so what was built is knowable afterwards.
A task tracker holding the real work
What the team is actually doing lives in a board that knows nothing about parts, revisions or orders — and is paid for monthly.
A revision warns the floor
Approving a new drawing revision flags the open orders built on the previous one, before the batch runs.
Nothing replaced the ERP. Something finally sat under it.
- Halvane Medical
- Ligne Ostéo
- 🧩Modèles
- 🧱Nomenclature
- 🏭Ordres de fabrication
- ordres_ouverts23
- 📐Plans & modèles
OF-2026-0418 — Vis corticale Ø3,5
- reference_piece
- OST-VC-035
- revision_lancee*
- Plan OST-VC-035 · indice D
- revision_courante*
- Indice E
- quantite
- 1 200
- statut*
- En cours
- ecart_de_revision
- 1 indice
Ordre lancé sur l'indice D. L'indice E a été approuvé depuis, avec une modification de congé de tête. L'écart est signalé avant que le lot ne parte : soit l'ordre est relancé, soit la dérogation est tracée.
| Name | statut_ordre* | ecart* | action* |
|---|---|---|---|
| OF-2026-0418 — Vis corticale Ø3,5 | En cours | 1 indice | À arbitrer |
| OF-2026-0402 — Vis corticale Ø3,5 | Clôturé | 1 indice | Tracé |
| OF-2026-0431 — Vis corticale Ø4,0 | Planifié | Aucun | Aucune |
What we modelled
From a new revision to the orders it touches
Approving index E asks one question the three systems could not: which open orders were released on index D.
Open orders against the current index
The list production never had. The right-hand column is computed from the link between order and revision.
| Ordre | Indice lancé | Indice courant | Écart |
|---|---|---|---|
| OF-2026-0418 | D | E | 1 indice |
| OF-2026-0431 | E | E | Aucun |
| OF-2026-0402 | D | E | 1 indice |
| OF-2026-0444 | C | E | 2 indices |
ƒ Écart is computed by Koddex, not typed by anyone.
One manufacturing order, in full
Vis corticale Ø3,5
OF-2026-0418- reference_piece
- OST-VC-035
- revision_lancee
- Indice D
- quantite
- 1 200
- ecart_de_revision
- 1 indicecurrent_index − released_index
What the graph computes
The question that decides whether a batch runs, is re-released, or runs under a traced deviation.
Turns approving a revision into a decision with a visible consequence, rather than a filing action.
An order that carries its revision, and a new index that names the orders it touches.
The bridge between design and the floor stopped being a person.
| Before | After | |
|---|---|---|
| What an order references | A part number | A part at a revision |
| Approving a revision | A filing action | A list of affected orders |
| What the floor builds to | Whatever was printed | The referenced revision |
| Deviations | Agreed verbally, traced later | Attached to the order |
| The three systems | Three records of the same part | Three views of one item |
Three things worth knowing before you defend this internally.
It does not replace the ERP
Manufacturing orders keep being executed where they are executed. What changes is that the order now references a revision, which is the link that was missing.
Production has to accept a new signal
A revision gap flag is only useful if somebody is accountable for arbitrating it. Adding the alert without naming that person just adds a red dot.
The task tracker does not disappear on day one
Day-to-day work moves last, and only once the parts and orders are trustworthy. Teams that try to move it first end up with two boards.
Frequently asked questions
Do we have to drop our ERP or EPDM?
No. Both keep doing what they do well — orders and drawing revisions. What was missing was a layer underneath where a part, its revision and its order are the same object seen from three angles.
What does the revision gap actually trigger?
A decision, not an automation. The order is either re-released against the current index or run under a deviation that is recorded against it. The point is that the choice is made knowingly, before the batch.
Where do we start?
With one part family and its open orders. The continuity is visible the first time a new drawing index names the orders released on the old one — which normally takes a few days, not a quarter.