Difference between revisions of "Federate Simulation Bridge"
Jump to navigation
Jump to search
(Created page with "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 ...") |
|||
| Line 1: | Line 1: | ||
| − | 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: | + | <!--Insert here introductory text regarding the term.--> |
| + | |||
| + | ==Definitions== | ||
| + | <!-- This section presents all available definitions of the above term.--> | ||
| + | |||
| + | === European Definitions === | ||
| + | <!-- Insert here definitions from European institutions or projects, 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: | ||
| + | ==== 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: | ||
* 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 introduces faults and attacks into running [[simulation]]s | * 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 introduces 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 === | ||
| + | <!-- 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 ==== | ||
| + | <!-- Insert the definition found in the document “2009 UNISDR Terminology on Disaster Risk Reduction” (this is an example). --> | ||
| + | |||
| + | === National Definitions === | ||
| + | <!-- Insert official national definitions, if available. Each definition should be formatted as a heading level 4, followed by the text of the definition. An example follows below: | ||
| + | ==== Country Name==== | ||
| + | Insert the definition found on the DHS Lexicon (this is an example). --> | ||
| + | |||
| + | ===Standard Definition=== | ||
| + | <!--Insert the text of the definition. Each definition should be formatted as a heading level 4, followed by the text of the definition. --> | ||
| + | |||
| + | == Discussion Topic == | ||
| + | <!-- Discuss topics related to the term, such as closely-related terms, differences among definitions, how to use the definitions provided, open issues, etc. --> | ||
| + | |||
| + | ==See also== | ||
| + | <!-- Add links to related terms --> | ||
| + | |||
| + | |||
| + | ==Notes== | ||
| + | <!-- The references will be automatically be listed below. In order to reference --> | ||
| + | <references /> | ||
| + | |||
| + | ==References== | ||
| + | <!-- Additional references can also be added below.--> | ||
| + | |||
| − | [[Category:DIESIS- | + | <!-- Add category, i.e. [[Category:Main]] --> |
| + | [[Category:DIESIS-Glossary]] | ||
Revision as of 11:50, 10 June 2014
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 introduces faults and attacks into running simulations
- a versatile timing mechanism to manage the synchronism inside the federated simulation.
