Multilateral Interoperability Programme Date: 29 Sep 06 Unclassified MIP @ 1999-20061 CIO-G6 JC3IEDM Briefing 9 November 2006 This Multilateral

Date: 29 Sep 06Unclassified

MIP @ 1999-2006 1

Multilateral Interoperability Programme

CIO-G6 JC3IEDM Briefing

9 November 2006www.mip-site.org

This Multilateral Interoperability Programme (MIP) Standard Briefing been reviewed and is hereby “Approved” by the Heads of Delegation of participating members. The information contained herein remains the property of the MIP Participants; as such, its release to nations or agencies, who are not themselves participants in the Multilateral

Interoperability Programme, including the media and general public is agreed however, unauthorised amendment of the information is not permitted. Use of MIP information, from this or any other MIP document, is entirely at the Users risk. Furthermore, if information contained within this document is used, appropriate acknowledgement to the MIP should

be made.

Unclassified MIP © 1999-2006 2

Multilateral Interoperability ProgrammeOutline

• Introduction• Aim• MIP Defined• The MIP Concept • Organisation • Governance / Objective / Advantages• JC3IEDM Structure – Select Views• Stakeholders / Documentation• Summary of Programme.


Multilateral Interoperability ProgrammeIntroduction (1)

• Looking for a “Common Understanding” of the Battlespace.

• “Interoperability of information” is essential.

• Information across national and language boundaries.

• From tactical to operational and strategic levels.

• Interaction with NGO.


Multilateral Interoperability ProgrammeIntroduction (2)

• The “Shared Awareness” implies “Shared Information”.

• A common language.• AIM: Deliver an assured

capability for interoperability of information

• Combined joint operations• C2IEDM & JC3IEDM

(STANAG 5525).• Covers War, CRO and DAT.


Multilateral Interoperability ProgrammeAim

• “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.”


Multilateral Interoperability ProgrammeMIP Defined (1)

• What it is and what it provides:

– Materiel / Combat developer forum.

– Mature Process. – Consensus-based Technical

Specs.– Venue for international

interoperability testing– Coordinates synchronization of

materiel fielding plans– System-independent capability

based on information interoperability



ConceptEnd-State

Effective C2 for international operationsEffective C2 for international operations

Shared Tactical Picture

NationalImplementation

(Nation A)

NationalImplementation

(Nation A)

NationalImplementation(Nation B)

NationalImplementation(Nation B)

AutomaticExchange Mechanism

CommonData

Model

CommonData

Model

StaffOfficers(Nation B)

StaffOfficers(Nation A)

Commander(Nation A)

Commander(Nation B)

COLLABORATION

COMMON UNDERSTANDING



ConceptOp. Requirements• Hierarchy and Prioritisation.



ASSOCIATE MEMBERS

AUS JCCS, BCSS LTU TAVVIS

AUT PHOENIX POL SZAFRAN

BEL ISIS PRT SICCE

BUL FICIS ROU SIAAB

CZE GF-TCCS SVN SITAWARE

FIN FINACCIS SWE ISMARK,SLB

GRC HARCCIS ACT BiSC - AIS

HUN HAVIR JFC

FULL MEMBERS

CAN TacC2IS

DNK DACCIS

FRA SICF, SIR

DEU HEROS-2/1

ITA SIACCON

NLD ISIS

NOR NORTaC/

NORCCIS

ESP SIMACET

TUR TACCIS

GBR ATacCS/

ComBAT

USA MCS

OrganisationMembers

*Country codes according NATO STANAG 1059 Ed 8.


Multilateral Interoperability ProgrammeOrganisation

MIP Steering Group(MSG)

Programme Management Group(PMG)

Systems Engineering& ArchitectureWorking Group

(SEAWG)

ConfigurationControl

Working Group

(CCWG)

NDAG

Data ModellingWorking Group

(DMWG)

Multi-Disciplinary Working Parties (MDWPs)

Chair

Deputy

OperationalWorking Group

(OWG)

Test & Evaluation

Working Group

(TEWG)

Chair Vice Chair

Chair Vice Chair


Multilateral Interoperability ProgrammeGovernance

• MSG

• PMG

• OWG

• SEAWG

• DMWG

• Priorities set by the PMG

• Technical solutions – 100% agreement

• Conflict resolution at the PMG level



Objective of the Initiative

To define the To define the minimumminimum operational and operational and technical requirements to be included technical requirements to be included within system specification which will within system specification which will allow national C2 systems to interoperate allow national C2 systems to interoperate by the automatic exchange of data i.e. by the automatic exchange of data i.e. Level 5 of System Interconnection.Level 5 of System Interconnection.



ADVANTAGES OF JC3IEDM

• Maximum reuse providing cost avoidance • Relatively simple, understandable structure with

broad applicability• Central concepts have been stable for 12 years• Multinational pedigree• General, based on military experience (Army Tactical

Command and Control Information System - ATCCIS); Easy to extend in response to operational data requirements

• Joint interfaces (Air Tasking Order (ATO)(NATO) Chemical Biological Radiological Nuclear (CBRN)(NATO) Maritime Mine Warfare (MMW)(NATO))



JC3IEDM Independent Entities

VERTICAL-DISTANCE

REFERENCE

GROUP-CHARACTERISTIC

COORDINATE-SYSTEM

AFFILIATION ADDRESS

ACTION

CONTEXT

OBJECT-ITEMOBJECT-TYPE LOCATION

REPORTING-DATA

RULE-OF-ENGAGEMENT

CAPABILITY

CANDIDATE-TARGET-LIST

• GH – LC2IEDM – C2IEDM – JC3IEDM

• Automated C2 Interface Exchange Mechanism To Support Liaison and Automation– Exchange Of Orders/Graphics– Holdings/Status Information

• e.g., AD Weapons Control & Running Status

• Operational exchange standards use a common vocabulary consisting of 176 information categories that include over 1500 content elements.

• Information Exchange Data Model• Serves as a Hub for functional areas• CRO & Joint IERs


Multilateral Interoperability ProgrammeThe JC3IEDM Kernel

Everything is directly derived from this kernel or supports it.

+ Unknown + Unknown



A Fundamental RelationshipAttribute Level

provides-applicable-information-for /is-referenced-to

is-classified-as

P

is-used-as-a-classification-for

OBJECT-ITEM-TYPE

object-item-id (FK)object-type-id (FK)object-item-type-index

reporting-data-id (FK)

REPORTING-DATA

reporting-data-id

reporting-data-accuracy-codereporting-data-category-codereporting-data-counting-indicator-codereporting-data-credibility-codereporting-data-reliability-codereporting-data-reporting-datereporting-data-reporting-timereporting-data-source-type-codereporting-data-timing-category-codereference-id (FK)reporting-data-reporting-organisation-id (FK)

OBJECT-ITEM

object-item-id

object-item-category-codeobject-item-nameobject-item-alternate-identification-text

OBJECT-TYPE

object-type-id

object-type-category-codeobject-type-dummy-indicator-codeobject-type-name


Multilateral Interoperability ProgrammePerson structure

is-identified-by /identifies

is-recognised-as-having /is-ascribed-to

PERSON-IDENTIFICATION-DOCUMENT

person-id (FK)person-identification-document-index

person-identification-document-codeperson-identification-document-number-text

PERSON-LANGUAGE-SKILL

person-id (FK)person-language-skill-index

person-language-skill-category-codeperson-language-skill-general-proficiency-codeperson-language-skill-listening-proficiency-level-codeperson-language-skill-reading-proficiency-level-codeperson-language-skill-speaking-proficiency-level-codeperson-language-skill-writing-proficiency-level-code

PERSON

person-id (FK)

person-birth-datetimeperson-blood-type-codeperson-gender-codeperson-professing-indicator-code


Multilateral Interoperability ProgrammeAffiliation

hashas

is-referenced-inis-ascribed-to

affiliation-category-code

AFFILIATION-RELIGION

affiliation-id (FK)

affiliation-religion-code

AFFILIATION-GEOPOLITICAL

affiliation-id (FK)

affiliation-geopolitical-code

AFFILIATION-FUNCTIONAL-GROUP

affiliation-id (FK)

affiliation-functional-group-codeaffiliation-functional-group-name-text

AFFILIATION-ETHNIC-GROUP

affiliation-id (FK)

affiliation-ethnic-group-code

AFFILIATION

affiliation-id

affiliation-category-code

OBJECT-ITEM-AFFILIATION

object-item-id (FK)affiliation-id (FK)object-item-affiliation-index

reporting-data-id (FK)

OBJECT-TYPE-AFFILIATION

object-type-id (FK)affiliation-id (FK)

OBJECT-ITEM

object-item-id

object-item-category-codeobject-item-name-text

OBJECT-TYPE

object-type-id

object-type-category-codeobject-type-decoy-indicator-codeobject-type-name-text


Multilateral Interoperability ProgrammeFacility Structure

APRON

apron-id (FK)

apron-weight-bearing-capacity-quantity

ROAD

road-id (FK)

road-category-coderoad-shoulder-width-coderoad-traffic-density-countroad-weather-condition-category-coderoad-quality-code

RAILWAY

railway-id (FK)

railway-track-gauge-coderailway-track-countrailway-train-density-countrailway-block-distance-dimensionrailway-sleeper-density-dimensionrailway-gross-trailing-load-quantityrailway-maximum-speed-raterailway-traction-system-coderailway-signal-system-coderailway-signal-system-efficiency-code

RUNWAY

runway-id (FK)

runway-lighting-presence-indicator-coderunway-weight-bearing-capacity-quantityrunway-pavement-classification-number-countrunway-pavement-type-coderunway-pavement-subgrade-category-coderunway-pavement-maximum-tyre-pressure-coderunway-pavement-evaluation-method-code

NETWORK

network-id (FK)

network-category-codenetwork-subcategory-codenetwork-architecture-codenetwork-channel-countnetwork-maximum-capacity-ratenetwork-minimum-capacity-ratenetwork-means-codenetwork-security-policy-codenetwork-set-number-count

BRIDGE

bridge-id (FK)

bridge-longest-span-length-dimensionbridge-span-countbridge-usage-code

FACILITY

facility-id (FK)

facility-category-codefacility-primary-construction-material-codefacility-base-identification-code-textfacility-height-dimensionfacility-length-dimensionfacility-width-dimensionfacility-major-building-type-id (FK)

facility-category-code

AIRFIELD

airfield-id (FK)

airfield-air-traffic-control-presence-indicator-codeairfield-hangar-area-quantityairfield-instrument-landing-system-presence-indicator-codeairfield-international-civil-aviation-organisation-codeairfield-visual-navigational-aid-indicator-code



Organization Structure

has-for-support-a-specific /is-constituted-to-support

ORGANISATION-TYPE

organisation-type-id (FK)

organisation-type-category-codeorganisation-type-command-function-indicator-codeorganisation-type-command-and-control-category-codeorganisation-type-description-text

UNIT-TYPE

unit-type-id (FK)

unit-type-category-codeunit-type-arm-category-codeunit-type-arm-specialisation-codeunit-type-supplementary-specialisation-codeunit-type-general-mobility-codeunit-type-qualifier-codeunit-type-size-codeunit-type-principal-equipment-type-id (FK)unit-type-supported-military-organisation-type-id (FK)

CIVILIAN-POST-TYPE

civilian-post-type-id (FK)

civilian-post-type-category-code

GOVERNMENT-ORGANISATION-TYPE

government-organisation-type-id (FK)

government-organisation-type-category-codegovernment-organisation-type-main-activity-code

GROUP-ORGANISATION-TYPE

group-organisation-type-id (FK)

group-organisation-type-category-code

PRIVATE-SECTOR-ORGANISATION-TYPE

private-sector-organisation-type-id (FK)

private-sector-organisation-type-category-codeprivate-sector-organisation-type-main-activity-code

organisation-type-category-code

MILITARY-ORGANISATION-TYPE

military-organisation-type-id (FK)

military-organisation-type-category-codemilitary-organisation-type-service-code

EXECUTIVE-MILITARY-ORGANISATION-TYPE

executive-military-organisation-type-id (FK)

executive-military-organisation-type-category-code

MILITARY-POST-TYPE

military-post-type-id (FK)

military-post-type-category-codemilitary-post-type-rank-code

TASK-FORMATION-TYPE

task-formation-type-id (FK)

task-formation-type-category-code

government-organisation-type-category-code

military-organisation-type-category-code



MIP Adoption & Stability

National C2ISNational C2IS

NATOCorporate Data Model

NATOCorporate Data Model

NATO Force Goal

NATO Force Goal

NATO Standardisation

Agreement

NATO Standardisation

Agreement

BiSC AISLand Functional

Services

BiSC AISLand Functional

Services

NATOC3 TechnicalArchitecture

NATOC3 TechnicalArchitecture

NATO PolicyNATO Policy

HRF(L) / NRFHRF(L) / NRF



US JC3IEDM Users & Stakeholders(Partial List)

• CIO/G-6: JC3IEDM foundation for US Army Data Strategy• G3: Has officially endorsed the JC3IEDM• GIG

– J6I has identified JC3IEDM / MIP addresses Key Interface Profile #17– Identified as applicable to User Defined Operational Picture (UDOP) COI

• ABCS – Current US MIP implementation program is Maneuver Control System– Implementation on-going in MCS 6.4 GE– Planned software reuse - other ABCS programs

• Army Future Combat Systems (FCS)– MIP being leveraged to satisfy coalition interoperability requirements– JC3IEDM integral to FCS data strategy (with extensions)

• Shared Tactical Picture - Ground (STP-G)– Germany (GE), Italy (IT), Sweden (SW), and the United Kingdom (UK)

• Blue Force Tracking (BFT) COI• Global Force Management (GFM) • Chemical, Biological, Radiological, Nuclear Community• DISA XML Registry: MIP XML in Coalition Namespace• DMSO: JC3IEDM adopted as basis for Modeling & Simulation Data Strategy• Strike COI investigating implementation• NECC (JC2) investigating implementation• Simulation to C4I Interoperability OIPT (5 Work Plans totaling $1.388M)



JC3IEDM Documentation

www.mip-site.org

• JC3IEDM-Overview-UK-DMWG-Edition3.0.pdf

• JC3IEDM-Main-UK-DMWG-Edition3.0.pdf (600 pgs)

• JC3IEDM-Annexes-UK-DMWG-Edition3.0.pdf (1400+ pgs)

• JC3IEDM-MIRD-UK-DMWG-Edition3.0-(Access2000).mdb

• JC3IEDM-Model-UK-DMWG-Edition3.0.ER1 (in ERwin Version 3.5.2)

• JC3IEDM-LogicalView-UK-DMWG-Edition3.0.pdf


Multilateral Interoperability ProgrammeSummary

• Firm Foundations– Proven Concept

• NATO Buy-in (NDAG MoA)• National Commitment Clear Roadmap to the Future• Return of investment by:

– Manageability– Legacy-tolerant– Evolutionary– Standard



MIP Website www.mip-site.org

Documents

Multilateral Interoperability Programme Date: 29 Sep 06 Unclassified MIP @ 1999-20061 CIO-G6 JC3IEDM Briefing 9 November 2006 This Multilateral