0
TECHNICAL NOTES

A Product Feature Evolution Validation Model for Engineering Change Management

[+] Author and Article Information
Nadjib Bouikni, Alain Desrochers

Department of Mechanical Engineering, University of Sherbrooke, 2500 Boulevard de l’Université, Sherbrooke, Quebec, J1H 2R1, Canada

Louis Rivest

Department of Automated Production Engineering, Ecole de technologie superieure, 1100 Notre-Dame West, Montreal, H3C1K3, Canada

J. Comput. Inf. Sci. Eng 6(2), 188-195 (Feb 10, 2006) (8 pages) doi:10.1115/1.2194909 History: Received March 31, 2004; Revised February 10, 2006

Product design integrates several disciplines in a concurrent engineering (CE) environment. Each one of these disciplines has a specific point of view on the product being developed. While each discipline exerts its own expertise and methods on the definition of the product and its related processes, information must remain consistent for all disciplines and through the evolution of the product definition. This paper proposes a product feature evolution validation (PFEV) model that aims at controlling the information flow needed to support a product definition evolution (PDE) while insuring its validation by all disciplines involved. The model applies both to the product design and modification phases, i.e., before and after releasing its definition. The PFEV model thus supports CE and enables managing the product feature evolution throughout the product life cycle. The PFEV model defines an exchange protocol between the disciplines in order to preserve the consistency of the numerical model, which includes the complete numerical information characterizing the product. The model addresses two qualities of an information system: dispatching relevant PDE information to appropriate disciplines and providing this information according to specific views. This is achieved by centralizing the product numerical model and by exploiting the product’s features rather than managing product model as black boxes. Links between features are formalized in a shared product features table that is used to dynamically identify all disciplines impacted by a product feature evolution (PFE). A PFE is also characterized by its potential impact, detrimental or beneficial, on every discipline previously identified as impacted. In the case of a detrimental impact, the discipline is asked to validate the evolution. If the impact is beneficial, the discipline is simply notified about the evolution. Specific views are generated for the impacted disciplines based on feature filtering and adaptation mechanisms.

FIGURES IN THIS ARTICLE
<>
Copyright © 2006 by American Society of Mechanical Engineers
Your Session has timed out. Please sign back in to continue.

References

Figures

Grahic Jump Location
Figure 1

Example for the generation of views for three disciplines

Grahic Jump Location
Figure 2

Mechanisms for the generation of the views

Grahic Jump Location
Figure 3

Adaptation of implicit information; example

Grahic Jump Location
Figure 4

Filtering of explicit information; example

Grahic Jump Location
Figure 6

Interfaces of the PFEV model application

Grahic Jump Location
Figure 7

Description of the “shoes storage furniture”

Tables

Errata

Discussions

Some tools below are only available to our subscribers or users with an online account.

Related Content

Customize your page view by dragging and repositioning the boxes below.

Related Journal Articles
Related eBook Content
Topic Collections

Sorry! You do not have access to this content. For assistance or to subscribe, please contact us:

  • TELEPHONE: 1-800-843-2763 (Toll-free in the USA)
  • EMAIL: asmedigitalcollection@asme.org
Sign In