PDM file Structure???? what are you doing... 1

[brudje]

I am working as PDM admin at my company. We are struggling with setting up a good vault file structure for our product line consisting of parts , toplevel assemblies , subassemblies and the like.
What we have in place works, but it has its shortfallls. We have set it up with individual parts residing in descriptive folders, and subasseblies and assemblies listed in descriptive folders by type and then finally by company we are making for.
Prior to any type of PDM,we just had everything by company folder, and we ran into the problem of having the same files in multiple locations. PDM is going to help prevent this type of structure...
I was wondering how other users out there have set up their vaults...

Thanks in advance for the help

 

[Standing]

We put all of your new drawings, part and assemblies into your own project folder. When the drawing is released we move it and related files to one released folder.

Bradley

 

[pdybeck]

brudje,

"Prior to any type of PDM,we just had everything by company folder, and we ran into the problem of having the same files in multiple locations. PDM is going to help prevent this type of structure..."

PDMWorks only allows a file to exist once in the vault, so you could arrange projects by company within PDMWorks. If a file (part) is used by many assemblies in different projects (folders), then it shows as a link in all but one of the assemblies to prevent from multiple copies of the file existing in the vault. Now, if you are talking about working outside the vault, then thats a different story. IMO it would be very nice if SolidWorks and or PDMWorks had a development/work area where a direct save could be made just like any other network drive, but a file could exist only once. This would prevent users from getting confused about which copy of the part is being worked on outside the vault. I am also working as PDMAdmin for my company and have broken out projects to capture products that we sell and manufacture. I also have projects for core technologies that we use in all our products - like sub-products in a way. I also have a folder called Support where all the hardware that we use is located in logical subfolders like nuts, washers, screws, sealants, adhesive sealants. This makes it easy for anyone to browse for hardware, and then drag and drop into their design. It works for us - so far at least.

Pete

 

[ctopher]

We have all in one PDMW project folder. A separate project folder for Tooling. You can have it set up any way that fits your company. Any way you do it, PDMW will manage it for you.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 2005 SP0.1

 

[Standing]

I remember that we had multiple models (of the same part) when we started. What we did, to get things into the PDM fast was to take the largest assembly and dump that in. For us that was a big mistake. That assembly was not using the latest parts that we really wanted. I wish we had put in only part models we knew were good to go.

Bradley

 

[rgrayclamps]

Since SolidWorks is a true "Object Orientated" program, it is best to use sequential numbers for part models and another ones for assembly models. We abandoned our traditional numbering system (part numbers had meaning!) and use this kind sequetial numbers, like social security numbers. We check in models (part or assembly) into Vault one by one through revision control of each object (a part or an assembly). Everything is very smooth.

Alex

 

[ctopher]

PDMWorks will automatically list your files sequentially. I usually don't check in parts/assys until the dwgs are finished, then each is checked in together, or bulk check in the entire project.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 2005 SP0.1

 

[Standing]

I agree with Chris. I like to keep the revisions the same if I can easily do it. That is why I check in parts/assemblies when the drawings are finished, and then each is checked in together. This is not a requirement.

Bradley