Introduction

Before saving any SOLIDWORKS files to 3DEXPERIENCE it is important that the SOLIDWORKS environment is configured to meet the customer’s requirements.  A poorly configured environment can result in a customer experiencing unexpected or unintended behaviour when using SOLIDWORKS. This could result in increased technical support overhead for a partner, and an increased risk of the customer rejecting the solution.

The following sections cover the key SOLIDWORKS configuration topics that need to be considered to ensure that the customer starts on the right track from day one. These are applicable to both the 3DEXPERIENCE SOLIDWORKS and the Collaborative Designer for SOLIDWORKS roles.

 

SOLIDWORKS MySession Settings

The SOLIDWORKS MySession settings provide the ability to configure the open and save behaviour on each individual user’s workstation. In order for a customer to have the best experience it’s important that users understand these options and how they affect the behavior of SOLIDWORKS. When teams of users are working together on the same project it’s important that the settings chosen are consistent across all workstations to avoid unexpected behavior.

The MySession options are located on the Tools tab of the MySession toolbar.

 

 

. 

Managing SOLIDWORKS System Options in 3DEXPERIENCE

In a situation where a user’s SOLIDWORKS system options are controlled by an administrator via an sldsettings file, the 3DEXPERIENCE platform can be used to store and manage the settings file. Managing the sldsettings file in 3DEXPERIENCE removes the need to store it on an inhouse server and provides a quick and easy way to deploy standardized SOLIDWORKS settings to multiple users at a company. 

A sldsettings file is generated using the Settings Administrator utility. For customers using 3DEXPERIENCE SOLIDWORKS, the utility is located in the SOLIDWORKS installation folder. For customers using SOLIDWORKS desktop and the Collaborative Designer for SOLIDWORKS role, the utility is located in the SOLIDWORKS administrative image.

SOLIDWORKS templates are the method of enabling all users at a company to work together using consistent SOLIDWORKS settings and defined drawing standards. For existing SOLIDWORKS customers adopting 3DEXPERIENCE , storing templates in the platform allows them to maintain that consistency of settings and standards with some added benefits.

Security, storing SOLIDWORKS templates in 3DEXPERIENCE provides control over who can modify and delete templates. This is important for customers operating in tightly regulated industries where drawings and have to adhere to strict standards, and for customers working concurrently on large assemblies where having consistent settings across all users will enable everyone to work in the most efficient way.

Storing and managing SOLIDWORKS templates in 3DEXPERIENCE provides the additional benefit of lowering administration overhead. Templates don’t need to be backed up from a server, and any modifications can be immediately made available to all users in a company, which can be a big benefit to customers both large and small.

The process of uploading Part, Assembly, or Drawing templates is the same as a regular SOLIDWORKS file. When opened in SOLIDWORKS a template is saved to a collaborative space using the MySession save. However there are a few subtle differences. Templates are recognized as their own object type which is XCAD Template. During the save the user is offered the option of either creating the template in the Released maturity state making available to all users, or in the Private maturity state where it will only be accessible to the person saving. Any templates saved in the Private state can always be promoted later to Released if required.

EXPERIENCE SolidPractices guide titled Storing Templates.

 

Working with SOLIDWORKS Properties and 3DEXPERIENCE Attributes

The majority of SOLIDWORKS users adopting 3DEXPERIENCE will be used to storing their files in a folder structure. The folder structure will typically follow a naming convention, for example project names, and users will either search or browse the folder structure to find and open content.

An existing SOLIDWORKS user’s experience of using attributes will be in the form of SOLIDWORKS Properties. Properties are typically used to capture information and display it in a drawing parts list and title block. Common properties could be for example, part number, material, weight, supplier etc. For many customers, especially ones who are not using SOLIDWORKS PDM, their usage of property information will not extend to anything more than this.

3DEXPERIENCE utilizes a different approach to organising content which is based around searching and filtering using attributes. SOLIDWORKS content is stored in a collaborative space which is a flat structure. Different apps provide the user with views of their content depending on what they need, for example a folder style view in Bookmarks Editor, interrogating an assembly structure using Product Explorer. No matter which of these apps is used to navigate content, attributes are used to enable the user to rapidly drill down, or “filter” their view to get to specific information. This to helps users make more informed product development decisions.

It is a different concept to using Windows folders, and it can take new users a little time to re-programme from thinking in terms of folders. However once users do, this approach offers a faster and more efficient method of interrogating design or project information.

Attributes from 3DEXPERIENCE can be mapped to SOLIDWORKS parts, assemblies, and drawings. There are two types, PLM attributes for example Revision and Maturity which are available without any set up, or user defined attributes from an object (Physical Product, Drawing). Likewise SOLIDWORKS properties can be mapped to 3DEXPERIENCE. This is useful for passing property values to 3DEXPERIENCE that are generate by SOLIDWORKS, for example Material

When configuring attribute mapping from SOLIDWORKS it’s important that the customer is familiar with the concept of CAD Family vs Physical Product in relation to SOLIDWORKS Parts and Assemblies. It is important that any properties defined in SOLIDWORKS are stored on the configuration specific tab. Configuration specific properties map to the related Physical Product and therefore will be searchable and visible in all of the 3DEXPERIENCE web apps.

For a comprehensive overview of how to configure attribute mapping with recommended best practices, please refer to the 3DEXPERIENCE SolidPractices guide Attribute Mapping for SOLIDWORKS.

 

Configuring the SOLIDWORKS Design Library for 3DEXPERIENCE

The SOLIDWORKS Design Library tab in the SOLIDWORKS Task Pane provides a central location for reusable design elements such as parts, assemblies, and sketches. Traditionally the Design Library displays sub folders and their contents located on a local or network drive.

Customers adopting 3DEXPERIENCE can store their Design Library parts and assemblies in a collaborative space, and organize them using a Bookmark structure. This is called a Connected Design Library and is displayed in the Task Pane with a blue library icon.

 

EXPERIENCE Utility is used to upload the files replicating the existing folder structure as Bookmarks. To avoid users unintentionally modifying the Design Library items it is recommended that after the upload, the library items are promoted from “In Work” to the “Released” state if no further modifications (geometry, attributes etc.) are required.

 

• In SOLIDWORKS Options > File Locations, show folders for Design Library and click Add

In the choose folder dialogue box, click Select from 3DEXPERIENCE.

 

Using a “Protected” Collaborative Space type provides a simple method of restricting the access to Design Library components undergoing modification while in the In Work maturity state, followed by automatic exposure of the Design Library components to the wider business when they are promoted later to the Released state.

 

Configuring SOLIDWORKS Toolbox for 3DEXPERIENCE

Its common practice for existing customers using SOLIDWORKS Professional and Premium to be utilizing Toolbox for their standard parts library.

The Toolbox component library can be fully managed using 3DEXPERIENCE, therefore it is important that both new and existing customers intending to use Toolbox have a complete understanding of how to use it in the context of 3DEXPERIENCE.

 

EXPERIENCE platform by the administrator. The package file can be automatically created from step 6 in the Toolbox configuration utility.EXPERIENCE the default collaborative space and initial maturity state of uploaded Toolbox components can be configured from the Standard Libraries Management area of the Collaborative Spaces Configuration Center.

 

 If Toolbox components need to edited before being made available to the wider design team, then its recommended that the default Maturity state to set to In_Work. When in the In Work state Toolbox components can modified and then promoted to the Released state as a separate operation.

For a comprehensive overview with recommended best practices, please refer to the SolidPractices guide titled Working with Toolbox.

 

Recommendations and Strategies for Using SOLIDWORKS Configurations

Before starting any new design project, it is important to choose the right strategy for working with SOLIDWORKS configurations. Failure to plan ahead can result in many unwanted and unnecessary linked Physical Products being created when saving new parts and assemblies. The result of this can lead to an unnecessarily complex experience for both SOLIDWORKS and other 3DEXPERIENCE users, loss of revision and lifecycle flexibility, and at worse degraded SOLIDWORKS opening and saving performance due to the additional items and information being managed in session.

Taking the right approach will enable you and your design teams to maximize the benefits of working in the 3DEXPERIENCE right from the start.

Prototype and Production Parts and Assemblies

Recommended Strategy - One Physical Product per Part and Assembly File

It’s recommended that parts and assemblies designed and developed in house for production should only have one SOLIDWORKS configuration converted to a Physical Product on save to 3DEXPERIENCE. This nominated SOLIDWORKS configuration should be configured to contain any key SOLIDWORKS properties related to engineering and manufacture. 

The resulting Physical Product in 3DEXPERIENCE will represent a single engineering definition for that part and assembly including the maturity state, Enterprise Item Number, plus any Physical Product specific attributes.

For existing SOLIDWORKS customers that are adopting 3DEXPERIENCE its important to understand how configurations have been used in their Parts and Assembly files before saving any to 3DEXPERIENCE. Due to their versatility its common practice for design teams to treat configurations as individual part numbers. In this scenario time will need to be spent analysing the files (see configuration rules utility) and factored in to any migration project.

If the intention is to maintain any part or assembly configurations as individually lifecycled engineering items, then those configurations must be split off into their own individual part and assembly files, each containing one Physical Product configuration only. Note, this is a manual process but can be automated using a SOLIDWORKS Macro. 

Understanding the Impact of maintaining Multiple Physical Product Configurations per part and assembly file

If a clearly defined single Physical Product configuration strategy for parts and assemblies is not put in place, then users can find themselves in the situation where multiple Physical Products are created for each file during the first save. Maintaining multiple Physical Product configurations per file can have several negative impacts on the user experience, and SOLIDWORKS performance. 

• Multiple Physical Products representing one SOLIDWORKS part or assembly can make it difficult for users to easily identify which is the actual Physical Product that represents the engineering definition of the part or assembly file.
• Individual revision and lifecycle operations are applied to all the Physical Products related to a single part or assembly at the same time. It is not possible to have related Physical Products at different revisions or maturity states to one another.
• When opening or saving a SOLIDWORKS part or assembly that contains multiple Physical Product configurations all of the attribute and lifecycle information for every Physical Product configuration is processed. This can negatively impact open and save performance in SOLIDWORKS.
• When a user deletes a Physical Product configuration from a part or assembly, this will cause issue if that configuration is referenced in another assembly. In some cases, it may no longer be possible to open the referenced assembly in SOLIDWORKS from 3DEXPERIENCE, without removing that Physical Product from the product structure first. The Product Structure Editor or Engineering Release widgets.

Summary

Adopting the recommended SOLIDWORKS configuration strategy for prototype and production items  outlined in this section will ensure that only one clearly defined engineering item will exist in 3DEXPERIENCE for each part and assembly. Taking this approach will enable you and your design teams to maximize the benefits of working in the 3DEXPERIENCE right from the start.

To learn more about working with configurations and how to tackle common customer use cases please refer to the SolidPractices guide “Using SOLIDWORKS Configurations with the 3DEXPERIENCE Platform” located here.

 

Standard Library and Purchased Parts and Assemblies

Recommended Strategy

Externally purchased parts and assemblies can be treated differently to components designed in house. Typically purchased items are managed in a library, and are not modified or revised by the engineers utilizing them in their designs. 

When deciding which SOLIDWORKS configuration strategy to take with purchased parts please consider the following:

1. SOLIDWORKS part files with configurations that represent different size variations

          a. If there are 20 or less size configurations per part file, Physical Product configurations can be used without negatively affecting               SOLIDWORKS performance.

           b. Greater than 20 configurations per part file, its recommended that a single Physical Product configuration per file strategy is                    deployed to maximize SOLIDWORKS performance. Each individual size configuration will need to be saved out to its own                      individual part file.

                            i. In this scenario Representation configurations must not be used to represent different size variations.                                                        Representation configurations are not saved to 3DEXPERIENCE, therefore the size variation of the part will not be                                  displayed in any of the 3DEXPERIENCE viewer widgets.

      2. SOLIDWORKS Assembly files with configurations 

           a. For all assembly files its recommended that a single Physical Product configuration per file strategy is deployed. Each                            individual size configuration will need to be saved out to its own individual assembly file.

Summary

When deciding on which configuration strategy to deploy for SOLIDWORKS library parts, it’s important to ensure that the user experience is kept consistent. Keep to one strategy, and avoid having a mix of single and multiple Physical Product library parts. 

 

Other areas to consider when implementing the 3DEXPERIENCE platform for SOLIDWORKS users

The table below provides a summary of additional SOLIDWORKS topics that must be considered as part of the SOLIDWORKS setup and configuration.  

 

Feedback

Was this page useful?

Hit the Like Button or let us know what we can improve in the comments section below.