Managing Design Knowledge Managing Exchanging Knowledge Underlying Aerospace

Managing Design Knowledge Managing & Exchanging Knowledge Underlying Aerospace Engineering Design Decisions Scottie-Beth Fleming & Dr. Amy R. Pritchett June 15, 2015 ASEE’s 122 nd Annual Conference & Exposition NSF, grant number DGE-0644493 1

Aerospace Engineering Design Engineering design is a structured approach to developing, validating, and implementing complex systems + Multiple points of interaction + Overlapping, interdependent, and often conflicting design parameters Pahl et al, 2007; Cross, 2006; DAU, 2001 Images from http: //wonderfulengineering. com/ http: //www. geaviation. com/ http: //www. airbus. com/ http: //www. boeing. com/

Aerospace Engineering Design Industry has expressed a need for engineering graduates to use effective approaches to system design, integration, and synthesis Dutson et al. , 1997 Images from http: //wonderfulengineering. com/ http: //www. geaviation. com/ http: //www. airbus. com/ http: //www. boeing. com/

Aerospace Engineering Design Education Capstone design can cultivate students’ skills to + Use understanding of the engineering design process to examine the full context of the design problem [ABET student outcome (c)] + Collaborate on multidisciplinary teams [ABET student outcome (d)] + Communicate effectively [ABET student outcome (g)] Senior Design Capstone Course ABET, 2014; Woods et al, 2000; Paretti, 2008 Images from http: //wonderfulengineering. com/ http: //www. geaviation. com/ http: //www. airbus. com/ http: //www. boeing. com/

Aerospace Engineering Design Education However, novice aerospace engineers are often unable to + integrate multidisciplinary design considerations + translate preferences, constraints, and decisions to others also engaging in the design process Examine the role of managing and exchanging knowledge underlying aerospace engineering design Seniordecisions. Design Capstone Course Ahmed et al, 2004; Daly et al. , 2001; Fleming & Coso, 2014; Gertler, 2014; Griffin, 2005; NTSB, 2013; Oakley et al, 2004; Richey, 2005 Images from http: //wonderfulengineering. com/ http: //www. geaviation. com/ http: //www. airbus. com/ http: //www. boeing. com/

Scholarship of Integration + “giving meaning to isolated facts, putting them in perspective…making connections across the disciplines, placing the specialties in larger context, illuminating data in a revealing way, often educating nonspecialists too. ” (Boyer, 1990) Frame the design context Aerospace Engineering Design Process Identify critical behaviors Literature from Org Behavior, I/O Psych, Education, Design Strategies for managing and exchanging design knowledge Boyer, 1990

AE Design Context: Multi. Team System Testing and Evaluation Chief Engineer Operations & Manufacturing System Integration Technical Components Certification Concept 7

Shared Knowledge + “Common ground" among collaborators + Used to survey and respond to environment + Engineering design teams are not always aware of interdisciplinary considerations Clark & Schaefer, 1981; Cramton, 2001; Keysar, Barr, Balin, & Paek, 1998 Image from http: //automotive-seo. net/getting-your-content-shared//

Boeing 787 Case “In retrospect, we may apply tighter test criteria or seek to understand test criteria a little more” ~Mike Sennett Operations & Manufacturing Testing and Evaluation Chief Engineer System Integration Engineering designers must recognize the Technical Components considerations and constraints of disciplines outside their own expertise Certification Electrical Systems Concept Li. Ion Batteries Special Conditions NTSB, 2013 9

Goal Alignment + Design teams share at least one high -level goal + More detailed goals and design requirements should remain consistent with the high-level goals. + However, detailed design preferences and specific disciplinebased goals do not necessarily align Griffin, 2005; Marks et al 2001; Mathieu et al, 2001; Mesmer-Magnus & De. Church, 2009; Richey, 2005 Image from http: //atomictoasters. com/2013/07/design-priority/

C-5 and F-111 Cases C-5 Galaxy F-111 Aardvark Design teams should specify and prioritize goals early in the design process, and continuously monitor progress toward mission accomplishment High-level design goal explicitly defined and understood at the start of the design process Griffin, 2005; Richey, 2005 Conflicting high-level design goals caused the Navy to terminate the F-111 B variant Images from http: //www. af. mil/ http: //aviationheritagepark. com/ 11

Information Sharing the collective exchange and utilization of knowledge and expertise previously held by a limited number of group members Awareness of the distribution of information Understanding of the approaches for sharing information Understanding of how information can be integrated into design decisions. Bunderson & Sutcliff, 2002; Jehn & Shah, 1997; Mesmer-Magnus & Dechurch, 2009; Stasser & Titus, 1985; Miranda & Saunders, 2003 Image from http: //electricarchaeologist. files. wordpress. com/2011/03/blogarch. png http: //nextforge. com/? p=1913 http: //www. theberkeleygraduate. com/2014/02/in-defense-of-the-interdiscipline/

AE Design Team Strategies Rolls-Royce Design Teams Boeing 787 Dreamliner Develop a collaborative strategy which incorporates information about team resources, member expertise, critical design events, and the changing nature of the design environment Informal communications across working groups allows for timely task feedback and reflection Baird et al, 2000; NTSB, 2013 Chief project engineer for 787 recognized communication and collaboration failures Images from http: //www. af. mil/ 13

Strategies for managing & exchanging design decisions Shared Knowledge Engineering designers must recognize the considerations and constraints of disciplines outside their own expertise Goal Alignment Design teams should specify and prioritize goals early in the design process, and continuously monitor progress toward mission accomplishment Information Sharing Designers should develop a collaborative strategy which incorporates information about team resources, member expertise, critical design events, and the changing nature of the design environment Workshop for Managing & Exchanging Design Decisions Problem Scoping & Design Integration

Workshop Wrapper: Systems Engineering Top-down comprehensive, iterative and recursive problem solving process, applied sequentially through all stages of development Decompose problem into manageable subsystems Synthesize interdependent design parameters into integrated solution Image copied from Systems Engineering Fundamentals (2001) Defense Acquisition University Press, 2001; van Lamsweerde & Letier, 2000; NASA 2007

Problem Scoping + + + System Decomposition Stakeholder Identification Information Gathering Mission Decomposition Requirements Definition

Design Integration + Jig-Saw, Role-Playing Activity + Participants become “experts” on one system component + System experts redistribute to multidisciplinary teams § Negotiate high-level design objectives and constraints § Identify critical design metrics of effectiveness

Final Thoughts Aerospace Engineering Design Process Strategies for Knowledge Management & Exchange Intervention Design

Thank you! Questions? This work was sponsored by the NSF, grant number DGE-0644493 19 19

20 20