Koddex bridges the gap between technical truth and program visibility, without forcing engineers into project management tools, or business teams into CAD viewers.
Configuration management for a reactor programme lives in a single spreadsheet. It holds, because the people who wrote it are still there. Nobody has asked what happens when they are not.
for the configuration of a whole reactor programme
« We need to get professional about this. »
How do you answer that today?
Configuration is a locked structure, not a file someone maintains.The same machine is configured and built on three continents. Each site rebuilds the bill of materials line by line from the others' exports, because there is no structure all three can write into.
no shared source, BOMs retyped line by line
« If it is complicated, people simply do not do it. »
Engineering, process and production each need a different view of the same product. There is one BOM, so aligning them means rewriting drawings that did not need to change — and the engineering office absorbs it.
so every change means redrawing
« Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »
Engineering data is locked in technical tools. The business team tracks milestones in Monday.com or Notion. Engineers track technical status in spreadsheets or CAD. Neither reflects the other. Decisions are made on stale data.
Status updates are manual and unreliable. Every weekly report requires someone to manually consolidate status from multiple tools. By the time it's distributed, it's already out of date.
Suppliers and partners operate in a different system. Sharing engineering deliverables with external partners means emailing files, losing version control, and having no visibility into what they actually received and when.
Program views read the same graph your engineers work in. No re-keying, no consolidation, the milestone you see is the technical state right now.
Status is queried from live data, not assembled by hand every week. By the time it's shared, it's still true.
Share deliverables in place with scoped permissions. You see exactly what each partner received and when, without emailing files and losing version control.
LIVE STATUS
Computed attributes aggregate completion, compliance, and open items across the full system, automatically.
EXTERNAL SHARING
Grant suppliers or clients view access to specific items, with full traceability of what was shared, when, and to whom.
DIGITAL THREAD
No more re-explaining context between teams. The link between a business decision and its engineering impact is explicit.
GOVERNANCE
Customer reviews, regulatory submissions, and partner audits are served from a single source of truth, not a folder of PDFs.
Program management across our industries
Class II–III device makers under EU MDR, FDA QMSR, ISO 13485.
Industrial, mobile and humanoid platforms under ISO 10218, EN ISO 13482, IEC 61508.
AS9100, DO-178C, DO-254 and EASA Part 21 programs with locked baselines.
RCC-M, 10 CFR 50 App. B, IAEA SSG-39 design control for reactor and SMR systems.
ISO 9001 / IATF 16949 plants with structured BOMs and revision control.
IEC 61400, IEC 61215 and DNV-GL wind, solar and storage assets with locked baselines.
Stop bleeding hours on version chasing, audit prep and cross-team sync. Ship certified hardware faster, on a foundation built for the next decade of complexity.
Enterprise-grade security. Library of certification-friendly templates. Custom deployment for teams of 200+.
Recommended reading for program managers
Software & Tools
A 2026 INCOSE study found systems engineers spend 14 hours per week reconstructing context. That is the real cost of fragmented tooling.
Industry Trends
Most industrial deals die not from technical incompetence but from structural friction. Inside the silent killer of hardware innovation: the cost of internal decision-making.
Software & Tools
Integrators receive a 400-page binder and a CAD bundle. Two weeks later they ask the same questions you already answered. The fix is structural.