Historian 2022 System Requirements

Software Requirements

Operating SystemHistorian requires one of the following operating systems, with latest service packs or revisions:
  • Microsoft® Windows® Server 2022 (64-bit)
  • Microsoft® Windows® Server 2019 (64-bit)
  • Microsoft® Windows® Server 2016 (64-bit)
  • Microsoft® Windows® Server 2012 R2 (64-bit)
  • Microsoft® Windows® 11 (64-bit)
  • Microsoft® Windows® 10 IoT (32-bit or 64-bit)
  • Microsoft® Windows® 10 (32-bit or 64-bit)
  • Microsoft® Windows® 8.1 Professional (32-bit or 64-bit)

Hardware Requirements

Standard Historian Server
Hardware Component Requirement
RAM 8 GB
Disk size An 80 GB free hard-drive space for the data archives, message files, buffer files, and log files used by the system
Processor Intel Core i3 or i5 or i7 CPU or an equivalent AMD Phenom CPU
CPU 2.4 GHz
Other requirements
  • A DVD-ROM drive.
  • 100 Mbps TCP/IP-compatible network interface adapter for network communication and certain I/O drivers.
Data Collector Node
Hardware Component Requirement
CPU speed, processor type, and RAM A 2.0 GHz clock-speed Intel Core i3 or i5 or i7 CPU or an equivalent AMD Phenom CPU with a 2 GB RAM.
Disk size A 40 GB free hard-drive space to store buffer data.
Other requirements
  • A DVD-ROM drive.
  • A TCP/IP-compatible network interface adapter for network communication and certain I/O drivers.
Network Speed

For a large Configuration Hub setup, it is recommended that the network speed is 1 GBPS.

Note:
  • 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.

Important: If you want to enable the Strict Authentication feature in Historian 7.2, be aware that you will need to apply the latest SIMs that support this feature for all Proficy clients that connect to the Archiver, including the ones listed in this table. In addition, there may be SIMS to allow pre-5.0 collectors and client applications such as Excel Add-In to connect. Refer to the SIM download page for update for Historian and other Proficy products.
Product Supported Version
CIMPLICITY 11.1, 2022
iFIX 6.5, 2022
Plant Applications 8.2, 2022
Workflow 2.6, 2.6 SP1
Operations Hub 2.1, 2022
Configuration Hub 2022
Proficy Authentication 2022
DreamReport 2020

* 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.

Important: Do not install Operations Hub and Web-based Clients on the same machine.

Steps to Download Your GE Digital Software