A successful SCADA installation assigns each computer a defined role, validates prerequisites, and proves tag, alarm, trend, and control functions before production use [S2][S3].
This guide covers development workstations, servers, runtime-only clients, web deployment, service registration, configuration, and rollback planning for industrial SCADA software [S2][S3].
Define the SCADA Installation Scope and Role
AVEVA Plant SCADA provides separate installation procedures for a Development Workstation, System Management Server, Runtime Server, Deployment Server, Industrial Graphics Server, OPC UA Server, and Runtime-only Client [S3].
Do not install every component on every machine, because a development environment, supervisory server, and operator station have different availability, security, and performance duties.
This approach is suitable for engineers commissioning a new plant, maintainers updating an existing installation, and system integrators separating development from production [S1][S3]. It is not a substitute for product-specific licensing, operating-system compatibility, and site cybersecurity requirements. The general design guidance also requires personnel to review installation, configuration, operation, and applicable-code instructions before commissioning equipment [S4].
Check Prerequisites Before Installing the Software
Rapid SCADA 5.8 establishes a specific Windows prerequisite chain: install Internet Information Services first, then the Microsoft .NET Framework version required by the system requirements [S2]. This order matters because the web application depends on IIS and the specified .NET runtime rather than operating independently of them.
For Rapid SCADA, the documented installation destination is C:\SCADA. Files from the package Arc folder are extracted there, and the IIS web application uses the physical path C:\SCADA\ScadaWeb with the application alias Scada [S2]. The web application pool must use .NET 4.0 and integrated pipeline mode [S2].
Installation is not complete merely when the binaries finish copying.
Install Web Services and Register Windows Services

Rapid SCADA documents three service registrations after the IIS application is created: ScadaServerService, ScadaCommService, and ScadaAgentService. Each is registered by running its corresponding svc_install.bat file with administrator privileges [S2]. The documented manual-installation sequence includes registering ScadaServerService, ScadaCommService, and ScadaAgentService [S2].
The supported manual sequence is: enable IIS through Windows Features; install the specified .NET Framework after IIS; extract the Arc files to C:\SCADA; create the Scada application in IIS Manager; assign .NET 4.0 with integrated pipeline mode; register all three services; create Administrator and Webstation shortcuts if needed; then launch the applications [S2].
When considering the SCADA software architecture for operator visualization, distinguish development configuration from runtime deployment. AVEVA Plant SCADA provides separate installation procedures for a development workstation, system management server, runtime server, deployment server, industrial graphics server, OPC UA server, and runtime-only client [S3].
Configure Security, Certificates, and Runtime Connections
For operator interfaces, test access through the selected HMI panel only after server and client identity mappings are established. The accepted result is not simply a visible screen: the correct user group must receive the intended alarm acknowledgment, trend access, set-point authority, and administrative permissions. An industrial display does not compensate for a broken server identity or OPC connection.
Prove Tags, Alarms, Trends, and Control Behavior

Commission the server path first, then test client behavior against controlled process inputs rather than assuming that a successful application launch proves field connectivity.
Use a four-part commissioning record. First, verify every mapped tag, engineering units, scan behavior, alarm limits, and communication status against the controller or simulator. Second, trigger alarm and clear alarm events and confirm the authorized operator receives and acknowledges each event. Third, confirm that a changing value produces the expected trend at the agreed sampling interval. Fourth, verify read-only versus writable points and reject unauthorized set-point changes.
For SCADA projects built from an HMI panel, include a visual acceptance test at the deployed panel resolution. Check navigation, date and time formatting, alarm banners, pop-up windows, operator login, logout, and loss of communication behavior. The acceptance criterion is deterministic behavior at each test point, not an attractive screen.
The commissioning plan should also state when the system is not ready: incorrect tag scaling, missing alarms, stale values without clear quality indication, failed user-group mapping, or inability to restore the approved configuration. Resolve these defects before moving from installation to live operation.
Manage Updates, Backups, and Uninstallation
AVEVA Plant SCADA separates online and offline upgrade methods and provides a Migration Tool, but supported upgrade paths must be checked before modifying an installed system [S3]. Back up projects, certificates, security mappings, and server configuration, then test the upgraded copy in a nonproduction environment before changing the live supervisory server.
Rapid SCADA provides a controlled uninstall sequence: remove the Scada web application through IIS Manager; stop ScadaServerService and ScadaCommService; close all open applications; unregister ScadaServerService, ScadaCommService, and ScadaAgentService; then delete the SCADA folder and desktop shortcuts [S2]. This order reverses dependencies and avoids leaving IIS or Windows service registrations pointing at removed files.
SCADAPack software installation documentation covers installation and updates for the SCADAPack x70 configuration environment. Its documented user guide is version 4.6.3, document reference 250520, released on 1 January 2026, and targets systems engineers, commissioning engineers, and maintenance technicians [S1]. Product-specific instructions must govern the x70 environment, including any supported update sequence and device configuration checks.
Close with a Traceable Commissioning Record

A SCADA installation is accepted only when role assignment, prerequisites, IIS configuration, service registration, security setup, field connectivity, and operator workflows all have recorded results. Archive the package version, installation date, Windows and runtime versions, IIS application settings, certificate references, user-group mappings, tag test results, alarm tests, trend tests, and the approved backup location. [S2]
Track two operational signals after commissioning: stale or invalid tag quality and failed operator actions after access changes. Both can expose a configuration or communication defect that a successful launch would miss. For broader architecture decisions, compare the operating roles and deployment limits described in SCADA software advantages, disadvantages, and selection.