Second Lieutenant CHATELET – Second Lieutenant HELLIO – Jan. 5 2011 1 United States Military Academy of West Point, New York USA. Interoperability among Federated Simulated Multinational Operations
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Second Lieutenant CHATELET – Second Lieutenant HELLIO – Jan. 5 2011
1
United States Military Academy of West Point, New York USA.
Interoperability among Federated Simulated
Multinational Operations
I/ Project presentation.
II/ Model-Based Data Engineering methodology.
III/ Command and Control Interface.
IV/ Results: improving interoperability within NATO.
V/ Application.
CONTENTS
2
Project presentation - goals
3
PoM DSE
C_BML VMASC
StCyr Client
Other NATO Client
T H E S I S
S I M U L T O R
M A T R E X
4
U.S. Amy ambush (source: U.S. Army Field Manual (Tactics)[1]). French Armée de Terre ambush (source: French Military Academy of Saint Cyr Field Manual (Tactics)[2]).
US/French Ambush Doctrine
Project presentation - tools Tools :
a) Coalition Battle Management Language: Command and Control Data Model based on the JC3IEDM NATO standard.
b) Primitives of Meaning: Simulation Data Model which allows to describe every basic task that a Unit or a SingleEntity has to execute on the battlefield.
c) Federated simulation: OneSAF combat simulator using the High Level Architecture Matrex FOM extended by the PoM.
5
6
Primitives of Meaning
New Interactions
• C2CommandScript • C2UnitCommandScript • C2CommandSignal • C2UnitCommandSignal • C2SendHumanSignal • C2SendUnitHumanSignal
• Move • Patrol • Halt • Set Weapons Control
Status • Orient • Fire • Set Posture • Observe
• Set Weapon State • Mount • Dismount • Search Entity • Search Route • Search Room • Clear Room • Send Signal
MATREX C2 Primitives
• Order of execution within script • Trigger Types
– As soon as possible – After completion of previous action – After delay – Upon signal
Action Trigger
• C2UnitCommandScript – Primitive Action Trigger Parameters – Move ASAP Speed = “Quick”; Formation = “Wedge” – Orient After Complete Orientation = 0 (North) – Fire Signal ANVIL 1 % of Magazine = 50; EA includes BLDG 100 – Orient After Complete Orientation = 45 degrees (East of BLDG 100) – Orient Signal HAMMER Orientation = 90 (Building 101) – Fire Signal ANVIL 2 % of Magazine = 50, EA includes BLDG 101
• C2CommandSignal “ANVIL 1” • C2CommandSignal “HAMMER” • C2CommandSignal “ANVIL 2”
Support By Fire
Project presentation - methodology Model-Based Data Engineering :
a) Data Administration: source documentation, format, data’s validity, fidelity and credibility.
b) Data Management: identify and describe data elements, map equivalent information expressions to each others.
c) Data Alignment: the data to be exchanged exists in both systems or can be derived from the available data or we need to had extensions.
d) Data Transformation: technical process of aggregating and disaggregating the systems’ entities to match information exchange requirements
11
MBDE - Data Admimistration.
12
CBML PoM
MBDE - Data Management.
13
<Task> <What> <Ac7onTask xsi:type="Ac7onTask"> <OID>00000000000000001033</OID> <NameText>Support by fire</NameText> <Ac7vityCode>ENGAGE</Ac7vityCode> </Ac7onTask> </What>
<When> <StartWhen> <Rela7veTime> <ObjectAc7onRef xsi:type="Ac7onTaskRef">
<OID>00000000000000001041</OID> <!-‐-‐ 1st FR PLT has reached its assault posi7on -‐-‐>
</ObjectAc7onRef> <Ac7onTemporalAssocia7on>
<OID>00000000000000000000</OID> <CategoryCode>STRENL</CategoryCode>
</Ac7onTemporalAssocia7on> </Rela7veTime> </StartWhen> </When>
-‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐
</Task>
<UnitCommand>
<UnitAc7ons> <SetWeaponsControlStatus> <Ac7onTrigger> <TriggerType>ASAP</TriggerType> <OrderOfExecu7on>1</OrderOfExecu7on> </Ac7onTrigger> <WeaponsControlStatus>Free</WeaponsControlStatus> </SetWeaponsControlStatus> </UnitAc7ons>
<UnitAc7ons> <Fire> <Ac7onTrigger> <TriggerType>Comple7onOfPrevious</TriggerType> <OrderOfExecu7on>2</OrderOfExecu7on> </Ac7onTrigger> <AreaGraphic>Oscar 1</AreaGraphic> <PercentOfMagazine>25.0</PercentOfMagazine> </Fire> </UnitAc7ons>
-‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐ -‐
</UnitCommand>
CBML PoM
⇒ CBML is much more user-friendly for operational level missions (regiments, brigades and higher) than tactical level (companies,
platoons and lower).
Heterogeneous and Structural conflicts.
MBDE - Data Management.
Data mis-alignment between C2DM and SDM => 2 solutions :
• Unpack high level mission terms.
=> it requires to make assumptions about what basic tasks each mission implies. We should add a new entity in CBML which is "DOCTRINE“.
• add extensions to CBML.
=> we would have to take every PoM concept and to check if, in CBML, an equivalent value from the entity ACTION-TASK and its attributes exists.
14
Conceptual mapping.
Attribute mapping.
Fire what-‐ac7on-‐task-‐ac7vity-‐code value ENGAGE Ac7onTrigger when-‐ac7on-‐task-‐start-‐qualifier-‐code or
when-‐ac7on-‐start-‐temporal-‐associa7on-‐category-‐code
EngagementArea affected-‐who-‐objet-‐item-‐id PercentOfMagazine extension needed as a_ribute
15
MBDE - Data Management
According to the solution we chose, we started building a list of the correspondence between CBML and PoM → Awareness of the PoM concepts which are missing in CBML. Descriptive conflicts.
Semantic conflicts.
16
Mount extension added as a new what-‐ac7on-‐task-‐ac7vity-‐code value: MOUNT Dismount extension added as a new what-‐ac7on-‐task-‐ac7vity-‐code value: DISMNT Halt extension added as a new what-‐ac7on-‐task-‐ac7vity-‐code value: HALT Orient extension added as a new what-‐ac7on-‐task-‐ac7vity-‐code value: ORIEN SendSignal extension added as a new what-‐ac7on-‐task-‐ac7vity-‐code value: SNDSIG Signal extension added as a new a_ribute of the JC3IEDM/CBML en7ty
ACTION-‐RESOURCE-‐EMPLOYMENT: ac7on-‐resource-‐employment-‐signal-‐text MessageTransmissionType extension added as a new a_ribute of the JC3IEDM/CBML en7ty
ACTION-‐RESOURCE-‐EMPLOYMENT: ac7on-‐resource-‐employment-‐message-‐transmission-‐type
Fire PercentOfMagazine extension added as a new a_ribute of the JC3IEDM/CBML en7ty
ACTION-‐RESOURCE-‐EMPLOYMENT: ac7on-‐resource-‐employment-‐percent-‐of-‐magazine
Move and Patrol
MoveSpeed extension added as a new a_ribute of the JC3IEDM/CBML en7ty ACTION-‐RESOURCE-‐EMPLOYMENT: ac7on-‐resource-‐employment-‐speed-‐code
Forma7on extension added as a new a_ribute of the JC3IEDM/CBML en7ty ACTION-‐RESOURCE-‐EMPLOYMENT: ac7on-‐resource-‐employment-‐forma7on-‐code
SetPosture
Posture extension added as a new a_ribute of the JC3IEDM/CBML en7ty ORGANISATION-‐STATUS: organisa7on-‐status-‐posture-‐code
SetICWeaponState or SetWeaponState
ICWeaponState or WeaponState extension added as a new a_ribute of the JC3IEDM/CBML en7ty ORGANISATION-‐STATUS: organisa7on-‐status-‐weapon-‐state
SingleEn7tyCommand exten7on added as a new taskee-‐who-‐organisa7on-‐ref type: PersonRef
MBDE - Data Alignment.
Command and Control Interface Purpose of the interface: • Objective: Create CBML-compliant XML files that use our extensions.
• Programmed in Java with Netbeans 9.6.1
17
Command and Control Interface
18
UML class diagram
Results: improving interoperability within NATO.
19
JE VEUX Appliquer des feux sur l’ENI situé au niveau de EA Oscar 1 à compter du 02 octobre 2010 à 06h30 pour au mieux détruire au pire chasser l’ENI qui l’occupe.
POUR CELA :
Me déplacer en ambiance sûreté jusqu’à l’intersec7on en 32.3695 º N 84.8068 º O, baptême terrain Hotel 1, puis en ambiance discré7on jusqu’à la corne de bois en 32.3696 º N 84.8045 º O, baptême terrain Oscar 1, pour y installer un disposi7f de surveillance et d’appui sur EA Oscar 1 pour 06h00.
En liaison permanente avec le 2nd PLT, appliquer des feux sur l’ENI situé au niveau de EA Oscar 1 à compter du 02 octobre 2010 à 06h30.
Me renseigner et renseigner la compagnie et le 2nd PLT sur l’ac7vité ENI dans et autour EA Oscar 1.
EMD Me_re en place un disposi7f de surveillance face au Nord et à l’Est à par7r des limites Ouest de EA Oscar 1 et à compter du 02 octobre 2010 06h35.
T1
T2
T3
20
Results: French OPORD for U.S. Army platoon.
21
French OPORD
Results: Translation into a CBML-compliant file
22
Results: From CBML to the Primitives of Meaning
French OPORD
23
Results: Displayed in OneSAF
French OPORD
RT OSCAR 1 OSCAR 1
French OPORD
24
Continued Development
• Extended C-BML Schema
• Replaced POM layer with direct C-BML translation to MATREX
• Develop simulation independent Andriod user interface that exchanges C-BML messages • Situation report • SALUTE report • Primitives of Meaning Order
• Implement in OneSAF via MATREX architecture
25
What Next
• Focused on dismounted ground domain • Continued user interface development
• Call for fire • Clearance of fires • Request MEDEVAC
• Continue to extend C-BML for tactical action – robotic forces • Integrate with C2 Core effort
Related Documents
