![]() |
|||||||||||||
![]() |
![]() |
||||||||||||
![]() |
![]() |
|||||||
| |
|
|||||||
|
|
||||||||
|
GARNET can be used by any organization needing a reliable, near-real-time delivery method for emergency alerts as well as other time-sensitive messages and announcements. Federal, state, and local governments as well as education and industry can benefit from GARNET’s wide-range of alerting applications:
|
||||||||
|
Technology Details |
How It Works
Disseminating alerts The heart of the simple-to-use GARNET system is a secure, Web browserbased interface. Authorized administrators enter alerts into the system. The administrator can select a severity level, message delivery method(s), and the group of affected users to whom the alert will be disseminated. The alert is then distributed to only those users, along with a link to further information such as suggested actions and related instructions. Alerts interrupt end-users’ work on desktop PCs, cell phones, PDAs, and other communication devices, helping to ensure that the message is acknowledged. Using push and pull technology to increase effectiveness Desktop PCs have two methods of polling a server for new messages or alerts:
Because e-mail alerts using only pull technology have an inherent delay, they may result in potential hazards in true emergency situations. To increase the timeliness of alert delivery, the GARNET system employs both push and pull technologies. The server is configured to push alert messages to systems that are not behind a firewall. Systems that are behind a firewall poll the server at intervals to receive new alerts. These determinations are made during client software startup and login. Securing alerts through a reliable system GARNET provides secure alert-delivery channels using SSL, server push/client pull technologies, and firewalls. Administrators are authorized before alerts can be sent through the GARNET system. The system provides separate zones for application servers and for replicated Web servers. Each zone is secured by a firewall. To send alerts, the Internet may refer to a center-wide network or to the Internet itself. Alert access can be limited to the network center to maximize security. System requirements, configuration, and maintenance Typical installation on a server usually requires the following software*:
Minimum software configuration requires only a central server with a database; however hosting the software on redundant servers with failover and load-balancing capabilities helps improve system reliability. Maintenance of the software is minimal; however, the system must be retested after any major operating system release and installation or when new versions of Java replace the current version. Why GARNET Is Better Historic and existing alert systems, such as fire alarms, PA systems, and sirens cannot provide the breadth and depth of information distributed by the GARNET system. Specifically, sound-based systems do not provide descriptive information about the alert and may not be adequate for communicating messages to the hearing impaired. Televisions can provide the detail but may not be turned on or tuned to the right channel to receive alerts. Using only PC or e-mail-based alerts does not account for users who are not at their desks or other e-mail systems. In addition, most existing alert systems cannot avoid interrupting people who may be unaffected by the information being distributed.
|
|||||||
|
Commercial Opportunity |
To request a demo, please contact Jack Spain at: (919) 342.6502 or by .
|
|||||||
|
Contact Information |
, (919) 342-6502
|
|||||||
This technology is owned by NASA Goddard Space Flight Center |
||||||||
![]()
Fuentek, LLC
Phone: (919) 303-5874
© 2008, Fuentek, LLC. All Rights Reserved.