Beruflich Dokumente
Kultur Dokumente
C2SC/MIP DEM
Document identification:
Code: DEM 01.01
Version: 0.0.1
Status: Draft
©
Copyright Ministry of Defence
PREFACE
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.
Contact information
− Telephone
CIVIL: 0318 - 683636 ((+31)318683636)
MDTN: *06 - 678 83636
− Fax
CIVIL: 0318-681545 ((+31)318681545)
MDTN: *06-678-81545
− GSM (+31)612995745
− Email:
Internal:
c2sc/st/frontoffice
External:
c2sc.st.frontoffice@rnla.mindef.nl
− Postal address
Elias Beeckmankazerne
MPC 41 A
P.O. Box 9012
6710 HC Ede
The Netherlands
− Visiting address
Elias Beeckmankazerne
Nieuwe kazernelaan 10
Building: 3 Room: 20/21
6711 JC Ede
The Netherlands
Introduction configuring the Gateway.............................. ......................5 Activate or deactivate the contract subscription.............................. .....29
Deactivate the contract subscription....................... .........................30
Configure nodes..................................................................... ...............5
Delete the contract subscription................................. .........................31
Configure the local node.................................................... ................5
Change node status.................................................................... .......7 Auto accept a contract proposal....................................... ...................32
Exchange node configuration information / save shopping list...........7 ...................................................................................................... ..........34
Add the remote node............................................... ..........................8
Node overview................................................................. ................10 Introduction Sending and requesting Bulk information....................... ..34
Node properties........................................................ .......................10 Send Catalog bulk............................................................... ................34
Configure remote node...................................... ..............................11
Change session status..................................................... ...................14 Send and request management bulk.......................................... .........34
Change the status of outgoing sessions..........................................14 Send management bulk................................................... ................34
Change the status of incoming sessions.................................. ........15 Request management bulk............................................ ..................34
Check if node is alive........................................... ...............................16 Send and request operational bulk....................................... ...............35
INTERNATIONAL
NLD MIP SOLUTION NATION B
GENERAL INTRODUCTION 5 (Lingua Franca)
5
CONTEXT CONTEXT
UPDATE UPDATE
MCI 4
O O
when.
ODB
C2 IEDM C2WS DB
The core of the MIP solution is the C2 Information Exchange Data Model
(C2 IEDM). This model consists of a common interface (the MIP
Gateway) and two exchange mechanisms:
− Message Exchange Mechanism (MEM).
− Data Exchange Mechanism (DEM). 2 1 3
The MIP – DEM is used to exchange data between MIP nations.The DEM The solution consists of the following elements:
(Data Exchange Mechanism) is used to exchange the information stored
in the C2IEDM. Configuring the Gateway. To enable data transfer, the local node
needs to be configured; remote node(s) need to be added and data
THE MIP DEM CONCEPT
transfer sessions need to be opened. This process is described in
The Data Exchange Mechanism is an automatic data push mechanism. If the chapter “Configuring the Gateway”.
the information in a C2 Information System (C2IS) is changed, this is Mapping of Operational Information Groups (OIGs). An OIG is a
recognized by the DEM. The change in information is automatically collection of data (units, control features etc.) that can be compared
replicated (disseminated) to all MIP nations that have a subscription for with a ‘Context’ in ISIS. In the mapping phase, the information in an
this particular information. OIG is ‘translated’ to the corresponding information in the ISIS
context (and vice versa). MIP rules specify how this information is
Data Exchange Mechanism solution
disseminated to other units. How to create and edit an OIG for the
The Ddata Eexchange Mmechanism solution is depicted hereafter. MIP Gateway, so that the OIG can be disseminated, is explained in
the chapter “Configuring Managing OIGs”.
Propose a Contract. A contract is an agreement between different
MIP nations to receive and deliver particular information (OIGs). A
contract is proposed by the MIP nation that wants to send
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.
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.
2 2
4
There are several ways to open the application. You can also
use the short cut on the desk top, if available.
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.
CONFIGURE NODES
1
2
2
3
2
Select the option Management from the list.
The node status of the local node will change from Active (AC) to
Management (MA).
All nodes of the other MIP nations to which you have an open session are
now informed that your node status has changed to MA. You will not
receive any operational data. When you want to be able to receive
operational data, you have to change the node status back to Active. Select the option File. The menu opens.
Select the option Export shopping list from the menu.
1 3
The shopping list is used for the configuration of the remote node.
Select the option Node. The dropdown menu opens.
Add the remote node Select the option Remote Node. The second menu opens.
Each node you want to exchange data with must be added as a remote Select the option Add from the menu.
node on your system.
To add the remote node, the following node configuration information
should be added to the local MIP node: node ID, node name, Mgt Owner-
id, IP address and port number of the remote node. This information can
be added in two ways:
− Automatically import configuration information.
− Manually enter configuration information.
1
2
Click the button Open to import the details of the remote node. Select the shopping list from which the details have to be imported.
Click the button Open.
The combination of IP address and port number should have
the following format: IP <space> port number. For
example:10.0.18.41 11000
3
The details of the remote node are added to the fields in the window
Create remote node.
Change the pre-selected node address of your system to the
address of the remote node (normally the default value). 2
Click the button OK to save changes and close the window.
The local node is displayed in the caption of the window.
Manually enter configuration information The remote node is displayed in the field Remote nodes.
If the shopping list is not available or the list cannot be send, you have to Node properties
enter the details of the remote node manually.
The properties of the remote node can be checked by using the option
(iets van: ) Properties.
The new node will now be added to the ‘Remote nodes’ section.
2
All details (name and others) of the remote node are listed in the
window Node Details.
Right click the remote node for which the configuration settings Click the button Close to close the property window.
should be changedproperties need to be checked. The drop down
menu opens. Configure remote node
Select the option Configuration Properties from the menu. The configuration of remote nodes is only changed with assistance form
from the support desk. Only functions which may be changed by the
operator are discussed here.
1
2
3
1
1
2
2
3 3
Management settings In the table hereafter, the configuration options are described.
In the overview “Management settings”, it can be configured whether
specific management events should be automatically accepted by the Option Description
gateway. Auto accept operational synchronization If the option Auto accept operational
request synchronization request has been ticked, all
operational datarequests from the remote
node to receive an operational bulk will be
automatically synchronizedaccepted.
Auto accept contract proposal If the option Auto accept contract proposal
has been ticked, any contract proposals
from the MIP nation that owns the remote
node will be automatically accepted.
Database settings
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
3 3
1 1
4
4
2 2
Right click the remote node for which the outgoing session should Right click the remote node for which the outgoing session should
be opened. The drop down menu opens. be closed. The drop down menu opens.
Select the option Session. The second menu opens. Select the option Session. The second menu opens.
Select the option Outgoing session. The third menu opens. Select the option Outgoing session. The third menu opens.
Select the option Open outgoing session from the menu. Select the option Close outgoing session from the menu.
The status Outgoing of the remote node will change to Open. Operational The status Outgoing of the remote node will change to Close.
data from the local node can flow to the remote node and vice versa.
Change the status of incoming sessions
Close outgoing session
A session can be closed by either the receiver of operational data (Data An incoming session can only be closed or aborted.
Receiver) or the sender.
4 1
2
Right click the remote node for which the incoming session should
be closed. The drop down menu opens. 2
Select the option Session from the menu. The second menu opens.
Select the option Incoming session from the menu. The third menu Right click the remote node for which the node connection should
opens. be checked. The drop down menu opens.
Select the option Close incoming session or Abort Incoming session Select the option Properties.
from the menu.
X
The status Incoming of the remote node will change to Close. Data from
the local remote MIP Gateway will not be transferred to theyour remote Click the button Check if node is alive.
local node.
If the node connection is OK, the notification Check successful Abort an incoming session
appears. 3
Click the button Close.
ABORT SESSIONS
Right click the remote node for which the outgoing session should
be closed. The drop down menu opens.
Select the option Session from the menu. The second menu opens. Right click the remote node for which the incoming session should
Select the option Outgoing session from the menu. The third menu be aborted. The drop down menu opens.
opens. Select the option Session from the menu. The second menu opens.
Select the option Abort outgoing session from the menu. Select the option Incoming session from the menu. The third menu
opens.
The transfer of outgoing data from the local MIP Gateway to the remote Select the option Abort incoming session from the menu.
node will be aborted.
The transfer of incoming data from this remote node to the local MIP
Gateway will be aborted.
REMOVE A NODE
You can remove remote nodes as well as your own (local) node.
2 1
Select the remote node to be removed. Remove the local node only if you are absolutely sure. All
Select the option Node. The dropdown menu opens. remote nodes will be removed as well!
Select the option Remote Node. The second menu opens.
Select the option Remove.
After the local node and remote node(s) are configured, the OIGs have to
be created.
The OIG can be read, edited and removed in a national Command &
Control Information System, such as the application ISIS.
The amount and kind of OIGs transferred is regulated through Select the option OIG. The dropdown menu opens.
so-called “Contracts”. How to manage contracts is explained in Select the option Create single OIG.
the section “Managing Contracts”.
1 EXPORT AN OIG
The function Export OIG(s) is used to export OIGs to the C2 Information
System (C2 IS) of other MIP nations, if there is no connection available.
3 2 An export will result in a file that contains the selected OIG(s) in the MIP
format. This file can be exchanged via any digital medium. Other nodes
can Import this file and the result will be the same as if the remote node
had received the OIG(s) via the MIP Gateway.
After a refresh of the C2 IS, this update will be visible in the OIG list of the
C2 IS.
Enter the name of the organization which is responsible for the OIG.
This is the name of the local node. 1
Select the type of OIG from the list.
2
There are six uniquely identified default types of OIGs:
− Friendly and neutral organizational.
− Friendly and neutral object.
− Globally significant.
− Enemy uncorrelated.
− Enemy correlated.
− Specific plan complete.
Of each type, you need to create one OIG. For the type “Specific plan
complete”, more OIGs can be created.
In one mission, there can be several OIGs of the type “Specific plan Select the option File. The dropdown menu opens.
complete”. Therefore, each plan OIG is identified with a number. Select the option Export OIG(s).
Click the button OK.
2 3
The system gives a notification if the OIG file has been successfully
imported. Click the button OK.
1
Results in C2 IS
The MIP system updates the new imported OIG data in the operational
2 database (for example the C2 FW database). The operational database
communicates the update (if any) to the C2 IS. In the example here after,
the results of an import in the C2 IS “ISIS” are shown.
3 1
The updated OIG(s) are green –coloured and shown in the library. New or changed OIGs are also displayed on the GIS.
PROPOSE A CONTRACT
The MIP nation that wants to share OIG datas (proposer of the contract),
proposes a contract to the MIP nation(s) it wants to share its OIG data
with (receiver of the contract). The MIP nation can propose contracts from
its “publications” as well as from its “subscriptions”that contain both locally
created OIGs as well as OIGs that where created by another MIP Node.
If the MIP Gateway is configured and the OIGs are created, you can
propose a contract for a set of OIGs to another MIP nation. The other 1
nation can propose a contract for a set of OIGs to you as well.
1
1
3
2
1
The proposer of the contract will see any subscriptions in its list of
publications, after he has refreshed his contract overview.
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.
2
2
Select the tab Management. Select the remote node from the drop down list.
Tick the option Auto accept contact proposal. Expand the list of publications or subscriptions (depending whether
Click the button OK. you are the data provider or data-receiver for the contract).
Select a publicationcontract.
If a contract proposal is sent (see the section “propose a contract”), the The publication contract has the status Inactive by default. Click the
other MIP nation will receive a notification of acceptation. button Activate to activate the publication.
ACTIVATE OR DEACTIVATE THE CONTRACT SUBSCRIPTION Both receiver and proposer of the contract can activate the contract. If the
receiver of the contract activates the contract however, the proposer
provider of the contract receives a notification and has to accept a
notification that the receiver wants to activate the contractthe activation of
the contract.
3
2
1
2 3
Select the request for activation. Select the remote node from the drop down list.
Click the button Accept to accept the activation. Expand the list of subscriptions or publications.
Click the button Reject to reject the activation. Select a subscriptioncontract.
The subscription contract has the status Inactive by default. Click
To see the changes, the receiver of the contract has to refresh its contract the button Refresh to refresh the subscriptioncontract.
overview.
Deactivate the contract subscription
Both receiver and proposer of the contract can deactivate the contract
subscription. This may be necessary if one of the MIP nations is
reconfiguring its nodes for exampleor if an error is detected in an OIG of
the contract. The following example is described from the point of view of
the data receiver.
3
2 1
4
3
2
AUTO ACCEPT A CONTRACT PROPOSAL Right click the Remote node of which the settings should be
changed.
By default, the settings of the gateway are such, that contracts are Select the option Configure…
automatically accepted by the system of a MIP nation. You can change
these settings for each remote unit separately.
When the MIP Gateway is configured, Operational Information Groups A Management bulk contains all the information from the Management
(OIGs) are being sent or updated and contracts are managed. Bulks are database that is relevant for the MIP Gateway of another MIP nation (for
used to synchronize two MIP Nodes. Three different kinds of bulks can be example the contracts and the statuses of these contracts). The
exchanged: Management bulk is automatically exchanged when a session is opened
− Catalog bulk. to a remote node. If the management data is modified the other node is
− Management bulk. automatically informed as well (after the session is opened).
− Operational bulk.
Send management bulk
Normally, synchronization is performed automatically and no human In case the remote node is not correctly synchronized (for example
intervention is required to send bulks. In some cases however it is useful because data is manually manipulated in the database), a Management
to send or request this bulk manually. For instance when the national bulk needs to be sent.
database has crashed, or when the Gateway has been out of order for a
time. X
If the database has crashed, follow the escalation procedure. Right click the remote node to which management bulk should be
Ask the support desk for assistance. send. The drop down menu opens.
Select the option Send. The second menu opens.
In the following paragraphs the meaning of each type of bulk is explained. Select the option Send Management bulk.
Request management bulk
SEND CATALOG BULK
In case the management data of the remote MIP node are manipulated
The Catalog bulk contains the list of available OIGs on which the remote without synchronizing, you need to request a management bulk from that
node can be subscribed. If the remote node needs an update of the list of node.
available OIGs, a catalog bulk needs to be send (for example because
data has been entered into the database by hand). X
Right click the remote node from which management bulk should be
requested. The drop down menu opens.
Right click the remote node to which the Catalog bulk should be Select the option Request. The second menu opens.
send. The drop down menu opens. Select the option Request Management bulk.
Select the option Send. The second menu opens.
Select the option Send Catalog bulk from the menu.
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.
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.
• Open the task window. Select the option View from the menu. The dropdown menu opens.
• Accept or reject events (Gateway Operator input is required). Select the option View Tasks.
• Dismiss events (Gateway Operator is informed about important
events). ACCEPT OR REJECT EVENTS
1
2 3
Multiple events can be accepted / rejected or dismissed. Use the Select the event.
keys ctrl + click – to select unordered events. Or shift + click – to Click the button Dismiss to indicate that you are aware of the event
select ordered events. that took place. The event will be removed from the list.
Accept / reject or dismiss events is also possible using the right Multiple events can be accepted / rejected or dismissed. Use the
mouse button. Select the event and click the right mouse button. keys ctrl + click – to select unordered events. Or shift + click – to
Click the appropriate menu option from the dropdown list. select ordered events.
DISMISS EVENTS Accept / reject or dismiss events is also possible using the right
mouse button. Select the event and click the right mouse button.
There are also events that appear in the task list to inform the MIP Click the appropriate menu option from the dropdown list.
Gateway Operator of important events (for example to report an aborted
session to another MIP node). In this case the MIP Gateway Operator can
only dismiss the event.