Architecture and Integration Update Derrick Franceschini A

1
Architecture and Integration UpdateDerrick
FranceschiniAI Chief Architect
One Semi-Automated Force (OneSAF)
2
v3.0 Accomplishments

• Requirements Integration Board (RIB) Requirements
• Data Collection and Analysis Support
• Load AMSAA Physical Performance Data
• Federate with JDLM in order to stimulate BCS3
• Operate (SCAMT) distributed over a WAN
• Usability Improvements
• Performance Improvements

3
Data Collection Capabilities Provided in v3.0

• This was a continuation of the previous task from
  v2.0.
• Includes the capability to merge data output
  files from multiple SimCores nodes.
• Enhanced Data Filters
• Tool Usability Enhancements
• User Defined XML Output Schema

4
Data Collection Specification Tool
Added Complex Data Filters
Improved Output Specification
5
Parametric Data LoadingRequirement

• Loading AMSAA Physical Performance Data Tools
  and documented processes to quickly generate a
  new brigade-sized classified scenario (for
  example SWA 103.2 and SWA 110) from fundamental
  source (AMSAA) data A to include loading a
  classified force and performance database .
  IMPROVE THE PROCESS OF LOADING OF PARAMETRIC DATA
  AND BEHAVIOR DATA.
• For those functionalities which OneSAF represents
  it must be able to load AMSAA APEDS data for a
  new scenario, and replace the data for an
  existing scenario. This would include an entire
  new performance data set as well as selected data
  items. Request, in this FY, documentation for
  this effort. This allows deletion of index item
  135.

6
Data Loading Capabilities Provided

• Document Data Model and identify relationships
  between keys.
• Document data relationship between behaviors,
  physical models, services, etc.
• Upgrade all AMSAA physical models to Standard
  File Format (SFF) 4.0. This includes data as
  well as model changes.

7
Data Relationships Support

• Benefits
• Allows switching between conflicting data sets
  within the same baseline.
• Enables users to quickly switch out data sets
  that override one another.
• Improves process of adding new entities, weapons
  etc. by identifying required data.
• Implementation Detail
• Provide traceability relationships between data
  files and entities, weapons, munitions etc. via
  the data model
• Supports analysis of Parametric data for a given
  scenario

8
Data Model Documentation
9
Data Model Documentation
10
Data Model Documentation
11
Data Documentation Validation
12
Data Documentation Validation
13
Data Documentation Battlebooks
14
Data Documentation Battlebooks
15
Federate with JDLM Requirement

• The Translation Services Component shall
  translate supported digital communications
  between OneSAF and the Battle Command Sustainment
  Support System (BCS3). OneSAF shall federate with
  JDLM in order to stimulate BCS3.

16
Federate with JDLM Capabilities Provided

• OneSAF shall interact with JDLM via the ERF v5
  FOM by supporting Logistics Interactions
• Update OneSAF's HLA mapping to the ERF FOM
• Includes mapping to OTH enumerations to internal
  enumerations, as well as internal supply
  enumerations to what is required by JDLM
• Includes adding equivalent interactions in the
  SORD
• Update OneSAF to use these interactions to
  interface with JDLM

17
OneSAF Entities in JDLM
18
OneSAF JDLM Interaction Support in v3.0

• LogHealthUpdate Full support
• LogisticsAssessment Full support
• LogisticsResupply Full support
• OrgStateInteraction Full support
• LogisticsResupplyRequest Full support
• BattleDamage Full support BattleDamageRepair
• Partial support (automatic delivery of
  med/maintenance is supported. On-command delivery
  is not).
• EntityControl Full support
• MunitionDetonation Partial support (Some OneSAF
  detonations are ineffective against JDLM
  entities)
• LogisticsResupplyControl Not supported (but not
  needed because it is presently a no-op in JDLM)
• UnitInsertion Not supported

19
WAN-Wide Execution(of the SCAMT) Requirement

• OneSAF must have the capability to operate
  distributed over a WAN in a OneSAF distributed
  mode (OneSAF to OneSAF via WAN) as if it was
  operating on a LAN in a OneSAF standalone
  distributed mode. In order accomplish this a
  "Master SCAMT" from a single location needs to be
  able to instantiate multiple OneSAF workstations
  (100 - 200) across multiple sites distributing a
  single scenario to all sites and workstations.

20
WAN-Wide Execution (of the SCAMT) Capabilities
Provided

• Update the System Configuration and Asset
  Management Tool (SCAMT) to support execution and
  control across a WAN to multiple simultaneous
  sites
• Does NOT imply large-scale exercise support of
  the SORD or HLA across a WAN
• SORD WAN is a 4.0 requirement

21
V3.0 SCAMT View
22
V3.0 SCAMT Object Assignment
23
SCAMT WAN Management
24
SCAMT WAN v3.0
HLA Adapter
HLA Adapter
HLA
SORD Cluster
SORD Cluster
HTTP
HLA
HLA
Remote SCAMT
Master SCAMT
HTTP
HLA Adapter
Remote SCAMT
SORD Cluster
25
Usability Enhancements Since 2.1

• PVD
• Support smooth-scrolling
• Allow display CADRG maps
• Improve Unit Symbology display
• Smarter Mouse Selection
• MCT
• Updated Mission Editor for ease of Use
• Provide better defaults to operators for behavior
  inputs
• Added ability to react to behavior input changes
  while task is running
• E.g., Change formation while MoveTactically is
  executing
• Added ability to keep a phase executing to enable
  re-executing completed tasks
• E.g., reuse IssueFireOrder with different target
  locations rather than copy/paste
• Improve unit lay-down interface
• MCT Interactive Route Planning
• Ares
• Launcher Wizard

26
V2.1 MCT
Wasted Space
27
V3.0 MCT
CADRG Support
Enhanced Unit Symbology
Smarter Mouse Selection
Mission Editor Wizard
28
v3.0 Mission Editor

• Added Estimates to Complete for long duration
  tasks

• Added context-sensitive wizard to simplify adding
  phases and tasks

29
MCT Route Planning
Add new Plan option for supported behaviors
03/24/09
30
MCT Route Planning
Select route planning method and plan details of
the route
03/24/09
31
MCT Route Planning
Route to be planned is highlighted.
03/24/09
32
MCT Route Planning
Vertices can be added, adjusted and removed.
Adjusted route
03/24/09
33
MCT Route Planning
Planning updates displayed in Mission Editor
When completed, planned behaviors are displayed
with a watermark.
03/24/09
34
Status Panel Update
Shrink to single line

• V2.1

Overhaul layout and contents so users dont have
to scroll/enlarge to get useful info

• V3.0

35
Force Laydown in the MCT

• Reduced from 15 mouse clicks to create
• a unit or entity to a minimum of 3

36
Ares

• 1. Minimap - Overview of terrain database, used
  for quick navigation.
• 2. In-game Menu - Displays an overview of
  controls used in the tool.
• 3. Create Control Measures - Click to create
  points, lines, or areas.
• 4. Selected Entity or Unit Information - Displays
  name, location, entity/unit icon, and camera
  attach buttons.
• 5. Damage - Displays current entity damage state.

• 6. Basic Load - Displays current entity/unit
  supply types and amount.
• 7. Weapon Control Status - View or change current
  entity/unit weapon control status.
• 8. Tasks - Orderable tasks for current
  entity/unit.
• 9. Current Location - Position on the ground
  directly below the camera.
• 10.Time - Sim time, elapsed sim time, or wall
  clock time.
• 11.Compass - Direction camera is currently
  facing.
• 12.Battlespace - The interactive 3D view of the
  battlespace.

37
OneSAF Launch Wizard
38
Completing Launch Wizard
39
Performance

• Performance comparison of OneSAF v3.0 and
  previous releases on Dell 670 CHP

40
OneSAF 4.0 Requirements
41
RIB 125 Large Scale Scenario Support

• Improve Network Management, Control and
  Installation of OneSAF
• Setup time Less than fifteen person/days to
  setup and install hardware/software
• Execution time A training event focused on a BDE
  would typically consist of a four day exercise
  running twenty-four hours a day (total 96 hrs).
  The simulation must be available and usable the
  entire 96 hours. AAR development time Produce an
  AAR with two hours of ENDEX.
• Provide battlemaster diagnostic tools to
  facilitate ease of setup, use and network/system
  diagnostics.

42
RIB 125 Capabilities Provided

• Harden system to provide battlemaster with more
  and better diagnostics to allow them to better
  predict and react to system problems.
• Support SCAMT restart/alter subcomponents of an
  application (e.g., restart a PVD within the MCT,
  disable comms) instead of requiring the entire
  composition/exercise to restart
• Provide rulesets to assist the SCAMT operator in
  predict problems and automatically offer
  suggested solutions to encountered problems.
• Provide support that assists the battlemaster in
  load-balancing simulation nodes
• Provide site-wide installation/configuration/audit
  ing tools to expedite install on up to 124 CHPs
  and verify correctness of installation.
• Provide user interface and tools to support
  site-wide installation and verification of
  installation, including network performance
  analysis and machine configuration auditing

43
SCAMT Ruleset Mockup
44
SCAMT Ruleset Mockup
03/24/09
45
RIB 300 SORD WAN

• For FY 09 Allow the SORD clients to communicate
  with other SORD clients across a WAN.

46
RIB 300 SORD WAN

• Create a SORD WAN Gateway that supports relaying
  SORD traffic between sites.
• Conceptually similar to how OneSAF interoperates
  via HLA across a WAN today clusters of OneSAF
  nodes will communicate with one another over a
  SORD link
• SORD WAN link will support transmission of
  Physical battlespace objects and interactions

47
SORD WAN v4.0
WAN GW
WAN GW
WAN
SORD Cluster
SORD Cluster
WAN
WAN
DIS Adapter
HLA Adapter
HLA
DIS
WAN GW
HLA Federation
DIS Application
SORD Cluster
48
RIB 142 Parametric Data Loading

• Loading Parametric AMSAA Weapon System
  Performance Data (Apeds0 Process to quickly load
  AMSAA APEDS and or other related input data
  tables (operational data).
• Request in FY09 the following
• a) Provide feedback mechanism that notifies user
  that all data was loaded properly
• b) Provide feedback when data is not found or
  retrieved during runtime
• c) Update weapons system performance data
  (APEDS) table structures defined within OneSAF
  such that they are commensurate with the latest
  AMSAA SFF version (SFF 5.0)

49
RIB 142 Parametric Data Loading

• OneSAF contains 500 data wrappers
• Post OneSAF 3.0, 50 remain that need to be
  stepped up to provide data details