Nimbus Alarm Server

Nimbus provides a solution for handling events from an alarm system to a variety of different  recipients, e.g: SMTP (email), HTTP (web), SMS (mobile phone) and pager.

The handling of the alarm events is based on different 'alarm route profiles'. According to different criteria, e.g. date, time, tag name, area, priority etc, the alarms are forwarded to the correct recipients.

An example of a system that can be imported is Alarm Viewer. The alarms can
be forwarded, by Nimbus, to different recipients, both sequentially and in
parallel. A list of some of the supported protocols is found below.


Example of usage:

The alarm reception programme AlarmViewer receives alarms via a
GSM-modem, e.g. a MultiModem V3. The alarms are automatically routed
into Nimbus, where they are processed and forwarded according to the configured alarm profiles.

Features:

Nimbus forwards alarm events using pre-defined profiles. Selections can be made based on date, time, tag name, area, priority etc. The alarm is then forwarded to the correct recipient.

Plain text messages can be sent with Nimbus Administrator or Nimbus Web Server.
 
Nimbus supports the following types of recipient :
- Most SMS recipients (UCP, TAP, PC-Text) etc.
- SMS via a MultiModem for quicker SMS (<15 seconds) without a land line.
- SOSAB and SECURIS (Securitas ASN.1 protocol).
- Different pager systems, e.g. MiniCall Text, MiniCall Numerik,
  TelePage Swiss, BT etc.
- Fax Class 2 and Class 2.0
- Network printers, e.g. '\\SERVER1\ALARMPRINTER'
- LPD printers using only an IP adress and port
- Local printers via DOS (no page feeds) with prefix/suffix codes
  (for different colours etc.)
- Modem printer
- Email (SMTP)
- HTTP for showing alarm lists in Web browsers
- Nimbus Alarm Receiver with modem or TCP/IP for Inter- /Intranet
- Text files
- ESPA 444
etc...

New recipient types are usually easy to add with a simple script file if some of the built-in protocols match.

Each recipient type has its own printing format. It can easily be changed to fit the current application.

Almost unlimited:
200 recipients
200 recipient types
100 users
100 profiles

The number of attempts to re-send and the re-send interval can be changed.

COM1 - COM16 can be used to send data via one or more modems. The port is closed between each session for other applications to have access.

Alarms can be sent according to sequence lists, i.e. if the alarm can not be received it is automatically forwarded to the next recipient.on the list.

Nimbus is available in English and Swedish but can be adapted to other languages.

Each alarm event is logged in a text file which can be stored for several months.

It is simple to install and easy to configure for an existing unit.

Can be run as service in Windows NT

The programme is built by defining
the recipients...




creating rules for the existing recipients in an 'alarm route profile'...




and then forwarding the alarms.