CIM Issues #6458
302, 457, Issues with different classes modelling the same behaviour WindGridMeasForProtection and WindGridMeasForControl
Description
I have encountered a strange design choice in the wind dynamics profile.
The WindGridMeasForProtection and WindGridMeasForControl classes are basically the same – they have the same parameters, model the same dynamics module but can be used for different purposes, namely for protection or for control.
The question is, why do we have two different classes then?
Could we have one CIM class type (for example WindGridMeasurement) and associate two object instances of the same class to the wind turbine dynamics model using different associations?
If we would have one single class type (WindGridMeasurement) we could then use for example:
• the WindTurbineType3or4IEC2. WindGridMeasForProtection association to assign a generic measurement to be used for protection and
• the WindTurbineType3or4IEC2.WindGridMeasForControl association to assign a generic measurement to be used for control
Proposed Solution
Use a single class and rely on the associations
Decision
Apply the change to have optimal modelling
Release Notes
The following changes are applied in 302 and 457
- rename class WindGridMeasForProtection to WindGridMeasurement and adapt the description
- move old associations from class WindGridMeasForControl to WindGridMeasurement and rename association role names
- delete class WindGridMeasForControl