Integrated Environment for Modeling and Simulation

1
Integrated Environment for Modeling and Simulation
Joseph Collins, Terry Foreman, Dan Speicher

• Modeling and Simulation of
• Minehunting Sonars in a
• Littoral Environment

PI Dr. Joseph B. Collins, NRL 5583,
collins_at_ait.nrl.navy.mil
2
Objectives

• Establish methodology for determining required
  resolution for environmental representations.
• Integrate environment with simulation system
  incorporate simulation effects models to use the
  environmental information correctly.
• Deliver and demonstrate the operation of the
  resulting capabilities in a Navy fleet battle
  simulation experiment.

3
Environmental Effects Server

• Natural Environment has Systemic effects
• Not one system, but whole simulation
• Spotty representation to date
• Environmental Effects Server for
• Consistency everyone sees same context
• Outsource intensive computation
• Outsource environmental data management

4
Synthetic Natural Environments
5
Support / Tasks

• ONR, CHSSI, DMSO
• Build Acoustic Transmission Loss Server
• Support SQS-53/56 Sonar
• Model ocean environment
• Demonstrate FBE - Juliet
• Study performance
• Begin implementation of Reverberation

6
Environment

• Shallow water
• ECOM (HydroQual)
• Deep water and boundary forcing
• NPACNFS - D.S. Ko, NRL-Stennis
• Surface forcing
• COAMPS - FNMOC (27km)
• NPMOC-SD (couldnt set up 9km)
• MODAS as backup

7
Maritime Environment for FBEs
Assemble Archived Data Sources
Initialize Model
Assimilate near Real time data
Atmosphere
Ocean
COAMPS Data
Wave Height
Buoy Data
MODAS and POM For water column
Bathymetry
Weeks before FBE
Months before FBE
Sources NAVO, NRL/SSC, MEL
Sources NAVO, NRL/SSC, any
8
Environmental Resolution Req.

• Recommended bathymetry resolution
• 500m horizontal for 30m-300mdepth
• 100m horizontal for depth for 10m-30m
• Bathy resolution directly affects RMS error
• Vertical - DB/B (or DV/(DAB)) 3-5
• Vertical ocean resolution
• variable spacing sigma profile
• 20 layer to span depths from 10m-1000m

9
Dataflow

• JSAF models Northrup Grumman
• (Logicon)
• NRL ATLoS
• OASES Server Northrup Grumman
• (TASC)
• HydroQual Ocean Environment

10
Acoustic Propagation Model

• Testing typical requests for multi-km ranges
• FeyRay-Fast Gaussian Ray Beam code
• HFBL bottom
• Bathymetry from Marine Trackline DB and ETOPO5

11
ATLoS(Acoustic Transmission Loss Server)

• Receives, queues requests computes transmission
  loss with FeyRay sends response
• Use some JSAF libraries, CTDB, Linux OS
• High Level Architecture (HLA) based Server A
  Separate Federate
• Included in FBE cvs-tree

12
ATLoS Request / Response

• Request gives
• Source location (lat, lon, depth)
• Receiver location (lat, lon, depth)
• Array of frequencies
• Identifiers for request and pair of entities
• Response gives
• Array of T-losses (corresponds to frequencies)
• Identifiers for request and pair of entities

13
Simulation Integration

• Collaboration with
• ONR, DMSO, CHSSI
• NWDC, RI, and BMH
• Anteon, VA
• Lockheed Martin, MA
• HydroQual, Inc
• Lockheed Martin, WA
• Northrup Grumman, RI (Logicon)
• Northrup Grumman, NH (TASC)
• NAVO, NRL-Stennis
• FNMOC

14
FBE-J

• Experiment Prep Spirals 0, 1, 2, 3
• Execution at FBE-J
• Testing for Transmission Loss
• Peak request rate - 50-70 per second
• Issues - bad requests, speed of performance
• Bathymetry and SOF-SAF
• Ocean needed for Amphib, SOFs

15
Proposed FY03 Activity

• Complete implementation of reverberation
• Support active mode for SQS-53/56 Kingfisher
• Improve ATLoS performance (speed, reliability)
• Support additional Sonar models with ATLoS and
  PCSWAT Servers
• Currently SQS-53/56, AQS-14, 20, SQQ-32
• Candidates RMS, LMRS, REMUS, BPAUV, CETUS
• LFA, sonobuoy
• Demonstrate at FBE-K
• Analysis of environmental fidelity requirements

16
Proposed FY03 Activity, contd.

• Integrate with TEDS
• Allows support of DII/COE TDAs
• Expand range of METOC support with TEDS based
  METOC station
• Begin environmental requirements determination
  beyond counter-mine

17
Interoperability Issues

• Reliable Transport / Best Effort
• Need reliable initialization updates?
• Are data discontinuities tolerable or do they
  defeat resolution?
• User Pull model vs. Subscribed Push?
• High bandwidth to server
• Caused by simple automated clients
• Limits expansion of server function

18
Interoperability Issues, Contd

• Data representation
• JSAF Coordinates
• Inherently 3-D, non-uniform, curvilinear grid
• Data interchange GRIB, netCDF, ArcInfo
• Need Environment Requirements Capture
• Extend broader Environment / Effects support
• Support domain of Composability
• Uncertainty