AVEVA (formerly Wonderware) System Platform
octoplant supports the management of galaxies of the AVEVA (formerly Wonderware) System Platform and enables the automatic creation of backups and the cyclical monitoring of galaxies.
Device Support Level
Key features
Workflow
System requirements
| AVEVA (formerly Wonderware) System Platform | 2012 R2 | 2014 R2 SP1 | 2017 SP1 Update3 | 2017 SP3 | 2020 R2 | 2023 |
|---|---|---|---|---|---|---|
| octoplant 101 | ✓ | ✓ | ✓ | ✓ | ✓ | |
| octoplant 101.3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Info
The comparison for AVEVA System Platform can use the extended address space on a 64-bit system and thus also process very large projects.
Other requirements
- To integrate projects, the editor must be installed on the same computer on which the server or an agent is running.
Info
Note that AVEVA used to be called Wonderware. For technical reasons, the original name is still used in octoplant. From now on there is also the new Component type, AVEVA. Depending on which version you are using, both component types can be used.
Supported formats for AVEVA (formerly Wonderware) System Platform
Complete backup (CAB)
- Consists of one file containing all objects. Example:
{Galaxy name}.cab. - Backup of the complete Galaxy and full restoration (disaster recovery) are possible.
- An MS SQL Server is required for a comparison. The MS SQL Server must have the same version as the MS SQL Server of the GRNode.
- The programs Bootstrap and Archestra IDE must be installed and licensed for the job.
- The IDE (including GRAccess) is required for the Upload.
Exported objects (AAPKG)
- Only selected objects are included.
- Comparison is possible, but no upload can be configured.
- No additional software is required for comparison.
- The IDE (including GRAccess) is required for automatic export during versioning.
Related topics
To get the basic workflow for intergrating the device, open General workflow.
Device-specific settings for this device, such as job configuration, can be found on the following pages: