A Practical Example of the Integration of Simulations, Battle - - PowerPoint PPT Presentation

▶
a practical example of the integration of simulations
SMART_READER_LITE
LIVE PREVIEW

A Practical Example of the Integration of Simulations, Battle - - PowerPoint PPT Presentation

Dec 25, 2023 163 likes •470 views

A Practical Example of the Integration of Simulations, Battle Command, and Modern Technology International European Multi Conference And Simulation Interoperability Workshop 2009 Dr. J. Mark Pullen Lori Topor C4I Center Northrop Grumman IT

slide-1
SLIDE 1

09E-SIW-025 1

International European Multi Conference And Simulation Interoperability Workshop 2009

A Practical Example of the Integration of Simulations, Battle Command, and Modern Technology

  • Dr. J. Mark Pullen

C4I Center George Mason University Fairfax, VA 22030 mpullen@netlab.gmu.edu Ted Troccola PM Battle Command Building 2525

  • Ft. Monmouth, NJ 07703

ted.troccola@us.army.mil Lori Topor Northrop Grumman IT 3045 Technology Parkway Orlando, FL 32826 ltopor@ideorlando.org

  • Dr. Stan Levine

Simulation to C4I Interoperability (SIMCI) OIPT StanLevine13@gmail.com

slide-2
SLIDE 2

09E-SIW-025 2

Outline

  • SIMCI Background
  • Combined Project Description

– Battle Command Design & Implementation – M&S Design & Implementation – Battle Management Design & Implementation

  • Reference Implementation
  • Operational Concept
  • Demonstration
  • Summary
slide-3
SLIDE 3

09E-SIW-025 3

M&S Battle Command

Interoperability of Current and Future Systems

M&S BC Shared Solutions Processes Common Data Reusable Components Architectures Common Standards

Vision: Achieve full interoperability between Modeling and Simulation

(M&S) systems and Battle Command (BC) systems as an integral part of the acquisition process, from capabilities determination through fielding and sustainment.

Mission: Provide policy, process, organizational, and technical

recommendations to Army Leadership that will improve M&S and BC systems interoperability.

Simulation-to-C4I Interoperability Overarching IPT (SIMCI OIPT)

slide-4
SLIDE 4

09E-SIW-025

Co-Chairs

PEO STRI PEO C3T CIO/G6 G3 DAMO-LB ASA(ALT) G8 TRADOC ARCIC

Core Members

CERDEC ATEC SMDC JFCOM JWFC PEO GCS TCM Live Signal CDID CAC CDID TCM Geospatial TCM LVC/NSC TRAC PM FCS (BCT) (BC) PM FCS (BCT) (MSO) PM FCS (BCT) (TNG IPT) CGSC DLDC TCM Virtual 3CE TCM N&S PEO IEW&S PEO EIS PEO Aviation PEO Soldier OTC G3 DAMO-MS

SIMCI OIPT Membership

(as of 18 Feb 09)

Army Staff Material Developers Combat Developers Cross Domain SIMCI Management

Council of Architects

  • Mr. Steve Whitson
  • Dr. Michael Hieb
  • Dr. Stan Levine
  • Mr. Chris Black
  • Mr. Dick Brown
  • Mr. John Chapman

Program Coordinator

  • Mr. Barry Drabczyk

Program Analyst

Secretariat

COL Karen Saunders LTC Pat Connors COL David Moore

  • Mr. Bob Carnevale
  • Ms. Laura Ziegler
  • Mr. Jim Blalock

COL John Lucynski

  • Mr. James Lee

COL Andy Riley

  • Mr. Jack Ogren
  • Mr. Tom Jordan
  • Ms. Monica

Farah-Stapleton MAJ Mike Blandford

  • Mr. Bill Krondak
  • Mr. Rick Ramsey
  • Mr. Wayne Koenig

MAJ Brian Vogt

  • Mr. John Rutt
  • Mr. Steve Davis
  • Ms. Cindy Harrison
  • Mr. Peter Haniak
  • Mr. Jeff Forbes
  • Mr. Matt Arnold
  • Mr. Don Timian
  • Ms. Alesya

Paschal

  • Mr. Joe During
  • Mr. Phil

Hallenbeck LTC Favio Lopez TBD

  • Mr. Eric Goodman

LTC Mike Palaza

  • Mr. Brian

Gregg

  • Mr. Bill Righter

TCM BC

LTC Mike Swehla

TEC

  • Mr. David

Lashlee

4

slide-5
SLIDE 5

09E-SIW-025 5

SIMCI BC – M&S Interoperability Web Service Project

  • Provide standard Net-Centric Enterprise

Services (NCES) compatible web-service interface between M&S and BC which can be re- used readily.

  • Provide standard secure JC3IEDM compliant

mediation capability for use by BC and M&S systems.

  • Provide standard NCES compatible web service

for Battle Management Language support for automated Tasking (part of Operations Order) and Reports.

slide-6
SLIDE 6

09E-SIW-025 6 C2 Adapter

Capes/JTCW

DMS

ABCS DDS

SIMCI BC – M&S Interoperability Web Service Project

Tactical Devices

US‐JC3IEDM XML and BML

US‐JC3IEDM To DDS Mapper

M&S BC

UBC FCS JLCCTC Coalition Systems

OneSAF

US‐JC3IEDM To OneSAF Mapper

slide-7
SLIDE 7

09E-SIW-025 7

ABCS DDS DMS Architecture

slide-8
SLIDE 8

09E-SIW-025 8

PASS Schema to US-JC3IEDM Data Mapping

PASS SCHEMA US-JC3IEDM DATA POS-RPT Friendly/Neutral organizations ENEMY-SIT Hostile/Unknown organizations, features and facilities OBS-POS Uncorrelated hostile/unknown

  • rganizations

GEO-REF Uncorrelated unknown facilities and features GRAPHICS Friendly/Neutral/Hostile non-

  • rganizations

TASK-ORG Friendly Organization Structures ORG-STAT Organization Status IND-WARN Same or similar mapping as ENEMY-SIT CTFP Same or similar mapping as ENEMY-SIT SIG-ACT Same or similar mapping as ENEMY-SIT

slide-9
SLIDE 9

09E-SIW-025 9

M&S Community

US-JC3IEDM XML

C4I Adapter

C2 Adapter Architecture

slide-10
SLIDE 10

09E-SIW-025 10

C2 Adapter Architecture

US-JC3IEDM XML

slide-11
SLIDE 11

09E-SIW-025 11

Mapper Generator

slide-12
SLIDE 12

09E-SIW-025 12

Joint Battle Management Language

slide-13
SLIDE 13

09E-SIW-025 13

MSG-048 I/ITSEC Demonstration Configuration

ISIS

C2LG

NORTaC- C2IS

ISIS translator FFI C2IEDM Gateway C-BML XML file plug-in Data prefill (OOB, etc.)

ICC

ICC translator

JSAF SCIPIO

C-BML WEB SERVICES JC3IEDM DATABASE

Orders & Reports Reports

C-BML XML file plug-in

Orders Orders & Reports Orders

POLLUX+

C2LG

Land C2IS Land C2IS Air C2IS

ISIS

C2LG

NORTaC- C2IS

ISIS translator FFI C2IEDM Gateway C-BML XML file plug-in Data prefill (OOB, etc.) Data prefill (OOB, etc.)

ICC

ICC translator

JSAF SCIPIO

C-BML WEB SERVICES JC3IEDM DATABASE

Orders & Reports Reports

C-BML XML file plug-in

Orders Orders & Reports Orders

POLLUX+

C2LG

Land C2IS Land C2IS Air C2IS

slide-14
SLIDE 14

09E-SIW-025 14

Scripted BML Architecture

slide-15
SLIDE 15

09E-SIW-025

Scripted BML WS Design

  • Basic operations: push and pull

– Currently, servers for SQL and RI databases – Scripts implement BML Orders and Reports

  • Script defines implementation of Business Objects

(constituents of the higher-level BML grammar)

  • ver the JC3IEDM data model

– BO is an XML subtree rooted at a defined node in the XML file – can invoke other BO

  • Interpreter uses two files plus WS input

– Mapping file contains script – BML schema file provides necessary context

slide-16
SLIDE 16

09E-SIW-025 16

Scripted Interpreter Advantages

  • A way to implement composite transactions

where:

– Validation requires only understanding of the object and JC3IEDM (but not Java) – Changes to the mapping are simple to implement – New business objects are easy to define and implement

  • Student did six of them in two weeks while learning
  • Scripting language provides a highly concise

definition of BML mapping

– SISO C-BML should use it for that

slide-17
SLIDE 17

09E-SIW-025 17

Supports distributed BML repository, replicated across instances of RI

Reference Implementation

slide-18
SLIDE 18

09E-SIW-025 18

Operational Concept

Workstations Servers

M&S Environment ABCS Environment

US‐JC3IEDM

Data Mediation Service

BCCS Server

C2 Adapter

DDS Army, Joint, & Coalition Systems FCS JLCCTC Coalition Systems BML Ifc

US‐JC3IEDM

BML or XML JC3IEDM Ifc

US-JC3IEDM XML

BML or XML

BML Ifc

JC3IEDM Ifc

Simulations & C2 Systems OneSAF ABCS

slide-19
SLIDE 19

09E-SIW-025 19

2008 SIMCI CP DEMO

C2-Sim Interoperation via JC3IEDM with BML

Data Mediation Service

BCCS Server MCT PVD

OneSAF

XML/BML WS Combined Project RI C2 Adapter Combined Project RI

DDS

MCS 1 JBC2S FBCB2 NVIG CAPES/JTCW BML WS XML WS JVMF HLA VIDEO

Level-I FCS Fusion Surrogate

Combined Project RI PASS PASS BN G3 Plans BDE G3 PLT 1a 1b 2 3b 3c 3a 4 4b 4a DIV CO + 4c 5 6 BN G3 3

slide-20
SLIDE 20

09E-SIW-025 20

Conclusion

  • This project will result in standard interfaces for BC to M&S

interoperability that will support both current capabilities and future capabilities. – It will support more efficient and effective transition to NCES and Army JC3IEDM compliance. – It has been estimated that this project will provide for significant cost savings as a result of becoming a standard M&S to BC interface standard.

  • The modifications/extensions to the C4I Adapter capabilities

(including the RI) will be included in C4I Adapter employment managed by PM OneSAF.

  • The DMS (including the RI) will be fielded by PM BC as part
  • f the BCCS within the ABCS system of systems.
  • The tools and reusable components (including the RI) will

be provided along with the JC3IEDM SDK for standard common Army use (M&S and BC).

slide-21
SLIDE 21

09E-SIW-025 21

Summary

  • The project will transition many products:
  • The modifications/extensions to the C2 Adapter

capabilities (including the BML interface) will be included in C2 Adapter employment managed by PM OneSAF.

  • The DMS (including the RI and BML interface)

will be included as part of the BCCS within the ABCS system of systems.

  • The tools and reusable components (including

the RI) will be provided along with the US- JC3IEDM SDK for standard common Army use.

  • Planning for integrated CM and processes for

the maintenance of products and documentation will be included in standard Army processes.

slide-22
SLIDE 22

09E-SIW-025 22

BACKUPS

slide-23
SLIDE 23

09E-SIW-025 23

JBML mapping to JC3IEDM Schema field <What>

action-task action-task-id (FK) category-code activity-code reference reference-id content-category- code action-reference- association action-id (FK) reference-id (FK) action-reference- association-index category-code action action-id category- code Where content- category-code is set to ‘ORDER’ (‘ORDER’) The category-code value will be set to ‘ACTION-TASK’ (‘ACTTA’) Used as the <OrderId> The category-code value will be set to ‘Is directed by’ (‘ISDSCR’) category-code is set to ‘ORDER’ (‘ORD’) Schema Reference: <xsd:complexType name="CommandType"> <xsd:sequence> <xsd:element name="What" type="GroundBMLWhatType"/> … <What>

1 2

Previous Mechanism: IDEF1x Mapping

  • Diagram not machine readable but highly structured
  • In its place we have created an XML coded script
slide-24
SLIDE 24

09E-SIW-025 24

Example BML to JC3IEDM Script Fragment

<!-- Name: PositionStatusReportPush--> <BusinessObjectTransaction> <transactionName>PositionStatusReportPush</transactionName> <tableQuery> <!-- 0 GET act name_txt = OrderID --> <mappingSequence>0</mappingSequence> <JC3IEDMTable>act</JC3IEDMTable> <queryAction>GET</queryAction> <resultName>act_id</resultName> <columnReference> <columnName>NAME_TXT</columnName> <businessObjectTag levelsUp="2"> Header/ReferenceOrderID </businessObjectTag> </columnReference> </tableQuery> <tableQuery> <!-- 1 GET act_ref_assoc name_txt = OrderID --> <mappingSequence>1</mappingSequence> <JC3IEDMTable>act_ref_assoc</JC3IEDMTable> <queryAction>GET</queryAction> <resultName>ref_id</resultName> <columnReference> <columnName>act_id</columnName> <workingVariable>act_id</workingVariable> </columnReference> </tableQuery>

…

slide-25
SLIDE 25

09E-SIW-025 25

Concept for Scripted DCS

  • Two levels of schemas

– Pure Business Object schema: one level of tags define parameters – Complex schema using Business Objects: XML tree branches define instances of Business Object

  • This requires that the script include the sequence
  • f XML nodes in BML schema that will invoke it

– Specification requires both schema and script

  • We have implemented two set of services

– JBMLv1.5 BML Web Service as used in MSG-048 November 2007 Demo at I/ITSEC (08S-SIW-082) – Integrated BML Reports for MSG-048 2008 experiment – Performance 4 times faster than hard-coded service

slide-26
SLIDE 26

09E-SIW-025 26

Invoking XML for PostitionStatusReportPush (Header)

<BMLREPORT …> <Header> <MessageID>10000</MessageID> <ReporterWho> <Equipment >AMBUL</Equipment> </ReporterWho> <AddresseeWho> <Equipment>ARMORD</Equipment> </AddresseeWho> <ReferenceOrderID>12345</ReferenceOrderID> <Precedence>ROUTINE</Precedence> <Classification>2</Classification> <Sendtime>101201ZSEP2008</Sendtime> </Header>

slide-27
SLIDE 27

09E-SIW-025 27

Invoking XML for PostitionStatusReportPush (Report)

<Report> <CategoryOfReport>StatusReport</CategoryOfReport> <TypeOfReport>PositionStatusReport</TypeOfReport> <StatusReport BusinessObject = "PositionStatusReportPush"> <PositionStatusReport> <Hostility>FRIEND</Hostility> <Executer> <Taskee><Equipment>AMPH</Equipment></Taskee> </Executer> <AtWhere> <WhereLabel>Objective_Alpha</WhereLabel> <WhereCategory>OBJECTIVEAREA</WhereCategory> <WhereClass>POINT</WhereClass> <Latitude>39.9476491008418</Latitude> <Longitude>48.9353472265578</Longitude> <ElevationAGL>0</ElevationAGL> <WhereQualifier/> </AtWhere> <When> <WhenTime> <WhenQualifier>AT</WhenQualifier> <DateTime>101201ZSEP2008</DateTime> </WhenTime> </When> <ReportID>802</ReportID> <Credibility> <Source>AOBSR</Source> <Reliability>A</Reliability> <Certainty>IND</Certainty> </Credibility> </PositionStatusReport> </StatusReport> </Report>

slide-28
SLIDE 28

09E-SIW-025 28

DEMO Steps

  • 0 – All systems are Pre-initialized with the Task

Organization – DIV – BDE - BN – CO – UAV Plt

  • 1 - OneSAF sends starting location and materiel

information for all Friendly Units

  • A - Location information will be received by the FBCB2

(via JVMF)

  • B - Location and Material information will be received by

MCS via the RIs, JC3IEDM, DMS, and DDS

  • 2 – CAPES/JTCW tasks UAV Recon PLT to go to and

recon area of operation through OneSAF RI to OneSAF

  • 3 – OneSAF moves 1 UAV to area of operation
  • A - OneSAF sends UAV PLT LDR position reports to

FBCB2 by JVMF

  • B - OneSAF sends UAV position reports to MCS

through the RIs, JC3IEDM, DMS, and DDS

  • C - OneSAF notifies NVIG of UAV movement through

HLA and NVIG simulates the video feeds on the JBC2S

slide-29
SLIDE 29

09E-SIW-025 29

DEMO Steps

  • 4 – OneSAF creates 12 UAV sensor reports (4 UAVs

sensing 3 enemy units each)

  • A – OneSAF sends the reports to the FBCB2 (via JVMF)

and through the RI to the Level-1 FCS Fusion Surrogate RI via XML WS

  • B – Level-1 FCS Fusion Surrogate correlates the 12

reports into 3 enemy units

  • C – Level-1 FCS Fusion Surrogate sends the

correlated report through the DMS RI, JC3IEDM, and DDS to the MCS

  • 5 - MCS sends CTRL Measures via DDS through the

DMS, JC3IEDM, RIs, to OneSAF

  • 6 – The CAPES/JTCW orders OneSAF unit (1

Company) to move and attack (the order includes the route to take and when to start)