Scalability is one of the most important considerations when choosing SCADA software. Once this significant investment has been made, how do end users get the most from it? Or more simply, how long will it last? Here are five ways to keep your SCADA young at heart.
1. Choose Built-In Core Functionalities
The first step is to ask your consultant, integrator, or OT department how many third-party software products will need to be integrated to provide the required functionality. Using third-party alarm notification products with SCADA systems often leads to issues with compatibility after numerous software or firmware updates. Additionally, if a third-party component is discontinued, it can cause significant problems. Choose a SCADA platform where all core functionalities, including the historian and communication drivers, are built-in. This approach prevents SCADA applications from becoming outdated prematurely. VTScada, for example, develops and maintains every part of its software, ensuring that each critical component works seamlessly with every update.
See integrated VTScada features.
2. Minimize Custom Coding – AKA Technical Debt
Another common issue with SCADA systems is the reliance on custom coding. While many integrators are accustomed to scripting standard features as well as those specific to individual customers, it becomes problematic over time. Maybe the person who wrote it has left or maybe so much time has passed that it’s difficult to understand how the code is meant to work. The more code you write, the more time it will take to maintain in the future. This problem is known as Technical Debt. Additionally, custom code makes it risky to upgrade the SCADA software or the operating system. To avoid this, choose a platform where core components like logging, trending, reporting, alarm management, mapping, and version control are pre-configured out-of-the-box. VTScada allows robust customization where needed but provides a standard set of advanced, ready-to-use features. This vastly reduces development time and makes it easy to grow and maintain indefinitely.
3. Don’t Assume Offline Servers Age Better
Many users attempt to manage reliability and security by locking SCADA servers in a room with no internet access and avoiding any updates to the SCADA software or the server operating system. The fear is that updates will disrupt custom coded features or break compatibility with third-party components. However, this eliminates new efficiency features, and more importantly, critical security updates. Note that offline servers are not inherently secure. Sophisticated malware can still piggy-back in on unknowing users and developers. Also, Microsoft® regularly deprecates older versions of their Windows®. Unlike other products, the most recent version of VTScada is compatible with the latest version of Windows.
See VTScada’s compatibility chart here.
4. Use Multiple Servers
Another reason many don’t update their systems is that they only have one server and don’t want to take it offline for fear of permanently missing logged data or critical alarms. Adopting one or more redundant servers allows you to transfer control to a backup while you make necessary updates. For critical systems, having multiple distributed servers is a critical part of ensuring resilience. Unlike other platforms, VTScada supports any number of redundant hot-backup servers that sync automatically over a WAN or LAN. No fragile scripting is required. This means that every server is a complete real-time backup of Historical data, alarms, and configuration history. The cost of an additional VTScada license and PC hardware is negligible compared to the cost of downtime and lost data. In addition to making redundancy practical for systems of any size, VTScada also provides discounted software bundles.
See VTScada pricing here.
5. Be Cautious with Unlimited I/O Tag Licensing
Recently, many end users are pressured to pay extra for “unlimited” SCADA I/O tag licensing based on the misconception that this will improve the scalability of their systems. The idea is that as they grow, they will always have enough tags. However, the reality is that most SCADA users will pay for far more than they need. No computer can run an unlimited number of tags and few users grow their systems rapidly and continuously. VTScada allows users to only pay for what they need and easily add tags, licenses, and optional features by simply updating their installation key.
Ask Before You Choose
Here are some important questions to ask your consultant or integrator before deciding on your next SCADA software platform.
- What is the typical life expectancy of the software?
- Does the software vendor periodically retire software versions?
- How many third-party products are required for basic SCADA functionality? (e.g., alarm dialers, thin client servers, communication drivers)
- How much custom code is required for basic features?
- What is the strategy for updates decades down the road?
- How many tags are needed now and over the next few years.
- How difficult is it to add tags and features over time?
- How many levels of redundancy are supported?