Skip to content
YTCC

Fundamentals 9 min read

How to choose SCADA software: what to check before you buy

What to check when you choose SCADA software and what to ask each vendor: protocols, the engineering tool, clients, alarms, historian, permissions, the license model and a trial.

Published:

A sample YTCC runtime screen for Renewable Energy (Solar / Wind / Hydro): process diagram, status cards, gauges, a trend chart and the alarm list.

SCADA software runs in a plant for years. The product you pick today is the one you will extend, maintain and relicense later. So base the decision on your devices, your team and your budget.

This article does not compare named products. It lists what to look at when you evaluate YTCC or other SCADA software, and the questions to put to each vendor. For the browser-based approach itself, see What is web-based SCADA?.

Write down your own requirements first

Before you look at products, describe your plant on one page. Without that page you end up comparing demos; with it, you ask every vendor the same questions.

  • How many signals will you read today, and how many in five years?
  • Which devices are in the field, and which protocols do they speak?
  • How many operator stations will you have? Will people also check screens from tablets or phones?
  • Which roles do you need: operator, maintenance, engineer, manager?
  • How long do you have to keep measurement and alarm history?
  • Who builds the project and who extends it: your own team or an integrator?

Can it talk to your field devices?

A protocol name on a datasheet is not enough. The role and the scope of the same protocol differ between products:

  • Role: To poll RTUs and PLCs in the field, the software needs the client (master) role. Check that each protocol offers the role you need.
  • Read and write: Some drivers only read. If you will send commands, ask which command types are supported.
  • Transport: How does the software reach your devices? Can you use the protocol’s security options, such as TLS and Secure Authentication in DNP3, or Sign and SignAndEncrypt in OPC UA?
  • Device side: Some devices need settings of their own. For outside access to a Siemens S7-1200 or S7-1500, PUT/GET access has to be enabled.

The surest answer comes from a test with your own device list. Find out at this stage whether each driver is priced separately.

Where does the engineering happen?

Screens, signals and alarms are built in an engineering tool. That tool may be a desktop program installed on a separate computer, or it may run in the browser. Ask:

  • Does the engineering tool need a license of its own?
  • Is there a ready-made symbol library? Can you draw a pump once and reuse it everywhere with parameters?
  • Can you import thousands of signals in bulk from Excel or CSV?
  • Can you write scripts for server-side logic such as calculations, schedules and automatic actions? In which language, and what can a script reach on the server?

Clients and access

Ask what has to be installed on each operator station and whether each client costs money. With installed clients, every station needs its own setup and updates. With browser-based systems the client is a web browser, and installation and updates happen on the server.

If screens will open on different sizes, ask whether you can design separate tablet and phone layouts of the same page. Process screens do not reflow like web pages.

Changes on a running system

In a plant that runs around the clock, stopping the system for every change is expensive. Ask whether adding a point or fixing an address restarts the driver. Is a change validated before it is applied, and does the tool show the difference from the current state? What happens when a driver crashes: does it restart by itself, and how does the operator see it?

Alarm management

Every product has an alarm list. The differences show when the number of alarms climbs. How do priorities, alarm groups, acknowledgement modes, shelving and out-of-service work? Does the system detect chattering alarms and alarm floods? When communication with a device is lost, do you get one alarm for each of its signals or a single alarm for the device? There is more on this in the article on alarm floods.

Historian and charts

Where is the history of measurements, alarms and commands stored? Does the database need a separate commercial license? Can you set which signals are archived, how often, with which deadband and for how long? Can you export the history to Excel or CSV?

Users, permissions and audit

Can you define your own roles? Are permissions checked in the browser or on the server? A button hidden in the browser is not a security measure. Also ask:

  • Are commands logged with the user, the value and the result? Do rejected commands go to the log too?
  • Do configuration changes keep the old and the new value?
  • Can two operators send commands to the same part of the plant at once, or does one person take control?
  • Can you set a password policy and lock accounts after failed logins?

Security and network layout

Part of security lives in the product and part in how you design the installation. NIST SP 800-82 recommends separating control systems from the business network in layers and granting access with least privilege. Ask the vendor which network segment the server belongs in, whether communication between its components is open to outside networks, and how far server scripts can reach files, the network and the field.

License model and total cost

SCADA licenses count different things: signals or tags, clients, servers, drivers or modules. Most add a yearly maintenance fee. That makes side-by-side price lists misleading. Give every vendor your own scenario instead: today’s signal, driver and client counts and your estimate for five years out. Then ask:

  • Does adding clients or users cost extra?
  • Are all features in the license, or are alarms, historian or scripting separate modules?
  • Is there a free tier for a small project or a trial? If so, does it cover commercial use?

Total cost also includes maintenance, engineering hours, server hardware and training.

Backup, migration and support

How do you back up a project and move it to another computer? What does the backup include: screens, configuration, users, history? Pin down support as well: which hours come with the license, which agreement covers 24/7 support if you need it, and through which channel you send requests.

Try it yourself

In a demo, the vendor’s own project is running. Before you choose, install the software on your own computer and run a small test:

  1. Connect to a device in the field and read a few signals.
  2. Draw a screen and bind its objects to those signals.
  3. Define an alarm, trigger it and acknowledge it.
  4. Send a command and check whose name the log shows.
  5. Add a point while the system is running.
  6. Back up the project and move it to another computer.

Checklist

TopicAsk the vendor
ProtocolsWith my devices, in which role, and with reads and writes?
EngineeringWhere does the tool run, and does it need its own license?
ClientsWhat goes on a station, and is there a fee per client?
ChangesDoes adding a point restart the driver?
AlarmsGroups, acknowledgement modes, chattering and flood detection?
HistorianA separate database license? Can I set retention?
Permissions and auditChecked on the server? Are commands logged by user?
LicenseWhat is counted, and what will I pay in five years?
Backup and supportWhat does a backup include? Which support hours and channel?

Frequently asked questions

Web-based SCADA or SCADA with installed clients?

If you have many operator stations, or people will view screens from different devices, a browser-based system moves client maintenance to the server. Decide together with your network layout and your security requirements.

How do I compare SCADA licenses?

Give every vendor your signal, driver and client counts and ask for the total cost today and in five years. Then you are comparing prices for the same scenario.

Can a free SCADA edition be used on a commercial project?

That depends on the license terms. Some free editions are for evaluation or non-commercial use only; others come with a time or signal limit. Get the commercial-use terms and the limits in writing.

Do I need a pilot project before I choose?

Yes. A small pilot with your own device answers most protocol and screen questions more clearly than a demo.

In YTCC

YTCC is an advanced SCADA/HMI platform with a core written in Rust. It runs on your own server; you design and operate from the browser. No client installation is needed besides the browser, and screens open from computers, tablets and phones on the local network.

Its drivers talk Modbus TCP, Siemens S7, OPC UA, IEC 60870-5-101, IEC 60870-5-104, IEC 61850 (MMS), DNP3, BACnet/IP, MQTT, SNMP, Beckhoff ADS and EtherNet/IP. Each driver instance runs in its own process, and the supervisor process restarts a driver that crashes. In the main drivers, adding and removing points and changing addresses and scaling apply without restarting the driver. You import signals in bulk from Excel or CSV. You write server scripts in TypeScript, and they run in a sandbox with no file, network or process access.

Alarm groups can be nested. There are four acknowledgement modes, chattering and flood detection, and shelving with a required reason and a time limit. When communication is lost you get one alarm per device. The historian keeps a separate database for each project, with no commercial database license needed. Role-based permissions are checked on the server, and logins, configuration changes and commands go to the audit log. One user at a time controls a responsibility zone.

Capacity Units (CU) set the price: the points you read from the field and the protocol drivers you use are counted, and clients are not. Every plan includes all features. 80 CU or less is free, commercial use included. Work out your own scenario with the calculator on the Pricing page. The project configuration is backed up in one file and moved to another computer (historian data excluded). Business-hours support is included with every license.

The protocols and the architecture are covered in detail on the Platform page. To test it with your own devices, download YTCC.

Sources

  1. NIST SP 800-82 Rev. 3: Guide to Operational Technology (OT) Security (opens in a new tab)
  2. SCADA (Wikipedia) (opens in a new tab)
  3. Alarm management (Wikipedia) (opens in a new tab)

More articles

  • A sample YTCC runtime screen for Water and Wastewater: process diagram, status cards, gauges, a trend chart and the alarm list.

    Fundamentals 8 min read

    What is SCADA and how does it work?

    SCADA collects data from field devices and gives a control center monitoring, alarms, history and remote control. Its parts, how it works and where it is used.

  • Aerial view of a water treatment plant with settling tanks and filter beds

    Fundamentals 7 min read

    SCADA vs HMI vs PLC vs DCS: what is the difference?

    A PLC controls in the field, an HMI shows the process to the operator, SCADA watches scattered sites from a control center and a DCS runs one plant's process as a single system.

YTCC. Your trusted control center for energy and industrial SCADA.

Download YTCC and build your first screen.