SCADA software types are categorized into four groups: enterprise-oriented software, middleware, embedded systems, and service-oriented software, while licensing models differ among platforms.
The practical choice depends on site count, tag volume, protocol support, alarm behavior, deployment model, and whether users need 10 to 20 years of operational continuity [S1][S5].
SCADA Software Types by System Architecture
A SCADA system acquires field data through remote terminal units and transmits supervisory information to a central master station. RTUs can also perform local real-time control autonomously, while the master station presents acquired data and enables remote operator commands [S3].
Monolithic SCADA concentrates acquisition, processing, visualization, and control functions in a tightly coupled central system. Technological developments and increasing demand for effective industrial automation fueled the evolution of SCADA. Networked SCADA uses communications links between distributed assets and master or submaster stations, with radio, telephone, microwave, and satellite listed as possible transmission media [S3].
Proprietary and Open Software Platforms
A SCADA system consists of RTUs that collect field data and perform local control functions, a communications system that links remote sites to the master station, and an operator interface for displaying information and controlling remote sites.
SCADA platforms can be compared across licensing models, technical architectures, security certifications, and industry-specific control capabilities to guide procurement decisions.
For operator-facing architecture, the SCADA software category is broader than the graphical layer. It includes acquisition, alarming, trending, historical data, connectivity, and supervisory control rather than only a visualization front end [S3].
Feature Categories and Interface Boundaries

Four broad software categories are identified as enterprise-oriented software, middleware, embedded systems, and service-oriented software [S4]. Interface boundaries are also classified into database, application, host, and Universal Linkage Interface categories, with each interface performing a different connection function [S4].
Database interfaces connect devices and host computing environments to data systems. Application interfaces link applications to their scripts or programming logic, while host interfaces establish host-specific communications. The Universal Linkage Interface can operate independently of, or depend on, the physical SCADA hardware and supports expansion without modifying the SCADA network [S4].
These categories answer different questions. Architecture type describes where functions run, proprietary versus open describes commercial ownership, and interface type describes where connectivity occurs. Treating them as interchangeable labels produces weak specifications because a proprietary package can still use distributed or networked architecture.
Selection Criteria for Industrial Procurement
Real-time monitoring and control must be evaluated together with alarm notifications by voice, text, and email. Rapid development can affect whether a SCADA project takes months instead of years.
Software-selection guidance identifies real-time monitoring and control, advanced alarming, and rapid development as important SCADA software features. For visualization engineering, an HMI panel is a physical operator interface, not a substitute for the complete SCADA software architecture that processes tags, alarms, trends, and connectivity.
Connectivity needs quantitative checking. AVEVA Plant SCADA is listed with per-tag tiered licensing, no support for a non-Windows operating system, no cloud deployment, and no free trial. Ignition SCADA is listed with per-server unlimited licensing and support for macOS and Linux in addition to Windows, while the licensing information for SIMATIC WinCC Unified is listed as N/A.
Deployment, Licensing, and Lifecycle Constraints

SCADA platforms may run for 10 to 20 years, making licensing, migration, support, and cybersecurity architecture procurement issues rather than install-time details. The compared platforms include per-server unlimited, per-tag, per-user, per-client, and tiered licensing models [S5].
Ignition SCADA is listed at $13,500 and AVEVA System Platform at $12,360 in the comparison, while several products have no public price listed. Such prices are comparison points, not universal quotes, because tag count, clients, drivers, modules, support, and deployment scope can alter commercial terms [S5].
Cloud deployment flags in the comparison identify only a subset of the reviewed platforms as cloud-capable. Ignition 8.3 added built-in Git version control, native REST APIs, and enhanced store-and-forward for unreliable networks in September 2025, while MQTT Sparkplug B support requires separate Cirrus Link modules [S5].
Applicability by Application and Industry
Networked or distributed SCADA fits geographically separated water, waste-water, power, oil, gas, and manufacturing operations because RTUs support field data acquisition and local control across remote sites [S2][S3]. Embedded SCADA is relevant where the supervisory application must operate inside a constrained device or machine, while service-oriented software suits applications exposed as reusable network services [S4].
Industry fit still narrows the field. AVEVA Enterprise SCADA is positioned for oil and gas pipeline and gas-distribution operations rather than general-purpose SCADA, and its architecture uses multi-redundant, push-based data transmission for control-room operators [S5]. AVEVA Plant SCADA is positioned for industrial plants with high tag counts and organizes pump tags, alarms, permissions, communications, schedules, and scripts around equipment-based references [S5].
SCADA is less suitable where only a local machine sequence is required, a small independent dataset needs review, or no supervisory alarms and remote control are justified. In those cases, a controller, historian, or operator interface may satisfy the actual scope without the cost and administration of a full SCADA platform.
Standards, Security, and Acceptance Testing

Protocol support is not the same as certification. A procurement specification should name every required driver, protocol version, operating system, redundancy model, database interface, licensing unit, and client limit before comparing vendor packages [S1][S5].
Security acceptance should cover authentication, authorization, encryption, auditability, patching, backup, and recovery. AVEVA System Platform is listed with node-to-node TLS encryption and single sign-on through AVEVA Connect or third-party providers, but the presence of one feature does not establish the security posture of an entire plant deployment [S5].
Operational acceptance should test alarm delivery through voice, text, and email; concurrent engineering access; SQL access; browser and mobile use; store-and-forward behavior during network loss; redundancy failover; tag counts; and interface performance with the intended industrial display hardware [S1][S5]. Vendor certifications and product reviews can support the shortlist, but the operating scenario must remain the final acceptance basis [S6].
Track 2 procurement signals before approval: the exact license metric for tags, clients, servers, and connections, plus the documented support path for the next 10 to 20 years. If either metric is unresolved, the architecture comparison is incomplete even when the operator interface passes a functional demonstration [S1][S5].