Project

General

Profile

CIM Issues #3994

Clean up of ShuntCompensator nomS, nomU, minU, and maxU Wh

Added by Herbert Falk over 2 years ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Kendall Demaree
Base Release:
61970cim14v15
Solution to be Applied To:
61970cim14v15
Solution Version:
CIM16
Solution Applied By:
KDD
Completion Date:
02/18/2011
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
CIM16
Origination Date:
02/15/2011
Origination ID:
13_37
Originally Assigned To:

Description

Clean up of ShuntCompensator nomS, nomU, minU, and maxU Why do we model the nomS, and why the nomU. These are not needed. Also the minU and maxU are rather odd attributes and might be either deleted or documented more clearly as limits of safe operation. The minU is confusing because these could be confused with voltage at which to operate or switch the cap. The nomU is the only one of these attributes in the 452 profile, but I don't see why it is needed for powerflow, because we don't have nomQ in the profile. Also documenation of normalSections is inappropriately tied to other attribues and confuses the normal and nominal, which are different.

Proposed Solution

Delete nomU, nomQ, minU, maxU. Clarify normalSections is just the normal value of sections switched on. Remove the cross attribute linkages in meaning which are cumbersome.

Decision

(2011-0216) Delete reactivePerSection,minU,maxU, nomQ and keep nomU in UML. OperationalLimits and regulator model are a replacement for these. Agree reactivePerSection can be dropped from 452, since bPerSection is same thing. Fix doc of nomU as just "rated voltage". Fix doc on integer attributes to not reference deleted nomQ.

No data to display

Also available in: Atom PDF