The short answer
AVEVA
AVEVA sells the software many water plants know as Wonderware: InTouch, the HMI that has run plant screens since the early 1990s; System Platform, the server-based platform with an object model in which every pump and valve is an object with attributes, scripts, and history; the Historian, a database built on the Microsoft SQL server; Plant SCADA, from the Citect lineage; and AVEVA Edge, the small HMI product from InduSoft. AVEVA is owned by Schneider Electric, and the product names have changed several times, which is why an installed system may carry any of them. A water plant built on this family is typically either an InTouch system with tags and windows on each workstation, or a System Platform system with a galaxy of objects deployed to engines on servers and InTouch or the newer operations interface as the client. Licensing has moved toward subscriptions, which affects what a utility budgets for.
Key points
- InTouch is the HMI; System Platform is the object-based server platform; the Historian is the database; Plant SCADA and Edge are separate products from acquisitions.
- Names have changed repeatedly; identify the product and version on the installed system before planning anything.
- System Platform builds a galaxy of objects with inheritance, deployed to engines on servers; changes propagate from templates.
- The Historian stores in a Microsoft SQL server database and needs database administration.
- Licensing has moved toward subscription; know the terms before an upgrade.
The products
| Product | Lineage | Role |
|---|---|---|
| InTouch HMI | Wonderware InTouch | Windows-based HMI with tags, windows, animations, and scripts; standalone or as the client for System Platform |
| System Platform | Wonderware Application Server, ArchestrA | Object-based server platform: templates, instances, engines, platforms, and a galaxy repository |
| Operations Management Interface | System Platform client | The newer client for System Platform, with layouts and apps rather than InTouch windows |
| Historian | Wonderware Historian, IndustrialSQL Server | Process history in a Microsoft SQL server database with retrieval extensions |
| Plant SCADA | Citect SCADA | A separate SCADA product with its own tags, clusters, and redundancy model |
| AVEVA Edge | InduSoft Web Studio | Small HMI and embedded product for panels and skids |
| Communication drivers | DAServers, OI servers | Driver products per controller family; OPC to the rest |
InTouch systems
An InTouch application is a set of windows with animations bound to tags in a tag dictionary, with scripts at the window, condition, and application levels, running on a workstation that also runs the communication driver. Many plants have one InTouch node per workstation with a shared application, history in the Historian or in the older local history files, and alarms distributed between nodes. Such systems are simple to understand and get out of hand through scripting and through tag counts that grow past the license.
System Platform
System Platform models the plant as objects: a pump template with its attributes, alarms, history settings, and scripts, instanced for every pump, assigned to an area, hosted by an engine on a platform, with I/O bound through device integration objects. A change to the template propagates to every instance on deployment, which is how a plant with hundreds of pumps stays consistent, and the galaxy repository holds the whole model. The client is InTouch for System Platform or the operations management interface. The system is more to learn and more to administer than InTouch alone, and it rewards a plant that invests in the object library.
The Historian
History lives in a Microsoft SQL server database managed by the Historian, with its own storage format for high-rate data and SQL access for reports. It needs the same care as any database server: disk, backups, retention, and a person who can restore it. Reports and dashboards from the companion products read it, and so can any SQL client with the retrieval extensions.
On a site visit
- 1
Identify the products
Which of the family is installed, at which versions, on which operating systems; the names on the shortcuts may be from three renamings ago.
- 2
Licensing
The license server and its status, the counts, and the expiry where subscriptions are used.
- 3
Backups
The InTouch application directory or the galaxy backup, the Historian database backup, and the driver configurations, in the library and offline.
- 4
Redundancy
Engine and platform redundancy in System Platform, or the alarm and I/O arrangements between InTouch nodes; the state and the last failover.
- 5
Drivers
Driver status and device diagnostics; a device with errors is failing.
Frequently asked questions
- Should a plant on InTouch move to System Platform?
- When the tag count, the number of workstations, or the need for consistency across many identical assets makes per-workstation applications unmanageable. A small plant with two workstations may never need to; a large plant with dozens of pumps and several operator stations usually benefits.
- What happened to the product names?
- Wonderware became Schneider Electric software, then AVEVA after the 2018 combination, and AVEVA itself was fully acquired by Schneider Electric in 2023. Product names were changed along the way. The installed version and its documentation identify what is actually on the server.
- Can the Historian be replaced by a different one?
- Yes, with a data migration project; the raw history exports through SQL. The retrieval extensions and the reports built on them are what has to be rebuilt.
- Does Plant SCADA integrate with System Platform?
- They are separate products with separate models, and they interoperate through the standard interfaces rather than sharing a database. A utility usually runs one or the other.
Related topics
- SCADA ArchitectureThe parts of a SCADA system and how data moves between them: I/O servers, the tag database, clients, the historian, the alarm server, and the topologies from a single panel PC to a redundant, distributed plant.
- Historian ArchitectureHow process history is collected, stored, and served: the collector, the archive, and the client layers, where the historian sits relative to SCADA and the DMZ, single-server and tiered designs for a utility, the store-and-forward buffer that survives outages, and the sizing that decides how many years fit on a disk.
- SQL IntegrationConnecting SCADA and historian data to relational databases: why a utility does it, the methods, a schema that handles time series, the query patterns for totals and reports, the mistakes that flood a database or stall a server, and security.
- Schneider SCADAField notes on Schneider Electric SCADA for water: EcoStruxure Geo SCADA Expert, formerly ClearSCADA, the telemetry platform built around DNP3 events, an object database, and hot standby servers, with SCADAPack RTUs, and how it relates to the AVEVA products.
- SCADA BackupsWhat a SCADA backup must contain to bring a system back: the project export, an image of each server, the databases, historian archives, licenses, certificates, scripts, and network device configurations, with frequency, retention, and the restore procedure.
- Other PlatformsThe SCADA and HMI products a water utility may meet beyond the common ones: Siemens WinCC, distributed control systems, independent SCADA products, hosted lift station monitoring, and open-source tools, and the questions that decide whether one belongs.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.