AVEVA™ System Platform 2023

Getting Started Guide

© 2022 AVEVA Group plc and its subsidiaries. All rights
reserved.
No part of this documentation shall be reproduced, stored in
a retrieval system, or transmitted by any means, electronic,
mechanical, photocopying, recording, or otherwise, without
the prior written permission of AVEVA. No liability is assumed
with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of
this documentation, AVEVA assumes no responsibility for
errors or omissions. The information in this documentation is
subject to change without notice and does not represent a
commitment on the part of AVEVA. The software described in
this documentation is furnished under a license agreement.
This software may be used or copied only in accordance with
the terms of such license agreement.
ArchestrA, Avantis, Citect, DYNSIM, eDNA, EYESIM, InBatch,
InduSoft, InStep, IntelaTrac, InTouch, OASyS, PIPEPHASE,
PRiSM, PRO/II, PROVISION, ROMeo, SIM4ME, SimCentral,
SimSci, Skelta, SmartGlance, Spiral Software, WindowMaker,
WindowViewer, and Wonderware are trademarks of AVEVA
and/or its subsidiaries. An extensive listing of AVEVA
trademarks can be found at: https://sw.aveva.com/legal. All
other brands may be trademarks of their respective owners.
Contact Information
AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 0HB. UK
https://sw.aveva.com/
For information on how to contact sales and customer
training, see https://sw.aveva.com/contact
For information on how to contact technical support, see
https://sw.aveva.com/support
For access to the AVEVA Knowledge and Support center, visit
https://softwaresupport.aveva.com
 Contents  i

Contents

Welcome to AVEVA System Platform......................................................1

AVEVA System Platform Enterprise ...................................................... 1
AVEVA System Platform Functional Components .............................. 2
AVEVA Application Server........................................................................ 2
AVEVA Development Studio ................................................................... 2
Visualization and Analysis Clients......................................................... 3
AVEVA Historian........................................................................................... 3
Device Integration Tools........................................................................... 3
AVEVA System Monitor............................................................................. 4
Other Tools .................................................................................................... 4
Before You Get Started.................................................................................. 5

Development Environment....................................................................... 7
Start the System Platform IDE.................................................................... 7
Create a Galaxy................................................................................................. 9
Connect to a Galaxy and Start System Platform IDE .......................10
Run the Default System Platform ViewApp........................................10
Become Familiar with Basic ViewApp Features.................................12

Workflow Group 1: Design Standards .................................................. 13

Build Symbol Standards..............................................................................14
Create a Symbol.........................................................................................14
Edit a Symbol ..............................................................................................15
Build a Symbol from Graphic Elements ............................................16
Build Object Standards ...............................................................................17
Create a Derived Template or an Instance ......................................18
Edit Objects .................................................................................................19
Work with Object Wizards ........................................................................20
Create a Basic Object Wizard ...............................................................21
Build Screen Profile Standards.................................................................22
Create a Screen Profile............................................................................23
Configure a Screen Profile.....................................................................23
Build Layout Standards ...............................................................................25
Create a Layout ..........................................................................................25
Configure a Layout...................................................................................26
Add Content to Layout Panes ..............................................................27
ii Contents

Workflow Group 2: Assemble a ViewApp...........................................29

Create a ViewApp .........................................................................................30
Assign Screen Profiles and Layouts to a ViewApp...........................31
Place Content in a ViewApp .....................................................................32
Search for Content....................................................................................32
Embed a Symbol in a ViewApp ...........................................................33
Place an Object in a ViewApp..............................................................34
Add External Content to a ViewApp .....................................................34
Create an External Content Item .........................................................35
Configure an External Content Item..................................................36
Associate External Content to a ViewApp .......................................37

Workflow Group 3: Deploy a ViewApp................................................39

Prepare to Deploy a ViewApp .................................................................40
Deploy a ViewApp........................................................................................41

Workflow Group 4: Run a ViewApp .....................................................43

Launch and Run a ViewApp .....................................................................43
Run a ViewApp in Preview Mode ...........................................................45

Get More Information ..............................................................................47

Easy Access to System Platform Documentation .............................48
Application Server ........................................................................................49
AVEVA OMI......................................................................................................50
AVEVA InTouch HMI.....................................................................................51
InTouch Access Anywhere .........................................................................53
AVEVA Historian ............................................................................................54
AVEVA Historian Client ...............................................................................55
Technical Support .........................................................................................55
Product Training ............................................................................................56
 1

Welcome to AVEVA System

Platform
AVEVATM System Platform is an industrial software platform
that uses System Platform technology for human machine
interface (HMI), operations management, SCADA, and
production and performance management.
System Platform contains an integrated set of services and an
extensible data model to manage plant control and
information management systems. System Platform supports
both the supervisory control layer and the manufacturing
execution system (MES) layer, presenting them as a single
information source.
Modular applications sit on top of System Platform. Other
third-party integrators are delivering a growing inventory of
application components that use System Platform services.

AVEVA System Platform Enterprise

AVEVA System Platform Enterprise builds upon the core
technology of AVEVA System Platform to bring large quantity
user accessibility and exclusive visualization extensions specific
for enterprise users in assembling an AVEVA Unified
Operations Center solution. This includes the AVEVA
Operations Management Interface (OMI) Web Client, allowing
applications to be viewed in a standard web browser. AVEVA
System Platform Enterprise is an AVEVA Flex subscription-
activated product.
2 Welcome to AVEVA System Platform

AVEVA System Platform Functional Components

The following figure shows a functional representation of
System Platform, which incorporates an architectural
framework.

The framework consists of server-side configuration and

deployment related components. In System Platform, these
components include a centralized object repository called
Galaxy Repository, an integrated development environment,
and a database to store historical data.

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.

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.
 AVEVA System Platform Functional Components 3

Visualization and Analysis Clients

Visualization and analysis clients enable you to visualize
real-time and historical data from System Platform.
• AVEVA InTouch HMI provides an optional visualization
capability for control and optimization of any industrial
and manufacturing process through unparalleled
situational awareness.
• AVEVA Operations Management Interface (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 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.
4 Welcome to AVEVA System Platform

Device Integration Tools

System Platform can connect to a diverse set of data sources
to integrate all plant and industrial data. The System Platform
IDE offers I/O auto-assignment and I/O mapping features to
streamline device integration and data access.
Data sources include OPC and OPC UA Servers, databases, and
any application that exposes data from an API such as XML,
SQL, HTTP, or.NET. In addition, a library of device integration
tools provide data from the factory floor.
• Communication protocols provide data from PLCs and
other factory devices to HMI applications. These protocols
can be used with any Microsoft Windows program or
supervisory application capable of acting as a DDE,
FastDDE, OPC, OPC UA, or SuiteLink™ client.
• The System Platform IDE includes the OPCClient device
integration object. In most cases, you will use the
OPCClient object to provide the interface from a PLC to
System Platform.
• A Communication Driver encapsulates the functionality of
an IO Server in the System Platform environment.
Communication Drivers are models of the network and
devices associated with a specific HMI application. The
hierarchy of the actual devices is the same as the hierarchy
of Communication Drivers.

AVEVA System Monitor

AVEVA System Monitor keeps a watchful eye on the critical
performance indicators associated with your AVEVA software
applications and the underlying hardware to proactively
maintain healthy systems for easy maintenance and reliability.

Other Tools
System Platform readily integrates with other applications
including:
• AVEVA Teamwork is a Software-as-a-Service (SaaS) app
that allows users to perform tasks, achieve learning goals,
identify and manage issues, and capture and document
 Before You Get Started 5

standards. AVEVA Teamwork enables industrial

organizations to implement skills development, knowledge
sharing, and collaboration management across their
enterprise from the cloud.
• AVEVA Reports is no-code software with simple
drag-and-drop, point-and-click configuration, and
integration of real-time sources and manual data to HMI/
SCADA, historians, enterprise software and relational
databases.

Before You Get Started

This booklet describes a set of essential workflows to get you
started building applications with System Platform. It explains
the essential steps to create an AVEVA OMI ViewApp.
For information about creating AVEVA InTouch HMI
applications, see the AVEVA InTouch HMI Getting Started Guide.
Before you get started building an AVEVA OMI ViewApp, you
must install, configure, and activate the licenses of your
System Platform products. The last section of this booklet
includes a set of tables that list the documentation for each
System Platform product.

Installation
Installing System Platform products is a straightforward
procedure of selecting options from a series of installation
dialogs. You can find more information about hardware and
software installation requirements in the AVEVA System
Platform Installation Guide.

Configuration
Immediately after installation, the Configurator appears to
configure various aspects of System Platform, including
product licensing, security, and the Historian database. The
AVEVA System Platform Installation Guide includes a chapter
that describes how to configure System Platform products.
6 Welcome to AVEVA System Platform

Licensing
All System Platform products must have their licenses
activated to be fully functional. Before you can complete the
procedures described in this booklet, you must activate your
product licenses with AVEVA License Manager. For more
information about the steps to activate licenses, see the AVEVA
Enterprise Licensing Guide and online help.
 7

Development Environment
System Platform IDE and AVEVA InTouch HMI WindowMaker
are typically installed on the same computer, referred to as the
System Platform Development Server. You use the System
Platform IDE to build AVEVA OMI ViewApps and AVEVA
InTouch HMI managed applications.

Start the System Platform IDE

You start the System Platform IDE by selecting the System
Platform IDE icon from your computer’s Start menu or the
Windows Apps window.
To start the System Platform IDE
1. Click the Apps icon on the Windows Start window to
show the Apps window.
2. Locate the AVEVA System Platform app group.
3. Select the System Platform IDE icon.
8 Development Environment

The IDE Home dialog box appears.

To create a new Galaxy, select the “New” button on the right.

You can also select one of the Galaxy templates that are shown.

Some Details
• You must connect to a Galaxy before the System Platform
IDE opens. That means you must create a Galaxy before
opening the IDE for the first time.
• Your product licenses must be activated before starting the
System Platform IDE.
• Users must be a member of the aaConfigTools Windows
user group to connect to a Galaxy from the IDE. Assign
users to this group through the Local Users and Groups
utility of the Windows Control Panel.
• For more information, see the “Steps to Create a Galaxy”
topic in the Application Server Help.
 Create a Galaxy 9

Create a Galaxy
You must connect to a new or existing Galaxy each time you
start the System Platform IDE.
To create a Galaxy
1. Start the System Platform IDE.
2. Select the New button and then select a galaxy template.
The New Galaxy dialog opens.

3. Enter a Galaxy name in the Galaxy name field.Complete

the fields of the New Galaxy dialog box.
4. Click Create to begin creating a new Galaxy.
5. Click Close after the new Galaxy is created.
Some Details
• The Galaxy Repository is the name of the single computer
where the Galaxy database is located.
• The Galaxy Repository stores information for AVEVA OMI
ViewApps or InTouch HMI managed applications.
• You can only create a new Galaxy on a computer with the
Bootstrap and Galaxy Repository software installed.
• The IDE automatically connects to the newly created Galaxy
when the “Connect to this Galaxy” is enabled.
• Select Default.cab as the Galaxy type to build AVEVA OMI
ViewApps.
10 Development Environment

Connect to a Galaxy and Start System Platform IDE

You must connect to a Galaxy before you can perform any
work on a ViewApp using the System Platform IDE.
To connect to an existing Galaxy
1. Start the System Platform IDE.
2. Select the Recent, Pinned, or On server tab and then
select the Galaxy that you want to open.
3. Select the Open icon.
The IDE opens and shows the different views of your
Galaxy.

The IDE provides different ways to view the structure of the

Galaxy and how it will be deployed to run time.

Some Details
• For more information, see the Connect to a Galaxy topic in
the AVEVA OMI help.

Run the Default System Platform ViewApp

System Platform provides a set of default symbols, apps, and
other content, and templates that are accessible from the
System Platform IDE. Folders containing default content and
templates are located in the Template Toolbox and Graphic
Toolbox.
 Run the Default System Platform ViewApp 11

A default ViewApp is also included. After deploying the

ViewApp, you can run immediately without any editing.
To run the default ViewApp
1. Select the Deployment tab at the bottom left of the IDE.
The Deployment view shows the arrangement of
supporting system objects that are required to run a
ViewApp. Beneath the ViewEngine object is the default
ViewApp named OMI_ViewApp_Desktop.
The yellow square next to each object indicates the object
is in an undeployed state.
2. Select Deploy from the ribbon bar, or right-click and
select it from the shortcut menu.
3. Click OK from the Deploy dialog box.
The Deploy dialog box shows the progress of deploying all
of the objects. The yellow square disappears after each
object is deployed.
4. Show the Windows desktop and locate the AVEVA Appli-
cation Manager icon.
5. Select AVEVA Application Manager to open it and click
the LAUNCH button.
The ViewApp should start running in several seconds.
Some Details
• Right-click on deployed objects and select Properties. The
General tab lists the template the object was derived from.
• Workflow Groups 3 and 4 in this booklet provide more
information about deploying and running a ViewApp.
12 Development Environment

Become Familiar with Basic ViewApp Features

The default ViewApp provided with System Platform
demonstrates some of the basic features of a ViewApp.

A slide-in pane can be placed at each side of a ViewApp

window. During run time, slide-in panes are hidden until the
user selects the tab to extend the slide-in pane and show its
contents.
Navigation icons can be placed within a pane that include short
navigation scripts to enable users to return to the home view or
scroll forward or backward through a sequence of views.

System Platform includes a default set of apps

that you can drag and drop onto a pane requir-
ing minimal configuration. This example shows
the default Map app, which provides controls and touch support to
enable users to pan to different areas of the map and zoom in or
out to show more or less map detail
System Platform includes a NavTree app that shows a
ViewApp's navigation items arranged in a hierarchical
tree. Selecting an item from the tree shows the content
of the selected view.
 Workflow Group 1: Design
Standards
You can create symbols and objects that are incorporated into
your ViewApps. Rather than create unique symbols and objects
for each ViewApp, you can use IDE tools to create a set of
reuseable template symbols and objects that can be
individually configured to meet the differing requirements of
your ViewApps.
The following figure summarizes the major workflows to create
reusable standards you need to build ViewApps. As shown in
the figure, the System Platform IDE includes a set of editors to
build reusable symbols, objects, scripts, layouts, and screen
profiles.

Design Standards

Workflow
Groups

Product
Tools Symbol Object Script Layout Screen
Editor Editor Editor Editor Profile Editor

ViewApp Objects Scripts Screen

Components Profiles

Layouts

Symbols
14 Workflow Group 1: Design Standards

Build Symbol Standards

System Platform provides a set of graphic tools and symbols
to visualize data in a ViewApp. You can use these tools within
the Graphic Editor to create symbols from basic graphic
elements, like rectangles, lines, and text.
You can also embed pre-built Industrial graphic and
Situational Awareness Library symbols in a template to
visualize object-specific information. Embedding a symbol
enables you to update one symbol template and cascade the
changes throughout all of the instances of the symbol in your
application.
Standard Industrial Graphics available from the Graphic
Toolbox show reasonably realistic views of process objects. You
can embed an Industrial Graphic in a template or instance of
an object to visualize object-specific information.

Situational Awareness Library symbols are protected symbols

that include multiple visual and functional configurations,
which are enabled by selecting values from a set of Wizard
Options associated with each symbol. Incorporating multiple
configurations in a single symbol reduces the types of symbols
you need to develop for an application.

Create a Symbol
You can create a symbol in the Graphic Toolbox by the
following methods:
• Keyboard shortcut: Press Ctrl + Shift + S
• Shortcut menu: From the Graphic Toolbox, right-click on
the Galaxy name, select New, and then select Symbol
 Build Symbol Standards 15

• Ribbon Bar: From the Home tab, select Symbol from the
Create group.
You should see the symbol listed in the Graphic Toolbox as
Symbol_001 with a blue background. The symbol is selected
and you can assign a new name by typing over the default
name.
Depending on your development requirements, you can select
where and how to store Industrial Graphics.
• Store symbols in the Graphic Toolbox if you want to
define them as a reusable standard that will be used
frequently.
• Store symbols as AutomationObject templates if you want
to re-use the symbol in combination with the object
functionality.
• Store symbols in the Content tab of an AutomationObject
instance. Do this if you are unlikely to re-use the symbol in
any other situation.
Some Details
• Symbol Names must be unique within the entire Graphic
Toolbox hierarchy.
• Valid characters for symbol names include alphanumeric
characters, #, and _ (underscore).
• Symbol names cannot contain spaces and the symbol
name cannot begin with the $character.

Edit a Symbol
After you create a symbol, you need to check it out to be able
to edit it in the Industrial Graphic Editor. You also need to
check in the symbol after you are finished editing it.
To edit a symbol in the Graphic Toolbox
1. Right-click on your symbol listed in the Graphic Toolbox
and select Check Out.
A red check mark appears to the left of your symbol's
name to indicate that it is checked out.
16 Workflow Group 1: Design Standards

2. Right-click on the checked-out symbol and select Open to

show the symbol in the Graphic Editor.
3. After you have finished editing the symbol, click Save and
Close from the task bar of the Graphic Editor.
4. Right-click on the symbol name shown in the Graphic
Toolbox and select Check In.
To edit a symbol contained in an object.
1. Open an object in the Object editor.
2. Click the Graphics tab.
3. Select the graphic to edit and click Open. The Industrial
Graphic Editor appears.
4. Edit the graphic.
5. Click Save and Close. The Industrial Graphic Editor
closes and the updated graphic is checked in.
Some Details
• Situational Awareness Library symbols are protected
templates and cannot be directly edited. You must embed
an instance of a Situational Awareness Library symbol in
another symbol to edit it and make configuration changes.
• You check out a graphic when you open it for editing with
the Industrial Graphic Editor. No other user can edit the
graphic while you have it checked out.

Build a Symbol from Graphic Elements

You can assemble and edit a set of graphic elements in the
Industrial Graphic Editor to represent a visual component.
To build a symbol from graphic elements
1. Check out and open a symbol.
The Industrial Graphic Editor opens and shows the Tools
menu in the upper left corner.
 Build Object Standards 17

2. Select a graphic element from Tools to include in the

symbol.
3. Move the cursor over the canvas area.
The cursor shape should change to a plus sign.
4. Holding your left mouse key down, drag the mouse to set
the initial size of the graphic element.
5. Select the graphic element and then select an option from
the Configuration bar to configure the visual appearance
of the graphic element.
6. Select all graphic elements, right-click, and then select
Grouping >Group option from the shortcut menu.
7. Save and Close the Industrial Graphic Editor.
8. Check the symbol back into the Graphic Toolbox.
Some Details
• For more information about creating and integrating
graphic elements into a ViewApp, see “Working with
Graphic Elements” in the Industrial Graphic Editor Help.

Build Object Standards

The Template Toolbox is the part of the System Platform IDE
that shows host objects organized by toolsets from which
other object templates are derived or instances are created.
18 Workflow Group 1: Design Standards

Derived templates are created from base templates. Base and

derived templates are identified in the Template Toolbox by a
dollar sign ($) as the prefix to their names.
Templates are elements that contain common configuration
parameters for object instances that can be re-used.
Object instances are the specific devices in your environment
that are deployed as part of your ViewApp. You create an
instance from a template and then customize the specific
instance as needed.
Some Details
• Instances are deployed to the run-time environment.
Templates exist in the development environment and
cannot be deployed to a ViewApp.

Create a Derived Template or an Instance

You first select the base template that you want to create a
derived template or instance from the Template Toolbox. You
can create a derived template or an instance by the following
methods:
• Keyboard shortcut
Derived template: Press Ctrl + Shift + N
Derived instance: Press Ctrl + N
• Shortcut menu
Right-click on the base template, select New, and then
select either Instance or Derived Template.
• Ribbon bar
From the Home tab, select Instance or Template from the
Create group.
The new derived template is listed in the Template Toolbox as
$ObjectName_001. A new instance appears in the Model,
Deployment, and Derivation views as ObjectName_001. You
can assign a new name to the derived template or instance by
typing over the default name.
Some Details
 Build Object Standards 19

• All templates you create are derived templates. A derived

template inherits attributes and behaviors from the base
template. You cannot change the attributes in a base
template.
• Derived template and instance names can be up to 32
alphanumeric characters. Derived template and instance
names must include at least one letter and cannot include
spaces. An instance name cannot have $ as the first
character.

Edit Objects
The Object Editor contains tabbed pages to modify objects.

Each Object Editor page modifies a specific aspect of objects. The

Attributes, Scripts, and Object pages are common to all objects.
Other pages are unique to certain object types
To edit an object
1. From the Template Toolbox, double-click on an object to
open it in the Object Editor.
2. Make your modifications to the object.
3. Select Save or Close from the Galaxy menu.
20 Workflow Group 1: Design Standards

Some Details
• When you open the Object Editor, the object is checked
out. No one else can edit an object.
• When you save an object, the configuration data for the
object is validated. If errors or warnings are identified
during validation, a message appears.

Work with Object Wizards

An Object Wizard can be added to any derived template to
provide a simplified user interface to build a set of object
configurations. Users select from these choices and options.
Each object configuration has a unique combination of
attributes, scripts, and graphics.

You can replace the requirement for many derived templates

by using a single template with an Object Wizard that
supports multiple configurations.
Some Details
• Attributes and features contained in the Object Wizard
that are not needed in a particular instance are removed
from the run-time object.
 Work with Object Wizards 21

• To maximize the benefits of using Object Wizards, add

your Object Wizard to the template as close to the top
level of the derivation hierarchy as possible.

Create a Basic Object Wizard

An Object Wizard includes Choice Groups, each with two or
more Choices, and/or Options. A Choice Group is a radio
button list that lets the user select one choice. An Option
contains a check box that can be selected or deselected.
To create an Object Wizard
1. Open a derived template in the Object Editor.
2. Configure the template by adding attributes, symbols,
and scripts.
3. Select the Configure Wizard Options button to open the
Object Wizard editor.

4. Add Choice Groups, Choices within each group, and

Options with the applicable Add button. Options are
enabled or disabled via a checkbox. Choices are selected
via radio buttons.
5. Use the Up and Down arrow buttons to change the order
of Choices, Choice Groups, or Options.
6. Associate attributes or content with a Choice or Option
a Select the Choice or Option.
b Select the attribute or content to associate with the
Choice or Option.
c Select the Add Association button.
22 Workflow Group 1: Design Standards

Settings for the selected attribute or content appear in

the Settings pane after making an association.
d Configure visibility and value overrides, as needed.

Build Screen Profile Standards

A screen profile defines the physical characteristics of one or
more screens and how these screens are arranged with respect
to each other. Each screen icon that appears in a screen profile
represents a physical screen that shows running a ViewApp.
A screen profile can represent all of the monitors in a
production control room or the single screen of a cell phone.

You assign a screen profile to a ViewApp with the

Initialization wizard the first time you open the ViewApp.
Some Details
• The System Platform IDE includes a set of default screen
profiles located in the Graphic Toolbox. See the Default
Content 1. Screen Profiles folder.
• A screen profile includes a set of lock properties to ensure
safety using touch screens while running a ViewApp.
 Build Screen Profile Standards 23

Create a Screen Profile

You can create a screen profile in the Graphic Toolbox by the
following methods:
• Keyboard shortcut: Press Ctrl + Shift + E
• Shortcut menu: Right-click on the Galaxy name, select
New, and then select Screen Profile.
• Ribbon bar: From the Home tab, select Screen Profile
from the Create group.
To create a screen profile
1. Open the System Platform IDE and select Graphic Tool-
box.
2. With your cursor, select a folder in the Graphic Toolbox
where you want to place the new screen profile.
3. Press Ctrl + Shift + E.
A screen profile appears in the Graphic Toolbox folder
with a default name of ScreenProfile_001 for the first
layout you create. A blue background around the screen
profile name indicates the name can be changed.

4. Select the screen profile and rename it.

Some Details
• A screen profile can replicate a computer's display
properties stored in Windows, including screen resolution,
screen orientation, and the configuration of screens to
each other.
• You can resize the screen profile shown with the size
controls at the bottom of the canvas area.F

Configure a Screen Profile

The typical workflow to configure a screen profile includes
these essential steps:
24 Workflow Group 1: Design Standards

• Add one or more screens to represent the computer

display that is running a ViewApp
• Position screen icons to represent the actual physical
arrangement of screens attached to a computer running a
ViewApp
• Assign values to each screens’ properties
To configure a screen profile
1. Click the red plus circle to add a screen to a profile.
2. Using a drag and drop mouse gesture, select a screen and
move it to the corner of an adjoining screen, and then
release the mouse key.

3. Select the check mark in the upper left corner of a screen

to designate it as the primary screen of the profile.
4. Define the physical characteristics of each screen by
assigning values to screen properties that are listed at the
right of the Screen Profile editor
Some Details
• Select the Has Taskbar property to show the Taskbar
Position property.
• Select the Is Touchscreen property to show the Touch
Local Level property.
• A valid screen configuration aligns the corner of one
screen to the corner of another screen.
 Build Layout Standards 25

Build Layout Standards

Layouts define the organization of rectangular areas of a
screen called panes that contain content shown in a ViewApp.

You configure layouts with the Layout editor. The Layout editor
includes controls to add panes and adjust their size and
arrangement to other panes within the layout's window. The
Layout editor provides properties to configure the layout itself
and each individual pane. You can also drag and drop content
onto panes as part of configuring a layout.
Some Details
• The Layout editor includes a script editor to write built-in
OnShow, While Showing, and On Hide scripts.
• Responsive layout mode enables you to create a layout for
ViewApps that will run on a variety of different device
screen sizes.

Create a Layout
Create a layout in the Graphic Toolbox by these methods:
• Keyboard shortcut: Press Ctrl + Shift + L
• Shortcut menu: Right-click on the Galaxy name, select
New, and then select Layout
26 Workflow Group 1: Design Standards

• Ribbon bar: From the Home tab, select Layout from the
from the Create group.
To create a layout
1. Open the System Platform IDE and select Graphic Tool-
box.
2. With your cursor, select a folder in the Graphic Toolbox
where you want to place the new layout.
3. Press Ctrl + Shift + L.
A layout appears in the Graphic Toolbox folder with a
default name of Layout_001 for the first layout you create.
A blue background around the layout name indicates the
name can be changed.

4. Select the layout and rename it.

Some Details
• The initial configuration of a new layout consists of a single
pane with no active slide in panes.
• Select the name shown in the upper corner of a pane to
rename the pane.

Configure a Layout
A layout configuration workflow includes these essential steps:
• Add panes
• Set layout and pane properties
 Build Layout Standards 27

To configure a layout
1. Select a layout to configure from the Graphic Toolbox.

2. Select an arrowhead on the Add Pane Control to add a

pane by splitting the currently selected pane in half.
3. Select Properties from the right column of the editor.
• Tap outside the border of the layout to show general
layout properties.
• Tap inside of a pane to show the specific properties of
the selected pane.
• Select the divider line between panes to show divider
properties.
4. Modify property values and save your changes.
Some Details
• Select Script from the menu bar to show the Predefined
Script editor.

Add Content to Layout Panes

You can use a drag and drop mouse action or touch gesture to
add content to panes.
To add content to a layout
1. Select a layout from the Graphic Toolbox to edit.
28 Workflow Group 1: Design Standards

2. If you want to add a graphic to a layout, select the Tool-

box tab and then select the folder containing the graphic
you want to add.
3. Locate the graphic thumbnail at the bottom of the Tool-
box area and drag and drop the thumbnail on the pane.

4. If you want to add an object to a layout, select the Assets

tab and then select the folder containing the object (app
or widget) you want to add.
5. Use the same drag and drop method to place the object
on the layout pane.
Some Details
• You are not required to add content to panes from the
Layout Editor. Content can be added with the ViewApp
Editor too.
• A layout contains multiple sets of properties. Layout
properties apply to the entire layout. Pane properties apply
to the individual panes of a layout. Each pane can be
configured separately.
 Workflow Group 2:
Assemble a ViewApp
A ViewApp typically includes a set of related screen profiles
and layouts. You associate screen profiles and layouts the first
time you open your ViewApp using the Initialization wizard.
Symbol and object standards can be added to a ViewApp from
either the Layout or ViewApp editors.
The ViewApp Editor is the integration tool to combine your
reusable standards to build a ViewApp. The ViewApp Editor
incorporates the ability to add, replace, and edit screen
profiles, layouts, and content.

Also, based on defined user roles and assigned access levels,

you can use the ViewApp editor to restrict the display of
ViewApp content to specific user roles.
30 Workflow Group 2: Assemble a ViewApp

Create a ViewApp
You must create a ViewApp derived template before you can
begin create a ViewApp instance (only instances can be
deployed to run time). Create a new ViewApp by any of the
following methods:
• Keyboard shortcut: Select base ViewApp template, then
press Ctrl + Shift + N to create a derived template. Press
Ctrl + N to create a ViewApp instance.
• Shortcut menu: Right-click on the ViewApp base template,
select New, and then select Derived Template. To create
an instance, select the derived template, select New, and
then select Instance.
• Ribbon bar: Select the ViewApp base template, and then
select Template from the ribbon bar. To create a ViewApp
instance, select the derived template, then select Instance
from ribbon bar.
To create a ViewApp derived template
1. Open the System Platform IDE and select the Template
Toolbox tab to show your Galaxy objects.
2. Expand the Default Templates folder and open the 4.
ViewApps folder.
3. Right-click on the $ViewApp base template, select the
New option, and then select Derived Template.
A $ViewApp derived template appears with a red icon to
indicate that it not yet configured..

Some Details
• A screen profile and layouts must be assigned the first
time you open a ViewApp in the ViewApp editor.
• See Steps to Create a ViewApp in the AVEVA OMI online
help for more information about assigning a screen profile
and layouts to a ViewApp,
 Assign Screen Profiles and Layouts to a ViewApp 31

Assign Screen Profiles and Layouts to a ViewApp

When you start the ViewApp Editor for the first time after
creating a Viewapp, the ViewApp Initialization Wizard opens.
Select a screen profile and layout(s) that will be used with the
ViewApp.
To assign screen profiles and layouts to a ViewApp
1. Open the System Platform IDE and select the Template
Toolbox tab to show your Galaxy objects.
2. Locate the ViewApp derived template and select it.
The ViewApp Initialization Wizard appears with a set of
screen profiles.

3. Select a screen profile from the list and select Next.

4. Select a screen within the profile to place a layout, then
select a layout and associate it with the screen.
5. Select Finish to open the ViewApp and start editing.

Some Details
• At least one screen in a screen profile must be associated
with a layout before editing with the ViewApp editor
(profiles can contain multiple screens).
• For more information about assigning a screen profile and
layouts to a ViewApp, see Steps to Create a ViewApp in the
AVEVA OMI online help.
32 Workflow Group 2: Assemble a ViewApp

Place Content in a ViewApp

You can add content to a ViewApp from the ViewApp Editor
using a drag and drop mouse action or finger gesture.
Assigning content to a pane adds a Show Content action to
the ViewApp’s navigation Action List.
Select either the Toolbox or Assets tab to show a list of
content.
Content can include graphics, layouts, controls, and app
Instances
If you select a folder, the content area beneath the list shows
thumbnails of the content within it.

Search for Content

You can search within the currently displayed Toolbox or Assets
folders to locate objects or graphics by name.
• An Assets search is applied across the entire Galaxy. The
results show the assets containing the search term in a
multi-column list displayed in alphabetical order.
• A Toolbox search is applied across the entire graphic
Toolbox. The results show thumbnails of the graphics that
match the search term in alphabetical order.
To search for assets or graphics
1. Open a ViewApp within the IDE.
2. Select either the Toolbox or Assets tab in the right col-
umn of the ViewApp to show the Search field.
3. Type a search phrase in the Search field. As you type, any
matching assets or graphics appear whose names contain
your search term.
 Place Content in a ViewApp 33

Some Details
• Double-clicking on an asset identified by a search shows
the thumbnails of the graphics associated with the asset.
• Place your cursor over a graphic thumbnail in the search
results to show its folder location within Toolbox.

Embed a Symbol in a ViewApp

Preview thumbnails of symbols appear beneath the tabbed
Toolbox list of the Graphic, Layout, or ViewApp editors.

You place a symbol in a ViewApp by using your mouse to

select and drag a symbol from the Toolbox area and drop it
onto a layout pane from the Layout or ViewApp editors.
Objects shown in the tabbed Assets area of the Layout or
ViewApp editors can be placed in a ViewApp using a similar
drag and drop method.
34 Workflow Group 2: Assemble a ViewApp

Place an Object in a ViewApp

You can create a graphic to embed in an empty pane shown
from the ViewApp Editor. Typically, you create a symbol to
contain an embedded graphic associated with an object.

The Graphic Editor appears again to embed the graphic you

selected in the new symbol.
The Configure New Asset wizard appears with options to
configure the symbol.
The pane in the ViewApp Editor should show the symbol you
created.

Add External Content to a ViewApp

External content refers to content outside of a Galaxy that can
be shown in a running ViewApp.
External content is associated with a ViewApp by placing an
External Content item on a layout pane during design time. An
External Content item is created and then configured with the
External Content editor to identify the location of the content
and the type of content.
 Add External Content to a ViewApp 35

The following figure summarizes the major workflows during

design time to configure an External Content item to point to
content that operators can display while managing a running
ViewApp.

Some Details
• An External Content item can be incorporated into a
ViewApp by dragging the item thumbnail onto a layout
pane or linking it to an object.
• System Platform includes a set of four default apps to
incorporate external videos, spreadsheets, Word
documents, or images into a running ViewApp.
• Place your external content at a folder location within your
network. Verify connectivity between your Desktop Studio
computer and the folder containing External content.

Create an External Content Item

You create an External Content item from the Graphic Toolbox
using one of the following methods:
• Keyboard shortcut: Press Ctrl + Shift + C
• Shortcut menu: Right-click on a folder within the Graphic
Toolbox to show a shortcut menu. Select New, and then
select External Content.
• Ribbon bar: From the Home tab, select External content
from the Create group.
36 Workflow Group 2: Assemble a ViewApp

To create an External Content item

1. Open the IDE and select the Graphic Toolbox tab.
2. Select a toolset folder within the Graphic Toolbox to cre-
ate the External Content item in the folder.
3. Use the Keyboard Shortcut method to create an External
Content item.
Press Ctrl + Shift + C
A new External Content item is created in the Graphic
Toolbox at the folder you selected. The name of the new
item follows a default naming convention of appending a
three-digit number to the word ExternalContent.

4. Rename the External Content item.

Some Details
• After you create an External Content item, it must be
configured to associate it to specific media content.
• Initially, the External Content item defaults to a set of
values that can be changed using the External Content
editor.

Configure an External Content Item

Each External Content item has three properties that must be
assigned values:
• URL or URI
• Media Type
• Content Type(s)
This step explains how to configure an External Content item
for the DocViewer app available with System Platform 2020
R2.
To configure an External Content Item
1. Open the IDE and select the Graphic Toolbox tab to
show the available External Content items.
2. Double click on an External Content item to open it with
the External Content editor.
 Add External Content to a ViewApp 37

3. Enter a URI string where the Word document is saved.

4. Select the type of media associated with Word documents
from the drop-down list of the Media Type field.
5. Select the type of content from the drop-down list of the
Content Type(s) field.
The configured External Content item for a Word
document should look like the following screen capture.

6. Save your changes and exit from the editor.

Some Details
• You can browse for external content by selecting the
vertical dots icon to the right of the URL or URI field. A
drop-down list includes an option that enables you to
browse your network and select a media file

Associate External Content to a ViewApp

You can place an External Content item directly onto a pane
from either the Layout or ViewApp editors. External Content
items are listed in the Toolbox or Assets tabs of either editor.
To associate External Content to a ViewApp
1. Open the System Platform IDE and select the Graphic
Toolbox tab to see the list of layouts.
2. Select a layout that you want to insert external content
and open it in the Layout editor.
3. Locate the External Content item you want to place in the
layout you selected.
External Content thumbnails appear beneath of the list of
content shown in the Toolbox list.
4. Select an External Content thumbnail from the Toolbox
area, and then drag and drop it onto a pane of a layout
incorporated into a ViewApp.
38 Workflow Group 2: Assemble a ViewApp

The External Content thumbnail appears in the pane

containing the name of the External Content item, the
media type of the external content, and the viewer app
that will display the media during runtime.
Some Details
• For more information about associating external content
to an object that will be included in a ViewApp, see Link an
External Content item to an Object in the AVEVA OMI help
• For more information about the entire set of workflows to
add external content to a ViewApp, see External Content in
the AVEVA OMI help.
 Workflow Group 3: Deploy
a ViewApp
An instance of your ViewApp must be deployed with a
ViewEngine and other system and application objects before
you can run it.
Deployment instantiates Galaxy objects in a runtime
environment, which are required to run a ViewApp. You must
deploy your objects before attempting to run a ViewApp.
You can see the arrangement of your system and application
object instances from the Deployment or Model views of the
System Platform IDE.

Some Details
• Deployment includes installing required software on a
target computer. Bootstrap software must be installed on
every computer running a ViewApp.
• No object can be in an error state to deploy a ViewApp.
• Objects must be checked into the Galaxy
40 Workflow Group 3: Deploy a ViewApp

Prepare to Deploy a ViewApp

You can deploy and test your objects at any time during
development. When you are ready to test or run a ViewApp in
production, you deploy the Galaxy. You can see what your
application looks like in the Deployment view or Model view
of the System Platform IDE. Both views show the structure of
your application.
The Deployment view provides the simplest way to
understand the object hierarchy during deployment. Objects
appear in a hierarchical tree structure according to their
distribution relationships.
Galaxy>WinPlatform>AppEngine>Area>App or
Communication Drivers
• The top of the tree is the Galaxy.
• WinPlatforms are shown under the Galaxy.
• AppEngines are under each WinPlatform
• Under each AppEngine, assigned Areas and device
integration (DI) objects, such as OPCClient objects, are
listed.
• Assigned application objects are listed under each Area.
• Under each application object, contained application
objects are listed. Multiple levels are allowed.
• Communication Drivers are listed under the device
integration object to which they are assigned.
• Unassigned objects are placed in the Unassigned Area
folder. Area and containment relationships are maintained
in this view
Some Details
• The appearance of the icons to the left of each object
shown in the Deployment view indicate the deployment
and quality status of each object.
• Select Galaxy Status on the Galaxy menu to see the
condition of your Galaxy.
 Deploy a ViewApp 41

Deploy a ViewApp
You can tell if you have objects that need to be deployed by
looking at the icons next to the objects shown in the
Deployment view. Typical deployment status icons include:
• Not deployed
• Deployed
• Deployed, but pending changes have not been deployed
To deploy a ViewApp
1. Right-click on the Galaxy object in the Deployment view
and select the Deploy option from the shortcut menu.
The Deploy dialog box appears.

2. Accept the default options and select OK.

Key Points
• During deployment, all files to run a ViewApp are copied
to a folder on the client computer designated to run the
ViewApp.
• A cascade deploy operation deploys all objects in
hierarchical order. A cascade operation deploys a host
object before deploying its child objects.
42 Workflow Group 3: Deploy a ViewApp
 Workflow Group 4: Run a
ViewApp
You typically run a ViewApp on a different computer than the
computer you use to develop a ViewApp. You start a ViewApp
by selecting it from a list of deployed ViewApps shown from
AVEVA OMI Application Manager.

Launch and Run a ViewApp

After you successfully deploy your ViewApp, you can launch it
from AVEVA OMI Application Manager.
44 Workflow Group 4: Run a ViewApp

To launch and run a ViewApp

1. Show the Windows desktop of the computer where the
ViewApp has been deployed.
2. Select the AVEVA OMI Application Manager icon shown
on the Windows desktop.

Application Manager appears with a list of deployed

ViewApps.

3. Select the LAUNCH button of the ViewApp that you want

to run.
After several seconds, the ViewApp's main window
appears in a separate window on your screen.
Some Details
• You can run multiple ViewApps simultaneously.
• Click the icon shown to the right of the LAUNCH button
for options to run the ViewApp in read/write mode
(default) or launch the ViewApp with a read-only data
connection.
 Run a ViewApp in Preview Mode 45

Run a ViewApp in Preview Mode

When you are building a ViewApp, you can immediately
preview and assess your editing changes in run time mode.
Previewing your work enables you to work more quickly
because you do not need to undeploy and redeploy your
Galaxy objects each time you modify your ViewApp to verify
your changes.
To preview a ViewApp
1. Open the System Platform IDE.
2. Open an undeployed ViewApp in the ViewApp editor.
3. Select the Preview button near the top right corner of the
ViewApp editor.

The first time you request a preview, a caution message

explains that preview mode is not intended for production
usage. Select the check box in the message to not show
the message again.
4. Click OK to continue.
Within several seconds the preview session launches from
the computer hosting the System Platform IDE.
5. Click the standard Close icon on the ViewApp window
frame to stop running in preview mode.
Some Details
• The AutoUpdate icon next to the Preview button enables
or disables any updates to the ViewApp to appear in
preview mode. If the ViewApp contains unsaved changes,
the ViewApp will be saved and the new configuration
passed to Preview
• The preview window opens and shows the current focus of
the ViewApp as it is edited in the ViewApp editor.
46 Workflow Group 4: Run a ViewApp
 Get More Information
The System Platform library consists of a set of online books
and help. Each product that is part of System Platform includes
individual documentation about using the product.
System Platform documentation is offered in two different
media:
• Portable Document File (PDF), which can be viewed with
Adobe® Reader®. Each book is included on the product
installation DVD as a PDF file.
• Online help from the System Platform IDE, which can be
viewed while developing AVEVA InTouch HMI or AVEVA
OMI applications.
The PDF books and online help include a table of contents, an
index, and a search function to find information quickly.
Product documentation uses a task-based approach. This
means information is organized in the typical workflows to
build, configure, and use System Platform products.
48 Get More Information

Easy Access to System Platform Documentation

During the installation of System Platform 2020 R2, hyperlinks
to documents are placed on your Windows Start menu. The
hyperlinks are listed within the AVEVA Documentation folder.
Clicking on a hyperlink opens the document with your PDF
viewer.
 Application Server 49

Application Server
The following table describes each Application Server
documentat in the library.

Publication Name
(file name) Description

AVEVA System Platform Readme Includes descriptions of new

Readme.htm product features introduced in
System Platform, installation
requirements, and any known
issues.

AVEVA Application Server User Explains configuring and deploying

Guide Application Server and AVEVA OMI
IDE.pdf applications.

Application Server Scripting Guide Reference for the Application

Scripting.pdf Server scripting language.

Industrial Graphics User Guide Explains how to create and manage

aaGraphics.pdf Industrial Graphics with the Graphic
Editor within the Integrated
Development Environment (IDE).

Object Viewer User’s Guide Explains how to acquire run-time

ObjectViewer.pdf data using the Object Viewer.

Alarm Control Guide Explains how to configure the

aaAlarmClientControl. pdf alarm control (client) to show
current and historical alarms and
events in a grid. 

Trend Client User Guide Explains how to configure a chart

aaTrendClient.pdf to trend real-time data values.

Platform Manager User Guide Explains how to start and stop

PlatformManager.pdf system components.

Galaxy Database Manager User Explains how to back up and

Guide restore the Galaxy database.
galaxymanagement.pdf
50 Get More Information

Publication Name
(file name) Description

Log Viewer User Guide Explains how to use the Log Viewer
LogViewer.pdf utility to determine system
diagnostics.

Log Flag Editor User Guide Explains how to turn on and off
LogFlagEditor.pdf certain diagnostics logging
messages.

AVEVA Enterprise Licensing Guide Explains how to use the AVEVA

AELicenseManagerGuide.pdf Licensing system to manage
software product licenses.

Protocols User Guide Explains background information

Protocol.pdf on the main communication
protocols used between
components of System Platform
products.

AVEVA InTouch HMI and Integration Explains how you can use the
Guide System Platform Integrated
ITAAIntegration.pdf Development Environment (IDE) to
manage InTouch HMI applications
so that you can use symbols you
create in the Industrial Graphic
Editor. This guide is available on the
AVEVA InTouch HMI installation CD.
Application Server documention is also available as online
help. Press F1 from the System Platform IDE to show the help
in your browser.

AVEVA OMI
All AVEVA OMI product documentation is available as online
help that you view with a web browser. Press F1 from the
System Platform IDE modern editors to show online help:
• Screen Profile editor
• Layout editor
• ViewApp editor
• ViewApp Namespace editor
 AVEVA InTouch HMI 51

• External Content editor

The AVEVA OMI help system includes tutorial videos, a search
engine, a table of contents, and a set of navigation controls to
find information quickly and easily.

AVEVA InTouch HMI

The following table describes the AVEVA InTouch HMI
documentation library delivered as PDF files. Online help is
available for each application.

Publication Name
(file name) Description

AVEVA™ InTouch HMI Contains information on creating

Creating Standards for standards for various InTouch HMI
InTouch HMI Components components, and describes how to
Guide prepare the development
ITStandards.pdf environment, view the application
in run time, and gain an
understanding on how to work with
tags, alarms, and data items in the
InTouch HMI to connect your
application to the physical devices
in your plant environment.

AVEVA™ InTouch HMI Contains information on creating

Application Development and managing InTouch HMI
Guide applications locally and in a
ITBuild.pdf network environment, including:
how to how to create visualization
windows, how to draw and animate
graphic elements, and how to use
wizards and ActiveX controls in
your application.
This guide also includes a reference
of the InTouch HMI scripting
language and functions, along with
details on working with Industrial
Graphics in the Cloud.
52 Get More Information

Publication Name
(file name) Description

AVEVA™ InTouch HMI Contains information on deploying

Application Deployment InTouch HMI applications to work
Guide with terminal and remote desktop
ITDeploy.pdf services, and describes how to
configure InTouch HMI Network
Application Development and use
Managed applications at run time.

AVEVA™ InTouch HMI Contains information on using

Application Run Time Guide WindowViewer and Web Client to
ITOperate.pdf view the InTouch HMI applications
in run time, and also describes
viewing application graphics in a
web browser, with a focus on
langugae switching, tag viewer, and
various alarm components.

AVEVA™ InTouch HMI Contains information on migrating

Application Maintenance and upgrading InTouch
Guide applications, components, and
ITMaintain.pdf alarms, and also describes how to
set up an InTouch HMI application
on tablet PC or multi monitors.

AVEVA™ InTouch HMI Contains troubleshooting

Troubleshooting Guide information to understand error
ITDiagnose.pdf messages and resolve issues with
the InTouch HMI application and
Web Client.

AVEVA™ InTouch HMI Contains licensing information for

Management Guide the InTouch HMI application and
ITManage.pdf Web Client, as well as generic and
InTouch-specific security
configurations, and also describes
using other supplementary
components.
 InTouch Access Anywhere 53

InTouch Access Anywhere

InTouch Access Anywhere is part of the System Platform family
of products and can display AVEVA OMI ViewApps on a variety
of portable devices. Its documentation is included in the
AVEVA OMI online help.
InTouch Access Anywhere can also be ordered as a separate
product with its documentation library delivered as PDF files.

Publication Name
(file name) Description

InTouch Access Anywhere Provides procedures and references

Server Administrator for system administrators to
Manual configure and manage the InTouch
ITAA_Server_Admin Access Anywhere server.
Manual.pdf

InTouch Access Anywhere Provides procedures and references

Secure Gateway for system administrators to
Administrator Manual configure and manage the InTouch
ITAA_Gateway_Admin Access Anywhere Secure Gateway.
Manual.pdf

InTouch Access Anywhere Provides guidelines for end users to

User Manual display remote InTouch applications
ITAA_UserManual.pdf by means of InTouch Access
Anywhere.
54 Get More Information

AVEVA Historian
The following table describes the AVEVA Historian
documentation library delivered as PDF files. Online help is
available from within the application.

Publication Name
(file name) Description

Historian Concepts Guide This guide provides an overview of

HistorianConcepts.pdf the entire Historian system and
describes each of the subsystems in
detail.

Historian Administration This guide describes how to

Guide administer and maintain an
HistorianAdmin.pdf installed Historian, such as
configuring data acquisition and
storage, managing security, and
monitoring the system.

Historian Database This guide provides documentation

Reference for all of the Historian database
HistorianDatabase.pdf entities, such as tables, views, and
stored procedures.

Historian Glossary This guide provides definitions for

HistorianGlossary.pdf terms used throughout the
documentation set.

Historian Retrieval Guide This guide describes the retrieval

HistorianRetrieval.pdf modes and options that you can
use to retrieve your data.

Historian Scenarios Guide This guide discusses how to use

HistorianScenarios.pdf Historian to address some common
customer scenarios.
 AVEVA Historian Client 55

AVEVA Historian Client

The following table describes the AVEVA Historian Client
documentation delivered as a PDF file. Online help is available
from within the application.

Publication Name
(file name) Description

Historian Client User Guide This guide describes how to use the
HistClient.pdf Historian Client to organize,
explore, analyze, present, and
disseminate process data in a wide
variety of formats.

Technical Support
AVEVA Technical Support consists of a global team of qualified
Certified Support Providers. If you have questions or concerns
about System Platform, contact AVEVA Technical Support.
Telephone: U.S. and Canada
800-966-3371
7 a.m. to 5 p.m Pacific Time

Outside the U.S. and Canada

For local support in your language, contact a
certified support provider in your area or country.
Refer to the following web address for a local
phone number in your country:
https://sw.aveva.com/support/
Dial your country's local international direct dialing
(IDD) code and then the 800-number listed for
your country.

Fax: +1 949-639-1545

E-mail: Customer First members, send an e-mail message

to our priority address:
custfirstsupport@aveva.com
56 Get More Information

Customers without a support agreement, send an

e-mail message to:
wwsupport@aveva.com

Web: Registered customers, submit your questions to

our Support web site.
Refer to the following web site for instructions to
register for AVEVA technical support:
https://sw.aveva.com/support/

Product Training
AVEVA offers a training course for System Platform and
individual courses for the products that make up System
Platform. Training courses are held at our training facilities in
Lake Forest, California, as well as at regional offices worldwide.
On-site customer training programs are also available at your
site.
Telephone: U.S. and Canada
866-998-7246

Outside the U.S. and Canada

+1 949-639-8508

Fax: 1-949-639-1847

Mail: AVEVA
26561 Rancho Parkway South
Lake Forest, CA 92630 USA
Attn: Training Department

E-mail: avevatraining@aveva.com

Web: For training in your language, contact an AVEVA

certified training provider in your area or country.
Refer to the following web address that lists
certified training providers in various countries:
https://sw.aveva.com/training/
 AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 OHB. UK
https://sw.aveva.com/
For information on how to contact sales, customer training,
and technical support, see https://sw.aveva.com/contact.

Part Number 13-0247