Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

InTouch HMI quick start deployment

Quick deployment hardware guidelines

  • Last UpdatedSep 23, 2024
  • 3 minute read

The following guidelines provide a range of choices for the type of system you wish to deploy. These guidelines focus on small, stand-alone systems with options for managed applications. This focus on a quick start deployment still gives you considerable flexibility, starting with these guidelines for preferred hardware types, followed by recommendations for each hardware type.

Preferred hardware by component

The following tables show preferred hardware types for different InTouch functions. For comparison purposes, standalone applications (InTouch 2023 R2) are included along with managed applications (InTouch for System Platform 2023 R2).

Also included for reference is InTouch Access Anywhere (ITAA), an InTouch extension that provides mobile and casual users access to InTouch applications via HTML5-compliant web browsers. ITAA appears grouped with RDP (Remote Desktop Protocol) which provides a graphical interface to connect to another computer over a network connection.

Thin Client Node Hardware

Client Node Hardware

Server Node Hardware

Thin Client Server Node Hardware

All-in-One Demo Node Hardware

AVEVA InTouch 2023 R2

WindowMaker

RDP

Supported

Preferred

Supported

Supported

WindowViewer

(run time only)

ITAA, RDP

Preferred

Supported

Supported

Supported

InTouch Web Clients

(run time only)

ITAA, RDP

Preferred

Supported

Supported

Supported

AVEVA InTouch for System Platform 2023 R2

WindowMaker

(Managed Apps)

RDP

Supported

Preferred

Supported

Supported

WindowViewer

(run time only)

ITAA, RDP

Preferred

Supported

Supported

Supported

Hardware recommendations

The following table shows both minimum and recommended hardware-specific levels of storage, RAM, and network speed for each hardware type, sorted by application type. Recommendations are limited to small systems, either all-in-one or standalone client and standalone server systems. Hardware requirements for larger, distributed systems are provided later in the InTouch HMI deployment guide, larger system deployments.

This table also includes hardware more specific to the Application Server IDE, necessary for managed applications, for comparison purposes.

Hardware class

Application

Level

Processors Cores

RAM

Free Disk Space

Network Speed

Thin Client Node Hardware

Thin Client Nodes

RDP clients, ITAA, mobile devices

Minimum

2

512 MB

N/A

100 Mbps

Recommended

4

2 GB

N/A

100 Mbps

Client Node Hardware

Client Nodes

WindowViewer, ViewApp (IDE), Historian Client, Remote IDE

Minimum

4

1 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Server Node Hardware

Application Server Nodes

Small Application

(1 - 25K I/O per Node)

Minimum

4

2 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Thin Client Server Node Hardware

Remote Desktop Server Nodes

Basic RDS, ITAA Server

(Supports up to 15 concurrent remote sessions)

Minimum

8

8 GB

200 GB

1 Gbps

Recommended

16

12 GB

500 GB

1 Gbps

All-In-One Demo Node Hardware

All-In-One Nodes

Small Application - All products on one node: 1,000 I/O max.

Minimum

8

8

200 GB

100 Mbps

Recommended

12

12 GB

500 GB

1 Gbps

Notes

1) Processors cores: Indicates physical cores. Note that the number of Logical Cores available to applications running on the CPU may be higher due to hyperthreading, but this table refers to the number of physical cores in the CPU die.

2) Free disk space: SSD drives are highly recommended

3) In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization (60% free resources)

4) For optimal performance of all-in-one nodes, a high clock speed (>3.0 GHz) is recommended.

5) For Application Server platform nodes, it is recommended that you deploy no more than two AppEngines per logical processor (typically one primary AppEngine and one backup).

6) For large applications on all-in-one nodes, dual XEON processors are recommended.

In This Topic
TitleResults for “How to create a CRG?”Also Available in