Project

General

Profile

CIM Issues #749

There are a variety of issues with advanced RegulatingControl.

Added by Herbert Falk almost 3 years ago. Updated 11 months ago.

Status:
Review
Priority:
Normal
Author/Contact Info:
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Yes
Breaking Change Description:
This is breaking
CIM Impacted Groups:
WG13, WG14, WG16
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

There are a variety of issues with RegulatingControl. These include the following and must be addressed in CIM18:

There are multiple issues with the CIM control model:

1. Multiple RegulatingControls on the same controlled point as you describe. One reason to use multiple regulating controls is discrete vs continuous control that require different parameter settings. All RegulatingControls on the same power flow bus must then be enabled.

2. With multiple RegulatingControls they may have different target values (targetValue) which force the receiving tool to make a choice. If different tools make different choices then we have a problem. I have seen this in a few IGMs.

3. The control dead band (targetDeadband) is different for different type of devices which makes it difficult to use the same RegulatingControl, e.g. switched and tapped shunts.

4. A RegulatingControl is connected to the controlled power flow bus (TopologicalNode) via a Terminal. In a node breaker model it is common that the Terminal is at a Switch. It may then happen that the RegulatingControl becomes disconnected from the power flow bus as a consequence of switching while the controlling devices (subclasses of RequlatingCondEq) are still actively controlling. This has been observed to happen in several IGMs.

So the CIM voltage/reactive control model is broken and need a complete revision. For backwards compatibility we must keep the current in parallel with the revised.


Decision

Reviewed on 12-Jun-2023 in Oslo:

The above list of issues contained in the description is a list of existing issues to be addressed by WG13.

#1

Updated by Herbert Falk almost 3 years ago

  • Subject changed from test to There are a variety of issues with RegulatingControl. These include the following and must be addressed in CIM18
  • Start date changed from 06/30/2021 to 12/19/2020
  • ID set to 13_317
  • Author/Contact Info set to Todd Viegut
#2

Updated by Herbert Falk almost 3 years ago

  • Description updated (diff)
  • Proposal descriptions updated (diff)
  • Base Release set to CIM17
  • Solution to be Applied To set to 61970cim18
#3

Updated by Herbert Falk almost 3 years ago

  • Proposed Solution updated (diff)
#4

Updated by Herbert Falk almost 3 years ago

  • CIM Keywords 1, 3 added
#5

Updated by Eric Stephan almost 3 years ago

  • Project changed from WG13 Issues to CIM Joint Issues
  • ID deleted (13_317)
  • Author/Contact Info deleted (Todd Viegut)
  • Base Release deleted (CIM17)
  • Solution to be Applied To deleted (61970cim18)
  • Proposed Solution updated (diff)
  • CIM Keywords deleted (1, 3)
#6

Updated by Eric Stephan almost 3 years ago

  • Breaking Change Description set to This is breaking
  • Breaking Change set to Yes
#7

Updated by Todd Viegut 11 months ago

  • Status changed from New to Open
  • CIM Impacted Groups WG13, WG14, WG16 added
#8

Updated by Todd Viegut 11 months ago

  • Subject changed from There are a variety of issues with RegulatingControl. These include the following and must be addressed in CIM18 to There are a variety of issues with advanced RegulatingControl.
  • Description updated (diff)
  • Status changed from Open to Review
  • Decision updated (diff)
#9

Updated by Todd Viegut 11 months ago

  • Project changed from CIM Joint Issues to WG13 Issues

Also available in: Atom PDF