Methods for assessing reliability of a utility company's power system

• US 8,321,804 B2
• Filed: 06/13/2008
• Issued: 11/27/2012
• Est. Priority Date: 07/26/2007
• Status: Active Grant

• Current Assignee: Alstom Technology Ltd. (Alstom SA)
• Original Assignee: Areva T&D SAS (GE Aerospace)
• Inventors: Castelli, Gennaro, Hackett, Michael, Howard, Michael Quinn, Jones, Lawrence Edmund, Shung, HuiChu Su, Brand, Heath Daniel
• Primary Examiner(s): Augustine, Nicholas
• Assistant Examiner(s): STITT, ERIK V
• Application Number:
  US12/139,194
• Publication Number:
  US 20090030556A1
• Time in Patent Office: 1,628 Days
• Field of Search: 715/771, 715/810, 715/764
• US Class Current: 715/771
• CPC Class Codes: G01R 31/40 Testing power supplies testing photovoltaic devices H02S50/10
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/0486 Drag-and-drop
• CPC Class Codes: G06F 3/14 Digital output to display device ; Cooperation and interconnection of the display device with other functional units
• CPC Class Codes: G06F 3/167 Audio in a user interface, e.g. using voice commands for navigating, audio feedback
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06T 11/206 Drawing of charts or graphs
• CPC Class Codes: G06T 11/60 Editing figures and text; Combining figures or text
• CPC Class Codes: G06T 3/40 Scaling of whole images or parts thereof, e.g. expanding or contracting
• CPC Class Codes: G08B 23/00 Alarms responsive to unspecified undesired or abnormal conditions
• CPC Class Codes: G09G 5/377 for mixing or overlaying two or more graphic patterns G09G5/02, G09G5/397 take precedence
• CPC Class Codes: H02J 2203/20 Simulating, e g planning, reliability check, modelling or computer assisted design [CAD]
• CPC Class Codes: H02J 3/00 Circuit arrangements for ac mains or ac distribution networks
• CPC Class Codes: H02J 3/0012 Contingency detection
• CPC Class Codes: H02J 3/008 involving trading of energy or energy transmission rights
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: Y02E 60/00 Enabling technologies; Technologies with a potential or indirect contribution to GHG emissions mitigation
• CPC Class Codes: Y04S 10/50 Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
• CPC Class Codes: Y04S 40/20 : Information technology specific aspects, e.g. CAD, simulation, modelling, system security
• CPC Class Codes: Y04S 50/10 : Energy trading, including energy flowing from end-user application to grid

Abstract

Methods are provided for assessing reliability of a power system of a utility company. At least one main overview display is obtained. Violation markers are displayed on the one main overview display. A monitored elements tab is updated with a list of monitored elements.

Claims

1. A method of assessing reliability of a power system of a utility company that has an energy management system with a control panel, comprising:

obtaining at least one main overview display;

selecting by an operator an area of the main overview display which it wishes to focus on by at least one of rubber-banding or lassoing the area;

detecting and analyzing a contingency case violation using a reliability assessment module;

displaying an alert when a new violation appears following execution of the contingency case violation analysis;

generating dynamically a contingent tab in the control panel with a list of contingencies impacting monitored elements in violations within the selected area;

cutting and pasting the area into a fly-out;

drawing projection lines to the fly-out; and

interacting with the fly-out to provide the operator with an awareness of a context of situations and information about a reference source of the fly-out;

interacting with the fly-out to display violation markers on the one main overview display; and

updating a monitored elements tab with a list of monitored elements.

2. The method of claim 1, wherein the monitored elements tab is updated with the monitored elements in a state of selected from at least one of, alarm, violation, and warning state.

3. The method of claim 1, further comprising:

using a reliability assessment module to detect and analyze a base case violations.

4. The method of claim 3, further comprising:

displaying an alert in response to a new violation.

5. The method of claim 4, wherein the alert is displayed of the viewport.

6. The method of claim 1, further comprising:

displaying a voltage contour of voltages at all buses for all KV levels.

7. The method of claim 1, wherein a branch violation marker is presented on a center of a branch.

8. The method of claim 1, wherein voltage violations are presented at the corresponding station where violated elements reside.

9. The method of claim 1, wherein color of a marker indicates the severity of a violation.

10. The method of claim 1, wherein marker is used to indicate type of violation.

11. The method of claim 1, further comprising:

selecting a violation marker; and

only displaying the selected violation marker on the main overview display while having the other violation markers disappear while the user performs an analysis of the situation.

12. The method of claim 11, further comprising:

showing only those violations associated for the selected violated element on the monitored elements tab.

13. The method of claim 1, further comprising:

showing vital data related to violations selected on the overview display.

14. The method of claim 13, further comprising:

showing the vital data with a control panel monitor element list shows the vital data.

15. The method of claim 14, further comprising:

displaying at a top line a name and a highest percent over a limit value violated.

16. The method of claim 1, wherein details for violations are selected from a least one of, limit value, current value and percent over the limit it violates.

17. The method of claim 14, wherein the violation is at a branch and an entry is provided for each end of the branch.

18. The method of claim 1, further comprising:

providing two icons for each monitored element in violation, with one icon locating the monitored element on the overview displays, and another icon for calling an associated line display in a dashboard tab to obtain additional information.

19. The method of claim 1, further comprising:

detecting and analyzing a contingency case violation using a reliability assessment module.

20. The method of claim 19, further comprising:

displaying an alert when a new violation appears following execution of the contingency case violation analysis.

21. The method of claim 20, further comprising:

updating a contingent tab in the control panel with a list of contingencies impacting monitored elements in violations.

22. The method of claim 21, further comprising:

using user interfaces at the control panel to analyze cause and effect from results provided by contingency analysis.

23. The method of claim 1, wherein material presented on the overview display includes contingency-related information.

24. The method of claim 1, further comprising:

visualizing and assessing a relationship between monitored elements and contingencies.

25. The method of claim 23, further comprising:

using combinations of the overview display, the control panel, and violation toolbar filters to enable a user to analyze the post contingency case violations.

26. The method of claim 25, wherein the analyses is facilitated by graphical and list formats.

27. The method of claim 23, wherein the control panel shows the monitored element with at least one of, name of the monitored element, type of violation, base case value, post contingency value, limit value associated with an alarm, violation or Warning being presented and a percent over a designated limit.

28. The method of claim 23, wherein when a contingent element creates a violation, a violation maker appears on a branch or substation.

29. The method of claim 28, further comprising:

selecting a contingent element marker for a contingent element; and

displaying all violations that the contingent element creates.

30. The method of claim 23, wherein the control panel includes both a monitored elements tab and a contingency tab.

31. The method of claim 30, wherein the contingency tab is automatically opened when a contingency marker is selected to show a list of contingencies that are impacting the monitored elements in at least one of, alarm, violation and warning states.