Architecture and Integration Update Derrick Franceschini A

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

• Data Collection
• Native Format Data Loading
• Scalability Improvements

3
Data Collection Improvements in v2.0

• Able to collect much wider breadth of data in the
  system
• Behavior data now collectable
• Able to specify and collect topics of interest,
  rather than individual attributes
• Provides more convenient descriptive approach to
  users
• Topics include Mobility, Battle Damage Assessment
• Requires significantly less developer effort to
  support
• Less code
• More data collection coverage
• Performance of data collection significantly
  improved

4
Native Data Format Loadingin v2.0

• Provided mechanism for end-users to more easily
  update data
• Supports what-if studies
• Supports classified data loads
• Removed a translation step into XML
• Models now read XML, Excel, csv, .dat files for
  data

5
Scalability Improvements in v2.0

• Added a new class of entities and units
  Ultra-Low Resource (ULR)
• Support a single sensor, single weapon, the
  ability to move
• Added the Scalable Comms Server application
• Stimulates the C4I Adapter with appropriate
  messages on behalf of Low Resource (LR) and ULR
  entities
• Significantly improved performance of MCT,
  Environment calls, and SimEngine
• Enabled the multi-threaded scheduler
• Added a new Pub/Sub protocol to reduce network
  traffic flowing to Management Control Tool
  (MCTs)
• Demonstrated a 30,000 entity exercise in OneSAF
  as part of the v2.0 assessment

6
v3.0 Enhancements

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

7
Data Collection Capabilities Provided for v3.0

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

8
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.

9
Data Loading Capabilities Provided

• Document Data Model and identify relationships
  between keys.
• Support composition based approach for data
  overrides and component swapping.
• Provide enhancements to the Data Management Tool
  (DMT) tool to display dependencies and provide
  guidance on the addition of new values for keys.
• Documents 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.

10
Data Relationships Support

• Notify users on what data files need to be
  updated when adding new entities, weapons etc.
• 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
• Update the DMT to trace through the set of
  affected data files.

11
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.

12
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 models and BCFs to use these interactions
  to interface with JDLM

13
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 substantiate multiple OneSAF workstations
  (100 - 200) across multiple sites distributing a
  single scenario to all sites and workstations.

14
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
• Support scalability assessment and improvements
  to allow Simulation Objective Runtime Database
  (SORD) communications between up to 300 OneSAF
  Workstations and simulation cores.
• Does NOT imply large-scale exercise support of
  the SORD or HLA across a WAN

15
Usability Enhancements

• PVD
• Support smooth-scrolling
• Allow display CADRG maps
• Improve Unit Symbology display
• MCT
• Provide better defaults to operators for behavior
  inputs
• Improve unit lay-down interface
• Provide an overview window
• SCAMT
• Add support for controlling properties
• Overhaul node status information
• Provide for centralized scenario and simulation
  control