Issues that should be discussed:

-          Issues Giatgen on dynamics

-          Issues from Christoph – validation tools

-          EMS test models

-          Other test models

-          Regulating control

-          General issues to solve

o   HVDC

o   Operational hypothesis

o   Project extension

o   Specification operational (for detailed model), short circuit

§  EQ – differences expressed in the header (different EQ profiles)

·         1. Core EQ

·         2. specific classes/attributes for switch based model exchange

·         3. Short circuit classes attributes

How many combinations we have? (1+2; 1+3; 1+2+3)

Do we define 3 different rdfs and have 3 different profile URI in the header?

§  TP

§  Operational hypothesis (can this be part of the SV instance file? How we can allow exchange on not solved case?)

§  SV

§  DI

§  GE

§  DY

Outcome of the discussion:

-          Regulating control: Lars-Ola explained the changes. These changes are minimal. There are use cases which are not covered. Christoph will start a discussion on what is missing. Then we will see what additional classes could be added to make the model clearer

-          Validation tools. Jun will update CIMSpy, but he needs fixed profile. We will try to fix EQ first

-          EQ “split”: One good option is to leave EQ complete but allow multiple profiles in the header. This will be suggested to WG13. Chavdar will present to WG13 how ENTSO-E stereotyped the classes attributes to Operation, ShortCircuit

-          EA versioning will be explored. This will allow vendors to track profile or UML changes in a better way.

Issues we need to cover in the next call:

-          Discuss the summary of Regulating Control issues that Christoph will prepare

-          Look at the different issues we have now and try to prioritise so that we can fix deadlines by when we have the issues resolved.

-          Discuss on test models