Mip - Dem Gateway 2

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

© Copyright Ministry of Defence

Ministry of Defence / DMO / WSB / LA / C2 Support CentreC2SC/MIP DEM

MIP - DEM Gateway 2.0 Operator - SUM

UNCLASSIFIED

PREFACE

Version history

Version Date Author(s) Description: Status

0.0.1 10012007 M. Fuchs First version 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

DEM 01.01; Version 0.0.1; document.doc ii Ministry of Defence / DMO / WSB / LA / C2SC

PREFACE

Contact information

C2SC Front Office

TelephoneCIVIL: 0318 - 683636 ((+31)318683636)MDTN: *06 - 678 83636

FaxCIVIL: 0318-681545 ((+31)318681545)MDTN: *06-678-81545

GSM (+31)612995745

Email: Internal:

c2sc/st/frontoffice External:

[email protected]

Postal address Elias BeeckmankazerneMPC 41 AP.O. Box 90126710 HC EdeThe Netherlands

Visiting addressElias BeeckmankazerneNieuwe kazernelaan 10Building: 3 Room: 20/216711 JC EdeThe 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

DEM 01.01; Version 0.0.1; document.doc iii Ministry of Defence / DMO / WSB / LA / C2SC

TABLE OF CONTENTS

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

Version history.....................................................................................iiVersion coding.....................................................................................iiDocument references..........................................................................iiContact 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....................................................3

Open the gateway...................................................................................3

Exit the Gateway.....................................................................................3

Logging Gateway data............................................................................4

Configuring the Gateway.........................................................................5

Introduction configuring the Gateway.....................................................5

Configure nodes.....................................................................................5

Configure the local node.....................................................................5Change node status............................................................................7Exchange node configuration information / save shopping list...........7Add the remote node..........................................................................8Node overview..................................................................................10Node properties................................................................................10Configure remote node.....................................................................11

Change session status.........................................................................14

Change the status of outgoing sessions...........................................14Change the status of incoming sessions..........................................15

Check if node is alive............................................................................15

Abort sessions......................................................................................16

Remove a node....................................................................................17

Remove a remote node....................................................................18Remove the local node.....................................................................18

Managing OIGs......................................................................................20

Introduction Managing Operational Information Groups.......................20

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

Export an OIG.......................................................................................21

Import an OIG.......................................................................................22

Results in C2 IS................................................................................23

Managing Contracts...............................................................................25

Introduction Managing contracts..........................................................25

Propose a contract................................................................................25

Accept or reject the contract proposal..................................................27

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

Activate or deactivate the contract subscription...................................29

Deactivate the contract subscription.................................................30

Delete the contract subscription...........................................................31

Auto accept a contract proposal...........................................................31

Sending and requesting bulk information...........................................33

Introduction Sending and requesting Bulk information.........................33

Send Catalog bulk................................................................................33

Send and request management bulk....................................................33

Send management bulk....................................................................33Request management bulk...............................................................34

Send and request operational bulk.......................................................34

DEM 01.01; Version 0.0.1; document.doc iv Ministry of Defence / DMO / WSB / LA / C2SC

TABLE OF CONTENTS

Send operational bulk.......................................................................34Request operational bulk..................................................................35

Managing tasks......................................................................................36

Introduction Managing tasks.................................................................36

Open the task window..........................................................................36

Accept or reject events.........................................................................36

Dismiss events......................................................................................37

Index.........................................................................................................38

DEM 01.01; Version 0.0.1; document.doc v Ministry of Defence / DMO / WSB / LA / C2SC

INTRODUCTION MIP DEM GATEWAY

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 (C2 IEDM). This model consists of a common interface (the MIP Gateway) and two exchange mechanisms:Message Exchange Mechanism (MEM).Data Exchange Mechanism (DEM).

The MIP – DEM is used to exchange data between MIP nations.The DEM (Data Exchange Mechanism) is used to exchange the information stored in the C2IEDM.

THE MIP DEM CONCEPT

The Data Exchange Mechanism is an automatic data push mechanism. If the information in a C2 Information System (C2IS) is changed, this is recognized by the DEM. The change in information is automatically replicated (disseminated) to all MIP nations that have a subscription for this particular information.

Data Exchange Mechanism solution

The Ddata Eexchange Mmechanism solution is depicted hereafter.

NLD

ISIS

C2WS DB

ISISISIS

C2WS DB

MCIC2IEDMC2IEDMC2IEDMC2IEDM

NATIONAL

C2IS (B)NATIONAL

C2IS (B)NATIONAL

C2IS (B)

ODB

INTERNATIONALMIP SOLUTION(Lingua Franca)

INTERNATIONALMIP SOLUTION(Lingua Franca)

NATION B

MAPPING

MAPPING

CONTEXT

CONTEXT

CONTEXT UPDATE

CONTEXT UPDATE

12

4 4

5 5

3

The solution consists of the following elements:

Configuring the Gateway. To enable data transfer, the local node needs to be configured; remote node(s) need to be added and data transfer sessions need to be opened. This process is described in the chapter “Configuring the Gateway”.

Mapping of Operational Information Groups (OIGs). An OIG is a collection of data (units, control features etc.) that can be compared with a ‘Context’ in ISIS. In the mapping phase, the information in an OIG is ‘translated’ to the corresponding information in the ISIS context (and vice versa). MIP rules specify how this information is disseminated to other units. How to create and edit an OIG for the 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 information. How to manage contracts is explained in the chapter “Contract ManagementManaging Contracts”.

DEM 01.01; Version 0.0.1; document.doc 1 Ministry of Defence / DMO / WSB / LA / C2SC

BC2SCEI1, 10-01-07,

Ik mis toch nog een wat algemenere introductie waarin termen als ‘sessie’, ‘node’, ‘contract’ etc worden verklaard en in samenhang met elkaar worden gebracht.

INTRODUCTION MIP DEM GATEWAY

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.


GENERAL FUNCTIONS MIP DEM GATEWAY

OPEN THE GATEWAY

Make sure you are logged in as Administrator.

2

3

4

1

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.

1

2

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


BC2SCEI1, 10-01-07,

Is volgens mij niet de bedoeling. Je zou op z’n hoogst kunnen zeggen dat je Administrator rights moet hebben…

GENERAL FUNCTIONS MIP DEM GATEWAY

1

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.


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. Exchange node configuration information/ save shopping list. 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 Manger.


BC2SCEI1, 10-01-07,

Wellicht beter om deze twee in volgorde om te draaien


1

2

3

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.

12

3

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

1

2



Enter the IP Address of the MIP 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.

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.

Exchange node configuration information / save shopping list

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 youwant 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 File. The menu opens. Select the option Export shopping list from the menu.



1

3

2

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

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

2

3

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



1

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

1

2

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

1

2

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

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.

(iets van: )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.

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.



1

2

Right click the remote node for which the configuration settings should be changedproperties need to be checked. The drop down menu opens.

Select the option Configuration Properties from the menu.

2

1

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



Open configuration window

1

2

Right click the remote node for which the configuration settings should be changed. The drop down menu opens.

Select the option Configuration from the menu.

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

3

2

1

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


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



3

1

2

Select the tab Protocol. Change protocol settings. Click the button OK.

Management settingsIn the overview “Management settings”, it can be configured whether specific management events should be automatically accepted by the gateway.

3

1

2

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



In the overview of the “Database settings” , it can be configured whether the integrity of the database should be checked for incoming an outgoing data.

3

1

2

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.

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 – can be created and send. This list is send through other (digital) media after all.

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


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

BC2SCEI1, 10-01-07,

Zou na deze wijziging eigenlijk onder de par ‘change node status oid komen’.


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 sessionA session can be closed by either the receiver of operational data (Data Receiver) or the sender.

1

2

3

4

Right click the remote node for which the outgoing session should 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 or aborted.



1

2

3

4

Right click the remote node for which the incoming session should be closed. The drop down menu opens.

Select the option Session from the menu. The second menu opens. Select the option Incoming session from the menu. The third menu

opens. Select the option Close incoming session or Abort Incoming session

from the menu.

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

CHECK IF NODE IS ALIVE

The option Check if node is alive is used to check 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. whether the connection with the remote node is still OK.

1

2

Right click the remote node for which the node connection should be checked. The drop down menu opens.

Select the option Properties.

X

Click the button Check if node is alive.


The status of the incoming and outgoing session are displayed per remote node. Just behind the status information the indications (MA) or (AC) are displayed. This is an indication whether the local or remote node is able to receive ONLY Management data (MA) or if the node can receive both Management AND Operational data (AC).

BC2SCEI1, 10-01-07,

Zou na deze wijziging eigenlijk onder de par ‘change node status oid komen’.


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. You can: 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 sessionX

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. Select the option Outgoing session from the menu. 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

1

2

3

4

Right click the remote node for which the incoming session should be aborted. The drop down menu opens.

Select the option Session from the menu. The second menu opens. Select the option Incoming session from the menu. 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 thate all outgoing and incoming sessions to and from the MIP Gatewayremote node are closed.



Remove a remote node

3

4

2

1

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.

1

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!



1

3

2

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

1

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

1

2

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


MANAGING OIGS

1

23

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.


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 (C2 IS) 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 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.

1

2

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


MANAGING OIGS

1

2

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.

1

32

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 C2 Information System (C2 IS) from other MIP nations.from a file.


MANAGING OIGS

1

2

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

1

2

3

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

1

The system gives a notification if the OIG file has been successfully imported. Click the button OK.

Results in C2 IS

The MIP system updates the new imported OIG data in the operational 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.


MANAGING OIGS

1

2

3

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

1

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

1

2

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

2

1

Select the remote node to which a contract should be proposed from the list.

Click the button Propose.

1

23

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

1

2

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.


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 in their task listof your contract proposal.The following is described from the point of view of the receiver of the contract.

If the events are automatically managed, the MIP nations do not have to accept or reject events (see the section “Configure remote node”).

1

32

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 contract proposals can be accepted / rejected. Use the keys ctrl + click – single selection of events. Or shift + click – to multi selection events.

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.


MANAGING CONTRACTS

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

1

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.

1

2

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

1

2

3


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 SUBSCRIPTION

1

2

3

Select the remote node from the drop down list. Expand the list of publications or subscriptions (depending whether

you are the data provider or data-receiver for the contract). Select a publicationcontract. The publication contract 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

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.

1

2 3

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.


BC2SCEI1, 10-01-07,

Terminologie… wellicht DP/DR? (heeft ook invloed op de rest van het verhaal)

BC2SCEI1, 10-01-07,

Nogmaals: ik zou hier het woord ‘subscription’ weghalen… (en verderop ook)

MANAGING CONTRACTS

3

4

1

2

Select the remote node from the drop down list. Expand the list of subscriptions or publications. Select a subscriptioncontract. The subscription contract has the status Inactive by default. Click

the button Refresh to refresh the subscriptioncontract.

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.

3

1

4

2

Select the remote node from the drop down list. Expand the list of publications / subscriptions. Select the subscriptioncontract. Click the button Deactivate to deactivate the subscriptioncontract.


MANAGING CONTRACTS

DELETE THE CONTRACT SUBSCRIPTION

3

4

1

2

Select the remote node from the drop down list. Expand the list of publications / subscriptions. Select the subscriptioncontract. Click the button Delete to delete the subscriptioncontract.

1

Click the button Yes to confirm the deletion.

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.


BC2SCEI1, 10-01-07,

Dit verhaal staat er nu 2 keer in!

MANAGING CONTRACTS

1

2

Right click the Remote node of which the settings should be changed.

Select the option Configure…

1

2

3

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.


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.

X

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.

X

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.


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.

X

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.

X

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:

1

2

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


BC2SCEI1, 10-01-07,

Let op: dit geldt alleen voor twee specifieke events: automatic accept contract proposal en automatic accept sync request!! NIET VOOR ALLE MANAGEMENT EVENTS!

BC2SCEI1, 10-01-07,

Consequent Hoofd of kleine letter…

MANAGING TASKS

1

32

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 unordered events. Or shift + click – to select ordered events.

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

1

2

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 unordered events. Or shift + click – to select ordered events.

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 16Accept a contract proposal 27Accept an event 36Accept or reject an event 36Activate a contract subscription 29Add a remote node 8Add OIGs to a contract 25Automatically accept a contract proposal 28, 31Automatically import configuration information 8

C

C2 IEDM 1C2 Information Exchange Data Model (C2 IEDM) 1C2 Information System (C2 IS) 2C2 IS 2Change node status 7Check if node is alive 15Close incoming session 15Close outgoing session 15common interface 1Configuration options 13Configure a remote node 11Configure the local node 5Configuring the Gateway 5Contract management window 25Create a contract 25Create an OIG 20

D

Data Exchange Mechanism 1

Data Exchange Mechanism (DEM) 1Data exchange mechanism solution 1Database settings 13Deactivate a contract subscription 30Default OIGs 21Delete a contract subscription 31DEM 1Dismiss the event 37

E

Escalation procedure 33Exchange Command and Control data 5Exchange node configuration information 7Exit the application 3Export an OIG 21Export shopping list 7

I

Import OIG(s) 22Incoming session 14IP Address 7

L

Logging Gateway data 4

M

Management settings 13Manually enter configuration information 8MIP 1Multilateral Interoperability Programme (MIP) 1


INDEX

N

Node ID 6Node settings 12

O

OIG list 21Open outgoing session 14Open the gateway 3Open the task window manually 36Operational bulk 34Operational Information Group (OIG) 20Outgoing session 14

P

Propose a contract 25Proposer of the contract 25Protocol settings 12

R

Receiver of the contract 25Reject a contract proposal 27

Reject an event 36Remote node properties 10Remove a local node 18Remove a remote node 18Request management bulk 34

S

Save shopping list 7Scope 2Send and request operational bulk 34Send catalog bulk 33Send management bulk 33Sending and requesting bulk information 33Shopping list 7Shut down the application 3Specific plan complete 21Synchronize two MIP Nodes 33

T

Task window 36Transfer of incoming data 17Transfer of outgoing data 17


Date post:	13-Nov-2014
Category:	Documents
Upload:	api-3727060
View:	161 times
Download:	0 times

Mip - Dem Gateway 2

Documents