Investigation of change in specifications during a product's lifecycle

Mohd Nizam Bin Sudin, Saeema Ahmed

    Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review

    252 Downloads (Pure)


    Engineering changes (ECs) constitutes a normal part of a product’s lifecycle. This paper aims to understand why changes are made to a product’s specification during a product’s lifecycle including understanding: the distribution of changes; the drivers for changes; how changes are discovered; which design attributes likely be changed; the initiation of change and how change in specifications are described. For this purpose, document analysis for a complex product has been carried out. In total, 271 reports of change request of an aero-engine that were associated to change in specifications were examined qualitative and quantitatively. Several patterns in change in specifications were quantified and observed. The findings showed that the majority of changes were found in the manufacture/build and testing phase and most of these changes were described in terms of need and solution regardless of how the request was initiated. The study showed that experience plays a vital role in discovering the need to change a complex product
    Original languageEnglish
    Title of host publicationProceedings of the 17th International Conference on Engineering Design : ICED'09
    Publication date2009
    ISBN (Print)978-1-904-670124
    Publication statusPublished - 2009
    Event17th International Conference on Engineering Design - Stanford, United States
    Duration: 24 Aug 200927 Aug 2009
    Conference number: 17


    Conference17th International Conference on Engineering Design
    Country/TerritoryUnited States
    Internet address


    • product's lifecycle
    • change in specification
    • change request
    • engineering change


    Dive into the research topics of 'Investigation of change in specifications during a product's lifecycle'. Together they form a unique fingerprint.

    Cite this