Best File Structure to Use

[Beggar]

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.

--------------------
Bring back the HP-15

http://www.hp15c.org

--------------------

 

[dsgnr1]

Beggar,
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

 

[MadMango]

We have Project folders where all SW file types (including DWG, PDFs, etc) are kept in a single folder during the development (R&D) stage. When a project is finalized and gets released to production, the models and files are copied to our Production folders on another network location (drive). This area has 36 subfolders, named 0-9 and A-Z. We have a separate drive location for standard hardware (nuts, bolts, bearings, etc).

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.

[green]"I think there is a world market for maybe five computers."[/green]
Thomas Watson, chairman of IBM, 1943.
Have you read faq731-376 to make the best use of Eng-Tips Forums?

 

[meintsi]

We do not use a PDM system here. We have many, many product lines and an absolutly massive number of possible configurations for each and have never had a problem. A PDM system might suit us well, but the cost is absolutly not worth it to us when "common sense" and well trained users is all that is required. (Nightly tape backup has saved us a couple of times though)

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...
[navy]"If you don't use your head,[/navy]
[navy]your going to have to use your feet."[/navy]

 

[ctopher]

Our system was used similar as MadMango and Meintsi, but didn't work well for us very long. With approx 10 people trying to work on dwgs and assy's, it was a nightmare. We all now use PDMWorks.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716

 

[PDMAdmin]

We went from "shared" files on the network to a PDM vault, and that made a huge difference. Our folders are arranged by project, and each project is divided into sub-folders that correspond to a particular section of the product. That has worked well for us, but ultimately it will depend on what your user base prefers.

 

[Beggar]

If you have an assembly that's used on multiple projects, does its model file get copied over and over into each project folder?

--------------------
Bring back the HP-15

http://www.hp15c.org

--------------------

 

[ctopher]

I suggest stay with only one copy of each file, anywhere. Multiple copies can cause grief.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716

 

[TateJ]

All our files are on the network drives. We have folders (We call it our LIBRARY) for standard parts & assemblies. Our "LIBRARY" is segregated for parts, assemblies & drawings (simply stated). Anything that is project specific goes in the project folder. The main thing is to decide on a strategy - then stick with it. Stop experimenting with different strategies. You'll chase your tail & get dizzy.

And I agree - no duplication of files - always a bad idea.

SolidWorks 2005 SP04.0 SpaceBall 400 FLX Microsoft Intellimouse Explorer Windows 2000 Professional Lava Lamp

 

[TateJ]

Also... You can copy an assembly to multiple locations (projects) & it's component files will not be duplicated. That's basic assembly theory 101. If you're having trouble understanding that - then you may need to work visit the tutorials again. It's too easy to over-look a basic idea & then get lost with the advanced stuff. Just ask me about algebra - I know.

SolidWorks 2005 SP04.0, SpaceBall 400 FLX, Microsoft Intellimouse Explorer, Windows 2000 Professional & a Lava Lamp

 

[engAlright]

If you have more than a few users, PDM of any kind is a great way to manage files - the more users, the more essential it becomes. That way you know you are working with the latest copy of a document, you can re-trace your steps in the design and it's much easier to share parts amongst the workgroup.

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.

 

[TateJ]

Without a PDM solution - having no way to secure your electronic documents - you live & die by your paper copies. So no matter how much $ they spend on the PCs & software... Now matter how many neat things we can make these boxes do... We're really just fancy board-drafters... Well, maybe we're faster at making these pretty drawings. But we're still just making paper drawings. Then agan... maybe I'm a little frusterated. Is it quitting time yet?

SolidWorks 2005 SP04.0, SpaceBall 400 FLX, Microsoft Intellimouse Explorer, Windows 2000 Professional & a Lava Lamp