How to Share SOLIDWORKS Files with Suppliers
What is the safest way to share SOLIDWORKS files with suppliers while maintaining version control?
Managing NX Files Without Teamcenter: Version Control and Supplier Review
What are the best cloud PDM solutions for sharing NX files with suppliers outside of Teamcenter?
TABLE OF CONTENTS
Short answer: NX data can be managed without Teamcenter by putting NX files under one controlled process: check out before editing, check in related parts and drawings together, preserve version history, validate assembly references, and release an approved baseline. Teamcenter adds enterprise lifecycle governance; a lighter cloud PDM layer covers file control, review, and supplier access. The right choice depends on whether the real bottleneck is enterprise governance or day-to-day file control.
Siemens NX is used for complex product design and engineering, and when paired with Siemens Teamcenter it forms an enterprise PLM ecosystem that manages the full product lifecycle. For many small and mid-sized engineering teams, however, a Teamcenter program is not a realistic starting point. The cost, implementation effort, and dedicated administration required are significant.
That leaves a practical question: if you are not running Teamcenter, how do you keep NX files, assemblies, and drawings under control? This guide covers what NX data management actually requires, what breaks in an unmanaged environment, the main approaches available, and where a lighter cloud PDM layer fits — including for teams that need cross-CAD collaboration with suppliers and partners.
What does managing NX data without Teamcenter mean?
It means applying product data management (PDM) discipline to NX files without adopting a full PLM suite.
The distinction matters because the two terms are often used interchangeably. Industry definitions generally separate them by scope: PDM governs engineering files, versions, and revisions, while PLM extends across the wider product lifecycle including configuration management, enterprise change processes, and integration with ERP and manufacturing systems.
For an NX team, PDM-level control means four concrete things:
- Every NX part, assembly, and drawing has one authoritative location.
- Edits are serialized so two engineers cannot silently overwrite each other.
- Version history is preserved and a released revision is distinguishable from a working version.
- Assembly references resolve correctly when files are opened by someone else.
None of those four requirements depends on owning Teamcenter. What Teamcenter adds is lifecycle governance on top of them.
Why Teamcenter is often out of reach for smaller NX teams
Teamcenter is one of the most capable PLM systems available and is widely deployed in aerospace and automotive supply chains — sectors where enterprise PLM is standard. The characteristics that make it powerful at that scale also make it hard to justify for a 5–50 person engineering team.
- Total cost of ownership. Because Siemens does not publish standard Teamcenter list pricing, teams usually need a vendor or implementation-partner quote to estimate license, deployment, configuration, and administration costs.
- Implementation effort. Deploying Teamcenter is an IT project, not a software install. It typically involves specialist consultants and an internal project team.
- Ongoing administration. Beyond go-live, Teamcenter requires sustained administration for user management, updates, and troubleshooting. Larger deployments commonly justify a dedicated administrator.
- Learning curve. Breadth of capability means training overhead, which takes engineers away from design work.
None of this makes Teamcenter the wrong tool. It makes it the wrong first tool for a team whose immediate problem is that nobody knows which NX file is current.
What goes wrong when NX data is unmanaged
Without a PDM layer, teams typically fall back on network drives, email, and generic cloud storage. Four failure modes follow.
- No single source of truth. When files live across local drives, shared folders, and attachments, current version becomes a matter of opinion. Engineers work from stale geometry, and the cost surfaces downstream as rework or scrap.
- Overwritten work. Without check-in and check-out, nothing prevents one engineer from saving over another's changes.
- Broken assembly references. NX assemblies depend on resolvable links to component files. Moving or renaming a part on a shared drive breaks the assembly, and the time cost is absorbed hunting for files.
- No process control. No formal review, approval, or change record means no audit trail for quality or compliance purposes.
The cost of poor engineering data flow is documented outside vendor marketing. A study prepared by RTI International for NIST estimated imperfect interoperability in the U.S. automotive supply chain at at least US$1 billion per year, with the largest share attributed to data exchange and rework rather than software licensing. A peer-reviewed gaps analysis co-authored by NIST researchers similarly found that design, manufacturing, and quality data frequently fails to move cleanly between organizations even when standard formats are available. Independent research by Tech-Clarity has repeatedly found that engineers lose meaningful time searching for and recreating data when file management is unstructured.
Those findings are about the general problem of engineering data control. They do not measure any specific product, but they do explain why the problem is worth solving before it becomes a lifecycle governance question.
How we evaluated the options
This comparison is an editorial framework, not a controlled benchmark. Each approach below is assessed against four criteria:
- NX coverage — can it handle NX parts, assemblies, and drawings, and are references preserved?
- Version-control consistency — is there one mechanism for locking, history, and released revisions?
- Review accessibility — can suppliers and non-CAD stakeholders inspect models without an NX license?
- Deployment depth — how much infrastructure, configuration, and administration is required?
CAD ROOMS is our own product, so the assessment of it should be read with that disclosure in mind. Every option below lists a real limitation.
Five approaches to NX data management
Approach | How it works | Real limitation |
Network drives and email | Files on a shared server, changes coordinated by convention | No locking, no reliable history, references break on move or rename |
NX-native / CAD-integrated PDM | Managed inside the NX environment with deep tool integration | Strongest for NX-only teams; weaker once suppliers use other CAD systems (see the trade-off) |
Neutral-format exchange (STEP, JT) | Convert and distribute derivative files for review and handoff | Conversion drops authoring intent; the derivative must not become the source of truth (format comparison) |
Lightweight cloud PDM | File-based control layer with version history, locking, browser review, and external access | Not a substitute for enterprise configuration management or formal lifecycle governance |
Enterprise PLM (Teamcenter) | Full lifecycle governance, configuration control, ERP and MES integration | Cost, implementation time, and administration overhead are difficult to justify below a certain scale |
Most teams that leave Teamcenter off the table end up combining rows two through four rather than picking one.
What to look for in a cloud PDM for NX files
When evaluating a cloud PDM layer for NX data, five capabilities matter more than feature counts.
- Version and revision history. Each check-in should create a retrievable version, and a released revision should be distinguishable from the latest working state.
- File locking. Explicit check-out prevents concurrent overwrites — the single most common failure in unmanaged environments.
- Reference awareness. The system should help teams preserve, inspect, or validate parent-child relationships between assemblies, sub-assemblies, parts, and drawings, so that opening an assembly resolves the intended component versions.
- Browser-based review. A viewer that renders NX geometry without an NX license is what makes supplier and stakeholder review practical.
- Change and release workflow. Structured review, approval, and release states create the audit trail that ad-hoc sharing cannot.
A practical workflow for NX teams without Teamcenter
- Establish one authoritative project location for all NX parts, assemblies, and drawings.
- Require check-out before editing so concurrent edits are serialized rather than merged after the fact.
- Check in related parts, sub-assemblies, and drawings together, so history reflects a coherent design state.
- Verify that assembly references resolve after check-in, especially following renames or restructuring.
- Route review through a browser viewer rather than emailed files, so reviewers see the version you intended.
- Mark an approved state as a release, and treat the release — not the newest save — as the manufacturing baseline.
- Generate neutral derivatives (STEP or JT) from the released revision when suppliers need them, and record which revision they came from.
- Give external partners scoped, permission-based access to only the projects they need.
Worked example
An OEM designs a housing in NX. A supplier machines it but works in a different CAD system. Instead of emailing a STEP file that immediately becomes ambiguous, the OEM releases NX revision B, generates the neutral derivative from that release, and grants the supplier viewer access to the released files only. When revision C arrives, the supplier sees the new released state in the same place — and the record shows which revision was quoted against.
Decision rule: If your problem is "we don't know which NX file is current and suppliers can't open our models", that is a PDM problem. If your problem is "we cannot demonstrate configuration control across product variants to an auditor", that is a PLM problem — and Teamcenter or a comparable suite is the right conversation.
Where CAD ROOMS fits — and where it does not
CAD ROOMS is a file-based cloud PDM platform. It lists formats associated with Siemens NX among its 35+ supported CAD and engineering formats, alongside SOLIDWORKS, Creo/Pro-E, Inventor, CATIA, and neutral formats such as STEP and IGES. It provides version control, check-in and check-out, revision history, a browser-based CAD viewer, role-based permissions, and release workflows. For a feature-level breakdown against Teamcenter specifically, see the Teamcenter vs CAD ROOMS comparison.
Strong fit when | A different approach may be better when |
NX files need version control and a clear released baseline without a PLM program | Formal configuration management across product variants is a contractual requirement |
Suppliers or reviewers use different CAD tools, or none at all | The team is entirely NX-only and needs deep in-application PDM commands |
External review and secure supplier collaboration matter as much as internal control | Data must remain on-premise or air-gapped for ITAR or classified work |
The team wants file control and IP protection without infrastructure to administer | Deep ERP or MES integration is the primary driver |
Guest access is included on all CAD ROOMS plans without consuming a paid seat, which is relevant when supplier review volume is unpredictable. Capability depth still varies by format, NX release, and assembly structure, so teams should validate reference resolution and viewer fidelity with their own representative datasets before relying on any platform for release control.
Key takeaways
- NX data control is a PDM requirement; Teamcenter solves a broader PLM problem.
- The four non-negotiables are one authoritative location, enforced locking, preserved history, and resolvable assembly references.
- Independent research attributes large interoperability costs to data exchange and rework, not licensing.
- Neutral formats are for exchange, not as a replacement source of truth.
- Choose based on whether the bottleneck is governance or day-to-day file control.
Frequently asked questions
Can NX be used with cloud PDM instead of Teamcenter?
Yes. Teamcenter is Siemens' full PLM suite; NX itself does not require it. A cloud PDM layer can hold NX parts, assemblies, and drawings, enforce check-in and check-out, preserve version history, and provide browser review, while engineers continue authoring in NX. CAD ROOMS provides multi-CAD compatibility for this pattern.
What is the difference between PDM and PLM for an NX team?
PDM governs engineering files — versions, revisions, locking, and release state. PLM extends across the wider lifecycle: configuration management, formal enterprise change processes, and integration with ERP and manufacturing systems. Many NX teams need the first without the second.
Do NX teams need to convert every file to STEP or JT?
No. Keep NX native files as the editable source and generate neutral derivatives when exchange or downstream use requires them. Conversion can omit authoring-specific information, so the derivative should not silently replace the native source. Record which revision each derivative came from.
How can suppliers review NX files without an NX license?
For supported formats, a browser-based CAD viewer lets reviewers inspect geometry without installing the authoring application. CAD ROOMS supports this through its CAD viewer combined with scoped guest sharing, so external collaborators only see the projects you share.
What is the difference between a version and a revision in an NX workflow?
A version is an incremental working state created during iteration. A revision is a reviewed or released milestone, such as Rev A or Rev B. A workflow should preserve both and never treat the newest working version as automatically approved. CAD ROOMS handles this through version history and revision management.
Does CAD ROOMS support Siemens NX files?
CAD ROOMS lists NX-associated formats among its 35+ supported CAD and engineering formats. Support can differ by file type, NX release, and operation, so teams should confirm browser viewing, assembly inspection, and reference behavior using their own project files.
Does a lightweight PDM automatically resolve every NX assembly reference?
No platform should be assumed to behave identically across every format, release, and assembly structure. CAD ROOMS manages supported files and provides assembly-oriented review, but reference resolution and dependency behavior should be tested against complex real datasets before a team depends on it for release control.
When should an NX team choose Teamcenter instead?
When the organization needs configuration management across product variants, formal enterprise change processes, deep ERP or MES integration, regulatory evidence, or governance across the full lifecycle. Those are PLM requirements, and a lightweight PDM layer is not a substitute for them. Teams can also use ECO workflows in a PDM layer as an interim step while assessing whether full PLM is warranted.
References
- NIST — STEP / ISO 10303 product data exchange resources.
- CIMdata — PLM Glossary.
- Trainer et al. (2016) — Design, manufacturing and quality data exchange gaps analysis.
- RTI International for NIST — Interoperability Cost Analysis of the U.S. Automotive Supply Chain.
- Tech-Clarity — CAD Data Management research.
- CAD ROOMS — Supported file formats.
- CAD ROOMS — Understanding version control and revision history.
About the author
Christina Rebel is CEO of CAD ROOMS and co-founder of Wikifactory. She has spent over a decade building cloud-based collaboration tools for engineering and hardware teams, and has written on engineering workflows and legacy tooling for DEVELOP3D and Eureka Magazine. Connect on LinkedIn.
Related articles
Related Posts
Setting Up Access Control: Who Should See What in Your PDM System
A practical guide to PDM access control—covering RBAC, least privilege, an access matrix by engineering role, supplier sharing via Guest access, quarterly access reviews, and what CAD ROOMS supports across Business and Enterprise plans.
CAD ROOMS in TNW: What the Industrial Accelerator Act Covers—and What It Leaves Out
TNW examines what the EU Industrial Accelerator Act currently covers, what it leaves out, and Christina Rebel’s argument for engineering data sovereignty.