Closed LennartOlsson closed 4 years ago
Is the (default) approach (?):
Unit
=> NETN-Aggregate aggregate unitEquipmentItem
=> NETN-Physical entityWe also need to revisit how VesselUnit
is modelled in NETN-ORG. With the above approach, a vessel is an EquipmentItem.
And what about Radios or Transmitters?
By default defines a Unit a NETN_Aggregate, but in some cases defines it a NETN-Physical object class, depending on the value at the attribute Unit.EntityType.
An EquipmentItem defines always a NETN-Physical object class if the EntityType value is provided in the Model attribute (datatype is a fixed record with fields EntityType and Resolution). The Model attribute should be Required.
All these attributes on EquipmentItem is defined in MSDL.
Maybe should the MSDL definition of EquipmentItemType and the object class EquipmentItem have a slot for the MILSTD-2525D symbol specification.
Object class EquipmentItem added in FOM module.
There is a need to model Equipment in the ORG FOM module.
Proposal: