1 of 21

Alexander Güldner1, Nico Bau1, Michael Gerz1, Franziska Kollmann1, Olivier Meyer², Christian Persie1, Magdalena Dechand1

1Fraunhofer FKIE, Germany, ²Airbus Defence and Space, France

Enhancing Operational Effectiveness through Capturing and Exchanging Capability Information between C2IS

29th ICCRTS, London

Formatvorlagen des Textmasters bearbeiten

Zweite Ebene

      • Dritte Ebene
        • Vierte Ebene
          • Fünfte Ebene

2 of 21

Agenda

  1. MIP Information Model (MIM)
  2. Operational Capabilities in the MIM
  3. A Redesign of Taxonomies
  4. Conclusion / Outlook

© Fraunhofer FKIE

Page 2

26.09.2024

3 of 21

What is MIP/MIM?�

MIP (Multilateral Interoperability Programme)

    • International standardisation body comprising 24 nations, NATO, and the European Defence Agency
    • Its main goal is to enable seamless communication between heterogenous C2IS from different nations

MIM (MIP Information Model)

    • UML-based semantic reference model standardises how information is exchanged and interpreted in the C2 domain
        • Essential for multinational operations, ensuring partners interpret and share information consistently
        • Communities of Interest (COIs) can adopt the MIM for developing interoperability specifications for their processes

© Fraunhofer FKIE

Page 3

26.09.2024

4 of 21

What constitutes the MIM?

© Fraunhofer FKIE

Page 4

26.09.2024

UML Class Model

Constraints

Free-Text Documentation

Meta Model

Class Diagrams

Examples

5 of 21

An Overview of MIM Concepts

© Fraunhofer FKIE

Page 5

26.09.2024

6 of 21

Capabilities in the MIM

© Fraunhofer FKIE

Page 6

26.09.2024

7 of 21

Capabilities in the MIM

© Fraunhofer FKIE

Page 7

26.09.2024

8 of 21

Issues Identified in the Current MIM Structure

1. Overgeneralisation

    • Capabilities can be applied too broadly (e.g., assigning “MaximumAltitude” to a ground vehicle)

2. Structural Issues

    • Flat lists of concepts (e.g. OperationalCapability includes 93 operational literals)

3. Object Attributes Representing Capabilities

    • Many capabilities are tied to specific objects (e.g. Harbour class: over 80% of attributes are capabilities, creating unnecessary overlap and complexity)
    • The Capability taxonomy is explicitly excluded from current MIP specifications!

© Fraunhofer FKIE

Page 8

26.09.2024

9 of 21

Re-Classification of Battle Space Object Attributes��

    • Out of a total of all 729 BSO attributes, 174 attributes have identified as capabilities
          • 27 attributes are still under consideration for their potential classification as capabilities

© Fraunhofer FKIE

Page 9

26.09.2024

10 of 21

Symmetry-Driven vs. Function-Driven Approach��

© Fraunhofer FKIE

Page 10

26.09.2024

SYMMETRY-DRIVEN

    • Object-Centric
    • Precise for individual objects

    • Redundant across objects
    • Difficult to adapt to new needs

FUNCTION-DRIVEN

    • Role-centric
    • Scalable / Adaptable
    • Multi-object capabilities

    • Lacks object-level granularity
    • Needs careful mapping to ensure relevance

11 of 21

Use Cases

© Fraunhofer FKIE

Page 11

26.09.2024

Real-time visualisation of assets and resources for decision making, helping commanders assess potential threats and support.

Situation Assessment

Detailed resource information, including unit types, equipment, limitations, and operational readiness. Useful for planning and logistics.

Capability Sheets

Mission planning based on desired outcomes and required capabilities, ensuring the right combination of resources for mission success.

Capability-Based Planning

Analysis of terrain, weather, and threats to determine the safest and most efficient movement routes for forces and resources.

Optimal Route Research

Evaluation of harbour capabilities for large-scale transport, including docking, cargo handling, security, and accessibility for operational planning.

Harbour Facility Selection

12 of 21

A Holistic Analysis of the Function-Driven Approach���

Why Function-Driven?

    • Focuses on operational outcomes, offering adaptability and scalability
    • Aligns with mission objectives
    • Ensures multi-object compatibility

© Fraunhofer FKIE

Page 12

26.09.2024

13 of 21

A Holistic Analysis of the Function-Driven Approach���

© Fraunhofer FKIE

Page 13

26.09.2024

Analysis of over 3000 MIM concepts

14 of 21

A Holistic Analysis of the Function-Driven Approach���

© Fraunhofer FKIE

Page 14

26.09.2024

Determine if a concept is Exclusively, Partially, or Non-Functional

15 of 21

A Holistic Analysis of the Function-Driven Approach���

© Fraunhofer FKIE

Page 15

26.09.2024

Determine whether a concept is influenced by organisational, technological, or design-related factors

16 of 21

A Holistic Analysis of the Function-Driven Approach���

© Fraunhofer FKIE

Page 16

26.09.2024

Categorise concepts according to their functional roles and further refine them into detailed subcategories.

17 of 21

A Holistic Analysis of the Function-Driven Approach���

© Fraunhofer FKIE

Page 17

26.09.2024

Assesses whether the functional characterisation and the concept class are accurately aligned

18 of 21

Functions and Capabilities Mapping

A new preliminary structure

    • Dichotomy: MilitaryFunction and CivilianOrDualFunction
    • (Sub-)categories define capability scope and mission roles for each function

© Fraunhofer FKIE

Page 18

26.09.2024

MilitaryFunction

CommandSupport

Combat

CombatSupport

CombatServiceSupport

SupportCapability

Logistics

HandlingCapability

MaintenanceCapability

StorageCapability

Transportation

Medical

MovementSupport

CivilianOrDualFunction

LawEnforcement

IndustrialProduction

Research

Telecommunications

Excerpt of new preliminary structure

19 of 21

Conclusion / Outlook

The function-driven approach looks promising, as key challenges such as overgeneralisation, flat concept lists, and capabilities outside of the current taxonomy have been addressed!

Need for further review

    • Further analysis is needed to assess whether all eligible elements in the MIM can be effectively integrated into the new taxonomy

Collaboration with Stakeholders

    • Engage relevant stakeholders in an iterative process to validate and adapt the taxonomy to evolving mission requirements and real-world use cases

© Fraunhofer FKIE

Page 19

26.09.2024

20 of 21

Thank you for your attention!

21 of 21

Alexander Güldner (M.A.)

Information Technology for Command and Control

alexander.gueldner@fkie.fraunhofer.de

Fraunhofer Institute for Communication, �Information Processing and Ergonomics FKIE

Fraunhoferstr. 20 | 53343 Wachtberg

www.fkie.fraunhofer.de

Contact