1 / 9

OneSAF Integration Overview

Synthetic Environment (SE) Core. OneSAF Integration Overview. Angela Chang SE Core OneSAF Integration Lead August 2007. SE Core Mission. Support the Training of our Warfighters by providing:.

shira
Download Presentation

OneSAF Integration Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Synthetic Environment (SE) Core OneSAF Integration Overview Angela Chang SE Core OneSAF Integration Lead August 2007

  2. SE Core Mission Support the Training of our Warfighters by providing: • OneSAF Objective System(OOS) Integration into AVCATT and CCTT and the development of virtual OOS 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. SE Core Requirements KPP 1. OneSAF Integration into CCTT and AVCATT KPP 2. Standard Terrain Database Generation Capability KPP 3. Dynamic Terrain KPP 4. Atmospheric Effects KPP 5. Net-Ready KPP 6. Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance (C4ISR) After-Action Review (AAR) Long Haul Networking Exercise Management Tools Master Terrain Database Visual Models Urban Operations Insets Training Support Package Chemical, Biological, Radiological, Nuclear and High Explosive Environment (CBRNE) Common Virtual Components

  4. Foundation to Fair Fight KPP 1. OneSAF Integration into CCTT and AVCATT (OneSAF’s Environmental Runtime Component (ERC) is the first step.) KPP 2. Standard Terrain Database Generation Capability (STDGC) STDGC OneSAF ERC 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.

  5. OneSAF Integration • OneSAF Integration (OOSI) • –SE Core integrates OneSAF into AVCATT and CCTT through phased development and integration activities. Initial capability provides the foundation for replacement of legacy SAFs, full capability provides a virtual OneSAF baseline. • Phase One: Integration of Environmental Runtime Component (ERC) (completed end of FY07) • Phase Two: Behaviors and Models (completed end of FY08) • Phase Three: System Functionality (completed end of FY09) FF

  6. Phased SAF Replacement • Phase One: Initial capability (FY07) • Integration of OneSAF into the CCTT and AVCATT virtual architectures. • Extension of CCTT and AVCATT capabilities with OneSAF functionality. • Replacement of the legacy terrain formats and environmental services in CCTT and AVCATT with OneSAF ERC. • Phase Two: Behaviors and Models (FY08) • Decomposition of MM to SAF interaction threads and implementation of critical models (physical, behavioral and environmental). • Establish sufficient virtual infrastructure and fidelity to minimize or halt CCTT and AVCATT SAF development. • Phase Three: System Functionality (FY09) • Addition of ancillary component capabilities, including PVD and CCTT modules and models. • Phase Four: Completed OneSAF Integration (FY10) • Scenario generation and conversion of remaining models. • Point of no return – System SAFs are retired. Legacy SAF development by exception after FY07

  7. Phase 1 FY07 Development • Integration of OneSAF into the CCTT and AVCATT virtual architectures: • Physical, simulation management, communication systems, and network as required by CCTT and AVCATT. • DIS services/standard enumerations CCTT MCC and AVCATT BMC simulation management of OneSAF. • Installation of OneSAF onto existing CCTT and AVCATT hardware. • Voice communications for the CCTT OneSAF workstation • Extension of AVCATT role player, SAF operator and BMC permissions to support use as either OneSAF or AVCATT SAF workstation • Internal simulation digital communications • Alignment of damage modeling between CCTT, AVCATT and OneSAF based upon ownship. • Infrastructure to support phased OneSAF integration

  8. Phase 1 FY07 Development • Extension of CCTT and AVCATT capabilities with OneSAF functionality. • OneSAF resides in the CCTT and AVCATT simulation systems and provides additional capabilities beyond the legacy virtual SAFs, including: • Support for OneSAF multiple sides/affiliations • Addition of OneSAF COE models • Replacement of the legacy terrain formats and environmental services in CCTT and AVCATT with OneSAF ERC. • Placing CCTT, AVCATT and OneSAF on the same terrain. • Addressing technical challenges within ERC/OTF critical to virtual domain. Phase 1 will put CCTT, AVCATT and OneSAF on the same terrain.

  9. OneSAF Integration • Date available • October 2007 - Interim drop to CCTT and AVCATT (Phase I) • The software for the FY07 delivery will consist of modifications to the AVCATT 7.02 baseline, the CCTT 12.0 baseline, and the OneSAF 1.1 baseline (includes patches provided before June 1, 2007) • March 2008 - CCTT & AVCATT field Phase I • October 2008 - Phase II verification testing • October 2009 - Virtual OneSAF Baseline • March 2010 - CCTT & AVCATT field Phase III • Integration support products • Interim drops available as coordinated with PM CATT • Operator training courseware • Installation procedures • Client Support and technical repository (component test plans/test cases, design notes)

More Related