1 of 33

An�‘MDO-enabled Architecture’ �for C2 systems

Having the right functionality with the right data at the right time at the right place at the fingertips of the right person

Dr. ir. Mark Peerdeman

Co-chair, NATO RTG SAS-IST 171

TNO

​

Franziska Kollmann

Researcher, NATO RTG SAS-IST 171

Fraunhofer FKIE

​

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

2 of 33

An�‘MDO-enabled Architecture’ �for C2 systems

Having the right functionality with the right data at the right time at the right place at the fingertips of the right person?

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

3 of 33

An�‘MDO-enabled Architecture’ �for C2 systems

Having the right functionality with the right data at the right time at the right place at the fingertips of the right person?

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

4 of 33

An�‘MDO-enabled Architecture’ �for C2 systems

Having the right functionality with the right data at the right time at the right place at the fingertips of the right person?

Lets’s ask AI…

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

5 of 33

M

NORTH ATLANTIC TREATY ORGANIZATION

SCIENCE & TECHNOLOGY ORGANIZATION

6 of 33

M

NORTH ATLANTIC TREATY ORGANIZATION

SCIENCE & TECHNOLOGY ORGANIZATION

7 of 33

An�‘MDO-enabled Architecture’ �for C2 systems

Having the right functionality with the right data at the right time at the right place at the fingertips of the right person?

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

8 of 33

NATO RTG SAS-IST 171

M

A G E N C Y

L. Aceti (Leonardo, ITA)

A. Eikelboom (TNO, NLD) (Co-chair)

R. El Abdouni Khayari (IABG, DEU)

F. Kollmann (Fraunhofer, DEU)

S. Lockwood (NCIA, NATO)

M. MacLean (DRDC, CAN)

M. Peerdeman (TNO, NLD) (Co-chair)

L. Pigeon (DRDC, CAN)

K. Tsetsos (UniBwM/Sicyon Risk, DEU)

T. van der Venne (TNO, NLD)

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

9 of 33

Part 1: Context�Part 2: Multi domain operations�Part 3: Architectural principles�Part 4: Architectural outcome

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

10 of 33

Part 1: Context

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

11 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 11

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

12 of 33

Part 2: Multi domain operations

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

13 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 13

Survey NATO SAS-IST 171

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

14 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 14

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

15 of 33

Scenario based approach

NATO UNCLASSIFIED

10/21/2024 | PAGE 15

KADRI+ Scenario – Vignettes

LEGEND:

DECISION: DECISIONS TAKEN BY JFC ON THE BASIS OF AVAILABLE INFORMATION

INFORMATION: INFORMATION FLOW FROM TO

RESULT: Outcome of previous decisions

REQUEST: Request posed to JFC/NRF

USE CASE

DATE TIME

EVENT

Stake holder

Impact domain

Effect dimension

NR

UC 4�Response to Kadri insurgency

24.4.25

 

07:00

• Mass forced migration of Neotonian refugees from Grey State commences as response to NATO air campaign

• Local authorities report 50.000 arrivals overnight, civilians panicked by shots

• Five border crossings are overrun by refugees, humanitarian crisis develops

• Groups of refugees present in entire area of operations moving West

 

• REQUEST: Neotonian government requests Air and Space assets from JFC to support local forces in determining refugee flows and insurgent movements

 

• DECISION: ISR area to be extended to affected regions to determine refugee flows and insurgent movements in AO and report

• INFORMATION: ISR data shared with Neotonian civilian authorities through liason

• DECISION: Establish common operational picture (COP) for refugee management operation NATO C2IS system to share unclassified ISR and Ops data with Neotonian civilian C2IS. Neotonian civilian C2IS to provide NATO C2IS with relevant sensor and intel data to form recognized COP via use of middleware

• INFORMATION: ISR data relevant to refugees crisis now shared with Neotonian civilian authorities through C2IS

• …….

Political, Security, Army, Airforce, Space

Land, Space

Cognitive, Physical

11

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

16 of 33

Harmonisation levels

NATO UNCLASSIFIED

10/21/2024 | PAGE 16

Scenario step

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

17 of 33

Part 3: �Architectural goals, principes and requirements

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

18 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 18

Theory

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

19 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 19

principles

goals

requirements

constraints

constraints

goals

goals

principles

Theory

Reality

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

20 of 33

VAULTIS goals (DoD)

NATO UNCLASSIFIED

10/21/2024 | PAGE 20

Visible�Information of particular interest should be easily publishable by, discoverable by, or advertised to, authorized users and partners as appropriate, where and when needed.

Accessible�Authorized users should be able to obtain information when they need it, including push mechanisms towards subscribed users. Access should only be permitted if compliant with laws, regulations and policies..

Understandable�Information should have a clear and well defined and standardized semantic meaning. Information should be baselined and inventoried with relevant information on purpose, ownership, points of contact, security, standards, interfaces, limitations, and restrictions on use.

Linked�Information should be linked such that relationships and dependencies can be uncovered and maintained and that connections between disparate sources can be made.

Trustworthy�Information should be subjected to data quality management, protection, lineage and tracing so the user can assess the risks of using the information.

Interoperable�Properly exchanging data between systems and maintaining semantic as well as syntactic interoperability are critical for successful decision-making and co-operation with partners. This interoperability extends in MDO context towards all instruments of power utilized.

Secure�Data needs to be protected at the appropriate level when in rest, in motion and in use. Access, use and disposition of data are fully audited.

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

21 of 33

Added FAIR principles

NATO UNCLASSIFIED

10/21/2024 | PAGE 21

Visible - Findable�Information of particular interest should be easily publishable by, discoverable by, or advertised to, authorized users and partners as appropriate, where and when needed.

Accessible - Accessible�Authorized users should be able to obtain information when they need it, including push mechanisms towards subscribed users. Access should only be permitted if compliant with laws, regulations and policies..

Understandable�Information should have a clear and well defined and standardized semantic meaning. Information should be baselined and inventoried with relevant information on purpose, ownership, points of contact, security, standards, interfaces, limitations, and restrictions on use.

Linked�Information should be linked such that relationships and dependencies can be uncovered and maintained and that connections between disparate sources can be made.

Trustworthy�Information should be subjected to data quality management, protection, lineage and tracing so the user can assess the risks of using the information.

Interoperable - Interoperable�Properly exchanging data between systems and maintaining semantic as well as syntactic interoperability are critical for successful decision-making and co-operation with partners. This interoperability extends in MDO context towards all instruments of power utilized.

Secure�Data needs to be protected at the appropriate level when in rest, in motion and in use. Access, use and disposition of data are fully audited.

Reusable�Data should be well described (Understandable) so it could be replicated and/or combined in different settings (Linked).

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

22 of 33

DoD Data principles

NATO UNCLASSIFIED

10/21/2024 | PAGE 22

Data is a strategic asset�

Collective data stewardship�

Data ethics�

Data collection�

Data access and availability�

Data for AI training�

Data fit for purpose�

Design for compliance�

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

23 of 33

DIB Commandments for software

NATO UNCLASSIFIED

10/21/2024 | PAGE 23

Make computing, storage, and bandwidth abundant to DoD developers and users�

All software procurement programs should start small, be iterative, and build on success ‒ or be terminated quickly�

Budgets should be constructed to support the full, iterative life-cycle of the software being acquired�

Adopt a DevOps culture for software systems�

Automate configuration, testing, and deployment of software to enable critical updates to be deployed in days to weeks, not months or years�

Every purpose-built DoD software system should include source code as a deliverable�

Every DoD system that includes software should have a local team of

DoD software experts who are able to modify or extend the software through source code or API access�

Only run modern operating systems that are receiving (and utilizing)

regular security updates for newly discovered security vulnerabilities�

Data should always be encrypted unless it is part of an active computation

All data generated by DoD systems ‒ in development and operations ‒ should be stored, mined, and made available for machine learning

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

24 of 33

MDO specific principles

NATO UNCLASSIFIED

10/21/2024 | PAGE 24

The architecture needs to be able to handle different configurations of harmonisation levels. Not all cooperations will require the same harmonisation levels at the same time. This includes interoperability between JIMP parties and other Instruments of Power (IoPs) in the MDO spectrum. This principle includes data, data sources and information models (ontologies) as well as functionality sharing (i.e., using C2 services from other parties) and timely response to enable true collaboration.

The architecture needs to be independent of the C2, management or authority structure, including cases where the military are not in primary command. Flexible connection of services and service configurations could therefore be required for a mission.

The architecture needs to be able to handle changing configurations in harmonisation levels over time or when the context changes. It needs to be agile in order to cater for changing requirements during the operation. In our paper a scenario is used to illustratie these agility requirements.

F

SAS 143 harmonization options

Scenario analysis

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

25 of 33

NATO UNCLASSIFIED

10/21/2024 | PAGE 25

Harmonization levels

FAIR

Agile SW dev

VAULTIS

DATA principles

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

26 of 33

Part 4: �Architectural outcome

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

27 of 33

Architectural outcome

NATO UNCLASSIFIED

10/21/2024 | PAGE 27

​

Data centric

​

Service oriented

​

Domain knowledge driven

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

28 of 33

Architectural outcome

NATO UNCLASSIFIED

10/21/2024 | PAGE 28

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

29 of 33

TNO architectural blocks

NATO UNCLASSIFIED

10/21/2024 | PAGE 29

The Knowledge engine

  • Ask for (or subscribe to) information without the need to know where the data components reside,
  • Find out what data is missing, ask a human,
  • Connect different data models (ontologies),
  • (future) query in natural language.

​

M

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

30 of 33

Fraunhofer architectural blocks

NATO UNCLASSIFIED

10/21/2024 | PAGE 30

Dynamic COI-services concept for the NCDF Data Lake

​

  • Based on a harmonized semantic reference model, the “MIP Information Model” (MIM) -> Core Model
  • Flexibly adapt to new requirements -> Extended Submodel
  • Transformation Service makes sure that COI information and the harmonized core information can be exchanged at the same time

​

​

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

31 of 33

COPDCM experiments

NATO UNCLASSIFIED

10/21/2024 | PAGE 31

  • COPDCM (Common Operation Picture for Disaster and Crisis Management) project aiming at improving civil-military cooperation through the creation of a common, recognized and shared operational picture during crisis situation.
  • IT solution/architecture to be developed should be able to be used both during any possible operation and for the purpose of training and mission rehearsal.

​

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

32 of 33

COPDCM experiments

NATO UNCLASSIFIED

10/21/2024 | PAGE 32

  • The use of newly implemented services as well as the implementation of existing standards (e.g. OTH Gold, WMTS) were decisive for the establishment of such interoperability.
  • Esp. C2SIM standard (STANREC) provided a very nice vehicle for creating interoperability between different C2s from two different domains as well as between the C2 world and a fictitious simulated environment.

​

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

33 of 33

So…�

Mark.Peerdeman@tno.nl�Franziska.Kollmann@fkie.fraunhofer.de

email

NATO UNCLASSIFIED

10/21/2024 | PAGE 33

  • NATO STO RTG SAS-IST 171:
    • The survey,
    • The MDO cube,
    • The harmonisation levels
    • The scenario
  • Use in architecture development
  • Several actual components from the research institutions
  • Captured in presentations, papers and a (coming) report

​

F

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION

NORTH ATLANTIC TREATY ORGANIZATION�SCIENCE & TECHNOLOGY ORGANIZATION