Product / Collaborate
One design, one identity, and the history that explains it.
A project is the boundary for designs, assemblies, manufacturing artifacts, and revision history. Chudware keeps the sequence of decisions attached to the geometry, so a handoff carries the deliverable and the reasoning behind it.
Revision history
History is a line you can walk back.
Save a checkpoint when a design decision is ready to preserve, and use the note to explain why the design changed and what evidence you checked. The design keeps one identity; history carries the sequence.
Inside a project
Keep related work under one root.
Native .step+ files belong under the project root so Chudware can connect them without relying on absolute paths. Design files register through their save and checkpoint flow; supporting non-design files are added as project items.
That distinction matters at handoff. A supplier PDF and a photo of a failed print are evidence, and they should sit beside the revision they justify rather than in someone's mailbox.
| Designs | Native .step+ parts and assemblies under the project root |
|---|---|
| History | Checkpoints with revision notes, newest first |
| Artifacts | Specifications, photos, reports, supplier files as project items |
| Manufacturing | Job output produced from the designs in the same project |
| Compare | An item at two history points, including a rendered geometry diff |
Project graph
See how the documents are actually connected.
The PLM workspace renders the project as a node-and-edge graph: documents and related items as nodes, their relationships as edges. You can search it, scope into a single node and its neighbors, or switch to a grid view with rendered document previews.
Jumping from a part in the Feature Manager to that part's links in the graph is one click.
Before a handoff
- Checkpoint the design so the recipient starts from a known state
- Confirm every referenced part is available in the project
- Include the relevant drawing, neutral export, or manufacturing output
- Leave the decision trail intact — the notes are the handoff
Next
Give the work a project before it needs one.
Open a browser workspace, or read how the copilot operates inside the same documents and history.