ZEE600 from ABB provides the substation HMI and automation systems, which connect the IEDs and devices within the substation as well as the offsite control center. This section examines the following aspects of system design related to ZEE600:
- ZEE600 components
- Use cases
- Substation edge deployment
- ZEE600 features
ABB ZEE600 refers to zenon Energy Edition (ZEE), which is built on COPA-DATA's zenon product suite. Throughout this documentation, the term ZEE600 includes both the underlying zenon functionality and ABB's augmented energy feature set.
ZEE600 components
The primary components of the ZEE600 software package are the Editor, which is used to create customized runtimes, and the Runtime, which is deployed on the wanted machine. Once deployed as a server, that same runtime can also be used to set up clients on other machines. There is also a set of tools that are included with ZEE600 that help manage, expand, or troubleshoot the deployment.
The following figure shows the components and features of ZEE600.
ZEE600 Editor
The Editor is used to configure a runtime for a specific substation. It is organized by Workspaces, which are a collection of projects the developer is working on. This workspace typically has an active project, which is the one being edited, and a start project, which is the project that starts when the run button is pressed. Projects can also be loaded from memory to view and edit them or unloaded from memory to free up resources.
The projects are composed of various components, such as drivers, variables, screens, and SCADA Logic. These components are covered in more detail later in this chapter and in subsequent chapters. These components can be edited, combined, exported, and imported to build the fully customized runtime.
ZEE600 Runtime
The Runtime is the compiled project that is created with the Editor. It is a collection of all the files that are required to run the application on a given machine. The Runtime includes data ingestion from IEDS and other devices, automation and SCADA logic, dashboard navigation and visualizations, related security and administration, and the functionality to auto-launch additional components, like process gateways. Once created, it can be deployed on the required machine without the Editor or deployed remotely using the Editor.
Supplementary tools
Some of the supplementary tools that are used in the validation are shown in the following table.
Tool | Use |
Startup Tool | Launch all the other applications bundled with ZEE600. |
License Manager | Add or release licenses and monitor the existing license configuration. |
Diagviewer | View and search through logs. |
Redundancy Management Tool | Configure redundant servers. |
Process Gateway | Run a tool or application independently of the Runtime - can be configured to run automatically with the Runtime. |
Application versions
The following application versions were used in validation, unless otherwise noted:
- ABB ZEE600 v2.0.1, containing:
- zenon Startup Tool v8.20
- zenon Editor v8.20
- zenon Runtime v8.20
- zenon Process Gateway v8.20
Use cases
A substation automation platform like ZEE600 plays a crucial role in electrical substations. It uses communication protocols and advanced automation applications to enhance substation monitoring and control operations.
The following are some use cases for ZEE600:
- Data aggregator—Collects measured values and state data from multiple downstream IEDs, such as protection relays, meters, and bay control units, using serial or TCP/IP-based communication protocols.
- Substation SCADA—Provides a local SCADA system in a substation, with features like HMI screens, Single Line Diagrams, a historian, reports, and alarms/events processing.
- Protocol gateway—Acts as a protocol gateway to send substation data to Advance Distribution Management System (ADMS) or Energy Management System (EMS) located in electrical utilities' control centers.
- Substation automation—Provides advanced automation features like interlocking, scheduler, and IEC 61131-3 programming. Utility customers can use these features to build customized automation applications that cater to their specific needs.
Substation edge deployment
This section discusses the deployment of ZEE600 components in a substation. All ZEE600 components are deployable on Windows machines-virtual machines for those components that are hosted on the virtualized VMware platform on PowerEdge XR12 servers and bare metal for those components that are hosted on the 3200 and 5200 Dell Edge Gateways.
Editor deployment
The Editor application is typically installed on an engineering workstation running Windows. This application only requires a network connection to the edge deployment when pushing changes to the Runtime files.
Runtime deployment
In this Dell Validated Design for Energy Edge, the customized ZEE600 Runtime is deployed to a VMware virtual machine running Windows 10 on an IEC 61850-3-certified Dell PowerEdge XR12 server at the substation.
ABB provides an easy-to-use installer application. The ZEE600 applications are easily selectable in the installer interface. For the distributed deployment used in this DVD, only the Runtime should be installed on the Dell PowerEdge XR12 virtual machine.
Deploying a project to the ABB Runtime
This Runtime is compiled in the Editor and can be pushed to the Runtime machine in two different ways:
- The project files can be copied from the Editor host machine and placed on the Runtime VM.
- The Runtime files can be pushed to the Runtime host from the Editor host over a secure network connection using the integrated Remote Transfer functionality. This allows a single user on the Editor machine to quickly make changes and push the updates to multiple runtime hosts with just a few clicks, eliminating the need to connect and log in to each Runtime host.
Runtime server
The ABB ZEE600 Runtime supports a client/server configuration, where IED connections and substation automation can be hosted on the Runtime server, and the HMI made available to operators can be viewed using the client machine.
This model provides flexibility on how the physical and digital security of devices is managed, how the respective workloads are distributed, and how HA/DR functionality is configured.
Runtime client
Other computers on the same network as the Runtime server can act as clients. While all devices, data, automation, and screens are hosted on the server, the client can host the interface used by operators and technicians.
Licensing
Every machine running an ABB ZEE600 component must have the appropriate license to gain the full functional value of the application. Demo mode is available prior to the activation of a license.
Licenses can be deployed to a host machine using either a hardware dongle that is attached to the host hardware or a software-based key that is added to the License Manager software on the machine. The activation of a license can be either online (see Online activation) or offline (see Offline activation), depending on the needs of the specific deployment.
Special consideration should be given to licensing Virtual machines—hardware dongles require a passthrough from the physical host to the VM, while software keys are tied to specific details of the host VM. Changing the VM, such as altering the computer resources, adding or removing network interfaces, or migrating the VM to a new host causes the software-based license to be invalidated. Therefore, software licenses should be returned using the License Manager prior to making any changes and then reactivated once the updates are complete. It is recommended to use the network licensing for virtual machines. For more information about this, see the Network dongles documentation.
For further details on licensing options and considerations, see Licensing.
ZEE600 features
Variables
Variables, also called process variables or data points, are the interface between a data source (IED, PLC, field bus, and so on) and the ZEE600. They represent certain measured values (line voltages, currents, frequency, and so on) or states of the field devices (circuit breaker, switch, and so on).
Variables can have many properties, including the specific address used by the driver, calculations for scaling, and limits. The following figure shows examples of ZEE600 variables and their typical properties.
Once a variable is defined and attached to a driver, it is available to other features of ZEE600 (HMI screens, functions, process gateways, and so on).
Protocol drivers
A protocol driver establishes connection between an IED and ZEE600, and then fetches measured values and states. Each protocol driver implements a specific communications protocol in client mode. ZEE600 provides drivers for common protocols that are used in the energy industry, including DNP3, Modbus RTU and TCP/IP, IEC 61850, IEC 60870-5-101, IEC 60870-5-103, and IEC 60870-5-104.
The following steps are typically used to integrate an IED with ZEE600:
- Create a driver and add the IED connection details. Configure its settings, like Serial Port, Baud Rate (for serial protocols) or IP Address of the IED, TCP port number (for network protocols).
- Create variables for measured values and states available in the IED. Configure properties of the variables like driver addressing, datatype, scaling, and limits.
- Map variables to HMI screens, functions, and process gateways.
See Variables in the ZEE600 manual for further details on configuring an IED connection in a protocol driver.
The following table lists the common protocol drivers that are used in the energy industry, and it includes links to driver manuals and integration strategies.
Protocol driver | Interface type | Driver manual | Recommended tools/Wizards for efficient integration of IEDs |
Modbus/RTU | Serial | Link |
|
Modbus/TCP | Network | Link |
|
DNP3 Serial | Serial | Link |
|
DNP3 TCP/UDP | Network | Link |
|
IEC 60870-5-101 | Serial | Link |
|
IEC 60870-5-103 | Serial | Link |
|
IEC 60870-5-104 | Network | Link |
|
IEC 61850 | Network | Link |
|
Process gateway
The process gateway in ZEE600 serves as a protocol server to higher-level systems, such as an ADMS or EMS in a control center. It mainly provides two use cases:
- Process data from ZEE600 Runtime can be forwarded to higher-level systems.
- Higher-level systems can write values or commands to the ZEE600 Runtime.
ZEE600 supports most protocol servers that are used in the energy industry: Modbus, DNP3, IEC 60870-5-101/104, OPC UA, and more. Furthermore, process gateways can be used to configure a syslog connection for central logging. For more information, see the Cybersecurity chapter.
The process gateway is intended as an add-on in the ZEE600 Runtime, and it maps variables from the Runtime by variable names in a project. Several process gateways can be started on one Runtime computer or virtual machine.
The following steps are typically required to configure a process gateway:
- Module selection—In the first stage of configuration, select the module for the server protocol. The following figure shows the list of available protocol server modules.
- Module-specific—Depending on the selected module, configure connection parameters and variable assignments.
- Autostart—Create a function to start the process gateway and configure a script (like the prebuilt AUTOSTART script) to run the function on Runtime startup or on another automated condition.
See the Process Gateway manual for the configuration details of the Process Gateway modules.
HMI features
Screens
The HMI is created by populating screens with the wanted elements. There are many basic elements available from the element toolbar, and those elements can be combined into symbols for reuse. Each element also has a list of properties, which are used to customize the element and link them to specific variables.
When building a ZEE600 project using the ABB ZEE600 Template Wizard, many screens and navigation interfaces are preconfigured to make customization quick and easy. A user login interface, alarm screen, menu navigation, and single line diagram screens are among the screens immediately available.
Further customization and standardization of the HMI can be achieved by using frames, font lists, styles, and color palettes.
Functions
Most HMI logic is encapsulated with functions, such as what happens when a button is pressed or when a variable changes. HMI navigation and opening pop-ups are handled through these functions.
Functions also play an important role in developing standardized HMIs. By using the Screen Switch function and replacing links or index parameters, all the variable links on a page can be changed dynamically. Then a single page can be used for multiple devices.
Historian
Variables which need to be tracked over time are added to the historian and grouped based on where and when the data is recorded. Data can also be set to expire after a fixed amount of time so that storage space is not overused.
This historical data can be displayed on the screen through the Trend Element or processed through SCADA logic.
For more details on HMI configuration, see the ZEE600 Manual.
Substation automation features
SCADA logic
Advanced automation can be added to any runtime by creating a SCADA logic project within the overall project. Doing this adds an internal driver to the Variables section and opens the SCADA Logic editor as seen in the following figure. Programs are written in any of the IEC 61131-3 languages and can execute cyclically or periodically.
By connecting to an active runtime, the SCADA Logic screen can be used to view the values of variables in real time and update the logic. This is useful while developing code and for troubleshooting.
This same interface is also available by creating a simulated driver as discussed in the Accelerated Time to Value chapter.
Command processing
The command processing component allows groups of variables to be connected for safe operation. This is an easier and more visible way to enforce intervariable logic than with a SCADA logic program and is most effective when combined with a Command Processing Screen (a template for this is already included in ZEE600 projects). For example, if a switch cannot be closed unless the closed enable variable is true, then this rule can be encapsulated in a command group. This supersedes any features in the HMI and reinforces safe operation.
Programming interfaces
All advanced programming, such as creating editor elements (wizards, graphics, and so on) are created in the programming interfaces option. This opens the VBA editor, or ideally Visual Studio with the appropriate add-on. By creating projects in VBA, the options to expand the functionality are limitless.
For further information about these and other available components, see the ZEE600 Manual.
Security features
ABB ZEE600 software has numerous security features available to secure data and restrict access to only authorized users.
Many of these security features are covered in detail in the Cybersecurity chapter.
User administration
This section of the Editor is where new users and user groups are created and configured. Users can be assigned authorization levels for security and organized into groups. Those groups can also be assigned authorization levels to make it easier to manage access for large numbers of users.