AlertWorks®
1.2
Building Blocks
for Wireless Alerting & Monitoring Applications |
|
mobileFOUNDATIONS'
alerting products (IncidentPortal®
for homeland
security and
FASAT for space operations and command
and control) are the most advanced monitoring and
alert notification products for their respective
industries. These products are built on
mobileFOUNDATIONS' AlertWorks®
technology
components: the AlertWorks Data Broker, the
AlertWorks Incident Engine, and the
AlertWorks Messaging Gateway. |
|
Now for the first time, these
components are available individually or combined, for integration
within third-party applications, under the Powered by AlertWorks™
licensing program. This allows companies to cost-effectively add
robust monitoring and/or alerting technologies to their applications,
without the significant research and development effort that would be
required.
AlertWorks Components
|
AlertWorks
Data Broker |
The Data Broker autonomously monitors external data sources (e.g.,
chemical and biological sensors) for user-defined “events of
interest.” Users first define what data sources to monitor via an
easy-to-use Web interface. Next, users build filters that define
the “events of interest” for each source (e.g., sensor “X” reads
“high”). Once the Data Broker identifies an event of interest, it
passes that data to the AlertWorks Incident Engine (described
below) for alerting. This relieves your staff from time-consuming
monitoring and logging duties. The Data Broker can monitor data
sources over a network (push or pull) or in a log file. It can
also monitor ASCII text, binary data, and XML streams.
|
|
|
|
AlertWorks
Incident Engine |
The Incident Engine can manage
all of the alerting logic for your application, including call
trees, round robins, group alerts, and alerts to individuals. It
also determines what content to send to each person, which devices
to notify, and in what order (for people who have multiple
devices). The Incident Engine also can be set to send “reminder”
messages to personnel who have not yet responded to an alert.
When combined with the AlertWorks Data Broker for monitoring
telemetry, the Incident Engine can also provide advanced data
distribution functions, such as: what should trigger an initial
alert, how often to send updates, what defines enough change in
the data to cause additional alerts, and when an incident ends.
In others words, the Incident Engine can monitor and track the
“state” of the incident. It also provides a user interface
component that provides a visual status of all of the
notifications and responses.
|
|
|
|
AlertWorks
Messaging Gateway |
The Messaging
Gateway is the heart of the alerting system. The
Messaging Gateway does not
just send simple text messages; instead, it employs comprehensive
messaging capabilities for wired (email) and wireless devices
(pagers, cell phones, PDA’s, PC’s, telephones via voice). The
Messaging Gateway supports both one-way and two-way alerting. The
Messaging Gateway has “knowledge” of the capabilities and limitations of the various
carriers and devices. It formats all messages to maximize content
and capability. The Messaging Gateway currently supports the following
protocols: SMS, SMTP, WCTP, TAP, and SNPP. The Messaging Gateway
can send messages over many networks including TCP/IP, 802.11, CDPD, CDMA, GPRS, and ReFLEX. The
Messaging Gateway can be accessed by your
application via XML. The Messaging Gateway also supports the CAP Protocol.
The Messaging Gateway can be coupled with the AlertWorks
Incident Engine and
Data Broker to provide an end-to-end monitoring and alerting
capability.
|
|
|
Download an
AlertWorks Brochure.
If you are interested in using
AlertWorks
to improve the operations of your enterprise or just wish to
find out more about this product please email us at
info@mobilefoundations.com.
Copyright 2001-2008 - mobileFOUNDATIONS®,
Inc. - All Rights
Reserved |
|
