CIM Issues #6459
302, 457 issue with “triple” association of WindPlantControlCommIEC.CommunicationIEC
Description
in regards to CommunicationIEC class and the “triple” association of WindPlantControlCommIEC.CommunicationIEC.
The WindPlantControlCommIEC class could be modified to use three separate associations, one for each communication module type (windPlantReferences, windPlantMeasurements and powerDeviceReferences) instead of the one multi-purpose association (WindPlantControlCommIEC.CommunicationIEC).
In that case the CommunicationIEC.kind parameter would not even be required because each association would determine the purpose of the communication object.
For example, use:
• WindPlantControlCommIEC.WindPlantReferences,
• WindPlantControlCommIEC.WindPlantMeasurements and
• WindPlantControlCommIEC.PowerDeviceReferences
Instead of the three WindPlantControlCommIEC.CommunicationIEC associations.
The current solution is atypical, because a triple-association is seldom used in CIM, and also clumsy to use, while still requiring a dedicated parameter to distinguish between communication modules that are basically of the same type.
Proposed Solution
• WindPlantControlCommIEC.WindPlantReference,
• WindPlantControlCommIEC.WindPlantMeasurement and
• WindPlantControlCommIEC.PowerDeviceReference
Instead of the three WindPlantControlCommIEC.CommunicationIEC associations.
Decision
Apply the changes as proposed in order to optimise the modelling
Release Notes
The following changes are applied to 302 and 457:
- Added the following associations between WindPlantControlCommIEC and CommunicationIEC
• WindPlantControlCommIEC.WindPlantReference,
• WindPlantControlCommIEC.WindPlantMeasurement and
• WindPlantControlCommIEC.PowerDeviceReference
- delete WindPlantControlCommIEC.CommunicationIEC association
- delete CommunicationModuleKind
- delete CommunicationIEC.kind