Citect SCADA 2016
ReadMe
(Updated 15/11/2016)
Please refer to the Installation and Configuration Guide for information on the installation of the product, and the upgrade process for existing projects.
1. Disclaimers
2. Features
4. Requirements
1.1. Disclaimer of All Warranties
As detailed in paragraph 9 of the End User Licence Agreement, SCHNEIDER ELECTRIC excludes all warranties and liabilities to the fullest extent permitted by law.
CITECT SCADA and all documentation are provided "AS IS" and your company understands that it assumes all risks pertaining to your use of CITECT SCADA.
YOUR COMPANY AGREES AND ACKNOWLEDGES THAT SCHNEIDER ELECTRIC SHALL HAVE NO LIABILITY WHATSOEVER TO YOUR COMPANY FOR ANY PROBLEMS IN OR CAUSED BY CITECT SCADA OR THE RELATED DOCUMENTATION, WHETHER DIRECT, INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL (INCLUDING LOSS OF PROFITS).
2.1. New Features
The following features have been added in Citect SCADA 2016 and are available in this release.
1. New Engineering Environment - Citect Studio
Citect SCADA 2016 comes with a brand new user interface that is intuitive and easy to use. The new interface is divided into several “activities” that reflect the workflow you would typically use to configure a Citect SCADA project. These activities (accessible via a vertical Activity Bar to the left) include:
· Projects - Create and manage your projects.
· Topology - Configure system computers, clusters and I/O devices.
· System Model - Configure and view equipment, variable tags, alarms, trend tags and accumulators.
· Visualization - View and configure menus and commands.
· Security - Configure user roles and user permissions.
· Standards - Manage assets for use across multiple projects.
· Setup - Manage assets that are typically only set up once.
· Deploy – Distribute project runtime components to computers in your network.
The highlight of Citect Studio is the Grid Editor, which allows tabular editing of alarms, variable tags, equipment, and so on, across an entire system rather than on a per project basis. The Grid Editor makes editing values easy as a change made to a single record can be propagated throughout the system. It also allows multi-column sorting and filtering. In addition, bulk editing of multiple records is possible.
Properties of a selected component are displayed next to the Grid Editor in a Property Grid where you can update component values.
2. Topology
Citect SCADA 2016 allows you to quickly visualize the computers, network addresses, clusters and services being used in your system through a new interface that displays the related information in a single view.
The Topology activity allows you to configure the computers in your SCADA system and organize the processes in clusters based on your system requirements. You can view configuration information for computers and components in two modes:
· By Computer - displays configuration on physical computers
· By Cluster - displays clusters and the servers assigned to each cluster
You can add and edit your system components using the Grid Editor.
3. Deployment
Citect SCADA 2016 allows you to roll out project changes to computers in your SCADA system located at a single site or across multiple sites through the Deployment feature. This feature allows for centralized management of project versions to be deployed to servers and clients including Citect Anywhere clients. Changes can be deployed automatically or through a customizable notification to the operator. Deployed changes can be rolled back if required. When new project versions are deployed, only the project changes are sent to the computers instead of the entire project. The amount of bandwidth available when deploying changes on the network can also be throttled.
4. Calculated Variables
A calculated variable allows you to generate a tag value at runtime that is the result of a Cicode expression. To configure a calculated variable, you use a variable tag that addresses an I/O device with its protocol set to "CICODE". If the variable tag address is a valid Cicode expression, the Cicode I/O device will calculate the result of the expression and present it as the tag value.
5. BACnet Schedule Integration
Scheduler now supports the integration of schedules that are configured locally on a BACNet device. You can also view and modify schedule-object and calendar-object properties on a BACNet device at runtime.
Schedule integration is enabled via the following process:
· A BACnet I/O device is configured in the engineering environment and connected to Citect SCADA via the BACNET driver.
· Variable tags and equipment definitions that represent the device's schedule and calendar objects are configured on the I/O server through tag import.
· The reports server subscribes to the tags on the I/O server and generates schedule entries in Scheduler.
· Any changes to the schedule entries are written back to the BACnet device via the I/O server.
6. Documentation
The product documentation has been moved to an HTML5 platform and is now delivered using an Internet browser. The content has also been restructured to align with the presentation of Citect Studio. You can access the new help system from the Help button at the bottom of the Activity Bar.
These features are documented in the Citect SCADA Help (see the topic “What’s New in Citect SCADA 2016” in the “Getting Started” section).
3.1. What are the known issues for Citect SCADA 2016?
1. Installation error on Windows Server 2012 R2 if the required Windows updates are not installed
Citect SCADA 2016 may not install correctly on Windows Server 2012 R2 if the required Windows updates have not been installed, stopping .NET 4.6.1 from being installed. Check Programs and Features in Control Panel, then go to View installed updates and look for hotfix KB2919355. If this hotfix does not exist, then download this hotfix from Microsoft website and install it manually. Then restart the computer.
2. Change to the name of the default project folder affects Beta projects
The default project folder has been renamed from "Citect SCADA 8.0" to "Citect SCADA 2016". This affects projects from Citect SCADA 2016 Beta because there is no automatic migration. Users on Citect SCADA 2016 Beta need to take a backup of their projects before upgrading to the latest version.
3. Alarm Server not starting
If running Citect SCADA on Windows 8.1 (builds released before 16th April 2014) or Windows Server 2012 R2 (released before 16th April 2014), the alarm server may not start successfully because the operating system may not have .NET 4.6.1 installed. To work around this:
i. Perform a Windows Update and restart until the operating system has no more pending updates.
ii. Check Programs and Features in Control Panel, then go to View installed updates and look for hotfix KB2919355. If this hotfix does not exist, then download this hotfix from Microsoft website and install it manually. Then restart the computer.
iii. Then, either download and install .NET 4.6.1 manually, or install it via Windows Update hotfix KB3102467. Then restart the computer. Note that both approaches depend on KB2919355 being installed successfully.
4. Port conflict between Wonderware System Platform and Citect SCADA 2016
When Wonderware System Platform and Citect SCADA 2016 are installed on the same computer, there may be a conflict on port 8090. Both ArchestrA Galaxy repository and Citect SCADA 2016 Floating License Manager listen on the same port. Wonderware IDE users will receive an error message that connection to the Galaxy repository is not possible. For users who need to install both products on the same computer, it is recommended that the port number for the Floating License Manager be changed. This can be done during installation or via the FlexNet License Administrator.
5. Windows Server 2016 support for drivers
Drivers that have been included with Citect SCADA 2016 have not been stamped as compatible with Windows Server 2016. For a list of drivers that are compatible with Windows Server 2016, refer to DriverWeb at http://www.citect.schneider-electric.com/scada/citectscada/downloads-updates/driverweb.
6. Checkbox next to a computer in the Deployment activity > Computers view not selected
The checkbox next to a computer in the Deployment activity > Computers view is not selected even if the computer or the group to which the computer belongs are selected. This is specific to system locales Finnish, Japanese, Portuguese and Spanish.
7. Status field in the Deployment activity > Computers view shows incorrect status
The Status field in the Deployment activity > Computers view may change from “Deploying” to “Running” if you switch to the Versions view from the Computers view and back again while deployment is in progress.
8. Windows Task Bar remains hidden when Citect Studio is maximized
When the Windows Task Bar is configured to use the Auto-Hide option and you maximize Citect Studio, the Task Bar will not be shown automatically if the mouse is moved to the bottom of the screen. Pressing the Windows logo key will display the Task Bar correctly.
9. HTML5 help missing images and controls when viewed in Windows High Contrast themes
If you view the Citect SCADA 2016 HTML5 help in Windows High Contrast themes, some images and controls may not be displayed on Internet Explorer and Microsoft Edge. It is recommended that you use Google Chrome if using a Windows High Contrast theme.
10.Uninstallation takes several minutes
For this release, the uninstallation process will take several minutes. This is mostly caused by duplicated documentation including uncompressed HTML5 content (instead of CHM files).
11. Web Client shuts down incorrectly when it does not get a license
When the Back button is pressed multiple times on the Web Client when it does not get a license, the Web Client may not shut down correctly.
12. Navigating Citect Studio with touch devices
Navigating Citect Studio for extremely long periods of time using a touch screen or screen reading software without restarting the application may result in high memory usage.
13. Uninstallation does not shut down running application
When uninstalling Citect SCADA 2016, the installation program will not shut down running Citect applications automatically. This may result in some applications not being uninstalled correctly, and Citect SCADA may no longer function properly.
14. Restoring localized projects to a different language environment displays an error message
The Period field on a trend may display the error message “Invalid time format” if a localized project is restored to an environment in a different language. The workaround is to distribute compiled projects.
4. Requirements
4.1. Software
Citect SCADA 2016 can be run on:
· Windows® 7 SP1 (32 and 64 bit)
· Windows® 8
· Windows® 8.1 (32 and 64 bit)
· Windows® 10 (32 and 64 bit)
· Windows® Server 2008 SP2 (32 and 64 bit)
· Windows® Server 2008 R2 SP1
· Windows® Server 2012
· Windows® Server 2012 R2
· Windows® Server 2016
Notes:
· Internet Explorer Version 9 or later is the minimum requirement when using the Process Analyst, the Citect SCADA Web Client, or the Citect SCADA Web Server. However, in line with Microsoft advice, we recommend you use the latest version of Internet Explorer with these products.
· Extended Memory mode for an alarm server can only be run on a 64-bit operating system.
4.2. Hardware
Selecting hardware is dependent upon a number of factors such as:
· The role of the hardware in your SCADA system
· The amount of I/O, Alarms, Trends and the frequency of change
· Number of Clients (for Servers)
· Server Clustering
· Complexity of your user interface
· Degree of customization
The requirements below have been tested using a simulated SCADA system with 10 clients connected maintaining a server CPU load of less than 25% and should be used as a guideline only due to the impact of the factors listed earlier.
|
Role |
CPU PassMark® |
Cores |
RAM |
HDD |
Graphics |
Screen Resolution |
Network |
|
Client |
2000 |
1 |
2GB |
10GB |
DirectX
or later with WDDM 1.0 Driver |
800 x 600 |
100 Mb |
|
Server |
2000 |
2 |
4GB |
10GB |
DirectX
or later with WDDM 1.0 Driver |
800 x 600 |
100 Mb |
|
Engineering |
2000 |
2 |
8GB |
10GB |
DirectX
or later with WDDM 1.0 Driver |
1920 x 1080 |
100 Mb |
|
HMI |
1400 |
2 |
8GB |
10GB |
DirectX
or later with WDDM 1.0 Driver |
800 x 600 |
N/A |
Notes:
1. The exception to the 10-client simulation is the HMI role, with a Server/Client combination operating without networking.
2. Refer to the detailed Hardware Requirements in the Citect SCADA 2016 Installation Guide to better gauge hardware recommendations specific to the size of your SCADA system.
PC Performance
General PC performance will be affected by the major elements of CPU, RAM, Bus, and HDD speed.
The clock speed no longer defines how powerful a CPU is; the required processor is defined according to an average CPU mark given by PassMark® Software. To check CPU performance, for example for a Core i3 CPU, type "PassMark Core i3" in the search engine of your internet browser. This will give you the CPU's calculated performance as compared to other similar well-known processors.
In general, it is recommended that computers in your SCADA network utilize no more than ~25% CPU in normal state. This allows the system to be responsive, and handle abnormal situations better.
5. Operational Notes
5.1. DriverWeb
For up-to-date information on drivers and related information, please visit DriverWeb at http://www.citect.schneider-electric.com/scada/citectscada/downloads-updates/driverweb. It is recommended that you subscribe to the forums for the drivers that you use so that you are alerted to any updates that occur.