Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Suggestions for quality data standards

2 views
Skip to first unread message

Kempf, Wayne R (MED)

unread,
Jan 25, 1999, 3:00:00 AM1/25/99
to
I am soon beginning a project to define practices regarding the
definition and collection of manufacturing process data. This will cover
such specifics as naming conventions(mnemonics) for database tables,
flat-file specifications for automated test equipment, revision control
of the software, etc.. Short of making this up, is anyone aware of a
publication or other documentation that attempts to define this sort of
stuff or does anyone have some experiences to share...??..

Thanks for your suggestions....

Wayne Kempf
GE Medical Systems
4855 W. Electric Ave.
Milwaukee, WI 53219
414-647-4318
Wayne...@med.ge.com

Patrick Perry

unread,
Jan 26, 1999, 3:00:00 AM1/26/99
to
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 ppe...@rand.com
===========================================

0 new messages