Server requirements
Server requirements for both the TrendMiner Server and the Plant Integrations connector are discussed in the following sections.
TrendMiner Server
The table below summarizes the system requirements for the (virtualized) TrendMiner server. TrendMiner always recommends provisioning the Recommended specifications to ensure a consistent and performant UX.
These resources may be increased with increasing TrendMiner usage or number of connected data sources. Please work with TrendMiner support to determine the projected resource requirements.
A few important notes on the disk space requirement:
The required disk space highly depends on the usage of the system: number of users and the amount of items they save on the system + the number of tags which are added and indexed. If usage increases further disk space increases might be required.
TrendMiner strongly advises thick provision of the VM TrendMiner is running on to avoid over-provisioning and increase write performance. Over-provisioning can result in TrendMiner going down because of a full disk without upfront alarm to the TrendMiner admin.
The TrendMiner Virtual Appliance is imported into a virtualization environment. TrendMiner provides images for VMware ESXi and Microsoft Hyper-V.
TrendMiner supports these hypervisors:
VMware ESXi 5.5 or higher.
Microsoft Windows Hyper-V Server 2012 R2 or higher
Other prerequisites:
Gigabit Ethernet or better is required for TrendMiner to work.
The TrendMiner appliance uses Kubernetes (K3S) as its infrastructure layer, which needs a range of IP addresses for internal communication between different pods and services. The following IP addresses should not be used by other applications/servers running on the network on which TrendMiner is deployed:
Plant Integrations system requirements
TrendMiner Plant Integrations is a web application running on Windows Internet Information Services (IIS). It is provided as a Web Deploy archive that can easily be deployed.
Since the Plant Integrations module is mainly a data transfer gateway, the hardware requirements are rather limited. They are listed below.
Resource | Amount |
|---|---|
vCPU | 2 |
RAM | 2GB |
Disk Space | 5GB |
The software requirements to successfully deploy the Plant Integrations module are:
Windows Server 2012 R2 or higher
IIS 7 or higher
.NET Framework 4.8 or higher
IIS Web Deploy 3.5 or higher
Depending on the historian connectivity desired, additional software is necessary:
Anmerkung
TrendMiner customers are responsible for properly licensing, obtaining, and installing historian drivers. TrendMiner does not provide them.
Plant Integrations does not need a lot of disk space and has very modest processing requirements. It can be installed on a dedicated machine, added to another web server, or installed on a historian server. The installation location of Plant Integrations depends on the historian connectivity required:
For Aveva PI: the PI AF SDK drivers provide good connection pooling and efficient transfer. The Plant Integrations and historian need not be co-located.
For other historians, TrendMiner recommends installing Plant Integrations on the historian server, as their drivers are normally firewall-unfriendly or latency-sensitive, mostly using DCOM. Experience tells us that an installation on the historian server leads to a better performance than installations that simply use the same network.