Systems engineering, systems thinking, and learning  a case study in space industry

Understanding Complex Systems Hubert Anton Moser Systems Engineering, Systems Thinking, and Learning A Case Study in Space Industry Tai ngay!!! Ban co the xoa dong chu nay!!! Understanding Complex Systems Founding Editor Prof Dr J.A Scott Kelso Center for Complex Systems & Brain Sciences Florida Atlantic University Boca Raton FL, USA E-mail: kelso@walt.ccs.fau.edu Editorial and Programme Advisory Board Dan Braha New England Complex Systems, Institute and University of Massachusetts, Dartmouth Péter Érdi Center for Complex Systems Studies, Kalamazoo College, USA and Hungarian Academy of Sciences, Budapest, Hungary Karl Friston Institute of Cognitive Neuroscience, University College London, London, UK Hermann Haken Center of Synergetics, University of Stuttgart, Stuttgart, Germany Viktor Jirsa Centre National de la Recherche Scientifique (CNRS), Université de la Méditerranée, Marseille, France Janusz Kacprzyk System Research, Polish Academy of Sciences, Warsaw, Poland Kunihiko Kaneko Research Center for Complex Systems Biology, The University of Tokyo, Tokyo, Japan Scott Kelso Center for Complex Systems and Brain Sciences, Florida Atlantic University, Boca Raton, USA Markus Kirkilionis Mathematics Institute and Centre for Complex Systems, University of Warwick, Coventry, UK Jürgen Kurths Potsdam Institute for Climate Impact Research (PIK), Potsdam, Germany Andrzej Nowak Department of Psychology, Warsaw University, Poland Linda Reichl Center for Complex Quantum Systems, University of Texas, Austin, USA Peter Schuster Theoretical Chemistry and Structural Biology, University of Vienna, Vienna, Austria Frank Schweitzer System Design, ETH Zürich, Zürich, Switzerland Didier Sornette Entrepreneurial Risk, ETH Zürich, Zürich, Switzerland For further volumes: http://www.springer.com/series/5394 Understanding Complex Systems Future scientific and technological developments in many fields will necessarily depend upon coming to grips with complex systems Such systems are complex in both their composition - typically many different kinds of components interacting simultaneously and nonlinearly with each other and their environments on multiple levels - and in the rich diversity of behavior of which they are capable The Springer Series in Understanding Complex Systems series (UCS) promotes new strategies and paradigms for understanding and realizing applications of complex systems research in a wide variety of fields and endeavors UCS is explicitly transdisciplinary It has three main goals: First, to elaborate the concepts, methods and tools of complex systems at all levels of description and in all scientific fields, especially newly emerging areas within the life, social, behavioral, economic, neuro and cognitive sciences (and derivatives thereof); second, to encourage novel applications of these ideas in various fields of engineering and computation such as robotics, nano-technology and informatics; third, to provide a single forum within which commonalities and differences in the workings of complex systems may be discerned, hence leading to deeper insight and understanding UCS will publish monographs, lecture notes and selected edited contributions aimed at communicating new findings to a large multidisciplinary audience Springer Complexity Springer Complexity is an interdisciplinary program publishing the best research and academic-level teaching on both fundamental and applied aspects of complex systems - cutting across all traditional disciplines of the natural and life sciences, engineering, economics, medicine, neuroscience, social and computer science Complex Systems are systems that comprise many interacting parts with the ability to generate a new quality of macroscopic collective behavior the manifestations of which are the spontaneous formation of distinctive temporal, spatial or functional structures Models of such systems can be successfully mapped onto quite diverse “real-life” situations like the climate, the coherent emission of light from lasers, chemical reaction-diffusion systems, biological cellular networks, the dynamics of stock markets and of the internet, earthquake statistics and prediction, freeway traffic, the human brain, or the formation of opinions in social systems, to name just some of the popular applications Although their scope and methodologies overlap somewhat, one can distinguish the following main concepts and tools: self-organization, nonlinear dynamics, synergetics, turbulence, dynamical systems, catastrophes, instabilities, stochastic processes, chaos, graphs and networks, cellular automata, adaptive systems, genetic algorithms and computational intelligence The two major book publication platforms of the Springer Complexity program are the monograph series “Understanding Complex Systems” focusing on the various applications of complexity, and the “Springer Series in Synergetics”, which is devoted to the quantitative theoretical and methodological foundations In addition to the books in these two core series, the program also incorporates individual titles ranging from textbooks to major reference works Hubert Anton Moser Systems Engineering, Systems Thinking, and Learning A Case Study in Space Industry ABC Hubert Anton Moser LuxSpace Sàrl Betzdorf Luxembourg ISSN 1860-0832 ISBN 978-3-319-03894-0 DOI 10.1007/978-3-319-03895-7 ISSN 1860-0840 (electronic) ISBN 978-3-319-03895-7 (eBook) Springer Cham Heidelberg New York Dordrecht London Library of Congress Control Number: 2013955727 c Springer International Publishing Switzerland 2014  This work is subject to copyright All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer Permissions for use may be obtained through RightsLink at the Copyright Clearance Center Violations are liable to prosecution under the respective Copyright Law The use of general descriptive names, registered names, trademarks, service marks, etc in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made The publisher makes no warranty, express or implied, with respect to the material contained herein Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com) Foreword Nowadays system development is multi-disciplinary Disciplinary knowledge, perspectives and thinking no longer suffice to develop systems in an efficient and effective way Development team members need to consider the system as a whole and work together closely across disciplinary boundaries, and systems engineers are required that know enough of the disciplines involved to ensure the total quality of the system Although the concepts of systems engineering and systems thinking have been around for several decades, an understanding of how developers actually work together across disciplinary boundaries and how they learn from each other, is still lacking What does it mean to think in terms of systems in the context of a highly integrated system in which partial, disciplinary solutions affect each other? How developers learn from each other in such a multi-disciplinary environment, i.e., how does systems thinking evolve? And most importantly, how can we improve this process: How can systems thinking be learned more effectively and efficiently given the fact that our education is essentially disciplinary? These questions are addressed in this book in a unique way as part of a PhD project executed within space systems industry To understand systems thinking, methods from educational and social sciences were used in an engineering context, multiple real development projects in industry were analyzed, and the analysis covered an extended period of time A multi-level analytical framework was developed, based on activity theory, allowing a detailed analysis of multidisciplinary interaction over time Short and long term mechanisms essential for learning to think in systems were identified, and finally, a strategy called WAVES (Work Activity for a Versatile Evolution of Systems engineering and thinking) was developed to improve the evolution of systems thinking This book is an excellent resource for researchers and practitioners interested in systems thinking and in solutions to support its evolution It not only provides an extensive overview of the developments in this field, but provides a unique and rich account of the practice of interaction between disciplines and learning across disciplinary boundaries Of particular interest for researchers is the developed analytical framework, which is applicable for the analysis of a wide variety of work activities in the context of engineering design and beyond Of particular interest for industry is the proposed human resource development strategy, WAVES, to improve the development process by improving the effectiveness of interaction between disciplines, the speed of systems thinking development, and the quality of boundary management When Hubert contacted me with his idea for a research project, we could not have anticipated the richness of the project and the results Not only did the VI Foreword research deal with multidisciplinarity in an engineering context, it was multidisciplinary in its own right, involving concepts, methods and strategies from yet other, non-engineering disciplines The dedicated involvement of LuxSpace and my colleague Gudrun Ziegler have been essential in achieving the depth and quality the topic requires Most of all, however, Hubert has to be credited with actually crossing boundaries, venturing into unfamiliar disciplines, bringing everything together, and providing the reader with a unique account of systems thinking and a solution for its improvement 20 October 2013 Luxembourg Lucienne Blessing Acknowledgements There are numerous people I would like to thank for their support during the endeavour of my doctoral dissertation, which is presented in this book I am not able to express my thanks to all of them I want to thank the members of my supervisory committee who facilitated this research project by their guidance and support From University of Luxembourg: Prof Dr.-Ing Lucienne Blessing (chair), Prof Dr Gudrun Ziegler, Prof Dr Charles Max, and Prof Dr Michel Marso From LuxSpace Dr Jeroen Buursink who supported me already before the start of this project when I started at LuxSpace and Florio Dalla Vedova who played a major role in the definition and initiation of this research project Furthermore, I would like to thank Prof Dr Alex Duffy from University of Strathclyde for his support and for being a member of my dissertation defence committee This work would not exist without the willingness of the study participants, in particular from LuxSpace and the DLR Institute of Space Systems It was a privilege to work with you Thanks for enabling the access to all the studies go to Jochen Harms (Managing Director of LuxSpace), Dr Oliver Romberg (Head of the Department System Analysis Space Segment in the DLR Institute of Space Systems), and Prof Dr André Balogh (International Space Science Institute, Headtutor of the Alpbach Summer School 2009) Special thanks go to the members of the research group DICA (Dynamics in Interaction, Communication, and Activity) who played an eminent role in my personal development and in this research project I would like to thank the members of the Engineering Design and Methodology research group of University of Luxembourg for their support and help I am also indebted to all the others who provided inspiration, help, support, and encouragement in various ways I am grateful to the National Research Fund of Luxembourg for funding this research project in a Public-Private Partnership of LuxSpace and University of Luxembourg under the AFR (Aides la Formation-Recherche) scheme I wish to thank Springer, in particular Dr Leontina Di Cecco, for providing me the opportunity and support to reach a broad audience My warmest thanks go to my family and friends who supported me during the challenging episodes and celebrated with me the delightful moments Villmols Merci Contents Foreword V Acknowledgements VII List of Acronyms XVII Part I: Introduction of the Research Project 1 Introduction 1.1 Motivation 1.2 Objectives and Research Question 1.3 Scope 1.4 Structure of the Book References 3 5 Systems Engineering and Learning 2.1 Systems Engineering 2.1.1 System 2.1.2 Characteristics of Systems Engineering 2.1.3 Systems Engineering within Multi-disciplinary Teams 2.1.4 Conclusion 2.2 Systems Thinking, Knowledge, and Interaction in Engineering 2.2.1 Systems Thinking 2.2.2 Knowledge 2.2.3 Interaction 2.2.4 Conclusion 2.3 Learning in Engineering 2.3.1 Definitions and Theories of Learning 2.3.2 Models of Learning 2.3.2.1 Circular Models of Learning 2.3.2.2 Non-circular Models of Learning 2.3.3 Conclusion 2.4 Space 2.4.1 Space Missions and Systems Engineering 11 11 11 13 21 22 22 23 28 30 33 33 33 36 36 40 42 42 42 X Contents 2.4.2 Multi-disciplinary Interaction in Space Systems Engineering 2.4.3 Microspace 2.4.4 Conclusion 2.5 Conclusion References Research Approach 3.1 Research Questions 3.2 Research Methodology, Strategy, Methods, and Plan 3.2.1 Research Methodology 3.2.2 Research Strategy and Methods 3.2.3 Research Plan 3.3 Data Collection and Processing Approach 3.3.1 Overview of Considered Data Collection Methods 3.3.2 Prioritisation of Data Collection Methods 3.3.3 Processing of Multiple Data Sources 3.4 Analysis Framework 3.4.1 Frameworks for Analysing Human Activity 3.4.1.1 Levels and Units of Analysis 3.4.1.2 Actor Network Theory 3.4.1.3 Distributed Cognition 3.4.1.4 Activity Theory 3.4.1.5 Comparison 3.4.2 Analysing Work with Activity Theory 3.4.2.1 Activity-Action-Operation 3.4.2.2 Models of Activity Systems 3.4.2.3 Five Principles of Activity Theory 3.4.2.4 Matrix of Situatedness 3.4.2.5 Conclusion 3.4.3 Systems Thinking Taxonomy for Analysing Change of Knowledge 3.4.3.1 Modification of the Taxonomy of Anderson et al (2001) 3.4.3.2 Combination with Different Fields of Knowledge 3.4.3.3 Conclusion 3.4.4 Analysis Framework 3.5 Analysis Approach 3.5.1 Activity-Theoretical Analysis 3.5.1.1 Description of the ASN 3.5.1.2 Identification of Contradictions 3.5.2 Theme-and-Key-Event Analysis 3.5.2.1 Key Event Identification and Link to Themes 45 47 48 48 49 59 59 60 60 61 62 63 64 65 67 68 68 68 68 69 70 70 71 71 72 74 75 77 77 78 80 81 81 82 83 83 84 86 86 312 Summary of Main Results, Contributions, and Outlook smallest scale contradictions Doubts in extra-disciplinary decisions are medium scale, and conflicts between different work standards and approaches are largescale contradictions The quality of the multi-disciplinary interaction is an essential factor influencing the practice of systems engineering and its evolution It is influenced by factors such as awareness of interactors' diversity and orientation towards extra-disciplinary interactors, differences in interactional responsiveness, and selection of interactional techniques Observed interactional techniques are referring to experience in remarks and narratives, physics basics, analogies and natural language The diversity of individual reference repertoires is an indirect measure of the level of systems thinking As learning in general, the evolution of systems thinking is regarded as change of knowledge This change is a vertical development within disciplines (fieldrelated and lifecycle-related disciplines) from immaturity to maturity (climbing the ladder of performance) Furthermore, it is a horizontal development, i.e beyond disciplinary boundaries (jumping from ladder to ladder) The horizontal development contains also relationships between the disciplines (platforms between ladders) The evolution of systems thinking, i.e learning of systems thinking, can be described as crisscross climbing in a scaffolding of ladders and platforms Change of factual, conceptual, and relational knowledge has been identified to occur within minutes, days, and years Change of procedural knowledge has been identified within days and years The short-term change can be identified as sudden insight within multi-disciplinary discussion The long-term change contains two types of continuous change The first type is a gradual movement from the periphery to the centre of extra-and intra-disciplinary fields of practice The second type is a cyclic process of activity systems, which starts with questioning current practices such as the work approach of engineering teams This second type of change is expansive learning How can the evolution of systems thinking in practice be improved? The answer to this second part of the main research question is: by tackling the factors, which influence the evolution of systems thinking This is the basis for the objectives of the developed support This support, the WAVES (Work Activity for a Versatile Evolution of Systems engineering and thinking) strategy, comprises two paths The first path, WAVES-intro focuses on the introduction of newcomers These are newcomers into professional life, to (space) industry, in a company, in a team, and newcomers to performing a task The second path, WAVES-conti, addresses the continuous development of systems thinking in practice It stresses the quality of multi-disciplinary interaction and discussion A combined implementation and evaluation approach was developed This approach is a step-wise implementation in iteration with the evaluation It starts within the S1 team of Company L before it is extended to entire Company L Afterwards it is planned to implement WAVES within systems engineering departments of two large organisations According to this approach, WAVES has been initially implemented in Company L The initial evaluation has shown positive results of the implemented instruments of the WAVES strategy 9.2 Contributions 9.2 313 Contributions The contributions of this research project are classified intro three different categories: contributions to research (see Section 9.2.1), contributions to engineering education (see Section 9.2.2), and contributions to industry (see Section 9.2.3) 9.2.1 Contributions to Research The two scientific objectives of the research project were: • • an improved understanding of learning in engineering teams who are developing (space) systems, and an improved understanding of systems thinking learning in practice The results of the research project contribute to an improved understanding of learning in high-technology environments This includes detailed insights into processes, which are often described as 'return of experience' and 'learning by experience.' The results provide insights into human activity where technology is used to design, develop, manufacture, test, and operate new technology as well as the change of this activity Findings from other research performed with grounded theory, phenomenology, and (experimental) work psychology are supported and stressed by the results In addition, this research project contributed to learning research in engineering by introducing an analysis framework based on activity theory This framework allows for studying human activity with and on technology on different temporal and organisational levels It has been shown that activity theory can be used to describe not only the man machine interaction but also the interaction of man creating machines Finally, this research project contributed to bridging the gap between latest social science research and engineering research by extending and crossing disciplinary boundaries 9.2.2 Contributions to Engineering Education The importance of multi-disciplinary interaction for the evolution of systems thinking has been identified The comparison of the four empirical studies showed that interactional techniques and multi-disciplinary quality of interaction are relevant for projects within industry as well as for student projects The diversity and size of the reference repertoire can be already increased in university Therefore, project work in multi-disciplinary teams is of high value for the individual students and future employees in industry This study shows benefits of participating in multi-disciplinary student projects such as working on educational satellites, cubesats, racing cars, robots, and rockets 314 9.2.3 Summary of Main Results, Contributions, and Outlook Contributions to Industry The practical objective of the research project was motivated by the question of how to best introduce newcomers into a small company This motivated the first objective of fostering learning of systems thinking in practice, which goes beyond the issue of optimum introduction of newcomers into a small company Based on the results of the empirical studies, the WAVES strategy has been developed, implemented, and partially evaluated Until now, these interventions are implemented in Company L and the implementation in Company D is foreseen WAVES has been developed as generic as possible to allow for its implementation in other companies and industries Although the major focus of WAVES is on fostering the learning of systems thinking, its application improves also the way of working, i.e the systems engineering approach 9.3 Outlook The research project has answered the research question and contributed to an improved understanding of the work activity within systems engineering teams in space industry From these insights, other interesting paths of continuation and open issues remain to be solved in future As this research project focuses on space industry and a limited number of cases, additional empirical studies should be performed to further analyse the evolution of systems thinking and learning in engineering practice The collected data allows for analyses with different research foci, e.g a quantitative analysis of the office records within S1 Coding by additional researchers would improve an analysis that focuses on quantitative aspects The rich data on interactions, allows for further investigation into critical interaction instances and into the use and role of interactional devices in work practice The link between critical interaction instances and extra-disciplinary questioning can be analysed in more detail The concept and definition of the multi-disciplinary quality of interaction can be reviewed, developed, and extended Reasons for the differences in preferred and required interactional responsiveness are an issue that should be studied in detail Such a study requires other research designs, e.g a survey of observations in different organisations and industries Another research strategy, such as longterm shadowing of multi-disciplinary teams and individuals would complement the results of this research project The implementation, evaluation, and refinement of the WAVES strategy should be continued within Company L The comprehensive evaluation of WAVES is a future project, which is of vital importance for following implementations Combined with this evaluation, WAVES should be implemented in other companies in the same sector and in other industry sectors Appendix A Overview of Data Collection Methods A A Overview of Data Co llection Methods Overview of Data Co llection Methods Research Journal A research journal is an ongoing chronologic document written by the researcher and containing different types of information Research journals, as other journals, reflect the perspective of the writer and cited perspectives of other informants It contains information, which complements data from project journals, descriptions of research setup, methods, and strategies as well as reflections of the researcher on the research project Research journals require a rather small effort from the researcher as they mainly serve as complementary data source and medium for reflections on the research project The categorisation and analysis of research journals is expected to require the largest effort for the researcher although this depends on the design, i.e if the journal is kept formally with a template and possibly in electronic form, or if it is in informal style written into a textbook Project Journals Similar to the research journal project journals are ongoing chronologic documents written by the researcher They contain project-specific information, i.e technical details of the system of the project and observations of the (participant) observer The observation information comprises field notes from the observations in different situations, such as desk, coffee corner, during lunch, and in meetings, and pointers to other data sources such as audio and video records, setups of audio and video recordings Technical details are related to the participant observers role in the corresponding project The researcher effort is a bit less than for the research journal as the journal is by definition focused on a single project Participant Journals Participant journals are project journals kept by participants Depending on the instructions, these journals can have a stringent template and formal character or completely free form providing the largest freedom for the writer Participant journals require a large effort of the participants This effort is comparable with 316 A Overview of Data Collection Methods the researcher effort for writing the research journals This data collection method requires the participants to document what they are doing and represents the exclusive perspective of the journal writer The researcher effort depends on the allowed freedom of the writers but can be generally compared to the other two aforementioned types of journals Audio and Video Records Audio and video records of observed activities are the least pre-filtered data collection method The data can be approached and revisited with different perspectives What is captured by the recorders can be observed with different foci several times as the main restriction on the data is viewpoint The viewpoint can be a stationary camera, which is not moved or refocused on pre-defined field of view, or it is a mobile camera that is switched on when the observer identifies something interesting during the observation This option causes already a preselection which might constrain the value of the data afterwards or ease the selection of critical situations as the observer's attention has been caught by something happening Audio and video records can be performed in regular formal and informal meetings, within offices of participants, and in the coffee corner to get insights into diverse work situations For a participant observer regular records represent the viewpoint of one member in a team, i.e only meetings are recorded in which the participant observer is involved The regular office records are made in the participant observer's office therefore show the interaction of the participant observer and the other participants located in the same office Writing the minutes of meeting and memos as a service in return increases the acceptance of the recording devices, which are quickly not noticed anymore by the participants in interaction Apart from acceptance, audio and video records require no participant effort Researcher effort is firstly to set access and permission to record Secondly, the records have to be listened/watched at least two times before selection and more in depth analysis Transcription of selected excerpts requires significant efforts Email Collection Collected emails provide insights into written interaction between co-located and distributed actors In addition to the email attachments such as pictures or other documents under discussion are accessible Only emails, from and addressed to (direct, cc, bcc) the participant observer in his role as thermo-mechanical specialist within the teams are stored Email collection does not require additional efforts for the participants and provides an authentic insight into written interaction between participants With common email exchange tools, which are implemented in standard office, software packages the search and tracking of email interaction can be performed with a small researcher effort A Overview of Data Collection Methods 317 Documentation Collection Documentation provides insight into formal documents such as technical drawings, minutes of meetings, requirements specifications, and statement of work These documents represent what is "frozen into documents" (Ehrlenspiel, 2007) In addition, informal documentation such as hand sketches written on napkins, paper, or whiteboards complement the set of information Documentation collection does not require an additional effort for the participants as the document creation is part of the observed work activity Documentation collection requires a higher researcher effort than email collection as the storage structure is mostly less organised and therefore a higher search and structuring approach is necessary Interviews Interviews require a small participant effort, as participants have to spend time to answer questions from the researcher Researcher effort depends on the structure of the interview A non-structured interview requires the highest analysis effort for the researcher but leaves the most freedom for the interviewee Physical Artefacts Physical artefacts such as prototypes, test models, and final products provide information on what and how has been realised in the end This information allows for analysing decided solutions and their implementation There is no participant effort and the researcher effort is small, mainly the documentation (e.g pictures) and its accurate localization in time Appendix B B Co mple mentary I nfor matio n o n S1 Complementary Information on S1 B Co mple mentary I nfor matio n o n S1 Table 68 List of S1 participants occurring in the analyses ID Information Aik Electronics engineer; started with ORCA2 and EAGLE2 projects; radiation analyst Aerospace engineer, specialisation on ground segment; L project manager of EAGLE2 Ben Cis Org Officer responsible for L Power Administrative team QAPA expert Ground segment Configuration manager of COLIBRI and EAGLE1 Finance and contracts QAPA manager Financial and contractual specialist; started with L ORCA2 and EAGLE2 projects Fid Aerospace engineer, specialisation on electroL mechanics; radio amateur Gab RF specialist; programme manager, project manager of L Payload; launcher EAGLE1 and COLIBRI; system architect of ORCA2; segment radio amateur Han Aerospace engineer, specialisations in L Structures and thermodynamics, structures and space systems mechanisms participant observer (author) Jan RF specialist sharing the tasks on the communication L subsystem with Pit Jas Geographer; Managing director of Company L L Director Jim Aerospace engineer, specialisation on software and L AOCS simulation Jon Aerospace engineer, specialisation on thermodynamics L Thermal, structures QAPA expert and space systems; ORCA2 project manager and mechanisms Kai Software and electronics engineer L OBDH Lam Project manager of ORCA1 L Pit RF specialist sharing the tasks on the communication L Communications subsystem with Jan; started with EAGLE2 and ORCA2 Etx1 Employee of electronics subcontractor involved in all ET five projects Orc1 Major contact person of ORCA2 customer O organisation Oth Other participants such as Ged (data service specialist of Company L), Nun (involved only in ORCA1), Mai (involved only in EAGLE1 and COLIBRI) 320 B Complementary Information on S1 Table 69 Chronology of project EAGLE1 within S1 T_S1 30 88 284 361 374 479 767-772 1158 1389 Start of project Start of researcher's involvement in project Environmental tests Design modifications because of electromagnetic issues Design modifications because of launcher interface issues Launch Commanded sleep for days of recovering Used to test ORCA2 ground stations Still operational Table 70 Chronology of project COLIBRI within S1 T_S1 37 61 73 85 248 302 326-405 424-430 438 466-474 494-527 541 737 848-858 863 920 1087 1088 1151 1389 Negotiation meeting with customer Kick off Start of work Schedule negotiation Start of researcher's involvement in project and start of detailed design stage Subcontracting integration of filter Design changes on filter and receiver unit L because of different simulation results Acceptance tests of filter and receiver units Delivery of receiver L and filter to customer and acceptance Computer unit retrieved from space for modifications Launch of receiver L, receiver N, and filter unit, waiting for re-launch of computer unit Successful long-term tests on ground involving filter and receiver L unit engineering models with the flight model of the computer unit Installation of antenna on ISS Switch on of receiver N Exchange of receiver N by receiver L; receiver L not functioning Rebuilt proposal for receiver unit L2 Inquiry board Retrieval of receiver unit L for error investigations Design modifications for receiver L2 Tests of retrieved receiver L flight model; full functioning according to specifications Launch and contractual situation for receiver L2 still pending B Complementary Information on S1 321 Table 71 Chronology of project ORCA1 within S1 T_S1 393 437 450 470 478 516 522 555 593 599 620 652 687 787 796 839 991 Top-level mission requirements Spacecraft concepts Introduction of concurrent engineering tool by project manager Green light from customer Team internal kick off Second team internal kick off Planned official kick off meeting postponed because of unexpected customer reasons Negotiation meeting Strategic decision to change team composition Kick Off meeting with customer Third team internal kick off Programmatic change also changing constraints on satellite architecture Midterm review; videoconference because of volcano cloud Second midterm review Strategic programme meeting including change of project management Researcher not anymore actively involved in project Final review meeting and closure of project Table 72 Chronology of project EAGLE2 within S1 T_S1 479 556 641 652 778 796 799 836-1138 1138 1146 1202 1270 1289 1290 1291 1292 Concept exploration start "Green light" for concept exploration Kick-off Programmatic change Vibration test of structure subsystem (option 1) Strategic programme meeting Upgrade meeting; free-flyer option (option 2) On hold; currently no launch opportunity because of ORCA2 priority and mass constraints; flat option (option 3) Distributed flat option (option 4) Earliest launch opportunity for spacecraft together with ORCA2 second spacecraft expected not before months Assembly and integration subcontracted to Company A because of ORCA2 priority In-official launch date shifted to one week earlier Vibration test of integrated system Discovery of major errors in assembly and integration Cancellation of launch opportunity On hold 322 B Complementary Information on S1 Table 73 Chronology of project ORCA2 within S1 T_S1 557 599 600 652 662 711 796 830 848 920+921 967+968 984 1082 1110 1142+1143 1146 1156 1195 1228 1228-1248 1254 1270 1277+1278 1285 1293 1317 1327 1327-1397 "Green light" from director to start with concept generation Start of negotiation with customer High level requirements and statement of work iteration meeting of the project team Programmatic change Kick-Off meeting Director: "we have a deal" Strategic programme meeting Go for purchase orders Contract signature Preliminary Design Review (telephone conference with customer) Critical Design Review, then start of production and deployment stage including assembly, integration and testing of first spacecraft Last spacecraft of customer quits service Test Readiness Review for first spacecraft Detailed design of second spacecraft for different launcher Vibration test of first spacecraft Earliest launch opportunity for second spacecraft together with EAGLE2 expected not before months Thermal vacuum test of first spacecraft Pre-Shipment Review and shipment of first spacecraft to launch base Launch of first spacecraft In orbit testing of first spacecraft Slight adaptations and integration of second spacecraft In-official launch date for second spacecraft shifted to one week earlier Vibration test of second satellite; ground station repair Pre-Shipment Review for second spacecraft Shipment of second spacecraft Launch of second spacecraft Contract closure Operations and support until project closure Appendix C C Co mpleme ntary I nformation o n S2 Complementary Information on S2 Table 74 Study participants within S2 ID Information Mod An engineer from the CEF core team, team leader and moderator role for the first time Sci1 A solar physicist from the scientific team who is continuously in the design session and responsible for the final mission proposal (as principal investigator); first time working in a concurrent design facility Sci2 A solar physicist from the scientific team who is participating from the first day to the afternoon of the third day; with a background in solar science instruments; first time working in a concurrent design facility Sci3 A solar physicist from the scientific team who is participating during the second day; first time working in a concurrent design facility Sci4 A solar physicist from the scientific team who is participating during the third and fourth day; first time working in a concurrent design facility Mis An engineer from the CEF core team Org Workplace Responsibility D1 Moderator Moderator Cos1 An engineer with degrees in electronics and finance Cos2 An engineer with degrees in technology management; supporting Cos1 Str1 A student doing an internship within the department Str2 An engineer who graduated approximately one year ago in this organisation (Company D) Str3 Student performing graduation thesis within the department; supporting Str1 and Str2 Thr An engineer specialised on thermodynamics Pwr An engineer from the CEF core team who worked as configuration officer within CEF1 but here as power officer; joined the session on the second day Aoc An engineer with focus on guidance, navigation and attitude control Prp Bachelor student performing graduation thesis within the department Com An engineer from the CEF core team who is normally doing the moderator role Dat Oth M System Science and System M Science Science M Science Science M Science Science D1 Mission D2 D1 Cost Cost Mission Analysis Cost Cost D1 D1 Structure Configuration D1 Structure Configuration Configuration Thermal Power D3 AOCS D1 Propulsion Attitude and Orbit Control Subsystem Propulsion D1 Communication D1 Configuration Thermal Power Communication and Ground System Student performing internship within the department; D4 Data Data Handling first time working in a concurrent design facility handling Subsystem (DHS) Other participants such as the head of department D1; visitors from other departments with interest in software issues; observers from DICA lab of University of Luxembourg Appendix D Basic Information on Themes D D Basic I nformation on The mes Basic informat ion on t hemes Table 75 Basic information on theme Interproject Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Interproject 29 (etic link) 1037 days EngS, AdminS, and CustS participants o Company L involved in different roles in all projects, as contractor and customer in EAGLE1 and EAGLE2, as subcontractor in COLIBRI, and as contractor in ORCA1 and ORCA2; o Company O as customer of ORCA2; o Company ET as subcontractor of EAGLE1, COLIBRI, EAGLE2, ORCA2; o Company ES as customer of COLIBRI and ORCA1; projects (EAGLE1, COLIBRI, EAGLE2, ORCA1, ORCA2) several project stages EAGLE1, COLIBRI, ORCA2 from concept exploration to operations and support, ORCA1 only concept exploration, EAGLE2 concept exploration to production and deployment Emails, documents (e.g lessons learned; ORCA2 statement of work, high level requirements), audio and video records of meetings, informal conversations with project manager of EAGLE2 and QAPA manager of Company L Macro Table 76 Basic information on theme Harness Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Harness (etic link) 20 days EngS team members Pit, Han, Jon, Jim, Gab, and Kai (all Company L staff), SubcoS team member (of Company G) o Company L involved in different roles in all projects, as contractor and customer in EAGLE1 and EAGLE2, as subcontractor in COLIBRI, and as contractor in ORCA1 and ORCA2; o Company G, involved as subcontractor for the harness manufacturing of ORCA2 project (ORCA2) in the detailed design stage Research journal, project journals, audio records of office talk, audio and video records of team meetings in ORCA2 Macro, meso (for d901 and d920) 326 D Basic Information on Themes Table 77 Basic information on theme Li-ion cells Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Li-ion cells (etic and emic links) 500 days EngS team members Aik, Jon, and Gab; AdminS team member Cib (all Company L staff) Company L involved in different roles in all projects, as contractor in ORCA2; project (ORCA2) in the detailed design stage Research journal, project journal, documentation, audio and video records of team meetings in ORCA2 Macro Table 78 Basic information on theme EMC & mechanics Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis EMC & mechanics (etic and emic links) 904 days EngS team members Han, Jon, Pit and Gab; AdminS team member Fid (all Company L staff) Company L involved in different roles in all projects, as contractor in ORCA2 projects: P3E (a small project of Han and Fid exploring concepts for electronics boxes) parallel to involvement in COLIBRI detailed development; and ORCA2 detailed development Research journal, project journal, documentation (change-log of CAD data), emails, physical artefacts audio records office work; Macro Table 79 Basic information on theme EMC & power Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis EMC & power (etic and emic links) 638 days EngS team members Han, Jon, Pit and Gab; AdminS team member Fid (all Company L staff); two different SubcoS team members o Company L involved in different roles in all projects, as contractor in ORCA2; o Company J as customer in another project but mainly as discussing partner on a problem that occurred in Company L and J o Company ET, as subcontractor involved in all three relevant projects experiencing the problem together with Company L o Company C, a subcontractor for the power subsystem being warned on an issue by Company L projects: EAGLE1 in the testing stage, EAGLE2 in the conceptual design stage and ORCA2 in the detailed development stage Research journal, project journal, documentation; emails; audio records of office work and meetings Macro D Basic Information on Themes 327 Table 80 Basic information on theme Sun sensor Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Sun sensor (emic link) 12 days EngS team members Han, Jon, Jim and Gab; Company L involved in different roles in all projects, as contractor in ORCA2 project: ORCA2 in operations and support of first spacecraft Research journal, project journal, documentation; emails; audio records of office work and meetings Macro Table 81 Basic information on theme Accommodation Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Accommodation (emic link) 352 days EngS team members Han, Jon; SubcoS team member etx1 o Company L involved in different roles in all projects, as contractor in ORCA2; o Company ET, as subcontractor involved in all three relevant projects experiencing the problem together with Company L projects: COLIBRI assembly stage (within production and deployment) and EAGLE2 conceptual design Research journal, project journal, documentation; emails; audio records of a meeting Macro Table 82 Basic information on theme Stiffness Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Stiffness (etic and emic links) 124 days EngS team members Gab, Han, Jon, Jim Company L involved in different roles in all projects, as contractor and customer in EAGLE1 and EAGLE2, as subcontractor in COLIBRI, and as contractor in ORCA1 and ORCA2 projects: EAGLE2 in production and deployment stage; ORCA2 in detailed design stage Research journal, project journals, audio and video records of office talk Macro; meso (for d892 and d899) 328 D Basic Information on Themes Table 83 Basic information on theme Radio Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Radio 29 (etic link) 964 days EngS team members Pit, Han, Jon, Jim, Gab, Ben, and Jan (all Company L staff) Company L involved in different roles in all projects, as contractor and customer in EAGLE1 and EAGLE2, as subcontractor in COLIBRI, and as contractor in ORCA1 and ORCA2 projects (EAGLE1, EAGLE2, ORCA2) from concept exploration to production and deployment research journal, project journals, audio records of office talk, audio and video records of EAGLE2 and ORCA2 team meetings Macro; meso for d794 Table 84 Basic information on theme AOCS-fuel Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis AOCS-fuel 10 (etic link) days CengS team members Aoc, Mod, Mis, Str1, Str2, Str3, Pwr (Company D staff); SciS team members Sci1, Sci2, Sci3 (Company M staff) o Company D (same institutional organisation as in PS2 (CEF1 project) but partially different participants as in PS2, acting as contractor) o Company M (institutional organisation as customer) o Company ES (addressee of proposal, sponsoring organisation) project: CEFX in concept exploration stage (preparation of project proposal) Research journal, project journals, audio and video records within S2 + interviews of participants performed during and after the study Macro, meso (for d2_1154), micro (for d2_1149) Table 85 Basic information on theme Occulter Theme Number of key events Duration of theme Participants (appearing in the analysis) Involved organisations and their roles Projects and project stages Data Level of analysis Occulter 17 (etic and emic links) days Aoc, Mis, Mod, Sci1, Sci2, Sci3, Str1, Str2, Str3, Pwr o Company D (same institutional organisation as in PS2 (CEF1 project) but partially different participants as in PS2, acting as contractor) o Company M (institutional organisation as customer) o Company ES (institutional organisation acting as envisaged sponsoring organisation) project: CEFX in concept exploration stage (preparation of project proposal) Diverse excerpts of video-records and interviews from S2 Macro