Download presentation
Presentation is loading. Please wait.
Published byMia miah Dolman Modified over 10 years ago
1
John Womack APM SE Core 1 April 2009 John Womack APM SE Core 1 April 2009
2
2 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) SE Core Mission
3
3 One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment. SE Core Vision
4
One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment. SE Core Vision
5
5 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) SE Core Requirements
6
6 Interoperable by use of the: 1. OneSAF 2. Common Terrain Databases 3. Long Haul Network 4. C4ISR Today Ad Hoc Work A-rounds SE Core Systematic “Plug & Play” SE Core Emerging Requirements
7
P=Program Office (gov’t) C=Contractor Support M=Matrix (gov’t) P=Program Office (gov’t) C=Contractor Support M=Matrix (gov’t) John Womack (P) APM Program Analyst Sandra Depew (M) Contracts Doug Greenwood (M) Mike Hickey (M) Acquisition Logistics Jeff Patterson (M) Project Systems Eng Susan Rodio (M) Virtual Architect Bill Reese (M) Deputy APM Leonard Hobbs (C) DVED PD Gene Strickland (P) Database Eng Bruce Howie (C) Database Eng Mark Johnson (C) Database Systems Eng Connie Perry (M) CVC Eng Pat Garrity (M) A&I PD Christina Bell (P) OSI/CVC Eng Keith Nielsen (M) Lead Architect Richard Deakins (M) OSI/C4I Eng Juan Garcia (M) CVC Coordination SE Core Organization Chart Staff Eng Phong Pham (M)
8
8 Combined Effort Between Both Primary Contractors SE Core Functional Breakdown
9
MayAprJunJulAugSepOctNovDecJanFebMar DR Fixes, Retest & Deliver Sep 7 - 30 GAT / Interop3 Aug 31 – Sep 18 CCTT IPT2 April 21-23 5.2 Build Eval / Interop2 June 1-5 5.3 Build Eval August 3-7 AVCATT IPT2 May 4-8 GAT Dry Run Aug 24 – Sep 11 Code Freeze GAT TRR Aug 27 CCTT, FCS, C4I, Misc Evaluation SE Core DR Work AVCATT, C4I, O2, GAT CCTT C4 and Other Development AVCATT C4I Development CCTT Misc Development Afghanistan Area 1 400 x 250 km Central Iraq 300 x 250 km Afghanistan Area 2 TBD OTF 8 AVCATT Database Validation Interoperable Database Validation AVCATT CM2 Delivery Re-turn of OTF 7 Databases FCS LCT LVC-IA Common Sensor Model AoA OpenFlight Plug-in AVCATT Database IPT Database Working Group SE Core Schedule
10
10 SE Core Interoperability Demonstration December 2008 CCTT Manned Module CCTT SAF Entities AVCATT Manned Module OneSAF Entities CCTT Manned Module Embedded OneSAF Entities AVCATT Manned Module Embedded OneSAF Entities AVCATT Spiral ERC Demo SE Core OSI IPD2 IPD1 Program Manned Modules DVED Interoperable databases Common SAF Common Models Environment CM2 Models Manned Module, Host and IG extensions. AVCATT ongoing integration of ERC and OneSAF AVCATT, CCTT Manned Modules and SAF running ERC Running CCTT Converted Baghdad OTF database. Air Focus DVED databases OneSAF replaces legacy SAFs Ground Focus Interoperability Continuum Capabilities to be Demonstrated in December 2008 CCTT/AVCATT/OneSAF Interoperability Successful execution of Air- Ground Scenario Embedded OneSAF entities interact and engage CCTT and AVCATT manned modules. AVCATT and CCTT running Same Terrain Database Common Format Common Features Cross platform model alignment Requires less setup time Reduces Engineering work around Jun 07 Jan 08 June 08 Dec 08 Apr 09 Sep 09 Sep 10
11
11 Block / Build Schedule 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 Build 4 (I&T) Build 1 Build 2 Build 3 Build 4 (I&T) Block 4Block 5 October 2007 – September 2008October 2008 – September 2009 10/01 – 01/11 04/05 – 06/27 06/28 – 09/26 09/27 – 01/09 01/10 – 04/03 04/04 – 06/26 06/27 – 09/25 Build 2 Build 3 Build 4 (Dev) 01/12 – 04/04 SGT & Databases
12
12 OSI Build Plan
13
DR Fixes, Retest & Deliver Sep 7 - 30 July Road To GAT JanFebMarAprilMayJune August Sept Final Integration GAT Dry Run Aug 24 – Sep 11 GAT / Interop3 Aug 31 – Sep 18 GAT TRR Aug 27 Build 5.2 5.1 Build Eval Feb. 23-27 Build 5.3 AVCATT IPT2 May 4-8 CCTT IPT2 April 21-23 Build 5.4 DR Fixes OneSAF Common Baseline GAT Initial Go/NoGo Decision Aug 7 DR Fixes 5.2 Build Eval / Interop2 June 1-5 DR Fixes 5.3 Build Eval August 3-7 DR Fixes Code Freeze CCTT Scenarios Available to SECore Jun 24
14
Schedule Post GAT SeptJulyMayAprilSeptOctNov/DecJanFebMarchJuneAugust SE Core A&I GAT (CCTT and AVCATT) CCTT FCS C4I Misc Evaluation AVCATT C4I O2 GAT AVCATT OSI RFT CCTT Integration of OSI AVCATT Integration of OSI SE Core DR Work CCTT C4I Development AVCATT C4I and Misc Development AVCATT OneSAF Operational (O2) Development CCTT OSI RFT 20092010 CCTT Misc Development
15
Behavior Working Group Process
16
Behaviors RWA Battle Position Search and Occupy Conduct Ground Reconnaissance Clear and Mark Breach Lanes Conduct Screening Operations Ground Tailgate Resupply RWA Attack Unit Defend Battle Position To the N th Behavior Working Group Steps (Overview) Requirement Analysis Internal Review Behavior Working Group Development Integration and Test Ready for GAT
17
17 December 2008I/ITSEC 2008 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
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
19 Database Virtual Environment Development
20
20 SE CORE DVED GAT OUTBRIEF Production Metrics Trend Analysis Metrics scaled to 100km x 100km database SE CORE DVED GAT OUTBRIEF10/3/2008 5 to 6X Productivity Improvement Over CCTT Legacy Databases and ~1.4X Improvement Over GVT CCTT Legacy SE Core Development SE Core GAT
21
21 DVED Government Acceptance Test Successes 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
22 Metric Collected Current Projected Unit DB Effort Release 2.0 Projected Unit DB Effort Release 2.1 Projected Unit DB Effort Release 2.2 Projected Unit DB Effort (man hours) Grand Total 309729972419.72096.66 FTE 18 1412 Sq. KM / Month with 12 people 22,09522,83228,28032,637 Sq. KM / Month with 18 people 33,14334,24942,42048,956 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. Production vs. Software Development
23
23 180 x 180
24
24 Database Production Schedule Oct 08 Jan 09 Apr 09Jul 09Oct 09 Jan 10 Apr 10 Jul 10 Oct 10 Ft. Stewart, Ft. Hood, Ft. Riley, Pinion Canyon Afghanistan Area 1 400 x 250 km Central Iraq 300 x 250 km Ft. Irwin Ft. Benning Ft. Campbell Afghanistan Area 2 TBD Ft. Bliss 400 x 250 km Korea TBD 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). 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
25 Correlated Dataset Required Standard Source Data NGA Commercial Joint Services Other Agencies Governments Countries Potential sources Automated tools use standard source data Correct / Align Data Add / Merge / Value Added Master Terrain DB Generation Toolset Non-Proprietary Open format IG Independent Correlated Data Traceability to Source Data Consumable by virtual Sims OOS EDM Expand for Virtual Domain Plug-Ins Tool Kit 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) Produce correlated runtime databases to enable training for mission planning, mission rehearsal, and mission execution. Standard / Rapid Terrain Database Generation Capability
26
26 December 2008I/ITSEC 2008 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
27
27 December 2008I/ITSEC 2008 Plug-ins Developed & Planned Plug-ins Developed to DatePlug-ins being developed in GFY09 EPX Plug-in (version 2.1.3 and 2.3)OTF (version 8.0) OTF (version 6.0)ESRI Shape with FFD attribution CCTT Plan View DisplayDTED CCTT Environment ManagerCADRG for FBCB2 CCTT Radio Database (TIREM)OpenFlight (version 15.7) SEDRIS (ISO compliant)CIB ESRI Geodatabase Plug-inEncapsulated Postscript
28
December 2008I/ITSEC 2008 GAT CCTT Database Highlights Fort StewartFort Hood Fort RileyPinion Canyon
29
29 CM2 Deliveries: -157 models to GCTT -261 models plus variants going to CCTT on 26 Nov 08 -Other deliveries include AF for evaluation Common Moving Models Sept 2009 CM2 to correlate with OneSAF (behaviors, geometry, bounding volumes, etc.)
30
30 December 2008I/ITSEC 2008 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
31
31 Program Concerns
34
34 Afghanistan Database RC(S) RC(E) Afghanistan – East TDB Afghanistan – South TDB
35
35 Afghanistan East
36
36 Generic FOB Photo Living Quarters Maintenance Building Storage Building Storage Containers Motor Pool Small Storage Containers Guard Tower HeliPad
37
37 Correlated Dataset Required Standard Source Data NGA Commercial Joint Services Other Agencies Governments Countries Potential sources Automated tools use standard source data Correct / Align Data Add / Merge / Value Added Master Terrain DB Generation Toolset Non-Proprietary Open format IG Independent Correlated Data Traceability to Source Data Consumable by virtual Sims OOS EDM Expand for Virtual Domain Plug-Ins Tool Kit 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) Produce correlated runtime databases to enable training for mission planning, mission rehearsal, and mission execution. Standard / Rapid Terrain Database Generation Capability
38
38 December 2008I/ITSEC 2008 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
39
39 December 2008I/ITSEC 2008 DVED STDGC Process Risk Status (Oct. 31, 2008)
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.