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>> Context and Overview Fair Fight Live, Virtual, ConstructiveVerification & ValidiationFair FightInteroperabilityService Based ApproachesDevelopment Processes
3>> The Levels of Conceptual Interoperability Model (LCIM) [Tolk 2003]
4>> 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]
5>> Fair Fight Examples for Violations Environment RepresentationObject RepresentationCapabilities of EntitiesComputation of Visibility / Line of SightWeapon Effect ComputationTime Management IssuesBandwith of Communication[Picture: IABG mbh]
6>> Fair Fight Verification & Validation Fair Fight is a V&V Issue!Fair fight violation violation of pragmatic interoperabilityReasons for violations can be found on all LCIM levelsFair fightRequirements must be defined at pragmatic levelDetection is subject to pragmatic levelValidity requirements für other (lower) levels can be derivedOpen questions:Unambiguous and quantifiable description of fair fight requirements?Systematic and reliable tests for fair fight?
7Do not explicitely address fair fight >> Fair Fight Service-Based ApproachesUsually: Service-Based architecture striving forReusabilityComposability using existing components offered as servicesOr: Simulation services as support functionsMost prominent example: HLA and its services (HLA Federate Interface Specification)Do not explicitely address fair fight
8>> Service Based Architecture VINTEL [Neugebauer et al. 2009]
9>> Service-Based Architecture in VINTEL Examples for Services Weapon Effect Service (WES)Service-Based computation of weapon effectsUnified algorithms and levels of detail within one simulationCommunication Effect Service (CES)Calculation of probabilities of radio communication between entitiesEqual algorithms, constraints, and side effectsSynthetic Environment Service (SES)Initial synthetic environmental dataUnified dynamic updates of this data
10>> Fair Fight Need for Conceptual Interoperability [Tolk 2003]
11>> Fair Fight Treatment in VEVA VEVA phasesDocumentation to be prepared according to VEVAProducts to be prepared and additional documentationObjectives and Requirements Organization and ExecutionIT Security ConceptGoal DefinitionScenarioConceptual PlanningConceptual ModelData Recording and Management PlanSimulation EnvironmentData Recording and Management PlanFederation Object Model (FOM)Federation AgreementsSystem-Dependent PlanningInitService ConfigurationStructural PlanAdapted ComponentsFederationExecution PreparationConfiguration and Execution PlanData Recording and Management PlanConfiguration and Execution PlanResultsExecutionSimulation DataProcessed and Verified DataAnalysisResultsResultsReusable ComponentsFollow-UpFinal Report(s)
12>> Fair Fight Meta Process complimenting VEVA Procedure Model VEVA tries to check for fair fight violationsPhase 3 (system dependent planning)Phase 4 ( execution preparation)Supported byList of known fair fight problems structured according to LCIMList Updates viaPhase 5 (simulation execution): simulation monitoring + identification of fair fight violationsPhase 7 (follow up): documenting and reporting fair fight violations
13Thank you for your attention. >> Fair FightThank you for your attention.Questions?Comments?