If no, then I would say that we move the components that use to build the assembly into the folder another area. That way we only have one version stored for each part number and they should always be current
If no, then I would say that we move the components that use to build the assembly into the folder another area. That way we only have one version stored for each part number and they should always be current
They can be anywhere, as long as they are referenced.
I suggest using PDM.
I always keep projects together, in one directory. The only exception to that is vendor parts and tool box stuff.
no need to use PDM, only a good "working method" is need, and a good part/drawing numbering.
All the settings in a "setting folder" on the network,
All the "Library" part in a "Library folder" on the network.
in addition, you can use the mighty and powerfull free Windows tool "read only" on each file, to lock Library files, or validated project files.
Solidworks can manage the read only since many years (without needing additionnal software, no need PDM)
see "collaboration" in "system options", and read the help for this feature.
and it's possible to have mutiple users on the same project at the same time, working on different sub-ASM.
without problem, with additionnal software…
Thank you so much for your reply and now I got the idea on this.
If they are all stored in one folder, then reusing just 1 part for another assembly breaks your methodology.
It still works just as fine, but now when you tell how to others, you introduce an "except when" and this often leads to others creating their own exceptions (and usually without first asking).
I recommend a folder for each part and a folder for each assembly.
This way, the story stays the same.
Kevin
Thank you so much for your reply. Now am clearly understand.
Kevin Chandler wrote:
If they are all stored in one folder, then reusing just 1 part for another assembly breaks your methodology.
It still works just as fine, but now when you tell how to others, you introduce an "except when" and this often leads to others creating their own exceptions (and usually without first asking).
I recommend a folder for each part and a folder for each assembly.
This way, the story stays the same.
Kevin
That sounds like each Part or Assembly is in a separate folder, so no folder has more than one component. That isn't what you mean, is it?
By the way, I use the method described above by Justin Pires. The Drawing and any project-specific Parts and Assemblies go into one folder. Common Parts and Assemblies are in a separate location and are not copied to the project folder. Drawings for those components are saved as pdf's and attached to the end of the project pdf.
On occasions when I want to use a project specific component for another project the file is copied to the new project folder and re-named before being used in a new Assembly.
Glenn Schroeder wrote:
Kevin Chandler wrote:
If they are all stored in one folder, then reusing just 1 part for another assembly breaks your methodology.
It still works just as fine, but now when you tell how to others, you introduce an "except when" and this often leads to others creating their own exceptions (and usually without first asking).
I recommend a folder for each part and a folder for each assembly.
This way, the story stays the same.
Kevin
That sounds like each Part or Assembly is in a separate folder, so no folder has more than one component. That isn't what you mean, is it?
By the way, I use the method described above by Justin Pires. The Drawing and any project-specific Parts and Assemblies go into one folder. Common Parts and Assemblies are in a separate location and are not copied to the project folder. Drawings for those components are saved as pdf's and attached to the end of the project pdf.
On occasions when I want to use a project specific component for another project the file is copied to the new project folder and re-named before being used in a new Assembly.
Yes. Part & assy folders are at the same level.
There is division by product line but parts and assemblies are assigned their own numbers and all docs for a particular assembly or part go into that numbered folder.
It's what I inherited.
We used to do nested within but when you look at a list of numbered folders, there'd be holes as not all parts had partners or parent assemblies.
And then you'd have to search/guess/know where something was buried.
I think this turned them away and started them on a one to one basis.
This is for internal numbers.
Client data is as they do it. Which is a mixture.
Kevin
It's advised to work locally but me and my co-workers work on servers without a problem.
There is a way to mimic working on a server while working locally, but it's a little too much hassle having to switch back and forth and keep both a server and local version updated, so we decided to only work on the server.
Our server is split up in 4 different partitions. Fabricated Parts, Bought components, Projects and another we call ModSW which is where we store our templates.
Fabricated parts has about 25 folders inside it, each containing from 1 to 15 sub-folders, each containing 100 parts, 100 assemblies and 200 drawings, maximum.
So when we work on projects, there are components coming from I'd say hundreds of folders, and we've never seen a difference with having everything inside the same folder(We've done some pack and go to test)
Our PDM system relies on everything being in one folder and it's fine.
no need to have PDM to work with only one folder,
if you have numbering system for file name.
but, as i used PDM, there is some limit to Don't reproduce, because PDM work with the use of a Windows interface, etc...
for example for a network system (no local files on the computer) :
"Library" is sub divided with each folder for a brand, then sub-folder is needed
(example : IFM / Pressure Sensor)
"Library" contain also some "generic folders" to put generic part Inside, with sub-folders for categories
(example :
Fastening / Screw
Fastening / Nut
Piping ASME / Flange
Piping ASME / Welding )
"SW Setting" folder, with sub-folders to put all your setting files (make sure each SW point to these files)
"Projects" folder, it depend your numbering system, you can split in two ASM and PRT, or not.
you can create a "Generic Parts folder" for parts that can be used in différents projects.
but if your folder may contain more than 1000, 2000, or 3000 files (number can be doubled if each files have a drawing, or if you have some ASM with child-PRT)
it better to anticipate that, and split in sub-folders :
0001-1999
2000-3999
4000-5900
and for a remind, SolidWorks already have the "read-only management feature" since many years,
and we can work on the same project with many users, with the SolidWorks collaboration options.
No. They can be anyway.
You have to make sure it is the same "path" for everyone.