Ministry of Defence / DMO / WSB / LA / C2 Support Centre

C2SC/MIP DEM

MIP - DEM Gateway 2.0 User - SUM

UNCLASSIFIED

Document identification:
Code: DEM 01.02
Version: 0.0.2
Status: Draft

©
Copyright Ministry of Defence
 PREFACE
x= New version of the application, documentation included.
‘y’ and ‘z’ will be set to 0 in the version coding. Status is Final.
Version history
y= Temporary release of the documentation based on approval
Version Date Author(s) Description: Status
C2SC/S&T; ‘z’ will be set to 0 in the version coding.
0.0.1 03012006 M. Fuchs Initial version. Pictures are not Draft Status is Draft.
correct and to illustrate z= New version of the documentation, ready for internal approval
actions only. by the project team only. Status is Draft.
0.0.2 15012006 M. Fuchs Draft. Comments Draft
development added. Added
section “Show MIP Document references
Exchangeable objects only”. Doc. Code Version Version date Title

Section “The MIP DEM DEM 01.01 MIP – DEM Gateway 2.0 Operator
concept” will probably need an SUM
adaption.
ISS 01.01 ISIS 4.0 - SUM

Version coding
x.y.z.:
DEM 01.02; Version 0.0.2; 8733507.doc ii 
Ministry of Defence / DMO / WSB / LA / C2SC
 PREFACE

Contact information

C2SC Front Office

− Telephone
CIVIL: 0318 - 683636 ((+31)318683636)
MDTN: *06 - 678 83636

− Fax
CIVIL: 0318-681545 ((+31)318681545)
MDTN: *06-678-81545

− GSM (+31)612995745

− Email:
Internal:
c2sc/st/frontoffice
External:
c2sc.st.frontoffice@rnla.mindef.nl

− Postal address
Elias Beeckmankazerne
MPC 41 A
P.O. Box 9012
6710 HC Ede
The Netherlands

− Visiting address
Elias Beeckmankazerne
Nieuwe kazernelaan 10
Building: 3 Room: 20/21
6711 JC Ede
The Netherlands

DEM 01.02; Version 0.0.2; 8733507.doc iii 

Ministry of Defence / DMO / WSB / LA / C2SC
 PREFACE
Used sub documents for this manual
(for C2SC documentation purposes only)

− Introduction ISIS for MIP User.doc

− Managing Operational Information Groups.doc
− Exchanging objects between C2 Information Systems.doc
− Authorization settings.doc

DEM 01.02; Version 0.0.2; 8733507.doc iv 

Ministry of Defence / DMO / WSB / LA / C2SC
 TABLE OF CONTENTS

......................................................................................................... .........ii
Version history................................................................................. ...ii
Version coding................................................................................. ...ii
Document references............................................................ .............ii
Contact information.................................................. .........................iii
......................................................................................................... .........1
General introduction............................................................. .................1
C2IEDM........................................................................... ..................1
The MIP DEM concept............................................... ...........................1
Data Exchange Mechanism solution...................................... ............1
Scope and Structure SUM............................................................ .........2
......................................................................................................... .........3
Introduction Managing operational Information groups..........................3
Overview OIGs........................................................................ ..............3
OIGs in the library.................................................................. ............3
OIGs on the GIS / overlay....................................................... ...........4
......................................................................................................... .........5
Introduction exchanging objects between C2 Information Systems.......5
Create a MIP exchangeable object on a national context......................5
Copy/ paste the object to an international OIG...................... ................6
Aggregate objects..................................................... ............................7
......................................................................................................... .........8
Introduction authorization settings........................................... ..............8
Setting the OIG authorization......................................... .......................8
......................................................................................................... .........9

DEM 01.02; Version 0.0.2; 8733507.doc v 

Ministry of Defence / DMO / WSB / LA / C2SC
 INTRODUCTION ISIS FOR MIP USER
GENERAL INTRODUCTION
INTERNATIONAL
NLD MIP SOLUTION NATION B
5 CONTEXT (Lingua Franca) CONTEXT
5
Notitie voor Betatesters: De afbeeldingen in deze SUM zijn UPDATE UPDATE

incorrect (in elke afbeelding worden de context entries met ISIS NATIONAL

ownerrights – groene kleur- aangegeven). De juiste C2IEDM C2IEDM C2IS (B)

4
C C

MCI 4
O O
N
afbeeldingen dienen in de betatestomgeving te worden T
E
X
N
T
E

gemaakt.
X
T MAPPING MAPPING T

The Application MIP – DEM is part of the Multilateral Interoperability
Programme solution (MIP solution). The MIP solution enables information
exchange between co-operating but distinct national C2 Systems. It
allows users to decide what information is exchanged, to whom and
when.
C2IEDM
The core of the MIP solution is the C2 Information Exchange Data Model
(C2IEDM). The DEM (Data Exchange Mechanism) is used to exchange
the information stored in the C2IEDM.
THE MIP DEM CONCEPT
The Data Exchange Mechanism is an automatic data push mechanism. If
the information in a C2 Information System (C2IS) is changed, this is
recognized by the DEM. The change in information is automatically
replicated (disseminated) to all MIP nations that have a subscription for
this particular information.
Data Exchange Mechanism solution
The Data Exchange Mechanism solution is depicted hereafter.
C2WS DB ODB
2 1 3
The solution consists of the following elements:
 Configuring the Gateway. To enable data transfer, the local node
needs to be configured; remote node(s) need to be added and data
transfer sessions need to be opened. This process is described in
the chapter “Configuring the Gateway”.
 Mapping of Operational Information Groups (OIGs). An OIG is a
collection of data (units, control features etc.) that can be compared
with a ‘Context’ in ISIS. In the mapping phase, the information in an
OIG is ‘translated’ to the corresponding information in the ISIS
context (and vice versa). MIP rules specify how this information is
disseminated to other units. How to create an OIG for the MIP
Gateway, so that the OIG can be disseminated, is explained in the
chapter “Managing OIGs”.
 Propose a Contract. A contract is an agreement between different
MIP nations to receive and deliver particular information. A contract
is proposed by the MIP nation that wants to send information. How

DEM 01.02; Version 0.0.2; 8733507.doc 1 

Ministry of Defence / DMO / WSB / LA / C2SC
 INTRODUCTION ISIS FOR MIP USER
to manage contracts is explained in the chapter “Managing
contracts”.
 The data will be received by the operational database of the MIP
nations and the C2IS systems of the nations will be updated.
 When the user updates information in the national C2 System, the
updates are converted into updates to the appropriate OIGs in MIP.
In ISIS the rights of the contexts have to be set properly in order to
allow the MIP Gateway to translate the data. How to use the C2
Information System as a MIP user, is described in the MIP – DEM
Gateway 2.0 User – SUM (Code: DEM 02.01).

As can be read from the DEM process, DEM involves two processes:
− Creation of contracts and setting up connections. The MIP Gateway
is used for this purpose.
− Setting authorization rights and reading / preparing data in the
C2IS. The C2 Workstation is used for this purpose.

SCOPE AND STRUCTURE SUM

The scope of this SUM is to explain how to enable the exchange of
operational information between C2 Information Systems (C2 IS) of
different MIP nations. This involves the reading and preparing of
Operational Information Groups (OIGs) and setting the authorization
rights for each OIG on the (local) C2 IS. The actions described in this
SUM have to be performed in the local environment; the actions on the
MIP DEM Gateway are outside the scope of this SUM.

How to use the MIP DEM Gateway for Data exchange

management is explained in the MIP - DEM Gateway 2.0
Operator – SUM. Code: DEM 01.01.

The SUM has been organized according to the workflow for reading and
organizing OIGs. The examples are based on the C2 Information System
“ISIS”. If another C2 Information System is used, please consult the
manual for that information system when necessary.

DEM 01.02; Version 0.0.2; 8733507.doc 2 

Ministry of Defence / DMO / WSB / LA / C2SC
 MANAGING OPERATIONAL INFORMATION GROUPS
INTRODUCTION MANAGING OPERATIONAL INFORMATION GROUPS
2
An Operation Information Group (OIG) is an international context with
information for international purposes. The information is grouped and
disseminated automatically according to MIP rules. The OIG is used as
container within which specific information can be added and removed. 1
Each international OIG is shared with MIP nations if they are subscribed
to the OIG. These nations have reading rights on the OIG (see section
“Setting the OIG authorization”).

OVERVIEW OIGS
The following types of OIGs exist:
− CORENU. Correlated unknown enemy.
− FRDNEU. Friendly and neurtralneutral organizational.
− FRNENO. Friendly and neurtralneutral non – organizational.
− GLBSGN. Globally significant.
− UNCORR. Uncorrelated enemy and unknown.
− COMPLN. Composed plan. An OIG in the library can be recognized by its extension (GLBSGN for
example).
In one mission, there can be several OIGs of the type “Specific plan Store different types of context entries in sections. This way, it is easy to
complete”. Therefore, each plan OIG is identified with a number. recognize several kinds of context entries.

The Gateway will update your OIG overview, each time an

update is available. Ask the Gateway Operator to delete the OIG
contract if the particular OIG is of no longer use (for example if How to create a section is explained in the section “Create a
the mission has ended). library entry” in the chapter “Library”, ISIS 4.0 – SUM (code: ISS
01.01).

The content of the OIG and the dissemination is prescribed in

the MIP Operational Handbook.2.6.

OIGs in the library

DEM 01.02; Version 0.0.2; 8733507.doc 3 

Ministry of Defence / DMO / WSB / LA / C2SC
 MANAGING OPERATIONAL INFORMATION GROUPS

OIGs on the GIS / overlay

An OIG can also be recognized on the GIS overlay tab by its extension
name.

New OIGs in the overview are marked green.

DEM 01.02; Version 0.0.2; 8733507.doc 4 

Ministry of Defence / DMO / WSB / LA / C2SC
 EXCHANGING OBJECTS BETWEEN C2 INFORMATION SYSTEMS
INTRODUCTION EXCHANGING OBJECTS BETWEEN C2 INFORMATION
SYSTEMS
On an OIG, objects can be placed and exchanged. Click the button Library from the launch menu to open the library.
To exchange objects, do the following: Open the national context from the library.
• Create a MIP exchangeable object on a national context. Click the option Create a new object from the toolbar. The property
• Copy the object as a shortcut to an international OIG. window opens.

Optionally, aggregate objects on the OIG. Aggregation is used to dense

the information. For example: Send the company information only, instead
of sending information about all platoons separately.

CREATE A MIP EXCHANGEABLE OBJECT ON A NATIONAL CONTEXT

Not all the object types can be identified by the C2 IS of the other MIP
nation. To create an object type that can be identified by the C2 IS of the
other MIP nation, create a MIP exchangeable object on the national 1
context.

3
2

1
Check the box Show MIP exchangeable types only to show the MIP
exchangeable objects only.
The objects in the following categories are MIP compliant:
− Unit.
− Task.
− Command and Control.
− Mobility/ Survivability.
− Fire support.
− Combat Service Support.

DEM 01.02; Version 0.0.2; 8733507.doc 5 

Ministry of Defence / DMO / WSB / LA / C2SC
 EXCHANGING OBJECTS BETWEEN C2 INFORMATION SYSTEMS
− MOOTW.
How to create an object in ISIS is explained in the section “
Create an object” in the chapter “ Objects and object
manipulation”, ISIS 4.0 – SUM (Code: ISS 01.01).
. OIG(s). Use the option Paste as short cut to create a short cut between
1
If the object is not MIP compliant, the other MIP nation will see the object
indicated with the symbol “Not Otherwise Specified” ( ).
The local MIP nation can always identify objects which are
created on the national context. These objects are never
indicated with the symbol “Not Otherwise Specified”. Therefore,
DEM 01.02; Version 0.0.2; 8733507.doc
describe each created object. Descriptions and description
format is agreed for each mission or operation separately.
COPY/ PASTE THE OBJECT TO AN INTERNATIONAL OIG
To share the local operational data, copy the data to the international
the object and the international OIG.
3
 Copy the object from the national context and open the overlay of
the international OIG.
How to copy an object in ISIS is explained in the section “Copy
and paste objects” in the chapter “Objects and object
manipulation”, ISIS 4.0 – SUM (Code: ISS 01.01).
 Right click on the map. The dropdown menu opens. Select the
option Paste special. The second dropdown menu opens.
 Select the option Paste as short cut.
6 
Ministry of Defence / DMO / WSB / LA / C2SC
 EXCHANGING OBJECTS BETWEEN C2 INFORMATION SYSTEMS

The object is copied from one OIG to another. If the object is changed in
the national context, all MIP nations with a contract for the OIG will see
the changes as long as the short cut is available.

 Click the button Save or Save all to activate the changes. All MIP
nations contracted to this OIG will see the changes.

AGGREGATE OBJECTS

Aggregation is a method to fuse individual information records into new

information. Aggregation helps to ensure relevant levels of command are
able to maintain situational awareness because the information overload
is reduced.

For example: a MIP nation can spread information about all platoons,
instead: it can aggregate this information by only sending its company
information.

Be aware that the aggregated objects will not automatically be updated by

changes in the national contexts.

Agreements on aggregated information are explained in the MIP

Operational Handbook 2.6. Application of the rules is agreed for
each mission or operation separately.

DEM 01.02; Version 0.0.2; 8733507.doc 7 

Ministry of Defence / DMO / WSB / LA / C2SC
 AUTHORIZATION SETTINGS
INTRODUCTION AUTHORIZATION SETTINGS

The national environment and the Gateway are configured in different

domains. To enable other MIP nations to read and / or modify information
on the OIG, the user rights for each national MIP context and international
OIG the authorization settings need to be configured.

The following user roles are available:

− MIP Owner. A user with MIP owner – rights on an OIG can modify
and publish this OIG.
− MIP Schrijven. A user with MIP schrijven – rights on an OIG can
modify this OIG.
− MIP Lezen. A user with MIP lezen – rights on an OIG can only read
the OIG.

SETTING THE OIG AUTHORIZATION

Different authorization rules apply, depending on the kind of OIG:

If the OIG is a national MIP context, the following rules apply:

− MIP OWNER. The MIP OWNER should have owner rights.
− MIP SCHRIJVEN. The MIP SCHRIJVEN should have write rights.
− MIP LEZEN. The MIP LEZEN should have read rights.

If the OIG is international, the following rules apply:

− MIP OWNER. The MIP OWNER should have owner rights.
− MIP SCHRIJVEN. The MIP SCHRIJVEN should have read rights.
− MIP LEZEN. The MIP LEZEN should have read rights.

How to set or change the authorization of an entry / OIG is explained in

the section “ Set / change authorization on an library” in the chapter “
Library”, ISIS 4.0 – SUM (code: ISS 01.01). In order to communicate with
the Gateway, the rights of the Gateway should be exactly the same as the
user rights.
DEM 01.02; Version 0.0.2; 8733507.doc 8 
Ministry of Defence / DMO / WSB / LA / C2SC
 INDEX

A T
Aggregation 5, 7 Types of OIGs 3
Authorization rules 8 U
Authorization settings 8 User roles 8
C
C2 Information Exchange Data Model (C2 IEDM) 1
Change the authorization of an entry 8
Container 3
Create a MIP exchangeable object 5
D
Data Exchange Mechanism 1
Data exchange mechanism solution 1
M
MIP compliant objects 5
MIP Lezen 8
MIP Owner 8
MIP rules 3
MIP Schrijven 8
Multilateral Interoperability Programme (MIP) 1
N
National environment 8
National MIP context 8
Not Otherwise Specified symbol 6
O
Operation Information Group (OIG) 3
P
Place objects on an OIG 5
S
Set / change authorization on an library 8
Share the local operational data 6
Show MIP exchangeable types 5
Specific plan complete 3

DEM 01.02; Version 0.0.2; 8733507.doc 9 

Ministry of Defence / DMO / WSB / LA / C2SC