MECHANISM AND APPROACH FOR MONITORING BUILDING AUTOMATION SYSTEMS THROUGH USER DEFINED CONTENT NOTIFICATIONS

• US 20140266671A1
• Filed: 03/12/2013
• Published: 09/18/2014
• Est. Priority Date: 03/12/2013
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Huynh, Cuong, Donaldson, Stuart
• Granted Patent: US 10,162,344 B2
• Time in Patent Office: Days
• US Class Current: 340/506
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: G05B 23/0216 Human interface functionality, e.g. monitoring system providing help to the user in the selection of tests or in its configuration

Abstract

A system or mechanism for monitoring a building automation system through configurable conditions that indicate non-optimal performance or failure of building equipment. The mechanism may deliver notifications when the conditions are triggered. The mechanism may enable complex conditions and arbitrary user defined contents providing a context of the system to be delivered as notifications of data to configured recipients. The mechanism may enable a configuring event including not only user defined system context data as part of the event notification but also complex user defined conditions as needed.

Claims

1. A mechanism for monitoring a building automation system, comprising:

an alarm/event triggering conditions configuration component;

an alarm/event monitoring component;

an alarm/event system context data notification configuration component integrated with the alarm/event triggering conditions configuration component and system configuration database component to support configuration for data notification;

a system configuration database that facilitates generating a default or a user-defined context data notification based on each alarm/event triggering condition configuration;

an alarm event monitoring component integrated with the alarm/event triggering conditions configuration component for configuration of alarms/events to monitor; and

a real-time data component and a history data component, providing data for monitoring alarm/event conditions.

2. The mechanism of claim 1, wherein:

the alarm/event triggering conditions configuration component obtains generated default notification views from the alarm/event system context data notification configuration component;

the alarm/event monitoring component obtains a triggering condition configuration from the alarm/event triggering conditions configuration component; and

the alarm/event triggering conditions configuration component obtains event monitoring from the alarm/event monitoring component.

3. The mechanism of claim 1, further comprising:

a real-time data component connected to the alarm/event monitoring component;

an alarm/event processor connected to the alarm/event monitoring component;

an alarm/event notification options component; and

an alarm/event notification component connected to the alarm/event notification options component and the alarm/event processor.

4. The mechanism of claim 3, wherein:

the alarm/event monitoring component obtains data from the real-time data component and event processing from the alarm/event processor;

the alarm/event processor obtains a notification from the alarm/event notification component; and

the alarm/event notification component obtains a notification options configuration from the alarm/event notification options component.

5. The mechanism of claim 3, further comprising a system context data notification contents component connected to the alarm/event notification options component, the alarm/event system context data notification configuration component, the alarm/event processor and the alarm/event notification component.

6. The mechanism of claim 5, wherein:

the alarm/event processor obtains a generating of notification content from the system context data notification contents component;

the alarm/event notification component obtains notification content from the system context data notification contents component; and

the system context data notification contents component obtains a notification options configuration from the alarm/event notification options component and a notification content configuration from the alarm/event system context data notification configuration component.

7. The mechanism of claim 5, further comprising:

a trend data collection component connected to the alarm/event triggering conditions configuration component and to the real-time data component; and

a trend/history data component connected to the alarm/event monitoring component, the system context data notification contents component, and the trend data collection component.

8. The mechanism of claim 7, wherein:

the alarm/event triggering conditions configuration component configures point data logging in the trend data collection component, whenever configured triggered conditions need history data;

the trend data collection component obtains data from the real-time data component and log data via the trend/history data component;

the alarm/event monitoring component obtains history data from the trend/history data component; and

the system context data notification contents component obtains history data from the trend/history data component.

9. The mechanism of claim 7, further comprising a content delivery server connected to the alarm/event notification component.

10. The mechanism of claim 1, wherein the alarm/event monitoring component is distributed to monitor an alarm/event in an embedded device.

11. A method for alarm/event monitoring and notification in a building automation system, comprising:

monitoring a triggering condition based on an alarm/event condition configuration;

evaluating the triggering condition from an alarm/event triggering condition configuration periodically or upon a change notification of a value in the triggered condition; and

polling data, monitoring for change of data values, and/or fetching/analyzing history data as required for evaluating the triggering condition.

12. The method of claim 11, wherein if the triggering condition is an advanced triggering condition configuration, then periodically evaluating the triggering condition requires one or more supporting components to evaluate an arbitrary expression with a term associated with a user defined function and data from the fetched/analyzed history data and/or real-time data.

13. The method of claim 11, further comprising:

collecting trend data; and

logging trend data; and

wherein;

collecting trend data comprises polling data or monitoring change of value from a data source and buffering collected data; and

logging trend data comprising logging the data into a system persistence store to support history data references.

14. The method of claim 13, further comprising:

polling or monitoring real-time point data; and

wherein real-time data supports a service to provide data for history data logging and/or for evaluating an alarm/event triggering condition.

15. The method of claim 14, further comprising:

routing an event; and

processing the event; and

wherein;

routing the event routes a triggered condition to the processing the event to perform a configurable action on a triggered event; and

the processing the event checks for action to be performed on a triggered event based on a configuration of the triggered event.

16. The method of claim 15, further comprising:

generating notification content based on a passed triggered event; and

wherein generating notification content locates a notification options configuration associated with the triggered event, if a notification options configuration exists.

17. The method of claim 16, wherein:

if a notification options configuration exists, then generating notification content would schedule to generate notification content based on a data and reporting configuration template from a retrieved notification option configuration; and

to schedule to generate notification content would be either immediately or at a specified later time depending on a logged data reference in the notification option configuration.

18. The method of claim 17, wherein to schedule to generate the notification content either immediately or at a specified later time would allow notification content for troubleshooting to include system context data up to an event/alarm occurrence time and also data in a small period following an event occurrence as referenced in the notification option configuration.

19. The method of claim 18, further comprising:

notifying the event; and

wherein;

the notifying the event delivers generated notification content, based on the notification option configuration, to one or more recipients; and

the one or more recipients can receive virtually complete notification contents to enable analyzing the event in absence of connecting to the building automation system to obtain additional data for analyzing the event.

20. A method for configuring alarm/event triggering for notification in a building automation system, comprising:

configuring alarm/event triggering conditions;

configuring alarm/event notification contents; and

configuring alarm/event notification options; and

wherein;

the configuring alarm/event triggering conditions can reference history data;

if history data is needed, the history data will be configured automatically as a result of configuring alarm/event triggering conditions; and

the configuring alarm/event notification contents can incorporate history data;

if history data is needed for notification contents, the history data will be configured automatically as a result of detecting history data as needed in the configured notification contents.

21. The method of claim 20, wherein the configuring notification contents have a format and data configurations.

22. The method of claim 20, wherein configuring the notification contents results in a building automation context data notification contents configuration.