- issue 225 - no change needed it is OK
- issue 228 - no need to be in the EQ profile. no change
- issue 230 - related to the SSH profile. See issue 300 implemented in profile v2.4.6
- issue 237 - it is OK - no change needed
- issue 238 - angle should be required. Changed in v 2.4.6. of the profile
- issue 242 - IOP call - 20 May discussed the issue and identified that the rule is not clearly defined in the standards i.e. it was more recommendation than a standard. 456 uses solution 2 as presented above. Therefore the ConnectivityNode should be abstract class in the TP so that we have what we need in the TP instance file according to the 456. The change is implemented in the v2.4.6. of the profile.
- issue 243 - ltcFlag - as built situation; regulationStatus - actual regulation status; WG13 will discus if regulationStatus can be renamed to controlEnabled; need attribute on the RegulatingCondEq. WG13 call on 22 May - agrred to change the regulationStatus to controlEnabled also added attribute in the RegulatingCondEq.Changes are implemented in profile v2.4.6 - 25 May
- issue 253 - here is no need to have the association in the EQ profile
- issue 254 -  The only need to have Terminal.phases if to the PetersonCoil model. A comment will be inserted to specify this; corrected in v2.4.6
- issue 258 - IOP call 20 May - it is OK like it is. No need of a note as the descriptions in CIM16 are clearer, i.e. it is excluded that the ratedU is usually the same as neutral voltage.
- issue 259 - IOP call - 20 May - targetDeadband should be optional; primary used when discrete is true
- issue 261 -  IOP call - 20 May - continuous mode can be applied to any device; so note is not needed