Menu

Cloud collaboration in SolidWorks: 10 reasons to switch to 3DEXPERIENCE for team development

A designer made a change to a part, opened the assembly – and it suddenly “broke”: some references disappeared, the drawing pulled in old geometry, and it later turned out that a colleague had been editing the same file from an old folder at the same time. For engineering teams, this is not a minor technical inconvenience, but a real risk to deadlines, production documentation and project quality. It is precisely these “broken links” that often become the biggest problem for teamwork in SolidWorks without centralised data management. In this article, we’ll look at how 3DEXPERIENCE cloud tools help solve this problem and nine other common issues: from version control to collaborative mark-ups, CAD-aware storage and secure collaboration with contractors.

Why the traditional approach to CAD data management does not scale

In many engineering teams, working with CAD data starts simply: there is a shared network folder, a local server or internal storage for SolidWorks files. This may suffice in the early stages, but as the number of projects grows, typical problems arise: constant IT support is required, it becomes more difficult to grant access to remote engineers, and the risk of file duplication and loss of up-to-date versions increases. If a company needs local control, approval workflows and structured document management, SolidWorks PDM could be the logical solution – a system that has its place within the engineering infrastructure.

The issue is not that on-premise PDM is outdated or doesn’t work. The problem arises when a team scales rapidly, brings in contractors, works from different locations, and does not want to spend resources on servers, VPNs, backups, and access administration. In such scenarios, cloud-based collaboration via 3DEXPERIENCE becomes a more flexible solution: it helps to centrally store CAD data, manage versions, grant access to the right people and reduce dependence on local IT infrastructure.

What is CAD-aware storage and why is it important

A standard cloud drive such as Google Drive or Dropbox stores CAD files as separate documents but does not understand their engineering logic. For SolidWorks, this is critical, as an assembly consists of more than just a single file: it contains parts, sub-assemblies, drawings, external references and dependencies between elements. When some files are renamed, moved or uploaded separately, the assembly can lose its links. This is precisely why, for teamwork, you need not just cloud storage, but CAD-aware storage that “sees” the project structure.

In 3DEXPERIENCE, these links are preserved automatically: parts, assemblies and drawings remain linked to one another, even when several engineers are working on the project. Open an assembly, and the system fetches the latest links without the need to manually search for files in folders. For teams wishing to combine their familiar workflow in SolidWorks with cloud-based data management, 3DEXPERIENCE SolidWorks is worth considering as an environment where CAD files are not merely stored, but remain an integral part of the engineering process.

Collaborative markups with intellectual property protection

In manufacturing teams, a model often needs to be shown not only to designers, but also to process engineers, contractors, clients or service specialists. However, sharing the original CAD files with all stakeholders is risky, especially when dealing with unique assemblies, industrial equipment or parts with commercial value. In 3DEXPERIENCE, you can grant access for viewing and commenting without editing rights, so the team receives feedback without losing control over intellectual property. This is useful when you need to quickly agree on a change, check installation access, or get feedback from an external partner.

This approach helps replace lengthy emails, screenshots and “for review” files with a clear annotation system. Comments are linked to a specific version of the model, rather than a randomly opened file, so everyone sees the same context:

  • a partner can leave a comment without access to edit the geometry;
  • the client sees the relevant section of the model and comments on it within their authorised permissions;
  • the contractor checks mounting locations, dimensions or assembly areas without receiving the full set of CAD data;
  • the engineer immediately understands which version of the model the comment refers to;
  • the project manager can view the discussion history and make decisions more quickly.

This is particularly important for manufacturing companies, because IP is not an abstract legal term, but a real business asset. If drawings, 3D models and technical solutions circulate uncontrollably among contractors, the team loses transparency and increases the risk of errors. Collaborative annotations in 3DEXPERIENCE help teams work openly, but without unnecessary access: each participant sees exactly what they need for their task.

Automatic version control – the end of manual file naming

Folders containing files named “part_final_v3_DEFINITELY_LAST.sldprt” appear when the team manages versions independently and relies effectively on the engineers’ memories. In 3DEXPERIENCE, automatic version control retains a complete history of changes: who updated the model, which revision was current, what has already been approved, and what is still under review. This directly impacts ECOs (Engineering Change Orders), as each change is linked not only to the file but also to the approval status, the reason for the amendment, and the responsible parties. As a result, production documentation becomes more accurate: the workshop, procurement department or contractor receives not a random copy from a folder, but a verified version that reflects the current state of the project.

PLM without IT infrastructure – how is this possible

Traditionally, PLM is perceived as a large and complex project: separate servers, months of implementation, hiring consultants, configuring processes and ongoing IT infrastructure support. 3DEXPERIENCE offers a different approach: a team can start with cloud-based PDM to manage CAD data, versions and access, and then gradually expand the system to PLM without switching to another platform. When the need arises for change management, task management, approvals or broader cross-departmental collaboration, simply add the required roles and licences. For small and medium-sized manufacturers, this provides access to enterprise-level engineering data management without the need to start with a complex infrastructure; you can find out more about the ecosystem of solutions for such a transition on the 3DExperience Works page.

10 reasons to switch to cloud-based collaboration in SolidWorks

  1. CAD-aware storage. 3DEXPERIENCE understands the structure of SolidWorks files: parts, assemblies, drawings and the relationships between them. This reduces the risk of broken links after files are moved or updated.
  2. Collaborative viewing without transferring CAD files. A team can grant access for viewing and commenting without editing rights. This is useful for working with contractors, clients and manufacturing partners.
  3. Automatic version control. The system keeps a history of changes and helps eliminate manual naming conventions such as “final_v5”. Engineers see the latest version and understand which changes have already been agreed upon.
  4. Mobile access to projects. Team members can view data, comments and statuses not just from their work computer, but also from any mobile device via a web browser. This is useful for managers, technologists and specialists on the production floor.
  5. Scalability without complex reconfiguration. As the team grows, you can add new users, roles and processes. There is no need to rebuild the entire system from scratch.
  6. No need for your own server. The cloud-based approach reduces reliance on local IT infrastructure. The team does not need to maintain a server, VPN, backups or access rights separately.
  7. Integration with SolidWorks. Engineers continue to work in their familiar CAD environment, but gain greater control over data. This reduces the time between the design, approval and handover stages.
  8. Managed access and security. Permissions can be defined for each participant: view, comment, edit or approve. This helps protect intellectual property and prevents the disclosure of unnecessary data.
  9. Gradual PLM implementation. The team can start with cloud-based PDM and then expand processes to include change management, task management and product lifecycle management. The transition takes place on the same platform.
  10. Affordable start-up costs. For small and medium-sized manufacturers, the cloud is often easier to get started with than a traditional PLM project involving server infrastructure. The company pays for the roles it needs and expands the system gradually.

Who is cloud PDM suitable for, and who is it not suitable for

Cloud PDM is suitable for teams that work from different locations, quickly onboard engineers and do not have their own IT infrastructure for servers, VPNs and backups. On-premise PDM is a better choice for companies with strict requirements for physical data storage, security or deep process customisation. Therefore, the decision should be based not on trends, but on the team’s actual needs.

To sum up: how GEO-MENTOR helps you choose the right collaboration model

3DEXPERIENCE does not replace SolidWorks, but extends it into a team platform where CAD data, versions, access rights, mark-ups and approvals all operate within a single environment. For some teams, the optimal solution will be cloud-based collaboration without their own IT infrastructure; for others, on-premise PDM with local control and more in-depth process customisation. GEO-MENTOR will help assess your workflow structure, security requirements, number of participants and scaling scenarios to select a model that truly suits your engineering team.

FAQ

  1. Does 3DEXPERIENCE replace standard SolidWorks?

No, 3DEXPERIENCE does not replace SolidWorks as a CAD system. It extends the workflow: adding cloud storage, collaborative annotations, version control, access management and a gradual transition to PLM.

  1. How does CAD-aware storage differ from Google Drive or Dropbox?

A standard drive stores a file but does not understand the structure of a CAD project. CAD-aware storage takes into account the relationships between parts, assemblies, drawings and revisions. This is critical for SolidWorks, as a single broken link can break the entire assembly.

  1. When is it better to keep SolidWorks PDM on-premise?

On-premise PDM is worth considering if a company has strict requirements for local data storage, complex approval workflows or extensive customisation. GEO-MENTOR can help compare both scenarios.