IOP call discussions:

1)      We negotiated a special hotel rate for the IOP week. The registration form is attached. Please pay attention that the deadline for the hotel beeking, if you want to use this hotel is 7 June 2013.

2)      Summary discussion – Operational Hypothesis

The notes from the last 2 calls are in the attached pdfs. The most important issues/agreements are:

·         To-Do WG13: advise if there should be clear separation of the profiles or not. For instance RegulatingControl.enabled is considered for OH profile:

o   Option 1 (preferable): the attribute is only exchanged in OH profile (instances)

o   Option 2: the attribute is present in both EQ profile and OH profile. The instance data from OH profile overrides the EQ instance data.

·         Regulating control: the following attributes are in the OH profile: discrete, enabled, targetDeadband, targetValue, targetVaueUnitMultiplier

·         To do WG13: We need attribute TapChanger.actualPosition to be exchanged in the OH profile

·         tapchanger: the solved position is exchanged in the SV – currently available attributes the solved position is exchanged in the SV – currently available attributes

·         To do WG13: Please advise on TapChanger.regulationStatus. There are 2 possibilities:

o   The attribute stays in the EQ and it is understood as a default value

o   The attribute goes to OH profile- used in case one RegulatingControl is used for multiple devices

·         To do WG13: Please advise on limits. Should they be in OH profile or they can be kept in the EQ profile. IOP call participants recommend to keep the limits in the EQ profile until the whole issue with limits is resolved.

·         ShuntCompensator.actualSections was created. This will be used in OH profile.

·         To do WG13: The description of Switch.open should be revised. Switch.open will used in TP profile as required.

·         Exchange of non-solved model includes EQ+TP+OH; Solved model is EQ+TP+OH+SV

·         To do WG13: plan update of 61970-456. ENTSO-E will use Terminal.connected in TP as required. (now it is optional)

·         LoadResponseCharacteristic should stay in EQ

·         To Do WG13: Load/generation/injection issues. Attributes such as actualP and actualQ are necessary for EnergyConsumer, GeneratingUnit, SynchronousMachine, classes in the Equivalent package, AsynchronousMachine, EnergySource, and maybe some other. There are 2 possibilities to manage this:

o   Apply association with Terminal (ACDCTerminal)

o   Add additional attributes to the existing classes

The naming of the attributes for the OH profile should be consistent, i.e. actualSections, actualP,etc.

Discussion needed on the following: we need to pay attention that for the voltage dependent loads nominal values should be assumed in the OH profile. The SV will bring the solution (the voltage dependent value).