Systems engineering and measurement. what do they have to do with one another? Geilson Loureiro,

Transcription

1 Systems engineering and measurement what do they have to do with one another? Geilson Loureiro, November 29th, 2012, São Paulo, SP

2 INCOSE OVERVIEW The International Council on Systems Engineering (INCOSE) is a not-for-profit membership organization founded in 1990 to develop and disseminate the interdisciplinary principles and practices that enable the realization of successful systems. MISSION: Share, promote and advance the best of systems engineering from across the globe for the benefit of humanity and the planet. 2

3 INCOSE Main Benefits Network with over 7,000 members in 40 countries. Quarterly e-publication, INSIGHT. Electronic version of Systems Engineering, the Journal of INCOSE. Collaborate with experts and practitioners. Access to i-pub, the INCOSE publications database (over 2,000 papers). Exclusive access to INCOSE Connect (collaborative space for Members). Annual International Symposia. Local Chapter Operations. INCOSE Representation on Standards Committees. JOIN INCOSE! CHOOSE INCOSE BRASIL AS YOUR CHAPTER! 3

4 CONTENTS Systems Engineering and Metrics Systems Engineering Process Laboratory of Integration and Testing Metrics along the systems engineering process Broader scope for modern SE Conclusion 4

5 SYSTEMS ENGINEERING and METRICS Systems engineering is an inter and multidisciplinary, collaborative, engineering approach to derive, evolve and verify a system solution balanced over its life cycle in order to provide satisfaction to stakeholders. IEEE 1220 A metric is a composite of quantifiable process and product attributes that communicate important information about quality, process, technology, product and/or resources. INCOSE Metrics Guidebook for Integrated Systems and Product Development 5

6 SYSTEMS ENGINEERING PROCESS OVERVIEW Stk s needs, requirements and approval Validation Detailed Design Unit Test/ Acceptance Baseline: firm and approved reference for all teams to proceed. Requirements Baseline (SRR) Architecture Baseline (PDR) Design Baseline (CDR) Design Baseline (Release for Testing) Product Baseline CM Configuration management Controlled Changes: impact analysis, approval, control

7 LABORATORY OF INTEGRATION AND TESTING

8 LIT S FACILITIES

9 LIT s Testing Hall Class

10 LIT s Integration Hall Class

11 LIT s industrial customers

12 SYSTEMS ENGINEERING PROCESS OVERVIEW Stk s needs, requirements and approval Validation Detailed Design Unit Test/ Acceptance Baseline: firm and approved reference for all teams to proceed. Requirements Baseline (SRR) Architecture Baseline (PDR) Design Baseline (CDR) Design Baseline (Release for Testing) Product Baseline CM Configuration management Controlled Changes: impact analysis, approval, control

13 STAKEHOLDER NEEDS ANALYSIS AND METRICS Statement of Need Goal_1 Goal_2 Goal_3 Objective_2.1 Objective_2.2 Stakeholders who control [process or scenario] e.g. Safety Inspectors concerns Metric_2.1.1 Measure_1.1.2,1 Measure_ Measures of effectiveness Qualification strategy Set of attributes that describe the achievement of the objective How to verify Stakeholders who are sources of Inputs e.g. Crew concerns Aircraft in [life cycle process or scenario] e.g Aircraft in preventive maintainance concerns concerns Stakeholders who are mechanisms or who provide mechanisms e.g. Maintainance technicians Stakeholders who are destination of outputs, e.g. Aircraft operators Inputs Controls IDEF0 Outputs Mechanisms

14 SYSTEM REQUIREMENTS AND METRICS Conditions Air taffic control pressure lift dragging Heat_from Atmosphere Wind speed Turbulence level Exhaust gases Heat_to Continuous values Cargo Cargo_weight Experience Training level Maturity Health Pilot Discrete values Co-pilot commands Flight info Flight reaction System at Perform flight operations scenario Functions damping Other_crew_members movement Passengers weight entertainment Performance

15 REQUIREMENTS WRITING AND METRICS The <system> shall <function> not less than <quantity> <object> while <operational condition>. Example: The communications system shall sustain telephone contact with not less than 10 callers while in the absence of external power. The <system> shall <function> <object> every <performance> <units>. Example: The coffee machine shall produce a hot drink every 10 seconds. Source: Hull et al, 2005

16 System analysis for architectural design Refinament ARCHITECTURAL DESIGN AND METRICS System analysis Assess technology alternatives Allocate functions to system elements Partition and aggregate system functions aiming at allocatable functions Select system design elements Perform functional analysis of system design elements aiming at defining physical interfaces Identify system design element alternatives Deploy down requirements to functions and system design elements Define physical interfaces Select preferred physical architecture (s) Compose functional architecture (s) Deploy requirements to lower level functions Compose preferred physical architecture (s) Allocate elements in the functional architecture to system design elements and physical interfaces in the physical architecture Allocate requirements to system design elements and physical interfaces in the physical architecture Synthesis Solution Functional Analysis Arch Selection

17 PRODUCT VS SYSTEM AN EXAMPLE Exploration Enterprise Exploration Value Delivery System Scientific - Economic - Security Exploration System Flight Ground Systems Systems Hardware Software CEV Humans Hardware Software Humans Implementing and Building Training and Skill Development Maintaining and Supplying 17

18 TRADITIONAL CONOPS 18

19 NECESSARY SCOPE FOR MISSION SUCCESS Microgravity Microgravidade Experiments Experimentos Trajectory Trajetória Reentry Reentrada Launching Lançamento navegadores C3 Recuperação comunidades locais navegadores Recovery Resgate comunidades Rescue locais navegadores Ground Solo Logistics Logística Data acquisition Aquisição de dados AIT 19

20 SE for product Scenarios Mission Life cycle processes and organization Scenarios within the scope of the development effort Product stk Concerns Product functional context Product implementation context Organization implementation context Organization functional context Organization stk Concerns MoEs External interface reqs External interface reqs MoEs Modes Modes Stk requirements System requirements Stk requirements Product functional structure Product functional behaviour Hazard and risk analysis Product functional attributes Product implementation architecture interconnects Product implementation architecture flows Product implementation attributes Organization functional structure Organization functional behaviour Hazard and risk analysis Organization functional attributes Organization implementation architecture interconnects Organization implementation architecture flows Organization implementation attributes System architecture Attributes relationship

21 PRODUCT AND ORGANIZATION CONCURRENT ENGINEERING 21

22 IPD FRAMEWORK Systems Engineering Concurrent Engineering

23 INTEGRATED PRODUCT DEVELOPMENT Evolution is translated by Need has Stakeholder Requirement derives Function Form derives validation Innovation Product has Life Cycle Process Organization relationships Learning Attribute is performed by affects is described by verification

24 IT S ALL ABOUT METRICS Problem Domain Stakeholders Requirements Relationships System Solution Domain Attributes

25 CONCLUSIONS Systems engineering is all about metrics! Systems engineering is simply not possible without metrics! 25

26 Thanks for your attention! Questions? 26

27 Back up slides 27

28 Background Electronics engineering, 1987, ITA Concurrent engineering, MSc, 1994, ITA Systems engineering, PhD, 1999, Loughborough University, UK System of systems for Space Exploration, 2004 and 2005, Post Doc, MIT, USA Managerial position at LIT from 1999 to 2008, worked on satellite manufacturing, assembly, integration, testing since 1988 at INPE Professor of systems engineering, requirements engineering, quality engineering and AIT at INPE and at ITA, since Master completions and 1 Doctoral completion since