An Environmental Data Model for the OneSAF Objective System

1
An Environmental Data Model for the OneSAF
Objective System

• Dale D. Miller, Ph.D.
• Annette C. Janett
• Melissa E. Nakanishi
• Richard Schaffer
• Deborah Wilbert
• Lockheed Martin Information Systems
• Advanced Simulation Center
• September 11, 2002

2
Subject Matter Experts
odyssey (od'i-se) n., An intellectual or
spiritual quest an odyssey of discovery.

• LTC Dave Vaden (TPO OneSAF)
• John Thomas (AMSAA RDA)
• George L. Mason (ERDC WES)
• Paul Richmond (ERDC CRREL)
• David Durda (TRAC WSMR ACR)
• Roy Ramsey (NSC TEMO)
• Jeff Bittel (TPO OneSAF)
• Frank Bush (TEMO)
• Mike Humphrey (KA/KE)
• Doug Brooks (JSIMS ASNE MSEA Liaison)

3
Environmental Data Model (EDM)Purpose and Scope

• High level specification of environmental
  phenomena
• To bound all possible environmental
  representations within OOS
• Features, attributes, attribute values,
  relationships
• Parameters to drive physical models and outputs
  of such models
• Logical data model
• Silent on the specific run-time data structures
• Supports interoperability with other systems
• JSIMS Land Component, CCTT
• Includes all environmental domains
• Terrain, Atmosphere, Ocean, Space
• Includes data elements targeted for efficient SAF
  reasoning

4
Environmental Data Models (EDMs)

2002
5
Common Data Model Framework

• Consistent approach to capturing EDMs
• Allows meaningful and effective comparisons
• Neutral representation methodology
• Independent of IDEF1X or UML
• Convertible to either, depending on audience
• Realized using a relational information model
• Well-defined schema MS Access 2000-based
  portable extendable
• Leverages community standards
• SEDRIS Environmental Data Coding Specification
• Implements a suite of task-centric tools
• Data capture, review, editing, and configuration
  management
• Report(s) generation (e.g., EDM-centric,
  cross-EDM comparisons)
• Automated generation of IDEF1x diagrams using MS
  Visio
• Data export (e.g., XML)
• Coupled to other tools (e.g., WARSIM TDFS, SEE-IT)

6
Benefits of Formalizing and Standardizing EDMs

• EDMs document environmental requirements
• provide lineage to their source
• e.g., course of action analysis
• Provide definitive data requirements to
  authoritative providers
• Identify deltas for value adding from other
  sources, planning research initiatives
• Support interoperability
• in a live simulation, what aspects of the
  environment are required from the simulator to
  drive the operational systems?

7
EDM Complexity
8
Data Dictionary EDCS

• Classifications, attributes, enumerants, units of
  measure
• ISO/IEC Committee Draft (ISO/IEC 18025)
• Qualified attributes
• EDCS extensions
• Labels vs Codes

9
OOS EDM Realized as Four Microsoft Access
Databases

• Terrain (EDM-T)
• Ultra High Resolution Buildings (EDM-UHRB)
• Atmosphere, Ocean and Space (EDM-AOS)
• Capstone (union) (OOS-EDM)

EDCS Access Database incorporated via table
linkages
10
Feature Types
11
EDM-T

• Physical Models related to the terrain
• Features
• Attributes
• Relationships

12
Military Functional Uses

• Extended WARSIM Military Functional Uses to meet
  OOS requirements
• Explicitly identify all MFUs in which each
  feature participates

13
Physical Models Related to Terrain

• Mobility
• Thermal
• Seismic and acoustic
• Freeze / thaw
• Sky glow
• NBC contamination inside buildings
• Flooding
• Nuclear contamination from damaged or destroyed
  reactor
• Dust
• Underwater mine detection

• From an EDM perspective, ideally, models would be
  selected and never changed
• then the inputs and/or output data elements of
  the models would be added to the EDM
• but this would negate the overarching goal of
  composability
• Strategy
• Examine existing models and add sufficient
  attribution to drive them
• Interact with model SMEs to provide sufficient
  description of the environment to drive future
  models

14
NATO Reference Mobility Model II (NRMM II)

• Validated model for mobility of vehicles on and
  off road
• WARSIM and CCTT use mobility models driven by
  tables derived from offline runs
• OOS attributes trafficable features with the
  input parameters to NRMM II

15
EDM-T Features

• Building representations
• Points
• Area footprints
• Polygonal Shell
• Three resolutions
• Medium (EDM-T)
• High (EDM-UHRB)
• Ultra High (EDM-UHRB)

Each building instance must have all three
Must be indistinguishable from an exterior visual
or sensor view
16
Roads

• SAF vehicles traditionally have poor drivers
• Lane features added to constrain vehicle
  movement
• Attributed with control information
• Multiresolution approach
• Road centerlines for planning
• Lanes for driving

Based upon approach of Longtin et al.,
01S-SIW-060
17
EDM-T Features (cont.)

• Bridges / Overpasses as LINE features
• Shares geometry with associated road
• Spans, piers, towers as POINT features
• All tied together via relationships
• Underground structures
• Sewers systems SEWER, MANHOLE_RISER and
  MANHOLE_COVER and ENTRANCE_AND_OR_EXIT
• Subways and tunnels have related
  ENTRANCE_AND_OR_EXIT (NODE) features
• Caves originally modeled like an underground
  room
• Later, cave networks were judged important
• ENTRANCE_AND_OR_EXIT (NODE)
• CAVE (AREA)
• CAVE (3DLINE)
• CAVE_CENTRELINE (LINE)

18
New Classifications Developed to Support EDM-T
19
EDM-T Example Attribution BUILT_UP_REGION
20
EDM-T Relationships

• Aggregation, adjacency, over/under, connectedness

21
EDM-UHRB

• Requirements
• ORD not specific
• TEMO training command vs. squad level
• Use case small force clearing single building
• Solicited requirements from Combined Arms MOUT
  Task Force (CAMTF), Infantry Center, Ft. Benning
• Results rooms, floors, walls, windows, doors,
  furniture, basements, attics, shafts, ducts,
  stairs, breach holes, wall fortification, .

22
UHRB Objectification

• Added generalization features
• Inheritance of attribution
• Inheritance of relationships
• Multi-level hierarchy
• Examples
• Building has layers
• Layers have compartments
• Compartments have horizontal and vertical
  partitions
• Partitions have openings
• Layers are connected by vertical passages

23
UHRB Category Relationships (generalization
features in yellow)
24
UHRB Attributes

• Categories of attributes
• Human mobility
• General geometry
• Material composition
• Construction type
• Visual and thermal characteristics
• Information to support breaching and damage
  assessment

Example Attributes of EXTERIOR_WALL
25
UHRB Relationships

• Building assembled from its components via
  relationships
• Buildings have layers,
• layers have rooms,
• rooms have walls, floors and ceilings,
• walls may have doors,
• exterior walls may have windows,
• floors may have trap doors,
• ceilings may have skylights and trapdoors

26
Example IDEF1X Partitions and Openings
27
EDM-AOS

• Quite different than EDM-T
• Terrain focuses on things and their attributes
• Bridges, buildings, vegetated regions
• Any attribute can change over time, but many
  attributes change rarely
• AOS focuses on metrics which vary in time and
  space
• Temperature, water current direction, ionospheric
  scintillation
• AOS attributes may be derivable from others
• EDM contains a rationalized subset of possible
  attributes from which others can be derived
• If derivation of an auxiliary attribute is not
  trivial, the auxiliary attribute is included
• E.g., air density
• AOS has relatively few features
• Which support complex feature types and rich sets
  of attributes

28
Atmosphere Features

• 2D and 3D grids
• 2D for
• Surface phenomena (2 m above ground)
• e.g., surface wind speed and direction
• Phenomena which are not a function of altitude
• e.g., CLOUD_CEILING_ALTITUDE, THUNDERSTORM_PROBABI
  LITY
• 3D for characteristics which vary in all
  dimensions
• E.g., ATM_PRESSURE, DEWPOINT_TEMPERATURE,
  PRECIPITATION_RATE
• Low, medium and high resolution grids
• Low (50 km) available as input to initialize
  the BFM model (e.g, MM5)
• Medium (10 km) resolution of IMETS/BFM output
• High (1 km) high resolution gridded wind data,
  to support the high fidelity propagation of
  chemical and biological clouds

29
Atmosphere Features (cont.)

• 2D and 3D models
• Algorithms implemented in software which may be
  queried at any 2D or 3D geospatial location
• e.g., MAGNETIC_FIELD, ILLUMINANCE,
  TRANSMISSIVITY_QD_BY_EM_BAND
• Dynamic points
• Localized AOS features which can move
• e.g., sun and moon, smoke puffs, local
  illumination sources

30
Example Atmosphere Attributes
31
Ocean Features
32
Space Features
33
Conclusions

• OneSAF EDM is most complex to date of MS EDMs
• Encompasses terrain, building interiors,
  atmosphere, ocean and space
• Building environmental database instances
  compliant with this EDM will be challenging
• For more information
• CD containing
• 20 EDMs for MS, C4ISR and authoritative source
  products
• Rationale Documents
• CDMF
• Contact
• Denise Hovanec
• US Army Topographic Engineering Center
• dhovanec_at_tec.army.mil
• Acknowledgements STRICOM, DMSO, TEC, Paul Birkel