AMSP-04 / NETN-ORG

NATO Education and Training Network (NETN) Organisation (ORG) Module
Other
1 stars 1 forks source link

From the relations it is not always possible to obtain an unique hostility for a unit. #33

Closed hendersonhc closed 10 months ago

hendersonhc commented 4 years ago

For simulations (like VR-Forces) each unit should be set to a certain hostility status:, for example Friendly, Hostile or Neutral. This can not be obtained from the relations since there each force has a hostility relation to another force.

Suppose we have 3 forces: Force1, Force2 and Force3 and that Force1 is Friendly against Force2 and Force1 is Hostile against Force3.
When we have to present a unit that belongs to Force1 how should it be presented (Friendly or Hostile). Since both are found in the relations it is not possible to decide which one to use.

lofstrandbjorn commented 4 years ago

A RPR based simulation using the ForceIdentifier attribute to determine not only force but also affiliation makes an implicit assumption that there is a standard pre-defined Force (normally BLUE FORCE/Own Force) and all other forces are listed as either neutral, hostile or friendly using a numbering scheme of the force identifier. This is not a very good design (I do not know if it will change in RPR FOM v3). From the relations in NETN-ORG you can only determine hostility if you compare to a specificed force.

lofstrandbjorn commented 4 years ago

Please provide suggestions for updating the FOM module or documenting its use to solve the issue.

lofstrandbjorn commented 4 years ago

Agree on reference force in federation agreements. Update documentation.

lofstrandbjorn commented 4 years ago

Suggest rethink the Force object class to capture federation wide scenario information including Reference Force and all the Force Relations. Consider including other attributes for data in the MSDL/Scenario.

lofstrandbjorn commented 1 year ago

In restructuring the NETN-ORG, a ForceIdetifier attribute is added to the Organization object class. Setting a "correct" ForceIdentifier with respect to a "Reference Force/Organization" is left to the federate publishing the organization structure. Physical and Aggregate entities published in the federation should use the ForceIdentifier defined for the Organization to which they belong. This information can either be obtained by subscribing to NETN-ORG data or through some other initialization means (configuration files etc.) and depend on federation agreements.