Browse Prior Art Database

Automatic Construction of an Engineering Change

IP.com Disclosure Number: IPCOM000107770D
Original Publication Date: 1992-Mar-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 3 page(s) / 119K

Publishing Venue

IBM

Related People

Folmar, DM: AUTHOR [+5]

Abstract

The Engineering Change (EC) process controls all changes to products being manufactured within the enterprise. With the focus on reduced cycle time, integrated computer systems are a must. Disclosed is an integrated system for the automatic construction of an EC's contents using object-oriented techniques and a rules-based database.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Automatic Construction of an Engineering Change

       The Engineering Change (EC) process controls all changes
to products being manufactured within the enterprise.  With the focus
on reduced cycle time, integrated computer systems are a must.
Disclosed is an integrated system for the automatic construction of
an EC's contents using object-oriented techniques and a rules-based
database.

      The basic concepts in the automatic construction of an
engineering change are implemented via several objects associated
with the EC object.  These include the following objects which are
described further in the following paragraphs:
      o  Deliverable object,
      o  Default deliverable object,
      o  EC Review object,
      o  Default EC Review object, and
      o  Rules-based object.

      One of the primary duties of the EC coordinator is to determine
what items and what data within the item must be changed with this
EC.  Along with each piece of item data or deliverable, the
coordinator must include who is going to complete the work and by
what date.  The deliverable object allows the coordinator to assign
an EC task to a particular individual and track its completion.

      However, with many items under a single EC, identifying all the
necessary pieces of item data that need be changed is still
cumbersome.  The default deliverable object allows the coordinator to
predefine canned deliverables for easy identification and inclusion
into the EC.  Additionally, the coordinator can establish rules in
the rules object which allow default deliverables to be automatically
picked and placed on an EC when items are placed on this EC.  Thus,
when an item with particular characteristics is created under an EC,
a standard set of deliverables complete with the proper technical
owner is established for that item.

      Another key task of the coordinator is to determine what set of
formal evaluations or reviews the EC and its completed data must go
through.  Typically, ECs of a particular type must go through a set
of enterprise-defined reviews.  With the EC review object the
coordinator can establish these reviews, the list of reviewers, and
track the completion of the on-line evaluation of the complete EC
package.

      Additionally, by defining rules in the rules-based object, a
set of default reviews can be automatically brought in and
established for an EC at the time of creating the EC.

      The rules-based object contains data which facilitate the
automatic creation of the EC's contents.  Rules are established based
on specific values of one object (say, an EC) and affect the creation
of other objects at some key event (like creating the EC).  For
example, say an enterprise has found that the cost of makin...