a framework for vulnerability/lethality modeling and ... · a framework for vulnerability/lethality...

A Framework forA Framework forVulnerability/LethalityVulnerability/Lethality

Modeling and SimulationModeling and SimulationNational Industrial Association 47National Industrial Association 47thth Annual Fuze Conference Annual Fuze Conference

April 10, 2003April 10, 2003

An Employee-Owned Company

Mr. Eric ScarboroughMr. Eric Scarborough(850) 678-5222(850) 678-5222

scarboroscarboro@@araara.com.com

Mr. Mr. IanTalbotIanTalbot(850) 882-4665(850) 882-4665

[email protected]@eglin.af.mil

Fuze Conference – Apr 03

2

Presentation OutlinePresentation Outline

u Introduction

uThe Framework Conceptl Base Fuze Class

uThe PILR Architecture

uEndgame Framework Benefits


3

Current M&S DeficienciesCurrent M&S Deficiencies• High/redundant

maintenance• Expert-friendly• Platform specific• Lack V&VA• Inconsistent units• Geometry-specific

• Monolithic software - notconfigurable

• Data driven• No synergy• Empirically-based• Lack visualization• Cannot link to other models

“Technical frameworks must be developed to ensure appropriate interoperabilityacross different simulations; reuse of simulation components; insertion of newtechnologies; and flexibility to respond to changing requirements.”

“Technical frameworks must be developed to ensure appropriate interoperabilityacross different simulations; reuse of simulation components; insertion of newtechnologies; and flexibility to respond to changing requirements.” DoD 5000.59-P


4

What is a Framework ?What is a Framework ?

A collection of classesA collection of classesthat abstract thethat abstract the

common functionalitycommon functionalityneeded by similarneeded by similar

applicationsapplications

Provides general solutionProvides general solutionmechanisms for a set ofmechanisms for a set of

similar problems.similar problems.

Desirable properties:Desirable properties:- Consistent- Consistent- Extensible- Extensible

- Flexible- Flexible

Framework CoreFramework Library

CUSTOM APPLICATION

Application Custom Extensions

UnusedLibraryClasses

FR

AM

EW

OR

K


5

Endgame FrameworkEndgame Framework

CUSTOM APPLICATION

Application Extensions

Common Library

- Model Objects (Fuzes)- Property Sets- Behaviors- State Change Objects

En

dg

ame

Fra

mew

ork

En

dg

ame

Fra

mew

ork

Framework Core

- Executive Controller- Geometric Model Information Server- Common User Interface- PILR Module Interface

Behavior1

Behavior2

Behavior3

Behavior4

CustomObjects


6

Base Base Fuze Fuze ClassClass

Base Fuze Class

SafeArmUpdate BPCA Contact Switch Impact Count Void Count Proximity HOBInitiate

Warhead ClassDetonate Blast FragmentationDispense

Sensor Class

AccelerometerRF DataIR Data

Weapon System Class


7

Endgame Framework VisionEndgame Framework Vision

Base Fuze

Endgame Framework

PILR

GEOMIS

GUI

Executive Controller

ICE

T LaserEffects

SpecialtyMATERIALREMOVAL

RUPTURE

BEAM PROP

FLUENCE

VENTING

TARGETRESPONSE

Common Tool Set Supporting IndependentMethodology Through Established APIs - Incorporate “Best of breed” legacy effects models - Technology to enable new effects methodology - Combine ground fixed, mobile, airborne, DE domains

Common Tool Set Supporting IndependentMethodology Through Established APIs - Incorporate “Best of breed” legacy effects models - Technology to enable new effects methodology - Combine ground fixed, mobile, airborne, DE domains

GroundFixed

Specialty

PENCURV

BLASTX

SAMPLL

COLLAPSE

CRATER

Fuze

AirborneSpecialty

Body-on-body

BLAST

FRAGS

DB FIRE

H RAM Fuze

GroundMobile

Specialty

LEAKAGE EXTERNALBLAST

FATEPEN

SPALL/BAD

REACTIVEMATERIAL

Fuze


8


9

PILR Behavior MethodsPILR Behavior MethodsuPropagation

(damage mechanism)lPenetrator, fragment, blast wave§ Ray traced or time stepped

lDetermine impact conditions§ Impact angles (in/out), surface normal, etc.

uInteraction/LoadlBased on component type or material typelDetermine and apply load to component§ KE load, pressure, thermal transfer, etc.§ may include damage mechanism

Propagation Collision

Interaction/Load

Load

PhysicalResponse

FunctionalResponse


10

PILR Behavior Methods PILR Behavior Methods (cont.)(cont.)

uPhysical Responsel Determine component physical

response to applied load§ Breach hole, spall generation, fracture,

igniting, etc.§ May include damage mechanism

(Fragment breakup, warhead failure, etc.)

uFunctional Responsel Based on damage applied§ Simple Pk§ Initiate method for leakage

§ Initiate method for component failure or degraded performance

Propagation Collision

Interaction/Load

Load

PhysicalResponse

PhysicalChange

FunctionalResponse

FunctionalChange


11

Interaction/Load

PILR ArchitecturePILR Architecture

uBehavior Modulel Template for phenomenology developmentl Registration of PILR methodsl Provides event generation

uStandardize low-level interfacesl Interface between interaction and response

methodologies§ Allows higher fidelity physics-based

representationsl Loose coupling between behavior

methodology and component property sets

uExtensible designl New methodologies require new state change

information§ New load types§ New physical change types

(damage, temperature, pressure,…)§ New functional change types

PhysicalResponse

Propagation

FunctionalResponse

Phenomenology Methods

Broken Down


12

Behavior Module InterfaceBehavior Module Interface

u Kernel interactionsu Interrogate Geometryl Ray trace, geometric primitive info

u Get/Set Spatial Infol Location/orientation/kinematics

u Submit Eventsl Automated within behavior modulel Understanding of PILR tables

u Apply State Changesu Get Model Propertiesl Materials, dimensions, others

Behavior

GEOMIScomponentproperties

Event

Kernelregister, initialize,reset, configure

State Change


13

DetonationDetonation(System Behavior)(System Behavior)

PILR ExamplePILR Example


14


PropagationPropagation(Blast Wave, Fragments)(Blast Wave, Fragments)



15



InteractionInteraction(DM vs. (DM vs. compnentcompnent))



16



InteractionInteraction(DM vs. component)(DM vs. component)

Physical ResponsePhysical Response(component damage)(component damage)



17



InteractionInteraction(DM vs. component)(DM vs. component)

Physical ResponsePhysical Response(component damage)(component damage)

Functional ResponseFunctional Response(component P(component PKK

start leakage, etc.)start leakage, etc.)



18

Endgame Framework FeaturesEndgame Framework Features

u Software Architecturel Object Orientedl Improved target interrogationl Time-stamped events &

component state historyl Improved stochastic

capabilitiesl Dynamic object creation

l Modern software design§ C++/OpenGL based

§ GUI: Qt based

§ Cross platform code &libraries

u Methodology Benefitsl Based on physics (PILR)l Collision detection

§ Wires/hydraulics

l Synergistic effects§ Multiple weapons

l Probability distribution w/confidence bounds

l Secondary spall

l Lower support costs§ Extensible standards§ Enhanced visualization§ Portable

– Windows & Linux


19

SummarySummary

uFramework ready for adaptation of existingV/L legacy applicationsl Immediate benefits gainedl Existing conventional legacy M&S applications

currently undergoing transformation

uDeveloper’s Release allows third partyparticipation

a framework for vulnerability/lethality modeling and ... · a framework for vulnerability/lethality...

Documents