Subject: Alarm Issue #10 - Detecting Alarm State Change

From: "Sharon Chisholm" <[email-masked]>
Date: Mon, 10 Dec 2001 17:10:12 -0500

hi

Alarm#10 Detecting Alarm State Change

During the lifetime of an alarm, it may progress
through different non-cleared states. For example,
a temperature alarm may start as minor and progress
to critical. 

To better support this detection, the text of 
alarmActiveModelPointer needs to be updated to not
only point at the model for this alarm, but also
to the specific state. Well, actually it needs this
update anyways.

So, then there are two ways that a manager can detect
that an alarm has changed state:
	1. Alarm state change notifications as defined in 
	the alarm model
	2. Querying the alarmActiveModelPointer

Related to the discussion of TimeFilter versus DateAndTime,
it was suggested that DateAndTime does not get updated 
when any of the objects in the row get updated. The advantage
of this is that it makes it easy to determine that you
are referring to the same alarm. The disadvantage of this 
is that you can't easily check to see if an alarm has changed
state unless you support notifications.

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario