Acquisition Of Defense Materiel Starts With More Questions Than Answers

Acquisition Of Defense Materiel
Starts With More Questions
Than Answers
Invited Lecture at ETSIAN ( Escuela Técnica Superior de
Ingenieros de Armas Navales )
Madrid, Spain, 16th April 2020
Dr. Bernardo A. Delicado
Technical Director AEIS-INCOSE
Bernardo.Delicado@incose.org

Contents
2
• Introduction
• Challenges
• Acquisition of SoS
• Systems/Systems Engineering
• Deployment of Systems Engineering
• INCOSE in Spain
• INCOSE Unstoppable Growth
Worldwide
• Conclusions

Contents
3
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Origins of Systems Engineering
5
1937 British multidisciplinary team to analize the air defence system
1939-45 Bell Labs supports NIKE development ( 1st US operational anti-aircraft missile system )
and Intercontinental Ballistic Missiles (ICBM) Program.
1951-60 SAGE ( Semi-automatic Ground Enviroment ) Air Defense System defined and
managed by MIT/Jay Forrester
1956 Invention of systems analysis by RAND corp.
1960-70 Apollo Program
First SE standards ( e.g. MIL-STD 499, NASA procedures )
1962 Publication of Arthur D. Hall – A Methodology for Systems Engineering
1989 EIA recognizes SE as important part of system development
1990 NCOSE is founded
1990-2000 Release of SE standards IEEE 1220, EIA 632
1994 NCOSE renamed to INCOSE
2002 Release of ISO/IEC/IEEE 15288
2008 App. 6500 INCOSE members worldwide
2009-2012 Systems Engineering Body of Knowledge (SEBoK)
2019 17000+ INCOSE members worldwide (70+ Chapters 35+ Countries )
2023 INCOSE Systems Engineering Handbook version 5

6
When you see a Space Shuttle , you will notice that there
are two big booster rockets attached to the sides of the
main fuel tank
Why did they use that
dimension in the design
specification ?

7
Transport was
needed from
production plant to
Space Center

8
The US standard railroad gauge (distance between
the rails) is 4 feet, 8.5 inches. That's an exceedingly
odd number.
Why was that gauge used? Because that's the way
they built them in England, and English expatriates
designed the US

9
The tunnel is slightly wider than the railroad track

10
Why did the English build them like that?
Because the first rail lines were built by the same
people who built the pre-railroad tramways, and
that's the gauge they used.

11
Why did they use that gauge then? Because the
people who built the tramways used the same
jigs and tools that they had used for building
wagons, which used that wheel spacing.

12
Why did the wagons have that particular odd
wheel spacing? Well, if they tried to use any other
spacing, the wagon wheels would break on some
of the old long distance roads in England,
because that's the spacing of the wheel ruts.

13
re of
as
rs ago
So who built those old rutted roads?
Imperial Rome built the first long distance roads in
Europe (including England) for their legions. Those
roads have been used ever since.
Since the chariots were made for Imperial Rome,
they were all alike in the matter of wheel spacing.

14
a major Space Shuttle design feature of
what is arguably the world's most
advanced transportation system was
determined over two thousand years ago
by the width of a horse's ass
Why did the wagons have that particular
odd wheel spacing?
Well, if they tried to use any other spacing,
the
wagon wheels would break on some of the
old,
long distance roads in England, because
that's
the spacing of the wheel ruts.
Imperial Roman army chariots were made just
wide enough to accommodate the rear ends of
two war horses
A major Space Shuttle design
feature of what is arguably the
world's most advanced
transportation system was
determined over two thousand
years ago by the width of
a horse's ass

Contents
15
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Root cause of failures on
acquisition programs : US DoD
17
• Inadequate understanding of requirements
• Lack of systems engineering discipline, authority, and resources
• Lack of technical planning and oversight
• Stovepipe developments with late integration
• Lack of subject matter expertise at the integration level
• Availability of systems integration facilities
• Incomplete, obsolete, or inflexible architectures
• Low visibility of software risk
• Technology maturity overestimated
Karen B. Bausman
Air Force Center for Systems Engineering
Revitalization of Systems Engineering: Past, Present and Future
NDIA 25 October 2005

18
SE Vision 2025. Copyright © 2014 by INCOSE. All rights reserved.
Increasing Complexity of System
Solutions
• High Complexity
• Multidisciplinary
• Cost
• Time

19
“in the future, all
companies will be
software companies” – in
other words, fulfilling the high
expectations of tomorrow’s
consumers will require a
seamless, coherent approach,
centered on big data, and
that this “software” will be the
ultimate source of competitive
advantage”.
George Colony,
CEO Forrester Research

Software vs Systems
20
Software is fundamental to the performance,
features, and value of most modern systems.
Software shapes the system architecture;
drives much of its complexity and emergent
behavior; strains its verification; and drives
much of the cost and schedule of its
development.
( SEBoK Version 1.9.1 2018 )

21
Dealing with complex solutions

Contents
22
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

23
Present
Still a platform-centric thinking

24
Future -> SoS
Credit : Airbus
SoS provides a Net-Centric Force which provides Commanders
with the capability to dynamically network ( connect, share,
and collaborate )
• Sensors ( regardless of platform )
• Decision-makers ( regardless of location )
• Shooters ( regardless of service )

25
System of Systems
Credit : Airbus
Credit : Airbus
NGWS
( New Generation Weapon System )
FCAS
( Future Combat Air System )

26
System vs System of Systems

Contents
27
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Systems
30
Seeing the world in a
particular way
Seeing the wholeness
instead of parts

A definition of System
31
System of Interest is the
system of concern to those
who have interest in it.
A system is a group of interacting,
interrelated, or interdependent
elements forming a complex whole.

Description of System
32
Credit : Dieter Scheithauer

Life Cycle of a System
33
A life cycle for a system generally consists of a series of stages regulated by a set of
management decisions which confirm that the system is mature enough to leave one
stage and enter another ( SEBoK Version 1.9.1 2018 )

Exploratory/Concept Stages
( Problem Space )
34
Never preconceived or
existing solutions, it kills
creativity and doesn’t
offer opportunities of
knowledge

Left Shift – Invest in the early
stages – Concept/Feasibility Studies
35
Credit : UCL

37
cost schedule
quality
domain areas
domain
engineering
science
integration
enterprise
management
systems
engineering
project
management

38
Meta-Discipline that integrates technical effort across the
Development Project
• Functional Disciplines
• Technology Domains
• Specialty Concerns
Meta-Discipline

Four dimensions for attacking a
problem
39
Information
Knowledge
SolutionProblem
To collect information about
existing solutions and products
To confront yourselves with
the need situation by
approching users
To compile a new
product design
specification by
modifiying the old
one
To synthesise a number of
alternative solutions
Problem
Space
About NEEDS
QUESTIONS
Solution
Space
About the offerings that
satisfy NEEDS
ANSWERS

Problem vs Solution
40
Who, When, Where, What, How and Why

Who, When, Where, What, How
and Why
42
Who, When,
Where
What
How
Why
Index
Rules
Model
Vision
Understand principles, what is best ?
Understand patterns
Understand rules

Problem Space vs Solution Space :
Keeping Separate is Critical
43
Requirements
Analysis
Functional
Definition
Physical
Definition
Design
Validation
Need Solution
Requirements Functions Potential
Solutions
Systems Engineering
Who, When, Where, What, How and Why

Systems Engineering vs
Military Capability
45
Who, When, Where,
What, How and Why
Military
CAPABILITY
SYSTEM
Concept
Assess
Iterative
+
Required
Behaviours
Other
Behaviours
( Emergent
Properties )

46
Which is the best way to
interact ?
System = Sum of Parts + Interactions+ Context
Architectures Evaluation

Systems Engineering ( V model )
47
Systems engineering is the
general term for the methods
used to provide optimally
engineered, operationally
effective, complex systems.
Systems engineering balances
capability, risk, complexity,
cost and technological
choices to provide a solution
which best meets the
customer’s needs

The practice of Systems
Engineering is…..
48
…..a balance between Systemic and Systematic
aspects:
Systemic - thinking about the whole system, its
context and stakeholders
Systematic - following a structured approach to
the realization of the system
( INCOSE UK)

Systemic Aspect in SE
System
(system of
interest )
Sistematic Aspect in SE
Life Cycle of System
System
MODEL
PROBLEM
/NEED
SYSTEM
SOLUTION
Product/
Service
lens
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
System
MODEL
Copyright © 2020 B Delicado prepared by the author

Contents
52
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Organizational Implementation
Methods
&
Tools
Systems Engineering Processes
People
( skills)

System Life Cycle Management
( SLCM ) Processes
54
Date of ratification by Spain :
08/05/2015
Date of national
implementation : 01/01/2018

System Life Cycle
Management ( SLCM )
55

System Life Cycle
Management ( SLCM )
56

ISO/IEC/IEEE 15288 ->
INCOSE Handbook
57

Systems Eng Processes
ISO/IEC/IEEE 15288
58

Need to adapt SE approaches
59
SE Vision 2025. Copyright © 2014 by INCOSE. All rights reserved.
Need for agility

Jumping to Solutions
It is very difficult for people
describing requirements to
avoid jumping to solutions
instead of describing
needs.

61
in conflictinadequate understanding of requirements

62
internal
Stakeholders
( views )

63
Views
Achieving balance
between inherent
conflicts

Instrucciones 67/2011 y 72/2012

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 =1 ILC =1 ICL =0
TLC = 10 ILC =4 ICL =6 TLC = 21 ILC =6 ICL =15 Between Teams

66
external
stakeholders
CUSTOMER/END USERS

Life Cycle
Military
Capability
System of
Systems
Systems
Elements
Tecnologies
SoS : 3 Dimensional Problem
SOFT
HARD

Succesive Refinement Loops
Operational Concept &
Desired Capabilities
Methods of Employment
( doctrine, organization )
Systems
Technologies
Discovery Invention
lead to
exploit
require
require
enable
enable
enable
enable

NATO Architecture Framework ( tools )
SoS essential tool
Integration of Views and Knowledge
MIRADO

72
Characteristics of a Good
Systems Engineer ( skills)

Contents
73
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Creation of Spanish Chapter
http://www.eoi.es/es/eventos/12360/constitucion-de-international-council-systems-engineering-incose-en-espana
13 June 2012

Creation of “Asociación Española de
Ingeniería de Sistemas ( AEIS )”
AEIS (professional non profit organization ) is a national legal entity
hosted by Spanish Royal Academy of Engineering established in
accordance with the law 30/1992 having the official representative role
of INCOSE in Spain. In addition, within the international structure of
INCOSE since December 2014, formally recognized as Spanish Chapter
of INCOSE.
http://www.aeis-incose.org

Figures in Spain
76
Total SEP members 68
ASEP 5
CSEP 61
ESEP 2
Active Not Active Total
Members
29/5/2019 85 106 191

Contents
78
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Contents
80
• Introduction
• Challenges
• INCOSE in Spain
Worldwide
• Conclusions

Conclusions
81
• Can't see the forest for the trees, too involved in the
details of a problem to look at the situation as a
whole.
• Apply Systems Thinking to understand Who, When,
Where, What, How and Why
• Keep separate Problem Space and Solution Space is
critical.

Conclusions
82
• Systems of Systems is becoming a critical perspective
in thinking about systems. Systems Engineering is a
key factor in making this complexity manageable.
• Spain moved toward a capability-based approach in
Materiel Acquisition, more than ever requires a
strategic commitment to expanding the role of
systems engineering among national the industries
and MoD/service communities.

HAVING a problem IS
NOT a problem.
PAYING a problem IS a
problem.

84
Come and join INCOSE
Professionals, students and
young graduates are welcome

Acquisition Of Defense Materiel Starts With More Questions Than Answers

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (9)

Ähnlich wie Acquisition Of Defense Materiel Starts With More Questions Than Answers

Ähnlich wie Acquisition Of Defense Materiel Starts With More Questions Than Answers (20)

Mehr von Bernardo A. Delicado

Mehr von Bernardo A. Delicado (17)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Acquisition Of Defense Materiel Starts With More Questions Than Answers