Project

General

Profile

CIM Issues #5977

Cardinality of PowerSystemResource to Location

Added by Martin Miller about 2 years ago. Updated 2 months ago.

Status:
Open
Priority:
Normal
Author/Contact Info:
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Yes
Breaking Change Description:
CIM Impacted Groups:
WG13, WG14
Requestor:
Standard(s):

61968-13, 61968-11, 61970-600-2

Version:
2
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

The cardinality of the relationship from PowerSystemResource to Location is 0..1. This prevents a PowerSystemResource from having both a ServiceLocation and a MaintenanceLocation. It also prevents a PowerSystemResource from having PositionPoint coordinates that are part of two different CoordinateSystems.


Proposed Solution

Increase the cardinality to 0..*


Decision

19-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:
Reviewed.

- We want to have human address information separate from geospacial coordinate information.
- We need to handle the fact that two different spacial coordinates can refer to the same place
- We also need to handle the case where two different human addresses may refer to the same place (the instructions may be stored separately and should be taken into consideration)

See the "related issue" linked to this issue.

Action Item: We need a proposal that allows for the existing 0..1 to stay as is but with modeling that takes into consideration the human address concerns raised above. Needs to articulate in the modelling the distinct concepts that better separate these concerns.


Related issues

Related to WG14 Part 11 Issues - CIM Issues #5880: Location should follow Spatial Data best practiceOpenActions
#1

Updated by Chavdar Ivanov 9 months ago

  • Standard(s) changed from 61968-13 to 61968-13, 61968-11, 61970-600-2
#2

Updated by Chavdar Ivanov 3 months ago

  • Status changed from New to Open
#3

Updated by Todd Viegut 2 months ago

  • Related to CIM Issues #5880: Location should follow Spatial Data best practice added
#4

Updated by Todd Viegut 2 months ago

  • Decision updated (diff)

Also available in: Atom PDF