ESD.33 --Systems Engineering

Session #2

INCOSE Model of SERCI Model of SE

Dan FreyDon Clausing

Plan For the Session

Follow-up from session #1

• INCOSE SE handbook

• RCI model of SE

• Review assignment #2

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

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?

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.

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

19

45

19

50

19

55

19

60

19

65

19

70

19

75

19

80

19

85

19

90

19

95

20

00

20

05

Cruise thrustspecific fuel

Consumption

lb fuel/hr

lb thrustP&W

deHavillan

d

RR

GE

Performance Drives Complexity

Need higher and higher turbine inlet temperatures for efficiency

η = 1−

T1

T2

= 1−P1

P2

γ(γ-1)

Consequently, complex secondary flows required

V

2 3

1 4

Brayton CycleP

Cognitive Parameters

Adapted from Simon, Herbert, 1969, Sciences of the Artificial, MIT Press.

memory working = 7 ± 2 chunksexpert knowledge 50,000 chunks

connections within a brain

connections between two brains106

rate of learning = about 5,000 chunks / yr

Secondary flow systems and controls cause a risk of rework

Adapted from Sosa, Manuel E., S. D. Eppinger, and C. M. Rowles, 2000, “DesigningModular and Integrative Systems”, Proceedings of the DETC, ASME.

Design Interface Matrix

ModularSystems

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)

• Follow-up from session #1

• INCOSE SE handbook

• RCI model of SE

• Review assignment #2

Plan For the Session

Questions to Probe Chapter 2According 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 EngineeringINCOSE

Systems Engineering Process Overview

Ch 4 Questions

• Who participates in each

process?

• What emerges from each

process?

Technical Management

PlanningProcess

AssessmentProcess

ControlProcess

TechnicalEvaluation

SystemsAnalysisProcess

RequirementsValidationProcess

SystemsVerification

Process

End ProductsValidationProcess

Acquisition& Supply

SupplyProcess

AcquisitionProcess

SystemDesign

RequirementsDefinition ProcessSolution Definition

Process

ProductRealization

ImplementationProcess

Transition touse Process

Outcomes&

Feedback

SystemProducts

Plans,Directives& Status

AcquisitionRequest

Requirements

Designs

Products

Systems Engineering Process

1) Define the System Objectives2) Establish the Functionality3) Establish the Performance Requirements4) Evolve Design and Operation Concepts5) Select a Baseline6) Verifythat the Baseline Meets Requirements7) Validate that the Baseline Satisfies the User8) Iterate the Process through Lower Levels

International Council on Systems EngineeringINCOSE

According to INCOSE, the basic Systems Engineering process tasks are:

System Design HierarchySystem Design Hierarchy

Customer DesiredSystem

System

Layer 2SolutionBlocks

Layer 4SolutionBlocks

Layer 3SolutionBlocks

Design Feedback

Design Feedback

Design Feedback

Design Feedback

Specified Requirements

Specified Requirements

Specified Requirements

Specified Requirements

AssignedRequirements

Other StakeholderRequirements

AssignedRequirements

AssignedRequirements

AssignedRequirements

Other StakeholderRequirements

Other StakeholderRequirements

Other StakeholderRequirements

Discussion PointUnder what conditions should “commercial” enterprises be plotted in the upper left quadrant?

1

0N0 Number of Strong Global Competitors

Influ

ence

of E

xter

nal R

igid

ities

,Esp

eci

ally

G

overn

ments

INCOSELEGACY

COMMERCIAL

Asking Better QuestionsQuestions

• What is the best way

to store and access our inventories?• How can we accurately predict

our field reliability?• Another example?

Better Questions• ?

• ?

• Follow-up from session #1

• INCOSE SE handbook

• RCI model of SE

• Review assignment #2

Plan For the Session

• Follow-up from session #1

• INCOSE SE handbook

• RCI model of SE

• Review assignment #2

Plan For the Session

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 company2. Do a value stream map of any value creating process of your choice3. Develop an example of a set-based approach

System Engineering Implemented in FPDSCustomer

Musts / Wants Customer

Musts / Wants Customer

Satisfaction Customer

Satisfaction

Customer FocusCustomer 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

FeasibilityFeedback

RequirementsCascade

FeasibilityFeedback

RequirementsCascade

FeasibilityFeedback

Part / Component Design‧ Component Design

Specification - CDS

Part / Component Fabrication / Verification

Highly lterative Mostly serial

PA PR J1SCSIKO

Adapted from Ford Motor Company.

CustomerRequiremen

ts

DVM / DVP

DVM / DVP

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