Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

System Platform functional components

  • Last UpdatedAug 12, 2024
  • 4 minute read

This Deployment Guide has been updated to include current AVEVA™ software product versions (current Service Packs are assumed for all software). However, the information is designed to apply to previous versions except where noted and is applicable to the following System Platform component products:

AVEVA™ Application Server

AVEVA Application Server provides an object-based framework repository to construct an asset hierarchy of your physical processes. This repository, called a Galaxy, is built on a SQL Server database that manages the deployment and operation of the run-time elements that form a System Platform application. Application Server functions can be divided by function onto multiple nodes. The Bootstrap module is automatically installed on each Application Server node.

  • GR node (configuration): Galaxy Repository node. Requires a supported version of SQL Server.

  • IDE node (configuration): Engineering development node. Requires installation of the IDE and optionally, InTouch WindowMaker.

  • AOS node (run time): Application Object Server node. Requires Bootstrap module only. Object instances run on AOS nodes when they are deployed.

  • DAS node (run time): Data Acquisition Server or I/O node. Requires installation of AVEVA™ Communication Drivers. Serves as the communication bridge between AOS nodes and the PLCs, RTUs, etc. in your control network.

  • OMI node (run time): Visualization client node. Requires Bootstrap module only. OMI ViewApps run on these nodes after being deployed.

  • InTouch HMI node (run time): Visualization client node. Requires Bootstrap module only. InTouch WindowViewer runs on these nodes after being deployed.

AVEVA™ Development Studio

AVEVA Development Studio is an engineering environment for developing, maintaining, and managing for all supervisory SCADA and HMI application development. It provides a shared development environment that helps you drive standards and best practices across your company. Development Studio includes the System Platform IDE, the Industrial Graphic Editor, and optionally, InTouch HMI WindowMaker.

AVEVA™ Historian

AVEVA Historian is a process database integrated with operations control, enabling access to your process, alarm, and event history data. It stores plant data from Communication Drivers and other data sources, allowing operators to make real-time decisions from a secure and trustworthy set of industrial data. AVEVA Historian also contains summary, configuration, and system monitoring information. AVEVA Historian enhances and is tightly coupled to Microsoft SQL Server.

Visualization and Analysis Clients

Visualization and analysis clients enable you to visualize real-time and historical data from System Platform.

  • AVEVA™ InTouch HMI WindowViewer provides an optional visualization capability for control and optimization of any industrial and manufacturing process through unparalleled situational awareness.

  • AVEVA™ Operations Management Interface (OMI) is an advanced visualization component bundled with Application Server. OMI delivers immersive control applications that weave context throughout the visual design, including situational awareness concepts, for improved operator performance. With AVEVA OMI you can create responsive visualization that organizes content based on user device and utilize AVEVA System Platform's asset model hierarchy to drive intuitive navigation, adapting content and context based on user selection.

  • AVEVA™ Insight is an AI-infused SaaS application for asset reliability and operational performance visualization for hybrid markets. Users can access critical asset and process data with powerful visualization tools that drive prescriptive actions, ranging from self-service analytics with no programming required, to comprehensive analytics for in-depth analysis of critical assets and processes.

AVEVA™ Enterprise Licensing

All System Platform products must have their licenses activated to be fully functional. The License Server can be installed on a standalone node or can be installed on a node with other components. If the License Server is combined with other components on a node, it should be installed on the node with the Galaxy Repository.

See the AVEVA Licensing Deployment Guide for information about deploying licenses and licensing-related recommendations for different topologies.

System Management Server

The System Management Server (SMS) is used to implement secure communications between System Platform nodes. To enable security, every System Platform node must communicate with the System Management Server. There should only be one System Management Server in your System Platform topology, otherwise, communication disruptions may occur. The System Management Server stores shared security certificates and establishes a trust relationship between machines. You can configure one additional node as a redundant SSO server, which functions as a backup for single sign-on if the System Management Server cannot be reached.

The System Management Server node is also the recommended node to use as the time master in multi-node configurations.

If you are implementing redundancy for Application Server, a System Management Server is required. Every redundant Application Server run-time node must be configured to use the System Management Server if data is being historized. Redundant nodes have an instance of HCAP running, which is used to synchronize tags and store-and-forward data between redundant AppEngines. With the release of System Platform 2023 R2, secure communication is required for HCAP, and thus, redundant nodes will not function without the SMS.

AVEVA™ System Monitor

System Monitor can monitor and manage the performance and availability of your System Platform installation, including the core software, engineered software application(s), and the related hardware and network infrastructure. It monitors key system attributes, and then generates alerts when those attributes exceed defined operational limits, and reports system performance issues, errors, and trends. Notifications can be sent to an internal support team and/or the AVEVA Knowledge and Support Center so the issue can be responded to proactively to prevent production interruption or downtime.

  • If an activated license is detected (Licensed mode), System Monitor provides FULL monitoring of an unlimited number of machines.

  • If no activated license is detected (Basic mode), System Monitor provides license server and license acquisition monitoring for all machines using software that requires activation-based licensing and FULL monitoring for one machine (user-selected).

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in