esd.33 systems engineering lecture 1 course introducon · pdf fileesd.33 systems engineering...
TRANSCRIPT
ESD.33 Systems Engineering Lecture 1
Course Introduc8on Instructors:
Dr. Qi Van Eikema Hommes Mr. Pat Hale
Mr. David Erickson
Teaching Assistants: Ellen Czaika
Ipshita Deepak
Agenda Welcome and Introduc8on of Teaching Staff Why are we here?
What are Systems?
What is Systems Engineering?
Why do we study Systems Engineering?
Course Schedule and Logis8cs
Qi Van Eikema Hommes© June 8, 2010 2
Dr. Qi Van Eikema Hommes • ESD Research Associate and Lecturer • 8 years of work experiences in automo8ve companies (Ford and GM) – Senior Research Scien8st at GM R&D – Powertrain Systems Engineer at Ford
Qi Van Eikema Hommes
Ph.D. and M.S. in Mechanical Engineering B.S. in Mechanical
Engineering
© June 8, 2010 3
MIT University ofKentucky
Dr. Pat Hale • SDM Director, ESD Senior Lecturer • Military experience: - 20 years in U.S. Navy: submarines
• Industry experience: - Draper Labs (Director, Systems Engineering) - O8s Elevator (first Director, Systems & Controls Engineering)
• Past INCOSE president
© June 8, 2010 Qi Van Eikema Hommes 4
Academic Background
B.S. Mechanical Engineering University of Minnesota
M.S. Mechanical Engineering Engineer’s Degree in Ocean Engineering Massachusetts Institute of Technology
MBA Cornell University
© June 8, 2010 Qi Van Eikema Hommes 5
About me:
Product designer/ manager, systems engineer, mobile tech enthusiast, a mother, vocal ar8st and a second year SDM student
© June 8, 2010 Qi Van Eikema Hommes 6
About me: SDM08 Former manager of systems engineering team Ethnographer Athlete (numerous sports: rowing, yoga, skiing/snowboarding, hiking, biking, sailing, surfing, etc.)
© June 8, 2010 Qi Van Eikema Hommes 7
Is This a System and Why?
http://science.howstuffworks.com/power.htm/printable
© June 8, 2010 Qi Van Eikema Hommes 10
Power grid image removed due to copyright restrictions.Image can be found at HowStuffWorks.com.
Is This a System and Why?
© June 8, 2010 Qi Van Eikema Hommes 12
Name
Headquarters
Security Department
NameStrategy
Department
NameFinance
Department
Name
IT Department
NamePersonnel
Department
NameLegal
Department
NamePublic Relations
Department
NameMarketing
Department
NameSales
Department
NameResearch
Department
NameLogistics
Department
Name
Production
Name
Administration
Name
Corporate Name
Image by MIT OpenCourseWare.
Is This a System and Why? http://ccl.northwestern.edu/netlogo/models/WolfSheepStrideInheritance (ANIMATION)Works in Firefox browser
Wolves eats sheep. Sheep eat grass. Wolves and sheep reproduce. They move in random directions.
Try when there are more wolves than sheep.
© June 8, 2010
© June 8, 2010 Qi Van Eikema Hommes 13
What Types of Systems Have You Worked on?
Why do you call them “systems?”
© June 8, 2010 Qi Van Eikema Hommes 14
Defini8on of Systems • A combina8on of interac8ng elements organized to achieve one more stated purposes.
• An integrated set of elements, subsystems, or assemblies that accomplish a defined objec8ve. These elements include products (hardware, sofware, firmware), processes, people, informa8on, techniques, facili8es, services, and other support element.
Source: INCOSE SE Handbook, V3.2
© June 8, 2010 Qi Van Eikema Hommes 15
Characteris8cs of Systems
• Interac8on • Hierarchical • Emergent
• Dynamic
• Interdisciplinary
© June 8, 2010 Qi Van Eikema Hommes 16
Digital Photography
© June 8, 2010 Qi Van Eikema Hommes 17
Inkjet Photo Printer
PictBridge CompatiblePrinters (with Direct Print)
PC CompatibleComputer
CF/SD Cards
USB Cable
USB Cable
USB Cable(FireWire IFC-200D4/D44 or IFC-450D4/D44cable for EOS 1Ds Mark IIand EOS 1D Mark II)
Interface CableIFC-300PCU/IFC-400PCU(EOS-1Ds Mark II, 1D Mark II,20D, Digital Rebel XT, Digital Rebel)
CF/SD CardReader
PC Card Adapter
EOS Digital Cameras(with Direct Print)
EOS-1Ds Mark II
EOS-1D Mark II
EOS-20D
EOSDigital Rebel
EOSDigital Rebel XT
Computers
MacintoshComputer
Compact Photo Printer
Image by MIT OpenCourseWare.
System of Systems Large‐scale inter‐disciplinary problems involving mul8ple, heterogeneous, distributed systems.
• System elements operate independently. • System elements have different life cycles. • The iniAal requirements are likely to be ambiguous.
• Complexity is a major issue. • Management can overshadow engineering. • Fuzzy boundaries cause confusion. • SoS engineering is never finished. Source: INCOSE SE Handbook V3.2
© June 8, 2010 Qi Van Eikema Hommes 18
Agenda Welcome and Introduc8on of Teaching Staff Why are we here?
What are Systems?
What is Systems Engineering?
Why do we study Systems Engineering?
Course Schedule and Logis8cs
© June 8, 2010 Qi Van Eikema Hommes 20
What is Systems Engineering?
• Systems engineering is a discipline that concentrates on the design and applica8on of the whole (system) as dis8nct from the parts. It involves looking at a problem in its en8rety, taking into account all the facets and all the variables and rela8ng the social to the technical aspect.
• Systems engineering is an itera8ve process of top‐down synthesis, development, and opera8on of a real‐world system that sa8sfies, in a near op8mal manner, the full range of requirements for the system.
INCOSE SE Handbook V3.2
© June 8, 2010 Qi Van Eikema Hommes 21
What is Systems Engineering?
• Systems engineering is an interdisciplinary approach and means to enable the realiza8on of successful systems. It focuses on defining customer needs and required func8onality early in the development cycle, documen8ng requirements, and then proceeding with design synthesis and system valida8on while considering the complete problem: opera8ons, cost and schedule, performance, training and support, test, manufacturing, and disposal. SE considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs.
INCOSE SE Handbook V3.2
© June 8, 2010 Qi Van Eikema Hommes 22
Applica8on Domains of Systems Engineering
• Aerospace • Urban Infrastructure • Communica8ons systems
• Data and informa8on systems • Healthcare systems
• Electric power systems
• Produc8on/construc8on systems • Waste disposal systems
• Transporta8on systems • Financial systems
• Educa8on systems • …
Source: Blanchard, Fabrycky, Systems Engineering and Analysis, 5th ed.
© June 8, 2010 Qi Van Eikema Hommes 23
Waterfall Process Model Introduced by Royce in 1970, initially for software development.
Source: Blanchard, Fabrycky, Systems Engineering and Analysis, 5th ed.
© June 8, 2010 Qi Van Eikema Hommes 24
RequirementsAnalysis
Specifications
Design
Implementation
Test
Maintenance
FEEDBACK
Image by MIT OpenCourseWare.
Spiral Process Model
• Boehm, 1986. • Adapted from Waterfall model
• Itera8ve • Prototyping
Source: Blanchard, Fabrycky, Systems Engineering and Analysis, 5th ed.
© June 8, 2010 Qi Van Eikema Hommes 25
Need
System
Requirements
Determination
Function
Definition
Detail
Requirements
Feasibility
Analysis
Requirements
Allocation
Component
Design
Components
SystemAnalysis
Syste
mSp
ecifi
catio
nSe
lect
Desig
nEq
uipm
ent
Defin
ition
Trade-OffStudies
Evaluation andOptimization
ConceptualReview
Test andReview
Formal DesignReview
Operational
Prototype
Synthesis
System
Prototype
Implementation
Image by MIT OpenCourseWare.
© June 8, 2010 Qi Van Eikema Hommes 26
Purchase, Operate& Maintain Disposal
VehicleVerification Production
SystemVerification
Vehicle Level InputsPurchase / Owner / OperatorRegulatory (FMVSS, EPA, ...)Corporate (WCR, ABS, Manuf, ...)
Vehicle AttributesVehicle System Specification - VDS
Vehicle Level Requirements
System &Subsystem Design Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /Verification
Part / Component Design
CustomerSatisfaction
CorporateKnowledge
Generic VDS &SDSCompetitiveBenchmarkDataReusabilityConstraints &DataProductKnowledgeManufacturingKnowledge &ReusabilityTechnologyWarranty DataModels
Highly Iterative Mostly Serial
KO SI SC PA PR J1
Purchase, Operate& Maintain Disposal
VehicleVerification
SystemVerification
Vehicle Level InputsPurchase / Owner / OperatorRegulatory (FMVSS, EPA, ...)Corporate (WCR, ABS, Manuf, ...)
Vehicle AttributesVehicle System Specification - VDS
Vehicle Level Requirements
System &Subsystem Design Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /Verification
Part / Component Design
CustomerSatisfaction
CustomerMusts / Wants
CorporateKnowledge
Generic VDS &SDS
CompetitiveBenchmarkData
ReusabilityConstraints &Data
ProductKnowledge
ManufacturingKnowledge &Reusability
Technology
Warranty Data
Models
Highly Iterative Mostly Serial
KO SI SC PA PR J1
RequirementsCascades
RequirementsCascade
RequirementsCascade
FeasibilityFeedback
FeasibilityFeedback
FeasibilityFeedback
CustomerRequirements
DVM / DVP
DVM / DVP
Customer FocusCustomer Experience & Feedback
System Engineering Implemented in FPDS
Production
Image by MIT OpenCourseWare.
Is There a Winner?
• It is observed that preferences expressed by individuals and groups for one of the system models is subjec8ve.
• Research is needed to see which model fits what situa8on bemer.
• Class Discussion: – What are common among these processes? – Is Systems Engineering the same from Product Development?
© June 8, 2010 Qi Van Eikema Hommes 28
Systems Engineering vs. Product Development
Planning Concept
Development System-Level
Design Detail
Design Testing and Refinement
Production Ramp-Up
Mission Approval
Concept Review
System Spec Review
Critical Design Review
Production Approval
Product Development Process (Ulrich and Eppinger)
© June 8, 2010 © June 8, 2010 Qi Van Eikema Hommes 29
Purchase, Operate& Maintain Disposal
VehicleVerification Production
SystemVerification
Vehicle Level InputsPurchase / Owner / OperatorRegulatory (FMVSS, EPA, ...)Corporate (WCR, ABS, Manuf, ...)
Vehicle AttributesVehicle System Specification - VDS
Vehicle Level Requirements
System &Subsystem Design Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /Verification
Part / Component Design
CustomerSatisfaction
CorporateKnowledge
Generic VDS &SDSCompetitiveBenchmarkDataReusabilityConstraints &DataProductKnowledgeManufacturingKnowledge &ReusabilityTechnologyWarranty DataModels
Highly Iterative Mostly Serial
KO SI SC PA PR J1
Purchase, Operate& Maintain Disposal
VehicleVerification
SystemVerification
Vehicle Level InputsPurchase / Owner / OperatorRegulatory (FMVSS, EPA, ...)Corporate (WCR, ABS, Manuf, ...)
Vehicle AttributesVehicle System Specification - VDS
Vehicle Level Requirements
System &Subsystem Design Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /Verification
Part / Component Design
CustomerSatisfaction
CustomerMusts / Wants
CorporateKnowledge
Generic VDS &SDS
CompetitiveBenchmarkData
ReusabilityConstraints &Data
ProductKnowledge
ManufacturingKnowledge &Reusability
Technology
Warranty Data
Models
Highly Iterative Mostly Serial
KO SI SC PA PR J1
RequirementsCascades
RequirementsCascade
RequirementsCascade
FeasibilityFeedback
FeasibilityFeedback
FeasibilityFeedback
CustomerRequirements
DVM / DVP
DVM / DVP
Customer FocusCustomer Experience & Feedback
System Engineering Implemented in FPDS
Production
Image by MIT OpenCourseWare.
Agenda Welcome and Introduc8on of Teaching Staff Why are we here?
What are Systems?
What is Systems Engineering?
Why do we study Systems Engineering?
Course Schedule and Logis8cs
© June 8, 2010 Qi Van Eikema Hommes 30
The Value of Systems Engineering
© June 8, 2010 Qi Van Eikema Hommes 31
Image by MIT OpenCourseWare.
The Value of Systems Engineering
• Systems engineering efforts reduce cost and schedule overrun.
• Class discussion: Why? Think back about the characteris8cs of systems. – Interac8on – Hierarchical – Emergence – Dynamic
– Interdisciplinary © June 8, 2010 Qi Van Eikema Hommes 32
History of Systems Engineering
The Machine Age
1940s
The Systems Age
© June 8, 2010 Qi Van Eikema Hommes 33
The Machine Age • Reduc9onism—Everything can be reduced, decomposed, or
disassembled to simple indivisible parts.
• Analy9cal way of thinking – Take apart what is to be explained – Explain the smaller parts.
– The whole is the sum of its parts.
• Mechanism – Cause and effect, determinis8c thinking
– Closed System Thinking—ignore the environment a phenomenon is in.
• Mechaniza9on
– Industrial revolu8on (18‐19th century) – Machine subs8tute people for physical work
– Dehumaniza8on of work
© June 8, 2010 Qi Van Eikema Hommes 34
Examples of Machine Age Thinking • Ancient roots
– Aristotle (Physics—fire, earth, air, water, aether )
– Archimedes
• Biology – Study of cells and organs
• Physics – Study of atoms
• F. W. Taylor “Scien8fic Management”
© June 8, 2010 Qi Van Eikema Hommes 35
Class Discussion Points
• Your examples? • Strength and Weakness of Machine Age Thinking
© June 8, 2010 Qi Van Eikema Hommes 36
The System Age • Circa 1940s
• Supplemen8ng the Machine Age thinking
• Expansionism
– All objects and events, and all experience of them as parts of larger wholes.
– Stochas8c view of the systems.
• Synthe9c Thinking (Systems Thinking)
– Instead of focusing on explaining the whole but taking it apart, synthe8c thinking focuses on explaining something in terms of its role in the larger system.
– The whole is not equal to the sum of its parts—some8mes more, some8mes less.
• Teleologically oriented – Systems have purposes
– More focuses on the human aspect of organiza8on design and management.
© June 8, 2010 Qi Van Eikema Hommes 37
Machine Age vs. Systems Age Machine Age Thinking Systems Age Thinking
Reduc8onism Expansionism
Analy8cal thinking Synthe8c thinking
Mechaniza8on Teleologically Oriented
• These two eras show continuous human inquiry to understand the world. • They are complementary, not contradictory. • System Engineering is a more recent phenomenon. • Understanding the history helps us to think critically.
© June 8, 2010 Qi Van Eikema Hommes 38
INCOSE
• The Interna8onal Council on Systems Engineering (INCOSE) is a not‐for‐profit membership organiza8on founded to develop and disseminate the interdisciplinary principles and prac8ces that enable the realiza8on of successful systems.
• Mission: Share, promote and advance the best of systems engineering from across the globe for the benefit of humanity and the planet.
• Vision: The world's authority on Systems Engineering.
• hmp://www.incose.org/
© June 8, 2010 Qi Van Eikema Hommes 39
Agenda Welcome and Introduc8on of Teaching Staff Why are we here?
What are Systems?
What is Systems Engineering?
Why do we study Systems Engineering?
Course Schedule and Logis8cs
© June 8, 2010 Qi Van Eikema Hommes 42
Course Learning Objec8ves • This course intends to help you develop the capability of systems thinking by
introducing classical and advanced systems engineering theory, methods, and tools. Afer taking this class, you should be able to:
– Develop a systems engineering plan for a realis8c project.
– Judge the applicability of any proposed process, strategy, or methodology for systems engineering using the fundamental concepts from disciplines such as of probability, economics, and cogni8ve science.
– Understand system engineers’ role and responsibili8es. Understand the role of organiza8ons.
– Apply systems engineering tools (e.g., requirements development and management, robust design, Design Structure Matrix) to realis8c problems;
– Recognize the value and limita8ons of modeling and simula8on.
– Formulate an effec8ve plan for gathering and using data.
– Know how to proac8vely design for and manage system lifecycle targets.
© June 8, 2010 Qi Van Eikema Hommes 43
��������������������
�
Qi Van Eikema Hommes© June 8, 2010 44
Lecture 4 Stakeholder Analysis and Requirements Defini8on
Lecture 2 Systems Engineering As Human Ac8vity
Lecture 13
Design Verifica8on
and Valida8on, Lifecycle
Management Lecture 5 innova8on in
Systems Engineering
Lecture 6 Axioma8c Design and DM‐DSM
Method
Lecture 8 Trade Space Explora8on Concept Selec8on
Lecture 10 : Experiments
Lecture 11Lecture 12:
: Robust Design I Robust Design II
Course Layout
Course Materials • Textbooks:
– INCOSE Systems Engineering Handbook, V3.2. – “40 Principles” – QBQ
• Reference books: – Strongly recommended: Blanchard, B. S., and Fabrycky, W. J., Systems Engineering and Analysis, 5th edi8on, Pren8ce Hall, 2010.
© June 8, 2010 Qi Van Eikema Hommes 45
Course Policies • Reading –please be prepared for class discussions
• Class sessions – 2 sessions/week, 2 hours/session– Session 3, 3 hours, project proposal – Sessions 19 and 20, 4 hours, final presenta8ons.
• Amendance and class par8cipa8on – Instructor will randomly pick student names for class discussion
© June 8, 2010 Qi Van Eikema Hommes 46
Class Time Commitment • Course is H 3‐0‐6 • This is a 9 units class in a normal semester (14 weeks).
• Summer is 10 weeks, which means this course requires 12.6 hours of work per week.
• 12.6 hours = 4 hours in class + 8.6 hours outside
• 8.6 hours include reading, homework assignments, and project work.
© June 8, 2010 Qi Van Eikema Hommes 47
Grading • Project (presenta8ons and reports):
– Individual Project proposal (presenta8on and 1‐page) 10% – Mid‐term (group presenta8on) 10%
– Final (group presenta8on) 20% • Homework Assignments 10% x 5
– The first four are individual assignments 10% x 4
– The fifh is a group presenta8on 10% • Amendance and class par8cipa8on 10%
– Each class unamended without instructors’ permission reduces 1% of the grade
– Please let the instructor know if you are unable to amend the class.
© June 8, 2010 Qi Van Eikema Hommes 48
Term Project • The goal is to apply the systems engineering methods and tools to a topic that fits your interest / your industry.
• Acceptable topic examples: – Design of a new system (technical, organiza8onal, enterprise level, etc.). The project must have enough detail so that it can demonstrate the use of the methods and tools taught in the class.
– In‐depth inves8ga8on of a successful or failed project
• Choose a project that you have access to informa8on and data.
© June 8, 2010 Qi Van Eikema Hommes 49
Term Project Deliverables • Proposal (Session 3)
– Individual students propose project topics – Voluntarily form teams of 3‐5. Four‐member teams are strongly encouraged.
– Submit team forma8on report by Session 5.
• Mid‐term presenta8on (Session 9) • Final presenta8on (Sessions 19 and 20)
© June 8, 2010 Qi Van Eikema Hommes 50
Homework Assignments • What if you were called to help NHSTA inves8gate the Toyota sudden accelera8on safety recall?
• Most of the homework assignments will be centered around the ques8on: What could have been done to prevent the problem?
• Your study should not be focused only on Toyota, but automobiles in general.
• More about the case study in a few slides.
© June 8, 2010 Qi Van Eikema Hommes 51
Homework Requirements • Homework is individual‐based. Collabora8on is encouraged, but work must be turned in by individuals.
• Acknowledge all help received. • Provide references to data and informa8on sources.
© June 8, 2010 Qi Van Eikema Hommes 52
Agenda Welcome and Introduc8on of Teaching Staff Why are we here?
What are Systems?
What is Systems Engineering?
Why do we study Systems Engineering?
Course Schedule and Logis8cs
© June 8, 2010 Qi Van Eikema Hommes 53
MIT OpenCourseWarehttp://ocw.mit.edu
ESD.33 Systems EngineeringSummer 2010
For information about citing these materials or our Terms of Use, visit: http://ocw.mit.edu/terms.