Intro to OneSAF IITSEC 20061

1
An Introduction to the OneSAF Objective System
(OOS)David Nash, Ph.D.Mike Saavedra Science
Applications International Corporation
2
Purpose

• The purpose of this tutorial is to provide an
  orientation to the prospective user of the
  OneSAF Objective System (OOS)
• The take-home result of this session will be a
  basic understanding of
• OOS stakeholders and their influence on design
• Important locations within the OneSAF file system
  
• Key technologies and tools
• Design and execution of an OOS scenario
• OneSAF is registered in the U.S. Patent and
  Trademark Office by the United States Department
  of the Army.

3
What is One Semi-Automated Forces (OneSAF)
Objective System (OOS)?
4
OneSAF Communities of Interest

• Three Domains
• ACR (Advanced Concepts and Requirements)
• Experiments with new concepts and advanced
  technologies to develop requirements in doctrine,
  training, leader development, organizations,
  materiel, and soldiers
• Evaluates the impact of horizontal technology
  integration through simulation and
  experimentation
• RDA (Research, Development, and Acquisition)
• Designs, develops, and acquires weapons systems
  and equipment
• Performs scientific inquiry to discover or revise
  facts and theories of phenomena, followed by
  transformation of these discoveries into physical
  representations
• TEMO (Training, Exercises, and Military
  Operations)
• Includes most forms of training at echelons from
  the individual soldier through collective,
  combined arms, joint and/or combined exercises
• Includes mission rehearsals and evaluations of
  all phases of war plans
• Includes analysis during the rehearsal or
  evaluation to validate the plan

5
OneSAF Users
6
The OneSAF Product Line Architecture
Architectural Applications (OneSAF
System Compositions)
SeamlessTraining System Composition
Test and Evaluation System Composition
Leader andStaff Training System Composition
Force and Organizations Analysis Tool System
Composition
Other System Compositions

OneSAF Product Layer
Simulation Generator
C4I Adapter
Simulation Core
Analysis Review
Repository Manager
SystemComposer
Technical Manager
Simulation Controller
Maintenance Environment
Event Planner
Knowledge Eng. Env.
Model Composer
OneSAF Component Layer
SystemComposerTool
KA/KETools
OneSAF Component Support Layer
System RepositoryServices
GUIServices
SimulationServices
Simulation Object RuntimeDatabase
CompositionServices
Modeling Services
EnvironmentRuntimeServices
EnvironmentReasoningServices
Plan ViewDisplay
DataCollectionServices
OneSAF Repository Component Layer
System Composition Repository
Military Scenario Repository
EnvironmentRepository
Parametric Initialization Repository
SoftwareRepository
Simulation Output Repository
KA/KERepository
Local ExerciseEnvironmentRepository
OneSAF Common Services Layer
Middleware Services
Monitor Services
Time Services
Messaging Services
Interchange Services
Name Directory Services
Coordinate Services
ORB
JDBC/ ODBC
WWW
Live Range Adapter
DIS
RTI
COEServices
OneSAF Platform Layer
Hardware
Operating System
Network
7
MSDE / AAR

• Military Scenario Definition Environment (MSDE)
• PowerPoint-based
• Creates scenario definition (units, command
  relationships, dispositions) in Military Scenario
  Definition Language (MSDL)
• MSDL is imported into a OneSAF scenario for
  execution
• After-action Review (AAR) Tool
• Generate slides of the simulated scenario
• Statistics of snapshot data items

8
OneSAF File System Layout
BINDIR onesaf/SWR/bin/services/sys/composition C
OMPDIR onesaf/PAIR/compositions
9
Whats in ?

• PAIR
• PAIR/compositions Unit, entity, behavior
  compositions
• PAIR/enum Open enumeration definitions
• PAIR/icons Iconic representations
• PAIR/mi/formationData Formation definitions
• SOR
• SOR/cache Pre-compiled versions of data
• SOR/collectedPublishedData Data collection
  output
• SOR/log Logging output

10
Whats in ?

• SWR
• SWR/bin Startup scripts for important
  applications
• SWR/bin/services/sys/composition Location of the
  runtimeloader and composer scripts
• SWR/docs Various forms of system documentation
• SWR/lib Software in system-loadable format
• SWR/SCR System component repository
• SWR/src Source code
• SYSTEM
• SYSTEM/difs Data interchange formats
• SYSTEM/properties Configurable load-time
  properties

11
OneSAF Composition Tools
12
Entity Composer
13
Using the Entity Composer

• System composition composers, therefore
  BINDIR/runtimeloader composers
• Typical components
• Physical
• Sensors (eyeballs, FLIR, etc.)
• Weapons
• Mobility
• Vulnerability
• Behavior
• Direct fire controller
• Operations
• Intel
• Supply

14
Unit Composer
15
Using the Unit Composer

• System composition composers, therefore
  BINDIR/runtimeloader composers
• Unit versions of components, e.g., Operations,
  Intel, Comms
• Units have associated formation data

16
Behavior Composer
17
Prepared Behaviors

• OneSAF will supply a set of approved entity,
  unit, and behavior compositions.
• Some representative behaviors
• Attack by fire
• Breach wall
• Conduct entity MEDEVAC
• Set engagement criteria
• Prepare fighting position
• Users may compose these behaviors as needed to
  meet their requirements.

18
System Composer
19
The Management and Control Tool
20
Environment Runtime Component (ERC)
21
Sides and Forces

• A force is a collection of entities, units, or
  forces.
• A side is a collection of entities, units,
  forces, or sides.
• Sides have relationships which determine
  behaviors.

22
Interoperability

• OneSAF instances interoperate via
• Internal protocol (OneSAF messaging services or
  C4I Adapter)
• External protocol (HLA or DIS)

23
Data Collection

• The Data Collection Specification Tool (DCST) is
  used to specify the sources and data elements
  that are to be collected.
• These data elements are written in XML format at
  run time to a file in the SOR.

24
Data interchange formats
25
Application programmer interface
26
OneSAF Summary

• OneSAF is a highly configurable suite of systems
  for the generation of semi-autonomous forces.
• Simulation behaviors and models are data-driven
  to the maximum extent possible, to support
  customization and what-if analysis.
• System capabilities are exposed by powerful
  visual tools.
• High degree of interoperability through DIS and
  HLA, and usage of XML for state.