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.
Warning
Security recommendation
To ensure secure communication between TrendMiner and your data sources, we strongly recommend enabling security features for the connector. This includes:
HTTPS/SSL encryption to protect data in transit. Learn how to enable HTTPS/SSL: How to enable HTTPS/SSL connection to the Connector?
Basic Authentication to restrict access to authorized users. Learn how to enable Basic Authentication: How to enable basic authentication for the connector?
Enabling these features helps prevent unauthorized access and protects sensitive data from interception.
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:
Note
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.