Remote IDAS requirements

A remote IDAS (I/O data acquisition service) runs on all supported operating systems: domain member, stand-alone workstation, or server. The IDAS accepts data coming from SuiteLink and other I/O sources, and forwards that data to the Historian and other components, such as the Trend Client.

To determine the CPU and memory needed for a remote IDAS, use the same guidelines of the Historian computer. For more information, see Server requirements.

The IDAS computer does not necessarily have to be as powerful as the server computer, because it will not be performing all of the same functions (for example, processing SQL Server transactions), but it should be powerful enough to handle the tag load that you expect.

The amount of free disk space required depends on whether or not you will have store-and-forward enabled for the IDAS. If store-and-forward is enabled, you need to make sure that the disk space on the remote IDAS computer is sufficient to store cached data if the network connection to the historian fails. Estimate the disk space requirements for a remote IDAS as that of the historian. For more information, see Disk space requirements for historical data files.

A remote IDAS configured for store-and-forward has more stringent requirements on memory to ensure that the IDAS local storage engine has sufficient resources to run properly. In general, estimate memory requirements for a remote IDAS configured for store-and-forward the same as you would for a historian having the corresponding tag count.