CIM Issues #5097
Allow OperationalLimitSet to be described by a Season by adding a new association between OperationalLimitSet and Season
Status:
In Progress
Priority:
Normal
Author/Contact Info:
Becky Iverson/Becky.Iverson@siemens.com
Base Release:
61970cim17v40
Solution to be Applied To:
CIM18
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Becky Iverson
Standard(s):
61970-301, 61970-452
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:
Description
Add a new association between OperationalLimitSet and Season. This will allow an OperationalLimitSet to be described by a defined Season rather than encoding the season "name" within the OperationalLimitSet.name.
Season 0..1 -> OperationalLimitSet 0..many
Proposed Solution
Add new association
Season 0..1 -> OperationalLimitSet 0..many
Decision
18-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:
Reviewed and agree that this proposed association seems reasonable. May be added to the model for CIM18.
Add new association
Season 0..1 -> OperationalLimitSet 0..many
Also, we need to then move Season into the Core package to maintain proper dependency management.
Should also be included in the 452.
Related issues
Updated by Todd Viegut about 1 month ago
- Status changed from Open to In Progress
- Solution to be Applied To set to CIM18
- Decision updated (diff)
Updated by Todd Viegut about 1 month ago
- Has duplicate CIM Issues #5012: Exchange of seasonal limit sets.Functionally this is excha added