12:56 Sep 12, 2017 |
English language (monolingual) [PRO] Military / Defense | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Helena Chavarria Spain Local time: 10:11 | ||||||
Grading comment
|
SUMMARY OF ALL EXPLANATIONS PROVIDED | ||||
---|---|---|---|---|
3 +1 | joint federation of effects-based operations |
|
Summary of reference entries provided | |||
---|---|---|---|
|
joint federation of effects-based operations Explanation: 1. Introduction a. This handbook is a pre-doctrinal follow-on to JWFC Pamphlet 7, Operational Implications of Effects-based Operations (EBO), and presents major aspects of an effects-based approach in the context of current and emerging joint doctrine. http://www.au.af.mil/au/awc/awcgate/jfcom/ebo_handbook_2006.... Please see the references I posted below. -------------------------------------------------- Note added at 6 hrs (2017-09-12 19:45:50 GMT) -------------------------------------------------- The high-level architecture (HLA) is a general purpose architecture for distributed computer simulation systems. Using HLA, computer simulations can interact (that is, to communicate data, and to synchronize actions) with other computer simulations regardless of the computing platforms. The interaction between simulations is managed by a run-time infrastructure (RTI). HLA is an interoperability standard for distributed simulation used to support analysis, engineering and training in a number of different domains in both military and civilian applications and is the standard technical architecture for all US Department of Defense simulations. Interface specification, that defines how HLA compliant simulators interact with the run-time infrastructure (RTI). The RTI provides a programming library and an application programming interface (API) compliant to the interface specification. Object model template (OMT), that specifies what information is communicated between simulations, and how it is documented. Rules, that simulations must obey in order to be compliant to the standard. Common HLA terminology Federate: an HLA compliant simulation entity. Federation: multiple simulation entities connected via the RTI using a common OMT. Object: a collection of related data sent between simulations. Attribute: data field of an object. Interaction: event sent between simulation entities. Parameter: data field of an interaction. https://en.wikipedia.org/wiki/High-level_architecture Federation: multiple simulation entities connected via the run-time infrastructure using a common object model template. -------------------------------------------------- Note added at 6 hrs (2017-09-12 19:50:40 GMT) -------------------------------------------------- In the reference I posted below, it says that the JOEF (Joint Operational Effects Federation) is a [i]simulation[/i] federation. |
| ||
Notes to answerer
| |||
Login to enter a peer comment (or grade) |
1 hr peer agreement (net): +1 |
Reference Reference information: JOEF (Joint Operational Effects Federation) is a simulation federation that supports CBRN (Chemical Biological Radiological and Nuclear) warfare on military operations. Its primary interface to users is JWARN (Joint Warning and Reporting Network), which is an automated reporting of CBRN incidents for the joint or each service. It also automates the transfer of data between CBRN detectors/sensors and C4I systems, and minimizes the effects of a hostile attack, accidents or incidents. Therefore, the fundamental role of JOEF is to provide the modeling and simulation analytical capability to determine and assess the impact of CBRN warfare on military operations. It specifically supports assessment of wartime operations and risk levels, assessment of wartime preparations for employment of CBRN defenses and resources, and advance planning and analysis to support assessment of CBRN operational alternatives in conjunction with JWARN in real-time mode. This paper describes the JOEF conceptual architecture for the structure of operational-effects models (i.e., transport and dispersion models). The architecture includes the specification of software module interfaces so that the modules become plug-and-play operational effect simulations. It also allows for direct interfaces to a web-based application and user interfaces. Finally, the architecture is compliant to DII-COE, which is the DOD C4I interface standard. https://www.mitre.org/publications/technical-papers/joef-joi... -------------------------------------------------- Note added at 1 hr (2017-09-12 14:12:47 GMT) -------------------------------------------------- Effects-based operations (EBO) is a United States military concept that emerged during the Persian Gulf War for the planning and conduct of operations combining military and non-military methods to achieve a particular effect.[1] An effects-based approach to operations was first applied in modern times in the design and execution of the Desert Storm air campaign of 1991. https://en.wikipedia.org/wiki/Effects-based_operations |
| |
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.