mip - dem gateway 2

© Copyright Ministry of Defence

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

Ministry of Defence / DMO / WSB / LA / C2 Support Centre C2SC/MIP DEM

MIP - DEM Gateway 2.0 Operator - SUM UNCLASSIFIED

PREFACE

DEM 01.01; Version 0.0.2; MIP - DEM Gateway 2.0 Operator - SUM ii Ministry of Defence / DMO / WSB / LA / C2SC

Version history

Version Date Author(s) Description: Status

0.0.1 10012007 M. Fuchs First version Draft

0.0.2 15012007 M. Fuchs Edited: “The MIP DEM concept”. Version for Betatest

Draft

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.

Document references

Doc. Code Version Version date Title

2.6 MIP Operational Handbook

DEM 02.01 MIP – DEM Gateway 2.0 User - SUM

PREFACE

DEM 01.01; Version 0.0.2; MIP - DEM Gateway 2.0 Operator - SUM iii Ministry of Defence / DMO / WSB / LA / C2SC

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: [email protected]

− 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

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

TABLE OF CONTENTS

DEM 01.01; Version 0.0.2; MIP - DEM Gateway 2.0 Operator - SUM iv Ministry of Defence / DMO / WSB / LA / C2SC

Preface ....................................................................................................ii

Version history .................................................................................. ii Version coding .................................................................................. ii Document references........................................................................ ii Contact information .......................................................................... iii

Introduction MIP DEM Gateway.............................................................1

General introduction .............................................................................1

C2 IEDM ...........................................................................................1

The MIP DEM concept..........................................................................1

Data Exchange Mechanism solution .................................................1

Scope and Structure SUM ....................................................................2

General Functions MIP DEM Gateway ..................................................4

Open the gateway.................................................................................4

Exit the Gateway...................................................................................4

Logging Gateway data ..........................................................................5

Configuring the Gateway .......................................................................6

Introduction configuring the Gateway....................................................6

Configure nodes ...................................................................................6

Configure the local node ...................................................................6 Change node status ..........................................................................8 Save shopping list / Exchange node configuration information ..........8 Add the remote node.........................................................................9 Node overview ................................................................................12 Node properties...............................................................................12 Configure remote node....................................................................13

Change session status........................................................................15

Change the status of outgoing sessions..........................................16 Change the status of incoming sessions .........................................16

Check if node is alive..........................................................................17

Abort sessions ....................................................................................18

Remove a node ..................................................................................19

Remove a remote node...................................................................19 Remove the local node ...................................................................20

Managing OIGs....................................................................................22

Introduction Managing Operational Information Groups......................22

Create an OIG on a local node ...........................................................22

Export an OIG.....................................................................................23

Import an OIG.....................................................................................24

Results in C2IS ...............................................................................25

Managing Contracts.............................................................................27

Introduction Managing contracts .........................................................27

Propose a contract..............................................................................27

Accept or reject the contract proposal.................................................29

Auto accept a contract proposal..........................................................30

Activate or deactivate the contract or subscription ..............................31

Deactivate the contract subscription................................................32

Delete the contract..............................................................................33

Sending and requesting bulk information ..........................................34

Introduction Sending and requesting Bulk information ........................34

Send Catalog bulk ..............................................................................34

Send and request management bulk ..................................................34

Send management bulk ..................................................................34 Request management bulk .............................................................35

Send and request operational bulk .....................................................35

Send operational bulk .....................................................................35 Request operational bulk.................................................................36

TABLE OF CONTENTS

DEM 01.01; Version 0.0.2; MIP - DEM Gateway 2.0 Operator - SUM v Ministry of Defence / DMO / WSB / LA / C2SC

Managing tasks ....................................................................................37

Introduction Managing tasks ...............................................................37

Open the task window.........................................................................37

Accept or reject events .......................................................................37

Dismiss events....................................................................................38

Index......................................................................................................39

INTRODUCTION MIP DEM GATEWAY

DEM 01.01; Version 0.0.2; MIP - DEM Gateway 2.0 Operator - SUM 1 Ministry of Defence / DMO / WSB / LA / C2SC

GENERAL INTRODUCTION

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.

C2 IEDM

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. It is based on the replication of data between nodes of different MIP nations; 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.

NLD

ISIS

C2WS DB

ISISISIS

C2WS DB

MCIC2IEDMC2IEDMC2IEDMC2IEDM

NATIONAL

C2IS (B)NATIONAL

C2IS (B)NATIONAL

C2IS (B)

ODB

INTERNATIONAL

MIP SOLUTION(Lingua Franca)

INTERNATIONAL

MIP SOLUTION(Lingua Franca)

NATION B

MAPPING

MAPPING

CONTEXT

CONTEXT

CONTEXT UPDATE

CONTEXT UPDATE

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 communication channels need to be opened. In order to communicate, each Gateway needs to know the details of the node (node name and node-id) and the connectivity information of the Gateway (IP-address, TCP port number and other technical data). The configuration process is described in the chapter “Configuring the Gateway”.

� Creating of Operational Information Groups (OIGs). After the local

node has been configured, the OIGs are created. 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 is explained in the chapter “Managing OIGs”.



� Add remote nodes to the Gateway.The connectivity information (IP-

address, TCP port number and other technical data) is saved in a so-called “Shopping list”. The shopping list is used to add remote nodes to the Gateway. It is exchanged off-line. How to add remote nodes to the Gateway is explained in the chapter “Configuring the Gateway”.

� Once the local node is configured, remote nodes are added to the

Gateway and a communication link is available, the communication channel to exchange operational data needs to be enabled. The first step to enable the communication channel is to open an outgoing session with the remote node you want to exchange operational data with. The following information is exchanged automatically: all the information from the Management database that is relevant for the Gateway of another MIP nation (Management bulk) and the list of available OIGs on which the remote node can be subscribed (Catalog bulk). Sessions can also be closed or aborted. How to manage sessions is explained in the chapter “Configuring the Gateway”.

� Propose a Contract. A contract is an agreement between different

MIP nations to receive and deliver (provide) OIGs. A contract contains a list of OIGs which are proposed by the MIP nation that wants to send the OIGs. The contract can be accepted (happens automatically), or rejected. The list of OIGs may contain own OIGs or OIGs created by another MIP nation (forwarding of data). An accepted contract is inactive by default (that is, no operational data are being exchanged). As soon as the subscription to the contract is activated, operational bulks are exchanged between the Gateways (operational synchronization) takes place automatically. During long term operations, it may be time consuming to synchronize all data. The option time filtered bulk is used to send the current data only. How 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 ISIS 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 (steps 1 to 3). The MIP Gateway is used for this purpose.

− Setting authorization rights and reading / preparing data in ISIS (steps 4 and 5). 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.

GENERAL FUNCTIONS MIP DEM GATEWAY


OPEN THE GATEWAY

To use the MIP Gateway, you need to have administrator rights.

� 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.

EXIT THE GATEWAY

To shut down the application, use the option Exit from the menu.

� Select the option File from the menu. � Select the option Exit.

GENERAL FUNCTIONS MIP DEM GATEWAY


� Click the button Yes.

LOGGING GATEWAY DATA

All incoming 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 of problems with the MIP Gateway.The support desk may ask you to send them.

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

CONFIGURING THE GATEWAY


INTRODUCTION CONFIGURING THE GATEWAY

In order to exchange Command and Control data with other MIP nations, the MIP Gateway has to be configured. For this configuration, the following information needs to be available:

− The name of the MIP node. This is usually the name of the unit that uses the MIP node (for example: “11(NLD) AMB BDE” ).

− The node ID (for example: “270770001”).

− The IP – address of the MIP node.

− The port that the MIP node uses. This is usually a fixed number. Configuring the MIP Gateway consists of the following possible actions:

• Configure the local MIP node.

• Add the MIP nodes of other nations (so-called “remote nodes”) to the local Node.

• Open sessions to the remote Nodes.

• Change the Node status.

• Change session status.

• Abort sessions.

• 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 possible actions:

• Configure the local node.

• Change the node status.

• Save shopping list / Exchange node configuration information.

• Add remote node to the MIP Gateway.

• Node overview.

• Node properties.

• Change configuration settings of the node.

Configure the local node

During an operation or exercise, you have to configure the local node (the node of your nation) first. The exact data (ip-address and other information that is needed to configure your own node) will be provided by the Information Manager.



� Select the option Node. The dropdown menu opens. � Select the option Local Node. The second menu opens. � Select the option Configure from the menu.

� Enter the node ID of the local node. � Enter the Node name of the local node. � Click the button Add.



� Enter the IP Address of the node, followed by a space and the port

number of MIP Gateway. � Click the button OK.

Change node status

The node status is by default Active. If you do not want to receive operational data, you have to set the status to Management.

� Select the option Management from the list. � The node status of the local node will change from Active (AC) to

Management (MA). The status “MA” and “AC” indicate whether the local or remote node is able to receive ONLY Management data (MA) or whether the node can receive both Management AND Operational data (AC).

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.

Save shopping list / Exchange node configuration information

To enable the nation on the other side to configure your node as remote node, the MIP nations should exchange their node configuration information. This information is send through a so-called “shopping list”. 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 option Export shopping list is used for creating this XML-file. 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.

The exchange of node configuration information is not related to the status of a node. If the node is in management mode, still the shopping list – which contains node configuration information – can be created and send.

You can also exchange the node information through other media, such as reading the shopping list over the phone.



� Select the option File. The menu opens. � Select the option Export shopping list from the menu.

� 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.

Add the remote node

Each node you want to exchange data with must be added as a remote node on your system. To add the remote node, the following node configuration information should be added to the local node: node ID, node name, IP address, Owner ID and port number of the remote node. This information can be added in two ways:

− Automatically import configuration information.

− Manually enter configuration information.



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.

� Select the option Node. The dropdown menu opens. � Select the option Remote Node. The second menu opens. � Select the option Add from the menu.

� Click the button Open to import the details of the remote node.

The combination of IP address and port number should have the following format: IP <space> port number. For example:10.0.18.41 11000



� Select the shopping list from which the details have to be imported. � Click the button Open.

� 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.

� Click the button OK to save changes and close the window. Manually enter configuration information If the shopping list is not available or the list cannot be send, you have to enter the details of the remote node manually.

An exclamation mark next to a field appears, if entered data have an incorrect format.



Node overview

1

2

� The local node is displayed in the caption of the window. � The remote node is displayed in the field Remote nodes.

Node properties

The properties of the remote node can be checked by using the option Properties.

� Right click the remote node for which the properties need to be

checked. The drop down menu opens. � Select the option Properties from the menu.



� All details (name and others) of the remote node are listed in the

window Node Details. � Click the button Close to close the property window.

Configure remote node

The configuration of remote nodes is only changed with assistance 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.

Open configuration window

1

2

� Right click the remote node for which the Configuration settings

need to be changed. The drop down menu opens. � Select the option Configuration from the menu. Node settings The node settings consist of settings for the outgoing session and settings for the synchronization of data. If the options of synchronization data are ticked, synchronization will take place automatically.



� Select the tab Node. � By default, the MIP Gateway sends the complete history of data

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 time-filtered).

� Click the button OK. Protocol settings The protocol settings determine the way data are communicated between systems. Considering bandwidth and capacity, you may decide to change the protocol settings. Ask for assistance of the support desk.

� Select the tab Protocol. � Change protocol settings. � Click the button OK. Management settings In the overview “Management settings”, it can be configured whether specific management events should be automatically accepted by the gateway.



� Select the tab Management. � Configure the Management events. � Click the button OK. In the table hereafter, the configuration options are described.

Option Description

Auto accept operational synchronization request

If the option Auto accept operational synchronization request has been ticked, all requests from the remote node to receive an operational bulk will be automatically accepted

Auto accept contract proposal If the option Auto accept contract proposal has been ticked, any contract proposals from the remote node will be automatically accepted.

Database settings In the overview of the “Database settings” , it can be configured whether the integrity of the database should be checked.

� Select the tab Database. � Configure the database settings. � Click the button OK.

CHANGE SESSION STATUS

A session is a one -way information channel between two nodes. Two 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 have the state ‘Opened’ in order to be able to exchange any data (both operational and management).



Make sure the local node status is “Active”; otherwise no operational data can be received. How to change the node status is explained in the section “Change node status”.

Change the status of outgoing sessions

An outgoing session can be:

− Opened.

− Closed. Open outgoing session An outgoing session can only be opened by the sender of operational data (Data Provider).

1

2

3

4

� Right click the remote node for which the outgoing session should

be opened. The drop down menu opens. � Select the option Session. The second menu opens. � Select the option Outgoing session. The third menu opens. � Select the option Open outgoing session from the menu.

The status Outgoing of the remote node will change to Open. Operational data from the local node can flow to the remote node and vice versa. Close outgoing session A session can be closed by either the receiver of operational data (Data Receiver) or the sender.


be closed. The drop down menu opens. � Select the option Session. The second menu opens. � Select the option Outgoing session. The third menu opens. � Select the option Close outgoing session from the menu. The status Outgoing of the remote node will change to Close.

Change the status of incoming sessions

An incoming session can only be closed.



� Right click the remote node for which the incoming session should

be closed. The drop down menu opens. � Select the option Session. The second menu opens. � Select the option Incoming session. The third menu opens. � Select the option Close incoming session from the menu. The status Incoming of the remote node will change to Close. Data from the remote MIP Gateway will not be transferred to your local node.

CHECK IF NODE IS ALIVE

The option Check if node is alive is used to assure that there is a physical connection between your node and the remote node and that the Gateway of the remote node is working properly.

� Right click the remote node for which the node connection should

be checked. The drop down menu opens. � Select the option Properties.



� Click the button Check if node is alive. � If the node connection is OK, the notification Check successful

appears. � Click the button Close.

ABORT SESSIONS

Aborting a session is a forced way of closing a session. Aborting a session consists of the following possible actions:

− Abort an outgoing session.

− Abort an incoming session.

The abort of a session deletes the physical connection with the remote node. Use it only if closing the session is not possible!

Abort an outgoing session

1

2

3

4


be closed. The drop down menu opens. � Select the option Session. The second menu opens. � Select the option Outgoing session. The third menu opens. � Select the option Abort outgoing session from the menu. The transfer of outgoing data from the local MIP Gateway to the remote node will be aborted.



Abort an incoming session

� Right click the remote node for which the incoming session should

be aborted. The drop down menu opens. � Select the option Session. The second menu opens. � Select the option Incoming session. The third menu opens. � Select the option Abort incoming session from the menu. 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 that all outgoing and incoming sessions to and from the remote node are closed.

Remove a remote node

� Select the remote node to be removed. � Select the option Node. The dropdown menu opens. � Select the option Remote Node. The second menu opens. � Select the option Remove.



� Click the button Yes to remove the node.

Remove the local node

Remove the local node only if you are absolutely sure. All remote nodes will be removed as well!

� Select the option Node. The dropdown menu opens. � Select the option Local Node. The second menu opens. � Select the option Remove.



� Click the button Yes to remove the node.

MANAGING OIGS


INTRODUCTION MANAGING OPERATIONAL INFORMATION

GROUPS

An operational Information Group (OIG) is information grouped and disseminated automatically according to MIP rules. The OIG is a 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 C2IS. The OIG can be used to store operational information. 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 so-called “Contracts”. How to manage contracts is explained in the section “Managing Contracts”.

Managing OIGs consists of the following possible actions:

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

• Export the OIG.

• Import the OIG. If the system is working properly, the system sends 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.

� Select the option OIG. The dropdown menu opens. � Select the option Create single OIG.

MANAGING OIGS


� Enter the name of the organization which is responsible for the OIG.

This is the name of the local node. � Select the type of OIG from the list. 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 complete”. Therefore, each plan OIG is identified with a number. � Click the button OK.

How to use each OIG is explained in the MIP operational Handbook, see MIP Operational Handbook 2.6.

EXPORT AN OIG

The function Export OIG(s) is used to export OIGs to the C2 Information System (C2IS) of other MIP nations, if there is no connection available. An export will result in a file that contains the selected OIG(s) in the MIP format. This file can be exchanged through any digital medium. Other MIP nations can import this file for their node configuration.

� Select the option File. The dropdown menu opens. � Select the option Export OIG(s).

MANAGING OIGS


� Tick the OIG(s) that should be exported to a transferable medium � Click the button OK. The OIG is exported and needs to be saved to disk.

� Select the location where the OIG should be saved. � Enter a filename for the OIG. � Click the button Save.

IMPORT AN OIG

The function Import OIG(s) is used to import OIGs from a file.

MANAGING OIGS


� Select the option File. The dropdown menu opens. � Select the option Import OIG(s).

� Select the location where the file is located. � Select the file to be imported. � Click the button Open.

� The system gives a notification if the OIG file has been successfully

imported. Click the button OK.

Results in C2IS

The MIP system updates the new imported OIG data in the operational database. The operational database communicates the update (if any) to the C2IS. In the example here after, the results of an import in the C2IS “ISIS” are shown.

MANAGING OIGS


� The updated OIG(s) are green –coloured and shown in the library.

� New or changed OIGs are also displayed on the GIS.

MANAGING CONTRACTS


INTRODUCTION MANAGING CONTRACTS

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 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.

• When the contract is no longer required: Delete the contract. In general, incoming contracts are automatically accepted by your MIP gateway. In the example in this instruction however, the procedure of contract management includes manual acceptation of the contract.

How to change the contract acceptation settings is explained in the section “Auto accept a contract proposal”.

PROPOSE A CONTRACT

The MIP nation that wants to share OIGs (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 that contain both locally created OIGs as well as OIGs that where created by another MIP Node.

� Right click the remote node to share OIG data with. The dropdown

menu opens. � Select the option Contract Management; the contract management

window will open.

MANAGING CONTRACTS


� Select the remote node to which a contract should be proposed

from the list. � Click the button Propose.

� Select the tab Contract. � 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 subscriptions of the receiver of the contract when the contract proposal is accepted.

� Optionally, enter a remark.

MANAGING CONTRACTS


� Select the tab OIG. � Tick the OIGs that should be added to the contract.

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.

� Click the button OK.

Normally, all OIGs are displayed in the list. You can also tick OIGs that are owned by other MIP nations and send these in a contract proposal.

ACCEPT OR REJECT THE CONTRACT PROPOSAL

The other MIP nation(s) receive a notification of your contract proposal. The following is described from the point of view of the receiver of the contract.

� 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. Use the keys ctrl + click– to select one event at a time. Or shift + click – to select multiple events at once.

Accept / reject a contract proposal is also possible using the right mouse button. Select the event and click the right mouse button. Click the appropriate menu option from the dropdown list.

The proposer of the contract will see any subscriptions in its list of publications, after he has refreshed his contract overview.

MANAGING CONTRACTS


� 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 separately.

� Right click the Remote node which settings should be changed. � Select the option Configure…

MANAGING CONTRACTS


� Select the tab Management. � Tick the option Auto accept contact proposal. � Click the button OK. If a contract proposal is sent (see the section “propose a contract”), the other MIP nation will receive a notification of acceptation.

ACTIVATE OR DEACTIVATE THE CONTRACT OR SUBSCRIPTION

� Select the remote node from the drop down list. � Expand the list of publications. � Select a publication. � The publication has the status Inactive by default. Click the button

Activate to activate the publication. Both receiver and proposer of the contract can activate the contract. If the receiver of the contract activates the contract however, the proposer of

the contract receives and has to accept a notification that the receiver wants to activate the contract.

� Select the request for activation. � Click the button Accept to accept the activation. � Click the button Reject to reject the activation. To see the changes, the receiver of the contract has to refresh its contract overview.

MANAGING CONTRACTS


� Select the remote node from the drop down list. � Expand the list of subscriptions. � Select a subscription. � The subscription has the status Inactive by default. Click the button

Refresh to refresh the subscription.

Deactivate the contract subscription

Both receiver and proposer of the contract can deactivate the contract subscription. This may be necessary f one of the MIP nations is reconfiguring its nodes for example. The following example is described from the point of view of the receiver.

� Select the remote node from the drop down list. � Expand the list of subscriptions. � Select the subscription. � Click the button Deactivate to deactivate the subscription.

MANAGING CONTRACTS


DELETE THE CONTRACT

� Select the remote node from the drop down list. � Expand the list of subscriptions. � Select the subscription. � Click the button Delete to delete the subscription.

� Click the button Yes to confirm the deletion.

SENDING AND REQUESTING BULK INFORMATION


INTRODUCTION SENDING AND REQUESTING BULK

INFORMATION

When the MIP Gateway is configured, Operational Information Groups (OIGs) are being sent or updated and contracts are managed. Bulks are used to synchronize two MIP Nodes. Three different kinds of bulks can be exchanged:

− Catalog bulk.

− Management bulk.

− Operational bulk. Normally, synchronization is performed automatically and no human intervention is required to send bulks. In some cases however it is useful to send or request this bulk manually. For instance when the national database has crashed, or when the Gateway has been out of order for a time.

If the database has crashed, follow the escalation procedure. Ask the support desk for assistance.

In the following paragraphs the meaning of each type of bulk is explained.

SEND CATALOG BULK

The Catalog bulk contains the list of available OIGs on which the remote node can be subscribed. If the remote node needs an update of the list of available OIGs, a catalog bulk needs to be send (for example because data has been entered into the database by hand).

� Right click the remote node to which the Catalog bulk should be

send. The drop down menu opens. � Select the option Send. The second menu opens. � Select the option Send Catalog bulk from the menu.

SEND AND REQUEST MANAGEMENT BULK

A Management bulk contains all the information from the Management database that is relevant for the MIP Gateway of another MIP nation (for example the contracts and the statuses of these contracts). The Management bulk is automatically exchanged when a session is opened to a remote node. If the management data is modified the other node is automatically informed as well (after the session is opened).

Send management bulk

In case the remote node is not correctly synchronized (for example because data is manually manipulated in the database), a Management bulk needs to be sent.



� Right click the remote node to which management bulk should be

send. The drop down menu opens. � Select the option Send. The second menu opens. � Select the option Send Management bulk.

Request management bulk

In case the management data of the remote MIP node are manipulated without synchronizing, you need to request a management bulk from that node.

� Right click the remote node from which management bulk should be

requested. The drop down menu opens. � Select the option Request. The second menu opens. � Select the option Request Management bulk.

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. The second 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.

MANAGING TASKS


INTRODUCTION MANAGING TASKS

When the MIP Gateway Operator needs to be informed of important 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 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.

• Accept or reject events (Gateway Operator input is required).

• Dismiss events (Gateway Operator is informed about important events).

OPEN THE TASK WINDOW

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 do the following:

� Select the option View from the menu. The dropdown menu opens. � Select the option View Tasks.

ACCEPT OR REJECT EVENTS

Sometimes the MIP Gateway Operator needs to accept or reject an event , for instance when another node has proposed a contract.

If the events are automatically managed, the MIP nations do 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.

MANAGING TASKS


� 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 keys ctrl + click – to select one event at a time. Or shift + click – to select multiple events at once.

Accept / reject or dismiss events is also possible using the right mouse button. Select the event and click the right mouse button. Click the appropriate menu option from the dropdown list.

DISMISS EVENTS

There are also events that appear in the task list to inform the MIP Gateway Operator of important events (for example to report an aborted session to another node). In this case the MIP Gateway Operator can only dismiss the event.

Some information – events may require that you contact the other MIP nation. These kind of actions are outside the scope of this chapter.

� Select the event. � Click the button Dismiss to indicate that you are aware of the event

that took place. The event will be removed from the list.

Multiple events can be accepted / rejected or dismissed. Use the keys ctrl + click – to select one event at a time. Or shift + click – to select multiple events at once.

Accept / reject or dismiss events is also possible using the right mouse button. Select the event and click the right mouse button. Click the appropriate menu option from the dropdown list.

INDEX


A

Aborting a session 18 Accept a contract proposal 29 Activate a contract subscription 31 Add OIGs to a contract 27 Automatically accept a contract proposal 30

C

C2 IEDM 1 C2 Information Exchange Data Model (C2 IEDM) 1 C2 Information System (C2 IS) 2 C2 IS 2 Change node status 8 Check if node is alive 17 Close incoming session 16 Close outgoing session 16 Configuration options 15 Configure a remote node 13 Configure the local node 6 Configuring the Gateway 6 Contract management window 27 Create a contract 27 Create an OIG 22

D

Data Exchange Mechanism 1 Data exchange mechanism solution 1 Database settings 15 Deactivate a contract subscription 32 Default OIGs 23 Delete a contract subscription 33 Dismiss the event 38

E

Escalation procedure 34 Exchange Command and Control data 6 Exchange node configuration information 8 Exit the application 4 Export an OIG 23 Export shopping list 8

I

Import OIG(s) 24 Incoming session 15 IP Address 8

L

Local node 1 Logging Gateway data 5

M

Management settings 14 MIP 1 Multilateral Interoperability Programme (MIP) 1

N

Node ID 7 Node settings 13 Node-id 1

O

OIG 1 Open outgoing session 16 Open the gateway 4

INDEX


Open the task window manually 37 Operational bulk 35 Operational Information Group (OIG) 22 Operational synchronization 2 Outgoing session 15, 16

P

Propose a contract 27 Proposer of the contract 27 Protocol settings 14

R

Receiver of the contract 27 Reject a contract proposal 29 Remote node 1 Remote node properties 12 Remove a local node 20 Remove a remote node 19 Request management bulk 35

S

Save shopping list 8 Scope 2 Send and request operational bulk 35 Send catalog bulk 34 Send management bulk 34 Sending and requesting bulk information 34 Shopping list 8 Shut down the application 4 Specific plan complete 23 Synchronize two MIP Nodes 34

T

Task window 37 TCP port 1 Transfer of incoming data 19 Transfer of outgoing data 18

mip - dem gateway 2

Documents