ESD.33 --Systems Engineering

1. ESD.33 --Systems Engineering INCOSE Model of SE RCI Model of SE Session #2 Dan Frey Don Clausing

2. Plan For the Session Follow-up from session #1 • INCOSE SE handbook • RCI model of SE • Review assignment #2

3. Engineering Systems &Systems Engineering ESD mission:To establish Engineering Systems as a field of study focusing on complex engineered systems and products viewed in a broad human, social and industrial context. Use the new knowledge gained to improve engineering education and practice. History of technology Engineering Systems Systems Engineering Technology policy

4. Discussion Point • Did the design of the CFM56 jet engine entail a systems engineering function? • Did the design of Whittle’sjet engine entail a systems engineering function?

5. Scott Thomson Hamilton Sundstrand, Section Lead -Electric Systems • I wanted to comment on the CFM56 vsWhittle engine. • The CFM56 engine is …an example of the system engineering aspects of organizations and their architecture/structure and how they relate to the partitioning of the engine itself. The engine being built by CFMI, which is a consortium of GE, SNECMA and Hispano-Suiza. No single player builds the entire engine … Whittle had his fairly small shop with a collection of machinists and his lab -all probably within his domain and span of control. • One of the other greatly complicating factors of the CFM56 vs. Whittle engine are all of the secondary power extractions that are powered from today's engines, which have an enormous impact on the engine's performance • SyEmakes this possible today; whereas Whittle was focused on a revolutionary powerplantfor propulsion.

6. Cruise thrust specific fuel Consumption lb fuel/hr lb thrust P&W deHavilland RR GE Evolution of Gas Turbine Engine Performance 1.05 1.00 0.95 0.90 0.85 0.80 0.75 0.70 0.65 0.60 0.55 0.50 0.45 0.40 1945 1950 1955 1960 1965 1970 1975 1980 1985 1990 1995 2000 2005

7. P1 P2 T1 T2 Performance Drives Complexity Brayton Cycle P 3 2 Consequently, complex secondary flows required 4 1 V Need higher and higher turbine inlet temperatures for efficiency γ(γ-1) η = 1− = 1−

8. memory working = 7 ± 2 chunks expert knowledge 50,000 chunks Cognitive Parameters rate of learning = about 5,000 chunks / yr connections within a brain connections between two brains 106 Adapted from Simon, Herbert, 1969, Sciences of the Artificial, MIT Press.

9. Secondary flow systems and controls cause a risk of rework Design Interface Matrix Adapted from Sosa, Manuel E., S. D. Eppinger, and C. M. Rowles, 2000, “Designing Modular and Integrative Systems”, Proceedings of the DETC, ASME.

10. Plan For the Session • Follow-up from session #1 • INCOSE SE handbook • RCI model of SE • Review assignment #2

11. Questions to Probe Chapter 2 According to INCOSE: • When did SE emerge as a separate branch of engineering? • What are some of the key functions of SE? • Who should carry out the SE function? • What fraction of the program budget should be spent on SE? • Do SE methods apply to “smaller” systems? INCOSE International Council on Systems Engineering

12. Ch 4 Questions • Who participates in each process? • What emerges from each process? Systems Engineering Process Overview Plans, Directives & Status Outcomes & Feedback Requirements System Products Acquisition Request Designs Products

13. Systems Engineering Process According to INCOSE, the basic Systems Engineering process tasks are: 1) Define the System Objectives 2) Establish the Functionality 3) Establish the Performance Requirements 4) Evolve Design and Operation Concepts 5) Select a Baseline 6) Verifythat the Baseline Meets Requirements 7) Validate that the Baseline Satisfies the User 8) Iterate the Process through Lower Levels INCOSE International Council on Systems Engineering

14. Layer 2 Solution Blocks Layer 4 Solution Blocks Layer 3 Solution Blocks Customer Desired System Design Feedback Assigned Requirements Specified Requirements System Other Stakeholder Requirements Design Feedback Assigned Requirements Specified Requirements Other Stakeholder Requirements Design Feedback Assigned Requirements Specified Requirements Other Stakeholder Requirements Design Feedback Assigned Requirements Other Stakeholder Requirements Specified Requirements System Design Hierarchy

15. Discussion Point Under what conditions should “commercial” enterprises be plotted in the upper left quadrant? 1 Influence of External Rigidities, Especially Governments INCOSE LEGACY COMMERCIAL 0 0 Number of Strong Global Competitors N

16. Asking Better Questions Better Questions • ? • ? Questions • What is the best way to store and access our inventories? • How can we accurately predict our field reliability? • Another example?

17. Plan For the Session • Follow-up from session #1 • INCOSE SE handbook • RCI model of SE • Review assignment #2

18. Plan For the Session • Follow-up from session #1 • INCOSE SE handbook • RCI model of SE • Review assignment #2

19. Assignment #2Frameworks • Due: Thursday 6/17 at 8:30AM • Self select teams of 2-4 (preferably at the same company or in the same industry) 1. Select a company and write about the tools/processes related to RCI at the company 2. Do a value stream map of any value creating process of your choice 3. Develop an example of a set-based approach

20. System Engineering Implemented in FPDS Part / Component Fabrication / Verification Part / Component Design ‧ Component Design Specification - CDS KO SI SC PA PR J1 Customer Satisfaction Customer Musts / Wants Customer Focus Customer Experience & Feedback Corporate Knowledge > Generic VDS & SDS > Competitive Benchmark Data > Reusability Constraints & Data > Product Knowledge > Manufacturing Knowledge & Reusability > Technology > Warranty Data > Models Vehicle Level Inputs ‧Purchase / owner / operator ‧ Regulatory (FMVSS, EPA, ...) ‧ Corporate (WCR, ABS, Manuf, ...) Purchase, Operate Disposal & Maintain Customer Requirements Requirements Cascades Feasibility Feedback Vehicle Level Requirements ‧Vehicle Attributes ‧Vehicle System Specification - VDS Vehicle Verification DVM / DVP Production Requirements Cascade Feasibility Feedback System / Subsystem Level ‧System & ‧Subsystem Design Specifications - SDS System Verification DVM / DVP Requirements Cascade Feasibility Feedback Highly lterative Mostly serial Adapted from Ford Motor Company.

21. Next Steps • Do the reading assignments for session #3 – Womak_LeanThinking Introduction.pdf – Stanke_Murman_LifecycleValue in Aerospace.pdf – Ward_TheSecond Toyota Paradox.pdf • If you want, begin Assignment #2 • Come to session #3 – 8:30AM Tuesday 15 June