Naval Training MetaFOM FOM Development Breakout Group

1
Naval Training Meta-FOMFOM Development Breakout
Group

• Progress Report
• Sean Reilly (Analysis and Technology)
• 11 November 2000

2
FOM Break Group Direction

• Design philosophy
• The NTMF will be an intelligent translation of
  trainer trainer data elements into a coherent
  whole.
• Implementation process
• Build FOM from a functional decomposition of the
  NTMF Use Cases.
• Assign FOM section to groups of 1-2 people.
• Allow FOM developers some design freedom within
  re-use constraints.
• Vote on FOM using a 75 acceptance rule within
  the NTMF community.
• Core volunteers to write FOM sections
• Sean Reilly AT Newport
• Kevin Geib NAWC Pax River
• Kristin Geeza NUWC Newport
• Mark Biddle SAIC
• Tim Spollen Booz-Allen Hamilton

3
Old Action Items
 
4
Jump Start from Coordinated ASW

• Our breakout group needs a concrete test scenario
  to move forward.
• But the Use Case breakout groups are just getting
  started.
• Existing instance of distributed simulation for
  actual Fleet Training?
• BFTT regularly used in Sea Combat Commander Team
  Training at FCTCPAC, San Diego.
• 4-5 Surface ASW platforms with live crews.
• TACDEW simulation for air platforms.
• JMCIS to present C4I data to the senior staff.
• BFTT to drive the common scenario and handle the
  debrief (ground truth vs. target tracks).
• Assumes that Coordinated ASW Use Case will be a
  superset of this one.

5
FCTCPAC Force Simulation Course
from http//www.fctcpac.navy.mil/

• K-221-0175 Sea Combat Commander Team Trainer
• CDP 588D
• NEC NONE
• LENGTH 1 WEEK
• QUOTA CONTROL FCTCPAC Course Manager (COMM)/DSN
  [phone]
• TAUGHT ON REQUEST
• This trainer prepares the Sea Combat Commander
  and individual ship CIC Watch teams to operate
  effectively in a multi-ship, surface/subsurface
  threat environment at the task group/unit level
  by employing current fleet SCC tactics, command
  and control procedures, and to evaluate OPTASK
  procedures at the deployed Battle Group level.
  Furthermore, it provides battle group SCC
  tactical decision makers and operators an
  opportunity to work together before going to sea.
  Overall, the primary focus is on command,
  control, communications and coordination. The
  SCCTT should be conducted once per IDTC prior to
  COMPTUEX. The scenario is broadcast from FCTCPAC
  BFTT Module (baseline 1)/MOD TACDEW baseline 0)
  to the home port of participating units.
  Satellite voice communications and MUTTS
  connectivity are also integrated into the
  exercise to enhance the reality of the scenario.

6
Sea Combat Commander Team Training
Combat Command Mockup
TACDEW
BFTT
Tactical Voice
Room full of computers Simulates air picture
TAC-3 Workstation Scenario Exec Debrief
JMCIS and other C4I displays
Link-11Tactical Data
Afloat Training Group
TCD
89-OBT Control
STU-III Modem
STU-III Modem
STU-III Modem
Exercise Coordination by Voice
4-5 Pierside ASW Ships AN/SQQ-89 On Board Trainer
TAC-3 Workstation Manages 89-OBT Comms
7
Functional Decomposition

• Assumes regeneration and interpretation of
  sensor data local to each federate.
• Sonar, Radar, ESM.
• Scenario Definition
• Pre-exercise Environment, Platforms, Order of
  Battle.
• Local translations handled as part of BFTT IDD.
• Leverage BFTT FOM
• Platform Behaviors
• Maneuvers, Expendables, Weapons.
• Ground truth information from the virtual battle.
• Ships, surveillance aircraft (P-3,S-3), ASW
  helicopters, civilian air/sea traffic.
• Leverage RPR FOM
• Continued

8
Functional Decomposition (cont.)

• Tactical Data
• Platform tracks, areas of uncertainty.
• Captured in a format useful for after action
  review.
• Leverage C4I FOM, DII COE
• Tactical Voice
• Command/control of the virtual battle (not
  necessarily voice).
• Captured in a format useful for after action
  review.
• Leverage C4I FOM? Tasmanian Devil?
• Exercise Coordination
• Equipment status and recovery.
• Huge portion of the instructors time spent here.
• Leverage C4I FOM? Tasmanian Devil?

9
NTMF Version 0.1

• Build a Coordinated ASW prototype to jump start
  FOM development discussions
• Start from RPR-FOM 2.0D4 (includes
  UnderwaterAcoustics)
• Take out Point/Linear/Areal Environment (per Fall
  SIW)
• Take out Intercom signals (per Fall SIW)
• Add in IsPartOf Aggregation
• Add in BFTT classes for Chaff, SupplementalEE,
  CenterOfGamingPoint
• Add in C4I track data from DII COE track
  management system.
• Delivered to PMS-430 on 10/09/2000

10
Platforms and Entities
11
Emitters and Beams
Acoustics that Maintain State Info
12
Analyzing C4I Data Options
Out of all of these only the DII COE (GCCS-M)
seemed to include a rich set of attributes that
span OTH-G, Link-11, and Link-16. A draft for
C4I data was built using this model.
13
C4I Track Objects
Posits and Uncertainty
Classification Info
Intelligence Data
14
Interactions
One-time Sounds
Scenerio Initialization
Attachment Negotiation
Simulation Management and Logistics Not Displayed
Here
15
What do we still need?

• A better understanding of FCTCs exercise.
• Can we get a typical scenario from BFTT?
• Missing communication channels?
• More depth on functional area content?
• Additions to the RPR FOM
• Analysis of GASS FOM relative to this structure.
• More Elements to support Scenario Definition?
• Do we need ACTS information also?
• Still need a starting point for Exercise
  Coordination
• Still need a starting point for Tactical Voice