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.
For OSIsoft PI: PI AF SDK 2017 or newer is recommended.
For AspenTech IP21: Aspen SQLplus ODBC driver, installed as part of the client tools of AspenOne 8 or higher
For Yokogawa Exaquantum: Exaquantum .NET API provided as part of the historian.
For Honeywell PHD: PHDAPINET.dll to communicate with historians.
For Wonderware: Wonderware 2014 R2 SP1 patch level 2 or higher are supported.
For ODBC/OLEDB: Compatible version of driver/client software to communicate with DBMS.
Anmerkung
TrendMiner customers are responsible for properly licensing, obtaining, and installing historian drivers. TrendMiner does not provide them.
Plant Integrations do not need a lot of disk space and have 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 OSIsoft 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.
It is possible for Plant Integrations to connect to other Plant Integration instances. This ensures optimal performance in distributed setups.