1.) Issue on

RegulatingControl.targetValue and mode

OperationalLimit.value

proposal: Should be moved out of the EQ set

ENTSO-E IOP Call – 20 Feb 2012:  It is OK for IOP participants
ENTSO-E IOP/WG13 Call – 27 Feb 2012:
WG13 comment: WG13 will further work on this issue for the call on 29 Feb. This information should be exchanged in the SV; default values will be still in EQ.  What about RegulatingControl.targetRange?

2) ExternalNetwork issue

Why is this defined as a subtype of RegulatingCondEq? – ENTSO-E IOP Call – 20 Feb 2012:  Because connection to a external grid that can have slack node (in most of the cases the ExternalNetwork is the slack); ExternalNetwork stands on its own – not part of reduction of a portion of a grid.

Was originally modeled as EquivalentInjection.  Why was this changed? ENTSO-E IOP Call – 20 Feb 2012:  EquivalentInjection is coming from grid reduction; this is not the same for ExternalNetwork

ENTSO-E IOP/WG13 Call – 27 Feb 2012:
ExternalNetwork produces/consumes active and reactive power. It could be compared to syncronous machine.
EquivalentInjection can result from grid reduction or not. The name "ExternalNetwork" is widely used.
WG13 will look for additional input from WG14 (Kurt will contact Tanja) and some more members of WG13. It seems the class is needed. Better name and description may be necessary.

Attribute voltageFactor is of type PU.  Why was this necessary?  Could this be changed to PerCent?  This needs to be clearly explained in the description. ENTSO-E IOP Call – 20 Feb 2012:  We need to check the description and IEC 60909
ENTSO-E IOP/WG13 Call – 27 Feb 2012: further check needed

Agreed to add the attributes from ExternalNetwork to EquivalentInjection. ENTSO-E IOP Call – 20 Feb 2012:  IOP participants insist to have the ExternalNetwork as a separate class as initially suggested

Do we need to add Short Circuit specific attributes for minP and maxP?  We assume that an extra set is not necessary. ENTSO-E IOP Call – 20 Feb 2012:  – If we have separate classes we don’t have this issue

3) Additional attributes to AsynchronousMachine

Attribute nominalFrequency needs more description. ENTSO-E IOP Call – 20 Feb 2012:  Nameplate data gives info if the machine is 50/60 Hz

ENTSO-E IOP/WG13 Call – 27 Feb 2012: Kurt will update
Attribute nominalSpeed needs more description. ENTSO-E IOP Call – 20 Feb 2012:  Nameplate data. Depends on the slip and number of pole pairs.
ENTSO-E IOP/WG13 Call – 27 Feb 2012: Kurt will update

Is “ratedP” the best name for mechanical power?  Would ratedMechanicalPower be better? ENTSO-E IOP Call – 20 Feb 2012:  OK  Should this be ActivePower? ENTSO-E IOP Call – 20 Feb 2012:  OK - Watts
ENTSO-E IOP/WG13 Call – 27 Feb 2012: Kurt will update

Description of “reversible” needs to be expanded. ENTSO-E IOP Call – 20 Feb 2012:  To be checked in IEC60909
ENTSO-E IOP/WG13 Call – 27 Feb 2012:

The description of the AsynchronousMachine.reversible should be: Indicates for converter drive motors if the power flow can be reversible. Used for short circuit data exchange according to IEC 60909


Other issues:
- WG13 is putting a high priority on the HVDC modelling. Lars-Ola si working on the next version of the model. It is expected that the model will be integrated in the official UML of WG13 before the end of March. The model will most probably have an impact on EQ, TP and SV.

- Kurt is working on the next version of the UML i.e. CIM16v05. He already added most of ENTSO-E Extensions. He is waiting the remaining open issues to be finalized and UML for CIM16v05 will be issued.

Participants: