Installation Guide

CitectSCADA 2015
Installation and Configuration Guide

June 2015
Legal Information
DISCLAIMER
Schneider Electric (Australia) Pty. Ltd. makes no representations or warranties with respect to this manual and, to the maximum
extent permitted by law, expressly limits its liability for breach of any warranty that may be implied to the replacement of this manual
with another. Further, Schneider Electric (Australia) Pty. Ltd. reserves the right to revise this publication at any time without incurring
an obligation to notify any person of the revision.
The Example Projects are provided to you for the purpose of illustrating how the SCADA software 2015 could be used in an
operational environment ("the Purpose").Schneider Electric grants you a royalty free, non exclusive, non transferable license to use the
example projects installed with your SCADA software version 2015 (“the Example Projects”) for the Purpose only.
The Example Projects are provided by Schneider Electric as part of the SCADA software version 2015 on an "as is" basis and Schneider
Electric does not guarantee the reliability, serviceability or function of the Example Projects.
Should you modify the Example Projects, you bear the risk of any use of such modified Example Projects.
Schneider Electric gives no express warranties, guarantees or conditions and to the extent permitted under applicable laws, Schneider
Electric disclaims all implied warranties, including any implied warranties of merchantability, fitness for a particular purpose or non-
infringement of third parties’ intellectual property rights.
Schneider Electric shall not be liable for any direct, indirect or consequential damages or costs of any type arising out of any action
taken by you or others related to the Example Projects.
COPYRIGHT
© Copyright 2015 Schneider Electric (Australia) Pty. Ltd. All rights reserved.
TRADEMARKS
Schneider Electric (Australia) Pty. Ltd. has made every effort to supply trademark information about company names, products and
services mentioned in this manual.
Citect, CitectHMI, and CitectSCADA are either registered trademarks or trademarks of Schneider Electric (Australia) Pty. Ltd. .
Pelco, Spectra, Sarix, Endura, are registered trademarks of Pelco, Inc.
IBM, IBM PC and IBM PC AT are registered trademarks of International Business Machines Corporation.
MS-DOS, Windows, Windows NT, Microsoft, and Excel are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
DigiBoard, PC/Xi and Com/Xi are trademarks of Digi International Inc.
Novell, Netware and Netware Lite are either registered trademarks or trademarks of Novell, Inc. in the United States and other
countries.
dBASE is a trademark of dataBased Intelligence, Inc.
All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their
respective holders.
GENERAL INFORMATION
Some product names used in this manual are used for identification purposes only and may be trademarks of their respective
companies.
June 2015 edition for CitectSCADA Version 2015.
Manual Revision Version 2015.
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed
by Schneider Electric (Australia) Pty. Ltd. for any consequences arising out of the use of this material. © 2015 Schneider Electric
(Australia) Pty. Ltd. . All Rights Reserved.
Validity Note
The present documentation is intended for qualified technical personnel responsible for the implementation, operation and
maintenance of the products described. It contains information necessary for the proper use of the products. However, those who wish
to make a more "advanced" use of our products may find it necessary to consult our nearest distributor in order to obtain additional
information.
The contents of this documentation are not contractual and in no way constitute an extension to, or restriction of, the
contractual warranty clauses.
Contact Schneider Electric today at www.schneider-electric.com

Contents
Legal Information 1
Contents 3
Safety Information 5
Chapter 1: Introduction 7
About This Guide 7
Purpose 7
Maintaining System Currency 7
Chapter 2: Upgrading 9
New Features 10
Introduced in 2015 10
Upgrading a Runtime-only Installation 12
Chapter 3: Installation Description 13

Task Selection Dialogs 13
Installation Profiles 13
Documentation Installation 15
Add-ons Installation 15
Communication Drivers 16
Chapter 4: Installation Requirements 17

All Core Components 17
System Hardware 17
System Software 18
Runtime Only Server or Client System Software 21
Software Protection 21
3
Contents
Software Licensing 22
Updating Your Hardware Key 22
Floating Point License Manager 23
FlexNet license server 23
Independent Point Count 24
CitectSCADA License Point Count 26
CiUSAFE dialog properties 27
Demo Mode 28
Dynamic-point count licensing 29
Chapter 5: Installation 31
The Installation Process 31
Preliminary Installation 31
Installation Profiles 34
Completing the Installation 38
Communication Drivers 41
Installing Additional Communication Drivers 44
Installing Service Packs 45
Modify, Repair, or Remove Components 45
Uninstall a Service Pack 47
Chapter 6: Configuration 49
Local Area Network Configuration 49
Network Communications Overview 50
Configuring Communications Over a WAN 51
Web Server Configuration 51
The IIS Virtual Directory 52
Setting Up Security 53
Web Client user account types 53
Configuring Security Using IIS 54
Testing the Web Server Security Settings 57
Logging on to the Web Server 58
Index 61
4
Safety Information
Hazard categories and special symbols
The following symbols and special messages may appear in this manual or on the
product to warn of potential hazards or to call attention to information that clarifies or
simplifies a procedure.
Symbol Description
The addition of either symbol to a “Danger” or “Warning” safety

label indicates that an electrical hazard exists which will result in
or personal injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to personal

injury hazards. Obey all safety messages that follow this symbol to
avoid possible injury or death.
DANGER indicates an imminently hazardous situation, which, if not avoided, will result in
death or serious injury.
WARNING indicates a potentially hazardous situation, which, if not avoided, can result in
death or serious injury.
CAUTION indicates a potentially hazardous situation which, if not avoided, can result in
minor or moderate injury.
NOTICE
NOTICE used without a safety alert symbol, indicates a potentially hazardous situation
which, if not avoided, can result in property or equipment damage.
Please Note
5
Safety Information
Electrical equipment should be installed, operated, serviced, and maintained only by

qualified personnel. No responsibility is assumed by Schneider Electric (Australia) Pty.
Ltd. for any consequences arising out of the use of this material.
Before You Begin
CitectSCADA is a Supervisory Control and Data Acquisition (SCADA) solution. It facil-

itates the creation of software to manage and monitor industrial systems and processes.
Due to CitectSCADA's central role in controlling systems and processes, you must appro-
priately design, commission, and test your CitectSCADA project before implementing it
in an operational setting. Observe the following:
UNINTENDED EQUIPMENT OPERATION
Do not use CitectSCADA or other SCADA software as a replacement for PLC-based control
programs. SCADA software is not designed for direct, high-speed system control.
Failure to follow these instructions can result in death, serious injury, or equip-
ment damage.
LOSS OF CONTROL
l The designer of any control scheme must consider the potential failure modes of con-
trol paths and, for certain critical control functions, provide a means to achieve a safe
state during and after a path failure. Examples of critical control functions are emer-
gency stop and overtravel stop, power outage and restart.
l Separate or redundant control paths must be provided for critical control functions.
l System control paths may include communication links. Consideration must be given
to the implications of unanticipated transmission delays or failures of the link.
l Observe all accident prevention regulations and local safety guidelines. 1
l Each implementation of a control system created using CitectSCADA must be indi-
vidually and thoroughly tested for proper operation before being placed into service.
Failure to follow these instructions can result in death, serious injury, or equip-
ment damage.
1. For additional information, refer to NEMA ICS 1.1 (latest edition) "Safety Guidelines
for the Application, Installation, and Maintenance of Solid State Control", and to NEMA
ICS 7.1 (latest edition) "Safety Standards for Construction and Guide for Selection, Install-
ation and Operation of Adjustable-Speed Drive Systems" or their equivalent governing
your particular location.
6
Chapter 1: Introduction
About This Guide
Purpose
This document is a guide for installing CitectSCADA. It describes the installation process
and optional components which can be installed in each environment, either on a single
workstation, or on a network (online upgrade).
The configuration section provides an overview of using CitectSCADA in a Local Area
Network (LAN), a Wide Area Network (WAN), and as a Web Server.
It includes information on the following aspects of installing CitectSCADA:
l "Upgrading"
l "Installation Description"
l "Installation Requirements"
l "Installation"
l "Configuration "
Maintaining System Currency

After you have completed the installation and configuration of CitectSCADA and
deployed it as your production system, it is very important that you keep your software
up to date. Schneider Electric (Australia) Pty. Ltd. will periodically publish updates in
the form of Service Packs, Hot Fixes or Advisories relating to safety, security and
functionality of CitectSCADA. These updates are available from the Knowledge Base
page of the “MyCitect” web site or http://www.citect.schneider-electric.com/servicepacks.
We especially recommend that you nominate a person in your organization to refer, and
subscribe, to the RSS feeds for Safety and Security, as well as the latest articles on the
web site.
7
Chapter 1: Introduction
8
Chapter 2: Upgrading
This chapter describes upgrading the product, and new features introduced in
CitectSCADA 2015.
Refer to the CitectSCADA User Guide for upgrade information for versions 7.0 to 2015.
Note: Cross version compatibility is not available for alarms version 7.20 onwards.
When updating the machine with a new product version, backup the existing projects
and uninstall the existing installation. Install the new version and restore projects into
the new version.
Note: The new version you are installing may have a service pack released. The
service pack may have a fix for the automatic upgrade and may be required to be
installed before restoring the project. Please refer to the service pack documentation.
Example installation/upgrade scenario

The example below is a generic overview of upgrading CitectSCADA across multiple
computers, in this instance a redundant system containing a pair of servers and several
clients.
Online Upgrade (Redundant system)
1. Backup existing projects and data.
2. On a non production machine perform the configuration project upgrade.
3. Shutdown project and remove the existing version of the product from first server.
4. Install new version of product and all recommended service packs.
5. Restore the upgraded project on the first server.
6. Restore the upgraded project on the clients you have chosen in step 5
Note: Once the new server(s) are online, a selection of clients can be updated. It is
recommended to leave a set of clients running the previous version in case there is a
need to return the system to the previous version during the migration process.
7. The second server in the redundant pair may now be upgraded. Uninstall the
existing version of the product.
8. Install new version of product and all recommended service packs.
9
9. Restore the upgraded project on the second server.

10. Refer to migrating to production in CitectSCADA User Guide for more information.
New Features
CitectSCADA 2015 includes the following new features or changes in functionality. In
many cases these new features will not impact the installation or initial configuration.
However, some of them may impact your project configuration and functionality. Once
you have installed this version, refer to the online help for information on how to
reconfigure your projects to take advantage of the new features and improved
functionality.
Introduced in 2015
The following list of new features introduced in this release is only a brief description.
For more details, and links to using the features in your projects, refer to the "What's
New in CitectSCADA 2015" page in the main CitectSCADA help.
Backup and Restore Included Projects
CitectSCADA 2015 now allows you to add a project's included projects to a backup file.
When you restore the project, you have the option to select which of its included projects
you would also like to restore.
These changes coincide with some improvements to the Restore Project tool, including
the addition of an Original product version field that indicates which version of
CitectSCADA was used to create the selected backup file.
Incremental Equipment Update
CitectSCADA 2015 now supports an incremental equipment update. When enabled, an

equipment update will only generate tags for equipment and equipment types that have
been modified since the last update occurred.
Incremental updates are enabled by default. You can disable this feature by deselecting
the Incremental Equipment Update check box on the Project Editor Options dialog (see
Setting the Project Editor options in CitectSCADA User Guide for more information).
Link a Genie to an Equipment Type
10
CitectSCADA 2015 now allows you to link a genie to an equipment type in the
Equipment Editor. This simplifies the process of deploying multiple equipment instances
on a project's graphics pages, as each time you place the genie on a page its equipment
associations will be preconfigured.
Partial Associations can be used with Dynamic Associations
In CitectSCADA 2015, Dynamic Associations (Super Genie Substitutions) can now use a
full or partial; variable tag, equipment name, and or equipment.item references.
Introducing partial association support means:
l Less or no code when using Dynamic Associations (see Configuring a Super Genie
Page for more Information)
l Context of the dynamic association (Super Genie substitution) is maintained directly
within the graphics page
l Easy to Maintain
Running as a Windows Service
CitectSCADA 2015 can be run as a Windows™ service, allowing for unattended

operation of a system's servers.
To run CitectSCADA as a service, you need to configure the service named "Citect
Runtime Manager" in Microsoft™ Management Console on each server computer. For
more information, see Configure a System to Run as a Windows Service.
Extended Memory Mode
In CitectSCADA 2015, you can configure an alarm server to operate in Extended

Memory mode. This allows the alarm server process to utilize memory beyond a 4GB
limit. It does this by running the process in 64 bit.
Extended Memory mode enables efficient query handling under the following
circumstances:
l On systems with a large archive of historical alarm data
l On high-capacity systems that can generate a large number of alarms.
OPC Factory Server Version Update
The installer for CitectSCADA 2015 now allows you to install version 3.50 of Schneider
Electric's OPC Factory Server (OFS). This resolves a possible security vulnerability that
was associated with OFS v3.40 (see OPC Factory Server (OFS) Security Updates for more
information).
You can select to install OPC Factory Server v3.50 from the launch page of the installer.
11
Upgrading a Runtime-only Installation

You can upgrade a runtime-only installation of CitectSCADA to a complete installation
that incorporates the configuration environment by simply running the installer again
and selecting the All Core Components option from the Installation Profiles page.
However, if a project has been restored and operated under the runtime-only
environment, it will not automatically appear in Citect Explorer following the upgrade to
a complete installation.
If you would like to add a missing project to Citect Explorer, you can use the Add
Project Link feature, accessible via the File menu. You can select the project from the
Add Project Directory dialog when it appears.
12
Chapter 3: Installation Description
Before you begin the installation of CitectSCADA, you need to first decide which
components you want to install. This is determined by the functionality you want the
installation to support.
After you have decided on the CitectSCADA environment, and any additional stand
alone components that you want to install, refer to Chapter 4 "Installation
Requirements" so that your hardware and system software meet the requirements for
your selected installation.
Once you have progressed through the preliminary dialogs of the installation interface,
you will be requested to begin selecting the components that you want to install. The
options that the installation interface will present to you are described below.
Task Selection Dialogs
Installation Profiles
The installer provides a set of profiles to help you select the appropriate components for
installation. Depending on the profile that you choose, the next dialog will have default
selections recommended for installation. You may accept the default components, or
select the ones of your choice on the components selection screen which is displayed
after you click Next on the Installation Profiles dialog.
The options are:
l All Core Components
l Runtime Only Server
l Runtime Only Client
l Custom
The All Core Components option will select the .Net Framework 4 (if not installed),
Configuration Environment, Runtime, Drivers and Sentinel Driver for installation. It is a
“Complete” installation which will install a fully functional CitectSCADA development
and server/client system. Such an installation will include the CitectSCADA
development environment, runtime infrastructure files, Client, I/O Server, Alarm Server,
Trend Server and Reports Server. Select this option if this is an initial installation of
13
CitectSCADA which will run as a single system, or act as a server to service a number of
client installations.
If the .NET Framework 4.5.1 installation does not complete, you can install it manually
from the installation file in the Extras folder of the CitectSCADA installation disk, then
install CitectSCADA. Note that .NET Framework 4.5.1 requires Windows Imaging
Component (available on the Windows Download Center web site) to be installed first.
The Runtime Only Server option will select Runtime, Sentinel Driver and
Communications Drivers for installation. It is an installation which will install the
runtime components for both a Server and Client. Such an installation will include
runtime infrastructure files, Client and I/O Server, Alarm Server, Trend Server and
Reports Server.
Select this option if this is an installation of CitectSCADA which will act as a server to
service a number of client installations.
The Runtime Only Client option will only select the Runtime system for installation. It
is an installation which will install the runtime components and a Client. Such an
installation will include runtime infrastructure files, but will exclude drivers.
Select this option if this is an installation of CitectSCADA which will be used as a client.
If you wish to upgrade either of the Runtime installations to a full installation, including
the Development and Configuration environment, insert the original installation media
and select "All Core Components" or "Custom" from the Installation Profiles dialog.
Note:You can also install the CitectSCADA Runtime Only Client from a single
installation file. This file is named CitectSCADA 7.50.exe and located in the
<discmedia>\CitectSCADA 7.50\Extras\Runtime Installer folder of the installation
DVD. This allows installation of the software to computers which only require the
runtime. The file can be copied to a network location for remote installation
The single-file installation does not include Communication Drivers, the Sentinel Driver,
or the Microsoft® .NET Framework which is a prerequisite of the runtime. If the .NET
Framework is not already installed on the target computer, you cannot use the single-file
installation. In this case, you may use the full package installer to automatically install
the .NET Framework during the installation of CitectSCADA. Alternatively you can
install .NET Framework from another source, then carry out the single file runtime
installation.
The Custom option will not select any components for installation; it will allow you to
select the core components that you specifically need, or allow you to install Add-ons or
documentation only.
14
Documentation Installation
The Product Documentation option will install a comprehensive library of user guides
and references in Adobe Portable Document Format (PDF). These can be accessed from a
master contents HTML page.
It is highly recommended that you install the product documentation for future
reference.
Add-ons Installation
Once you have selected the components that you want to install, the next dialog allows
you to select any Add-ons that you wish to use in your installed system..
The options are:
l Project DBF Add-in for Excel™
l Web Server for IIS
The Project DBF Add-in for Excel option will install an Add-In for Microsoft™ Excel.
When this Add-In is loaded into Excel, it allows you to browse, open, edit and save
CitectSCADA .dbf files in the correct format. This is only available for selection if
Microsoft Excel 2007 or above is installed on the computer. Otherwise, it is visible but is
deselected and disabled.
The Web Server option will install a Web Server running on Microsoft Internet
Information Service (IIS). The Web Server performs the server-side functionality of a Web
Service to the Web Client. As well as facilitating communication, it directs a client to the
graphical and functional content of a CitectSCADA project and the location of the
runtime servers. This information is stored on the Web Server when a CitectSCADA
project is deployed. A Web Server can contain multiple deployments.
Note: If the Web Server and CitectSCADA runtime server are set up on different
machines, and it is not possible to establish a trust relationship between them, the
two machines need to be on the same domain so that the Web server can access the
directory on the CitectSCADA server that's hosting the web deployment files. If,
conversely, a trust relationship can be established between the Web Server and the
CitectSCADA server, they can be on different domains as long as the Web server has
read access to the project folder on the CitectSCADA server.
15
Communication Drivers
CitectSCADA communicates with control or monitoring I/O Devices that have a
communication port or data highway - including PLCs (Programmable Logic
Controllers), loop controllers, bar code readers, scientific analyzers, remote terminal units
(RTUs), and distributed control systems (DCS). This communication takes place with
each device through the implementation of a communications driver. It is important that
these drivers are the latest version.
The installation of CitectSCADA prior to v7.10 installed all the available communication
drivers automatically with the installation of the product. From v7.10 the installation of
these drivers is performed at the final stage of the product installation using a separate
installation process. This installation process allows you to select individual drivers that
you want to install, specific to your system and its I/O devices. There are certain drivers
that the product installation will install that are necessary for CitectSCADA to function
correctly. These will be installed automatically as in previous releases.
Only install drivers which are identified as being compatible with the computers
operating system. If you select any driver that is not yet identified as being compatible,
or is specifically identified as not compatible, the installation process will provide an
alert to that effect, and will allow you to deselect the driver prior to continuing with the
installation.
INCOMPATIBLE DRIVERS
Do not ignore alerts during driver installation. If you choose to ignore such alerts, the
driver will be installed but may operate incorrectly.
Failure to follow these instructions can result in death, serious injury, or

equipment damage.
The communication driver installation can also be invoked individually at any time
after the product installation to install additional drivers.
16
Chapter 4: Installation Requirements
This chapter describes the requirements for hardware, operating system software and
system configuration prior to installing CitectSCADA and any of its components.
These requirements will vary subject to the components of CitectSCADA that you intend
to install on any computer. Refer to chapter 3"Installation Description" to determine the
components that you want to install. This chapter identifies the basic hardware and
system software requirements, as well as requirements specific to each particular
component.
Before you begin to install CitectSCADA it is important that you install the latest updates
from Microsoft® for your operating system and system software.
All Core Components
System Hardware
NOTICE
The minimum and recommended hardware requirements have changed in this release.
Upgrading customers should load test their system as part of their upgrade procedure to
ensure that the hardware in use is adequate for the needs of their system.
The following tables indicate the computer hardware requirements for the CitectSCADA
“All Core Components” installation and all optional components.
Description Minimum Specification
Processor Speed 2 cores @ 1.8 GHz for a server

or
2 cores @ 2 Ghz for a client
Random Access Memory 2GB if SCADA client

(RAM)
or
4GB if SCADA server
Network 100Mbps
17
Description Minimum Specification
Available Disk Space 10GB
Graphics Adapter (see

With 64MB of VRAM
note below)
Description Recommended Specification or Higher
Processor Speed 4 cores @ 2 GHz for a server
Random Access memory 8GB

(RAM)
Available Disk Space 100GB
Network 1Gbps
Graphics Adapter (see

With 128 MB of VRAM
note below)
Note:In CitectSCADA it is recommended that screen resolution be set at 1024 by 768

pixels or higher.
Note: In CitectSCADA you need to increase system resources (both memory and
number of available cores) in the following circumstances:
•When running a large number of tags on a server (> 100,000)
•When running multiple clusters on the same machine
•Your system has a high rate of change of data (either IO or alarms)
•Your graphics pages contain a large number of alarm count calls (more than 500
per page).
System Software
The following table indicates the system software that is needed on any computer onto
which you want to install the CitectSCADA All Core Components installation and all
optional components.
CitectSCADA
Minimum System Software
Component
All Core Components Operating System
18
CitectSCADA
Minimum System Software
Component
Windows 8 or
Windows Server 2012
Windows 7 with Service Pack 1(32 Bit and 64 Bit)or

Windows Server 2008 R2 with Service Pack 1 (32 Bit and 64
Bit)
Microsoft .NET Framework 4.5.1 (installed with CitectSCADA if

not already installed).
Microsoft .NET Framework 2.0 (x64) is required by "Schneider

Electric License Manager" and "Schneider Electric Software
Update" if using Windows Server 2012.
Internet Explorer Version 9.0 or greater.
A Local Area Network (LAN) if you want to have multiple clients

access a remote server.
If running under virtualization with VMWare, the minimum

system requirement is VMWorkstation 6.03 and later.
Virtualization Host The following virtualization environments are supported:

Support
l Microsoft Hyper-V: based on the version of Windows
l VMware 5.0: basic virtualization without High Availability
and Disaster Recovery
l VMware Workstation
For further information on virtualization, please refer to the
online Knowledge Base (http://www.citect.schneider-
electric.com/scada/citectscada/find-answers/knowledge-
base).
CitectSCADA As for CitectSCADA all Core Components with the addition of:
WebServer
A LAN running TCP/IP
and
Microsoft Internet Information Services (IIS) See Microsoft IIS

Compatibility for information.
Product As for All Core Components.

Documentation
Project DBF Add-in for As for All Core Components, and Microsoft Excel 2007or later.
Excel Microsoft Excel 2013 (32 bit only)
19
Note: Use an NTFS file system on the target drive for the Web Server software,
otherwise you won't have effective access to the necessary Windows security settings
(that is, the Folder Properties dialog will not have a Security tab). If you are currently
using a FAT/FAT32 system, convert the drive to NTFS before installing the Web
Server software.
Microsoft IIS Compatibility

For correct operation of the WebServer, install the appropriate Microsoft Internet
Information Services (IIS) feature for your operating system:
Operating System IIS version
Windows 8.1 8.5
Windows Server 2012 R2 8.5
Windows 8 8.0
Windows Server 2012 8.0
Windows 7 7.5
Windows Server 2008 R2 7.5
Windows Server 2008 7.0
Components recommended for Web Server Installation
Management Tools IIS Management

Console
IIS6 Management
Compatibility
IIS6 Metabase and
IIS6 Configuration
compatibility
IIS Management
Services
Application Development Features ASP

ISAPI Extensions
Request filtering
Security Windows
Authentication
20
Runtime Only Server or Client System Software

An installation of a CitectSCADA Runtime Only Server or Client has the same hardware
and system software requirements as the Core.
Software Protection
CitectSCADA supports two different software licensing models to help maintain license
conformance:
l a Sentinel Licensing solution using a SafeNet hardware dongle (the legacy methods
used by the product)
l a FLEXERA softkey solution using a license locked to PC attributes (see FlexNet
License Server in the main help for more information).
In both cases the hardware dongle is a physical key that plugs into either the parallel
port or USB port of your computer, and contains details of your user license, such as
type and I/O point count.
You may choose to use either the SafeNet licensing method, or the new FLEXERA
method
Both the existing SafeNet licensing method and the new FLEXERA method now contain
the following features:
l Separate licensing for drivers used for importing tags, such as SpeedLink and
FasLinx is no longer required.
l There is no longer a distinction between Control Client or View-Only Client and their
web counterparts Internet Control Client or Internet View-Only Client.
For further information on the new licensing method, refer to Independent Point Count.
See Also
CiUSAFE dialog properties
Demo mode
Dynamic-point count licensing
21
Software Licensing
CitectSCADA uses a hardware key to help manage the software licensing. The hardware
key is a physical key that plugs into either the parallel port or USB port of your
computer. The hardware key contains details of your user license, such as type and I/O
point limit. There is also the new licensing mechanism introduce with 7.30. Refer to
"New Licensing Method" in the section Introduced in 7.30.
Updating Your Hardware Key

When you upgrade to a new version of CitectSCADA, you might need to update your
hardware key to enable the system to run. See the CitectSCADA Readme file to confirm
whether you need to perform an update.
Updating the hardware key involves running the CitectSCADA Key Update command,
which is found in the Help menu of Citect Explorer.
Note: If you have CitectSCADA 5.21 or 5.20, run ciusafe.exe from the Citect bin
directory. You can also download the latest version of the upgrade program from the
AuthCode Generator section of the CitectSCADA website at
http://www.citect.schneider-electric.com/.
To update the hardware key:
1. In Citect Explorer choose Help | Sentinel Key Update. A Key ID is displayed. The
hardware key's serial number might also appear. If not, read the serial number from
the label on the key.
2. Visit http://www.citect.schneider-electric.com/authcode/ and enter the serial number
as prompted. You might also be asked for the Key ID and your web login name and
password.
3. The authorization code is displayed. Type the code (or copy and paste it from the
web site) into the Authorization Code field in CiUSAFE. Do not use any spaces when
entering the characters.
4. Click Update.
The Return Code field indicates whether the hardware key was updated successfully.For
a detailed explanation of the fields in the CiUSAFE dialog, click the Help button on the
dialog.
22
Note: Each time you run the Sentinel Key Update, a different Key ID is generated
which is normal. However, if you obtain an authorization code but do not
immediately update the hardware key, you can enter the same authorization code
the next time you run the update.
Floating Point License Manager

Floating licensing benefits both users and license administrators. Users make more
efficient use of fewer licenses by sharing them on the network.
The Floating Point License Manager is used to list available floating licenses which have
been provided by the FLEXNET license server. The details are displayed of each license,
such as product name, version, part number, point count, and license expiration.
From the list of available license you can activate any that you wish to use on you
system.
There are several other activities that you can undertake within the Floating Point
License Manager interface. The interface has its own dedicated on line help which you
can display from the Help item on the interface menu.
See Also
Software Protection
FlexNet license server

The FlexNet license Server allows software licenses to be available (or float) anywhere on
a network, instead of being tied to specific machines. License administrators control who
uses the licensed applications and the machines where the licenses are available. The
licensed software is then managed by the Floating Point License Manager for a floating
license, and the License manager for a node-locked license..
The FlexNet license server consists of four required components:
l The FlexEnabled application, with the FlexNet Publisher static client library linked
into it.
23
l The license server manager, which handles the initial contact with the licensed
applications, passing the connection on to the appropriate vendor daemon. It also
starts and restarts the vendor daemons.
l A vendor daemon, one process for each vendor who has a licensed product on the
network. The vendor daemons keep track of how many licenses are checked out, and
who has them. Licensed applications communicate with the vendor daemons
through TCP/IP network communications.
l A source for license rights, a license file installed by the license administrator. This
source contains information about the server machines and vendor daemons and has
at least one entry for each licensed product, specifying that product’s license details.
See Also
Software Protection
Independent Point Count

On a given SCADA machine a local client acts as a license server. Upon reading its
[Client]ComputerRole INI parameter, it knows what type of license it is entitled to.
A remote client, needing a license, obtains its point count via TRAN subsystem from the
display client, residing on the machine that has access to the licensing information. The
count that it receives depends on its licensing entitlements (Computer Role).
A client can specify what point count it requires by [Client]PointCountRequired INI
parameter. If this parameter is not specified, the client will get the first available
matching point count. If the parameter is specified, but the required point count is not
found within the license, no point count (no license) is served to that client.
For example. if a license has
l 2 Full License entitlements with 10000 points and 20000 points.
l 2 View-Only License entitlements with 500 points each.
1. A local client specifies [Client]PointCountRequired=30000. When it starts, it gets shut
down with invalid point count message (because the license has no Full License
entitlement with 30000 points).
2. A local client specifies no [Client]PointCountRequired. When it starts, it gets 10000
point count.
3. A local client specifies [Client]PointCountRequired=20000. When it starts, it gets
20000 point count.
24
A remote client connects to it, requesting Full License with 40000 points. It gets no
license, since such a license is not available.
Another remote client connects to it, requesting Full License with 20000 points. It
gets no license, since such a license is not available (it is used by the local client).
Another remote client connects to it, requesting Full License with 10000 points or
with no point count specified (i.e. that remote client has no [Client]
PointCountRequired in its INI file). It gets served the second available Full license.
Another remote client connects to it, requesting View-Only License with no point
count specified. It gets served one of the View-Only licenses with 500 points.
When any of the remote clients disconnect, the corresponding licenses served to them
earlier are reclaimed.
With the Sentinel licensing, each license has the same point count and a Sentinel key
will map to the new licensing as shown below.
Sentinel key with point count of 5000 New license model
run time users – 1 key 1 Full License – 5000 points
control clients – 3 key 3 Control Client License – 5000 points each
view only users – 2 key 2 View-Only Client License – 5000 points each
Point count special rule
A display client running in Full License mode (Client+Server or Control Client with Full
License) has a special rule for point count limits; if its full license entitlement is >= 500,
its client point count component is treated as unlimited.
Taking this special rule into account, the following describes the licensing scenario:
Assume a client with a dongle attached (acting as a local licensing server), the runtime
point count is calculated on the basis of:
l Server component (consolidated point count from Alarm, Report, & Trend servers)
l Client component (consolidated point count from OPC Server, CtAPI, and page
displays, i.e. subscriptions)
Normally the overall runtime point count is calculated by taking the maximum of the
above two components; client and server. However, if the client is fully-licensed and the
point limit specified on the license is greater than 500 points, when calculating the
overall runtime point count, the client component is disregarded and only the server
component is considered.
For Example:
l Alarm, Report, and Trend servers report 100 points (server component)
l CtAPI, OPC Server, and display pages use 200 points (client component)
25
l If the license entitlement is 499 points, the overall point count reported is 200 points
(maximum between 100 & 200)
l If the licenseentitlement is 500 points, the overall point count reported is 100 points
(since client component is disregarded)
See Also
Demo mode
CitectSCADA License Point Count

The point limit is the maximum number of I/O device addresses (variable tags) that can
be read, and is specified by your CitectSCADA license. CitectSCADA counts all I/O
device addresses dynamically at runtime.
This includes all tags used by alarms, trends, reports, events, pages, in Super Genies, use
of the TagRead() and TagWrite() Cicode functions, or internal values written using DDE,
ODBC, or the CTAPI.
It does not count any points statically at compile time.
l Dynamic points are counted only once, regardless of how many times they are used.
l At runtime, the dynamic point counts are available through the Kernel and the
CitectInfo() Cicode function.
l Existing MEMORY_PLC tags from before v7.0 are converted to the new "local
variables" during migration. Local variables are stored on the client and resolved on
the client and they are not included in the point count.
l When you plan your system be aware of your point count so that you do not exceed
your point limit. This is particularly important, as at runtime, you can incrementally
add to your point count by using tags that have not yet been included in the total
count.
When you run CitectSCADA at runtime, the dynamic point count is continuously
checked against your hardware key. When the total number of dynamic points (at
runtime) pushes the total point count above the point license limit, CitectSCADA will
refuse to get values for the additional points.
CitectSCADA has two preconfigured 'watermark' messages that will display to the user
when the dynamic point count reaches 95% and 98% of their point license limit. You
can configure these percentages in the Citect.ini file.
26

The CiUSAFE dialog box has the following properties:
Serial Number
The serial number of the computer's hardware key. It will only appear if the key was
delivered after September 11 2000, or has been updated since this time. If this is not the
case, you can read the number from the label on the hardware key. You need to enter the
serial number at the Schneider Electric (Australia) Pty. Ltd. web site to update the key.
KeyID
Each time you launch CiUSAFE, a Key ID will display in the KEYID field. You might
need to provide the Key ID plus the serial number when updating the hardware key.
This depends on the status of the key in the CitectSCADA license database, and you are
prompted if the Key ID is required. Click Save KeyID to save the Key ID and serial
number to a text file, which you can refer to when visiting the Schneider Electric
(Australia) Pty. Ltd. web site.
Authorization Code
To update the hardware key, enter the 106-character authorization code. You are asked
for this code once you have entered the Key ID and serial number, and your license and
Customer Service agreement have been verified. Click Update to update your hardware
key.
Return Code
The Return Code indicates the result of the key update:
0 The key was updated successfully.
1,3 Either the KeyID or the Authorization code you entered is invalid.
2 Either the KeyID or the Authorization code you entered has been corrupted.
Either the KeyID or the Authorization code you entered is invalid.

4,-
16
9 No hardware key could be found.
To close the program, click Exit.
27
Demo Mode
You can run CitectSCADA without the hardware key in demonstration (Demo) mode.
Demonstration mode lets you use all CitectSCADA features normally, but with restricted
runtime and I/O.
The following demonstration modes are available:
l 15 minutes with a maximum of 50,000 real I/O.
l 10 hours with a maximum of 1 dynamic real I/O. This is useful for demonstrations
using memory and disk I/O. CitectSCADA starts in this mode if no hardware key is
available. If the system detects that you are using more than 1 real I/O point at
runtime then it will swap to the 15 minutes demo mode.
Note: Writing to any tag through DDE, CTAPI, or ODBC will cause that tag to
contribute to the dynamic point count even if it is a memory or disk I/O point. So if
you write to more than 1 point through these interfaces it will swap to the 15 minute
demo mode.
l 8 hours with a maximum of 42,000 real I/O. This is only available through special
CitectSCADA Integration Partners (CIP) keys.
28

In CitectSCADA 6.10 or earlier, multiple tags that share the same I/O device address will
be counted as a single I/O point. This is calculated at compilation time and the compiler
will report the number I/O points used in a project and is referred to as the Static Point
Count. Any other tags used in super genies, read/written to via CTAPI, ODBC, DDE,
TagRead() and TagWrite() are counted at runtime and are referred to the Dynamic Point
Count. Thus, the total I/O point count will be equal to Dynamic Count plus Static Count,
which is calculated at runtime.
However, from CitectSCADA 7.0 the compiler does not generate any static point count
any more. CitectSCADA counts I/O device addresses dynamically at runtime. This
includes tags used by alarms, trends, reports, events, pages, in Super Genies, use of the
TagRead() and TagWrite() Cicode functions, or read or written to using DDE, ODBC, or
the CTAPI. A particular variable tag is only counted towards your point count the first
time it is requested. That is, even though you may have configured a certain tag on a
particular page in your project, unless you navigate to that page and request the data,
the variable tag will not be counted towards your point count.
In addition to this, there have been a number of other changes that have been made to
the licensing structure from CitectSCADA 7.0. These are listed below:
l I/O point count is now tag based not address based. For example, two tags that use
the same PLC address will be counted twice. If two trend tags use the same variable
tag, it will be counted once. The same applies to alarms.
l For the multi-process mode, each server component will accumulate its own point
count. The server component point count is the count added up from each server
component - if two server components use the same tags, say alarm and trend, the
tags will not be counted twice when the point count gets totaled, each unique point is
counted once only.
l For the multi-process mode, the client component will also accumulate its own point
count including super genie and CTAPI tags.
l For the multi-process mode, the machine point count will be the point count on the
client component or the point count added up from each server component,
whichever is bigger. For example, if the total point count for each server component
is 100, and the client component point count including CTAPI and super genies is 95,
the kernel "General" window will show 100. If the client component point count
reaches 120 later and the server component point count still remains 100, the kernel
"General" window will show 120. In CitectSCADA 7.30 a special case has been
29
introduced; if the server point count is greater than 500, the client component point
count is disregarded
l Reading properties of a tag with TagGetProperty() will cause that tag to be included
in the point count, even if the value is not read.
l Writing to local variables or disk IO variable tags via OPC etc will also increase the
point count. For example, if you use an OPC client to write to a local variable, each
local variable will be counted once, the first time it is used.
With the release of 7.30 further changes to licensing point count have been included,
with the introduction of the “One License” product licensing method.
These are listed below:
l If a given tag is used by both, say, trend and alarm servers each server reports actual
tags used (Cluster.TagName), so the same tag is not counted twice.
l A new INI parameter has been added to control IP addresses aging. It is used to
indicate how long to reserve a license for a given IP address in cases when a remote
client connection is lost. This does not apply to FULL licenses. The parameter is
[General]LicenseReservationTimeout.
l In previous versions there was a single point count within the licensing model, now
there are multiple point counts as a pair of values: License Type – Point Limit.
See Also
Software Protection
Demo mode
30
Chapter 5: Installation
The Installation Process
Note: Backup your existing projects then uninstall prior versions before installing
2015, as CitectSCADA does not support different versions running side-by-side.
Note: Remove existing Floating License Managers installations before installing the
new version.
Preliminary Installation
Do not have Windows Update running when attempting to install CitectSCADA.
When you begin the installation any additional system software that is necessary will be
installed prior to the initial CitectSCADA Setup dialog being displayed..
1. To begin the installation, place the CitectSCADA DVD in the DVD drive of your
computer. If you have autorun enabled the initial CitectSCADA Setup dialog will
display. If this does not occur, use Windows Explorer to navigate to the root directory
of the DVD and click Launch.exe to display the initial CitectSCADA Setup dialog.
31
When the CitectSCADA Setup dialog is displayed choose which application you
wish to install.
NOTICE
You must install CitectSCADA before you install the OPC Factory Server to have the OFS
Server licensed using the CitectSCADA license key. This will allow the correct Part and
Serial number combination to be registered during the OFS Server installation.
The OPC Factory Server, based on the OPC protocol, software enables Windows
client applications to communicate with PLCs of the TSX Compact, micro, TSX
Momentum, TSX/PCX Premium, Quantum, M340, TSX Series 7 and TSX S1000
families in order to supply the OPC clients with data.
If you choose the OPC Factory Server follow the on screen instruction. Complete
details on the installation options for OPC Factory Server can be found in the OPC
Factory Server User Manual located in OFS v3.35\Documentation on the
installation DVD.
If you choose the CitectSCADA installation, click Next to display the Welcome to
CitectSCADA dialog.
2. When this dialog is displayed, click Next to begin the installation process and
display the Welcome to CitectSCADA dialog.
32
3. Click Next to display the Installation Documentation dialog. This allows you to read
the Installation Guide (this document), the readme file and Release Notes prior to
continuing the installation. It is recommended that you read them.
33
4. Click Next to display the License Agreement dialog. Read the license agreement, and
if you accept the terms of the agreement, select the appropriate radio button, then
click Next to display the Installation Profiles dialog.
Installation Profiles
1. In the Installation Profiles dialog select the profile that represents the type of
installation that you require. For information on the profiles and their application
components refer to Chapter 3, "Installation Description".
34
2. Click Next to display the subsequent dialog in the installation sequence. The optional
components selected by default in the subsequent dialog will vary subject to the
option that you select in this Installation Profiles dialog.
As an example, if you selected the All Core Components option in the previous step,
when you click Next the Core Components dialog will be displayed and will have all
the components selected by default. If you had selected another profile in the previous
step, only some of the components will be selected.
35
This dialog allows you to change the selected components if you wish to have a different
installation configuration from the default provided by the profile which you chose in
the previous step. Microsoft® .Net Framework is needed. If this component option is
disabled then it is already installed on your system. If it is enabled, select it to continue
the installation.
Note: The Sentinal Driver is not necessary on a client that gets a floating license from
a server. However if you upgrade from a Runtime installation to a Configuration
and Development Environment you need to select the Sentinel Driver so that the
hardware protection key will be recognized.
Note: Remove existing Floating License Managers installations before installing the
new version.
3. When you are satisfied with the components that are selected click Next to display
the Documentation dialog
36
The Documentation dialog allows you to install the Product Documentation.

4. When you have made your selection, click Next to display the Add-on selection
dialog.
37
The Add-on dialog allows you to select specific additional components for your
installation.
The options are:
l Project DBF Add-in for Excel™ (Only selectable if Microsoft Excel 2007 or later is
installed on the computer.)
l Web Server for IIS
Refer to Chapter 3, "Installation Description", for a description of these optional Add-on
components.
The Web Server on IIS (Internet Information Services) option will use IIS as a platform
for your server.
If you proceed with the Web Server for IIS installation, the installer automatically
determines if IIS is installed. An error message is displayed if IIS is not installed.
Install IIS before you continue with the Web Server for IIS installation.
5. Proceed to Completing the Installation.
Completing the Installation
1. The Destination Folder dialog identifies the folders into which the CitectSCADA
program files you have selected will be installed.
38
You may change the folder locations by clicking the Change buttons and selecting
alternative locations.
2. When you are satisfied with the folder selections, click Next to display the Base
folder dialog.
39
The Base Folder dialog identifies the base folder into which the additional or optional
components of CitectSCADA that you have selected will be installed. You may change
the folder location by clicking the Change buttons and selecting an alternative location.
If you are satisfied with the folder selection, click Next to display the Ready to Install
the Program dialog.
The Ready to Install the Program dialog lists the CitectSCADA programs that will be
installed.
40
3. Review the list and if you wish to change the selections click the Back button
through the previous dialog until you reach the selection that you want to change.
Click Install to install the programs in the list and display the Installing
CitectSCADA dialog.
4. The Installing CitectSCADA dialog displays a progress bar and identifies the status
of the installation. You can click Cancel if you want to terminate the installation.
During the course of the final installation you may be asked to confirm certain actions,
depending on the additional components that you have selected to install. In such cases
follow the prompts on the dialogs.
Communication Drivers
If CitectSCADA Drivers was selected, the communication driver installation will
commence towards the end of the main product installation.
You can also run the communications driver separately at a later time from the user
interface or the command line if you want to install additional drivers. For details see
Installing Additional Communication Drivers.
Installation of the drivers commences with the drivers being extracted to a temporary
folder. The Driver Selection dialog will then be displayed. .
41
The Driver Selection dialog lists all the drivers that are available for installation. There
are certain drivers that the product installation will install that are necessary for
CitectSCADA to function correctly. These are not displayed in the list and will be
installed automatically as in previous releases. For convenience, the most commonly
used drivers are selected by default. In addition it will advise you of any drivers that are
time limited or not supported by your operating system. If you see that any of the drivers
in the list are subject to limitations, click the Back button and deselect them from the
previous dialog.
Select the check box against the drivers that you wish to install, or deselect any that you
do not wish to install. You may select all the drivers by clicking the Select All
button.Then click the Next button to display the Driver Information dialog.
42
The Driver Information dialog displays a confirmation list of the drivers that will be
installed.
In addition it will advise you of any drivers that are time limited or not supported by
your operating system. In particular, some drivers may have not yet been confirmed to
operate correctly, or have been confirmed specifically to not operate correctly with
Microsoft® Windows Vista™ or Windows 7. If you see that any of the drivers in the list
are subject to limitations, click the Back button and deselect them from the previous
dialog, then click Next to return to the Driver Information dialog. When you are
satisfied that the correct drivers will be installed click the Next button to install the
selected drivers.
When the driver installation is finished, any Add Ons that you selected to install earlier
will be installed, followed by the main product installation Setup Completed dialog.
This lists a summary of the programs that have been installed. If you wish to be
connected to the Citect on line registration web site select the check box. Click Finish to
close the installation dialog.
43
Installing Additional Communication Drivers

You can install additional communications drivers at any time after you have installed
the main CitectSCADA product.
To install additional drivers:
1. From the Installation DVD locate the CitectDriverInstaller.exe file located in the root
directory.
Note: If you are using the Microsoft® Windows Vista™ or Windows 7 operating
system and have User Account Control (UAC) switched on the UAC dialog will
display when you open the file. You will be required to supply administrator
credentials if you are not an administrator of the computer.
2. Open the file to display the Welcome dialog and follow the steps above in
Communication Drivers noting the following additional step.
3. After you have accepted the license agreement an additional Choose Destination
dialog will display. This will identify the default folder in which to install the
drivers. You can accept the default location or change to another folder using the
Browse button. The installation folder has to contain the citect32.exe file otherwise an
44
alert message will be generated. In other words the location needs to have an existing
CitectSCADA product installed in that location.
4. Click the Next button to display the Driver Selection dialog and continue with the
installation as described in Communication Drivers.
Installing Service Packs

Schneider Electric (Australia) Pty. Ltd. distributes upgrades for current versions of
CitectSCADA via Service Packs. A Service Pack is a minor version upgrade of
CitectSCADA executable and/or database files. These files are upgraded to provide bug
fixes and necessary enhancements. Enhancements are included only when they will aid
in more enhanced debugging of CitectSCADA Runtime.
When to install a Service Pack
A Release Notes document is distributed when Technical Support for this product
release a Service Pack. Read the Release Notes and see if it states that a problem you are
experiencing has been fixed. If so, then apply the Service Pack. However, do not be apply
Service Packs on the premise that they will fix a problem not stated in the readme.
Service Packs include the fixes or enhancements of all previous Service Packs. So, if you
are running a released version, and you install Service Pack 3, for instance, you get all
fixes and enhancements for Service Pack 1 and Service Pack 2. The Release Notes
document for each Service Pack also identifies the fixes or enhancements of the previous
Service Packs.
How to install a Service Pack:
1. Download the necessary Service Pack, and the associated Release Notes document
from http://www.citect.schneider-electric.com/scada/citectscada/downloads-
updates/service-packs
2. Close all CitectSCADA applications. Ideally, close all Windows applications.
3. Follow the installation instructions in the Release Notes document specific to that
Service Pack, and to the CitectSCADA components that are installed on your
machine.
Modify, Repair, or Remove Components

You can modify, repair or remove installed CitectSCADA components by using the
Windows Add/Remove Programs (or "Programs and Features" icon in Microsoft Vista).
45
Note: The CitectSCADA 2015 installation can only be removed using this operation.
You cannot Modify or Repair this installation. In order to Modify or Repair this
installation you need to re-install it from the main CitectSCADA installation
interface.
To perform a Modify, Repair, or Remove follow these steps.
1. From the Start menu select Settings, Control Panel to display the Control Panel
window.
2. Select Add or Remove Programs to display the Add or Remove Programs dialog box.
3. Locate the CitectSCADA program on which you want to carry out the operation from
the list.
4. If the Change button is present, you can modify or repair the installation. If only the
Remove button is available you can only remove the installation, to do so click
Remove and follow the prompts on the dialog.
5. If you click the Change button, the CitectSCADA Installation Wizard will display.
Click Next to display the Program Maintenance dialog.
6. On the Program Maintenance dialog, click the radio button for the operation that you
wish to undertake and follow the prompts on the dialog.
Note: When uninstalling on a computer running the Microsoft Vista operating

system and you have User Access Control switched on, the UAC dialog will be
displayed before the uninstaller is launched. If prompted, select "Allow" and proceed
with uninstall. This is a limitation imposed by the User Access Control and cannot
be avoided.
The available maintenance operations are shown below.

l Modify allows you to add CitectSCADA components that were not installed during
the original installation, or remove selected components via the Custom Setup dialog.
If you select the Modify operation, when you click the Next button the Custom Setup
dialog will be displayed.
l Repair the existing CitectSCADAcomponent installation by reinstalling all non-
customizable files in the same location as the previous installation. If any of the files
were accidentally deleted or modified, then this option will restore the software back
to its original state.
l Remove CitectSCADA component files and remove all the registry entries. This will
restore the computer to the state prior to installation of the CitectSCADA component.
If you select the Remove operation, when you click the Next button a message box
will display requesting that you confirm or cancel the operation. If you confirm the
operation, the CitectSCADA component will be uninstalled.
46
Note: The uninstallation of CitectSCADA does not uninstall the Sentinel Protection
Software (used by the hardware protection key), Schneider Electric Licensing
software, Web Server, or the Project DB Add-in. To uninstall these applications use
the same procedure as for uninstalling CitectSCADA, but select the appropriate
installer from the list displayed in the Add or Remove Programs dialog, then follow
the on screen instructions.
Uninstall a Service Pack

When a Service Pack is installed, a backup directory is created. This backup directory
structure mirrors the CitectSCADA directory including all subdirectories. Files that were
replaced during the Service Pack installation will be backed up in these directories.
To uninstall a Service Pack:
1. Close all CitectSCADA for Windows applications. Ideally, close all Windows
applications.
2. Follow the un-installation instructions in the Release Notes document specific to that
Service Pack, and to the CitectSCADA components, that are installed on your
machine.
3. Recompile all your CitectSCADA projects.
After following this procedure, you will be running the CitectSCADA version and
Service Pack level you were running before installing the latest Service Pack.
47
48
Chapter 6: Configuration
In all but the smallest system, CitectSCADA will need to operate over a Local Area
Network (LAN) or a Wide Area Network (WAN).
You can use TCP/IP with CitectSCADA. CitectSCADA supports scalable architecture,
which lets you initially implement CitectSCADA on a single computer, or over a small
network, and then expand the system later without changing your existing hardware,
software, or system configuration.
Using CitectSCADA on a LAN adds more flexibility to the system, and coordination
within large plants can be more easily achieved. You can control and monitor
autonomous areas within the plant separately, and interrogate the whole plant using
any CitectSCADA computer on the network if you want.
In any of these scenarios there are basic configurations that you have to make for the
successful operation of your CitectSCADA system. The configuration steps are described
in this chapter.
Local Area Network Configuration

To set up a local area network (LAN) for CitectSCADA, you need to have successfully
installed network hardware and software in strict accordance with the instructions
provided by the manufacturer, and also be familiar with the basic operation of the
network.
Install the CitectSCADA software on every PC you want to use as a CitectSCADA
design-time development machine, CitectSCADA Runtime Only Client, CitectSCADA I/O
server, CitectSCADA Alarm, Report, or Trend server.
Also, set up CitectSCADA for your network, using the Computer Setup Wizard on every
one of the machines. To access the Computer Setup Wizard, Open Citect Explorer. In the
project list area, select My Projects and double-click the Computer Setup Wizard icon, or
choose Tools, Computer Setup.
Note: You need a compiled project to select in order to run the Computer Setup
Wizard.
For a detailed explanation on the Computer Setup Wizard, and its options refer to
“Running the Computer Setup Wizard” in the online help.
49
Network Communications Overview
Networking and Microsoft Windows 7
Microsoft Windows 7 distinguishes between Public, Home and Work networks. Each
network has its own firewall profile, which allows you to configure different firewall
rules depending on the security requirements of your location. The CitectSCADA
installers automatically modify the windows firewall settings for the current active
network profile during installation. If you later change network settings, you will need to
manually modify the firewall settings within Windows.
Note:CitectSCADA networking and redundancy needs the options "CitectSCADA

FTP server" and "CitectSCADA Runtime" to communicate through a Windows
firewall. You will need to manually add an application to the Windows 7 firewall
exception list for a particular network profile.
Using TCP/IP for network communications
CitectSCADA uses TCP/IP to facilitate communications across a network.

To set your system to TCP/IP-based communications, a number of parameters need to be
set in the citect.ini file. These parameters will be set automatically when you run the
Computer Setup Wizard and select TCP/IP, after you have completed the installation of
CitectSCADA. For details of these parameters, and others, refer to “Citect.ini File
Parameters” in the online help.
The Computer Setup Wizard will recognize the computers IP address and match it to the
IP address configured in the project for the various servers in the Networking Addresses
dialog under the Servers menu in the CitectSCADA Project Editor.
For example, if you had the following servers in your system:
Citect_IO_1
Citect_IO_2
Citect.PrimaryAlarm
Citect.StandbyAlarm
Citect.PrimaryTrend
Citect.StandbyTrend
Citect.PrimaryReport
Citect.StandbyReport
50
If the role you need for your PC is not available, you will also have to determine the IP
address and update the project accordingly. You can use the DOS command “ipconfig”
to obtain this information. Alternatively, you can change the PCs IP address to match
that defined in the project.
Configuring Communications Over a WAN

You can configure your system for use with wide area networks (WANs).
Using a Wide Area Network (WAN) is configured in much the same way as using a
LAN, with several additional considerations:
1. That the PCs on the WAN can see each other.
2. That appropriate security precautions (eg: VPN) are used when connecting networks
over a potentially public link (eg: the Internet).
3. Performance of the connections is appropriate to the data being transferred.
4. Reliability of the connection is appropriate to the requirement for access.
Web Server Configuration

To display a live CitectSCADA project in an Internet browser, you need to publish the
content of the project pages and the current data these pages present using standard,
Web-based communication protocols.
For the web server to function you need to create an exception in the Windows firewall
or any other third party firewall to allow TCP traffic to flow on port 80. Specifically, if
the machine hosting the web server is running the Windows Vista or Windows 7
operating system, enable the World Wide Web Services (HTTP) option in the Windows
Vista inbound firewall.
To understand the communication architecture for the CitectSCADA Web Client, it's
easiest to consider the role each of the following components play in achieving this
outcome:
l CitectSCADA Web Server - Performs the server-side functionality of the system. As
well as providing communication, it directs a client to the graphical and functional
content of a CitectSCADA project and the location of the runtime servers. This
information is stored on the Web Server when a CitectSCADA project is configured as
a “deployment”. A CitectSCADA Web Server can contain multiple deployments.
l CitectSCADA Runtime Servers (including the I/O Server, Alarms Server, Trends
Server and Report Server) - Monitor the physical production facility and contain the
live variable tag data, alarms and trends that the Web Client will display.
51
l Web Client - provides the platform to merge a deployed project's pages and content
with the raw data drawn from the runtime servers. Again, standard Web
technologies are needed, so the client uses Microsoft Internet Explorer.
Once you've installed CitectSCADA Web Server for IIS, you will find the following
directories under the \Inetpub\wwwroot\Citect folder.
l The base directory primarily hosts the administrative pages that are displayed by a
Web Server.
l The cgi-bin and images directories contain the content necessary to display these
pages.
l The client folder contains the client components (.cab files) that are delivered to a
remote computer to run a deployment. Any subdirectories includes the components
associated with a particular release (in this case, v2015).
l The deploy folder includes the files associated with any deployments (CitectSCADA
projects) configured on the Web Server.
l The #displayclientfolder (located in the Deploy folder) plays a key role in the Web
Server security, as the permissions defined for this folder determine the access rights
for each user.
l The locales folder contains the files necessary to support different languages for the
client interface. See “Implementing Multiple Language Support” in the Web Client
topic of the CitectSCADA online help.
The IIS Virtual Directory

The installation process also adds a virtual directory called Citect to Windows IIS
(Internet Information Services). This virtual directory establishes the Web Server as a
valid destination for client applications. However, it also plays an important role in
managing which users have access to the site.
You can view evidence of this virtual directory in the IIS management console, which is
launched by selecting Internet Information Services (or Internet Services Manager on
Windows 2000) from Windows' Administration Tools menu. The CitectSCADA virtual
directory is shown under the list of default web sites.
You can view the properties for the directory by selecting Properties from the right-click
menu.
The Virtual Directory inherits all security settings from the computer's default web site,
with the following exceptions:
l Directory Browsing is enabled
l Script Source Access is disabled
l The default document is set to default.htm only
52
l Anonymous access is disabled

l Integrated Authentication is disabled
l Basic Authentication is enabled
These security settings, including integrated authentication, anonymous access and SSL
Encryption, can be customized by the local administrator. However, proper
configuration needs experience with IIS and an understanding of the implications of
adjusting its settings.
Setting Up Security
If you want to use a Web Server/Client for communications in your CitectSCADA system
there are configuration requirements for both the server and the client. The major
configuration needed is that of security on the server.
Security on the Web Server is based on the implementation of user accounts. In the case
of an IIS-based Web server, security is tightly integrated with Windows user
authentication. For information on setting security on each of these, refer to Configuring
Security Using IIS.
Web Client user account types

Both systems support the same three user account types on a Web Client.
Client type Description
Administrator User is permitted to remotely view, add, update and delete

deployments.
Control Client User can view project pages and make adjustments to writable
values.
View-only Client User can only view the project pages.
The Web Server tests the access rights for each user when they log in and then displays
or hides the appropriate buttons on the home page accordingly.
Note: Although the Web Client security architecture controls access to your projects
on the Web Server, the CitectSCADA system security (privilege/area settings) still
manages the control system, maintaining a primary level of security.
53
Configuring Security Using IIS

Setting up security on an IIS-based Web Server primarily involves creating three
Windows user groups, each representing one of the Web Client user account types.
Individual users can then be assigned to the relevant user group, and automatically
inherit appropriate access rights based on the Windows security settings defined for the
group.
Note: To avoid security access issues for operating systems Windows Vista® and
above, creation of these Windows user groups is mandatory.
Client Type Access Rights
The following table defines the access rights that each type of user has to the Web
Server's installed directories, as defined by the properties for each.
In the table, read means Read & Execute, List Folder Contents and Read user
permissions are allowed; read and write means Full Control is allowed, and access
denied means Full Control is denied.
Installed directory ADMINISTRATOR CONTROL VIEW-ONLY
Citect read read read
Citect \ cgi-bin read read read
Citect \ client read read read
Citect \ deploy read and write read read
Citect \ deploy \ #displayclient read read access denied
Citect \ images read read read
For example, an administrator client needs to be able to read all the installed folders to
fully access the components of the home page. Additionally, they need write access to
the Deploy subdirectory to create new deployments.
By comparison, a View-only Client needs to be denied access to the #displayclient folder
to deny the ability to write back to a CitectSCADA project.
Therefore, when setting up security on the Web Server, your user accounts need to align
appropriately with the permissions outlined in the table above.
To implement the Web Server’s security strategy successfully, follow the procedure
below to configure your system, and simplify managing client accounts.
The ongoing management of your Web Server security then involves adding and
removing individual accounts as needed.
54
Note:
l The installation and initial configuration of the Web Server needs to be performed by
a Windows user with local administrator permissions; that is, they need to be able to
add and edit Windows User accounts, and modify files and folders. This capability is
needed to set up Web Client user accounts and manage security settings.
l It is important to understand the distinction between the role of the Windows Local
Administrator, and the Web Client’s Administrator users:
l Windows Administrator - configures security on the Web Server and sets up client
accounts.
l Web Client Administrator - an end user capable of modifying and managing
projects deployed on the Web Server.
The two roles parallel a CitectSCADA configuration engineer and a runtime operator
To create the client account user groups:
1. From the Computer Management tool, locate Local Users and Groups in the directory
tree. This is where the users and groups for the local machine are configured and
managed.
2. Right-click the Groups folder and select New Group. This displays the New Group
dialog.
3. In the Group Name, type Web Client Administrator (or something appropriate), and
describe the group's purpose.
4. Click Create.
The group you have just created will appear in the list of groups presented in the
Computer Management console.
Repeat the steps above to create Control Client and View-only Client user groups.
To test your security settings, add at least one user to each group.
Preparing the Citect folder
You need to set the security settings for the Citect folder and its sub-directories, as this
will determine the access granted to each type of client account.
To prepare the Citect folder:
1. Log on to the Web Server computer as a Windows Administrator.

2. Launch Windows Explorer and browse to the Citect folder. The Citect folder is located
in the installation directory. By default, this is Inetpub\wwwroot\Citect on the web
server computer.
3. Right-click the Citect folder and select Properties.
4. From the Properties dialog, select the Security tab to display the users currently
configured for the folder.
55
There will probably be several groups already defined in this folder. The two you need to
pay attention to are the Administrators group and the Everyone group.
l The Administrators group represents all the Windows users recognized by the
Web Server computer with Local Administrator rights. This group has Full
Control permissions on the folder, facilitating the ability to adjust the Web Server
security settings. If this is the case, there should be no reason to modify this group.
l The Everyone group represents all other users recognized by the local machine.
Give this group the following access to the Citect folder; allow Read & Execute,
List Folders Contents, and Read permissions. This provides local users on the
Web Server machine with the equivalent of Control Client permissions.
5. Add the three groups that you created in Configuring Client Account User Groups to
the Citect folder.
6. Confirm the security settings for the three newly created groups. Each has to have the
same access as the Everyone group: Read & Execute, List Folders Contents, and
Read permissions
7. All the subdirectories have to inherit the permissions set for the Citect folder. To do
this click the Advanced button on the Security tab of the properties dialog, and select
Replace permission entries on all child objects, then click OK.
This provides consistent security settings across all the installed directories. A Security
dialog might appear to alert you that this will “remove or reset explicitly defined
permissions on child objects”. Click Yes to continue.
Setting Access Rights for Client Accounts
The three client account types supported by the Web Client are defined by the security
settings for each within the installed directories on the Web Server machine.
The differences, outlined in the table in Client Type Access Rights, need specific security
settings for the Administrator Client and View-only Client types. An Administrator
needs write access to the Deploy subdirectory, and the View-only Client needs to be
denied access to the #displayclient subdirectory.
To configure security setting for the Administrator Client group:
The Administrator Client needs full access to the Deploy subdirectory to enable the
creation and modification of deployments.
1. Locate the Deploy subdirectory in the Citect folder. By default, this is
InetPub\wwwroot\Citect\Deploy.
2. Right-click the folder and select Properties to display the Deploy folder properties.
3. Click the Security tab and locate the Web Client Administrator group you created in
56
the list of users and groups.

4. Edit the permissions set for the group to Allow Full Control.
To configure the security settings for the View-only Client group:
The View-only Client needs to be denied access to the #displayclient subdirectory to
deny write changes being made to a deployed CitectSCADA project.
1. Locate the #displayclient subdirectory in the Citect folder. By default, this is
Inetpub\wwwroot\Citect\Deploy\#displayclient.
2. Right-click the folder and select Properties to display the folder properties.
3. Click the Security tab and locate the View-only Client group you created in the list of
users and groups.
4. Edit the permissions set for the group, and change to Deny Full Control
5. A Security dialog appears “Deny entries take priority over all Allow entries”. Click
Yes to continue.
Note: The Control Client group needs no additional configuration, as it uses the
settings outlined in Preparing the Citect folder.
Set security permissions accurately in order for the web server to operate correctly. If you
experience any problem with communicating from the web client check that the security
settings are correct for your installation.
Deleting a User Account
You can deny a user access to the Web Server by removing them from the groups that
have permissions set for the Citect folder.
However, if security is a concern, deny the user access to the Citect folder before you
delete the user. This avoids a situation where the operating system doesn't immediately
acknowledge that a user account has been deleted, creating a short period where a
deleted user can still log on.
To absolutely delete a user account:
1. Add the user as an individual to the Citect folder.

2. Set their access rights to Deny Full Control.
3. Remove the user from the groups that have permissions set for the Citect folder.
With all access denied, they cannot do anything even if they gain access.
Testing the Web Server Security Settings

To test the security settings for your Web Server client groups:
57
1. Launch Internet Explorer on the Web Server machine.

2. Call up the Web Client home page by typing in the following address:
http://localhost/Citect
3. Log in to the home page using a user name and password that's been added to the
Administrator Client group.
If successful, the System Messages dialog will read “LOGINADMIN Admin
(UserName) logged in”.
If the message starts with LOGINDC (for Control Client) or LOGINMC (for View-
only Client), there is a problem with your configuration. Confirm that you are
using the correct user name for the group you are testing. If the problem still
occurs, revisit the process in Setting up security using IIS to check that an error
hasn't been made.
4. Repeat this process with a Control Client and View-only Client user.
Once you have confirmed that security is correctly set up on the Web Server, you can
now prepare your CitectSCADA project for deployment. For more information see
Configuring a deployment in the online help.
Logging on to the Web Server

After setting up your client accounts, you need to provide the following details to each
end user so they can log on to the Web Server:
l Address of the Web Server
This is the address users have to type into their Web browser to gain access to the
CitectSCADA Web Server. If they are doing this remotely, the address is:
http://<machine name>/Citect
or
http://<machine IP address>/Citect
If they are logging on to the Web Server computer, the address is:
http://localhost/Citect
l User name and password

Once the browser has arrived at the Web Server, the end user is asked to provide a
user name and password. Typically, you just need to tell them that their Windows
user name and password will provide appropriate access. If you had to create a
new user profile for someone, provide them with the details.
58
Note: In some operating systems users may be logged in automatically. To modify

this behavior so the user is prompted to login, go to User Authentication in Internet
Explorer|Tools|Internet Options|Security Settings.
Once you have finalized the security setup on the Web Server, you are ready to prepare
your CitectSCADA projects for deployment.
59
60
Index
A
additional drivers 44
C
Citect license point count 26
CiUSAFE dialog box 27
communications drivers 41
Computer Setup Wizard configuration 49
configuration 49
D
demo mode 28
description
Integrated Environment 13
drivers 41, 44
dynamic point count 29
F
FlexNet license manager 23
FlexNet license server 23
floating 23
H
hardware key 22
I
IIS components 20
installation modify, repair or remove 45
Installation Requirements 17
Installing dialog 41
installing drivers 41
Installing Web Server 38
IPX/SPX 49
L
LAN 49
License Agreement dialog 33-34
license points
dynamic 26
static 26
licensing 21, 23
M
migration 9
Modify 46
Modify, Repair, or Remove 45
N
NetBEUI 49
Networking and Microsoft Windows 7 50
new features 9
new functionality 9
P
point count, independent 24
preliminary installation 31
Program Maintenance dialog 46
R
Remove 46
Repair 46
Requirements
hardware 18
IIS 20
LAN 19
operating system 18
RAM 17
System Software 18
S
Server Components dialog. 35
service pack
installing 45
uninstalling 47
Setup dialog 31
software licensing 21
T
TCP/IP 49
TCP/IP setup 50
W
WAN 49
Web Server
on IIS 38

Installation Guide

Uploaded by

Copyright:

Available Formats

Installation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Guide

Uploaded by

Copyright:

Available Formats

CitectSCADA 2015

Installation and Configuration Guide

Contact Schneider Electric today at www.schneider-electric.com

Chapter 3: Installation Description 13

Chapter 4: Installation Requirements 17

The addition of either symbol to a “Danger” or “Warning” safety

This is the safety alert symbol. It is used to alert you to personal

Electrical equipment should be installed, operated, serviced, and maintained only by

Before You Begin

CitectSCADA is a Supervisory Control and Data Acquisition (SCADA) solution. It facil-

UNINTENDED EQUIPMENT OPERATION

About This Guide

Maintaining System Currency

Example installation/upgrade scenario

9. Restore the upgraded project on the second server.

Backup and Restore Included Projects

Incremental Equipment Update

CitectSCADA 2015 now supports an incremental equipment update. When enabled, an

Link a Genie to an Equipment Type

Partial Associations can be used with Dynamic Associations

Running as a Windows Service

CitectSCADA 2015 can be run as a Windows™ service, allowing for unattended

Extended Memory Mode

In CitectSCADA 2015, you can configure an alarm server to operate in Extended

OPC Factory Server Version Update

Upgrading a Runtime-only Installation

Task Selection Dialogs

Failure to follow these instructions can result in death, serious injury, or

All Core Components

Description Minimum Specification

Processor Speed 2 cores @ 1.8 GHz for a server

Random Access Memory 2GB if SCADA client

Description Minimum Specification

Available Disk Space 10GB

Graphics Adapter (see

Description Recommended Specification or Higher

Processor Speed 4 cores @ 2 GHz for a server

Random Access memory 8GB

Available Disk Space 100GB

Graphics Adapter (see

Note:In CitectSCADA it is recommended that screen resolution be set at 1024 by 768

All Core Components Operating System

Windows Server 2012

Windows 7 with Service Pack 1(32 Bit and 64 Bit)or

Microsoft .NET Framework 4.5.1 (installed with CitectSCADA if

Microsoft .NET Framework 2.0 (x64) is required by "Schneider

Internet Explorer Version 9.0 or greater.

A Local Area Network (LAN) if you want to have multiple clients

If running under virtualization with VMWare, the minimum

Virtualization Host The following virtualization environments are supported:

Microsoft Internet Information Services (IIS) See Microsoft IIS

Product As for All Core Components.

Microsoft IIS Compatibility

Operating System IIS version

Windows 8.1 8.5

Windows Server 2012 R2 8.5

Windows Server 2012 8.0

Windows Server 2008 R2 7.5

Windows Server 2008 7.0

Components recommended for Web Server Installation