Reliable automation systems are essential for monitoring production, managing industrial processes, and preserving operational efficiency in modern manufacturing facilities. As industries expand, managing multiple machines, production lines and control systems becomes increasingly complex. A well-designed automation architecture connects these operations through a centralized platform.
AVEVA System Platform, formerly known as Wonderware System Platform, provides an integrated industrial software environment for developing, managing and visualizing automation applications. Its object-based architecture connects field devices, manages real-time information, builds supervisory applications and collects historical process data.
Understanding its architecture, components and deployment methods is essential for designing scalable industrial automation solutions.
AVEVA System Platform follows a distributed, object-oriented architecture based on Archestra technology. Engineers can create reusable objects representing physical equipment and industrial processes instead of developing separate applications for every machine.
These objects are organized within a centralized environment called a Galaxy, which maintains application configurations, object templates, relationships and deployment information.
The architecture connects three operational layers:
This structure enables communication between equipment, applications and operators.
Within the overall architecture, each component serves a particular purpose.
The Galaxy Repository is the central configuration database of System Platform. It stores application objects, templates, attributes, security settings and deployment configurations. Microsoft SQL Server is used for database administration.
Application Server is the core runtime component responsible for executing industrial application objects. It manages equipment information, process attributes, alarms and communication between objects.
Engineers can create reusable templates for pumps, motors, valves and tanks, reducing development time and maintaining consistency.
The Application Object Server provides the runtime environment for deployed application objects. It hosts AppEngines, areas and equipment-related objects. Multiple AOS nodes can distribute processing loads and support redundancy.
The Integrated Development Environment provides engineering tools for designing, configuring and deploying applications. Engineers use it to create object templates, configure attributes, establish relationships and manage the Galaxy.
Communication drivers connect System Platform with PLCs, RTUs and other industrial controllers through supported communication protocols and interfaces. They enable the exchange of process values, equipment status and control information.
AVEVA Historian collects and stores time-series process information, including temperatures, pressures, production values and equipment conditions. Historical records support trending, reporting, production analysis and troubleshooting.
The Operations Management Interface (OMI) provides contextual graphical applications for monitoring plant operations through reusable industrial graphics.
AVEVA InTouch HMI provides operator interfaces for displaying alarms, monitoring machine conditions and interacting with industrial processes.
The working principle involves continuous communication between field equipment, application objects, data services and visualization clients.
PLCs, RTUs and industrial controllers collect information from connected sensors and machines. Communication drivers transfer process data to System Platform.
Application Server receives and manages information through configured objects and attributes. Engineers define equipment parameters, operating conditions, alarm limits and application logic.
Equipment is represented through reusable objects organized into structured hierarchies. For example, a manufacturing plant may contain production areas with machines, motors, pumps and valves.
OMI or InTouch HMI displays real-time equipment information. Operators can monitor process conditions, identify alarms and perform authorized control actions.
AVEVA Historian records selected process values and events, supporting production monitoring, performance evaluation and troubleshooting.
Deployment defines how System Platform components are installed and distributed across computers within an industrial network. The configuration depends on plant size, I/O requirements, application complexity and availability.
Multiple components can operate on a single computer, depending on hardware capacity and software requirements. This approach is suitable for development, testing and smaller automation applications.
Large manufacturing facilities benefit from distributing components across multiple computers. For example, one server can host the Galaxy Repository, separate AOS nodes can execute application objects, another server can manage historical data, and client computers can run OMI or InTouch applications.
This configuration improves resource management and supports future expansion.
For applications requiring higher availability, primary and backup components can be configured to improve system resilience and reduce the impact of individual component failures.
Cloud and hybrid architectures connect industrial operations with centralized infrastructure for data management, remote monitoring and enterprise information access. However, critical OT communication requires appropriate security controls, network design and latency considerations.
AVEVA System Platform supports automation and monitoring requirements across various industries:
Its flexible architecture allows applications to adapt to different industrial environments.
AVEVA System Platform provides a structured approach to industrial automation through object-based application development, centralized configuration management, real-time data processing and advanced visualization.
Understanding its components, working principles and deployment architecture helps engineers design automation systems that are easier to maintain, expand and manage. Whether implemented in a small production facility or a large manufacturing environment, selecting the right architecture is essential for reliable and efficient operations.