THE MIP INFORMATION MODEL - dodccrp.org · Organisation Materiel Person Facility Feature Object...

THE MIP INFORMATION MODEL

A Platform-Independent Reference Data Modelfor a Future Interoperability Solution

Nico Bau

nico.bau@fkie.fraunhofer.de

OUTLINE

Multilateral Interoperability Programme (MIP)

Introducing the MIP Information Model

Restructuring the Model

Additional Transformations

Summary and Outlook

Multilateral Interoperability Programme

NATION A

NATIONAL

C2IS (A)

MCI JC3IEDMJC3IEDM

NATIONAL

C2IS (B)

INTERNATIONALMIP SOLUTION

(Lingua Franca)NATION B

SpecificationsSOPsDocuments

MAPPING MAPPING

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

OUTLINE

Summary and Outlook

History of the MIP Information Model

Generic Hub 4ATCCIS

LC2IEDM 2.2MIP Block 1

C2IEDM 6.15MIP Block 2

JC3IEDMMIP Block 3

NCDM RMNATO

MIP/NDAG-MergerMOA 2004-02-04

View Models

MIMNo baseline released yet

PersonOrganisation Materiel FeatureFacility

Object

Extensive hierarchy of battle space objects (147 subclasses)

Classification

Status

The MIMCore Elements

Object

Location

GeometricVolumeLine Point Surface

2..* {ordered}

Location hierarchy

2D and 3D geometry

Including relative and absolute coordinate systems

Object

Location

Action

Event Task

2..* {ordered}

0..*{bag}

Object

Location

Action

Event Task

ActionObjective

ActionResource

ActionEffect

2..* {ordered}

0..*{bag}

+focuses

+requirements

+observedResults 0..*

Object

Capability

Comment

GroupAccount

Location

Action

Event Task

ActionObjective

ActionResource

ActionEffect

2..* {ordered}

0..*{bag}

0..1 0..*

+focuses

+requirements

0..10..1

Object

AddressAffiliation

Holding

ObjectTypeEstablishment

Capability

Comment

GroupAccount

Location

Action

Event Task

ActionObjective

ActionResource

ActionEffect

Holding

1 0..*

2..* {ordered}

0..*{bag}

0..1 0..*

+focuses

+requirements

0..10..1

Object

AddressAffiliation

Holding

Capability

Comment

GroupAccount

Location

Action

Event Task

ActionObjective

ActionResource

ActionEffect

OrganisationStructureCandidateTargetList RuleOfEngagement

Holding

1 0..*

2..* {ordered}

0..*{bag}

0..1 0..*

+focuses

+requirements

0..*0..1

0..10..1

+constraints 0..*

Object

AddressAffiliation

Holding

Capability

Comment

GroupAccount

Location

Action

Event Task

ActionObjective

ActionResource

ActionEffect

PlanOrder PlanOrderComponentOrganisationStructureCandidateTargetList RuleOfEngagement

Holding

1 0..*

2..* {ordered}

0..*{bag}

0..1 0..*

+focuses

+requirements

0..*{bag}

1 0..*{ordered} +topic 0..1

+subTopic 0..*

0..*0..1

0..10..1

+constraints 0..*

The MIMInformation Groups and Metadata

Appraisal

Assessment

AssessmentGroup

Correlation

InformationGroupMetadata

OperationalInformationGroup

ReportingData

TemporalValidity

OtherInformationGroup

ReferenceDescription

SecurityClassification

0..10..*

informationClassification

rawInformation

MIM by Numbers

Comparison JC3IEDM 3.0.2ER Model

MIM 1.0UML Model

Business Rules 14,764 MIRD DB Records

310OCL Constraints -98%*

Entities / Classes 273 326 +19%

Attributes 898(1472 incl. key attributes) 873 -3%

(-41%)Associations(incl. subtyping) 397 394 -1%

Code Types 470 400 -15%

*some OCL constraints map to multiple MIRD DB records

OUTLINE

Summary and Outlook

TaskFormationConv oy

«rate»+ daySpeedRate [0..1]+ nightSpeedRate [0..1]

«dimension»+ dayVehicleGapDimension [0..1]+ nightVehicleGapDimension [0..1]+ packetGapDimension [0..1]

«duration»+ haltDuration [0..1]

«count»+ packetSizeCount [0..1]

Organisation

ObjectItem

«text»+ nameText

TaskFormationType

«code»+ categoryCode

MilitaryOrganisationType

«code»+ serviceCode

GovernmentOrganisationType

«code»+ mainActivityCode [0..1]

OrganisationType

«code»+ commandAndControlCategoryCode [0..1]+ commandFunctionIndicatorCode

«text»+ descriptionText [0..1]

ObjectType

«code»+ decoyIndicatorCode

«text»+ nameText

ObjectItemStatus

«code»+ boobyTrapPresenceCode [0..1]+ emissionControlCode [0..1]

OrganisationStatus

«code»+ availabil ityCode [0..1]+ cbrnDressStateCode [0..1]+ commandAndControlRoleCode [0..1]+ commitmentStatusCode [0..1]+ fireModeCode [0..1]+ operationalStatusCode+ operationalStatusQualifierCode [0..1]+ readinessCode [0..1]+ reinforcementCode [0..1]+ reserveIndicatorCode [0..1]+ trainingCode [0..1]+ usageStatusCode [0..1]

«quantity»+ radiationDoseQuantity [0..1]

«duration»+ readinessDuration [0..1]

«invariant»{inv: self.classification->forAll(ot | ot.oclIsTypeOf(TaskFormationType) and ot.oclAsType(TaskFormationType).categoryCode = Enumerations::TaskFormationTypeCategoryCode::MLCNVY)}

+classification

1..*10..*

Aligning Hierarchies

Conv oy

Organisation

ObjectItem

«text»+ nameText

TaskFormationType

OrganisationType

ObjectType

«text»+ nameText

ObjectItemStatus

OrganisationStatus

MilitaryOrganisation

GovernmentOrganisation

Conv oyType

TaskFormation

Gov ernmentOrganisationStatus

MilitaryOrganisationStatus

TaskFormationStatus

Conv oyStatus

10..* 0..*

+classification

Aligning Hierarchies

Conv oy

Organisation

ObjectItem

«text»+ nameText

TaskFormationType

OrganisationType

ObjectType

«text»+ nameText

ObjectItemStatus

OrganisationStatus

Conv oyType

TaskFormation

TaskFormationStatus

Conv oyStatus

10..* 0..*

+classification

Making the Model Timeless and Sourceless

Only one classification at a given time provided by a single

reporter

Maximum one status at a given time provided by a single

reporter

Conv oy

Organisation

ObjectItem

«text»+ nameText

TaskFormationType

OrganisationType

ObjectType

«text»+ nameText

ObjectItemStatus

OrganisationStatus

Conv oyType

TaskFormation

TaskFormationStatus

Conv oyStatus

10..* 0..*

+classification

Merging Hierarchies

0..1 1<<code,status>>

<<code,status>>

<<quantity,status>>

<<duration,status>>

<<code,type>>

<<text,type>>

Merging Hierarchies

MilitaryConv oy

«quantity»+ packetSizeQuantity [0..1]

TaskFormation

«code, type»+ serviceCode

Gov ernmentOrganisation

«code, type»+ mainActivityCode [0..1]

Organisation

«code, status»+ availabil ityCode [0..1]+ cbrnDressStateCode [0..1]+ commandAndControlRoleCode [0..1]+ fireModeCode [0..1]+ operationalStatusCode+ operationalStatusQualifierCode [0..1]+ readinessCode [0..1]+ reinforcementCode [0..1]+ trainingCode [0..1]

«indicator, status»+ isCommittedIndicator [0..1]+ isInReserveIndicator [0..1]+ isInActionIndicator [0..1]

«quantity, status»+ radiationDoseQuantity [0..1]

«duration, status»+ readinessDuration [0..1]

Object

«name»+ name

Eliminating Business Rules (1)

ConsumableMaterielBiologicalMateriel

«code, type»+ categoryCode+ persistencyCode [0..1]+ subcategoryCode [0..1]

«enumeration»BiologicalMaterielCategoryCode

«codeValue, enum» BACTRL TOXIN TOXMAT VIRAL

«enumeration»BiologicalMaterielSubcategoryCode

«codeValue, enum» CHLMYD RCKETS

BiologicalMateriel.categoryCode BiologicalMateriel.subcategoryCode

Bacterial ChlamydiaRickettsiae[NULL]

Toxic Industrial Material [NULL]

Toxin [NULL]

Viral [NULL]

Valid combinations of Domain Values for BiologicalMateriel

Eliminating Business Rules (2)

«code, type»+ persistencyCode [0..1]

Bacterial

«code, type»+ categoryCode [0..1]

OtherBiologicalMateriel

«code, type»+ categoryCode

«enumeration»BacterialCategoryCode

«enumeration»OtherBiologicalMaterielCategoryCode

«codeValue, enum» TOXIN TOXMAT VIRAL

OUTLINE

Summary and Outlook

MDA Transformation Tool Chain

MIM as a starting point

Step 1:

Create a subview

Step 2:

Re-introduce versioning if required

Re-introduce ObjectType hierarchy if required

Step 3:

Perform additional transformations if required

Step 1: Create Conformant Subview

A conformant subview does not violate constraints of the MIM

(i.e. follows Liskov substitution principle)

Business Rules

May be dropped if they result in a constant expression

Mandatory Attributes

May be set to read-only with a given default value

Mandatory Associations

Have to be included

Optional Attributes / Associations

May be ignored

Step 2: Re-introduce versioning and ObjectType (1)

If the exchange of history is required, versioning needs to be modeled

Entities vs. value objects

A generic superstructure will enable versioning of entities by allowing multiple instances per identifier

If the exchange of type information is required, Object and ObjectType will be split again

All <<type>> attributes will be moved to the ObjectType hierarchy

All <<typerole>> association ends will be moved to the ObjectType hierarchy

Step 2: Re-introduce versioning and ObjectType (2)

Materiel

«status, code»+ bodyColourCode [0..1]+ demolitionStatusCode [0..1]+ markingCode [0..1]+ markingColourCode [0..1]+ operationalStatusCode+ operationalStatusModeCode [0..1]+ operationalStatusQualifierCode [0..1]+ usageStatusCode [0..1]

«indicator, status»+ isInReserveIndicator [0..1]

«dimension, type»+ issuingHeightDimension [0..1]+ issuingLengthDimension [0..1]+ issuingWidthDimension [0..1]

«identifier»+ lotIdentifier [0..1]+ serialNumberIdentifier [0..1]

«type, identifier»+ reportableItemIdentifier [0..1]+ stockNumberIdentifier [0..1]

«code, type»+ supplyClassCode [0..1]

Object

«status, code»+ boobyTrapPresenceCode [0..1]+ emissionControlCode [0..1]

«code, status»+ hostil ityStatusCode [0..1]

«indicator, type»+ isDecoyIndicator

«name»+ name

«type, name»+ typeName

Object

«status, code»+ boobyTrapPresenceCode [0..1]+ emissionControlCode [0..1]

«code, status»+ hostil ityStatusCode [0..1]

«name»+ name

ObjectType

«indicator, type»+ isDecoyIndicator

«type, name»+ typeName

Materiel

«status, code»+ bodyColourCode [0..1]+ demolitionStatusCode [0..1]+ markingCode [0..1]+ markingColourCode [0..1]+ operationalStatusCode+ operationalStatusModeCode [0..1]+ operationalStatusQualifierCode [0..1]+ usageStatusCode [0..1]

«indicator, status»+ isInReserveIndicator [0..1]

«identifier»+ lotIdentifier [0..1]+ serialNumberIdentifier [0..1]

MaterielType

«dimension, type»+ issuingHeightDimension [0..1]+ issuingLengthDimension [0..1]+ issuingWidthDimension [0..1]

«type, identifier»+ reportableItemIdentifier [0..1]+ stockNumberIdentifier [0..1]

+instance

0..*{subsetsinstance}

+classification

1{subsetsclassification}

+classification

+instance

Split Object and ObjectType

Step 3: Additional Transformations (Example)

Bacterial

«code, type»+ categoryCode [0..1]

«code, type»+ categoryCode

«enumeration»BacterialCategoryCode

«enumeration»OtherBiologicalMaterielCategoryCode

«codeValue, enum» TOXIN TOXMAT VIRAL

ChangeDiscriminatorCodesToSubtypes

Changes all categoryCode attributes to subclasses

Would add 3300 new subclasses throughout the model

Chlamydia Rickettsiae

Bacterial

ToxicIndustrialMaterial Viral

OUTLINE

Summary and Outlook

Summary and Outlook (1)

MIP Information Model Version 1.0

UML Class Model, operational content of JC3IEDM 3.0.2

Timeless, sourceless

Attributes stereotyped according to UN/CEFACT’s Core Components Data Type Catalogue

Metadata and Grouping split from core elements

Available at http://mipcee-svn.lsec.dnd.ca/DEV/SVN/PIM/tags/Releases/MIM%201.0

MIP Information Model Version 1.1

Work in progress

Will include all changes from JC3IEDM 3.1.4 (MIP Block 3.1)

Summary and Outlook (2)

MDA Tools

Java based tools to perform additional transformations on the MIM

Documentation of tools and best practices still missing

Available athttp://mipcee-svn.lsec.dnd.ca/DEV/SVN/SRC/trunk/CPProcessor

Further investigation into different transformations ongoing

Questions?Comments?

Thank you very much for your attention

We would like to thank all active participants of MIP

THE MIP INFORMATION MODEL - dodccrp.org · Organisation Materiel Person Facility Feature Object...

Documents

Varnish Documentation - err.no · 5.4 VCL Expressions ... how report bugs etc. ... Varnish Documentation, Release 3.0.2

16th ICCRTS Paper ID 155 - dodccrp.org

Joint Command, Control, and Consultation Information Exchange Data Model (JC3IEDM)

CloudStack 3.0.2 Release Notes · CloudStack 3.0.2 Release Notes For CloudStack Version 3.0.2 Revised May 17, 2012 8:33 PM Pacific

The Entrepreneurial Roller Coaster - dodccrp.org€¦ · The Entrepreneurial Roller Coaster The Entrepreneurial ... • Building the “balanced” team ... • Structure of the market

Neuron ESB 3.0.2 Release! More great things from the

GSM 09.10 - Version 3.0.2 - European Digital Cellular

ANNEX O. EXTENSIBLE MARKUP LANGUAGE (XML ... Document Library/99...2009/05/14 · JC3IEDM - Annex O - DMWG 20090514 Edition 3.0.2 O1. BACKGROUND O1.1 The use of the Extensible Mark-up

List of Products supported by ESAP 3.0.2 for PCS 8.2Rx ...€¦ · List of Products supported by ESAP 3.0.2 for PCS 8.2Rx / PPS 5.3Rx and later Contents Introduction: ... 187 avast!

The Role of Social Media in Crisis - dodccrp.org

IP Momentum Confidential Cisco IP Phone Provisioning GuideSylantro- hosted Service Release 3.0.2 1/06/05

OpenGL ES 3.0.2 (April 8, 2013) - Khronos Group

IBM Monitoring and Diagnostics Tools - Health Center 3.0.2

Documento de Informações Periódicas DIOPS Versão 3.0.2 DIOPE - Diretoria de Normas e Habilitação das Operadoras

OVERVIEW OF THE JOINT C3 INFORMATION EXCHANGE DATA … Document Library/04... · 2016-12-08 · JC3IEDM - Overview - IPT3 V3.1.4 MULTILATERAL INTEROPERABILITY PROGRAMME (MIP) OVERVIEW

VMware Infrastructure 3.0.2 Update 1 for Dell™ PowerEdge ... · This document helps you to deploy VMware® Infrastructure 3.0.2 on Dell™ PowerEdge™ systems and provides information

BILGI AS 2018-03-23 SIRKET SUNUMU › upload › Node › 237 › files › BILGI_AS... · 2018-03-23 · MIP (Multilateral Interoperability Programme) uyumluluğu NATO JC3IEDM ve

SDE 3.0.2 System Requirements - ArcGIShelp.arcgis.com/en/previous_versions/system_requirements/...SDE 3.0.2 System Requirements This PDF contains system requirements information, including

Mobilkommunikation: Medienzugriff Mobilkommunikation Kapitel 3 : Medienzugriff Motivation SDMA, TDMA, FDMA Aloha Reservierungsverfahren 3.0.2 Kollisionsvermeidung,

User's Manual for Nuance 3.0.2