ESD'33 Systems Engineering - PowerPoint PPT Presentation

Loading...

PPT – ESD'33 Systems Engineering PowerPoint presentation | free to view - id: 26de24-NmJmN



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

ESD'33 Systems Engineering

Description:

the new knowledge gained to improve. engineering ... Process. System. Design. Implementation. Process. Transition to. use Process. Product. Realization ... – PowerPoint PPT presentation

Number of Views:53
Avg rating:3.0/5.0
Slides: 22
Provided by: sarr150
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: ESD'33 Systems Engineering


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 missionTo 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 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
7
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
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
Systems Engineering Process Overview
  • Ch 4 Questions
  • Who participates in each
  • process?
  • What emerges from each
  • process?

Outcomes Feedback
Plans, Directives Status
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
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
N
0
Number of Strong Global Competitors
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
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 830AM
  • 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 Satisfaction
Customer Musts / Wants
Customer Focus
Customer Experience Feedback
Corporate Knowledge gt Generic VDS
SDS gt Competitive Benchmark Data gt
Reusability Constraints Data gt Product
Knowledge gt Manufacturing Knowledge
Reusability gt Technology gt Warranty Data gt
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
  • 830AM Tuesday 15 June
About PowerShow.com