1 / 39

John Womack APM SE Core 1 April 2009

John Womack APM SE Core 1 April 2009. SE Core Mission. OneSAF Integration into AVCATT and CCTT and the development of virtual OneSAF composition as the standard computer generated forces for the virtual domain.

thai
Download Presentation

John Womack APM SE Core 1 April 2009

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. John Womack APM SE Core 1 April 2009

  2. SE Core Mission • 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. SE Core Vision One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment.

  4. SE Core Vision One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment.

  5. 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) Other Non-KPP requirements: 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)

  6. SE Core 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. C4ISR

  7. SE Core Organization Chart John Womack (P) APM P=Program Office (gov’t) C=Contractor Support M=Matrix (gov’t) Virtual Architect Bill Reese (M) Deputy APM Leonard Hobbs (C) Contracts Doug Greenwood (M) Mike Hickey (M) Program Analyst Sandra Depew (M) Acquisition Logistics Jeff Patterson (M) Project Systems Eng Susan Rodio (M) DVED PD Gene Strickland (P) A&I PD Christina Bell (P) Database Systems Eng Connie Perry (M) Lead Architect Richard Deakins (M) CVC Coordination CVC Eng Pat Garrity (M) Database Eng Bruce Howie (C) Database Eng Mark Johnson (C) OSI/C4I Eng Juan Garcia (M) Staff Eng Phong Pham (M) OSI/CVC Eng Keith Nielsen (M)

  8. SE Core Functional Breakdown

  9. Afghanistan Area 1 400 x 250 km Central Iraq 300 x 250 km Afghanistan Area 2 TBD SE Core Schedule Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 5.2 Build Eval / Interop2 June 1-5 CCTT IPT2 April 21-23 AVCATT IPT2 May 4-8 5.3 Build Eval August 3-7 GAT Dry Run Aug 24 – Sep 11 SE Core DR Work GAT / Interop3 Aug 31 – Sep 18 CCTT C4 and Other Development Code Freeze CCTT, FCS, C4I, Misc Evaluation DR Fixes, Retest & Deliver Sep 7 - 30 GAT TRR Aug 27 CCTT Misc Development AVCATT, C4I, O2, GAT AVCATT C4I Development AVCATT Database Validation Interoperable Database Validation AVCATT Database IPT OTF 8 OpenFlight Plug-in AVCATT CM2 Delivery Database Working Group Common Sensor Model AoA Re-turn of OTF 7 Databases FCS LCT LVC-IA

  10. SE Core Interoperability Demonstration December 2008 Capabilities to be Demonstrated AVCATT Manned Module AVCATT Manned Module in December 2008 • CCTT/AVCATT/ OneSAF Embedded OneSAF Entities Interoperability OneSAF Entities • Successful execution of Air - Ground Scenario • Embedded OneSAF entities interact and engage CCTT and AVCATT manned modules. • AVCATT and CCTT running CCTT Manned Module CCTT Manned Module Same Terrain Database • Common Format • Common Features Embedded OneSAF Entities CCTT SAF Entities • Cross platform model alignment • Requires less setup time Interoperability Continuum • Reduces Engineering work Jun 07 Jan 08 June 08 Dec 08 Apr 09 Sep 09 Sep 10 around Running ERC AVCATT SE Core Program IPD2 Converted Demo Spiral OSI Manned CCTT Modules Air AVCATT Baghdad IPD1 AVCATT, Focus DVED databases DVED Interoperable ongoing OTF CCTT Manned OneSAF replaces legacy SAFs Ground Focus databases integration of database. Manned Module, Host Common SAF ERC and Modules and and IG Common Models OneSAF SAF running extensions. ERC Environment CM2 Models

  11. Block / Build Schedule Build 4 (I&T) 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 (I&T) 04/05 – 06/27 SGT & Databases 04/04 – 06/26 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 Gov’t fiscal year • Builds are approximately 3 months each • Build Demonstrations to verify interim capabilities • Facilitates incremental development and testing of capability

  12. OSI Build Plan

  13. Road To GAT Jan Feb Mar April May June July August Sept Build 5.2 Build 5.3 Build 5.4 Code Freeze Final Integration GAT Dry Run Aug 24 – Sep 11 5.2 Build Eval / Interop2 June 1-5 AVCATT IPT2 May 4-8 CCTT IPT2 April 21-23 5.3 Build Eval August 3-7 5.1 Build Eval Feb. 23-27 GAT / Interop3 Aug 31 – Sep 18 DR Fixes DR Fixes DR Fixes DR Fixes DR Fixes DR Fixes, Retest & Deliver Sep 7 - 30 GAT Initial Go/NoGo Decision Aug 7 GAT TRR Aug 27 OneSAF Common Baseline CCTT Scenarios Available to SECore Jun 24

  14. Schedule Post GAT 2009 2010 Sept Oct Nov/Dec Jan Feb March April May June July August Sept SE Core A&I GAT (CCTT and AVCATT) CCTT FCS C4I Misc Evaluation SE Core DR Work CCTT OSI RFT CCTT C4I Development CCTT Integration of OSI CCTT Misc Development AVCATT C4I O2 GAT AVCATT C4I and Misc Development AVCATT OSI RFT AVCATT Integration of OSI AVCATT OneSAF Operational (O2) Development

  15. Behavior Working Group Process

  16. Behaviors

  17. Why Use OneSAF Provide interoperability Virtual Trainers LVC-IA Provide for a Fair Fight OneSAF equals one fight Configuration Control Maintain one SAF for entire Virtual Domain CCTT SAF AVSAF Longbow Crew Trainer Save money December 2008 I/ITSEC 2008

  18. Life After OneSAF Integration Dynamic Environment (terrain, atmospherics, sensor) Virtual Simulation Architecture (VSA) V-DIS advancement into IEEE DIS standard Extend existing CVCs for customers AAR, Interop Gateway, C4I, Scenario Generation Maintain SE Core portal New CVC opportunities Distributed AAR Market research

  19. Database VirtualEnvironment Development

  20. Production Metrics Trend Analysis Metrics scaled to 100km x 100km database CCTT Legacy SE Core Development SE Core GAT 5 to 6X Productivity Improvement Over CCTT Legacy Databases and ~1.4X Improvement Over GVT 10/3/2008 SE CORE DVED GAT OUTBRIEF SE CORE DVED GAT OUTBRIEF

  21. DVED Government Acceptance TestSuccesses of the Test The GAT has produced four databases covering a larger area than those current CCTT terrain databases. Production of the 180 x 180 (32,400 sq. km.) databases will be larger than any CCTT terrain database.

  22. Production vs. Software Development Production vs. Software Development Achieving desired production rate requires 6 additional database engineers plus some continued CM2 support to enhance model libraries. The DVED team has evaluated the cost benefit of hiring six additional production bodies as opposed to software development.

  23. 180 x 180

  24. Database Production Schedule Apr 09 Jul 09 Oct 09 Jul 10 Apr 10 Oct 10 Jan 09 Jan 10 Oct 08 Ft. Stewart, Ft. Hood, Ft. Riley, Pinion Canyon Afghanistan Area 1 400 x 250 km Central Iraq 300 x 250 km Afghanistan Area 2 TBD Korea TBD Ft. Bliss 400 x 250 km Ft. Irwin Ft. Benning Ft. Campbell Database Priorities As Determined by TCM-V 1. Satisfy operational training requirements. 2. Replace existing CCTT and AVCATT DBs. 3. New requirements (such as FCS).

  25. Standard / Rapid Terrain Database Generation Capability OOS EDM Standard Source Data Expand for Virtual Domain Master Terrain DB Generation Toolset • Non-Proprietary • Open format • IG Independent • Correlated Data • Traceability to Source Data • Consumable by virtual Sims Master DB Potential sources • NGA • Commercial • Joint Services • Other • Agencies • Governments • Countries Plug-Ins • Total development time of 96 hours (72 hrs) • 180 km x 180 km (DTED level 3) (300km x 300km) • 2.5km x 2.5km (DTED level 5) urban insert (50km x 50 km) • (1000km x 1000km (DTED level 1) large areas) Tool Kit Produce correlated runtime databases to enable training for mission planning, mission rehearsal, and mission execution. • Automated tools • use standard source data • Correct / Align Data • Add / Merge / Value Added Correlated Dataset Required

  26. Plug-in Development Process To access correlated databases from SE Core DVED, programs are required to use a “plug-in” to the Runtime Database Generation Toolkit (RDGT) The major elements in the plug-in development process are: Go to the SE Core Portal (http://se-core.org) and request a copy of the DVED SEE API SDK (DVED Government Sponsorship required) Develop the plug-in Build the sample database and moving models directly to your runtime format On-site DVED testing Testing in the DVED Controlled Development Lab on more robust data Run correlation tests Distributed processing testing Documentation review Receive Plug-in Validation for DVED production December 2008 I/ITSEC 2008

  27. Plug-ins Developed & Planned December 2008 I/ITSEC 2008

  28. GAT CCTT Database Highlights Fort Stewart Fort Hood Fort Riley Pinion Canyon December 2008 I/ITSEC 2008

  29. Common Moving Models • CM2 Deliveries: • 157 models to GCTT • 261 models plus variants going to CCTT on 26 Nov 08 • Other deliveries include AF for evaluation • Sept 2009 CM2 to correlate with OneSAF (behaviors, geometry, • bounding volumes, etc.)

  30. DVED Summary Significant production efficiencies have been realized through enhancement of tools, processes, and training Integrated suite of multiple-vendor plug-ins rapidly produces correlated runtime databases using multiple geographic projections in a single build GAT successfully conducted and databases validated on CCTT Terrain Database Production Go Ahead Received CM2 Production well underway with over 256 models currently available December 2008 I/ITSEC 2008

  31. Program Concerns

  32. Afghanistan Database Afghanistan – East TDB Afghanistan – South TDB RC(E) RC(S) 34

  33. Afghanistan East 35

  34. Generic FOB Photo Storage Building Storage Containers Motor Pool Maintenance Building HeliPad Living Quarters Small Storage Containers Guard Tower 36

  35. Standard / Rapid Terrain Database Generation Capability OOS EDM Standard Source Data Expand for Virtual Domain Master Terrain DB Generation Toolset • Non-Proprietary • Open format • IG Independent • Correlated Data • Traceability to Source Data • Consumable by virtual Sims Master DB Potential sources • NGA • Commercial • Joint Services • Other • Agencies • Governments • Countries Plug-Ins • Total development time of 96 hours (72 hrs) • 180 km x 180 km (DTED level 3) (300km x 300km) • 2.5km x 2.5km (DTED level 5) urban insert (50km x 50 km) • (1000km x 1000km (DTED level 1) large areas) Tool Kit Produce correlated runtime databases to enable training for mission planning, mission rehearsal, and mission execution. • Automated tools • use standard source data • Correct / Align Data • Add / Merge / Value Added Correlated Dataset Required

  36. Architectural Overview • Key Challenges • Common DB products must address the needs of many • Optimizing Tools, Processes & Personnel to achieve > 10X improvement in DB productivity while satisfying multiple confederates • Concurrent development with other major initiatives (OneSAF) and Confederate upgrades • Requires a significant User paradigm shift from traditional DB development and acceptance methods December 2008 I/ITSEC 2008

  37. DVED STDGC Process Risk Status (Oct. 31, 2008) December 2008 I/ITSEC 2008

More Related