Systems-of-Systems CoE: Systems in Context
Changing threat situations increase the need for flexibility and adaptability in the way warfighters configure and apply suites of systems.
Systems Operate in a Broader Context than They Used To
With the adoption of a net-centric approach to information management, developers are increasingly recognizing that systems operate in a broader context today than in the past. Most importantly, changing threat situations increase the need for flexibility and adaptability in the way warfighters configure and apply suites of systems to respond to change. The notion of “Systems-of-Systems” (SoS) is becoming a critical perspective in thinking about systems. Examples of SoS, either existing or proposed, can be found in all societal sectors: air and road transportation, power grids, healthcare, water management, industrial processes, building complexes, critical infrastructures, enterprise systems, and smart homes and cities.
In 2006, the Deputy Under Secretary of Defense for Acquisition and Technology charged the Systems and Software Engineering Directorate to develop guidance for Systems Engineering of SoS, recognizing the value of systems engineering as a key enabler of successful systems acquisition and the growing importance of systems interdependencies in the achievement of warfighter capability.
Most military systems today are part of an SoS even if they are not explicitly recognized as such. Operationally, the DoD acts as an SoS as the battle space commander brings together a mix of systems in an operation to meet mission objectives. SoS systems engineering typically focuses on the evolution of capability over time, with initial efforts working to enhance the way current systems work together, anticipating change in internal or external effects on the SoS, and eventually adding new functionality through new systems or changes to existing systems.
The Context for Applying Systems Engineering Processes
- Emerging Tech shall translate SoS capability objectives into high-level SoS requirements.
- Emerging Tech shall understand the constituent systems and their relationships over time.
- Emerging Tech shall assess the extent to which SoS performance meets capability objectives over time.
- Emerging Tech shall develop, evolve, and maintain an architecture for the SoS.
- Emerging Tech shall monitor and assess potential impacts of changes on SoS performance.
- Emerging Tech shall address SoS requirements and solution options.
- Emerging Tech shall orchestrate upgrades to SoS.
Aligned to the International SoS Standards
ISO/IEC/IEEE 21839
Provides a definition of SoS and constituent system. This standard provides a set of critical considerations to be addressed at key points in the life cycle of systems created by humans, and refers to a constituent system that will interact in a system of systems as the system of interest (SOI). These considerations are aligned with ISO/IEC/IEEE 15288 and the ISO/IEC/IEEE 24748 framework for system life cycle stages and associated terminology.
ISO/IEC/IEEE 21840
Guidelines for the utilization of ISO/IEC/IEEE 15288 in the context of System of Systems (SoS) Engineering. While ISO/IEC/IEEE 15288 applies to systems (including constituent systems), this document provides guidance on application of these processes to SoS. It is intended to be used in conjunction with ISO/IEC/IEEE 15288, 21839 and 21841.
ISO/IEC/IEEE 21841
Taxonomy of Systems of Systems. The purpose of this standard is to define normalized taxonomies for systems of systems (SoS) to facilitate communications among stakeholders.
Integrating Systems that Were Never Designed to Talk?
Let’s talk about the architecture.