New to AVEVA System Platform? Learn the key concepts every engineer should understand, including the Galaxy Repository, templates, object-oriented design, and best practices for scalable industrial applications
AVEVA System Platform (formerly Wonderware System Platform) is more than just a SCADA system. It is a unified, object-oriented industrial software platform designed to scale from a single facility to enterprise-wide deployment
For engineers new to System Platform, understanding its core concepts is critical. These concepts define how applications are modeled, deployed, and maintained — and they form the foundation for advanced features such as integration with Historian, MES, and enterprise systems.
This article introduces the key elements every engineer should know before building or managing a System Platform project
1. The Galaxy Repository (GR)
At the heart of System Platform is the Galaxy Repository — a centralized database that stores your entire application.
- Think of it as the “single source of truth” for objects, templates, graphics, alarms, and configuration.
- Changes made in the GR automatically flow to deployed instances across the system
- Supports versioning and backups, ensuring system integrity
Best Practice:
- Always configure regular GR backups
- For larger systems, use a dedicated SQL Server for performance and resilience
2. Object-Oriented Engineering
Unlike traditional SCADA that relies on flat tag databases, System Platform uses an object-oriented model
- Equipment and processes are represented as objects (e.g., Pump, Motor, Tank
- Objects are based on templates, which define common behaviors, attributes, and graphics
- Changes to templates cascade to all instances automatically — ensuring consistency and reducing engineering time
Example: Create a Pump template once, then instantiate Pump01, Pump02, Pump03. Any future changes to the template update all pumps instantly
3. Areas and Equipment Hierarchy
System Platform applications are structured into Areas and Equipment Hierarchies:
- Areas: Logical groupings (e.g., Plant A, Plant B, or Packaging Line)
- Equipment Hierarchy: Nested structure of Units, Equipment, and Subsystems
This hierarchy simplifies navigation, security, and reporting by aligning the digital model with the plant’s physical layout
Best Practice:
- Mirror your plant breakdown structure when designing hierarchies
- Use consistent naming conventions across all objects
4. ArchestrA Graphics & Situational Awareness
System Platform leverages ArchestrA Graphics for HMI development
- Graphics are reusable symbols linked to object attributes
- Situational Awareness graphics reduce clutter and use color sparingly, focusing operator attention on abnormal states
- Graphics are stored in the Galaxy and can be deployed across multiple clients
Best Practice:
- Build a standardized symbol library early in the project
- Use grayscale for normal states, and reserve bright colors for alarms
5. Alarms and Events
Alarms are defined at the object level, making them reusable across instances
- Supports alarm shelving, filtering, and prioritization
- Integrates with Alarm Adviser for KPI reporting and analysis
- All alarms are centrally managed, ensuring consistency
Best Practice:
- Follow ISA 18.2 alarm management principles
- Document alarm philosophy before configuration to avoid alarm floods
6. Deployment Architecture
System Platform applications are deployed via Application Object Servers (AppServers).
- Each AppServer hosts one or more objects
- Objects can be distributed across multiple servers for scalability
- Supports redundancy for high availability and fault tolerance
Best Practice:
- For small sites, a single AppServer may be sufficient
- For large/critical sites, design for redundant AppServers and dedicated GR servers
7. Integration with Historian and Beyond
System Platform integrates natively with AVEVA Historian for high-performance data logging.
- Historian tags can be mapped directly to object attributes
- Supports integration with MES, ERP, and cloud analytics platforms
- Forms the foundation of digital transformation initiatives
Best Practice:
- Start small (logging key KPIs) and expand logging strategy gradually
- Use consistent engineering units and tag naming for reliable reporting
Understanding and applying these concepts will help you unlock the full potential of AVEVA System Platform. Whether you are learning the basics or looking to scale across enterprise systems, success comes from mastering its three core components — Application Server, Historian, and OMI.
Take your System Platform skills further with hands-on training:
Our System Platform Training is a complete program that provides practical, instructor-led experience in:
- Application Server – object modeling, deployment, redundancy, and alarm configuration.
- Historian – high-performance data logging, retention strategies, and analytics.
- OMI – modern visualization with ArchestrA graphics, situational awareness, and context-driven navigation.
Register today and gain the confidence to design, configure, and deploy System Platform applications that are efficient, scalable, and future-ready
