Best File Structure to Use
Best File Structure to Use
(OP)
I've got about 1500 hours of SWX under my belt but have had no training. I've brought it into two tiny companies as the only user and haven't had the benefit of either seeing an efficient deployment nor working as part of a team to develop one.
I've been struggling with finding the best way to handle my file structure. I once tried creating separate folders for .DWG, .SLDPRT, .SLDDRW, & .SLDASM files. I also tried putting standard buyout parts in different categorized folders but keeping organic design files in one folder. I now just dump all my SWX files into one folder and my ACAD files into another (still haven't figured out how best to deal with .PDF copies of my SWX or ACAD files).
I'd love to hear some details about how others do it and the pros and cons they've experienced.
We have a standard design but have only built two systems (which consist of several pieces of discrete equipment connected by a pneumatic conveying system). We will be modifying the equipment design as we learn more about our technology. Also, each deployment will require some customization according to the customer's specifications.
FWIW, I don't currently use PDMWorks but I do have the software (I'm running '05 Office Pro with a subscription). Having poked around it a bit has left me a bit apprehensive about how best to deploy it.
I've been struggling with finding the best way to handle my file structure. I once tried creating separate folders for .DWG, .SLDPRT, .SLDDRW, & .SLDASM files. I also tried putting standard buyout parts in different categorized folders but keeping organic design files in one folder. I now just dump all my SWX files into one folder and my ACAD files into another (still haven't figured out how best to deal with .PDF copies of my SWX or ACAD files).
I'd love to hear some details about how others do it and the pros and cons they've experienced.
We have a standard design but have only built two systems (which consist of several pieces of discrete equipment connected by a pneumatic conveying system). We will be modifying the equipment design as we learn more about our technology. Also, each deployment will require some customization according to the customer's specifications.
FWIW, I don't currently use PDMWorks but I do have the software (I'm running '05 Office Pro with a subscription). Having poked around it a bit has left me a bit apprehensive about how best to deploy it.
--------------------
Bring back the HP-15
www.hp15c.org
--------------------






RE: Best File Structure to Use
We thought about file structure before implementing PDMWorks for a moment and then realized that we really didn't need to address the issue. Parts get integrated with the assemblies that they are used in and searching is so easy within PdMWorks that it really doesn't matter.
I remember seeing suggestions (maybe matt lombards URL) about how to structure, but it wasn't really a big issue.
PDMWorks does a great job handling the files.
dsgnr1
¿)
To get the best from these forums read FAQ731-376 before posting
RE: Best File Structure to Use
This system works for us because we only use a 5 digit non-significant part number, and do not use a revision in the file name unless it is an old revision. Current revs only use 5 digits. Part models and related drawings have the same file name. Assemblies and related drawings use the same file name.
We have over 7 product lines, many with at least 4-5 different configurations (some as many as 8), and we do not use any PDM systems.
"I think there is a world market for maybe five computers."
Thomas Watson, chairman of IBM, 1943.
Have you read FAQ731-376 to make the best use of Eng-Tips Forums?
RE: Best File Structure to Use
We have top level folders of Released, Details, Obsolete, & Prototype. (the prototype folder is split by designer who splits by project or as they see fit.)
The Released, Details, and Obsolete folders have subfolders of R000, R100, etc., D000, D100 etc. where all parts are filed by part number ie. (22222.617 where 22222 is a numerical sequence and the .617 is an indicator of the part family - in this case a valve spool)
All three also contain folders for the product assemblies filed by model code.
The details folder is for modeled parts/assemblies where new drawings have not yet been created.
The released folder also contians the drawings, pdf's, another incidentals we need to create from time to time.
Detached drawings are created and stored in the obsolete folder like 22222.617NoRev or 22222.617RevA etc. before the current released part is revised.
Remember...
"If you don't use your head,
your going to have to use your feet."
RE: Best File Structure to Use
Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716
RE: Best File Structure to Use
RE: Best File Structure to Use
--------------------
Bring back the HP-15
www.hp15c.org
--------------------
RE: Best File Structure to Use
Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716
RE: Best File Structure to Use
And I agree - no duplication of files - always a bad idea.
RE: Best File Structure to Use
RE: Best File Structure to Use
If you have disciplined and concientious users you can get by using the collaboration options in Solidworks and sharing stuff over the network, but PDMWorks (for it's cost) is a much better way to go.
RE: Best File Structure to Use