Introduction to Systems Engineering

1. Unraveling Systems
Engineering
Escuela Técnica Superior de Ingeniería Aeronáutica y del Espacio
Universidad Politécnica de Madrid
Madrid, Spain, 27th November 2017
Bernardo A. Delicado
Bernardo.Delicado@incose.org

2. 2
About me

3. Content
3
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

4. Content
4
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

5. Why am I passionate about SE ?
5
Systems Engineering means Good Engineering
Blanchard & Fabrycky (1998)
Systems Engineering done well -> Projects run well
Systems Engineering done bad -> Projects run bad
Stoewer (2012 )

6. 6
Systems Engineer Best Job in
America in 2009

7. Industrial Revolution
7
more than ever
have to develop a
systems engineering
approach and skill
set
(Bechtold et al, 2014)

8. Industrial Revolution
8

9. Systems Engineering
9
What it is?

10. SE differentiates itself from
“Traditional Engineering”
10
“Traditional” Engineering activities
have been typically limited to a
definite discipline, with
practitioners very likely to become
“specialists/experts” in the
relevant field.
The specialist “knows” very well
his own tiny corner of the universe;
he/she is radically ignorant of all
the rest.
Arrichiello ( 2014 )
Ortega-Gasset ( 1930)

11. SE differentiates itself from
“Traditional Engineering”
11
SE differs from mechanical, electrical, software
,aerospace and other engineering disciplines in
several important ways.
SE is focused on the system as a whole – it
emphasizes its total operation:
• Looks at the system from the outside as well as the inside
• Interactions with other systems and the environment
• Concerned with not only engineering design but also
external factors

12. Systems Engineering
12
Why is it
needed ?

13. SE needed due to product
complexity is increasing
• High Complexity
• Multidisciplinary
• Cost & Time

14. Late and Over-Budget
14
The challenges associated with
technical complexity continue to
grow over time.
Deloitte (2008)

15. Industry Outlook
15
A closer look at several large-scale
programs that have missed their
commitments in the last few years
reveals many root causes, including the
use of immature technologies, lack of
appropriate levels of systems
engineering discipline, and a plethora
of complex engineering changes.
Other causes for the overruns include
inadequate supplier business maturity,
capacity, and performance, as well as
optimistic scheduling with poor time
and resources planning for
contingencies.
Deloitte ( 2012 )

16. Complex Global Trends
16
SE Vision 2025. Copyright © 2014 by INCOSE. All rights reserved.
Human Needs translate to…
Societal Needs that are satisfied by…
System Solutions

17. Systems
17
Seeing the world in a particular
way, because how you see
things affects the way you
approach situations or undertake
specific tasks.

18. Video 1
Complexity &
Systems
18

19. Origins of SE
19
• No specific date can be associated with the origins of SE
• Recognition of SE as a distinct discipline is often associated with
the effects of WWII ( 1935-1940 )
• SE as a discipline evolved as a result of rapid growth of
technology & its application to military & commercial operations
during the 2nd half of the 20th century ( used intensively in Apollo
Program )

20. Systems Engineering =
Processes ?
20

21. Processes
Philosophy
Culture
Profession
Methods
Tools
Terminology
Technical
Management
Language
Competencies
Colaborative Engineering Teamwork
Capability
Discipline
Problem Approach
¿What is
Systems
Engineering ?
Problem Solving
Systems Thinking Systems Integration

22. Processes are a good check-list to be
followed
@bernardo
Systems engineering not only
processes

23. Content
23
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

24. Views of the Problem
( Perspectives )
24

25. Aircraft
25
What is the most
important for you
in aircraft design?

26. 26
Different Views of the same
Problem
@bernardo

27. 27
Problem
Space
Who? What ?
Where ?
When?
Why ?
How?
Specialists Views

28. The “Best” System ( Aircraft)
“The best is the name of the good”
“SE is the art of the good enough”
SE seeks the “best” possible system, which often is not the
one that provides the best performance
28
(Ntaimo, 2008)

29. Specialists
The detailed specialists or experts (mechanical
engineers, electronics engineers, software engineers,
etc.) can produce very good designs, but not
necessarily good systems
29

30. SE relies on SE Teams
“A good SE team will include many individual specialists who have
learned how to work their areas into sensible interfaces with the
contributions of the other specialists. It is the team that must include
the total intelligence, background, experience, wisdom, and creative
ability to cover all aspects of the problem of applying science and
technology, and particularly, who must integrate the overall
intelligence“
The specialists are managed and coordinated by a systems engineers
Systems engineering is all about sharing,
communicating, coordinating, and
optimizing
30
Ramo & St.Clair (1998)

31. SE Practice & Life Cycle
31
Shamieh ( 2011)
LifeCycle

32. 32
Copyright © 2014 Jeff Patton. All rights reserved.
Teamwork Complexity

33. Teamwork Complexity
Total Lines of Communication (TLC)
TLC = N*(N-1)/2
Individual Lines of Communication (ILC)
ILC = N-1
Individual Communication Loss (ICL)
ICL = TLC - ILC
TLC =0 ILC =0 ICL =0
TLC = 10 ILC =4 ICL =6 TLC = 21 ILC =6 ICL =15 Between Teams
SOURCE : https://dev.to/lpasqualis/the-stages-of-teamwork-complexity-ce8?lipi=urn%3Ali%3Apage%3Ad_flagship3_search_srp_content%3BSGRrYkQ%2BQF%2BtrOyIwzG7kw%3D%3D

34. Procesosde Ingeniería de Sistemas
Personas
con competencias
Organización
Engineering decision-
making process is a
challenge
@bernardo

35. Systems Engineering : Definitions
According to INCOSE (International Council on Systems Engineering)
SE is an interdisciplinary approach and a means to enable
the realization of successful systems. It focuses on defining customer
needs and required functionality early in the development cycle,
documenting requirements, then proceeding with design synthesis
and system validation while considering the complete problem:
operations, cost and schedule, performance, training and support,
test, manufacturing, and disposal.
SE integrates other disciplines and specialty groups into a team
effort, forming a structured development process that proceeds from
concept to production to operation 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

36. Video 2
Interdisciplinary
Collaboration
36

37. Design in Engineering
37
Arrichiello ( 2014 )
All design begins with a
clearly defined need
All designs result in a
system, product or project
which meets the need
All designs arise from a
creative response to a
need

38. Systems Approach in SE
38
( The UK Royal Academy of Engineering , 2017)

39. Guiding principles for complex
development in SE
39
• Keep your eyes on the prize.
• Involve key stakeholders.
• Define the problem before assuming a solution.
• Break down the problem into manageable chunks
ensuring they will be integrated successfully and ultimately
deliver the required emergent capabilities.
• Delay specific technology choices.
• Connect the dots between requirements and design.
• Test early, test often.
Shamieh, Cathleen ( 2011)

40. Creating Systems = Battle
40
Conceive Design Implement Operate
PROBLEM PROBLEM PROBLEM PROBLEM PROBLEM
Problem Solving Method = Systems Engineering
Need Vision Delivery
Life Cycle

41. Problem
41
HAVING a problem IS NOT a problem.
PAYING a problem IS a problem.
( Salado, 2013 )

42. Problem Space vs Solution Space :
Keeping Separate is Critical
42
Problem
Space
Systems
QUESTIONS
Solution
Space
Technologies &
Products
ANSWERS
It is all about needs
It is all about the offerings
that satisfy needs

43. Introduction to INCOSE 43
The problemProblem Understanding is Key
Don´t jump to the solution

44. Introduction to INCOSE 44

45. Introduction to INCOSE 45

46. Introduction to INCOSE 46

47. Introduction to INCOSE 47

48. Introduction to INCOSE 48

49. Introduction to INCOSE 49

50. Introduction to INCOSE 50

51. 51
No comments

52. Addressed Users' Real Needs ?
Introduction to INCOSE 52

53. Introduction to INCOSE 53
Solved the Problem ?

54. Introduction to INCOSE 54
Solved the Problem ?

55. 55Shamieh, Cathleen ( 2011)
Large systems development efforts suffer from poor communications :
• Teams are widely dispersed across cities, companies, and countries.
• Language and cultural barriers make communication difficult, and time
differences often hamper collaboration.
• Even for employees within the same company, organizational silos can
impede communication and reduce productivity.
Poor communication can cause many problems, including:
• Lack of clarity of system goals
• Multiple interpretations of system requirements
• Incomplete or overlooked requirements
• Time wasted gathering information manually from multiple sources
• Teams working with outdated documents
• Gaps or redundancies in responsibilities
Poor Communication

56. 56
Examples of Problems

57. 57

58. 58

59. 59

60. 60

61. 61

62. 62

63. 63

64. 64

65. 65

66. Content
66
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

67. Pillars of Systems Engineering
67

68. Implementation of Systems Engineering
( A Socio-Technical Problem )
Methods
&
Tools
Systems Engineering Processes
People
Project
Enterprise

69. 69
Processes
Technical
Processes
Project
Management
Processes
Business &
Organization
OtherOrganizations
@incose
Dimensions of SE
V

70. TAILORING IS KEY
The appropriate amount of SE
effort is devoted to the
appropriate activities to reduce
project risk to an acceptable
level while at the same time
making most cost-effective use of
engineering resources

71. Video 3
SE Process &
Tools
71

72. Creating Systems that work :
Principles
1. Debate, define, revise and pursue the purpose
2. Think holistic/systemic
3. Follow a systematic procedure
4. Be creative
5. Take account of the people
6. Manage the project and the relationships
72
( The UK Royal Academy of Engineering , 2007)

73. Systemic
System
(system of
interest )
Sistematic
Conceive Design Implement OperateSystem
PROBLEM
SOLUTION
Product
lens
System Life Cycle
refers to the holistic appreciation
of the problem/system of interest,
considering its context,
stakeholders, and the
interrelationships and
interconnections
( SYSTEMS THINKING )
refers to taking a structured, orderly
approach to solve the problem and to
implement the system
SOFT
HARD

75. Systems Thinking
Systems thinking is a set of synergistic analytic
skills used to improve the capability of
identifying and understanding systems,
predicting their behaviors, and devising
modifications to them in order to produce
desired effects.
75
Arnold & Wade (2015 )

76. Systems Thinking
76Arnold & Wade (2015 )

77. Video 4
Systems
Thinking
77

78. Why Systems Engineering ?
78
%
100
50
75
25
Commitment to technology,
configuration, cost, etc.
System specific knowledge
Cost incurred
Ease of change
Conceive Design Implement Operate
Blanchard & Fabrycky (1998)

79. 21st Century Systems Engineering:
A Practice in Transition Moving from
Document-Centric to Model-Centric
79INCOSE Model-Based Systems Engineering Workshop, February 2010. Copyright © 2010 by INCOSE. All rights reserved.
Today
standalone models related
through documents
Future
shared system model with multiple
views, and connected to discipline
models

80. Content
80
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

81. SE as a profession
81
The establishment of SE as a unique discipline has been inhibited
by the absence of a body of knowledge until 2013.
Despite those obstacles, the recognized need for SE in industry
and governments has spurred the establishment of a number of
academic programs offering master’s degrees in SE ( mainly in
USA, UK, France, Germany, Norway and Italy )
There has also been a relatively recent recognition of SE as a
profession in the formation of the professional society INCOSE (
Certification Program ). One of whose primary objectives is the
promotion of SE education, and the recognition of SE as a
professional career.
Ntaimo ( 2008 )

82. T-Shaped = Systems Engineer
82
Breath
Deep
Ability to work outside of core area
Specialty or core
area of expertise

83. Systems Engineering Role
83
The systems engineer is like
the maestro ,who knows
what the music should sound
like ( the look and function of
a design ) and has the skills
to lead a team in achieving
the desired sound( meeting
the system requirements )
Ryschkewitsch et al ( 2009 )

84. Systems Engineers
84
• Understand the fundamentals of mathematics, physics, and
other pertinent sciences,
• Have mastered a technical discipline and learned multiple
disciplines
• Must understand the end game and over all objectives of the
endeavor
• Create a vision and approach for attaining the objectives
• May be architects or designers
• Select and shape the technical issues to be addressed by
multidisciplinary teams
• Must often interpret and communicate objectives,
requirements, system architecture , and design
• Are responsible for the design’s technical integrity
• Organize and lead multidisciplinary teams
• Are responsible for the success of the performance
Ryschkewitsch et al ( 2009 )

85. The Personal Characteristics of
Good Systems Engineers
85
Ryschkewitsch et al ( 2009 )

86. Technical Leadership = Systems
Engineering Leadership Behaviors
86
LTI. Copyright © 2017 by INCOSE. All rights reserved.
Technical
Competence
Leadership
Skills
Technical Leadership

87. Content
87
Problem Space vs SE
SE Implementation
SE Career Path
Conclusions
Introduction

88. Conclusions
• Complexity, technical diversity, and the need to involve
many specialists/experts leads to the need for Systems
Engineering
• Systems Engineering is about complementary systemic
and systematic approaches
• Systems Engineering is about empowerment of good
interdisciplinary teams
• Systems Engineering is about seeing the world in a
particular way ( Systems Thinking )
• Systems Engineering is about a profession with future in all
sectors ( not only aerospace )
88

89. 89
“Si quieres construir un barco, no ordenes a los
hombres ir a por madera ni distribuyas entre ellos
los distintos trabajos. Es preferible que les enseñes
el anhelo por la inmensidad del mar “
Antoine Marie Jean-Baptiste Roger de Saint-Exupéry
Conde de Saint-Exupéry

90. Thank You

91. References
• Arnold, Ross D.; Wade Jon P. (2015), “A Definition of Systems Thinking: A Systems Approach” , 2015
Conference on Systems Engineering Research USA, Elsevier, www.sciencedirect.com,doi:
10.1016/j.procs.2015.03.050
• Arrichiello, Vincenzo ( 2014 ), “Introduction to Systems Engineering”, INCOSE Italian Chapter Conference
on Systems Engineering (CIISE2014), Rome, Italy, November 24 – 25, 2014
• Bechtold, Jochen ; Kern, Andreas; Lauenstein, Christoph ; Bernhofer, Lena ( 2014 ), “Industry 4.0 - The
Capgemini Consulting View: Sharpening the Picture beyond the Hype”, Capgemini Consulting.
• Ntaimo, Lewis ( 2008), Presentation “Introduction to Systems Engineering”, Chapter 1, Course ISEN 689
Systems Thinking and Analysis, 2008 Spring Semester , Department of Industrial & Systems Engineering ,
Texas A&M University, USA.
• Ortega y Gassett, José ( 1930 ), “ THE REVOLT OF THE MASSES”
• Patton, Jeff (2014), “User Story Mapping”, Published by O’Reilly Media, Inc., ISBN: 978-1-491-90490-9
• Ramo, Simon ; St.Clair, Robin K. (1998), “ The Systems Approach : Fresh Solutions to Complex Problems
Through Combining Science and Practical Common Sense”, Kni Incorporated, California
• Ryschkewitsch, Michael; Schaible, Dawn; Larson , Wiley (2009), “The Art and Science of Systems
Engineering”, Systems Research, Forum Vol 03, Issue 2, 81-100 (2009). DOI: 10.1142/S1793966609000080
• Salado, Alejandro ( 2013) , “Problems during system integration: When architecture and contracts
meet”, KSEE 2013 - Kongsberg systems engineering event.
• Shamieh, Cathleen ( 2011), “Systems Engineering For Dummies”, IBM Limited Edition, Wiley Publishing
Inc, ISBN: 978-1-118-10001-1
• Stoewer, Heinz ( 2012), Presentation “Future Systems and Systems Engineering -Challenges ahead !”, 3rd
EADS Systems Engineering Forum, Toulouse 18. October, 2012
• The UK Royal Academy of Engineering ( 2007), “Creating systems that work: Principles of engineering
systems for the 21st century”, ISBN: 1-903496-34-9
• The UK Royal Academy of Engineering ( 2017),“ Engineering better care a systems approach to health
and care design and continuous improvement” ISBN: 978-1-1909327-35-1
91