🚀 go-pugleaf

In my previous professional life I worked for a major manufacturer.  We had
to manage drawings and programs.  The naming convention that was utilized
there was "made up".  Granted, a lot of the pieces where logical extensions
of the actual work (i.e. a production bearing drawing had the prefix pb).

As far as revisioning is concerned, when the part or program where put into
production that revision became locked.  If any changes (even as minor as a
misspelled word in the title block of a drawing) were needed, the drawing
or program had to be revised.  In speaking of parts, if the "revision"
changed form, fit, or function, the part could not be revised; a new part
needed to be generated.

As general guidelines:
Pick a naming convention that conveys a general meeting to the users.
Remain constancy through the naming.
The revision as part of the module name is convenient, but not absolutely
necessary.
Investigate software (document management, project management, product data
management) to help control releases and revision; and retrieval of
information.
Define specific instances when a program/data module can be revised; and
when a new program/data module should be created.

Hope this helps.
===========================================
Patrick L. Perry                   PDM Implementation Engineer
Rand Worldwide                        Phone 770-806-9200
3675 Crestwood Parkway, Suite 400  Fax 770-806-9277
Duluth, GA 30136                     Email pperry@rand.com
===========================================