search

AMSP-04 / NETN-ETR

NATO Education and Training Network (NETN) Entity Tasking and Reporting (ETR) Module
Other
2 stars 0 forks source link

NETN-ETR FOM module #52

Closed ngcheeki closed 11 months ago

ngcheeki commented 3 years ago

Hi,

Our current virtual simulation project is mandated by our customer to use NETN-FOM and one of the features in the project is made used of existing interaction classes in NETN-FOM to do C2 tasking.

While assessing the usage of the Entity Tasking and reporting interaction classes, we came crossed ETR-Task interaction class. We had some on the ETR_Task base classes

The parameters of the ETR_Task interaction class are defined as follows:

ETR_Task TaskId: TransactionId ;Required. Uniqie identifier for the task. Taskee: UUID; Required. Reference to the entity that will execute the task. Tasker: Callsign; Optional. Callsign of the commander of the task. If missing, the commander is undefined. StartWhen:Datetime18; Required. Time when the task execution should start. Use the value 00000000000000.000 to indicate that the time is undefined. Why: HLAunicodeString; Optional. A text describing the reason for this task. TaskMode: TaskModeEnum8; Required. Determines the task mode. CommunicationNetworkIds: ArrayOfText64 ;

  1. Why is the Taskee and Tasker instance identifier datatype is different? The Taskee is using UUID and the Tasker is using callsign datatype? Furthermore, why is the Tasker parameter an optional parameter instead of a required field?
  2. The Callsign for an simulated entity in an scenario may not be unique. Hence, I would proposed the Tasker datatype as UUID even though it is not readable.

With Regards,

Chee KIong

lofstrandbjorn commented 3 years ago

Hello Chee,

This is a good question. The exact resoning behind this design is based on work by TNO in the Netherlands and FFI in Norway who developed the original mode to connect a C2 system with VR-Forces. I agree that originator of the task, if provided, should be a unique reference and UUID would probably be the best datatype. In the recently released NETN-ETR module (released 26 March 2021 and superceeds the LLBML in NETN-FOM v3.0) the same datatypes are used so this was obviously not addressed the recent work conduced to update the modules.

Can I ask you to submit an issue in GitHub on the NETN-ETR FOM module repository and then we will address it in the current work (NATO MSG-191) that will deliver NETN-FOM v4.0 in a couple of years. FYI. NETN-FOM v4.0 will be based on RPR-FOM v3.0 and HLA4 concepts which will improve and simplify the class structures of all NETN FOM modules.

Best Regards /Björn

lofstrandbjorn commented 1 year ago

Tasker datatype changed to UUID. Tasker parameter remains Optional allowing tasking from scenario control with no explicit commanding unit/entity.