Program Information Overview

1
Synthetic Environment (SE) Core
Program Information Overview
John Womack Assistant Project Manager
2
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)

3
What was Presented at the Last Info Briefing

• What is an ERC
• AI User Test
• DVED Government Verification Test
• Demonstrations
• OneSAF Integration
• NTC Database
• Scenario Generation Tool
• Models
• CVCs
• After Action Review
• Long Haul Network
• C4I Adaptor

4
What is Presented this Briefing

• Accomplishments
• AI
• DVED
• SE Core Priorities
• Decisions Made at the Last PMR
• Product Line Architecture
• OneSAF Integration
• Database Schedule
• Integrated Schedule

5
AI Accomplishments SinceLast Info Briefing

• Delivered
• Environmental Runtime Component
• COE Behaviors
• Common Operating Environment
• After Action Review
• Long Haul Network
• C4I Adapter
• Data Logger selected by FCS Training Common
  Components (TCC) for the basis of their AAR

6
DVED Accomplishments SinceLast Info Briefing

• Government Verification Testing
• Ft Irwin database build
• Demonstration of Ft Irwin database on CCTT system
• Correlated visual, SAF, PVD, Radio, Env Mgr and
  SEDRIS databases created and demonstrated
• Process and tool enhancements implemented to
  improve production rate. Enhanced Transportation
  Modules (ETM) being integrated into process
• EPX-50 Plug-in
• Supports runtime 2.1.3 and 2.3 schemas
• Common Moving models
• Technical interchange meetings with CCTT, AVCATT
  and GCTT to refine CM2 model preferences
• Initial delivery of 23 models to GCTT scheduled
  for 2/29 delivery

7
SE Core Priorities

• OneSAF integration into AVCATT and CCTT, and
  retirement of the current system SAFs.
• Produce Databases
• Develop and Maintain a Product Line Architecture
• Develop and Field Common Virtual Components

8
Decisions Made at the PMR

• 96 hour test delayed two years
• Allows us to move more quickly into production
• Not relieved of the 96 requirement
• Number of Database Centers reduced to two
• The two centers must have the same capacity of
  original five centers
• Reduces cost by reducing overhead
• AVCATT Plug-in Status
• Short term Look to third party to develop a
  Radar / DRLMS database layer
• Long term Find / develop and common sensor
  model
• In FY08 SE Core will deliver a OneSAF beta
  version for Virtual Domain testing and SME review
  with the full deliverable SAF in FY09.

9
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)

10
Common Virtual Components Delivered
These SE Core products are available for use by
Programs. Product can be requested from the APM
SE Core.
11
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)

12
VSAA Product Line Architecture

• Virtual Simulation Architecture (VSA)
• Defines common structure and rules to promote
  interoperability, reuse, and adaptability to both
  current and future systems within the virtual
  domain.
• SE Core Product Line approach
• Establishes structural boundaries / interfaces,
  data interchange formats, standards, services,
  and support processes
• Provides the context for developing a set of
  common Products which can be tailored to meet the
  needs of specific training systems
• System developers / maintainers use artifacts
  from SE Core to satisfy their training and
  service needs at a reduced overall lifecycle cost

SE Core is not providing a complete system,
rather a toolkit of pieces that can be put
together to create a system
13
Why a Product Line Approach
Army Enterprise Level Training Need
with stove piped acquisitions
resulting in unnecessarily different approaches
that usually dont interoperate.
The Same Need
shall train C4I


Less Bang for the Warfighter Buck!

Duplicate work, lost money!
No Enterprise/System Engineering Across Similar
Acquisitions!
14
Product Line Architecture Framework (PLAF)
15
Example Product Definition
16
VSAA Product Line Architecture
Early Successes

• Standards
• VSA DIS Dialect (V-DIS )
• Common DIS dialect for use across the virtual
  domain
• Software Data Model (SDM)
• Defines a consistent data schema for data
  exchanges between VSA Components and the
  VSA Services
• Spatial Reference Model (SRM)
• Standardizes coordinate and orientation
  representation within the VSA

• Products
• Long Haul Network Interoperability CVC
• C4I CVC
• Scenario Generation Tool (SGT) CVC
• After Action Review (AAR) CVC
• Common Moving Models

Building Blocks of Core capability developed by
leveraging others investments yielding enhanced
training for the Warfighter.
17
VSAA Product Line Architecture
Early and Interested Parties

• Interested Parties
• Common Embedded Training System (CETS)
• CH-47F TFPS
• UH-60L/M TBOS
• UAS Embedded GCS and IMS/PMS
• ARH-70A ARMS
• PM Heavy Brigade Combat Team (HBCT)
• PM Stryker Brigade Combat Team (SBCT)
• PM Abrams

• Customer Programs
• FCS
• CCTT
• AVCATT
• PM GCTT
• CFFT
• Longbow Crew Trainer

18
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)

19
Next PoP Block /Build Schedule
Build 4 (IT)
Build 1
Build 1
Build 2
10/01 01/11
Build 2
Build 3
09/27 01/09
Build 3
01/12 04/04
Build 4 (Dev)
01/10 04/03
Build 4 (IT)
04/05 06/27
04/04 06/26
SGT Databases
06/28 09/26
06/27 09/25
Block 4
Block 5
October 2007 September 2008
October 2008 September 2009

• A Block is 1 year duration, tied to the Govt
  fiscal year
• Builds are approximately 3 months each
• Facilitates incremental development and testing
  of capability
• Within each build there will be an integration
  and test activity

20
SE Core Supportive Efforts
Available FY08
Available for Testing FY09
Available 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

• 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

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

21
SE Core Supportive Efforts
Available FY08
Available for Testing FY09
Available 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

• 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

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

22
OneSAF Functionality Fielding
23
OneSAF Functionality FieldingThread Basic JAAT
Mission
24
OneSAF Functionality Fielding
25
OneSAF Functionality FieldingThread Basic JAAT
Mission (Continued)
26
Thread Basic JAAT Mission
27
OneSAF Functionality FieldingThread Basic JAAT
MissionThread Breach an Obstacle
28
OneSAF Functionality Fielding
29
Proper Behaviors
Usability
Proper SAF Behaviors and Interactions
Performance
Functionality
Behaviors
Threads
Common Environment
Physical Models
30
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)

31
Database Schedule
TCM-V is the office that determines the Database
production priorities
32
Getting to the Database Schedule

• CM2 Deliveries
• Lot 0 - 29 Feb 2008
• Lot 1 - 13 Mar 2008
• Lot 2 25 Mar 2008
• Lot 3 - 3 Apr 2008
• Lot 4 - 15 Apr 2008
• Lot 5 17 Apr 2008
• In-process Test Number Five
• Fort Benning - 14 Mar 2008 31 Mar 2008
• Fort Campbell 21 Mar 2008 7 Apr 2008
• Validation 7 Apr 2008 17 Apr 2008
• Government Acceptance Testing (2 June 2008 14
  July 2008)
• AVCATT - 5 Aug 2008 25 Aug 2008
• Interoperable 26 Aug 2008 16 Sep 2008

33
(No Transcript)
34
Questions?