CIM Issues #6678
Refactoring Outage Class Modeling
Status:
Review
Priority:
Normal
Author/Contact Info:
Henry B. Dotson, III
Base Release:
CIM101
Solution to be Applied To:
CIM101
Solution Version:
Enterprise14v04
Solution Applied By:
Henry Dotson
Completion Date:
04/08/2025
CIM Keywords:
61968-Common, 61968-Operations
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG14
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:
Description
Currently the Outage class inherits from the Document class. This modeling is not semantically correct because an outage is not a document, it is an event. Therefore, the modeling should be refactored to correctly express the intended semantics.
Proposed Solution
Have Outage inherit from IdentifiedObject and create an association between Outage and ActivityRecord.
Updated by Henry Dotson about 1 month ago
- Status changed from Open to In Progress
- Solution Version changed from CIM101 to Enterprise14v04
- Solution Applied By set to Henry Dotson
- Completion Date set to 04/08/2025
Updated by Henry Dotson 2 days ago
- Status changed from In Progress to Review
09-May-2025:
Refactoring the model will also require a modification in the description of the Outage class. It is currently described as a document. The change would redefine the class as an event that is documented by its association with an activity record.