PricingBlogLog in

Feature

PDM for Hardware Startups, Without the Vault Server

Product data management that works from the browser: one editor at a time, released versions that change only when you decide they should, file history that never loses a drawing, and every project pinned to the exact version of each shared part it was built with. No SQL Server, no reseller, no CAD-specific vault.

Check-out

One editor

Exclusive edit rights, visible to everyone

Versions

Your call

New name or deliberate replace, with a warning

Design files

Retired, not deleted

Every replaced file stays in history

The PDM Checklist, and How oroForge Covers It

These are the capabilities a PDM system is expected to have. Here is where each one lives in oroForge.

PDM capabilityHow oroForge handles it
Central part / item masterParts catalog with internal part numbers (IPNs), Owner-defined global fields, and per-part unique fields
Multi-level BOM managementMultiple BOMs per project, sub-assemblies as parts, a BOM tree, and cost roll-up through every level
Check-out / check-inOne editor at a time per custom part, including its files and its sub-assembly BOM
Revision control and releasesNamed versions (A, B, 03, v2), new names create versions, reusing a name replaces it after a warning, each project held at its own version
File vaulting with historyReplaced design files are retired, never deleted; project files are recorded in every project version
Change controlECO workflow with baselines, a reviewable diff, approval, and optional enforcement
Configuration snapshotsProject versions that pin every BOM and sub-assembly to an exact saved version
Rollback and version comparisonEvery named version retrievable; revert a part, sub-assembly, BOM, or whole project, and see what changed between versions
Access control and audit trailRoles, per-project access, Viewer access for contract manufacturers, and a full activity log
Viewing CAD without the CAD toolIn-browser 3D viewer for STEP and STL, SOLIDWORKS preview images, and in-app PDFs

One Parts Catalog as the Item Master

Every part lives once, in one catalog, under its internal part number, and every BOM that uses it points to that same record. Owners define global fields that every part carries (think material, finish, or RoHS status), and any part can add its own unique fields on top. When a part numbering scheme and a field list are agreed once, they stay consistent across every product you build.

Check-Out and Check-In: One Editor at a Time

Two engineers editing the same bracket drawing is how a team ends up with two Rev Cs. In oroForge, editing a custom part starts with checking it out. While you hold it, you are the only one who can change its fields, its files, and, if it is a sub-assembly, the BOM inside it. Everyone else sees who has it checked out.

Checking in hands it back, with an optional comment and an optional new version name. If someone goes on vacation with a part checked out, an Owner can force the check-in, and the activity log records that it happened and who did it.

Version Control on Your Terms

Name versions however your team already does: A, B, C; 01, 02, 03; or v1, v2. oroForge suggests the next one by continuing your pattern. Saving under a new name creates a new version and leaves the old one untouched. Saving under a name that already exists replaces that version, and oroForge tells you before it does, so fixing a typo in Rev B is a deliberate choice, not an accident. Check-ins between versions show as iterations in the history when you want them and stay out of the way when you don't.

Each release records the files that were active at that moment and what changed since the previous one: files added, removed, or replaced, with each replacement paired to the file it superseded. A custom part's catalog data (MPN, manufacturer, description, unit cost, and its fields) is versioned with it, while the IPN stays the part's permanent identity.

Each Product Stays on Its Own Version of a Shared Part

The moment two products share a sub-assembly, a change for one of them is a risk to the other. Most lightweight tools give you one live part that every product reads, so an edit for the new model silently changes the one already in production.

oroForge keeps each project on a released version of every custom part and sub-assembly it uses. When you check out a shared part, you choose which projects follow the edit; every other project stays exactly where it is until someone working on it chooses to update to the latest version. Where-used shows which version each BOM is held at, and forking a project keeps both copies on the same versions until one of them moves on.

File History That Never Loses a Drawing

Replace a design file and the old one is retired, not deleted: it leaves the active file list and your exports, but it stays in the part's history and can still be downloaded. Deleting a file that was part of a released version retires it the same way. Files attached to the project itself (test reports, assembly instructions, compliance documents) are recorded in every project version, and removing one detaches it rather than destroying it, so reverting the project or cancelling a change order brings it back.

Project Versions as Configuration Snapshots

A project version is a manifest: it pins every top-level BOM and every sub-assembly below it to an exact saved version, along with the project's own files. Open any version to see what changed since the previous one, or revert the whole project to it. When your CM asks what was in the EVT build, the answer is a version name, not an archaeology project.

Roll Back When a New Design Breaks Something

Every named version stays retrievable, so a bad change is never the end of the road. If the new bracket doesn't fit or the new board revision fails bring-up, roll back at whatever level the problem lives:

  • Put a project back on an earlier version of a custom part or sub-assembly, without touching the other products that use it
  • Revert a single BOM to an earlier saved version
  • Revert an entire project to an earlier project version, BOMs, sub-assemblies, and project files included

And because every change in oroForge is tracked, you can always see what actually changed between versions: open any version of a part, sub-assembly, or project and compare it with the one before it, down to line items, quantities, fields, and files. When something breaks, you find out what moved before you decide what to roll back.

Change Control When You Need It

Early on, check-out and released versions are enough. When you are ready for formal control, turn on ECO enforcement: check-outs, new versions, file changes, and moving a project to a newer version of a shared part all happen inside an engineering change order, show up in its diff for review, and are released together on approval. Cancelling the ECO puts things back. If you are not sure when that moment comes, see when to start using ECOs.

Access Control and a Complete Audit Trail

Roles decide what each person can do; per-project access decides what they can see. A user limited to selected projects reaches those projects plus the sub-assemblies below them, and nothing above. Add your contract manufacturer as a Viewer and they can open and export the current BOMs and files without editing anything. Every edit, check-out, check-in, release, and file change is recorded with who did it and when.

View CAD Without Opening the CAD Tool

Not everyone who needs to look at a part has a CAD seat. STEP and STL files open in an in-browser 3D viewer with rotate, pan, zoom, and wireframe, so purchasing, your CM, or a reviewer on an ECO can see the part they are signing off on. SOLIDWORKS part and assembly files show the preview image SOLIDWORKS saves inside them; native SOLIDWORKS geometry has no 3D view, so attach a STEP export alongside it when the 3D view matters. PDFs open in the app too. Files are uploaded through the browser from any CAD tool, mechanical or electrical; there is no CAD plugin to install.

At a glance

  • One parts catalog with IPNs, global fields, and unique fields
  • Check-out / check-in with one editor per custom part
  • Owner force check-in, recorded in the activity log
  • Free-form version names with the next one suggested
  • Reusing a version name replaces it, only after a warning
  • Release history with files added, removed, and replaced
  • Each project held at its own version of shared parts
  • Replaced and deleted design files retired, still downloadable
  • Project versions pinning every BOM and sub-assembly
  • Roll back a part, sub-assembly, BOM, or whole project
  • Compare any version with the previous one to see what changed
  • ECO enforcement over check-outs, versions, and files
  • Per-project access and Viewer access for CMs
  • In-browser STEP/STL 3D viewer and SOLIDWORKS previews

Frequently asked questions

Is oroForge a PDM or a PLM?

Both, sized for a hardware startup. The PDM layer covers the part master, check-out/check-in, released versions, and file history; the PLM layer adds engineering change orders, project versions, and controlled handoff to your contract manufacturer. There is no server to install and no vault to configure.

How does check-out and check-in work?

Only one person can edit a custom part at a time. Checking it out gives you the exclusive right to edit its fields, files, and (for a sub-assembly) its BOM; everyone else sees who holds it. Checking in releases it, with an optional comment and an optional new version name. An Owner can force a check-in when someone is away, and that is recorded in the activity log.

Can I overwrite a version that was already saved?

Yes, if you choose to. Saving under a new name like Rev C creates a new version and leaves Rev B as it was. Saving under an existing name replaces that version, and oroForge warns you before it does, so a version only changes when someone decides it should.

If two products share a sub-assembly, does editing it change both?

Only if you choose. When you check out a shared part, you pick which projects should follow the edit. Every other project stays on the version it uses today until someone on that project chooses to update to the latest version.

Can I view STEP or SOLIDWORKS files without a CAD license?

Yes. STEP and STL files open in an in-browser 3D viewer with rotate, pan, zoom, and wireframe. SOLIDWORKS part and assembly files show the preview image SOLIDWORKS embeds in them; there is no 3D view of native SOLIDWORKS geometry. PDFs open in the app as well.

Can I roll back if a new design breaks something?

Yes. Every named version stays retrievable. Revert a whole project to an earlier project version, revert a single BOM to an earlier saved version, or put a project back on an earlier version of a custom part or sub-assembly. Every change is tracked, so you can also compare any version with the one before it to see exactly what changed.

What happens to a design file when I replace or delete it?

Replacing a design file retires the old one instead of deleting it: it drops out of the active file list and exports but stays in the history and can still be downloaded. Deleting a file that was part of a released version retires it the same way.

Related reading:

Try PDM built for hardware startups

Free plan available. Team plan at $50/month for 10 seats. No sales call required.

No credit card required · No implementation consultant