Академический Документы
Профессиональный Документы
Культура Документы
customer interruptions.
Reliability indices are statistical aggregations of reliability data for a
reporting process and, in addition, there is a wide range of practices employed by utilities.
Obviously, a large variation in data collection and reporting
outage reporting. An overall comparison is also provided, and the section ends with a discussion on different industry trends.
Event capture Start time Customer count Step restoration Restoration time Verification of events Computation of indices
h.
Event Capture
Event capture refers to events that involve customer interruptions being
dispatched.
Fair: Manually captured when crew is dispatched. Poor: Captured from paper tickets collected daily. Worst: Captured from paper tickets collected monthly.
Start Time
Start time refers to the time that customers are interrupted. Accurate start times are typically available if SCADA information is
available, but a large percentage of events are not detectable through SCADA; the time of the first customer call is commonly used.
Start times can also be impacted by their method of entry into the
outage database.
Perhaps the worst systems are those that rely solely on paper outage
tickets.
Customer Count
Obtaining the correct number of customers interrupted by an
to dynamically track the distribution transformers that are out of service due to protection device operations and/or switching device operations.
Many systems that utilities have developed in-house utilize
system topology changes, new customer connections, etc., and uses affected device inference logic.
Fair: Based on customer call patterns with no affected device inference
logic.
Poor: Inferred from transformer power ratings.
Step/Partial Restoration
Step restoration refers to the restoration of some customers before
the
topology and are able to compute each restoration step and the impact to each customer.
Less sophisticated systems are able to infer the impact of step restoration
who updates a dynamic connectivity model that is able to precisely track all
restoration.
Good: Step restoration is tracked at the customer level, but based on a normal-state
recorded properly, many are recorded improperly, and many are not recorded.
Restoration Time
The point at which the last customer associated with an
actions and mobile data terminals in trucks are used for all lower level
events.
Good: Radio communication is required for all switching events, but
monthly.
Verification Of Events
Most utilities have some process for verifying outage event data before it is
allows dispatchers, trouble men, and construction crews to be contacted if an outage event is missing data or appears unusual in some way.
Less aggressive processes sample a portion of outage events based on
criteria ranging from compute generated exception reports, outages impacting more than a threshold number of customers, all feeder-level outages, and random sample.
Verification of Events
Best: All events are examined daily.
Computing Indices
After raw outage data is entered into an electronic database,
be used for reliability indices such as customer-level events, nonoutage construction jobs, and excluded storm events. The way these exclusions are handled can also impact reliability index calculations.
Computing Indices
Best: Indices calculated automatically from dispatch system database.
outage management system or an extraction used specifically for reliability directly reporting.
Poor: Indices calculated from a reliability analyst using spreadsheets populated
Escalated Events
Utility processes typically change when many outages are occurring within
certain situations, requiring the system to be de-activated and resulting in the potential loss of outage event data.
For some utilities, escalated event handling is not a reliability reporting
issue since most escalated events are excluded from reported reliability indices.
The best utilities have systems that perform the same for all events that will
Escalated Events
Best: All events that will be included in reported reliability indices are captured
during escalated events. Any escalated event that may alter the use of systems and processes is likely to be excluded from reported indices.
Good: Systems and processes are able to handle escalated events, but reportable
cases, the system must be turned off and outage data must be collected manually.
Worst: No exclusions are allowed, and outage data is not captured during
storms.
Conclusion
In general, utility reliability reporting practices have been improving because of
(OMS). These improvements not only have increased the accuracy of outage reporting but also have enabled improved customer communications during power
interruptions.
Most enhanced capabilities arise from automated data interfaces between the
corporate GIS, OMS, SCADA and Call Centers, resulting in greater data accuracy, reporting productivity, more timely information for dispatchers and customers, and quicker outage restoration.