Patent Description:
A method according to the invention is defined in claim <NUM>.

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

In some implementations, the method further includes receiving data charactering selection of the at least portion of the event dataset to be included in the alarm event report based on interaction of the first user with the one or more of the plurality of interactive graphical objects in a dialog box in the first web-based GUI; and generating the alarm event report including the selected portion of the information of the alarm event. In some implementations, information of the alarm event associated with the first industrial machine includes one or more of location of the first industrial machine. An alarm level is associated with the alarm event and operating parameters of the first industrial machine.

In some implementations, the method further includes receiving, via the second web-based GUI, data characterizing a request to switch from the second web-based GUI to the first GUI of the first monitoring system; and providing the first monitoring system access to the at least a portion of the event dataset via the first GUI of the first monitoring system. In some implementations, the first monitoring system is configured to monitor the operations of the first industrial machine. The monitoring includes receiving operating characteristic from sensors operatively coupled to the first industrial machine, and generating an alarm event.

In some implementations, the method further includes generating the first web-based GUI including a first portion and a second portion. The first portion includes a list of a plurality of industrial machines in the industrial enterprise. The method also includes receiving data characterizing selection of the first industrial machine from the list of the plurality of industrial machines; and displaying in the second portion of the web-based GUI, information associated with the alarm event of the first industrial machine. In some implementations, the second portion of the web-based GUI, includes a plot of an operating parameter of the first industrial machine as a function of time of detection of the operating parameter.

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

In some implementations, the method further includes generating, via the first GUI of the first monitoring system, a revised alarm event report associated with the first industrial machine. The revised alarm event report is based at least on the additional information. The revised alarm event report at least includes the additional information received via the first GUI and an identity of a third user assigned to work on the alarm event report by the second user. The method also includes providing the revised alarm event report to a second monitoring system of a second industrial site. The industrial enterprise includes the second industrial site. The method further includes receiving, via a second GUI of the second monitoring system, data characterizing second additional information associated with the alarm event; and storing data characterizing the second additional information associated with the alarm event in the database.

Industrial machines can be monitored by monitoring systems to ensure operation within acceptable tolerances. In general, machine monitoring can include measuring operating parameters of one or more of the machine components by sensors, determining whether the machine components are operating properly from the operating parameter measurements, and issuing warnings if a machine component is determined to be operating improperly. These warnings can allow corrective action to be taken in advance of machine failure, providing benefits such as lower production costs, reduced equipment down time, improved reliability, and/or improved safety.

An industrial enterprise can include multiple industrial sites that can be geographically separated (e.g., across the globe). An industrial site can include multiple industrial machines. The industrial site can include a monitoring system configured to monitor the industrial machines at the industrial site. In the existing paradigm, a user of a first monitoring system may not be aware of alarm events at a 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 undertaken at the second monitoring to resolve the alarm event, etc.). As a result, establishing collaboration between users of different monitoring systems may be challenging. For example, the expertise of a recycle compressor expert at a first industrial site may not be leveraged to handle a failure / alarm event associated with a recycle compressor at a different industrial site.

In some implementations, the current subject matter provides for an ecosystem that allows seamless collaboration between users across different industrial sites of an industrial enterprise. This can result in an improved (e.g., optimized) asset management. For example, an enterprise monitoring system is provided that supports web-based graphical user interfaces (GUI) through which a user can monitor and manage an industrial machine located anywhere in the industrial site. The first user may seamlessly hand over the management of an alarm event of an industrial machine to a second user. The first user may also control the access level of the second user (e.g., operations that the second user can perform, alarm event data that the second user can have access to, etc.). In some implementations, the work done by first user on the alarm event can be curated and provided to the second user. This can improve the efficiency of collaboration as the first user may not have to use a different communication means (e.g., an email service) to communicate to the second user the details of the alarm event, work done on the alarm event, etc..

<FIG> is a schematic representation of an exemplary embodiment of a GUI <NUM> of a condition monitoring system associated with industrial machines at an industrial site. The GUI <NUM> 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 visual representation of the industrial machine corresponding to option selected within the first GUI portion 100A. As shown, the first GUI portion 100A includes a selection option <NUM>, primary display options 104A, secondary display options 104B, and a plurality of view spaces <NUM> having content that can dynamically change in response to the industrial machine selected via the selection option <NUM>. As shown, the selection option <NUM> can include industrial machines and condition monitoring devices (e.g., physical monitors) at the industrial site.

The primary display options 104A can include status, events, plots, and case history associated with the industrial machine or device selected from the selection option <NUM>. Status can include a condition of the selected industrial machine based upon one or more measurements acquired by the sensors or received by a third party system (e.g., Satisfactory, Unsatisfactory, Warning, Alarm, etc.) Events can be alarm or system logs that alert the user to potential component health issues (e.g., a measured parameter or exceeding a threshold value). Plots can include any graphical representation of measured data. The case history can include plots of historical data and historical reports. The secondary display options 104B can include sub-types of displays views based upon the selection option <NUM> and primary display option 104A. Examples of display sub-types can include a type of defined charting view (e.g. vibration, surge curve) and/or a type of display (e.g., list, bar graph, etc.).

The dynamic view space <NUM> can include information associated with the industrial machine selected via the selection option <NUM>. The information can include hierarchical information displayed in a hierarchical view space 106A of the dynamic view space <NUM>. The hierarchical information can include a first level associated with the site of the industrial machine, a second level associated with the process system associated with the industrial machine, a third level indicative of the type of machine, etc. The information can include operating parameters derived from measurements acquired from sensors (e.g., acceleration, temperature, speed, displacement, gap distance, etc.) associated with the selected machine. The operating parameter can be displayed in measurement view space 106B of the dynamic view space <NUM>. Under circumstances where operating parameters are displayed in the second GUI portion 100B (e.g., a plot), the displayed operating parameter can be selected from the measurement view space 106B.

The GUI <NUM> of <FIG> illustrates a visual representation in the second GUI portion 100B corresponding to selection of a machine (e.g., a recycle compressor) from the plurality of machines in the component options <NUM>, a view selected from the primary display options 104A, and a view list selected from the secondary display options 104B. The visual representation of the selected machine can include visualizations of the components of the selected machine. For example the visual representation of a recycle compressor can include a first visualization <NUM> of a motor of the recycle compressor, a second visualization <NUM> of a gearbox of the recycle compressor and a third visualization <NUM> of the compressor of the recycle compressor. The second GUI portion 100B can include an identifier (e.g., name) associated with the various components of the selected industrial machine and one or more data fields. For example, the second GUI portion 100B can include graphical objects <NUM> that display data entries <NUM> associated with a respective machine component. The data entries <NUM> can include operational parameters such as real-time measurement data (e.g., operating state of the machine, status indication, speed, etc.) received from various sensors <NUM> disposed on a respective machine component <NUM>, outputs of analyses performed by the processor based upon measurement data received from various sensors disposed on a respective machine component, or the like. GUI <NUM> further updates the measurement view space 106B to display operational parameters (e.g., acceleration, temperature, speed, displacement, gap distance, etc.) associated with a selected machine component.

<FIG> illustrates an exemplary web-based GUI <NUM>. The web-based GUI includes a first portion <NUM> and a second portion <NUM>. The first portion <NUM> includes multiple interactive graphical objects <NUM>-<NUM>. Each of the graphical objects <NUM>-<NUM> can represent an industrial site. For example, graphical object <NUM> represents a first industrial site, graphical object <NUM> represents a second industrial site, and graphical object <NUM> represents a third industrial site. An industrial machine at an industrial site can be selected from a drop-down menu that is presented in the first portion <NUM> upon interaction with the graphical object indicative of the industrial site. Upon selection of an industrial machine in the first portion <NUM>, an alarm list <NUM> (including a list of events / alarms associated with the selected industrial machine) is displayed in the second portion <NUM> of the web-based GUI <NUM>. An alarm event (e.g., one of the alarm events <NUM>-<NUM>) can be selected from the alarm list <NUM>, and information associated with the selected alarm event can be displayed in the alarm window <NUM> in the second portion <NUM> of the web-based GUI <NUM>.

As an example, clicking on the third graphical object <NUM> can generate a drop-down menu from which the recycle compressor (included in the hydrocracker at the third industrial site) can be selected and a list of alarms associated with the recycle compressor can be displayed in the alarm list <NUM>. From the alarm list <NUM>, a first alarm event <NUM> (associated with detection of sub synchronous rub in the recycle compressor) can be selected, and information associated with the sub synchronous rub detection can be displayed in the alarm window <NUM>.

The alarm information can include operating parameters / operating states of the industrial machine that has been detected (or determined) as a function of time, alarm activity (e.g., active, cleared, etc.), alarm acknowledgement (e.g. whether the alarm event has been acknowledged or not), whether the alarm has been suppressed or shelved, etc. In some implementations, alarm information can include a plot <NUM> of the operating parameters / operating state as a function of time that can be displayed in the alarm window <NUM>. The alarm information can include case management status of the alarm event that can include case activity (e.g., new, open, closed), assignment status (e.g., who the alarm event has been assigned to), associated alarm events, notes/annotations associated with the alarm, etc..

A user interacting with the web-based GUI <NUM> may review the alarm event and the associated alarm information and decide to assign the review of the alarm event to a second user. The web-based GUI <NUM> can allow the user to communicate with the second user and provide the second user with the desirable information that is needed to perform the review. This can be done, for example, by generating an alarm event report. The web-based GUI <NUM> includes an interactive graphical object <NUM> that can be used to generate the alarm event report. In some implementations, the user can select a subset of the alarm information (e.g., alarm information available in the alarm window <NUM>) to be included in the alarm report. The details of the generation of alarm report are described below.

An enterprise monitoring system can monitor the operations of industrial machines across the industrial enterprise. For example, the enterprise monitoring system is communicatively coupled with monitoring systems across the industrial enterprise and receive alarm event information of the industrial machines from their respective monitoring system, and present the alarm event information via a web-based GUI (e.g., web-based GUI <NUM>). <FIG> illustrates an exemplary enterprise monitoring system <NUM> of the industrial enterprise. The enterprise monitoring system <NUM> includes a processor <NUM>, a memory <NUM> and a data storage <NUM>. The enterprise monitoring system <NUM> generates multiple web-based GUIs. The enterprise monitoring system <NUM> communicates with multiple monitoring systems associated with different industrial sites. For example, a first monitoring system <NUM> and a second monitoring system <NUM> are configured to monitor the industrial machine <NUM> and industrial machine <NUM>, respectively. The monitoring systems <NUM> and <NUM> are communicatively coupled to the enterprise monitoring system <NUM>.

Each web-based GUI can be presented to a user of monitoring system. In some implementations, the web-based GUI can be presented to a user via a display device of a computing system communicatively coupled to the enterprise monitoring system <NUM> via the World Wide Web. For example, a first web-based GUI (e.g., web-based GUI <NUM>) can be presented to a first user via a first user computing device <NUM> and a second web-based GUI (e.g., web-based GUI <NUM>) can be presented to a second user via a second user computing device <NUM>. An exemplary first / second web-based GUI is described in <FIG> above.

The first user computing device <NUM> (second user computing device <NUM>) can be communicatively coupled to the first monitoring system <NUM> (second monitoring system <NUM>) (e.g., via the world-wide web). In some implementations, the user computing devices (e.g., first computing device <NUM>, second computing device <NUM>, etc.) can be included in the monitoring system (e.g., first monitoring system <NUM>, second monitoring system <NUM>, etc.).

The first monitoring system <NUM> can include components configured to display data, process data, and analyze data. As shown, the first monitoring system <NUM> (second monitoring system <NUM>) includes a communication component <NUM> (communication component <NUM>), a processor <NUM> (processor <NUM>), a memory <NUM> (memory <NUM>), a data storage <NUM> (data storage <NUM>), input/output (I/O) port <NUM> (input/output (I/O) ports <NUM>), and the like. The communication component can be a wireless or wired communication component that facilitates communication between the respective monitoring system and the enterprise monitoring system <NUM>, sensors coupled to the industrial machine (e.g., first industrial machine <NUM>, second industrial machine <NUM>, etc.) monitored by the respective monitoring system (e.g., first monitoring system <NUM>, second monitoring system <NUM>, etc.) and the like. The processor can be any type of computer processor or microprocessor capable of executing computer-executable code. The memory and the data storage can be any suitable articles of manufacture that can serve as media to store processor-executable code, data, or the like. The processor can be configured to generate graphical user interface (GUI) configured for display upon a display device of the monitoring system or on the user computing device. The GUI <NUM> (or GUI <NUM>) can include visualizations that represent the industrial machines / sensors in the industrial site being monitored by the condition monitoring system <NUM>. As such, users of the monitoring system <NUM> (monitoring system <NUM>) may monitor the health or status of first industrial machine <NUM> (second industrial machine <NUM>) via the GUI <NUM> (GUI <NUM>). GUI <NUM> is an example of GUI <NUM> or GUI <NUM>.

<FIG> is a flowchart <NUM> of an exemplary method of industrial asset management via an enterprise monitoring system of an industrial enterprise. At step <NUM>, data characterizing an alarm event report associated with a first industrial machine (e.g., recycle compressor) can be generated by a first user via a first web-based graphical user interface (e.g., web-based GUI <NUM>). The web-based GUI <NUM> is associated with the enterprise monitoring system <NUM> (e.g., communicatively coupled to the enterprise monitoring system <NUM>) of the industrial enterprise that includes the first industrial asset. In some implementations, the data storage <NUM> of the enterprise monitoring system can store event datasets that include information associated with various alarm events in the industrial enterprise. For example, an event dataset associated with the alarm event of the first industrial machine can be stored in the data storage <NUM>.

In some implementations, a monitoring system can detect an alarm event and generate a local event dataset (e.g., stored in local data storage <NUM> / <NUM>) that includes various information associated with the alarm. The monitoring system may provide the local event dataset to the enterprise monitoring system <NUM> that can be stored as event dataset in the data storage <NUM>. In some implementations, the local event dataset may have a large size and it may be inefficient to send the entire local event dataset to the enterprise monitoring system <NUM>. In this case, a portion of the local event dataset can be communicated to the enterprise monitoring system <NUM>. For example, the enterprise monitoring system <NUM> may request that a portion of the local event dataset is transferred to the data storage <NUM>. Additionally or alternately, a low resolution copy of the local event dataset is communicated to the enterprise monitoring system.

As discussed above, the first industrial machine can be selected from the first portion <NUM> of the first web-based GUI <NUM>, and an alarm event <NUM> associated with the first industrial machine (e.g., detection of sub synchronous rub) can be selected from the alarm list <NUM>. Based on the selection of the alarm event <NUM>, the corresponding alarm information can be displayed in the alarm window <NUM>. This can be done, for example, by retrieving the alarm information from the event dataset associated with the selected alarm event (e.g., detection of sub synchronous rub) and stored in the data storage <NUM>.

The first user can generate the alarm event report based on interaction with the interactive graphical object <NUM>. For example, the first user can click on the interactive graphical object <NUM> that can result in the generation the dialog box <NUM> in the web-based GUI <NUM> (as illustrated in <FIG>). The first user can select the portions of the alarm information (e.g., displayed in the alarm window <NUM>) and request the generation of the alarm event report that includes the selected information. The user can select portions of the alarm information via interaction with interactive graphical object <NUM>, interactive graphical object <NUM>, etc. in the dialog box <NUM>. For example, the user can select the fault conditions <NUM> via the interactive graphical object <NUM>, the plot <NUM> in the alarm window <NUM> via the interactive graphical object <NUM>, etc. In some implementations, certain information associated with the alarm event (e.g., name of the first industrial machine, location of the first industrial machine, etc.) can be automatically added to the alarm event report.

The first user can request generation of the alarm event report (e.g., by interacting the graphical object <NUM> in the dialog box <NUM>) that includes the selected portions of the alarm information. In other words, the alarm event report includes portions of the event dataset associated with the selected alarm event (e.g., detection of sub synchronous rub). The selected portions of the alarm information can further include location of the first industrial machine, an alarm level associated with the alarm event, operating parameters of the first industrial machine, etc. In some implementations, the alarm event report can be stored in data storage <NUM>. The alarm event report can include the identity of a second user to whom the first user may wish to assign to work on the selected alarm event. For example, the alarm event report can include the contact information (e.g., email address), an identifier assigned to the second user (e.g., by the enterprise monitoring system <NUM>), etc..

Returning back to <FIG>, at step <NUM>, the alarm event report can be provided to the second web-based graphical user interface (GUI) associated with the enterprise monitoring system (e.g., based on the identity of the second user). For example, the enterprise monitoring system <NUM> can provide the alarm event report to the second user via a second web-based graphical user <NUM> in a second user computing device <NUM>. In some implementations, the second web-based GUI can include a portion of the alarm event report (e.g., the portion of the alarm event report to which the second user has been provided access to by the first user).

The alarm event report can include the access (e.g., alarm management rights, database management rights, etc.) provided to the second user. The alarm management rights can allow the second user to access the monitoring system that monitors the alarm event of the first industrial machine, and determine the access level (e.g., actions that can be taken to respond to the alarm event) of the second user. For example, the alarm event can be associated with the first industrial machine <NUM> that is monitored by the first monitoring system <NUM>. The alarm event report can allow the second user (e.g., associated with the second monitoring system <NUM>) to have access to the first monitoring system and respond to the alarm event. The alarm event report can limit the access of the second user to actions / data in the first monitoring system <NUM>. For example, the second user may have access to the data of a selected industrial machines monitored by the first monitoring system, or the second user can perform an allowed set of operations / actions (e.g., shelve the alarm event, reset the alarm count (e.g., number of times the alarm has occurred), acknowledge the alarm event, etc.).

The database management rights can determine a type of edit that the second user can make to the information associated with alarm event (e.g., changes that the user can make to the alarm event report / event dataset in the data storage <NUM>). For example, the second user may be authorized to access (e.g., read) a first portion of the alarm event report; the second user may be authorized to make changes (e.g., edit, delete, etc.) to a second portion of the alarm report, etc..

The second user can review the alarm event presented on the second web-based GUI <NUM>. The second user may decide to review the alarm event report using a monitoring system. For example, the second user may want to switch from the second web-based GUI <NUM> to the GUI <NUM> associated with the monitoring system <NUM>. Switching from the second web-based GUI <NUM> to the GUI <NUM> of the monitoring system may be desirable as the latter can provide a larger suite of tools to review and assess the alarm event. For example, the GUI of the monitoring system can include plotting tools, data viewing tools that may not be available in the second web-based GUI. In some implementations, the GUI of the monitoring system may have access to information associated with the alarm event this is not included in the alarm event report. For example, if the industrial machine associated with the alarm event report (e.g., industrial machine <NUM>) is monitored by the monitoring system (e.g., monitoring system <NUM>), it might be desirable to work in the GUI (e.g., GUI <NUM>) associated with the monitoring system as it may allow, the second user to have access to more information associated with the alarm event (e.g., high resolution data) that is not available in the alarm event report.

In order to switch from the second web-based GUI <NUM> to the GUI of the monitoring system, the second user can request the enterprise monitoring system <NUM>. The monitoring system <NUM> can receive data characterizing the request to switch from the second web-based GUI <NUM> to the GUI <NUM> of the monitoring system <NUM>, and providing the monitoring system <NUM> access to alarm event report (or at least a portion of the event dataset) in the data storage <NUM> via the GUI of the monitoring system. In some implementations the GUI <NUM> of the monitoring system <NUM> can be displayed on the second user's computing device (e.g., on the display of the second user computing device <NUM>).

Returning back to <FIG>, at step <NUM>, data characterizing additional information associated with the alarm event and/or edits to the event dataset can be received from the second user via GUI of the monitoring system (e.g., GUI <NUM> of monitoring system <NUM>). In some implementations, the second user can add additional information associated with the alarm event that is generated at the GUI of the monitoring system. For example, GUI <NUM> of the monitoring system <NUM> can be used to generate new plot(s) associated with the alarm event (e.g., generated using plotting tools available in the GUI of the monitoring system). <FIG> illustrates an example of the GUI <NUM>. The second user can request storing additional information associated with the alarm event via the window <NUM> in the GUI <NUM>. The window <NUM> can include a comment portion <NUM> from which the second user can add new comments (e.g., based on the review of the second user) to the alarm event report (or to a revised alarm event report). The window <NUM> can include a graphical object <NUM> via which the second user can change the alarm priority (e.g., high, low, satisfactory, unsatisfactory, etc.). The window <NUM> can include a second graphical object <NUM> via which the second user can determine the time line for next review (e.g., when the next review should be performed). After the additional information is prepared via the window <NUM>, the additional information can be saved in the data storage <NUM> by clicking on the third interactive graphical object <NUM>.

The second user may request that the additional data associated with the alarm event (e.g., operational parameter of the first industrial machine that is available at the monitoring system <NUM> and not included in the alarm event report / event dataset in the data storage <NUM>) is added to the alarm event report / event dataset in the storage <NUM>. The second user may request changing data values (e.g., fault condition, alarm acknowledgement, etc.) in the alarm event report / event dataset. As discussed above, the ability of the second user to request changes to the alarm event report / event dataset can be based on the access level provided to the second user by the first user. The request from the second user (e.g., including data characterizing additional information associated with the alarm event, edits to the event dataset / alarm event report, etc.) can be received by the enterprise monitoring system <NUM>.

At step <NUM>, data characterizing additional information associated with the alarm event can be stored in data in the data storage <NUM> or existing event dataset / alarm event report stored in the database <NUM> can be revised. In some implementations, a revised alarm event report associated with the first industrial machine can be generated and stored in the data storage <NUM>. The revised alarm event report can include the additional information, portions of the previous alarm event report / event dataset. The additional information in the revised alarm event report can be received via the monitoring system GUI (e.g., GUI <NUM>).

In some implementations, the second user may assign a third user for further review of the alarm event. For example, the second user can communicate to the third user (e.g., via the monitoring system GUI <NUM>, the second web-based GUI <NUM>, etc.) and provide the third user with the desirable information needed to perform the review. This can be done, for example, by providing the third user with the revised alarm event report, the previous alarm event report (e.g., generated by the first user). In some implementations, the revised alarm report can include the identity of the third user to whom the second user may wish to assign to work on the selected alarm event. For example, the revised alarm event report can include the contact information (e.g., email address), an identifier assigned to the third user (e.g., by the enterprise monitoring system <NUM>), etc. The enterprise monitoring system can identify and communicate with the third user based on the identity of the third user in the revised alarm event report. As described in steps <NUM> and <NUM> of <FIG>, the third user can provide new information associated with the alarm event that can be stored in the data storage <NUM> (e.g., as a second revised alarm event report), or can be used to edit the existing revised alarm event report, alarm event report, event dataset, etc..

Certain exemplary embodiments have been described to provide an overall understanding of the principles of the structure, function, manufacture, and use of the systems, devices, and methods disclosed herein. One or more examples of these embodiments have been illustrated in the accompanying drawings. Those skilled in the art will understand that the systems, devices, and methods specifically described herein and illustrated in the accompanying drawings are nonlimiting exemplary embodiments and that the scope of the present invention is defined solely by the claims.

The subject matter described herein can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such w-end, middleware, and front-end components.

Claim 1:
A method (<NUM>) comprising:
receiving (<NUM>) data characterizing an alarm event report associated with a first industrial machine (<NUM>) generated by a first user via a first web-based graphical user interface (GUI) (<NUM>), the first web-based GUI (<NUM>) associated with an enterprise monitoring system (<NUM>) of an industrial enterprise that includes the first industrial machine (<NUM>), the enterprise monitoring system (<NUM>) being configured to monitor the operations of industrial machines across the industrial enterprise,
wherein the alarm event report includes at least a portion of an event dataset including information of an alarm event associated with the first industrial machine (<NUM>), and an identity of a second user assigned to work on the alarm event report by the first user,
wherein the event dataset is stored in a database (<NUM>) associated with the enterprise monitoring system (<NUM>);
providing (<NUM>) the alarm event report to a second web-based graphical user interface (GUI) (<NUM>) associated with the enterprise monitoring system (<NUM>);
receiving (<NUM>), via a first GUI (<NUM>) of a first monitoring system (<NUM>) configured to monitor the first industrial machine (<NUM>), data characterizing additional information associated with the alarm event and/or edits to the event dataset; and
storing (<NUM>) data characterizing additional information associated with the alarm event in the event dataset in the database (<NUM>) and/or editing the event dataset in the database (<NUM>).