Better alarm handling

I'm currently administering HP's OpenView TeMIP (almost like OVO/NNM,
but for Telecom).

I notice that neither OVO, NNM or NetXMS takes care of the whole life
cycle of an alarm. The current behavior of these mentioned products is
just to acknowledge the alarm and then it disappears into history.
What I really like about TeMIP, and which I really would like to see in
NetXMS, is a really good way of handling alarms.

Alarm handling in TeMIP can be splitted into two status processes; the
operators "state" and the state of the alarm it self.

The life cycle of states (column S in picture):
1. Outstanding (The alarm is not taken care of by any of the
operators/administrators)
2. Acknowledged (The alarm is taken by an operator, and marked with the
operators login name)
3. Terminated (The same as NetXMS meaning of Acknowledge. The alarm is
transfered to the history view)

On new alarm, alarm clearance flag is set to off, and on clear its set
to true (In the picture in the column A).
Today NetXMS has simple clear correlation feature which just acknowledge
the alarm with specified identifier. This way of doing it makes it hard
for the operator to really see what has happened.

The Original Event Time is the first occur of the alarm, and Event time
is updated on every update on the alarm (ex. on clear or repeated alarm)

Column P is the status of an incident report if the alarm was
reported/attached by the operator to a trouble ticket system(TTS)
(Servicedesk, Remedy etc). If so you are not able to terminate the alarm
until the TTS has released the handle. (Of course the TTS must have a
way of communicate with NetXMS. )

The column O is Outage. If the device is set to outage, a flag will
appear here.

I would also propose multiple alarmlists (Operational Context in TeMIP
(OC)), TeMIP has the ability to distribute the event to one or more OCs.
Use cases:
- Diffrent OC for diffrent equipment
- OC per responsibility areas (Networkadmin / Serveradmin)
- OC per location

Please consider my suggestions, and excuse my bad English. NetXMS is
becoming a great / advanced product with good potentials.

-- 
Christoffer Blindheim