SYSTEM GRAPH
One graph. Every dependency.
From top-level assembly to every sub-component. Relationships are explicit, typed, and always current.
CTO / VP Engineering
Your team is scaling. Your engineering data isn't keeping up.
Koddex gives engineering leaders a structured, computable operating layer from BOM to baselines to AI-ready data, without adding process overhead.
- 01
No single source of truth. Product data lives in CAD tools, spreadsheets, Confluence pages, and email threads. Nobody agrees on what "current" means.
- 02
Baselines drift. Teams edit files after a design freeze. "Locked" configurations get modified without formal revision. You find out during an audit, or after a field incident.
- 03
Certification pressure is increasing across every industry. EU MDR and FDA QMSR raised the bar for MedTech. AS9100 is becoming IA9100 and DO-178C / DO-254 demand connected baselines for aerospace. ISO 10218, EN ISO 13482 and IEC 61508 reshape robotics. RCC-M and 10 CFR 50 App. B run nuclear and energy. Every regulatory update demands structured, traceable engineering data. Your current toolstack wasn't built for that level of proof.
Assembly A1842 g
Module M-12612 g
Component C-04+12 g
COMPUTED ATTRIBUTES
Mass budgets that calculate themselves.
Change a component value. Every parent assembly recalculates up the full hierarchy. Instantly. No formula maintenance.
🔒Rev A
🔒ITEM-01
🔒ITEM-02
🔒ITEM-03
Rev B
Baseline locked · Rev A
BASELINES
Lock the configuration. Branch for what's next.
Freeze a baseline before production or audit. Create a new revision without touching the locked state.
agent_read / BOM_v3 / 14:02:31
agent_read / REQ-042 / 14:02:33
MCP & AI AGENTS
Every AI agent gets the same fine-grained access as your engineers.
The Koddex MCP server exposes your engineering graph to AI tools with full traceability and permission controls.
How Koddex compares for engineering leaders
| Criteria | Excel / Sheets | Confluence / Notion | Jira | Flow Engineering | Koddex |
|---|---|---|---|---|---|
| Structured BOM with typed attributes | |||||
| Automatic roll-up calculations across hierarchy | |||||
| Item-level baseline locking (structural) | |||||
| Formal revision lineage with predecessor link | 1 | 2 | 3 | ||
| Permissions scoped at individual item level | |||||
| Requirements linked to components | |||||
| AI / MCP agent access with audit trail | |||||
| API schema derived from live data model |
- 1.Confluence tracks page version history but not structured engineering object lineage.
- 2.Jira tracks issue change history but not revision lineage between typed engineering items.
- 3.Flow Engineering tracks requirement versions within its own model, not across a full system graph.
Engineering leadership across our industries
MedTech
Class II–III device makers under EU MDR, FDA QMSR, ISO 13485.
Robotics
Industrial, mobile and humanoid platforms under ISO 10218, EN ISO 13482, IEC 61508.
Aerospace & Defense
AS9100, DO-178C, DO-254 and EASA Part 21 programs with locked baselines.
Nuclear & Energy
RCC-M, 10 CFR 50 App. B, IAEA SSG-39 design control for reactor and SMR systems.
Advanced Manufacturing
ISO 9001 / IATF 16949 plants with structured BOMs and revision control.
Complex Infrastructure
Multi-decade systems with long-lifecycle configuration and audit obligations.
