Document describing details of an active or planned outage in a part of the electrical network.
A non-planned outage may be created upon:
- a breaker trip,
- a fault indicator status change,
- a meter event indicating customer outage,
- a reception of one or more customer trouble calls, or
- an operator command, reflecting information obtained from the field crew.
Outage restoration may be performed using a switching plan which complements the outage information with detailed switching activities, including the relationship to the crew and work.
A planned outage may be created upon:
- a request for service, maintenance or construction work in the field, or
- an operator-defined outage for what-if/contingency network analysis.
nan
Status of subject matter (e.g., Agreement, Work) this document represents. For status of the document itself, use 'docStatus' attribute.
Status value at 'dateTime'; prior status changes may have been kept in instances of activity records associated with the object to which this status applies.
Reason code or explanation for why an object went to the current status 'value'.
Pertinent information regarding the current 'value', as free form text.
Date and time for which status 'value' applies.
Free text comment.
Status of this document. For status of subject matter this document represents (e.g., Agreement, Work), use 'status' attribute.
Example values for 'docStatus.status' are draft, approved, cancelled, etc.
Electronic address.
World wide web address.
User ID needed to log in, which can be for an individual person, an organisation, a location, etc.
MAC (Media Access Control) address.
Radio address.
Password needed to log in.
Alternate email address.
Address on local area network.
Primary email address.
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
defines the status of the crew as in dispatched or arrived, etc.
This contains an disclaimers the utility would like to place on the data provided to any stakeholder. This may be different for different stakeholders. This should possibly be an attribute under the Organization class but it is placed here for now.
Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).
Document title.
a name to denote the community - this could be a name or a code of some kind.
Revision number for this document.
the total number of customers that are served in the area (both outaged and not outaged).
Estimated outage period for a planned outage. The start of the period is the start of the planned outage and the end of the period corresponds to the end of the planned outage.
End date and time of this interval. The end date and time where the interval is defined up to, but excluded.
Start date and time of this interval. The start date and time is included in the defined interval.
number of customers that have been restored in the area.
Date and time that this document was created.
The original number of meters that were affected as reported by the OMS within the utility. That is, this is the total number of meters that were out at the beginning of the outage.
Document subject.
The reason for the planned outage.
Summary counts of service points (customers) affected by this outage.
Number of critical service (delivery) points affected by an outage.
Number of all service (delivery) points affected by an outage.
The updated number of meters affected by the outage as reported by the OMS within the utility. It is assumed this number will be updated repeatedly until the full outage is resolved.
Date and time this document was last modified. Documents may potentially be modified many times during their lifetime.
Actual outage period; end of the period corresponds to the actual restoration time.
Same definition as Outage.estimatedPeriodDefines if the outage has been verified or is only estimated
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy.
The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time.
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended.
For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
The name is any free human readable and possibly non unique text naming the object.
Document describing the consequence of an unplanned outage in a part of the electrical network. For the purposes of this model, an unplanned outage refers to a state where energy is not delivered; such as, customers out of service, a street light is not served, etc.
A unplanned outage may be created upon:
- impacts the SAIDI calculation
- a breaker trip,
- a fault indicator status change,
- a meter event indicating customer outage,
- a reception of one or more customer trouble calls, or
- an operator command, reflecting information obtained from the field crew.
Outage restoration may be performed using a switching plan which complements the outage information with detailed switching activities, including the relationship to the crew and work.
Status of subject matter (e.g., Agreement, Work) this document represents. For status of the document itself, use 'docStatus' attribute.
Same definition as Document.statusFree text comment.
Status of this document. For status of subject matter this document represents (e.g., Agreement, Work), use 'status' attribute.
Example values for 'docStatus.status' are draft, approved, cancelled, etc.
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
defines the status of the crew as in dispatched or arrived, etc.
Same definition as Outage.statusKindThis contains an disclaimers the utility would like to place on the data provided to any stakeholder. This may be different for different stakeholders. This should possibly be an attribute under the Organization class but it is placed here for now.
Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).
Document title.
a name to denote the community - this could be a name or a code of some kind.
Revision number for this document.
the total number of customers that are served in the area (both outaged and not outaged).
Estimated outage period for a planned outage. The start of the period is the start of the planned outage and the end of the period corresponds to the end of the planned outage.
Same definition as Outage.estimatedPeriodnumber of customers that have been restored in the area.
Date and time that this document was created.
The possible cause that could be associated with this unplanned outage.
The original number of meters that were affected as reported by the OMS within the utility. That is, this is the total number of meters that were out at the beginning of the outage.
Document subject.
Date and time this document was last modified. Documents may potentially be modified many times during their lifetime.
Summary counts of service points (customers) affected by this outage.
Same definition as Outage.summaryThe updated number of meters affected by the outage as reported by the OMS within the utility. It is assumed this number will be updated repeatedly until the full outage is resolved.
The earliest start time of the Outage - as reported by some system or individual
Actual outage period; end of the period corresponds to the actual restoration time.
Same definition as Outage.estimatedPeriodThe cause of this outage. This is the cause that is used to present to external entities. That is, the cause is weather, equipment failure, etc.
Note: At present, this is a free string text; it could be replaced with an enumeration in the future.
Defines if the outage has been verified or is only estimated
Same definition as Outage.outageKindThe aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy.
The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time.
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended.
For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
The name is any free human readable and possibly non unique text naming the object.