Presentation is loading. Please wait.

Presentation is loading. Please wait.

>> How to Ensure Fair Fight in LVC Simulation: Architectural and Procedural Approaches Robert Siegfried, Johannes Lüthi, Günter Herrmann, Matthias Hahn.

Similar presentations


Presentation on theme: ">> How to Ensure Fair Fight in LVC Simulation: Architectural and Procedural Approaches Robert Siegfried, Johannes Lüthi, Günter Herrmann, Matthias Hahn."— Presentation transcript:

1 >> How to Ensure Fair Fight in LVC Simulation: Architectural and Procedural Approaches Robert Siegfried, Johannes Lüthi, Günter Herrmann, Matthias Hahn

2 2 >> Context and Overview Fair Fight Interoperability Verification & Validiation Development Processes Service Based Approaches Live, Virtual, Constructive

3 3 >> The Levels of Conceptual Interoperability Model (LCIM) [Tolk 2003]

4 Two or more simulations may be considered to be in a fair fight when differences in the simulations performance characteristics have significantly less effect on the outcome of the conflict than actions taken by the simulation participants. [DIS Glossary, 1995] Fair-Fight exists among two simulation systems if the differences in representing and mapping reality in the simulation models does not lead to a systematic model immanent advantage and consequently unrealistic simulation results for one of the simulation systems. [Ufer et al., 2009] Fair Fight is obtained when the systems are interoperable and the system performance capabilities of the simulators are complimentary for a given task throughout the simulation environment. Fair Fight is also task dependent and includes items such as similarity in the equality made in use of the synthetic environment features, automated force behaviors, etc. Equality of use is determined within pre-determined tolerances. [Goldiez, Sottilare, 2008] 4 >> Fair Fight Definitions

5 Environment Representation Object Representation Capabilities of Entities Computation of Visibility / Line of Sight Weapon Effect Computation Time Management Issues Bandwith of Communication 5 >> Fair Fight Examples for Violations [Picture: IABG mbh]

6 Fair Fight is a V&V Issue! Fair fight violation violation of pragmatic interoperability Reasons for violations can be found on all LCIM levels Fair fight –Requirements must be defined at pragmatic level –Detection is subject to pragmatic level Validity requirements für other (lower) levels can be derived Open questions: –Unambiguous and quantifiable description of fair fight requirements? –Systematic and reliable tests for fair fight? 6 >> Fair Fight Verification & Validation

7 Usually: Service-Based architecture striving for –Reusability –Composability using existing components offered as services Or: Simulation services as support functions –Most prominent example: HLA and its services (HLA Federate Interface Specification) 7 >> Fair Fight Service-Based Approaches Do not explicitely address fair fight

8 8 >> Service Based Architecture VINTEL [Neugebauer et al. 2009]

9 Weapon Effect Service (WES) –Service-Based computation of weapon effects –Unified algorithms and levels of detail within one simulation Communication Effect Service (CES) –Calculation of probabilities of radio communication between entities –Equal algorithms, constraints, and side effects Synthetic Environment Service (SES) –Initial synthetic environmental data –Unified dynamic updates of this data 9 >> Service-Based Architecture in VINTEL Examples for Services

10 10 >> Fair Fight Need for Conceptual Interoperability [Tolk 2003]

11 Simulation Environment Data Recording and Management Plan Conceptual Model Data Recording and Management Plan Configuration and Execution Plan Data Recording and Management Plan Configuration and Execution Plan Results Objectives and Requirements Organization and Execution Goal Definition Conceptual Planning System-Dependent Planning Execution Preparation Execution Analysis Follow-Up Scenario Federation Object Model (FOM) Federation Agreements InitService Configuration Structural Plan Adapted Components Federation Simulation Data Processed and Verified Data Reusable Components VEVA phasesDocumentation to be prepared according to VEVA Products to be prepared and additional documentation IT Security Concept Final Report(s) >> Fair Fight Treatment in VEVA

12 Procedure Model VEVA tries to check for fair fight violations –Phase 3 (system dependent planning) –Phase 4 ( execution preparation) Supported by –List of known fair fight problems structured according to LCIM List Updates via –Phase 5 (simulation execution): simulation monitoring + identification of fair fight violations –Phase 7 (follow up): documenting and reporting fair fight violations 12 >> Fair Fight Meta Process complimenting VEVA

13 13 >> Fair Fight


Download ppt ">> How to Ensure Fair Fight in LVC Simulation: Architectural and Procedural Approaches Robert Siegfried, Johannes Lüthi, Günter Herrmann, Matthias Hahn."

Similar presentations


Ads by Google