Mip - Dem Gateway 2

Ministry of Defence / DMO / WSB / LA / C2 Support Centre
C2SC/MIP DEM
MIP - DEM Gateway 2.0 Operator - SUM

UNCLASSIFIED
Document identification:
Code: DEM 01.01
Version: 0.0.1
Status: Draft
©
Copyright Ministry of Defence
PREFACE
Version history Document references

Version Date Author(s) Description: Status Doc. Code Version Version date Title
0.0.1 10012007 M. Fuchs First version Draft 2.6 MIP Operational Handbook
DEM 02.01 MIP – DEM Gateway 2.0 User - SUM
Version coding
x.y.z.:
x= New version of the application, documentation included.
‘y’ and ‘z’ will be set to 0 in the version coding. Status is Final.
y= Temporary release of the documentation based on approval
C2SC/S&T; ‘z’ will be set to 0 in the version coding.
Status is Draft.
z= New version of the documentation, ready for internal approval
by the project team only. Status is Draft.
DEM 01.01; Version 0.0.1; 8733427.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.01; Version 0.0.1; 8733427.doc iii 

PREFACE
Used sub documents for this manual
(for C2SC documentation purposes only)
− Introduction MIP DEM Gateway.doc

− General Functions MIP DEM Gateway.doc
− Configuring the Gateway.doc
− Managing OIGs.doc
− Contract Management.doc
− Sending and requesting bulk information.doc
− Managing tasks.doc
DEM 01.01; Version 0.0.1; 8733427.doc iv 

TABLE OF CONTENTS
......................................................................................................... .........ii Abort sessions............................................................................. ........17

Version history................................................................................. ...ii Remove a node.................................................................... ...............17
Version coding................................................................................. ...ii Remove a remote node....................................... ............................18
Document references............................................................ .............ii Remove the local node.............................................. ......................18
Contact information.................................................. .........................iii
...................................................................................................... ..........20
......................................................................................................... .........1
Introduction Managing Operational Information Groups......................20
General introduction............................................................. .................1
Create an OIG on a local node................................................ ............20
C2 IEDM.......................................................................... ..................1
The MIP DEM concept............................................... ...........................1 Export an OIG........................................................... ..........................21
Data Exchange Mechanism solution...................................... ............1 Import an OIG..................................................................................... .22
Scope and Structure SUM............................................................ .........2 Results in C2 IS............................................................. ..................23
......................................................................................................... .........3 ...................................................................................................... ..........25
Open the gateway........................................................... ......................3 Introduction Managing contracts......................................................... .25
Exit the Gateway............................................................. ......................3 Propose a contract....................................................... .......................25
Logging Gateway data........................................................................... 4 Accept or reject the contract proposal.......................... .......................27
......................................................................................................... .........5 Auto accept a contract proposal....................................... ...................28
Introduction configuring the Gateway.............................. ......................5 Activate or deactivate the contract subscription.............................. .....29
Deactivate the contract subscription....................... .........................30
Configure nodes..................................................................... ...............5
Delete the contract subscription................................. .........................31
Configure the local node.................................................... ................5
Change node status.................................................................... .......7 Auto accept a contract proposal....................................... ...................32
Exchange node configuration information / save shopping list...........7 ...................................................................................................... ..........34
Add the remote node............................................... ..........................8
Node overview................................................................. ................10 Introduction Sending and requesting Bulk information....................... ..34
Node properties........................................................ .......................10 Send Catalog bulk............................................................... ................34
Configure remote node...................................... ..............................11
Change session status..................................................... ...................14 Send and request management bulk.......................................... .........34
Change the status of outgoing sessions..........................................14 Send management bulk................................................... ................34
Change the status of incoming sessions.................................. ........15 Request management bulk............................................ ..................34
Check if node is alive........................................... ...............................16 Send and request operational bulk....................................... ...............35
DEM 01.01; Version 0.0.1; 8733427.doc v 

TABLE OF CONTENTS
Send operational bulk................................................. .....................35
Request operational bulk.......................................... .......................35
...................................................................................................... ..........36
Introduction Managing tasks............................................................ ....36
Open the task window .................................................... ....................36
Accept or reject events........................................................... .............36
Dismiss events .............................................................. .....................37
...................................................................................................... ..........38
DEM 01.01; Version 0.0.1; 8733427.doc vi 

INTRODUCTION MIP DEM GATEWAY
INTERNATIONAL
NLD MIP SOLUTION NATION B
GENERAL INTRODUCTION 5 (Lingua Franca)
5
CONTEXT CONTEXT
UPDATE UPDATE
The Application MIP – DEM is part of the Multilateral Interoperability NATIONAL

ISIS C2IS (B)
Programme solution (MIP solution). The MIP solution enables information C2IEDM C2IEDM
4
C C
MCI 4
O O
exchange between co-operating but distinct national C2 Systems. It

N N
T T
E E
allows users to decide what information is exchanged, to whom and

X X
T MAPPING MAPPING T
when.
ODB
C2 IEDM C2WS DB
The core of the MIP solution is the C2 Information Exchange Data Model
(C2 IEDM). This model consists of a common interface (the MIP
Gateway) and two exchange mechanisms:
− Message Exchange Mechanism (MEM).
− Data Exchange Mechanism (DEM). 2 1 3
The MIP – DEM is used to exchange data between MIP nations.The DEM The solution consists of the following elements:
(Data Exchange Mechanism) is used to exchange the information stored
in the C2IEDM.  Configuring the Gateway. To enable data transfer, the local node
needs to be configured; remote node(s) need to be added and data
THE MIP DEM CONCEPT
transfer sessions need to be opened. This process is described in
The Data Exchange Mechanism is an automatic data push mechanism. If the chapter “Configuring the Gateway”.
the information in a C2 Information System (C2IS) is changed, this is  Mapping of Operational Information Groups (OIGs). An OIG is a
recognized by the DEM. The change in information is automatically collection of data (units, control features etc.) that can be compared
replicated (disseminated) to all MIP nations that have a subscription for with a ‘Context’ in ISIS. In the mapping phase, the information in an
this particular information. OIG is ‘translated’ to the corresponding information in the ISIS
context (and vice versa). MIP rules specify how this information is
Data Exchange Mechanism solution
disseminated to other units. How to create and edit an OIG for the
The Ddata Eexchange Mmechanism solution is depicted hereafter. MIP Gateway, so that the OIG can be disseminated, is explained in
the chapter “Configuring Managing OIGs”.
 Propose a Contract. A contract is an agreement between different
MIP nations to receive and deliver particular information (OIGs). A
contract is proposed by the MIP nation that wants to send
DEM 01.01; Version 0.0.1; 8733427.doc 1 

INTRODUCTION MIP DEM GATEWAY
information. How to manage contracts is explained in the chapter
“Contract ManagementManaging 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 data exchange
between different MIP nations, using the MIP Gateway. This involves the
creation of contracts and setting up connections; setting authorization
rights and reading and preparing data in the C2 Information System (C2
IS) is outside the scope of this SUM.
How to use the C2 IS for Data exchange management is

explained in the MIP - DEM Gateway 2.0 user – SUM (Code:
DEM 02.01).
The SUM has been organized according to the workflow for setting up the
MIP environment (as far as possible). Where applicable, a chapter starts
with an overview of the MIP solution and elements that contribute to this
solution. The parts of the solution, which are explained in the specific
chapter, are highlighted.
DEM 01.01; Version 0.0.1; 8733427.doc 2 

GENERAL FUNCTIONS MIP DEM GATEWAY
OPEN THE GATEWAY EXIT THE GATEWAY
To shut down the application, use the option Exit from the menu.
Make sure you are logged in as Administrator.
2 2
4
 Select the option File from the menu.

1 3
 Select the option Exit.
 Click on the Windows Start button. The menu opens.

 Select the option All Programs. The second menu opens.
 Select C2SC. The third menu opens.
 Select the option MIP Gateway. The MIP Gateway starts. The MIP
Gateway needs to be configured before it can exchange operational
data.
There are several ways to open the application. You can also
use the short cut on the desk top, if available.
DEM 01.01; Version 0.0.1; 8733427.doc 3 

GENERAL FUNCTIONS MIP DEM GATEWAY
 Click the button Yes.
LOGGING GATEWAY DATA
All Iincoming and outgoing data from the local MIP Gateway are
automatically logged. In case of specific errors or warnings, entries are
written in the event-log. These MIP logs and event entries are used in
case If there areof any problems with the MIP transportation or the
Gateway, you may be asked to send them log files. The following data are
logged:
− Management data.
− Catalog data.
− Operational data.
By default, data are logged in D:\MIPLOG.
DEM 01.01; Version 0.0.1; 8733427.doc 4 

CONFIGURING THE GATEWAY
• Change session status.
• Abort sessions.
INTRODUCTION CONFIGURING THE GATEWAY • Remove a node.
• Propose an information contract to the Remote Node.
How to propose an information contract is explained in the

chapter “Managing Contracts”.
CONFIGURE NODES
The local node needs to be configured and remote nodes need to be

added before information between nodes can be exchanged.
To connect two MIP nodes and send over information, the connection
information of the local node needs to be exchanged with the remote
node of the other MIP nation (this is depicted in the picture in the
introduction of this chapter).
Establishing a connection between the nodes consists of the following

In order to exchange Command and Control data with other MIP nations, possible actions:
the MIP Gateway has to be configured. For this configuration, the
following information needs to be available: • Configure the local node.
− The name of the MIP node. This is usually the name of the unit that • Change the node status.
uses the MIP node (for example: “11(NLD) AMB BDE” ). • Exchange node configuration information/ save shopping list.
− The node ID (for example: “270770001”).
• Add remote node to the MIP Gateway.
− The IP – address of the MIP node.
• Node overview.
− The port that the MIP node uses. This is usually a fixed number.
• Node properties.
• Change configuration settings of the node.
Configuring the MIP Gateway consists of the following possible actions:
Configure the local node
• Configure the local MIP node. During an operation or exercise, you have to configure the local node (the
• Add the MIP nodes of other nations (so-called “remote nodes”) to node of your nation) first. The exact data (ip-address and other
the local Node. information that is needed to configure your own node) will be provided by
• Open sessions to the remote Nodes. the Information Manger.
• Change the Node status.
DEM 01.01; Version 0.0.1; 8733427.doc 5 
1
2
2
3
 Enter the node ID of the local node.

3  Enter the Node name of the local node.
 Click the button Add.
 Select the option Node from the menu. The dropdown menu opens.
 Select the option Local Node from the menu. The second menu
opens.
 Select the option Configure from the menu.
DEM 01.01; Version 0.0.1; 8733427.doc 6 

Exchange node configuration information / save shopping list
 Enter the IP Address of the MIP node, followed by a space and the To enable the nation on the other side to configure your node as remote
port number of MIP Gateway. node, the MIP nations should exchange their node configuration
 Click the button OK. information. This information is send through a so-called “shopping list”.
Change node status
This is an XML – file with the details of the node. The file can be send
through e-mail or any other digital medium.
The node status is by default Active. If you do not want to receive The option Export shopping list is used for creating this XML-file.
operational data, you have to set the status to Management. The following example shows how to export the shopping list of your local
node; this information needs to be handed over to the remote nodes you
want to connect to.
You can also exchange the node information through other

media, such as reading the shopping list over the phone.
1
2
 Select the option Management from the list.
 The node status of the local node will change from Active (AC) to
Management (MA).
All nodes of the other MIP nations to which you have an open session are
now informed that your node status has changed to MA. You will not
receive any operational data. When you want to be able to receive
operational data, you have to change the node status back to Active.  Select the option File. The menu opens.
 Select the option Export shopping list from the menu.
DEM 01.01; Version 0.0.1; 8733427.doc 7 

3 Automatically import configuration information

MIP Nations can exchange / export their node configuration details by
creating and sending their shopping list. If the shopping list of the other
nation is available, the details of the remote node can automatically be
imported in the window Create remote node.
1
1 3
 Select a location to save the shopping list.

 Enter a file name.
 Click the button Save.
The shopping list is used for the configuration of the remote node.
 Select the option Node. The dropdown menu opens.
Add the remote node  Select the option Remote Node. The second menu opens.
Each node you want to exchange data with must be added as a remote  Select the option Add from the menu.
node on your system.
To add the remote node, the following node configuration information
should be added to the local MIP node: node ID, node name, Mgt Owner-
id, IP address and port number of the remote node. This information can
be added in two ways:
− Automatically import configuration information.
− Manually enter configuration information.
DEM 01.01; Version 0.0.1; 8733427.doc 8 

1
2
 Click the button Open to import the details of the remote node.  Select the shopping list from which the details have to be imported.
 Click the button Open.
The combination of IP address and port number should have
the following format: IP <space> port number. For
example:10.0.18.41 11000
DEM 01.01; Version 0.0.1; 8733427.doc 9 

Node overview
3
 The details of the remote node are added to the fields in the window
Create remote node.
 Change the pre-selected node address of your system to the
address of the remote node (normally the default value). 2
 Click the button OK to save changes and close the window.
 The local node is displayed in the caption of the window.
Manually enter configuration information  The remote node is displayed in the field Remote nodes.
If the shopping list is not available or the list cannot be send, you have to Node properties
enter the details of the remote node manually.
The properties of the remote node can be checked by using the option
(iets van: ) Properties.
The new node will now be added to the ‘Remote nodes’ section.
An exclamation mark next to a field appears, if entered data

have an incorrect format.
DEM 01.01; Version 0.0.1; 8733427.doc 10 

2
 All details (name and others) of the remote node are listed in the
window Node Details.
 Right click the remote node for which the configuration settings  Click the button Close to close the property window.
should be changedproperties need to be checked. The drop down
menu opens. Configure remote node
 Select the option Configuration Properties from the menu. The configuration of remote nodes is only changed with assistance form
from the support desk. Only functions which may be changed by the
operator are discussed here.
Do not change the settings, unless you are requested to do so

by the support desk. Ask for assistance of the support desk.
DEM 01.01; Version 0.0.1; 8733427.doc 11 

Open configuration window
1
2
3
 Select the tab Node.

 By default, the MIP Gateway sends the complete history of data
2
with the bulk. Tick the option Use time filtered bulk to send only the
most recent bulk information (MIP rules specify which OIG will be
 Right click the remote node for which the configuration settings time-filtered).
should be changed. The drop down menu opens.  Click the button OK.
 Select the option Configuration from the menu.
Protocol settings
Node settings The protocol settings determine the way data are communicated between
The node settings consist of settings for the outgoing session and settings systems. Considering bandwidth and capacity, you may decide to change
for the synchronization of data. If the options of synchronization data are the protocol settings. Ask for assistance of the support desk.
ticked, synchronization will take place automatically.
DEM 01.01; Version 0.0.1; 8733427.doc 12 

1
1
2
2
3 3
 Select the tab Protocol.  Select the tab Management.

 Change protocol settings.  Configure the Management events.
 Click the button OK.  Click the button OK.
Management settings In the table hereafter, the configuration options are described.
In the overview “Management settings”, it can be configured whether
specific management events should be automatically accepted by the Option Description
gateway. Auto accept operational synchronization If the option Auto accept operational
request synchronization request has been ticked, all
operational datarequests from the remote
node to receive an operational bulk will be
automatically synchronizedaccepted.
Auto accept contract proposal If the option Auto accept contract proposal
has been ticked, any contract proposals
from the MIP nation that owns the remote
node will be automatically accepted.
Database settings
DEM 01.01; Version 0.0.1; 8733427.doc 13 

In the overview of the “Database settings” , it can be configured whether have the state ‘Opened’ in order to be able to exchange any data (both
the integrity of the database should be checked for incoming an outgoing operational and management)
data.
Make sure the local node status is “Active”; otherwise no
operational data can be received. How to change the node
1 status is explained in the section “Change node status”.
The status of a node is not related to the exchange of node

2 configuration information. If the node is in management mode,
still the shopping list – which contains node configuration
information – can be created and send.
Change the status of outgoing sessions
An outgoing session can be:
− Opened.
3
− Closed.
The status of a session is not related to the exchange of node

configuration information. If all sessions are closed, still the
shopping list – which contains node configuration information –
 Select the tab Database.
can be created and send. This list is send through other (digital)
 Configure the database settings.
media after all.
 Click the button OK.
Open outgoing session
CHANGE SESSION STATUS
An outgoing session can only be opened by the sender of operational
A session is a one -way information channel between two nodes. Two data (Data Provider).
types of information channels exist:
− Outgoing sessions.
− Incoming sessions.
An outgoing session is used to send operational data from the local node
to the remote node. An incoming session is used to receive operational
data from the remote node to the local node. Both incoming and outgoing
sessions can have a state ‘Opened’ and ‘Closed’. Sessions should be
DEM 01.01; Version 0.0.1; 8733427.doc 14 

3 3
1 1
4
4
2 2
 Right click the remote node for which the outgoing session should  Right click the remote node for which the outgoing session should
be opened. The drop down menu opens. be closed. The drop down menu opens.
 Select the option Session. The second menu opens.  Select the option Session. The second menu opens.
 Select the option Outgoing session. The third menu opens.  Select the option Outgoing session. The third menu opens.
 Select the option Open outgoing session from the menu.  Select the option Close outgoing session from the menu.
The status Outgoing of the remote node will change to Open. Operational The status Outgoing of the remote node will change to Close.
data from the local node can flow to the remote node and vice versa.
Change the status of incoming sessions
Close outgoing session
A session can be closed by either the receiver of operational data (Data An incoming session can only be closed or aborted.
Receiver) or the sender.
DEM 01.01; Version 0.0.1; 8733427.doc 15 

3 Gateway of the remote node is working properly. whether the connection

with the remote node is still OK.
4 1
2
 Right click the remote node for which the incoming session should
be closed. The drop down menu opens. 2
 Select the option Session from the menu. The second menu opens.
 Select the option Incoming session from the menu. The third menu  Right click the remote node for which the node connection should
opens. be checked. The drop down menu opens.
 Select the option Close incoming session or Abort Incoming session  Select the option Properties.
from the menu.
X
The status Incoming of the remote node will change to Close. Data from
the local remote MIP Gateway will not be transferred to theyour remote  Click the button Check if node is alive.
local node.
The status of the incoming and outgoing session are displayed

per remote node. Just behind the status information the
CHECK IF NODE IS ALIVE indications (MA) or (AC) are displayed. This is an indication
whether the local or remote node is able to receive ONLY
The option Check if node is alive is used to check assure that there is a Management data (MA) or if the node can receive both
physical connection between your node and the remote node and that the Management AND Operational data (AC).
DEM 01.01; Version 0.0.1; 8733427.doc 16 
 If the node connection is OK, the notification Check successful Abort an incoming session
appears. 3
 Click the button Close.
ABORT SESSIONS
Aborting a session is a forced way of closing a session. You can:

− Abort an outgoing session.
− Abort an incoming session.
1
The abort of a session deletes the physical connection with the

remote node. Use it only if closing the session is not possible! 4
2
Abort an outgoing session

X
 Right click the remote node for which the outgoing session should
be closed. The drop down menu opens.
 Select the option Session from the menu. The second menu opens.  Right click the remote node for which the incoming session should
 Select the option Outgoing session from the menu. The third menu be aborted. The drop down menu opens.
opens.  Select the option Session from the menu. The second menu opens.
 Select the option Abort outgoing session from the menu.  Select the option Incoming session from the menu. The third menu
opens.
The transfer of outgoing data from the local MIP Gateway to the remote  Select the option Abort incoming session from the menu.
node will be aborted.
The transfer of incoming data from this remote node to the local MIP
Gateway will be aborted.
REMOVE A NODE
You can remove remote nodes as well as your own (local) node.
Make sure thate all outgoing and incoming sessions to and

from the MIP Gatewayremote node are closed.
DEM 01.01; Version 0.0.1; 8733427.doc 17 

Remove a remote node
2 1
 Click the button Yes to remove the node.

1 Remove the local node
 Select the remote node to be removed. Remove the local node only if you are absolutely sure. All
 Select the option Node. The dropdown menu opens. remote nodes will be removed as well!
 Select the option Remote Node. The second menu opens.
 Select the option Remove.
DEM 01.01; Version 0.0.1; 8733427.doc 18 

 Click the button Yes to remove the node.
 Select the option Node. The dropdown menu opens.

 Select the option Local Node. The second menu opens.
 Select the option Remove.
DEM 01.01; Version 0.0.1; 8733427.doc 19 

MANAGING OIGS
• Create an OIG on a local node to exchange information.

INTRODUCTION MANAGING OPERATIONAL INFORMATION GROUPS • Export the OIG.
• Import the OIG.
If the system is working properly, the system imports and exportssends

and receives OIGs automatically. The functions Export OIG(s) and Import
OIG(s) are used in case of system problem.
CREATE AN OIG ON A LOCAL NODE
After the local node and remote node(s) are configured, the OIGs have to
be created.
An operational Information Group (OIG) is information grouped and

disseminated automatically according to MIP rules. The OIG is a 2
container within which specific information can be added and removed.
By creating the OIG, a link is established between an OIG in MIP and a
Context in the C2 IS. The OIG can be used to store operational
information on the battlefield.
The OIG can be read, edited and removed in a national Command &
Control Information System, such as the application ISIS.
The amount and kind of OIGs transferred is regulated through  Select the option OIG. The dropdown menu opens.
so-called “Contracts”. How to manage contracts is explained in  Select the option Create single OIG.
the section “Managing Contracts”.
Managing OIGs consists of the following possible actions:
DEM 01.01; Version 0.0.1; 8733427.doc 20 

MANAGING OIGS
How to use each OIG is explained in the MIP operational

Handbook, see MIP Operational Handbook 2.6.
1 EXPORT AN OIG
The function Export OIG(s) is used to export OIGs to the C2 Information
System (C2 IS) of other MIP nations, if there is no connection available.
3 2 An export will result in a file that contains the selected OIG(s) in the MIP
format. This file can be exchanged via any digital medium. Other nodes
can Import this file and the result will be the same as if the remote node
had received the OIG(s) via the MIP Gateway.
After a refresh of the C2 IS, this update will be visible in the OIG list of the
C2 IS.
 Enter the name of the organization which is responsible for the OIG.
This is the name of the local node. 1
 Select the type of OIG from the list.
2
There are six uniquely identified default types of OIGs:
− Friendly and neutral organizational.
− Friendly and neutral object.
− Globally significant.
− Enemy uncorrelated.
− Enemy correlated.
− Specific plan complete.
Of each type, you need to create one OIG. For the type “Specific plan
complete”, more OIGs can be created.
In one mission, there can be several OIGs of the type “Specific plan  Select the option File. The dropdown menu opens.
complete”. Therefore, each plan OIG is identified with a number.  Select the option Export OIG(s).
DEM 01.01; Version 0.0.1; 8733427.doc 21 

MANAGING OIGS
2 3
 Select the location where the OIG should be saved.

 Enter a filename for the OIG.
 Tick the OIG(s) that should be exported to a transferable medium  Click the button Save.
 Click the button OK.
IMPORT AN OIG
The OIG is exported and needs to be saved to disk.
The function Import OIG(s) is used to import OIGs from C2 Information
System (C2 IS) from other MIP nations.from a file.
DEM 01.01; Version 0.0.1; 8733427.doc 22 

MANAGING OIGS
 Select the location where the file is located.

 Select the file to be imported.
 Click the button Open.
 Select the option File. The dropdown menu opens.

 Select the option Import OIG(s).
 The system gives a notification if the OIG file has been successfully
imported. Click the button OK.
1
Results in C2 IS
The MIP system updates the new imported OIG data in the operational
2 database (for example the C2 FW database). The operational database
communicates the update (if any) to the C2 IS. In the example here after,
the results of an import in the C2 IS “ISIS” are shown.
DEM 01.01; Version 0.0.1; 8733427.doc 23 

MANAGING OIGS
3 1
 The updated OIG(s) are green –coloured and shown in the library.  New or changed OIGs are also displayed on the GIS.
DEM 01.01; Version 0.0.1; 8733427.doc 24 

MANAGING CONTRACTS
How to change the contract acceptation settings is explained in

INTRODUCTION MANAGING CONTRACTS
the section “Auto accept a contract proposal”.
PROPOSE A CONTRACT
The MIP nation that wants to share OIG datas (proposer of the contract),
proposes a contract to the MIP nation(s) it wants to share its OIG data
with (receiver of the contract). The MIP nation can propose contracts from
its “publications” as well as from its “subscriptions”that contain both locally
created OIGs as well as OIGs that where created by another MIP Node.
If the MIP Gateway is configured and the OIGs are created, you can
propose a contract for a set of OIGs to another MIP nation. The other 1
nation can propose a contract for a set of OIGs to you as well.
Creating a contract between two MIP nations consists of the following

actions:
• Propose a contract to another MIP nation.

• Accept or reject the contract proposal.
• Activate or deactivate the contract or subscription. 2
• When the contract is no longer required: Delete the contract.
 Right click the remote node to share OIG data with. The dropdown
In general, incoming contracts are automatically accepted by your MIP menu opens.
gateway. In the example in this instruction however, the procedure of  Select the option Contract Management; the contract management
contract management includes manual acceptation of the contract. window will open.
DEM 01.01; Version 0.0.1; 8733427.doc 25 
MANAGING CONTRACTS
1
1
3
2
 Select the tab Contract.

2
 Enter the name of the contract. This name will be visible in the list of
publications of the proposer of the contract and in the list of
 Select the remote node to which a contract should be proposed subscriptions of the receiver of the contract when the contract
from the list. proposal is accepted.
 Click the button Propose.  Optionally, enter a remark.
DEM 01.01; Version 0.0.1; 8733427.doc 26 

MANAGING CONTRACTS
The following is described from the point of view of the receiver of the
contract.
1 If the events are automatically managed, the MIP nations do

not have to accept or reject events (see the section “Configure
remote node”).
 Select the tab OIG.

 Tick the OIGs that should be added to the contract.
2 3
The OIGs are sorted by the name of the organization that created
the OIGs. If you want to select all OIGs from that specific
organization, just tick the organization-name. If you want to select
specific OIGs from that organization, select the ‘+’ sign and tick the
individual OIGs.
 Select the contract proposal.
Normally, all OIGs are displayed in the list. You can also tick  Click the button Accept if you agree to a contract.
OIGs that are owned by other MIP nations and send these in a  Click the button Reject if you don’t want to accept the contract.
contract proposal.
Multiple contract proposals can be accepted / rejected. Use the
keys ctrl + click – single selection of events. Or shift + click – to
ACCEPT OR REJECT THE CONTRACT PROPOSAL multi selection events.
The other MIP nation(s) receive a notification in their task listof your
Accept / reject a contract proposal is also possible using the right
contract proposal.
mouse button. Select the event and click the right mouse button.
Click the appropriate menu option from the dropdown list.
DEM 01.01; Version 0.0.1; 8733427.doc 27 
MANAGING CONTRACTS
1
The proposer of the contract will see any subscriptions in its list of
publications, after he has refreshed his contract overview.
 Right click the Remote node which settings should be changed.

 Select the option Configure…
 Click the button Refresh.
AUTO ACCEPT A CONTRACT PROPOSAL
By default, the settings of the gateway are such, that contracts are
automatically accepted by the system of a MIP nation. You can change
these settings for each remote unit node separately.
DEM 01.01; Version 0.0.1; 8733427.doc 28 

MANAGING CONTRACTS
2
2
 Select the tab Management.  Select the remote node from the drop down list.
 Tick the option Auto accept contact proposal.  Expand the list of publications or subscriptions (depending whether
 Click the button OK. you are the data provider or data-receiver for the contract).
 Select a publicationcontract.
If a contract proposal is sent (see the section “propose a contract”), the  The publication contract has the status Inactive by default. Click the
other MIP nation will receive a notification of acceptation. button Activate to activate the publication.
ACTIVATE OR DEACTIVATE THE CONTRACT SUBSCRIPTION Both receiver and proposer of the contract can activate the contract. If the
receiver of the contract activates the contract however, the proposer
provider of the contract receives a notification and has to accept a
notification that the receiver wants to activate the contractthe activation of
the contract.
DEM 01.01; Version 0.0.1; 8733427.doc 29 

MANAGING CONTRACTS
3
2
1
2 3
 Select the request for activation.  Select the remote node from the drop down list.
 Click the button Accept to accept the activation.  Expand the list of subscriptions or publications.
 Click the button Reject to reject the activation.  Select a subscriptioncontract.
 The subscription contract has the status Inactive by default. Click
To see the changes, the receiver of the contract has to refresh its contract the button Refresh to refresh the subscriptioncontract.
overview.
Deactivate the contract subscription
Both receiver and proposer of the contract can deactivate the contract
subscription. This may be necessary if one of the MIP nations is
reconfiguring its nodes for exampleor if an error is detected in an OIG of
the contract. The following example is described from the point of view of
the data receiver.
DEM 01.01; Version 0.0.1; 8733427.doc 30 

MANAGING CONTRACTS
1 DELETE THE CONTRACT SUBSCRIPTION
3
2 1
4
3
2
 Select the remote node from the drop down list.

 Expand the list of publications / subscriptions.
 Select the subscriptioncontract.  Select the remote node from the drop down list.
 Click the button Deactivate to deactivate the subscriptioncontract.  Expand the list of publications / subscriptions.
 Select the subscriptioncontract.
 Click the button Delete to delete the subscriptioncontract.
DEM 01.01; Version 0.0.1; 8733427.doc 31 

MANAGING CONTRACTS
 Click the button Yes to confirm the deletion.
AUTO ACCEPT A CONTRACT PROPOSAL  Right click the Remote node of which the settings should be
changed.
By default, the settings of the gateway are such, that contracts are  Select the option Configure…
automatically accepted by the system of a MIP nation. You can change
these settings for each remote unit separately.
DEM 01.01; Version 0.0.1; 8733427.doc 32 

MANAGING CONTRACTS
 Select the tab Management.

 Tick the option Auto accept contact proposal.
If a contract proposal is sent (see the section “propose a contract”), the

other MIP nation will receive a notification of acceptation.
DEM 01.01; Version 0.0.1; 8733427.doc 33 

SENDING AND REQUESTING BULK INFORMATION
INTRODUCTION SENDING AND REQUESTING BULK INFORMATION SEND AND REQUEST MANAGEMENT BULK
When the MIP Gateway is configured, Operational Information Groups A Management bulk contains all the information from the Management
(OIGs) are being sent or updated and contracts are managed. Bulks are database that is relevant for the MIP Gateway of another MIP nation (for
used to synchronize two MIP Nodes. Three different kinds of bulks can be example the contracts and the statuses of these contracts). The
exchanged: Management bulk is automatically exchanged when a session is opened
− Catalog bulk. to a remote node. If the management data is modified the other node is
− Management bulk. automatically informed as well (after the session is opened).
− Operational bulk.
Send management bulk
Normally, synchronization is performed automatically and no human In case the remote node is not correctly synchronized (for example
intervention is required to send bulks. In some cases however it is useful because data is manually manipulated in the database), a Management
to send or request this bulk manually. For instance when the national bulk needs to be sent.
database has crashed, or when the Gateway has been out of order for a
time. X
If the database has crashed, follow the escalation procedure.  Right click the remote node to which management bulk should be
Ask the support desk for assistance. send. The drop down menu opens.
 Select the option Send. The second menu opens.
In the following paragraphs the meaning of each type of bulk is explained.  Select the option Send Management bulk.
Request management bulk
SEND CATALOG BULK
In case the management data of the remote MIP node are manipulated
The Catalog bulk contains the list of available OIGs on which the remote without synchronizing, you need to request a management bulk from that
node can be subscribed. If the remote node needs an update of the list of node.
available OIGs, a catalog bulk needs to be send (for example because
data has been entered into the database by hand). X
 Right click the remote node from which management bulk should be
requested. The drop down menu opens.
 Right click the remote node to which the Catalog bulk should be  Select the option Request. The second menu opens.
send. The drop down menu opens.  Select the option Request Management bulk.
 Select the option Send Catalog bulk from the menu.
DEM 01.01; Version 0.0.1; 8733427.doc 34 

SENDING AND REQUESTING BULK INFORMATION
SEND AND REQUEST OPERATIONAL BULK
The Operational bulk contains information from the operational database

(for example location and status of units on the map).
By default an initial Operational bulk is exchanged to synchronize all

operational data in the OIGs of the contract, when a contract is activated
for the first time. There after, only updates are sent to keep the
operational data synchronized.
Send operational bulk
If the operational data of the remote node is out of sync, an operational
bulk can be sent to synchronize.
 Right click the remote node to which operational bulk should be

send. The drop down menu opens.
 Select the option Send Operational bulk from the menu.
Request operational bulk
You can also request an operational bulk from a remote node if your
operational data are out of sync.
 Right click the remote node from which operational bulk should be
requested. The drop down menu opens.
 Select the option Request from the menu. The second menu opens.
 Select the option Request Operational bulk.
DEM 01.01; Version 0.0.1; 8733427.doc 35 

MANAGING TASKS
INTRODUCTION MANAGING TASKS
When the MIP Gateway Operator needs to be informed of important 1

events (like a broken session to another node) or when the input of the
MIP Gateway Operator is required (for example to accept a proposed
contract) the Task window will automatically pop up. The Task window can 2
also be opened manually.
The task window displays the source node of the task/event; the type of
event (for example a contract proposal) a short description of the event
and the time at which the event was issued.
Managing tasks consists of the following possible actions:
• Open the task window.  Select the option View from the menu. The dropdown menu opens.
• Accept or reject events (Gateway Operator input is required).  Select the option View Tasks.
• Dismiss events (Gateway Operator is informed about important
events). ACCEPT OR REJECT EVENTS
OPEN THE TASK WINDOW

Sometimes the MIP Gateway Operator needs to accept or reject an
event, for instance when another MIP Node has proposed a contract.
Whenever new entries are written into the Task window, this window will
automatically pop-up. In case you want to open the task window manually If the events are automatically managed, the MIP nations do
do the following: not have to accept or reject events (see the section “Configure
remote node”).
The acceptation and rejection of a contract is given as an example.
DEM 01.01; Version 0.0.1; 8733427.doc 36 

MANAGING TASKS
Some information – events may require that you contact the
other MIP nation. These kind of actions are outside the scope
of this chapter.
1
2 3
 Select the contract proposal.

 Click the button Accept if you agree to a contract.
 Click the button Reject if you don’t want to accept the contract.
Multiple events can be accepted / rejected or dismissed. Use the  Select the event.
keys ctrl + click – to select unordered events. Or shift + click – to  Click the button Dismiss to indicate that you are aware of the event
select ordered events. that took place. The event will be removed from the list.
Accept / reject or dismiss events is also possible using the right Multiple events can be accepted / rejected or dismissed. Use the
mouse button. Select the event and click the right mouse button. keys ctrl + click – to select unordered events. Or shift + click – to
Click the appropriate menu option from the dropdown list. select ordered events.
DISMISS EVENTS Accept / reject or dismiss events is also possible using the right
mouse button. Select the event and click the right mouse button.
There are also events that appear in the task list to inform the MIP Click the appropriate menu option from the dropdown list.
Gateway Operator of important events (for example to report an aborted
session to another MIP node). In this case the MIP Gateway Operator can
only dismiss the event.
DEM 01.01; Version 0.0.1; 8733427.doc 37 

INDEX
A Exchange node configuration information 7

Aborting a session 17 Export an OIG 21
Accept a contract proposal 27 Export shopping list 7
Accept or reject an event 36 I
Activate a contract subscription 29 Import OIG(s) 22
Add a remote node 8 Incoming session 14
Automatically accept a contract proposal 28, 32 IP Address 7
Automatically import configuration information 8 L
C Logging Gateway data 4
C2 Information Exchange Data Model (C2 IEDM) 1 M
C2 Information System (C2 IS) 2 Management settings 13
Change node status 7 Manually enter configuration information 8
Check if node is alive 16 Multilateral Interoperability Programme (MIP) 1
Close incoming session 15 N
Close outgoing session 15 Node ID 6
common interface 1 Node settings 12
Configuration options 13
O
Configure a remote node 11
Configure the local node 5 OIG list 21
Contract management window 25 Open outgoing session 14
Create an OIG 20 Open the gateway 3
Open the task window manually 36
D
Operational bulk 35
Data Exchange Mechanism 1 Operational Information Group (OIG) 20
Data Exchange Mechanism (DEM) 1 Outgoing session 14
Data exchange mechanism solution 1
P
Database settings 14
Deactivate a contract subscription 30 Propose a contract 25
Default OIGs 21 Proposer of the contract 25
Delete a contract subscription 31 Protocol settings 12
Dismiss the event 37 R
E Receiver of the contract 25
Escalation procedure 34 Remote node properties 10
Exchange Command and Control data 5 Remove a local node 18
Remove a remote node 18
DEM 01.01; Version 0.0.1; 8733427.doc 38 
INDEX
Request management bulk 34
S
Scope 2
Send and request operational bulk 35
Send catalog bulk 34
Send management bulk 34
Sending and requesting bulk information 34
Shut down the application 3
Specific plan complete 21
Synchronize two MIP Nodes 34
T
Task window 36
Transfer of incoming data 17
Transfer of outgoing data 17
DEM 01.01; Version 0.0.1; 8733427.doc 39 


Mip - Dem Gateway 2

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mip - Dem Gateway 2

Transféré par

Droits d'auteur :

Formats disponibles

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

MIP - DEM Gateway 2.0 Operator - SUM

Version history Document references

DEM 02.01 MIP – DEM Gateway 2.0 User - SUM

DEM 01.01; Version 0.0.1; 8733427.doc ii 

C2SC Front Office

DEM 01.01; Version 0.0.1; 8733427.doc iii 

− Introduction MIP DEM Gateway.doc

DEM 01.01; Version 0.0.1; 8733427.doc iv 

......................................................................................................... .........ii Abort sessions............................................................................. ........17

Open the gateway........................................................... ......................3 Introduction Managing contracts......................................................... .25

Exit the Gateway............................................................. ......................3 Propose a contract....................................................... .......................25

Logging Gateway data........................................................................... 4 Accept or reject the contract proposal.......................... .......................27

......................................................................................................... .........5 Auto accept a contract proposal....................................... ...................28

DEM 01.01; Version 0.0.1; 8733427.doc v 

DEM 01.01; Version 0.0.1; 8733427.doc vi 

The Application MIP – DEM is part of the Multilateral Interoperability NATIONAL

exchange between co-operating but distinct national C2 Systems. It

allows users to decide what information is exchanged, to whom and

DEM 01.01; Version 0.0.1; 8733427.doc 1 

SCOPE AND STRUCTURE SUM

How to use the C2 IS for Data exchange management is

DEM 01.01; Version 0.0.1; 8733427.doc 2 

Make sure you are logged in as Administrator.

 Select the option File from the menu.

 Click on the Windows Start button. The menu opens.

DEM 01.01; Version 0.0.1; 8733427.doc 3 

 Click the button Yes.

LOGGING GATEWAY DATA

By default, data are logged in D:\MIPLOG.

DEM 01.01; Version 0.0.1; 8733427.doc 4 

How to propose an information contract is explained in the

The local node needs to be configured and remote nodes need to be

Establishing a connection between the nodes consists of the following

 Enter the node ID of the local node.

DEM 01.01; Version 0.0.1; 8733427.doc 6 

You can also exchange the node information through other

DEM 01.01; Version 0.0.1; 8733427.doc 7 

3 Automatically import configuration information

 Select a location to save the shopping list.

DEM 01.01; Version 0.0.1; 8733427.doc 8 

DEM 01.01; Version 0.0.1; 8733427.doc 9 

An exclamation mark next to a field appears, if entered data

DEM 01.01; Version 0.0.1; 8733427.doc 10 

Do not change the settings, unless you are requested to do so

DEM 01.01; Version 0.0.1; 8733427.doc 11 

 Select the tab Node.

DEM 01.01; Version 0.0.1; 8733427.doc 12 

 Select the tab Protocol.  Select the tab Management.

DEM 01.01; Version 0.0.1; 8733427.doc 13 

The status of a node is not related to the exchange of node

The status of a session is not related to the exchange of node

DEM 01.01; Version 0.0.1; 8733427.doc 14 

DEM 01.01; Version 0.0.1; 8733427.doc 15 

3 Gateway of the remote node is working properly. whether the connection

The status of the incoming and outgoing session are displayed

Aborting a session is a forced way of closing a session. You can:

The abort of a session deletes the physical connection with the

Abort an outgoing session

Make sure thate all outgoing and incoming sessions to and

DEM 01.01; Version 0.0.1; 8733427.doc 17 

 Click the button Yes to remove the node.

DEM 01.01; Version 0.0.1; 8733427.doc 18 