« Message-driven SOA - what goes around? | Main | Don't be afraid to ask for SOA help »

August 29, 2008

Alerts vs Notifications - moving to a business focus

I have been doing some research recently on how the world of alerts has changed, and I am now a convert in the alerts vs notifications debate to the notifications team. The change of terminology is not just cosmetic - to me it really represents the difference between a technical perspective and a business one, and the business one embodies so much more value.

My own memories of alerts stem from systems management tools, where if a monitor detected a problem an alert was sent to the operational bridge or perhaps some other node for action. This is a simpe answer to a technical problem - "I need to let someone know that something has happened, so they can work out what to do (if anything)". But from a business perspective this is pretty damn inadequate. This 'fire and forget' approach of raising an alarm and then walking away is no good if there is a business reason to CARE about what might be done.

Notification is a different word - most dictionaries talk about alerts as 'warnings'. In contrast, the Oxford dictionary describes notify as meaning to 'inform or give notice to (a person)'. In other words, notifications are more about an exchange of information as opposed to turning on a warning light.

So what does this mean in real terms? Is this just a grammatical argument? The answer is - not at all. Notification software suppliers are focused not on just getting a warning out, but communicating with the 'right' individual to get some action to happen and tracking activity to resolution. Good notification software has to not only get the message to the target in the appropriate way, such as email, SMS text, fax or voicemail, but also has to be able to 'close the loop' in the whole process of reacting to the detected event. For example, what if the target person is not available? Can calendars be consulted? Is there a way to implement an escalation process? Can the recipient of the notification communicate status back? Is there a way for the notification to be officially closed when resolved?

If real business value is to be obtained from notifications, it is imperative that the whole notification process can fit into the overall operational workflow. For anyone interested in more about this subject, and the necessary functionality to make closed loop notifications work, Lustratus has just published a report, "Closed Loop Notification Software", available from the Lustratus store.  

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d834539c9269e200e5547379058833

Listed below are links to weblogs that reference Alerts vs Notifications - moving to a business focus:

Comments

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

June 2009

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

Statcounter