3DEXPERIENCE World 2025: How to Enable the Paradigm Shift in SolidWorks Data Management

I came back from 3DEXPERIENCE WORLD 2025, organized by Dassault Systèmes. The event, traditionally focused on SolidWorks customers (formerly known as SolidWorks World), is probably the biggest gathering of mechanical engineers, resellers, and partners in the SolidWorks community. Celebrating 30 years of SolidWorks, the red-colored Houston Convention Center added an additional charm, honoring SolidWorks’ roots at the event.

Check my earlier article – 3DEXPERIENCE World 2025: What’s New from Dassault Systèmes and SOLIDWORKS? which gives you a concentrated list of all news and big announcements made by Dassault Systemes and Solidworks executives.

In my article today, I want to share my thoughts on the paradigm shift in the SolidWorks community and the introduction of the 3DEXPERIENCE platform to SolidWorks customers. Bringing something new is always challenging, especially when it involves competing with past success. Therefore, it is no surprise that SolidWorks users have experienced difficulties in adopting 3DX. The article – 37 things that confuse me about 3DEXPERIENCE by Peter Brinkhuis is a great example of the struggle.

I attended the Go-Engineer session, where they spoke about file management and new roles in 3DX, focusing on data management (Classification), CAD BOM management (Release Engineering), and MBOM (Manufacturing Item Manager). These are core elements of the 3DX solution aimed at helping SolidWorks users move beyond the current file management paradigm (File Explorer-based), which remains dominant among SolidWorks users. Here is a picture that captures the old way versus the new way.

The landscape of file management has undergone a significant transformation, shifting from traditional local storage systems to modern cloud-based database solutions. This shift is driven by the need for better data organization, enhanced accessibility, and seamless workflow integration.

However, the transition comes with challenges, as organizations must overcome resistance to change, manage complexity, and address integration issues.

Old Paradigm or Old Way?

Here are some of my thoughts about real and perceived limitations of the “old (Windows File Explorer based) way”.

1. Reliance on Local Systems: Traditional file management depends heavily on Windows File Explorer, making data storage and retrieval dependent on individual computers.
2. Difficulty in Locating and Managing Files: Without advanced search capabilities, users struggle to find files quickly, leading to duplicate storage and inefficiencies.
3. Challenges with Version Control: Determining the latest revision of a document or CAD file is cumbersome, often requiring manual tracking and renaming conventions.
4. Limited Workflow Integration: The file-based approach operates in isolation, making it difficult to integrate with enterprise applications, such as PLM, ERP, and collaboration tools.
5. Dependence on Individual Knowledge: Employees rely on personal folder structures and naming conventions, making it challenging for new team members to navigate and understand data organization.

While I agree with the points above, here’s a small twist. SolidWorks PDM (acquired from Conisio 20 years ago) placed database behavior behind a file-explorer paradigm. It was one of the most successful implementations of old-fashioned PDM systems, but it shares an important common ground with SolidWorks users. Both SolidWorks and Conisio relied on the Windows file paradigm as the foundation for user acceptance and the user experience—a paradigm widely appreciated by users.

The Modern Approach: Cloud Database Storage

The following bullet points clearly outline the new approach, which is intended to introduce SolidWorks customers to modern cloud-based data management.

1. Centralized, Scalable Storage: Cloud databases offer a centralized repository, ensuring data consistency, eliminating redundancy, and providing scalability.
2. Improved Organization and Searchability: With metadata management, indexing, and search filters, users can quickly find relevant data without manual sorting.
3. Enhanced Collaboration Across Departments: Cloud storage extends workflows beyond engineering, enabling seamless collaboration between product development, manufacturing, and procurement teams.
4. Advanced Version Control: Automatic version tracking ensures that users always work with the latest file, reducing the risk of outdated or conflicting data.
5. Increased Accessibility and Mobility: Data can be accessed from any location with an internet connection, supporting remote work and multi-site operations.

So far, everything seems to be good. Cloud database offers a better data management and everyone should move. Where is the problem? Let’s talk about it a bit more and unpack potentially issues.

Potential Issues with the Comparison

While file management was taken as a basis, most users who only use files will simply upload them to Google Drive, Dropbox, or similar solutions without bothering with anything else. The real comparison is between people using SolidWorks PDM and cloud-based file databases, making the comparison more complex and uncertain.

The comparison between old and new approaches primarily focuses on the typical advantages of cloud-based data management, which represents a technological shift—replacing file explorer-based management with a database-driven approach. However, a more granular comparison reveals that this shift is purely technological:

• Local PDM vs. Cloud Database
• File explorer user experience vs. Browser-based user experience
• File-based attributes vs. Cloud data organization
• Single-file structure (PDM) vs. Multi-structured PLM data organization

The biggest advantage of the “new” approach is a centralized cloud platform, which undeniably enhances data organization (as all cloud systems do) while providing anywhere access without reliance on local networks or multiple VPNs. The main challenge, however, is that it introduces a new and unfamiliar workflow for customers accustomed to the file explorer paradigm.

Challenges in Adopting New Cloud-Database Paradigm

Organizations often face resistance when transitioning from a familiar local file system to a cloud-databased paradigms. The following factors contribute to adoption difficulties:

1. Resistance to Change: Users accustomed to Windows File Explorer may hesitate to learn a new system, fearing disruption to their daily workflows.
2. Perceived Complexity: The term “cloud database” might sound intimidating to non-technical users, creating psychological barriers to adoption.
3. Unclear Value Proposition: Employees may not immediately recognize how cloud-based file management improves their work, leading to reluctance in adopting new processes.
4. Disruption to Existing Workflows: Moving to a new system often requires process adjustments, leading to temporary inefficiencies and user frustration.
5. “If It Ain’t Broke, Don’t Fix It” Mentality: If employees can complete tasks using the old method, they may see no incentive to change, even if inefficiencies exist.

Overcoming Adoption Challenges

Customer transformation is a complex challenge that often raises many questions and is difficult to solve. We can look at examples from the past. Every major shift has relied on two key factors: the widespread adoption of new technology or a familiar user experience.

I can highlight two examples: Microsoft SharePoint introduced a cloud-based database while maintaining the familiar “file user experience.” Similarly, the transition to touch-screen devices was driven by the exceptional performance of multi-touch technology, exemplified by the iPhone and its successors.

So, how can we transition SolidWorks (and many other desktop CAD users) to the new cloud paradigm? In my view, there are three key elements for a successful transition:

1. Seamless integration with the existing desktop tech stack.
2. A familiar cloud user experience that feels effortless for existing users.
3. Compatibility and integration with existing systems to preserve prior investments.

What is my conclusion?

The shift from traditional file management to cloud-based database storage represents a significant advancement in data accessibility, organization, and collaboration. However, successful adoption requires addressing challenges related to resistance, complexity, and integration.

The transition from classic file-based PDM solutions to modern cloud-based file and data management requires a bridge between the familiar file explorer paradigm and a new approach that ensures a seamless user experience. This transition must prioritize ease of adoption while integrating with existing systems to preserve past investments and intellectual property.

Just my thoughts…

Best, Oleg

Disclaimer: I’m the co-founder and CEO of OpenBOM, a digital-thread platform providing cloud-native collaborative services including PDM, PLM, and ERP capabilities. With extensive experience in federated CAD-PDM and PLM architecture, I’m advocates for agile, open product models and cloud technologies in manufacturing. My opinion can be unintentionally biased