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.
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

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
Cruise thrust
specific fuel
Consumption
lb fuel/hr
lb thrust
1945
1950
1955
1960
1965
1970
1975
1980
1985
1990
1995
2000
2005
P&W
deHavilland RR GE

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

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

9. Secondary flow systems and controls cause a risk of rework
Modular
Systems
FAN system
(7 components)
LPC system
HPC system
B/D system
(5 components)
HPT system
LPT system
(6 components)
Integrative
Mech. components
Externals and
Controls
(10 components)
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. Systems Engineering Process Overview
Technical Management
Planning
Process
Assessment
Control
Ch 4 Questions
• Who participates in each
process?
• What emerges from each
Plans,
Directives
& Status
Outcomes
&
Feedback
Acquisition
& Supply
Supply
Process
Requirements
System
Design
Requirements
Definition Process
Solution Definition
Process
Acquisition
Request
System
Products
Designs
Product
Realization
Implementation
Process
Transition to
use Process
Products
Technical
Evaluation
Systems
Analysis
Process
Requirements
Validation
Verification
End 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. System Design Hierarchy
Customer Desired
System
Design Feedback
Assigned
Requirements
System
Specified Requirements
Other Stakeholder
Requirements
Design Feedback
Layer 2
Solution
Blocks
Assigned
Requirements
Specified Requirements
Other Stakeholder
Requirements
Design Feedback
Assigned
Requirements
Layer 3
Solution
Blocks
Specified
Requirements
Other Stakeholder
Requirements
Design Feedback
Assigned
Requirements
Layer 4
Solution
Blocks
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
Number of Strong Global Competitors N

16. Asking Better 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. 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 #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. Customer Experience & Feedback
System Engineering Implemented in FPDS
Customer
Satisfaction
Customer
Musts / Wants
Customer Focus
Customer Experience & Feedback
Corporate
Knowledge
> Generic VDS &
SDS
> Competitive
Benchmark
Data
> Reusability
Constraints &
> Product
> 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
Part / Component Design
‧ Component Design Specification - CDS
Part / Component Fabrication / Verification
Highly lterative
Mostly serial PA PR J1 SC SI KO
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