SCADA System Requirements

These operating system and hardware specifications are provided as a guide. Actual HMI SCADA software system requirements will depend upon your specific SCADA application architecture. We are happy to assist you with this choice. Contact us for recommendations for systems including Panel PCs.

For Installed Runtime or Development Runtime Licenses

VTScada 11.2 Minimum Requirements

Servers or Workstation PCs

  • 32 or 64-bit Windows Operating System (See table below)
  • 2GHz dual-core processor
  • 20GB free hard drive space
  • 8GB of RAM

Laptops, Tablet PCs, and Panel PCs

  • 32 or 64-bit Windows Operating System (See table below)
  • 2GHz dual-core processor
  • 20GB free hard drive space
  • 4GB of RAM

Recommendations

  • 64-bit versions of the Windows OS for all systems.
  • 3GHz dual or quad core processors.
  • More cores won’t help to increase performance, but higher clock speeds will.
  • 16Gb or more of RAM for systems over 100K tags.
  • Solid State Drives (SSD) for the highest performance.
  • Avoid using RAID for file-based Historian.
  • Keep historian on a separate hard drive from VTScada and the OS.
  • Windows-compatible printer to print VTScada pages or reports.
  • 100Mb/1Gb Ethernet required for networking.
  • A voice modem is required for the VTScada Alarm Notification System to send voice phone notifications.
  • An SMS Appliance is required for the VTScada Alarm Notification System to send text notifications.
  • A connection to an email server is required for the VTScada Alarm Notification System to send email notifications.
  • Sound card and speakers are required for alarm annunciation.
  • RS-232 port if needed for communications with serial I/O devices.
  • VTScada supports virtual servers. However, avoid more than one VS per computer if one of them (i.e. VTScada) is mission critical.
  • Cloning a virtual server with VTScada installed leads to repository issues.
  • WAP was removed in version 11.2. Use VTScada Thin Clients instead.

Compatible Operating Systems

VTScada Compatible Operating Systems

Note: VTScada versions 11.1 and 11.2 support the Windows 10® operating system.

For Thin Clients on Smartphones, Tablets, Desktops, and Laptops

Windows Desktop/Laptop Systems

The VTScada Internet Client (VIC)

  • Requires at least one installed VTScada License to act as the server
  • Requires one or more concurrent VTScada Thin Client licenses
  • Launch clients from any networked computer running Windows Server 2003 or newer (no VTScada installation required)
    • Launch using Internet Explorer (ensure ActiveX is enabled) using a web address (URL)
    • Launch from your desktop using a small program downloaded once from your VTScada server via any browser

Other Operating Systems

VTScada Anywhere Client and the VTScada Mobile Internet Client (MIC)

  • Network connection to a running VTScada server
  • An HTML5-compliant web browser. We recommend the latest versions of the following:
    • Safari® (OS X, iOS)
    • Chrome® (Windows®, iOS®, Android®)
  • Other HTML5-compliant browsers
    • Microsoft Edge® (Windows®)
    • Opera® (Windows®, iOS®, Android®)
    • Firefox® (Windows®, iOS®, Android®)
    • Internet Explorer Mobile® (Windows Mobile®)

Recommended Modems

Please see our Recommended Modems page for more info.

Please Note

  • NetDDE is not available on Windows Vista and higher. (It was removed in XP Service Pack II)
  • VTScada 10 and higher uses IANA registered TCP/IP port 5780 (not 1160). Configure firewalls to route RPC traffic accordingly.
  • When reusing internal modems or sound cards ensure that new computers have the correct motherboard slots.
  • Ensure 3rd-party software used with VTScada (e.g. accounting, reporting) is compatible with new OS.
  • There are no drivers that allow A-Open modems to work with an OS newer than Vista.
    Download this guide to learn more about selecting and configuring modems.
  • When using virtual servers; never clone a computer after installing VTScada to make another virtual image (this leads to repository issues since both computers will have the same machine GUID in the registry)
  1. Server 2008 computers often require speakers or audio cards for some Alarm Notification functionality. Manual modem configuration may be required.
  2. Windows has discontinued support for XP® and Server 2003®. https://support.microsoft.com/en-us/help/14223/windows-xp-end-of-support