A Framework for Vulnerability/Lethality Modeling and Simulation National Industrial Association 47 th Annual Fuze Conference April 10, 2003

Transcription

1 A Framework for Vulnerability/Lethality Modeling and Simulation National Industrial Association 47 th Annual Fuze Conference April 10, 2003 Mr. Eric Scarborough (850) ara.com Mr. IanTalbot (850) An Employee-Owned Company

2 Presentation Outline Introduction The Framework Concept Base Fuze Class The PILR Architecture Endgame Framework Benefits 2

3 Current M&S Deficiencies Monolithic software - not configurable Data driven No synergy Empirically-based Lack visualization Cannot link to other models High/redundant maintenance Expert-friendly Platform specific Lack V&VA Inconsistent units Geometry-specific Technical Technical frameworks frameworks must must be be developed developed to to ensure ensure appropriate appropriate interoperability interoperability across across different different simulations; simulations; reuse reuse of of simulation simulation components; components; insertion insertion of of new new technologies; technologies; and and flexibility flexibility to to respond respond to to changing changing requirements. requirements. DoD P 3

4 What is a Framework? FRAMEWORK Framework Library Unused Library Classes CUSTOM APPLICATION Framework Core Application Custom Extensions A collection of classes that abstract the common functionality needed by similar applications Provides general solution mechanisms for a set of similar problems. Desirable properties: - Consistent - Extensible - Flexible 4

5 Endgame Framework CUSTOM APPLICATION Endgame Framework Common Library - Model Objects (Fuzes) - Property Sets - Behaviors - State Change Objects Framework Core - Executive Controller - Geometric Model Information Server - Common User Interface - PILR Module Interface Custom Objects Behavior 1 Behavior 2 Behavior 3 Behavior 4 Application Extensions 5

6 Base Fuze Class Weapon System Class Sensor Class Accelerometer RF Data IR Data Base Fuze Class Safe Arm Update BPCA Contact Switch Impact Count Void Count Proximity HOB Initiate Warhead Class Detonate Blast Fragmentation Dispense 6

7 Endgame Framework Vision ICET Endgame Framework PILR Base Fuze GUI COLLAPSE SAMPLL PENCURV Ground Fixed Specialty BLASTX Fuze CRATER FRAGS H RAM Airborne Specialty Body-onbody BLAST DB FIRE LEAKAGE FATEPEN REACTIVE MATERIAL SPALL/BAD Fuze EXTERNAL BLAST Fuze Ground Mobile Specialty VENTING MATERIAL REMOVAL TARGET RESPONSE Laser Effects Specialty FLUENCE RUPTURE BEAM PROP GEOMIS Executive Controller Common Common Tool Tool Set Set Supporting Supporting Independent Independent Methodology Methodology Through Through Established Established APIs APIs -- Incorporate Incorporate Best Best of of breed breed legacy legacy effects effects models models -- Technology Technology to to enable enable new new effects effects methodology methodology -- Combine Combine ground ground fixed, fixed, mobile, mobile, airborne, airborne, DE DE domains domains 7

8 8

9 PILR Behavior Methods Propagation (damage mechanism) Penetrator, fragment, blast wave Ray traced or time stepped Determine impact conditions Propagation Interaction/ Load Impact angles (in/out), surface normal, etc. Interaction/Load Based on component type or material type Determine and apply load to component KE load, pressure, thermal transfer, etc. may include damage mechanism Collision Physical Response Load Functional Response 9

10 PILR Behavior Methods (cont.) Physical Response Determine component physical response to applied load Breach hole, spall generation, fracture, igniting, etc. May include damage mechanism (Fragment breakup, warhead failure, etc.) Functional Response Based on damage applied Simple Pk Initiate method for leakage Propagation Interaction/ Load Collision Physical Response Load Functional Response Initiate method for component failure or degraded performance Physical Change Functional Change 10

11 PILR Architecture Behavior Module Template for phenomenology development Registration of PILR methods Provides event generation Standardize low-level interfaces Interface between interaction and response methodologies Allows higher fidelity physics-based representations Loose coupling between behavior methodology and component property sets Extensible design New methodologies require new state change information New load types New physical change types (damage, temperature, pressure, ) New functional change types Propagation Interaction/ Load Phenomenology Methods Broken Down Physical Response Functional Response 11

12 Behavior Module Interface Kernel interactions Interrogate Geometry Ray trace, geometric primitive info Get/Set Spatial Info Location/orientation/kinematics Submit Events Automated within behavior module Understanding of PILR tables Apply State Changes Get Model Properties Materials, dimensions, others Kernel register, initialize, reset, configure GEOMIS component properties Event Behavior State Change 12

13 PILR Example Detonation (System Behavior) 13

14 PILR Example Detonation (System Behavior) Propagation (Blast Wave, Fragments) 14

15 PILR Example Detonation (System Behavior) Propagation (Blast Wave, Fragments) Interaction (DM vs. compnent) 15

16 PILR Example Detonation (System Behavior) Propagation (Blast Wave, Fragments) Interaction (DM vs. component) Physical Response (component damage) 16

17 PILR Example Detonation (System Behavior) Propagation (Blast Wave, Fragments) Interaction (DM vs. component) Physical Response (component damage) Functional Response (component P K start leakage, etc.) 17

18 Endgame Framework Features Software Architecture Object Oriented Improved target interrogation Time-stamped events & component state history Improved stochastic capabilities Dynamic object creation Modern software design C++/OpenGL based GUI: Qt based Cross platform code & libraries Methodology Benefits Based on physics (PILR) Collision detection Wires/hydraulics Synergistic effects Multiple weapons Probability distribution w/ confidence bounds Secondary spall Lower support costs Extensible standards Enhanced visualization Portable Windows & Linux 18

19 Summary Framework ready for adaptation of existing V/L legacy applications Immediate benefits gained Existing conventional legacy M&S applications currently undergoing transformation Developer s Release allows third party participation 19