Definition of System of Systems

A system of systems is a collection of independent systems that interact to provide capabilities that none of the individual systems can provide alone.

The constituent systems are useful in their own right, may be independently managed, and may continue to operate even when separated from the broader system of systems.

Core Definition

A system of systems exists when multiple systems are integrated, coordinated, or networked to achieve a broader purpose.

The individual systems may have:

• Their own stakeholders
• Their own objectives
• Their own funding
• Their own operators
• Their own development life cycles
• Their own governance
• Their own sustainment plans
• Their own evolution paths

The system of systems emerges from the relationships and interactions among these constituent systems.

Example

An airport transportation capability may involve:

• Air traffic control systems
• Aircraft systems
• Airport operations systems
• Baggage handling systems
• Security systems
• Passenger information systems
• Ground transportation systems
• Weather systems
• Airline scheduling systems
• Emergency response systems

Each system has independent value. Together, they enable a larger transportation capability.

Characteristics of a System of Systems

Common characteristics include:

Operational Independence

Each constituent system can operate independently and provide useful capability outside the system of systems.

Managerial Independence

Each constituent system may be owned, managed, funded, or operated by different organizations.

Evolutionary Development

The system of systems evolves over time as constituent systems are added, removed, modified, upgraded, or replaced.

Emergent Behavior

The broader capability emerges from interactions between constituent systems.

Geographic or Organizational Distribution

Constituent systems may be distributed across locations, organizations, networks, or jurisdictions.

Types of Systems of Systems

Systems of systems may be described in several ways.

Directed System of Systems

A directed system of systems has a central authority responsible for managing the system of systems and its constituent systems toward a common purpose.

Acknowledged System of Systems

An acknowledged system of systems has recognized objectives, management, and resources, but constituent systems retain some independent ownership and decision-making authority.

Collaborative System of Systems

A collaborative system of systems has no single central authority. Constituent systems voluntarily cooperate to achieve shared or compatible objectives.

Virtual System of Systems

A virtual system of systems has no central management authority and may not have an explicit shared purpose. Capability emerges from interactions among systems.

Systems Engineering Challenges

Systems of systems create additional engineering challenges because the systems engineer may not control all constituent systems.

Challenges include:

• Conflicting stakeholder priorities
• Independent funding and schedules
• Legacy systems
• Incomplete interface control
• Data incompatibility
• Cybersecurity exposure
• Governance complexity
• Emergent behavior
• Operational uncertainty
• Continuous evolution
• Verification and validation difficulty

Interfaces in a System of Systems

Interfaces are especially important in a system of systems.

Interfaces may include:

• Data interfaces
• Command and control interfaces
• Physical interfaces
• Service interfaces
• Organizational interfaces
• Policy interfaces
• Human decision interfaces
• Timing and synchronization dependencies

Interface control is often more difficult because constituent systems may belong to different organizations or suppliers.

Requirements in a System of Systems

Requirements for a system of systems often focus on capability, interoperability, resilience, information exchange, governance, and operational outcomes.

Unlike a single system, the system of systems may not be designed from a clean starting point. It may include existing systems with fixed constraints.

Requirements engineering must therefore address:

• Constituent system constraints
• Legacy limitations
• Interface agreements
• Operational scenarios
• Evolution paths
• Cross-system risks
• Governance responsibilities

Verification and Validation

Verification and validation of a system of systems can be difficult because:

• Not all constituent systems may be available at the same time
• Operational scenarios may be complex
• Emergent behavior may not appear until late integration
• Some systems may change independently
• Test environments may not fully represent reality

Approaches may include:

• Modeling and simulation
• Incremental integration
• Interface verification
• Scenario-based validation
• Operational exercises
• Digital engineering environments
• Mission thread analysis

System of Systems vs. Large System

A large system is not automatically a system of systems.

A system of systems is distinguished by the independence of its constituent systems. If the constituent elements do not have meaningful operational or managerial independence, the arrangement may be better understood as a complex system rather than a system of systems.

Relationship to Systems Engineering

Systems Engineering is essential for systems of systems because it provides the methods needed to understand context, interfaces, dependencies, stakeholders, risks, emergent behavior, and evolving capability.

However, Systems Engineering for a system of systems often places more emphasis on:

• Governance
• Interoperability
• Architecture frameworks
• Mission threads
• Interface agreements
• Evolutionary planning
• Capability management
• Cross-organizational coordination

Key Takeaway

A system of systems is not just a bigger system. It is a set of independent systems that interact to create broader capability, often under distributed ownership and continuous evolution.