Just installed AVEVA Plant SCADA? Follow this 10-step checklist to ensure your system is secure, functional, and ready for project development.
Installing AVEVA Plant SCADA (formerly CitectSCADA) is only the first step toward a robust industrial control system
Before starting graphic design, tag creation, or Cicode scripting, it’s critical to configure and verify key settings. Skipping these checks often results in security risks, unstable systems, and extra troubleshooting later.
This guide covers the 10 essential tasks every engineer should perform immediately after installation.
1. Verify Software Version & Licensing
- Confirm you are running the latest stable version that matches your project requirements.
- Check that your license covers your I/O count, clients, and any add-on features (e.g., Historian interface).
Example:
If your project will have 50,000 tags but your license is limited to 30,000, you must upgrade before development to avoid costly rework. Always check license details in the License Manager before development starts. Upgrade if needed.
2. Configure I/O Servers
- Define the primary and standby I/O servers.
- Ensure communication protocols (e.g., Modbus, OPC UA) are correctly installed and licensed.
- Test connectivity to PLCs/RTUs with diagnostic tools.
Example:
Modbus TCP device connected but no live values appeared because the IP address in the I/O server config was mistyped. Use the built-in Diagnostic Tools in Plant SCADA to verify communications.
3. Set Project Paths
- Store project files in a structured, version-controlled folder.
- Define backup locations — ideally on separate physical drives or network storage.
Example:
When a developer’s laptop failed, no central backup existed, causing a 2-week rebuild. Store projects in version-controlled shared folders and set automatic backups.
4. Check Network Settings
- Assign static IP addresses to SCADA servers.
- Verify that required Plant SCADA ports are open and not blocked by firewalls.
Example:
Using DHCP for SCADA servers can cause IP changes, breaking client-server communication. Assign static IPs and document all addresses.
5. Apply Security Policies
- Create user roles (e.g., Operator, Engineer, Administrator).
- Assign minimal privileges based on role.
- Remove or change all default credentials.
Example:
A contractor logged in remotely using a factory default password, bypassing security protocols. Use role-based access and enforce strong password policies.
6. Backup the Fresh Installation
- Take a snapshot of the clean, functional system.
- Store it securely for future disaster recovery.
Example:
Corruption occurred during configuration, but no clean image was available to restore. Take a snapshot backup before making any changes.
7. Test Cicode Runtime
- Create a simple test script to confirm event processing works.
- Use the Cicode Editor’s syntax check to ensure no compilation issues.
Example:
A batch start script failed in production because basic syntax errors were never tested. Run a simple Message() test script before large-scale coding.
8. Configure Alarm Categories
- Define at least one alarm category for testing.
- Verify that alarm sounds, popups, and logging work correctly.
Example:
During a pump failure, critical alarms were buried in a flood of low-priority alerts. Set clear categories from the start (e.g., Safety, Equipment, Process).
9. Check Historian or Data Logging
- Configure trend logging for a few key tags.
- Verify that historical data is being stored and retrieved correctly.
Example:
Logged values were blank because the tag mapping was incorrect. Log a few key tags and confirm they appear in historical trends.
10. Document Everything
- Maintain a setup document containing IP addresses, usernames, passwords, and file locations.
- Update this document after every major change.
Example:
When an engineer left the company, no one knew the admin credentials for the Historian server. Maintain and regularly update a secure configuration document.
A well-prepared system saves countless hours later in the project. Completing this checklist ensures your Plant SCADA installation is secure, stable, and ready for development.
Take the next step:
Our Plant SCADA Training covers installation, configuration, project setup, and alarm/logging basics.
For deeper skills, our Plant SCADA Advanced Training explores redundancy, advanced alarming, performance tuning, and Historian integration.
Register today to start your SCADA projects with confidence.
