1. ESD.33 --Systems Engineering Session #2 INCOSE Model of SE RCI Model of SE 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. Technology policy Systems Engineering History of technology Engineering Systems

4. Discussion Point Did the design of the CFM56 jet engine entail a systems engineering function? Did the design of Whittlesjet 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. 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 Cruise thrust specific fuel Consumption lb fuel/hr lb thrust P&W deHavilland RR GE

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

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

9. Secondary flow systems and controls cause a risk of rework Adapted from Sosa, Manuel E., S. D. Eppinger, and C. M. Rowles, 2000, Designing Modular and Integrative Systems, Proceedings of the DETC, ASME. Design Interface Matrix Modular Systems FAN system (7 components) LPC system (7 components) HPC system (7 components) B/D system (5 components) HPT system (5 components) LPT system (6 components) Integrative Systems Mech. components (7 components) Externals and Controls (10 components)

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

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? International Council on Systems Engineering INCOSE

12. Systems Engineering Process Overview Ch 4 Questions Who participates in each process? What emerges from each process? Technical Management Planning Process Assessment Process Control Process Technical Evaluation Systems Analysis Process Requirements Validation Process Systems Verification Process End Products Validation Process Acquisition & Supply Supply Process Acquisition Process System Design Requirements Definition Process Solution Definition Process Product Realization Implementation Process Transition to use Process Outcomes & Feedback System Products Plans, Directives & Status Acquisition Request Requirements Designs Products

13. Systems Engineering Process 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 International Council on Systems Engineering INCOSE According to INCOSE, the basic Systems Engineering process tasks are:

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

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

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

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

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

19. Assignment #2 Frameworks 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 Customer Musts / Wants Customer Musts / Wants Customer Satisfaction Customer Satisfaction 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 Vehicle Level Requirements Vehicle Attributes Vehicle System Specification - VDS System / Subsystem Level System & Subsystem Design Specifications - SDS Vehicle Verification Production System Verification Requirements Cascades Feasibility Feedback Requirements Cascade Feasibility Feedback Requirements Cascade Feasibility Feedback Part / Component Design Component Design Specification - CDS Part / Component Fabrication / Verification Highly lterativeMostly serial PAPRJ1SCSIKO Adapted from Ford Motor Company. Customer Requirements DVM / DVP

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