CIM Issues #6346
[GMDM #14] Indicating starting point for feeder tracing
61970-301,, 61968-13
Description
The GMDM test model expressed the nominal containership of each ConductingEquipment child in a Feeder by means of the recently created Equipment.EquipmentContainer association with the AdditionalEquipmentContainer role. The decision was made not to use the Feeder.Terminal association for the support of energization training, however. An alternative was implemented which leveraged a proposed Feeder.ConnectivityNode association, specifying a node assumed to always be energized if the feeder was energized.
This issue is related to Issue #
Files
Decision
18-Sep-2024 Joint TF Hybrid Meeting:
Feeder.NormalHeadTerminal association's description must be changed to explain which direction to start tracing.
Current description is: "The normal head terminal or terminals of the feeder."
Should be updated to: "The normal head terminal (or terminals) of the feeder. The tracing is done towards the conducting equipment associated with the head terminal (or terminals)."
Approved for application in the model.
Related issues
Updated by Pat Brown over 1 year ago
- Related to CIM Issues #4989: Feeder:How to modelize a feeder as a collection of equipme added
Updated by Pat Brown over 1 year ago
- File GMDM 14 - Modeling of starting point for feeder tracing.docx GMDM 14 - Modeling of starting point for feeder tracing.docx added
- Author/Contact Info set to Pat Brown pat@cimpledata.com
- Base Release set to CIM17
- Breaking Change set to No
- Requestor set to Pat Brown
- Standard(s) set to 61970-301,, 61968-13
- CIM Keywords 61970-Wires added
- CIM Impacted Groups WG13 added
- CIM Impacted Groups deleted (
None)
Updated by Pat Brown about 1 year ago
Pat Brown wrote:
The GMDM test model expressed the nominal containership of each ConductingEquipment child in a Feeder by means of the recently created Equipment.EquipmentContainer association with the AdditionalEquipmentContainer role. The decision was made not to use the Feeder.Terminal association for the support of energization training, however. An alternative was implemented which leveraged a proposed Feeder.ConnectivityNode association, specifying a node assumed to always be energized if the feeder was energized.
This issue is related to Issue #4989.
Updated by Todd Viegut 2 months ago
- Status changed from Open to In Progress
- Decision updated (diff)