Can you tell which entities are OneSAF?

1
SE Core Information Brief
Can you tell which entities are OneSAF? Can you
tell which ones are CCTT? Can you find the CCTT
ownship? This is on a OneSAF Terrain Format
(OTF). The scenario had 300 CCTT entities and
200 OneSAF entities. Everyone could kill each
other.
2
Synthetic Environment (SE) Core
Program Information Overview
John Womack Assistant Project Manager
3
SE Core Mission

• Support the Training of our Warfighters by
  providing

• OneSAF Integration into AVCATT and CCTT and the
  development of virtual OneSAF composition as the
  standard computer generated forces for the
  virtual domain.
• Development of a standard Terrain Database (TDB)
  generation process to create a non-proprietary,
  open format, image generator (IG) independent,
  Master TDB (MTDB) consumable by virtual
  simulations, within a total development time of
  96 hours.
• The development of a Virtual Simulation
  Architecture (VSA) to provide a Common Virtual
  Environment (CVE) that links system and
  non-system simulations into a fully integrated
  and interoperable training capability.
• Development of Common Virtual Components (CVC)
  that will reduce redundancy, increase realism,
  and facilitate an integrated live, virtual,
  constructive training environment. (LVC TE)

4
Emerging Requirements

• Today
• Ad Hoc
• Work A-rounds
• SE Core
• Systematic
• Plug Play

Interoperable by use of the 1. OneSAF 2. Common
Terrain Databases 3. Long Haul Network 4.
Common Components
5
SE Core Vision
One fight involving multiple simulators, using
one SAF, on a common terrain database, resulting
in a fair fight environment.
6
Foundation to Fair Fight
Standard Terrain Database Generation Capability
OneSAF Integration
Replacement of the legacy terrain formats and
environmental services in CCTT and AVCATT with
OneSAF Environmental Runtime Component
Develop Standard/Rapid Terrain Database
Generation Capability tools and processes that
will create a non-proprietary, open format, image
generator (IG) independent, Synthetic Environment
Master Database (MDB)
OneSAF Environmental Runtime Component
The Terrain Database runs on the ERC to provide
correlation and SAF interoperability.
7
What is the ERC?

• Environmental Runtime Component (ERC) provides
  the services the Manned Modules and SAF use to
  obtain terrain information from the OneSAF
  Terrain Format (OTF).
• Examples
• Height of Terrain (HOT)
• Line of Sight (LOS)
• Munition Intersection

8
Why is ERC important?
CCTT Manned Modules
CCTT Manned Modules
CCTT Other Systems
CCTT Other Systems
ERC SNE
Legacy SNE
ERC SNE
Legacy SNE
Integrate
Integrate
AVCATT Manned Modules
AVCATT Manned Modules
CCTT SAF SAF WS
CCTT SAF SAF WS
ERC SNE
Legacy SNE
ERC SNE
Legacy SNE
Integrate
Integrate
AVCATT SAF
AVCATT SAF
CCTT CGF
CCTT CGF
ERC SNE
Legacy SNE
ERC SNE
Legacy SNE
Integrate
Integrate
OOS SAF Front-End
OOS SAF Back-End
OOS SAF Front-End
OOS SAF Back-End
Extend
ERC SNE
Legacy SNE
Legacy SNE
ERC SNE
Extend
9
Why is SE Core needed?

• SE Core is key to interoperability of simulators
  within the virtual environment.
• Differences in simulators create problems
• Interoperability
• Capabilities disparity
• Fair fight
• Weapon Engagements
• Same Terrain
• Common Models

Virtual Environment
Terrain
SAF
Common Components
10
OneSAF Virtual Enhancements

• Optimize EDM for visual cueswhat it looks like.
• Support real time performance.
• Represent orientation articulated parts
• Stimulate Manned Module displays.
• Interface with embedded communication devices.

11
SE Core Supportive Efforts
FY08
FY09
FY10

• Terrain improvements
• General PTR fixes
• Visual System issues (smoothing)
• Tool (composers, etc) fixes and improvements
• Behavior improvements (sniper)
• DIS improvements
• Focus on Armor, Artillery, ADA, FWA/RWA
• Mobility Component, Models Analysis

• Prioritization comes from SE Core
• Some are long lead items
• Continual feedback is key

• PTR Fixes
• Focus areas Mech Infantry, Armor, Artillery,
  Dismounted
• Infantry, Ground mobility, Ground Vehicle
  Sensors,
• Dynamic Terrain- Craters, Smoke Dust,
• Environment/Meteorological, Air Mobility - Lift
  and Utility,
• RWA, Slingload, RWA internal loads, Fixed Wing
  Aircraft,
• Manual Laser Ops

• PTR Fixes
• Focus areas RWA Scout Attack, IFF Fire
  Control Radar, Aircraft Lighting,
• Ground Markers, Aircraft Survivability Equipment,
  Missiles, Hellfire, FARP,
• Air Defense Artillery, ADA Missile Model, C4I,
  Wingman Behaviors,
• Scenario Generation, PFPS Integration

12
Demonstrations

• CCTT/OneSAF Scenario
• Ft Bliss and NTC Database
• Scenario Generation Tool (SGT)
• Sensor Model Video (I/ITSEC)
• Longhaul Network (I/ITSEC)
• C4I Capability (I/ITSEC)

13
AI Users Test Results
Total Test DRs Written during all UT (AVCATT and
CCTT) 110
14
AI Users Test Results

• Top Priorities for DR Resolution and Retest
• ERC (includes AVCATT/CCTT legacy SAF and MM,
  Databases)
• OneSAF Functionality (SIMAN, Voice
  Communications, Damage Assessment )

Currently working to close out 17 DRs and
complete retest to support a Dec 07 Delivery
15
CCTT Database
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
Ft Bliss Database
21
Ft Irwin NTC Database
22
Master Database (MDB)
The MDB is NOT a runtime format. The MDB is NOT a
terrain database used by simulators. The MDB is
an integral part in building new and legacy
runtime databases. The MDB contents can be
updated as new source data is gathered and
cleaned.
23
Standard/Rapid Terrain Database Generation
Capability (STDGC)
Produce correlated runtime databases to enable
training for mission planning, mission rehearsal,
and mission execution.
FF

• Automated tools
• use standard source data
• Correct / Align Data
• Add / Merge / Value Added

Correlated Dataset Required
24
Database Plug-Ins
What is a Plug-in and why do I need one?
A plug-in simply formats the data extracted from
the MDB so your simulator can read it.

• A simulator must be able to read data extracted
  from the MDB.
• SAF
• Environmental / Visual
• Radio
• Radar
• PVD
• SEDRIS
• Others

25
Database Vision
One Plug-in for each System (meets system
capabilities).
One database with all the needs of the Virtual
Domain contained within the database!
26
Database Status Today
Plug-ins developed to meet the needs of the
individual system.
One database with Most of the Virtual Domain
needs contained within the database!
27
Database Distribution
KTR
CCTT PDSS
CCTT Site
World File Config. Files IR Color File Paths
Database Center
AVCATT Site
AVCATT
CFFT Site
CFFT
CDT Site
CDT
28
Database Government Verification Test (GVT)

• Overview of the GVT Efforts
• Successfully produced a Ft Irwin database (90km x
  110km) in 30 days
• Validated processes and procedures for database
  development
• Gathered production metrics on various aspects of
  the production efforts to help identify areas of
  improvement
• Validated the CM2 modeling tools and capabilities
  for production of SE Core Moving Models
• Remaining GVT Items
• Load GVT databases on CCTT system
• Waiting on OTF plug-in testing to complete
• CM2 model integration tests
• Waiting on EPX plug-in testing to complete

29
Database Snapshots

• Training Area

30
Database Snapshots
31
Database Snapshots

• Geospecific Models

32
Enhanced Transportation Modules (ETM)
Elevation Slope Analyzer
Enhanced Bridge Generator (EBG)
33
Enhanced Bridge Generator
34
ETM Modules

• Enhanced Urban Roads (EUR)

35
Enhanced Urban Roads
36
ETM Modules
Ford Generator (FG)
Multi-State Bridges and Complex Buildings (MSBCB)
37
Standard/Rapid Terrain Database Generation
Capability (STDGC)
Produce correlated runtime databases to enable
training for mission planning, mission rehearsal,
and mission execution.
FF

• Automated tools
• use standard source data
• Correct / Align Data
• Add / Merge / Value Added

Correlated Dataset Required
38
Scenario Generation Tool

• Provide users the ability to
• Create, modify, and verify scenario files.
• Specify entities, tactical overlays, and
  environment parameters.

Ability to translate legacy scenario files into
the new scenario file format able to translate
the new scenario files back into the legacy
format
Simulation System
The SGT is developed to be utilized as an
off-line pre-runtime tool that can be run on a
laptop and provide a modular scenario development
environment
39
Common Models
40
Why are CM2 needed?

• Moving Models are a key ingredient to most
  virtual environments
• Differences in moving models creates problems
• Interoperating simulations
• Overlapping training capabilities
• Fair fight
• Detection
• Recognition
• Identification

Virtual Environment
Terrain
Feature Models
Moving Models
41
Evolution of CM2

• SME Testing on PEO STRI virtual training
  simulators created a real need for CM2
• An IPT was formed to build specifications and
  determine model building priorities
• SE Core took control of CM2 with the DVED
  contract award to Team CAE USA
• The CM2 process has matured via spiral development

CM2

• Key Ingredients
• IG independent
• Multiple resolutions
• Multiple presentation domains
• Open and available specifications
• Government purpose rights

End State 500 models
Born on Date October 2005
42
Model Example
CCTT New Model
CCTT Legacy Model
43
Levels of Fidelity (LOFs)
44
Example
LOF 5 843 total polygons
45
Example
LOF 4 471 total polygons
46
Example
LOF 3 270 total polygons
47
Example
LOF 2 106 total polygons
48
After Action Review (AAR)
Data Collection Data Analysis Stealth
49
Long Haul Network Interoperability
LHNI CVC
LHNI CVC
Other Virtual Sim Gateway

• Supports multiple DIS dialects concurrently
• Communicates with gateways of existing simulation
  systems
• Provides secure communication of network traffic
  through National Information Assurance
  Partnership (NIAP) approved encryption products

50
C4I CVC
Data Communications Live C4I systems - Virtual
Sims C4I Message Translation SA picture for
entities that do not already produce their own
position reports
Tactical LAN
51
PM CATT I/ITSEC BOOTH
3
-
Phase
480
V
-
100
Amps
,
conductors terminated
Carpeted Area
T
-
1
or Point to Point drop
52
Questions?