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

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

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

>> Fair Fight Definitions „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]

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

>> Fair Fight Verification & Validation 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?

Do not explicitely address fair fight >> Fair Fight Service-Based Approaches 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) Do not explicitely address fair fight

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

>> Service-Based Architecture in VINTEL Examples for Services 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

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

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

>> Fair Fight Meta Process complimenting VEVA 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

Thank you for your attention. >> Fair Fight Thank you for your attention. Questions? Comments?