Remote Alarm Manager

Operating Manual
Copyright Notice
We at Schneider Electric have tried to make the information contained in this
document as accurate and reliable as possible. Nevertheless, Schneider Electric
disclaims any warranty of any kind, whether express or implied, as to any matter
whatsoever relating to this document, including without limitation the
merchantability or fitness for any particular purpose. Schneider Electric will, from
time to time, revise the product(s) described in this document and reserves the
right to make such changes without obligation to notify the purchaser. In no event
shall Schneider Electric be liable for any indirect, special, incidental or
consequential damages arising out of purchase or use of this document or the
information contained herein.

Do not use the product(s) for any other purposes than those indicated in this
document.

Only licensed users of the product(s) and the document(s) are permitted to use this document or any
information therein. Distribution, disclosure, copying, storing or use of the product(s), information or
illustrations in this document on the part of non-licensed users, in electronic or mechanical form, as a
recording or by other means, including but not limited to, photography or information storage and retrieval
systems, without the express written permission of Schneider Electric, will be regarded as a violation of
copyright laws and is strictly prohibited.

Copyright © 2011 Schneider Electric

All brand names, trademarks and registered trademarks
are the property of their respective owners. Information
contained within this document is subject to change
without notice. All rights reserved. www.schneider-electric.com/buildings
Operating Manual

Contents
INTRODUCTION
1 About this Manual. . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Acrobat (PDF) Conventions. . . . . . . . . . . . . 8
1.4 Typographic Conventions . . . . . . . . . . . . . . 8
1.5 Terminology. . . . . . . . . . . . . . . . . . . . . . . . 10
2 About the Remote Alarm Manager . . . . . . . . . . . 13
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Summary of Key Features . . . . . . . . . . . . . 15
2.2.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.2 Intelligent Routing . . . . . . . . . . . . . . . . . . . 15
2.2.3 Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.4 Acknowledgement . . . . . . . . . . . . . . . . . . . 16
2.2.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.6 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 System Examples . . . . . . . . . . . . . . . . . . . . 17
2.4 How the Remote Alarm Manager Works . 19
OPERATING
3 Starting the Console . . . . . . . . . . . . . . . . . . . . . . 25
3.1 Starting the Console . . . . . . . . . . . . . . . . . . 25
3.2 Starting the engine service . . . . . . . . . . . . . 26
4 The Console Interface . . . . . . . . . . . . . . . . . . . . . 29
4.1 The Active Alarms Tab . . . . . . . . . . . . . . . 29
4.2 The Runtime Tab . . . . . . . . . . . . . . . . . . . . 31
4.3 The Configuration Tab. . . . . . . . . . . . . . . . 32
4.4 The File Menu . . . . . . . . . . . . . . . . . . . . . . 33
4.5 The Edit Menu . . . . . . . . . . . . . . . . . . . . . . 34
4.6 The Help Menu . . . . . . . . . . . . . . . . . . . . . 34
4.7 Alarm Banners . . . . . . . . . . . . . . . . . . . . . . 34
4.8 The Monitor . . . . . . . . . . . . . . . . . . . . . . . . 34
4.9 The Information Banner. . . . . . . . . . . . . . . 35

Schneider Electric, Sep 2011 3 (80)

 Operating Manual

5 Common Console Operations . . . . . . . . . . . . . . .37

5.1 About the Wizards. . . . . . . . . . . . . . . . . . . .37
5.2 Starting the Console . . . . . . . . . . . . . . . . . .38
5.3 Setting up Automatic Logon . . . . . . . . . . . .38
5.4 Modifying Active Actions. . . . . . . . . . . . . .39
5.5 Acknowledging Active Alarms. . . . . . . . . .41
5.6 Suppressing Alarm Actions. . . . . . . . . . . . .42
5.7 Setting Up Duty Exceptions . . . . . . . . . . . .43
5.8 Reviewing ‘On Duty’ Alarm Actions . . . . .45
5.9 Displaying Alarm Banners . . . . . . . . . . . . .46
5.10 Reviewing History . . . . . . . . . . . . . . . . . . .48
6 Message Management . . . . . . . . . . . . . . . . . . . . .49
6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
6.2 Operator Actions . . . . . . . . . . . . . . . . . . . . .49
6.3 Recipient Actions . . . . . . . . . . . . . . . . . . . .50
6.3.1 Replying to Messages . . . . . . . . . . . . . . . . .50
6.3.2 Accept, Busy and Refuse Messages . . . . . .50
6.3.3 Off-Duty or On-Duty Commands . . . . . . . .50
6.3.4 Formatting Replies to Messages . . . . . . . . .51
6.3.5 Responses to Busy and Refuse Messages . .52
6.3.6 Replying via the Web Interface. . . . . . . . . .53
6.3.7 Replying via the WAP Interface . . . . . . . . .57
ADMINISTERING
7 User and Recipient Management . . . . . . . . . . . . .65
7.1 Starting the Console . . . . . . . . . . . . . . . . . .65
7.2 User Management . . . . . . . . . . . . . . . . . . . .65
7.2.1 Modifying User Details. . . . . . . . . . . . . . . .66
7.2.2 Adding a New User . . . . . . . . . . . . . . . . . . .68
7.2.3 Deleting a User . . . . . . . . . . . . . . . . . . . . . .69
7.3 Recipient Management . . . . . . . . . . . . . . . .70
7.3.1 Modifying Recipient Details . . . . . . . . . . . .70
7.3.2 Adding a New Recipient . . . . . . . . . . . . . . .72
7.3.3 Deleting a Recipient . . . . . . . . . . . . . . . . . .72
7.4 Duty Roster Management . . . . . . . . . . . . . .73
7.4.1 Modifying a Duty Roster . . . . . . . . . . . . . .73
7.4.2 Adding a Duty Roster . . . . . . . . . . . . . . . . .77
7.4.3 Deleting a Duty Roster . . . . . . . . . . . . . . . .77
4 (80) Schneider Electric, Sep 2011
 INTRODUCTION
1 About this Manual
2 About the Remote Alarm Manager
Operating Manual 1 About this Manual

1 About this Manual

This manual explains how to use the Remote Alarm Manager software
with your Building Management System (BMS). Current compatible
systems are:
• BAS2800+
• MicroNet
• Satchwell Sigma
• TAC Vista.
The procedures within this manual apply to any of the above systems;
however for simplicity, just one system (Sigma) has been selected to
represent all systems where screenshots of the software are shown.
Screenshots from the other systems are very similar to those shown for
Sigma.
For information on how to install the software, refer to the Remote
Alarm Manager Engineering Manual.
For information on third party products, refer to the instructions deliv-
ered with the third party product.
If you discover errors and/or unclear descriptions in this manual,
please contact your Schneider Electric representative.

Note
We are continuously improving our documentation. This manual
may have been updated.
Please check http://extranet.tac.com for the latest version.

The Remote Alarm Manager is used for remote management of

alarms. The system monitors alarms from the BMS, distributes alarm
messages to the relevant people (recipients) using fax messages,
printed output, email or WAP/text messages on mobile phones, and
allows alarms to be accepted and acknowledged remotely.

Schneider Electric, Sep 2011 7 (80)

1 About this Manual Operating Manual

After reading this manual, you should understand how to use the soft-
ware to operate a Remote Alarm Manager Interface.

1.1 Structure
The manual is divided into the following parts:
• Introduction
The Introduction section contains information on how this man-
ual is structured and how it should be used to find information
in the most efficient way.
• Operating
The Operating section contains step-by-step descriptions of
how to carry out different tasks for day-to-day operation.
• Administering
The Administering section contains step-by-step descriptions of
tasks which are less frequent than day-to-day operation tasks.

1.2 Prerequisites
To be able to benefit from the contents in this manual, it is recom-
mended that you are familiar with your BMS(s) and that you read the
Remote Alarm Manager Engineering Manual.

1.3 Acrobat (PDF) Conventions

If reading this manual online in Adobe® Acrobat® Reader (.PDF file
format), numerous hypertext links exist for all entries in the Table of
Contents, and other standard cross references. These links are indi-
cated when the cursor changes to a hand with a pointing finger.

1.4 Typographic Conventions

The following conventions are used in this manual:
• Bold is used for option names.
• Italics are used for references to external manuals.
In addition, the following specially marked texts may occur through-
out the manual:

8 (80) Schneider Electric, Sep 2011

Operating Manual 1 About this Manual

! Warning
• Alerts you that failure to take, or avoid, a specific action
might result in physical harm to you or to the hardware.

Caution
• Alerts you to possible data loss, breaches of security, or
other more serious problems.

Important
• Alerts you to supplementary information that is essential to
the completion of a task.

Note
• Alerts you to supplementary information.

Tip
• Alerts you to supplementary information that is not essential
to the completion of the task at hand.

Advanced
• Alerts you that the following information applies to complex
tasks or tasks restricted by access.

Schneider Electric, Sep 2011 9 (80)

1 About this Manual Operating Manual

1.5 Terminology

Term Description

ADSL Asymmetric Digital Subscriber Line

BAS Building Automation System

BMS Building Management System

CD Compact Disk

DOA Det Offentlige Alarmnet (Danish public alarm

network

ESPA European Selective Paging Manufacturers’ Asso-

ciation

GSM Global System for Mobile Communications

ID Identification

IPX Internetwork Packet Exchange

ISP Internet Service Provider

MB Mega Bytes

PC Personal Computer

PDF Portable Document Format

RAM Random Access Memory

ROM Read Only Memory

SMS Short Message Service

SMTP Simple Mail Transfer Protocol

SPX Sequenced Packet Exchange

SVGA Super Video Graphics Adapter

10 (80) Schneider Electric, Sep 2011

Operating Manual 1 About this Manual

Term Description

TAP Telocator Alphanumeric Protocol

UCP Universal Computer Protocol

WAP Wireless Application Protocol

XML Extensible Markup Language

Note
This manual, together with the Remote Alarm Manager
Engineering Manual and the Remote Alarm Manager
Advanced Scripting Guide, is available as a PDF file in the
C:\Program Files\Schneider Electric\Binary\Remote
Alarm Manager\Manuals folder after installation, also via
the Start - All Programs - Schneider Electric - Remote
Alarm Manager menu option.

Schneider Electric, Sep 2011 11 (80)

1 About this Manual Operating Manual

12 (80) Schneider Electric, Sep 2011

Operating Manual 2 About the Remote Alarm Manager

2 About the Remote Alarm

Manager
2.1 General
The Remote Alarm Manager is a system for the remote display and
management of alarms. The system can collect and display alarms
from your BMS, distribute those alarms as messages to the relevant
personnel and allow remote message acceptance. This process is illus-
trated in Fig. 2.1.
Alarm messages can be distributed in a variety of different forms,
including as fax messages, printed output, e-mails or in WAP or text
messages to mobile phones. The content of messages can be custom-
ised, and can be different for different recipients.
Alarm messages can be routed to different recipients or devices
depending on factors such as alarm priority and type of alarm. Alarm
messages can be routed simultaneously to everyone in a call list, or in
rotation until one person in the list accepts the alarm. In addition, duty
rosters can be set up to specify the recipients or devices that are to
receive alarm messages during specified periods of the week.
To guarantee successful transmission, alarm messages can be set up to
require acceptance from a recipient. Acceptance can be carried out
from the Remote Alarm Manager ‘Console’ (the main user interface),
from a GSM or WAP-enabled mobile phone, by email, or from a Web
browser over the Internet. Accepting an alarm message can automati-
cally cause the alarm to be acknowledged in the Console and can also
cause that acknowledgement to be passed through to your BMS
(MicroNet View and Vista).
Typically, the Remote Alarm Manager is installed on the same PC as
your BMS, although the system supports full client/server networks,
where different components of the system can be installed on different
computers.

Schneider Electric, Sep 2011 13 (80)

2 About the Remote Alarm Manager Operating Manual

BMS Network (Sigma illustrated)

DNN

Alarms
DNN
UNC532
UNCx96

BMS with the Remote Alarm

Manager.
Alarm messages can be
accepted from, for
example, mobile
phones.

The Remote
Alarm Manager sends
alarm messages to Fax

remote personnel and devices

such as printers, fax machines
and mobile phones.

Fig. 2.1: The Remote Alarm Manager

14 (80) Schneider Electric, Sep 2011

Operating Manual 2 About the Remote Alarm Manager

2.2 Summary of Key Features

2.2.1 Alarms
• Monitors alarms from your BMS.
• A watchdog function enables the Remote Alarm Manager to
generate an alarm message if it is not able to communicate with
a source system or device.
• The content of alarm messages can be customised, and can dif-
fer between recipients and devices.
• Visual Basic scripts can be used to set up advanced actions on
receipt of alarms.

2.2.2 Intelligent Routing

• Alarm messages can be routed to different recipients or devices
depending on factors such as alarm priority and type of alarm.
• An alarm message can be routed simultaneously to everyone in
a call list, or in rotation until one person in the list accepts the
alarm (which can optionally acknowledge the alarm).
• A backup recipient or device can be nominated in the event that
a message cannot be delivered to any of the standard destina-
tions.
• Duty rosters can be set up to specify the recipients or devices
that are to receive alarm messages during specified periods of
the week.
• Temporary changes to duty rosters can be made. For example, a
recipient can be temporarily removed from a duty roster when
absent.

2.2.3 Acceptance
Acceptance applies to messages (or more correctly alarm messages)
which the Remote Alarm Manager sends to recipients.
The acceptance process determines whether a message is repeated to
the same recipient or sent (perhaps again) to other recipients. Accep-
tance is made via SMS text, WAP-enabled mobile phones, Web

Schneider Electric, Sep 2011 15 (80)

2 About the Remote Alarm Manager Operating Manual

browser, Email or at the Console; the user can choose to reply

"Accept", " Busy" or "Refuse".
Accepted messages can optionally cause the alarm to be acknowl-
edged in the Console.
A Remote Alarm Manager user can be associated with a MicroNet
View, BAS2800+ or a third party (XML) BMS user. Alarms acknowl-
edged in the Console are then automatically acknowledged in
MicroNet View (provided that the user account and access control
permits this) and can be acknowledged in a third party (XML) system
(using an acknowledgement file). It is also possible to pass an
acknowledgement from the console to TAC Vista (with some limita-
tions).

2.2.4 Acknowledgement
Acknowledgments generally apply to alarms as they arrive at the
Remote Alarm Manager. Acknowledgements made in the BMS are
passed through and shown in the ‘Active Alarms’ area of the Console
(subject to any filtering in the BMS Interface). Acknowledgement of
alarms in the Remote Alarm Manager is achieved in the Active
Alarms area of the Console or the Active Alarms section of the Web
page or WAP mobile phone interface.
Acknowledgements made in the Remote Alarm Manager can be
passed back to MicroNet View provided there is a "user association",
and with limitations, to TAC Vista.
An alarm being acknowledged can:
• Stop transmission of further alarm messages.
• Generate a message informing of the acknowledgement.
An alarm being cleared can:
• Stop transmission of further alarm messages.
• Send an alarm clear message.

2.2.5 Security
Access to the Remote Alarm Manager Console is available only to
identified users.
User privileges specify the actions users can perform.

16 (80) Schneider Electric, Sep 2011

Operating Manual 2 About the Remote Alarm Manager

2.2.6 History
All Remote Alarm Manager events, including configuration changes,
are logged.
History can be easily browsed using a navigation tree and is accessible
from the Console.

2.3 System Examples

Fig. 2.2 shows a straightforward example of a system which sends
alarm messages to SMS mobile phones and fax machines. The exam-
ple uses just one PC installed with a BMS and the Remote Alarm Man-
ager.

PSTN

BMS Modem

Fax
Remote Alarm
Manager

SMS
GSM Modem

SMS

GSM Network

Fig. 2.2: A Straightforward Remote Alarm Manager System

The next example (see Fig. 2.3) has interfaces to multiple output
devices: SMS and WAP mobile phones, fax machines, Web browsers
and TAP phones or pagers.
The example again uses just one PC for the installation of both the
Remote Alarm Manager and the BMS. However, with such a system,
it may be an advantage to install interfaces to, for example, the Web
browsers on a different client machine for performance and security
benefits. The benefits of client/server systems are described in the
Remote Alarm Manager Engineering Manual.

Schneider Electric, Sep 2011 17 (80)

2 About the Remote Alarm Manager Operating Manual

Fax

PSTN
TAP Service
BMS Modem
Software
Remote Alarm Modem

Manager

GSM Modem

GSM Modem

Internet

GSM Network

WAP
WAP Gateway

SMS
WEB Browser WAP

SMS
WEB Browser

Fig. 2.3: A More Complex System

18 (80) Schneider Electric, Sep 2011

Operating Manual 2 About the Remote Alarm Manager

2.4 How the Remote Alarm Manager

Works
This section explains the basic principles about how the Remote
Alarm Manager works.
The background functions (Remote Alarm Manager Engine & Inter-
face host) are described in the Remote Alarm Manager Engineering
Manual; The console is not normally running and is used for adminis-
tration and configuration (typically). All of these functions are trans-
parent to the user during day-to-day use (until an alarm occurs).
Refer to Fig. 2.4. The following take place:
1 An alarm occurs at the BMS (BAS2800+, Sigma, MicroNet or
Vista).
2 The Remote Alarm Manager picks up the alarm and initiates an
alarm action (configurable in Actions).
3 An alarm message is generated (configurable in Actions).
4 The alarm message is passed to a recipient with access to an
interface device (configurable in Interfaces). If the message is
to be sent to multiple recipients, it is sent either in rotation (one
recipient at a time) or to all recipients at the same time (configu-
rable in Actions).
5 A recipient (configurable in Recipients) reads the alarm mes-
sage directly at the interface device (e.g. at a printer) or indi-
rectly though a service provider (e.g. by mobile phone),
depending on the configured interface.
6 The recipient replies to the alarm message. Reply messages are
Accept, Busy or Refuse with respect to the alarm message.The
format of the message is configured in Interfaces. The method
of reply is via one of the following:
• At the console.
• Short Message Service (SMS) (i.e. text messages) on a
mobile phone.
• E-mail.
• Web interface.
• Wireless Application Protocol (WAP) interface.

Schneider Electric, Sep 2011 19 (80)

2 About the Remote Alarm Manager Operating Manual

If the recipient does not reply to the message within a configured

timeout period and the alarm message is configured to repeat, the
alarm message is repeated a set number of times or until the
recipient replies.
7 The Remote Alarm Manager reacts according to the recipient’s
reply message:
• If Accept is the reply message, alarm messages will stop
being sent and the recipient then assumes responsibility
for dealing with the event which caused the original alarm
in the BMS.
The Accept message can be used to acknowledge the alarm
in the Remote Alarm Manager Active Actions, and in the
case of MicroNet View (and to a limited extent, TAC
Vista), can also be used to acknowledge the alarm in the
source system (i.e. the BMS).
• If Busy or Refuse is the reply message, the Remote Alarm
Manager will try to find another recipient, if more than
one is configured and the delivery is set to be rotational. If
there are no more recipients then the alarm action will be
closed. If the recipients are configured to receive the
alarm message simultaneously, the alarm action will also
be closed (but see note below).

Note
The response of the Remote Alarm Manager to Busy or Refuse
varies according to configuration. The previous paragraph
describes general behaviour.

20 (80) Schneider Electric, Sep 2011

Operating Manual 2 About the Remote Alarm Manager

Fig. 2.4: How the Remote Alarm Manager works

Schneider Electric, Sep 2011 21 (80)
2 About the Remote Alarm Manager Operating Manual

22 (80) Schneider Electric, Sep 2011

 OPERATING
3 Starting the Console
4 The Console Interface
5 Common Console Operations
6 Message Management
Operating Manual 3 Starting the Console

3 Starting the Console

The Remote Alarm Manager Console provides the user interface for
configuring the system, viewing alarm information and determining
the status of the software. A description of the Console is contained in
Chapter 4.

3.1 Starting the Console

Start the Console as follows:
1 Select Console from Start - All Programs - Schneider Elec-
tric - Remote Alarm Manager.
2 If prompted, log on using your Remote Alarm Manager User
ID and password (these will be supplied by your system admin-
istrator):

3 If you are not prompted to log on, MicroNet View user access
control may be being used (see Page 66), or your Windows
login username may cause an automatic logon to the Remote
Alarm Manager (see Page 38 for details of how to set up auto-
matic logon).

Schneider Electric, Sep 2011 25 (80)

3 Starting the Console Operating Manual

When you have logged in, the Console is displayed, as shown next.
The Console contains three tabs:
• Active Alarms
• Runtime
• Configuration (only displayed if the level of access rights is set
to ‘Administrator’.
These tabs are explained in the next chapter.

Note that the name of the current user (in this case the Administrator)
is displayed in the bottom right hand side of the Console.

3.2 Starting the engine service

If the Console is not displayed, but instead the following screen
appears:

1 Click Close.

26 (80) Schneider Electric, Sep 2011

Operating Manual 3 Starting the Console

2 At the node (PC) where the Engine is located, Select Start - All
Programs - Schneider Electric - Remote Alarm Manager -
Computer Configuration. The Remote Alarm Manager
Computer Configuration Wizard will be displayed:

3 Click Finish. The following dialog will be displayed:

4 Click Yes. The services will be re-started and you can now start
the console as described at the beginning of this chapter.

Note
In normal operating mode, the Engine is started when the the PC is
started. Refer to Chapter 3 of the Remote Alarm Manager Engi-
neering Guide.

Schneider Electric, Sep 2011 27 (80)

3 Starting the Console Operating Manual

28 (80) Schneider Electric, Sep 2011

Operating Manual 4 The Console Interface

4 The Console Interface

The console contains three tabs and three menus as follows:
• The Active Alarms tab
• The Runtime tab
• The Configuration tab.
• The File menu
• The Edit menu
• The Help menu.

4.1 The Active Alarms Tab

The Active Alarms tab is used to review and determine the current
status of alarms and to acknowledge and delete alarms. It contains two
panes as follows:

The left hand pane displays the alarm groups. The right hand pane dis-
plays any alarms in a given group (scroll across to see acknowledge-
ment details). The following groups are at the top level:
• The Remote Alarm Manager group, which contains any sys-
tem alarms, such as those generated if an interface stops.

Schneider Electric, Sep 2011 29 (80)

4 The Console Interface Operating Manual

• A group for each source interface, which could be any compati-

ble Building Management System (BMS). In this case the BMS
is Sigma R4, which contains alarms generated by Sigma
(Release 4), divided into the following sub-groups:
• Controllers (displayed only if the interface is configured
to monitor controller status) – Contains alarms indicating
offline controllers.
• Objects – Contains object alarms. The group is subdi-
vided into the index view, as set up in the Sigma System
Manager.
• Messages (displayed only if the interface is configured to
collect system messages) – Contains Sigma system mes-
sages, such as "node reset".

Note
There can be more than one source (BMS) interface; each will
have its own structure. The number of columns in the right hand
pane is also determined by the source BMS.

An alarm-bell icon is displayed next to each alarm to indicate its sta-

tus. The meanings of the alarm icons are as follows:

Red bell – Alarm is still current and is not acknowledged.

Green bell – Alarm has cleared, but has not yet been
acknowledged.
Yellow bell – Alarm does not require acknowledgement.

Red bell with blue tick – Alarm has been acknowledged,

but has not yet cleared.

Note
If the text in the right hand pane is blue (when not highlighted,
there is an associated Active Action.
If the text is ‘greyed out’ (both panes), there is a fault associated
with the interface.

30 (80) Schneider Electric, Sep 2011

Operating Manual 4 The Console Interface

4.2 The Runtime Tab

The Runtime tab contains two panes as follows:

The left hand pane contains a number of options:

• Interfaces – Enables the current state of local interfaces to be
determined (generally for engineer use only).
• Active Actions – Shows how messages are being processed.
This is normally for engineer use only, but right-clicking on a
message and selecting Properties allows Accept/Busy/Refuse
of a message in the same way as for a remote response (to mod-
ify active actions, refer to page 39).
• Alarm Action Suppression – Allows alarm messages to be
suppressed between specified dates and times (to suppress
alarm actions, refer to page 42).
• Duty Exceptions – Enables a user, recipient, device or duty
roster to be placed off duty between specified dates and times.
You may want to do this if, for example, a recipient is on holi-
day (to set up duty exceptions, refer to page 43).
• On duty – Shows the alarm actions set up for each recipient, or
the recipients for all alarm actions (to review on duty recipients,
refer to page 45).
• Log – Enables the daily log to be reviewed. The log includes
details of, for example, previous alarms, when alarms were
acknowledged, and who acknowledged them. Engineering only.
The right hand pane contains detailed data relating to the selected
option in the left hand pane.
Schneider Electric, Sep 2011 31 (80)
4 The Console Interface Operating Manual

4.3 The Configuration Tab

The Configuration tab contains two panes as follows:

The right hand pane contains detailed data relating to the selected
option in the left hand pane.
The options on the Configuration tab enable you to change the config-
uration settings. Although the Remote Alarm Manager should have
been configured at the time of installation, it is likely that end users
will need to modify the system configuration from time to time.
Table 4.1 lists typical configuration tasks that should be carried out by
end users, and provides a cross reference for further information.

Table 4.1: Typical Configuration Tasks for End Users

Task Details Page

Change A Remote Alarm Manager user needs to be set 65
or add up for each person who needs to log in to the
new user. system, and for each person who is to receive
alarm messages (e.g. by mobile phone).
Change A recipient is the name of a person who will 70
or add receive alarm messages, and the method used to
new contact that person (e.g. fax). You may want to
recipient. modify existing recipient details or add new
recipients.

32 (80) Schneider Electric, Sep 2011

Operating Manual 4 The Console Interface

Table 4.1: Typical Configuration Tasks for End Users

Change A duty roster defines the periods within a week 73

or add that a set of recipients and/or devices are
new duty expected to receive alarm messages. You may
roster. want to make permanent changes to duty rosters
from time to time.

4.4 The File Menu

The options available in the File menu depend on which tab is cur-
rently selected. The options are:
• New - Enables you to create:
• New configuration components in the Configuration tab
(refer to Chapter 7, “User and Recipient Management”, on
Page 65 for examples of operator configuration).
• New Alarm Action Suppressions and Duty Exceptions in
the Runtime tab (refer to Chapter 6, “Message Manage-
ment”, on Page 49 for examples of operator runtime
actions).
• Delete - Enables you to delete Active Alarms (in the Active
Alarms tab), Active Actions, Alarm Action Suppressions and
Duty Exceptions (Runtime tab), and configuration components
(Configuration tab).
• Properties - You can choose to display a properties dialog for
each of the items as described for Delete above, except for the
configuration components properties which will be displayed in
‘Wizard’ pages (refer to Chapter 6, “Message Management”, on
Page 49 for a description of the Wizards).
• Log in... and Log out to the Remote Alarm Manager (refer to
Chapter 3, “Starting the Console”, on Page 25). The Log out
menu option will tell you who is currently logged in.
• Close - closes the Console.

Schneider Electric, Sep 2011 33 (80)

4 The Console Interface Operating Manual

4.5 The Edit Menu

The options available in the Edit menu depend on which tab is cur-
rently selected:
• If in the Active Alarms tab, you can acknowledge alarms or an
alarm group (see also Section 5.5, “Acknowledging Active
Alarms”, on Page 41).
• If in the Runtime tab you can accept one or all Active Actions
(see also Section 5.4, “Modifying Active Actions”, on Page 39).
• If in the Configuration tab you can quickly create new users,
recipients and duty rosters by using the Copy and Paste menu
options.

4.6 The Help Menu

The Help menu provides details of the software licences currently in
use; also which version of the Remote Alarm Manager is installed.

4.7 Alarm Banners

An alarm banner consists of a user specified panel with alarm counters
that match a specified alarm banner filter. When selected for display,
it will be displayed in the Remote Alarm Manager console above the
three console tabs. You can display as many alarm banners as there are
alarm banner filters.
To set up alarm banner filters, refer to the Remote Alarm Manager
Engineering Manual. To display alarm banners, refer to page 46.

4.8 The Monitor

The Monitor enables you to view and interact with Remote Alarm
Manager icons in the Windows Notification Area (to the right of the
Taskbar).
The icons are not displayed by default. To view the icons, select Start
- All Programs - Schneider Electric - Remote Alarm Manager -
Monitor.

34 (80) Schneider Electric, Sep 2011

Operating Manual 4 The Console Interface

The following icons can be displayed :

Indicates that the remote Alarm Manager Engine or Inter-

face Host is running.
Indicates the current status of alarms in the Console. If, for
example, there are unacknowledged alarms, the icon alter-
nates between yellow and red.
Indicates a licence problem.

An exclamation mark over an icon indicates that may be a problem

with one or more of the interfaces. An exclamation mark in a red back-
ground indicates an error (it is normal to see this before the software
has been configured). An exclamation mark in a yellow background
indicates a warning condition.

4.9 The Information Banner

The information banner provides a summary of alarms, interface
errors and actions.

The information banner is not displayed by default. To view the infor-

mation banner, select Start - All Programs - Schneider Electric -
Remote Alarm Manager - Information Banner.
You can control the display of the information banner using the right-
mouse menu (and also the display of the Remote Alarm Manager Con-
sole):

Schneider Electric, Sep 2011 35 (80)

4 The Console Interface Operating Manual

36 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

5 Common Console
Operations
The following are common end user operating procedures for a fully
configured and operational Remote Alarm Manager:
• Setting up Automatic Logon
• Modifying Active Actions
• Acknowledging Active Alarms
• Suppressing Alarm Actions
• Setting Up Duty Exceptions
• Reviewing ‘On Duty’ Alarm Actions
• Displaying Alarm Banners.
These procedures may take place at the Remote Alarm Manager con-
sole on a day-to-day basis. Other less common end user procedures i.e.
user and recipient management and the modification of duty rosters
are covered in the Administering part of this manual (see Section 7,
“User and Recipient Management”).
Other less common procedures e.g, printer replacement, change of
interface type such as replacing a traditional modem with a GSM
modem are covered in the Remote Alarm Manager Engineering Man-
ual.

5.1 About the Wizards

Remote Alarm Manager configuration at the console is done via con-
figuration ‘Wizards’. When adding new configuration components,
such as adding a new user or recipient to the system (see Chapter 7,
“User and Recipient Management”, on page 65), the appropriate wiz-
ard will guide you through the whole configuration process.
You can step backwards and forwards through the wizards; once you
have entered data or made selections in any page in the wizard, your
data or selections are held in the system until modified or deleted.

Schneider Electric, Sep 2011 37 (80)

5 Common Console Operations Operating Manual

When simply modifying a configuration component, such as changing

a recipient’s mobile phone number, you can go directly to the relevant
page of the configuration wizard by selecting that page on the left
hand side of the wizard.

5.2 Starting the Console

Start and log on to the Remote Alarm Manager Console as described
in Chapter 3, “Starting the Console”, on page 25.

5.3 Setting up Automatic Logon

You can set up the console to automatically logon for a certain user
without him having to use his ID and password.
To set up automatic logon:
1 Click the Runtime tab.
2 Click the System folder, then double-click Local console dis-
play:

3 In the Local Console Display dialog, click the Settings tab.

4 Enter your User ID and Password (in this example, the User ID
is WM for William Moss, an existing user)

38 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

5 Tick the Shift, Ctrl, Alt checkboxes in any combination.

Remember your settings, you will have to use this combination
of keystrokes when closing down the console.
6 Set the Other display related settings as required.
7 Click OK.

Note
Each time you shut down the Remote Alarm Manager, you must
press one or more of the Shift/Ctrl/Alt keys simultaneously in the
combination selected, before closing the console dialog, otherwise
the console will not shut down. When restarting the console, you
will no longer need to use your user ID and password.

5.4 Modifying Active Actions

Active actions show how messages are being processed. You can
Accept/Busy/Refuse a message in the same way as for a remote
response (see page 50).
To modify an active action:
1 Click the Runtime tab.

Schneider Electric, Sep 2011 39 (80)

5 Common Console Operations Operating Manual

2 Click the Active actions folder.

3 Right-click the active action of interest and select Properties.
The Active Action Properties page will be displayed.
4 Review the properties and if required, click Accept, Busy or
Refuse.

40 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

5.5 Acknowledging Active Alarms

Acknowledging an alarm indicates that you have understood the alarm
and are taking the appropriate action.
To acknowledge an alarm:
1 Click the Active Alarms tab.

2 Right-click on the alarm and choose Acknowledge. The

Acknowledge dialog will be displayed, prompting you to enter
acknowledgement text.
3 Enter text if required and click the Acknowledge button. The
alarm will then be displayed with a blue tick to signify that it
has been acknowledged:

You can also select an alarm group and choose Acknowledge

group. All alarms in the group and in its sub-groups will be
acknowledged, or you can right-click in the alarms area and
choose Acknowledge group.

Schneider Electric, Sep 2011 41 (80)

5 Common Console Operations Operating Manual

Alarms can also be acknowledged remotely; see page 50.

Note
Alarms acknowledged through the Remote Alarm Manager are not
automatically acknowledged in Sigma (although they can be in
MicroNet View if you are configured to have a ‘user association’
with that BMSSome acknowledgements (with limitations) can
also be passed back to TAC Vista.

5.6 Suppressing Alarm Actions

Alarm action suppression allows specific alarm messages to be sup-
pressed between specified dates and times.

To suppress an alarm action:

1 Click the Runtime tab.
2 Click Alarm action suppressions.
3 Double-click Add new alarm action suppression...

42 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

4 In the Alarm Action Suppression dialog, click an individual

alarm, or select a folder containing a group of alarms, for which
you want alarm actions to be suppressed:

5 Enter the times and dates you wish to start and stop suppression
of the alarm actions.

5.7 Setting Up Duty Exceptions

The Duty Exceptions option in the Runtime tab is of particular use to
end users, as it enables a user, recipient, device or duty roster to be
placed off duty between specified dates and times. You may want to
do this if, for example, a recipient is on holiday.

To set up a duty exception:

1 Click the Runtime tab.
2 Click Duty exceptions.

Schneider Electric, Sep 2011 43 (80)

5 Common Console Operations Operating Manual

3 Double-Click Add new duty exception....

4 Complete the Duty Exception dialog. Note the following:

• The drop-down Off duty identity list contains all pre-
configured users, recipients, devices and duty rosters.
• You can set the off duty period to be indeterminate, or for
a set period of time up to 12 hours, or until a certain date.
• You can redirect messages to an alternative recipient or
device during the off-duty period.

44 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

5.8 Reviewing ‘On Duty’ Alarm Actions

‘On duty’ shows the alarm actions set up for each recipient, or the
recipients for all alarm actions. You can also send a message to any
individual recipient.
To review on duty alarm actions:
1 Click the Runtime tab.
2 Click On Duty.

3 You can then select to View by recipients or to View by alarm

actions.
To send a message to a recipient:
1 Right-click the name of the recipient and click Send Message.
2 In the Send message to... dialog, type your message and if you
require the recipient to accept the message, tick the Message
acceptance expected checkbox.

Schneider Electric, Sep 2011 45 (80)

5 Common Console Operations Operating Manual

5.9 Displaying Alarm Banners

To display alarm banners:
1 Click the System folder, then double-click Local console dis-
play:

2 In the Local Console Display dialog, click the Alarm Banner

tab.

3 Select Yes - display alarm banner with the panels below.

4 Click OK. An alarm banner will be displayed for each filter
present, and each alarm banner will match the state of the
alarms within that filter. For example, the alarms shown below
in the right hand pane are the critical alarms shown in the left
hand banner:

46 (80) Schneider Electric, Sep 2011

Operating Manual 5 Common Console Operations

Note
If no filters are present, or if you wish to reconfigure a filter, refer
to the Remote Alarm Manager Engineering Manual.

To turn off the display of all alarm banners:

1 In the Alarm Banner tab, select No - just display active
alarms in groups.
2 Click OK.

Schneider Electric, Sep 2011 47 (80)

5 Common Console Operations Operating Manual

5.10 Reviewing History

Reviewing history is primarily an engineer function, although there
may be occasions when the end user needs to review the logs. The log
shown is a complete system log, i.e. Engine and interfaces.

To Review History:
1 Click the Runtime tab.
2 Click Log. The logs are grouped in folders by date. Alarms,
messages and user activity are among the activities recorded.
The level of logging for the Engine can be set in the System
folder of the Configuration tab. In addition, the level of logging
for the interfaces can be set in the Debugging page of each inter-
face. Refer to the Remote Alarm Manager Engineering Manual.

48 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

6 Message Management
6.1 General
It is assumed for the purposes of this chapter that the person who is
responsible for the day-to-day operation of the Remote Alarm Man-
ager console is called the operator and that any person who receives
messages from the Remote Alarm Manager is called a recipient.

6.2 Operator Actions

As the console operator you must be aware of the formats required for
the recipient’s replies to Remote Alarm Manager messages; these will
have been set up by the person who installed and initially configured
the Remote Alarm Manager. It is also essential that you make all
recipients aware of the formats that have been set for replies to mes-
sages.
For more information on how to change the formatting of the recipi-
ent’s replies to messages, refer to any of the relevant output interface
descriptions (GSM Modem, WAP Server, Web Server or E-mail inter-
faces) in Chapter 9 of the Remote Alarm Manager Engineering Man-
ual.

Schneider Electric, Sep 2011 49 (80)

6 Message Management Operating Manual

6.3 Recipient Actions

6.3.1 Replying to Messages
If you are using the GSM Modem, WAP Server, Web Server or E-mail
interface, you can reply to alarm messages remotely. You can also use
these methods to reply to messages which you have received via an
interface through which you cannot reply to a message, e.g. a printer
or a fax machine.
If you have access to the Remote Alarm Manager console you can also
make your reply there.

6.3.2 Accept, Busy and Refuse Messages

When you receive a message from the Remote Alarm Manager (for
example, at a mobile phone), you can choose one of three actions:
• You can ‘accept’ the message. This will stop any further mes-
sages being sent to other recipients or from being repeated to
the same recipient. It may also acknowledge the alarm in the
Active Alarms tab depending on how the alarm action is set up.
• You can indicate that you are ‘busy’ and the Remote Alarm
Manager should try to find another recipient. In this case, you
may receive the message again if no other recipient accepts the
message.
• You can ‘refuse’ the message, indicating that you cannot attend
to it. You will not receive the message again.
The method used to reply to alarm messages depends on the interface
you are using. For further details of a particular interface, refer to the
Remote Alarm Manager Engineering Manual. For detailed informa-
tion about the actions following Busy and Refuse messages, refer to
Section 6.3.5, “Responses to Busy and Refuse Messages”.

6.3.3 Off-Duty or On-Duty Commands

If you are using the GSM Modem, WAP Server or E-mail interface,
you can send a command (e.g. from your mobile phone) to take you
off duty for a specified number of hours. A separate command allows
you to report back on duty before the off-duty period has elapsed.

50 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

Refer to the relevant interface description in the Remote Alarm Man-

ager Engineering Manual for further details.

6.3.4 Formatting Replies to Messages

When responding to a message from the Remote Alarm Manager, you
can either reply with a text message or you can send an On or Off duty
command. In either case, the formatting of the reply or command is
pre-configured in the Remote Alarm Manager and it is this formatting
which is expected. It is therefore strongly recommended that you talk
to the person who operates the interface to determine the correct for-
matting.
Some examples of the different formatting for recipient replies to mes-
sages are shown in Table 6.1.

Table 6.1: Examples of Recipient Reply Formats

ACCEPT BUSY REFUSE OFF DUTY OFF DUTY

USR PASS USR PASS USR PASS USR PASS USR PASS
A 123 B 123 R 123 OFF X ON

USR PASS USR PASS USR PASS

ACCEPT BUSY 123 NO 123
123

USR PASS
OK 123

USR PASS
YES 123

Key:
USR = User ID
PASS = Password
123 = Message number
X = Number of hours off duty

Schneider Electric, Sep 2011 51 (80)

6 Message Management Operating Manual

6.3.5 Responses to Busy and Refuse Messages

Table 6.2 shows in detail the actions that take place when a Busy or
Refuse message is sent to the Remote Alarm Manager, depending on
configuration settings.

Table 6.2: Remote Alarm Manager responses to Busy and Refuse

Number of 1 1 >1 >1 >1 >1 >1 >1

recipients

Delivery Type - - Sim Sim Rot Rot Rot Rot

Number of times 1 >1 1 >1 1 >1 1 >1

to each recipient

Number of cycles - - - - 1 1 >1 >1

through recipients

Action when Busy C C CD NR+ NR NR0 NR+ NR-1

message Rec’d

Action when C C C C NR NR0 NR0 NR0

Refuse message
Rec’d

Key:
>1 = Multiple.
Sim = Simultaneous delivery to Recipients.
Rot = Rotational delivery to Recipients.
C = Action Closed immediately.
CD = Action Closed after Delay.
NR = Message passed to Next Recipient.
NR+ = Message passed to Next Recipient; recipient will receive further
messages.
NR-1 = Message passed to Next Recipient; recipient will receive all ex-
cept one of further messages.
NR0 = Message passed to Next Recipient; recipient will not receive fur-
ther messages.

52 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

6.3.6 Replying via the Web Interface

The Remote Alarm Manager web interface allows you to view, via a
web browser, a subset of the data that you would normally be able to
view if you were at the Remote Alarm Manager Console.
You will have to log in to the interface using the same user ID and
password you would use to access the Remote Alarm Manager Con-
sole.
Using the web interface, you can also reply to messages that you have
received via another interface, but cannot reply via the same interface,
e.g. a printer or fax machine.
The web interface contains an interactive list on the left hand side of
the page, as shown below:

By default, ‘Your messages’ is the first page displayed. This will dis-
play all current messages for a user.
The available pages are described as follows:
• Your messages - displays all your current messages. On this
page you can select Accept, Busy or Refuse as required. The

Schneider Electric, Sep 2011 53 (80)

6 Message Management Operating Manual

messages are not necessarily alarm messages, they could be

clear messages; each message will be preceded by an appropri-
ately coloured alarm symbol. In addition, the message symbol
will display the status of the message (accepted, busy or
refused).
• Active alarms - this is the list of current alarms in the Remote
Alarm Manager, with the times the alarms arrived. If you click
on an individual active alarm, its details will be displayed and
you can acknowledge it here, which will cause a corresponding
acknowledgement in the console.
• Active messages - this is the list of Active Actions and corre-
sponds to the list of Active Actions shown in the console.
• Interfaces status - the list of current interfaces and whether
they are functional.
• Recipients on duty - a list of recipients on duty, shown by
alarm action and by recipient.
• End session - enables you to terminate the current web session.
Starting the web interface
Start the web interface as follows:
1 Open your web browser and enter the address of the PC where
the Remote Alarm Manager is running.
2 Enter your Remote Alarm Manager User ID and Password.

Note
You can use two methods of addressing this PC:
• Use the IP address, in the format:
http://12.157.73.26:781/
• Use the PC name, in the format:
http://wsukb0qs41j:781/. You can find the computer name in
the System section of the Control Panel.

54 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

Accepting a message
To accept a message:
1 In the Action drop-down list, select either Accept, Busy or
Refuse, relating to the message you have received.

2 Click the Submit button. The message will disappear from the
list, and the Remote Alarm Manager will respond, if appropri-
ate, depending on how the interface is configured.

Note
You can also accept a message using the same method as above
after clicking an Active Action in the Active Actions page.

The message icon will change according to whether the message

was categorised as accept, busy or refuse, as will the message
status.
Acknowledging an alarm
To acknowledge an alarm:

1 In the Active alarms page, click the appropriate alarm to dis-

play the Alarm details page, then click Acknowledge.

Schneider Electric, Sep 2011 55 (80)

6 Message Management Operating Manual

A corresponding acknowledgement will be available for display

in the console:

56 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

Ending the web interface session

End the web interface session as follows:
1 Click End Session.

6.3.7 Replying via the WAP Interface

The Remote Alarm Manager WAP interface allows you to view, at a
WAP enabled mobile phone, browser, a subset of the data that you
would normally be able to view if you were at the Remote Alarm Man-
ager Console.
You will have to log in to the interface using the same user ID and
password you would use to access the Remote Alarm Manager Con-
sole.
Using the WAP interface, you can also reply to messages that you
have received via another interface, but cannot reply via the same
interface, e.g. a printer or fax machine.
The WAP mobile interface contains an interactive list, as shown:

You can select any of these options (and options in subsequent

screens) using the Up/Down and Enter buttons on your WAP mobile.

Note
The layout and method of selection of the options in the WAP
interface may vary from the examples shown depending on the
type of mobile phone you are using.

Schneider Electric, Sep 2011 57 (80)

6 Message Management Operating Manual

The available options are described as follows:

• Your msg - displays all messages for the current recipient.
From this screen you can select and display a message and
Accept if required. In addition, the message symbol will display
the status of the message (accepted).
• Alarms - this is the list of current alarms in the Remote Alarm
Manager. If you select an individual alarm, its details will be
displayed and you can acknowledge it here, which will cause a
corresponding acknowledgement in the console.
• Messages - this is the list of messages for the all recipients.
• Interfaces - the list of current interfaces and whether they are
functional.
• On duty - a list of recipients on duty, shown by alarm action
and by recipient.
• Log out- enables you to terminate the current WAP session.
Starting the WAP interface
Start the web interface as follows:
1 Open your web browser and enter the address of the PC where
the Remote Alarm Manager is running.
2 Enter your Remote Alarm Manager User ID and Password.

Note
You can use two methods of addressing this PC:
• Use the IP address, in the format:
http://12.157.73.26:782/
• Use the PC name, in the format:
http://wsukb0qs41j:782/. You can find the computer name in
the System section of the Control Panel.
For further details of PC addressing for the WAP interface,
refer to the Remote Alarm Manager Engineering Manual.

58 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

Accepting a message
To accept a message:
1 Select and display the message from the Your msg list:

The message will contain a full list of parameters as shown.

Note
For further details of the formatting of WAP messages, refer to the
Remote Alarm Manager Engineering Manual.

2 Using the method available in your particular mobile, select

either Accept, relating to the message you have received:

The message will then disappear from the screen and the Remote
Alarm Manager will respond, if appropriate, depending on how
the interface is configured.

Schneider Electric, Sep 2011 59 (80)

6 Message Management Operating Manual

Acknowledging an alarm
To acknowledge an alarm:

1 Select and display the alarm within the Alarms list:

2 Using the method available in your particular WAP mobile,

select Acknowledge, relating to the alarm you have received:

The alarm will now show who acknowledged the alarm and the
time of acknowledgement.

60 (80) Schneider Electric, Sep 2011

Operating Manual 6 Message Management

A corresponding acknowledgement will be available for display

in the console:

Ending the WAP interface session

End the WAP interface session as follows:
1 Navigate to the first screen after log on and select Log out.

Schneider Electric, Sep 2011 61 (80)

6 Message Management Operating Manual

62 (80) Schneider Electric, Sep 2011

 ADMINISTERING
7 User and Recipient Management
Operating Manual 7 User and Recipient Management

7 User and Recipient

Management
User and Recipient Management involves managing the details of per-
sonnel who use the Remote Alarm Manager Console and recipients to
whom messages will be sent; also the management of duty rosters for
recipients, so that the Remote Alarm Manager sends messages to on-
duty personnel only.
It is assumed that an interface and recipients have previously been set
up by an engineer, and that duty rosters have been set up for the mes-
sage recipients.

7.1 Starting the Console

Start and log on to the Remote Alarm Manager Console as described
in Chapter 3, “Starting the Console”.

7.2 User Management

Use the Users configuration option to reconfigure the user ID, pass-
word and privileges for each person who uses the Console, and for
each person who is to be a recipient and receive alarm messages from
the Remote Alarm Manager. Also to add and delete users.

Schneider Electric, Sep 2011 65 (80)

7 User and Recipient Management Operating Manual

7.2.1 Modifying User Details

To modify the details of an existing user:
1 Double-click the name of the user.
2 Modify as required any of the pages in the User Configuration
Wizard:

The pages are described as follows:

Name page – Contains the real name of the user. This is used to
identify the user in duty rosters and in message recipient config-
uration.
Password page - Contains the user ID and password that the user
must use to log in to the Remote Alarm Manager.
User type page - This page is used to select whether or not the
user is associated with another (main) system.
Main system(s) page - this page is only visible if you chose to
associate the user with a main system on the User type page. It
allows you to select user association with MicroNet View,
66 (80) Schneider Electric, Sep 2011
Operating Manual 7 User and Recipient Management

BAS2800+, third party (XML) systems and Windows, depend-

ing on the available source:
a MicroNet View - Associating the user with MicroNet
View has two benefits. It enables:
• Automatic logon to the Remote Alarm Manager Console.
If the user currently logged on to MicroNet Win-
dowViewer is also an associated user within the Remote
Alarm Manager, the Console Login screen is bypassed.
• Alarms acknowledged in the Remote Alarm Manager
Active Alarms to be automatically acknowledged in
MicroNet View.

Note
If you switch on user access control in the MicroNet View inter-
face, make sure you also switch it on in the MicroNet View Project
Manager, otherwise full access will be given to the Remote Alarm
Manager, without the need to log on.

b BAS2800+ - Associating the user with BAS2800+ enables

automatic logon to the Remote Alarm Manager Console.
If the user currently logged on to BAS2800+ is also an
associated user within the Remote Alarm Manager, the
Console Login screen is bypassed.
c Third Party (XML) Systems - Associating the user with
the third party (XML) system enables automatic logon to
the Remote Alarm Manager Console. If the user currently
logged on to the third party (XML) system is also an asso-
ciated user within the Remote Alarm Manager, the Con-
sole Login screen is bypassed.
d Windows - Association with Windows allows automatic
logon to the Remote Alarm Manager Console. If the user
currently logged on to Microsoft Windows is also an asso-
ciated user within the Remote Alarm Manager, the Con-
sole Login screen is bypassed.

Schneider Electric, Sep 2011 67 (80)

7 User and Recipient Management Operating Manual

Note
The association with Windows option is displayed only if a Win-
dows Logon interface has been set up.

General notes about user association

The first-created user (fixed as Administrator) cannot be associ-
ated with a main system.
If you use user association with a particular main system, make
sure you do so for all users. If you do not, any Remote Alarm Man-
ager users who are not associated will not be able to acknowledge
alarms in the Remote Alarm Manager.

Association page - Select a main system and enter the main sys-
tem login name of the user. Repeat for other main systems as
required.
Access page - Used to set the user’s privileges when using the
Remote Alarm Manager. Slide the controls up/down to choose
the required privileges. The on-screen text, which changes as
you slide the controls, explains the currently-selected privileges.
You cannot change the local access privileges for the first-cre-
ated user (fixed as Administrator).

Tip
You can select pages in any order by clicking the name of the page
in the left hand side of the User Configuration Wizard. When a
page is selected, an arrow will appear next to the page name. In the
example shown above, the Access page has been selected.

7.2.2 Adding a New User

To add a new user:
1 Double-click Add new user...

68 (80) Schneider Electric, Sep 2011

Operating Manual 7 User and Recipient Management

2 Complete each of the pages in turn, following the prompts. For

descriptions of the pages, refer to the previous instructions for
modifying a user’s details.
3 After you have created a new user, you will be prompted to cre-
ate a recipient for that user, as follows:

4 If you wish to create a new recipient, select Yes, then refer to

Section 7.3, “Recipient Management”.

7.2.3 Deleting a User

To delete a user:
1 Right-click the name of the user you wish to delete.
2 Select Delete.

Note
When attempting to delete a user, a Deletion Blocked message
may be displayed (see below). This will inform you that the user
cannot be removed for the reasons given. You may have to delete
or revise other configuration components first (e.g. Recipients,
Alarm Actions).

Schneider Electric, Sep 2011 69 (80)

7 User and Recipient Management Operating Manual

7.3 Recipient Management

Use the Recipient configuration option to reconfigure the name of a
person who will receive alarm messages, and the interface used to
contact that person. A recipient can be used in alarm actions to route
alarm messages to a specific person. You can also add and delete
recipients.

You can set up several recipients that relate to the same person. This
enables the same person to be reached by different methods (e.g.
mobile phone or fax).

7.3.1 Modifying Recipient Details

To modify the details of a recipient:
1 Double-click the name of the recipient.

70 (80) Schneider Electric, Sep 2011

Operating Manual 7 User and Recipient Management

2 Modify as required any of the pages in the Recipient and

Device Configuration Wizard:

The pages are described as follows:

User page – Contains the Remote Alarm Manager user who is to
be the recipient.
Interface page – The interface used to contact the recipient.
Settings page – Contains the required information for the inter-
face selected (e.g. for the GSM Modem interface, the phone
number of the recipient).
Message type page – Contains the information to include in any
messages sent to the recipient (can be overridden in alarm
actions; page 39).
Verbose messages include Long Text (when configured in
Sigma).
Confirmation page – This page is displayed only for certain
interfaces, such as the GSM Modem interface. The page enables

Schneider Electric, Sep 2011 71 (80)

7 User and Recipient Management Operating Manual

you to configure the Remote Alarm Manager to send confirma-

tion messages to the recipient whenever the recipient replies to a
alarm message or sends a command.
Test type page – Used to determine whether or not a test mes-
sage is sent to the recipient.
Test settings page – This page is displayed only if you have cho-
sen to send a test message in the Test type page. You can use the
page to carry out the test.

7.3.2 Adding a New Recipient

To add a new recipient:
1 Double-click Add new recipient...
2 Complete each of the pages in turn, following the prompts. For
descriptions of the pages, refer to the previous instructions for
modifying a recipient’s details.

7.3.3 Deleting a Recipient

To delete a recipient:
1 Right-click the name of the recipient you wish to delete.
2 Select Delete.

Note
When attempting to delete a recipient, a Deletion Blocked mes-
sage may be displayed (see below). This will inform you that the
recipient cannot be removed for the reasons given. You may have
to delete or revise other configuration components first (e.g. Alarm
Actions).

72 (80) Schneider Electric, Sep 2011

Operating Manual 7 User and Recipient Management

7.4 Duty Roster Management

A duty roster defines the periods within a week that a set of recipients
and/or devices are "on duty". That is, the periods within a week that
they are expected to receive alarm messages.
If a simple Normal hours/Out-of-hours arrangement is being used, a
single Duty Roster should be used with individual recipients assigned
appropriately to the two periods. If however shifts are used, separate
Duty Rosters are required to cover the whole of the week.
Duty arrangements can rotate on a weekly basis.

7.4.1 Modifying a Duty Roster

To modify a duty roster:
1 Double-click the name of a Duty Roster.

Schneider Electric, Sep 2011 73 (80)

7 User and Recipient Management Operating Manual

2 Modify as required any of the pages in the Duty Roster Wiz-

ard:

The pages are described as follows:

Name page – Contains the duty roster name.
Period page – Contains the dates the duty roster should become
active and inactive. The duty roster will not operate after the
inactive date. If you choose Never, the duty roster will never
become inactive.
Recipients page – Contains the recipients and/or devices who
are on duty in the Green period of the duty roster.
Alternate page – Contains the recipients and/or devices who are
on duty in the White period of the duty roster.
Type page – This page is visible only if more than one recipient
is specified in either the Green or White period. It contains two
options:

74 (80) Schneider Electric, Sep 2011

Operating Manual 7 User and Recipient Management

• All recipients assigned the Green (or White) period are

simultaneously on duty, every week.
• Each recipient assigned the Green (or White) period is
independently on duty, for one week at a time. For exam-
ple, if two recipients are assigned the Green period, they
are each alternately on duty during the Green period only
for one week per fortnight.
Schedule page – A graphical display of the periods within each
week that the recipients and/or devices are on duty. You can use
the mouse to modify these periods using ‘click-and-drag’.
Exceptions page – Specifies the dates and time periods of
exceptions to duty periods for that roster only. You can:
• Change a particular date to use a schedule based on
another weekday.
• Specify a start and end times, between which the roster is
excepted from duty (i.e. a number of hours up to 24
hours).
Duty roster example
The following page extracts from a Duty Roster Wizard show a Duty
Roster where one person is on duty in normal hours (the White period,
08:30 to 17:30) and two people are on duty out-of-hours (the Green
period, 17:30 to 08:30).
• Both Robert Avery and George White are selected to be on duty
in the Green period (selections/deselections are made using the
right and left arrows):

Schneider Electric, Sep 2011 75 (80)

7 User and Recipient Management Operating Manual

• William Moss is selected to be on duty in the White period:

• The Type page (which is only shown when there is more than
one recipient in the Green or White period) shows that the two
recipients in the Green period are selected to be on duty inde-
pendently for one week at a time.

• The Schedule page (next) confirms that Robert Avery and

George White are on duty during the Green period (in this case,
out-of-hours) and William Moss is on duty during the White
period (in this case, in normal hours).

76 (80) Schneider Electric, Sep 2011

Operating Manual 7 User and Recipient Management

• Note, however, that the Schedule page does not show that Rob-
ert Avery and George White are on duty on alternate weeks as
set up in the Type page.

7.4.2 Adding a Duty Roster

To add a duty roster:
1 Double-click Add new duty roster....
2 Complete each of the pages in turn, following the prompts. For
descriptions of the pages, refer to the previous instructions for
modifying a duty roster.

7.4.3 Deleting a Duty Roster

To delete a duty roster:
1 Right-click the name of the duty roster you wish to delete.
2 Select Delete.

Schneider Electric, Sep 2011 77 (80)

7 User and Recipient Management Operating Manual

Note
When attempting to delete a duty roster, a Deletion Blocked mes-
sage may be displayed (see below). This will inform you that the
duty roster cannot be removed for the reasons given. You may
have to delete or revise other configuration components first (e.g.
Alarm Actions).

78 (80) Schneider Electric, Sep 2011

Copyright © 2011 Schneider Electric Schneider Electric
All brand names, trademarks and registered trademarks Malmö, Sweden
are the property of their respective owners. Information +46 40 38 68 50
contained within this document is subject to change
without notice. All rights reserved.
Product Support Services
+44 (0) 1628 741147
S3533878002 product.support@schneider-electric.com

www.schneider-electric.com/buildings