Knowledge integration for problem solving in the development of complex aerospace systems

Abstract

The development of complex products requires widespread knowledge interactions among a significant number of individuals and teams designing numerous interrelated components. Increasing product complexity typically leads to a corresponding increase in the types and sources of knowledge that need to be tapped during development, and a common strategy for managing product complexity is to outsource parts and components to external suppliers. As a result, the knowledge required for development is increasingly specialized and distributed across multiple boundaries spanning large-scale organizational networks, thus requiring the subsequent integration of this knowledge in order to accomplish the development task. A framework for knowledge integration in the development of complex systems in a large-scale organizational context is proposed in this thesis using an extensive review of the pertinent literature. The framework consists of the main channels, strategies, practices and mechanisms most commonly used to transfer, share and apply knowledge in the course of complex technical problem solving. The framework is progressively refined using empirical data collected through several rounds of interviews and a questionnaire instrument administered across three major aircraft programs in the defense aerospace industry. We find that knowledge integration in routine problem solving situations is most efficiently and effectively accomplished through extensive transfer and sharing of codified information using formal mechanisms such as information systems, while knowledge integration for major non-routine troubleshooting events requires extensive integration of individual expertise and know-how through both formal and informal advice sharing as well as direct assistance across internal and external organizational boundaries.

(cont.) A principal contribution of this research is in demonstrating how different characteristics of the engineering artifact defined in terms of product complexity, architecture and technology newness, and different aspects of problem solving including problem type and novelty, drive the knowledge integration process and the organizational system. We conclude that permeability of cross-program boundaries, direct relationships with functional groups and rich tacit knowledge flow from suppliers are critical for countering rampant firefighting in complex product development.