Visual TD Installation Guide
Visual TD Installation Guide
Fax: +1.514.227.5256
Web: http://www.eaton.com/smartgrid
Email: [email protected]
Contents i
4 Visual T&D configuration..........................................................................................................................................28
4.1 Visual T&D server configuration....................................................................................................................... 28
4.1.1 The Visual T&D Server Agent.............................................................................................................. 28
4.1.1.1 Deactivating Visual T&D Server Agent status notifications................................................. 28
4.1.1.2 Removing the Visual T&D server agent icon from the system tray..................................... 28
4.1.2 The Visual T&D server Control Panel.................................................................................................. 29
4.1.2.1 Accessing the Visual T&D server Control Panel................................................................. 29
4.1.3 Visual T&D and Windows user account privileges...............................................................................30
4.1.3.1 Creating groups to grant privileges to users........................................................................30
4.1.3.2 Modifying an existing privilege group.................................................................................. 31
4.1.4 Visual T&D and Windows user accounts............................................................................................. 31
4.1.4.1 User accounts password requirements............................................................................... 31
4.1.4.2 Modifying password requirements for Visual T&D user accounts....................................... 32
4.1.4.3 Creating a new Visual T&D user account............................................................................ 32
4.1.4.4 Modifying an existing Visual T&D user account.................................................................. 33
4.1.4.5 Creating a Windows user account in Visual T&D................................................................ 33
4.1.4.6 Modifying an existing Windows user account......................................................................34
4.1.4.7 Configuring the Visual T&D authentication mode................................................................34
4.1.4.8 Changing a Visual T&D user account password in Visual T&D Explorer............................ 35
4.1.4.9 Allowing multiple login using the same credentials............................................................. 35
4.1.5 Remote Visual T&D server management............................................................................................ 35
4.1.5.1 Allowing remote Visual T&D server management............................................................... 36
4.1.6 Control operations in Visual T&D......................................................................................................... 36
4.1.6.1 Visual T&D SCADA control interlock................................................................................... 37
4.1.6.2 Activating Visual T&D SCADA control interlock.................................................................. 37
4.1.6.3 Visual T&D control operation privilege timeout....................................................................37
4.1.6.4 Specifying the Visual T&D control operation privilege timeout............................................ 38
4.1.6.5 Deactivating simultaneous control operations from multiple users......................................38
4.1.7 Visual T&D general alarm management settings.................................................................................38
4.1.7.1 Specifying how alarms and events must be managed on a given Visual T&D server........ 38
4.1.8 Visual T&D configuration files management........................................................................................ 39
4.1.8.1 Specifying the folder location to store Visual T&D configuration files..................................39
4.1.9 Visual T&D task management settings................................................................................................ 40
4.1.9.1 Specifying a dedicated account for Visual T&D tasks......................................................... 40
4.1.10 Syslog export module for Visual T&D.................................................................................................. 41
4.1.10.1 Activating the Syslog transmitter......................................................................................... 41
4.1.10.2 Specifying the address of the receiver................................................................................ 41
4.1.10.3 Log category options for the Syslog export module............................................................ 42
4.1.10.4 Selecting which log categories to transmit.......................................................................... 44
4.1.10.5 Adjusting the timestamp of Syslog messages..................................................................... 45
4.2 Visual T&D engine configuration.......................................................................................................................45
4.2.1 The Visual T&D Manager.....................................................................................................................45
4.2.2 The Visual T&D datalog....................................................................................................................... 46
4.2.2.1 Adding an SQL server database to the list of Visual T&D database servers...................... 46
4.2.2.2 Adding a PostgreSQL database to the list of Visual T&D database servers....................... 47
Contents ii
4.2.2.3 Setting up the Visual T&D datalog.......................................................................................47
4.2.3 MultiSpeak specification interface........................................................................................................48
4.2.3.1 Implemented methods......................................................................................................... 48
4.2.3.2 Setting up Multispeak.......................................................................................................... 49
4.3 Services configuration and control....................................................................................................................50
5 Security hardening.................................................................................................................................................... 52
5.1 Restricting Visual T&D resources access......................................................................................................... 52
5.2 Restricting access to Visual T&D server resources.......................................................................................... 54
5.2.1 Restricting access to Visual T&D server resources through folder properties.....................................56
5.2.2 Add a group or user to a folder security or registry access list............................................................ 56
5.2.3 Remove Windows "Users" group or any other inherited privilege from a folder security or registry
access list.............................................................................................................................................57
5.2.4 Restricting access to Visual T&D server resources through registry settings......................................57
5.2.5 Specifying the Windows logon account for the Visual T&D server service..........................................58
5.2.6 Specifying the Windows logon account for the Visual T&D Engine service.........................................59
5.3 Restricting access to Visual T&D client application resources......................................................................... 60
5.3.1 Restricting Access to Visual T&D Client Application Resources through Folder Properties............... 62
5.3.2 Add a group or user to a folder security or registry access list (client application).............................. 62
5.3.3 Remove Windows "Users" group or any other inherited privilege from a folder security or registry
access list (client application).............................................................................................................. 62
5.3.4 Restricting access to Visual T&D workstation resources through registry settings............................. 63
5.4 Using the database server account with minimal privileges............................................................................. 63
5.5 Exception for communication ports...................................................................................................................63
5.5.1 Allowing communication with the Visual T&D through the firewall.......................................................63
5.5.2 Allowing communication with the Visual T&D server through DCOM ports.........................................65
5.5.3 Restricting access to Visual T&D server DCOM ports.........................................................................65
5.6 DCOM authentication level for communication with Visual T&D server........................................................... 66
5.6.1 Reinforcing data integrity in communications with Visual T&D server................................................. 67
5.6.2 Using DCOM with unidentified access.................................................................................................68
5.7 Displaying appropriate use banner................................................................................................................... 68
5.8 About Windows automatic updates...................................................................................................................69
Contents iii
7 Visual T&D server maintenance...............................................................................................................................76
7.1 Visual T&D backup and restore operations...................................................................................................... 76
7.1.1 Visual T&D backup considerations...................................................................................................... 76
7.1.2 Backing up a site configuration using Visual T&D Support Assistant.................................................. 76
7.1.3 Restoring a site configuration backed up using Visual T&D Support Assistant................................... 77
7.2 License key management................................................................................................................................. 78
7.2.1 Viewing Current Visual T&D License Information................................................................................ 78
7.2.2 Managing Eaton license key................................................................................................................ 79
7.2.2.1 Migrating your legacy license key to an Eaton license key................................................. 79
7.2.2.2 Upgrading your current Eaton license key...........................................................................79
7.2.2.3 Moving your current Eaton license key to another machine................................................79
7.2.3 Managing legacy license key............................................................................................................... 80
7.2.3.1 How Visual T&D is selecting its license............................................................................... 81
7.2.3.2 The SafeNet Web tool to manage the HASP HL Net key....................................................83
7.2.3.2.1 Verifying the availability of a license key......................................................... 83
7.2.3.2.2 Setting up security for remote configuration access for the HASP HL Net
key................................................................................................................... 84
7.2.3.2.3 Setting up a Visual TD host computer to find HASP HL Net keys...................85
7.2.3.2.4 Setting up remote host computers from the local ACC................................... 86
7.2.3.2.5 Setting up users access from the key's local ACC.......................................... 87
7.2.3.2.6 Consulting active sessions on a specific HASP HL Net key............................88
7.2.3.3 The License Activator utility program.................................................................................. 89
7.2.3.4 Upgrading your current Visual T&D license using License Activator...................................90
Appendix.................................................................................................................................................................... 98
External libraries licensing descriptions............................................................................................................ 98
Contents iv
List of Tables
Table 1 : Sections of the document.............................................................................................................................. 2
Table 2 : Related documentation..................................................................................................................................3
Table 3 : Optional Visual T&D functions.......................................................................................................................8
Table 4 : Windows account specifications in reference with the security model........................................................ 13
Table 5 : Windows accounts specifications................................................................................................................ 16
Table 6 : Available options for the installer used in command line interpreter........................................................... 19
Table 7 : Specific issues related to a Visual T&D upgrade.........................................................................................27
Table 8 : Visual T&D and Windows user account privileges...................................................................................... 30
Table 9 : SMP Gateway system data points for SCADA Control Interlock.................................................................37
Table 10 : Log Category Options..................................................................................................................................42
Table 11 : Visual T&D Server resource accesses for different accounts..................................................................... 54
Table 12 : Visual T&D client application resource accesses for different accounts..................................................... 60
Table 13 : Ports opened by Visual T&D....................................................................................................................... 64
Table 14 : Ports used by Visual T&D............................................................................................................................64
Table 15 : DCOM authentication levels supported according to the Visual T&D version.............................................66
Table 16 : Forcing the Visual T&D server to choose a license key with a lower priority.............................................. 82
Table 17 : Cybersecurity guidelines, description of the categories.............................................................................. 92
Contents v
List of Figures
Figure 1 : The Visual T&D software architecture........................................................................................................... 6
Figure 2 : Operating system interaction with Visual T&D............................................................................................ 10
Figure 3 : Visual T&D components with Windows accounts running them..................................................................14
Figure 4 : Planning T&D installation............................................................................................................................ 15
Figure 5 : Visual T&D components with access levels to folders................................................................................ 52
Figure 6 : Planning privileges for each resource......................................................................................................... 53
Contents vi
Introduction Chapter 1
1 Introduction
This is the installation guide of Visual T&D, a software solution that is part of Eaton family of product for energy automa-
tion.
In addition to providing the basic installation procedures for the Visual T&D software components, this document also
proposes some guidance on how to securely deploy a Visual T&D system in a production environment.
1.2 Overview
This document contains all the information required to install, configure and perform the maintenance of a Visual T&D
complete system.
The guidance provided for the secure deployment of the Visual T&D software components are focused on the Visual
T&D product itself, by pointing which elements of the operating system are used by Visual T&D and guiding the system
administrator and integrator on the most secure way to deploy Visual T&D software components.
This document cannot be used for hardening the whole operating system host. We recommend using this document in
combination with any best-practice guidelines published for your operating system.
Note: The configuration of a Visual T&D site, which includes the specification of data sources, data points settings,
alarms, events and other site-related features, is performed using the Visual T&D Explorer client application.
The Visual T&D Installation Guide is divided into the following sections:
Introduction This is the current chapter. It presents the purpose and scope of this document,
indicates how to contact Eaton for assistance, and lists all related documents.
Visual T&D overview This chapter presents the Visual T&D software architecture, its general hardware
and software requirements and, the operating system interaction with the different
Visual T&D software components.
Visual T&D installation This chapter first presents basic elements for the Visual T&D installation planning.
Visual T&D server This chapter presents the different tools to configure the Visual T&D server.
configuration
Security hardening Visual T&D components store application data mainly on the operating file system
and in the registry. The access to those resources can be restricted to specific
Windows accounts or groups to ensure data confidentiality and also minimizing
software attack surface.
The Visual T&D standalone This chapter presents the Visual T&D Standalone HMI mode and explains how to
HMI mode configure Visual T&D, using the Visual T&D Shell Configurator application, to run in
this mode.
Visual T&D server This chapter contains all the information required to perform maintenance of your
maintenance Visual T&D system.
Eaton product secure This chapter provides important guidelines for secure deployment and configuration
configuration guidelines of Visual T&D.
Visual T&D Explorer User MN914001EN This document presents the Visual T&D Explorer, an application
Manual providing immediate access to all Visual T&D data points in real-
time, in a variety of formats, with minimum configuration effort.
It also explains how to configure these data points and the
various real-time and historical views, but also how to set up
alarms and events based on these data points' values.
Visual T&D Diagram Editor MN914002EN This document presents the Diagram Editor, a Visual T&D
User Guide application allowing the creation of interactive diagrams used to
monitor and operate a substation or an electric grid.
Visual T&D Excel Add-In MN914006EN This document presents the Visual T&D Excel Add-In, a
User Guide Microsoft Excel add-in that allows Visual T&D users to access
® ®
Visual T&D Communication MN914007EN This document explains how to set up the Visual T&D
Server User Guide Communication Server, an optional component of Visual T&D
that allows you to connect substation devices to the Visual T&D
server without having to go through an SMP Gateway or an OPC
server.
Visual T&D Cluster MN914008EN This document describes the various operations that must
Configuration Guide be performed to install and set up Visual T&D in a failover
cluster configuration.
Real-Time Monitor User MN914019EN This document contains all the information required to install,
Manual configure and use the Real-Time Monitor Web Solution, an
extension to the Visual T&D software that allows to access a
Web HMI for day-to-day operations.
Integrating Visual T&D to a MN914021EN This technical specification presents all necessary instructions
database server to integrate Visual T&D to a new or existing database server
as well as the technical aspects to consider for a successful
integration.
These documents are found in the Visual T&D installation package. They are installed on the computer hosting Visual
T&D along with the software applications. Some technical notes are also provided.
Note: Documentation related to Windows accounts settings and operating system’s best practices can be found
online on Microsoft sites.
Technical Support
Eaton
Energy Automation Solutions
Business hours are from 8 a.m. and 5 p.m. CST, Monday to Friday.
1. Select Windows > Programs > Eaton Visual T&D > Support Assistant.
2. In the Visual T&D Support Assistant window, click Create.
3. If the proposed site configuration file is not the one for which you need assistance, click the Browse button, locate
the corresponding site configuration file (.mdb), and then click Open.
4. Type the complete path and name of the folder where the ZIP file will be copied, or use the corresponding Browse
button to locate and select that folder.
5. Click Fetch to generate the ZIP file at the specified location.
6. Once the ZIP file was properly generated, click Close.
• OPC servers
• The Visual T&D Communication Server
• Enterprise Gateway
Each of these data sources can itself be connected to large number of binary or analog data points.
In most systems, configuring the data acquisition parameters for each data point is often quite a challenging task. With
Visual T&D, this task is greatly simplified by the built-in capability to query the data sources and automatically import the
configuration of all their data points. Furthermore, once the system is set up, the server can detect changes to the data
sources and update the site configuration accordingly.
Once the data sources are set up and the data points have been identified, the server can immediately start performing
basic data acquisition and data logging functions. With a minimum of effort, you can use Visual T&D to chart and display
significant data related to the substation.
If you provide additional configuration parameters, the server will be able to perform even more advanced functions,
such as scaling analog readings, detecting thresholds, and generating alarms and events.
Reports Allows you to generate reports of significant events for a selected time frame.
DFR Allows you to view historical charts of the different channels on a device, subsequent
to a problem that caused the generation of a digital fault record.
Alarm and Event Allows you to notify interested parties, via email, SMS or pager, when significant
Notification events occur.
OPC Data Access Allows you to access the real-time values, quality flags and timestamps of the data
points via an OPC client. Visual T&D then operates as an OPC server supporting
version 2.05a of the OPC Data Access standard.
Communication Server Allows you to connect substation devices to your Visual T&D computer without having
to go through an SMP Gateway or an OPC server.
Redundancy Allows you to install Visual T&D in a cluster for fault tolerance, to ensure high
availability of the Visual T&D server in case of hardware or software failure.
Import of data from Allows you to import data stored in the datalog of a Visual T&D server version 3.7 or
previous Visual T&D earlier.
datalog versions
MultiSpeak Allows you to communicate with external enterprise application software using the
SCADA interface of the MultiSpeak protocol.
Note: To make a Visual T&D data point available through the Visual T&D OPC server, you must select the
Publish OPC setting specific to this data point.
The COM server name (i.e. ProgID) of the Visual T&D OPC server is Cybectec.VisualSubstation.1.
Note: If the Visual T&D server must be installed on a failover cluster, refer to the following website to learn the
requirements that apply to this particular scenario:http://technet.microsoft.com/en-us/library/cc771404.aspx
Note: The supported Windows Code Page is 1252 - Windows Latin. The installer will refuse to install Visual T&D if
this specific Code Page is not supported by the Windows version installed on the computer.
Note: The use of a local or remote Microsoft SQL Server or PostgreSQL database does not require a license
option.
The Visual T&D Maintenance Plan provides you with continuous access to the latest version of the Visual T&D software:
• Free access to software releases. You will have free access to new software releases. A minimum of one update
per year is planned.
• Notifications. You will receive notifications of updates, patches, and fixes to existing versions of your covered
software products (Subject to product life cycle policy).
Software maintenance is included with all new software purchase. You will be notified by the software when the
maintenance period is about to expire.
Please contact our inside sales department for a quote based on your needs at [email protected].
Note: If you are installing redundant Visual T&D servers, refer to the Visual T&D Cluster Configuration Guide,
MN914008EN, rather than using the procedure described in this chapter.
Note: The installer is used to perform offline installation of the Visual T&D software, which means that it does
not require an internet connection: it contains everything that needs to be installed, including third-party software
components.
Note: Regardless of the selected authentication method, roles and privileges are managed using local database
accounts.
If Windows Authentication is selected, refer to section Planning Windows accounts before Visual T&D installation to
plan and configure users executing Visual T&D services. In that case, the service account will be used to connect to the
historian database.
3.2 Roles and privileges tied to the Visual T&D security model
In Visual T&D, the security model relies on specific roles and privileges to describe its intended security deployment.
Privileges are tied to a physical person and give the right to run or access a specific software component or function.
Groups associate together user privileges, they are used for the permission to access a specific set of resources
belonging to an application; they confine security rules and apply the least privilege principle. Depending on the
customer’s policies and local organization, two or more roles can be assumed by the same physical person.
The following table resumes the Windows account specifications in reference to the security model defined for the Visual
T&D system and according to the physical person involved and its role and relation with the Visual T&D system.
Visual T&D administrator (integrator) • Install Visual T&D product Tied to a local machine privilege
• Configure all settings for a right
successful deployment
Network administrator Help the Visual T&D administrator to Tied to a domain administrator
configure every request related to: account
• Windows accounts and groups
• Administrator settings that are
part of the deployment
Visual T&D operators Use the Visual T&D system on a day Tied to a Windows account with
to day basis credentials for each user
Visual T&D engineer In charge of Visual T&D system Tied to a Windows account
configuration (operational)
Using the table below as a guide will help you for the creation of required and optional accounts, if they do not already
exist in your network environment.
Local machine R Must be a member of the local group: • Install the product
administrator • Administrators • Access Visual T&D security
settings located in the Visual
T&D Server Control Panel.
Visual T&D R • Non administrative Windows account • One account for each physical
Operator • Can be member of a domain group person accessing Visual T&D via
called "VTD Operators" product client application.
Visual T&D R Must be a member of the local group: • Visual T&D configuration in an
Engineer • Administrators operational standpoint.
• Access to Visual T&D security
settings located in the Visual
T&D Server Control Panel.
Visual T&D R • Non -Administrative Windows account • Execute the configured “start an
Task • Must have the following privilege: application” type task (launched
- Execute (for the executable by Visual T&D Server).
location set in the configured
These required and optional Windows accounts, if they do not already exits, will be configured as the Visual T&D
component installation process evolves.
Note: It is possible to install Visual T&D in silent mode, for example in an automated installation. To do that, a
script is necessary and this script must take into account all visual T&D installation parameters as well as all the
Visual T&D product prerequisites. This installation method is not yet documented; if you want to install Visual T&D
system in silent mode, please contact our Technical Support at Getting assistance, and we will be happy to assist
you with this task.
With both installation methods, once the installation competed, it is possible to consult the installation log. To do that:
• Find the host computer temporary directory (e.g.: C:\Windows\Temp\)
• In this directory, open the MSI log file. The file is identified as VTD_M.m.b.sp where:
Ex: VTD_4.3.9.0 (the number is different from the software version identification, e.g.: 5.3R3)
3.4.1 Deploying a Visual T&D system on the server using the installer
The following instructions explain how to install and deploy a Visual T&D system using the Visual T&D installer.
Note: Visual T&D applications are installed both in English and French. Although it is possible to change
the client applications language at runtime, the server data always remains in the same language, which is
determined at installation time.
3. Components selection
a. Select components to install.
b. If the Visual T&D Communication Server module is required, click on the corresponding icon and select
This feature will be installed on local hard drive.
c. For each selected feature, you can also click Change to change the installation folder of that feature.
d. Once finished with the selection of the feature to install, click Next to continue.
4. In the final pane, click Create shortcuts to Visual T&D client applications on your desktop if you want to create
shortcuts to the Visual T&D Explorer and Visual T&D Diagram Editor programs on the server computer desktop.
5. Click Install to start the installation process.
The installer will proceed with the installation of the selected Visual T&D components, along with third-party software
components that are required by Visual T&D.
6. If required by the installer, restart the computer to complete the installation process. Once the installation completes
successfully, click Done.
The Visual T&D Server should start automatically, and a startup notification message should be displayed in the
Windows system tray by the Visual T&D Server Agent.
Note: If a problem occurs when installing the Microsoft Redistributable VC90 component, try the following
procedure:
a. Using the Regedit application, create the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE
\Cybectec\Common.
b. Created the following DWORD value: Release_VC9.0Redist and set the DWORD value to 1.
c. Close the Regedit application and restart the installation.
3.4.2 Deploying a Visual T&D system on the server using the command line
interpreter
The following instructions explain how to install and deploy a Visual T&D system using the command line interpreter.
This installation is performed without any user intervention and uses predefined option choices included in the syntax.
The options that are not specified are using the default settings.
/s Optional Installs Visual T&D silently. Must be used in conjunction with the /gn
option (see section Product specific options below)
/gn, /gr, /gb or /gf Refer to the documentation of user interface levels for Microsoft MSI
installer: none, reduced, basic and full.
Table 6 : Available options for the installer used in command line interpreter
Server
Communication
Server
OPCServer
FORCE_INSTALL In the case when one value related to the options is affected, it
ignores the operation validation result that require a reboot before
proceeding with the installation procedure.
IS_NET_API_LOGON Mandatory Visual T&D local account password that will be either verified or
_PASSWORD created to run VTDEngine service.
Table 6 : Available options for the installer used in command line interpreter
SERVICE_NAME_ This parameter allows to specify a given prefix to all "Visual T&D
PREFIX Server" services names. All characters must be included in the
specified prefix, including the space character if needed.
For example: SERVICE_NAME_PREFIX="YFA - "
Table 6 : Available options for the installer used in command line interpreter
Note: The Visual T&D installer has been developed using MSI technology. To learn more about basic options
for a MSI installer in command line interpreter, run the following command: msiexec /?.
3. In the Activation ID(s) section, simply cut and paste the activation ID copied from the email you received into the
empty field. Be careful not to copy any leading or trailing spaces. Press the Enter key and repeat the same process
for all activation IDs.
4. If the Visual T&D server does not have Internet access or you are activating the Eaton license for the first time,
follow these instructions. Otherwise, go to the next step:
a. In the Offline section, click the Export button. This will generate a "capability request" file.
b. Using another computer that has access to Internet, open the following Eaton licensing website: https://
eaton.flexnetoperations.com/flexnet/operationsportal/logon.do and click the Register
link. You can get to this URL by clicking on the Open licensing website button.
c. Enter your registration information in the form, and select Complete when finished. Please note that we
may contact you in the future regarding updates and/or renewal of the Visual T&D software. Your contact
information will not be used for marketing purposes without your express consent and opt-in.
e. Verify that the option Generate license is selected. Then, click the Choose file button to browse and select
the Capability request file that you generated using Visual T&D Manager.
f. Click Upload. When the process is completed, a message area will be displayed near the top of your
browser window with a link to download a Capability response file.
g. Click the link to download the Capability response file.
h. Return to Visual T&D Manager and click on the Import button to select and upload the capability response
file that you previously downloaded.
i. Click Apply.
5. If the Visual T&D server has Internet access and you are not activating the license for the first time, you can activate
your license from Visual T&D Manager using the online mode:
a. In the Options section, select the Online mode option.
b. Click Apply.
Note: If the Visual T&D server machine uses a proxy for outgoing connections, you must
open the following file: C:\Program Files (x86)\Eaton\Visual T&D\Engine
\VTD.Engine.exe.config, uncomment the proxy settings section and specify the proxy address in
the relevant settings section. The URL must have the following format : http://proxy.abc.com:8080.
6. Select the Options page, to verify that the required license options are activated for your Visual T&D system.
The License Activator program must be installed on the Visual T&D server computer.
Note: License Activator is automatically installed with the Visual T&D server components.
License key activation is only required for software key, or license key upgrades; hardware keys do not need to be acti-
vated.
License Activator will collect some hardware characteristics of the computer; these characteristics are required to
generate the software key, and will be stored in a .c2v file.
3. Select a location for .c2v file, type its name, and then click Save.
4. Send the .c2v file to the following email address : [email protected].
What to do next:
Using License Activator, generate a new .c2v file and send it to Eaton to the aforementioned email address. This will:
• Inform us that the activation process was successfully completed;
• Help us providing you with a new license key faster if you purchase new options for your current Visual T&D
installation.
Make sure the Visual T&D installer is copied on the client computer.
The Visual T&D Explorer and Visual T&D Diagram Editor client applications can also be installed on computers that do
not host a Visual T&D server.
To install Visual T&D applications on a client computer:
The installer will proceed with the installation of the selected Visual T&D components, along with third- party soft-
ware components that are required by Visual T&D.
6. Once the installation completes successfully, click Done.
Data log feature 5.0 and With version 4.0 of the Visual T&D software, Technical specification:
earlier the Visual T&D data log feature was redesigned Integrating Visual T&D
to store the data in a professional third-party to a database server
database engine. Data log files transfer (MN914021EN)
from previous versions does not take place
automatically. To do so, you need to use the
Visual T&D Server Configuration application.
Note that this step is required before upgrading
to version 5.1 or later database schema.
With version 5.1 of the Visual T&D software,
the Visual T&D data log feature was
redesigned for scalability improvements. If the
datalog version is between 4.0 and 5.0 then
the Visual T&D Database Migration Tool must
be used.
DCOM 4.3 and Visual T&D uses the DCOM authentication level Using DCOM with
unidentified earlier CALL by default. The DCOM authentication unidentified access
access level NONE is required if the Visual T&D Server
computer cannot recognize the calling Windows
account coming from the Visual T&D Explorer
or Diagram application. Usually it is the case
if computers are not part of a domain network,
where accounts definitions are centralized.
Communication 5.2 and later With version 5.1 and earlier of the Visual T&D
Server feature Communication Server, the configuration file
in SMP Config used an SMP 16 automation
platform by default. This platform is not
recognized anymore in the latest version of
SMP Config; therefore, it must to be manually
changed for an SMP SG-42xx automation
platform.
To make this change, you must use the SMP
Config tool installed with the latest SMP Tools
package. In addition, you have to delete the
previous versions of the configuration file
located under: C:\Users\<username>
\AppData\Roaming\Cooper Power
Systems\Visual T&D\Explorer\Param
\<sitename>\.
Note: The configuration of a Visual T&D site, which includes the specification of data sources, data points settings,
alarms, events and other site-related features, is performed using the Visual T&D Explorer client application.
1. Right-click the Visual T&D Server Agent icon in the Windows system tray.
2. If there is a check mark beside the Show status changed notifications command, click the command to deactivate
such notifications.
Note: To reactivate these notifications, click the Show status changed notifications command again to
make the check mark appear beside it.
4.1.1.2 Removing the Visual T&D server agent icon from the system tray
To remove the Visual T&D server agent icon from the system tray:
1. Right-click the Visual T&D Server Agent icon in the Windows system tray.
2. Click the Remove Agent Icon command.
Note: To restore the icon, select Windows > Programs > Eaton > Visual T&D > Visual T&D Server Agent.
To be able to access the Visual T&D server Control Panel and set up Visual T&D server properties, you must log on to
the computer with a user account that has administrative privileges.
To access the Visual T&D server Control Panel:
Privilege Description
User can edit site Allow the user to edit site configurations, and to update the current site configuration
configuration on the Visual T&D server.
User can perform control Allow the user to perform control operations through Visual T&D.
operations
User can simulate data Allow the user to put the Visual T&D server into Simulation mode, in order to simulate
transitions on the data points for engineering and commissioning purposes.
User can acknowledge Allow the user to acknowledge and clear alarms.
and clear alarms
User can set silent, Allow the user to set alarms as silent, permanent or blocked.
permanent and blocked
alarms
User can manage tags Allow the user to tag data points.
User can manage tags Allow the user to edit and delete tags that were created by other users.
added by other users
Note: This privilege can only be granted to users who have the User can man-
age tags privilege.
User can create user Allow the user to create and edit its own user events.
events and modify its own
events
User can modify user Allow the use to edit user events that were created by other users.
events created by other
users Note: This privilege can only be granted to users who have the User can create
user events and modify its own events privilege.
3. Under User List, click on the Groups folder, the name of the already configured Visual T&D groups are displayed in
the right pane.
4. Click Add; a new group is created and called New Group by default. Change the name.
5. Select this newly created group and, in the right pane, select the privileges you want to assign to this group.
6. Click OK.
A password must be assigned to each Visual T&D and Windows user account.
The network administrator creates the Windows accounts and therefore, will set the passwords with their requirements
for theses accounts.
For the Visual T&D user accounts, the Visual T&D system administrators can set the passwords' minimum length; this
length value must be larger than or equal to 6.
Visual T&D system administrators can also enforce passwords to meet specific complexity requirements, by requiring
each password to contain characters from each of the 3 following categories:
• alphabetic high caps (A to Z) or small caps (a to z)
• numeric (0 to 9)
• special characters (ex: !$%?&*)
Unless it is configured to never expire, a Visual T&D user account password expires after 42 days. If the user connects
to the Visual T&D server during the 7-day period prior to the password expiration date, the Visual T&D client application
informs him about this matter and offers him to change his password.
Note: Activating password complexity requirements does not invalidate existing passwords, thus users will be
affected only when they will change their current password.
5. Select Enable account lock if you want the account to automatically lock for 30 minutes after three (3) failed login
attempts.
6. Click OK.
It is recommended to define the password requirements for Visual T&D user accounts before creating any new account.
To create a new Visual T&D user account:
b. If you want to prevent the user from being able to change his password, select User cannot change
password.
c. If you want to prevent the password from expiring, select Password never expires; otherwise, the
password will expire after 42 days.
d. If you want to temporarily deactivate this account, select Account is disabled.
Note that a user with a disabled account will remain deactivated, even if this user is also part of an active
user group.
8. Click OK.
The user newly created is added in the list under the Users folder, in the left pane.
What to do next:
You must now grant privileges to the newly created Visual T&D user. To do that, in the right pane, under Group , select
the groups that the user should be given access to.
Windows authentication is configured as single sign-on account. You can create more than one Windows Users
accounts but the currently signed-on Windows account, the one the user used to logon to its Windows session, is the
default one. To logon with another Windows user account, the user must use the “Run as a different user” Windows
function to override the current Windows user.
To create a Windows user account in Visual T&D:
5. Using the Select Users or Groups window, find the Windows account you want to configure as a Windows user
account in Visual T&D.
6. Click OK.
The user account newly created is added in the list under the Windows Users folder, in the left pane with a user
name corresponding to its corresponding Windows account name.
What to do next:
You must now grant privileges to the newly created Windows User. To do that, in the right pane, under Group, select the
groups that the user should be given access to.
Note: This applies at the Visual T&D server authentication level. It does not disable the Windows account
itself.
5. Click OK.
In Visual T&D, two different authentication modes are allowed for Explorer and Diagram authentication.
To configure which authentication modes are allowed in Visual T&D:
4.1.4.8 Changing a Visual T&D user account password in Visual T&D Explorer
When a user authenticated himself with a Visual T&D user account in Visual T&D Explorer, It is possible for this user to
change its password in Visual T&D Explorer.
To change a Visual T&D user account password in Visual T&D Explorer:
It is possible, for a user, to logon from different workstations with the same user account.
Note: This option does not apply to the Visual T&D web HMI. With the web interface, it is always possible to use
the same credentials from different workstations.
3. Under Remote Privileges, select which operations Visual T&D users will be able to perform from a remote
computer, if they have the required privileges.
4. Click OK.
The Visual T&D SCADA Control Interlock mechanism is used with an SMP Gateway data source, to allow or forbid con-
trol operations from local substations, that is, from Visual T&D.
The SMP Gateway provides two system data points that are used by the mechanism:
_smp___localControl This binary input point indicates the state of the local control lock.
When this point has a value of 1, local control is enabled; when the value is 0, local
control is locked.
_smp___setLocalControl This binary output point is used to modify the local control lock state, from
Visual T&D or from the SCADA.
Table 9 : SMP Gateway system data points for SCADA Control Interlock
This procedure explains how to activate the Visual T&D SCADA Control Interlock mechanism, not to perform the Inter-
lock operation itself; once activated, users can then operate the corresponding SMP Gateway system data point to tog-
gle between the Local and Local/Remote operation modes.
To activate Visual T&D SCADA control interlock:
The Visual T&D server can automatically suspends the control operation privilege of a user if his workstation remains
inactive for a certain amount of time.
This function prevents unauthorized persons from performing control and tag operations in the Visual T&D Diagram
Editor or Explorer programs. After the specified timeout period, the user has to reenter his password to re-establish his
privileges.
The aforementioned timeout period can be configured using the Visual T&D server Control Panel.
To deactivate the control operation privilege timeout feature, specify a value of 0 for the timeout value.
Note: This function only works when the current user is authenticated with a Visual T&D account. Since Visual
T&D does not directly manage Windows-authenticated Visual T&D accounts, other operating system features (e.g.
Windows screen saver lock ) can be used in these situations.
In a setup where multiple users have privileges over control operations, it is possible to limit control operations to a sin-
gle user at a time. In such a case, users will need to gain exclusive access before being able to perform control opera-
tions.
To deactivate simultaneous control operations from multiple users:
4.1.7.1 Specifying how alarms and events must be managed on a given Visual T&D server
To specifying how alarms and events must be managed on a given Visual T&D server:
will be triggered immediately when an analog transition exceeds the configured deadband.
4. If you selected the Custom option, click Customize.
4.1.8.1 Specifying the folder location to store Visual T&D configuration files
• The specified path must exist and can be local or on a mapped network drive.
• Click Browse to navigate to the desired folder.
• Click Default to select the default folder path, which is set to: C:\ProgramData\Eaton\Visual T&D
\Server\.
4. Click OK.
An automatic copying process of the configuration files will then be launched and the Visual T&D server will be restarted.
If the copying process fails, the specified folder will automatically rollback to the previous folder path setting.
This procedure explains how to proceed to create a Windows account dedicated to Visual T&D automated task execu-
tion, via the Visual T&D server Control Panel.
This configuration procedure is only required if you need Visual T&D to perform automated tasks that start applications.
Such tasks are configured in Visual T&D Explorer, using the Task Manager.
3. In the User name and Password boxes, type the name and password of the Windows account that will be
dedicated to Visual T&D task execution.
4. In the Domain box, select the corresponding workgroup or domain of the account.
5. Click Validate.
6. If the account does not exist, you will be prompted to create the account (if you have sufficient privileges to do so).
The Credentials are valid message will appear if the specified credentials are those of a valid account or if the specified
account was successfully created.
Note: Specific privileges tied to this account may be required. The need for these privileges depends if the task
of type “Launch an application” is needed for the account. This is specified in the table from section Planning
Windows accounts before Visual T&D installation.
This configuration is performed from the Visual T&D server Control Panel.
This operation is performed from the Visual T&D server Control Panel and the Syslog transmitter must be activated.
4. Still under Receiver Parameters, in the Port number box, type the port number used for the Syslog message
transmission. The default port number is 514.
5. Click OK.
The following table presents the various categories of logs that can be generated by Visual T&D with the suggested Sys-
log facility and severity levels to use for each category:
This operation is performed from the Visual T&D server Control Panel and the Syslog transmitter must be activated.
Timestamp of Syslog messages are adjusted to the time zone of the receiver to display messages in local time at the
receiver side.
This operation is performed from the Visual T&D server Control Panel. The Syslog transmitter must be activated and the
Receiver Parameters must be configured.
Note: To be able to open the Visual T&D Manager, you must log on to the computer with a user account that has
administrative privileges.
Note: By default, the Need Log setting is selected for all binary points added to a site configuration; this is not
the case for newly added analog points, which can generate a large amount of transitions.
The Visual T&D server components and the Visual T&D datalog database can be installed on the same computer.
However, it is recommended to install them on different computers or, at least, on different disk drives.
4.2.2.1 Adding an SQL server database to the list of Visual T&D database servers
This procedure explains how to add a corporate Microsoft SQL server database to the list of Visual T&D database
servers in the Visual T&D Manager.
Before you begin:
Note: If Windows Authentication is selected, make sure that the corresponding Windows account is
assigned to the Visual T&D engine service.
Otherwise, if Database authentication is selected, make sure that the database server is configured to
allow mixed authentication (SQL Server and Windows Authentication).
4.2.2.2 Adding a PostgreSQL database to the list of Visual T&D database servers
This procedure explains how to add a corporate PostgreSQL database to the list of Visual T&D database servers in the
Visual T&D Manager.
To add a PostgreSQL database to the list of Visual T&D database servers:
Note: The default PostgreSQL port is 5432. The default PostgreSQL port in a earlier Visual T&D
installation is 5433.
c. In the Authentication box, select the authentication method that the Visual T&D engine will use to connect
with the database server.
Note: If Windows Authentication is selected, make sure that the corresponding Windows account is
assigned to the Visual T&D engine service.
d. Enter the credentials of the corresponding account in the Username and Password boxes
6. Modify the Database name if needed.
7. To use this database for the Visual T&D datalog, click Is active.
8. Click Apply.
This procedure explains how to configure the Visual T&D datalog settings.
To purge old data automatically:
The MultiSpeak specification is a standard for integrating enterprise application software commonly used by utilities. It
®
defines standardized communications among servers in the utility domain. Visual T&D supports MultiSpeak Specification
versions 4 and 5 which are accessible using the following URLs:
• http://<VTD server>:8095/multispeak/v4/SCADA_Server
• http://<VTD server>:8095/multispeak/v5/SCADA_Server
Where <VTD server> is the UNC name or IP addresss of the Visual T&D server.
Visual T&D implements the Supervisory Control and Data Acquisition (SCADA) Web Service endpoint. This endpoint
provides status detection, logging of analog information, and control of remote power system equipment, typically within
a substation.
Similar functionality is provided for down line devices by the distribution automation (DA) endpoint. Usually SCADA
devices are inside the substation fence and distribution automation devices are outside of the substation, but this
distinction is somewhat arbitrary and an application implementing either the SCADA or the DA endpoint could control
and monitor devices anywhere on the power system.
Please visit www.multispeak.org for more information on the MultiSpeak 4 and 5 specifications.
GetAllSCADAPoints
This method is implemented for every interface supported by Visual T&D. This method requests a list of SCADA point
definitions.
GetSCADAStatusBySCADAPointID
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This method requests the
most recent SCADA statuses for specific SCADA Status points by SCADAPointID.
GetSCADAAnalogsByDateRangeAndPointID
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This method Requests
history records for a specific SCADA Analog point by SCADAPointID within a defined time range.
RequestRegistrationID
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This service requests
from the publisher a unique registration ID that would subsequently be used to refer unambiguously to that specific
subscription. The return parameter is the registrationID, which is a string-type value. It is recommended that the server
do not implement registration in such a manner that one client can guess the registrationID of another. For instance, the
use of sequential numbers for registrationIDs is strongly discouraged.
RegisterForService
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This method establishes
a subscription using a previously requested registrationID. Subsequent calls to RegisterForService on an existing
subscription replace prior subscription details in their entirety - they do NOT add to an existing subscription. The client
should first obtain a registrationID and then register for service.
UnregisterForService
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This method deletes a
previously established subscription (registration for service) that carries the registration identifier listed in the input
parameter registrationID.
GetPublishMethods
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. The requester requests the
list of methods that are supported by the publisher. Responder returns information about failed transactions using the
result element of the response message header.
GetRegistrationInfoByID
This method is only implemented in Visual T&D for version 4 of the MultiSpeak specification. This method requests
the return of existing registration information (that means the details of what is subscribed on this subscription) for a
specific registrationID. Responder returns information about failed transactions using the result element of the response
message header. The server should return a SOAPFault if the registrationID is not valid.
Important: You must first contact Eaton if you want to purchase the Multispeak option.
5 Security hardening
Visual T&D components store application data mainly on the operating file system and in the registry. The access to
those resources can be restricted to specific Windows accounts or groups to ensure data confidentiality and also mini-
mizing software attack surface.
Note: Accounts and prescribed access rights are focusing on Visual T&D environment. Other Windows generic
and administrative accounts are usually part of the described assets. On the other hand, public and other users’
accounts should not have access to those.
Planning privileges for each resource in a restricting access mindset
To help plan the privileges for your Visual T&D environment, you must first establish your needs; the following diagram
will help you in your decision making.
VTD
VTD VTD VTD Windows
Resource Operator Database
Resource Required/Optional Server Service Engine "Users"
icon and VTD Service
Service Layer Service group
Engineer
(default)
"Read &
\%ProgramFiles(X86)%\Eaton Full Full Full execute", "
Required No access No access
\Visual T&D\ control control control List folder
content",
"Read"
Required. This
folder can be set
during installation,
No No No Full
\[Database Data]\ or afterwards. No access No access
access access access control
Default value is
[INSTALL_DRIVE]
\Visual TD Datalog\
HKLM\SOFTWARE
Full No Full
\Wow6432Node \Cybectec Required No access No access No access
control access control
\Visual Substation Server\
(default)
"Read &
HKLM\SOFTWARE
Full No Full execute", "
\Wow6432Node \Cybectec Required No access No access
control access control List folder
\Visual Substation\
content",
"Read"
Optional. Only
If Visual T&D is
Full No No
USB Port deployed with a No access No access (Default)
control access access
hardware license
dongle key.
Optional. Only
If Visual T&D is "Read", "Read",
not deployed "List No "List
\%ProgramData%\Cybectec\ No access No access No access
with a hardware folder access folder
license dongle key. content" content"
(Developer mode)
Note:
• Folders locations \[Target IMS]\ and \[Source DFR]\ are chosen by the Visual T&D Administrator.
Consider those resources only if you plan to use the “DFR” and “Export to IMS” features.
• When a resource is “optional” and does not apply to your planned Visual T&D usage, grant no access to
the corresponding account.
5.2.3 Remove Windows "Users" group or any other inherited privilege from
a folder security or registry access list
To remove Windows "Users" group or any other inherited privilege from a folder security or registry access list, logon to
the Visual T&D server with administrator privileges.
For each folder described in the table located in section Restricting access to Visual T&D server resources :
5.2.5 Specifying the Windows logon account for the Visual T&D server
service
If the Visual T&D server must connect to the database server using a Windows account, plan and configure users exe-
cuting Visual T&D services by referring to the following sections:
• Planning Windows accounts before Visual T&D installation
• Adding an SQL server database to the list of Visual T&D database servers
Also, refer to the following sections for detailed characteristics of this account.
5.2.6 Specifying the Windows logon account for the Visual T&D Engine
service
Refer to the following sections for detailed characteristics of this account:
• Planning Windows accounts before Visual T&D installation
• Restricting access to Visual T&D server resources
To specify the Windows logon account for the Visual T&D Engine service:
Note: If you are using the Multispeak interface, you must add access rights by using the following commands from
an elevated command prompt:
Netsh http delete urlacl url=http://+:8095/multispeak/v4/SCADA_Server/
Netsh http add urlacl url=http://+:8095/multispeak/v4/SCADA_Server/
user="<username>"
Netsh http delete urlacl url=http://+:8095/multispeak/v5/SCADA_Server/
Netsh http add urlacl url=http://+:8095/multispeak/v5/SCADA_Server/
user="<username>"
Where <username> must be replaced by the VTD Engine service account name. Then, restart the service.
Workstation Accounts
VTD
VTD VTD VTD Windows
Resource Operator Database
Resource Required/Optional Server Service Engine "Users"
icon and VTD Service
Service Layer Service group
Engineer
\%ProgramData%\Eaton\Visual No No No
Required Full control No access No access
T&D\ access access access
(default)
"Read &
"Read &
Execute", "
\%ProgramFiles(X86)%\Eaton No No No execute", "
Required List folder No access
\Visual T&D\ (see note below) access access access List folder
content",
content",
"Read"
"Read"
No No No
%AppData%\Eaton\Visual T&D\ Required Full control No access No access
access access access
HKCU\Software\Cybectec\Visual No No No
Required Full control No access No access
Substation Diagram\ access access access
HKCU\Software\Cybectec\Visual No No No
Required Full control No access No access
Substation Explorer\ access access access
Table 12 : Visual T&D client application resource accesses for different accounts
Workstation Accounts
HKCU\Software\Cybectec\Visual No No No
Required Full control No access No access
Substation\ access access access
Optional. Based
on local needs, No No No
Print system resources Full control No access No access
depends on local IT access access access
policies.
Table 12 : Visual T&D client application resource accesses for different accounts
Note: The Visual T&D installer sets “Write” permission to the sub folder “Program Files (x86)\Eaton\Visual T&D\Client\Libraries” for Visual T&D Diagram
Editor to manage shape libraries.
5.3.2 Add a group or user to a folder security or registry access list (client
application)
To add a group or user to a folder security or registry access list, logon to the Visual T&D server with administrator privi-
leges.
For each folder described in the table located in section Restricting access to Visual T&D client application resources :
5.3.3 Remove Windows "Users" group or any other inherited privilege from
a folder security or registry access list (client application)
To remove Windows "Users" group or any other inherited privilege from a folder security or registry access list, logon to
the Visual T&D server with administrator privileges.
For each folder described in the table located in section Restricting access to Visual T&D client application resources :
5.5.1 Allowing communication with the Visual T&D through the firewall
The following tables list the communication ports used by Visual T&D and the Visual T&D server. These tables will help
you through the access restriction process to Visual T&D server resources.
HASP HL Net license Allow this port on the Visual T&D server when the HASP
TCP 1947
key HL Net key is used for the Visual T&D application.
TCP 1432 (default) Allow this port on the server where the database
PostgreSQL database TCP 1433 ( if installed with server resides, only if you plan to use the PostgreSQL
server an earlier version of Visual database engine.
T&D)
5.5.2 Allowing communication with the Visual T&D server through DCOM
ports
To allow communication with the Visual T&D server through a restricted range of DCOM ports, follow these in-
structions:
1. Decide how many TCP ports you want to allocate to DCOM processes. Visual T&D will use as many ports as DCOM
connections with the Visual T&D Server. We recommend using a range of at least 100 ports (Recommended by
Microsoft). Other DCOM components residing on the server are also to consider. Consider a range of 20 000 and
more; refer to Microsoft sites for more information on the subject.
2. To start Dcomcnfg.exe
a. Click Windows Start button and type Dcomcnfg.exe in the search program and files field.
b. Then press Enter.
c. On the left pane from the Component Services window, browse through Component
services>Computers>My Computer.
d. In the right pane, click on the more actions arrow and select Properties from the pop up menu.
e. Select the Default Protocols tab, click on the Properties button for the DCOM Protocols section.
f. Set the desired port range.
g. Verify that the Port range assignment and Default dynamic port allocation are both set to Internet range.
3. Configure your corporate Firewall according to the previously specified port range, to allow the remote
communication for administration through UDP and TCP exception ports.
1. Click Windows Start button and type Dcomcnfg.exe in the search program and files field.
2. Then press Enter.
3. On the left pane from the Component Services window, browse through Component services>Computers>My
Computer.
4. In the right pane, Click on the more actions arrow and select Properties from the pop up menu.
5. Select the COM Security tab, click on the Edit limits button under the Access Permissions pane.
6. Verify that every non administrator Windows users or groups containing non administrator users (e.g. VTD
Operators group) are included for Remote Access. These users or groups should not be given access to the Visual
T&D Server for security purposes, but only to DCOM Servers via the DCOM Edit Limits properties.
7. In the COM Security tab, click on the Edit limits button under the Launch and Activation Permissions pane.
8. Verify that every non administrator Windows users or groups containing non administrator users (e.g. VTD
Operators group) are included for Remote Launch and Remote Activation . These users or groups should not be
given access to the Visual T&D Server for security purposes, but only to DCOM Servers via the DCOM Edit Limits
properties.
9. Click OK to close the two windows to come back to the Component services window.
10. In the left pane, in the tree control , browse through Component services>Computers>My Computer>DCOM
configuration.
11. In the middle pane, from the component list, select Cybectec Visual Substation Server and right click on it.
12. Select Properties and then select the Security tab.
13. In the Access Authorization pane, select Customize and click the Edit button.
14. Add VTD Operator group (or users) to the list and set both local and Remote privileges to Allow.
15. Remove ANONYMOUS LOGON and any other non-admin users and groups from the list.
0 - DEFAULT
3 - CALL (default)
5 - INTEGRITY
6 - PRIVACY
0 - DEFAULT
1 - NONE
2 - CONNECT Supported
Supported (CALL (Visual T&D
4.3R3 to 5.0 Supported
3 - CALL (default) level required) authentication
only)
4 - PKT
5 - INTEGRITY
Table 15 : DCOM authentication levels supported according to the Visual T&D version
6 - PRIVACY
0 - DEFAULT
1 - NONE
2 - CONNECT
Supported
Supported (CALL (Visual T&D
5.1R1 and later 3 - CALL Supported
level required) authentication
only)
4 - PKT
5 - INTEGRITY
6 - PRIVACY (default)
Table 15 : DCOM authentication levels supported according to the Visual T&D version
Note: The actual DCOM authentication level used in a Visual T&D client/server connection is set by the highest
setting between the two of them.
1. Using the Regedit application, locate and select the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE
\Wow6432Node\Cybectec\Visual Substation.
2. Create the following Dword value : DcomAuthenticationLevel
a. Set the DWORD to the value 6. This value correspond to the PRIVACY authentication level (the most
restrictive authentication level).
b. Close the Regedit application.
3. Restart the Visual T&D service.
1. Create a text file named Banner.txt. The file should have the following form:
• [Title] <Insert the Appropriate Use Banner dialog box title here>
• [Text] <Insert the appropriate use banner text here>
2. Under Title, type a title for the dialog box that may be used to display the banner.
3. Under Text, type the banner text required by the security policies of your company.
4. To display the banner, copy the banner file to the configuration files folder as set in Visual T&D Server Configuration
application.
The following screenshot presents an example of an appropriate use banner that is displayed when connecting to the
Visual T&D server.
Note:
There is a difference between the activation of the Standalone HMI mode, and the action of the computer that
enters this mode.
When the Standalone HMI mode is active, you can still log on using a Windows account that is not the dedicated
one, allowing you to use all of Windows usual functions.
The computer enters the Standalone HMI mode when you log on using the dedicated Windows account, or simply
when the computer restarts.
3. You must also decide whether to run the Diagram Editor application in the Full Screen and Kiosk modes.
4. When the Standalone HMI mode is correctly configured, all that is left is the activation of this mode, which becomes
effective upon the computer’s next startup.
1. Select Windows > Programs > Eaton Visual T&D > Visual T&D Shell Configurator.
If the Visual T&D Standalone HMI mode is currently active, you must first deactivate it to access these logon information
settings.
To specifying logon information for the Visual T&D Standalone HMI mode:
Note: If the computer is in a workgroup and the specified account does not exist, the application will
offer to create the account for you. If you accept, you must type the password again, and then type it
another time to confirm it.
d. Click Validate.
If the credentials are not valid, an error message appears besides the validation button; review the creden-
tials you provided and correct any mistake.
If these credentials are specified for a given network domain, make sure a corresponding account exists.
4. Under Visual T&D Logon Information, enter the credentials of the dedicated Visual T&D account:
a. Type the user name.
b. Type the corresponding password.
c. Click Validate.
If the credentials are not valid, an error message appears besides the validation button; review the creden-
tials you provided and correct any mistake.
Note: Make sure the account exists on the Visual T&D server, as you cannot create such an account
from the Visual T&D Shell Configurator.
5. Click OK to save the logon information and close this window.
If the Visual T&D Standalone HMI mode is currently active, you must first deactivate it to access these application set-
tings.
You must decide at configuration time which applications are available while in the Visual T&D Standalone HMI mode.
By default, both Visual T&D Explorer and Visual T&D Diagram Editor will be available, but you can select not to start one
of those two applications. You can also select some other non-Visual T&D applications.
To configuring applications for Visual T&D Standalone HMI mode:
3. Under Startup Information, select the Visual T&D client applications that you want to use while in the Standalone
HMI mode. By default, both Explorer and Diagram Editor should be selected (with a check mark). If you do not want
to start either application, clear the check box that appears beside the corresponding application name.
Note: The topmost application is the one that will be started last.
c. Click Move down if you want the selected application to be started before the application that is currently
under the selected one.
Note: The bottommost application is the one that will be started first.
d. Repeat for each application as required.
b. In the Name box, type the name of the application, as it should appear in the list.
c. In the Executable file name and path box, type the complete name and path of the application executable
file.
d. Click OK to add the application to the list.
e. Move up or down the application in the list to specify when it should be started compared to others.
f. Repeat the steps above for each application to add to the list.
6. Under Startup Information, to remove an application from the list:
a. Select the application to remove.
b. Click Remove.
Note: Visual T&D client applications cannot be removed from the list. If you want one of those not to be
started, clear its corresponding check box.
7. Under Visual T&D Diagram Options, select Start in Full Screen mode if you want Visual T&D Diagram Editor to
start in the Full Screen display mode.
8. If you selected Start in Full Screen mode, you also have the possibility to activate the Kiosk mode by selecting
Kiosk mode.
9. Click OK to save the changes.
1. In the Visual T&D Shell Configurator, click Enable Standalone HMI Mode.
2. Confirm the password of the current Windows account (the one you are currently logged on under) when requested
to do so.
Note: Note that if you log off and enter the credentials of the Windows dedicated account, the computer will
enter the Standalone HMI mode.
1. In Visual T&D Explorer or Visual T&D Diagram Editor, select File > Exit and log off.
Note: You can also leave the Standalone HMI mode by pressing and holding the SHIFT key during Windows’
startup to bypass the Windows automatic logon. At the end of the startup, instead of entering the Standalone
HMI mode, the computer will ask you enter your user name and password.
2. If the dedicated Windows account does not have administrative privileges, the Visual T&D Shell application asks for
administrative credentials. Enter the user name, password and domain of an account with such privileges, and then
click OK to log off.
Note: Since the Standalone HMI mode is still active, the computer will reenter it upon next computer restart, or
the next time you log on using the dedicated Windows account credentials.
1. Select Windows > Programs > Eaton Visual T&D > Support Assistant.
2. In the Visual T&D Support Assistant window, click Create.
3. If the proposed site configuration file is not the one that you want to back up, click the Browse button, locate the
corresponding site configuration file (.mdb), and then click Open.
4. Type the complete path and name of the folder where the backup (.zip) file will be copied, or use the corresponding
Browse button to locate and select that folder.
5. If you don't want to include system information, unselect the Include system information check box. System
information includes hardware description, list of installed drivers and other running services that the Eaton
Technical Support representative may need in order to help you.
6. Click Fetch to generate the ZIP file at the specified location.
7. Once the ZIP file was properly generated, click Close.
8. Keep a copy of the file in a secure location, per your company's backup policy.
1. Select Windows > Programs > Eaton Visual T&D > Support Assistant.
2. In the Visual T&D Support Assistant window, click Recover.
3. In the File to recover box, type the complete path and name of the backup (.zip) file, or browse the computer to find
it.
4. Select which backed up content you want to restore:
a. To restore the site configuration that was stored on the server, select Recover server files.
b. To restore the client-specific files, such as local views and queries, select Recover client files.
Note: Only client files associated to the account of the user who performed the backup will be
restored.
c. To restore custom diagram libraries that were created on this computer, select Recover Visual T&D
Diagram libraries.
Note: Unlike other client files, all diagram libraries that were created by all users will be restored.
5. To replace existing server or client files with the restored files, select Overwrite existing files; otherwise, if some of
these files already exist, the Visual T&D Support Assistant will detect file conflicts and the restore process will fail.
6. To rename the restored site and save it into a new folder (named after the new site name), select Rename the
recovered site and the new name into the corresponding box.
7. When you are ready to start the restore process, click Recover.
8. Once the restore process is completed, click Close.
This procedure explains how to proceed to migrate an existing Legacy license key towards an Eaton license key.
To migrate your legacy license key to an Eaton license key:
You will then receive an email with the new activation ID(s) for the Eaton license.
3. Follow the procedure in section Activating Visual T&D using Eaton License to activate the license options.
You will receive another email which includes the corresponding .v2c file. This .v2c file will be used to deactivate the
legacy license key.
4. Save the .v2c file on the Visual T&D server computer.
5. In License Activator, click Apply V2C.
6. Select the .v2c file received from Eaton, and then click OK.
7. Restart the Visual T&D Server.
8. Using License Activator, generate a new .c2v file and send it to Eaton to the email address mentioned in step 2. This
last step will confirm that the legacy license key was correctly deactivated.
This procedure explains how to upgrade an existing Eaton license key using the Visual T&D Manager application.
To upgrade your current Eaton license key:
You will receive an email from Eaton with new activation ID(s).
2. Retrieve the information containing the new activation ID(s) received from Eaton and send it back along with the
desired new options.
3. Follow the procedure in section Activating Visual T&D using Eaton License to activate the new options.
Note: If the Visual T&D server has Internet access, the online activation option can be used to accelerate the
process.
This procedure explains how to proceed to move an existing Eaton license key to another machine.
To move your current Eaton license key to another machine:
Note: The list of activation IDs can be found in the Options page. Make sure to copy all the activation
IDs for future reactivation.
d. In the Options section, check the option Deactivate License.
e. Use the online or offline mode to apply the license deactivation.
f. In the Options page, you can verify that the license options are deactivated for your existing Visual T&D
system.
2. On the new machine:
a. Access Visual T&D Manager.
b. Select the Licensing tab.
c. In the Activation ID section, click the Add button and enter the activation ID that must be reactivated on
this new machine. Be careful not to copy any leading or trailing spaces. Repeat the same process for all
activation IDs.
d. Make sure to uncheck the option Deactivate License
e. Use the online or offline mode to apply the license activation.
f. In the Options page, you can verify that the license options are activated for your new Visual T&D system.
Restriction:
• Hasp SL Software keys are available for Visual T&D versions 4.1 or later.
• Hasp HL Net Hardware keys are available for Visual T&D 4.3R4 or later.
Visual T&D license keys are activated and upgraded using the License Activator utility program.
This section describes how the Visual T&D program is selecting its license depending on available keys and their valid-
ity.
An HL type license key that was used on a previous Visual T&D session is set as a persistent key (the key ID is used as
reference). It is preferable not to switch from one license key to another when many license keys are accessible from a
given Visual T&D host system because license options may be different from one license key to another.
For this reason, when more than one license key are available for a given Visual T&D host system, the priority goes to
the persistent license key. If another key type is temporarily used, the HL persistent key ID will be remembered by Visual
T&D so that the next time the server starts, the priority will be given to persistent key. It is however possible to remove
access to the persistent key to force the system to select another license key with lower priority.
Note: In order for the Visual T&D application to change the license key already in use, the Visual T&D server
service must be stopped and restarted (Windows > Administrative Tools > Services).
The key selection process is the following:
• When the Visual T&D server starts, it first checks for a persistent HL type key ID. If such a key is accessible, the
Visual T&D application is licensed with the HL type key (HL or HL Net).
• If there is no persistent key, the priority goes first to a HL key and then to a HL Net key.
Note: If there is an accessible HL Net key but no session on that key is available, then the Visual T&D
application is not licensed. There will be no search performed for a legacy or SL license key.
• If no HL type key is accessible, the system looks for a HL legacy key. If such a key is accessible, the Visual T&D
application is licensed with a HL legacy key.
• If still no valid HL key was found, the system then looks for a valid SL key. If a SL key is found, the Visual T&D
application is licensed with a SL key.
• Finally, if no valid SL key was found, the Visual T&D application is not licensed. The system falls into developer
mode.
Selected license key type What needs to be done to force the use of a lower priority license key
Remove the key from the USB port, then stop and restart the Visual T&D server
HASP HL
service and restart the Visual T&D server.
Remove the key from the USB port, then stop and restart the Visual T&D server
HL Legacy
service. Restart the Visual T&D server.
Stop the Sentinel LDK license Manager service (Windows > Administrative Tools >
HASP SL Services), then restart the Visual T&D server. Because no license will be found, the
system will fall into developer mode.
Table 16 : Forcing the Visual T&D server to choose a license key with a lower priority
7.2.3.2 The SafeNet Web tool to manage the HASP HL Net key
The SafeNet web tool called the Sentinel Admin Control Center (ACC) is installed by the Visual T&D installer and
accessible at the following URL: http://127.0.0.1:1947. For the Visual T&D application, the web tool is mainly used to
manage access, control sessions and troubleshoot problems with the HASP HL Net license key. It is however possible
to also visualize the availability of the HASP SL and HL license keys locally and on the network.
The next sections describe how to use the ACC for the Visual T&D usage; they explain how to:
• Validate the availability of a HASP license key (SL, HL and HL Net keys)
• Setup security for remote configuration access for the HASP HL Net key
• Setup the Visual T&D host computer to find HASP HL Net keys on the network
• Setup remote Visual T&D host computers to access the HASP HL Net key
• Setup users allowed to access the HASP HL Net key
• Consult active sessions on a HASP HL Net key
Note: The SafeNet web tool provides a comprehensive help feature. For this reason, detailed explanations about
the web tool content is not provided in this manual.
To be able to visualize available license keys, Visual T&D computers and users must be allowed access to the License
Manager of the computer hosting the license key. Refer to sections Setting up remote host computers from the local
ACC and Setting up users access from the key's local ACC for information on how to manage these accesses.
To verify the availability of a license key:
1. Connect to the SafeNet web tool called the ACC at the following URL: http://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Configuration.
3. Select the Network tab, then on the Network Visibility pane, select All Network Adapters.
4. On the Options field, on the left side of the web page, select Sentinel Keys.
5. The table, displayed on the web page, shows all license keys that the Visual T&D host system has access to.
6. The Actions column, displays different buttons to provide further information about the specific key.
Note: In the Key Type column, if the key is an HL type, the specific model is displayed
7.2.3.2.2 Setting up security for remote configuration access for the HASP HL Net key
Use this procedure to allow or remove remote access to the ACC of the computer where the HASP HL Net key is physi-
cally connected (local). When remote access is enabled, remote users can access and perform actions on the HASP HL
Net key' ACC.
Before you begin:
To allow remote access to the ACC of the computer hosting the HASP HL Net key, the user must access the ACC
locally. However, removing the remote access can be performed from a remote computer.
To Set up security for remote configuration access for the HASP HL Net key:
1. Connect to the SafeNet web tool called the ACC at the following URL: http://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Configuration.
3. Select the Basic Settings tab.
4. Allowing access to the key's local ACC to remote users must be performed locally: If you want remote ACC to
access the local ACC,
a. Select Allow Remote Access to ACC.
b. Click on the Submit button.
c. Select the Network tab.
d. On the Network Visibility pane, select All Network Adapters.
e. Click on the Submit button.
Note: Other configuration settings can be adjusted according to the user's needs, refer to the SafeNet web
tool's help documentation for that matter.
5. To remove access to the HASP HL Net key's local ACC to remote users (can be performed remotely):
a. Unselect Allow Remote Access to ACC
b. Click on the Submit button.
1. Connect to the SafeNet web tool called the ACC at the following URL: http://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Configuration.
3. Select the Access to Remote License Managers tab.
4. Select Allow Access to Remote Licenses.
5. Various options can be chosen to search for remote licenses, they are:
a. Select Broadcast Search for Remote Licenses to enable the computer to search for remote License
Managers on the local network.
Note: The broadcast uses random UDP port, this may be an issue with certain firewalls.
b. Define specific computers that may be searched on the local network by writing the IP address or machine
name of these computers in the Specify Search Parameters field, using a different line for each computer.
c. Combine option a and option b.
6. Click the Submit button.
Note: The Aggressive Search for Remote Licenses parameter can also be selected in case of trouble with
firewalls.
When enabled, access is allowed by default to all computers. If computer restrictions are to be set, the specific IP
address or computer name of the computer(s) you want to give or deny access to must be entered in the Access
Restrictions field, before the allow=all line. Examples will be shown for both cases.
To set up remote host computers from the local ACC:
1. Connect to the SafeNet web tool of the computer hosting the HASP HL Net key, called the ACC, at the following
URL: http://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Configuration.
3. Select the Access from Remote Clients tab.
4. Select Allow Access from Remote Clients.
5. To allow access only to specific computers (by default access is allowed to all computers):
a. You must know the IP addresses or computer names of the computer(s) you want to give access to. The
Show Recent Client Access button can be helpful to select these computers if they already accessed
the License Manager. In this case, click on the allow button next to the IP address or computer name.
Otherwise, write the IP addresses or computer names manually.
b. Then, the line deny=all must be added before the allow=all line, to cancel the allow=all line, which is
permanent.
The example below shows a configuration that allow access only to Computer A and Computer B.
The example below show a configuration that allow access to all computers except for Computer A and
Computer B.
Access is allowed by default to all users. If user restrictions are to be set, the specific usernames, hostnames or
user@host names you want to give or deny access to must be entered in the User Restrictions field, before the
allow=all @all line. Examples will be shown for both cases.
To set up users access from the key's local ACC:
1. Connect to the SafeNet web tool of the computer hosting the HASP HL Net key, called the ACC, at the following
URL: http://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Configuration.
3. Select the Users tab.
4. To allow access only to specific users (by default access is allowed to all users):
a. You must know the usernames, hostnames or user@host names you want to give access to. The Show
Recent Users button can be helpful to select users if they already accessed the License Manager. In this
case, click on the allow button next to the username, hostname or user@host name. Otherwise, write the
names manually.
b. Then, the line deny=all must be added before the allow=all line, to cancel the allow=all line, which is
permanent.
The example below shows a configuration that allow access only to User A and system users.
The example below show a configuration that allow access to all users except for User A and User B.
1. Connect to the SafeNet web tool called the ACC at the following URL: https://127.0.0.1:1947.
2. On the Options field, on the left side of the web page, select Sentinel Keys.
3. Locate the HASP HL Net key (Red key logo) associated with the targeted Visual T&D system (the Vendor or Key ID
can be helpful for identifying the right key).
4. The number of open sessions for the selected key is displayed under the Sessions column. When there is at least
one active session, a Sessions button is available under the Actions column of the key's local ACC.
Note: The Visual T&D system offers different options and characteristics, these are identified as features for a
given product on the SafeNet web tool pages. The number of sessions displayed under the Sessions column
correspond to the number of Visual T&D features multiplied by the number of users logged in. For example,
if three (3) users are using Visual T&D, all with eight (8) features, the number displayed under the Sessions
column would be twenty-four (24).
5. Under the # Location column, verify, for the selected key, if the key is local or on a remote computer. If it is on
a remote computer, the machine name of the computer is displayed. To be able to access the key's Visual T&D
sessions page, the user must access the key's local ACC.
6. If you are already local, jump to step 8. If you are remote, click on the machine name of the selected key to open
the key's local ACC in a new window. If you are denied permission to the key's local ACC, refer to sections Setting
up security for remote configuration access for the HASP HL Net key, Setting up a Visual TD host computer to find
HASP HL Net keys and Setting up users access from the key's local ACC .
7. In the newly open window, locate the Hasp HL Net key associated with the targeted Visual T&D system. Under the #
Location column, it should be written Local. Now you have access to the Session page located under the Actions
column .
8. Under the Actions column, click on the Sessions button. For the specific key, active sessions for each features are
displayed.
The License Activator utility program is provided by Eaton for the generation of license keys for Eaton software products.
Two types of license keys are available: hardware keys and software keys.
A hardware key does not require to be activated: you just need to connect it to the computer that hosts the Eaton
software. However, you must use the License Activator program if you need to upgrade the license of such a key (for
example, when you purchase an additional software option or increase the maximum number of data points supported
by the software).
Software keys are generated based on hardware characteristics of the computer that hosts the Eaton software product.
As a result, you must use the License Activator program to generate a customer-to-vendor (.c2v) file that will include that
information and send this file to Eaton. In response, you will receive a vendor-to-customer (.v2c) file that includes the
software key information: using License Activator, you can then use this .v2c file to activate the software key. License
upgrades are performed the same way.
7.2.3.4 Upgrading your current Visual T&D license using License Activator
The following procedure explains how to proceed to upgrade an existing Visual T&D license key using the License Acti-
vator program.
Before you begin:
4. Select a location for .c2v file, type its name, and then click Save.
5. Send the .c2v file to the following email address : [email protected].
What to do next:
Using License Activator, generate a new .c2v file and send it to Eaton to the aforementioned email address. This will:
• Inform us that the activation process was successfully completed;
• Help us providing you with a new license key faster if you purchase new options for your current Visual T&D
installation.
Category Description
Intended Use & The guidance provided for the secure deployment of the Visual T&D software components
Deployment Context are focused on the Visual T&D itself, by pointing which elements of the operating system
are used by Visual T&D and guiding the system administrator and integrator on the most
secure way to deploy Visual T&D software components.
Asset Management Keeping track of software and hardware assets in your environment is a per-requisite
for effectively managing cybersecurity. Eaton recommends that you maintain an asset
inventory that uniquely identifies each important component. To facilitate this, Visual T&D
supports the following identifying information: publisher, name and version.
This information is available on the What’s new page of the Visual T&D installation.
Category Description
Defense in Depth Defense in Depth basically means applying multiple counter-measures for mitigating
risks, in a layered or step wise manner. A layered approach to security as shown in the
below diagram is what is recommended. Defense in Depth is the responsibility of both the
manufacturer and the customer.
Risk Assessment Eaton recommends conducting a risk assessment to identify and assess reasonably
foreseeable internal and external risks to the confidentiality, availability and integrity of the
system | device and its environment. This exercise should be conducted in accordance
with applicable technical and regulatory frameworks such as IEC 62443 and NERC-CIP.
The risk assessment should be repeated periodically.
Physical Security An attacker with unauthorized physical access can cause serious disruption to system/
device functionality. Additionally, Industrial Control Protocols don’t offer cryptographic
protections, making ICS and SCADA communications especially vulnerable to threats to
their confidentiality. Physical security is an important layer of defense in such cases. Visual
T&D is designed to be deployed and operated in a physically secure location. Following
are some best practices that Eaton recommends to physically secure your system/device:
• Secure the facility and equipment rooms or closets with access control mechanisms
such as locks, entry card readers, guards, man traps, CCTV, etc. as appropriate.
• Restrict physical access to cabinets and/or enclosures containing Visual T&D and the
associated system. Monitor and log the access at all times.
• Physical access to the telecommunication lines and network cabling should be
restricted to protect against attempts to intercept or sabotage communications. It’s a
best practice to use metal conduits for the network cabling running between equipment
cabinets.
• Do not connect removable media (e.g., USB devices, SD cards, etc.) for any operation
(e.g., firmware upgrade, configuration change, or boot application change) unless the
origin of the media is known and trusted.
• Before connecting any portable device through a USB port or SD card slot, scan the
device for malware and viruses.
Category Description
COTS Platform Eaton recommends that customers harden third-party commercial off-the-shelf (COTS)
Security operating systems or platforms that are used to run Eaton applications / products (e.g.,
third party hardware, operating systems and hypervisors, such as those made available by
Dell, Microsoft, VMware, Cisco, etc.).
• Eaton recommends that customers refer to the COTS vendor’s documentation for
guidance on how to harden these components.
• Vendor-neutral guidance is made available by the Center for Internet Security https://
www.cisecurity.org/
Irrespective of the platform, customers should consider the following best practices:
• Install all security updates made available by the COTS manufacturer.
• Change default credentials upon first login.
• Disable or lock unused built-in accounts.
• Limit use of privileged generic accounts (e.g., disable interactive login).
• Change default SNMP community strings.
• Restrict SNMP access using access control lists.
• Disable unneeded ports & services.
Account Management Logical access to the system/device should be restricted to legitimate users, who should
be assigned only the privileges necessary to complete their job roles/functions. Some of
the following best practices may need to be implemented by incorporating them into the
organization’s written policies:
• Ensure default credentials are changed upon first login. Visual T&D should not be
deployed in production environments with default credentials, as default credentials
are publicly known.
• No account sharing – Each user should be provisioned a unique account instead of
sharing accounts and passwords. Security monitoring/logging features in the product
are designed based on each user having a unique account. Allowing users to share
credentials weakens security.
• Restrict administrative privileges - Attackers seek to gain control of legitimate
credentials, especially those for highly privileged accounts. Administrative privileges
should be assigned only to accounts specifically designated for administrative duties
and not for regular use.
• Leverage the roles / access privileges to provide tiered access to the users as per
the business /operational need. Follow the principle of least privilege (allocate the
minimum authority level and access to system resources required for the role).
• Perform periodic account maintenance (remove unused accounts).
• Ensure password length, complexity and expiration requirements are appropriately
set, particularly for all administrative accounts (e.g., minimum 10 characters, mix of
upper- and lower-case and special characters, and expire every 90 days, or otherwise
in accordance with your organization’s policies).
• Enforce session time-out after a period of inactivity.
Category Description
Time Synchronization Many operations in power grids and IT networks heavily depend on precise timing
information.
Ensure the system clock is synchronized with an authoritative time source (using manual
configuration, NTP, SNTP, or IEEE 1588).
Network Security Visual T&D supports network communication with other devices in the environment.
This capability can present risks if it’s not configured securely. Following are Eaton
recommended best practices to help secure the network. Additional information about
various network protection strategies is available in Eaton Cybersecurity Considerations
for Electrical Distribution Systems [R1].
Eaton recommends segmentation of networks into logical enclaves, denying
traffic between segments except that which is specifically allowed, and restricting
communication to host-to-host paths (for example, using router ACLs and firewall rules).
This helps to protect sensitive information and critical services and creates additional
barriers in the event of a network perimeter breach. At a minimum, a utility Industrial
Control Systems network should be segmented into a three-tiered architecture (as
recommended by NIST SP 800-82[R3]) for better security control.
Eaton recommends opening only ports that are required for operations and protect the
network communication using network protection systems like firewalls and intrusion
detection systems / intrusion prevention systems. Use the information below to configure
your firewall rules to allow access needed for Visual T&D to operate smoothly.
See section: Exception for communication ports.
Remote Access Remote access to devices/systems creates another entry point into the network. Strict
management and validation of termination of such access is vital for maintaining control
over overall ICS security.
See section: Remote Visual T&D server management.
Logging and Event • Eaton recommends logging all relevant system and application events, including all
Management administrative and maintenance activities.
• Logs should be protected from tampering and other risks to their integrity (for example,
by restricting permissions to access and modify logs, transmitting logs to a security
information and event management system, etc.).
• Ensure that logs are retained for a reasonable and appropriate length of time.
• Review the logs regularly. The frequency of review should be reasonable, taking into
account the sensitivity and criticality of the system | device and any data it processes.
Category Description
Vulnerability Scanning It is possible to install and use third-party software with Visual T&D . Any known critical
or high severity vulnerabilities on third party component/libraries used to run software /
applications should be remediated before putting the system/device into production.
• Eaton recommends running a vulnerability scan to identify known vulnerabilities for
software used with the product. For COTS components (e.g., applications running
on Windows), vulnerabilities can be tracked on the National Vulnerability Database
(NVD), available at https://nvd.nist.gov/.
• Keep software updated by monitoring security patches made available by COTS
vendors and installing them as soon as possible.
Note: Many compliance frameworks and security best practices require a monthly
vulnerability review. For many non-COTS products vulnerabilities will be communi-
cated directly through the vendor site.
Malware Defenses Eaton recommends deploying adequate malware defenses to protect the product or the
platforms used to run the Eaton product.
Secure Maintenance The system/device includes documentation to allow a service engineer with help from site
administrator to trouble shoot the system/device functionality.
See section: Visual T&D server maintenance.
Best Practices
Update software prior to putting the system/device into production. Thereafter, apply
software patches and updates regularly.
Eaton publishes patches and updates for its products to protect them against
vulnerabilities that are discovered. Eaton encourages customers to maintain a consistent
process to promptly monitor for and install new firmware updates.
Please check Eaton’s cybersecurity website for information bulletins about available
firmware and software updates.
See section: About Windows automatic updates.
Sensitive Information Eaton recommends that sensitive information (i.e. connectivity, log data, personal
Disclosure information) that may be stored by Visual T&D be adequately protected through the
deployment of organizational security practices.
8.2 References
[R1] Cybersecurity Considerations for Electrical Distribution Systems (WP152002EN):http://www.eaton.com/ecm/
groups/public/@pub/@eaton/@corp/documents/content/pct_1603172.pdf
[R2] Cybersecurity Best Practices Checklist Reminder (WP910003EN):http://www.cooperindustries.com/content/
dam/public/powersystems/resources/library/1100_EAS/WP910003EN.pdf
[R3] NIST SP 800-82 Rev 2, Guide to Industrial Control Systems (ICS) Security, May 2015:
https://ics-cert.us-cert.gov/Standards-and-References
[R4] National Institute of Technology (NIST) Interagency “Guidelines on Firewalls and Firewall
Policy, NIST Special Publication 800-41”, October 2009: http://nvlpubs.nist.gov/nistpubs/Legacy/SP/
nistspecialpublication800-41r1.pdf
[R5] NIST SP 800-88, Guidelines for Media Sanitization, September 2006:http://ws680.nist.gov/publication/
get_pdf.cfm?pub_id=50819
[R6] Cybersecurity Best Practices for Modern Vehicles - NHTSAhttps://www.nhtsa.gov/staticfiles/nvs/
pdf/812333_CybersecurityForModernVehicles.pdf
[R7] A Summary of Cybersecurity Best Practices - Homeland Securityhttps://www.hsdl.org/?view&did=806518
[R8] Characterization of Potential Security Threats in Modern Automobiles - NHTSA
https://www.nhtsa.gov/DOT/NHTSA/NVS/Crash%20Avoidance/Technical
%20Publications/2014/812074_Characterization_PotentialThreatsAutos(1).pdf
[R9] Threat Modeling for Automotive Security Analysishttp://nvlpubs.nist.gov/nistpubs/Legacy/SP/
nistspecialpublication800-41r1.pdf
Appendix
External libraries licensing descriptions
The Visual T&D software contains some code and class libraries from third party vendors or open source communi-
ties.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Npgsql
Copyright (c) 2002-2023, Npgsql
Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and
without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the
following two paragraphs appear in all copies.
IN NO EVENT SHALL NPGSQL BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS
SOFTWARE AND ITS DOCUMENTATION, EVEN IF Npgsql HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
NPGSQL SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND Npgsql HAS NO OBLIGATIONS TO PROVIDE
MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
ImageMagick
Copyright 1999-2021 ImageMagick Studio LLC, a non-profit organization dedicated to making software imaging
solutions freely available.
1. Definitions.
License shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1
through 9 of this document.
Licensor shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
Legal Entity shall mean the union of the acting entity and all other entities that control, are controlled by, or are
under common control with that entity. For the purposes of this definition, control means (i) the power, direct or
indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership
of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
You (or Your) shall mean an individual or Legal Entity exercising permissions granted by this License.
Source form shall mean the preferred form for making modifications, including but not limited to software source
code, documentation source, and configuration files.
Object form shall mean any form resulting from mechanical transformation or translation of a Source form,
including but not limited to compiled object code, generated documentation, and conversions to other media
types.
Work shall mean the work of authorship, whether in Source or Object form, made available under the License,
as indicated by a copyright notice that is included in or attached to the work (an example is provided in the
Appendix below).
Derivative Works shall mean any work, whether in Source or Object form, that is based on (or derived from)
the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a
whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works
that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works
thereof.
Contribution shall mean any work of authorship, including the original version of the Work and any modifications
or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion
in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the
copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written
communication sent to the Licensor or its representatives, including but not limited to communication on
electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on
behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that
is conspicuously marked or otherwise designated in writing by the copyright owner as Not a Contribution.
Contributor shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been
received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to
reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work
and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to
You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section)
patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such
license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was
submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent
infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the
date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any
medium, with or without modifications, and in Source or Object form, provided that You meet the following
conditions:
a. You must give any other recipients of the Work or Derivative Works a copy of this License; and
b. You must cause any modified files to carry prominent notices stating that You changed the files; and
c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do not
pertain to any part of the Derivative Works; and
d. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You
distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the
following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source
form or documentation, if provided along with the Derivative Works; or, within a display generated by the
Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE
file are for informational purposes only and do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text
from the Work, provided that such additional attribution notices cannot be construed as modifying the
License.
You may add Your own copyright statement to Your modifications and may provide additional or different license
terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works
as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions
stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for
inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any
additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of
any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or
product names of the Licensor, except as required for reasonable and customary use in describing the origin of
the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the
Work (and each Contributor provides its Contributions) on an AS IS BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are
solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks
associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract,
or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in
writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or
consequential damages of any character arising as a result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction,
or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility
of such damages.
9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for,
acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License.
However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility,
not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor
harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting
any such warranty or additional liability.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Apache
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1
through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the
License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are
under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or
indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership
of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software
source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form,
including but not limited to compiled object code, generated documentation, and conversions to other media
types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License,
as indicated by a copyright notice that is included in or attached to the work (an example is provided in the
Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from)
the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a
whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works
that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works
thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any
modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf
of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal,
or written communication sent to the Licensor or its representatives, including but not limited to communication
on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on
behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that
is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been
received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to
reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work
and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to
You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section)
patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such
license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was
submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent
infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the
date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any
medium, with or without modifications, and in Source or Object form, provided that You meet the following
conditions:
a. You must give any other recipients of the Work or Derivative Works a copy of this License; and
b. You must cause any modified files to carry prominent notices stating that You changed the files; and
c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do not
pertain to any part of the Derivative Works; and
d. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You
distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the
following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source
form or documentation, if provided along with the Derivative Works; or, within a display generated by the
Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE
file are for informational purposes only and do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text
from the Work, provided that such additional attribution notices cannot be construed as modifying the
License.
You may add Your own copyright statement to Your modifications and may provide additional or different license
terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works
as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions
stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for
inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any
additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of
any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or
product names of the Licensor, except as required for reasonable and customary use in describing the origin of
the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the
Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are
solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks
associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract,
or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in
writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or
consequential damages of any character arising as a result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction,
or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility
of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof,
You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability
obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree
to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against,
such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
MIT
Permission is hereby granted, free of charge, to any person obtaining a copy of _____ (the "Software"), to deal in
the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies
or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL _____ BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Code Project
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CODE PROJECT OPEN
LICENSE ("LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW.
ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS
PROHIBITED.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HEREIN, YOU ACCEPT AND AGREE TO BE BOUND
BY THE TERMS OF THIS LICENSE. THE AUTHOR GRANTS YOU THE RIGHTS CONTAINED HEREIN IN
CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO
ACCEPT AND BE BOUND BY THE TERMS OF THIS LICENSE, YOU CANNOT MAKE ANY USE OF THE WORK.
1. Definitions.
a. "Articles" means, collectively, all articles written by Author which describes how the Source Code and
Executable Files for the Work may be used by a user.
b. "Author" means the individual or entity that offers the Work under the terms of this License.
c. "Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works.
d. "Executable Files" refer to the executables, binary files, configuration and any required data files
included in the Work.
e. "Publisher" means the provider of the website, magazine, CD-ROM, DVD or other medium from or by
which the Work is obtained by You.
f. "Source Code" refers to the collection of source code and configuration files used to create the
Executable Files.
g. "Standard Version" refers to such a Work if it has not been modified, or has been modified in accordance
with the consent of the Author, such consent being in the full discretion of the Author.
h. "Work" refers to the collection of files distributed by the Publisher, including the Source Code, Executable
Files, binaries, data files, documentation, whitepapers and the Articles.
i. "You" is you, an individual or entity wishing to use the Work and exercise your rights under this License.
2. Fair Use/Fair Use Rights. Nothing in this License is intended to reduce, limit, or restrict any rights arising from
fair use, fair dealing, first sale or other limitations on the exclusive rights of the copyright owner under copyright
law or other applicable laws.
3. License Grant. Subject to the terms and conditions of this License, the Author hereby grants You a worldwide,
royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in
the Work as stated below:
a. You may use the standard version of the Source Code or Executable Files in Your own applications.
b. You may apply bug fixes, portability fixes and other modifications obtained from the Public Domain or
from the Author. A Work modified in such a way shall still be considered the standard version and will be
subject to this License.
c. You may otherwise modify Your copy of this Work (excluding the Articles) in any way to create a
Derivative Work, provided that You insert a prominent notice in each changed file stating how, when and
where You changed that file.
d. You may distribute the standard version of the Executable Files and Source Code or Derivative Work in
aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software
distribution.
e. The Articles discussing the Work published in any form by the author may not be distributed or
republished without the Author's consent. The author retains copyright to any such Articles. You may use
the Executable Files and Source Code pursuant to this License but you may not repost or republish or
otherwise distribute or make available the Articles, without the prior written consent of the Author.
Any subroutines or modules supplied by You and linked into the Source Code or Executable Files of this Work
shall not be considered part of this Work and will not be subject to the terms of this License.
4. Patent License. Subject to the terms and conditions of this License, each Author hereby grants to You a
perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent
license to make, have made, use, import, and otherwise transfer the Work.
5. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following
restrictions:
a. You agree not to remove any of the original copyright, patent, trademark, and attribution notices and
associated disclaimers that may appear in the Source Code or Executable Files.
b. You agree not to advertise or in any way imply that this Work is a product of Your own.
c. The name of the Author may not be used to endorse or promote products derived from the Work without
the prior written consent of the Author.
d. You agree not to sell, lease, or rent any part of the Work. This does not restrict you from including the
Work or any part of the Work inside a larger software distribution that itself is being sold. The Work by
itself, though, cannot be sold, leased or rented.
e. You may distribute the Executable Files and Source Code only under the terms of this License, and
You must include a copy of, or the Uniform Resource Identifier for, this License with every copy of the
Executable Files or Source Code You distribute and ensure that anyone receiving such Executable
Files and Source Code agrees that the terms of this License apply to such Executable Files and/or
Source Code. You may not offer or impose any terms on the Work that alter or restrict the terms of this
License or the recipients' exercise of the rights granted hereunder. You may not sublicense the Work.
You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may
not distribute the Executable Files or Source Code with any technological measures that control access
or use of the Work in a manner inconsistent with the terms of this License.
f. You agree not to use the Work for illegal, immoral or improper purposes, or on pages containing illegal,
immoral or improper material. The Work is subject to applicable export laws. You agree to comply with all
such laws and regulations that may apply to the Work after Your receipt of the Work.
6. Representations, Warranties and Disclaimer. THIS WORK IS PROVIDED "AS IS", "WHERE IS" AND "AS
AVAILABLE", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OR GUARANTEES.
YOU, THE USER, ASSUME ALL RISK IN ITS USE, INCLUDING COPYRIGHT INFRINGEMENT, PATENT
INFRINGEMENT, SUITABILITY, ETC. AUTHOR EXPRESSLY DISCLAIMS ALL EXPRESS, IMPLIED OR
STATUTORY WARRANTIES OR CONDITIONS, INCLUDING WITHOUT LIMITATION, WARRANTIES OR
CONDITIONS OF MERCHANTABILITY, MERCHANTABLE QUALITY OR FITNESS FOR A PARTICULAR
PURPOSE, OR ANY WARRANTY OF TITLE OR NON-INFRINGEMENT, OR THAT THE WORK (OR ANY
PORTION THEREOF) IS CORRECT, USEFUL, BUG-FREE OR FREE OF VIRUSES. YOU MUST PASS THIS
DISCLAIMER ON WHENEVER YOU DISTRIBUTE THE WORK OR DERIVATIVE WORKS.
7. Indemnity. You agree to defend, indemnify and hold harmless the Author and the Publisher from and against
any claims, suits, losses, damages, liabilities, costs, and expenses (including reasonable legal or attorneys’ fees)
resulting from or relating to any use of the Work by You.
8. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL
THE AUTHOR OR THE PUBLISHER BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE
OR THE USE OF THE WORK OR OTHERWISE, EVEN IF THE AUTHOR OR THE PUBLISHER HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
9. Termination.
a. This License and the rights granted hereunder will terminate automatically upon any breach by You of
any term of this License. Individuals or entities who have received Derivative Works from You under this
License, however, will not have their licenses terminated provided such individuals or entities remain in
full compliance with those licenses. Sections 1, 2, 6, 7, 8, 9, 10 and 11 will survive any termination of this
License.
b. If You bring a copyright, trademark, patent or any other infringement claim against any contributor over
infringements You claim are made by the Work, your License from such contributor to the Work ends
automatically.
c. Subject to the above terms and conditions, this License is perpetual (for the duration of the applicable
copyright in the Work). Notwithstanding the above, the Author reserves the right to release the Work
under different license terms or to stop distributing the Work at any time; provided, however that any
such election will not serve to withdraw this License (or any other license that has been, or is required to
be, granted under the terms of this License), and this License will continue in full force and effect unless
terminated as stated above.
10. Publisher. The parties hereby confirm that the Publisher shall not, under any circumstances, be responsible for
and shall not have any liability in respect of the subject matter of this License. The Publisher makes no warranty
whatsoever in connection with the Work and shall not be liable to You or any party on any legal theory for any
damages whatsoever, including without limitation any general, special, incidental or consequential damages
arising in connection to this license. The Publisher reserves the right to cease making the Work available to You
at any time without notice
11. Miscellaneous.
a. This License shall be governed by the laws of the location of the head office of the Author or if the Author
is an individual, the laws of location of the principal place of residence of the Author.
b. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the
validity or enforceability of the remainder of the terms of this License, and without further action by the
parties to this License, such provision shall be reformed to the minimum extent necessary to make such
provision valid and enforceable.
c. No term or provision of this License shall be deemed waived and no breach consented to unless such
waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
d. This License constitutes the entire agreement between the parties with respect to the Work licensed
herein. There are no understandings, agreements or representations with respect to the Work not
specified herein. The Author shall not be bound by any additional provisions that may appear in any
communication from You. This License may not be modified without the mutual written agreement of the
Author and You.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Librdkafka
Copyright (c) 2012-2022, Magnus Edenhill.
https://github.com/edenhill/librdkafka
librdkafka is a C library implementation of the Apache Kafka protocol, providing Producer, Consumer and Admin
clients. It was designed with message delivery reliability and high performance in mind, current figures exceed 1
million msgs/second for the producer and 3 million msgs/second for the consumer.
librdkafka is licensed under the 2-clause BSD license.
KAFKA is a registered trademark of The Apache Software Foundation and has been licensed for use by librdkafka.
librdkafka has no affiliation with and is not endorsed by The Apache Software Foundation.
We warrant that you will receive ongoing free email support, one year free bugs fixing and one year free upgrades to
new versions.
SqlApi++
SQLAPI++ Library License Agreement and Warranty
You should carefully read the following terms and conditions before using this software. Your use of this software
indicates your acceptance of this license agreement and warranty.
License Agreement
You have the non-exclusive right to use the library. The Company retains all title and ownership of the library.
Evaluation
The SQLAPI++ library is distributed as shareware. You can use the library for evaluation purposes without charge
for unlimited period. The evaluation version has no limits or functional differences from registered version, but it will
display registration messages occasionally.
While in evaluation you may not distribute your applications written with trial version of SQLAPI++ library.
Registered Versions
You have to purchase SQLAPI++ Personal license for every developer, or one Site license for up to 10 developers in
your company or one Site+ license for unlimited number of developers in your company.
You may distribute, directly and indirectly, applications written with SQLAPI++ (including SQLAPI++ run-time) without
any additional charge.
You may not distribute SQLAPI++ source codes (original or modified).
Registered version (Personal license)
One registered copy of SQLAPI++ library may be used by a single person who uses it personally on one or more
computers.
You may access the registered version of SQLAPI++ library through a network, provided that you have obtained
individual licenses for the software covering all developers that will access the software through the network.
Registered version (Site license)
One registered copy of SQLAPI++ may be used by up to 10 developers in the same company.
Registered version (Site+ license)
One registered copy of SQLAPI++ may be used by any number of developers in the same company.
Warranty and limitation of liability
We warrant that you will receive ongoing free email support, one year free bugs fixing and one year free upgrades to
new versions.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Zlib
zlib.h -- interface of the 'zlib' general purpose compression library
Version 1.2.13, October 13th, 2022
Copyright (C) 1995-2022 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable
for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter
it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software.
If you use this software in a product, an acknowledgment in the product documentation would be appreciated but
is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original
software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly Mark Adler
[email protected] [email protected]
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
OPC Redistributables
Version 1.3, February 06, 2017, OPC Foundation
The terms and conditions of the Agreement apply to the Software Deliverables including without limitation any OPC
Foundation:
• updates,
• supplements
• Internet-based services, and
• support services
for the Software Deliverables, unless OPC Foundation specifies that any other terms accompany such items, in
which case the alternate terms specified by OPC Foundation would apply.
BY USING THE SOURCE DELIVERABLES, YOU ACCEPT THE TERMS OF THIS AGREEMENT. IF YOU DO NOT
ACCEPT THE TERMS OF THIS AGREEMENT, DO NOT USE THE SOFTWARE DELIVERABLES.
If you comply with this Agreement, you have the rights below.
1. INSTALLATION AND USE RIGHTS.
You may install and use any number of copies of the Software Deliverables.
2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.
Distributable Code. The Software Deliverables contain compiled code that you are permitted to distribute with
programs you develop if you comply with the terms below.
• i. Right to Use and Distribute.
• You may copy and distribute all files that are part of this Software Deliverables.
• Third Party Distribution. You may permit distributors of your programs to copy and distribute the
Software Deliverables as part of those programs.
• ii. Distribution Requirements. For any Software Deliverables you distribute, you must:
• iii. add significant primary functionality to it in your programs;
• iv. require distributors and external end users to agree to terms that protect it at least as much as this
Agreement;
• v. display your valid copyright notice on your programs; and
• vi. indemnify, defend, and hold harmless the OPC Foundation from any claims, including attorneys’ fees,
related to the distribution or use of your programs.
Agreement does not change your rights under the laws of your country if the laws of your country do not permit it
to do so.
11. DISCLAIMER OF WARRANTY.
THE SOFTWARE DELIVERABLES ARE LICENSED “AS-IS.” YOU BEAR THE RISK OF USING THE
SPECIFICATIONS. THE OPC FOUNDATION MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR
IMPLIED, WITH REGARD TO THE SOFTWARE DELIVERABLES, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY, OR WARRANTY
OF FITNESS FOR A PARTICULAR PURPOSE OR USE.YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS
UNDER YOUR LOCAL LAWS THAT THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED
UNDER YOUR LOCAL LAWS, THE OPC FOUNDATION EXCLUDES THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
IN NO EVENT SHALL THE OPC FOUNDATION BE LIABLE FOR ERRORS CONTAINED IN THE SOURCE
DELIVERABLES OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR
COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA, OR USE, INCURRED BY ANY USER
OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THE
SOFTWARE DELIVERABLES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE USING THE SOFTWARE DELIVERABLES IS BORNE BY
YOU AND/OR THE USER.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
GNU
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast,
the GNU General Public License is intended to guarantee your freedom to share and change free software--to
make sure the software is free for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it. (Some other Free Software
Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your
programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed
to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish),
that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new
free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that
forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain
responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all
the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show
them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no
warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to
know that what they have is not the original, so that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To
prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it
may be distributed under the terms of this General Public License. The "Program", below, refers to any such program
or work, and a "work based on the Program" means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated
into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee
is addressed as "you". Activities other than copying, distribution and modification are not covered by this License;
they are outside its scope. The act of running the Program is not restricted, and the output from the Program is
covered only if its contents constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium,
provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and
give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the
physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the
Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you
also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any
change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the
Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this
License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running
for such interactive use in the most ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users
may redistribute the program under these conditions, and telling the user how to view a copy of this License.
(Exception: if the Program itself is interactive but does not normally print such an announcement, your work based
on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from
the Program, and can be reasonably considered independent and separate works in themselves, then this License,
and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute
the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be
on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on
the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this
License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable
form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under
the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than
your cost of physically performing source distribution, a complete machine-readable copy of the corresponding
source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software
interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This
alternative is allowed only for noncommercial distribution and only if you received the program in object code or
executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable
work, complete source code means all the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation of the executable. However, as a special
exception, the source code distributed need not include anything that is normally distributed (in either source
or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering
equivalent access to copy the source code from the same place counts as distribution of the source code, even
though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License.
Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate
your rights under this License. However, parties who have received copies, or rights, from you under this License will
not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you
permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do
not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program),
you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives
a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions.
You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not
responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited
to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict
the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute
so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a
consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free
redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you
could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the
section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to
contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software
distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application
of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted
interfaces, the original copyright holder who places the Program under this License may add an explicit geographical
distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time
to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new
problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and conditions either of that
version or of any later version published by the Free Software Foundation. If the Program does not specify a version
number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are
different, write to the author to ask for permission. For software which is copyrighted by the Free Software
Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the
sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM
AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
PowerPage
Object Code License. Subject to the terms and conditions of this Agreement, Tanner & Associates grants Company a
nonexclusive, nontransferable license to link Object Code.
Source Code License. Subject to the terms and conditions of this Agreement, Tanner & Associates grants Company
a nonexclusive, nontransferable license to use, modify, and compile Source Code. Company may not use, disclose,
sell, copy, license or distribute Source Code in any other form or for any purpose whatsoever. Company may use and
maintain a copy of Source Code on a single CPU for general development purposes (the "Designated CPU").
Derivative Software Product License. Subject to the terms and conditions of this Agreement, Tanner & Associates
grants Company a nonexclusive, nontransferable license to reproduce and distribute the Derivative Software Product
as a component part of Company Products.
Company shall not assign, transfer or sublicense this license (or any right granted herein) in any manner to any
third party. In the event Company should need to transfer distribution rights for Object Code, Source Code, and/
or Documentation to third party, third party is required to contact Tanner & Associates directly in order to purchase
separate license.
Ownership of Proprietary Rights. This Agreement does not grant to Company any title or right of ownership in or to
the Object Code or Source Code or related portion of the Derivative Software Product. Company agrees to provide
Tanner & Associates a copy of Source Code enhancements and modifications on demand.
Company will only distribute the Derivative Software Product under license. Company will take all steps necessary to
protect Tanner & Associates' proprietary rights in the Derivative Software Product. This agreement does not convey a
license to any third party who may create derivative software products based on Company's product.
Documentation. Company may reproduce operating instructions, user manuals or other Documentation listed in
Exhibit A. Documentation.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
PostgreSQL
PostgreSQL is released under the PostgreSQL License, a liberal Open Source license, similar to the BSD or MIT
licenses.
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)
Portions Copyright © 1996-2023, The PostgreSQL Global Development Group
Portions Copyright © 1994, The Regents of the University of California
Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and
without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the
following two paragraphs appear in all copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE
USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF
CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,
OR MODIFICATIONS.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-
Stingray Studio
IMPORTANT – READ CAREFULLY: THIS SOFTWARE LICENSE AGREEMENT (THE “LICENSE AGREEMENT”)
IS A LEGAL AGREEMENT BY AND BETWEEN YOU AND ROGUE WAVE SOFTWARE, INC., A SUBSIDIARY
OF PERFORCE SOFTWARE, INC. (“ROGUE WAVE”). IF YOU ARE INSTALLING THE LICENSED SOFTWARE
FOR PERSONAL USE, THIS LICENSE AGREEMENT APPLIES TO AND BINDS YOU PERSONALLY. IF YOU ARE
INSTALLING THE LICENSED SOFTWARE AS PART OF YOUR WORK FOR AN ORGANIZATION, THIS LICENSE
AGREEMENT APPLIES TO AND BINDS SUCH ORGANIZATION. “LICENSEE” OR "YOU" AND “YOUR” REFER
TO THE PERSON OR ENTITY THAT IS LICENSEE OF THE LICENSED SOFTWARE. BY INSTALLING, COPYING,
OR OTHERWISE USING THE LICENSED SOFTWARE THAT ACCOMPANIES THIS LICENSE AGREEMENT,
YOU OR SUCH ORGANIZATION AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS LICENSE
AGREEMENT. IF YOU OR SUCH ORGANIZATION DOES NOT AGREE TO BE BOUND BY THIS LICENSE
AGREEMENT, YOU MAY NOT USE, COPY, OR INSTALL THE LICENSED SOFTWARE.
1. DEFINITIONS.
1.1 “Application” means a software application that makes use of or incorporates the RW Libraries in its
implementation without exposing any part of the Licensed Software application programming interface either directly
or indirectly.
1.2 “Licensed Developer” means a natural person, employed by, or under contract to, Licensee, for whom
Licensee has designated as a “Licensed Developer,” and for whom Licensee has paid the applicable development
license fees required to authorize such natural person to use the Licensed Software to develop Applications on
Licensee’s behalf. Licenses for Licensed Developers are priced on a per natural person, and per product, or per
module, of the Licensed Software basis.
1.3 “Licensed Software” means the Rogue Wave software components, in source code or binary form, for which
Licensee has paid the applicable per product or per module license fees, together with the user guides, build guides,
reference manuals and other documentation accompanying such software components or otherwise made available
by Rogue Wave (collectively, the “Documentation”), any executables delivered with the software components
and any modified or updated versions of any of the foregoing made available to Licensee pursuant to Licensee’s
purchase of Maintenance and Support. Licensed Software does not include any third-party software products that
may be embedded in or bundled with the Licensed Software, which products are separately licensed by the copyright
holder.
1.4 “Order” means, collectively, a duly authorized quotation issued by Rogue Wave to Licensee that specifies the
Licensed Software and may include other terms and conditions governing such Licensed Software (such as the fees
and the term of the license) and a purchase order, if applicable, issued by Licensee to Rogue Wave in response
to and reflecting such quotation (with no additional or different terms, unless such additional or different terms are
expressly accepted by Rogue Wave in writing).
1.5 “Maintenance and Support” means the technical support and software maintenance services on the Licensed
Software for which Licensee has paid the applicable Maintenance and Support fees, either separately for perpetual
licenses of the Licensed Software, or as included in the subscription license fee for the Licensed Software, as
applicable.
1.6 “RW Libraries” means any Licensed Software library, in binary form, intended to be embedded in an Application
or used in the execution of an Application.
2. LICENSE GRANTS.
2.1 Development License Grant. Subject to the terms and conditions of this License Agreement, including
Licensee’s agreement to pay the applicable fees, for the applicable term (perpetual or subscription/time-limited) as
is set forth in an Order, Rogue Wave grants to Licensee a nonexclusive, nontransferable, limited right and license to:
(a) permit Licensed Developers to install and use the Licensed Software, on a per product or per module basis, for
the sole purpose of creating Applications; (b) permit a reasonable number of other persons employed by or under
contract to Licensee to install and use the Licensed Software for the sole purpose of building the RW Libraries,
and to use the RW Libraries for the sole purpose of linking, compiling, or testing Applications created by Licensed
Developers; and (c) copy or have copied the Licensed Software and RW Libraries as necessary for the purpose
of exercising the rights granted under this Section 2.1 or for back-up or disaster recovery purposes, provided, that
Rogue Wave’s copyright notice and other proprietary rights notices are reproduced on each copy.
2.2 Deployment and Distribution License Grant. Subject to the terms and conditions of this License Agreement,
for the applicable term (perpetual or subscription/time-limited) as is set forth in an Order, Rogue Wave grants to
Licensee a nonexclusive, nontransferable, royalty-free, limited right and license to: (a) install and use the RW
Libraries in connection with the execution of Applications created in compliance with Section 2.1, on physical
hardware or virtual machines owned or leased by Licensee or by contractors under Licensee’s control that are
located at facilities owned or leased by Licensee or by contractors under Licensee’s control; (b) distribute and grant
to Licensee’s customers pursuant to a license agreement at least as protective of the rights of Rogue Wave as this
License Agreement the right to install and use the RW Libraries in connection with the execution of Applications
created in compliance with Section 2.1, on physical hardware or on virtual machines owned or leased by the
customer or by contractors under the customer’s control that are located at facilities owned or leased by the
customer or by contractors under the customer’s control; and (c) copy or have copied the RW Libraries embedded
in or used in the execution of Applications as necessary for the purpose of exercising the rights granted under this
Section 2.2 or for back-up or disaster recovery purposes, provided, that Rogue Wave’s copyright notice and other
proprietary rights notices are reproduced on each copy.
3. LICENSE RESTRICTIONS AND LICENSEE RESPONSIBILITIES.
3.1 Development Restrictions. The development rights granted to Licensee in Section 2.1 may only be exercised
by individual developers employed by or under contract to Licensee that Licensee has designated as “Licensed
Developers” and for whom Licensee has paid the applicable per product or per module development license fees.
If one Licensed Developer ceases to be employed by or under contract to Licensee or permanently ceases work
on projects involving the Licensed Software, then Licensee may designate an alternate developer to replace such
Licensed Developer at no additional cost. However, the development license is not a concurrent license that may be
used by numerous developers in shifts or on an outsourced basis for a temporary period. Licensee may not create
a programmatic interface that makes use of the Licensed Software application programming interfaces for use by
any party other than Licensed Developers and must ensure that persons other than Licensed Developers do not
have programmatic access to the Licensed Software or RW Libraries either directly or indirectly. Nothing herein
shall grant Licensee the right to grant its customers the right to programmatically use or grant others the right to
programmatically use the Licensed Software or RW Libraries.
3.2 General Use Limitations. All rights not specifically granted herein are retained by Rogue Wave. Licensee may
not, nor may Licensee permit any other person or entity to use, copy, modify, or distribute the Licensed Software
(electronically or otherwise), or any copy, adaptation, transcription, or merged portion thereof (including the RW
Libraries), or the Documentation except as expressly authorized by Rogue Wave. Licensee may not modify or
port the Licensed Software or RW Libraries to operate on or deploy the RW Libraries or Applications on platforms
or architectures other than those for which it has paid the appropriate fees. Licensee may not, nor may Licensee
permit any other person or entity to, reverse assemble, reverse compile, or otherwise translate any binary forms
of the Licensed Software, except to the extent applicable laws specifically prohibit such restriction. Licensee’s
rights may not be transferred, leased, assigned, or sublicensed except as expressly authorized by Rogue Wave in
writing. No service bureau work, multiple-user license, or time-sharing arrangement is permitted, except as expressly
authorized by Rogue Wave. If Licensee uses, copies, or modifies the Licensed Software or RW Libraries or transfers
possession of any copy, adaptation, transcription, or merged portion thereof to any other party in any way not
expressly authorized by Rogue Wave, all licenses under this License Agreement are automatically terminated.
3.3 Proprietary Protection. Rogue Wave shall have sole and exclusive ownership of all right, title, and interest
in and to the Licensed Software and all modifications and enhancements thereof (including ownership of all trade
secrets and copyrights pertaining thereto), subject only to the rights and privileges expressly granted to Licensee
herein by Rogue Wave. This License Agreement does not provide Licensee with title or ownership of the Licensed
Software, but only a right of limited use. Licensee must keep the Licensed Software free and clear of all claims, liens,
and encumbrances.
3.4 Compliance Verification. Licensee must have a commercially reasonable process in place to track the
number of developers using the Licensed Software in order to ensure that the appropriate license fees have been
paid. Licensee will, upon Rogue Wave’s request, certify in writing the number developers using the Licensed
Software, on a per product or per module basis, as of the date of the request. In the event Licensee fails to provide
such certification within thirty (30) days of Rogue Wave’s request, or, if Rogue Wave reasonably believes that a
certification provided by Licensee is inaccurate or that Licensee is otherwise not in compliance with the terms of this
License Agreement, Licensee will permit Rogue Wave, or a mutually-approved independent representative, to enter
Licensee’s premises, during regular business hours, to verify Licensee’s compliance with the terms of this License
Agreement.
3.5 Confidentiality.
(a) Confidentiality General Terms. Each party to this License Agreement agrees to keep confidential and to use only
for purposes of performing its obligations under this License Agreement, any proprietary or confidential information
of the other party disclosed pursuant to this License Agreement that is marked as confidential, is identified at the
time of disclosure as confidential, or that would reasonably be considered confidential or proprietary in nature. The
obligation of confidentiality shall not apply to information that is publicly available through authorized disclosure,
or information that is required to be disclosed by law, government order, or request to be disclosed (provided that
the receiving party shall give reasonable advance written notice to the other party prior to such disclosure and
an opportunity, at the objecting party’s expense, to take legal steps to resist or narrow such request). Licensee
acknowledges and agrees that the Licensed Software and its source code shall be deemed as Rogue Wave’s
confidential information, as more particularly provided in Section 3.5(b) of this License Agreement. Each party's
obligations of nondisclosure with regard to proprietary or confidential information are effective as of the date such
proprietary or confidential information is first disclosed to the receiving party and will expire five (5) years thereafter;
provided, however, that with respect to any proprietary or confidential information that constitutes a trade secret (as
determined under applicable laws), such obligations of nondisclosure will survive the termination or expiration of
this License Agreement for as long as such proprietary or confidential information remains subject to trade secret
protection under applicable laws.
(b) Confidentiality of Source Code. Licensee agrees to maintain in confidence the source code version of the
Licensed Software by using at least the same physical and other security measures as Licensee uses for its own
confidential technical information and documentation, but in no case less than reasonable measures. Licensee
further agrees not to disclose the source code version of the Licensed Software, or any aspect thereof (including,
without limitation, header files), to anyone other than employees or contractors who have a need to know or obtain
access to such information in order to support Licensee’s authorized use of the Licensed Software and are bound
to protect such information against any other use or disclosure. These obligations shall not apply to any information
generally available to the public, ascertainable based on the operation of the binary code version of Applications,
independently developed or obtained without reliance on Rogue Wave's information, or as approved for release in
writing by Rogue Wave without restriction.
3.6 Development of Applications. The Licensed Software is intended for use by sophisticated developers.
Licensee is responsible for selecting persons who are qualified to use the Licensed Software on Licensee’s
own equipment and are familiar with the Licensed Software. Licensee is also responsible for ensuring a proper
environment and proper utilities for the development and execution of Applications utilizing the Licensed Software.
Licensee represents that it has the requisite expertise to evaluate the suitability of the Licensed Software and that
it has undertaken its own investigation of the suitability of the Licensed Software in the Applications. Licensee
represents that it has relied upon its own skill and judgment in selecting the Licensed Software and developing the
Applications.
3.7 Relationship with End Users. There are no third-party beneficiaries to this License Agreement. Consequently,
Rogue Wave provides no warranty at all to any person, other than the limited warranty provided to Licensee
hereunder. Licensee will be solely responsible for the development of the Applications authorized by this License
Agreement and for providing all support or services required or requested by end users of the Applications. Licensee
will not make any representations or warranties to its employees, customers, end users or any other third party
on Rogue Wave’s behalf. Rogue Wave assumes no responsibility under this License Agreement, either directly
or indirectly, for damages to Licensee or third parties resulting from the direct or indirect use of the Applications
created by or on behalf of Licensee and Licensee shall defend and hold harmless Rogue Wave from any such
damages. Licensee hereby agrees to indemnify and hold harmless Rogue Wave from and against all claims, actions,
or demands arising with respect to Applications developed and/or distributed by Licensee, with the sole exception of
those matters for which Rogue Wave bears responsibility under Section 7 of this License Agreement. The foregoing
indemnity shall be contingent upon Rogue Wave: (a) giving written notice to the Licensee of any claim, demand, or
action for which indemnity is sought; (b) fully cooperating in the defense or settlement of any such claim, demand, or
action; and (c) obtaining the prior written agreement of the Licensee to any settlement or proposal of settlement.
3.8 Remedies. Licensee acknowledges that, in the event of Licensee’s breach of any of the foregoing provisions,
Rogue Wave will not have an adequate remedy in money or damages. Rogue Wave will therefore be entitled to
obtain an injunction against such breach from any court of competent jurisdiction immediately upon request without
posting a bond. Rogue Wave’s right to obtain injunctive relief shall not limit its right to seek further remedies.
4. MAINTENANCE AND SUPPORT OF LICENSED SOFTWARE. Rogue Wave or its authorized resellers shall
provide Maintenance and Support on the Licensed Software at the level and for the period for which Licensee has
paid the applicable fees as specified in on the Order. Maintenance and Support services provided by Rogue Wave
are provided in accordance with Rogue Wave’s standard maintenance and support and obsolescence policies, which
are subject to change. Maintenance and Support is limited to platforms listed on Rogue Wave’s current product
support matrix, which is also subject to change. Licensee is responsible for ensuring that its development and
deployment environment is on the current product support matrix. Off-matrix support is available from Rogue Wave
for an additional fee.
5. FEES AND PAYMENT. License fees and Maintenance and Support fees will be as set forth on the applicable
Order. All license fees and Maintenance and Support fees that are invoiced to Licensee will be payable by Licensee
in United States Dollars, unless otherwise set forth on the Order. All invoices shall be due and payable within thirty
(30) days after the invoice date. If Licensee fails to pay any amounts due under this License Agreement by the
due date, Rogue Wave will have the right to charge interest at a rate equal to the lesser of 1.5% per month, or the
maximum rate permitted by applicable law, until Licensee pays all amounts due. Licensee is required to pay any
sales, use GST, value-added withholding, or similar taxes or levies, whether domestic or foreign, other than taxes
based on the income of Rogue Wave. Rogue Wave may adjust the fees charged to Licensee hereunder on notice
(electronic notice is sufficient) delivered to Licensee at least forty-five (45) days prior to the end of the then-current
subscription term, or Maintenance and Support term (and such fees will take effect beginning on the start of the
next term). Notwithstanding the foregoing, Rogue Wave may increase the fees for any term over the fees from
the preceding term by the greater of 5% and CPI. Except as expressly set forth in Section 6.1, all fees are non-
refundable.
6. LIMITED WARRANTY, DISCLAIMER AND LIMITATION OF LIABILITY.
6.1 Limited Warranty. Rogue Wave warrants to Licensee that the unaltered Licensed Software, when used as
permitted under the License Agreement and in accordance with the instructions in the Documentation, will operate
substantially as described in the Documentation for a period of thirty (30) days from the date of delivery (the
“Software Warranty Period”). The Licensed Software is provided to Licensee as source code and is for use by
sophisticated software developers, and Rogue Wave does not warrant that use of the Licensed Software will be
uninterrupted or error-free, that all errors will be corrected, or that use of the Licensed Software will meet Licensee’s
needs. Rogue Wave will, at its own expense and as its sole obligation and Licensee’s sole and exclusive remedy for
any breach of this warranty, use commercially reasonable efforts to correct any reproducible error in the Licensed
Software reported to Rogue Wave by Licensee in writing during the Software Warranty Period; provided, however,
that no such error correction provided to Licensee will extend the original Software Warranty Period. If Rogue Wave
determines that it is unable to correct the error, Rogue Wave may, upon approval by Licensee, refund to Licensee
the fees paid by the Licensee for the defective Licensed Software and terminate the License Agreement and all
licenses granted herein. In the event Licensee does not approve of such refund and termination of the License
Agreement, Licensee will be entitled to keep the Licensed Software and use it pursuant to the licenses granted
herein; provided, however, that Rogue Wave will not be obligated to provide Maintenance and Support for the
Licensed Software that is impacted by the reported defect.
6.2 Exclusions. The limited warranty set forth above will not apply to defects resulting from, or because of,
modifications made to the Licensed Software by anyone other than Rogue Wave, misuse, failure of media not
furnished by Rogue Wave, operation with media, software or equipment not authorized by Rogue Wave in the
Documentation or not meeting or not maintained in accordance with the supplier’s specifications or causes other
than ordinary use. The warranty set forth above will not be enlarged, diminished, or affected by, and no obligation
or liability will arise from, Rogue Wave’s rendering of technical advice, assistance or service in connection with
Licensee’s selection or use of the Licensed Software. Certain open source or other-vendor software may be
distributed with the Licensed Software or recommended in connection with its installation and use. Such products
are provided or recommended for Licensee’s convenience only. Rogue Wave makes no representation or warranty
of any kind regarding such products. Rogue Wave offers no support for such products and shall have no liability
associated with their use. Licensee’s use of these products shall be in accordance with the licenses for such
products, copies of which are included with the products and/or in the Rogue Wave documentation.
6.3 DISCLAIMER. EXCEPT FOR THE LIMITED WARRANTY SET FORTH IN SECTION 6.1 ABOVE, THE
LICENSED SOFTWARE IS PROVIDED “AS IS,” WITHOUT REPRESENTATIONS OR WARRANTIES OF
ANY KIND. ROGUE WAVE SPECIFICALLY DISCLAIMS ALL OTHER PROMISES, REPRESENTATIONS OR
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ANY
IMPLIED WARRANTY ARISING FROM COURSE OF PERFORMANCE OR COURSE OF DEALING.
6.4 LIMITATION OF LIABILITY. THE CUMULATIVE LIABILITY OF ROGUE WAVE TO LICENSEE FOR ALL
CLAIMS RELATING TO THE LICENSED SOFTWARE AND THIS LICENSE AGREEMENT, INCLUDING ANY
CAUSE OF ACTION SOUNDING IN CONTRACT, TORT, OR STRICT LIABILITY, SHALL NOT EXCEED THE
TOTAL AMOUNT OF ALL LICENSE FEES PAID TO ROGUE WAVE HEREUNDER. THIS LIMITATION OF
LIABILITY IS INTENDED TO APPLY WITHOUT REGARD TO WHETHER OTHER PROVISIONS OF THIS
LICENSE AGREEMENT HAVE BEEN BREACHED OR HAVE PROVEN INEFFECTIVE. THIS LIMITATION OF
LIABILITY SHALL NOT APPLY TO THE INDEMNIFICATION PROVIDED IN SECTION 5 HEREOF. ROGUE
WAVE SHALL HAVE NO LIABILITY FOR LOSS OF DATA OR DOCUMENTATION, IT BEING UNDERSTOOD
THAT LICENSEE IS RESPONSIBLE FOR REASONABLE BACK-UP PRECAUTIONS. IN NO EVENT SHALL
ROGUE WAVE BE LIABLE FOR ANY LOSS OF PROFITS; ANY INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES; OR ANY CLAIMS OR DEMANDS BROUGHT AGAINST LICENSEE, EVEN IF
ROGUE WAVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH CLAIMS OR DEMANDS. THIS LIMITATION
UPON DAMAGES AND CLAIMS IS INTENDED TO APPLY WITHOUT REGARD TO WHETHER OTHER
PROVISIONS OF THIS LICENSE AGREEMENT HAVE BEEN BREACHED OR HAVE PROVEN INEFFECTIVE.
LICENSEE MAY HAVE ADDITIONAL RIGHTS UNDER CERTAIN LAWS (E.G., CONSUMER LAWS) THAT DO
NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, OR THE EXCLUSION OR LIMITATION OF CERTAIN
DAMAGES. IF SUCH LAWS APPLY, CERTAIN EXCLUSIONS OR LIMITATIONS MAY NOT APPLY TO LICENSEE;
HOWEVER, ALL OTHER RESTRICTIONS AND LIMITATIONS SHALL REMAIN IN EFFECT.
7. INDEMNIFICATION. Rogue Wave agrees to defend Licensee from and against any third-party claims alleging that
the Licensed Software furnished and used within the scope of this Agreement infringes or misappropriates a U.S.
patent issued as of the Effective Date, copyright, trademark or trade secret and will pay all final judgments awarded
or settlements entered into on such claims. The foregoing indemnity obligation shall not extend to any claims of
infringement arising out of or related to (i) a modification of a Licensed Software by anyone other than Rogue Wave
or its duly authorized agent; (ii) the incorporation into the Licensed Software of any information provided by or
requested by Licensee; (iii) a combination of the Licensed Software with any third party software or equipment not
specified in the Documentation and where such combination is the cause of such infringement; or (iv) the use of
a version of a Licensed Software other than the then-current version if the infringement would have been avoided
by using of the then-current version. In the event the Licensed Software is held or is believed by Rogue Wave to
infringe, Rogue Wave may, at its sole option and expense, elect to (a) modify the Licensed Software so that it is non-
infringing; (b) replace the Licensed Software with non-infringing Licensed Software which is functionally equivalent;
(c) obtain a license for Licensee to continue to use the Licensed Software as provided hereunder; or if none of
(a), (b), or (c) is commercially reasonable, then (d) terminate the license for the infringing Licensed Software and
refund the license fees paid for that Licensed Software, prorated over a five (5) year term from the Effective Date.
THIS SECTION 7 STATES ROGUE WAVE’S ENTIRE LIABILITY AND LICENSEE’S SOLE AND EXCLUSIVE
REMEDY FOR ANY INFRINGEMENT OF THIRD-PARTY PROPRIETARY RIGHTS OF ANY KIND. Rogue Wave’s
indemnification obligations under this Section 7 are conditioned upon the Licensee: (a) giving prompt notice of the
claim to Rogue Wave; (b) granting sole control of the defense or settlement of the claim or action to Rogue Wave;
and (c) providing reasonable cooperation to Rogue Wave and, at Rogue Wave’s request and expense, assistance in
the defense or settlement of the claim.
8. TERMINATION.
8.1 Term. The term of this License Agreement will begin as of the date that Licensee receives the Licensed Software
and will remain in effect perpetually unless terminated under this Section 8.
8.2 Termination for Cause. Rogue Wave may terminate this License Agreement if Licensee breaches its obligations
hereunder. Rogue Wave will begin the termination process by giving Licensee notice of termination, specifying
therein the alleged breach. If the breach is curable, Licensee will have a grace period of thirty (30) days after such
notice is served to cure the breach described therein. If the breach is cured within the thirty (30) day grace period,
then this License Agreement will remain in effect; otherwise, this License Agreement will automatically terminate
upon the conclusion of the thirty (30) day grace period.
8.3 Effect of Termination. Upon termination of the License Agreement for any reason the following terms shall apply:
(a) all rights granted under this License Agreement will immediately terminate and Licensee must immediately stop
all use of the Licensed Software; (b) Licensee must return to Rogue Wave or destroy all copies of the Licensed
Software provided to or made by or on behalf of Licensee, and will, within ten (10) days after the effective date of
termination, provide Rogue Wave with written certification that all such copies have been returned or destroyed; and
(c) all provisions of this License Agreement with the exception of the licenses granted in Section 2 and Maintenance
and Support obligations set forth in Section 4 will survive termination of this License Agreement for any reason.
Termination of the License Agreement will not affect Licensee’s obligation to pay all amounts accrued hereunder
prior to the effective date of termination.
9. MISCELLANEOUS.
9.1 Severability. If any term or provision of the License Agreement is found to be invalid under any applicable
statute or rule of law, then, that provision notwithstanding, the License Agreement will remain in full force and effect,
and in such event, such provision will be changed and interpreted so as to best accomplish the objectives of such
unenforceable or invalid provision within the limits of applicable law or applicable court decisions.
9.2 Force Majeure. Neither party will be deemed to be in breach of this License Agreement, nor otherwise liable
to the other, by reason of any delay in performance or non-performance of any of its obligations under this License
Agreement arising out matters beyond the reasonable control of a party, including, war, strikes, lock outs, or
industrial disputes (except in relation to a party's own workforce), outbreak of hostilities, riots, civil disturbances,
pandemics, epidemics, or quarantines, acts or orders of any government department or constituted body, fire,
explosion, earthquake, flood, acts of God, or acts of terrorism; provided, however, that no event will be treated as
beyond the reasonable control of a party if it is attributable to a willful act or omission by such party, or any failure
by such party to take reasonable precautions or any failure to mitigate or take reasonable steps to overcome such
event. If the performance of the impacted party is prevented for a period of thirty (30) days or more, the party not
affected may terminate this License Agreement upon providing seven (7) days’ advance written notice to the affected
party.
9.3 Governing Law/Forum Selection. The License Agreement and the parties’ rights and obligations hereunder
shall be solely and exclusively construed, interpreted and enforced under and in accordance with the laws of the
State of Delaware, United States of America, without any reference to conflicts of law principles. The parties agree
that the U.N. Convention on the International Sale of Goods shall not apply to the License Agreement. All disputes
between the parties shall be brought and resolved solely and exclusively in the state or federal courts located in
the State of Delaware, United States of America. Both parties hereby irrevocably consent to the jurisdiction of such
courts and service of process in connection therewith. Any judgment rendered by such courts may be entered and
enforced by any court having jurisdiction over the party against which an award is entered or its assets. Both parties
hereby irrevocably waive any objections to the jurisdiction of such courts based on any ground, including without
limitation improper venue or forum non conveniens.
9.4 No Joint Venture. Nothing contained in the License Agreement will be construed so as to make the parties
partners or joint venturers or to permit either party to bind the other party to any agreement or purport to act on
behalf of the other party in any respect.
9.5 Waiver and Modifications. Failure by either party to enforce any rights under this License Agreement will not
be construed as a waiver of such rights, and a waiver by either party of a default hereunder in one or more instances
will not be construed as constituting a continuing waiver or as a waiver in other instances. No modification of this
License Agreement shall be binding unless it is in writing and is signed by an authorized representative of the party
against whom enforcement of the modification is sought.
9.6 Import/Export Law. Licensee may not import, use, or otherwise export or re-export the Licensed Software
except as authorized by United States law and the laws of the jurisdiction in which the Licensed Software was
obtained.
9.7 Taxes. License fees and Maintenance and Support fees are exclusive of, and Licensee will pay, all shipping
charges and all taxes, duties and other charges or fees imposed by governmental authorities arising out of the
License Agreement or the use of the Licensed Software by Licensee and its Licensed Developer(s). In addition, if
any Licensed Software will be delivered to points outside of the United States, all export duties, import duties, tariffs,
value added taxes, licenses and other similar taxes, duties and fees will be paid by Licensee. If Licensee is required
by the laws of any jurisdiction to deduct or withhold from any payment to Rogue Wave any income taxes which
may be levied against Rogue Wave, then Licensee’s payment shall be increased to an amount equal to the pre-tax
payment due divided by a factor equal to one minus the applicable foreign tax rate. The tax shall then be applied to
and deducted from the increased payment.
9.8 U.S. Government Rights. The Licensed Software is a “commercial item” as that term is defined at 48 C.F.R.
2.101, consisting of “commercial computer software” and “commercial computer software documentation” as
such terms are used in 48 C.F.R. 12.212. Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through
227.7202-4, all U.S. Government end users acquire the Licensed Software with only those rights set forth in this
License Agreement.
9.9 Assignment. This License Agreement, or any of your rights and obligations under this License Agreement,
cannot be assigned or otherwise transferred in whole or in part, and any such attempted assignment or transfer by
Licensee in violation of the foregoing will be null and void.
9.10 Entire Agreement. This License Agreement, including all invoices hereunder, constitutes the sole and entire
agreement of the parties with respect to the subject matter hereof and supersedes and cancels any prior and
contemporaneous oral or written proposals, promises, or agreements. There are no promises, covenants, or
undertakings other than those expressly set forth in this License Agreement. If Licensee issues a Licensee purchase
order, or any other Licensee-generated documentation, and the terms and conditions conflict with this License
Agreement, the terms and conditions contained in this License Agreement, including all invoices incorporated
hereunder, will control. For purposes of clarity, no terms, or conditions, including any pre-printed or boilerplate terms
and conditions, stated in any Licensee purchase order, or in any other Licensee documentation, will be incorporated
into or form any part of this License Agreement, and all such terms or conditions will be null and void and of no force
and effect.
9.11 English Language. The parties hereto have expressly required that the present License Agreement be drawn
up in the English language. / Les parties aux présentes, ont expressément exigé que la présente Convention soient
rédigées en langue anglaise.
10. EVALUATION LICENSE. The terms of this Section 10 shall solely apply to Licensed Software licensed for
purposes of Evaluation (the “Evaluation Software”). The terms of Sections 2, 6.1, 6.2, 6.3 and 8 shall not apply to the
parties’ rights and obligations with respect to Evaluation Software.