Best Practice for Large Assembly - Copy to another folder

I'm asking for help on how to best copy a large assembly from one folder to another. We have a working folder called "Sandbox" that contains multiple subsystems making up the large assembly. As a lead systems engineers deem appropriate (>80%), we want to copy these subsystems to a new "production" folder and "build" the top-level assembly from each part. I'm asking for guidance and best practices for approaching this critical step in our engineering processes. One fact: duplicates in our PDM vault are enabled. I'm not a fan of that and I welcome feedback if we should allow duplicate file names in our PDM vault. I'm not sure if a Pack & Go of each sub-assembly is best, then reconstrain and mate components again in the new "Production" folder? Has anyone done a copy like this from a prototype "Sandbox" type folder to a production folder?

Comments 3
AV
AV 2021-08-05

Before providing suggestions, there is one important question to ask: does your company use PDM?

MJ
MJ 2021-08-05

Personally I would not allow duplicates in the PDM system especially with solidworks and it's annoying habit of load models "It wants to" from "Where ever it wants to".


There are lots of ways of doing it from a copy paste, PDM Copy Tree, pack and go, save as and so on. How you do it will depend entirely on what you're copying, why and what results you want.


Typically if I'm truly making a copy, IE nothing from this will be used in that, I will use either PDM copy or Pack and go. Both allow for name changes, suffixes etc etc. I believe the "Preferred", "Correct way recommended by our VAR" is to use copy tree.


On the other hand if I'm only making a copy of the assembly that will be similar and reusing parts I will do a "Save as" and rinse and repeat that on any assemblies, sub assemblies etc that I plan on changing.

MP
MP 2021-08-06

I am not a fan of using folders for structuring documents. Period. 

In our pdm vault we use folders for the sole purpose of containing parts and breaking them up into manageable chunks of 1000 or so files each. The 1000 number is just so that file explorer does not choke on "browse to".

Instead use search methods or more generic structural methods to organize parts. This way there is not competition for the "best" place to "store" a part. and part reuse is encourage rather than discouraged. Either build boms or use some kind of tagging or state method to distinguish "sandbox" from "production" depending on what you are trying to accomplish. Search is king... folder browsing was not designed for engineering.
I agree with not allowing duplicates. Solidworks hates duplicate file names.

If you truly want to "cut ties" with your sandbox parts and "start over" for production, I would use copy tree and prepend something to the file name to signify that it is a production part, but first I would question why you really want to "start over" and rather focus on your business rules and workflows to accommodate the sharing of parts, and build workflows with states that reflect "sandbox vs production" etc.