Difference between revisions of "Federate Simulation Bridge"

From CIPedia
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 ...")
(No difference)

Revision as of 13:12, 3 June 2014

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.