Do I need to change how I use NX?

No. OpenVault sits underneath the files you already create. You work in NX as you always have. When you save a part, OpenVault can version it automatically or you can commit it explicitly from the command line. No plug-in required, no workflow changes in the CAD tool.

How large can a .prt file be?

NX parts can easily be 100+ MB, and assemblies with many subparts can be larger. OpenVault routes files through Git LFS automatically, so the repository stays fast even with large binaries. Cloning, pulling, and branching remain quick because Git LFS defers downloading the actual file bytes until you check them out.

Can I version drawings and BOMs alongside the part?

Yes. A single commit can include the .prt file, the associated drawing (.dwg or .pdf), the BOM spreadsheet, and any simulation results. Commit them all together, and they travel together. This keeps the relationship between model, drawing, and BOM coherent across revisions.

How does conflict resolution work with binary files?

When two branches change the same .prt file, Git detects the conflict and OpenVault shows you both versions. You cannot automatically merge binary geometry because there is no correct way to combine two 3D models without losing one of them. You examine both versions and decide which one to keep, or you re-edit the file manually to incorporate both changes. The person with the best context makes the call.

Can I view old versions of a .prt file without checking it out?

Yes. Use `git log` and `git show` to inspect history. If you want a visual comparison, ToolCrib CLI can convert two versions to STEP and run a 3D diff, showing additions in green, removals in red, and unchanged geometry in gray.

What about suppliers and contract manufacturers?

Export to STEP and share via Tool Crib Cloud for web preview, comments, and approval. Contract manufacturers can see the full history and trace a design back to its intent. Internal teams use the Git repository for version control. Supplier handoffs use STEP and Tool Crib Cloud for review and sign-off.

NX version control with OpenVault

Siemens NX part and assembly files (.prt) are binary and large. OpenVault handles them through Git LFS, so your design stays clean, histories stay legible, and your team works offline then syncs. Convert to STEP for exchange with ToolCrib.

Why NX needs version control

NX is a powerful CAD system, but NX files are large binary objects. A single assembly can span hundreds of megabytes. Traditional shared folders break down fast: file copies pile up, naming conventions fail, and there's no way to recover a previous design without hunting through backups.

NX also locks files. If a teammate is editing a part, you cannot edit the same part at the same time. This works for some teams but blocks parallel development: two designers can't iterate on different branches of the same feature, and there's no easy way to explore design variants without disrupting the main work.

OpenVault brings Git's branch-and-merge workflow to NX. You work offline, explore freely in your own branch, and sync when ready. Conflicts surface cleanly so you can resolve them by hand, keeping design intent intact. Large binary files move through Git LFS automatically.

OpenVault + NX: the workflow

storage

Git LFS for .prt files

NX part and assembly files (.prt) are binary and often 100+ MB. OpenVault routes them through Git LFS so your repository stays fast and history stays readable.

merge

Branch and merge

Create a branch to explore a design variant without touching the main assembly. Iterate freely in your own space, then merge back when it's ready.

cloud_off

Offline work

Clone the repository once. Work anywhere: in the field, on a plane, on a disconnected network. Sync your commits when you reconnect.

difference

Conflict resolution

If two teammates edit the same .prt file, OpenVault flags the conflict and shows both versions. The engineer with the best context decides.

history

Full audit trail

Every commit carries author, timestamp, and message. When a regulator asks how a part evolved, the history is already there. No archaeology required.

conversion_path

STEP export via ToolCrib

Convert .prt files to STEP for exchange with suppliers, simulation, or manufacturing systems. ToolCrib CLI handles format conversion in batch.

The workflow: NX + OpenVault + ToolCrib

Your team uses Siemens NX to design assemblies. The part files (.prt) live in a Git repository managed by OpenVault.

Sync and review. At the start of the day, you sync your local clone. OpenVault pulls down what teammates committed overnight. You can see which parts changed, who changed them, and why (the commit message). No guesswork, no shared-folder archaeology.

Branch to design. When you start new work, you branch. Now you have a private space to iterate. You can edit the part, try a different approach, revert a mistake, all without affecting the main assembly. Your teammates see nothing until you push.

Commit coherence. When you finish a piece of work, you commit the updated .prt file along with any drawings, BOMs, or simulation files that came with it. The pieces that belong together travel together in one changeset. A teammate who syncs gets the whole coherent update at once.

Merge back. When your branch is ready, you merge it. OpenVault handles the binary conflict detection: if nobody else touched that .prt file while you were working, the merge is clean and fast. If someone did, OpenVault stops and shows you both versions so you can decide.

STEP exchange. When you need to share geometry with a supplier, a CAM system, or a simulation team, you export to STEP. ToolCrib CLI converts .prt to .step in batch, and you can upload the result to Tool Crib Cloud for web preview, annotation, and approval.

# Clone the NX repository
git clone https://your-repo-host/nx-designs
cd nx-designs

# Branch to design a new feature
git checkout -b feature/improved-bracket

# (Edit in NX, then commit)
git add bracket_assembly.prt
git commit -m "redesign bracket for weight reduction"

# When ready, sync and merge
git push origin feature/improved-bracket
# (open pull request on GitHub / GitLab, or merge locally)

# Convert to STEP for suppliers or CAM
toolcrib convert bracket_assembly.prt --to step

Binary file handling

NX files are not text. OpenVault does not try to merge them line by line. When two people edit the same .prt file, the result would be corrupted. OpenVault flags the conflict instead and shows both complete versions so the designer with the best context can decide.

This is honest and safe. The alternative, offered by some tools, is to automatically attempt a merge on binary data, which usually corrupts the design. OpenVault trusts engineers to resolve design conflicts manually.

Conflict happens on purpose: when two people are designing the same part in parallel and you need to decide which approach wins. OpenVault makes that decision point explicit instead of hiding it or breaking the file.

Regulated industries: aerospace, automotive, medical

If you work in aerospace (AS9100), automotive (IATF), or medical device manufacturing, you must answer "what changed, when, by whom, and why" for any part of the design.

With OpenVault, that audit trail is automatic. Every commit already carries author, timestamp, and rationale. You are not assembling the history after the fact. The discipline that keeps your team from losing work also keeps you audit-ready.

Tool Crib Cloud adds approval workflows and digital signatures if your process requires sign-off on design changes before release.

NX and OpenVault questions

Do I need to change how I use NX?: No. OpenVault sits underneath the files you already create. You work in NX as you always have. When you save a part, OpenVault can version it automatically or you can commit it explicitly from the command line. No plug-in required, no workflow changes in the CAD tool.
How large can a .prt file be?: NX parts can easily be 100+ MB, and assemblies with many subparts can be larger. OpenVault routes files through Git LFS automatically, so the repository stays fast even with large binaries. Cloning, pulling, and branching remain quick because Git LFS defers downloading the actual file bytes until you check them out.
Can I version drawings and BOMs alongside the part?: Yes. A single commit can include the .prt file, the associated drawing (.dwg or .pdf), the BOM spreadsheet, and any simulation results. Commit them all together, and they travel together. This keeps the relationship between model, drawing, and BOM coherent across revisions.
How does conflict resolution work with binary files?: When two branches change the same .prt file, Git detects the conflict and OpenVault shows you both versions. You cannot automatically merge binary geometry because there is no correct way to combine two 3D models without losing one of them. You examine both versions and decide which one to keep, or you re-edit the file manually to incorporate both changes. The person with the best context makes the call.
Can I view old versions of a .prt file without checking it out?: Yes. Use `git log` and `git show` to inspect history. If you want a visual comparison, ToolCrib CLI can convert two versions to STEP and run a 3D diff, showing additions in green, removals in red, and unchanged geometry in gray.
What about suppliers and contract manufacturers?: Export to STEP and share via Tool Crib Cloud for web preview, comments, and approval. Contract manufacturers can see the full history and trace a design back to its intent. Internal teams use the Git repository for version control. Supplier handoffs use STEP and Tool Crib Cloud for review and sign-off.

Start version controlling NX today

OpenVault is free and open source. Install it with pip, initialize a repository, and commit your NX designs. When your team wants a shared cloud workspace with web preview and approval workflows, Tool Crib Cloud adds that without changing your local Git workflow.