Event list management system

Methods and systems are provided for event list management. In one embodiment, the method can include accessing data characterizing an operation of a machine. The data can include time durations of a plurality of events associated with the operation of the machine. The plurality of events can share a property. The method can include displaying a first view of the accessed data in a graphical display. The method can also include receiving data characterizing a user input indicative of a view change request. The method can further include determining an aggregate operation time and a number of occurrences of the plurality of events. The method can also include replacing, in the graphical display, the first view with a second view. The second view can include a single visual representation for the plurality of events. The single visual representation can include the determined aggregate operation time and the number of occurrences.

BACKGROUND

It can be difficult to manually monitor complex machines that have several moving and/or vibrating parts (e.g., turbines, compressors, and the like). Monitoring systems are commonly used to monitor the operation of complex machines, and generate events (e.g., events associated with an alarm) when the machine is not operating as desired. Monitoring systems can include sensors to detect operational information (e.g., operating parameters, operational states, and the like) associated with the machines, and relay a signal to a computing device, which can visually present the operational information for a designated person. For example, a turbine can include an accelerometer that can monitor the motion of blades of a turbine and relay angular velocity measurements to a computer for visualization.

Operational information of a complex machine can include information related to multiple operational parameters and multiple operational states of the machine. Operational states can include a state in which the machine is starting up or shutting down (“startup-shutdown state), a state of normal operation (“running state”), and a state in which the machine is turned off (“machine off state”). The operating parameters of the various operational states can include, turbine angular velocity, machine-part vibration rate, and the like. The computing device can automatically generate events to identify undesirable behavior of the machine, which can transition through multiple operational states. These events can be generated based off of alarm triggers or set points, which can be uniquely configured for the different operational states of a machine. As the machine transitions through multiple operational states, multiple events can be generated for each state. If the generated events are not presented in an easily decipherable manner, a user many not be able to effectively diagnose a problem associated with the machine, or respond effectively.

SUMMARY

In general, apparatus, systems, and methods for managing event lists associated with an alarm are provided.

In one embodiment, a method of event list management system is provided. The method can include accessing data characterizing an operation of a machine. The data can include time durations of a plurality of events associated with the operation of the machine. The plurality of events can share a property. The method can include displaying a first view of the accessed data in a graphical display. The first view can include separate visual representations for each of the plurality of events. The method can also include receiving data characterizing a user input indicative of a view change request. The method can further include determining an aggregate operation time and a number of occurrences of the plurality of events. The method can also include replacing, in the graphical display, the first view with a second view. The second view can include a single visual representation for the plurality of events. The single visual representation can include the determined aggregate operation time and the number of occurrences.

One or more of the following features can be included in any feasible combination.

In one embodiment, the property can be an operational state of the machine. In another embodiment, the property can be an anomalous behavior in the operation of the machine. In yet another embodiment, the property is a system health associated with the operation of the machine. The determined aggregate operation time can be displayed in a first column of the row, and the number of occurrences can be displayed in a second column of the row.

In one embodiment, the single visual representation can be a row in a data table in the graphical display. In another embodiment, the aggregate operation time and the number of occurrences can be determined in response to the user input. In yet another embodiment, the method can include receiving data characterizing a second user input and replacing, based on the second user input, the second view with the first view. In one embodiment, at least one of the accessing, the displaying, the receiving, the determining and the replacing can be performed by at least one data processor forming part of at least one computing system.

In another embodiment, a non-transitory computer program product is provided for storing instructions that can be executed by at least one data processor of at least one computing system. When executed, the instructions can implement operations that can include accessing data characterizing an operation of a machine. The data can include time durations of a plurality of events associated with the operation of the machine. The plurality of events can share a property. The operations can include displaying a first view of the accessed data in a graphical display. The first view can include separate visual representations for each of the plurality of events. The operations can also include receiving data characterizing a user input indicative of a view change request. The operations can further include determining an aggregate operation time and a number of occurrences of the plurality of events. The operations can also include replacing, in the graphical display, the first view with a second view. The second view can include a single visual representation for the plurality of events. The single visual representation can include the determined aggregate operation time and the number of occurrences.

One or more of the following features can be included in any feasible combination.

In one embodiment of the non-transitory computer program product, the property can be an operational state of the machine. In another embodiment, the property can be an anomalous behavior in the operation of the machine. In yet another embodiment, the property is a system health associated with the operation of the machine. The determined aggregate operation time can be displayed in a first column of the row, and the number of occurrences can be displayed in a second column of the row. In another aspect, the operations can include receiving data characterizing a second user input and replacing, based on the second user input, the second view with the first view.

In yet another embodiment, a system is provided having at least one data processor and memory storing instructions which, when executed by the at least one data processor, can cause the at least one data processor to perform operations that can include accessing data characterizing an operation of a machine. The data can include time durations of a plurality of events associated with the operation of the machine. The plurality of events can share a property. The operations can include displaying a first view of the accessed data in a graphical display. The first view can include separate visual representations for each of the plurality of events. The operations can also include receiving data characterizing a user input indicative of a view change request. The operations can further include determining an aggregate operation time and a number of occurrences of the plurality of events. The operations can also include replacing, in the graphical display, the first view with a second view. The second view can include a single visual representation for the plurality of events. The single visual representation can include the determined aggregate operation time and the number of occurrences.

One or more of the following features can be included in any feasible combination.

In one embodiment of the system, the property can be an operational state of the machine. In another embodiment of the system, the property can be an anomalous behavior in the operation of the machine. In yet another embodiment of the system, the property is a system health associated with the operation of the machine. In another aspect of the system, the operations can further include receiving data characterizing a second user input and replacing, based on the second user input, the second view with the first view.

Various aspects of the disclosed subject matter may provide one or more of the following capabilities. Some implementations of event list management system described in this application can allow a machine operator to group triggered events based on one or more properties of the event. For example, the operator can group events with similar event properties into a single event. Some implementations of the event list management system can generate summary statistics of the triggered events. Grouping of similar events and the summary statistics can enhance the operator's ability to efficiently make decisions to improve machine performance.

These and other capabilities of the disclosed subject matter will be more fully understood after a review of the following figures, detailed description, and claims.

DETAILED DESCRIPTION

It can be desirable to monitor the operation of a machine (e.g., by a network of sensors) and notify a user of an undesired behavior in an operation of the machine. This can be done, for example, by triggering an alarm when an undesired behavior of the machine is detected. A complex machine can have many operational parameters that need to be monitored. This can result in the triggering of multiple alarms at any given time. This can make it difficult for a user to detect a problem in the machine based on patterns of anomalous behavior, or determine a solution for solving the detected problem (e.g., replacing a machine part). This problem can be solved by allowing the user to group (e.g., combine) the triggered alarms (“events”) based on a property of the event (e.g., operational state associated with the event, the origin of the event, and the like). Additionally, the user can be provided with statistics associated with an event (e.g., number of times an event has been triggered, total time the machine has operated after the event has been triggered, and the like). The ability to quickly combine and visualize “like” event types as a single event with summary information improves interpretation of operating information. This aggregated view enhances machine operator decision making.

FIG. 1illustrates an exemplary method of operating an event list management system for use with machines such as industrial equipment (e.g., motors, turbines, oil pumps and the like). At102, data characterizing an operation of a machine can be accessed. The data can include machine operational information such as operational state of the machine; operational parameters associated with the operational state; timing information associated with the operational parameters (e.g., time of measurement of the operational parameters); time stamps of entry into and exit out of the operational state; information related to transition of the machine through various operational states; and the like.

The data can include information related to events associated with the operation of the machine (e.g., timing information associated with the plurality of events) can be generated and/or selected based on machine operational information. An event can indicate various attributes (e.g., vibration rate of the machine) associated with the operation of the machine. For example, events can provide benchmarks (e.g., maximum/minimum threshold values) that can be used to detect anomalous behavior in the operational parameters. Because the operation of a machine can vary based on the operational state of the machine the benchmarks for detection of anomalous behavior can change with operational state. As a result, events can be operational state dependent.

The events of the machine can have several event properties (e.g., operational state identifier, alarm activity, alarm level, alarm type, and alarm source, and the like). The operational state identifier property can indicate a predetermined operational state of the machine (e.g., “startup-shutdown state,” “running state,” “machine-off state,” and the like) to which the event can be assigned. The alarm activity can be indicative of the current state of the event. For example, if an alarm has exited an alarm condition, the alarm activity can be set to a predetermined value (e.g., “cleared”) indicating that the event associated with the alarm is no longer active. If an alarm has not cleared, and the machine is in the operational state associated with the alarm, the alarm activity value can be set to a second predetermined value (e.g., “active”). If an alarm has not cleared, and the machine is not in the operational state associated with the alarm, the alarm activity value can be set to a third predetermined value (e.g., “shelved”), which can indicate that the alarm has been suppressed.

Alarm source can be related to the capabilities of the alarm. For example, if the alarm can be configured to monitor the operation of a machine, the alarm can be referred to as having “condition monitoring” alarm source. On the other hand, alarms that have been configured to shut-down the machine rather than warn and/or notify a user can be referred to as having “protection” alarm source. As another example, another property of an alarm can be an alarm type Alarm type can include, for example, “not communicating,” “configuration out of data,” “database wrapping,” “authentication failure,” and the like. Alarm type can also include system health, which can be indicative of the health of the machine.

Multiple events can share event properties. Two or more events can be associated with one operational state and/or have a common value for alarm activity, alarm level, alarm type, alarm source, and the like. For example, data accessed at step102can include information (e.g., time durations) of a plurality of events that share one or more alarm properties.

In some implementations, the data can be accessed by a computing device.

FIG. 2is a system block diagram illustrating an exemplary system200that can perform event list management. The system200can include a machine202(e.g., turbine, motor, oil pump, and the like), a sensor204(e.g., accelerometer, position sensor, and the like), a computing device206(e.g., laptop, mobile phone, and the like), a display208and an input device210(e.g., keyboard, mouse, and the like). The sensor204can detect operational information of the machine202, and can relay the detected information to the computing device206. The computing device206can receive and save this information, and can visually present the information on a graphical display space of the display208. The computing device206can also generate/select events, and can graphically present the events on the graphical display space. As described before, an event can include various event properties. The generated and/or selected event and the operational parameters information of the machine202can be stored in a memory device. Information associated with the generated and/or selected events (e.g., alarm properties) can be accessed by the computing device206(e.g., as described in step102ofFIG. 1).

Returning back toFIG. 1, at104, a first view of the accessed data can be displayed in a graphical display (e.g., a graphical display space of display208).FIG. 3illustrates an exemplary graphical display space300where information related to the operation of a machine (e.g., plot of operational parameter vs. time, visual representations of alarms, event properties, and the like) can be displayed. For example, the data accessed in step102ofFIG. 1can be displayed on a display (e.g., display208). The graphical display space300can include a plot view302, an event list304, and a machine list306.

In the plot view302, a plot of the machine operational parameters as a function of time can be displayed. The plot view302can include a first axis340representative of a time related to the detection time of the operational parameter344. The first axis340can also indicate timing information associated with the operational state of the machine, for example, the time at which the machine enters an operational state, the duration of the operational state, and the time at which the machine exits the operational state. The first axis340inFIG. 3can represent the operation of a machine over a configurable time period, such as over the course of several months (e.g., January to August of 2016), weeks, days, hours, and the like.

The plot view302can also include a second axis342representative of, for example, the value of the operational parameter344. In addition to the operational parameter344, the plot view302can include graphical objects346,348,350that represent various alarms set points or triggers (e.g., “over” alarm type, “under” alarm type, “out of band” alarm type, and the like). The alarm set points can be triggered by a computing device (e.g., computing device206) or selected by the computing device from a database of alarms (e.g., selecting an alarm data structure). The alarm properties can be visually represented by the graphical objects, for example, by color, orientation, shape, size, and location of the graphical objects.

The event list304can provide information related to the various events associated with the machine. The event list304can also provide information related to the various alarm properties. For example, rows of the event list304can be representative of different events and the columns can be representative of the different alarm properties. As shown inFIG. 3, the alarm properties can include alarm path308, machine associated with alarm310, alarm operational state312, alarm trigger314, alarm activity316, alarm entry time318, alarm exit time320, alarm duration322and alarm count324.

The graphical display space300can include a machine list306that includes information/identity of the machines associated with the database (e.g., machines that are/have been monitored by the monitoring system). The machines can be organized into categories and subcategories that can allow a machine operator to navigate through the machine list306. Machine information can be organized in a hierarchy (e.g., a tree structure) that has multiple hierarchical levels. For example, as shown inFIG. 3, the machine list306illustrates machines of a peaker power plant360that can include machines grouped together into machine categories. For example, the peaker power plant (e.g., first hierarchical level) can include a category for steam turbine362(e.g., second hierarchical level).

The peaker power plant360and the steam turbine362can constitute a hierarchical chain with two hierarchical levels. The hierarchy can be presented in an indented pattern (e.g., hierarchical levels can be indented with respected to the higher and/or lower hierarchical levels). The machine operator can expand or collapse portions of the hierarchical structure by clicking on the icon representing a hierarchical level. For example, by clicking on the icon representing a hierarchical level (e.g., icon for steam turbine362), icons of lower hierarchy in the hierarchical chain can be collapsed.

In some implementations, a row of the event list304can be representative of a unique event. For example, as shown inFIG. 4, rows330,332,334,336,338of the event list304are representative of events of steam turbine328. The events can share one or more alarm properties. For example, row330and338are representative of “machine-off” operational state, which was entered/exited at different time. Intersections of columns318,320and322with the row330can provide the time of entry, time of exit, and event duration, respectively, for a first machine-off state. Intersection of columns318,320and322and row338can provide the time of entry, time of exit, and event duration for a second machine-off state. This can indicate that the steam turbine328can transition from a “machine-off” state to different operating states. At one or more time durations after exiting from the “machine-off” state, the steam turbine328can return to the “machine-off” state. For a machine operator, it can be desirable to know the number of times a machine (e.g., steam turbine328) has entered an operational state (e.g., “machine-off” state) and/or the total time duration spent in the operational state.

Embodiments of event list management system described in this application can allow the user to group multiple events that share a common alarm property (e.g., machine operational state, alarm type, and the like), and modify the event list304to reflect the grouping. Returning back to step106ofFIG. 1, data characterizing a user input indicative of a view change request can be received. For example, a user can provide an input through an input device (e.g., input device210) which can be received by a computing system (e.g., computing device206). The input can be provided, for example, by clicking on an icon on the display208(e.g., icons362/364on the display space300). The icon can be indicative of the alarm property based on which the events can be grouped. In some implementations, the icon can provide the user with multiple alarm properties to choose from. For example, clicking on the icon can provide a dropdown menu from which a desired alarm property can be chosen (e.g., by clicking).

At step108ofFIG. 1, an aggregate operation time and a number of occurrences of the plurality of events can be determined. A computing device (e.g., computing device206) can determine a total number of events associated with the alarm property provided/selected by the user. The total number of events can be calculated from the operational data of the machine (e.g., data characterizing the operation of the machine accessed at step102ofFIG. 1). The computing device can also determine the aggregate operation time of the machine in the selected event. This can be done, for example, by adding the durations of the events that share the selected alarm property. The duration of an event can be presented at the intersection of the row representing the event and alarm duration column322.

At step110, the first view (e.g., view of the accessed data displayed at step104) can be replaced with a second view in the graphical display space (e.g., a graphical display space of display208). The second view can include a single visual representation for multiple events. For example, the multiple events can share an alarm property (e.g., alarm property, which can be selected at step108). In one implementation the single visual representation can include a row in the event list304. If, for example, the user selects operational state as the alarm property based on which the events are to be grouped, the rows in the event list304that have a common operational state can be replaced by a single row. The single row can be representative of multiple events associated with an operational state. For example, the first view of the event list304that includes rows330,332,334,336, and338(illustrated inFIG. 4) can be replaced by the second view of the event list304that includes rows331,333,335,337, and339(illustrated inFIG. 5). Row331can represent the single visual representation of events associated with “machine-off” state.

The single visual representation can include the aggregate operation time and the number of occurrence of the event represented by the single visual representation (e.g., events with a common alarm property). As illustrated inFIG. 5, the second view of the event list304includes columns for total duration of alarm states326and total count of the events328. Intersection of row331and column326can present the value of the total time the machine spent in the multiple events represented by the row331(e.g., events that represent a “machine-off” state). The total time value can be calculated, for example, by adding the time duration values (e.g., time duration values presented in row322ofFIG. 4) of the rows representing the multiple events represented by the single visual representation. Intersection of row331and column328can present the number of events represented by the single visual representation in row331. For example, inFIG. 5, the value (“365”) displayed at the intersection of row331and column328indicates the number of times events related to a “machine-off” operational state has occurred.

The event list304can allow the user to view events that have occurred during a desired time period. For example, the event list can include an icon panel370that can allow the user to select a predetermined time period. The selected time period can include, for example previous hour, day, week, month, year, and the like. This can be done by clicking on an icon (e.g., icon from the icon panel370) representative of the predetermined time period. In some implementations, the user can provide the range of the desired time period (e.g., by entering through the input device210a start time and an end time of the time period). The event list304may display only the events that have occurred during the time period selected/entered by the user. This can allow the user to develop an understanding of the behavior of the machine (e.g., machine202) as a function of time. For example, if the machine had developed a problem in January, 2016, it may be desirable to know about the operation of the machine (e.g., alarm events generated) during that time period.

FIG. 6illustrates a graphical representation of a first view an event list604. The event list604includes rows630,632,634,636,638representative of various events associated with one or more machines (e.g., devices BPF3_3500, BPF2_3500, and the like). The event list604can include an icon panel670that can allow the user to select a predetermined time period (e.g., previous hour, day, week, month, year, and the like). This can be done by clicking on an icon (e.g., in the icon panel670) representative of the predetermined time period. In some implementations, the user can provide the range of the desired time period (e.g., by entering through the input device210a start time and an end time of the time period). This can allow the user to develop an understanding of the behavior of the machine (e.g., machine202) as a function of time. For example, column624can display the cumulative time spent by the machine in a given operational state (e.g., not communicating state) during the selected/entered time period. The event list604can include columns representing alarm path608, alarm device610, alarm type612, alarm activity614, alarm entry time616, alarm exit time618, and alarm count622.

FIG. 7illustrates a graphical representation of a second view of the event list604. The second view can include a single visual representation for multiple events. For example, the multiple events can share the alarm type and the machine associated with the event. The single visual representation can include a row in the event list604. If, the user selects alarm type and the machine associated with the event as the basis of grouping events, the rows in the alarm604that share the alarm type and the associated machine can be replaced by a single row. For example, the first view of the event list604that includes rows630,632,634,636, and638(illustrated inFIG. 6) can be replaced by the second view of the event list604that includes rows631,633,635,637, and639(illustrated inFIG. 7). Row631can represent the single visual representation of events associated with device BPF3_3500 and “not communicating” alarm type.

The single visual representation (e.g., row631) can include the aggregate operation time and the number of occurrence of the event represented by the single visual representation (e.g., events with a common alarm type and machine associated with the event). As illustrated inFIG. 7, the second view of the event list604includes columns for total duration of alarm states624and total count of the events626. Intersection of row631and column624can present the value of the total time the machine spent in the multiple events represented by the row631(e.g., events that represent “not communicating” alarm type for device BPF3_3500). The total time value can be calculated, for example, by adding the time duration values (e.g., time duration values presented in column620ofFIG. 6) of the rows of the multiple events represented by the single visual representation. Intersection of row631and column626can present the number of events represented by the single visual representation in row631. For example, inFIG. 7, the value (“15”) displayed at the intersection of row631and column626indicates the number of times events related to “not communicating” alarm type for device BPF3_3500.

FIGS. 8 and 9illustrate exemplary graphical representations of event list804. InFIG. 8, rows830,832,834,836,838of the event list804represent a first view of events associated with a steam turbine machine. The first view also includes alarm properties (e.g. alarm level807, machine associated with alarm808, alarm point810, alarm measurement812, alarm type814, alarm value816, alarm trigger818, alarm set820, alarm state822, alarm activity824, alarm entry time826, alarm exit time828, alarm duration829and alarm count805). InFIG. 9, rows831,833,835,837,839of the event list804represent a second view of events associated with the steam turbine machine. The second view includes column825representative of total time duration and column827representative of the number of occurrences of the events represented by a single visual representation of several events (e.g., sharing a common alarm property).