admin

SCADA System Recommendations

VTScada 12.1

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 On Windows® Operating Systems

 Small Systems
Less than 1K I/O

  • 32- or 64-bit Windows OS.
  • 2 GHz dual-core processor.
  • 40 GB free drive space.
  • 4 GB RAM.
  • 100 Mb/s Ethernet or higher.

Medium Systems
1K to 25K I/O

  • 64-bit Windows OS.
  • 3 GHz or more quad-core processor. Note: High clock speeds are more helpful than more cores.
  • Solid State Drive.
  • 1TB free space.
  • 16 GB RAM.
  • 1 Gb/s Ethernet or higher.

Large Systems
Over 25K I/O

  • Medium Systems spec (left) should be adequate for +100K systems.
  • Increase processor clock speed to 4 GHz or higher.
  • Scale to large systems by load sharing services across servers or using Master & Subordinate Apps.
  • If using blade servers, high clock speeds help, more cores don’t.
  • Use segmented networks.

Compatible Operating Systems by VTScada Version

Compatible Operating Systems by VTScada Version

Note: VTScada runs on Windows® 10 IoT Enterprise not IoT Core. Microsoft has ended support for XP®, Vista®, Windows 7®, Windows 8®, Server 2008®, and Server 2008 R2®.

Alarm
Notifications

  • 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.

Virtualized
Servers

  • 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.

Other
Recommendations

  • If you need RS-232 ports to communicate with legacy devices, we recommend Ethernet to serial converters.
  • Keep VTScada & History data on separate drive from OS.
  • NetDDE is not available on Vista and higher (removed in XP Service Pack II).
  • VTScada uses IANA registered TCP/IP port 5780. Set up firewalls to route RPC traffic accordingly.
  • VTScada’s architecture makes RAID drives unnecessary in redundant systems. For performance reasons, they are not ideal for any historian. If you must, use SSDs for better performance.

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 VTScada Anywhere Client
For HTML5-Compliant Browsers on Mobile Devices, PCs, Macs, and LINUX

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

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

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®.
    or…
  • Run a small desktop program (downloaded once from your application via a browser)

PC Hardware – See “Small Systems” recommendations above.

PC OS – Windows 8® or newer

Contact Us For Help Download This Datasheet