Navy Aviation Simulation Master Plan Interoperable Database: Process

1
Navy Aviation Simulation Master Plan
Interoperable Database Process Tools

• Steve Schwalm
• L3 Communications
• Orlando, Florida USA

2
Overview

• Goals
• Study Requirements
• Functional Diagram
• CONOPs for the process

3
Goals

• Provide interoperable databases for dissimilar
  systems
• Databases must correlated well enough to achieve
  fair fight
• Must address visual, sensor, radar, radio and CGF
  databases (to name a few)

4
Study Requirements

• Determine workable process for interoperable
  databases
• Determine candidate tools compatible with process
• Ensure commercial availability
• Outline specification for interoperable formats
• Data formats, content
• Acquire sample tools
• Develop Sample Refined Source Data (RSD) set
• NAS Fallon area
• 4 geo-cells - terrain, models, geo-specific
  texture
• Distribute Sample RSD to other suppliers as
  beta test
• Evaluate results
• Compare run-time versions

5
Database Functional Diagram
6
CONOPs Overview

• 12 Step Process
• NASMP to provide refined source data and
  correlation requirements
• Simulation Vendor formats into unique system
  format based on requirements

7
Conops for Database Production

• Step 1 Requirements Definition
• NASMP determines need for new gaming area to
  support distributed mission training across
  multiple platforms
• F-18, F-14, EA-6B, E-2C, etc.
• Defines geographic area, airfields, target areas,
  etc.
• Defines training requirements for gaming area
• Low level, ground attack, air-to-air, takeoff and
  landing, etc.
• Will lead to polygon allocations (terrain vs. 3D
  features), texture resolution
• Defines correlation requirements for all
  participants
• Tolerance for terrain skin, placement of feature
  models

8
Conops for Database Production

• Step 2 Database Developer Identified/Selected
• a) NASMP identifies initial supplier of gaming
  area
• Included in simulator program
• Stand alone database procurement
• b) Plans to develop the database with government
  assets
• Initial target IG defined, performance
  specifications understood
• Step 3 Source Data Collection
• Source data is collected for gaming area
• Government and/or supplier to acquire source data
• The more the better
• SMEs are consulted to refine database
  requirements

9
Conops for Database Production

• Step 4 Refined Data Set Production
• Source data is corrected, altered, filtered to
  meet training requirements
• Terrain data corrected, areas flattened
• Feature data corrected to match geo-specific
  imagery
• Adjusted to terrain data
• 3D models developed - altered from previous
  library
• Imagery is rectified, blended, adapted for
  texture map application
• Refined data archived
• Original source data archived

10
Conops for Database Production

• Step 5 Database Production
• Refined data applied to creation of database
  areas
• Terrain skinned, tiled
• Feature models applied
• Texture maps created from refined imagery
• Hand build models inserted
• Airfields, target areas, areas of interest
• Sensor characteristics applied as required
• Only sensors for initial target aircraft are
  included
• Normal database production process
• Database Working Groups to monitor progress,
  content
• Normal database acceptance process
• Final tuning on simulator
• Determine compliance with requirements
• Correlation of database to RSD set

11
Conops for Database Production

• Step 6 Database Goes Into Training
• Initial application operational
• Step 7 Refined Source Data Set Finalized
• Database specific features added to refined data
• Actual polygons for terrain skin, derived
  features
• 3D models
• Release notes document content, design decisions
• Similar to Database Design Document

12
Conops for Database Production

• Step 8 RSD Set Accepted by NASMP
• RSD tested for content, format
• Evaluated against original requirements for RSD
• Step 9 NASMP Distributes RSD to Follow On
  Database Suppliers
• Original requirements apply
• Correlation requirements included

13
Conops for Database Production

• Step 10 Follow On Database Production
• Suppliers use their normal tool sets
• Choose the portions of the RSD that work best
  with native tools
• Consult with initial supplier as required
• Optimize database for aircraft mission and Image
  Generator performance

14
Conops for Database Production

• Step 11 Follow On Database Acceptance, In
  Training
• As in step 5 for initial database
• Step 12 Feed Back Added Source Data (optional)
• NASMP determines when extensions to the source
  data are required
• Example Added material coded texture maps
• Example Added new and/or improved models

15
Contact

• Steve Schwalm
• L3 Communications
• 407-382-2197
• srschwalm_at_link.com
• Dan Paterson
• NAVAIR Orlando Training Systems Division
• 407-380-2564
• patersondj_at_navair.navy.mil