white paperdefencesystems.info/wp-content/uploads/2012/10/ic2is2_whitepaper… · mirka vadnova 14...

White Paper

Integrated

Command &

Control

Information

System's

Simulation

Train

ing

is Life S

av

ing

ASII/2012/IC2IS2/002 - Revision 1.02 Objectives are the Touchstones of our Character

of 28 ASII/2012/IC2IS2/002 - Revision 1.02

Preface

Trademark

All brand names and product names are trademarks or registered trademarks of

Asiistech Ltd

Copyright

©Copyright 2012 Asiistech Ltd

All rights reserved

Asiistech, tehnološki razvoj in storitve, d.o.o.

Mirka Vadnova 14 SI-4000 Kranj Slovenija Tel: 059 046 770 Fax: 059 010 144 [email protected]

www.asiistech.com

Asiistech Ltd

Mirka Vadnova 14 SI-4000 Kranj Slovenia Tel: +386 59 046 770 Fax: +386 59 010 144 [email protected]

http://www.asiistech.com/

ASII/2012/IC2IS2/002 - Revision 1.02 of 28

Contents

1 INTRODUCTION ............................................................................................................................... 4

2 OBJECTIVES ...................................................................................................................................... 6

3 STRUCTURE ...................................................................................................................................... 9

4 FEATURES ...................................................................................................................................... 10

4.1 Concepts ................................................................................................................................ 10

4.1.1 Real vs C2 data .............................................................................................................. 11

4.1.2 SIM to C2 ....................................................................................................................... 12

4.1.3 Sensor data vs C2 data .................................................................................................. 12

4.1.4 Distributed C2 environment .......................................................................................... 12

4.1.5 Operation type .............................................................................................................. 13

4.1.6 Fog of war ...................................................................................................................... 14

4.1.7 Classroom – Configuration – Scenario - Execution isolation ......................................... 14

4.2 IC2IS2 Configuration .............................................................................................................. 16

4.3 IC2IS2 Planning ...................................................................................................................... 17

4.3.1 ORBAT Editor ................................................................................................................. 18

4.3.2 Map Module .................................................................................................................. 19

4.3.3 Data Distribution Editor................................................................................................. 19

4.3.4 Event Editor ................................................................................................................... 20

4.3.5 Blue vs Blue War-gaming Module ................................................................................. 21

4.4 IC2IS2 Execution .................................................................................................................... 21

4.4.1 Virtual Sensor System .................................................................................................... 22

4.5 Simulated Voice Networks .................................................................................................... 23

5 TRAINING & EXPERIMENTING ....................................................................................................... 25

5.1 IC2IS2 roles ............................................................................................................................ 25

5.2 Basic training/experimenting ................................................................................................ 25

5.3 Blue Vs Blue War-gaming ...................................................................................................... 26

6 BENEFITS ........................................................................................................................................ 27

7 TECHNICAL SPECIFICATIONS .......................................................................................................... 28


1 INTRODUCTION

In recent years, modern warfare is strongly influenced by the paradigm of Network

Centric Warfare (also NNEC – NATO Network Enabled Capabilities). Military

effectiveness is significantly correlated with the employment of modern

communication and information systems, both providing a means for improved

information sharing and collaboration. Both of them enhance the quality of

information, shared situational awareness and self-synchronisation thus enhancing

sustainability and speed of command. These in turn dramatically increase mission

effectiveness. However, the transition from theory into practice has to take into the

account the limitation factors:

- Information domain limitations; Communication systems are subject to

physical constraints (electromagnetic waves: emitting power, wavelength,

bandwidth) and jamming, resulting in non-reliable data transfer and data

latency. Information systems on other hand, demand data integration and

process optimisation to successfully exploit new capabilities.

- Cognitive domain enables the translation of data and information provided

by information domain into shared awareness and self synchronisation. The

translation takes place inside human brains and is therefore subject to

individual human perception burdened with social, cultural, educational and

religious differences. Information comprehension is furthermore affected by

data latency, erroneous data, missing data and data overflow.

The cognitive domain and its dependency on information domain represent key

success factor to effective command and control (hereafter C2). Understanding the

limitations of information domain and using its powers in a correct way are two

elements that cannot be provided by technical solutions, but only by consistent

TRAINING AND EXPERIMENTATION.


Figure 1: The role of IC2IS2

Integrated Command & Control Information System's Simulation (hereafter IC2IS2)

was developed to provide military community with the generic training and

experimenting platform. IC2IS2 suite combines the capabilities of standard military

simulations and modern Command and Control Information Systems (hereafter

C2IS). IC2IS2 works as a generic intermediate between Live, Virtual or Constructive

(hereafter LVC) military simulations and C2IS.

IC2IS2 is a highly scalable training and experimenting platform that can be easily

tailored to a specific customer’s requirements, either by adding specific LVC

simulation or by linking it to a particular C2IS.


2 OBJECTIVES

It is evident, that the binding of LVC simulation systems and C2IS, represents next

logical step in C2 training and experimenting. Successful roll-out of C2IS, seen in the

last decade, has put forward new training requirements, involving simultaneous

usage of LVC simulations and C2IS through computer aided exercises.

The paradigm of »war-gaming network-centric warfare« describes the nature of C2

training and experimenting in NCW.

In training process, the objective is to acquaint players with warfare situations and

exercise their decision-making skills. The »realistic« component may be ignored in

the training process, where SIM scenarios may somewhat stretch the bounds of

probability to reach the training objectives. However, experimenting is designed to

generate insights into military problems - realism becomes a vital component.

The only way to game network-centric warfare is to create a network of players with

shared awareness. Units in the network must be able to generate information for

headquarters, and anomalous behaviour on the part of a few units is necessary in

order to create realism in the command centre. To achieve that, distributed gaming is

necessary. C2IS technology that distributes the gaming must be the same as is used

by the units in actual operations and the trainees must not be allowed perfect

knowledge on the »ground truth«. The ground truth requirement demands that the

trainees must rely on their own interpretations of the “observables”, supplied to

them where:

- The information is distributed through C2IS network. Each unit (C2 node) is a

producer of its own information and receiver of other unit's information

according to data distribution rules. In practice, it means that the operational

picture will vary from C2 node to C2. The level of variation is correlated to

»information distance«, function of: data distribution rules, number of

intermediate C2 nodes (networks), bandwidth and jamming.

- The information on a particular C2 node is burdened with time delay,

function of: bandwidth, number of intermediate C2 nodes and jamming.

- The information about »non-Blue« C2 objects is time dependent in a sense

that the information evolves through time. As the game continues more and

more information is available – the knowledge is upgraded.

- Intelligence data, in particular, consists of reports/observations which

frequently are a subject of human perception. Uncertain, approximate, aged

and erroneous data is expected.

- Sensor data is by definition the most precise data. However it should be

emphasised that the data is instantly available only for the C2 node, owner of

the sensor equipment.


The producers of LVC simulations and the producers of C2IS systems are trying to

answer new challenges by:

- Incorporating C2 capabilities into the LVC simulations. This means that LVC

simulations are upgraded with »LVC command and control systems«.

- Developing C2-gateways (typically MIP gateways) for LVC simulations.

- Developing SIM-gateways for C2IS.

Each of those solutions encompasses the point of view of a native system (LVC or

C2IS), usually simplifying the other side of the challenge.

Delivering »LVC command and control system« (hereafter: LVC C2) into the LVC

simulation means that the trainees are not using the same C2IS as in a real situation.

The capabilities, functionalities and user experience of LVC C2 differs from

capabilities, functionalities and user experience of C2IS, thus producing expert users

of LVC C2 and not C2IS.

C2 gateways for LVC simulations on other hand largely simplify the nature of C2

systems. Typically they are built in a form of MIP gateways, providing SIM to MIP

data mapping. The limiting factors of these solutions are:

- Data is mapped into the C2IS in a single point – gateway, thus ignoring data

distribution throughout C2IS network.

- Data provided through the gateway is on-line generated by LVC simulation.

There is no way to fulfil the requirements related to time delay, data

evolution and generation of uncertain and erroneous intelligence data.

LVC gateways for C2IS systems could provide the solution to distributed nature of c2

environment; however it fails because of its technology orientation. Typically each

C2IS product is equipped with its own LVC gateway – one for each LVC simulation

system. The drawbacks are:

- C2 systems in the network centric environment normally involve multiple

different systems, produced by one or many different providers. The number

of LVC gateways equals the product of: number of C2IS products with the

number of LVC simulations. The maintenance of such system would be

expensive and cumbersome.

- The configuration of a certain gateway is done on the level of gateway. The

exercise/experiment, involving the usage of multiple gateways (very likely to

happen in network environment), would anticipate separate configuration of

each gateway where the configurations are mutually harmonised. The level

of complexity (imagine only adjustment of multiple ORBATS and their

mapping parameters) is too high for a »handwork«.

- Data received through the gateway is generated by LVC simulation. There is

no way to fulfil the requirements related to generation of uncertain and

erroneous intelligence data. The gateway would need its own simulation


engine to simulate erroneous data – the scope which is by definition beyond

gateway functionality.

The analysis shows that all three solutions fail to fulfil ground-truth requirement.

There are other limitations imposed to LVC simulations – especially to Virtual

simulation systems. Virtual Reality (VR - substance of Virtual simulations) is by nature

highly resource demanding – therefore constrained by available hardware resources.

The consequence is that the VR terrain is spatially constrained, usually to several km2

(up to few hundred). The effect on C2IS is shown in the absence of flanking and

superior units.

The solution to the problems, described above can be overcome only by the in-

between mediator system, with following characteristics:

- The mediator system conforms to LVC and C2 standards. At least following

standards must be supported:

JC3IEDM (Joint Consultation Command Control Information

Exchange Data Model) by MIP (Multilateral Interoperability

Programme) standards.

DIS (Distributed Interactive Simulation) by SISO (Simulation

Interoperability Standards Organisation).

- The system is generic in a way that it supports integration (connection) with

multiple different LVC simulations and multiple different C2IS systems. It

means that the system is LVC and C2IS independent.

- The system supports at least two levels of C2:

Headquarter.

Battle Management System.

- The system has to support design and creation of C2 distributed environment

(C2 networks).

- The system should comply with the »ground truth requirement« (see above).

- The system should overcome the spatial limitations of Virtual and Live

simulations.

IC2IS2 suite is Asiistech's answer to the challenge.

See chapters 3-5 for further description of IC2IS2 suite.


3 STRUCTURE

IC2IS2 consists of five main components and their adapters/gateways (see figure 2):

- Data layer consisting of Configuration database, Scenario database and

Execution database. Configuration database stores the IC2IS2 administration

data such as: SIM to C2 translation (mapping) parameters, GIS mapping

parameters and classroom configuration (see chapter 4.2 for further

explanation). Scenario database stores the data on IC2IS2 scenarios. The

execution database is used as a temporary data store during the scenario

execution.

Figure 2: IC2IS2 structure

- JCAX Administration consists of tools for the configuration of IC2IS2

environment. These tools are used to set the administrative parameters

stored in the Configuration database (see chapter 4.2 for further

explanation).

- JCAX Application layer incorporates the tools for manipulation of IC2IS2

scenario. Application layer is used to prepare and later, during the execution

phase, monitor the execution of IC2IS2 scenario. The application layer

components are further described in the chapter 4.3.

- JCAX server is an IC2IS2 component used only during the execution phase. It

means that during the preparation phase the scenario is prepared

independently of the server components. The server is the governing

component of IC2IS2 distributed environment - it runs the scenario during

the execution and harmonize the activities of all IC2IS2 parts.

- JCAX client components are installed on all of the client computers. The

Client monitor is the application that configures and monitors the software

components of IC2IS2. Virtual sensor system (VSS) is the component that

emulates the influx of sensor data (see chapter 4.4.1). Client monitor and VSS

are both hidden components of the system and are not seen by the users.


Voice client is the only client application part – user interface (simulating

intercom and combat radios), directly used by the users of the IC2IS2 (see

chapter 4.5).

- DIS gateway comes in two variations, one for IC2IS2 server and one for each

IC2IS2 client. Its role is to read data from Distributed Interactive Simulations

(SISO standard, hereafter: DIS) and transfer it either to IC2IS2 runtime server

or to particular VSS.

- Simulation specific adapters (Figure 2 - shown in cyan) are non-standardized

gateways, serving as an importer of LVC SIM scenario (see chapter 4.3.1). LVC

SIM systems are not standardized in a manner of scenario storage; therefore

it is necessary to use a specific scenario importer for each particular LVC SIM

system.

- C2 gateway serves (Figure 2 – shown in orange) as a mediator between

IC2IS2 runtime server and particular C2IS environment. Its role is to initialize

C2IS and to mediate the data from IC2IS2 server to C2IS2 nodes (see chapter

4.1.4).

4 FEATURES

4.1 Concepts

The IC2IS2 training/experimenting setting can be quite complicated. Two different

systems, LVC simulation system and C2 system, both of them complex itself, are

connected through IC2IS2 to form a single training/experimenting environment.

For the purpose of this document some of the terms used in this chapter and

thereafter are explained as:

SIM entity is an element of the simulated world that is classified by its type,

identified by its attribute values and can be manipulated. Besides simulation-

related manipulations (shooting, exploding, moving, etc) SIM entity can be

controlled by SIM scenario or manually by the human operator during the

execution of simulation.

C2 entity is an element of the C2 world that is classified by its type, identified by

its attribute values and can be manipulated (order, tactical graphic, military unit,

etc).

Trigger is a condition which, when conditions are met, raises an Event. Usually

trigger conditions are evaluated when a change of the system or entity state

occurs. One trigger can raise only one event. Action is a consequence of an

event. One event can execute one or more actions.

Activation is a special type of event, where SIM or C2 entities are activated

(become visible to trainees). With an activation entity becomes part of current

SIM Situation or current C2 Situation and performs a specific action related to


specific entity (battle vehicle becomes visible in VR world, order is sent to

subordinate units, etc).

4.1.1 Real vs C2 data

IC2IS2 assumes that the SIM component of the system plays the role of the “real-

world” while the C2 component of the system tries to mimic the behaviour of C2IS in

real environment. This means that:

- The original source of “real-world” data is simulation (with the exception of

IC2IS2 native simulation engine, see chapter 4.1.5).

- The data is first received, mapped and modified (see chapter 4.1.6) by the

IC2IS2, to be later transferred to C2IS.

- The data received by the C2IS (C2 data) therefore represents approximation

of real world data.

The consequence is that in IC2IS2 every C2 entity comprises two sets of data: real

data and C2 data.

Figure 3: Real and C2 data in IC2IS2

C2 data is mediated to C2IS in a form of »Reporting data«. The mediation requires

marking C2 data with the ownership metadata, not provided by the LVC simulation:

Reporting Unit.

By default Blue forces are owners of its own reported data. The ownership of Red

and Neutral forces data is defined piece by piece during the Scenario preparation.


4.1.2 SIM to C2

Transferring the LVC data into the C2IS data requires two operations:

- DIS to JC3IEDM mapping defines translation from DIS standard to JC3IEDM.

Mapping defines how SIM entity types (soldier, vehicle, weapon, ammunition

types) map to C2 entity types.

- Aggregation of SIM entities into C2 entities is an operation where one or

many SIM entities aggregate into C2 entity (example: 10 SIM entities -

soldiers with all of their equipment and consumables aggregate into C2

entity: 1st Infantry Squad)

4.1.3 Sensor data vs C2 data

During the IC2IS2 scenario execution phase, the LVC simulation provides the data in a

form of DIS Protocol Data Units (hereafter PDU). IC2IS2 uses the data, provided by

PDUs in two ways:

- The data is mapped and aggregated by IC2IS2 runtime server to represent C2

entities. This kind of data is delivered directly into C2IS data layers.

- The data is used to construct influx of sensor data to a particular C2 node

(example: EntityStatePDU contains positional data which is used to simulate

GPS signal for a particular BMS)

Figure 4: C2 and sensor data

See chapter 4.4 for further explanation.

4.1.4 Distributed C2 environment

Distributed C2 environment is in IC2IS2 defined through:

- ORBAT (Blue forces) defines C2 units participating in the C2 environment.

- C2 Networks = data distribution (replication) networks are prepared with DD

Editor (see 4.3.3).


- C2 units (Blue forces) are assigned to particular C2 networks (many-to-many)

Creation of distributed C2 environment is just a first (prerequisite) step when

simulating network centric warfare.

During the execution phase several other elements of IC2IS2 scenario define the

exact position in C2 environment, where the data is sent to. Receiving data

node/network is defined by:

- Reporting unit (see chapter 4.1.1).

- Reporting unit’s memberships in the C2 networks.

- The ORBAT position of reporting unit. It is assumed that if reporting unit is

not a member of any C2 network, its data is recorded into the C2IS by its

superior unit.

4.1.5 Operation type

In previous chapters the only the patterns where the data originates in LVC

simulation were discussed. In fact, IC2IS2 offers much broader spectrum of

possibilities. The origin of C2 data is fixed during the creation of ORBAT. The property

“Operation type” (see Figure 3: Real and C2 data in IC2IS2) is used to define the

originating system of C2 data:

- Data originating in LVC simulations is marked by “Simulated with centre of

gravity”.

- Data originating in IC2IS2 is marked by “Simulated with waypoints” or

“Simulated with point(s)”.

- The native C2IS data (manipulated by players) is marked by “Operated by

trainees” or “Operated by operators”.

Figure 5: IC2IS2 operation types


4.1.6 Fog of war

Since C2 data in a real C2 environment is never consistent with real-world (ground

truth requirement – see chapter 2), IC2IS2 is designed to introduce Fog-of-war

elements into C2 data:

- Erroneous data is the data that is not present in any LVC simulation system,

nor is it part of the C2IS itself. The IC2IS2 solves it by introducing native

IC2IS2 data, produced by native C2 SIM engine (part of IC2IS2 runtime server,

see Figure 15: IC2IS2 execution). The engine enables the construction of

»false« data by creating C2 units with the operation type »Simulated by

waypoints« and »Simulated by point(s)«. This kind of C2 data performs

spatial movements and reports C2 data.

- Reporting interval and data delay are two properties of C2 data affecting the

reporting frequency and age of data reported to C2. In practice, it means that

C2 reporting data will be old and reported in preset time-intervals (see Figure

6: Reporting delay).

- Activation time is another C2 metadata influencing the transmission of C2

data into C2IS. Activation time determines the time, when a certain C2 entity

becomes visible in the C2IS. The data on C2 entity is not sent to C2IS until the

execution time passes the activation time.

- Trigger-action constructs (see chapter 4.3.4) enables further data »blurring«

by freezing/unfreezing C2 data and setting new data values.

Figure 6: Reporting delay

4.1.7 Classroom – Configuration – Scenario - Execution isolation

The execution of training/experimenting scenario demands synchronisation of all

IC2IS2 components (see Figure 7: Classroom – Configuration – Scenario - Execution):

- Classroom/experimenting equipment typically consists of multiple hardware

equipment, each of them comprising its own hardware and software

configuration.


- IC2IS2 static configuration elements are seldom changed. Typical example

represents mapping configuration between standards. It would be

configured only once and then used for all of the operational activities.

- Training/experimenting scenario is basic holder of IC2IS2 scenario elements

(DIS-2-C2 aggregation, scenario ORBAT, tactical situation, C2 network, roles

in the scenario)

Figure 7: Classroom – Configuration – Scenario - Execution

Some of the facts are evident at once.

Complex scenarios would involve the participation of high number of users with

different user roles. High number of users causes even higher number of hardware

components. The coupling of user roles with available hardware components would

demand long preparation time involving number of IT experts.

Classroom configuration can alter frequently, new hardware brought in, old

hardware taken out, new software installed and old software removed/reconfigured.

IC2IS2 scenarios should be decoupled from classroom configuration. Planner should

not be constrained by available hardware/software components while preparing

training/experimenting scenario. The coupling of scenario roles and available

hardware/software should take place in the initialisation of scenario execution

phase.

The IC2IS2 incorporate tools facilitating easy scenario deployment (see chapter 4.4).


4.2 IC2IS2 Configuration

IC2IS2 Administration is an isolated process performed by IC2IS2 administrator. Only

JCAX Configuration tool is used to perform:

- Classroom management.

- Item-type management.

- DIS-2-C2 mapping.

- SIM-2-GIS mapping.

- IC2IS2 unit administration.

Figure 8: Configuration components

Classroom management contains tools for hardware and software management of

the training/experimenting environment. All the computers in the training

environment are catalogued together with their software configuration. Each

computer has listed all potential roles it can assume during the execution. The

classroom management is essential for the exercise initialisation phase, where the

IC2IS2 roles, defined in the scenario, are distributed among available classroom

computers.

Item-type management is a tool for management of holding-type definitions

according to MIP/JC3IEDM standards. Item-types are dependent on the equipment,

consumable and personnel types employed in particular armed forces. The item

types are therefore army-specific.

DIS-2-C2 mapping administration defines and manages mapping between DIS

standard and MIP/JC3IEDM standard. Mapping parameters are directly related to

holding type definitions and are therefore army-specific as well. The mapping

parameters describe how a certain type of SIM entity maps into C2 entity’s holdings.

SIM-2GIS mapping administration is used to eliminate possible spatial discrepancies

between LVC simulation's terrain and real geographic data, used in the C2IS.

IC2IS2 unit type administration enables the creation of own C2 unit type library. Unit

types facilitate rapid scenario development by eliminating repetitive actions during

the creation of scenario ORBAT.


Figure 9: IC2IS2 Configuration tool

4.3 IC2IS2 Planning

Scenario is prepared using JCAX application and its modules. The planning phase

does not involve the usage of IC2IS2 server.

Figure 10: IC2IS2 planning

Scenario preparation is a straightforward process:

- Building ORBAT, using ORBAT editor.

- Creating IC2IS2 spatial elements, using Map module.

- Constructing data distribution networks, using Data distribution editor.

- Defining advanced features by using Event editor.

- Defining trainee roles.


4.3.1 ORBAT Editor

ORBAT editor is a basic tool in the initial phases of IC2IS2 scenario preparation.

Supported functionalities:

- Creating C2 entities (C2 units).

- Arranging units into commanding hierarchy.

- Defining operation types.

- Setting unit properties (nationality, size, category, etc).

- Adding unit holdings.

- Importing LVC simulation scenario. This functionality is performed by SIM

adapter (see Figure 10: IC2IS2 planning). Every LVC simulation system

supports different kinds of SIM/C2 entities and stores the scenario in its own

data format. The result of importing therefore depends on LVC SIM system.

Some of the systems support only SIM entities, which means that the whole

ORBAT has to be prepared in IC2IS2, the others make it possible to import

the ORBAT as well. Either way, after the importing procedure, the IC2IS2

process continues similarly.

- Defining aggregation rules = arranging SIM entities into joint IC2IS2 ORBAT.

- Defining C2 data ownership (reporting unit).

- Setting C2 reporting parameters (activation time, time delay, reporting

interval)

Figure 11: ORBAT editor


ORBAT editor has incorporated many useful features:

- C2 filtering.

- SIM filtering.

- Switching the view between Real data view and C2 data view.

4.3.2 Map Module

Map module is used to:

- Create spatial references for the units that are not linked to SIM entities

(Simulated by centre of gravity).

- Draw waypoints and points for units with operation type: Simulated by

waypoints and Simulated by point(s).

- Draw tactical graphics (C2 data).

- Draw IC2IS2 control lines – part of spatial triggering mechanism (see chapter

4.3.4)

Figure 12: Map module

Map module offers standardised military simbology. It has incorporated play

capabilities, thus helping the scenario player to play through IC2IS2 native simulation

elements (waypoints, triggers-actions, etc).

4.3.3 Data Distribution Editor

Data distribution editor is a powerful tool used to create C2 distributed environment:

- Design data replication networks.


- Assign replication membership to C2 entities. Every “Blue” C2 unit can be

part of multiple data replication networks. The nature of membership can be

defined as: read/write or read only.

The resulting scenario’s C2 distributed environment is later used in the scenario

initialisation phase, where the whole C2 environment is set up automatically by

IC2IS2.

Figure 13: Data replication editor

4.3.4 Event Editor

Event editor is used to create advanced scenario elements using trigger-action

constructs.

Current version of IC2IS2 supports time triggering and spatial triggering while the

actions naturally affect only C2 entities:

- Activating C2 entity.

- Updating C2 data (hostility, category, symbol, operational status, holdings,

etc).

- Freeze/unfreeze C2 data.


Figure 14: Event editor

4.3.5 Blue vs Blue War-gaming Module

Blue vs Blue War-gaming module is a special module enabling the two-side war

gaming (see chapter 0).

4.4 IC2IS2 Execution

The execution stage of IC2IS2 is the most complex part of the IC2IS2

training/experimenting process. One of the strongest IC2IS2 features is that the

process itself is highly automatized and requires just a minimum user interaction.

JCAX application is used only as run/stop scenario tool and read-only user interface

to the training.

Two interactions are required by the user to run the IC2IS2 scenario:

- User has to couple user roles with the available classroom configuration. The

coupling are later stored in the scenario and can be later re-used and edited.

- If C2IS environment is not deployed already, the user has to deploy it. The

deployment of C2IS environment is again highly automatized, since all of the

configuration elements are prepared automatically by IC2IS2. The

deployment of C2IS environment is therefore just a few clicks away.

The rest of the scenario initialisation is automatic:

- IC2IS2 runtime server configures virtual sensor systems throughout the

whole training/experimenting environment.

- Initial data definitions (item-types) are distributed into C2IS environment.

- The initial data fills are distributed to all C2IS nodes according to the scenario

regulations (ORBAT, unit data, and tactical graphics).


Figure 15: IC2IS2 execution

During the scenario execution IC2IS2 server:

- Reads the data in DIS PDUs, maps it according to mapping rules, aggregates it

according to scenario parameters, delays it according to C2 reporting

parameters and finally distributes it to the C2IS nodes.

- Runs C2 SIM engine in order to:

Simulate native IC2IS2 data (intelligence data, erroneous data,

flanking units, superior units, etc).

Drive the execution of trigger-action constructs.

4.4.1 Virtual Sensor System

Virtual sensor system (VSS) is a client part of the IC2IS2 suite. Typically it is installed

on all C2IS nodes that need a simulated stream of sensor data. VSS is configured by

the IC2IS2 runtime server during the initialisation stage. The configuration contains

two necessary sets of data:

- The C2 unit ID is an identification describing which C2 unit (also C2IS node) is

simulated by a particular instance of VSS.

- The set of simulated sensors (GPS, Laser Range Finder, Laser Warning

System, etc).

After the initialisation every instance of VSS works independently by itself, for its C2IS

node. Virtual sensor system:

- Reads DIS PDUs.


- Filters DIS PDUs according to VSS configuration – it disregards all of the data

irrelevant for its C2IS node.

- Simulates the sensor data stream.

4.5 Simulated Voice Networks

Simulated Voice Networks are somehow separate part of the IC2IS2 suite. It is used

to train the users of military communication devices: Combat Net Radios and

Intercom devices. Users familiarise themselves with the communication equipment,

its employment, the nature of military voice communication and communication

related SOPs in classroom environment, without requiring any contact with the

actual equipment, just using standard PC-based computers.

IC2IS2 Voice Communication Simulation can be used as a standalone training system

or it can be used in the combination with other parts of IC2IS2 system where voice

communications become a constituent part of complex military training simulations.

Figure 16: IC2IS2 voice simulation

Voice networks are designed in the IC2IS2 planning phase, using the Voice Admin

Module - performing similar functions for Voice networks as Data distribution editor

for data distribution networks.


-

Figure 17: CNR voice client

The IC2IS2 initialisation stage is used to:

- Configure IC2IS voice server networks.

- Configure voice clients - touch screen based graphical user interface (GUI)

enabling users to use simulated radio stations and intercom switch. Standard

voice client interface upgrade is a fixed-price GUI adaptation to reach high

level of resemblance (feel-and-look) with actual communication devices.


5 TRAINING & EXPERIMENTING

5.1 IC2IS2 roles

IC2IS2 supports several different user roles. Each of them interacts with the different

components of the system (IC2IS2, LVC SIM and C2IS) as it is presented in the table:

The training/experimenting configuration is a subject of a planner’s imagination.

Basic training set-ups are described in chapters 5.2 and 0.

5.2 Basic training/experimenting

Headquarter training/experimenting is often performed as computer aided exercise,

where the combat situation is provided by constructive simulation system (JCATS,

JTLS, etc). Simulation data received by IC2IS2 is first blurred and later transferred to

C2IS environment.

Combat team training/experimenting is usually performed with the employment of

virtual simulation systems. The trainees are using desktop VR solutions or specially

designed training modules (see Figure 18: Combat team training) to train, combat

procedure, inter-team communications and interactions with C2IS equipment.


Figure 18: Combat team training

Multi-level unit training/experimenting is a combination of headquarter and combat

team training where multiple C2 nodes simultaneously train (or experiment) several

levels of command chain.

5.3 Blue Vs Blue War-gaming

Blue versus Blue War-gaming is a special IC2IS2 capability delivered by BBW module

(see Figure 2: IC2IS2 structure). The module gives the opportunity to simultaneously

train or experiment with two headquarters fighting each other (see Figure 19: Blue

versus blue war-gaming).

The simulated data is fed to two separate instances of C2 distributed environment

where:

- Each instance uses its own C2IS infrastructure (C2 networks and data

distribution rules).

- Friendly and Enemy ORBAT in first instance are mirrored in the second

instance.

- Data ownership has to be separately defined for each instance.

- C2 reporting parameters, erroneous data, trigger-actions constructs and

other inconsistencies are separately designed for each C2IS instance.

The BBW shows the potential to become a comprehensive experimenting tool,

especially in the field of experimenting with C2 procedures, with C2IS network

configuration and data inconsistencies.


Figure 19: Blue versus blue war-gaming

6 BENEFITS

Benefits brought by the IC2IS2 can be summarised in few points:

IC2IS2 fulfils main ground truth requirements. The information is distributed

through C2IS network and is subject to “fog-of-war corruption”.

Automated scenario deployment significantly reduces the time and effort,

required to prepare the training environment and start the execution of the

exercise/experiment.

IC2IS2 eliminates the need for SIM-2C2 operators (common approach when

combining constructive simulations with C2IS).

IC2IS2 serves as a standardised generic hub between LVC and C2IS, offering the

possibility to connect with any “standardises” LVC or C2IS system.

COST

EFFECTIVE

REALISTIC


7 TECHNICAL SPECIFICATIONS

The IC2IS2 components run on:

- Microsoft Windows 7 (32 or 64-bit editions),

- Microsoft Windows Server 2008 R2.

IC2IS2 environment requirements:

- Microsoft SQL 2008 R2 database server,

- Microsoft .NET 4.0

- ArcGIS Desktop 10 with SP3 or higher,

- ArcGIS Military Overlay Editor 10 with SP3 or higher,

- ArcGIS Military Analyst 10 with SP3 or higher

- Asterisk 1.8.4.x or higher with DAHDI extension,

- Conaito VOIP Client,

- Virtual Audio Cable 4.10.

white paperdefencesystems.info/wp-content/uploads/2012/10/ic2is2_whitepaper… · mirka vadnova 14...

Documents