top of page

System of Systems Thinking: What Is It and Why Does It Matter?

4 days ago
2 min read

One drone is a system. Add a whole fleet of them, plus air traffic control, ground crews, regulations and live weather data, and you've got something else entirely: a system of systems. Spotting the difference is one of the most useful skills a systems engineer can build.

So, what is a system of systems?

A system of systems is a group of independent systems that work together to do something none of them could do alone. The key word is independent. Each part (often called a constituent system) has its own purpose, its own owner, and usually its own timeline. They've been brought together, or have grown together, to deliver a bigger goal.

What does it look like in real life?

•     Air traffic management: aircraft, airports, radar, communications and controllers, all run by different organisations.

•     A smart city: transport, energy and emergency services sharing data to keep things moving.

•     A rail network: trains, signalling, stations and timetables, each with its own owners and upgrade cycles.

What makes it different?

Systems of systems tend to share a few traits:

•     Independent parts: each system can work on its own and often does.

•     Different owners: no single team or organisation controls everything.

•     Emergent behaviour: the whole does things the individual parts can't, some helpful and some surprising.

•     Constant change: parts are upgraded, replaced or added over time.

Why does system of systems thinking matter?

Because problems love to hide in the gaps. Every system can pass its own tests and the combination can still fail, simply because nobody looked at the whole.

Thinking in systems of systems nudges you to ask better questions early. What's the bigger goal all these systems are serving? Who owns each system, and each interface between them? What happens elsewhere when one part changes? And how will we know the whole thing works?

Where does systems engineering come in?

This is where good systems engineering earns its keep: agreeing the overall purpose, defining the interfaces, planning how the whole will be verified and validated (not just the parts), and keeping everyone talking as things change. It's the same discipline as planning a single system, just with more people, more owners and more moving parts.

Ready to take it further?

Already doing the work and want to refresh your knowledge, validate your experience, or even earn an official INCOSE qualification for it? Take a look at our courses.

New graduate, or completely new to systems engineering? We've got courses designed for you too. Start here.

 

 
 
 

Recent Posts

See All

Comments


bottom of page