TECHNICAL FIELD

[0001] The present invention relates generally to building automation system and more particularly to configuration of fault detection and diagnostics rules.

BACKGROUND

[0002] Most modern buildings are built with security systems, emergency systems, heating, ventilating, and air conditioning (HVAC) systems, all of which have many sensors, fans, values, and actuators. These systems together are commonly referred to as building automation systems (BAS). Many of these devices are controlled by microcontroller or microprocessor located in field panels. The programming of each panel is often unique based upon the different devices coupled to the panel. The initial provisioning of a BAS takes multiple hours to layout the design, develop the programing for the panels and other programmable devices, program the devices, tweak the devices, and test the devices and programs. The configuration of the BAS is typically stored in a database accessible by the BAS. Over time, additional changes and modification occur to the BAS and its corresponding database. These changes and modification often occur with different naming conventions and descriptions resulting in similar devices in the BAS using different naming conventions for equipment and data points in the BAS. Thus, in some BAS the naming conventions are not rigidly defined and enforced allowing strings to be used as labels (referred to as "weak naming."

[0003] Often different types of tools, such as fault detection tools and performance analysis tools require knowledge of subsets of points (physical and logical elements of a BAS) and hardware subsystems in the BAS to be identified. Further, information about the function and meaning of points and associated meta-data is often required to give meanings for system analytics and such information is not typically embedded in traditional BASs. The identification of such subsets is a manual process that is prone to errors due to weak naming conventions and typing used in configuring the BAS.

[0004] Fault detection and diagnostics (FDD) in a BAS typically requires rules to be predefined and manual identification and configuration of data collected from points in the BAS. The more complex the rule, the more identification and configuration of points is required. Furthermore, the more complex the rules, the greater the chance to errors being made in the implementation of the FDD rules. The identification and configuration of FDD rules becomes even more complex with weak naming convention.

[0005] In view of the foregoing, there is an ongoing need for systems, apparatuses and methods for correctly identifying elements in a BAS database associated with subsystems and the elements needed for configuration of FDD rules.

SUMMARY

[0006] An approach for selection of fault detection and diagnostic (FDD) rules and implementation of the FDD rules in a building automation system (BAS) controlled by a process that selects FDD rules based upon business outcomes. In response to selected FDD rules entries in a BAS's database required by the FDD rule are identified. Additionally, required elements that are missing are also identified and able to be configured.

[0007] Other devices, apparatus, systems, methods, features, and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The invention can be better understood by referring to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention. In the figures, like reference numerals designate corresponding parts throughout the different views.

[0009] Figure 1 is an illustration of a processor controlled device that is able to access a database associated with a building automation system (BAS) in accordance with an example implementation of the invention.

[0010] Figure 2 is a graphical illustration of a HVAC building air handler subsystem implementation in accordance with an example implementation of the invention.

[0011] Figure 3 is a graphical user interface controlled by the processor of figure 1 depicting a list of available panels associated with a subsystem in the BAS having unidentified items in accordance with an example implementation of the invention.

[0012] Figure 4 is a list of approaches for identifying associations (i.e. mappings) between items in a subsystem of the BAS of figure 1 in accordance with an example implementation of the invention.

[0013] Figure 5 is a flow diagram of an approach to identify unidentified items associated with a subsystem of a BAS of figure 1 in accordance with an example implementation of the invention.

[0014] Figure 6 is a graphical user interface (GUI) depicting a first iteration of selecting elements associated with the selected air handler subsystem of figure 3 in accordance with an example implementation. [0015] Figure 7 is a graphical user interface depicting the approach of unidentified elements being mapped via the "Edit Mapping" button of figure 6 not discovered in accordance with an example implementation.

[0016] Figure 8 is a diagram of the updating of the definition file of strings and suffixes based upon the output of the discovery and identification of equipment and points application that resides in application memory of figure 1 in accordance with an example implementation.

[0017] Figure 9 is a graphical user interface depicting on a display selectable business outcomes in accordance with an example implementation.

[0018] Figure 10 is a table of selectable business outcomes in accordance with an example implementation.

[0019] Figure 11 is a graphical user interface depicting equipment types to be monitored by a selected FDD rule in accordance with an example implementation.

[0020] Figure 12 is a graphical user interface of FDD rule status based upon elements from the database of the BAS in accordance with an example implementation.

[0021] Figure 13 is a graphical user interface for project rules in accordance with an example implementation.

[0022] Figure 14 is a graphical user interface depicting a summary for rules and equipment needed to be defined for the selected business outcomes.

[0023] Figure 15 is a flow diagram of the approach for selecting a FDD rules based upon business outcomes and equipment in accordance with an example implementation. DETAILED DESCRIPTION

[0024] As used herein, an approach for fault detection and diagnostics rule selection and configuration based on business outcome.

[0025] Turning to figure 1, an illustration 100 of a processor controlled device 102 that is able to access a database 126 associated with a BAS 136 in accordance with an example implementation of the invention. The processor controlled device 102 may have a controller 104 (processor) coupled to a memory 106, network interface 108, video controller 110, and input/output (I/O) interface 112 by address/data bus 114. The network interface 108 may couple the processor controlled device 102 to a network, such as one or more local area networks (LANs)/internet/cloud 116 and servers, such as server 132 located in the cloud, and BAS 136. The connection to the LANs/internet/cloud 116 may be wired or wireless (such as IEEE 802. l lg or 802.11η standards). The video controller 110 may be coupled to one or more displays, such as display 118. The display is typically a digital video display, such as HD television or VGA computer display. The I/O interface 112 may be coupled to a keyboard 122, optical disk reader 120, and mouse 124.

[0026] The controller 104 executes instructions that may be stored in memory 106 that facilitate the operation of the processor controlled device 102. The memory 106 may be logically or physically split into an operational memory 128 that provide operational instructions for the processor controlled device 102 and an application memory 130. The memory 106 may have one or more databases, such as database 126 stored therein for access by the application when executed by the controller 104 stored in application memory 130. In other implementations, the application memory 130 may be dedicated to one application. An initial naming convention may initially be loaded into application memory 130, where the initial naming definition file is a typical approach to naming different elements in the database 126 and contains partial names, such as suffixes and/or strings of text. [0027] The database 126 is copied from database 125 in BAS 136 and may be downloaded or otherwise copied into memory 106 by the controller 104. In other implementations, the database 125 may be read in real-time from the BAS or server servicing the BAS located in the cloud or an external network. In yet other implementations, the database from the BAS 136 may have been previously stored in the memory or disk storage of server 132. The database 125 and copy 126 contain element and configuration data for the BAS 136, including hardware, points, and associated data.

[0028] The BAS 136 may also have a proxy process 140 that sends collected data, for example trend data, from the BAS 136 to a metrics/analytics service (MAS) 142 that is implemented on server 132. The MAS 142 in other implementations may be internal to the BAS 136. In yet other implementations, the MAS 142 may be implemented on a remote device, such as processor controlled device 102. The collected data may be real time data or data stored in database 125 and periodically sent via the proxy process 140 to the metrics/analytics service 142.

[0029] The application in application memory 130 is executed by the controller 104 and results in s a graphical user interface 138 appearing on display 118 for identification of the elements that comprise a subsystem of the BAS 136. The elements may include points, panels, hardware, and data associated with the subsystems, such as the simplified subsystem of figure 2.

[0030] In figure 2, a graphical illustration of a HVAC building implementation 200 in accordance with an example implementation of the invention is depicted. A building 202 with a room 204 has a supply air vent 206 and return air vent 208. Outside air is brought into the building via an outside inlet vent 210 and exhausted via outside exhaust vent 212. An air mixer 214 may have an exhaust air damper 216, outdoor air damper 218, return air damper 220, and supply air damper 222. A supply fan 224 may aid in moving the supply air and have a supply variable frequency drive 226. A heating supply control valve 228 may control the heating of the supply air and similarly a supply air cooling valve 230 may control the cooling of the supply air, and thermostat 232 may also be present in room 204. Return air exits the room 204 via the return air vent 208 and may be aided by return fan 234 that may be controlled by return variable frequency drive 236. The return air enters the air mixer 214 via return air damper 220. The room 204 may also have lighting control 238 and blind control 240 as shown in figure 2. All the devices may be controlled by one or more field panels, such as panel 242 that control the different elements of the BAS 136. The field panel may be directly or indirectly coupled to a building's telecommunication network 239 and/or the internet/cloud. The field panel may have one or microcontrollers that are programmed to operate the different components of the BAS 136.

[0031] Turning to figure 3, a graphical user interface (GUI) 300 controlled by the processor of figure 1 depicting a list of available panels 302 associated with a subsystem in the BAS 136 having unidentified items in accordance with an example implementation of the invention is illustrated. A panel 304 is selected from the list of available panels 304. The panel is added to the list of selected panels 306 with an "Add" button 308 in the current implementations. Other approaches for selecting items may be employed, such as check boxes, drag-and-drop, or other known graphical user interface selection approaches. A button, such as "Add All" button 310, may be available to add all panels in the list of available panels 302. Similarly, items such as panels may be selected in the list of selected panels 306 and buttons may be available for removing the selected panels from the list of selected panels 306. Examples of such buttons include the "Remove" button 312 and "Remove All" button 314. In other implementations, other known approaches for selecting and removing items in a graphical user interface may be employed. Once all the desired selection have been made for an area or set of equipment, such as air handler of figure 2, the selection can be committed or otherwise accepted using an "OK" button 316. If a user desire's to not to continue, the "Cancel" button may be selected.

[0032] Once the items, such as the panels for the air handler of figure 2 are selected and accepted, the associated equipment and points in the database are discovered with the aid of an initial definition file. Unlike approaches with strong naming types, weak naming allows names to be user defined strings in the database and associations to be undiscoverable even with an initial definition file. In order to resolve undiscovered associations, a plurality of approaches is implemented. In figure 4, a list of approaches 400 for identifying associations (i.e. mappings) between items in a subsystem of the BAS 136 of figure 1 in accordance with an example implementation of the invention is depicted. There are five possible results from the selection that occurred in figure 3. First, equipment, such as any device 208-240 in figure 2, may not be discovered 402. For example, equipment or items that exist in the subsystem of the BAS 136 are not discovered from the selected items or panel. Second, equipment or items are discovered in error 404. For example, equipment or items are listed in response to the selection using GUI 300 that do not really exist. Third, in response to the selection using GUI 300 duplicate equipment is listed 406. The same piece of equipment is listed more than once in response to the selection using GUI 300. Fourth, incorrectly mapped points associated with the selected panels 408. The point function assigned to a point is incorrectly mapped in response to the selection using GUI 300. The fifth possible result is points are unmapped 410 to any panel or item. The selected panels in figure 3 results in a plurality of point mappings, but some points are unmapped.

[0033] Turning to figure 5, a flow diagram 500 of an approach to identify unidentified items associated with a subsystem of a BAS 136 of figure 1 in accordance with an example implementation of the invention is illustrated. The controller 104 executes the application from the application memory 130 that reads a definition file 502. The copy of the database is accessed in step 504 and a listing of panels is provided in the GUI 300 of figure 3. Panels or elements are selected in step 506 associated with an area in the building or subsystem of the BAS 136. The controller then searches the copy of the BAS 136 database 126 using the definition file and generates mappings of points and equipment associated with selected items or panels or elements in step 508. A report with results is then generated that includes points with inconsistencies that need further processing or missing points in step 510. If equipment associated with the selected panels is not discovered in step 512 and is known to exist, then the equipment not discovered but known to exist is identified in step 514. If equipment is identified as being discovered in error in step 516, then the erroneous equipment is removed from the list of subsystem equipment and points in step 518. If duplicate equipment is identified in step 520, it is removed in step 522 from the list of subsystem equipment and points. In some implementations, steps 522 include merging duplicate equipment and combining of their mappings. If unmapped points are in the resulting list of subsystem equipment and points 528 and identified as inconsistencies, then the unmapped points are mapped in step 530 to the correct equipment or device using techniques as further described herein. The resulting list of points that has been modified to resolve at least a portion of the inconsistencies in the list of mappings that result in a complete list of mappings and unmapped points for the desired room or subsystem may then be saved in step 532. In other implementations, the order of the checking and/or corrections to the list may be done in a different order or with less than five checks for the resulting list of points and equipment.

[0034] In figure 6, a graphical user interface (GUI) 600 depicting a first iteration of selecting elements 602 associated with the selected air handler 300 subsystem of figure 3 in accordance with an example implementation is depicted. When the air handler 604 is selected in the GUI 600 and discovery is run via the "Run Discovery" button 610 a listing of point functions 606 is provided via the mappings of points and functions present in the database. Unmapped points or elements 608 are also depicted that appear to be mapped to the air handler 604. If all elements or points are correct and the subsystem mapping are complete, then the resulting list of elements may be exported using the "Export" button 612. Unmapped point functions 608 of the air handler 604 are mapped using the "Edit Mapping" button 614 and associations or mappings entered.

[0035] Turning to figure 7 a graphical user interface 700 depicting the approach of unidentified elements being mapped via the "Edit Mapping" button of figure 6 not discovered in accordance with an example implementation is depicted. The identified unknown equipment strings 702 are listed for the equipment type 704. Equipment strings may be added or removed 706, 708. Equipment strings 702 may each be individually associated or mapped with a point function 710. Similarly, point suffixes 712 may be added 714 or removed 716 to further map the unmapped points or items. Once the mappings are complete, they may be committed or saved by selecting the "OK" button 718 or cancelled with the "Cancel" button 720. Thus, equipment strings may be added, removed, point function mapped, and point suffixes added and removed to resolve unmapped or mismapped elements.

[0036] In figure 8, a diagram 800 of the updating 810 of the definition file 804 of strings and suffixes 804 based upon the output of the discovery and identification of equipment and points application 802 that resides in application memory 130 figure 1 in accordance with an example implementation is depicted. A subsystem or location in BAS 136 is selected using the discovery and identification of equipment and points application 802 using the definition file of strings and suffixes 804 resulting in an updated definition file of strings and suffixes 806 and in some cases unmapped items 808 that were not part of the selected subsystem or location. A definition file of strings and suffixes feedback process 810 is executed by the controller 104 using the updated definition file of strings and suffixes 806 and in some implementations portions of strings and suffixes from the unmapped items 808 as input. In order to identify strings and suffixes, approaches such as Random Forest Test Classification or Multinomial Naive Bayes Text classification may be used to identify and add new strings for classifying points and elements for use in mappings. That file is divided into training data and test data. The training data is used along with the definition file of strings and suffixes 804 and different types of weighting algorithms, such as are available in the PYTHON programing language are applied to the training data and definition file of strings and suffixes 804 resulting in an updated definition file of strings and suffixes that are used with the test data and the discovery and identification of equipment and points application 802 to verify an improvement in performance of using the updated file. If an improvement in performance is achieved, the updated definition file of strings and suffixes replaces the current definition file of strings and suffixes 804.

[0037] Turning to figure 9, a GUI 900 depicts on a display selectable business outcomes or value categories 902 in accordance with an example implementation. The value categories 902 in the current implementation include "energy", "environmental", "Financial", "sustainability", "Lifecycle", "System", and "compliance". Once a value category 902 has been selected, the selection may be accepted or other entered using an "OK" button 904. If no selection is desired, the "Cancel" button may be selected.

[0038] In figure 10, a table 1000 of value categories 1002 and descriptions 1004 in accordance with an example implementation are depicted. The "Financial" 1006 value category is a category of FDD rules that reduce maintenance costs and maximizes return on investment. "Sustainability" 1008 value category employs FDD rules that achieve sustainability goals and certifications. The "Environment" 1010 value category uses FDD rules that are optimized for comfort, safety, and security. The "Energy" 1012 value category employs FDD rules for maximizing energy efficiencies. The "System" 1014 value category uses FDD rules to enhance system performance. The "Lifecycle" 1016 value category FDD rules attempts to extend equipment life. The "compliance" 1018 value category FDD rules fulfill regulatory requirements. The "Reliability" 1020 category FFD rule seeks to maximize system uptime. In other implementations, more or less value categories may be employed.

[0039] Turning to figure 11 , a GUI 1100 depicting equipment types 1102 to be monitored by a selected FDD rules in accordance with an example implementation is depicted. Desired equipment to be monitored may be selected using a check box 1 104 in the current implementation. Thus, the value categories and the selected equipment types are used to generate a FDD rule mapping between BAS elements and FDD rules.

[0040] In figure 12, a GUI 1200 of FDD rule status 1202 based upon elements from the database of the BAS 136 in accordance with an example implementation is shown. The elements from the database of the BAS 136 depicted are points associated with selected equipment 1204. The available rules 1206 are listed and availability of the required points in the BAS 136 are depicted using a color code 1208. The green points are points in the BAS 136 that are available and mapped to the equipment 1204 (where the green color code reflects an availability indicator). The red points are points that are not available, but required for the rule 1206 (where the red color code reflects an unavailability indicator). The FDD rule 1206 may be selected using a "check" box and then committed using the "OK" button 1210.

[0041] Turning to figure 13, a GUI 1300 for project rules 1302 in accordance with an example implementation is depicted. Selected project rules associated with the system (subsystem) and value categories that are ready to be run are depicted. Thus, the rules having all their points defined in figure 12 are listed along with the selected equipment 1304 and ready to run in GUI 1300. Similarly, in figure 14 a GUI 1400 depicting a summary for rules and equipment needed to be defined for the selected business outcomes is depicted. The GUI 1400 identifies the number of rules selected for each piece of equipment and the number of elements 1402 that need to be mapped or otherwise configured.

[0042] Turning to figure 15 is a flow diagram 1500 of the approach for selecting FDD rules based upon business outcomes and equipment in accordance with an example implementation. Select value categories for a project in step 1502, such as "Energy". The selection may be accomplished via a graphical user interface 900 of figure 9. The equipment to be the subject of the FDD, is then selected in step 1504. The equipment selection occurs using GUI 1102 to select the equipment that is part of the BAS. A point mapping is then generated in step 1506. The generation of the point mapping occurs in the current example according to the approach depicted in the flow diagram 500 of figure 5. Project rules are selected in step 1508 using GUI depicted in figure 13. Pluralities of project rules are presented in response to the value category selected and equipment selected for the project. The rules are predefined and accessed from a rules catalog. The rules catalog may be located on a server 132 that resides in the cloud and is accessed over the Internet. In other implementations, the rules catalog may reside on the processor controlled device 102. Equipment rules that apply to a piece of equipment associated with the project rules may be reviewed and selected in step 1510.

[0043] The selected rules and equipment are then reviewed for readiness in step 1512. As each rule needs multiple points to be implemented and properly mapped in order to be properly executed a report is generated to verify the readiness for the rules to implement. If points or mappings are identified as missing in step 1512, then they need to be defined for the rules to function properly and step 1506 is executed to define the missing points or mappings. If in step 1512, the FDD is ready and fully defined, then a configuration file may be defined 5014 and implemented.

[0044] In other implementations, the definition file of strings and suffixes 804 may be stored in a library with multiple flavors or versions. Each flavor or version may be associated with an engineer, engineering group, installer of the BAS, manufacturer of the BAS, size of the BAS, or similar attribute. Such attributes may be contained in the database of the BAS 136. The definition file of strings and suffixes 804 or library of definition files of strings and suffixes may be stored on one or more servers located in the cloud, such as server 132.

[0045] It will be understood, and is appreciated by persons skilled in the art, that one or more processes, sub-processes, or process steps described in connection with figure 15 may be performed by hardware and/or software (machine readable instructions). If the approach is performed by software, the software may reside in application memory in a suitable electronic processing component or system such as one or more of the functional components or modules schematically depicted in the figures.

[0046] The software in the application memory may include an ordered listing of executable instructions for implementing logical functions (that is, "logic" that may be implemented either in digital form such as digital circuitry or source code or in analog form such as analog circuitry or an analog source such an analog electrical, sound or video signal), and may selectively be embodied in any tangible computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that may selectively fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this disclosure, a "computer- readable medium" is any tangible means that may contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. The tangible computer readable medium may selectively be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device. More specific examples, but nonetheless a non-exhaustive list, of tangible computer-readable media would include the following: a portable computer diskette (magnetic), a RAM (electronic), a read-only memory "ROM' (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic) and a portable compact disc read-only memory "CDROM' (optical). Note that the computer-readable medium may even be paper (punch cards or punch tape) or another suitable medium upon which the instructions may be electronically captured, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and stored in a computer memory.

[0047] The foregoing detailed description of one or more embodiments of the approach for selection of FDD rules and implementation of the FDD rules in a BAS controlled by a process that selects FDD rules based upon business outcomes has been presented herein by way of example only and not limitation. It will be recognized that there are advantages to certain individual features and functions described herein that may be obtained without incorporating other features and functions described herein. Moreover, it will be recognized that various alternatives, modifications, variations, or improvements of the above-disclosed embodiments and other features and functions, or alternatives thereof, may be desirably combined into many other different embodiments, systems or applications. Presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the appended claims. Therefore, the spirit and scope of any appended claims should not be limited to the description of the embodiments contained herein.