Requirements and Recommendations
Learn about the Software and Hardware requirements and recommendations relevant to the i4scada product.
This topic contains the software and hardware requirements and recommendations for viewing and creating SCADA visualizations and also for development using Ewon by HMS Networks Client SDK and Server SDK.
Software Requirements
These system requirements are applicable to i4scada Version 3.8 and above. These are the minimum requirements for the basic functionality of the software. Actual conditions can vary, depending on the system configuration, the software that is installed, and the features
The default operating system compatibility of i4scada is limited by the requirements of the SQL Server 2022 Express Edition, which is delivered by default with the i4scada Setup. The following operating systems are supported by SQL Server 2022 Express Edition:
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2022 Datacenter
Windows Server 2022 Standard
Windows Server 2022 Essentials
Windows 10
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 11
Windows 11 Professional
Windows 11 Enterprise
Windows 11 IoT Enterprise
Read more information about the Microsoft SQL Server 2022 requirements.
Viewing visualizations requirements | Description | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Operating Systems | Any Operating System with an HTML5 (and/or Silverlight) enabled web browser. | |||||||||||||||||||||
Web Browser | Web browser with HTML5 and/or Silverlight support. Check the below table for an overview of web browser compatibility with HTML5 and Silverlight:
| |||||||||||||||||||||
Silverlight run time | Microsoft Silverlight version 5 (relevant for the i4scada 3.8.3 version and higher) |
Running i4scada Requirements | Description |
|---|---|
Operating Systems |
|
Supported SQL Servers |
|
.NET Framework | Microsoft .NET Framework 4.6.2 or above NOTE - For optimal results when working with the i4scada, a set of Windows Roles and Features need to be enabled.
|
Silverlight SDK | Microsoft Silverlight 5 SDK (relevant for the i4scada 3.8.3 version and higher) |
Webserver | Microsoft Internet Information Services (IIS) NoteThe use of a Windows Server operating system is recommended to allow access for several clients. For optimal results when working with the i4scada, a set of Windows Roles and Features need to be enabled.
|
IDE |
|
Developing with i4scada Client SDK. Silverlight, WPF and HTML5 | Description |
|---|---|
Operating System | Microsoft Windows 10 (x64) or higher |
.NET Framework | Microsoft .NET Framework 4.6.2 or higher |
Silverlight SDK | Microsoft Silverlight 5 SDK or higher (relevant for the i4scada 3.8.3 version and higher) |
Silverlight Toolkit | Microsoft Silverlight 5 Toolkit (relevant for the i4scada 3.8.3 version and higher) |
Silverlight Developer Runtime | Microsoft Silverlight 5 Developer Runtime or newer (relevant for the i4scada 3.8.3 version and higher) |
IDE for Silverlight |
|
IDE for WPF (SmartEditor controls) |
|
IDE for HTML5 |
|
Developing with i4scada Server SDK | Developing |
|---|---|
Operating System | Microsoft Windows 10 (x64) or higher |
IDE |
|
Hardware Recommendations
These hardware recommendations are applicable to i4scada Version 3.9. Actual conditions can vary, depending on the amount of data logging, alarms, and update rates.
Server requirements | Small Projects (Up to 5000 items) | Medium Projects (5000 to 50000 items) | Large Projects (50000+ items) | Large Projects (80000+ items) |
|---|---|---|---|---|
RAM Memory | 16 GB | 32 GB | >32 GB | >64GB |
CPU cores | 4 | 8 | >8 | >12 |
Note
The above server requirements are based on previous projects. However, not every project size meets the recommended requirements.
The main resource-intensive tasks are determined by the signal update rate, alarm trigger rate, and log trigger rate.
For example, a "small" project with 3000 alarms and a flurry of alarms that are triggered regularly will consume more resources than the same project with a slow alarm trigger rate, therefore it is better to have more RAM in general.
A "large" project with 50.000+ signals but a slow signal refresh rate or slow log trigger rate might fall into the "medium" category, which is probably the same category for a "small" project with a fast alarm refresh rate or fast log trigger rate.
As a rule of thumb, we recommend using the next higher project size category if there is some uncertainty or the possibility of expanding RAM / CORE resources during rentier.
A large project with 50.000 + signals requires fast processing of log data. Therefore projects with 50.000+ signals should not be operated with the MS SQL Express Server, it is recommended to use the MS SQL Standard Edition.
For projects with 80.000 + signals, it is recommended to use the MS SQL Standard Edition, with at least 64GB RAM and 12 CPU cores. The cores and RAM are then assigned to the SQL Server, depending on the system load. E.g. 4-6 cores and/or 16-32 GB RAM.
Client requirements | Description |
|---|---|
RAM Memory | 4 GB |
CPU cores | 2 |
GPU | A dedicated graphics adapter or a performant integrated graphics chip. Due to the wide range of available graphic adapters, there is no general recommendation. But using a low-performance graphic adapter will result in slow graphic response and delayed page reaction times. |