Here a short summary of the call

 1) Issue with the External network

o   An attribute (acceleration time constant for frequency behaviour) is missing in the CIM – should be fixed.

o   Possible solutions:

§  For the test the value could be add manually (to represent infinite; constant frequency )

§  Preferable option?: A solution to add a machine (big enough) to reach the same results; no short circuit data for this machine

2)  Losses at the breakers issue

o   The calculation should be done with ideal breakers – no losses 

3)         Nominal values for the machines – P and Q calculated; no losses at breakers

 Agreements and action items:

- Emile will propose a solution (adding an attribute related to the EternalNetwork; probably ExternalNetworkDynamics should be created) to update the dynamics profile. We will agree on the solution and then a revision of the dynamics profile will be released
- in order not to block the work vendors will adapt the model after the import, if this is required to be done (not all vendors need to do such action) 

4) Agreements on finalization on the Load flow model:

-          The model exported by Power Factory is close to be final. Therefore Christoph and Richart will do a minor updates of the model and post it by 28 Jan

-          by 31 Jan: All vendors should check if the load flow is the same. If this is the case then this model will be used as a base case

-          3 Feb: xls template for Case 1, Case 2 and Case 3 should be completed by each vendor and posted in the CIMug site. Then Chavdar & Wim will merge the results and prepare the chart. After this action we will start testing individual models. (one model will be taken out of the test case and replaced by another one)

5) Agreements on the Dynamics part

-          Use typical values for controllers that are in the profile. If there are no values we need to agree on a set. Vendors should signal if there is a problem with a the typical values set. If a better set is found the values in the dynamics profile could be updated.
-          PI controller in the ExcSEXS: Chavdar will double check the PI block: Kc/Tc…. It looks like that it is coming form PSLF. The general objective is in the standard models to use elementary blocks that are well defined (refer to the user defined set of elementary blocks discussed in the EPRI Project CIM for Dynamics). If some blocks are not well defined we need to agree on a modification which is understandable by all.

o   For the purpose of the test we will use Tc=0 and Kc=1

It is practical that once the load flow case is finalized only the DY file will be exchanged.

Calls will be organized every 2nd Monday at 15h CET (i.e. before the ENTSO-E IOP calls which are planned to start from 10 Feb)

Call participants: