VoiceAlarm is a standalone application allowing interaction with a control system using a common
telephone and handset.  Supporting off the shelf voice capable modems, process exceptions are played in
the operators voice allowing acknowledgement through touch tone entries made from the handset.

VoiceAlarm monitors process alarms using OPC,  ODBC, and direct connection to the CPUtilities RTDB.  
Alarm messages are recorded using an inexpensive microphone attached to a standard sound card.
See additional requirements at bottom of page
Process Connection

The connection to process alarms can be made using any one or combination of three methods:

  • OPC allows connections to hundreds of PLCs and field devices through third party drivers.  Popular
    SCADA packages support OPC clients providing an access path to process exceptions.

    VoiceAlarm provides an intuitive browser interface allowing simple point and click selection from
    the OPC Server's item address space.

  • Making an ODBC connection to a database table allows VoiceAlarm to access alarm values from a
    variety of external sources.  Using a "single record" table, notifications may be triggered by any
    SCADA or database application.  Exceptions may come from one or more tables and may even span
    across databases from unique Vendors.

    Using an intuitive point and click interface,  table columns are interactively browsed during alarm

  • A native connection to the CPUtilities, RTDB allows notifications to be generated from any project
    tag.  Tags are selected for processing using an interactive browser interface.

VoiceAlarm provides "system health" monitoring for each of the three methods.  Notifications may be
activated if the source connection fails for any reason.  When failures are detected, a new connection will
be attempted each few minutes allowing automatic system recovery.

Call Interaction

A call session is initiated by either the state change of a monitored exception or when an incoming call is
detected.  The user is greeted with a welcome message and prompted for a password.  On successful
login, each active alarm's message is played followed by a menu prompting for the desired action to take.  
Alarms may be acknowledged, disabled, or skipped.

Additional menu choices provide message playback of recent call session actions allowing users to access
prior acknowledged and disabled alarm states.

Email and Text Message Notification

System users may be setup to receive phone calls, an email, and/or text messages when alarms enter the
active state.  This notification includes the alarm description, date and time, and the pre-configured
interval the exception was in the pending state prior to a call out.

Recording Messages

All menu, prompt, and alarm messages are recorded and stored in the Window's wav file format.  Up to 30
seconds of audio may be recorded for each alarm including alarm identification and optional comments to
plant personnel directing their course of action.

Microsoft TAPI

Designed on TAPI technology, VoiceAlarm is compatible with a variety of voice modem hardware.  
Although the software has been tested with external serial and USB modems, internal versions provide the
highest audio quality.

System Requirements

  • Windows XP Professional, Windows 7, Windows 8, or Windows 10
  • ODBC Driver and Database Software (option)
  • OPC Server Driver (option)
  • CPUtilities SCADA Software (option)
  • Minimum 2 GHz Processor, 4GB RAM
  • Video Adapter 1024 x 768 Pixel Resolution or Greater
  • Sound Card with Microphone attached to Line In Jack
  • Voice Capable Modem or Voice Telephony Board (note)
  • 512 GB HD

One or more of the three noted options must be included for the connection to the process alarms.

Telephony boards supporting the TAPI 3 specification are compatible.  Intel Corporation provides se
cards in their Dialogic line of products.  Less expensive PCI modems, such as p
roducts based on the
Conexant chip set
work well.  Modem brands must support the Telephone Answering Machine (TAM)