The Application of SE Methodologies to the design and development of a Space Telescope

Transcription

1 SWISSED15 The Application of SE Methodologies to the design and development of a Space Telescope Mike Johnson CSEP, Systems Engineering Teamleader at RUAG Space

2 Overview / Aim / Agenda Aim: That you and I learn something useful. Agenda Mike and Mars histories etc CaSSIS - Colour and Stereo Surface imaging System Understanding of SE Application of SE to CaSSIS design, development and verification Results and analyses Final thought Questions and acknowledgements

3 Curriculum Vitae: Mike Johnson CSEP

4 A brief History of Space Missions to Mars 1992 Mars Observer US Failure Lost prior to Mars arrival 1996 Mars Global Surv. US Success More images than all Mars Missions 1996 Mars 96 USSR Failure Launch vehicle failure 1996 Mars Pathfinder US Success Technology experiment lasting 5 times 1998 Nozomi Japan Failure No orbit insertion; fuel problems 1998 Mars Climate Orbiter US Failure Lost on arrival 1999 Mars Polar Lander US Failure Lost on arrival 1999 Deep Space 2 US Failure Lost on arrival (carried on Mars Polar Lander) 2001 Mars Odyssey US Success High resolution images of Mars 2003 Mars Express Orb. ESA Both Orbiter imaging Mars in detail and lander lost 2003 MER Spirit US Success Operating lifetime of more than 15 times 2003 MER- Opportunity US Success Operating lifetime of more than 2005 MRO US Success Returned more than 26 terabits of 2007 Phoenix Mars Lander US Sucesss Landed in North Polar Regions 2012 Mars MSL Curiosity US Success Landed large RTG powered rover at Gale Crater 4

5 Agenda Mike and Mars histories etc CaSSIS - Colour and Stereo Surface imaging System Understanding of SE Application of SE to CaSSIS design, development and verification Results and analyses Final thought Questions and acknowledgements

6 ExoMars 2016 and 2018 Scientific investigations: Search for signs of past and present life on Mars; Investigate how the water and geochemical environment varies; and Investigate Martian atmospheric trace gases and their sources. 6

7 ExoMars 2016: The CaSSIS Instrument University of Bern Prime Investigator CaSSIS will characterise sites identified as potential sources of trace gases investigate processes which may contribute to atmospheric gases. be used to certify potential landing sites by characterising local slopes, rocks and other possible hazards. 7

8 CaSSIS Telescope Assembly RUAG Space prime Concept developed Challenge: To design, develop, manufacture and verify in circa 17 months. First imaging telescope for RUAG Space. Re-use from Optical Communications telescopes mandatory to meet schedule. Typical manufacturing of mirrors takes 9-12 months. 8

9 Agenda Mike and Mars histories etc CaSSIS - Colour and Stereo Surface imaging System Understanding of SE Application of SE to CaSSIS design, development and verification Results and analyses Final thought Questions and acknowledgements

10 What is my understanding of SE? At the end of the day, responsible for technical performance of the delivered solution. Ensuring the flow of the right information to the right people at the right time. Often being the middle man Trying to find the simplest solutions Understanding the overall technical problem that needs solving.. Planning, Tracking and configuring design, development and verification Doing the jobs no one else does, chasing up simple things injecting energy into the development. 10

11 The Iron Triangle It was clear from day 1, Schedule was the King. 11

12 Inspiration from the INCOSE H/book System Life cycle Processes Overview per ISO/IEC 15288:2008; Source: INCOSE SE Handbook

13 Agenda Mike and Mars histories etc CaSSIS - Colour and Stereo Surface imaging System Understanding of SE Application of SE to CaSSIS design, development and verification Results and analyses Final thought Questions and acknowledgements

14 1. Stakeholder Analysis 1/3 Heuristic : Get to know your Stakeholders SE Input: Begin with Stakeholder management CUSTOMER Dedication, passion and pride Based in academia RUAG Team Multi-cultural (Swiss, Italien, French, German, British!!) Multi-disciplinary approach; «Very controlled design» versus «anything can change» Ages, experiences and ambitions Sub-contractors / Suppliers Me?? History of delivering on time, schedule and budget? Strengths and weaknesses let s be honest!! 14

15 1. Stakeholder Analysis 2/3 Thermal Engineers Mechanical Engineers Electronic Engineers Optical Engineers 15

16 1. Stakeholder Analysis 3/3 M&P Engineers Product Assurance Engineers MAIT Engineers Project Management 16

17 2. Reqs Analysis Heuristic : Find out what the Customer needs SE Input: emphasis put on the importance of the requirements What happened Requirements under varying degrees of configuration control Reqs matured quickly, deviations were quickly identified and addressed Identified and held discussions on key requirements took design away from what the «Customer wants» Key technical requirements identified: Optical performance, Mass, volume, Op. and non-op. temperatures, power Implemented MAIT requirements Reflections: Good expectation management 17

18 3. Architectural Design Heuristic : Apply simplicity and control interfaces SE Input: re-use in-house technology and interfaces What happened: Electrical design needed to be simplified after growing out of control! All disciplines worked for common goals Output: Telescope Assembly System Electrical I/F Well known interfaces Simple architecture Telescope Assembly Thermal Sub-system Electrical I/F Telescope Assembly Grounding Sub-system Mechanical I/F Electrical I/F Thermal I/F Telescope & Rotation Assembly Structural Sub- System Telescope Structure Mirror mounts Baffles Internal Baffle External Baffle Thermal Control Sub- System Telescope Assembly MLI (TBD) Power Control Board (TBD) Wiring and harnesses (TBD) Temperature sensors (TBD) Heaters (TBD) Optical Sub-System Mirror M1 Coating M1 Mirror M2 Coating M2 Mirror M3 GSE Transport Container Handling Jigs (TBD) Protective RBF Cover (TBD) Telescope Assembly GSE Mechanical I/F Thermal I/F Mechanical I/F Telescope Assembly Structural Sub-System Electrical I/F Thermal I/F Mechanical I/F Optical I/F FPA TAC External Mechanical Interfaces Telescope to Rotation Drive I/F Telescope to FPA I/F Mirror M4 Coating M3 Coating M4 Thermal I/F Mechanical I/F Electrical I/F Thermal I/F S/C thermal environment Telescope Assembly Optical subsystem 18 RUAG Space Thermal I/F Space / Surface of Mars thermal environment

19 4. Implementation Heuristic : No news is not good news! SE Input: Effective flow of information What happened: Regular meetings with Customer reviewing design progress and resolving identified issues Regular system meetings; strong focus on only making meetings when the right people and right information were available Technical Risk Management - it s a way of life! Regular risk reviews within team, many risk mitigations actioned. Tracking of design Reflections: Don t be afraid of change, but have respect for its consequeces. Issues and risks regularly openly discussed 19

20 5. Integration Heuristic : Hardware does not tell lies SE Inputs: MAIT team well connected with the development team What happened: There was no blame culture Implemented a good British value: Reflections: Don t be afraid of the hardware. Don t let your speciality dominate remember to be there for the System! Control the team s automatic panic responses. 20

21 6. Verification Heuristic : Plan verification from Day 1 SE Inputs: Verification discussed throughout whole project What happened Wrote requirements in a verifiable way, agreed verification methods from early on. MAIT on the project from day 1 Understand the facilities and the job of the facilities workers Looked at similar projects and identified what caused successes and failures.. Often simple things: Holiday planning and Information flow Regular checks that team members knew their roles and responsibilities in the upcoming activities. Reflections: Verification campaign met its schedule Simpler Customer reviews achieved 21

22 7. Tailoring Heuristic : Processes are the roadmap, not the destination SE Inputs: Monitor useful level of SE What happened: Not everything needed to be formal (eg. In DOORS) Adapted SE processes and methodologies to the project, eg. there are always many considerations when applying an SE tool, eg Tradeoff You don t solve different problems the same way! Reflections: Benefits reaped from Stakeholder analyses. Systems Engineering needs to become a state of mind. 22

23 8. Decision Making 15 Minutes to review and test it SE Inputs: Ensure all voices are listened to team trust grew as project developed. What happened: Heuristic : Listen to Einstein! Albert Einstein, once asked to put up a schedule to solve a complex and important problem in one hour, answered: 40 Minutes to analyze the situation 5 Minutes to find solution and decide Not forced into making quick poorly informed decisions. Problem solving process implemented ( Systems Engineering, Methodik und Praxis ), especially for tradeoffs. Reflections: remember, once you have discovered a problem: Do not keep quiet about it. Consider cultures. Share the problem with team members, SE, PM, 23

24 Agenda Mike and Mars histories etc CaSSIS - Colour and Stereo Surface imaging System Understanding of SE Application of SE to CaSSIS design, development and verification Results and analyses Final thought Questions and acknowledgements

25 Results and analysis How to analyse SE effectiveness from results?... Eric Honor gives us a measure Reduced variation in Budget, Schedule and Scope. The application of SE should improve the prediction of Schedule, Technical performance and Cost (Iron Triangle!!) Schedule: Planned: 17months delivered 21 months Technical performance: several deviations from the specification in order to meet the schedule, but no show stoppers! Cost: Within planned costs. Comparison to similar projects quite difficult due to lack of available data but correlation to iron triangle looks good 25

26 Results and analysis CaSSIS Hubble JWST 26

27 Thanks to all the team! See daily updates: 28

28 Final thought In my humble opionion A Systems Engineer is like a musical conductor, when they are doing very well it looks like they are not needed. When they try to do too much themselves it all sounds awful!!!. You decide!!! 29

29 30

30 Acknowledgements RUAG Space AG and The University of Bern INCOSE SE Handbook Prof. Anton Ivanov Prof. W. Deanzer, Systems Engineering, Methodik und Praxis. Several Images from: NASA/JPL/University of Arizona