1)      Review overall planning – 15 min

ü  27 May: IOP call to discuss issues and TP profile part of the HVDC including Boundary

·         29 May: Chavdar to summarize all issues for WG13. Some of these issues may be resolved in the WG13 call on 29 May. The rest will be discussed in the WG13 meeting 4-7 June

·         3 June: Chavdar to produce a new version of the profile which fixes resolved issues during IOP call 27 May and WG13 call on 29 May; we should get stabilized on attributes to be included in the SSH

·         3 June: IOP call to discuss test procedure and profile document; we can discuss small issues as well; freeze the content of the test dynamics models; agree on which model will have HVDC; we need to agree how we exchange information on test models (we need a common place for models and models description)  

·         3 June: Chavdar to send xls table to identify: who is coming; who is testing what (we may need to divide the work so that we have all main areas covered);

·         4-7 June: WG13 meeting to resolve some issues or give directions; should not leave issues after 7 June if we want to test in the IOP

·         10 June: no IOP call

·         10 June: Chavdar produces a profile, if we need update

·         12 June: CIMug meeting – no WG13 call

·         17 June: IOP call – 2h: discussion on status of the test models and issues with validation; see how we test specific issues like project support

·         24 June: IOP call – 1h: freeze test procedures and profile document for the IOP

·         1 July: IOP call – discussion on test models – areas of enhancement/improvement

·         8 July: IOP week

2)      What should be included in the TP profile for HVDC; as well as for Boundary profiles; “Xnodes” for HVDC – 1h

Classes/attributes for the TP profile

·         DCTerminal.polarity

·         DCNode

·         DCTopologicalNode

·          

DCTopologicalIsland – this goes to SV

Boundary profile

-          No need to change the boundary profile. The HVDC MAS will refer to ConnectivityNode or to TopologicalNode in the Boundary model

-          HVDC can be exchanged as a MAS – separate instance files (EQ, TP, SSH, SV); normally if one TSO is responsible for the HVDC the HVDC model is included in the TSO MAS (EQ, TP, SSH, SV)

-          In case of more than one HVDC interconnections (including interconnections with different TSOs) the TSO can include them in a single HVDC MAS or in its MAS.

3)      Clean as many issues as we can from the xls table – 45 min

We discussed a lot of issues from the xls. I will make necessary changes in the profile and also make a clearer list for WG13.