Transcript Dynamic Complexity in System of Systems

Dynamic Complexity in
System of Systems
Ron Johnson
Vice President, Engineering & Technology
Advanced Systems
The Boeing Company
BOEING is a trademark of Boeing Management Company.
Copyright © 2007 Boeing. All rights reserved.
QDR Objective – Shift in Focus
 National Defense Strategy & QDR addresses threats:
 Traditional
 Irregular
 Disruptive
 Catastrophic
 QDR themes
 Irregular, asymmetric operations
 Joint and combined operations
 Integrated, interdependent forces
 CONUS-based expeditionary forces
 Information, knowledge, intelligence
 Massing effects
Recent military lessons learned continue to validate the QDR
Copyright © 2006 Boeing. All rights reserved. -#RBEO92
2
Systems Engineering Development
 Systems Engineering:
Complicated
Complex
the process by which a customer’s needs
are satisfied through the conceptualization, design, modeling, testing,
implementation, and operation of a working system.
Enterprise SE
System of Systems
Systems Engineering Management
Product Systems Engineering
Systems Theory
1950-1960s
 Challenge
1970s
1980s
1990s
2000s
2010+
– Increasing complexity as the field moves to integrated and
interoperable enterprise systems
* Dr. Hal Sorenson Professor & Faculty Director - Architecture-based Enterprise Systems Engineering
(AESE) - Joint Graduate Program - Jacobs School of Engineering & Rady School of Management University of California, San Diego
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
3
The Network Revolution
 Shared mental model of the force structure
 Facilitates rapid, adaptive, responsive behavior
 Requires “system of systems” development approach
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
4
Net-Centric Operations - Beyond Connectivity
THE BATTLEFIELD
Connectivity
Collaborative
Environment
Situational
Awareness for
Decision Making
Collaborative
Environment
Situational
Awareness for
Decision Making
Mission
Effectiveness
THE BUSINESS
1
Integrated
Technology
Development Labs
MC2
Candidate Stakeholder
F-22
C4ISR
J-UCAS
AWACS
ABL
DEMPC
FCS
Wichita
Philadelphia
C4ISR
FABFAB-T
C4ISR
BIC
EAST
F-15
Mesa
F-18
Huntsville
JTRS
BIC
2
Boeing Integration
Center
Satellite
C-17
3
Virtual Warfare Center
Connectivity
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
Mission Assurance/
Program Success
5
SoS in Platform Centric Versus
Network Centric Environments
Evolution of The SoS with the
insertion of NCO technologies
and CONOPS
Network Centric
Environment
Platform Centric
Environment
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
6
What is a “System-of-Systems”?
 Definition*:
A System-of-Systems (SoS) created for Net-Centric Operations (NCO) is a “supersystem” comprised of elements that are themselves complex, independent systems
which interact to achieve a common goal.
 Common Characteristics:
– The component systems achieve well-substantiated purposes in their own right even if
detached from the overall
systema large, complex system
Not just
– The components systems are managed in large part for their own purposes
systems
rather than the purposesIndependent
of the whole
– It exhibits behavior, including emergent behavior, not achievable by the component systems
acting independently
Value of the net
– Component systems, functions, and behaviors may be added or removed during its use
Dynamic environment
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
*After Maier, Sega, Levis
7
Enterprise Mission Example
CONOPS
SoS Architecture
Enterprise Mission implemented with SoS
CONOPS Drives Architecture
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
8
SoS Context View
Enterprise
Mission 1
Mission 2
Mission 3
Mission 4
Mission 5
SoS
#1
SoS
#2
SoS
#3
SoS
#4
SoS
#5
System 1 System 2 System 3 System 4 System 5 System 6 System 7 System 8 System 9 System 10 System 11 System 12
(Enterprise
Infrastructure
System)
Capabilities
• The Enterprise is an organization (or collection of organizations) with a welldefined objective and set of missions
• Missions are performed by means of a SoS, which employs capabilities
provided by systems, to achieve effects in the environment
• Systems provide capabilities to perform missions
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
9
Many-to-Many and Dynamic Complexity
The challenge of SoS development is to define balanced solutions in an
environment of many-to-many relationships
– A Mission can require many capabilities
– A Capability can support many missions
– A System can provide many capabilities and support many missions
– Many Systems can provide the same or similar capabilities
– Some Capabilities are provided by collaboration of multiple Systems
– Systems may be controlled and developed by many different stakeholders
Balancing resources and capabilities involves iterative analysis of
the Enterprise / Campaign level structure and missions using
analysis, modeling, simulation and experimentation
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
10
SoS Engineering Must Address Dynamic Complexity and Distributed
Ownership and Control of Systems
Enterprise
SoS model in traditional
Systems Engineering approach*
Mission 1
Mission 2
Mission 3
Mission 4
Mission 5
SoS
#1
SoS
#2
SoS
#3
SoS
#4
SoS
#5
SoS
System
1
System
2
System
3
Element 2A
Element 2B
Element 2C
Subsystem 2Ba
Subsystem 2Bb
Subsystem 2Bc
*presented in university training material
System 1 System 2 System 3 System 4 System 5 System 6 System 7 System 8 System 9 System 10 System 11 System 12
(Enterprise
Infrastructure
System)
Capabilities
SoS Engineering needs to address
decomposition of the SoS
requirements/functions to systems not
owned by the SoS that can vary and
evolve over time. Requires both top
down and bottom up methodology.
Traditional Systems Engineering hierarchy treats system elements as stable
and controlled by the decomposition and allocation of requirements and
functions from a higher tier element. COTS reuse is an example of where it must
make exception.
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
11
Benefits for Robust Systems Engineering*
SoS
#2
Missions
SoS
#3
SoS
#5
System
Capabilities
Capability Capability Capability Capability
1
2
3
4
Robust System
• Supports multiple missions
• Interoperable with other
systems in SoS
• Provides multiple capabilities
• Able to adapt as missions,
CONOPS, and environment
changes
Illustration
Deterrent
Surveillance Deterrent
B-58
Nuclear
Bomb
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
CAS
Strategic
Precision
Weapons
Sensors
Tactical
B-52
Speed
Nuclear
Bombs
*Dr. Sambur, former SAF-AQ
Convent.
Bombs
Cruise
Missiles
Range
Payload
12
DoD Framework--One Architecture …Three Views
Operational View
Describes and interrelates the
operational elements, tasks and
activities, and information flows
Systems View
Describes and associates systems
and their interconnections and
performance to the operational view
and its requirements.
Technical View
Describes the minimal set of rules
governing the arrangement,
interaction, and interdependence of
system parts or elements.
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
13
SoS Modeling & Sim (M&S) Grand Challenges
SoS complexity (Can we get the interactions right?)
– Standardized SoS-level metrics across missions
– Improved integration of M&S into the development process
– Improved test, verification & validation tools
Emergent effects & behavior (Can we model unpredicted effects?)
– Agile methods reduce the “model-analyze-remodel” simulation cycle
– Agent-based simulation captures emergence and adaptation
Human decision making (Can we predict group behavior?)
– Social modeling – Culture and influence on decision-making
– Cognitive Modeling – Information interpretation and decision-making
 Virtual Modeling – immersive environment for human-in-the-loop
feedback
– Effects-based operations modeling – Interaction of diplomatic,
information, military & economic interventions
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
14
SoSE Provides the Framework for NCO
Implementation
Architecture
Centric
• DOD Architecture Framework
• Unified Modeling
Language (UML)
• Net Ready KPPs
• Capabilities Based
• Evolutionary Development
Modeling &
Simulation
Elements of SoSE
Interoperability
Standards
• Levels of Information Interoperability for
Net-Centric Operations (LIINCO)
• Strategic Architecture Reference Model (SARM)
• NCO Industry Consortium (NCOIC)
• DoD IT Standards Registry
• DoD Guidance: NCOW-RM, NCES, NESI
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
• Simulation Becomes
Product
• Life Cycle Affordability
• Constructive & Virtual
• Agent Based SoS
Effectiveness
Cutting Edge
Technologies
& Capabilities
• Phantom Works
• Strategic Investments
• Key Suppliers
• Universities
15
Levels of Information Interoperability for
Net-Centric Operations (LIINCO)
Legacy Systems can
evolve to provide some
limited interoperability
in the near term…
with a realistic path to
becoming nodes in a
fully interoperable
System-of-Systems
Level 1
Interoperability
Level 4
Interoperability
Level 3
Interoperability
Level 2
Interoperability
Data exchange and
some fusion
capability / complex
node activity
Extensive fusion
capability / theaterwide operational
control
Fusion capability and
multi-node tasking
giving it area C2
capability
( MLI )
Can receive and read
some data
Effecter Node
SYSTEM 1
SYSTEM 2
SYSTEM 1
SYSTEM 3
SYSTEM 5
Sensor Node
SYSTEM 1
Level 0
Interoperability
No Generic
Interoperability
Copyright © 2007 Boeing. All rights reserved. – #RBEO92
SYSTEM 2
COMMS Interface S4C/S3B
COMMS Interface S1C/S3B
SYSTEM 1
EXTERNAL
CONNECTION
Logistics NODE
SYSTEM 4
16
The Future: Integrated Functionality through
Integrated Technologies
Integrated
Technologies
Need to Achieve this Level of Integration
in Future Products
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
17
SoS Technology Interchanges
Technology
•
•
•
•
Large Scale Arch. Modeling & Analysis
Sensors
Communications
Data and Text Mining
•
•
•
•
•
•
•
•
•
•
•
•
•
Optimization
Information Integration
Operations Research
Intelligent Agent Technology
Automation and Decision Aids
Modeling & Simulation
Integrated Systems Modeling
Knowledge Management
Probability and Statistics
Signal and Image Processing
Visualization and Interaction
Collaboration
Data Fusion
•
•
•
•
•
Situational Awareness Systems
Grid Computing
Data Distribution
Performance and Scalability
Model driven architecture
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
Examples
CMU, USC, UC Berkeley
University of Colorado
IBM, Cisco, Internet-2, …
Wisconsin, JPL, Cal Tech, Illinois-Urbana, IBM,
CMU, Inxight, U. Tenn., Clearforest
UCSD, Rice, Northwestern, U. of Stuttgart
U. Wisconsin, Adobe, UC Berkley, Oracle, IBM
Ga. Tech, MIT, Cornell, Stanford, UC Berkley
Univ. of West Florida, IBM Zurich
UCSD, ASI, Sterling Software
University Central Florida, CACI, SAIC
Hitachi, University of Texas, Cal Tech
UNM, U. Wash., UT-Austin, USC, Stanford
University of Washington
University of Colorado
UNC, U. Utah, Caltech, IBM, Microsoft, Stanford
IBM/Lotus, Microsoft, Xerox, Mich., CMU, Lancaster UK
SUNY, Alphatech, Orincon, Wagner & Associates,
BTG, Raytheon
DARPA, DoD
IBM, NASA, Argonne, VCSD
UCSD
IBM, Hitachi
CMU, IBM
18
System of Systems Integration is the Future


The need for better decision making and efficiency is driving
more integration among military and commercial products
Managing the dynamic complexity of system of systems is a
challenge being addressed with robust systems engineer
principles.
Copyright © 2007 Boeing. All rights reserved.- #RBEO92
19
BOEING is a trademark of Boeing Management Company.
Copyright
Copyright ©
© 2006
2007 Boeing.
Boeing. All
All rights
rights reserved.
reserved.
20