Notification system
From Wikipedia, the free encyclopedia
A modern notification system is a combination of software and hardware that provides a means of delivering a message to a set of recipients. For example, notification systems can send an e-mail when a new topic has been added to Wikipedia. The complexity of the notification system is often dependent on the types of messages that must be sent. An e-mail noting when a page has been inserted into Wikipedia is adequate for such a straightforward task. However, notifying individuals when a building is on fire would require real-time interaction, escalation, scheduling, rosters, and fail-over scenarios.
Contents |
[edit] Notification system features
[edit] Opt-In
A notification system is only as good is the contact data contained within. Uploading recipient data is not ideal, as data can be wrong (miskeyed number or letter), false (purposely wrong data), or invalid (phone number has changed). Therefore, notification systems with opt-in data collection can validate data in realtime for all said errors and more. In addition, due to the escallation of unwanted email (spam) and unwanted calls (do not call list), notification system providers are weary of violating existing laws and/or blacklisting by 3rd parties who carry the notification. An opt-in process of collecting data harbors the provider from unlawful use, because each recipient is giving the notification provider permission to contact him or her.
[edit] Real-time interaction
In the event of a fire, or any emergency situation that requires human intervention, notification systems can provide a way of accepting feedback. The feedback can be used to determine what tasks the system should perform. For example, a chief firefighter, when notified of a pending fire, must acknowledge that the truck is en route, thus eliminating the need for further notifications.
[edit] Escalation
The criticality of an event might change before the event is finally resolved. Sometimes a small failure may trigger a chain of failures that can lead to events that require immediate attention. For example, an e-mail that fails to send is not a significant error, and may be classified as a warning. However, the original incident that noted the e-mail failure may spawn a ping of the mail server responsible for relaying the e-mails. If the ping fails, the event may be escalated to a severe level, to indicate that a more important issue requires resolution.
[edit] Scheduling
When deciding the list of recipients to notify of an event, a notification system might take into consideration the hours in which a recipient can be notified. Someone working a midnight shift may be available for handling emergencies between 11:00pm and 7:00am. The system should make no attempt to notify this person outside of those hours. A notification system could take into consideration vacation times, weekends, holidays, and so forth, to prevent notifying people when they are not available.
[edit] Rosters
If a notification system cannot contact the intended party, often it is not sufficient to let the matter drop. In the previous example, the chief firefighter was informed of a pending fire. However, if the chief was assisting a tree-bound cat, the notification might not reach its target. Consequently the system must find another person to notify, typically by scanning a predefined roster.
[edit] Fail-over scenarios
High availability means that a system must be up and running 99.999% of the time. The only acceptable downtime is for upgrades, which must be kept to an absolute minimum. To achieve the goal of high availability (HA), software-based notification systems must take into consideration the failure of hardware upon which they are running. The hardware failure could be as simple as someone accidentally unplugging a network connection, or as messy as a hard drive crash. The "brains" of the notification systems are often distributed across separate physical machines to ensure that if one machine is no longer available, another system can handle sending messages and resolving new events.
[edit] Interactive media
The number of ways a person can interact with technology has steadily increased. Advanced notification systems support at least one and sometimes all of the following communications media:
- Text Messaging (SMS)
- Voice (telephone, cellphone, VoIP, outdoor loudspeaker, indoor PA system)
- E-mail (POP, IMAP, SMTP)
- Desktop alert (PC, Mac)
- Pager (SNPP)
- Instant Messaging (AIM, Jabber, MSN, ICQ)
- RSS (RSS reader, digital signage)
- Web page (Javascript, XML)
- Fax
[edit] Industries
Notification systems are used throughout the following industries:
- Financial institutions (banks, stockbrokers, credit unions)
- Emergency services (police, fire department, ambulance)
- Manufacturing (computer hardware, motorcycles, television)
- Information technology (help desk, networks, software monitors)
- Weather (storms, earthquake, tsunami)
- Government
- Education
[edit] See also
- Driver-Attentive Notification System
- Emergency telephone number
[edit] External links
- Desktop Alert - Mass Notification Products. Desktop Alert, Inc.
- Omnilert - Multimodal Notification Network. Omnilert, LLC.
- e2Campus - Emergency Notification System. e2Campus.com.
- Amerilert - Mass Notification System. Amerilert.com.
- TechRdium, Inc. Patent Holder 7,174,005 and 7,130,389 in Modern Emergency Notification Systems. USPTO (2008-04-01). Retrieved on 2008-04-01.
- 0395440 Emergency Notification Systems. Educause Connect (2007-09-19). Retrieved on 2007-09-21.
- Rutrell Yasin (2007-04-30). Emergency notification systems get the call. GSN.com. Retrieved on 2007-09-21.
- Notification Systems Research @ VT. Virginia Polytechnic Institute and State University. Retrieved on 2007-09-21.
- Public Safety Emergency Notification System. PoliceSoftware.com.
- ccAlert - Mass Notification Service. Contextconnect.com.
- Send Word Now Alert & Response Management Service. SWN Communications Inc..

