a platform-independent jc3iedm as a semantic...

© Fraunhofer FKIE

A platform-independent JC3IEDM as a semantic reference for future interoperability solutions

Nico Bau [email protected]

2011 BML Research Symposium Boston, USA – 8 April 2011

© Fraunhofer FKIE

Table of Contents

  Introduction   MIP Baseline 3   JC3IEDM 3.0.2

  JC3IEDM PIM   Motivation

  PIM Restructuring   Key characteristics   Overview of changes

  The new PIM   Colorful Pictures

  Summary

© Fraunhofer FKIE

Introduction

© Fraunhofer FKIE

Multilateral Interoperability Programme

“The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to battalion, or lowest appropriate level, in order to support multinational (including NATO), combined and joint operations and the advancement of digitization in the international arena.“

MIP has approved Baseline 3 in October 2009

© Fraunhofer FKIE

JC3IEDM

  Joint Consultation, Command, and Control Information Exchange Data Model

  NATO ratification as STANAG 5525   Latest version: JC3IEDM 3.0.2

  Plans & Orders, ATO, MMW, CBRN, …

  Complex data model based on generic core concepts

  Entity relationship model   Semantic definitions

  Business Rules   Free-text documentation

© Fraunhofer FKIE

JC3IEDM PIM

© Fraunhofer FKIE

Motivation

  JC3IEDM has been transformed from a small, generic hub into a comprehensive data model

  Configuration Management   Growing size and complexity results in configuration management challenges   Tracking and applying changes is laborious   Faster response to user requirements

  From operational requirement to the field   Keep existing information exchange services stable

  Incremental delivery of independent capabilities   Modular interoperability solution

0

200

400

600

800

1000

1200

1400

1600

LC2IEDM 2.2

C2IEDM 6.15e

JC3IEDM 3.0.2

JC3IEDM PIM

Classes

Attributes

Non-Key Attr

Code Types

Associations

Generalizations

© Fraunhofer FKIE

Motivation (2)

  Entity-Relationship model in IDEF1X is platform-specific   Database concepts, e.g., key attributes, discriminator codes for sub-typing   Not perfectly suited to other application areas

  Resolve well-known problems/workarounds, e.g.,   Deletion/update of information   Grouping of information   Archiving

  Make the model independent from a specific exchange mechanism

  Generalize existing concepts

  Provide a sound basis for the definition of capability- and COI-specific sub-models

© Fraunhofer FKIE

Restructuring the “conceptual” Model

© Fraunhofer FKIE

Restructured PIM Key Characteristics

  Modular

  It should be easy to define meaningful sub-models

  Different sub-models should be comparable and checked for consistency (Tool support)

  Separation of Concerns

  Grouping

  Every information could be “groupable”

  Metadata

  Every information could have Metadata

  Core

  Extending the operational content of the JC3IEDM should be easy

© Fraunhofer FKIE

Restructured PIM Key Characteristics (2)

  Stateless

  The restructured PIM cannot describe the evolution of objects over time.

  Sourceless

  The restructured PIM does not handle conflicting information from different reporters.

  Contextless

  The restructured PIM does not take into account the fact that e.g. current situation and planning situation can coexist in a C2 system.

This allows for a stricter and unambiguous specification

© Fraunhofer FKIE

Modularity of Classes

e.g.: ReportingData

before after

© Fraunhofer FKIE

Modularity of Associations

e.g.: ObjectItemAssociation

before after

© Fraunhofer FKIE

Modularity of Enumerations

e.g.: SubsurfaceVesselType

before after

© Fraunhofer FKIE

Navigability

  Defines the way an association can be queried efficiently

  Gives a hint on the direction an association should be read

  Allows for easier construction of e.g. XML schemata

before after

© Fraunhofer FKIE

Composition

  Defines one class as a part of another class

  Makes the lifecycle of the part dependent on the “whole”

  Gives a hint on value objects vs entity objects

  Makes the part non-shareable

before after

© Fraunhofer FKIE

Multiplicities

Since the restructured PIM removes some reasons for many-to-many associations, some associations can be defined stricter

before after

© Fraunhofer FKIE

Separation of Concerns - Grouping Information

© Fraunhofer FKIE

Separation of Concerns - Metadata

© Fraunhofer FKIE

Separation of Concerns - Core Elements

© Fraunhofer FKIE

Further Restructuring & Cleanup

  Role Names on Associations

  UML-ify the Model

  Aligning Hierarchies

  Remove structural differences in Item, Type, and Status hierarchies

  Formal Business Rule

  Specified in the Object Constraint Language (OCL)

  Feedback from BML-Community

  Revise ActionTemporalAssociation

  ...

© Fraunhofer FKIE

Summary (1)

  Restructured PIM

  Addresses issues, constraints, and workarounds

  Concise

  Understandable

  Former operational concepts are maintained

  Includes navigability and composition as “new” logical concepts

  Model Driven Architecture

  Derive lower level PIMs and PSMs from the restructured PIM

  Aspects such as Grouping, Metadata, Logging, Modification,... are introduced as needed, but always rule-based!

© Fraunhofer FKIE

Summary (2)

  Modularity   Supports incremental delivery of new capabilities/services

  Smaller, but clearer specified capabilities   In the context of NAF

  JC3IEDM is used as a semantic reference

  Restructured PIM with all changes approved so far is available at   http://mda.cloudexp.com/DEV/SVN/PIM/trunk/

  How can the BML community improve and employ the JC3IEDM PIM?   Look at the restructured PIM – it’s free!   Do the operational & structural aspects match with your expectations?   Grab the PIM tools from the website and produce your favourite sub-model(s)!   For help and feedback do not hesitate to contact us!

a platform-independent jc3iedm as a semantic...

Documents