Project

General

Profile

CIM Issues #5946

Association Terminal.TopologicalNode

Added by Chavdar Ivanov over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
High
Author/Contact Info:
Base Release:
17v40
Solution to be Applied To:
CIM18v04
Solution Version:
CIM18v04
Solution Applied By:
Chavdar Ivanov
Completion Date:
02/19/2023
CIM Keywords:
Breaking Change:
Yes
Breaking Change Description:
Removing required association in TP profile and making other associations in TP and EQ required
CIM Impacted Groups:
WG13
Requestor:
Standard(s):

61970-456

Version:
CIM18v04
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
08/09/2022
Origination ID:
Originally Assigned To:
Svein Olsen (9/19/2022)

Description

As CIM17 standards moved in the direction that ConnectivityNode is required for building the connectivity, the association Terminal.TopologicalNode is not necessary in the TP profile and it shall be removed. Keeping this association and expecially with cardinality 1..* at the side of Terminal requires that additional constraints are defined.

Proposed Solution

Remove the association Terminal.TopologicalNode in Topology (TP) profile.

Updated proposed solution.
Necessary changes are:
in TP
- remove association Terminal.TopologicalNode
- remove association DCBaseTerminal.DCTopologicalNode (note the association DCNode to DCTopologicalNode is already required association)

in EQ
- change cardinality of association Terminal.ConnectivityNode from 0..1 to 1. Note that we are reinforcing this by constrain now when we say we need to have all models build with ConnectivityNodes. There is no point to have Terminal without connection to ConnectivityNode in the EQ profile
- change the cardinality of the DCBaseTerminal.DCNode from 0..1 to 1. This will match the way we are doing for AC part. It will also patch the pattern we have with required associations ConnectivityNode.TopologicalNode and DCNode.DCToplologicalNode

By applying these changes we can remove a couple of constraints in EQ and TP as the cardinalities will drive the modelling style.

Decision

No disagreements for making the change (9/19/2022 hybrid meeting). We reconfirmed once again in our 15-Feb-2023 in-person meeting that we are fine with proceeding with this proposal.

Release Notes

The following changes are applied:

in the Topology profile (to be published in 61970-456)
- remove association Terminal.TopologicalNode
- remove association DCBaseTerminal.DCTopologicalNode (note the association DCNode to DCTopologicalNode is already required association)
- delete classes Terminal, ACDCTerminal, DCBaseTerminal, ACDCConverterDCTerminal, DCTerminal as they are no longer needed in the profile after removal of the associations.
- a diagram in 456 is updated

in the Equipment profile (to be published in 61970-452)
- change cardinality of association Terminal.ConnectivityNode from 0..1 to 1. This is necessary bacause since CIM17 the models are build on the basis of ConnectivityNode for both node breaker and bus branch modelling styles.
- change the cardinality of the DCBaseTerminal.DCNode from 0..1 to 1. This will match the way it is done for AC part.
- the following rule was updated
R:452:ALL:ConductingEquipment:connectivity
All subtypes of ConductingEquipment are required to have associations to Terminals. The number of associated Terminals is specified in IEC 61970-301 in section 4.8.2 “Number of terminals for ConductingEquipment objects.”

Also available in: Atom PDF