PDM/Works Project Naming Strategies

[rokahn]

What project and sub-project naming strategries have people found to work with PDM/Works?

I like the idea of a date code followed by descriptive text:
040326 donut glazer
indicates the project was created 26Mar2004 and is for a donut glazer.

Do others prefer an assembly number for projects? (using non-significant numbering, no doubt?). Do other people use subprojects or keep everything flat file?

Cheers,
Rocky

 

[ctopher]

We checkin in all SW files into one folder in PDMW. No need to have a date for the name, after a time you will not need it...PDM keeps track of the dates. We have 5 digit p/n's (part/assy) and model no's (assy) for our files.

 

[Standing]

We keep our drawings in several different folders called the project number, e.g. M131, W015100 or H165. Those folders are under a main folder labeled “Projects”. Remember you can put “Actual Name” and “Descriptive name” in the PDM, which are tied together. The first person putting the model into the PDM knows the Project it is related too. Then anyone knows what to charge his or her work too. When the drawing is released we move it to a released folder.

Bradley

 

[KBeitel]

We use the lifecycle management for document status. It is preliminary until it is released to production. At that time the project manager changes the status to Released. The documents are then all read only to everyone. We also have three other status (ECO, Superceded, & Obsolete) A document can not revert back to preliminary once it is released. I just goes through the ECO procedure and back to Released status as a new revision.

Take care & have fun!

Kevin

"Hell, there are no rules here -- we're trying to accomplish something." - Thomas A. Edison