C2 Adapter User

1
C2 AdapterUsers ConferenceOneSAF 3.0
2
Major new C2 Adapter Functionality since OneSAF
2.1

• Now supports both Linux and Windows
• 32 bit only (CMP restriction)
• Must upgrade CMP to version 5.1.0.0 (included in
  3.0 baseline)
• Tighter integration into the core OneSAF
  architecture
• The Adapter now runs like any other system
  composition
• Two compositions available
• c2core Runs just the Adapter
• c2mct Runs the Adapter and an MCT
• Built in network distribution and management
• Elimination of need for Java Jini to handle
  client discovery and network data transfers
• Ability to start / stop the Adapter from SCAMT

3
New C2 Adapter Functionality, cont

• Automated the configuration of multicast group
  listeners
• Users used to have to examine the LDIF and then
  edit a configuration file
• Now these are setup automatically for each
  execution based on the URNs being used by
  simulated entities
• Mapper file management and referencing was
  improved
• A configuration file ties mappers to specific
  Adapter configurations
• This will lessen errors due to cases where
  multiple programs have mappers that are similar,
  but different and the wrong one was instanced

4
New C2 Adapter Functionality, cont

• New generic parser/encoder framework
• Compartmentalizes the different parsers/encoders
  to enable adding or omitting a specific
  parser/encoder very easily without rippling
  throughout the code base
• Currently have one each for the CMP, WARSIM and
  JC3IEDM components
• Allows for specific parser/encoders to be
  deliberately loaded or not loaded as part of the
  C2 Adapter installation.
• Will now allow the C2 Adapter to be provided to
  International users
• Was not possible before because of tight coupling
  with CMP, which OneSAF is not able to deliver
  Internationally
• They can add new parsers/encoders that enable
  communication with their Countrys battle command
  systems.

5
New C2 Adapter Functionality, cont

• New JC3IEDM Web Service
• SIMCI (Simulation to C4I interoperability) funded
  project combined project with 2 other teams
• JC3IEDM RI (Reference Implementation) is a J2EE
  Pub / Sub service oriented architecture (SOA)
  application which allows for interoperability
  with other systems in a JC3IEDM compliant manner
• Demonstrated the functionality by interfacing
  OneSAF with
• Battle Management Language (BML) Received a BML
  order and used it to initiate a OneSAF behavior
  execution
• PM Battle Commands Data Mediation Services (DMS)
  application Translated the JC3IEDM data and
  published it into the ABCS PASS server
• Additional hardening of the application being
  worked in 09 application available for use via
  OneSAF 3.0 and follow-on releases

JC3IEDM Joint Consultation Command and Control
Information Exchange Data Model
6
New C2 Adapter Functionality, cont

• Message addressing data (URNs, IP Addresses,
  etc.) can now come from multiple sources
• LDIF
• MSDL
• New Mappers
• VMF P11 outbound K02.01 checkfire
• JVMF R5 6017 outbound K05.13 Threat Warning

7
New C2 Adapter GUI
Improved user interface that provides much better
information on status, health and message flow
Address book(s) being used are displayed
Bound URNs shows Real and Simulated C2 Devices in
the scenario file
C2 Adapter is configured for OneSAF using
ABCS_SWB1
8
New C2 Adapter GUI
Simulation Tactical IP addresses displayed
How many messages have been processed?
Number of Devices Bound, Live , Simulated
Worker threads configured available
How many messages in the Main Queue as well as
Final Queue
9
New C2 Adapter GUI
Communications running UDP, TCP, Multicast
FDL enabled to this AMDWS role
CMP Validation of messages turned on
10
Message Statistics Window
Messages generated by the applicable URN in the
simulation
Message number and how many
11
Message Flow Window
IP Address to send to (unicast IP C2 or
multicast IP SA)
Target message type, example R5-VMF K05.01
Producer of the message (OneSAF or Tactical)
Timestamp of the message
If CMP Validation turned on, validity status
12
Preview Panel Window
Allows preview of the CMP formatted message at
runtime
13
Additional GUI Functionality

• Enumerations window
• shows current enum files with ability to add /
  delete or modify at runtime
• Properties window
• shows current C4I property settings and allows
  for some to be changed at runtime
• Mapper window
• shows current mapper files with ability to add /
  delete or modify at runtime
• Red SA configuration Allows the user to select
  the recipient of K04.01 Observation Reports
  (usually the S3 ASAS at BN/BDE)
• This is done in the Adapter rather than the
  scenario file because ALL K04.01 for a specific
  Bn should be sent to a specific ASAS

14
(No Transcript)
15
Re-Architected Adapter Components

• Split apart inbound outbound tasks into
• Protocol / addressing
• Translating
• This allowed other services such as SECore to use
  the Adapter for translation even though the
  transport of the information is via the DIS
  interoperability service (and not via one of the
  C2 Adapter transport mechanisms).

16
Re-Architected Adapter Components

• Mappers and Mapper Generator Tool
• Prior to 3.0, mapper code not directly reusable
  unless the source and target data structures
  identical (only KA/KE reusable
• Now, mappers split apart so that an existing to
  or from mapping is directly reusable when
  building mappers via the Mapper Generator Tool
• For Example If an existing OneSAF -gt JVMF 6017
  K04.01 mapper exists, you could create a WARSIM
  -gt JVMF 6017 K04.01 easily, reusing the existing
  JVMF xml mappings

17
C2 Adapter Code Cleanup

• Unused code (legacy) removed
• Redundant code from multiple sources was combined
  into common routines to satisfy both
  implementations
• One example is the FDL functionality
• WARSIM and OneSAF each had their own FDL
  interfaces with slightly different functionality
• Now one routine to satisfy both sets of
  interfaces
• Dead Reckoning code
• Dead Reckoning code in the Adapter multiple times
  to satisfy different requirements for FDL (WARSIM
  OneSAF) as well as WARSIMs SA Generator
  application
• Now one Dead Reckoning service satisfying all
  interface needs

18
Software Block II Certification

• The C2 Adapter and OneSAF went through the
  rigorous Software Block II certification process
  with the CTSF and DIL
• All the Software Block II threads passed the
  assessment successfully

19
C4I Devices used at 3.0 Assessment

• The 3.0 Assessment events were conducted
  interfacing to ABCS Software Block I devices.
• A full regression test of the ABCS Software Block
  II interface was also conducted internal to
  OneSAF with the 3.0 baseline.
• The C4I devices interfaced to included
• FBCB2
• AFATDS
• MCS Workstation
• MCS Gateway
• ASAS-L
• AMDWS

20
OneSAF Version 3.0 C4I Supported Messages JVMF
Versions R5 (SWBI) and 6017 (SWBII)
K01.01 Freetext K04.02 Land Route Report K04.03
Obstacle Report K04.09 Bridge Report K05.01
Location Report K05.02 NBC1 K05.05 NBC4 K05.06
NBC5 K05.14 Situation Report
K01.01 Freetext K02.01 Check Fire K02.04 Call For
Fire K02.06 Observer Mission Update K02.16
EOM K02.22 Subsequent Adjust K05.01 Location
Report
K05.19 Entity Data Message (Bridge, Obstacle,
Nbc1, Supply point, Observation, Threat
Warning) K05.01 Location Report
MCS-WS
AFATDS (JVMF 6017)
F3 Track Report
AMDWS
K05.17 Overlay K05.18 MOPP Message
K02.01 Check Fire K02.04 Call For Fire K02.06
Observer Mission Update K02.12 Command to
Fire K02.14 Message to Observer K02.22 Subsequent
Adjust
K01.01 Freetext Message K04.02 Land Route
Report K05.01 Location Report K05.13 Threat
Warning K05.14 Situation Report K05.19 Entity
Data Message (Bridge, Obstacle, Supply Point,
Observation, NBC1, Threat Warning) K07.03
Logistics Report K07.04 Personnel Status K07.07
Medical Unit Sitrep K07.09 Supply Point
Status K07.12 Task Management K07.01 Medical
Evacuation Request
K01.50 Freetext K02.01 Check Fire K02.04 Call For
Fire K02.06 Observer Mission Update K02.09 Target
Data (MFR) K02.11 Ammunition Inventory K02.14
Message to Observer K02.16 EOM K02.22 Subsequent
Adjust K02.51 Sitrep (for Location updates)
AFATDS
FBCB2
AFATDS (P11)
K04.03 Obstacle Report R5 only K04.09 Bridge
Report R5 only K05.13 Threat Warning K05.17
Overlay Message K05.18 MOPP Message K05.19 Entity
Data Message (obstacle, target data, bridge,
observation, threat warning K07.06 CTIL/BRIL
K02.01 Check Fire K02.04 Call For Fire K02.06
Observer Mission Update K02.09 Target Data
(MFR) K02.12 On-Call Fire Command K02.14 Message
to Observer K02.16 End of Mission K02.15 Fire
Support Coordination Measures K02.22 Subsequent
Adjust
21
Post 3.0 Planned Enhancements

• Add PASS / DDS support to the Adapter
• SECore 45A tasks
• Add AFAPD parser / encoder
• Add multiple AFAPD mappers
• Add / update existing JVMF mappers for SECore
  (CCTT, AVCATT) these will be for both Software
  Block I (JVMF R5) and Software Block II (JVMF
  6017)
• Add ability to ingest a FBCB2 / BFT database load
  to use for C2 Adapter address book
• Add ability to handle multiple message versions
  concurrently in one Adapter instance
• Support new communications architecture within
  OneSAF for ack processing
• JCR / TSG
• Initial work SE prototyping as risk reduction