Hello
We are currently in the process of switching from ProE (without PDM) to SolidWorks (with PDM), and we are experiencing issues in managing our 3D models.
Assumptions:
We make customizable machines for each customer.
We have 5 sizes of machines (0.8m, 0.9m, 1m, 1.3m, & 1.8m)
Each machine size has 4 versions (1 or 2 doors, left or right technical area)
Each machine may or may not have many options
On ProE:
We have a basic model per machine size with all possible versions/options managed by programs/instances.
For each customer, we copy the entire machine model to the customer directory (except for standard parts), where we make customer-specific changes.
To capitalize, we create instances in our parts/subassemblies following customer modifications, which we then replace in our base models.
On SolidWorks/PDM:
The PDM does not manage the versions of each configuration, how do you manage the versioning of parts with configurations? Do you work with configurations? Is it the PDM that manages the file versions or is it manually populated? Do you have a different way of working?
How is it possible to manage our basic models? Configurations? Programs? Another software suite? 1 model per version/option so more than 150 models in our case?
Do you have a working methodology that would meet our needs?
Thanks in advance,
Hello Lionel!
I would advise you to take a look at the DriveWorks technology.
You already have a free version with SOLIDWORKS called DriveWorksXpress that will help you with your problem.
DriveWorksXpress will allow you to generate your automatically configured 3D models by filling out a form.
Then DriveWorks sells two other versions called DriveWorks Solo and DriveWorks Pro, DriveWorks Pro which has an integration with PDM for example.
Happy searching!
Kind regards
Thomas
1 Like
Hello
Thank you for your answer... Indeed, I had looked at DriveWorks which seems simple and effective in the exercise of furniture. On the other hand, is it applicable for a complete machine? Are there any configurations to manage?
I have a doubt that my management will agree to put their hand in their pocket to buy an additional module...
Hello, DriveWorks is only a tool for creating product configurators and sales configurators.
The example of the piece of furniture is only a very simple example to show the principle.
I don't know your machines so I can't get too far ahead of myself, but it's very rare that DriveWorks can't automate even very complex SOLIDWORKS designs.
If you are concerned, I would recommend contacting your SOLIDWORKS reseller so that they can show you the technology in more detail.
Other examples are available on the www.driveworkslive.com website, for example a semi-trailer demo: http://web2.driveworkslive.com/Apps/Trailer/
I hope it can help.
Happy searching.
Thomas
Thank you... On paper, it looks very good and very beautiful.
How is the basic model(s) to configure the machine managed? A single model with configurations? And so how do you manage this model in the PDM?
In short, I'll have to take a serious look at DriveWorks before we start the new studies on SolidWorks.
Driveworx is indeed very powerful but it is still quite heavy to set up (especially when it starts to be complicated).
Generally with a special machine we copy assemblies and rename with a different project name (which EPDM can do very well if it is well configured or with the project copy by making selections). What is impossible to do in EPDM is to make duplicates (files with the same names in 2 different directories). Simply change the name of the copied file to resolve this issue. At the very least, the addition of a suffix/prefix solves this.
PDM does not manage the versions of configurations but of parts or assemblies. Nevertheless, in a PDM assembly knows very well which configuration of a part (or a subassembly) you are using.
We use part configurations to handle different materials and/or lengths. Adding one (or more) new configuration requires a new version of the file. It takes up disk space on the server but it's not problematic in absolute terms (anyway if you don't use the configurations you would have created a new part...).
We work in taps with specific parts (valve body) and standard parts (operating devices). Generally, we duplicate existing assemblies to save time and we have libraries of standard sub-assemblies for the operating part of the assembly.
Now, to limit the number of sub-assemblies registered, we work a lot in virtual assemblies (all sub-assemblies are saved in the main assembly). This makes copying easier and limits folder errors.
On the other hand, the virtual is very badly managed by EPDM in version 2015 (we had to develop a report generator to have the use cases of the files used by virtual subassemblies: since the virtual assembly has no real existence on the server it is not really managed by EPDM)
Thank you for your answer... But I didn't get the part about managing part configurations well.
What do you mean by creating a file version? Are you creating a new file?
How do you handle configuration versioning? Via PDM, manually or no management?
And how do you manage a basic model of a machine with options? with configurations?
DriveWorks Pro allows you to define which version of the base models to use to generate new models.
For more info on DriveWorks and the PDM plugin:
http://docs.driveworkspro.com/Topic/SolidWorksEnterprisePDMPluginSettings
- Get the latest version with 'Ensure latest master models and drawings'
- Define a specific version with 'Get specific version of Master model'
Kind regards
Thomas