1
spreadsheet
One reactor, one spreadsheet
for the configuration of a whole reactor programme
« We need to get professional about this. »Configuration is a locked structure, not a file someone maintains.
Project & programme management
Your programme status, computed, not reported.
Changes, deliverables and suppliers on one graph. Every owner notified, every dashboard current.
koddex · change impact across a programme
1
backbone shared with every external partner
1 day
impact analysis, instead of 2 weeks
10 s
to find information, instead of 45 min
+30 %
time back on engineering
Measured at our reference customer after a year in use. Your first scope measures them on your own programme.
What we heard
The spreadsheet, the three sites.
3
sites
Three sites, three continents, one machine
no shared source, BOMs retyped line by line
« If it is complicated, people simply do not do it. »One workspace the three sites write into, not three that export.
3
views, one BOM
Three bills of materials pretending to be one
so every change means redrawing
« Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »One structure, three views. Each discipline reads what it needs.
The gain
Before and with Koddex.
| Before Koddex | With Koddex | |
|---|---|---|
| Work with external organisations | Files by email, one version per partner | One backbone, partners read at the source |
| Impact analysis of a change | 2 weeks of meetings and spreadsheets | 1 day, propagated across the graph |
| Find the right information | 45 min across four tools | 10 s, where-used in one click |
| Engineering productivity | Time lost to administration | +30 % of time back on the product |
| Produce the certification file | A project before every review | Exported in one click |
Measured at our reference customer after a year in use. Your first scope measures them on your own programme.
Built with teams like yours
Changes across organisations, sites and orders.
Aerospace · Tier 2 supplierReference scenario
A Tier 2 supplier, five organisations, one graph
5
organisations, one graph
11
items reached by one change
0
routings visible to the customer
Koddex/Novae Aerostructures/Part
Part
M7QK2PNovae AerostructuresR&DSharedModel
ContentWhere-usedActivityInstances
Model relationsInheritance tree
- IntegrateRe-keyed from PDFsImported once, linked to parts
- ShareWeekly spreadsheet by emailScoped access to the kit
- Keep privateStripped from each file by handRoutings never carry the customer tag
The core of Koddex
Model, structure, synchronise.
koddex · models
Model
Your objects and business tasks, modelled by your teams in your vocabulary.
See the featurekoddex · lock & revisions
Structure
Requirements, BOMs, tests and changes become linked objects, with rights and revisions.
See the featurekoddex · computed values
Synchronise
Data flows in from your PDM, ERP and MES; computed values propagate on their own.
See the featureNEXT STEP
Get a live demo, custom-built for your organisation.
A free live demo on your own workspace
We build a Koddex workspace with your models and your vocabulary, on programme management use cases, then walk your team through it live. Free, 30 minutes.
Book my custom demo →IN THEIR WORDS
Verbatims: what hardware teams say about Koddex.