Welcome to Systems-of-Systems Subgroup (a subgroup of EWICS

Mission statement

The Systems-of-Systems subgroup of EWICS aims at providing a guideline for building, safe systems-of-systems.


A system of systems (SoS) consists of at least two dedicated, independent systems which interact to provide more functionality/performance than the union of the individual functionalities.

A dedicated system is a system, that has its own purpose (in particular not auxiliary but stand alone) and goal. In particular, dedicted systems in one SoS are typically/possibly developed independently (of each other), owned by different entities) and/or are designed for different environments/working contexts.

The context of a (dedicated) system is a descripton of properties/attributes of the environment which are relevant for the system.

Here, independent means the ability of working alone (with respect to the other dedicate subsystems of the SoS).

Aspects of SoS

When combining SoS out of dedicated system, then

  • ... the context of all dedicated subsystems might need to be changed/extended.
  • ... the requirements may differ from the union of requirements of the dedicated subsystems.
  • ... responsibilities become unclear.
  • ... controllable systems might become uncontrollable, stable systems might become unstable.

Active members:

If you want to be actively involved, please add yourself to the following list, or give us a call at dvla uk support.

  • Frank Ortmeier, Otto-von-Guericke-Universität Magdeburg
  • Francesca Saglietti
  • Amund Skavhaug
  • Maritta Heisel
  • Erwin Schoitsch
  • Christoph Schmitz
  • Friedemann Bitsch
  • Wolfgang Ehrenberger
  • Zdzislaw Zurakowski
  • Tim Kelly
  • Uwe Becker
  • Mario Trapp
  • Friedemann Bitsch
  • Martin Rothfelder
  • Odd Nordland
  • Philippa Ryan
  • ...

Registering for the Wiki: Either use the "register" button or this link (in case you want to invite somebody)

Short term goals (next meetings)

  • Set frame/structure for SoS guideline.
  • Identify person responsible for filling in initial versions for each section.

Workshop in Spring

Organisation and Planning

Results of the Workshop

Mid-term goals

A guideline for developing dependable SoS!

Minutes from our meetings

The minutes of our previous meeting: protocols

Related groups and scientists

Please EXTEND these lists:

Related groups =

  • George Despotou, Dependable Systems-of-Sytems, York (
  • Systems Engineering Guide for Systems of Systems (DOD US and MITRE)
  • Definition by J. Clarke
  • Introduction Cybernetics by Ashby
  • Defintion by H. Kopetz
  • Organizers of Dependable SoS workshop (EDCC): Richard Payne (Newcastle University, UK ), Zoe Andrews (Newcastle University, UK)), Uwe Schulze (Bremen University, DE)
  • J. Fitzgerald
  • INCOSE SoS WG: Alan Harding/BAESYSTEMS (Alan.D.Harding@…); Judith Dahmann/Mitre? Corp. (jdahmann@…)

Related papers

Related papers

Related definitions

Levels of system of system engineering

IESE suggestion/classification (tbd): three levels of building systems of systems

  • Level A: Experts build a composite system out of dedicated subsystems.
  • Level B: A non-expert builds the composite system in the field.
  • Level C: The composite system is without human intervention being composed out of dedicated subsystems based on a pre-defined autonomous composition mechanism.

(wording by AS+FB+ON)

Related Standards

  • AAMI/UL2800 "Interoperable Medical Device Interface Safety" upcoming UL standard for systems of systems
  • ASTM 2761 "Medical Devices and Medical Systems — Essential safety requirements for equipment comprising the patient-centric integrated clinical environment (ICE)" — Part 1 - 9 also known as MD PnP Standard
  • ISO/IEEE 11073 "Health informatics - Point-of-care medical device communication"
  • General Standard IEC60601 (like the others above) refers to IEC80001

Starting Points

For a complete list of local wiki pages, see TitleIndex.

Last modified 5 months ago Last modified on 01/07/19 18:25:36