Methods and systems for managing execution of standard operating procedures by an operator to address alarms generated by a facility management system

0001This is a continuation of co-pending U.S. patent application Ser. No. 16/888,352, filed May 29, 2020, which is incorporated herein by reference.

TECHNICAL FIELD

0002The disclosure relates generally to facility management systems, and more particularly to methods and systems for managing execution of standard operating procedures by an operator to address alarms generated by the facility management systems.

BACKGROUND

0003Large facility management systems typically include a computer system programmed for processing input from numerous alarm sensors distributed throughout a facility (e.g., an airport, a hospital, a campus, a shopping mall, a group of buildings, an office building, etc.). The alarm sensors are configured to detect troubling events, such as a fire, a card reader failure, HVAC equipment failure or degradation, vandalism, security breaches, and the like. Some alarm sensors are video cameras, wherein the computer system applies video analytics for recognizing troubling events such as vandalism, accidents, trespassing, and the presence of unauthorized individuals.

0004The alarms are typically displayed on an operator console, often in real time. An operator must typically decide how to effectively address each incoming alarm. It can be difficult for the operator to properly deal with each of the alarms, particularly in a timely manner, when the operator is deluged with a flood of alarms from the facilities management system.

SUMMARY

0005The present disclosure generally pertains to a computer assisted facility monitoring method for providing a user with predefined operating procedures that are tailored for addressing one or more specific alarms acknowledged by the user. The predefined operating procedures are created and stored prior to the occurrence of the alarms. These predefined operating procedures may be considered Standard Operating Procedures, or SOPs.

0006In some examples of the disclosure, a facility monitoring method includes displaying a plurality of alarm notifications corresponding to a plurality of troubling events and providing a user with an option for acknowledging at least one of the alarm notifications. In response to the user acknowledging at least one alarm notification, the user is presented with a predefined operating procedure for the acknowledged alarm notification(s). The predefined operating procedure includes at least one recommended action step to address the corresponding troubling event, and the user can then perform the recommended action step(s).

0007In some examples of the disclosure, a facility monitoring method includes a computer storing a plurality of predefined operating procedures including a first predefined operating procedure with at least one recommended action step for addressing a first troubling event. The computer displays a plurality of alarm notifications corresponding to the plurality of troubling events, and the plurality of alarm notifications includes a first alarm notification for the first troubling event. The computer enables the user to acknowledge at least the first alarm notification. When the user acknowledges the first alarm notification, the computer provides the user with a choice between a first option of proceeding with the first predefined operating procedure and a second option of bypassing the first predefined operating procedure. When the user chooses the first option, the computer presents the user with at least one recommended action step to address the first troubling event. When the user chooses the second option, the first alarm notification is dismissed.

0008In some examples of the disclosure, facility monitoring method includes storing a plurality of predefined operating procedures including a first predefined operating procedure with a plurality of recommended action steps for addressing a first troubling event. The facility monitoring method displays a plurality of alarm notifications corresponding to the plurality of troubling events, wherein the plurality of alarm notifications includes a first alarm notification for the first troubling event. The user is enabled to acknowledge at least the first alarm notification. When the user acknowledges the first alarm notification, the user is presented with the first predetermined operating procedure along with its plurality of recommended action steps for addressing the first troubling event. The user can clear the first alarm notification when the plurality of recommended action steps have been completed. Alternatively, the user can clear the first alarm notification even if the plurality of recommended action steps are uncompleted, provided the user enters into the computer an explanation as to why the plurality of recommended action steps need not be completed.

0009In some examples of the disclosure, in response to acknowledging an alarm occurrence, the user may be provided with an option for bypassing or disregarding the alarm, as some such acknowledgements may have been for false alarms.

0010In some examples of the disclosure, the predefined operating procedure may specify multiple action steps for addressing an alarm. In such examples, the user can close out or settle an alarm incident even without completing all of the action steps, provided the user enters a reason for doing so.

0011In some examples of the disclosure, the user can check off individual action steps as they are completed, and a progress of completion indicator illustrates how many of the action steps have been completed and how many more still need to be done.

0012In some examples of the disclosure, a user can batch-select a group of alarms, wherein perhaps only some of the acknowledged alarms in the group have corresponding predefined operating procedures.

0013The preceding summary is provided to facilitate an understanding of some of the features of the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings and abstract as a whole.

BRIEF DESCRIPTION OF THE DRAWINGS

0014The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments of the disclosure in connection with the accompanying drawings in which:

0015<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a schematic block diagram of an example facility management system;

0016<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a view of an example Alarm Acknowledgement screen of a facility monitoring method;

0017<figref idref="DRAWINGS">FIG. <b>3</b></figref> is a view of an example Incident Action screen of a facility monitoring method;

0018<figref idref="DRAWINGS">FIG. <b>4</b></figref> is a view of an example Incident Dismissal window of a facility monitoring method;

0019<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a view of an example Incident Confirmation window of a facility monitoring method;

0020<figref idref="DRAWINGS">FIG. <b>6</b></figref> is a view of an example Incident Activation window of a facility monitoring method;

0021<figref idref="DRAWINGS">FIG. <b>7</b></figref> is a view of an example Incident Status window of a facility monitoring method; and

0022<figref idref="DRAWINGS">FIG. <b>8</b></figref> is a view of an example Clear Incident screen of a facility monitoring method.

0023While the disclosure is amendable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular illustrative embodiments described herein. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

DESCRIPTION

0024The following description should be read with reference to the drawings wherein like reference numerals indicate like elements throughout the several views. The description and drawings show several examples that are meant to be illustrative of the disclosure.

0025In some examples, the disclosure pertains to a computer assisted facility monitoring method for providing a user with predefined operating procedures that are recommended for addressing one or more alarms acknowledged by the user. The predefined operating procedures are created prior to the occurrence of the alarms. In some examples, after acknowledging an alarm occurrence, the user may be provided with an option for bypassing or disregarding the alarm, as some such acknowledgements may have been for false alarms. In some examples, the predefined operating procedure may specify multiple action steps for addressing an alarm. In such examples, the user can close out or settle an alarm incident even without completing all of the action steps, provided the user gives a valid reason for doing so. In some examples, a user can batch-select a group of alarms, wherein perhaps only some of the acknowledged alarms in the group have corresponding predefined operating procedures. In some examples, the user can check off individual action steps as they are completed, and a progress of completion indicator illustrates how many of the action steps have been completed and how many more still need to be done for each alarm.

0026<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a schematic diagram illustrating one example of a facility management system <b>10</b> for a facility <b>14</b>. The disclosure uses a facilities management system <b>10</b> as an example, which may include an HVAC system, a security system, a fire system, a lighting system, an industrial process control system, and/or any other suitable facility management system. The facility may include a commercial or residential building, a factory, a power plant, an airplane, a ship, or any other suitable facility. It is contemplated that the present disclosure may be applied to any application where alarms are generated and acknowledged by an operator.

0027The facility management system <b>10</b> may implement a facility monitoring method for providing a user <b>18</b> with a predefined operating procedure <b>16</b> for addressing troubling events <b>12</b> that might occur at the facility <b>14</b>. The term “predefined operating procedure” refers to one or more recommended action steps for addressing a troubling event, wherein the recommended action steps were determined ahead of time, i.e., prior to the occurrence of the troubling event. These predefined operating procedures may be considered Standard Operating Procedures, or SOPs. In this example, facility management system <b>10</b> involves the use of a computer system <b>22</b>, a display <b>24</b> associated with computer system <b>22</b>, and a plurality of sensors <b>26</b> for generating alarm signals <b>28</b> in response to detecting one or more troubling events <b>12</b> at facility <b>14</b>.

0028The term “facility” refers to any designated area such as, for example, a part or zone of a building, a single building, a group of buildings, an airport, a campus, a predefined outdoor area, a park, fairgrounds, a worksite, a parking lot, a neighborhood, etc. The term “troubling event” refers to the occurrence of a possible problem of concern at the facility. Some examples of troubling events <b>12</b> may include an alarm triggered event, an observed problem, a reported problem, etc. An observed or reported problem can be any troubling event witnessed by someone that verbally or otherwise notifies user <b>18</b>.

0029The term “user” refers to one or more people associated with monitoring or addressing the security, safety, maintenance, and/or operation of a facility. Some example users include an operator, a supervisor, an administrator, security personnel, parking attendants, transportation security attendants, and maintenance workers. In some examples, a user comprises two or more individuals, wherein one individual does one action and a second individual does another action.

0030An alarm triggered event is any occurrence that causes at least one sensor <b>26</b> to generate at least one alarm signal <b>28</b>. Some example sensors <b>26</b> for generating alarm signals <b>28</b> include a smoke detector, a fire detector, a card reader, a badge reader, a proximity switch, a motion detector, a temperature sensor, a humidity sensor, a current and/or voltage sensor, a microphone, a light sensor, a contact witch, a video camera, etc. Alarm signal <b>28</b> is any physical, electrical or visual communication that indicates that something wrong, abnormal or unexpected has occurred. Some examples of alarm-triggered events include a fire, an HVAC degradation or failure, other equipment degradation or failures, a breakage of equipment, an improper use of a door, a badge detection failure, trespassing, theft, vandalism, a security breach, and/or the video detection of an unexpected or unauthorized individual in a certain area.

0031Computer system <b>22</b> is schematically illustrated to represent one or more digital components with a computer readable medium <b>34</b> having stored thereon, in a non-transitory state, an executable program code that, when executed, causes certain intended physical outcomes. Some examples of such physical outcomes include displaying information on display <b>24</b> (e.g., one or more computer monitors), receiving and processing input alarm signals <b>28</b>, and responding to input from user <b>18</b> via mouse-clicks, keyboard entries, touchscreen inputs, etc.

0032The term, “computer readable medium” refers to any device for storing information for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, for caching of the information, etc). The term, “program code” refers to executable instructions (e.g., computer readable instruction, machine readable instructions, software, etc.). The term, “non-transitory computer readable medium” is specifically defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media.

0033In some examples, computer system <b>22</b> may include a memory <b>32</b> for storing predefined operating procedures <b>16</b>. In some examples, one or more portions of memory <b>32</b> and/or other portions of computer system <b>22</b> may be remotely located but accessible through an internet connection or through some other known communication link.

0034In some examples of facility management system <b>10</b>, computer system <b>22</b> controls display <b>24</b> to provide user <b>18</b> with various informative and/or interactive screens and popup windows, such as those shown in <figref idref="DRAWINGS">FIGS. <b>2</b>-<b>8</b></figref>. Some examples may include an Alarm Acknowledgement screen <b>20</b> (<figref idref="DRAWINGS">FIG. <b>2</b></figref>), an Incident Action screen <b>30</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>), an Incident Dismissal window <b>40</b> (<figref idref="DRAWINGS">FIG. <b>4</b></figref>), an Incident Confirmation window <b>50</b> (<figref idref="DRAWINGS">FIG. <b>5</b></figref>), an Incident Activation window <b>60</b> (<figref idref="DRAWINGS">FIG. <b>6</b></figref>), an Incident Status window <b>70</b> (<figref idref="DRAWINGS">FIG. <b>7</b></figref>), and a Clear Incident screen <b>80</b> (<figref idref="DRAWINGS">FIG. <b>8</b></figref>). In some examples, one or more screens/windows <b>20</b>, <b>30</b>, <b>40</b>, <b>50</b>, <b>60</b>, <b>70</b>, and <b>80</b> may include navigation tabs that enable user <b>18</b> to switch from one screen/window to another, in any order.

0035In the example illustrated in <figref idref="DRAWINGS">FIG. <b>2</b></figref>, Alarm Acknowledgement screen <b>20</b> happens to show four alarm notifications <b>36</b> (alarm notifications <b>36</b><i>a</i>, <b>36</b><i>b</i>, <b>36</b><i>c</i>, and <b>36</b><i>d</i>); however, any number of alarm notifications <b>36</b> can be presented. The term, “alarm notification” refers to any message or identifier indicating the occurrence of an alarm-triggered event or some other troubling event. In the illustrated example, each alarm notification <b>36</b> may provide a brief description of the alarm, its general location, and approximate time of occurrence.

0036In some examples, Alarm Acknowledgement screen <b>20</b> may include an Unacknowledged button <b>38</b>, an Acknowledged button <b>42</b>, a checkbox column <b>44</b>, a priority rank column <b>46</b>, an Alarm column <b>48</b>, an ID column <b>52</b>, a Device column <b>54</b>, a Time column <b>56</b>, an Action column <b>58</b>, a group Acknowledge button <b>55</b>, and an options column <b>62</b>. Alarm column <b>48</b> provides a list of alarm notifications <b>36</b>. Priority rank column <b>46</b> provides a symbol at each alarm notification <b>36</b> to indicate its level of priority, importance, or urgency. For instance, in some examples, a hexagon might identify alarms with the highest level of priority, a triangle pointing up might represent a moderate priority, and a triangle pointing down might represent a relatively low priority.

0037ID column <b>52</b> provides each alarm with an assigned identification or serial number. Those same identification numbers can be used in other screens and windows to help quickly identify which alarms are being evaluated, processed or otherwise referenced

0038A Description column <b>64</b> may provide each alarm with additional descriptive information. Alarm column <b>48</b>, for example, includes a Fire alarm notification for a fire in Room <b>143</b>, while Description column <b>64</b> may point out that a smoke detector is what triggered the alarm. Device column <b>54</b> may provide even more specific information, e.g., the smoke detector has a device identification number of F47592. Time column <b>56</b> indicates the date and time of when the alarm occurred.

0039Action column <b>58</b> provides a set of Acknowledge buttons <b>66</b> for a corresponding set of alarm notifications <b>36</b> in Alarm column <b>48</b>. Each Acknowledge button <b>66</b> provides user <b>18</b> with a way for acknowledging a corresponding alarm notification <b>36</b>. The term “acknowledge” (and derivatives thereof), as it pertains to a user acknowledging a computer displayed alarm notification means that the user physically performed some sort of computer related input action directed to the displayed alarm notification. Some examples of such an input action may include selecting or highlighting one or more computer displayed elements, such as checkboxes, words, descriptions, numbers, symbols, boxes, buttons, objects, icons, and/or combinations thereof; wherein the selecting or highlighting action may be done via a mouse (e.g., mouse-clicking <b>68</b>), keyboard, touchscreen, and/or verbal input.

0040Each Acknowledge button <b>66</b> directly acknowledges a corresponding individual alarm notification <b>36</b>. Mouse-clicking or otherwise selecting an individual Acknowledge button <b>66</b> automatically issues an incident with a predefined operating procedure <b>16</b>. More specifically, in some examples, user <b>18</b> acknowledges alarm notification <b>36</b><i>a </i>(Fire in Room <b>143</b>) by mouse-clicking <b>68</b> (or using a touchscreen, etc.) on Acknowledge button <b>66</b><i>a</i>. Likewise, user <b>18</b> can acknowledge alarm notification <b>36</b><i>b </i>(Invalid Card in Parking A2) by mouse-clicking on Acknowledge button <b>66</b><i>b. </i>

0041Acknowledged button <b>42</b> and Unacknowledge button <b>38</b> may provide user <b>18</b> with a way for toggling between Alarm Acknowledgement screen <b>20</b> (<figref idref="DRAWINGS">FIG. <b>2</b></figref>) and Clear Incident screen <b>80</b> (<figref idref="DRAWINGS">FIG. <b>8</b></figref>). Clear Incident screen <b>80</b> will be explained later.

0042For sake of example, in Alarm Acknowledgement screen <b>20</b>, user <b>18</b> might mouse-click or otherwise select Acknowledge button <b>66</b><i>c </i>to acknowledge alarm notification <b>36</b><i>c </i>(Invalid Badge, ID <b>210</b>). In response to this user acknowledgement, user <b>18</b> is automatically presented with Incident Action screen <b>30</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>). In this example, Incident Action screen <b>30</b> provides user <b>18</b> with a predefined operating procedure <b>16</b><i>c </i>with one or more recommended action steps <b>74</b> for addressing acknowledged alarm notification <b>36</b><i>c </i>(Invalid Badge, ID <b>210</b>). Some examples of Incident Action screen <b>30</b> include symbols <b>76</b> (e.g., checkboxes, circles, buttons, etc.) that enable user <b>18</b> to mark individual action steps <b>74</b> as being completed.

0043Incident Action screen <b>30</b>, in this particular example, may confirm or repeat some of the same information found on Alarm Acknowledgement screen <b>20</b> as it pertains to an acknowledged alarm notification <b>36</b>, such as, for example, alarm notification <b>36</b><i>c </i>(Invalid Badge, ID <b>210</b>). In some examples, Incident Action screen <b>30</b> may also provide a Workflow Name <b>78</b>, an identification <b>82</b> of a user <b>18</b> assigned to the incident, an Activity log <b>84</b>, a Respond Now button <b>86</b>, a Complete button <b>88</b>, and a Dismiss button <b>92</b>.

0044User <b>18</b> can mouse-click or otherwise select the Respond Now button <b>86</b>, which may assign a chosen user <b>18</b> (e.g., Jane) to the alarm. In this particular example, Jane then performs the list of recommended action steps <b>74</b> either directly herself and/or with the assistance of others. Symbols <b>76</b> allow Jane to record her progress by marking the completion of individual action steps <b>74</b>, and the progress of the response is recorded in Activity log <b>84</b>.

0045When all of the action steps <b>74</b> have been completed and/or the alarm associated with alarm notification <b>36</b><i>c </i>has been resolved, user <b>18</b> can mouse-click or otherwise select the Complete button <b>88</b>. If all of the action steps <b>74</b> have been completed, as indicated by all of the symbols <b>76</b> being checked, selecting the Complete button <b>88</b> ends the process of responding to alarm notification <b>36</b><i>c</i>. If, however, Complete button <b>88</b> is selected while symbols <b>76</b> indicate that not all of the action steps <b>74</b> have been completed, then Incident Dismissal window <b>40</b> (<figref idref="DRAWINGS">FIG. <b>4</b></figref>) appears.

0046Incident Dismissal window <b>40</b> provides a textbox <b>94</b> that offers user <b>18</b> with an opportunity to enter a reason for dismissing an alarm notification <b>36</b> (e.g., dismissing alarm notification <b>36</b><i>c</i>). After entering a reason for dismissal, user <b>18</b> may confirm the dismissal by mouse-clicking or otherwise selecting a Dismiss Incident button <b>96</b>. Selecting the Dismiss Incident button <b>96</b> ends the process of responding to alarm notification <b>36</b><i>c. </i>

0047If, however, user <b>18</b> decides not to Dismiss Incident after all, user <b>18</b> can select a Back to Incident button <b>98</b>. Back to Incident button <b>98</b> returns user <b>18</b> to Incident Action screen <b>30</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>). This allows user <b>18</b> to continue working on the predefined operating procedure <b>16</b> for alarm notification <b>36</b><i>c. </i>

0048Returning to <figref idref="DRAWINGS">FIG. <b>2</b></figref>, in some examples, rather than using acknowledge buttons <b>66</b> for acknowledging alarm notifications <b>36</b> and thereby automatically creating an incident directly, user <b>18</b> may confirm a selected alarm notification <b>36</b> by instead mouse-clicking or otherwise selecting a corresponding options icon <b>72</b> in options column <b>62</b>. This leads to Incident Confirmation window <b>50</b> (<figref idref="DRAWINGS">FIG. <b>5</b></figref>). Incident Confirmation window <b>50</b> provides more flexible options when user <b>18</b> acknowledges or otherwise handles a chosen alarm in this manner.

0049In some examples, Incident Confirmation window <b>50</b> may display incident information <b>102</b> (e.g., Invalid Badge, ID <b>210</b>, level of priority, etc.) and may provide user <b>18</b> with options for mouse-clicking or otherwise selecting a Cancel button <b>104</b>, an Acknowledge button <b>106</b>, and a Bypass Incident button <b>108</b>. Acknowledge button <b>106</b> (first option) confirms the acknowledgement of the subject alarm notification <b>36</b> (e.g., alarm notification <b>36</b><i>c</i>, Invalid Badge, ID <b>210</b>) and then, in some examples, presents Incident Action screen <b>30</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>) to user <b>18</b>. In addition or alternatively, in some examples, Acknowledge button <b>106</b> leads user <b>18</b> to Incident Activation screen <b>60</b> (<figref idref="DRAWINGS">FIG. <b>6</b></figref>). User <b>18</b> mouse-clicking or otherwise selecting Bypass Incident button <b>108</b> (second option) dismisses or clears the subject alarm notification <b>36</b><i>c</i>, whereby the troubling event <b>12</b> associated with alarm notification <b>36</b><i>c </i>is considered to have been resolved, and alarm notification <b>36</b><i>c </i>is deemed no longer valid or active. Cancel button <b>104</b> returns user <b>18</b> to Alarm Acknowledgement screen <b>20</b> (<figref idref="DRAWINGS">FIG. <b>2</b></figref>) and gives user <b>18</b> the opportunity to confirm or change the user's previous action taken in Alarm Acknowledgement screen <b>20</b>.

0050In some examples, Incident Confirmation window <b>50</b> provides additional information and/or options. For instance, in the example shown in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, Incident Confirmation window <b>50</b> may provide a Response tab <b>112</b> for displaying what is shown in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, an Instructions tab <b>114</b> for displaying instructions regarding alarm notification <b>36</b><i>c</i>, a Details tab <b>116</b> for more specific information about alarm notification <b>36</b><i>c</i>, and perhaps a Video tab <b>118</b> for any relevant videos regarding alarm notification <b>36</b><i>c </i>and its associated troubling event <b>12</b>.

0051In the illustrated example, Incident Confirmation window <b>50</b> may also provide a Select Response button <b>122</b>, a View Previous Response button <b>124</b>, and a textbox <b>126</b>. Select Response button <b>122</b> may provide a dropdown menu of one or more predefined responses or predefined operating procedures for addressing the subject alarm notification <b>36</b><i>c</i>. View Previous Response button <b>124</b> may provide user <b>18</b> with prior responses to alarm notification <b>36</b><i>c</i>. And textbox <b>126</b> is for user <b>18</b> to enter and document any relevant additional information.

0052In some examples, instead of acknowledging alarm notifications <b>36</b> individually through acknowledgement buttons <b>66</b> or options icons <b>72</b>, user <b>18</b> may select multiple checkboxes <b>44</b>′ to collectively acknowledge a batch of alarm notifications <b>36</b>′ (e.g., alarm notifications <b>36</b><i>a</i>, <b>36</b><i>b</i>, and <b>36</b><i>c</i>). After selecting the batch of alarm notifications <b>36</b>′, user <b>18</b> may click on group acknowledgment button <b>55</b> (<figref idref="DRAWINGS">FIG. <b>2</b></figref>). This leads to Incident Activation window <b>60</b> (<figref idref="DRAWINGS">FIG. <b>6</b></figref>).

0053In some examples, Incident Activation window <b>60</b> may provide information as to how many of the alarms selected in Alarm Acknowledgement screen <b>20</b> have a predefined operating procedure <b>36</b>. In addition or alternatively, some examples of Incident Activation window <b>60</b> may provide user <b>18</b> with a Cancel button <b>128</b>, a Proceed button <b>132</b>, and a choice <b>134</b> between two mutually exclusive selectable (e.g., mouse-clickable) elements <b>136</b> and <b>138</b>. User <b>18</b> choosing element <b>136</b> (first option) acknowledges one or more alarm notifications and creates one or more incidents, which applies one or more predefined operating procedures <b>36</b> to the corresponding one or more alarm notifications <b>36</b>. User <b>18</b> choosing element <b>138</b> (second option) acknowledges one or more alarm notifications but does not create any incidents for them, thus the troubling events <b>12</b> associated with alarm notifications <b>36</b> will still need to be addressed but without necessarily the benefit of any predefined operating procedures <b>16</b>. User <b>18</b> mouse-clicking or otherwise selecting Proceed button <b>132</b> enacts or confirms the user's choice of element <b>136</b> or <b>138</b>. User <b>18</b> mouse-clicking or otherwise selecting Cancel button <b>128</b> may return user <b>18</b> to a previous window or screen, such as Alarm Acknowledgement screen <b>20</b>.

0054In some examples, selecting Proceed button <b>132</b> of Incident Activation window <b>60</b> may lead user <b>18</b> to Incident Action screen <b>30</b> or Incident Status window <b>70</b>. In some examples, Incident Status window <b>70</b> may include Alarm column <b>48</b>, an Owner column <b>142</b> and a Progress column <b>144</b>. Owner column <b>142</b> may identify one or more users <b>18</b> responsible for addressing troubling events <b>12</b> associated with alarm notifications <b>36</b>. In the illustrated example, Progress column <b>144</b> provides one or more progress of completion indicators <b>146</b> that illustrate how many recommended actions steps <b>74</b> have been completed for each alarm notification <b>36</b> in Alarm column <b>48</b>. In some examples, mouse-clicking or otherwise selecting an alarm notification <b>48</b> and/or its corresponding progress of completion indicator <b>146</b> may lead user <b>18</b> back to Incident Action screen <b>30</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>).

0055If all of the action steps <b>74</b> of an alarm notification <b>36</b> have been completed, as indicated by the progress of completion indicator <b>146</b>, then mouse-clicking or otherwise selecting Complete button <b>88</b> on Incident Action screen <b>30</b> may close out and clear that alarm notification <b>36</b>. If, however, one or more of the action steps <b>74</b> are not completed, as indicated by the progress of completion indicator <b>146</b>, then mouse-clicking or otherwise selecting Dismiss button <b>92</b> on Incident Action screen <b>30</b> may lead user <b>18</b> to Incident Dismissal window <b>40</b> (<figref idref="DRAWINGS">FIG. <b>4</b></figref>).

0056As mentioned earlier, Incident Dismissal window <b>40</b> provides textbox <b>94</b> for entering a reason for dismissing an alarm notification <b>36</b>. After entering a reason for dismissal in textbox <b>94</b>, user <b>18</b> may confirm the dismissal by mouse-clicking or otherwise selecting Dismiss Incident button <b>96</b> of Incident Dismissal window <b>40</b>. Selecting the Dismiss Incident button <b>96</b> ends the process of responding to the subject alarm notification <b>36</b>. In some examples, user <b>18</b> might select Dismiss Incident button <b>96</b> simply because the incident is getting old and may have resolved itself without ongoing user intervention.

0057Referring back to Alarm Acknowledgement screen <b>20</b> (<figref idref="DRAWINGS">FIG. <b>2</b></figref>) and Clear Incident screen <b>80</b> (<figref idref="DRAWINGS">FIG. <b>8</b></figref>), those two screens <b>20</b> and <b>80</b> each include Acknowledged button <b>42</b> and Unacknowledge button <b>38</b>. Buttons <b>38</b> and <b>42</b> for provide user <b>18</b> with a way to toggle between Alarm Acknowledgement screen <b>20</b> and Clear Incident screen <b>80</b>.

0058In the illustrated example, Clear Incident screen <b>80</b> includes an Action column <b>148</b> with a series of Clear buttons <b>152</b>. Mouse-clicking or otherwise selecting one or more Clear buttons <b>152</b> may provide user <b>18</b> with a way for clearing, silencing or resetting a sensor <b>26</b> without necessarily dismissing the alarm notification <b>36</b> associated with the corresponding sensor <b>26</b>. In some examples, selecting one or more Clear buttons <b>152</b> may lead user <b>18</b> back to Incident Dismissal window <b>40</b> (<figref idref="DRAWINGS">FIG. <b>4</b></figref>). In Incident Dismissal window <b>40</b>, user <b>18</b> may fully dismiss the incident associated with the alarm cleared in the Clear Incident screen <b>80</b> (<figref idref="DRAWINGS">FIG. <b>8</b></figref>). In some examples, Clear Incident screen <b>80</b> provides popup messages indicating whether a selecting a Clear button <b>152</b> was successful or unsuccessful based on whether an incident had any outstanding, uncompleted action steps <b>74</b>.

0059Various steps of operating the facility management system <b>10</b> are illustrated in <figref idref="DRAWINGS">FIGS. <b>1</b>-<b>8</b></figref> as follows. Alarm Acknowledgement screen <b>20</b> is one example illustration of displaying a plurality of alarm notifications <b>36</b> corresponding to the plurality of troubling events <b>12</b>. Acknowledgement buttons <b>66</b> of <figref idref="DRAWINGS">FIG. <b>2</b></figref> is one example illustration of providing user <b>18</b> with an option for acknowledging at least one alarm notification (e.g., alarm notification <b>36</b><i>c</i>) of the plurality of alarm notifications <b>36</b>. User <b>18</b> mouse-clicking <b>68</b> on an Acknowledge button <b>66</b> in <figref idref="DRAWINGS">FIG. <b>2</b></figref> is one example illustrating that in response to user <b>18</b> acknowledging the at least one alarm notification <b>36</b> (e.g., via Acknowledge button <b>36</b><i>a</i>, <b>36</b><i>b</i>, <b>36</b><i>c</i>, or <b>36</b><i>d</i>), presenting user <b>18</b> (e.g., via Incident Action screen <b>30</b> of <figref idref="DRAWINGS">FIG. <b>3</b></figref>) with predefined operating procedure <b>16</b> for the at least one alarm notification <b>36</b> acknowledged by user <b>18</b>, wherein <figref idref="DRAWINGS">FIG. <b>3</b></figref> shows the predefined operating procedure <b>16</b> includes at least one recommended action step <b>74</b> to address the corresponding troubling event <b>12</b> shown in <figref idref="DRAWINGS">FIG. <b>1</b></figref>. An arrow <b>154</b> of <figref idref="DRAWINGS">FIG. <b>1</b></figref> represents user <b>18</b> performing at least one recommended action step <b>74</b> to address the corresponding troubling event <b>12</b>.

0060Arrows <b>156</b> and memory <b>32</b> of <figref idref="DRAWINGS">FIG. <b>1</b></figref> represent creating and storing predefined operating procedure <b>16</b> before the plurality of troubling events <b>12</b> occur. Checkboxes <b>44</b> and options icons <b>72</b> shown in <figref idref="DRAWINGS">FIG. <b>2</b></figref> represents providing user <b>18</b> with a batch-select option for acknowledging a batch of alarm notifications <b>36</b>′ of the plurality of alarm notifications <b>36</b>, wherein the batch of alarm notifications <b>36</b>′ are a subset of the plurality of alarm notifications <b>36</b>, and the batch of alarm notifications <b>36</b>′ includes the at least one alarm notification <b>36</b><i>c</i>. Multiple viewings of Incident Action screen <b>30</b>, shown in <figref idref="DRAWINGS">FIG. <b>3</b></figref>, is one example illustrating that in response to user <b>18</b> choosing and exercising the batch-select option (shown in <figref idref="DRAWINGS">FIG. <b>2</b></figref>), presenting user <b>18</b> with a plurality of predefined operating procedures <b>16</b> corresponding to the batch of alarm notifications <b>36</b>′. Bypass Incident button <b>108</b> of <figref idref="DRAWINGS">FIG. <b>5</b></figref> represents providing user <b>18</b> with a bypass option for allowing user <b>18</b> to cancel a false alarm notification (possibly any one of alarm notifications <b>36</b> after first acknowledging the false alarm notification, e.g., via option icons <b>72</b>) without presenting user <b>18</b> with a predefined operating procedure <b>16</b> for the false alarm notification (e.g., going from Alarm Acknowledgement screen <b>20</b> to Incident Confirmation window <b>50</b> without first going to Incident Action screen <b>30</b>). Symbols <b>76</b> (<figref idref="DRAWINGS">FIG. <b>3</b></figref>) represent enabling user <b>18</b> to mark an individual action step of the plurality of recommended action steps as being completed. <figref idref="DRAWINGS">FIG. <b>7</b></figref> illustrates displaying progress of completion indicator <b>146</b> that shows how many of the plurality of recommended actions steps have been performed. <figref idref="DRAWINGS">FIGS. <b>3</b>, <b>7</b> and <b>8</b></figref> illustrate examples of displaying an identifier (e.g., Jane, Admin1, Supervisor, etc.) of a user responsible for performing the at least one recommended action step.

0061Acknowledge button <b>106</b> (first option) and Bypass Incident button <b>108</b> (second option), both shown in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, illustrate that when the user acknowledges the first alarm notification, providing the user, via the computer, with a choice between a first option of proceeding with the first predefined operating procedure and a second option of bypassing the first predefined operating procedure. The action steps shown in <figref idref="DRAWINGS">FIG. <b>3</b></figref> illustrate that when the user chooses the first option, presenting the user, via the computer, with the at least one recommended action step to address the first troubling event. Bypass Incident button <b>108</b> in <figref idref="DRAWINGS">FIG. <b>5</b></figref> illustrates that when the user chooses the second option, dismissing the first alarm notification via the computer. Clear buttons <b>152</b> in <figref idref="DRAWINGS">FIG. <b>8</b></figref> illustrate enabling the user to clear alarm notifications. Textbox <b>94</b> of <figref idref="DRAWINGS">FIG. <b>4</b></figref> represents enabling the user to enter into the computer a reason or explanation as to why some of the recommended action steps need not be completed, and the horizontal lines in textbox <b>94</b> represent the user actually entering the text.

0062Some example methods for operating facility management system <b>10</b> can be defined as follows:

0063Example-1 A facility monitoring method for assisting a user in addressing a plurality of troubling events at a facility being monitored, the method comprising:

0064displaying a plurality of alarm notifications corresponding to the plurality of troubling events;

0065associating a plurality of predefined operating procedures with only some of the plurality of alarm notifications, each predefined operating procedure of the plurality of predefined operating procedures includes at least one recommended action step for addressing at least one of the plurality of troubling events; and

0066enabling the user to collectively acknowledge a batch of alarm notifications of the plurality of alarm notifications, the batch of alarm notifications being a subset of the plurality of alarm notifications, and only a portion of the batch of alarm notifications are associated with the plurality of predefined operating procedures.

0067Example-2 A facility monitoring method with a computer for assisting a user in addressing at least a first troubling event and a second troubling event of a plurality of troubling events at a facility being monitored, the method comprising:

0068displaying a plurality of alarm notifications corresponding to the plurality of troubling events, wherein the plurality of alarm notifications includes at least a first alarm notification and a second alarm notification, the first alarm notification being associated with a first predefined operating procedure with a plurality of recommended action steps for addressing the first troubling event, the second alarm notification being for the second troubling event;

0069enabling the user to collectively acknowledge a batch of alarm notifications including the first alarm notification and the second alarm notification;

0070presenting the user with the first predetermined operating procedure including the plurality of recommended action steps for addressing the first troubling event;

0071enabling the user to clear the first alarm notification when the plurality of recommended action steps have been completed; and

0072enabling the user to clear the second alarm notification regardless of whether the user performed any action to address the second troubling event.

0073The disclosure should not be considered limited to the particular examples described above. Various modifications, equivalent processes, as well as numerous structures to which the disclosure can be applicable will be readily apparent to those of skill in the art upon review of the instant specification.