PDM/Works Project Naming Strategies
PDM/Works Project Naming Strategies
(OP)
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
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






RE: PDM/Works Project Naming Strategies
RE: PDM/Works Project Naming Strategies
Bradley
RE: PDM/Works Project Naming Strategies
Take care & have fun!
Kevin
"Hell, there are no rules here -- we're trying to accomplish something." - Thomas A. Edison