0
release process
SharePoint has no idea what a release is
« We are on SharePoint, but we need formal version control and unique document ids. »A revision is a state with a signature, not a filename.
Use case · Project management · Engineering
Freeze a baseline in one click, compare any two baselines item by item, and release with the approvals attached. Koddex handles configuration management without a separate spreadsheet.
0
edits possible on a released revision
1 click
to open the next revision
Properties of the release rules shown, not measured outcomes.
Watch it in 60 seconds
0
release process
« We are on SharePoint, but we need formal version control and unique document ids. »A revision is a state with a signature, not a filename.
0
electronic signatures
« We need control over revisions and releases — the kind PDM gives you. SharePoint does not. »Approval locks the item and signs it. Changing it needs a new revision.
20
clicks
« If it is complicated, people do not do it. »Revising is one action on the item, so it actually gets done.
Approval locks the item, so what was validated stays exactly as signed and the next change opens a new revision instead of overwriting it.
Each review gate is a baseline, and comparing it with the previous one shows what changed since PDR, item by item.
Revise from the released state and Koddex keeps the lineage, with no manual renumbering and no file copied under a new suffix.
01
Lock a scope at a milestone and its content is sealed with a hash, so anyone can check that what they read is what was approved.
02
The approval is recorded on the item with who signed which revision.
03
Open the next revision from the released one and the lineage is kept, so the configuration at any past date can be retrieved in one query.
03
It picks up the task in Koddex, works on your product data, comments on what it found and hands you the result to approve.
AI release engineer
▸List what changed between the PDR and CDR baselines of the gripper.
11 items changed: 4 parts revised, 3 requirements reworded and 4 tests added. 2 of the revised parts are not approved yet, so I moved them to review and notified their approvers.
Every agent action logged · scoped to the user's permissions
The scope you select: the entities, their attribute values, and the links between them. A content hash is written over that scope, so any later difference is detectable rather than a matter of trust.
Yes. Locking creates an immutable reference point; work continues on the next revision. The locked state stays readable and traversable alongside the live one.
No. Koddex sits with your CAD, PLM and ERP, not instead of them. It links what is already there on one graph and computes the effects of a change, and it connects to PLM, QMS, ERP and MES platforms through its API.
The first use case is typically live within 48 hours, and full onboarding takes about three weeks, led by a dedicated Customer Success Manager.
Exclusively in the European Union, in the AWS Europe (Ireland) region. No customer data leaves the European Economic Area without your prior written agreement.
Bring the release that took a week to assemble. In the demo, we freeze, compare and revise a release like yours in Koddex.
0-5 min
you describe the product and the change
5-15 min
we show the use case in Koddex on a product like yours
15-20 min
you leave with a plan for your first use case, live within a month
We use cookies to keep the site running and to understand how it's used so we can improve it, like most sites do. Read the cookie policy