Difference between revisions of "Federate Simulation Bridge"
Jump to navigation
Jump to search
| (5 intermediate revisions by 4 users not shown) | |||
| Line 4: | Line 4: | ||
<!-- This section presents all available definitions of the above term.--> | <!-- This section presents all available definitions of the above term.--> | ||
| − | === European Definitions === | + | === European Project Definitions === |
| − | + | ==== CIPRNet project ==== | |
| − | ==== | + | {{quote-ciprnet|Federate simulation bridge is the coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. }}<br/> |
| − | - | + | |
==== DIESIS project ==== | ==== DIESIS project ==== | ||
{{quote-diesis|The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or [[cyber dependency | cyber (inter)dependencies]] between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a [[federated simulation]] between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including: | {{quote-diesis|The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or [[cyber dependency | cyber (inter)dependencies]] between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a [[federated simulation]] between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including: | ||
* a Knowledge Base System (KBS) - shared among the [[federate]] subjects – able to gather, filter and maintain traces of any possible synergic actions driving a [[federated simulation]] | * a Knowledge Base System (KBS) - shared among the [[federate]] subjects – able to gather, filter and maintain traces of any possible synergic actions driving a [[federated simulation]] | ||
| − | * a basic [[model]] to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A [[scenario]] can also include some kind of script to | + | * a basic [[model]] to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A [[scenario]] can also include some kind of script to introduce faults and attacks into running [[simulation]]s |
* a versatile timing mechanism to manage the synchronism inside the [[federated simulation]].}} | * a versatile timing mechanism to manage the synchronism inside the [[federated simulation]].}} | ||
| − | + | <!--- | |
=== Other International Definitions === | === Other International Definitions === | ||
| − | |||
==== United Nations’ Definition ==== | ==== United Nations’ Definition ==== | ||
| − | |||
=== National Definitions === | === National Definitions === | ||
| − | |||
==== Country Name==== | ==== Country Name==== | ||
| − | + | ||
| + | ===Standard Definition=== | ||
| + | --> | ||
===Standard Definition=== | ===Standard Definition=== | ||
| Line 31: | Line 30: | ||
==See also== | ==See also== | ||
| − | + | * [[Simulation]] | |
| + | * [[Federate]] | ||
| Line 43: | Line 43: | ||
<!-- Add category, i.e. [[Category:Main]] --> | <!-- Add category, i.e. [[Category:Main]] --> | ||
| − | [[Category:DIESIS-Glossary]] | + | [[Category:CIPRNet-Glossary]][[Category:DIESIS-Glossary]][[Category:Simulation]] |
| + | {{#set:defined by=EU project}} | ||
Latest revision as of 14:04, 22 December 2016
Contents
Definitions
European Project Definitions
CIPRNet project
The CIPRNet project [1] uses the following definition:
Federate simulation bridge is the coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators.
DIESIS project
The DIESIS project [2] gives the following definition:
The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or cyber (inter)dependencies between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a federated simulation between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including:
- a Knowledge Base System (KBS) - shared among the federate subjects – able to gather, filter and maintain traces of any possible synergic actions driving a federated simulation
- a basic model to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A scenario can also include some kind of script to introduce faults and attacks into running simulations
- a versatile timing mechanism to manage the synchronism inside the federated simulation.
Standard Definition
Discussion Topic
See also
