SCADA System Recommendations

VTScada 12.1

Updated January 16, 2024

This is simply a guide. Actual SCADA software requirements will depend on your application architecture.

Contact Us For Help Download This Datasheet

VTScada PC Recommendations

For VTScada Licenses Installed

Small Systems
Up to 1K Licensed Tags
Medium Systems
1K to 25K Licensed Tags
Large Systems
25K to 100K Licensed Tags
Enterprise Systems
Over 100K Licensed Tags
Windows OS 32- or 64-bit 64-bit 64-bit 64-bit
Processor* 2 GHz Dual Core 3 GHz Quad Core 4 GHz Quad Core 4+ GHz Quad Core
RAM 8GB 16 GB 32 GB 48 GB
Hard Drive 500 GB 1 TB 2 TB SSD 4 TB SSD
Historical Logging 1K data changes/sec requires 1,500 GB/year

* High clock speeds are more helpful than more cores.

Compatible Operating Systems by VTScada Version

Compatible Operating Systems by VTScada Version

Microsoft has ended support for: XP®, Vista®, Windows 7®, Windows 8®, Windows 8.1®, Server 2008®, Server 2008 R2®, Server 2012®, and 2012 R2®.


  • Text-to-speech phone alerts require a voice modem or web-based messaging service like Twilio®.
  • See the VTScada Users Forum for help choosing modems.
  • Connection to an email server required for email alarm notifications.
  • Cell modem or email account required for text alarm notifications.
  • Sound card and speakers required for local alarm annunciation.


  • VTScada can run on virtual Servers.
  • Don’t clone virtual servers with VTScada installed. To learn more, search ‘virtual servers’ in VTScada Help.
  • Ensure host PCs have enough capacity for all VMs, e.g., CPU, RAM, drive space, ports, Ethernet bandwidth.
  • Twilio (left) offers a simple alternative to configuring voice modems in virtual server environments.


  • Load share services across servers.
  • Use Master & Subordinate Apps.
  • Configure RAID with solid-state drives (SSDs).
  • Keep VTScada & History data on separate drive from OS.
  • VTScada can use up to 4 CPU cores.
  • Provide enough RAM for the OS and file cache (About twice the number reported in the VAM).

VTScada Thin Clients on Mobile Devices

For Thin Client Connections on Devices Without VTScada Installed

  • Requires a connection to a running VTScada application server with Thin Clients enabled.
  • Does not require Remote Desktop Protocol® (RDP).
    Does not require dedicated thin client hardware such as Wyse® devices.
  • Performance is more related to the quality of the server and network rather than the power of the end user devices below.
  • Thin Clients work well over slower connections so long as the network latency is low.
  • The VIC (below right) can support multi-monitors and graphical configuration tools.

The VTScada Anywhere Client
For HTML5 Browsers on Mobile Devices, PCs, Macs, and LINUX

To Launch – Enter a URL into one of the browsers below.

  • Safari® (OS X, iOS)
  • Chrome® (Windows®, Android®)
  • Firefox® (Windows®)
  • Edge®(Windows®)

Phone Hardware – 2 GB RAM (at least 200 MBs free space)

PC Hardware – See “Small Systems” recommendations above.

The VTScada Internet Client (VIC)
For Windows Desktops, Laptops, and Servers

To Launch

  • Enter a URL into a Windows browser such as Chrome®, Firefox®, or Edge®.
  • Run a small desktop program (downloaded once from your application)

PC Hardware – See “Small Systems” recommendations above.

PC OS – Windows 12® or newer

Contact Us For Help Download This Datasheet