Skip to main content
Log in

Capturing and reusing knowledge in engineering change management: A case of automobile development

  • Published:
Information Systems Frontiers Aims and scope Submit manuscript

Abstract

The development of complex products, such as automobiles, involves engineering changes that frequently require redesigning or altering the products. Although it has been found that efficient management of knowledge and collaboration in engineering changes is crucial for the success of new product development, extant systems for engineering changes focus mainly on storing documents related to the engineering changes or simply automating the approval processes, while the knowledge that is generated from collaboration and decision-making processes may not be captured and managed easily. This consequently limits the use of the systems by the participants in engineering change processes. This paper describes a model for knowledge management and collaboration in engineering change processes, and based on the model, builds a prototype system that demonstrates the model’s strengths. We studied a major Korean automobile company to analyze the automobile industry’s unique requirements regarding engineering changes. We also developed domain ontologies from the case to facilitate knowledge sharing in the design process. For achieving efficient retrieval and reuse of past engineering changes, we used a case-based reasoning (CBR) with a concept-based similarity measure.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13
Fig. 14

Similar content being viewed by others

References

  • Abecker, A., Bernardi, A., Hinkelmann, K., Kühn, O., & Sintek, M. (2000). Context-aware, proactive delivery of task-specific information: The knowmore project. Information Systems Frontiers, 2(3/4), 253–276.

    Article  Google Scholar 

  • Adler, P. S., & Clark, K. B. (1991). Behind the learning curve: A sketch of the learning process. Management Science, 37(3), 267–281.

    Google Scholar 

  • Agostini, A., De Michelis, G., & Grasso, M. A. (1997). Rethinking CSCW systems: The architecture of Milano. In Proceedings of the Fifth European Conference on Computer Supported Cooperative Work, pp. 33–48.

  • Ahn H. J., Lee, H. J., Cho, K. H., & Park, S. J. (2005). Utilizing knowledge context in virtual collaborative work. Decision Support Systems, 39, 563–582.

    Article  Google Scholar 

  • Alavi, M., & Leidner, D. (2001). Knowledge management and knowledge management systems: Conceptual foundations and research issues. MIS Quarterly, 25(1), 107–136.

    Article  Google Scholar 

  • Bergmann, R., & Schaaf, M. (2003). Structural case-based reasoning and ontology-based knowledge management: A perfect match? Journal of Universal Computer Science, 9(7), 608–626.

    Google Scholar 

  • Berners-Lee, T., Hendler, J., & Lassila, O. (2001). The semantic web. Scientific American; May.

  • Broekstra, J., Kampman, A., & Harmelen, F. (2003). Sesame: A generic architecture for storing and querying RDF and RDF schema. In J. Davies, D. Fensel, & F. Harmelen (Eds.), Towards the semantic web: Ontology-driven knowledge management (pp. 71–89), West Sussex: Wiley.

    Google Scholar 

  • Chen, C., & Huang, C. (2001). A multiple criteria evaluation of high-tech industries for the science-based industrial park in Taiwan. Information & Management, 41, 839–851.

    Article  Google Scholar 

  • Clark K. B., & Fujimoto, T. (1991). Product development performance: Strategy, organization, and management in the world auto industry. Boston: Harvard Business School Press.

    Google Scholar 

  • Clark, K. B., & Wheelright, S. C. (1993). Managing new product and process development: Text and cases. New York: Free Press.

    Google Scholar 

  • Conklin, J., & Begeman, M. (1988). gIBIS: A hypertext tool for exploratory policy discussion. ACM Transactions on Office Information Systems, 6(4), 303–331.

    Article  Google Scholar 

  • Decker, S., Mitra, P., & Melnik, S. (2000). Framework for the semantic web—an RDF tutorial. IEEE Internet Computing, 4(6), 68–73.

    Article  Google Scholar 

  • Delteil, A., Faron-Zucker, C., & Dieng, R. (2001). Learning ontologies from RDF annotations. In Proceedings of the Second Workshop on Ontology Learning, p. 38.

  • De Michelis, G., & Grasso, M. A. (1994). Situating conversation within the language/action perspective: The Milan Conversation Model. In Proceedings of the 5th Conference on CSCW, pp. 89–100.

  • Golebiowska, J., Dieng-Kuntz, R., Corby, O., & Mousseau, D. (2001). Building and exploiting ontologies for an automobile project memory. In Proceedings of K-CAP’01, Victoria, October.

  • Grant, R. (1996). Toward a knowledge-based theory of the firm. Strategic Management Journal, 17, 109–122.

    Article  Google Scholar 

  • Grant, R. (1997). The knowledge-based view of the firm: Implications for management practice. Long Range Planning, 30(3), 450–454.

    Article  Google Scholar 

  • Huang, G. Q., & Mak, K. L. (1998). Computer aids for engineering change control. Journal of Materials Processing Technology, 76, 187–191.

    Article  Google Scholar 

  • Huang, G. Q., Yee, W. Y., & Mak, K. L. (2001). Development of a web-based system for engineering change management. Robotics and Computer Integrated Manufacturing, 17, 255–267.

    Article  Google Scholar 

  • Huang, G. Q., Yee, W. Y., & Mak, K. L. (2003). Current practice of engineering change management in Hong Kong manufacturing industries. Journal of Materials Processing Technology, 139, 481–487.

    Article  Google Scholar 

  • Jarvenpaa, S. L., & Leidner, D. E. (1999). Communication and trust in global virtual teams. Organization Science, 10(6), 791–815.

    Article  Google Scholar 

  • Karvounarakis, G., Magkanaraki, A., Alexaki, S., Christophides, V., Plexousakis, D., Scholl, M., et al. (2003). Querying the semantic web with RQL. Computer Networks and ISDN Systems, 42(5), 617–640.

    Google Scholar 

  • Kolodner, J. (1993). Case-based reasoning. San Francisco, CA: Morgan Kaufmann Publishers.

    Google Scholar 

  • Loch, C. H., & Terwiesch, C. (1996). Accelerating the process of engineering change orders: Capacity and congestion effects. Journal of Product Innovation Management, 16, 145–159.

    Article  Google Scholar 

  • Lorenzo, M. M. G., & Perez, R. E. B. (1997). A model and its different application to case-based reasoning. Knowledge-Based Systems, 9(7), 465–473.

    Article  Google Scholar 

  • Maus, H. (2001). Workflow context as a means for intelligent information support. In Akman, V. et al (Eds.), CONTEXT 2001, LNAI, Vol. 2116, pp. 261–274.

  • May, A., Carter, C., & Joyner, S. (2000). Virtual team working in the European automotive industry: User requirements and a case study approach. Human Factors and Ergonomics in Manufacturing, 10(3), 273–289.

    Article  Google Scholar 

  • May, A., & Carter, C. (2001). A case study of virtual team working in the European automotive industry. International Journal of Industrial Ergonomics, 27, 171–186.

    Article  Google Scholar 

  • Melnik, S. (2000). Representing UML in RDF. Available at http://www-db.stanford.edu/~melnik/rdf/uml/.

  • Melink, S., & Decker, S. (2000). A layered approach to information modeling and interoperability on the web. In Proceedings of ECDL’00 Workshop on the Semantic Web, Lisbon, Portugal, September.

  • Monplaisir, L. (1999). An integrated CSCW architecture for integrated product/process design and development. Robotics and Computer-Integrated Manufacturing, 15, 145–153.

    Article  Google Scholar 

  • Nonaka, I., & Konno, N. (1999). The concept of “Ba”: Building a foundation for knowledge creation. California Management Review, 40(3), 40–54.

    Google Scholar 

  • Numata, J., & Taura, T. (1996). A case study: A network system for knowledge amplification in the product development process. IEEE Transactions on Engineering Management, 43(4), 356–367.

    Article  Google Scholar 

  • Pikosz, P., & Malmqvist, J. (1998). A comparative study of engineering change management in three Swedish engineering companies. In Proceedings of DETC’98, Atlanta, GA, USA.

  • Ramesh, B., & Tiwana, A. (1999). Supporting collaborative process knowledge management in New Product Development Teams. Decision Support Systems, 27, 213–235.

    Article  Google Scholar 

  • RDF. Resource Description Framework, 1999. Available at http://www.w3.org/TR/rec-edf-syntax/.

  • RDFS. RDF Schema, 2000. Available at http://www.w3.org/TR/rdf-schema/.

  • Resnik, P. (1999). Semantic similarity in a taxonomy: An information-based measure and its application to problems of ambiguity in natural language. Journal of Artificial Intelligence Research, 11, 95–130.

    Google Scholar 

  • Saaty, T. L. (1980). The analytic hierarchy process. New York: McGraw-Hill.

    Google Scholar 

  • Salton, G., & McGill, M. (1983). Introduction to Modern Information Retrieval. New York: McGraw-Hill.

    Google Scholar 

  • Terwiesch, C., & Loch, C. H. (1999). Managing the process of engineering change orders: The case of the climate control system in automobile development. Journal of Product Innovation Management, 16, 160–172.

    Article  Google Scholar 

  • Wong, S., & Burton, R. M. (2000). Virtual teams: What are their characteristics, and impact on team performance? Computational and Mathematical Organization Theory, 6, 339–360.

    Article  Google Scholar 

  • Wright, I. C. (1997). A review of research into engineering change management: Implications for product design. Design Studies, 18, 33–42.

    Article  Google Scholar 

  • Yoo, S. B., & Kim, Y. (2002). Web-based knowledge management for sharing product data in virtual enterprises. International Journal of Production Economics, 75, 173–183.

    Article  Google Scholar 

Download references

Acknowledgment

The authors acknowledge the help of the many interviewees at the host Korean automobile company in conducting the case study and research survey.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Hong Joo Lee.

Appendices

Appendix A. Brief introduction to the AHP method used to calculate the weights of the ontologies

We have O 1, O 2, ..., O n as the criterion for which weight values should be calculated. Using the n criterion, an (n × n) matrix A can be defined where element a ij of A is the experts’ preference of O i over O j when retrieving relevant engineering change cases. It is also assumed that the elements of A adhere to the following rules:

  1. Rule 1.

    If a ij  = α, then a ji  = 1/α, α ≠ 0.

  2. Rule 2.

    If O i is judged to be of equal relative importance as O j , then a ij  = 1, a ji  = 1; in particular, a ii  = 1 for all i.

The final objective is to calculate the weight value w i for each ontology O i . Using the above matrix, w i can be calculated using the following formula:

$$ w_{i} = \frac{1} {{\lambda _{{\max }} }}{\sum\limits_{j = 1}^n {a_{{ij}} w_{j} } }\,{\left( {i = 1,2,...,n} \right)}, $$

where λmax is the maximum eigenvalue of matrix A (Saaty, 1980).

A set of pair-wise comparisons of ontologies was collected from the experts in the target company using questionnaires. Matrix A was obtained by integrating the experts’ preferences as follows:

 

Component

Problem

Process

Product

Solution

Component

1

5.593

6.804

3.476

1.197

Problem

0.179

1

6.082

2.924

1.71

Process

0.147

0.164

1

0.281

0.147

Product

0.288

0.342

3.557

1

0.43

Solution

0.836

0.585

6.804

2.327

1

Consequently, we obtained the normalized weights of the ontologies:

$$ {\left\{ {w_{c} ,w_{{pb}} ,w_{{pc}} ,w_{{pd}} ,w_{s} } \right\}} = {\left\{ {0.447,0.21,0.035,0.094,0.214} \right\}} $$

The terms w c , w pb , w pc , w pd , and w s are the weights of the component, problem, process, product, and solution ontologies, respectively.

Appendix B. Definition of the similarity measure

1.1 B.1 Definition of ontologies

Each ontology O i is defined as a tree of concept nodes, C ki (k = 1, 2, ...). (Note that when designating a specific ontology, we use the terms O pd , O pb , O pc , O c , and O s for the product, problem, process, component, and solution ontologies, respectively.)

1.2 B.2 Definition of an engineering change case

An engineering change case E j is defined as the set of concepts that correspond to the concepts in the ontologies, i.e., \(E_{j} = {\left\{ {a_{{kj}} \left| {a_{{kj}} } \right. \in O_{{pd}} \cup O_{{pb}} \cup O_{{pc}} \cup O_{c} \cup O_{s} \;{\text{and }}k\; = 1,\,\,2,...,\;{\text{number of concepts in the case}}} \right\}}\).

1.3 B.3 Definition of the similarity between two concepts in a single ontology

The similarity between two concepts c pi and c qi in O i is defined as (Resnik, 1999)

$$ sim{\left( {c_{{pi}} ,c_{{qi}} } \right)} = - \log \frac{{N{\left( {{\left\{ {E_{j} \left| {c_{{ri}} \in E_{j} } \right.} \right\}}} \right)}}} {{N{\left( U \right)}}}, $$

where c ri is the closest common parent (CCP) to both c pi and c qi and U is the entire set of engineering change cases in the case base. N({E j |c ri  ∈ E j }) is the number of engineering change cases that belong to concept c ri . The CCP represents a node in O I , which is the parent or ancestor of both of the two given concepts located closest to it. (Note that the numerator in the log term can become much smaller in large ontologies with greater depth and more concepts. For this reason, it is expected that the average value of the similarity is proportional to the size of an ontology.) For example, if we calculate a similarity value between the ‘Screwing’ and ‘Fitting’ concepts in the problem ontology in Fig. 6, the parents of the ‘Screwing’ concept are ‘Fixing,’ ‘Assembly,’ and ‘Problem,’ and the parents of the ‘Fitting’ concept are ‘Installation,’ ‘Assembly,’ and ‘Problem.’ Therefore, the common parents in this case are ‘Assembly’ and ‘Problem’ and the CCP is ‘Assembly’ because ‘Assembly’ is closer to ‘Screwing’ and ‘Fitting’ than ‘Problem.’

1.4 B.4 Definition of the compensation factor for reducing size effects (Inverse Concept Frequency)

The compensation factor f i for O i is defined as

$$ f_{i} = \log \frac{{{\sum\limits_m {N{\left( {O_{m} } \right)}} }}} {{N{\left( {O_{i} } \right)}}}. $$

(Note that this measure is similar to the inverse document frequency (IDF) measure widely used in information retrieval [Salton & McGill, 1983].)

1.5 B.5 Definition of the similarity between two engineering change cases

The similarity between two cases, E 1 and E 2, is defined as

$$ Sim{\left( {E_{1} ,E_{2} } \right)} = \frac{{{\sum\limits_i {w_{i} \times f_{i} \times sim_{i} {\left( {c_{{1i}} ,c_{{2i}} } \right)}} }}} {{{\sum\limits_i {w_{i} } }}}, $$

where c 1i and c 2i are the concepts of E 1 and E 2 , respectively, defined in the O i dimension, c 1 ∈ E 1 , c 2i  ∈ E 2 , c 1i  ∈ O i , and c 2i  ∈ O i .

Rights and permissions

Reprints and permissions

About this article

Cite this article

Lee, H.J., Ahn, H.J., Kim, J.W. et al. Capturing and reusing knowledge in engineering change management: A case of automobile development. Inf Syst Front 8, 375–394 (2006). https://doi.org/10.1007/s10796-006-9009-0

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10796-006-9009-0

Keywords

Navigation