I n t e g r a t e d C o n t r o l S o l u t i o n s & E n e r g y S a v i n g s

remote supervision solutions

User manual
3
ENG
+0400022EN - rel. 1.1 - 18.11.2010
i
n
s
t
a
l
l
e
r
Content
1. SYSTEM REQUIREMENTS 5
1.1 Minimum hardware requirements (recommended) .....5
1.2 Software requirements ..................................................5
1.3 Languages .........................................................................5
2. GENERAL SCREENS 6
2.1 Login ..................................................................................6
2.2 Desktop .............................................................................6
2.3 Lists ....................................................................................7
2.4 Details ................................................................................8
2.5 Favourites .........................................................................9
3. START-UP 10
3.1 Install the software ..........................................................10
3.2 Activate thwe software license .....................................12
4. CONFIGURATION 13
4.1 Congure the supervisor network ...............................13
4.2 Congure the modem connection .............................15
4.3 Manage the address book ............................................15
4.4 Create new user .............................................................16
5. LIFE TEST MANAGEMENT 18
5.1 Congure the life test .....................................................18
6. ALARM AND EVENT MANAGEMENT 19
6.1 Congure the email ........................................................19
6.2 Congure the rule engine .............................................19
6.3 Congure the notication groups ...............................20
6.4 Congure the time bands .............................................21
7. DATA MANAGEMENT 22
7.1 Congure data alignment ..............................................22
8. KPI REPORTS 23
8.1 Congure the variables analysed on the KPI reports .....23
8.2 Congure data presentation on the KPI reports .....24
9. REMOTE MANAGEMENT OF LOCAL USERS 25
9.1 Display local users ..........................................................25
9.2 Create and edit local users ...........................................25
4
ENG
+0400022EN - rel. 1.1 - 18.11.2010
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
10. ACCESSING THE LOCAL SUPERVISORS 28
10.1 Display local supervisors .............................................28
11. SUPERVISOR LIFE TEST 30
11.1 Display life test status ...................................................30
12. DISPLAYING ALARMS AND EVENTS 31
12.1 Display alarms................................................................31
12.2 Display alarms and events in supervisor detail .....32
12.3 Display alarm report ....................................................33
13. DISPLAYING DATA 34
13.1 Display graphs ...............................................................34
13.2 Send reports by email .................................................36
14. DISPLAYING KPI REPORTS 37
14.1 KPI temperature report ................................................37
14.2 Display KPI daily temperature reports .....................38
14.3 Display KPI performance reports ..............................38
14.4 Display KPI energy reports .........................................39
15. ALARM SYNCHRONISATION 40
15.1 Synchronise local and remote supervisor ...............40
15.2 Manage remote alarms ...............................................41
15.3 Inhibit alarms .................................................................43
5
ENG
+0400022EN - rel. 1.1 - 18.11.2010
1. SYSTEM REQUIREMENTS
1.1 Minimum hardware requirements (recommended)
Processor: Intel Core 2 2.66 GHz (or equivalent);
RAM: 2GB (4GB recommended);
Hard Disk: 500GB;
Screen resolution: 1024 x 768;
CD-Rom.
1.2 Software requirements
Operating systems supported:
Windows XP Professional SP3,
Windows Server 2003,
Windows Server 2008,
Windows Vista Business Edition,
Windows 7 Professional
Browsers supported:
Internet Explorer 7,
Internet Explorer 8,
Mozilla Firefox,
Google Chrome.
Note: if the software is used to connect to local supervisors (PlantVisorPRO, pCOWeb, PlantWatchPRO,
PlantVisor Enhanced), see the related manual to check browser compatibility.
1.3 Languages
Italian
English
German
French
Chinese
Spanish
Turkish
Note: the list of languages is only indicative. Contact Carel reference personnel for the updated list.
6
ENG
+0400022EN - rel. 1.1 - 18.11.2010
2. GENERAL SCREENS
2.1 Login
To access the system, enter the user name and
password and select login.
2.2 Desktop
When accessing RemotePRO, the starting page is displayed. This provides access to all the pages of the
program. The layout of each page is described in the fgure below, which represents the desktop area:
The desktop includes:
1. A bar at the top showing information relating to the user (description, language used). Select a fag
from the pop-up menu to change the language used to display the information. On the right is a series
of buttons (favourites) that can be modifed by the user and that allow quick access to the functions
provided by the system. The frst button is always featured and is used to logout.
2. The menu bar, set out in several levels, providing access to the program functions.
3. The browsing path that traces the pages accessed in the application. This helps return to the previous
maps at any time (e.g. once having opened the detail of a map, the user can return to the originating list).
4. A series of tabs that vary depending on the context.
5. An area with the function buttons.
6. The body of the currently displayed map.
7
ENG
+0400022EN - rel. 1.1 - 18.11.2010
To simplify the experience for the user, almost all the pages have been divided into two categories:
1. Lists: the records are grouped in a table that includes the fltering, sorting and page layout functions.
2. Details: by double clicking a row in the table, complete information on the record in question can be
displayed, and several essential functions performed (create, edit, display, delete).
2.3 Lists
The main sections on each list page can be easily identifed:
1. The parameters that can be set to flter the data in the list. Once the data has been entered, select to
flter the information. resets the fltering felds, displaying all the data.
2. Some pages feature the automatic refresh option. In this case a countdown will be displayed to highlight
the time remaining until the next refresh. The check box to its side is used to temporarily disable the
function.
3. The and buttons are used to add and remove data to/from the list.
4. The rows feld is used to modify the number of rows displayed on each page (default 15).
Note: access system -> confguration-> global to modify the default value.
5. If there is more than one page, buttons are displayed to access a specifc page or move to the next,
previous, frst or last page (using the arrows).
6. The columns with the icon are used to sort the data in the table (by selecting the column header row)
in increasing or decreasing order.
7. At the foot of the page are buttons used to export the data in the list (all the data that satisfy the flters set)
in diferent formats (csv, xls, xml, pdf ).
8
ENG
+0400022EN - rel. 1.1 - 18.11.2010
2.4 Details
For all complex entities, the list pages can only display a limited amount of information. In these cases, double
click the row to zoom in and display the details of the selected record.
1. Each page includes the basic functions (create, edit, display, delete) and/or the specifc functions for the
page;
2. The required felds (for example, to create a new record) are highlighted in purple;
3. At the bottom of the page are details on the user and the date the record was created, as well as the date
the record was last updated and the user;
4. The search buttons open popup boxes to help complete the felds.
1
2
3
4
9
ENG
+0400022EN - rel. 1.1 - 18.11.2010
2.5 Favourites
The Administration -> Favourites menu is used to access the map of favourites, listing the transactions that
the user expects to access more frequently.
The order feld indicates the position of the quick access buttons on the top bar.

Clicking or selecting an existing record accesses the detail map used to create or edit the favourites:

10
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
3. START-UP
O
Insert the CD in the CD drive.
The installation procedure starts automatically; if it
doesnt, access the CD drive and run start.bat, then
follow the instructions on the screen.
O
Read and accept the license terms, then click
next .
O
Click install to start installing the software.
O
Wait until all the components of the software
have been installed.
O
When installation is completed, the system
needs to be rebooted, click yes.
Before starting the installation procedure, make sure the features of the PC where the software will be installed
are equal to or higher than the minimum system requirements. For correct installation of the software, the
system needs to be accessed using an account with administrator rights.
3.1 Install the software
11
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
O
Select fnish and wait for the PC to restart

O
When the PC restarts, the screen on the right
is displayed automatically (Splash Screen); this
indicates initialisation of the application.
Note: in some operating systems display of
this screenshot is not supported. This does not
afect system operation.
O
Wait for the Splash Screen to close and double
click the RemotePro icon to start the program.
O
If a security warning is displayed when accessing
the program, click on Continue to this website
(not recommended) or on the equivalent
message, according to the browser being used.

12
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
3.2 Activate thwe software license
Use of the software requires registration of the license using an activation code; this code is provided to the
user after registration on the Carel website (www.carel.com).
To register the software, the user needs to provide:
the Mac Address (unique identifer of the unit network card) that is shown on the license registration page;
the Serial Number shown on the label applied to the installation CD packaging.
O
Access: administration -> modules
Note: the icons on the page indicate:
software activated
software not activated
The trial column indicates the possibility
to use a module for a limited period of
time without activation:
the software can be used until the trial
period expires.
Important: The Mac Address feld shows the
codes of all the network cards available on
the unit (for example Ethernet board and/
or wireless board), separated by ;. When
registering on the Carel webste, provide just
one of the codes.
O
Enter the serial number containing the
information relating to the software being
activated
O
Enter the activation code provided when
registering
O
Click .
Note: all software that can be registered is
distributed with the corresponding Serial
Number.
13
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
4. CONFIGURATION
4.1 Confgure the supervisor network
Each local supervisor must be confgured in the system.
O
For each supervisor to be confgured, access:
census -> installation -> supervisors
This page lists the supervisors that are currently
confgured, showing:
The unique identifer of the supervisor.
The description.
An icon that represents the type of
supervisor (PlantVisorPRO, PlantWatchPRO,
pCOWeb or PlantVisor Enhanced).
An icon that represents the supervisor
connection mode (modem or LAN).
The supervisor IP address or phone number
(depending on the connection mode).
An icon that indicates whether or not access
via internet (from outside the LAN) is enabled.
In the Remote Service and Data Central
Management version, the functions activated:
synchronisation (C = confguration,
A = alarms, E = events, N = notes)
data alignment (D)
outgoing life test (T)
incoming life test (L)
OSelecting the button opens the details page
for confguring a new supervisor.
O
Enter the data required to confgure the local
supervisor.
The identifer and the password must be the
same as set on the local supervisor, otherwise
synchronisation will not be possible. These
data are required for the functions included in
the Remote Service version.
The identifer feld must be unique, therefore
the local supervisors also need to be
confgured correctly (see the related manuals).
The Mac Address feld (unique identifer
of the network card) is only needed for the
pCOWeb.
14
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
If the supervisor is connected via LAN, in the
IP address enter the number that uniquely
identifes the device connected to the network
or the DNS name.
If the supervisor is connected via modem, in the
Phone feld enter the phone number to dial.
Important: the modem connection is a slow
data transmission channel. When confguring a
supervisor that uses this channel, the data to be
transferred between the local and remote
supervisors need to be selected carefully, to limit
traf c on the channel and reduce communication
times.
To ensure correct operation of the system, the
number of supervisors that can be connected
via modem is limited to 20.
Important: in the type feld, choose the
model carefully (PlantVisorPRO, PlantVisor
Enhanced, PlantWatchPRO or pCOWeb), as after
having created the supervisor, this value can no
longer be edited.
Enable or disable the possibility to access
the supervisor via internet. This option
makes supervisors that would otherwise be
unreachable accessible from outside of the LAN.
Select the information to be downloaded from
the local supervisor during synchronisation
(e.g. alarms, events, notes). This function is
included in the Remote Service version.
Indicate whether to enable the life test
function. This function is included in the
Remote Service version.
there are two functions: "incoming" and
"outgoing" life test.
Indicate whether to enable the option for
aligning the data from the local supervisor.
This function is included in the Data Central
Management version.
O
Click .
Important: The pCOWeb credentials section is
required if the supervisor is a pCOWeb. For the
data to be entered in this section, see the user
manual for this device.
15
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
4.2 Confgure the modem connection
This page is used to confgure the modem for connecting to the local supervisors.
The modems connected are automatically detected when starting the application, and are visible in the
modem drop-down list from: system -> channel -> RAS confguration
O
To confgure new modem access: system ->
channel -> RAS confguration
O
Enter all the data required to confgure the
modem.
O
Click .
Important: after having confgured a new
modem, the PC needs to be rebooted so it can
be recognised by the system.
Note: the frst button can be used to
close a modem and make it available again
if communication faults occur (for example,
if a user does not correctly close the modem
connection to a local supervisor).
Note: the second button can be used to
display the log fle that keeps track of the trend
in modem connections and any errors.
4.3 Manage the address book
The address book saves all the contacts for the various supervisors. The contacts are used by the rules engine
to send notifcations in the event of alarms.
O
Access to: census -> address book
O
Click .
O
Enter a unique code and a description.
O
Enter the various details for the contact.
O
Click .
16
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
4.4 Create new user
O
To create a new user, access administration ->
access -> users
O
Click .
O
Complete all the felds required to confgure the
new user and click .
The "status" feld indicates whether or not the
application can be accessed; this allows users to be
temporarily disabled.
Important: the status feld must be enabled
to allow the user to login.
The correct profile must be selected, as each profile
allows access to different functions.

Three types of profiles are available:
- Installer
- User
- Maintainer
Installer users can access all the functions available
in the application (both system confguration and
operation).
The User profle ofers read-only access to the main
transactions.
Maintainance users have extended access that
allows complete management of the alarms.
17
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
The following table shows which functions are enabled for the diferent types of profle:
Installer User Maintenance
SUPERVISION
Supervisor status Read/write Read-only Read/write for synchronisation
Alarms Read/write Read-only Read/write
CENSUS
Supervisor installation Read/write Read-only Read-only
Model installation Read/write Read-only Read-only
Address book Read/write Read-only Read-only
REPORTS
Log report Read/write Read/write Read/write
Export data log Read/write Read/write Read/write
Alarm report Read/write Read/write Read/write
Confguration Read/write Read-only
KPI temperature Read-only Read-only Read-only
KPI energy Read-only Read-only Read-only
SYSTEM
System register Read/write Read/write Read/write
Rules engine Read/write Read-only Read-only
Channel Read/write
Log Read/write
Global Read/write
Life test Read/write
Data alignment Read/write
ADMINISTRATION
User access Read/write
Access /edit user Read/write Read/write Read/write
Favourites Read/write Read/write Read/write
System page Read/write Read/write Read/write
Modules Read/write
Export log fle Read/write
18
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
5. LIFE TEST MANAGEMENT
It is important to know whether the local supervisors are communicating correctly with the remote supervisor,
or whether there are problems that prevent communication. The status of each supervisor can be checked
using the life test that is performed periodically by the remote supervisor for each local supervisor confgured.
5.1 Confgure the life test
Important: the life test is only performed for the supervisors that have selected at least one of the items,
either "incoming life test" or "outgoing life test" on the supervisor details page. Otherwise the life test
will not be performed for that supervisor and its status will not be known.
Note: Check under census -> installation -> supervisors in columns "T" and "L" respectively which
supervisors are enabled for the "outgoing life test" and/or the "incoming life test" ( ).
The number of times the life test must be performed every day can be set.
If, for example, a frequency of 4 incoming life tests is set per day, the tests will be performed at 00:00, 06:00,
12:00 and 18:00. The test at 06:00 checks if there has been at least one call from the local supervisor between
00:00 and 05:59, and so on.
O
Access:
system -> confguration -> life test.
O
Select how many times the life test should be
performed every day using the corresponding felds.
"outgoing": to periodically send a request to each
supervisor enabled. The remote supervisor calls
the local supervisor (i.e.: the remote makes the call
via modem);
"incoming": to check whether at least one request
has been received from the local supervisors
enabled over the recent period: the local
supervisors must actively contact the remote
(i.e.: the local makes the call via modem). See
the corresponding manual to confgure the local
supervisors for contacting the remote.
OClick .
Note: Diferent intervals can be defned for
life test via LAN (maximum 24 times a day,
that is, once an hour) and life test via modem
(maximum 6 times a day, that is, once every 4
hours).
19
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
6. ALARM AND EVENT MANAGEMENT
6.1 Confgure the email
The I/O peripherals must be confgured in order to send notifcations via email when alarms occur.
O
Access:
system -> channel -> email confguration.
O
Enter all the data required for Email confguration.
OClick .
6.2 Confgure the rule engine
Synchronised alarms can be managed by the rules engine and notifed via email to relevant personnel who need
to respond. Notifcation groups can be defned to group diferent contacts together.
Whenever an alarm is signalled on the remote supervisor, a special procedure checks whether there are alarm
notifcation rules in the time band. If there are, the specifc alarm is checked to see whether there are specifc rules
(for example, based on alarm priority). If there is at least one specifc rule, all the groups of contacts associated
with the alarm will be notifed.
O
Access:
system -> rules engine -> rules.
O
Click .
O
Enter all the data needed for correct alarm
management. Each alarm can be managed
by the rules engine based on certain features
set by the user, such as its priority, the type of
supervisor, alarm status.

O
Click .
20
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
6.3 Confgure the notifcation groups
O
Access:
system -> rules engine -> notifcation groups
O
Click .
O
Enter a description for the group.
O
Click .
O
Go to the contacts tab and from the drop-down
menu select the required contacts.
O
Click .
Important: The drop-down menu displays all
the email contacts confgured in the address
book.
O
Repeat steps 5 and 6 to associate other contacts
with the notifcation group.
21
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
6.4 Confgure the time bands
O
Access:
system -> rules engine -> time band.

O
Click .
O
Select the day of the week or "every day".
O
Select the rule to be applied.
O
Select the time interval for the rule.
O
Click .
Important: if the "enabled" check box is not
selected the time band is ignored.
O
Select the Notifcation groups tab.
O
From the drop-down menu select the group in
question and click the button.
O
Repeat steps 7 and 8 to associate other
notifcation groups to the rule.

22
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
7. DATA MANAGEMENT
The data alignment function downloads to the remote supervisor the data related to the variables logged by
the instruments connected to the local supervisors.
This function centralises the various types of information acquired from the feld in just one location, allowing
comparative analysis to be performed.
7.1 Confgure data alignment
The data alignment function is a scheduled operation that is run automatically by the system once a day. The
user can set the time when the function starts as desired.
Important: data alignment is only performed for supervisors that have been suitably confgured. To
enable the function, select the data check box on the supervisor detail page.
Note: in census -> installation -> supervisors column D shows which supervisors are enabled for data
alignment ( ).
O
To confgure data alignment access:
system -> confguration -> data alignment
O
Set the data alignment start time in the data
alignment start time feld.
Note: data alignment should be started in
the night-time band, as the quantity of data
processed may lead to a decline in system
performance.
O
In the FTP server feld enter the IP address of
the PC where the application is installed. The
localhost alias is not allowed for this feld.
Note: this information is only used for
communication with PCOWeb supervisors.
Important: if the network of supervisors
extends outside a LAN (access via Internet), the
public IP of the server needs to be specifed for
correct interaction with pCOWeb supervisors.
O
Click .
23
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
8. KPI REPORTS
The KPI report ofers the user a rapid overview of the performance of each supervisor.
The data used for analysis are retrieved from the local supervisor; data alignment confguration is therefore required
to use this function
8.1 Confgure the variables analysed on the KPI reports
Following the frst synchronisation with a supervisor, to
confgure the variables analysed proceed as follows:
O
For each supervisor to be confgured access:
database -> installation -> supervisors
O
Double click the supervisor in question to open
the details page.
O
Click the devices tab.
O
In the device model column set the correct
model for the controllers being confgured.
OClick .
Note: the same model can be associated with more
than one device, selecting them and using the global
models list.
To exclude a controller from the report, disable it by
setting NO for the value in the KPI column.
Important: only devices with an associated model
will be considered for the KPI reports.
Important: data alignment on the local supervisors
must be correctly confgured for all the variables
required to process the KPI reports (see the
corresponding manual).
For the KPI energy report only the variable indicating
total consumption (kWh) is required.
For the KPI temperature report, the following variables
are required:
Temperature value;
Set point;
Diferential;
Compressor status;
Defrost status;
High temp. alarm (optional);
Low temp. alarm (optional).
24
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
8.2 Confgure data presentation on the KPI reports
To customise the colours on the KPI reports, proceed as
follows:
O
Access:
report -> KPI -> confguration KPI
O
Select the various colours (background and font)
OClick .
Note: use the button to restore the original
confguration
To normalise energy consumption values, considering
that sites may difer enormously in aspects such as size,
opening times, number of controllers:
O
Access:
report -> KPI -> KPI energy -> supervisor weight
O
For each supervisor, set a normalisation value (other
than 0)
OClick .
O
if necessary, customise the description of the
normalisation quotient under report -> KPI -> KPI
confguration
OClick .
The normalisation value set will be used as the quotient
for the absolute consumption value.
25
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
9. REMOTE MANAGEMENT OF LOCAL USERS
Local User management allows RemotePRO to set a list of users for accessing the local supervisors (for simplicity
these will be called local users) and then automatically confgure the supervisors accordingly, without having
to repeat the confguration for each individual user on each supervisor.
9.1 Display local users
Note: This list is considered an addition to the list of users already available on the supervisors, as pre-existing
users will not be deleted or overwritten, unless Local User management is used to create/edit/delete users with the
same username as users already listed on the supervisor.
O
Access:
administration -> access -> local users
This page lists the local users currently
confgured, displaying:
username;
two numbers that represent the number
of supervisors confgured (the frst number
indicates those that the user can access, the
second indicates the supervisors yet to be
synchronised);
Note: moving over each number with the
mouse cursor displays the list of corresponding
supervisors confgured.
an icon indicating any supervisors connected
via modem;
user profle.

9.2 Create and edit local users
Note: supervisors that support remote management of Local Users must be enabled to accept this
function. To enable the function see the specifc manual for the supervisor used.
Important: remote management of Local Users is currently only supported by PlantVisorPRO version 2.0
and higher.
O
Access:
administration -> access -> local users
O
Select the button to access the screen for
creating/editing a user
O
Specify the username for the user being created.
26
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
O
Set the password
Note: The password must be at least eight
characters, and must contain at least one number,
one letter (upper or lower case) and one of the
following special characters: . , _ ! ? $ % &
O
Select the profle
Note: The four standard PlantVisorPRO 2.0
profles can be selected (System Administrator,
Installer, Service, End User), The operations
available on the supervisor when the user has
been created will vary depending on which
functions are enabled in the profle used on the
specifc supervisor.
O
Select the button.
O
At the bottom of the page, indicate the list of
supervisors that the newly-created user can
access, using:
the button to add all the supervisors listed
in the system in just one click
the help window and the button to only
add the supervisor selected in the list.
The status column represents the operation
to be executed on the local supervisor; in
particular, the yellow background highlights the
operations yet to be performed, and the various
icons indicate that the user:
must be added to those on the local
supervisor;
has already been added to those on the
supervisor, but needs to be updated (for
example, the password has been changed);
must be removed.
To remove one or more supervisors from the list,
simply select them using the special checkbox
and select the button.
Note: if a supervisor is cancelled from the list
of the supervisors available for the user, it will be
marked by the icon only if the user has
previously been created. If the user has never
been created on the supervisor with Local User
management, the item will be removed directly
from the list, without applying any changes to
the supervisor.
27
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
O
Access: administration -> access -> local users
O
Select the button to transfer the changes
made so far to the confguration of supervisor
local users
Important: All changes made to the users
and the list of supervisors will not be applied
until the button is selected on the page with
the list of Local Users
Note: Synchronisation is performed in real
time only with the supervisors connected to
RemotePRO via LAN. To optimise usage of the
analogue line, supervisors connected via
modem will be updated during the frst alarm
synchronisation (performed manually by a user
on RemotePRO or based on a rule to
communicate with the remote system set on the
local supervisor).
28
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
10. ACCESSING THE LOCAL SUPERVISORS
10.1 Display local supervisors
RemotePRO allows quick connection to all local supervisors confgured in the system:
O
Access: supervision -> supervisor status
This page lists the supervisors that are currently
confgured, showing:
Status of the last life test (Remote Service
version only).
The alarms active on the supervisor (Remote
Maintainer version only).
The description of the supervisor.
An icon that represents the type of supervisor
(PlantVisorPRO, PlantWatchPRO, pCOWeb or
PlantVisor Enhanced).
An icon that represents the supervisor
connection mode (modem or LAN).
An icon that indicates whether or not the
supervisor can be accessed via internet.
A button used to connect to the supervisor,
opening a LAN or modem connection.
Date of last life test performed
(Remote Service version only)
date of the last data alignment (only in the
"Data Central Management" version).
Date of last supervisor connection
Note: the last connection date indicates
the most recent activity that opened a
connection to the local supervisor; this may
be browsing by the user, a life test,
synchronisation of alarms/events or data
alignment.
Note:
Connection to a supervisor can only be
established by selecting the green
buttons. For LAN connection, more than one
connection can be opened at the same time.
When opening a modem communication to
a supervisor, next to the green button is
a second red button used to close the
modem connection and that indicates which
supervisor is currently occupying the channel.
All the other supervisors will not be accessible
until the modem has been freed up. This
status is indicated by a yellow icon .
29
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
Important:
the only user that can close communication
via modem is the one currently using the
connection. Any other users connected
to the system will see the modem busy
icon
y
for all supervisors connected via
modem.
It is important to close the open modem
connections using the red button, to
avoid malfunctions.
Note: an authorised user can access the
system -> channel -> RAS confguration and
close the modem connection using the frst
button.
30
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
11. SUPERVISOR LIFE TEST
11.1 Display life test status
O
To display the result of the life test, access:
supervision -> supervisor status.
O
Check the life test column, showing the
outcome of the life test:
led verde: both life tests (or the
one enabled) have been
successful

led rosso: at least one of the two life
tests has failed

led arancione: at least one of the two life
test is enabled, but has not
yet been performed
led grigio: no life test enabled
Important: a negative outcome of the life
test ( ) does not necessarily mean that the
local supervisor is not working correctly: there
may be problems involving the network that
prevent communication between the local
supervisor and remote supervisor.
Accessing to the supervisor details and selecting "life
test events" tab shows the log of the tests performed
for the specifc supervisor
31
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
12. DISPLAYING ALARMS AND EVENTS
The alarms received from the local supervisor can be
displayed by accessing: supervision -> alarms ->
active alarms.
This table shows all the alarms that have not been
acknowledged on the remote, or have not yet ceased
on the local. Therefore these may be alarms that are
still active on the local, that is, only have a start time,
and alarms that have already been reset, that is, those
with an end time.
Note: when an alarm has an end time, or
has been acknowledged on the remote, it is
highlighted in the same colour but darker.
The alarms are highlighted in diferent colours, based
on their priority:
Note: the possibility to display reset alarms
yet to be acknowledged on this page can
be enabled under system > confguration >
synchronisation.

Active
alarm
Reset
alarm
Priority
Technical alarm (e.g. life test)
Highest
High
Medium
Low
12.1 Display alarms
32
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
12.2 Display alarms and events in supervisor detail
Alarms and events can be displayed corresponding to just one supervisor.
O
Access: census -> installation -> supervisors
O
Double click the supervisor in question to open
the details page.
Note: from this page it is possible to access
all the information downloaded during
synchronisation with the local supervisor (e.g.
alarms, life test events, local events, notes.) by
clicking the desired tab.
O
To display the alarms on the supervisor, click the
active alarms tab.
This page only displays the alarms corresponding
to the selected supervisor.
O
To display the local events for the supervisor,
click the Local Events tab.

Note: on the local supervisor, the events are divided into three types:

info: information relating to correct system operation.
warning: signals any confguration problems.
error: signals problems that stop operation of the system.

33
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
12.3 Display alarm report
To display an alarm report, access: report -> alarms
and select the type of report.
Note: diferent types of reports are available
that group the alarms (active and reset) by:
priority (highest, high, medium, low);
description.
O
select the desired period using the calendars
O
click
Note: the reports can be exported (in PDF
format) by clicking .

34
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
13. DISPLAYING DATA
13.1 Display graphs
Once having received data on the server, the user can, for each device, display a graph showing the aligned
variables.
O
To display the graph for a device, access:
census -> installation -> supervisors
O
Double click the supervisor in question to open
the details page
O
Click the controllers tab. The list of all the
instruments connected to the local supervisor
is displayed.

O
Double click the device to display the
corresponding graph.
35
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
O
Click the Log data graphs tab.
Note: the frst time the graph is accessed for
a device, the variables displayed need to be
selected.
O
Select the variables, choose the colour and click
.
O
Select the starting date and the duration of the
period and click .
Note: an area on the graph can be selected
to zoom the data displayed. Selecting the
button returns to the previous zoom level.
36
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
O
To send a report by email access:
report -> log report -> export log data
O
Enter the email address to send the report to
O
Select the type of report (daily, weekly, monthly,
generic), the date, the supervisor and the device.
O
Select the desired variables and click
. The selected variables are moved to the
window on the right.
O
Click to send the report
13.2 Send reports by email
Reports can be generated and sent by email.
37
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
14. DISPLAYING KPI REPORTS
After having confgured the KPI reports and performed at least one data alignment, the reports corresponding
to temperature and energy consumption can be displayed.
14.1 KPI temperature report
There are two diferent temperature reports. The frst performs daily analysis and presents a report of the trend
over 24 hours; the second examines a selected period and presents operation of the devices in percentage
terms. Both reports are based on comparison of temperature against the set point, diferential and a user
parameter called critical variation. The areas that these three parameters identify are defned as follows:
Over critical: temperature's value raised over high critical threshold;

Over range: temperature's value varied between diferential and high critical threshold;

In range: temperature's value varied between set point and diferential threshold;
Under range: temperature's value varied between set point and low critical threshold;
Under critical: temperature's value descended under low critical threshold;
where the high and of low critical thresholds are defned respectively as the diferential + critical variation and
set point - critical variation.
The following graph shows an example of the temperature trend compared against the thresholds, and
describes the areas that these thresholds defne:
As well as the colours of the areas described previously, two other colours are envisaged, which identify:
Defrost defrost relay have been turned on;
Undefned temperature's value have not been stored.
38
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
14.2 Display KPI daily temperature reports
This page lists the devices on the supervisor and displays the 24 hours of the day divided into intervals that
represent the temperature values compared against the thresholds
O
To display the KPI daily temperature reports
access:
report -> KPI -> KPI temperature -> KPI daily
temperature
O
Select the supervisor to analyse
O
Select the analysis date (default today)
O
Set the critical variation (default 2)
O
Select the step for the intervals to divide the
hours into (for example, setting 15 minutes
means 4 intervals each hour)
OClick .
Note: if the temperature deviates to the point of
setting of an alarm, a specifc icon will be displayed at
the time the alarm occurred:
low temperature alarm
high temperature alarm
Note: to access the graph with the trend of
device variables over the selected period, double
click a row.
14.3 Display KPI performance reports
O
To display the KPI performance reports access:
report -> KPI -> KPI temperature -> KPI
temperature
This page lists the supervisor devices and displays:
the percentage of operation in the diferent areas;
the defrost time over the selected period;
the compressor operating time over the
selected period;
the number of low and high temperature alarms
the total number of alarms
O
Select the supervisor to analyse
O
Select the analysis date (default today)
O
Select the period (daily, weekly or monthly)
O
Set the critical variation (default 2)
O
Click .
Note: double clicking a row accesses the graph
showing the trend of device variables over the selected
period.
39
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
14.4 Display KPI energy reports
O
To display the KPI energy reports access:
report -> KPI -> KPI energy -> KPI energy for
supervisor
This page lists the supervisors and displays:
The value of the normalisation quotient;
The number of devices connected to the
supervisor (excluding the energy meter);
Efective energy consumption, either the
sum of consumption from the partial energy
meters or the value of the global energy
meter.
Note: for each model of energy meter
(e.g.: Ducati, Gavazzi) there are two versions
that indicates whether the device should be
considered partial or global
Energy consumption as a percentage;
The normalised value of energy consumption
based on the quotient parameter;
Normalised consumption as a percentage;
The normalised value of the energy
consumption based on the number of
devices.
O
Select the analysis date (default today)
O
Click .
At the foot of the table are the totals of consumption
and the average of efective and normalised
consumption.
Note: the normalised consumption values
provide a most reliable comparison of performance
between supervisors.
Double clicking a row accesses the consumption
details for the selected supervisor:This page lists the
energy meters on the supervisor and displays:
An icon that indicates whether the device is
global;
Efective energy consumption;
For partial meters:
- Energy consumption as a percentage of the sum
of partial values;
- Energy consumption as a percentage of the sum
of global values..
At the foot of the table are the totals of partial
consumption and the average consumption from
partial meters.
Colour Performances
Best
Better than average
Worse than average
Worst
40
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
INFORMATION THAT CAN BE SYNCHED
Type of supervisor Notes Data Eventa Alarms
PlantVisorPRO YES YES YES YES
PlantVisorEnhanced NO YES NO YES
PlantWatchPRO NO YES (*) YES YES
pCOWeb NO YES NO YES
(*) starting from version 2.1
15. ALARM SYNCHRONISATION
15.1 Synchronise local and remote supervisor
After having confgured a local supervisor, an initial synchronisation should be performed with the remote,
involving downloading the information selected during confguration (e.g. alarms, events...).
O
Access the list of supervisors from: census ->
installation -> supervisors.
O
Double click the supervisor in question to open
the details page.
O
Click to start a synchronisation.
Note: under supervision -> supervisor status
the date can be displayed corresponding to
the most recent synchronisation performed, in
the last synchronisation column.
Note: progress of the synchronisation process
can be displayed in the status window shown
at the top right or by accessing system ->
system registry -> events.
Synchronisation with the remote supervisor can
be started manually by the user from the remote,
as described above, or alternatively can start
automatically if a rule is set on the local supervisor to
call the remote in response to an alarm or an event
(see the manual).
Upon frst synchronisation the system receives the
system confguration; in addition, the alarms, events
and notes no older than 5 days are downloaded. This
maximum synchronisation interval can be confgured
under system -> confguration -> synchronisation
in the max synch days feld.
The table on the right shows the information that can
be synchronised, for each type of supervisor.
Note: the life test can be enabled for any type
of local supervisor.
41
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
15.2 Manage remote alarms
In order for an alarm on the remote to be considered as having ceased, it must have an end alarm time and
have been acknowledged (remote ack).
The user can also acknowledge alarms that are still active. When these cease on the local supervisor, they are
automatically moved from the table of active alarms to reset alarms.
If this option is not required, access system > confguration > synchronisation and disable mandatory
acknowledgement for alarms.
Individual alarms or groups of alarms can be acknowledged at the same time.
To acknowledge an individual alarm, access:
supervision -> alarms -> active alarms.
O
Double click the alarm to be acknowledged so
as to open the details page.
O
Enter any notes and click .
Important: A note must be entered before
acknowledging an alarm.
Under system -> confguration ->
synchronisation this rule can be disabled by
changing the value of the check notes on
acknowledged alarm feld. Alarms with low
priority can always be acknowledged without
entering a note.
O
Click .
Then if the alarm has an end time, it automatically
moves to the reset alarms page. If the end time is
not available, it remains in the active alarms table
until it is reset on the local supervisor.
42
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
To acknowledge more than one alarm at the same
time, access: supervision -> alarms -> active alarms.
O
Select all the alarms to be acknowledged. The
selected alarms are highlighted.
O
Click . A pop-up confrmation message is
displayed.
O
Click to confrm acknowledgement of the
alarms.
Note: These alarms are assigned a default
note that can be changed under system ->
confguration -> synchronisation in the default
acknowledge note feld.
Important: if no alarm is selected and
acknowledge is clicked, all the alarms that
satisfy the fltering criteria are acknowledged.


43
ENG
i
n
s
t
a
l
l
e
r
u
s
e
r
m
a
i
n
t
e
n
a
n
c
e
+0400022EN - rel. 1.1 - 18.11.2010
15.3 Inhibit alarms
Some alarms on the remote may still be active even if in reality they have ceased on the local supervisor.
This may occur, for example, if a local supervisor remains of line (inaccessible) for a time exceeding the max
synch days set. The active alarms on the remote that cease on the local during this period can no longer be
synchronised, thus appearing as active on the remote supervisor.
In these situations of inconsistency, alarm reset can be forced using the inhibition function on the remote
Note: an alarm that has already been reset on the remote supervisor cannot be inhibited.
O
Select all the alarms to be inhibited.
Note: The procedure for selecting the alarms
to be inhibited is the same as described for
acknowledgement.
O
Click .
CAREL INDUSTRIES Hqs
Via dellIndustria, 11 - 35020 Brugine - Padova (Italy)
Tel. (+39) 049.9716611 - Fax (+39) 049.9716600
e-mail: CAREL@CAREL.com - www.CAREL.com
Agenzia / Agency:
+
0
4
0
0
0
2
2
E
N

-

r
e
l
.

1
.
1

-

1
8
.
1
1
.
2
0
1
0