Project

General

Profile

CIM Issues #5731

MktGeneratingUnit association use for GeneratingUnit

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

Status:
Closed
Priority:
Normal
Author/Contact Info:
Lars/Becky
Base Release:
iec61970cim16v21iec61968cim12v07iec62325cim03v01
Solution to be Applied To:
Solution Version:
N/A
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
None
Requestor:
Standard(s):
Version:
Clause:
MktGeneratingUnit
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
09/10/2013
Origination ID:
16_0015
Originally Assigned To:

Description

MktGeneratingUnit class is used to provide for an association to GeneratingUnit from package 61970.

Proposed Solution

Suggestion is to remove this subclass, and add an association directly from RegisteredGenerator to the GeneratingUnit.

Decision

Requirement existed within the CMM Guide during the merge of package IEC62325. WG16 complied with this requirement by updating the IEC62325 package throughout to introduce the subclassing approach. These changes affected more than 30 classes which manage over 100 associations. The effort was not small. XSDs have been developed using MktGeneratingUnit class and changes would introduce tremendous cost to all utilities.

Moving forward, as new model requirements are identified, new associations to other IEC package classes will not be contained within Mkt subclasses. Existing associations contained within the Mkt subclasses in 301 Edition 1 will stay as is. The priority of the WG16 modeling team is to focus on model support for profiles.

#1

Updated by Becky Iverson almost 2 years ago

  • Status changed from New to Closed
  • Base Release changed from iec61970cim16v21 iec61968cim12v07 iec62325cim03v01 to iec61970cim16v21iec61968cim12v07iec62325cim03v01
  • Decision updated (diff)

Also available in: Atom PDF