Event visualization for asset condition monitoring

Abstract

Event visualization for asset condition monitoring is disclosed. In one aspect, a method includes receiving data characterizing an alert event report associated with a first industrial machine, the alert event report generated by a first user through a first network-based graphical user interface (GUI). The first network-based GUI is associated with an enterprise monitoring system of an industrial enterprise that includes the first industrial machine. The alert event report includes at least a portion of an event data set that includes information of an alert event associated with the first industrial machine and an identity of a second user designated by the first user to handle the alert event report. The method further includes providing the alert event report to a second network-based graphical user interface (GUI) associated with the enterprise monitoring system. The method also includes receiving, through the first GUI of the first monitoring system, data characterizing additional information associated with the alert event and / or edits to the event data set.

Description

Background Technology

[0001] Many process-intensive industries, such as hydrocarbon refining and power generation, rely heavily on the operation of machinery, and in some cases, on its continuous operation. In these environments, the failure of one or more machines can incur significant costs due to repair expenses, production losses, and potential harm to workers. Given these risks, it is common practice to monitor certain operating parameters of one or more machine components. Measurement of these operating parameters provides an indication of the mechanical condition of the machine components, allowing for preventative maintenance (e.g., repair, replacement, etc.) to be performed before failure occurs. This condition monitoring can provide one or more long-term benefits, such as lower production costs, reduced equipment downtime, improved reliability, and enhanced safety. Summary of the Invention

[0002] In some aspects, a method includes receiving data characterizing an alarm event report associated with a first industrial machine, the alarm event report being generated by a first user via a first web-based graphical user interface (GUI). The first web-based GUI is associated with an enterprise monitoring system of an industrial enterprise including the first industrial machine. The alarm event report includes at least a portion of an event dataset containing information about an alarm event associated with the first industrial machine, and the identity of a second user designated by the first user to process the alarm event report. The event dataset is stored in a database associated with the enterprise monitoring system. The method also includes providing the alarm event report to a second web-based graphical user interface (GUI) associated with the enterprise monitoring system. The method further includes receiving data characterizing additional information associated with the alarm event and / or editing the event dataset via the first GUI of the first monitoring system. The method also includes storing data characterizing the additional information associated with the alarm event in the event dataset stored in the database and / or editing the event dataset in the database.

[0003] One or more of the following features may be included in any feasible combination.

[0004] In some embodiments, the method further includes receiving data representing at least a portion of an event dataset to be included in an alarm event report, based on interaction between a first user and one or more interactive graphical objects in a dialog box in a first web-based GUI; and generating an alarm event report including the selected portion of information about the alarm event. In some embodiments, the information about the alarm event associated with the first industrial machine includes one or more locations of the first industrial machine. The alarm level is associated with the alarm event and operating parameters of the first industrial machine.

[0005] In some embodiments, the method further includes receiving data representing a request to switch from the second network-based GUI to a first GUI of the first monitoring system via a second network-based GUI; and providing the first monitoring system with access to at least a portion of an event dataset via the first GUI of the first monitoring system. In some embodiments, the first monitoring system is configured to monitor the operation of a first industrial machine. This monitoring includes receiving operational characteristics from sensors connected to the first industrial machine at the operational site, and generating alarm events.

[0006] In some embodiments, the method further includes generating a first web-based GUI comprising a first part and a second part. The first part includes a list of multiple industrial machines in an industrial enterprise. The method also includes receiving data representing the selection of the first industrial machine from the list of multiple industrial machines; and displaying information associated with alarm events of the first industrial machine in the second part of the web-based GUI. In some embodiments, the second part of the web-based GUI includes a graph of the operating parameters of the first industrial machine as a function of detection time, which is an operating parameter.

[0007] In some implementations, the alarm event report also includes an access level associated with a second user. The access level determines the type of editing of information associated with the alarm event and / or the type of access to information stored in a database associated with the first industrial machine. In some implementations, data characterizing additional information associated with the alarm event includes analysis of the alarm event generated via a first GUI of the first monitoring system.

[0008] In some implementations, the method further includes generating a modified alarm event report associated with the first industrial machine via a first GUI of the first monitoring system. The modified alarm event report is based at least on additional information. The modified alarm event report includes at least the additional information received via the first GUI and the identity of a third user designated by a second user to process the alarm event report. The method also includes providing the modified alarm event report to a second monitoring system at a second industrial site. The industrial enterprise includes the second industrial site. The method further includes receiving data representing second additional information associated with the alarm event via a second GUI of the second monitoring system; and storing the data representing the second additional information associated with the alarm event in a database. Attached Figure Description

[0009] These and other features will be more readily understood from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0010] Figure 1 This is a schematic diagram of an exemplary implementation of a GUI for a monitoring system associated with an industrial site that includes multiple industrial machines;

[0011] Figure 2 An exemplary web-based graphical user interface (GUI) is shown;

[0012] Figure 3 An exemplary enterprise monitoring system for an industrial company is shown;

[0013] Figure 4 This is a flowchart illustrating an exemplary method for managing industrial assets through an enterprise monitoring system;

[0014] Figure 5 It shows Figure 2 It includes a web-based GUI with dialog boxes for generating alarm event reports; and

[0015] Figure 6 An exemplary GUI for a monitoring system in an industrial enterprise is shown.

[0016] It should be noted that the accompanying drawings are not necessarily drawn to scale. The drawings are intended only to depict typical aspects of the subject matter disclosed herein and should not be considered as limiting the scope of this disclosure. Detailed Implementation

[0017] Industrial machines can be monitored by monitoring systems to ensure they operate within acceptable tolerances. Generally, machine monitoring may involve sensors measuring operating parameters of one or more components of the machine, determining whether the machine components are functioning correctly based on these measurements, and issuing warnings when malfunctions are detected. These warnings allow for corrective actions to be taken before machine failures occur, providing beneficial effects such as lower production costs, reduced equipment downtime, improved reliability, and enhanced safety.

[0018] Industrial enterprises may include multiple industrial sites that can be geographically separated (e.g., worldwide). An industrial site may include multiple industrial machines. An industrial site may include monitoring systems configured to monitor the industrial machines at the industrial site. In existing paradigms, the user of the first monitoring system may not be aware of alarm events at the second monitoring system. Even if the user is aware, he / she may not have access to the second monitoring system (e.g., operational data detected by the second monitoring system, steps taken at the second monitoring site to handle alarm events, etc.). Therefore, establishing collaboration between users of different monitoring systems can be challenging. For example, the expertise of a circulating compressor specialist at the first industrial site may not be applicable to handling malfunction / alarm events associated with circulating compressors at different industrial sites.

[0019] In some implementations, the present topic provides an ecosystem that allows seamless collaboration between users across different industrial sites within an industrial enterprise. This improves (e.g., optimizes) asset management. For example, an enterprise monitoring system supporting a web-based graphical user interface (GUI) is provided, through which users can monitor and manage industrial machines located anywhere within the industrial site. A first user can seamlessly decentralize the management of alarm events for industrial machines to a second user. The first user can also control the access level of the second user (e.g., actions the second user can perform, alarm event data the second user can access, etc.). In some implementations, the first user's handling of alarm events can be compiled and made available to the second user. This improves the efficiency of collaboration because the first user does not need to use different communication methods (e.g., email services) to convey details of alarm events, actions taken, etc., to the second user.

[0020] Figure 1 This is a schematic diagram of an exemplary embodiment of a GUI 100 for a condition monitoring system associated with industrial machinery at an industrial site. The GUI 100 includes a first portion 100A and a second portion 100B. The first GUI portion 100A includes user-selectable options, while the second GUI portion 100B is updated to display a visual representation of the industrial machinery corresponding to the option selected within the first GUI portion 100A. As shown, the first GUI portion 100A includes a selection option 102, a main display option 104A, a secondary display option 104B, and multiple view spaces 106 having content that dynamically changes in response to the industrial machinery selected via the selection option 102. As shown, the selection option 102 may include industrial machinery and condition monitoring devices (e.g., physical monitors) at the industrial site.

[0021] The main display option 104A may include status, events, graphs, and instance history associated with the industrial machine or device selected from selection option 102. Status may include the condition of the selected industrial machine (e.g., satisfactory, unsatisfactory, warning, alarm, etc.) based on one or more measurements acquired by sensors or received by a third-party system. Events may be alarms or system logs that alert the user to potential component health problems (e.g., measured parameters exceeding thresholds). Graphs may include any graphical representation of the measurement data. Instance history may include graphs of historical data and historical reports. The auxiliary display option 104B may include subtypes of the display views based on selection option 102 and main display option 104A. Examples of display subtypes may include the type of defined graph view (e.g., vibration, surge curve) and / or the type of display (e.g., list, bar chart, etc.).

[0022] The dynamic view space 106 may include information associated with the industrial machine selected via selection option 102. This information may include hierarchical information displayed in the hierarchical view space 106A of the dynamic view space 106. The hierarchical information may include a first level associated with the location of the industrial machine, a second level associated with the processing system associated with the industrial machine, a third level indicating the type of machine, etc. This information may include operating parameters (e.g., acceleration, temperature, velocity, displacement, clearance distance, etc.) derived from measurements obtained from sensors associated with the selected machine. The operating parameters may be displayed in the measurement view space 106B of the dynamic view space 106. When the operating parameters are displayed in the second GUI section 100B (e.g., a graph), the displayed operating parameters may be selected from the measurement view space 106B.

[0023] Figure 1 The GUI 100 shows a visual representation in the second GUI section 100B, corresponding to a machine selected from a plurality of machines in the component options 102 (e.g., a circulating compressor), a view selected from the main display option 104A, and a list of views selected from the auxiliary display option 104B. The visual representation of the selected machine may include visualizations of the components of the selected machine. For example, the visual representation of the circulating compressor may include a first visualization 122 of the motor of the circulating compressor, a second visualization 124 of the gearbox of the circulating compressor, and a third visualization 126 of the compressor of the circulating compressor. The second GUI section 100B may include identifiers (e.g., names) and one or more data fields associated with the various components of the selected industrial machine. For example, the second GUI section 100B may include a graphical object 114 displaying data entries 116 associated with the respective machine components. Data entries 116 may include operating parameters, such as real-time measurement data received from various sensors 18 disposed on the respective machine component 112 (e.g., machine operating status, status indication, speed, etc.), outputs of analyses performed by a processor based on the measurement data received from the various sensors disposed on the respective machine component, etc. The GUI 100 further updates the measurement view space 106B to display operating parameters (e.g., acceleration, temperature, speed, displacement, clearance distance, etc.) associated with the selected machine part.

[0024] Figure 2An exemplary web-based GUI 200 is illustrated. The web-based GUI includes a first section 202 and a second section 204. The first section 202 includes a plurality of interactive graphical objects 206 to 210. Each of the graphical objects 206 to 210 may represent an industrial site. For example, graphical object 206 represents a first industrial site, graphical object 208 represents a second industrial site, and graphical object 210 represents a third industrial site. When interacting with the graphical object indicating the industrial site, an industrial machine at the industrial site can be selected from a drop-down menu presented in the first section 202. When an industrial machine is selected in the first section 202, an alarm list 212 (including a list of events / alarms associated with the selected industrial machine) is displayed in the second section 204 of the web-based GUI 200. An alarm event (e.g., one of alarm events 214 to 320) can be selected from the alarm list 212, and information associated with the selected alarm event can be displayed in an alarm window 222 in the second section 204 of the web-based GUI 200.

[0025] For example, clicking the third graphic object 210 generates a drop-down menu from which a circulating compressor (including one in a hydrogen cracker at a third industrial site) can be selected, and a list of alarms associated with the circulating compressor can be displayed in alarm list 212. A first alarm event 214 (associated with the detection of secondary synchronizing friction in the circulating compressor) can be selected from alarm list 212, and information associated with the detection of secondary synchronizing friction can be displayed in alarm window 222.

[0026] Alarm information may include detected (or determined) operating parameters / operating status of the industrial machine as a function of time, alarm validity (e.g., valid, deactivated, etc.), alarm confirmation (e.g., whether the alarm event has been confirmed or not), and whether the alarm has been controlled or suspended. In some implementations, alarm information may include a graph 224 of the operating parameters / operating status as a function of time, which can be displayed in alarm window 222. Alarm information may include the case management status of the alarm event, which may include case validity (e.g., new, open, closed), assignment status (e.g., to whom the alarm event has been assigned), associated alarm events, and comments / notes associated with the alarm.

[0027] Users interacting with the web-based GUI 200 can view alarm events and associated alarm information, and decide to assign the viewing of alarm events to a second user. The web-based GUI 200 allows the user to communicate with the second user and provide the second user with the necessary information to perform the viewing. This can be done, for example, by generating an alarm event report. The web-based GUI 200 includes an interactive graphical object 230 that can be used to generate alarm event reports. In some implementations, the user can select a subset of alarm information to be included in the alarm report (e.g., alarm information available in alarm window 222). Details regarding the generation of alarm reports are described below.

[0028] Enterprise monitoring systems can monitor the operation of industrial machines throughout an industrial enterprise. For example, an enterprise monitoring system can communicatively connect to the monitoring systems of the entire industrial enterprise, receive alarm event information of industrial machines from its respective monitoring systems, and present the alarm event information through a web-based GUI (e.g., web-based GUI 200). Figure 3 An exemplary enterprise monitoring system 300 for an industrial enterprise is illustrated. The enterprise monitoring system 300 may include a processor 302, a memory 304, and a data storage device 306. The enterprise monitoring system 300 can generate multiple web-based GUIs. The enterprise monitoring system 300 can communicate with multiple monitoring systems associated with different industrial sites. For example, a first monitoring system 310 and a second monitoring system 330 may be configured to monitor industrial machine 370 and industrial machine 380, respectively. Monitoring systems 310 and 330 can be communicatively coupled to the enterprise monitoring system 300.

[0029] Each web-based GUI can be presented to users of the monitoring system. In some implementations, the web-based GUI can be presented to users via a display device of a computing system communicatively connected to the enterprise monitoring system 300 via the World Wide Web. For example, a first web-based GUI (e.g., web-based GUI 200) can be presented to a first user via a first user computing device 350, and a second web-based GUI (e.g., web-based GUI 200) can be presented to a second user via a second user computing device 360. Figure 2 The document describes an exemplary first / second network-based GUI.

[0030] The first user computing device 350 (second user computing device 360) may be communicatively connected to the first monitoring system 310 (second monitoring system 330) (e.g., via the World Wide Web). In some embodiments, the user computing devices (e.g., the first computing device 350, the second computing device 360, etc.) may be included in the monitoring system (e.g., the first monitoring system 310, the second monitoring system 330, etc.).

[0031] The first monitoring system 310 may include components configured to display, process, and analyze data. As shown, the first monitoring system 310 (second monitoring system 330) includes a communication component 314 (communication component 334), a processor 316 (processor 336), a memory 318 (memory 338), a data storage device 320 (data storage device 340), an input / output (I / O) port 322 (input / output (I / O) port 342), etc. The communication component may be a wireless or wired communication component that facilitates communication between the corresponding monitoring system, the enterprise monitoring system 300, and the sensor connected to an industrial machine (e.g., first industrial machine 370, second industrial machine 380, etc.) monitored by the corresponding monitoring system (e.g., first monitoring system 310, second monitoring system 330, etc.). The processor may be any type of computer processor or microprocessor capable of executing computer-executable code. The memory and data storage device may be any suitable article of manufacture that can be used as a medium for storing processor-executable code, data, etc. The processor can be configured to generate a graphical user interface (GUI) configured for display on a display device of the monitoring system or a user computing device. GUI 312 (GUI 332) may include visualizations representing industrial machines / sensors in an industrial site monitored by the condition monitoring system 310. Therefore, a user of the monitoring system 310 (monitoring system 330) can monitor the health or status of the first industrial machine 370 (second industrial machine 380) via GUI 312 (GUI 332). GUI 100 is an example of GUI 312 or GUI 332.

[0032] Figure 4 This is a flowchart 400 of an exemplary method for managing industrial assets through an industrial enterprise's enterprise monitoring system. At step 402, data characterizing alarm event reports associated with a first industrial machine (e.g., a circulating compressor) may be generated by a first user via a first web-based graphical user interface (e.g., a web-based GUI 200). The web-based GUI 200 is associated with (e.g., communicatively connected to) an enterprise monitoring system 300 that includes the first industrial asset. In some implementations, a data storage device 306 of the enterprise monitoring system may store an event dataset including information associated with various alarm events in the industrial enterprise. For example, an event dataset associated with alarm events of the first industrial machine may be stored in the data storage device 306.

[0033] In some implementations, the monitoring system may detect alarm events and generate a local event dataset (e.g., stored in local data storage devices 320 / 340) that includes various information associated with the alarm. The monitoring system may provide the local event dataset to the enterprise monitoring system 300, which may be stored as an event dataset in data storage device 306. In some implementations, the local event dataset may be large, and sending the entire local event dataset to the enterprise monitoring system 300 may be inefficient. In this case, a portion of the local event dataset may be sent to the enterprise monitoring system 300. For example, the enterprise monitoring system 300 may request that a portion of the local event dataset be transferred to data storage device 306. Additionally or alternatively, a low-resolution copy of the local event dataset may be sent to the enterprise monitoring system.

[0034] As described above, a first industrial machine can be selected from the first portion 202 of the first web-based GUI 200, and an alarm event 214 associated with the first industrial machine (e.g., secondary synchronous friction detected) can be selected from the alarm list 212. Based on the selection of alarm event 214, the corresponding alarm information can be displayed in the alarm window 222. This can be achieved, for example, by retrieving the alarm information (e.g., secondary synchronous friction detected) from an event dataset associated with the selected alarm event and stored in the data storage device 306.

[0035] The first user can generate an alarm event report based on interaction with the interactive graphical object 230. For example, the first user can click on the interactive graphical object 230, which can be displayed in a web-based GUI 200 (such as...). Figure 5 A dialog box 500 is generated in the dialog box 500 (shown in the diagram). The first user can select a portion of the alarm information (e.g., displayed in the alarm window 222) and request the generation of an alarm event report including the selected information. The user can select the portion of the alarm information by interacting with interactive graphical objects 502, 504, etc., in the dialog box 500. For example, the user can select fault condition 226 using interactive graphical object 502, and select graph 224 in the alarm window 222 using interactive graphical object 502. In some implementations, specific information associated with the alarm event (e.g., the name of the first industrial machine, the location of the first industrial machine, etc.) can be automatically added to the alarm event report.

[0036] A first user may (e.g., by interacting with a graphical object 506 in dialog box 500) request the generation of an alarm event report that includes a selected portion of alarm information. In other words, the alarm event report includes a portion of the event dataset associated with the selected alarm event (e.g., secondary synchronous friction detected). The selected portion of the alarm information may also include the location of a first industrial machine, the alarm level associated with the alarm event, operating parameters of the first industrial machine, etc. In some implementations, the alarm event report may be stored in data storage device 306. The alarm event report may include the identity of a second user, whom the first user may wish to designate to handle the selected alarm event. For example, the alarm event report may include contact information (e.g., email address), an identifier assigned to the second user (e.g., by the enterprise monitoring system 300), etc.

[0037] Return to Figure 4 At step 404, (e.g., based on the identity of the second user) an alarm event report may be provided to a second web-based graphical user interface (GUI) associated with the enterprise monitoring system. For example, the enterprise monitoring system 300 may provide the alarm event report to the second user via a second web-based graphical user 362 in the second user's computing device 360. In some implementations, the second web-based GUI may include a portion of the alarm event report (e.g., a portion of the alarm event report for which the first user has already granted access rights to the second user).

[0038] Alarm event reports may include access permissions granted to a second user (e.g., alarm management rights, database management rights, etc.). Alarm management rights may allow the second user to access the monitoring system that monitors alarm events for the first industrial machine and determine the second user's access level (e.g., actions that can be taken in response to an alarm event). For example, an alarm event may be associated with a first industrial machine 370 monitored by a first monitoring system 310. Alarm event reports may allow a second user (e.g., associated with a second monitoring system 330) to access the first monitoring system and respond to alarm events. Alarm event reports may restrict the second user's access to actions / data in the first monitoring system 310. For example, the second user may access data for selected industrial machines monitored by the first monitoring system, or the second user may perform a set of permitted operations / actions (e.g., suspend an alarm event, reset an alarm count (e.g., the number of alarms that have occurred), acknowledge an alarm event, etc.).

[0039] Database management rights can determine the types of information that a second user can edit associated with an alarm event (e.g., changes that a user can make to alarm event reports / event datasets in data storage device 306). For example, a second user can be authorized to access (e.g., read) a first part of an alarm event report; a second user can be authorized to make changes to a second part of an alarm report (e.g., edit, delete, etc.), etc.

[0040] A second user can view alarm events presented on a second web-based GUI 362. The second user may decide to use the monitoring system to view alarm event reports. For example, the second user might want to switch from the second web-based GUI 362 to the GUI 332 associated with the monitoring system 330. Switching from the second web-based GUI 362 to the monitoring system's GUI 332 might be desirable because the latter offers a larger suite of tools for viewing and evaluating alarm events. For example, the monitoring system's GUI may include plotting tools and data viewing tools that might not be available in the second web-based GUI. In some implementations, the monitoring system's GUI may access information associated with alarm events that is not included in the alarm event reports. For example, if an industrial machine (e.g., industrial machine 380) associated with an alarm event report is monitored by a monitoring system (e.g., monitoring system 330), it might be desirable to work in the GUI associated with the monitoring system (e.g., GUI 332) because it may allow the second user to access more information (e.g., high-resolution data) associated with alarm events that are not available in the alarm event reports.

[0041] To switch from the second web-based GUI 362 to the monitoring system's GUI, the second user may request the enterprise monitoring system 300. The monitoring system 300 may receive data representing a request to switch from the second web-based GUI 362 to the monitoring system 330's GUI 332, and provide the monitoring system 330 with access to alarm event reports (or at least a portion of the event dataset) in the data storage device 306 via its GUI. In some implementations, the monitoring system 330's GUI 332 may be displayed on the second user's computing device (e.g., on the display of the second user's computing device 360).

[0042] Return to Figure 4At step 406, the second user may receive data representing additional information associated with the alarm event and / or edits to the event dataset via the monitoring system's GUI (e.g., GUI 332 of monitoring system 330). In some implementations, the second user may add additional information associated with the alarm event, which is generated at the monitoring system's GUI. For example, GUI 332 of monitoring system 300 may be used to generate new graphs associated with the alarm event (e.g., using plotting tools available in the monitoring system's GUI). Figure 6 An example of GUI 332 is shown. A second user can request storage of additional information associated with an alarm event through window 600 in GUI 332. Window 600 may include a comment section 602 from which the second user can add new comments (e.g., based on the second user's view) to the alarm event report (or a modified alarm event report). Window 600 may include a graphical object 604 through which the second user can change the alarm priority (e.g., high, low, satisfied, dissatisfied, etc.). Window 600 may include a second graphical object 606 through which the second user can determine the timeline for the next view (e.g., when the next view should be performed). After creating additional information through window 600, the additional information can be saved in data storage device 306 by clicking a third interactive graphical object 608.

[0043] A second user may request that additional data associated with an alarm event (e.g., operating parameters of a first industrial machine available at monitoring system 330 but not included in the alarm event report / event dataset in data storage device 306) be added to the alarm event report / event dataset in data storage device 306. The second user may also request to change data values ​​in the alarm event report / event dataset (e.g., fault condition, alarm confirmation, etc.). As described above, the second user's ability to request changes to the alarm event report / event dataset may be based on the access level granted to the second user by the first user. Requests from the second user (e.g., data including additional information associated with the alarm event, editing of the event dataset / alarm event report, etc.) may be received by the enterprise monitoring system 300.

[0044] At step 408, additional information characterizing the alarm event may be stored in the data in data storage device 306, or an existing event dataset / alarm event report stored in database 306 may be modified. In some embodiments, a modified alarm event report associated with the first industrial machine may be generated and stored in data storage device 306. The modified alarm event report may include additional information and portions of previous alarm event reports / event datasets. The additional information in the modified alarm event report may be received via a monitoring system GUI (e.g., GUI 332).

[0045] In some implementations, a second user may designate a third user to further view the alert event. For example, the second user may communicate with the third user (e.g., via the monitoring system GUI 332, a second web-based GUI 362, etc.) and provide the third user with the necessary information to perform the viewing. This can be achieved, for example, by providing the third user with a modified alert event report or a previous alert event report (e.g., generated by the first user). In some implementations, the modified alert report may include the identity of the third user, whom the second user may wish to designate to handle selected alert events. For example, the modified alert event report may include contact information (e.g., email address), an identifier assigned to the third user (e.g., assigned by the enterprise monitoring system 300), etc. The enterprise monitoring system may identify and communicate with the third user based on the identity of the third user in the modified alert event report. Figure 4 As described in steps 406 and 408, the third user can provide new information associated with the alarm event, which can be stored in the data storage device 306 (e.g., as a second modified alarm event report) or used to edit existing modified alarm event reports, alarm event reports, event datasets, etc.

[0046] Certain exemplary embodiments are described to provide a comprehensive understanding of the principles of structure, function, manufacture, and use of the systems, apparatuses, and methods disclosed herein. One or more examples of these embodiments are illustrated in the accompanying drawings. It will be understood by those skilled in the art that the systems, apparatuses, and methods specifically described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments, and that the scope of the invention is defined only by the claims. Features shown or described in conjunction with one exemplary embodiment may be combined with features of other embodiments. Such modifications and variations are intended to be included within the scope of the invention. Furthermore, in this disclosure, similarly named components of embodiments generally have similar features, and therefore, within a specific embodiment, not every feature of every similarly named component is necessarily fully described.

[0047] The subject matter described herein may be implemented in analog electronic circuits, digital electronic circuits and / or computer software, firmware or hardware (including the structural means disclosed herein and their structural equivalents) or combinations thereof. The subject matter described herein may be implemented as one or more computer program products, such as those tangibly embodied in an information carrier (e.g., embodied in a machine-readable storage device) or embodied in a propagated signal, for execution by or control of the operation of a data processing device (e.g., a programmable processor, a computer, or multiple computers). A computer program (also referred to as a program, software, software application, or code) may be written in any form of programming language (including compiled or interpreted languages) and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for a computing environment. A computer program does not necessarily correspond to a file. A program may be stored as a portion of a file containing other programs or data, in a single file dedicated to the program under consideration, or in multiple co-located files (e.g., a file storing portions of one or more modules, subroutines, or code). Computer programs can be deployed to run on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0048] The processes and logical flows described in this specification, including the method steps of the subject matter herein, can be executed by one or more programmable processors that execute one or more computer programs to perform the functions of the subject matter herein by manipulating input data and generating output. These processes and logical flows can also be executed by special-purpose logic circuitry (e.g., FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits)), and the devices of the subject matter herein can be implemented as special-purpose logic circuitry (e.g., FPGAs or ASICs).

[0049] By way of example, processors suitable for executing computer programs include both general-purpose microprocessors and special-purpose microprocessors, as well as any one or more processors in any kind of digital computer. Generally, a processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or operatively coupled to receive data from or / and transfer data to one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable magnetic disks); magneto-optical disks; and optical disks (e.g., CDs and DVDs). The processor and memory may be supplemented by or incorporated into special-purpose logic circuitry.

[0050] To provide interaction with the user, the subject matter described herein can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user, and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user. For example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user can be received in any form, including sound, speech, or tactile input.

[0051] The techniques described herein can be implemented using one or more modules. As used herein, the term "module" refers to computing software, firmware, hardware, and / or various combinations thereof. However, at a minimum, a module should not be construed as software not implemented on hardware, firmware, or documented on a non-transitory processor-readable storage medium (i.e., a module itself is not software). In practice, a "module" will be interpreted as always including at least some physical non-transitory hardware, such as a processor or part of a computer. Two different modules may share the same physical hardware (e.g., two different modules may use the same processor and network interface). Modules described herein can be combined, integrated, separated, and / or replicated to support a variety of applications. Additionally, instead of functions performed at a particular module, or functions performed at a particular module, the functions described herein as performing at a particular module may be performed at one or more other modules and / or by one or more other devices. Furthermore, modules may be implemented locally or remotely across multiple devices and / or other components relative to each other. Additionally, modules may be moved from one device and added to another device, and / or may be included in two devices.

[0052] The subject matter described herein can be implemented in a computing system that includes back-end components (e.g., a data server), middleware components (e.g., an application server), or front-end components (e.g., a client computer with a graphical user interface or web browser through which a user interacts with embodiments of the subject matter described herein), or any combination of such front-end, middleware, and front-end components. Components of the system can be interconnected via any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks (“LANs”) and wide area networks (“WANs”), such as the Internet.

[0053] As used herein throughout the specification and claims, approximate language may be used to modify any quantitative expression that may vary but does not result in a change in the essential function associated with it. Therefore, values ​​modified by one or more terms such as “about,” “approximately,” and “substantially” should not be limited to the specified precise value. In at least some cases, approximate language may correspond to the precision of the instrument used to measure the value. Scope limitations may be combined and / or interchanged herein and throughout the specification and claims, and unless otherwise indicated by context or language, such scopes are identified and include all subscopes contained therein.

[0054] Based on the above embodiments, those skilled in the art will understand other features and advantages of the present invention. Therefore, except as indicated in the appended claims, this application is not limited to the content specifically shown and described. All publications and references cited herein are expressly incorporated in their entirety by reference.

Claims

1. An industrial asset management method, the method comprising: The system receives data characterizing alarm event reports associated with a first industrial machine, the alarm event reports being generated by a first user via a web-based first graphical user interface (GUI), the first GUI being associated with an enterprise monitoring system of the industrial enterprise including the first industrial machine. The alarm event report includes at least a portion of an event dataset, which includes information about alarm events associated with the first industrial machine, and the identity of a second user designated by the first user to handle the alarm event report. The event dataset is stored in a database associated with the enterprise monitoring system; The alarm event report is provided to a web-based second graphical user interface (GUI) associated with the enterprise monitoring system; The first monitoring system receives data representing additional information associated with the alarm event through its first GUI; The data representing additional information associated with the alarm event is stored in the event dataset in the database; A modified alarm event report associated with the first industrial machine is generated through the first GUI of the first monitoring system. The modified alarm event report is based at least on the additional information, wherein the modified alarm event report includes at least the additional information received through the first GUI and the identity of a third user designated by the second user to process the alarm event report. The modified alarm event report is provided to a second monitoring system at a second industrial site, wherein the industrial enterprise includes the second industrial site; The second monitoring system receives data representing second additional information associated with the alarm event through its second GUI; and The database stores the second additional information that characterizes the alarm event.

2. The method according to claim 1, further comprising: Based on the interaction between the first user and one or more interactive graphical objects in a dialog box in the network-based first GUI, data representing the selection of at least a portion of the event dataset to be included in the alarm event report is received. as well as Generate an alarm event report that includes a selected portion of the information from the alarm event.

3. The method of claim 2, wherein, The information associated with the alarm event includes one or more locations of the first industrial machine, the alarm level associated with the alarm event, and the operating parameters of the first industrial machine.

4. The method according to claim 2, further comprising: The network-based second GUI receives data representing a request to switch from the network-based second GUI to the first GUI of the first monitoring system; as well as The first monitoring system provides access to at least a portion of the event dataset through its first GUI.

5. The method of claim 4, wherein, The first monitoring system is configured to monitor the operation of the first industrial machine, the monitoring including: The sensor connected to the first industrial machine at the operating location receives operational characteristics, and Generate an alarm event.

6. The method according to claim 1, further comprising: Generate the first web-based GUI comprising a first part and a second part, wherein the first part comprises a list of multiple industrial machines in the industrial enterprise; Receive data representing the selection of the first industrial machine from the list of the plurality of industrial machines; and Information associated with the alarm event of the first industrial machine is displayed in the second part of the first web-based GUI.

7. The method according to claim 6, wherein, The second part of the network-based first GUI includes a graph of the operating parameters as a function of the detection time, which is an operating parameter of the first industrial machine.

8. The method of claim 1, wherein, The alarm event report also includes an access level associated with the second user, wherein the access level determines the type of editing of information associated with the alarm event and / or the type of access to information associated with the first industrial machine stored in the database.

9. The method of claim 1, wherein, The data characterizing the additional information associated with the alarm event includes analysis of the alarm event generated through the first GUI of the first monitoring system.

10. The method according to claim 1, further comprising: Editing of the event dataset is received through the first GUI of the first monitoring system; as well as Edit the event dataset in the database.

11. An enterprise monitoring system, the system comprising: At least one data processor; A memory coupled to the at least one data processor, the memory storing instructions to cause the at least one data processor to perform an operation, the operation including: The system receives data characterizing alarm event reports associated with a first industrial machine, the alarm event reports being generated by a first user via a web-based first graphical user interface (GUI), the first GUI being associated with an enterprise monitoring system of the industrial enterprise including the first industrial machine. The alarm event report includes at least a portion of an event dataset, which includes information about alarm events associated with the first industrial machine, and the identity of a second user designated by the first user to handle the alarm event report. The event dataset is stored in a database associated with the enterprise monitoring system; The alarm event report is provided to a web-based second graphical user interface (GUI) associated with the enterprise monitoring system; The first monitoring system receives data representing additional information associated with the alarm event through its first GUI; The data representing additional information associated with the alarm event is stored in the event dataset in the database; A modified alarm event report associated with the first industrial machine is generated through the first GUI of the first monitoring system. The modified alarm event report is based at least on the additional information, wherein the modified alarm event report includes at least the additional information received through the first GUI and the identity of a third user designated by the second user to process the alarm event report. The modified alarm event report is provided to a second monitoring system at a second industrial site, wherein the industrial enterprise includes the second industrial site; The second monitoring system receives data representing second additional information associated with the alarm event through its second GUI; and The database stores the second additional information that characterizes the alarm event.

12. The system of claim 11, wherein, The operation also includes: Based on the interaction between the first user and one or more interactive graphical objects among a plurality of interactive graphical objects in a dialog box in the network-based first GUI, data representing the selection of at least a portion of the event dataset to be included in the alarm event report is received; and Generate an alarm event report that includes a selected portion of the information from the alarm event.

13. The system of claim 12, wherein, The information associated with the alarm event includes one or more locations of the first industrial machine, the alarm level associated with the alarm event, and the operating parameters of the first industrial machine.

14. The system of claim 12, wherein, The operation also includes: The network-based second GUI receives data representing a request to switch from the network-based second GUI to the first GUI of the first monitoring system; and The first monitoring system provides access to at least a portion of the event dataset through its first GUI.

15. The system of claim 14, wherein, The first monitoring system is configured to monitor the operation of the first industrial machine, the monitoring including: The sensor connected to the first industrial machine at the operating location receives operational characteristics, and Generate an alarm event.

16. The system of claim 11, wherein, The operation also includes: Generate the first web-based GUI comprising a first part and a second part, wherein the first part comprises a list of multiple industrial machines in the industrial enterprise; Receive data representing the selection of the first industrial machine from the list of the plurality of industrial machines; and Information associated with the alarm event of the first industrial machine is displayed in the second part of the first web-based GUI.

17. The system of claim 16, wherein, The second part of the network-based first GUI includes a graph of the operating parameters as a function of the detection time, which is an operating parameter of the first industrial machine.

18. The system of claim 11, wherein, The alarm event report also includes an access level associated with the second user, wherein the access level determines the type of editing of information associated with the alarm event and / or the type of access to information associated with the first industrial machine stored in the database.

19. The system of claim 11, wherein, The data characterizing the additional information associated with the alarm event includes analysis of the alarm event generated through the first GUI of the first monitoring system.

20. The system of claim 11, wherein, The operation also includes: The event dataset is edited via a first GUI of the first monitoring system; and Edit the event dataset in the database.

21. A computer program product comprising a non-transitory machine-readable medium storing instructions, the instructions, when executed by at least one programmable processor including at least one physical core and a plurality of logical cores, causing the at least one programmable processor to perform operations, the operations including: The system receives data characterizing alarm event reports associated with a first industrial machine, the alarm event reports being generated by a first user via a web-based first graphical user interface (GUI), the first GUI being associated with an enterprise monitoring system of the industrial enterprise including the first industrial machine. The alarm event report includes at least a portion of an event dataset, which includes information about alarm events associated with the first industrial machine, and the identity of a second user designated by the first user to handle the alarm event report. The event dataset is stored in a database associated with the enterprise monitoring system; The alarm event report is provided to a web-based second graphical user interface (GUI) associated with the enterprise monitoring system; The first monitoring system receives data representing additional information associated with the alarm event through its first GUI; The data representing additional information associated with the alarm event is stored in the event dataset in the database; A modified alarm event report associated with the first industrial machine is generated through the first GUI of the first monitoring system. The modified alarm event report is based at least on the additional information, wherein the modified alarm event report includes at least the additional information received through the first GUI and the identity of a third user designated by the second user to process the alarm event report. The modified alarm event report is provided to a second monitoring system at a second industrial site, wherein the industrial enterprise includes the second industrial site; The second monitoring system receives data representing second additional information associated with the alarm event through its second GUI; and The database stores the second additional information that characterizes the alarm event.

22. The computer program product of claim 21, wherein, The operation also includes: The event dataset is edited via a first GUI of the first monitoring system; and Edit the event dataset in the database.

Images