Difference between revisions of "Federate Simulation Bridge"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=== European Definitions === | === European Definitions === | ||
| − | |||
| − | |||
| − | |||
==== 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: | ||
| Line 15: | Line 12: | ||
=== Other International Definitions === | === Other International Definitions === | ||
| − | <!-- Insert here definitions from international organizations, if available. Each new definition should be formatted as a heading level 4, followed by the unformatted text of the definition. An example follows below: | + | <!-- Insert here definitions from international organizations, if available. Each new definition should be formatted as a heading level 4, followed by the unformatted text of the definition. An example follows below:==== United Nations’ Definition ==== |
| − | ==== United Nations’ Definition ==== | + | Insert the definition found in the document “2009 UNISDR Terminology on Disaster Risk Reduction” (this is an example). --> |
| − | |||
=== National Definitions === | === National Definitions === | ||
| Line 45: | Line 41: | ||
[[Category:DIESIS-Glossary]] | [[Category:DIESIS-Glossary]] | ||
[[Category:Simulation]] | [[Category:Simulation]] | ||
| + | {{#set:defined by=EU project}} | ||
Revision as of 15:35, 10 June 2015
Contents
Definitions
European Definitions
DIESIS project
The DIESIS project [1] 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.
