Project

General

Profile

CIM Issues #5047

Clarifications on equivalents, e.g., EquivalentInjection, ExternalNetworkInjections and the aggregate attribute

Added by Herbert Falk over 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Todd Viegut
Base Release:
CIM17
Solution to be Applied To:
CIM18v03
Solution Version:
CIM18v03
Solution Applied By:
Chavdar Ivanov
Completion Date:
02/11/2023
CIM Keywords:
61970-Equivalents
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):

61970-301

Version:
7.1
Clause:
Equivalents
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
01/14/2020
Origination ID:
13_301
Originally Assigned To:

Description

Per CDV country comments CH_86 for 301 Ed7:

Many TSOs use external network injections which can have distant regulation for modelling distribution network, although it is stated that the class is used for IEC 60909 calculations. It is necessary to specify in which use cases it is suggested to use EquivalentInjection and in which cases ExternalNetworkInjection.


Proposed Solution

Update the descriptions to clarify the usage. Perhaps EquivalentInjections should be used for distribution network equivalenting and not ExternalNetworkInjections, but this needs to be clarified.

Clarifications to be applied in CIM18 because there are multiple uses currently in implementations. Must be discussed with distribution experts. The description should go into the 600 specs as well.

Assign to Energy Model Requirements Subgroup
See additional information:
https://github.com/CIMug-org/WG13InformationModel/issues/5

Update: Feb 2023 by Chavdar
452 and 600 use this constraint
• C:452:EQ:EquivalenInjection:instance
Using EquivalentInjection to model a distribution network equivalent is recommended practice instead of using ExternalNetworkInjection-s.


Decision

14-Jan-2020 Decision to apply the proposed resolution when revving to CIM18


Release Notes

- Added the following clarification to the EquivalentInjection description

Using EquivalentInjection to model a distribution network equivalent is recommended practice instead of using ExternalNetworkInjection-s if it is not necessary that the equivalent contains detailed information representing a short circuit equivalent according to IEC 60909 which is relevant for short circuit studies.

- Added the following clarification to the ExternalNetworkInjection description
It is only used if EquivalentInjection cannot provide the details required by IEC 60909 on short circuit equivalent of an external network.

- Modeified the following statement in the Equipment.aggregate to include ExternalNetworkInjection. The revised version is:
The attribute is not used for EquivalentBranch, EquivalentShunt, EquivalentInjection and ExternalNetworkInjection.

- Deleted the folling constraint from 452
• C:452:EQ:EquivalenInjection:instance
Using EquivalentInjection to model a distribution network equivalent is recommended practice instead of using ExternalNetworkInjection-s.

#1

Updated by Eric Stephan over 3 years ago

  • Subject changed from Per CDV country comments CH_86 for 301 Ed7: Many TSOs use to Per CDV country comments CH_86 for 301 Ed7:Many TSOs use
  • Proposed Solution updated (diff)
  • Decision updated (diff)
#2

Updated by Svein Olsen over 3 years ago

  • Subject changed from Per CDV country comments CH_86 for 301 Ed7:Many TSOs use to Equivalent CDV CH_86 for 301 Ed7
  • Description updated (diff)
  • Standard(s) set to 61970-301
  • Version set to 7.1
  • Clause set to Equivalents
  • Decision updated (diff)
#3

Updated by Eric Stephan about 3 years ago

  • Proposed Solution updated (diff)
  • Decision updated (diff)
  • CIM Keywords 61970-Equivalents added
#4

Updated by Yang Feng over 2 years ago

  • Subject changed from Equivalent CDV CH_86 for 301 Ed7 to Clarifications on equivalents, e.g., EquivalentInjection, ExternalNetworkInjections and the aggregate attribute
#5

Updated by Svein Olsen over 2 years ago

  • Proposed Solution updated (diff)
  • Decision updated (diff)
#6

Updated by Chavdar Ivanov almost 2 years ago

  • Status changed from Open to In Progress
  • Proposed Solution updated (diff)
  • Release Notes updated (diff)
#7

Updated by Chavdar Ivanov almost 2 years ago

  • Solution to be Applied To changed from 61970cim18 to CIM18v03
  • Solution Version set to CIM18v03
  • Solution Applied By set to Chavdar Ivanov
  • Completion Date set to 02/11/2023
  • Release Notes updated (diff)
#8

Updated by Chavdar Ivanov almost 2 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF