Learn how to design and manage object templates in AVEVA System Platform to improve consistency, scalability, and maintainability across industrial applications.
Templates are the foundation of AVEVA System Platform’s Application Server. Instead of creating tags and graphics for each device individually, engineers build templates that define common behaviors, attributes, alarms, and graphics. These templates can then be instantiated multiple times as objects (e.g., Pump01, Pump02, Pump03)
A well-designed template library reduces engineering effort, improves consistency, and makes scaling across large systems far easier. Poorly designed templates, on the other hand, can lead to duplication, confusion, and maintenance headaches
This guide shares the best practices every engineer should follow when designing object templates.
1. Understand Templates vs. Instances
- Template = the blueprint. Defines attributes, alarms, scripts, and graphics
- Instance = the object created from the template (e.g., Pump01). Inherits all properties but can have local overrides
Best Practice:
- Minimize local customization on instances; rely on templates for standardization
- Document which attributes are intended to be configurable at the instance level
2. Build Modular, Reusable Templates
- Break complex equipment into logical modules (e.g., Motor, Valve, Pump)
- Reuse building blocks across different equipment types
- Apply inheritance where possible: a “Motor” template can be the parent for “Pump” or “Fan” template.
Example: Instead of building five different pump templates, create one modular template with parameters for type, capacity, and control mode.
3. Define Attributes Clearly
- Use clear, descriptive names (e.g., SpeedSetpoint instead of SP1)
- Include engineering units and descriptions
- Group attributes logically (control, feedback, alarms, metadata)
Best Practice:
- Avoid “misc” attributes; every attribute should have a defined purpose
- Use consistent naming conventions across all templates
4. Configure Alarms at the Template Level
- Define alarms (e.g., high pressure, low level) inside templates so they apply automatically to all instances
- Assign categories, priorities, and severities for operator clarity
- Document expected operator response for each alarm type
Best Practice:
- Avoid leaving alarm definitions to be added ad hoc at the instance level
- Use ISA 18.2 principles when defining alarm behavior
5. Link Graphics and ArchestrA Symbols
- Associate reusable ArchestrA graphics with templates
- Bind symbol properties to template attributes for consistency
- Store graphics in the Galaxy for centralized management
Example: A Pump symbol linked to attributes Pump01.Status and Pump01.Command automatically works for Pump02, Pump03, etc
6. Document and Version Control Your Templates
- Maintain a template library document describing purpose, attributes, and parameters
- Version templates carefully; document changes so instances remain traceable
- For larger teams, establish a review and approval process for template changes
7. Common Mistakes to Avoid
- Over-customizing instances (leads to inconsistency)
- Creating too many “one-off” templates (duplication)
- Using unclear attribute names that confuse operators or integrators
- Not testing template behavior thoroughly before mass deployment
Well-structured templates are the key to consistency, scalability, and maintainability in AVEVA System Platform. By designing reusable, modular templates and enforcing naming and alarm standards, engineers can drastically reduce engineering hours and future maintenance costs.
Master template design with hands-on training:
Our System Platform Training is a comprehensive program that provides practical, instructor-led experience in:
- Building and managing object templates for pumps, motors, and valves.
- Linking templates with ArchestrA graphics and OMI displays.
- Standardizing alarms, attributes, and hierarchies for scalable deployments.
Register today and learn how to create System Platform applications that are structured, efficient, and built to grow with your plant.
