1 / 13

Training, Exercises, Military Operations (TEMO) Domain Update One Semi-Automated Force

Training, Exercises, Military Operations (TEMO) Domain Update One Semi-Automated Force. LTC Tom Greenwald TEMO Domain Rep National Simulation Center 20 August 2007. NSC Way Ahead. Coordination with TPO/PM–OneSAF on v2.0 Use Cases, Measures of Effectiveness, Measures of Performance

mostyn
Download Presentation

Training, Exercises, Military Operations (TEMO) Domain Update One Semi-Automated Force

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. Training, Exercises, Military Operations (TEMO) Domain UpdateOne Semi-Automated Force LTC Tom Greenwald TEMO Domain Rep National Simulation Center 20 August 2007

  2. NSC Way Ahead • Coordination with TPO/PM–OneSAF on v2.0 Use Cases, Measures of Effectiveness, Measures of Performance • Develop TEMO User community team including selected units, Army Schools & Centers, selected simulation centers for OneSAF assessment • Subject OneSAF v2.0 to full TEMO-standard Operational Readiness Exercise • BCT-level Warfighter event • Will not test capabilities that Program Manager says aren’t ready

  3. Jan/Feb 08 V2.0 TEMO Assessment NSC OneSAF Evaluation Schedule Jan 08 Dec 07 Aug 07 Jan 07 Jul 07 Jan 07 • March – October 07 • Assess v1.1 fixes to current baseline (75 PTRs, 52 testable by NSC) • June – November 07 • Assessment of OneSAF v1.5 • Execute threads, vignettes and an increasingly complex scenario • Coordinate assessment plan, performance metrics with TPO and PM-OneSAF • December 07 – February 08 • TPO Assessment of OneSAF v2.0 (pre-release software) Dec 07 • TEMO Assessment of OneSAF v2.0 Jan/Feb 08 Sep 06 Coord Test Cases, Scope, Eval Criteria Assess v1.1 Fixes Complete Complete Complete V1.1 Delivery V1.5 Delivery V1.0 Delivery V2.0 TPO Assessment (Pre-release) V2.0 Delivery V1.5 PM Assessment (Pre-release) V1.0 Assessment

  4. v1.0 TEMO Prerequisite Threshold Requirements • Eight Threshold System-level Requirements • BCT WFX • Usability • Models & Behaviors • Distributed Exercising • After Action Review • User Documentation • Terrain Database Library • Ability to Federate w/Constructive and Virtual simulations/simulators • TEMO projection of how each OneSAF version ‘services’ these Threshold Requirements is shown at right v2.0 v3.0 v4.0 Note: assumes that prioritization of requirements/P3I facilitates implementation of TEMO requirements

  5. Provide Simulation/Stimulation Support for a Brigade-level Warfighter Exercise v1.0 v2.0 v3.0 v4.0 • Primary Training Audience is BCT and subordinate commanders and staffs • Secondary TA is company and platoon personnel in Response Cells and simulation workstations • Exercise duration up to four days, 24-hour operations • Hardware required for all functions (simulation, workstations, AAR, etc.) cannot exceed 124 Common Hardware Platforms (standard Basis of Issue for brigade-level Battle Command Training Center) • Simulation entity count of up to 25,000 • Operator train-up with two days instruction and one day Practical Exercise • Robust Command and Control (C2) stimulation • Equal to the training capability of the Joint Land Component Constructive Training Capability Entity Resolution Federation (JLCCTC ERF)

  6. Meet Minimum Usability Requirements v1.0 v2.0 v3.0 v4.0 • Build exercise database in not more than two weeks • Build terrain database in not more than four weeks, for up to 300km2, • System set-up (HW, SW, C2 connectivity, communications network connectivity) in not more than two days • Simulation stability to provide a minimum availability of 98 percent (availability in minutes divided by exercise duration in minutes) • Simulation lag/latency not to exceed one minute, for both simulation-internal and simulation to C2 messaging.

  7. Provide Minimum Capabilities for Models and Associated Behaviors v1.0 v2.0 v3.0 v4.0 • Relevant to the Contemporary Operational Environment (COE) • Small/irregular unit combat • MOUT/complex terrain operations • IED offensive/defensive operations • Small arms Air Defense • Political/Military/Economic/Social/Infrastructure/Information effects • Properly executes workstation commands • Correct movement, sensor- and/or shooter-target interactions and effects • Outcomes/results of interactions are consistently within accepted ranges of ‘real world’ effects • Ability to ‘compose’ basic model attributes to create any variant of a piece of equipment (tank, Infantry Fighting Vehicle, truck, radar, rifle, etc.)

  8. Support a Distributed Exercise Architecture with Servers and Workstations at Separate Locations v1.0 v2.0 v3.0 v4.0 • Simulation and workstations geographically separated • Support functions (technical control, AAR) able to function at ‘any’ location

  9. Provide After Action Review Capability v1.0 v2.0 v3.0 v4.0 • Develop AAR products concurrent with simulation execution • Collect data/develop AAR products for both OneSAF ‘stand alone’ and ‘federated’ applications • Text, graphic, 2D and 3D products • ‘Playback’, with ability to select point(s) in time, playback faster than real time, pause, reverse, and filter on selected units/information • Provide formal AAR presentation in no more than two hours from PAUSEX/ENDEX.

  10. Provide User Documentation for BCTC Personnel and Simulation Augmentation Personnel • Technical ‘How to Run’ manuals: usable by BCTC personnel • Operational ‘How to Use/How to Manipulate’ manuals • Usable by ‘Virtual Warriors’ (BCTC augmentee personnel) v1.0 v2.0 v3.0 v4.0

  11. Terrain Database Library v1.0 v2.0 v3.0 v4.0 • The TPO-directed requirement for OneSAF is to provide five terrain databases with the fully-fielded version • Korea • Southwest Asia • Fort Hood • NTC • JRTC • Units worldwide build/maintain own terrain databases

  12. Ability to Federate with Constructive and Virtual Simulations/Simulators v1.0 v2.0 v3.0 v4.0 • Provide required modeling/effects • Provide consistent shared view between Constructive & Virtual sims • Common Environment • Replace CCTT and AVCATT SAFs • Provide a “Fair Fight”

  13. Summary • Actively working with TPO-OneSAF, PM-OneSAF, and other domains • Supporting PM in assessing v1.0, v1.1, v1.5 • Planning in progress for evaluating v2.0, Dec 07 • Possible (best case) TEMO certification of OneSAF v3.0 with fielding in FY 09-10 timeframe • Probable (most likely) TEMO certification of OneSAF v4.0 with fielding in FY 10-11 timeframe

More Related