ENG - Carel

Transcription

ENG - Carel
remote supervision solutions
User manual
Integrated Control Solutions & Energy Savings
Content
SYSTEM REQUIREMENTS
1.1
1.2
1.3
2.
3.
5.
6.
7.
8.
23
Configure the email ....................................................................................................................................23
Configure the rule engine .......................................................................................................................23
Configure the notification groups .....................................................................................................24
Configure the time bands .......................................................................................................................25
DATA MANAGEMENT
8.1
8.2
22
Configure the life test.................................................................................................................................22
ALARM AND EVENT MANAGEMENT
7.1
7.2
7.3
7.4
20
Import a new model...................................................................................................................................20
Configure a model for use in KPI reports .......................................................................................21
LIFE TEST MANAGEMENT
6.1
13
Configure the supervisor network .....................................................................................................13
Configure the local network ..................................................................................................................15
Configure the modem connection ...................................................................................................16
Configure global parameters ................................................................................................................16
Manage the address book ......................................................................................................................17
Create new user .............................................................................................................................................18
MODELS
5.1
5.2
10
Install the software.......................................................................................................................................10
Activate thwe software license ............................................................................................................12
CONFIGURATION
4.1
4.2
4.3
4.4
4.5
4.6
6
Login ........................................................................................................................................................................6
Desktop..................................................................................................................................................................6
Lists ...........................................................................................................................................................................7
Details .....................................................................................................................................................................8
Favourites..............................................................................................................................................................9
START UP
3.1
3.2
4.
Minimum hardware requirements (recommended) .................................................................5
Software requirements.................................................................................................................................5
Languages............................................................................................................................................................5
GENERAL SCREENS
2.1
2.2
2.3
2.4
2.5
5
26
Configure data alignment .......................................................................................................................26
Configure logged variables ....................................................................................................................27
installer
1.
KPI REPORTS
9.1
9.2
28
Configure the variables analysed on the KPI reports .............................................................28
Configure data presentation on the KPI reports .......................................................................29
10. REMOTE MANAGEMENT OF LOCAL USERS
30
10.1 Display local users ........................................................................................................................................30
10.2 Create and edit local users ......................................................................................................................30
11. TROUBLESHOOTING
installer
9.
32
11.1 Export log files ................................................................................................................................................32
12. CHANGE USER DATA
33
12.1 Cambio dati utente ....................................................................................................................................33
13. ACCESSING THE LOCAL SUPERVISORS
34
13.1 Display local supervisors ..........................................................................................................................34
14. SUPERVISOR LIFE TEST
14.1
35
Display life test status................................................................................................................................35
15. DISPLAYING ALARMS AND EVENTS
36
16. DISPLAYING DATA
39
user
15.1 Display alarms .................................................................................................................................................36
15.2 Display alarms and events in supervisor detail ..........................................................................37
15.3 Display alarm report....................................................................................................................................38
16.1 Display graphs ...............................................................................................................................................39
17. EXPORT DATA LOG
41
17.1 Create export template.............................................................................................................................41
17.2 Scheduled export .........................................................................................................................................42
17.3 Download report ..........................................................................................................................................42
18. DISPLAYING KPI REPORTS
43
KPI temperature report .............................................................................................................................43
Display KPI daily temperature reports .............................................................................................44
Display KPI performance reports ........................................................................................................44
Display KPI energy reports ......................................................................................................................45
19. ALARM SYNCHRONISATION
46
19.1 Synchronise local and remote supervisor .....................................................................................46
19.2 Manage remote alarms .............................................................................................................................47
19.3 Inhibit alarms...................................................................................................................................................49
maintenance
18.1
18.2
18.3
18.4
ENG
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,
Internet Explorer 9,
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.
5
"remotepro "+0400022EN - rel. 1.2 - 14.03.2012
ENG
2.
2.1
GENERAL SCREENS
Login
Connect with a supported browser to: https:// [server address] / Remote (replace [server address] with the IP address
or name of the computer where RemotePRO is installed).
To access the system, enter the user name and password and select login:
When installing RemotePRO, only one system user is created, with Installer profile and the following credentials:
• username: admin;
• password: adminadmin.
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 figure 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 flag 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 modified by the user and that allow quick access to the functions provided by the
system. The first 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.
"remotepro" +0400022EN - rel. 1.2 - 14.03.2012
6
ENG
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 filtering, 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 identified:
1. The parameters that can be set to filter the data in the list. Once the data has been entered, select
2.
to filter the
information.
resets the filtering fields, displaying all the data.
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” field is used to modify the number of rows displayed on each page (default 15).
Note: under Administration -> Access -> Edit User this default value can be changed for the current
user.
5. If there is more than one page, buttons are displayed to access a specific page or move to the next, previous, first
or last page (using the arrows).
6. The columns with the
7.
icon are used to sort the data in the table (by selecting the column header row) in
increasing or decreasing order.
At the foot of the page are buttons used to export the data in the list (all the data that satisfy the filters set) in
different formats (csv, xls, xml, pdf ).
7
"remotepro "+0400022EN - rel. 1.2 - 14.03.2012
ENG
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
2
3
1. Each page includes the basic functions (create, edit, display, delete) and/or the specific functions for the page;
2. The required fields (for example, to create a new record) are highlighted by a red asterisk;
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 fields.
"remotepro" +0400022EN - rel. 1.2 - 14.03.2012
8
ENG
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 field 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:
9
"remotepro "+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
3.
START UP
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
user
 Insert the CD in the CD drive.
The installation procedure starts automatically; if it doesn’t, access the CD drive and run “start.bat”, then follow the
instructions on the screen.
 Read and accept the license terms, then click
“
maintenance
next “.
 Click “install” to start installing the software.
 Wait until all the components of the software
have been installed.
 When
installation is completed, the system
needs to be rebooted, click “yes”.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
10
ENG
user
installer
 Select “finish” and wait for the PC to restart
 When the PC restarts, the screen on the right
is displayed automatically (Splash Screen); this
indicates initialisation of the application.
maintenance
Note: in some operating systems display of
this screenshot is not supported. This does not
affect system operation.
 Wait for the Splash Screen to close and double
click the RemotePro icon to access the system.
 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.
11
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
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).
The available modules are:
• ‘Remote Service’, that allows management of the alarms, up to max 50 supervisors;
• ‘Central Data Management’, for the log storage server up to 7000 variables from the local supervisors.
user
To register the software, the user needs to provide:
• the “Mac Address” (unique identifier 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.

Access: Administration -> Module
Note: the icons on the page indicate:
software activated
maintenance
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” field 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.
 Enter the serial number containing the information
relating to the software being activated
 Enter the activation code provided when
registering
 Click
.
Note: all software that can be registered is distributed with the corresponding “Serial Number”.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
12
ENG
4.1
CONFIGURATION
installer
4.
Configure the supervisor network
Each local supervisor must be configured in the system.
 For each supervisor to be configured, access: census
-> installation -> supervisors
maintenance
user
This page lists the supervisors that are currently
configured, showing:
• The unique identifier 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 = configuration,
A = alarms, E = events, N = notes)
• data alignment (D)
• outgoing life test (T)
• incoming life test (L)
 Selecting the
button opens the details page for
configuring a new supervisor.
 Enter
the data required to configure the local
supervisor.
• The “identifier” 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 “identifier” field must be unique, therefore
the local supervisors also need to be configured
correctly (see the related manuals).
• The “Mac Address” field (unique identifier of the
network card) is only needed for the pCOWeb.
13
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
user
installer
ENG
If the supervisor is connected via LAN, in the “IP address”
enter the number that uniquely identifies the device
connected to the network or the DNS name.
If the supervisor is connected via modem, in the
“Phone” field enter the phone number to dial.
Important: the modem connection is a slow data
transmission channel. When configuring a supervisor
that uses this channel, the data to be transferred
between the local and remote supervisors need to be
selected carefully, to limit traffic 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” field, 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.
 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.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
14
ENG
Configure the local network
Especially for systems operating in a company LAN, access to the network over HTTP and HTTPS protocols may be
controlled via a network proxy.
As the RemotePRO server communicates with PlantVisorPRO local supervisors using HTTPS and with the
PlantWatchPRO and pCOWeb supervisors using HTTP, the system can be configured to communicate with these
supervisors using a network proxy.
installer
4.2
2. Enter the required fields
3. Click
Important: the proxy cannot be enabled for just come of the supervisors configured. If a series of supervisors can
only be accessed via proxy and another series does not require this, the system administrator also needs to configure
the proxy to access the latter
Note: below is a list of ports required for correct communication between RemotePRO and the various different
types of local supervisor:
Supervisor type:
Source:
PlantVisor Enhanced PlantVisor
Enhanced
RemotePRO
RemotePRO
Destination and port:
RemotePRO: TCP/2016
Use:
Synchronisation action
PlantVisor Enhanced:
TCP/20 & TCP/21
PlantVisor Enhanced:
TCP/80
Data Synchronisation and Alignment
RemotePRO: TCP/443
RemotePRO: TCP/8443
PlantVisorPRO: TCP/443
Synchronisation action
Synchronisation action (PVP version < 2.0 ONLY)
Online Browsing, Data Synchronisation and Alignment
Online Browsing
PlantVisorPRO
PlantVisorPRO
PVP
RemotePRO
PlantWatch PRO
PlantWatchPRO RemotePRO: TCP/2008
Synchronisation action
RemotePRO
PlantWatchPRO: TCP/1981 Data Synchronisation and Alignment
RemotePRO
PlantWatchPRO: TCP/80
Online Browsing
pCOWeb
pCOWeb
RemotePRO
RemotePRO
RemotePRO: TCP/20 &
TCP21
pCOWeb: TCP/80
pCOWeb: TCP/20 and
TCP/21
15
Data Synchronisation and Alignment
Online Browsing and Data Log Request
Data Log Request
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
user
1. Access: System->Channel-> LAN Configuration
ENG
user
installer
4.3
Configure the modem connection
This page is used to configure 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 configuration

To configure new modem access:
channel -> RAS configuration
system ->
 Enter all the data required to configure the modem.

Click
.
maintenance
Important: after having configured a new modem, the PC needs to be rebooted so it can be recognised by
the system.
Note: the first
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).
button can be used to display the log file that keeps track of the trend in modem
Note: the second
connections and any errors.
4.4
Configure global parameters
This section describes how to configure certain global operating parameters:
• Server public IP: IP address or domain name of the RemotePRO server used for access from the outside to the
supervisors connected to the Intranet (if enabled);
• checkbox to enable encoding of the addresses generated (by default a path is created based on the local
supervisor address);
• path of the backup directory on the server where data is saved during system maintenance;
• checkbox to enable password strength checking;


Enter the options
Click
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
16
Important: the server public IP must be an address that’s available to anyone needing to access the local
supervisors (if the function also needs to be available via Internet, it must be a public IP address or a registered
domain name)
Important: saving the parameters relating to access via Internet to local supervisors involves restarting part of
the RemotePRO server, which may mean a few seconds of slower operation
installer
ENG
4.5
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
notifications in the event of alarms.
 Click
maintenance
 Access to: census -> address book
.
 Enter a unique code and a description.
 Enter the various details for the contact.
 Click
user
Note: a password is considered strong if it contains at least one letter of the alphabet, a number and one of
the following special characters .,_!?$%&
.
17
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
 To create a new user, access administration ->
 Click
maintenance
installer
Create new user
user
4.6
access -> users
.
 Complete all the fields required to configure the new
user and click
.
The “status” field indicates whether or not the application can be accessed; this allows users to be temporarily disabled.
The “list refresh frequency” field, if not equal to zero, specifies the number of minutes between automatic refreshing
for the pages where this is supported (e.g. List of alarms and Supervisor status), while the “rows per page” field defines
how many rows are displayed in the lists, unless otherwise specified.
Important: the “status” field must be “enabled” to allow the user to login.
Important: if the Password Complexity item is enabled under System -> Configuration -> Global, user
passwords must contain at least one letter of the alphabet, a number and one of the following symbols: .
(decimal point) , (comma) _ (underscore) ! (exclamation mark) ? (question mark) $ (dollar sign) % (percentage)
and & (ampersand)
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 configuration and operation).
The User profile offers read-only access to the main transactions.
Maintainance users have extended access that allows complete management of the alarms.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
18
ENG
Maintenance
Read/write
Read/write
Read-only
Read-only
Read/write for synchronisation
Read/write
CENSUS
Supervisor installation
Model installation
Address book
Read/write
Read/write
Read/write
Read-only
Read-only
Read-only
Read-only
Read-only
Read-only
REPORTS
Log report
Export data log
Alarm report
Configuration
KPI temperature
KPI energy
Read/write
Read/write
Read/write
Read/write
Read-only
Read-only
Read/write
Read/write
Read/write
Read-only
Read-only
Read-only
Read/write
Read/write
Read/write
Read-only
Read-only
Read/write
Read/write
Read/write
Read/write
Read/write
Read/write
Read/write
Read/write
Read-only
Read/write
Read-only
Read/write
Read/write
Read/write
Read/write
Read/write
Read/write
SYSTEM
System register
Rules engine
Channel
Log
Global
Life test
Data alignment
ADMINISTRATION
User access
Access /edit user
Favourites
System page
Modules
Export log file
Read/write
Read/write
Read/write
Read/write
Read/write
Read/write
19
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
user
User
maintenance
Installer
SUPERVISION
Supervisor status
Alarms
installer
The following table shows which functions are enabled for the different types of profile:
ENG
MODELS
Device models can be used to associate information with variables from pCOWeb supervisors or alternatively to display
values from custom devices for KPI temperature and energy.
maintenance
user
installer
5.
5.1




Import a new model
To import a new model, access: Configuration>Installation ->Models
Click
Fill in the fields describing the model, select the
ZIP file containing the required files (see the
note) and select the reference language for the
descriptions
Click
Important: the language must be included among those configured for the model
Important: the information that identifies a variable (type, address, variable length, variable size and bit
position) must be unique, so as to allow correct association with the devices
Note: data can only be imported from a file taken from a Carel 1Tool project.
The imported file must be a standard ZIP (without password and not using the maximum compression ratio),
containing just two project files:
- 2CF
- 2CT.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
20
ENG

Access:
Configuration->Installation ->Models
Double click the model to be configured
Click the Variable Model tab

For the model variables select the corresponding
sub-devices and KPI meanings (see the note)

Click
Note: each device can refer to several cabinets / energy meters (up to 10).
The model variables must be divided into corresponding sub-devices. If the model has just one cabinet /
energy meter, all the variables involved will be associated with the same sub-device
Note: for each model involved in KPI reports, the meaning of the variables needs to be specified so that the
system can process them correctly
For KPI temperature reports, the following variables are used:
Temperature value;
Set point;
Differential;
Compressor status;
Defrost status;
High temp. alarm (optional);
Low temp. alarm (optional).
•
•
•
•
•
•
•
KPI energy reports allow multiple meters for the same supervisor. If some of these are cascaded, the meters that are
downstream, that measure just some of the energy and that are upstream can all be specified, indicating the total
count to avoid errors in calculating overall energy.
For a total energy meter the only variable required is: Total Energy
while for a partial energy meter the only variable required is: Energy
Note: for a sub-device to be included in the KPI reports, all the required variables must be correctly logged by
the RemotePRO server
21
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
user


Configure a model for use in KPI reports
installer
5.2
ENG
installer
6.
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 configured.
6.1
user
LIFE TEST MANAGEMENT
Configure 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.
maintenance
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.
 Access:
system -> configuration -> life test.
 Select
how many times the life test should be
performed every day using the corresponding fields.
• “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 configure the
local supervisors for contacting the remote.
 Click
.
Note: Different intervals can be defined 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).
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
22
ENG
7.1
ALARM AND EVENT MANAGEMENT
Configure the email
The I/O peripherals must be configured in order to send notifications via email when alarms occur.
installer
7.
 Access:
system -> channel -> email configuration.
 Click
user
 Enter all the data required for Email configuration.
.
7.2
Configure the rule engine
Synchronised alarms can be managed by the rules engine and notified via email to relevant personnel who need to
respond. Notification groups can be defined to group different contacts together.
Whenever an alarm is signalled on the remote supervisor, a special procedure checks whether there are alarm notification
rules in the time band. If there are, the specific alarm is checked to see whether there are specific rules (for example,
based on alarm priority). If there is at least one specific rule, all the groups of contacts associated with the alarm will be
notified.
 Access:
system -> rules engine -> rules.
 Click
.
 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.
 Click
.
23
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
Note: once the configuration has been saved,
an email address can be entered in the Recipient
field to perform a test send
ENG
installer
7.3
Configure the notification groups
 Access:
system -> rules engine -> notification groups
.
user
 Click
maintenance
 Enter a description for the group.
Important: notification groups cannot be
created for a channel (e.g. email) that’s not
configured.
 Click
.
 Go to the “contacts” tab and from the drop-down
menu select the required contacts from popup.
 Click
.
Important: The drop-down menu displays all
the email contacts configured in the address book.
 Repeat steps 5 and 6 to associate other contacts
with the notification group.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
24
ENG
7.4
Configure the time bands
installer
 Access:
.
maintenance
 Click
user
system -> rules engine -> time band.
 Select the day of the week or “every day”.
 Select the rule to be applied.
 Select the time interval for the rule.
 Click
.
Important: if the “enabled” check box is not
selected the time band is ignored.
 Select the “Notification groups” tab.
 From
the drop-down menu select the group in
question and click the button.
 Repeat steps 7 and 8 to associate other notification
groups to the rule.
25
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
8.
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 field in just one location, allowing
comparative analysis to be performed.
user
8.1
maintenance
DATA MANAGEMENT
Configure 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 configured. 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” ( ).
 To configure data alignment access:
system -> configuration -> data alignment
 Set
the data alignment start time in the “data
alignment start time” field.
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.
 In the “FTP server” field enter the IP address of the
PC where the application is installed. The “localhost”
alias is not allowed for this field.
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 specified for
correct interaction with pCOWeb supervisors.
 Click
.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
26
ENG
Configure logged variables


The list of variables that are logged can be
changed under:
system->log->variables
The top part of the page is used to set the filters
for reducing the number of variables displayed
(click


maintenance
The system acquires the variables to be logged in the order these are received from the local supervisors.
By default the system accepts all variables until reaching the maximum number allowed by the “Data Central
Management” license.
On reaching this limit, the system then ignores the values of new variables:
to apply the filters)
In the “FTP server” field enter the IP address of
the PC where the application is installed, insert
to the end ‘RemotePRO’.
Click
user
installer
8.2
to apply the changes
Important: if an update attempts to enable the log for a number of variables that exceeds the license limits,
the operation will in any case terminate when reaching this maximum value
Note: the last field in the filter area shows the number of the variables that can still be logged (this is zero
when the license limits are reached)
Note: for a variable to be shown in the list, at least one synchronisation must have been performed (except
for pCOWeb supervisors) and the values must effectively derive from a data alignment procedure (for correct
configuration of the log and data alignment on the local supervisor, see the corresponding manual)
27
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
9.
KPI REPORTS
The KPI report offers the user a rapid overview of the performance of each supervisor.
The data used for analysis are retrieved from the local supervisor; data alignment configuration is therefore required
to use this function
9.1
Configure the variables analysed on the KPI reports
user
Following the first synchronisation with a supervisor, to configure the variables analysed proceed as follows:
 For each supervisor to be configured access:
database -> installation -> supervisors
 Double click the supervisor in question to open the
maintenance
details page.
 Click the “devices” tab.
 In the “device model” column set the correct model
for the controllers being configured.
 Click .
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 configured 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;
• Differential;
• Compressor status;
• Defrost status;
• High temp. alarm (optional);
• Low temp. alarm (optional).
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
28
ENG
9.2
Configure data presentation on the KPI reports
installer
To customise the colours on the KPI reports, proceed as follows:
 Access:
report -> KPI -> configuration KPI
 Select the various colours (background and font)
 Click .
user
button to restore the original
To normalise energy consumption values, considering that sites may differ enormously in aspects such as size,
opening times, number of controllers:
 Access:
report -> KPI -> KPI energy -> supervisor weight
 For each supervisor, set a normalisation value (other
than 0)
 Click .
 if necessary, customise the description of the

“normalisation quotient” under report -> KPI -> KPI
configuration
Click .
The normalisation value set will be used as the quotient
for the absolute consumption value.
29
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
Note: use the
configuration
ENG
installer
10. REMOTE MANAGEMENT OF LOCAL USERS
Important: remote management of Local Users is currently only supported by PlantVisorPRO version 2.0 and
higher.
user
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 configure the supervisors accordingly, without having to
repeat the configuration for each individual user on each supervisor.
10.1 Display local users
maintenance
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.
 Access:
administration -> access -> local users
This page lists the local users currently configured,
displaying:
• username;
• two numbers that represent the number
of supervisors configured (the first 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 configured.
an icon indicating any supervisors connected via
modem;
user profile.
10.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 specific manual for the supervisor used.
 Access:
administration -> access -> local users
 Select
the
button to access the screen for
creating/editing a user
 Specify the username for the user being created.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
30
ENG
 Set the password
installer
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: . , _ ! ? $ % &
 Select the profile
button.
maintenance
 Select the
user
Note: The four standard PlantVisorPRO 2.0
profiles 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 profile used on the specific supervisor.
 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
icon only if the user has
marked by the
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.
31
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
 Access: administration -> access -> local users
 Select the
user
button to transfer the changes
made so far to the configuration of supervisor local
users
Important: All changes made to the users and
the list of supervisors will not be applied until the
maintenance
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 first 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).
11. TROUBLESHOOTING
11.1 Export log files
To provide further information during service, it may be useful to export and attach the system log files.
 To get the RemotePRO system log files access:
Administration->Export Log Files;
 Click
to prepare an updated file;
 Click
to download a ZIP file containing the log files.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
32
ENG
installer
12. CHANGE USER DATA
The currently connected user can change their own personal details, access password and display preferences.
 Access: Administration -> Users -> Edit User
 Edit the data as desired
 Click
33
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
utente
12.1 Cambio dati utente
ENG
maintenance
user
installer
13. ACCESSING THE LOCAL SUPERVISORS
13.1 Display local supervisors
RemotePRO allows quick connection to all local supervisors configured in the system:
 Access: supervision -> supervisor status
This page lists the supervisors that are currently
configured, 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).
Note:
•
Connection to a supervisor can only be established by selecting the green
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
buttons. For LAN connection,
.
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
modem.
•
It is important to close the open modem connections using the red
Note: an authorised user can access the system
-> channel -> RAS configuration and close the
modem connection using the first
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
button.
34
for all supervisors connected via
button, to avoid malfunctions.
ENG
14.1
installer
14. SUPERVISOR LIFE TEST
Display life test status
 To
utente
display the result of the life test, access:
supervision -> supervisor status.
 Check the “life test” column, showing the outcome
maintenance
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 specific supervisor
35
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
15.1 Display alarms
The alarms received from the local supervisor can be
displayed by accessing: supervision -> alarms ->
active alarms.
maintenance
user
installer
15. DISPLAYING ALARMS AND EVENTS
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 different colours, based on their priority:
Note: the possibility to display reset alarms yet to be acknowledged on this page can be enabled under system
> configuration > synchronisation.
When an alarm ends on the local supervisor and has been acknowledged on the remote system, if configured, the
alarm is shown in the list of reset alarms, visible by accessing: supervision -> alarms -> reset alarms.
Active
alarm
Reset
alarm
Priority
Technical alarm (e.g. life test)
Highest
High
Medium
Low
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
36
ENG
15.2 Display alarms and events in supervisor detail
installer
Alarms and events can be displayed corresponding to just one supervisor.
utente
 Access: supervision -> supervisor status
 Double click the supervisor in question to open the
details page.
maintenance
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.
 To display the alarms on the supervisor, click the
“active alarms” tab.
This page only displays the alarms corresponding to
the selected supervisor.
 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 configuration problems.
error:
signals problems that stop operation of the system.
37
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
To display an alarm report, access: report -> alarms and
select the type of report.
maintenance
user
installer
15.3 Display alarm report
 Select the desired period using the calendars
 Click
Note: the reports can be exported (in PDF format) by clicking
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
38
.
ENG
16.1 Display graphs
Once having received data on the server, the user can, for each device, display a graph showing the aligned variables.
installer
16. DISPLAYING DATA
 To display a device graph, access to: supervision->
utente
supervisor status
maintenance
 Double click the supervisor in question to open the
details page
 Click
the “controllers” tab. The list of all the
instruments connected to the local supervisor is
displayed.
 Double click the device to display the corresponding
graph.

Click the “Log data graphs” tab.
Note: the first time the graph is accessed for a
device, the variables displayed need to be selected.
39
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
user
installer
 Select the variables, choose the colour.
 Select the starting date and the duration of the
maintenance
period and click
.
Note: an area on the graph can be selected to
zoom the data displayed. Selecting the
returns to the previous zoom level.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
button
40
ENG
17.1 Create export template
To speed up and standardise exporting of logged data, a template configuration has been introduced for specifying
which variables are to be included in the report.
Access:
Report->Log Report->Report Templates


Click .
Enter the required fields (see Note 1)

Enter the list of variables to be exported (see Note
2)

Click
maintenance
utente

installer
17. EXPORT DATA LOG
.
Note: a template can be defined as private, i.e. only available to the user that created it, or alternatively as
shared, i.e. accessible to all system users. The information relating to the report channel (email or download),
export frequency and period will be applied by default when effectively used (manually or scheduled),
however this can also be changed at the time if required.
Note: select ‘Variable model’ to add variables taken from known models and export the data relating to these
variables from all instances corresponding to such models. On the other hand, select ‘Variable’ to export the
selected variables.
Important: Non è possibile esportare contemporaneamente variabili puntuali e variabili prese dai modelli.
17.2 Manual export

Access:
Report->Log Report-> Export Report


Select the template
Modify the template default values if necessary
41
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
installer
ENG


Select the export date and period
Click
Note: the report is placed in the queue and processed in the background so as to avoid overloading the
system.
At the end of the export operation, the report will be available on the selected channel (email or download page)
maintenance
user
17.3 Scheduled export

Access:
Report->Log Report-> Scheduled Reports


Click .
Select the template

Modify the template default values as required

Select the required scheduling (monthly, weekly
choosing the day, daily) and time

Click
.
Important: when scheduling a report, remember that data alignment is performed once a day at a set time.
To ensure maximum data is available, the export operation should be scheduled after data alignment (data
alignment processing time varies based on the volume of data).
17.4 Download report
1. To access the reports (scheduled or manual) created for download, access: Report->Log Report->Reports
Archive:
2. To download an individual report click the green down arrow
3. To download several reports at the same time, click the corresponding checkbox and then click
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
42
.
ENG
After having configured the KPI reports and performed at least one data alignment, the reports corresponding to
temperature and energy consumption can be displayed.
installer
18. DISPLAYING KPI REPORTS
Over critical:
Over range:
In range:
Under range:
Under critical:
temperature's value raised over high critical threshold;
temperature's value varied between differential and high critical threshold;
temperature's value varied between set point and differential threshold;
temperature's value varied between set point and low critical threshold;
temperature's value descended under low critical threshold;
where the high and of low critical thresholds are defined respectively as the differential + 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 define:
As well as the colours of the areas described previously, two other colours are envisaged, which identify:
Defrost
Undefined
defrost relay have been turned on;
temperature's value have not been stored.
43
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
maintenance
There are two different temperature reports. The first 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, differential and a user parameter called “critical
variation”. The areas that these three parameters identify are defined as follows:
utente
18.1 KPI temperature report
ENG
user
installer
18.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
 To display the KPI daily temperature reports access:
report -> KPI -> KPI temperature -> KPI daily
temperature
 Select the supervisor to analyse
 Select the analysis date (default “today”)
 Set the critical variation (default 2°)
 Select the step for the intervals to divide the hours
maintenance

into (for example, setting 15 minutes means 4
intervals each hour)
Click .
Note: if the temperature deviates to the point of
setting off an alarm, a specific 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
18.3 Display KPI performance reports
 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 different 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
Select the supervisor to analyse

 Select the analysis date (default “today”)
 Select the period (daily, weekly or monthly)
 Set the critical variation (default 2°)
 Click .
Note: double clicking a row accesses the graph
showing the trend of device variables over the selected
period.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
44
ENG
18.4 Display KPI energy reports
installer
 To display the KPI energy reports access:
utente
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);
• Effective energy consumption, either the sum of
consumption from the partial energy meters or
the value of the global energy meter.

 Click
maintenance
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.
Select the analysis date (default “today”)
.
At the foot of the table are the totals of consumption and
the average of effective and normalised consumption.
Colour
Note: the normalised consumption values provide
a most reliable comparison of performance between
supervisors.
Performances
Best
Better than average
Worse than average
Worst
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;
• Effective 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.
45
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
installer
19. ALARM SYNCHRONISATION
19.1 Synchronise local and remote supervisor
After having configured a local supervisor, an initial synchronisation should be performed with the remote, involving
downloading the information selected during configuration (e.g. alarms, events...).
 Access
user
the list of supervisors from: census ->
installation -> supervisors.
 Double click the supervisor in question to open the
maintenance
details page.
 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 first synchronisation the system receives the system configuration; in addition, the alarms, events and notes
no older than 5 days are downloaded. This maximum synchronisation interval can be configured under system ->
configuration -> synchronisation in the “max synch days” field.
The table on the right shows the information that can be synchronised, for each type of supervisor.
INFORMATION THAT CAN BE SYNCHED
Type of supervisor
Notes Data Eventa
Alarms
PlantVisorPRO
PlantVisorEnhanced
PlantWatchPRO
YES
YES
NO
YES
NO YES (*)
YES
NO
YES
YES
YES
YES
pCOWeb
NO
NO
YES
YES
(*) starting from version 2.1
Note: the “life test” can be enabled for any type of local supervisor.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
46
ENG
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 > configuration > synchronisation and disable mandatory
acknowledgement for alarms.
Individual alarms or groups of alarms can be acknowledged at the same time.
installer
19.2 Manage remote alarms
maintenance
uter
To acknowledge an individual alarm, access:
supervision -> alarms -> active alarms.
 Double click the alarm to be acknowledged so as to
open the details page.
 Enter any notes and click
.
Important: A note must be entered before
acknowledging an alarm.
Under system -> configuration -> synchronisation
this rule can be disabled by changing the value
of the “check notes on acknowledged alarm”
field. Alarms with low priority can always be
acknowledged without entering a note.
 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.
47
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
ENG
 Select
all the alarms to be acknowledged. The
selected alarms are highlighted.
maintenance
user
installer
To acknowledge more than one alarm at the same time,
access: supervision -> alarms -> active alarms.
 Click
. A pop-up confirmation message is
displayed.
 Click
to confirm acknowledgement of the
alarms.
Note: These alarms are assigned a default note
that can be changed under system -> configuration
-> synchronisation in the “default acknowledge
note” field.
Important: if no alarm is selected and
“acknowledge” is clicked, all the alarms that satisfy
the filtering criteria are acknowledged.
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
48
ENG
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 off 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
installer
19.3 Inhibit alarms
Note: an alarm that has already been reset on the remote supervisor cannot be inhibited.
uter
 Select all the alarms to be inhibited.
 Click
maintenance
Note: The procedure for selecting the alarms to
be inhibited is the same as described for
acknowledgement.
.
49
“remotepro “+0400022EN - rel. 1.2 - 14.03.2012
NOTE: ______________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
NOTE: ______________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
CAREL INDUSTRIES Hqs
Via dell’Industria, 11 - 35020 Brugine - Padova (Italy)
Tel. (+39) 049.9716611 - Fax (+39) 049.9716600
e-mail: [email protected] - www.CAREL.com
"remotepro" +0400022EN - rel. 1.2 - 14.03.2012
Agenzia / Agency: