Glossary · Methodology
Agile PLM: Why the Real Answer Is an Engineering Operating System
Teams searching for an “agile PLM” usually want one thing: a substrate that moves at engineering speed without losing the rigor certification demands. Koddex is not an agile PLM, it is an Engineering Operating System that owns the typed graph of requirements, BOMs, tests, and baselines on a single substrate. The agile cadence below falls out of that architecture; this page is the operational reference for what it looks like in practice.
Agility + rigor is one face of an Engineering OS
Teams that search for "agile PLM" are usually trying to fix one symptom: the heavy-weight PLM moves too slow for how the team actually works. Solving that symptom with another PLM stops short. Koddex is not an agile PLM, it is an Engineering Operating System that owns the entire engineering graph and turns it into operational excellence. The agile cadence below is what falls out of that architecture, not a feature toggle on a lighter-weight PLM — and it is what makes the engineering infrastructure an industrial advantage.
The cadence difference, in one engineering scenario
A single change request, "swap the BLDC motor for a higher-torque variant" - touches requirements, BOM, harness routing, thermal analysis, two test plans, and one supplier qualification record. Same checkboxes either way. The day-to-day cadence is where the categories diverge.
Change request creation
PLM-centric stack
ECR form opened in the PLM, manually populated with affected parts looked up from a separate spreadsheet BOM. Initiator estimates impact based on memory. ECR sits in inbox for the next CCB.
Engineering OS (Koddex)
Initiator selects the motor entity in the graph. System computes the impact set automatically: 12 dependent components, 4 requirements, 2 test plans, 1 supplier. CR opens with the impact pre-attached.
Impact review
PLM-centric stack
CCB convenes weekly. 30 minutes per item. Reviewers ask 'wait, does this touch X?' Engineers leave to check. Decision deferred until next week.
Engineering OS (Koddex)
Reviewers see the impact graph in the CR itself. Cross-discipline reviewers comment threaded on the specific entity. Approval is asynchronous; deadlock requires a 15-minute call, not a CCB slot.
Propagation after approval
PLM-centric stack
Engineer manually updates the BOM in the PLM, the requirement in the RM tool, the test plan in the ALM tool, the thermal model in CAE. Three days of cross-tool edits. One tool is forgotten 40% of the time.
Engineering OS (Koddex)
Approval mutates the typed graph atomically. Dependent entities are flagged stale automatically; affected owners are notified. The thermal model is the only manual step because it lives in a CAE tool, flagged in the to-do for the analyst.
Baseline update
PLM-centric stack
At the next baseline (monthly), someone reconciles which approved changes landed. PDF Bill of Material is regenerated. Three discrepancies are found and emailed around.
Engineering OS (Koddex)
Baseline is a cryptographic snapshot taken on demand. The pre/post diff is computable: every entity that changed since the previous baseline, with its approver and rationale. Reconciliation is the export, not a meeting.
What a 5-week onboarding actually looks like
Not a six-month "discovery phase". Concrete deliverables per week, scoped to land an active engineering program on the platform.
Week 1
Pick the metamodel.
Deliverable
Template loaded (MedTech / Robotics / Aerospace / Nuclear / Manufacturing / Infrastructure). Standard entities live. First requirements imported.
Week 2
Bring the BOM.
Deliverable
Existing spreadsheet BOM imported as typed components with rollups. Cost, mass, supplier fields wired. First impact analysis runs end-to-end.
Week 3
Wire two integrations.
Deliverable
CAD source (your CAD authoring tool) connected. ALM source (the RM tool) federated. Round-trip changes verified.
Week 4
Cut the first baseline.
Deliverable
Signed cryptographic baseline of the engineering graph. Replay verified for an arbitrary past date. Audit export tested against the target certification.
Week 5
Hand off to the team.
Deliverable
Three engineers + program manager trained. AI agent permissions configured. Audit trail compiling. Team works on the platform full-time.
Integration footprint: what stays, what connects, what disappears
Agile PLM is federation-first. You don't migrate decades of CAD libraries; you give them a shared backbone.
Where the time-cost goes
For a 50-engineer hardware program. Rough numbers, but the order of magnitude is what matters.