Historian 2024 System Requirements
Software Requirements
Operating System
- Microsoft® Windows® Server 2022 (64-bit)
- Microsoft® Windows® Server 2019 (64-bit)
- Microsoft® Windows® Server 2016 (64-bit)
- Microsoft® Windows® 11 (64-bit)
- Microsoft® Windows® 10 (64-bit), Professional ,or Enterprise Edition
- Microsoft® Windows® 10 IoT Enterprise with LTSC enabled
- The TCP/IP network protocol is required
Microsoft®.NET Core or .NET Framework
- Microsoft®.NET Core Framework 3.1: This is required if you want to use the new Client Access API.
- Microsoft®.NET Framework 4.8: This is required on the machine on which you will install the Excel Add-in for Operations Hub. In addition, this is required for Historian collectors.
- Microsoft®.NET Framework 4.5.1: This is required for all the other Historian components. You can install it manually, or you will be prompted to download and install it while installing Historian.
Microsoft® SQL Server®
- Microsoft® SQL Server® 2019
- Microsoft® SQL Server® 2017
Browser
- Firefox version 46 or later
- Google Chrome version 92 or later
To access Configuration Hub, use Google Chrome only.
Screen Resolution
- 1280 x 1024
- 1366 x 768
Microsoft Excel
- Microsoft® Excel® 2021 (32 & 64 bit)
- Microsoft® Excel® 2019 (32 & 64 bit)
- Microsoft® Excel® 2016 (32 & 64 bit)
- Microsoft® Excel® 2013 (32 & 64 bit)
Web Server
- Microsoft®.NET Framework 4.5.2
- Historian Client Tools 7.0 or later
- OLE DB, User API, and Historian Client Access Assembly
Hardware Requirements
Standard Historian ServerHardware Component | Standard Historian | Enterprise Historian, Data Mirroring |
---|---|---|
RAM | 8 GB | 16 GB or 32 GB (recommended) |
Disk size | 80 GB free hard-drive space | 250 GB (minimum) |
Processor type | Intel Core i3 or i5 or i7 CPU or an equivalent AMD Phenom CPU | Intel Core i5, i7 family, or equivalent |
CPU | Dual/Quad cores | |
CPU speed | 2.4 GHz | 2.8 GHz |
Recommended CPU clock | 2.4 GHz | 2.8 GHz |
Storage type | SAS SSD with RAID Level 0 configured | |
Operating system |
|
|
Tags | Up to 50,000 | |
Years of data online | 1 year | |
Other requirements |
|
- The number of tags from which data is collected. The number of tags is an indicator of the number of concurrent users likely to access the system. The primary factor is server memory requirements; CPU load is a secondary factor. If the number of concurrent users is significantly different from the suggested guidelines, adjust server memory size accordingly.
- The rate of alarms and events collection.
- The frequency of data collection.
- The amount of data you want to keep online.
Hardware Component | Less than 10,000 tags | 10,000 to 50,000 tags | 100,000 to 1,000,000 tags | 1,000,000 to 2,000,000 tags | 2,000,000 to 5,000,000 tags |
---|---|---|---|---|---|
RAM (GB) | 8/16 (recommended for a single node setup) | 16 or 32 | 16 or 32 | 16 or 32 | 32 or 64 |
Disk size (GB) | 100 or 250 | 250 | 250 | 500 | 500 |
Processor type | Intel Core i5, i7 family, or equivalent | Intel Core i5, i7 family, or equivalent | Intel Xeon (56xx, E5 family or AMD Opteron 42xx/62xx family) | ||
CPU | Dual/Quad core | Dual/Quad core | Dual/Quad core | 2-socket | 2-socket or 4-socket |
CPU speed (GHz) | 2.8 | 2.8 | 2.8 | 2.6 | 2.6 |
CPU clock speed (GHz) | 2.8 | 2.8 | 2.8 | 2.6 | 2.6 |
Storage type | SAS SSD with RAID Level 0 configured | SAS SSD with RAID Level 0 configured | Direct-attached or shared storage with SAS enterprise class drives. Hardware RAID controller with cache memory. SAN recommended over NAS. | High-speed shared storage with SAS or SSD drive types. Hardware RAID controller with cache memory. SAN recommended over NAS. | |
Years of data online | 1 | 1 | 1 | 1 | 1 |
- The Historian server runs only on 64-bit versions of Windows.
- When possible, for performance reasons, consider using computers with multiple disk drives so that archives and buffers can be given their own drive. Or, multiple data stores can each have their own drive.
- Sustained event rate is 60-100 million samples per minute.
- Historian supports Intel Core i3, i5, i7 Duo based processors as long as they are compatible with the operating system.
- Historian does not support Titanium processors.
Hardware Component | For a Medium-sized Server | For a Large-sized Server |
---|---|---|
Processor type | Intel Xeon 5540 | Intel Xeon E5-2670 or E5-4650 |
CPU | Dual socket | Dual socket or quad socket |
CPU speed (GHz) | 2.5 | 2.7 |
RAM (GB) | 64 | 256 |
Hardware Component | Recommendation |
---|---|
RAM (GB) | 8 |
Disk size (GB) | 80 |
Historian collectors | 32-bit or 64-bit Note: GE Data Collector for Wonderware support only
64-bit |
- Historian Collectors work as 32-bit applications on a 64-bit Windows operating systems using WoW64 mode (Windows-on-Windows 64-bit). However, you can read and write data from a 64-bit Historian Server.
- RAM and Disk Size required may vary based on the collectors available on the system.
- Recommended number of tags per collector is 20 to 30K.
- For iFIX systems, count each Node.Tag.Field (NTF) as a separate tag when you determine the size of the system. For example, FIX.FIC101.F_CV and FIX.FIC101.B_CUALM (current alarm) both count as tags, even though they are derived from the same iFIX tag.
Microsoft Windows Server
Hardware Component | Requirement |
---|---|
CPU speed, processor type, and RAM | 2.6 GHz clock-speed Intel Core i3 or i5 or i7 CPU or Xeon or equivalent AMD Opteron CPU with minimum 8 GB RAM. |
Disk size | 80 GB free hard-drive space and a 40 GB shared SCSI hard drive (RAID preferred). |
Other requirements | Two 100Mbit TCP/IP-compatible network interface adapters for network communication and certain I/O drivers (one for public network, another for private network). |
Hardware Component | Requirement |
---|---|
Operating System | 64-bit Windows operating system |
RAM (GB) | 8 (minimum) Note: If using a single-node setup, 32 GB are
recommended. |
Processor type | Dual-core processor |
Ensure that you are using the same hardware requirement for the mirror node as well.
Network SpeedFor a large Configuration Hub setup, it is recommended that the network speed is 1 GBPS.
- If you are using a single node setup, then it is recommended to use 32 GB RAM.
- Ensure that you are using the same hardware requirement for the mirror node as well.
- You must have a minimum of 10 GB free space available for the data archiver to start.
- Many desktop-class computers are not certified to run Windows server. Check the Microsoft website and your computer hardware vendor website for possible conflicts between your hardware and Windows server. These specifications are sufficient to meet the needs of a small pilot application. However, production system requirements may be significantly different depending on many application-specific factors. Please contact your product manager to review the requirements of your application.
Compatibility with Other Products
Several GE products work with Historian. The following is a general set of required versions to work with Historian.
Product | Supported Version |
---|---|
CIMPLICITY | 11.1, 2022 |
iFIX | 6.5, 2022, 2023 pre-release |
Plant Applications | 8.2, 2022, 2023 pre-release |
Workflow | 2.6, 2.6 SP1 |
Operations Hub | 2.1, 2022, 2023 pre-release |
Configuration Hub | 2023 |
Proficy Authentication | 2023 |
DreamReport | 2020 for Proficy |
* For customers using iFIX, there was a change in the HKEY_CURRENT_USER registry values for WebSpace and it will no longer work with the existing SIM. Ensure that you get the latest iFIX SIMs. The following article provides additional instructions: https://ge-ip.force.com/communities/en_US/Article/iFIX-Webspace-Strict-Historian-Authentication
** For Plant Apps customers using the ‘Historian Type = ‘GE Proficy – Historian 3.0’
to connect to Historian 7.2, both the Enabled and Disabled options for Enforce Strict Client Authentication selection are supported.
** For Plant Apps customers using the ‘Historian Type = ‘GE Proficy – Historian’ to connect to Proficy Historian 7.2, only the Disabled option for Enforce Strict Client Authentication selection is supported.
In Historian 5.0, the Historian HKEY_CURRENT_USER registry key values were changed. The programs accessing the server collection through the SDK are unaffected. Any program or script that directly accesses the registry keys or any Terminal Server login scripts that try to configure a list of servers by importing registry keys directly will no longer work. Such programs need to access the server collection via SDK calls, not directly.
Historian REST APIs are required to integrate between Historian and Operations Hub. Historian REST APIs are installed automatically when you install Historian Web-based Clients.