Meeting Notes (agreements in red):

1) Feedback from WG13 on ExternalNetwork issue

From the minutes of WG13 call here is what they proposed for the ExternalNetwork issue.

-         Agreed to add the necessary short circuit attributes suggested by ENTSO-E to the EnergySource class and change EnergySource to inherit from RegulatingCondEq.  The description of EnergySource will also be updated to clarify its usage.  The class name will not be changed.

In case more discussion with WG13 is needed interested people should join WG 13 call on Wed.

The name may not be appropriate as ExternalNetwork maybe also energy consumer. It should you be made clear in the description of EnergySource class. 

WG13 to check if EnergySource use for transmission will not confuse the use for distribution. Additional explanations in the class description are necessary
 

2) Boundary set

The 2nd edition of the ENTSO-E CIM profile covers planning and operations exchanges therefore boundary Set should be able to support this. A few issues related to this are necessary to agree

2.1. NameTypeAuthority

Introduce a fixed NameTypeAuthority. In addition the 452 need to state the use of NameTypeAuthority which would mean ENTSO-E need to add

NameTypeAuthority.Name = www.entsoe.eu

 
OK

Issues to WG13:
- to explain the usage of NameTypeAuthority
- to reconsider .description. There is added value to have it back in the IdentifiedObject. .description should be used only for user information; no system should read this to connect the model....

2.2. Add Connectivity Node

Add ConnectivityNode so that the boundary file can be used for operation as well as planning

- ConnectivityNode - in CIM it is placed in a substation
- When using ConnectivityNode the "Xnode" can be placed in a different than electrical middle location
- Special conditions for ConnectivityNode in the Boundary Set - does not contained in VoltageLevel and Substation 

Question to WG13:
- Do we need dummy Substations and VoltageLevels in the Boundary Set? The Standard should cover US case when boundary could be inside a real Substation and the EU case where the the boundary is on a virtual point on an ACLineSegment.    
- If a ConnectivityNode is introduced (in the Boundary) should TopologicalNode refer to it?

2.3. Change x-node for DCLine

Based on the discussion on HVDC we would need to introduce x-node (ConnectivityNode and/or TopologyNodes) on the ACLineSegment connected to the HVDC on both side. The HVDC network cannot be split into two.

This issue should be discussed later on when we have a clear view on the HVDC model

3) Test procedures

Look at test procedures and discuss

The topic will be covered in the next call.