For Action:

1.       7 June 2013: Please complete the table - list of participants. The purpose is to see how we could cover all issues with minimal effort. It is not necessary that everyone test everything. We should have 2-3 vendors per item. Please pay attention that these items are not concrete test procedures, but only areas of the profile.

2.       7 June 2013: Please confirm the scope for the test models for Dynamics and HVDC (see below)

The next call will be on 17 June – see the planning below

1)      Issues

Issue No354 is now closed. It is OK like this. CoordinateSystem and Location inherit from IdentifiedObject

2)      Test models – the models below are in addition to regular test models SCADA/EMS type, or bus branch type discussed in previous calls

a.       Dynamics

                                                               i.      ENTSO-E 16 (11 July 2011)

1.       BE part: ExcAC4A, GovSteam0, GovSteam1, PssIEEE2B,

2.       NL part: ExcAC1A, ExcST1A, GovHydro1, GovHydro2, PssIEEE2B,

The IOP will use the following standard models: ExcIEEEAC1A, ExcIEEEAC4A, ExcIEEEST1, GovSteam0, GovSteam1, GovHydro1, GovHydro2, PssIEEE2B. In addition standard model for synchronous machines

                                                Variant Dyn1: all represented as standard models

            Variant Dyn2: ExcIEEEST1 represented as proprietary model

b.      HVDC

                                                               i.      ENTSO-E 16

1.       Variant DC1: One of the tie-lines should be HVDC CSC

2.       Variant DC2: one internal line should be HVDC VSC

3.       Variant DC3 (optional): combination of variant 1 and variant 2.

Status planning

ü  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