1. Profile status v2.4.2

- dynamics profile updated – it will be exported after the call

·         From now on the dynamics package/profile is considered frozen for the IOP

·         If additional changes are possible in the dynamics package, but these should not affect the IOP

·         If any changes in the dynamics profile which affects the IOP they should be agreed in IOP call

-          Other part of the profile – some issues are pending on WG13 or other discussions. It should be finalized within agreed schedule

2. Test Procedures

-          We need to update it to reflect changes in the profile.

o   Any changes to test issues we identified in IOP 2012. Some of these are

§  Operational hypothesis

§  Export DACF file from SCADA/EMS and import in regional model (it challenges the link between SCADA/EMS model and bus-branch model)

§  Importing load flow model by SCADA/EMS vendors should be checked (Lars-Ola will revisit the test procedure)

o   Test exchange of HVDC  - HVDC subset for the test procedures

§  Data model to be tested

§  Comparison of load flow is an additional option – depends on how many vendors implement load flow for HVDC.

o   Dynamics testing – revision is necessary to include

§  Tests to confirm interconnections with standard models and proprietary models (one standard model exchanged as proprietary)

§  Validate a few standard models and confirm a process how other standard models will be validated after the dynamics profile is approved by ENTSO-E: ExcAC1A, ExcST1A, ExcAC4A, GovSteam0, GovSteam1, GovHydro1, GovHydro2, PssIEEE2B (the list to be checked against the ENTSO-E 16 nodes model).

§  Validate the approach of exchange of a proprietary model

3. Test models

-          ENTSO-E 16 Node (are we OK with the update from CIM15 -> CIM16?) – remote regulation issue; we need to improve diagrams and have load flow results

o   EQ, TP, SV

o   EU_EQ, EU_TP

o   Dynamic (DY) – Chuck has intention to work on this

o   Diagram Layout (DI) – needs update (most probably no change since last year)

o   Geographical (GE)? – may be easier to debug if we have it

-          IEEE118 Node

o   EQ, TP, SV

o   EU_EQ, EU_TP – could be generated

o   Dynamic (DY) – not available and difficult to add

o   No short circuit

o   HVDC – depends on the type of the model

o   Diagram Layout (DI) – the diagram is now bus branch; multiple diagrams could be included;

o   Geographical (GE) - available

o   Can we create a node/breaker model extension so that we can test EMS with this? (Alan has some model there. ConnectivityNodes and switches added)

-          ABB40Bus – Lars-Ola will update; HVDC may be added to it.

-          FGH

-          Mikronika

-          ShortCircuitModel

-          Reliability Test System (1979 and 1996)

We need test models that cover:

-          ENTSO-E planning process

-          Models with special attention of all types of PST

-          ENTSO-E DACF process

-          Core exchange: EQ, TP, SV

-          Incremental (EQ + DIFF (as minimum))

-          Short-Circuit

-          Dynamic

-          DC

o   Embedded HVDC model (1 area with HVDC line in the area)

o   Boundary HVDC model (HVDC line between 2 areas; issue with where the Xnode is)

-          Diagram Layout

-          Geographical

-          Operation to planning model

-          High coverage of profiles (EQ, TP, SV, DY, DC, DI, DE)

-          High coverage of classes (e.g. LinearShuntCompensator and NonLinearShuntCompensator)

-          High coverage of functionality (e.g. retain switch, regulation etc)

-          Performance (volume, load flow calculation etc)

 

Participants: