(OOS)? - OneSAF Public Site

(OneSAF)
Program Overview
LTC John R. “Buck” Surdu
PM OneSAF
May 04

The Challenge of Entity-Level Modeling
THE RULE OF LGOPs
(LGOP = Little Groups of Paratroopers)
After the demise of the best Airborne plan, a most
terrifying effect occurs on the battlefield. This effect is
known as the rule of the LGOPs. This is, in its purest form,
small groups of angry 19-year-old American paratroopers.
They are well-trained, armed to the teeth, and lack serious
adult supervision. They collectively remember the
Commander's intent as "March to the sound of the guns and
kill anyone who is not dressed like you..." or something like
that.
Happily they go about the day's work.....

OneSAF Consists of two separate
programs: OTB
FY2003
FY2004
FY2005
FY2006
1.0 2.0 2.1 Retired!
OneSAF
Testbed
Baseline
OTB is an interactive, high
resolution, entity-level
simulation that represents
combined arms tactical
operations up to the battalion
level.

Composition of OTB
UAMBL
version
TRAC LEE
CSS
International
AVCATT
SAF
JVB
VERTS
OTB
1.0
OTB
2.x
DI
SAF

OneSAF Consists of two separate
programs: OTB and OOS
FY2003
FY2004
FY2005
OOS is new development, with a new
core architecture. It is a composable,
next generation CGF that can
represent forces from the entity to the
brigade level.
OOS will replace BBS, OTB, Janus
(A/T), AVCATT/CCTT SAF, and
JCATS MOUT.
FY2006
FOC Fielding
OneSAF
Objective
System

OneSAF Consists of two separate
programs: OTB and OOS
FY2003
FY2004
OOS is not
FY2005
OOS is new development, with a new
just the next
core architecture. It is a composable,
next generation CGF that can
represent forces from the entity to the
brigade level.
version of OTB.
It is a completely new
simulation!
OOS will replace BBS, OTB, Janus
(A/T), AVCATT/CCTT SAF, and
JCATS MOUT.
FY2006
FOC Fielding
OneSAF
Objective
System

Mission Needs Statement for OOS
Reduce Logistics Overhead
“The need for OneSAF capabilities is
not a response to a specific
warfighting threat against the force:
the need is driven by the guidance to
reduce duplication of M&S
investments, foster interoperability
and reuse across M&S domains, and
meet M&S requirements of the future
force.”
Mission Needs Statement form OneSAF,
approved May 1997 by the Deputy Commanding General, Training and Doctrine Command (TRADOC)

OOS Spiral Development:
Block A: “Architecture and Tools”
FY2003
FY2004
Block A (Completed FY02)
FY2005
OOS is new development, with a new
core architecture. It is a composable,
next generation CGF that can
represent forces from the entity to the
brigade level.
•Working simulation infrastructure
•Environmental data data model, runtime
component, etc. etc.
•Military Scenario Development
Environment
•Composer tools tools
•KA/KE, data data specifications, user user interfaces,
and and system flow flow work begins
•AAR tools tools
•C4I •C4I adapter
OOS will replace BBS, OTB, Janus
(A/T), AVCATT/CCTT SAF, and
JCATS MOUT.
FY2006
FOC Fielding
OneSAF
Objective
System

OOS Spiral Development:
Block B: “Some Janus-like Functionality”
FY2003
FY2004
Block B (Completed FY04)
FY2005
OOS is new development, with a new
core architecture. It is a composable,
next generation CGF that can
represent forces from the entity to the
brigade subset of level. FOC capabilities)
OOS •Minimum will replace of of 9 distinct BBS, sides sides OTB, Janus
(A/T), •Initial AVCATT/CCTT HLA-based interoperability
SAF, and
JCATS MOUT.
FY2006
FOC Fielding
•First military capability with with primitive behaviors
•Synthetic environment: weather and and its its effects, terrain, natural
illumination, NBC, and and Ultra High High Resolution Buildings
•Unit representations: BLUFOR and and OPFOR to to company (small
subset of FOC capabilities)
•Full •Full automation: BLUFOR and and OPFOR to to platoon
•Some high-fidelity dismounted and and MOUT behaviors
•Limited ATCCS & FBCB2 interoperability
OneSAF
Objective
System

OOS Spiral Development:
Block C: “OTB Functionality”
FY2003
Block C Goals
FY2004
FY2005
OOS is new development, with a new
core architecture. It is a composable,
next generation CGF that can
OPFOR combat to to brigade
represent forces from the entity to the
brigade level.
OOS •Mixed will replace BBS, OTB, Janus
fidelity physical models
(A/T), •Up •Up to to 25 AVCATT/CCTT 25 composable sides sidesSAF, and
JCATS MOUT.
FY2006
FOC Fielding
•Enhanced synthetic environment: dynamic weather, man-made
illumination, improved MOUT terrain, obscurants, and and smoke
•Unit representation: BLUFOR combat to to brigade for for selected units,
•Automation: BLUEFOR and and OPFOR to to company
•BN/BDE (HITL) with with CP CP representation (physically in in the the SE SE and and
attackable but but the the C2 C2 is is human)
•Command posts: BLUFOR and and OPFOR to to brigade
•CCTT/AVCATT crawl-walk-run interoperability events
OneSAF
Objective
System

OOS Spiral Development:
Block D: “CCTT/AVCATT SAF, BBS, ++”
FY2003
Block D
FY2004
FY2005
OOS is new development, with a new
•Expanded
core CSS
architecture. CSS It is a composable,
•Dynamic, high-resolution terrain
next generation CGF that can
represent OPFOR to to forces division from for for selected the entity units units to the
brigade level.
OOS •WARSIM will replace interoperability
BBS, OTB, Janus
(A/T), AVCATT/CCTT SAF, and
JCATS MOUT.
FY2006
FOC Fielding
•Unit representation: BLUFOR to to brigade for for selected units,
•Automation: BLUFOR and and OPFOR to to brigade (command entities)
•Interoperability with with ACTF IAW IAW DOD 5000.9 M&S Glossary
•Enhanced MOUT and and some SASO capabilities
•Capability to to replace CCTT/AVCATT SAF SAF
OneSAF
Objective
System

OOS is Purple
“Becoming a de facto Joint Model”
• USMC (PM TRASYS) spending FY04 dollars to build Marine
behaviors for OOS
• Coordination ongoing with AFAMS to build Air Force behaviors in
FY04 as well
• Conducted discussions with the Navy about OOS – no agreement yet
• Begun discussions with the U.S. Coast Guard
• JROC expected within the next couple of months
• Coordinating with JFCOM J7 and J9
• Some SOCOM systems (e.g., MH 60M and MH 47G trainers) will use
OOS
• Signed Project Agreement with the UK to build their behaviors for
OOS
• Several countries are preparing to stand up their own IDE

The Army User Community
(Modeling & Simulation Domains)
ACR
(Doctrine, Analysis & Concepts Forces)
• Analysis of Alternatives
• O&O Development
• Doctrine Development
• Requirements
• Army Transformation
• FCS
• Mobilization Analysis and
Planning
RDA
(Equipping the Force)
• System Design
• Life Cycle Cost
• Logistics Analysis
• Component Analysis & Design
• Vulnerability Analysis
• Testing
• Lethality Analysis
• Performance Factors
• Reliability Analysis
• Manprint
• Collective Training
• Staff Training
TEMO
(Warfighters:CBT, CS, CSS Forces)
• Individual Training
• Mission Rehearsal
• Distributed Training
• Crew Training
• Embedded Training

AMSAA OneSAF Support
¿ OneSAF technical representative for for RDA RDA Domain
ü Requirements
Requirements
ü Requirements
Requirements
Analysis
Analysis
ü Technical
Technical
Assessments
Assessments
ü Source
Source
Selection
Selection
Team
Team
ü WIPT,
WIPT,
Test
Test
Working
Working
Group
Group
ü Configuration
Configuration
Management
Management
– Configuration
Configuration
Control
Control
Board
Board
ü OneSAF
OneSAF
SMARTeam
SMARTeam
member
member
All Models
AMSAA
Validated
u
u
u
OneSAF POC POC for for Combat Physical Models
ü Reuse
Reuse
Focus
Focus
& Standardization
Standardization
ü Synchronization
Synchronization
w/COMBAT
w/COMBAT XXI XXI
Knowledge Acquisition/Knowledge Engineering
ü Lead
Lead
-
-
Physical
Physical
Model
Model
Knowledge
Knowledge
Acquisition
Acquisition
Documents
Documents
(PKADs)
(PKADs)
ü Characteristic
Characteristic
& Performance
Performance
Data
Data
– Certified
Certified
Data
Data
Test Test & Evaluation
ü Recommended
Recommended
Government
Government
Lead
Lead
ü Developed
Developed
Draft
Draft
Test
Test
& Evaluation
Evaluation
Plan
Plan
ü Participating
Participating
in
in
Planning,
Planning,
Executing
Executing
and
and
Documenting
Documenting
ü Verification
Verification
& Validation
Validation
lead
lead
for
for
Combat
Combat
Physical
Physical
Models
Models

OOS Development “Beta Sites”
Block B
Organization
TRADOC Program Office OOS
TRAC Monterey
TRAC White Sands
National Simulation Center
Futures Lab
Dept of Computer Science
Department of Systems Engineering
J9 – Joint Experimentation
Research Development and Engineering Center
Battle Command Training Center
Army Materiel Sciences Analysis Activity
Topographic Engineering Center
Soldier Battle Lab
Unit of Action Mounted Battlespace Battlelab
Operational Test Command
NAVAIR
CERDEC
USMC PM TRASYS
Objective Force Warrior
Warrior Preparation Center
…
Location
Ft Monroe
Naval Postgraduate School
White Sands Missile Range
Ft Leavenworth
Ft Leavenworth
West Point
West Point
Joint Forces Command
Huntsville
Ft Hood
Aberdeen Proving Grounds
Ft Belvoir
Ft Benning
Ft Knox
Ft Hood
BMH Orlando
Ft Monmouth
Orlando, FL
Natick, MA
Ramstein, Germany
User Feedback: Early and Often

OneSAF Program Schedule
OneSAF
Test Bed
Baseline
(OTB)
FY98 FY99 FY00 FY01 FY02 FY03 FY04 FY05
Currently On Time
On Budget
Build A
Meeting All ORD Requirements
Build B
V2.0
V2.1
FY06
OneSAF
Objective
System (OOS)
BLOCK A
BLOCK B
BLOCK C
BLOCK D
P3I
OOS Program
Milestones
MS A
STOC Award
ORD V1.0 ORD V1.1
MS B/C
FOC
OTB
V1.0
OTB
V2.0
OOS
V1.0

What is One Semi-Automated Forces
(OneSAF) Objective System (OOS)
•A composable, next generation CGF
•Represent a full range of operations, systems, and control processes (TTP)
•Entity up to brigade level
•Variable level of fidelity
•Supports multiple Army M&S domain (ACR, RDA, TEMO) applications.
Software only
Automated
Composable
Extensible
Interoperable
Platform Independent
Capable of replacing legacy entitybased
simulations: BBS,
OTB/ModSAF, CCTT/AVCATT
SAF, Janus, JCATS MOUT
Field to:
RDECs / Battle Labs
National Guard Armories
Reserve Training Centers
All Active Duty Brigades
and Battalions

OOS’ Composability:
Solution to the ORD Dilemma
Entity
Count
Fidelity
•System composer
•Entity composer
•Unit composer
•Behavior composer

Multiple Levels of Fidelity
qMost entities come in low, medium, and high
fidelity
qInteractions between entities of different levels of
fidelity are tested
qAllows users to “dial up” the level of fidelity
where it is needed
Low Medium High

What is Composability
“OOS is a Box of Tools”
Leader and Staff Training
Leader and Staff MOUT Training Leader and Staff Mission Rehearsal
System Composition
System Composition
System Composition
Standalone Analytic Simulation
Stimulator for Virtual Simulations
Test and Evaluation Support
Other
System Composition
System Composition
System Composition
System Compositions
THE ONESAF
ARCHITECTURAL
APPROACH
FACILITATES
MEETING BOTH
CURRENT AND
FUTURE
UNDEFINED
REQUIREMENTS

OOS Provides Leap-Ahead Capabilities over
Current Simulations
•High Resolution MOUT Capabilities
•High Resolution Synthetic Natural
Environment (SNE)
•Variable Resolution Models
•Adjustable Entity and Unit Behaviors
•Composability – “Tailorablity”

OOS’ Enhanced MOUT Capabilities
q Enhanced DI SAF behaviors
q Leveraging Urban Operations FACT
q Validated, physics-based models
q Ultra-high resolution buildings (UHRB):
• Stairs
• Usable roofs
• Interior walls
• Furniture
• Rubble
JRTC
q Underground structures:
• Cellars/basements
• Tunnels
• Hiding holes
Screen shot
Of UHRB
Editor

OneSAF SASO-Type Capabilities
qMultiple sides (25)
qChangeable relationships
• Friendly
• Hostile
• Suspect
• Neutral
qMilitary and nonmilitary
forces
qConventional and
unconventional weapons
qNon-military vehicles

OOS’ Enhanced Synthetic Natural
Environment
• Increased number of
trafficability categories
• Increased number of
attributes and features
• Enhancement of mixedfidelity
terrain modeling

Supported Terrain Features
in Various CGF’s
400
350
300
250
200
150
100
50
0
Janus OTB/JSAF OOS

SNE Quantitative Analysis
120.0%
100.0%
Features
80.0%
60.0%
40.0%
20.0%
0.0%
DNC
DTOP
FFD
SWBD
120.00%
TOD0
TOD1
100.00%
80.00%
60.00%
40.00%
20.00%
0.00%
TOD2
TOD4
UVMAP
VMAP0
VMAP1
Union of Digital Sources
Attributes
DNC
DTOP
FFD
SWBD
TOD0
TOD1
TOD2
TOD4
UVMAP
ONC
TLM
CCTT
OOS
VMAP0
VMAP1
Union of Digital Sources
ONC
TLM
CCTT
OOS

Block B
NTC
CCTT P2
Environment Repository
Block A
JRTC
WARSIM Reuse/Interoperability
VMAP Level 1 (1:250,000 Scale)
Global Availability ~2004
Block C/D
CMTC
CCTT P6
Block B (NEW)
Caspian
(Azerbizhan)
UABL Reuse
Block B/C
Korea
CCTT P5
Block TBD
Ft Hood
CCTT P3
Block TBD
Balkans
CCTT P4
Block B
Golden
Database
NEW :Urban
Templates
MOUT FACT
1:12500 Area
High
Density
Area
Algorithmic
Terrain
Area
Tactical
Terrain
Areas

OOS’ Enhanced Modeling
•Contemporary
Operating Environment
(COE) behavior models
based on TSD design.
•Tools that expose
internal models to users
Tools
•Processes to assist users
enhance and modify the
models

Composer Tools:
OneSAF Desktop
Behavior Composer
Entity Composer
Unit Composer

Composer Tools:
System Composer

Composer Tools:
Entity Composer
Entity composed of of
various physical
models
Geometry Editor for for
placing sensors, etc.
on on entities

Composer Tools:
Unit Composer
Units built from
entities and other units
Subordinate units and entities are are
“by reference”

Composer Tools:
Behavior Composer
Behavior Primitives
Conditional
branching;
if-then rules
Other Composite Behaviors

Composer Tools:
Management and Control Tool
Two different
map views
Order of of Battle
Mission Editor

3D Stealth Tool (AcuScene)
AAR Use Case
•AARs after
battle
•OC’s during
battle
Not a Virtual Simulator!
Team OneSAF is is Collecting 3D model
repositories from CCTT, AVCATT, CAV
SIM, ABCA, etc.

OneSAF is REAL
qOneSAF Testbed Baseline (OTB)
Current Contributions and Uses
qOneSAF Objective System
Planned Contributions and Uses

OneSAF Technology Empowering
the Current Force (OTB)
300+ user sites, including…
BLCSE
MATREX
AVCATT
CAV SIM
VERTS
FCS Analysis
USMC
CAST UP,
CACCTUS
& DVTE
JSAF,
SAGIS,
CFFT
JVB
DI SAF

OneSAF Technology Empowering
our Allies
OTB V1.0 International
OTB V1.0 ABCA
ModSAF International
OTB Project Agreement
Data Exchange Agreement

OneSAF Technology Empowering
the Future Force (OOS)
Battle
Army Constructive
Laboratory
Training Federation
Constructive
(ACTF)
Simulation
Environment
(BLCSE)
Modeling Architecture
FCS
for Technology,
Embedded Research &
Training
Experimentation
(MATREX)

What is MPARS
qA collection of OOS
components and OTB
qUseful in operational
course of action
development and
analysis
qHas been linked to
C2PC (USMC) and
CAPES (Army)
MSDE
(Scenario
Editor)
Power
Stripes
(AAR Tool)
OneSAF
(Simulation
Engine)
AcuScene
(Stealth
Viewer)

One Semi Automated Forces
(OneSAF)
Technical Highlights

OneSAF Product Line Architecture
Framework (Original)

Development of the OneSAF Product
Line Architecture
Leader and Staff Training
Leader and Staff MOUT Training Leader and Staff Mission Rehearsal
System Composition
System Composition
System Composition
Standalone Analytic Simulation
Stimulator for Virtual Simulations
Test and Evaluation Support
Other
System Composition
System Composition
System Composition
System Compositions
THE ONESAF
ARCHITECTURAL
APPROACH
FACILITATES
MEETING BOTH
CURRENT AND
FUTURE
UNDEFINED
REQUIREMENTS

OOS Development
Examples of Cutting Edge Technologies
qSoftware Development:
• Spiral development
• An implementation of extreme programming
• Real teaming – government, contractors, users colocated
• Continuous user participation
• SEI Level 4 and continuous process improvement
• Heavy reuse of existing software
• Heavy use of open-source products
• Will be delivered with source code

OOS Development
Examples of Cutting Edge Technologies
qSoftware Technologies
• Platform-independent software (Linux, Windows,
and Solaris) (currently 1.9M lines of code,
eventually 3.5M)
• Tailorable, product-line architecture
• Enterprise Java Beans allow software to be
modified without recompiling code
• Heavy use of XML for nearly all data – with no
data stored in the program itself
• Exposed models through user tools

PEO STRI L-V-C Architecture
Built Atop A Common Framework
Interoperable Applications
LVC LVC Core Core Architecture
Common Components
Common Common
API’s API’s DIF’s, DIF’s, &
Protocols Protocols
SE SE Core, Core, C4I C4I Adapter, Adapter, SNE, SNE, AAR, AAR,
Scenario Scenario Generation, Generation, etc. etc.
OOS, OOS, CTIA, CTIA, OIS, OIS,
CATT, CATT, OneTESS OneTESS
Gunner Gunner Trainers, Trainers, Staff Staff Trainers, Trainers,
Virtual Virtual Trainers, Trainers, etc. etc.

T & E
RTCA
Instrumentation
-OneTESS
-MILES
Live – Virtual – Constructive
“Enabled by Objective Systems”
CTCs
Home
Stations
Joint Range Architecture
(Test & Training)
Common Components
Deployed
ACTF
WARSIM
OneSAF
JDLM
CATT
Manned
Modules
OneSAF
Common
Real World
SE CORE
Components
Common
C2 and ISR
Components
Live Constructive Virtual
Fully Interoperable Training Capability
FCS
Manned
Modules
OneSAF
Common
Components

OneSAF Objective System (OOS)
Emerging Standards
MSDL MSDL –– Military Military Scenario Scenario Definition Definition Language Language
Defines Defines the the language language between between tools tools & simulations simulations
to to provide provide military military scenario scenario information information to to
OneSAF. OneSAF. Currently Currently MSDE, MSDE, C2PC C2PC and and CAPES CAPES
interoperate interoperate with with OTB OTB & OOS OOS using using MSDL. MSDL.
Future Future efforts efforts to to include include FCS FCS C2 C2 systems systems and and
Battlefield Battlefield Mgmnt MgmntLanguage (BML) (BML) integration. integration.
OTF OTF --Objective Objective Terrain Terrain Format Format
Defines Defines the the OOS OOS Synthetic Synthetic Natural Natural
Environment. Environment. Provides Provides a a common common LVC LVC
environmental environmental representation representation for for USA USA
simulations simulations (CATT (CATT/ / AVCATT AVCATT // CTIA CTIA //
WARSIM WARSIM // Combat Combat XXI) XXI) and and federations federations
(ACTF (ACTF/ / BLCSE BLCSE // MATREX). MATREX).
PLAF PLAF --Product Product Line Line Architecture Architecture Framework Framework
A modular, modular, composable composable architecture architecture with with
well well defined defined APIs APIs and and data data schemas schemas for for all all
components. components. Supporting Supporting current current USA USA & USMC USMC
constructive constructive & virtual virtual simulation simulation development.
development.
SORD SORD –– Simulation Simulation Object Object Runtime Runtime Database Database Contains Contains shared shared battlespace battlespaceobjects, which which
include include platforms, platforms, units, units, dynamic dynamic environment environment objects objects (smoke (smoke clouds, clouds, obstacles) obstacles) missions, missions,
orders, orders, and and reports. reports. Provides Provides ability ability for for any any SORD SORD client client to to access access the the data data in in the the OOS OOS
database database if if it it has has properly properly expressed expressed interest interest for for those those objects. objects.

OOS API Example – MSDL
“Committed to Open Standards”
MSDL is the Military Scenario Development Language.
Formatted in XML, MSDL is used to exchange scenario data
for interoperability across systems.
CAPES CAPES
ABCS ABCS
Legacy Legacy
Sims Sims
OTB
CATT
WarSIM
Janus
Others…
C2PC C2PC
MSDE MSDE
PFPS PFPS //
Falconview Falconview
MSDL MSDL
OTB OTB
OneSAF OneSAF
SSDE SSDE
OneSAF OneSAF
AAR AAR
O
O
SS

Lifecycle Phases
2:
Product Line
Development
3:
Product Line
Deployment &
Install
14: Retrieval
4: Event
Planning
5: Database
Development
1: Knowledge
Acquisition /
Engineering
1-3: OneSAF Product Line
Devel. & Deploy phases
13: Archival
12: Post-
Execution
Analysis/AAR
OneSAF
Repositories
OneSAF
Software
6: Software
Development
7: Model
Composition
4-8: Pre-Event phases
9-11: Event phases
12-14: Post-Event phases
11: Simulation
Execution
10: Systems
Test &
Verification
9: Simulation
Configuration
8: Scenario
Generation

Software Development Process

Component Development Contract

Component Testing Phases
Developer Testing
Freq of Test
Developmental
Testing
Class /
Unit
Test
Integration Testing
Formal
Integration
Component
Integration
User Assessment
Baseline
SWIT
Engineering
Review
Board
Engineering /
Integration
Baseline
Informal
Integration
Tests
Continuous
Periodic
or
event driven
Once per
Block
Government Testing
User Testing
“Operational like”
BRT
Dry Run
Test
Readiness
Review
At the conclusion of Block D
BRT
Culminating T & E
Event
Major / Block
Release
A,B,C,D

Establishment of OneSAF.net
q All OneSAF task orders are
using it for communications
‣ Program oversight through
weekly IPT meetings
‣ Supports daily work processes
used across the program
‣ Publication of technical
materials
‣ Configuration managed
continuously
q OneSAF.net accessible
remotely with a valid user
account and password

Questions
LTC John R. “Buck” Surdu
PM OneSAF
john.surdu@us.army.mil
Mr. John Logsdon
DPM OneSAF
john.logsdon@peostri.army.mil