1. EDCSS Support to JLVC Steve Lowe, John Holdzkom
Modeling & Simulation Division
Atmospheric & Environmental Research, Inc.
Usual introduction.

2. Simulated Operational Products
EDCSS Support to JNTC
Simulated Operational Products
(C4ISR)
EDCSS
Event
Support
Training Audience
White Cell
Simulation Domain
Situational
Awareness
GoogleEarth
NWARS-ng
Targeting
Mobility
CBRNE
Acoustic Detection
IR Targeting
MISREP Reports
Base Weather
ISR Collections

3. EDCSS Process for Training Event Support
EDCSS Production Site
Consistent,
Multi-Domain
Environmental
Scenario
Data
Event Planners
Effects
Project
Conditions,
Place/Time,
Components
Imagery
Messages
DMZ
DMZ
EDCSS
Distributor
HTTP Simulation Network
C4I Domain
RIM
Simulation
Control
White Cell
Trainees
RIM
Point out that runtime simulation is only part of the Training Event.
RIM
RIM
RIM
AWSIM
JCATS
NWARS
JSAF
JBUS
HLA–to-C4I Bridge
HLA Simulation Network
RIM = Runtime Integration Module
HLA = High-Level Architecture 3

4. EDC Distributor Client and Runtime API
Product-Based
Web Services
EDC Runtime Integration Module
SOAP
/ XML
Java App
Java App
ZIP Files
Product
Cache
Data
Cache
EDC Dist. Client
EDC Runtime
EDC RIM API
Load product files
(in requested format)
getData(Parm, Level, Time, Lat, Lon)
Simulation Application

5. Advantages of RIM usage
Automation of product download from Distributor
Downloads by component (e.g. JCATS, AWSIM, etc.)
Right products at the right time
Future …
The Distributor will have “scenario control” features added that will allow centralized management of game-time changes to the weather scenario in play. These changes will be very difficult to respond to with the current manual process.
Optional Programming Interface to Data/Effects
Applications can code to RIM API for efficient access to data (or pre-computed effects) by Time, Lat, and Lon.
JSAF JBUS capability already built to utilize RIM Data API
AWSIM Hypercube Read-API is prototype for RIM Effects API

6. EDCSS Version 1.3 EDC Production Web Site EDC Distributor
All current JLVC products fully automated
Automatic Date Rolling (historical to scenario)
System Impacts Service / Rules Management
User Roles
EDC Distributor
Locally managed Exercise Support Site
Site improvements (classification banner, tab layout)
User Security
Product download via web service by hour (V1.2 supports date only)
EDC Runtime Integration Module
Improved polling logic in Distributor Client (still a pull, no push)
Automated population of RIM Data Cache
API implementation improvements driven by JSAF / JBUS integration 6 6

7. B A C K U P S L I D E S

8. EDCSS Supported Events
TF-09 Support
Produced full suite of EDCSS products to support PACOM defined scenario
Daily weather briefing to training audience by PACOM Senior METOC Officer
Exercise Support Site available in TB30 (JTEN)
“Manual Adjudication” in JLVC simulation
NWDC JSAF played correlated ocean representation
EDCSS products made available on Navy Oceanography Portal
AC-09 Support
Produced full suite of EDCSS products to support EUCOM defined scenario
Ops Weather Squadron ingested EDCSS products
Over 10,000 weather products used to support exercise
290,000 synthetic observations
“consensus from all levels that products were realistic, consistent, and relevant to the warfighter” (USEUCOM Senior METOC Officer)

9. EDCSS Production Site JMB Data Standards SEIS Terrain Data WRF OutputAF
Atmos
EDCSS Production Site
Satellite
Imagery
Data
Hypercube
COSINE
Effects
Product
Generation
JMB Data Standards
Navy
Atmos
Imagery
Graphics
(KML)
Messages
Navy
Ocean
METAR/TAF
System
Impacts
Mineable
Databases
Ad- Hoc Sources
SEIS
Terrain Data
WRF Output

10. EDCSS Requirements Data Model
Project
Where
When
Who *
Components
JCATS
AWSIM
White Cell
JET
AWSIM *
Data
Effects
IR Hypercube
Products
Available Increments
Spatial Resolution/Projection
Generation Service
JLVC CSV
This is the EDCSS requirements model. At the lowest level Environment Representation Products are defined
that have an application specific definition of content, representation, and format, and which are bound to a
generating service for production. This mechanism allows the specification and generation of products to be
encapsulated as a simple entry in the EDCSS production database, which can then be logically associated with
components and projects. Components are a generic concept for defining users of one or more products.
A component can be a specific application or user, or a group (or class) of users that desire to receive a specific
set of products. For example, the Navy JSAF simulation uses three different GRIB data sets with specific content
and the AF AWSIM simulation utilizes CSV weather data files and Hypercubes for pre-computed effects.
At the top level is the concept of Projects. Note that there is no direct connection between Projects and Products.
The idea is that an end-user with minimal or no knowledge about the intricacies of the underlying applications in
their domain can easily define a Project by specifying a spatial domain and time range, and then selecting the
components involved in their event. The EDCSS requirements model allows this simple specification to be
transformed into a compete and detailed requirements specification at the Product level.
JCATS – Joint Conflict And Tactical Simulation
AWSIM – air warfare simulation model (US DoD)
JET – Joint Expeditionary Tasking (US DoD)
METAR – Meteorological Aviation Report
TAF - Terminal Area Forecast (aviation/meteorology)
JSAF GRIB
Text
METAR
TAF
Image
Weather Graphics
Synthetic Satellite

12. EDCSS Exercise Support Site
EDCSS Product Samples
EDCSS Exercise Support Site

13. EDCSS Product Portfolio
Satellite/Radar (Google Earth)
Satellite
Probability of Detection
Radar

14. EDCSS Product Portfolio (Cont)
Soil moisture content
Systems impact (stop light chart)
Ocean wave dir/height
Weather synopsis

15. The Payoff – Runtime Access in Milliseconds !!
Hypercube Concept
Example: IR Sensor modeling using Target Acquisition Weapons Software (TAWS)
Sensor
Properties
Atmospheric
Transmission
4 Target Types
4 Sensors
4 Target Orientations
8 Sensor-Target Azimuths
5 Sensor-Target Ranges
3 Sensor Altitudes
3 Background Types
24 Times per day
400 Lat/Lon locations
=> 220 million
TAWS computations
Target
Thermal
Properties
Background
Thermal
Properties
The Payoff – Runtime Access in Milliseconds !!

16. Hypercube Concept
Provide pre-computed performance data for simulations that can’t afford the computational burden at run-time
Use a physics solution to a slightly different problem
Compute a desired metric for an n-dimensional parameterized space
Pd = f (Sensor, Target, Background, Weather, Tactics)
Provide a simple API to allow applications to rapidly sample that space for the closest match to the run-time situation
Provides for multi-dimensional interpolation, as appropriate