1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: AlarmHandler as a daemon or service |
From: | Randy Flood <[email protected]> |
To: | [email protected] |
Date: | Wed, 05 Apr 2006 07:23:44 -0500 |
As an AlarmHandler user it has always struck me that there should be a better way to manage alarms. In the real world it is quite common to have a device sitting just on the edge of the MINOR alarm point, creating nuisance alarms. We do not generally manage alarms by actively changing HIGH or LOW, since these are set by system experts. This leaves the user with the choice of disabling the alarm, which means that if the device reaches the MAJOR parameter no alarm will be heard or dealing with the nuisance alarms. Bad enough when a single channel behave such. When you have thousands of channels, not uncommon for a few to have this problem, especially during times of general machine instability, such as start up. It would be nice to be able to separately acknowledge or bypass MINOR alarms, a kind of "yeah we know we need to look at you, you're alright for now call us when you get to the MAJOR setpoint.
Terry
-- Randy Flood Chief of Operations ASD Operations Group 630-252-1767 4-1767