LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 1

C2  AND  SIMULATION  SYSTEMS  WHICH  HAVE  BEEN  IMPLEMENTED                APPROVED  FOR  PUBLIC  RELEASE  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 2

Example  Systems  •  SAFIR  

Ø C2:  SIR,  SICF,  BCIP  5.4  Ø M&S:  APLET,  SWORD,  JSAF  

•  COMELEC  FRA-­‐DEU  Ø C2:  SICF,  FIS-­‐H  Ø M&S:  SWORD,  KORA  

•  MSG  Experimenta<on  Ø C2:  SICF,  ICC,  9LANDBMS,  SITAWARE,  ESRI  COP  Viewer,  JADOCS,  ISIS,  CAPES,  C2PC,  JCHAT,  TALOS  

Ø M&S:  APLET,  JSAF,  OneSAF,  VBS2  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 3

Architectural  Framework  Model  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 4

Specific  Examples  •  ICC  –  JSAF  

Ø  ICC  Ø JSAF  

•  System  overview  for  each  of  the  chosen  systems  •  System  interface  •  Specifics  for  C2Sim,  e.g.  bolt-­‐on  translator,  i/f  to  WS,  message  

sets,  etc  •  Video  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 5

UML  View  

ICC & NIRIS Message Processing and Middleware JSAF Simulation

cmp Components

ICC

tagsVersion = 2.8.2

JSAF

tagsVersion = 2007

NIRIS

tagsVersion = 3.7

ATOReader

Web Serv ice

ReportSubscriber ReportPublisher

OrderListener

JSAFIF

SQLite

tagsVersion = 3.6.18

«shell script»runJFASIF

«shell script»OrderListener

«shell script»publishReports

«shell script»subscribeReports

«shell script»runJSAF

«shell script»publishOrderToWS

«shell script»run_atoreader

«Internal Format»

«C-BML Order»

«C-BML Reports» «C-BML Reports»

«ATO»

«Report Content»

«DB Exchange»

«HLA»

«NFFI»

«C-BML Orders»«Order Content»

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 6

cmp BaseArchitecture

JSAF BML INTERFACE 2.0 ARCHITECTURE

SYSTEM TO BML TASKING

BML TO SYSTEM REPORTING SYSTEM TO BML REPORTING

BML TO SYSTEM TASKING

BML Server

BmlServ erIF

«interface»IBmlServ erWrapper

Bml2SysTaskTranslator

SysTasker

SysReportReceiv er

SysReport2BmlTranslator

:BmlParser

:BmlMsgSender

:BmlMsgReceiv er

:BmlMsgReceiv er

:BmlParser

SysTaskReceiv er

SysTask2BmlTranslator:BmlMsgSender

Bml2SysReportTranslator

SysReportDispatcher

:External Component

:External Component

:External Component

:External Component

 TASKING  

 REPORTING  

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

Air Operations Messaging Capability

Can connect to SBML or CBMS Server

Green components are common to all C-BML

servers

Yellow components are templates for message

translators and wrappers

Red components are system specific

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 7

cmp BaseArchitecture

JSAF BML INTERFACE 2.0 ARCHITECTURE

SYSTEM TO BML TASKING

BML TO SYSTEM REPORTING SYSTEM TO BML REPORTING

BML TO SYSTEM TASKING

BML Server

BmlServ erIF

«interface»IBmlServ erWrapper

Bml2SysTaskTranslator

SysTasker

SysReportReceiv er

SysReport2BmlTranslator

:BmlParser

:BmlMsgSender

:BmlMsgReceiv er

:BmlMsgReceiv er

:BmlParser

SysTaskReceiv er

SysTask2BmlTranslator:BmlMsgSender

Bml2SysReportTranslator

SysReportDispatcher

:External Component

:External Component

:External Component

:External Component

 TASKING  

 REPORTING  

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

Can connect to SBML or CBMS Server

Red components are system specific

TASKING

REPORTING

Yellow components are templates for message

translators and wrappers

Green components are common to all C-BML

servers

Air Operations Messaging Capability

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 8

Specific  Systems  –  ICC  •  ICC  –  NATO  Integrated  Command  and  Control  –  soYware  for  air  operaZons  Ø This  is  an  Air  Campaign  planning  tool  widely  used  in  NATO  Ø  It  can  generate  ACOs,  ATOs  and  ACMREQs  Ø  It  can  be  integrated  with  a  targeZng  tool  (JTS/FAST)  Ø  It  can  be  used  to  display  a  Recognised  Air  Picture  and  Common  

OperaZonal  Picture  from  operaZonal  feeds  Ø  It  can  integrate  with  ISTAR  assets,  e.g.  using  the  CSD  

•  ACO – Airspace Control Order •  ATO – Air Tasking Order •  ACMREQ – Airspace Control Measure Request •  JTS – Joint Targeting System •  FAST – Flexible Advanced C2 Services for Time-Sensitive Targeting •  CSD – Coalition Shared Database

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 9

ICC  –  The  User  Interface  

TaskOrg 2D Map

Mission Editor

Mission Tote & ATO

Resources

ACMs

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 10

ICC  Tasking  (C-­‐BML  Order)  Translator  

C2Sim WS

ICC

ICC DB

ACO & ATO

Parse ACO, ATO

Create & Publish C-BML

Orders

Load ACO, ATO

or

Develop ACO, ATO

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 11

Specific  Systems  –  JSAF  •  JSAF  –  Joint  Semi-­‐Automated  Force  simulaZon  

Ø  This  can  be  modified  for  C2-­‐Sim  because:  §  It  can  be  iniZalised  with  structured  data  §  It  has  behavioural  models  for  Units,  EnZZes  and  Equipment  §  There  is  an  accessible  dynamic  tasking  interface  (not  scripted)  

Ø  ‘Front-­‐end/Back-­‐end’  MVC  distributed  architecture  (not  Server/Client)  Ø  HLA  FOM  already  includes:  

§  Tasking  InteracZons:  –  Tasking  State  –  Tasking  Parameters  –  Background  Parameters  –  Behaviour  Status  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 12

JSAF  –  The  User  Interface  

User Tools

Units

Unit Status

Tasking Matrix

Environment

Overlays, Graphics

Detailed O/P

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 13

JSAF  Tasking  (C-­‐BML  Order)  Translator  

Internal format with permanent

or transient storage

C2Sim WS

Parse C-BML Create & Publish

Overlays and Tactical Graphics

Populate, Schedule and Publish Tasking

Interaction

Subscribe (Filter if

necessary)

JSAF

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 14

Repor<ng  •  SimulaZon  provides  Ground  Truth  •  Reports  to  C2  provide  Perceived  Truth  

Ø Latency,  sampling  frequency,  sensor  errors,  idenZficaZon  errors,  etc  increase  inaccuracy  

•  C-­‐BML  reports:  Ø PosiZons,  Tracks,  Event  locaZons  –  Should  be  displayed  graphically  on  a  map  display  

Ø Other  status,  e.g.    LogisZcs,  Mission  reports,  Acknowledgements  –  Becer  displayed  in  a  wricen  list  

•  A  C2  display,  say  of  a  COP,  is  merely  an  extension  of  the  operator’s  memory  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 15

Repor<ng  (cont)  •  Need  to  get  symbology  correct,  MSDL  is  helpful  here  as  it  can  

include  2525D  symbol  codes  for  units/equipment  •  Mapping  to  operaZonal  message  sets  is  important,  not  all  use  

2525D  codes,  e.g.  OTH-­‐Gold  •  Overloading  C2  systems  and  middleware  with  reports  is  a  

potenZal  difficulty:  Ø May  need  to  throcle,  filter  or  sieve  reports  Ø May  need  to  be  controlled  on  both  or  either  side  of  server  

•  Timestamping  of  reports  is  a  challenge  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 16

Suppor<ng  Approaches  •  DSEEP  Overlay  for  C2Sim  •  SISO  Guide  to  Scenario  Development  •  M&S  and  C2Sim  as  Services  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 17

C2Sim  DSEEP  Overlay  •  Distributed  SimulaZon  Engineering  and  ExecuZon  Process  •  Developed  by  MSG-­‐085  to  help  capture  the  systems  

engineering  processes  required  to  support  a  C2Sim  federaZon,  parZcularly  the  System  Design  Agreements  

•  RecommendaZon  of  MSG-­‐085  is  to  use  a  C2Sim  DSEEP  Overlay  when  developing  complex  federaZons  

•  Lends  itself  very  well  to  Agile  development  methods  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 18

A  C2Sim  DSEEP  Overlay  

C2SIM XML

Schema

Scenario Documentation

C2SIM Federation

Requirements XML Schema Extensions ?

Extensions required

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 19

Guideline  on  Scenario  Development  

•  SISO  Guide  (currently  in  draY,  Aug  2015)  •  C-­‐BML  idenZfied  as  having  a  role  in  formal  

scenario  specificaZon  for  OperaZonal  and  Executable  scenarios  

•  Refinement  processes  may  require  extra  data  definiZons  over  and  above  what  C2Sim  supplies  

Operational Scenario

Conceptual Scenario

Executable Scenario

User M&S Experts Operator

Refine Refine

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 20

M&S  as  a  Service  •  NATO  MSG-­‐136  research  programme  is  invesZgaZng  cloud-­‐based  compuZng  systems  to  support  M&S  as  a  Service  Ø Clients  access  Services,  Plalorms  and  Infrastructure  ‘in  a  cloud  environment’  

•  What  is  require  to  extend  this  to  include  C2Sim  as  a  Service?  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 21

C2Sim  as  a  Service  •  C2Sim  Interoperability  Services  are  needed  to  support:  

Ø  IniZalisaZon,  development,  validaZon,  storing,  merging  and  distribuZon  Ø  Exchange  of  C2Sim  messages  –  push/pull,  pub/sub,  unicast,  mulZcast,  broadcast  

§  Addressing,  RouZng,  Acknowledgement,  Error-­‐handling  

Ø  Logging,  replay  and  analysis  of  C2Sim  messages  Ø  AugmentaZon  of  C2Sim  messages,  e.g.  adding  common  metadata  Ø  ModificaZon  of  C2Sim  messages,  e.g.  Zmestamp  shiYing  Ø  TranslaZon  of  C2Sim  messages,  e.g.  between  different  ‘dialects’  Ø  Exercise  Management  

§  CoordinaZon/monitoring  of  parZcipants  –  which  sites/players  are  joined,  their  capabiliZes,  status,  etc  

§  CoordinaZon/monitoring  of  applicaZons  –  which  applicaZons  are  joined,  etc  §  Security  –  which  data  is  it  possible  to  exchange  and  with  whom?  §  Time  management  §  FederaZon  agreements  

•  Need  to  provide  service  profile  meta-­‐data  to  permit  registraZon,  discovery  and  execuZon  

LS-141 - C2 to Simulation Interoperability (C2SIM) Slide 22

Ques<ons