Title: SE Core OneSAF Integration Update
1Synthetic Environment (SE) Core
SE Core OneSAF Integration Update
Angela Chang Peggy Hughley
2SE 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)
3Accomplishments SinceLast Briefing
- Delivered in FY07
- OneSAF Integration
- Environmental Runtime Component
- COE Behaviors
- Common Simulation Management
- After Action Review CVC
- Long Haul Network CVC
- C4I Adapter CVC
- Delivered in FY08
- Scenario Generation Tool (SGT) CVC
4SE Core Development
- Provide Common Solutions across the Virtual
Domain - Employs Software Reuse to Meet Virtual Simulation
Needs - OneSAF is the Key Reuse Component for many
solutions - Scenario Generation Tool (SGT) CVC
- C4I CVC
- ERC Integration
- OneSAF Integration
5SGT Purpose of EffortPOC Gina Moerk
moerkg_at_se-core.net
- To develop a Scenario Generation Tool (SGT) that
meets the virtual training requirements for the
Advanced Gunnery Training System (AGTS) - Output a Scenario File Format (in XML) to meet
exercise requirements for multiple gunnery
systems - Read in legacy scenario files for updates
- Ability to Create, Modify, and Verify scenario
files - Provide a user interface to be used by students
and instructors - Provide point-to-point and field-of-view LOS
Capability - Provide a 2D map view of the scenario file for
verification - Provide a 3D view of the scenario file for
verification
6SGT System Design
7OneSAF Extensions for SGT
- Extended OneSAFs Privileges Architecture to a
data driven approach - Added new Gunnery Behaviors reusing the existing
primitive and composite Behaviors - Added new Unit Compositions reusing the existing
entity compositions - Integrated 3D Viewer reusing the DIS Framework
- Converted AGTS CTDB into OTF
- Extended the SORD and the MCT to include Entitys
having malfunctions - Extended the SORD to contain Weather Attributes
- Added a Translator to read and write Gunnery
Legacy Scenario Files and convert it to SORD
(Only support AGTS in this instance) - Modified Directory Services to enforce password
security rules - Added usability improvements
8C4I CVC Purpose of EffortPOC Jeff Conner
connerj_at_se-core.net
- Provide data communications between the Tactical
Internet (TI) and the virtual simulation - Translate C4I messages from live C4I systems,
connected to the TI, to the VSA Simulation
Network Protocol for use within a virtual
simulation - Provide bridge between the internal elements of a
Training System and the external tactical C4ISR
equipment within a Tactical Operations Center
(TOC) - Includes data format conversions, data
validation, and communications standards,
ensuring that messages passing between the live
and virtual environments are comprehensible by
recipients on both sides of the TII.
9C4I CVC System Design
- OneSAF C4I Adapter provides the capability to
- Interface with Tactical C2 Equipment
- Ability to Parse Tactical Messages
- Ability to Translate Tactical Messages via Joint
Mapper Engine (JME) - Ability to Route Tactical Messages
- SE Core provides the capability to
- Model Signal Degradation based on Radio
Capabilities via Interchangeable Radio Systems
Models. (Composability allowing for varying
fidelity modeling).
- Model Message routing on the Tactical Internet
via Interchangeable Tactical Network Models.
(Composability allowing for varying fidelity
modeling). - Support multiple message parsers at runtime
within the C2 Adapter for Baselines not in CMPs
control. - Communicate with Virtual Simulation Nodes via
V-DIS and other DIS Dialects (AVCATT DIS etc.) - Radio Communication Family PDUs
- SIMAN PDUs
10OneSAF Extensions for C4I CVC
- Extracted the C4I Adapter from OneSAF
- Added simulation side acknowledgement in a new
bidirectional acknowledgement system. - Enhanced message pass through capabilities to
support complete bidirectional pass through. - Added runtime multi-parser support.
- Encapsulated radio and network capabilities for
modeling purposes. - Added support for BFT-based systems.
- Added support for AVCATT VMF to both Adapter and
Mapper Tool.
11ERC Integration Purpose of EffortPOC Matt Reilly
reillym_at_se-core.net
- Provide a common SNE component for virtual
applications - CCTT and AVCATT use different SNE components with
different software features, different terrain
formats/support, different runtime communication
protocols - ERC is highly reusable in terms of applicable
software features in non-OneSAF systems - ERC Integration puts AVCATT, CCTT, and OneSAF on
common terrain (OTF) - ERC Integration included AVCATT and CCTT
Components including the SAF and Manned Modules - Convert Databases from legacy formats to OTF
12ERC Integration System Design
Applications
- Examples of Applications
- CCTT MM, SAF, AAR, MCC, CGF, OC WS
- AVCATT MM, SAF, and SAF PVD
Manned Sims, SAF, Etc.
- Minimize external interface changes
- Implement wrapping layer for each system
- Support swapping between legacy SNE and ERC
- Test by comparison and partial integration
- Specialized services, unique to each SAF
- Ex path planning, cover and conceal
- Majority of legacy functionality retained
- Terrain data accessed thru ERC
- Modify legacy software to operate on ERC-based
data
Legacy Services
Services that relied on CTDB or MrTDB
ERC
New capabilities
- Hidden from legacy services via Virtual C API
OTF
Common Database
13OneSAF Extensions for ERC Integration
- Created a virtual API to add virtual
functionality to ERC Component - Environment Data Model (EDM) contains all of the
features required for virtual simulations - Added the attributes needed to the EDM to support
the virtual environment - Subseted EDM to minimize OTF size
- Coordinated all efforts with the OneSAF ERC Team
14OneSAF Integration PurposePOC Chris Marino
marinoc_at_se-core.net
- Provide OneSAF as SAF and CGF components in
AVCATT and CCTT Virtual Training Systems - Provide Additional OneSAF capabilities to AVCATT
and CCTT systems - COE Behaviors
- Add System Level Capabilities to OneSAF
- Voice Communications
15CCTT with OneSAF Integrated
CCTT GATEWAY
HMMWV
All/Most Components -- New SNE Services
C4I GATEWAY
Manned Module
AAR
Legend Blue Few or no
modifications Red New, OOS-based S/W
CCTT NETWORK 100BaseFx Ethernet
EDIMM HMI
DIMM CGF
DIS Interop
SEOD
OOS SimCore
OOS MCT (SAF WS)
MCC
CCTT CGF
OC Workstations
CCTT SAF WS
Env Mgr
SORD
SEOD
16AVCATT with OneSAF Integrated
BDA
TOC
AAR Controller
AAR Participant
AAR Stealth
Simulated Radio
Simulated Radio
ERC
AVCATT Gateway
HLA Gateway
DIS
HLA
DIS
Simulated Radio
Real Time Data Logger
BMC Controller
BMC Participant
BMC Stealth
SAF Operator
Role Player
Realtime Data Logger
Role Player
Role Player
Role Player
ERC
ERC
ERC
ERC
ERC
ERC
Legend Blue Few or no
modifications Red New, OOS-based S/W
DIS Traffic only
SORD Traffic only
DIS SORD Traffic
17OneSAF Extensions for OneSAF Integration
- Created User Logins with appropriate privilege
access - Extended DIS Interoperability Component
- Created System Specific User preferences for PVD
Display Options - Extended C4I Mappers to support CCTT and AVCATT
required message data - Extended OneSAF to support unique POV
functionality - Added support for DIS Node Failure
- Integrated Voice Communications
18Next PoP Block /Build Schedule for OneSAF Integ
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
19SE 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, - Environment/Meteorological, Air Mobility - Lift
and Utility, - RWA, 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, Slingload, JAAT, Missiles, Hellfire,
FARP, Air Defense Artillery, ADA Missile Model,
C4I, Wingman Behaviors, Scenario Generation, PFPS
Integration, Dynamic Terrain- Craters, Smoke
Dust
202008 IT Schedule
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Build 4.2
Build 4.3
Build 4.4
Build 4.1
AVCATT IPD
Build Demo
Build Demo
CCTT IPD
I/ITSEC
CCTT DB Testing
- AVCATT 7.02
- CCTT 12.1
- OneSAF 1.1
- AVCATT 7.02
- CCTT 12.1
- OneSAF 2.0
- AVCATT 9.04
- CCTT 12.4
- OneSAF 2.1
- AVCATT 9.04
- CCTT 12.4
- OneSAF 2.5
- AVCATT 7.02
- CCTT 12.1
- OneSAF 2.0
20
212009 Milestone Schedule
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Build 5.2
Build 5.3
Build 5.4
Build 5.1
Build Demo
AVCATT IPD
Integration / Dry Run
CCTT IPD
Acceptance
21
22