SYSTEM AND METHOD FOR ANALYZING AND RETRIEVING DATA OBTAINED FROM TURBINE OPERATIONS

• US 20120232806A1
• Filed: 03/10/2011
• Published: 09/13/2012
• Est. Priority Date: 03/10/2011
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Haynes, Leon Ericson, Srinivasan, Jayanthi, Johnson, David Neal, Singleton, Charles B., Agady, Olga
• Application Number:
  US13/044,924
• Publication Number:
  US 20120232806A1
• Time in Patent Office: Days
• US Class Current: 702/33
• CPC Class Codes: G05B 23/0216 Human interface functionality, e.g. monitoring system providing help to the user in the selection of tests or in its configuration
• CPC Class Codes: G05B 23/0264 Control of logging system, e.g. decision on which data to store; time-stamping measurements

Abstract

Systems and methods for analyzing and retrieving data from a monitoring system for monitoring a plurality of rotary machinery, such as turbines, is disclosed. A notification of an anomaly event is received from the monitoring system and tag data associated with the anomaly event is retrieved using a computer-implemented data retrieval tool. The tag data is stored at a central location and one or more objects are generated at the central location according to an event model. The one or more objects are stored as an event data object at the central location. The event data object is accessible by one or more client devices configured to render the one or more objects associated with the event data object in a graphical user interface.

Claims

1. A method for retrieving data from a monitoring system for monitoring a plurality of machines, comprising:

receiving a notification of an anomaly event from the monitoring system;

retrieving tag data associated with the anomaly event from the monitoring system using a computer-implemented data retrieval tool;

storing the tag data at a central server;

generating one or more objects from the tag data at the central server according to an event model; and

storing the one or more objects as an event data object associated with the anomaly event at the central server.

2. The method of claim 1, wherein generating one or more objects associated with the tag data at the central server according to an event model, comprises:

determining an event type associated with the anomaly event;

identifying one or more objects associated with the event type in the event model; and

generating the one or more objects associated with event type.

3. The method of claim 1, wherein the method comprises adjusting at least one parameter of the event model.

4. The method of claim 1, wherein the one or more objects associated with the tag data comprise chart objects.

5. The method of claim 1, wherein the method further comprises:

receiving a request from a client device for access to the event data object; and

providing the client device access to the event data object.

6. The method of claim 5, wherein the method further comprises:

storing the event data object at the client device; and

rendering the one or more objects associated with the event data object at the client device.

7. The method of claim 5, wherein the method further comprises:

creating a spreadsheet template at the client device for the tag data;

providing tag data associated with the event data object to the spreadsheet template.

8. The method of claim 1, wherein the method comprises:

maintaining a list of anomaly events at the central server;

updating the list of anomaly events at the central server; and

providing the updated event list to a client device in operable communication with the central server.

9. The method of claim 8, wherein updating the list of anomaly events at the central server based on information received from the monitoring system comprises at least one of:

adding an anomaly event to the list of anomaly events when the notification of an anomaly event is received from the monitoring system;

removing false positive anomaly events from the list of anomaly events;

or

removing resolved anomaly events from the list of anomaly events.

17. The system of claim 1, wherein said executable instructions are configured to control said central server to:

maintain a list of anomaly events at the central server;

update the list of anomaly events at the central server; and

provide the updated list of anomaly event to a client device over a second communication link.

18. The system of claim 17, wherein said executable instructions are configure to control said central server to update the list of anomaly events at said central server by controlling said central server to perform at least one of:

adding an anomaly event to the list of anomaly events when the notification of an anomaly event is received from the monitoring system;

removing false positive anomaly events from the list of anomaly events;

or removing resolved anomaly events from the list of anomaly events.

10. A system for retrieving data from a monitoring system for monitoring a plurality of rotary machines, comprising:

a central server comprising a database and a first communication link between said central server and the monitoring system, said central server configured to receive a notification of an anomaly event from the monitoring system over said first communication link, said central server further comprising;

a data collection engine configured to retrieve tag data associated with the anomaly event from the monitoring system and to store the tag data in said database; and

a computer readable medium comprising executable instructions configured to control said central server to generate one or more objects from the tag data according to an event model and to store the one or more objects as an event data object associated with the anomaly event in said database.

11. The system of claim 10, wherein said executable instructions are further configured to control said central server to:

determine an event type associated with the anomaly event;

identify one or more objects associated with the event type in the event model; and

generate one or more objects associated with the event type by the event model.

12. The system of claim 10, wherein said central server further comprises a user interface, said user interface configured to receive instructions from a user to configure one or more parameters of the event model.

13. The system of claim 10, wherein the one or more objects comprise chart objects.

14. The system of claim 10, wherein the system further comprises a client device and a second communication link between said client device and said central server, said central server configured to receive a request from said client device for access to the event data object and to push the event data object to said client device.

15. The system of claim 14, wherein said client device comprises a processing device configured to:

store the event data object at the client device; and

render the one or more objects associated with the event data object in a graphical user interface.

16. The system of claim 14, wherein the client device comprises a processing device configured to:

create a spreadsheet template at the client device for the event data; and

provide the tag data associated event data object to the spreadsheet template.

19. A method for retrieving data from a monitoring system for monitoring a plurality of rotary machines, the method comprising:

receiving a push notification of an anomaly event from the monitoring system;

retrieving tag data associated with the anomaly event from the monitoring system using a computer-implemented data retrieval tool;

storing the tag data at a central server;

determining an event type associated with the anomaly event;

identifying one or more objects associated with the event type by an event model;

generating the one or more objects associated with event type according to the event model using the retrieved tag data; and

storing the one or more objects as a single event data object associated with the anomaly event at the central server;

wherein the single event data object is accessible by a client device configured to render the one or more objects associated with the event data object in a graphical user interface.

20. The method of claim 19, wherein the one or more objects comprise chart objects.