Basic Adroit Ignite Training Manual 2021 - Rev06

COPYRIGHT
Copyright © 2021 Advanced Worx 112 (Pty) Ltd. All rights reserved.
Information in this document is subject to change without notice. The software described in this document is furnished under a
license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those
agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means
electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the
written permission of Advanced Worx 112 (Pty) Ltd.
Advanced Worx 112 (Pty) Ltd

20 Waterford Office Park
189 Witkoppen Road (c/o Waterford Drive)
Fourways
South Africa
www.adroitscada.com
Version Date Author Comment Approval

1.0 12.07.2021 J. Duncan / J. Stone Original
2.0 23.07.2021 J. Duncan / J. Stone Various Updates and Exercise modifications
3.0 25.07.2021 J. Duncan Add Ignite Logo
3.0 27.07.2021 J. Duncan / D. Wibberley Strategic changes and improvements
4.0 29.07.2021 J. Duncan / J. Stone Finalise formatting and content
5.0 03.08.2021 J. Duncan / D. Wibberley Finalise flow and content
6.0 12.08.2021 J. Duncan / D. Wibberley Update content
__________________________________________________________________________________________________________________________
Basic Adroit Ignite Training Manual 2021_Rev06.docx Page|2
Contents
1. Introduction........................................................................................................................................ 7
1.1. Adroit Ignite HMI Overview ......................................................................................................... 8
1.2. Introducing Adroit Ignite HMI ...................................................................................................... 9
1.3. How is Adroit Ignite HMI packaged? ............................................................................................. 9
1.3.1. Licensing Definitions .......................................................................................................................... 10
2. Course Overview............................................................................................................................... 11
2.1. The Batching Plant Training Project ............................................................................................ 11
3. A Guide to Best Practices.................................................................................................................. 11
3.1. Define the end goal of the Automation Solution ........................................................................... 11
3.2. Visualisation and Control Strategy .............................................................................................. 12
3.2.1. Three Primary Principles ..................................................................................................................... 12
3.2.2. Graphic Hierarchy .............................................................................................................................. 12
3.2.3. Control Plan...................................................................................................................................... 12
3.2.4. HMI Standards .................................................................................................................................. 13
3.2.5. HMI/PLC Interface ............................................................................................................................. 13
3.2.6. Reporting Strategy ............................................................................................................................ 13
3.2.7. Alarming Strategy.............................................................................................................................. 14
3.2.8. Security Strategy ............................................................................................................................... 14
4. Main Components and Architecture ................................................................................................. 15
4.1. Data Layer............................................................................................................................... 15
4.1.1. Agent Server .................................................................................................................................... 15
4.2. The Ignite Server ..................................................................................................................... 16
4.3. Presentation Layer.................................................................................................................... 16
4.3.1. The Designer .................................................................................................................................... 16
4.3.2. The Operator .................................................................................................................................... 17
4.4. Help and ReadMe Files .............................................................................................................. 18
5. Installing Adroit Ignite HMI ............................................................................................................. 19
5.1. Hardware & Software Requirements ........................................................................................... 19
5.1.1. Recommended Hardware & Software ................................................................................................... 19
5.1.2. Additional Software............................................................................................................................ 19
5.2. Licensing ................................................................................................................................. 19
5.2.1. Licensing definitions........................................................................................................................... 19
5.3. Pre-requisites for installing Adroit Ignite HMI software.................................................................. 19
Exercise 1 - Installation of the Adroit Ignite HMI software ................................................................................... 20
5.4. License Installation ................................................................................................................... 22
Exercise 2 - Installation of the Adroit Ignite HMI License ..................................................................................... 23
Exercise 3 – Starting the Adroit Ignite HMI ........................................................................................................ 25
6. Training Course................................................................................................................................. 27
6.1.1. Objective of the Training Course .......................................................................................................... 27
6.1.2. Overview Drawing ............................................................................................................................. 28
6.2. Batching Simulation OPC Server ................................................................................................. 29
7. Adroit Ignite Config Editor ............................................................................................................... 31
Exercise 4 - Creating a New Configuration ......................................................................................................... 32
Exercise 5 - Driver Configuration...................................................................................................................... 34
Exercise 6 - Launching the Designer ................................................................................................................. 35
8. The Designer ..................................................................................................................................... 36
8.1. The Agent Configurator............................................................................................................. 37
8.2. Default Tool & View Windows .................................................................................................... 38
8.3. The Home Menu: ..................................................................................................................... 42
8.4. The View Menu: ....................................................................................................................... 43
8.5. The SCADA Menu: .................................................................................................................... 45
8.6. The Configuration Menu: ........................................................................................................... 46
8.7. The Diagnostics & Tools Menu: .................................................................................................. 47
8.8. The Project Menu: .................................................................................................................... 48
8.9. The Design Menu: .................................................................................................................... 49
___________________________________________________________________________________________________________________________
8.10. The Behaviors Menu: ................................................................................................................ 50
8.11. Shapes Wizards & Examples Menus ............................................................................................ 51
8.12. Graphic Form Toolbar ............................................................................................................... 52
8.12.1. Save Functions .............................................................................................................................. 52
8.12.2. Substitutions ................................................................................................................................. 52
8.12.3. Launch Script Editor ....................................................................................................................... 52
8.12.4. Design & Run................................................................................................................................ 52
8.12.5. Zoom........................................................................................................................................... 53
8.12.6. Optimise Graphic Form ................................................................................................................... 53
8.12.7. Statistics, Optimizations & Find and Replace ...................................................................................... 53
9. Agents ............................................................................................................................................... 54
9.1. Overview - Agent Groups and Agent Types ................................................................................. 54
9.2. Naming Convention .................................................................................................................. 56
9.2.1. Agent .............................................................................................................................................. 56
9.2.2. Device ............................................................................................................................................. 56
9.2.3. Agent Types Overview ....................................................................................................................... 57
9.2.4. Slots................................................................................................................................................ 58
9.2.5. Data Elements .................................................................................................................................. 59
9.2.6. Header Slots ..................................................................................................................................... 60
9.2.7. Status Bits/Agent Header Slots ............................................................................................................ 61
9.3. Primitive Agent Types ............................................................................................................... 62
9.3.1. Boolean Agent .................................................................................................................................. 62
9.3.2. Text Agent ....................................................................................................................................... 62
9.4. Basic Agent Types .................................................................................................................... 63
9.4.1. Analog Agent .................................................................................................................................... 63
9.4.2. Counter Agent .................................................................................................................................. 64
9.4.3. Digital Agent..................................................................................................................................... 64
9.4.4. Expression Agent............................................................................................................................... 65
9.4.5. String Agent ..................................................................................................................................... 66
9.4.6. StringList Agent ................................................................................................................................ 66
9.4.7. Timer Agent ..................................................................................................................................... 67
9.5. Advanced Agent Types.............................................................................................................. 68
9.5.1. AgentGroup ...................................................................................................................................... 68
9.5.2. Alarm Agent ..................................................................................................................................... 68
9.5.3. AlarmList Agent................................................................................................................................. 69
9.5.4. Command Agent ............................................................................................................................... 70
9.5.5. DBQuery Agent ................................................................................................................................. 70
9.5.6. DBLog Agent .................................................................................................................................... 71
9.5.7. EventLogging Agent........................................................................................................................... 71
9.5.8. EventOutput Agent ............................................................................................................................ 72
9.5.9. MultiMedia Agent............................................................................................................................... 72
9.5.10. Notify Agent ................................................................................................................................. 73
9.5.11. Script Agent.................................................................................................................................. 73
9.5.12. Shift Agent ................................................................................................................................... 74
9.5.13. Statistical Agent ............................................................................................................................ 74
9.6. MIS/MES Agent Types............................................................................................................... 75
9.6.1. Accumulator Agent ............................................................................................................................ 75
9.7. IT/IoT Agent Types .................................................................................................................. 76
9.7.1. PerfMon Agent .................................................................................................................................. 76
9.8. System Agent Types ................................................................................................................. 77
9.8.1. Alias Agent ....................................................................................................................................... 77
9.8.2. DataLog Agent .................................................................................................................................. 77
9.8.3. Device Agent .................................................................................................................................... 79
9.8.4. Other System Agent Types ................................................................................................................. 79
9.9. Adding the Tags for the Batching Plant ....................................................................................... 81
Exercise 7 - Configuring Digital Agents: First Principles........................................................................................ 82
Exercise 8 - Configuring Analog Agents: First Principles ....................................................................................... 84
Exercise 9 - Configuring Stringlist Agents: First Principles .................................................................................... 86
Exercise 10 - Configuring Expression Agents: First Principles ................................................................................ 88
Exercise 11 - Configuring Counter Agents: First Principles .................................................................................... 90
9.10. Scanning Agents/Tags .............................................................................................................. 92
9.10.1. The Principles of Scanning .............................................................................................................. 92
___________________________________________________________________________________________________________________________
9.10.2. Golden Rules for Scanning: ............................................................................................................. 92
9.10.3. Device and Scan Agents ................................................................................................................. 93
9.10.4. Calculating the Scan Period ............................................................................................................. 93
Exercise 12 - Scanning Digital Agents: First Principles ......................................................................................... 94
Exercise 13 - Scanning Analog Agents: First Principles......................................................................................... 97
Exercise 14 - Scanning StringList Agents: First Principles ..................................................................................... 99
10. Project Tree and Graphic Forms ..................................................................................................... 100
Exercise 15 - Creating a Project Tree ............................................................................................................... 101
11. Behaviours ...................................................................................................................................... 103
11.1. Bind Value Behaviour ............................................................................................................... 103
11.2. Colour Behaviour..................................................................................................................... 103
11.3. Display Value Behaviour ........................................................................................................... 104
11.4. Execute Command Behaviour ................................................................................................... 104
11.5. Flip Bitmap Behaviour .............................................................................................................. 104
11.6. Location Behaviour .................................................................................................................. 104
11.7. Operator Action Behaviour........................................................................................................ 104
11.8. Percentage Fill Behaviour ......................................................................................................... 104
11.9. Rotation Behaviour .................................................................................................................. 105
11.10. Size Behaviour..................................................................................................................... 105
11.11. Tooltip Behaviour................................................................................................................. 105
11.12. Visibility Behaviours ............................................................................................................. 105
12. Design Mode: Building Graphic Forms............................................................................................ 106
Exercise 16 - Building the Batching Plant Graphic Form ...................................................................................... 107
Exercise 17 - Adding Static Graphics and Colour Behaviour [Part 1]...................................................................... 109
Exercise 18 - Adding Static Graphics and Colour Behaviour [Part 2]...................................................................... 111
Exercise 19 - Percentage Fill Behaviour ............................................................................................................ 113
Exercise 20 - Location and Visibility Behaviour [Part 1] ....................................................................................... 115
12.1. Creating Labels and Displaying Real Time Data ........................................................................... 116
Exercise 21 - Creating Labels.......................................................................................................................... 117
Exercise 22 - Display Value Behaviour (Level & Status) ...................................................................................... 118
Exercise 23 - Visibility Behaviour ..................................................................................................................... 120
Exercise 24 - Bind Behaviour .......................................................................................................................... 121
Exercise 25 - Tooltip Behaviour....................................................................................................................... 122
Exercise 26 - Blinking Behaviour ..................................................................................................................... 123
Exercise 27 - Operator Behaviour [Part 1] ........................................................................................................ 124
Exercise 28 - Operator Behaviour [Part 2] ........................................................................................................ 125
Exercise 29 – Execute Command Behaviour ...................................................................................................... 127
13. Datalogging .................................................................................................................................... 129
14. Trends/Charts................................................................................................................................. 130
Exercise 30 - Basic Datalogging (.LGD file) ....................................................................................................... 131
Exercise 31 - Displaying Logged Data in a Trend ............................................................................................... 132
Exercise 32 - Retrieve Logged Data ................................................................................................................. 135
15. Wizards & Templates ...................................................................................................................... 136
15.1. Wizards .................................................................................................................................. 136
15.1.1. Creating a Wizard ......................................................................................................................... 136
Exercise 33 - Creating a Basic Dynamic Wizard [Method 1] ................................................................................. 137
Exercise 34 - Creating a Basic Dynamic Wizard [Method 2] ................................................................................. 139
Exercise 35 - Making use of a User Defined Wizard ............................................................................................ 141
15.2. Templates .............................................................................................................................. 142
Exercise 36 - Creating a Template [Part 1] ....................................................................................................... 143
Exercise 37 - Creating a Template [Part 2] – Display Actual/Target Values ............................................................ 146
Exercise 38 - Creating a Template [Part 3] - Trend Button .................................................................................. 147
Exercise 39 - Creating a Template [Part 4] - Close Button................................................................................... 148
16. System Events ................................................................................................................................ 149
16.1. What is an Event? ................................................................................................................... 149
Exercise 40 - Adding a Tab Control.................................................................................................................. 150
Exercise 41 - Event View Window ................................................................................................................... 151
17. Alarms ............................................................................................................................................. 152
___________________________________________________________________________________________________________________________
17.1. What is an Alarm? ................................................................................................................... 152
17.2. Alarm Type ............................................................................................................................. 153
17.3. Configuring the Alarm Agent Instance........................................................................................ 154
Exercise 42 - Configuring Alarm Routes............................................................................................................ 155
17.4. Alarming an Agent Instance...................................................................................................... 158
Exercise 43 - Setting up Alarm Masks .............................................................................................................. 159
17.5. Alarm List Viewer Control ......................................................................................................... 161
Exercise 44 - Setting up Alarm View Windows ................................................................................................... 162
17.6. What is the difference between Alarms and Events? .................................................................... 163
18. Navigation ...................................................................................................................................... 164
Exercise 45 – Navigation [Part 1] .................................................................................................................... 165
Exercise 46 - Navigation [Part 2] - Adding Menu Items and Graphic Forms............................................................ 167
Exercise 47 - Navigation [Part 3] - Add a Default Graphic on Home Page .............................................................. 168
19. Operator Settings ........................................................................................................................... 169
19.1. Customizable Operators Settings & Configuration ........................................................................ 169
Exercise 48 - Adding a Default Graphic Form to the Operator .............................................................................. 171
20. Ignite Utilities ................................................................................................................................. 172
20.1. Adtech Licensing Utility ............................................................................................................ 172
20.2. Agent Browser ........................................................................................................................ 173
20.3. OPC Browser .......................................................................................................................... 173
20.4. OPC Server ............................................................................................................................. 174
20.5. Scanning Monitor .................................................................................................................... 174
20.6. Driver Monitor......................................................................................................................... 174
20.7. Scheduler ............................................................................................................................... 175
20.8. Script Editor............................................................................................................................ 176
21. System Backup and Restore ........................................................................................................... 177
Exercise 49 - Project Backup .......................................................................................................................... 177
Exercise 50 - Project Restore .......................................................................................................................... 178
22. Batch Plant I/O Schedules ............................................................................................................. 180
22.1. Analog Agents......................................................................................................................... 180
22.2. Digital Agents ......................................................................................................................... 181
22.3. StringList Agent ...................................................................................................................... 182
22.4. Expression Agents ................................................................................................................... 182
22.5. Counter Agents ....................................................................................................................... 182
23. Adroit Ignite HMI Competency Test (Optional) ............................................................................. 183
23.1. Introduction............................................................................................................................ 183
23.2. Procedure, URS and Process Description .................................................................................... 183
23.2.1. Certificate of Competency .............................................................................................................. 184
___________________________________________________________________________________________________________________________
1. Introduction
Adroit (Advanced Distributed Real-time Object-oriented Intelligent Toolkit), is an English word that
means “flexible or dexterous”.
Adroit Ignite HMI is an open, object-oriented, human machine, process automation software, structured
around a distributed client-server architecture, where:
• The I/O Server component is known as the Agent Server.
• The Ignite Server is a middleware layer and;
• The Client component is typically the Ignite Designer and Operator.
In order to understand Adroit Ignite HMI, it is important to understand the basic architecture of the
product. Below is a diagram, which represents the basic architecture:
• Front End Device (FED): The front-end device is a general term used for a PLC; OPC server;
RTU; a controller; or any software package that allows third party communication (i.e.
SIMATIC NET).
• Protocol drivers: Adroit Ignite HMI supports +- 100 different protocols. Once a new driver
has been created and configured, it is called a device. A single protocol can support multiple
devices. An example of this is the user can have multiple FEDs which use the same protocol
(i.e. MODBUS Ethernet), each FED will have its own IP address/Address. A device will need to
be created for each FED.
• Datasource: Each source of data (i.e. Adroit Ignite HMI Agent Server) requires a datasource
plugin before it can be associated with the Ignite Server. This provides the ability to expose
its data as Data Elements.
An example of a Data Element is Adroit.Analog._SAMPLEANALOG.value.
Adroit Ignite HMI supplies the following datasources as standard: -

Datasource Purpose
Adroit Exposes the configured Agents and their slots, of the connected Adroit Ignite HMI
Agent Server.
Event Log Exposes the events within the Windows event logs of the connected specific
computer.
OLE DB Exposes the data within a specific OLE DB compliant database or data store.
Server Scripts Stores scripts that can be run on the Server.
Simulation Exposes a wide variety of different types of generated data
Note: For further information on the available Datasource see the Adroit Ignite HMI help.
• Agent Server (AS): (I/O Server) is the real-time database, which handles the real-time
values and if configured, will log and/or alarm the data.
• Ignite Server: is a middleware layer server which exposes data from a number of disparate
sources, and also acts as a repository for the graphic forms or mimics.
• Clients: The Adroit Ignite HMI comes with two types of clients which connects to the Ignite
Server:
o The Designer: The Designer allows the user to configure Datasources as well as create
and design graphic forms.
o The Operator allows you to operate graphic forms.
When connecting to the Ignite Server the user will be prompted for login credentials. The default
credentials are the same as the windows credentials that the user installed Adroit Ignite HMI.
___________________________________________________________________________________________________________________________
1.1. Adroit Ignite HMI Overview
Figure 1 Adroit Ignite HMI Overview
__________________________________________________________________________________________________________________________________________________________________________________
1.2. Introducing Adroit Ignite HMI
Adroit Ignite HMI is a process visualisation/SCADA product and as such is primarily concerned with
process values, since these are essentially used to supervise and control processes. Like all programs,
Adroit Ignite HMI has its own terminology or language and in this case, the language applies to how it
refers to these process values.
• Agent Architecture: Create the necessary Agents to both acquire and store the process
variables and perform more advanced calculations and manipulations.
• Communication of process values: This is the primary function of any SCADA; in that it
allows a user to bring in and send out values via front-end devices in the field. This allows the
process to be supervised (SCADA).
• Alarming of values: When values transgress configurable operational limits, an alarm can
be created to notify the user of this transgression using a variety of methods.
• Logging or recording of values: This allows the values of the process to be saved to
proprietary historical files and/or to databases, so that they can be retrieved for long-term
analysis and reporting purposes (ASI) and/or real time trending.
• Displaying of values: This is usually performed through the creation of graphic forms where
values can be displayed, manipulated and / or used to animate the graphic forms.
• Trending of values: it is also possible to visually trend the fluctuations of these values, both
in real-time and / or when combined with logged values, to provide historical trending too.
Adroit Ignite HMI is built on a client-server architecture, where the Agent Server is the database that
contains the values and the Ignite Server and Clients which provides the capability of accessing,
configuring, displaying and manipulating the values
1.3. How is Adroit Ignite HMI packaged?

The Adroit Ignite HMI software is licensed based on two criteria i.e. the number of Agents you will use
and Ignite Operators or other Clients that will concurrently be needed by a user. Remote clients refer to
the number of additional PCs that will be running Adroit Ignite HMI Operators so that multiple users can
view the process simultaneously. The maximum number of Operators that can be licensed is two
additional connections.
Typically, Adroit Ignite is licensed using our software licensing mechanism. You will be given 30 days to
complete and complete licensing on the machine you will be deploying in the field. Once licensed it is
not possible to transfer the license to another machine.
Alternatively you may purchase a USB dongle/HASP software protection key, which is inserted into the
USB port of the computer on which the Agent Server is running. This HASP is then programmed in
accordance with your specific license agreement. Please note this option makes it easy to transfer
between machines, but this option costs US$50 plus transport costs additional to the cost of the software.
Adroit Ignite HMI is packaged in different scan point sizes; these are 8 (Free), 30, 75, 150. This allows
the user to purchase the size that best fits the application. Functionality of all packages is uniform,
irrespective of the number of Agents and remote clients.
On purchasing Adroit Ignite HMI the customer receives the following:

A link to the latest release of the software containing all of the Adroit Ignite HMI tools to configure and
run the system that can be downloaded from our website. The download also contains all available PLC
drivers/interfaces, over 300 pre-configured graphic objects such as meters, lights, conveyors, pumps
etc., sample applications, and a comprehensive help system. The link to the downloads page is also
available Here.
_________________________________________________________________________________________________________________________
______________________________________________________
Basic Adroit Ignite Training Manual 2021_Rev06.docx
Page|9
1.3.1. Licensing Definitions
Adroit Ignite HMI is licensed based on the following:-
• Agents: When a memory address is scanned/attached in the PLC and every DBQuery and
Script that is used.
• Remote Clients/Operator Stations: A remote client licence is required for every client
connection.
• Number of other licenses applications such the HTML5 Performance Anywhere Client or the
Adroit Air Mobile application. Both of which can be used with the Adroit Ignite HMI software.
• Version: Adroit Ignite installations are licensed against versions of Adroit.
• OEM: Additional components are licensed against the OEM code license. E.g. Siemens
Ethernet driver; Allen Bradley.
_________________________________________________________________________________________________________________________
Basic Adroit Ignite Training Manual 2021_Rev06.docx P a g e | 10
2. Course Overview
2.1. The Batching Plant Training Project
The Adroit Ignite HMI training project is based on a Batch Plant simulation OPC Server that is supplied
as part of the Adroit Ignite HMI install. This OPC Server simulates a PLC that controls a simple Batching
Process, including Process Parameter Setting and Production Target Setting etc. along with various
Process variables for doing quality, alarming etc.
This course has been designed as to both empower the user to discover the wide, wonderful and powerful
world of Adroit Ignite HMI and at the same time reveal the fundamentals of the product. It must be
borne in mind that Adroit Ignite HMI, while being very user friendly, is a flexible, scalable and open
product that allows a user to achieve almost anything no matter how complex.
While every attempt has been made to make this manual a complete guide to the product, it remains to
be said that it must be used in conjunction with the Help file and Adroit Ignite HMI documentation as
found on the website (www.adroitscada.com).
Further, it is intended to assist in defining a project and the resulting expectations from the Adroit Ignite
HMI product. It helps to clarify all possible issues prior to “going down the road” and then hitting
limitations (either environmental or product) that may not have been addressed in the pre-project phase.
Also, if fleshed out in enough detail, it can stand as a complete project document, not only for the initial
phase but also for years to come and can be used as a knowledge and standards base for the life of any
plant.
3. A Guide to Best Practices

Planning is the process of identifying the means, resources and actions necessary to accomplish one or
more objectives. The scenario below is a combination of various methods and is by no means an attempt
to establish precedence. It is simply an example and basic guide to planning.
"A best practice tends to spread throughout a field or industry after a success has been demonstrated.
However, it is often noted that demonstrated best practices can be slow to spread, even within an
organization. According to the American Productivity & Quality Centre, the three main barriers to
adoption of a best practice are a lack of knowledge about current best practices, a lack of motivation to
make changes involved in their adoption, and a lack of knowledge and skills required to do so."
This covers how you approach an Adroit Ignite HMI project and product choice.
3.1. Define the end goal of the Automation Solution

Choose the Value-Added Features of Adroit Ignite HMI to complete the task
Consider the following criteria when licensing Adroit Ignite HMI:
• The number of Agents you will need. This may be a little difficult as the license is based on
the number of Agents you use to complete a task. A good starting point would be the number
of I/O that will be scanned in from a device, such as a PLC. This would determine the minimum
size system. However, once you realise the power of the internal Agents within Adroit Ignite
HMI you will soon realise just how easy it is to build a solution using these instead of potentially
coding in the PLC or in the SCADA.
• The protocol drivers required for the existing and new hardware.
_________________________________________________________________________________________________________________________
• The number of concurrent connections the system will have - Operators and or 3rd party
applications.
• The no. of Performance Anywhere clients
• The no. of Adroit Air mobile app connections required.
Once all criteria have been taken into account, all the standard tools and features of Adroit Ignite HMI
can be used to build the solution.
3.2. Visualisation and Control Strategy

Much has been learned over the years regarding good and bad HMI design practises. Having learned
through trial and error, the good is retained and the bad disregarded. Below are three primary principles
which need to be implemented for an efficient HMI design.
3.2.1. Three Primary Principles

Clarity
• Graphics are easy to read and intuitively understandable.
• Graphics show the process state and conditions clearly.
• Graphic elements used to manipulate the process are clearly distinguishable and consistently
implemented.
• Graphics do not contain unnecessary details and clutter
• Graphics convey relevant information, not just data.
• Information has prominence based upon relative importance.
• Alarms and indications of abnormal situations are clear, prominent, and consistently
distinguishable.
Consistency
• Graphics functions are standardised, intuitive, straightforward and involve minimum
keystrokes or pointer manipulations.
• The HMI is set up for navigation in a logical, hierarchical and performance-oriented manner.
Feedback
• Graphic elements and objects (wizards/controls) must behave and function consistently in all
graphics and all situations.
• Important actions with significant consequences will have confirmation mechanisms to avoid
inadvertent activation.
• Design principles will be used to minimize user fatigue, since operations personnel use the
graphics constantly.
3.2.2. Graphic Hierarchy

High performance graphics are designed in a hierarchy for progressive disclosure of further details.
• Level 1 – Process Area Overview.
• Level 2 – Process Unit control.
• Level 3 – Process Unit Detail.
• Level 4 – Process Unit Support and Diagnostic Displays
3.2.3. Control Plan

Understand the control philosophy to be used in the plant:
• Formulate SCADA requirements
• The User Requirements Specification (URS)
• The Functional Design Specification (FDS)
• PLC Function blocks and / or wizards
• Graphic Form Layout and Design
• Landing and Navigation Graphic Form
_________________________________________________________________________________________________________________________
3.2.4. HMI Standards
Colour conventions for:
• Red = Off
• Green = On
• Flash yellow and current state colour = Fault
• Naming conventions
• Numbering conventions
3.2.5. HMI/PLC Interface
• Create I/O schedule for the plant (Physical Agents)
• Create virtual I/O for plant (Virtual Agents)
• Display I/O
• Stop signals
• Start signals
• Fault signals
• Control signals
Project Information PLC Address
Plant Items Description Agent name Slot name Agent Type PLC Output PLC Input
Motor Physical tag RUNSTOP1 rawValue Digital
Motor Physical tag FAULT1 rawValue Digital
Motor Virtual tag MOTOR_RUNTIME1 onTotalTime Counter
Motor Virtual tag MOTOR_RUNTIME1 offTotalTime Counter
Motor Physical tag SPEED1 rawValue Analog
Motor Virtual tag SPEED_STATS1 average Statistical
Motor Virtual tag MOTOR_CUTOUT1 value Expression
Mimic Control Virtual tag LIST value StringList

Security Virtual tag OPERATOR_SEC_GP value Text
Security Virtual tag ENGINEER__SEC_GP value Text
Security Virtual tag CONFIG_SEC_GP value Text
Clock Physical tag TRIGGER rawValue Boolean

An example of Plant/Project information
3.2.6. Reporting Strategy

The reporting strategy and requirements must be clearly defined before any detailed reports are created.
All data required for reports should be stored in SQL. It is recommended that the following be created
using Microsoft SQL Express.
Datalogging
• Use value deadbands to avoid small analog fluctuations from being logged where necessary.
• All Adroit log files must be stored in their own specific User defined areas and uniquely named
files. It is preferable to create many small log files.
• Dead banding should only be implemented after a project is complete to optimize processes.
• Set the logging standards and strategy, e.g. logging frequency, log period, log files, SQL
logging, DBLog, DBQuery Agent, etc.
• During design phase it must be decided how much data to log and view on a trend.
_________________________________________________________________________________________________________________________
Trending/Charts
The Adroit Ignite HMI data logging sub-system is used to store\log historical data for trending purpose.
The data log should be configured as follows.
• LineChart
• Template trends
• All BULK flows shall be stored for 60 days at a frequency of 15 minutes.
• All SMALL flows (wasting, de-sludging) shall be stored for 1 week at a frequency of 1 minute.
• All DOSING flows shall be stored for 1 week at a frequency of 5 minutes.
• All PROCESS variables (pH’s etc) shall be stored for 1 week at a frequency of 1 minute.
• All BULK levels (big dams) shall be stored for 60 days at a frequency of 15 minutes.
• All TANK levels shall be stored for 1 week at a frequency of 1 minute.
• All motor running digitals must be logged on exception (every stop/start) and stored for 30
days.
3.2.7. Alarming Strategy

When planning the alarming requirements, the following points could be considered:
• Events and Alarms (Incidents/Events)
• Alarm Management
• Acknowledgement rules
• Audio-visual techniques
• Notification
Alarming Standards
The solution is to be configured in accordance with best practices. In principle, it has to be identified as
what constitutes an alarm and what constitutes an event and the two kept separate. Applying the
definition that an “Alarm is an event that requires an operator to acknowledge and take some action”,
thereby not cluttering up the alarm viewers with unnecessary data.
To start it is recommended that all the defined alarms be broken into three categories.. Each category
can be assigned an Alarm route in the Alarm Agent and an outcome using the associated Agents.
For example:
Events
o Global Alarm list
Non-Critical Alarms
o Global Alarm list
o Non-critical Alarm list - These alarms require the Operator to acknowledge them.
Critical Alarms
o Global Alarm list
o Non-critical Alarm list - These alarms require the Operator to acknowledge them.
SMS
o Sends the alarm to a predefined cell number.
3.2.8. Security Strategy
The security system is user-centric and operates on top of the traditional Windows operating system
security. This uses a configurable sub-set of the existing users and groups that are "allowed" on each
Adroit Ignite HMI computer.
All security users and groups would be configured in Windows / on the domain (outside of our software)
and then groups and / or users would be allowed access to the Adroit Ignite Server and then to certain
Data Elements (normal security config applies in the Designer).
_________________________________________________________________________________________________________________________
4. Main Components and Architecture
4.1. Data Layer
Adroit Ignite HMI offers users the unique ability to securely integrate both real-time and transactional
data into a rich and functional user interface. This is done through creating connections from the
Ignite Server into the various Datasources that make up the data layer.
Sources of data can include:
• Agent Server (I/O Server)
• OLE DB Databases (external to Adroit Ignite HMI)
• Web Services
• Adroit Air (configuration tool)
A more detailed description of each Datasource is described later however to summarise:

In Adroit, the I/O server part of this architecture is called an Agent Server. This contains a collection of
intelligent objects known as Agents. Agents are intelligent objects because, in addition to containing
"state" information, as do conventional database records, they also embody "behaviour".
A more detailed examination of the implications and meaning of this is presented under the sub-heading
Agents later in this document.
4.1.1. Agent Server

An Agent Server is the repository of Agents and Tags. It is a data store and has attached DLLs, which
contain information concerning the identity and characteristics pertaining to Agents.
Figure 2 Agents Server
The Agent Server is the equivalent of an I/O Server in some other SCADA systems and performs the
real-time data acquisition, storage and alarming of all data from devices in the field. The data stored
within the Agent Server is said to be historical data.
The Agent Server is a separate program within the package and must run for Adroit Ignite HMI to be
able to control a plant or whatever it is configured to do.
When the Agent Server application is run its Window shows the various Agents being loaded, debugged,
along with other information such as Drivers, WGP details etc.
_________________________________________________________________________________________________________________________
Figure 3 Agents Sever Window
The Agent Server is responsible for scanning data, pre-processing, logging and alarming and interacting
with external systems such as databases and third-party applications wishing to use the data available
from the plant.
4.2. The Ignite Server

The Ignite Server is responsible for managing access to the data layer, graphic forms, and management
and storage of user profiles governing security access rights and many other default operator settings
etc.
The Ignite Server is the middle-layer that brings all the available datasources into a unified data model
for use within a project. It is a data portal which exposes data from a number of disparate datasources,
both external and internal to it. The data sources included as standard are one Agent Server data source,
multiple databases, web services multiple Windows event sources.
In the Ignite Server you can add different datasources, configure profiles, security and create, edit and
delete graphic projects.
4.3. Presentation Layer

4.3.1. The Designer
This application is the entry point into building any Adroit Ignite HMI solution. A secure log-on and rights
applied allows users to manage what capability and user or group of users has on the system. In addition,
the Designer is the engineering environment in which users create access to data, manage users and
groups and build graphic forms to be displayed in the Operator.
The graphical plant display windows within the Operator are themselves composed from objects, in this
case display objects known as picture elements. In addition to state information, such as size, location,
colour, etc., display objects may also be configured to have a wide variety of animation behaviours. By
connecting presentation layer animation behaviours to plant values represented by Agents within Agent
Servers, many different animated display effects can be configured that, in real-time and to visualise
your plant in exactly the way that you require.
_________________________________________________________________________________________________________________________
Figure 4 Designer
4.3.2. The Operator

The Operator is Internet-enabled and built on top of the Microsoft .Net framework allowing for greater
flexibility and more custom programming functionality, but with no compromise to security.
Figure 5 Operator - Display example
_________________________________________________________________________________________________________________________
4.4. Help and ReadMe Files
A hypertext online context sensitive help system - ReadMe files contain the latest information regarding
small improvements and updates, which will not be found in the Help file. It contains the Supplementary
Release Notes for Adroit, which includes installation and upgrading information and any known issues
concerning the operation of the product.
In and around Adroit Ignite HMI Windows there will be Help buttons (question marks) and/or Help About
on the Menu bar, or a Help button.
For example:
Figure 6 Adroit Help
_________________________________________________________________________________________________________________________
5. Installing Adroit Ignite HMI
5.1. Hardware & Software Requirements
5.1.1. Recommended Hardware & Software
Please refer to the Hardware & Software Specification document available from our website. Here
5.1.2. Additional Software

Additional software that will expand the functionality of Adroit Ignite HMI:
• Internet information services (IIS): Required for web service and distribution service
• SQL with advanced reporting services: used for historical data logging and reporting. Adroit
Ignite HMI ships with the free SQL Express that can be used for these purposes.
5.2. Licensing
The Adroit Ignite HMI software is, by default licensed using our soft licensing mechanism. This means
it has to be licensed finally on the machine you intend to ship your solution on. Should There is no way
of transferring these licenses between machines and each final project will need a new license to be
purchased
In situations where you would want a transferrable physical HASP USB security dongle this is available
on request and there is a cost of around US$50 (excluding transport) per HASP license or license
change.
For further details, contact your Adroit Ignite HMI representative.
5.2.1. Licensing definitions

• Agents: When an Agent is used it consumes a license.
• Clients: typically Operators and/or Designers
• Mobile/Web Clients: typically Performance Anywhere or Adroit Air clients.
• OEM: Additional components that are separately licensed are specified as separate textual
entries in the product license e.g. Allan Bradley, Siemens Ethernet driver.
5.3. Pre-requisites for installing Adroit Ignite HMI software

Ensure that the Windows operating system on which you intend to install Adroit Ignite HMI has been
and remains legally licensed and ACTIVATED, since Adroit Ignite HMI is not supported when it is run on
an unlicensed Windows operating system.
Ensure that you are not using the built-in Administrator account to run Adroit Ignite HMI, since UAC is
automatically disabled whenever this built-in Administrator account is used.
When installing and running Adroit Ignite HMI on an operating system that provides User Account Control
(UAC), please ensure that UAC is always ENABLED, since Adroit Ignite HMI is not supported when it is
run with UAC disabled.
Adroit Ignite HMI requires the Microsoft .NET Framework 4.8
The Web Service component can ONLY be installed on a computer that has IIS (Internet Information
Services) installed.
_________________________________________________________________________________________________________________________
Exercise 1 - Installation of the Adroit Ignite HMI software
Install the latest build of Adroit Ignite HMI onto a workstation.

Objective:
User with administrator rights to a workstation.

Prerequisites: Windows OS preconfigured to accept Adroit Ignite HMI.
1. Run the Adroit Ignite HMI executable and follow the installation instructions.
NOTE: The release notes contain all the information regarding the new version of Adroit Ignite HMI. It is recommended that
the user familiarize themselves with this document, then click the next button.
Note: Requires Administrator User name and Password.
_________________________________________________________________________________________________________________________
Figure 7 Installation Process
2. The following icons will be created and placed on the desktop.
Notes:
_________________________________________________________________________________________________________________________
5.4. License Installation
On the completion of your purchase of the Adroit Ignite HMI, you will receive a Temporary License valid
for 30 days. This Temporary License can be used on as many machines as the purchaser would like and
will include all the features as per the order placed.
Once the payment has cleared, the purchaser will receive a notification via email with instructions on
how to obtain this Permanent License.
This permanent licence will then be generated in the form of a .V2C file. The purchaser will then apply
this .V2C using the Ignite Utilities (Adroit Licensing Utility) on the machine intended for use in the final
application.
NB This final license is NOT transferrable.
Notes:
_________________________________________________________________________________________________________________________
Exercise 2 - Installation of the Adroit Ignite HMI License
Install the Adroit Ignite HMI License onto a workstation.

Objective:

1. Click on the Ignite Utilities icon.
Figure 8 Adroit Ignite HMI Utilities
2. Open the Adtech Licensing Utility, and under the Additional Options tab, click on “Apply V2C”
Figure 9 Adtech Licensing Utility (ALU)
_________________________________________________________________________________________________________________________
Figure 10 ALU : License Details
Notes:
_________________________________________________________________________________________________________________________
Exercise 3 – Starting the Adroit Ignite HMI
Launching the Adroit Ignite HMI.

Objective:

Adroit Ignite HMI is a Client/Server application and as such in a distributed architecture. In smaller
stand-alone applications the Agent Server, Ignite Server, Designer and Operator would reside on a
single PC. For this reason you need to start the Agent Server and the Client Applications
(Designer/Operator) separately. The Ignite Server will start automatically when you start the Agent
Server application
On the desktop start the Adroit Ignite HMI Agent Server.
The Adroit Ignite HMI Agent Server (AS) will load. Check that the server loads without any
errors and that the AS displays a LOAD complete.
Figure 11 Adroit Ignite HMI Agent Server
Once the Agent Server has finished loading the Ignite Server will start automatically.
_________________________________________________________________________________________________________________________
Check to make sure that the Ignite Server shows it is Running. This can be done by launching
the Ignite Server application icon on the desktop or the icon located in the tray.
In normal conditions you don’t need to do this but for starters it’s worthwhile understanding
each component within the system.
Figure 12 Ignite Server
It is also possible to open the Batching Simulation OPC Server by browsing to:
C:\Program Files (x86)\Adroit Technologies\Adroit
and launch the Batchopc.exe file and get a feel of how the simulation process will run.
Notes:
_________________________________________________________________________________________________________________________
6. Training Course
Using all the basic functions of Adroit Ignite to build an HMI.
The Adroit Ignite HMI Configuration Course has been designed around a specific graphic forms used in
building an interface for a simple Batching Plant. It demonstrates many of Adroit Ignite HMI’s functions
and capabilities.
Delegates will be expected to design a graphic form/mimic of the plant while being exposed to the various
aspects/ concepts including Agents, Behaviours and Properties of Adroit Ignite HMI. During the course,
the delegate will be guided through developing the Batching Plant, as and when the various Adroit Ignite
HMI concepts arise, they will be discussed in depth and examined in detail. The typical SCADA functions:
Scanning, Alarming, Logging and Trending will be addressed in this course.
In a real-world scenario, interfacing the Adroit Ignite HMI SCADA onto some real-world hardware device
such as a Programmable Logic Controller (PLC) or a Remote Terminal Unit (RTU) is done through the
(Input/Output) I/O schedule, which maps the addresses in the PLC to Agents/Tags in Adroit Ignite HMI.
The I/O schedule must cover which addresses are Agents needing to be just read into the SCADA, which
Agents need to be written out to the PLC/RTU, which ones need to be logged and which ones alarmed.
An understanding of the project is essential. Find the attached Plant I/O schedule and become familiar
with the document.
6.1.1. Objective of the Training Course

Design, develop and implement an Adroit Ignite HMI Project that represents, monitors and allows for the
control of a Batching Plant.
As with any real-world solution provision must be made for:
Connecting to the Batching Simulation OPC Server.

Ingredient A, Ingredient B and Water are to be mixed in any ratio;
The mixture must be heated to any temperature between 0oC and 45oC;
The state of the plant should be visually displayed at all times as well as all alarms and events
together with the amounts of all ingredients used;
The total time that the plant is running and stopped to be displayed;
The operator must be able to Acknowledge/Reset alarms;
Manually input data to change the quantities of water & ingredients to be added.
_________________________________________________________________________________________________________________________
6.1.2. Overview Drawing
A piping and instrumentation diagram (P&ID) is a detailed diagram in the process industry which shows
the piping and vessels in the process flow, together with the instrumentation and control devices.
Figure 13 Batching Plant Overview Drawing
_________________________________________________________________________________________________________________________
6.2. Batching Simulation OPC Server
Familiarising yourself with the workings of the Batching Plant.
To do this, browse to the Batching OPC Server executable which resides in C:\Program Files
(x86)\Adroit Technologies\Adroit folder and is called:
Start this application and the user interface will appear. You can play around with various setpoints, stop
and start the Batch Simulation OPC Server to become familiar with it as it is effectively the PLC side of
the training project.
Figure 14 Batching Simulation OPC Server
The Batching Simulation OPC Server is a built-in fixed simulator to which you can connect your Adroit
Ignite HMI project. It consists of 3 simulations namely Batching, Conveyors and Turbine. Our Training
Course is built around the Batching simulation.
The Batching simulation has an Auto and a Manual operation.

In Manual, you are only able to stop and start the Agitator and Pump. (Select Manual Mode and start/stop
the devices via the blue text selections. It will turn green when active.
_________________________________________________________________________________________________________________________
Figure 15 Manual Mode
For Automatic mode, select the no. of batches required, select Auto Mode and then Auto Start. The
Batching program will proceed as per the sequence on the left hand side of the Batching screen, as well
as according to the values pre-set for each of the ingredients, mixing time, heating time and discharge
time. All of these are adjustable by selecting the appropriate value (blue text) and setting a new value
as shown below.
Figure 16 Changing Setpoints in Batching Simulator OPC Server
Alarms are randomly generated and can either be reset manually via the pushbutton or automatically
when selecting the Auto alarm reset checkbox.
As part of this course, various exercises will teach you how to set these values from controls within
your project.
Browse the Batching Simulation OPC Server for 2 other simulation packages, Conveyors and Turbine.
These can also be used by yourself to create additional training sessions.
Notes:
_________________________________________________________________________________________________________________________
7. Adroit Ignite Config Editor
The Config Editor is used to configure default settings for the Agent Server, Designer and Operator.
Preferences may vary from project to project depending on a project’s architecture. Normally on a stand-
alone or simple distributed system, the user would not have to edit this configuration.
Figure 17 Config Editor
_________________________________________________________________________________________________________________________
Exercise 4 - Creating a New Configuration
Configure an Adroit Ignite HMI Database.

Objective: Project Structure.
Configuration files that conforms to the specifications given
above.
The latest build of Adroit Ignite HMI.
Prerequisites:
Run the Configurator program – Ignite HMI Config Editor
Select Configuration in the tree view on the left-hand side.

Check on the ‘Allow Multiple Configurations’
Select the Add New Configuration button.
Type Juice into the textbox.

Click OK.
Figure 18 Config Editor - Configurations
The project files have been created in the following paths:

a. Adroit
C:\ProgramData\Adroit Technologies\Adroit\Configurations\JUICE
b. SmartUI
C:\ProgramData\Adroit Technologies\Adroit\SmartUI\Configurations\JUICE
From the ‘Welcome’ menu, browse to the Agent Server Configuration
Set the Server Project Name to Juice.
_________________________________________________________________________________________________________________________
Figure 19 Config Editor - Advanced Agent Configuration
Notes:
_________________________________________________________________________________________________________________________
Exercise 5 - Driver Configuration
How to connect to the Batching Simulation OPC Server.

Objective:

Prerequisites:
1. Run the Configurator program – Ignite HMI Config Editor
2. Browse to, Welcome in the tree view on the left-hand side.

3. From the Agent Server Configuration Menu, select the Driver Configuration.
4. Select OPC Client Protocol Driver and click the Add button.
5. Name the new Device BATCH and click OK button.
6. Select “Adroit Batch OPC Server” from the OPC Server pulldown list.
7. Click OK.
8. Click Finish.
Figure 20 Config Editor - Driver Configuration
_________________________________________________________________________________________________________________________
Exercise 6 - Launching the Designer
Connect to the Designer.

Objective:

Prerequisites:
1. Start the Agent Server from the Ignite Agent Server Icon.
2. Ensure the Ignite Server is running by checking the Windows taskbar.

3. Run the Designer.
4. Log on to the Designer as the Administrator.

5. Enter the correct credentials for the Administrator account
NOTE: The default user will be the Windows user profile (and Administrators group) that was logged on when Adroit Ignite
HMI was installed
Figure 21 Adroit Designer User Login Screen
6. Check the Automatic Login feature.

7. Click Finish.
Notes:
_________________________________________________________________________________________________________________________
8. The Designer
Figure 22 Designer Welcome Screen
The Designer Application allows a user to manage Datasource connections, create and design graphic
forms, customize the work environment and manage both user and data security at the same time. The
work environment of the Designer consists of two types of windows:
• The Design workspace and,
• Tool Windows/Views – Dockable windows.
The Design workspace is the main work area, which is always opened in the centre of the Designer
application window. This is used to display all the graphic forms, which are currently open in the
Designer.
Multiple graphic forms can be opened simultaneously but only one graphic form in focus at any one time.
Graphic forms can be run within this environment to allow for testing during configuration. Each graphic
form that is opened is identified by means of a tab, which is displayed at the top of this window to easily
select the required graphic form. If one or more graphic forms are already opened, then this tab is added
to the right of any existing tabs.
_________________________________________________________________________________________________________________________
8.1. The Agent Configurator
The Agent Configurator is the engineering interface to Agent Server and has functions to find, add, edit,
remove and otherwise configure Agents belonging to an Agent Server running either locally or on a
remote machine somewhere on the network. Suitably authorized users therefore have access to all
Agents in an Agent Server on the network, meaning that separate engineering stations are not required.
Figure 23 Launching the Agent Configurator
The Agent Configurator top-level dialog is shown below. It is from this dialog that users are led in a
structured way to select the next aspect of configuration (scanning, logging, alarming, etc.).
Figure 24 Agent Configurator
The Agent Configurator provides access to the Agent Server or Tag database. It provides the user with
an Agent editing and configuration tool.
_________________________________________________________________________________________________________________________
8.2. Default Tool & View Windows
Tool windows are dockable windows that can be arranged to increase the viewing and editing space
provided by the design workspace. The following is a list of all the tool windows that are provided, by
default, within the Designer application workspace.
Enterprise Manager
This window provides the means for viewing and working with projects and
Datasources and Servers. This “explorer” view has been designed to emulate
the windows explorer environment as much as possible for ease of use.
This window displays an expandable/collapsible hierarchy of connections to

one or more Servers, and the Datasources and projects that have been added.
A right-click on any item in the Enterprise Manager, a menu will open with
the available options, if any, for working with that item.
Figure 25 Enterprise Manager
_________________________________________________________________________________________________________________________
Toolbox
This tool window contains the available forms components/.net controls which
can be added to graphic forms when they are being configured or designed.
This tool window displays a number of categories:

• Windows Forms: standard .NET and components
• Data: chart and other data viewing controls,
• SCADA Controls: alarm and event viewing controls,
• Gauges: Various Gauges created using Spiders and Script,
• Vectors: vector-based graphic controls. Vector graphics are geometrical
primitives such as points, lines, curves, and shapes or polygon(s)
• Templates: Graphic default templates
• Graphic Form Tools: Pointer and Custom Title Bar
• Adroit: Alarm and Event Viewers
By double clicking the required control or component, it is added to the graphic

form.
Figure 26 Toolbox
Properties
This tool window can be used to view and, if necessary, manually
configure the properties and events exposed by the graphic form and/or
its form component(s) that is currently in focus.
Figure 27 Properties
_________________________________________________________________________________________________________________________
Other Designer Windows
These Windows are useful Windows but probably wont be used in your basic HMI projects. To turn and
manage the view of these windows use the “View” tab in the Designer (dealt with a little later).
Output Events
This tool window is a log window for Client based low-priority events, such as Spiders execution failing,
connection event outputs, etc.
Figure 28 Output Events
Progress Window
This tool window displays the progress of any Client-Server communication. This can be used to
determine if a (lengthy) process has completed, which is especially useful when the Client has connected
to the Server over the Internet. New operations are added to the top of the list. The progress of each
operation is indicated by means of a progress bar per item. To the right of this progress bar, the name
of the current sub-task is displayed as it is being performed, which is replaced with the total time taken,
in milliseconds, once this operation has completed.
Figure 29 Progress Window
Watches Window
This tool window makes it possible to quickly view (and if possible modify), the real-time value of Data
Elements in the Designer which can otherwise only be viewed when graphic forms are run in the Design
workspace.
Figure 30 Watches Window
_________________________________________________________________________________________________________________________
Levels and Layers Window
This tool window contains the levels and layers configured for the graphic form that is currently opened.
Levels and layers are used to display or hide controls and/or graphic elements in order to create overlays
or masking effects.
Figure 31 Levels and Layers
Translation Window
This translation table performs the actual translating of text values of graphic form components. This
graphic form translation table consists of a row for each property that contains a string values and a
column for each configured language for runtime multi language applications. These languages are
related to user profile language settings.
Figure 32 Translation
Note: Always refer to when additional information is required.
_________________________________________________________________________________________________________________________
8.3. The Home Menu:
Figure 33 Home Menu
Connection Description
Connect This will connect the Designer from the Ignite Server.
Disconnect This will disconnect the Designer from the Ignite Server.
Refresh This refreshes the server view in the Enterprise Manager.
Save Server Data All data in the Server will be saved.
Clipboard Description
Paste When in design mode on the graphic form you can paste copied objects.
Copy Copy any object on your graphic form.
Cut Cut objects on your graphic form that you would like to paste
Project Description
New Folder This creates a new folder in your project.
New Graphic Form This button creates a graphic form in the selected project or folder.
New Graphic Form (Styled) This button creates a graphic form in the selected project or folder.
New Project Creates a new project from this button.
New Wizard In order to create a wizard object, it needs to be created on a wizard page.
Delete Deletes the selected graphic form, wizard, folder or project.
Find To find where a tag (agent name) has been referenced and used throughout
a project.
Graphic Form Description

Save Save the graphic form.
Save As Save the graphic form with another name.
Save All Save all graphic forms as is.
Close Graphic Form Close the current graphic form
Close All Graphic Forms Close all graphic forms that are currently open.
Agent Server Description

Open Configurator This button will open the Configurator where users can create, log, alarm and
scan the Agents within the Agent Server.
_________________________________________________________________________________________________________________________
8.4. The View Menu:
Figure 34 View Menu
Menu Section Description

Reset Window Layout This resets your windows layout only.
Reset to Default Layout This button will reset your design workspace to the default layout settings.
Spider Configuration Mode = Beginner

Content Section Description
This button will hide or show the translation properties window at the bottom
Translation
of the screen
Watches This will hide or show the Watches window at the bottom of the screen.
Progress This will hide or show the Progress window at the bottom of the screen.
Launch Script Editor
Levels and Layers This will hide or show the levels and layers window at the bottom of the screen.
Output Events
The button will hide or show the contents window on the right side of the
Contents
screen.
Enterprise Manager This will hide or show the Enterprise Manager.
Favourites
Properties This will hide or show the properties window on the right of the screen.
Toolbox This will hide or show the toolbox window on the left of the screen.
Context View
Spider Configuration Mode = Intermediate

Translation
of the screen
Levels and Layers This will hide/ show the levels and layers window at the bottom of the screen.
Output Events
Contents This will hide/show the contents window on the right of the screen
Favourites
can be accessed but is not displayed by default and any spider regions
Spider Configuration
associated with configured Behaviours cannot be accessed
Context View
_________________________________________________________________________________________________________________________
Spider Configuration Mode = Advanced
Translation
of the screen
Levels and Layers This will hide or show the levels and layers window at the bottom of the screen.
Output Events
The button will hide or show the contents window on the right side of the
Contents
screen.
Favourites
Spider Configuration grants full access to the Spider Configuration window and opens this window.
Context View
Spider Configuration
Description
Mode Section
Beginner
Intermediate
Advanced
_________________________________________________________________________________________________________________________
8.5. The SCADA Menu:
Figure 35 SCADA Menu
Pointer Mouse pointer
Vectors
Button Add Button
Check Box Add Check Box
DropDown Add Drop Down
Ellipse Add Ellipse
Line Add Line
Picture Add Picture
Pipe Add Pipe
Polyline Add Polyline
Rectangle Add Rectangle
Scale Add Scale
Slider Add Slider
Spline Add Spline
Text Add Text
Adroit
AlarmViewer Add AlarmViewer
EventViewer Add EventViewer
HistoricalAlarmViewer Add HistoricalAlarmViewer
Data
BarChart Add BarChart
ColumnChart Add ColumnChart
LineChart Add LineChart
PieChart Add PieChart
VIZNETDataBinder Add VIZNETDataBinder
XYPlotChart Add XYPlotChart
_________________________________________________________________________________________________________________________
8.6. The Configuration Menu:
Figure 36 Configuration Menu
Adroit Ignite HMI

The fundamental Agent Server settings and can install or configure the
Agent Server Configuration
Agent Server service
Driver Configuration manage the Adroit protocol drivers and their devices.
Setting up the Server Opens Config Editor to allow setup for the Ignite Server
Setting up the Designer Opens Config Editor to allow setup for the Designer
Setting up the Operator Opens Config Editor to allow setup for the Operator
Open Projects Folder Opens Windows Explorer in the Projects directory
System Backup and Restore

Backup Opens Config Editor to allow setup for the system backup function
Restore Opens Config Editor to allow setup for the system restore function
_________________________________________________________________________________________________________________________
8.7. The Diagnostics & Tools Menu:
Figure 37 Diagnostics & Tools Menu
Monitoring
This utility allows users to monitor the operation of their installed protocol
Driver Monitor
drivers and provides many diagnostic capabilities.
This utility is designed to assist experienced users in fine-tuning the scanning
Scanning Monitor subsystem to achieve optimal performance, by providing an intuitive report-
like view of advanced diagnostic information
This utility allows you to display all the items within an OPC Server and if
OPC Browser necessary, you can browse for and select the required address of particular
OPC items.
This utility is typically provided for advanced users for diagnosing or
Agent Server Monitor
troubleshooting the Agent Server.
Diagnostics
This utility inspects the structure of your existing Agent database (.WGP)
WGP Inspector
files.
License Utility
Adroit is licensed via the Agent Server and this licensing typically occurs via a
License Utility HASP software protection key, which is programmed in accordance with the
required license.
Other
This utility allows you to run commands and utilities run today, tomorrow, or
Scheduler
on a particular day of the week or month at a specific time.
_________________________________________________________________________________________________________________________
8.8. The Project Menu:
Figure 38 Project Menu
Adroit Classic
Import Mimic This will import any Classic UI mimic onto the graphic form.
Import Trend This will import any Classic UI trend onto the graphic form.
XAML Graphics
Import XAML This allows you to import any graphics that is in XAML format.
Project Style
When creating a project, you can choose to associate either a predefined or
custom style to the project, which creates a hidden graphic form, called
Style
!Style, which configures the following common graphic form display
properties to save you design time and ensure a consistent look and feel.
This allows you to set the physical dimensions, specified in pixels: either
Size select a Predefined width and height, which specify common monitor
resolutions or specify your own Custom dimensions.
Width This allows you to set the width.
Height This allows you to set the height.
Size This allows you to set the size.
The BackColor of the graphic form.
BackColor Note: Depending on the controls that you add to this graphic form, they may
inherit the specified BackColor.
The default Font of the graphic form and any controls that you add to this
Font
graphic form.
ForeColor The Fore Color of the graphic form.
Font Size The Font Size of the graphic form.
After editing this project style graphic form, click the Save Project Style item
Save Project Style to save these project style changes.
Note: You can only edit the style of a single project at a time.
Open Project Style opens the project style graphic form (!Style), so that you
can add form components to this project style graphic form, such as a banner
Open Project Style
(header) or footer or logo or any other element or graphic that all your styled
graphic forms have in common and/or configure their default properties.
_________________________________________________________________________________________________________________________
8.9. The Design Menu:
Figure 39 Design Menu
Vectors
Create Vector Group This creates a group of objects into one group.
Break Vector Group Press this button to break the one group into separate objects.
Reset Centre This will reset the centre of the object.
Rotate This rotates the object.
Rotate This rotates the object by the selected degrees.
Workspace
Alignment Use this to align selected items.
Size Use this to size all selected items to the same size.
Spacing Use this to space selected items equally.
Layout Select an item to be in front or at the back of another object.
View Tab Order
Font Specify your font settings here.
Colour Choose a colour to be applied to an object.
Snapping Snap Mode.
Shapes Choose a basic shape.
Specify which users have access to which properties exposed by the

Graphic Form Security
controls that have been added to the graphic form.
_________________________________________________________________________________________________________________________
8.10. The Behaviors Menu:
Figure 40 Behaviors Menu
Display
Display Value This behavior allows you to display values from Agents in the Agent Server.
This behavior can drive a data element (value) to and/or from the value of a
Bind Value
property of a control or vector.
Visibility This is a simple true/false visibility behaviour to show an object.
Tooltip This behaviour brings up a window with info on it for an action.
Define an index list of images and when manipulating the index, the image
Flip Bitmap
assigned to the index number will display.
Database
Transforms
This behaviour allows to dynamically move the object linearly in a defined X-Y
Location
direction by means of monitored value.
Rotation This behaviour dynamically rotates the object by means of a monitored value.
This behaviour dynamically resizes the object linearly by means of a monitored
Size
value.
Colors
This behaviour allows assigning colours to the two states of a digital (Boolean)
Color value; blink a specific colour property or the VISIBILITY property either
continuously or triggered by a value.
Percentage Fill This behaviour dynamically fill the object by means of a monitored value.
Actions
This behaviour typically provides methods that allow end-users to change a
Operator Action
value at runtime.
This behaviour perform commands such as launching an application or
Execute Command opening, closing or printing a graphic form or logging a user on or off and/or
switching users.
Remove This removes selected behaviours on objects.
Edit Behaviour This edits behaviours on objects
_________________________________________________________________________________________________________________________
8.11. Shapes Wizards & Examples Menus
Figure 41 Shapes Wizards & Examples Menu – Electrical Symbols
Figure 42 Shapes Wizards & Examples Menu – Hardware
Figure 43 Shapes Wizards & Examples Menu – Process Symbols
Figure 44 Shapes Wizards & Examples Menu – Situational Awareness Symbols
Figure 45 Shapes Wizards & Examples Menu – Static Graphics Symbols
Figure 46 Shapes Wizards & Examples Menu – Templates
Figure 47 Shapes Wizards & Examples Menu – Wizards
_________________________________________________________________________________________________________________________
8.12. Graphic Form Toolbar
Note: This menu bar is visible once a graphic form has been loaded.
8.12.1. Save Functions
Save Menu
Save Save the current graphic form
Save a duplicate of a graphic form with an alternative name or within another
Save As
folder.
Save as Wizard Convert graphic template/form to wizard format
Publishing will create a run-time version of a graphic for use in the operator
Save and Publish
only.
8.12.2. Substitutions
Substitutions Menu
Substitutions Selection become available during wizard creation
Selection become available when a deployed wizard is selected, allowing the
Substitution Assignment configuration of the assign substitutions
8.12.3. Launch Script Editor
Script Editor
Brings forth the script for the selected graphic form, allowing
editing of the script
8.12.4. Design & Run
Design & Run Menu

Design Allows user to work within the design workspace.
Switches from design mode to run mode, allowing the user to view behaviours
Run
in action and for testing purposes.
_________________________________________________________________________________________________________________________
8.12.5. Zoom
Zoom Menu
Zoom In Zoom into your graphic form, vectors only
Zoom Out Zoom out of the graphic from, vectors only
Zoom Home To view all components
8.12.6. Optimise Graphic Form
Optimise Graphic Form Size Menu

Optimise Graphic Form Optimise graphic form size graphic form toolbar button resizes the graphic
Size form to fit its contents by shrinking or enlarging the graphic form.
8.12.7. Statistics, Optimizations & Find and Replace
Optimise Graphic Form Size Menu

To determine the efficacy of the graphic form optimization process, by
Statistics comparing an optimised graphic form to its original, for instance, to see the
difference in the number of design elements.
Optimizations Launches a configuration dialog that provides a number of search routines you
can choose to use to analyse your graphic form to detect design issues.
Find and Replace Locating all the references of a Tag on a graphic form allowing indirect
mechanisms so that you can change these references to the required
replacement one at a time.
_________________________________________________________________________________________________________________________
9. Agents
9.1. Overview - Agent Groups and Agent Types
Adroit Ignite HMI configurations are made up of one or more collections of intelligent, cooperating
objects known as Agents. An Agent is said to be "intelligent" because, in addition to containing "state"
information as would a conventional database "record" or "structure", it also embodies "action".
Property Naming Convention Description Example
Agent Object type Intelligent Adroit object type Analog, Digital, Counter etc
Tag name.slot Property of an Agent ADT_JU_MX_MIX_TNK_LVL.value
A Data Element is built up using the

name of the datasources. Each
Data source.type.name.slot source of data requires a Adroit.Analog.ADT_JU_MX_MIX_TNK_LVL.value
Element datasource plugin before it can be
associated with the Ignite Server.
Consider for a moment the Analog Agent type. Each Analog Agent contains, amongst other things, the
following data values, also often referred to as attributes, slots, or properties depending on your
preferred terminology.
Here is a dialogue box representing an Analog Agent.

As you can see the name of the Agent is ADT_JU_MX_HTR_TEMP_ACT and the slots are the
attributes of the Agent.
Figure 48 Analog Agent
_________________________________________________________________________________________________________________________
Value Description
rawValue Used to hold the raw or unconditioned value read-in from a front end device
rawMin Device Span minimum value
rawMax Device Span maximum value
engMin Engineering Span, i.e. conditioned or scaled, minimum value
engMax Engineering Span, i.e. conditioned or scaled, maximum value
value Conditioned or scaled value of the Analog
The Agent's "state" at any instant in time, is the collective value of these, and any other attributes.
Because our Agent is of type Analog, it has the inherent knowledge to transform any value coming into
its rawValue slot into a scaled or conditioned value for its value slot, using the rawMin, rawMax, engMin,
and engMax scaling parameters.
An Agent's "state" can therefore be defined as the collective value of all its data attributes at an instant
in time, and its "action" can be defined as the collection of expectations as to how it will respond to
externally generated stimuli, such as, for example, a change to one or more of its data attributes.
Agents have both generic and type-specific action and attributes. Generic action and attributes is
something that all types of Agents possess, whereas type-specific action and attributes, as the name
suggests, is something that pertains only to Agents of the specific type.
Some of the generic actions possessed by all Agent types are, for example, the ability to create, destroy,
save, and load instances. Examples of generic attributes are name, description, status, etc. The above
partial description of an Analog Agent highlights some of the type-specific action and attributes of the
Analog Agent type.
As will be explained in more detail later, Adroit Ignite HMI makes use of different Agent types to
implement a wide variety of system related, as well as application-specific tasks. The benefit of
implementing everything as Agents in Adroit Ignite HMI is that the standard mechanisms developed for
displaying, scanning, logging, alarming, eventing, etc., of process values can also be used to monitor
and control Adroit Ignite HMI itself. This has proved to be of enormous benefit from an adaptability
and flexibility point of view and will continue to pay dividends as Adroit Ignite HMI continues to evolve
in the future.
One of the generic Agent attributes is a 32-bit status word that is used by the Agent to store binary
information about its state. The first 16 bits of this word are common to all Agent types (i.e., Agent
Bad, Log Inhibit, etc.), while the last 16 bits are type-specific, for instance the Analog Agent uses the
first type-specific bit to indicate a Low Alarm condition.
It is also critical to understand that any Tag (Agent+Slot) can be in itself, scanned, alarmed, and logged
which makes Adroit Ignite HMI an incredibly powerful platform for any application. In real life this
means that, by way of example that the Analog Alarm limits could be scanned to PLC addresses without
having to create another Tag as often required in competitive HMI products, saving time and license
costs.
_________________________________________________________________________________________________________________________
9.2. Naming Convention
Each Agent (instance of an Agent type) is referred to by its own unique name therefore Adroit will not
permit an Agent name to be used twice within an Agent Server. Usually this name is defined by the user
when the Agent is created, however, some Agents are created by Adroit itself in which case a name is
usually automatically generated.
In Adroit a Tag means “AgentName.slotName”. It will be seen during the course that any slot of any
Agent can be accessed, its data displayed or edited, provided that the Adroit naming convention is
adhered to.
When naming Agents, Adroit will not accept lower case characters, spaces, $ or % signs, commas,
periods, or backslashes in the name.
Therefore, in order to make the name of an Agent read to make sense, the _ (underscore) is used to
separate words into something readable.
Agent names should be, especially on distributed systems, unique and not longer than 32 characters.
Duplicate Agent names are only permitted in distributed Agent Servers used in Active Clustering (Hot
Standby and Redundancy) configurations.
Example: The status word of a pump controlled from PLCA A on the Bioreactor in Unit 1 may have an
Agent name as follows: BIO1_A_BR_PMP01_STS
9.2.1. Agent
VVV_WWW_XXX_YYY_ZZZ_##
Symbol Description* Abbreviation
VVV Production PRO
WWW PLC-A PLA
XXX Booster Pump BSP
YYY Pump A PPA
ZZZ Trip TRP
## Module number 01
Agent name = PRO_PLA_BSP_PPA_TRP_01
9.2.2. Device
VVV_WWW_##
Symbol Description* Abbreviation
VVV Production PRO
WWW PLC-A PLA
## An incremental number to support multiple devices 00
Device Name = PRO_PLA_00
_________________________________________________________________________________________________________________________
9.2.3. Agent Types Overview
An Agent is the basis and the building block of Adroit residing within the Agent Server. Agents do not
only store data, but also have intelligence in that they know how to manipulate that data. An Agent
therefore contains data and the operations with which to manipulate it.
Primitive:
These Agent types are primitive because they offer limited value and are limited in functionality
when compared to the Basic Agents, they are essentially single value containers.
Boolean, Text.
IMPORTANT: These Agent types CANNOT be alarmed, and their values are not scaled etc, so use the Basic Agent
types instead to represent your process values.
Basic:
These Agent types form the basic building blocks of a system and are used for gathering,
handling and processing data to and from the physical external world.
Analog, Counter, Date, Digital, Expression, String, StringList, Timer.
Advanced:
These Agent types provide powerful SCADA and integration functionality that allow the Basic
Agents to be alarmed and logged to databases and provides various means of reporting and/or
controlling their values.
AgentGroup, Alarm, AlarmList, Command, DBLog, DBQuery, EventLogging,
EventOutput, MultiMedia, Notify, Script, Shift, Statistical Agent.
MIS/MES:
These are very specific and usually quite complex Agent types used to do monitor, control and
solve higher level shop-floor and general industrial challenges.
Accumulator.
IT/IoT:
These Agent types facilitate the integration and management of SCADA and IT.
IoT, Perfmon.
System:
These Agent types are used internally to perform certain SCADA and other specific functions.
Note: Instances of these Agents are created automatically and cannot be added manually by
the user.
Alias, Beeper, DataLog, Device, Hasp, Proxy, Scan, SystemInformation.
_________________________________________________________________________________________________________________________
9.2.4. Slots
All and any data within an Agent is accessible to other Agents in the Agent Server. This data is accessed
in properties of the Agent called Slots. Each slot has a unique name so that when referring to a particular
slot within an Agent, the notation AgentName.slotName is used. This is essentially what many other
SCADA products refer to as Tags.
A slot is that part of the internal structure of an Agent that contains data. It may vary from a bit to a
variable length text.
Figure 49 Slots Explanation and Types
_________________________________________________________________________________________________________________________
9.2.5. Data Elements
The Ignite Server is a "data portal" which integrates data from a number of disparate sources of data
(Datasources). Each source of data requires a datasource plugin before it can be associated with the
Ignite Server. This provides the ability to expose its data as Data Elements to the Server and, if necessary,
provides special functions or methods to further interact with its data.
In the case of an Adroit Datasource,

A Data Element is built up using the name of the Datasources+ Agent+Slot of the Agent.
So in the Adroit world, a conventional “Tag” is an Agent.Slot.
For example to read the value slot of an Analog Agent called ADT_JU_MX_MIX_TNK_LVL, it would be
addressed in the following manner:
Adroit.Analog.ADT_JU_MX_MIX_TNK_LVL.value
where:
Property Description
Adroit the name of the Agent Server Datasource.
Analog the Agent Group that the Agent belongs to.
ADT_JU_MX_MIX_TNK_LVL the Agent Name.
value the Slot of the Agent being displayed/addressed
_________________________________________________________________________________________________________________________
9.2.6. Header Slots
Every Agent has header slots that are split into three sections. All header slots on all Agents are identical
although the meanings of the last 16 bits depend on the type of Agent. The three sections contain data
referring to: the name, description and priority, 16 common status bits and 16 specific status bits
Figure 50 Header Slots
_________________________________________________________________________________________________________________________
9.2.7. Status Bits/Agent Header Slots
This status slots are contained in a 32-bit word containing configuration and run-time status information
about the Agent. Each bit of this 32-bit word is also exposed as a slot, allowing up to 32 status flags to
be accessed at any time. The overall status of an Agent can be determined from its status slot, which is
a header or generic slot and so is common to all Agent types.
Figure 51 Status Bits
_________________________________________________________________________________________________________________________
9.3. Primitive Agent Types
Primitive Agents are used for gathering, handling and processing data to and from the physical external
world, however they offer limited value add and are limited in functionality when compared to even the
Basic Agents.
• The Boolean and Text Agent types make up this group. They are essentially single value
containers and can’t be alarmed, data can be scanned in from or out to external devices.
9.3.1. Boolean Agent

A Boolean Agent will hold a Boolean value (0 or 1)
9.3.2. Text Agent

One of the simplest types of Agent is the Text Agent, which stores a 79-character text string that can be
defined at start-up, and then updated on request. A text string may also be specified as a cold start
value.
_________________________________________________________________________________________________________________________
9.4. Basic Agent Types
Basic Agents are used for gathering, handling and processing data to and from the physical external
world. Together these form the basic building blocks of a system. For instance:
• the Analog and Digital Agent types perform some conditioning or conversion process on
data normally scanned in from or out to external devices.
• The Counter Agent type performs the counting and averaging of discrete values.
• The String, StringList Agent type provides a means of indexing text.
• The Expression and Timer Agent types order and transform information for calculation and
control purposes.
• The Date Agent type holds time and date information broken down into the year, month,
day, hour, minute, second and millisecond constituents.
The most useful Basic Agents are described below and are listed in Alphabetical order.
9.4.1. Analog Agent
An Analog Agent stores a floating-point

value that has been scaled according to
user defined scaling parameters. This
scaled value is checked by the Agent
against the low-low, low, high, high-high
and rate-of-change alarm settings. Any
infringement of the alarm limits causes
the Agent to set the appropriate bits in its
status word.
Square root extraction for the

linearization of flow signals, alarm
deadband settings and cold-start
initialization options are also settable by
the user. Analog Agents provide a change
monitoring feature which if enabled, logs
an event and sets the Changed status bit
when the value slots changes.
Figure 52 Analog Agent
_________________________________________________________________________________________________________________________
9.4.2. Counter Agent
A Counter Agent is a simple counter and average calculator which takes data from any other Agent’s
Boolean (on/off) slots and calculates the time spent on and the time spent off, counts the number of on
and off events, and totalizes the on
and off time. Each of these values can
be individually alarmed (by clicking
the Alarms… button). This allows
you, for example, to generate an
event when a motor has started more
than a required number of times.
This Agent is particularly useful for

monitoring production lines, counts in
a line, asset management. An
example might be a Pump Running
Signal as the digital input to drive the
Agent, a setpoint of the number of run
hours and an Alarm generated once
that setpoint has been reached. All
done within a single intelligent object,
no complex PLC coding to achieve
this.
Figure 53 Counter Agent
9.4.3. Digital Agent
A Digital Agent stores a digital (ON/OFF) value as

well as the text descriptions for each of the two
discrete states. Value inversion, cold-start
initialization, alarm infringement checking and a
pulsed output option are provided.
With the pulsed output option enabled, the Agent

maintains its ON state until a configurable delay has
elapsed. As the pulsed output option is applied to
the scaled value, inverting the value inverts the
effect of the pulsed output. Digital Agents provide a
change monitoring feature which, if enabled, logs an
event and sets the Changed status bit when the
value slots changes.
Figure 54 Digital Agent
_________________________________________________________________________________________________________________________
9.4.4. Expression Agent
The Expression Agent type is an extremely powerful mechanism for implementing user-defined
calculations. These calculations can be used for a number of purposes.
Some of the more obvious uses are:
• For constructing control strategies by combining and connecting expressions into arbitrarily
complex networks, and for scanning out one or more of the resulting values;
• For enabling or
disabling of alarming;
• For enabling logging on
a section of plant when
a process value
exceeds a certain
threshold;
• For creating
sophisticated animation
effects by linking the
output of an expression
to a display object
animation behaviour;
and
• For creating relatively
simple plant
simulations by
connecting a network
of expressions
together.
Figure 55 Typical application where an Expression Agent can be used
Each expression Agent can contain up to 20 input variables, each of which can be sourced from any
other Agent attribute or directly from a front-end device. For complex calculations, expression Agents
can be interconnected with the result of one expression becoming an input to the next.
The expression slot contains the

actual mathematical ex3pression to
be evaluated. To make the
expression readable, any number of
new lines or spaces are permitted.
The expression syntax supported is
that of a full ANSI-C expression (i.e.,
not a partial subset), including sub-
expressions nested to an arbitrary
depth, conditional operators, bit
wise operators, logical operators,
relational operators, unary
operators, etc., as well as a
comprehensive suite of
mathematical functions.
The use of variable input names V1,

V2, etc., are used in the expression
Figure 56 Expression Agent so that it is generic. For example,
_________________________________________________________________________________________________________________________
by associating different Agent.slot combinations with the input variable definitions, an expression Agent
can be reused in many different contexts without changing the actual expression. An expression can be
configured to evaluate either continuously, or on receipt of a trigger pulse (the default). By connecting
an expression's trigger input to another Agent slot that changes periodically it is possible to cause periodic
evaluation of the expression.
Alternatively, the trigger can be connected to some other input, possibly common to a number of other
expressions, which may be used to constrain the group of expressions to evaluate, for example, only
when data is valid.
9.4.5. String Agent

The String Agent provides a repository for text. It can hold up to 79 characters.
Figure 57 String Agent
9.4.6. StringList Agent
The StringList Agent can store any number

of character strings of variable length.
These character strings are indexed and
the current string being pointed to by the
index is duplicated in the value field.
Function – Where a number in a PLC

represents a state of a process. The value
of the number in the Agent then presents
the text relating to its index value. In this
example a value of 2 in the PLC would then
display “Starting” on the Operator screen.
This makes this common feature extremely
easy to implement in an Adroit system.
Figure 58 StringList Agent
_________________________________________________________________________________________________________________________
9.4.7. Timer Agent
The Timer Agent is able to perform several
commonly used timing operations, which
previously could only be inefficiently
accomplished by using expressions and scripts.
This Agent also provides a Boolean value slot as
an output, which is enabled (set to TRUE) and
disabled (set to FALSE) by the Agent, depending
upon its current mode of operation. This slot can
therefore be used to enable or disable or
schedule other Agents.
Figure 59 Timer Agent
_________________________________________________________________________________________________________________________
9.5. Advanced Agent Types
These provide the powerful SCADA and integration functionality which allows the basic Agents described
above to be flexibly grouped, scripted and routed to external databases, as well as presenting related
information to the user in event logs, etc. The most important advanced Agents are described below.
• The AgentGroup, Alarm, AlarmList, Command, DBLog, DBQuery, EventLogging,
EventOutput, MultiMedia, Notify, Script, Shift, Statistical Agent types make up this
group
9.5.1. AgentGroup
Agents that are considered to have something in common can be grouped together by means of
AgentGroup Agents. For instance, all Agents of type Analog can be grouped in an Agent group called
ANALOGS, and all Agents belonging to the North Plant of a process plant would be grouped in the
NORTH_PLANT Agent group. AgentGroups can, and usually do, have overlapping memberships.
By collecting Agents together in Agent groups, any changes made to certain AgentGroup status bits will
affect the status bits of all Agents in that group. As an example, consider the situation when part of a
plant (say the North Plant) is shut down for routine maintenance, and it is required to disable scanning
of all Agents belonging to this plant section. By setting the Scan Inhibit bit for the NORTH_PLANT
AgentGroup Agent, the Scan Inhibit bits would be set for all the Agents that belong to the North Plant.
9.5.2. Alarm Agent

In Adroit Ignite HMI, incidents (alarms or events)
are handled by Alarm Agents, which control the
presentation and routing of the alarm events.
Typically, each Agent Server is configured to contain
an alarm Agent that routes the incidents to one or
more alarm lists, output devices, audio devices and
event logs.
The flexibility in configuring alarms allows the user

total freedom in formulating an alarm strategy.
Users may create as many alarm types as needed,
which are the conditions or states of each Agent
that you need to alarm. Any status bit that is set by
an Agent can be used for alarming that Agent. In
this way, the criteria for what constitutes an alarm
condition can be left up to an Agent to decide. This
is why alarming is Agent type-specific.
An incident is associated with a routing path, an

Figure 60 Alarm Agent alarm name and an acknowledgment option.
Each alarm type can report the status of any number of applicable slots. Taking an Analog Agent as an
example, the type High can be configured to report the values contained in the value, high alarm limit
and units’ slots to the alarm list. The entry in the alarm list will then show the occurrence of the alarm
event together with the actual value of the Agent, the engineering units and the associated high alarm
limits.
You can configure alarm types directly from the Alarming dialog and specify the Priority of each incident
(Current alarm type), in addition to assigning an Agent-specific priority. So, in the case of an Analog
Agent the HighHigh incident can have a higher priority than the High incident, etc. Typically, you
_________________________________________________________________________________________________________________________
prioritize your incidents to ensure that your operators ONLY receive IMPORTANT alarms since some
alarms are critical, whereas others are more informational in nature.
You can also configure a Delay (secs) for each incident (Current alarm type). Typically, this is added
to delay an active incident from entering the alarm system to prevent intermittent alarms from flooding
your alarm system or to ensure that this alarm is raised when the operator needs to respond to it.
Do Conditional expression to ensure that each incident is unique and does not duplicate existing
active incidents. In this way you can implement first-up alarming, which disregards the incidents that
echo existing problems, so that your operators can focus on the real issues at hand.
It is also possible to do Alarm shelving, commonly used in areas where maintenance is being carried out
and the user does not want false data making its way into the Alarm Management Reports.
If necessary, you can temporarily suspend the alarming of an incident for a predefined period of time,
using the Inhibited until option.
This option should be used when an alarm indicator may be malfunctioning or may need to be repaired
or replaced or in situations when you need to disable ALL the alarms of a particular item of equipment
and you cannot disable the alarming of an Alarm Agent.
9.5.3. AlarmList Agent
AlarmList Agents are the middle ground between

Operator and server-side alarming capabilities in
that they act as routing destinations for Alarm
Agents and data sources for Alarm List Viewers,
used on graphic forms.
Figure 61 AlarmList Agent
_________________________________________________________________________________________________________________________
9.5.4. Command Agent
Command Agents can both send and
receive SMS messages via a SMS GSM
modem. SMS messages can be sent to a
single recipient either manually or
automatically, e.g., to remotely monitor
the status of important process values.
Sent SMS messages can also be
monitored for auditing purposes and if
they are not received and/or responded
to within a specified period, can also be
sent via another Command Agent to
another recipient.
However, the name of this Agent is

derived from its ability to receive SMS
messages or textual commands from one
or more callers that it can perform to
remotely configure Adroit Ignite HMI, for Figure 62 Command Agent
instance, by acknowledging alarms,
setting process values, etc. In this way it is possible to remotely supervise and, if necessary, control
your process.
Command Agents bypass the scanning subsystem by using a device of this new GSM_SMS driver directly.
This means that instead of being restricted to only 79 characters, the full 160-character SMS message
length can be utilized, both when sending and receiving SMS messages.
9.5.5. DBQuery Agent

The latest enhancement to this technology is the
DBQuery Agent that allows the user to execute queries
on a database that return a single record that would be
available as the .value slot of the Agent.
Where the DBLog Agent is designed to easily perform

INSERT transactions, the DBQuery Agent is designed
to easily perform SELECT transactions on a database -
however the DBQuery Agent can be configured to
perform any SQL Query transaction on a database
using the custom query option.
The Agent can be configured to be run manually,

triggered from a Tag or periodically.
Figure 63 DBQuery Agent
_________________________________________________________________________________________________________________________
9.5.6. DBLog Agent
This Agent is a bulk OLE DB logging Agent for typically logging Analog and/or Digital values to a specific
table in a database for later retrieval. In other words,
instead of logging each Analog and/or Digital value
separately, you can simply specify a list of Tags to log
and either export/import this list from a file or browse
in this list individually in the required DBLog Agent.
This Agent also provides:
• A Logging method list box to select the
required methods for specifying when and
how the listed Tags are logged.
• A String logging checkbox (the BOOLEAN
strLog slot), which when enabled logs the
Tag values as Strings and not numeric values;
this also allows you to log other string slots
(this will log the first 79 characters).
• A Housekeeping section to specify how
long, in days, that you want to store your
logged Tags. This depends upon the storage
capacity you have available for your database
and how useful this data becomes to you the
older it gets.
• A method of dealing with a problematic
connection to the specified database (if the
connection is lost) or when this Agent is
logging a large number of Tags frequently so Figure 64 DBLog Agent
that it becomes overworked.
9.5.7. EventLogging Agent

Adroit Ignite HMI event logging is handled by Eventlogging Agents that use the standard Windows based
Operating System functions for storage but supplement these facilities for retrieval and display. The
number of logged events is limited only by disk space, or the user can limit the number by setting a fixed
length file. With a fixed-length file older events are overwritten. Events can be directed to event log
Agents anywhere on the network.
The scope of these events are extensive, including alarm

events, control events and system events: alarm events
are caused by Agents going into alarm, being
acknowledged and cleared; control events are
generated by any operator control action (e.g., opening
or closing a valve, changing the set point of a process
controller, etc.). The operator logging on or off, a start-
up and shutdown of the control system, printer out of
paper, communication failures or configuration activities
(adding, deleting or modification of Agents), etc., are
examples of system events.
This Agent can log events to an OLE DB compatible

database such as MS Access or MS SQL.
Figure 65 EventLogging Agent
_________________________________________________________________________________________________________________________
9.5.8. EventOutput Agent
The EventOutput Agent directs event log messages to output devices (printers, serial ports and parallel
ports), and to SQL compliant databases.
To cater for the various output devices, EventOutput Agents accept a variety of user configurable general
fields that are used for the layout and format of the data, and the device specific information.
Figure 66 EventOutput Agent
Output of data to the device will depend on the triggering criteria selected: on demand, line at a time
as the event occurs, only after x lines, based on time criteria or as a combination of the above.
9.5.9. MultiMedia Agent

A Multimedia Agent can be used to play .WAV, .MID and .AVI multimedia files to create special audio
and/or video effects on a multimedia workstation.
Figure 67 MultiMedia Agent
_________________________________________________________________________________________________________________________
9.5.10. Notify Agent
The Notify Agent allows alarms to be routed directly to a designated person, using:
• A pager service;
• A mobile phone using the Short Message Service (SMS); and
• An email address.
The alarm message to be transmitted can be configured to include up to 15 fields (Action, Agent, Alarm
Type, Category, Computer, Date, Description,
Event ID, Extra Data, Filter Group, Priority,
Reported Data, Source, Sub-Source and Time), and
custom messages can be sent on demand by the
operator.
The Notify Agent can now transmit alarms by email

to the required recipients by using the Email driver.
This is in addition to transmitting alarms as text

messages via cellular phone Short Message Service
(SMS) or a paging service directly to a designated
person.
The Body and/or Subject line of these automatically
Figure 68 Notify Agent
sent email messages can contain text macros that
are parsed to before the message is sent.
In addition to automatically sending alarms as email messages, the Notify Agent can also be configured
to allow your operators to manually send email messages via an appropriately configured mimic or
graphic form.
9.5.11. Script Agent

Adroit Ignite HMI Script Agent provides a basic scripting language allowing users of Adroit Ignite HMI to
automate complex or repetitive tasks. Two scripting languages are supported – Visual Basic (VBScript)
and Java (Jscript) – both allowing users to define their own subroutines and functions and pass data to
other applications using OLE Automation.
A script may be employed to perform simple

scheduled tasks. The Script Agent can be executed
on demand, by scheduling, triggering and by using
a combination of triggering and scheduling.
A number of functions are supported to allow

interaction with Agents within an Adroit Ignite HMI
system and include but are not limited to GetTag,
SetTag, and TriggerValue allowing complex
calculations to be carried out programmatically.
Figure 69 Script Agent
_________________________________________________________________________________________________________________________
9.5.12. Shift Agent
Various Agents in Adroit Ignite HMI require knowledge of the current shift number. Instead of configuring
the shift pattern information into each
instance of these Agents, you can
instead configure these shift patterns
globally, in a Shift Agent, for use by any
interested Agents.
The value slot of the Shift Agent should

also be scanned and output enabled to
any PLCs that perform any shift-end
functions, such as resetting shift count
accumulators.
Figure 70 Shift Agent
The Shift Agent continually monitors the current time and checks it against the configured shift pattern
to determine the current shift number. If NO matching shift pattern is found, the shift value is set to 0.
9.5.13. Statistical Agent

A statistical Agent provides the basic
functionality for a User to build a
statistical process control strategy using
its built-in data collection method and by
linking the Agent to other Adroit Ignite
HMI Agents.
The method of data sampling offered by

the statistical Agent is called streaming,
whereby all the collected input values are
placed in one sample for analysis.
Each input value may be collected on an

event basis. The statistical Agent
calculates maximum, minimum, average,
standard deviation, total and rate for all
the values collected.
Figure 71 Statustical Agent
_________________________________________________________________________________________________________________________
9.6. MIS/MES Agent Types
These Agents are the building blocks around getting more from your Adroit Ignite HMI system. They are
very specific and usually quite complex Agents used to do monitor, control and solve higher level shop-
floor and general industrial challenges.
9.6.1. Accumulator Agent

An Accumulator Agent gets its name from the type of
process value that it operates upon and NOT from what
it actually does.
Since an Accumulator Agent requires as an input a value

that accumulates over time in other words which simply
gets bigger and bigger, which the Accumulator Agent
uses to calculate the difference in value (or delta)
between successive events or over a specific time period
(interval).
This Agent calculates the total for a period based on a

predefined trigger or time interval. When such an event
occurs:
• the Agent subtracts the previous interval input

value from the current input value to determine
the value differential for the current period, which
represents for example the total production for
the last hour or shift or day etc.
• the Agent calculates the rate of change in value,

which is this differential value for the current
period divided by the interval of this period (value
per hour).
In order to maintain a history of these periodic

counts/totals, you need to connect this Accumulator
Agent to a MS SQL database. Each record specifies the
start and end times of the period and its start and end
values and the differential value for this period.
If you want to provide the automatic management of

this data, then a housekeeping period can be defined to
ensure that only the most relevant (most recent)
records are kept.
Figure 72 Accumulator Agent
You can also configure alarm limits for both the
(differential) value and rate of change in value for the
current period, which will be used to monitor the current value and/or rate against these alarm limits:
low-low, low, high and high-high.
Any infringement of these alarm limits causes the Agent to set its corresponding status bit, which can
be alarmed.
_________________________________________________________________________________________________________________________
9.7. IT/IoT Agent Types
These Agents are the building blocks around integration and management of SCADA and IT and are
summarised here.
9.7.1. PerfMon Agent

The PerfMon Agent is used to
monitor Windows Performance
counters, which belong to
performance objects such as
the Agent Server, Processor,
Memory and others.
These counters facilitate the

monitoring of the computer’s
performance and assist in
detecting performance
bottlenecks that could
adversely affect the functioning
of Adroit Ignite HMI.
Figure 73 PerfMon Agent
The values of these counters are updated every second and can also be assigned other Adroit Ignite HMI
Tags, such as Analog Tags, which can then be appropriately alarmed. Up to 16 performance counters
can be monitored per Agent.
_________________________________________________________________________________________________________________________
9.8. System Agent Types
System Agents are used internally by Adroit Ignite HMI to perform certain SCADA and other specific
functions. Instances of these Agents are created automatically and cannot be added manually by the
user.
• The Alias, Beeper, DataLog, Device, Hasp, Proxy, Scan and SystemInformation Agent types
make up this group.
9.8.1. Alias Agent

Alias Agents are the fundamental indirect scanning mechanisms in
Adroit Ignite HMI. They act as a references or pointers to other
Agents in the system.
As a reference to the Agent it is aliasing, the Alias Agent has the

same behaviour and state information but differs only in identity.
Figure 74 Alias Agent

9.8.2. DataLog Agent
Adroit Ignite HMI provides extensive historical logging facilities, either by using the proprietary data
logging facility or by specifying the required OLE DB compliant
database to log the data.
If this latter method is used, one can specify which table is used
for logging this data.
Any attribute of any Agent can be configured to have its values
historically logged.
Logging can take place either to native Adroit Ignite HMI binary
files or to any ADO datasource (SQL Server, Oracle, MS Access,
etc.).
When logged, the values are time stamped and are made
available via a DataLog Agent, to any client such as historical
trends, reports, external spread sheets, etc.
Select the Enable CSV backups option to ensure that the

logged data is backed up into multiple .CSV files for long-term
storage.
Figure 75 Datalog Agent

Select the Advanced… button to configure ALL the global
settings that affect the operation of the data logging subsystem.
Historical values are stored in a central file, with each DataLog Agent "owning" a defined portion of the
file. The total amount of disk space required for data logging depends on the total number of values
logged, as well as the rate at which and period for which each value is logged.
The following formula can be used to calculate disk file sizes:
_________________________________________________________________________________________________________________________
Description Formula
Index file size (bytes) = 8 + (56 * number of logged values)
Raw buffer size (bytes) = 20 * (Period/Rate) rounded up to next multiple of 8
Raw file size (bytes) =  Raw buffer sizes
Total disk space = Index file size + Raw file size
By default historical logging is an event-based function; in other words values are only logged when they
change and only then if the amount of change exceeds the value deadband parameter.
When the value of a logged point does not exceed the previously logged value by more than the value
deadband, the value is not logged.
Similarly, values that change more frequently than the user-defined time deadband will have a value
logged that depends on the logging method selected: actual value, average value, minimum value or
maximum value, as follows:
Value Description
actual The value logged is the value at the end of the time slice.
A time-weighted average is maintained of all the changes that occur and logged at the end
average
of the time slice.
minimum Only the lowest or minimum value is logged at the end of the time slice.
maximum The highest or maximum value is logged.
The formula presented above calculates a raw log file size based on the value changing exactly at the
logging rate (i.e., worst case scenario).
However, in a typical application, a compression factor of 3 to 5 or more is likely to be achieved. This

means that the actual period for which data is retained may be 3 to 5 times longer than the specified
logging period.
It is possible to override the default on-change-only logging behaviour and cause values to be logged
periodically or according to some other application-relevant trigger criteria.
Historically logged values can be retrieved for viewing within Adroit Ignite HMI or exported for further
processing as a .CSV file. This file format is recognized by many commercial spread sheet and database
packages.
Adroit Ignite HMI also provides a means of merging values from a .CSV file into an existing historical
database of Data Log Agents. The .CSV file may have been originally created by the Extract utility or
exported directly.
Out of limit monitoring enables Datalog Agents to immediately log out of limit values (values that are
not within their specified operating range), by ignoring the normal time deadband value and using a
faster log rate specified by the out of limit time deadband instead.
Each Datalog Agent can create their own backup (.LGB) files, when their associated .LGD files wrap.
Once created, the datalogging subsystem automatically retrieves the data from these .LGB files, if
required by trends (charts) or other requests for historical data.
This feature can also extend the potential amount of logged data without creating larger log files, since
larger log files have the side effect of causing the Agent Server to take longer to start up.
IMPORTANT: When backing up datalogs we recommend the creation and use of .LGB files.
_________________________________________________________________________________________________________________________
9.8.3. Device Agent
Device Agents, in conjunction with protocol drivers, coordinate scanning in Adroit Ignite HMI and are
responsible for creating, deleting and otherwise configuring Scan Agents which handle the actual
scanning to and from front-end devices.
The number of device Agents in a system

will depend solely on the number of
different front-end devices. A system with
one PLC controlling, say Boiler 1, would
have only one Device Agent called BOILER1
(or any other name chosen by the user). On
the other hand, a system with many
different front-end devices, possibly of
different types, will have one Device Agent
per device.
Each scan Agent is in fact a separate,

independently scheduled Windows thread
which means that genuine, concurrent,
parallel scanning will happen in Adroit Ignite
HMI whenever the characteristics and/or
connection(s) to the front-end device(s)
permit.
Figure 76 Device Agent
Due to Adroit Ignite HMI‘s inherent flexibility, it is possible to scan in and out of any slot of any Agent.
For example, a Data Log Agent can be started by scanning its start slot from an external device, thereby
effectively achieving event-triggered logging; a new value can be uploaded to the high alarm limit of an
Analog Agent, etc. Each slot to be scanned is associated with an address in an external device, a scan
period in milliseconds, and a deadband. A value is only updated into the relevant slot when it changes
by more than the deadband setting.
In addition, scanning is the means by which any two Agent slots are "linked" or "connected" together.
The implication of this is that Agents can source their data from any other Agent as well as from a front-
end device. This feature is particularly valuable when used in conjunction with Expression Agents (the
Expression Agent is explained later).
9.8.4. Other System Agent Types

Other system Agent types include Beeper, Hasp, Proxy, Scan and SystemInformation.
The Beeper Agent drives the built-in PC speaker and is typically used to annunciate alarms.
A single Hasp Agent instance called LICENCE holds details about how many scan points and users are
currently licenced.
Proxy Agents are created automatically when an application requests information about an Agent that
exists in a remote Agent Server. The proxy Agent assumes the role of the remote Agent in the local
environment and is continuously updated with any changes that occur in the remote Agent. The function
of updating the proxy is transparent to applications such as Operators as well as any 3rd party applications
interacting locally or remotely with the server containing the proxy.
_________________________________________________________________________________________________________________________
Scan Agents are created dynamically by the system as a function of the user-specified scan
configuration and capabilities of the protocol driver mapped by the device creating the scan Agent.
There is also a single SystemInformation instance called systemInfo that contains a variety of system
wide configuration, run-time, and diagnostic information.
Figure 77 Systeminfo Agent
This Agent contains some very valuable information that can be used to present a more detailed view of
what is going on within a Server. Again, as has been explained the information available are all contained
with slots and available to be presented on a graphic form or used within a system.
Figure 78 Systeminfo – Running Attributes
Examples of useful “Tags” would be

SystemInformation.SystemInfo.Second – is the local second of time on the PC and can be used to trigger
events or used in scripts or calculations in Expressions
The same applies to minute, hour, day, dayOfWeek, currentTime, month, year, saveNow, saveOnExit
_________________________________________________________________________________________________________________________
9.9. Adding the Tags for the Batching Plant
As per the IO Schedule and Agents required to run the Batching Plant we will now configure the first of
the Agents required. The IO Schedule can be found at the end of this document, you may want to print
them out in hard copy for easy reference.
Note: Once you are familiar with the first principals Agents can be generated from our EXCEL Add-in
tool and bulk engineering allows this to be done very quickly and efficiently. An additional Training
manual is available for this Excel Add-in tool.
Note: We will deal with Scanning to the OPC Server in the next section, in normal projects you would
do all at the time you would be adding Agents.
_________________________________________________________________________________________________________________________
Exercise 7 - Configuring Digital Agents: First Principles
Adding Digital Agents to the Adroit Datasource using first

Objective:
principles.
In this exercise the following Agent will be configured to represent
the Batching Plant Water Pump Status.
Active Agent Server and Ignite Server.
Prerequisites: Active Designer.
1. Open the Designer and navigate to the Open Configurator from the Home menu.
Alternatively, expand Datasource in the Enterprise Manager, right click on Adroit and select Open
Configurator.
2. Select the Agent Type Digital.
3. In the Name dialog box, add the Agent ADT_JU_MX_PMP_STATUS.
4. Insert the description Water Pump Inlet into the Description dialog box.
5. Click the Add Button. (once viewed in the Agent’s window, the Agent has been added to the Datasource)
Figure 79 Digital Agent Configuration Window
6. Click OK and close the Agent Configurator and save the changes.
7. Repeat the above exercise for the balance of the Digital Agents in the IO Schedule.
_________________________________________________________________________________________________________________________
OFF ON
Name Description
state state
ADT_JU_MX_AGIT_START Agitator Manual Start OFF ON
ADT_JU_MX_AGIT_STATUS Agitator Motor Status Stopped Running
ADT_JU_MX_AGIT_STOP Agitator Manual Stop OFF ON
ADT_JU_MX_ALM-RESET Reset OPC Alarms OFF ON
ADT_JU_MX_AUT_MAN Plant Auto/Manual Automatic Manual
ADT_JU_MX_AUT_STRT Start OPC Plant OFF ON
ADT_JU_MX_FED_A_STATUS Ingredient A Feeder OFF ON
ADT_JU_MX_FED_B_STATUS Ingredient B Feeder OFF ON
ADT_JU_MX_OPC_RESET Reset OPC Plant OFF ON
ADT_JU_MX_PMP_MAN_STP Manual Stop OFF ON
ADT_JU_MX_PMP_MAN_STRT Manual Start OFF ON
ADT_JU_MX_PMP_STATUS Water Pump Status OFF ON
ADT_JU_MX_PMP_TRIP Water Pump Alarm OFF ON
ADT_JU_MX_VLV_ALM Discharge Valve Alarm OFF ON
ADT_JU_MX_VLV_STAT Discharge Valve Status Closed Open
Notes:
_________________________________________________________________________________________________________________________
Exercise 8 - Configuring Analog Agents: First Principles
Adding Analog Agents to the Adroit Datasource using first

Objective: principles.
the Analogue Agents required to run the Batching Plant Water
Actual Mass Pumped value:

Alternatively, expand Datasource in the Enterprise Manager, right click on Adroit and select Open Configurator.
2. Select Agent Type Analog.
3. In the Name dialog box, add the Agent ADT_JU_MX_PMP_MASS_ACT.
4. Insert the description Water Mass Actual into the Description dialog box.
5. Select the Agent in the Agents window and click Edit.
6. Set the following parameters as per the supplied I/O Schedule:
Figure 80 Analog Configuration Window
7. Once limits have been set, click Update and OK.
____________________________________________________________________________________________________________________________
8. Repeat the above exercise for the balance of the Analog Agents in the IO Schedule
Device Span Engineering Span Alarms

Name Description High- Low-
Minimum Maximum Minimum Maximum Unit High Low
high low
ADT_JU_MX_AGIT_TIME_ACT Agitator Time - Actual 0 100 0 100 sec 100 100 0 0
ADT_JU_MX_AGIT_TIME_TGT Agitator Time - Target 0 100 0 100 sec 100 100 0 0
ADT_JU_MX_BTCH_NUM Batch Number 0 100 0 100 100 100 0 0
ADT_JU_MX_BTCH_NUM_SP Batches to Run 0 100 0 100 100 100 0 0
ADT_JU_MX_FED_A_MASS_ACT Ingredient A - Actual 0 100 0 100 Kg 85 70 35 20
ADT_JU_MX_FED_A_MASS_TGT Ingredient A - Target 0 100 0 100 Kg 85 75 35 20
ADT_JU_MX_FED_B_MASS_ACT Ingredient B - Actual 0 100 0 100 Kg 85 70 35 20
ADT_JU_MX_FED_B_MASS_TGT Ingredient B - Target 0 100 0 100 Kg 100 100 0 0
ADT_JU_MX_HTR_TEMP_ACT Batch Temperature - Actual 0 4096 0 45 °C 45 35 15 0
ADT_JU_MX_HTR_TEMP_TGT Batch Temperature - Target 0 4096 0 45 °C 45 35 15 0
ADT_JU_MX_MIX_TNK_LVL Mix Tank level 0 100 0 100 Kg 85 70 5 0
ADT_JU_MX_PMP_MASS_ACT Water - Actual 0 100 0 100 Litres 85 70 35 20
ADT_JU_MX_PMP_MASS_TGT Water - Target 0 100 0 100 Litres 100 100 0 0
ADT_JU_MX_VLV_RATE Discharge Valve Flow Rate 0 100 0 100 Kg/s 100 100 0 0
ADT_JU_MX_VLV_TIME Discharge Time 0 100 0 100 sec 100 100 0 0
9. Close the Agent Configurator and save the changes.
Notes:
_______________________________________________________________________________________________________________________________________________________________________________
Exercise 9 - Configuring Stringlist Agents: First Principles
Adding StringList Agents to the Adroit Datasource using first

the Batching Plant Status.

2. Select Agent Type Stringlist.
3. In the Name dialog box, add the Agent ADT_JU_MX_BTCH_STAT.
4. Insert the description Plant Phase into the Description dialog box.
7. Select Add as indicated below to add to the list
Figure 81 Stringlist Configuration Window
8. Once parameters have been set, click Update and OK.

____________________________________________________________________________________________________________________________
Name Description Index String
0 STOPPED
1 BATCHING
2 MIXING
ADT_JU_MX_BTCH_STAT Plant Phase 3 HEATING
4 DISCHARGING
5 BATCH COMPLETE
8 OPC ALARM
Notes:
__________________________________________________________________________________________________________________________
Exercise 10 - Configuring Expression Agents: First Principles
Adding Expression Agents to the Adroit Datasource using first

In this exercise the Tank Level will be calculated:
2. Select Agent Type Expression.
3. In the Name dialog box, add the Agent ADT_JU_MX_MIX_TOTL_MASS.
4. Insert the description Tank Level Calculation into the Description dialog box.
6. Set the following parameters in the Variable Slots and other settings of the Expression Agent as per
the supplied I/O Schedule:
Figure 82 Expression Configuration Window
7. Once parameters have been set, click Update and OK.

9. The Value is generated by the using an Expression Agent.
__________________________________________________________________________________________________________________________
Name Description Engineered Data Range
Value = ADT_JU_MX_MIX_TNK_LVL.value
Variable Slots:
V01 = ADT_JU_MX_FED_A_MASS_ACT.value
V02 = ADT_JU_MX_FED_B_MASS_ACT.value
V03 = ADT_JU_MX_PMP_MASS_ACT.value
ADT_JU_MX_MIX_TOTL_MASS Tank level Calculation V04 = ADT_JU_MX_VLV_RATE.value
V05 = ADT_JU_MX_VLV_TIME.value
Expression = v1+v2+v3-(v4*v5)
Evaluation = Continuous
10. Add and configure the balance of the Expression Agents as per the IO Schedule

V01 = ADT_JU_MX_BTCH_STAT.index
Expression = v1 == 8 ? 1 : 0
ADT_JU_MX_ALM_STAT Alarm Status
Expression = v1 == 3 ? 1 : 0
ADT_JU_MX_HTR_STATUS Heater Status
Notes:
__________________________________________________________________________________________________________________________
Exercise 11 - Configuring Counter Agents: First Principles
We are using the Adroit Ignite Counter Agents to give us data around the Stop/Start and Running Statistics
of the various pieces of equipment running the Batching Plant.
Adding Counter Agents to the Adroit Datasource using first

In this exercise the Agitator Data will be configured.
2. Select Agent Type Counter.
3. In the Name dialog box, add the Agent ADT_JU_MX_AGIT_DAT.
4. Insert the description Agitator Data into the Description dialog box.
Figure 83 Expression Configuration Window
7. Once parameters have been set, Click Start then OK.

__________________________________________________________________________________________________________________________
9. Add and configure the balance of the Counter Agents as per the IO Schedule
Name Description Input Tag Triggered Trigger
ADT_JU_MX_AGIT_DAT Agitator Data ADT_JU_MX_AGIT_STATUS.value ✓ systemInfo.second
ADT_JU_MX_FED_A_DAT Ingredient A Feeder ADT_JU_MX_FED_A_STATUS.value ✓ systemInfo.second
ADT_JU_MX_FED_B_DAT Ingredient B Feeder ADT_JU_MX_FED_B_STATUS.value ✓ systemInfo.second
ADT_JU_MX_HTR_DAT Heater ADT_JU_MX_HTR_STATUS.value ✓ systemInfo.second
ADT_JU_MX_PMP_DAT Water Pump ADT_JU_MX_PMP_STATUS.value ✓ systemInfo.second
Notes:
__________________________________________________________________________________________________________________________
9.10. Scanning Agents/Tags
Scanning in Adroit Ignite HMI refers to the sending of or the communication of values between Adroit
Ignite HMI Tags (Agent.slot) and the front-end devices in the field, such as PLCs, RTUs, etc.
Since front-end devices use different protocols or languages for communication, Adroit has developed a
large number of protocol drivers, which allow Adroit Ignite HMI to communicate to these front-end devices.
Once installed, a protocol driver provides the protocol or language to communicate to front-end devices
that use this protocol. However, it is necessary to add one or more devices through which the
communication actually occurs. Each device is essentially a logical connection to the front-end device that
it is communicating to.
In other words, while the installed protocol driver is the language that needs to be communicated, the
devices are the actual translators that use this language to communicate between the front-end devices
and Adroit Ignite HMI.
Scanning allows for both conventional poll-response and exception protocols. Scan rates can be defined
on individual I/O ports that are automatically optimised for orderly scanning and traffic loading. Drivers
can be configured dynamically online and support auto recovery with primary and secondary channel
redundancy.
The Driver configuration is saved in the system registry and should the Agent Server be run on another
machine; the Drivers must be reconfigured on that machine. Protocol Drivers can be installed and
configured using the Driver Configuration in the Adroit Ignite Config Editor.
9.10.1. The Principles of Scanning

It is important to ensure that the data is well organised and arranged continuously wherever possible.
This will ensure efficient scanning of the PLC and data, optimising response and update times.
The fundamentals are as follows:
• PLC hardware that is connected to Adroit Ignite HMI via the Protocol Driver and the named Device
Agent.
• Add the relevant Agent that best maps the data type, for example an Analog Agent to map variable
data.
• Scan the slot of the Agent to the Device and map it to the correct address within the PLC.
• If a simple read and display data function is required, scan the Agent.slot to the PLC and address.
• If required to interact from the Adroit Ignite HMI to the point in the PLC, the “Output Enabled”
check box must be checked before scanning is done.
• Typically, all the Agents would be added and configured, all the scanning done and then the graphic
forms built to match the P&ID drawing and the data requirements.
9.10.2. Golden Rules for Scanning:

• If available, scan the rawValue slot not the value slot, this is especially important for Analog Agents.
• Do not scan faster than needed.
__________________________________________________________________________________________________________________________
9.10.3. Device and Scan Agents
Figure 84 Device and Scan Agent
Scanning is managed in Adroit Ignite HMI by means of active and specialist Agents called Scan Agents.
The appropriate Device Agents automatically create them when needed and concentrates data types
together for efficiency.
Device names may not exceed 27 Adroit legal characters that are unique, as they eventually become the
names of the Device Agent within the Agent Server.
Figure 85 OPC Client Configuration Dialogue
9.10.4. Calculating the Scan Period

It is very easy to oversubscribe (scan) to data, there are limitations to any communications medium – the
document will assume serial-based communications, as it’s the one most easily overestimated.
A few assumptions will have to be made:
• Total number of Outstations on the network.
• Total number of I/O scan tasks per outstation (approx.) and their size in characters (approx.).
• Approximate/Average Turnaround Time for a transaction.
• Network characteristics such as baud rates/bandwidth etc.
Assume for the ideal case, i.e. No errors, retries, pre transmission delays, latency delays etc.
__________________________________________________________________________________________________________________________
Exercise 12 - Scanning Digital Agents: First Principles
Now we have created all the Agents required for the Batching Plant we can go ahead and start tying the
Agents up to the Batch Simulation OPC Server items.
Scanning Digital Tags to the Adroit Datasource using first


Preconfigured database.
2. Select the Agent type you wish to scan. In this case we are going to scan a Digital Agent
3. In the name dialog box, select the Agent ADT_JU_MX_PMP_STATUS.
4. With the Tag highlighted, click the Scan button.
5. Select your device that you wish to scan to.ie. BATCH
a. Select the correct Device
Figure 86 Create Device Agent
b. Click yes to create the Device Agent automatically

Note: once this Device Agent has been created, it will automatically be available on the taskbar.
__________________________________________________________________________________________________________________________
c. Browse in the correct addressing for the Batching Simulation OPC Server (in this case
PumpRunning) Double click on the name in the OPC Browser to load or highlight the item and
click Select.
d. Change Scan Rate to 1000ms
6. Click Scan. Tag should appear in the Currently Scanned Tags List.
Figure 87 Digital Scan Config
7. Click “Started” radial button to initiate the scanning.

8. Click OK.
9. Save and close the Agent Configurator.
Notes:
__________________________________________________________________________________________________________________________
8. Repeat the above exercise for the balance of the Digital Agents in the IO Schedule.
OFF ON Scan Scan

Name Description
state state Output Enabled OPC Address
ADT_JU_MX_AGIT_START Agitator Manual Start OFF ON Yes StartAgitatorMan
ADT_JU_MX_AGIT_STATUS Agitator Motor Status Stopped Running No AgitatorRunning
ADT_JU_MX_AGIT_STOP Agitator Manual Stop OFF ON Yes StopAgitatorMan
ADT_JU_MX_ALM-RESET Reset OPC Alarms OFF ON Yes AlmReset
ADT_JU_MX_AUT_MAN Plant Auto/Manual Automatic Manual Yes ManAuto
ADT_JU_MX_AUT_STRT Start OPC Plant OFF ON Yes AutoStart
ADT_JU_MX_FED_A_STATUS Ingredient A Feeder OFF ON No FeedARunning
ADT_JU_MX_FED_B_STATUS Ingredient B Feeder OFF ON No FeedBRunning
ADT_JU_MX_OPC_RESET Reset OPC Plant OFF ON Yes PlantReset
ADT_JU_MX_PMP_MAN_STP Manual Stop OFF ON Yes StopPumpMan
ADT_JU_MX_PMP_MAN_STRT Manual Start OFF ON Yes StartPumpMan
ADT_JU_MX_PMP_STATUS Water Pump Status OFF ON No PumpRunning
ADT_JU_MX_PMP_TRIP Water Pump Alarm OFF ON No PumpTrip
ADT_JU_MX_VLV_ALM Discharge Valve Alarm OFF ON No DischargeAlm
ADT_JU_MX_VLV_STAT Discharge Valve Status Closed Open No DischValveOpen
Notes:
_______________________________________________________________________________________________________________________________________________________________________________
Exercise 13 - Scanning Analog Agents: First Principles
Scanning Analog Tags to the Adroit Datasource using first


2. Select the Agent type you wish to scan. In this case we are going to scan an Analog Agent
3. Select the Tag ADT_JU_MX_PMP_MASS_ACT
b. Browse in the correct addressing for the Batching Simulation OPC Server (in this case
IngMassA)
c. Change Scan Rate to 1000ms
Figure 88 Analog Scan Config

8. Click OK.
Notes:
____________________________________________________________________________________________________________________________
9. Repeat the above exercise for the balance of the Analog Agents in the IO Schedule
Device Span Engineering Span Alarms Scan

Name Description High- Low- OPC Output
high low Address Enabled
ADT_JU_MX_AGIT_TIME_ACT Agitator Time - Actual 0 1000 0 1000 sec 100 100 0 0 ActualMixTime No
ADT_JU_MX_AGIT_TIME_TGT Agitator Time - Target 0 1000 0 1000 sec 100 100 0 0 TargetMixTime Yes
ADT_JU_MX_BTCH_NUM Batch Number 0 1000 0 1000 100 100 0 0 BatchNumber No
ADT_JU_MX_BTCH_NUM_SP Batches to Run 0 1000 0 1000 100 100 0 0 NumBatches Yes
ADT_JU_MX_FED_A_MASS_ACT Ingredient A - Actual 0 100 0 100 Kg 85 70 35 20 IngMassA No
ADT_JU_MX_FED_A_MASS_TGT Ingredient A - Target 0 100 0 100 Kg 85 75 35 20 IngTargetA Yes
ADT_JU_MX_FED_B_MASS_ACT Ingredient B - Actual 0 100 0 100 Kg 85 70 35 20 IngMassB No
ADT_JU_MX_FED_B_MASS_TGT Ingredient B - Target 0 100 0 100 Kg 100 100 0 0 IngTargetB Yes
ADT_JU_MX_HTR_TEMP_ACT Batch Temperature - Actual 0 4096 0 45 °C 45 35 15 0 ActualMixTemp No
ADT_JU_MX_HTR_TEMP_TGT Batch Temperature - Target 0 4096 0 45 °C 45 35 15 0 TargetTemp Yes
ADT_JU_MX_MIX_TNK_LVL Mix Tank level 0 100 0 100 Kg 85 70 5 0 - -
ADT_JU_MX_PMP_MASS_ACT Water - Actual 0 100 0 100 Litres 85 70 35 20 IngMassH20 No
ADT_JU_MX_PMP_MASS_TGT Water - Target 0 100 0 100 Litres 100 100 0 0 IngTargetH2O Yes
ADT_JU_MX_VLV_RATE Discharge Valve Flow Rate 0 100 0 100 Kg/s 100 100 0 0 DischRate Yes
ADT_JU_MX_VLV_TIME Discharge Time 0 1000 0 1000 s 100 100 0 0 ActualDischTime Yes
Notes:
_______________________________________________________________________________________________________________________________________________________________________________
Exercise 14 - Scanning StringList Agents: First Principles
Scanning StringList Tags to the Adroit Datasource using first


2. Select the Agent type you wish to scan. In this case we are going to scan an StringList Agent
3. Select the Tag ADT_JU_MX_BTCH_STAT
b. Browse in the correct addressing for the Batching Simulation OPC Server (in this case Status)
c. Change Scan Rate to 1000ms
Figure 89 StringList Scan Config

8. Click OK.
Notes:
____________________________________________________________________________________________________________________________
10. Project Tree and Graphic Forms
Projects manage the creation, opening and storage of graphic forms and wizards, which can be organized
through the creation of folders and sub-folders.
A project exists in two main states:
• The design state, which is used to add, import and configure or design the graphic forms within
the Designer.
• The operational or run-time state, which is used to view and interact with these graphic forms,
typically within the Operator although it is also possible to do this within the Designer.
Figure 90 Project Tree and Graphic Forms
___________________________________________________________________________________________________________________________
Exercise 15 - Creating a Project Tree
If you look at the BatchOPC Server our sample Juice Plant is going to be made up of a Batching Plant so
we are going to create a single Project called Juice that would have sub-project directories called Batching
that would contain the Graphic Forms (Mimics) stored in an organised manner.
Create a Project Tree structure.

Objective:
An active Agent Server.

Prerequisites: An active Ignite Server.
The Designer running.
1. Access the Enterprise Manager, Projects Folder.

2. Right click on icon:
Figure 91 Home Menu - New Project Icon
3. Add a new Project named Juice.

a. Navigate to the tab Project Style
b. Under Project Style Settings, ensure the Predefined radial button is selected, and via the drop-
down menu select the option 1920x1080
c. Set the BackColor to System, ControlDark
d. Via the Font dialog, set you Font to Arial, Bold, 10
e. Click Finish.
4. Right click on the Juice project and create the following new folders:
a. Batching Plant
b. Filter Plant (for Competency Test use)
c. Landing
d. Templates
e. Wizards
___________________________________________________________________________________________________________________________
Figure 92 Enterprise Manager Projects Folder
___________________________________________________________________________________________________________________________
11. Behaviours
Behaviours can animate or provide additional functionality to controls graphic elements that are added to
a graphic form. In other words, you typically use behaviours to display the values of your data, either
actually of graphically, by using the available properties of the selected control or graphic element and to
perform other functions.
11.1. Bind Value Behaviour

This behaviour can drive a Data Element to and/or from the value of a property of a control or vector.
Examples:-
• Displaying a value on a label or button with applied string formatting.
• Driving a gauge control from the value of an Adroit Agent.
• Driving a slider control from the value of an Adroit Agent and writing this value back to Adroit
when the slider is manually adjusted.
The Bind Value behaviour provides the following options:

• To Control Property: this is the default option, where a value (Data Element) is linked to a
property of a control/vector. If this is a String property, then you also have the option of applying
string formatting to this value before it displayed. This allows a Data Element (Value) to drive
the value of a property of a control/vector.
• From Control Property: this connects a property of a specific control or vector to a value
(Data Element) and specifies which event of this control or vector is used to update this Data
Element with the current value of this property. This allows the value of a property of a control
or vector to drive the value of a Data Element.
• Both (To/From Control Property): this both sets a property of a control or vector to a Data
Element and when a specific user event occurs to this control or vector, then the current value
of this property is written back to this Data Element. This facilitates a two-way feedback
connection between the specified property of the control/vector and the Data Element
11.2. Colour Behaviour

You can apply this behaviour to controls and graphic elements (vectors) to achieve the following effects:
• To assign colours to the two states of a Boolean or digital value, so that depending on its value,
this object will alternate between these two pre-defined colours.
• To blink a specific Colour property of the object (alternate between two pre-defined colours at
a specified interval in milliseconds) and display another pre-defined colour when this blinking is
stopped.
• This blinking can either be continuous or be started and stopped by a value.
• To blink the visibility of the object (alternate between hiding and showing the object at a
specified interval in milliseconds) .
• This blinking can either be continuous or be started and stopped by a value.
• To define coloured states, each associated with specific value(s).
If necessary, one or more of these states can blink.
• If necessary, one or more of these bit masks can blink.
Note: Only numerical and Boolean values can be used to activate blinking. Invalid values grey out the associated object.
___________________________________________________________________________________________________________________________
11.3. Display Value Behaviour
This behaviour can ONLY configure controls that have String properties that end-users can see, to display
the value of a specific Data Element. If necessary, this value can be formatted before it is displayed.
Note: It is not recommended to add more than one Display Value behaviour as typically ONLY the value
of the last defined behaviour is displayed.
11.4. Execute Command Behaviour

This behaviour can be applied to controls and graphic elements to perform the following commands:
• Start Application – to launch an application and specify any required parameters.
• Open Graphic Form – to open a specific graphic form
• Close Graphic form either close a specific graphic form or the current open form
• Print Graphic form – to send the currently displayed graphic form to the default printer
• Log Off – to log off the current user
• Log On - to perform a “switch user” operation by logging in another user.
11.5. Flip Bitmap Behaviour

This behaviour allows the value of a Tag to create animation effects by determining which bitmap picture
(.BMP file) is displayed by the Bitmap picture element e.g. to display the appropriate bitmap picture (.BMP
file) when a switch is in the On and Off positions.
Note: It is necessary to add the required bitmap pictures (.BMP files) to the required Bitmap picture element first.
11.6. Location Behaviour

This behaviour can be applied to controls and graphic elements (vectors) to dynamically move the object
linearly in a defined X-Y direction by means of a monitored value:
In other words, you need to monitor a value, which has a defined minimum and maximum value and then
specify the maximum required movement in the X (horizontal) and/or Y (vertical) dimensions, when the
value reaches its maximum value.
For example, when the monitored value is at 50% of its maximum, then this object moves halfway.
11.7. Operator Action Behaviour

This behaviour can be applied to controls and graphic elements to typically allow users to change the value
of a specific Data Element at runtime
Operator action provides the following three methods of changing values at runtime
• Control Action – to increase or decrease a numerical value or to set (enable or disable) or
invert a Boolean value.
• Data Entry – to display a dialog box so your end users can typically specify a numerical value
within a predefined range
• Data Element Set - To specify either another value (Data Element) or a static value to set this
value. Any subsequent change to the specified Data Element will change the input value.
Note: Ensure that the data of this value is compatible with the value you are configuring.
11.8. Percentage Fill Behaviour

This behaviour can ONLY be applied to graphic elements (vectors) to dynamically fill the object by means
of a monitored value.
completely fills the object when the value reaches its maximum value.
For example, when the monitored value is at 50% of its maximum, then this object is half filled.
___________________________________________________________________________________________________________________________
11.9. Rotation Behaviour
This behaviour can ONLY be applied to graphic elements (vectors) to dynamically rotate the object by
means of a monitored value.
specify the maximum required rotation, in degrees, when the value reaches its maximum value.
11.10. Size Behaviour

This behaviour can be applied to controls and graphic elements (vectors) to dynamically resize the object
linearly by means of a monitored value.
specify the maximum required width and/or height magnifications, when the value reaches its maximum
value.
For example, specifying a factor of 2 for both the width and height dimensions then the object doubles its
size when the measured (Input Data Element) is at the specified Maximum Data Element/value.
Note: The object retains its original size when the monitored value is less than or equal to the specified Minimum value.
11.11. Tooltip Behaviour

This behaviour can be applied to controls and graphic elements to display additional information usually
concerning this object when the mouse cursor (pointer) hovers over. These tooltips are similar to those
associated with toolbars, in that when the mouse pointer hovers over the object, a rectangle containing
text appears.
11.12. Visibility Behaviours

This behaviour can be applied to controls and graphic elements to enable or disable Boolean properties
that users can see
___________________________________________________________________________________________________________________________
12. Design Mode: Building Graphic Forms
The Designer is the interface you will use to interact with and configure projects within the Ignite Server.
Figure 93 Designer – Default Layout
The top part of the window is the quick access design menu. This menu is based on the very popular
ribbon menu you see in Microsoft products.
Figure 94 Designer – Detailed Display Example
___________________________________________________________________________________________________________________________
Exercise 16 - Building the Batching Plant Graphic Form
Create a new graphic form (Styled) named Batching Plant.

Objective: Design the graphic form to conform to the P&ID drawing.
-
Prerequisites:
1. In the Enterprise Manager, right click on the Batching Plant Folder and select Create Graphic Form
(Styled).
2. Name the graphic form Batching Plant.
Property Value
Size: 1920, 1080
3. From Toolbox tab, navigate to Vectors, select Rectangle and place on the graphic form.
4. Set the properties of the Rectangle as follows.
Property Value
Name: cORTankBody
Size: 300,400
5. From Toolbox tab, navigate to Vectors, select Ellipse and place on the graphic form.
6. Set the properties of the Ellipse as follows.
Property Value
Name: cOETankTop
Size: 300,60
7. Align the Ellipse from the top corners of the rectangle, that it creates an appearance of a cylinder.
8. Copy the ellipse and position at the bottom of the rectangle to form that base of the tank
9. Select all 3 vectors, navigate to the Design menu, and click Alignment, choosing Align Centres.
10. With all three vectors selected, click Create Vector Group.
11. Save the graphic form.
___________________________________________________________________________________________________________________________
Notes:
___________________________________________________________________________________________________________________________
Exercise 17 - Adding Static Graphics and Colour Behaviour [Part 1]
Adding Static Graphics to graphic forms.

Objective: Changing colours based on status.
-
Prerequisites:
1. Option A: Browse through Shapes Wizards and Examples Menu, Electrical Symbols, Static Graphics,
Agitators. Select the Vertical Axis Agitator, then click on the graphic form to paste.
Option B: From the Enterprise Manager navigate to Projects, Shapes Wizards and Examples, Static
Graphics, Agitators; Drag the Vertical Axis Agitator on the Batching Plant Graphic and select Paste
Graphic Form contents.
2. With the Agitator selected, navigate to the Contents window.
3. Expose the various contents of the Agitator, selecting a part that you wish to add a Behaviour to.
4. Right click on the selected content and select Add new Colour behaviour
5. Select the option digital state and browse the Data Element:
Adroit.Digital.ADT_JU_MX_AGIT_STATUS.value
6. Set the On and Off to green and red respectively.
Figure 95 Colour Behaviour Configuration

___________________________________________________________________________________________________________________________
7. Click Finish.
8. Size the Agitator that is proportional in size to your tank.
9. Add a Screw Conveyor to the graphic form from the Static Graphics library, Conveyors.
10. Size the Screw Conveyor that is proportional in size to your tank.
11. Copy and paste the Screw Conveyor and selecting flip horizontally in the Design ribbon under the rotate
drop-down menu.
12. Align the 2 x Screw Conveyors to the top of the tank.
13. Access the contents of each screw conveyer and place a Colour Behaviour, with the digital state option,
on a section of the object making use of the following two Data Elements:
− Adroit.Digital.ADT_JU_MX_FED_A_STATUS.value
− Adroit.Digital.ADT_JU_MX_FED_B_STATUS.value
Figure 96 Static Graphics
14. Position the 2 Screw conveyors as per the diagram above.

15. Save your graphic form.
16. Switch to run mode and run the Batching Simulation OPC Server to test.
Notes:
___________________________________________________________________________________________________________________________
Exercise 18 - Adding Static Graphics and Colour Behaviour [Part 2]
Adding Static Graphics to graphic forms.

Objective: Changing colours based on status.
-
Prerequisites:
1. Navigate to the Batching Plant graphic form.

2. Making use of the static Library, add a Filter, Motor and pipe work as per the image.
3. Add a colour behaviour to the motor part of the graphic object, using digital state with the following
Data Element:
− Adroit.Digital.ADT_JU_MX_PMP_STATUS.value
4. Save you graphic form.
5. Switch to run mode and run the Batching Simulation OPC Server to test.
6. Using the Static Graphic Library, create an outlet pipe for the tank
7. Add a Pipework and outlet valve to the graphic form from the Static Graphics library.
8. Access the contents of Valve and place a colour behaviour, with the digital state option, on a section
of the object making use of the following Data Elements:
− Adroit.Digital.ADT_JU_MX_VLV_STAT.value
9. In the properties change the name to DischargeValve.
10. Close and save the Agent Configurator.
11. Save the graphic form and Run.
Figure 97 Batching Plant – Motor & Discharge Valve
___________________________________________________________________________________________________________________________
Notes:
___________________________________________________________________________________________________________________________
Exercise 19 - Percentage Fill Behaviour
Use a Percentage Fill behaviour.

Objective:
-
Prerequisites:
1. Navigate to the Batching Plant graphic form and select the Mixing Tank Body.
2. As this object is part of a vector group, select the Contents page. Browse for the cORTankBody.
3. Right click and select Add new Percentage Fill behaviour.
4. Browse in the Input Data Element Adroit.Analog.ADT_JU_MX_MIX_TNK_LVL.value
5. Ensure that the Minimum and Maximum dialogs are populated.
6. Select the fill direction, Bottom to Top.
7. Click Finish.
9. Toggle to Run Mode and test the graphic form from the Batching Simulation OPC Server.
You will notice that the Data Element Adroit.Analog.ADT_JU_MX_MIX_TNK_LVL.value, is not being
scanned from the Batching Simulator OPC Server as per the I/O Schedule:
The Value is generated by the using the Expression Agent you have already created.
V04 = ADT_JU_MX_VLV_RATE.value
ADT_JU_MX_MIX_TOTL_MASS Tank level Calculation
___________________________________________________________________________________________________________________________
Figure 98 Expression Agent Configuration Dialogue
The Expression = v1+v2+v3-(v4*v5)
The Value in this case:

ADT_JU_MX_MIX_TNK_LVL.value is the total of the 3 ingredients (Ingredient A, Ingredient B and
Water) less the amount discharged though the valve.
To test the Expression, open the Configurator, Edit, Click the Display Values radial button and click on
Calculate.
The values will reflect the actual Batching Simulator OPC Server values.
In the Expression, all variables are V01 – V20, while the Value slot is also refer to V99.
Notes:
___________________________________________________________________________________________________________________________
Exercise 20 - Location and Visibility Behaviour [Part 1]
Make the tank bottom ellipse invisible when the tank is empty.
Objective: Get an Ellipse to move vertically.
-
Prerequisites:
1. Select your Mixing Tank and access the Contents.

2. Select the bottom tank Ellipse, and make a duplicate, with the use of the copy and paste buttons on
the Home Ribbon tab.
3. Give the newly created copy of the ellipse that same colour as you percentage fill behaviour.
4. Access the visibility behaviour via the Smart Tag ( ).
5. Browse in the Data element, making sure the correct slot is chosen:
Adroit.Analog.ADT_JU_MX_MIX_TNK_LVL.Low-low
6. Click the Invisible radio button.
7. Click finish and position the Ellipse on top of the bottom ellipse of the Mixing tank.
8. Right click on the visibility ellipse and select copy with behaviours and paste on a section of the form.
9. Make note of the height of the cORTankBody.
10. Add the location behaviour to the ellipse that was just copied and browse in the Data Element:
11. Set the following:
X plot = 0
Y plot = height of the tank, adding a negative symbol before the number.
Note: Check the height of the Tank by viewing the Location in Properties.
Note: Adroit Ignite HMI makes use of pixels when plotting the x and y Points and not a Cartesian graph.
12. Position the Ellipse on top of the original.

13. Save the graphic form and test by toggling to run mode and activating the Batching Simulation OPC
Server.
Notes:
___________________________________________________________________________________________________________________________
12.1. Creating Labels and Displaying Real Time Data
This can be done in a number of ways depending on the specific requirements. Real-Time Data is
information that is delivered immediately after collection The basic definition of real-time data is that it is
data that is not kept or stored but is passed along to the end user as quickly as it is gathered. It is helpful
for all sorts of analytics projects and for keeping people informed about their natural environment through
the power of instant data delivery.
Labels & Real

time data
Figure 99 Creating labels and real time data
___________________________________________________________________________________________________________________________
Exercise 21 - Creating Labels
Label the individual plant items.

Objective:
-
Prerequisites:
1. Select and position a Windows Form Label on the graphic form.

2. Change the Label Properties as follows
Property Value
Name lblFeederA
AutoSize True
Text Ingredient A
Backcolor Web, Silver
Font Arial,Bold,12
3. Position the Text object over Feeder A
4. Copy and paste the label control and position over Feeder B
5. Change the label properties as follows
Property Value
Name lblFeederB
Text Ingredient B
6. Repeat for the Water Pump, Discharge valve and the Agitator configuring the correct properties.
Figure 100 Batching Plant Window Form Labels
Notes:
___________________________________________________________________________________________________________________________
Exercise 22 - Display Value Behaviour (Level & Status)
Display the level of the Mixing tank, and the status of the plant.
Objective:
-
Prerequisites:
1. Select and position a Windows Form Label control on the centre of the MixingTank.
2. Set the properties of the label as follows.
Property Value
Name lblTankLevel
AutoSize True
BackColor Web, White
3. Attached a Display Value behaviour on the label, browsing in the Data Element
4. Change the formatting to: Tank Level {0:F2} Kg
5. Create another 2 x Labels and set the following properties:

Property Value
Name lblStatus
AutoSize True
BackColor Gray
Font Arial, 14pt, Bold
Text Plant State
Property Value
Name cOStatus
BackColor Gray
Text Plant State
TextAlign TopCentre
___________________________________________________________________________________________________________________________
6. Select both labels and align their centres:
7. Assign a Display Value behaviour to the label cOStatus and assign the Data Element:
Adroit.StringList.ADT_JU_MX_BTCH_STAT.value
8. The formatting should be set to {0:N0}
9. Copy (with behaviours) and paste the Plant State labels and change the following properties:
Property Value
cOStatus1
Name cOBatchNumber
Text Batch Number
lblStatus1
Name lblBatchNumber
Text Batch Number
10. Change the Display Value behaviour to use the Analog Tag:
Adroit.Analog.ADT_JU_MX_BTCH_NUM.value
11. Save graphic form.
Notes:
___________________________________________________________________________________________________________________________
Exercise 23 - Visibility Behaviour
Make the heater element visible depending on the Batching

Objective: process stage.
-
Prerequisites:
1. In Shapes, Wizards & Examples, navigate to Static Graphics and browse to Heat Exchangers.
2. Drag the graphic Heat Exchanger 01 onto the graphic form.
Figure 101 Heat Exchanger 01
3. Rename the heater vector group to cOHeaterStatus

4. Size the Heat Exchanger to fit into the bottom of the tank.
5. Set the back colour of the heater to a suitable colour. For example Red.
6. On the Heater graphic add the Visibility behaviour, browsing in the Expression
Adroit.Expression.ADT_JU_MX_HTR_STATUS.value
7. Set Visibility to Visible as shown below.
Notes:
___________________________________________________________________________________________________________________________
Exercise 24 - Bind Behaviour
Displaying the actual Temperature by using a Gauge.

Objective:
-
Prerequisites:
1. Navigate to the Gauges menu within the Toolbox.

2. Select the CircularFullGuage and add to Batching Plant graphic form
Figure 102 Circular Full Gauge
3. Add a Bind behaviour to the Gauge.

4. Rename Behaviour Name to ‘Bind Min’.
5. Specify the Data Element Adroit.Analog.ADT_JU_MX_HTR_TEMP_ACT.engMin in the ‘From
Data Element’ textbox.
6. Create another Bind behaviour called ‘Bind Max’ and binding the Data Element
Adroit.Analog.ADT_JU_MX_HTR_TEMP_ACT.engMax to the MaxValue property of the gauge.
7. Create another bind behaviour called ‘Bind Value’ and binding the Data Element
Adroit.Analog.ADT_JU_MX_HTR_TEMP_ACT.value to the Value property of the Gauge.
Notes:
___________________________________________________________________________________________________________________________
Exercise 25 - Tooltip Behaviour
Add a Tooltip to the Gauge.

Objective:
-
Prerequisites:
1. Add a Tooltip behaviour to the gauge

2. Add the Data Element Adroit.Analog.ADT_JU_MX_HTR_TEMP_ACT.value
3. In the ToolTip Text Window. Enter the following text:
Batch Temperature {0:F2} °C
Note: to get the Celsius symbol hold the ALT Key and type in the number 0176
4. Click Finish.
5. Save the graphic from.
6. Toggle to Run mode and test.
Notes:
___________________________________________________________________________________________________________________________
Exercise 26 - Blinking Behaviour
Cause an object to blink under Alarm conditions.

Objective:
-
Prerequisites:
1. Add a Colour behaviour to the Label cOStatus
2. Select the Blink option in the colour behaviour.

3. Change the On colour to RED, the OFF and STOP colour to the same as the graphic for BackColor
(Gray)
4. Select the radial button “Started by Data Element” and browse in:
Adroit.Expression.ADT_JU_MX_ALM_STAT.value
Figure 103 Colour Behaviour, Blinking
5. Click Finish
6. Save and Run the graphic form.
Notes:
___________________________________________________________________________________________________________________________
Exercise 27 - Operator Behaviour [Part 1]
Switch between Automatic and Manual mode via the use of an

Objective: operator action behaviour.
-
Prerequisites:
1. Place a Windows Forms Button control on the graphic form with the following properties
Property Value
Name btnManAuto
Font Arial, 12, Bold
Text Auto/Man
AutoSize True
2. Assign a Display Value Behaviour to btnManAuto that it is connect to the Data Element
Adroit.Digital.ADT_JU_MX_AUT_MAN.textValue
3. Set the formatting to No Formatting {0}
4. Assign an Operator Action Behaviour to the button using the Data Element
Adroit.Digital.ADT_JU_MX_AUT_MAN.value
5. Set the Control Action of Toggle Boolean.
6. Click Finish.
7. Save and Run the graphic form
Notes:
___________________________________________________________________________________________________________________________
Exercise 28 - Operator Behaviour [Part 2]
Enabling the Operator to Start and Stop the Production of the

Objective: Batching Plant Project.
-
Prerequisites:
1. Position 3 Buttons on the Batching Plant graphic form with the following Properties:
Property Value
Name btnPlantStart
Text Start Plant
AutoSize True
Property Value
Name btnResetPlant
Text Reset Plant
AutoSize True
Property Value
Name btnAlmReset
Text Reset Alarm
AutoSize True
2. The Reset Alarm, Reset Plant and Start Plant buttons each have an Operation Action attached to ‘SET
BOOLEAN TRUE’ and assigned the appropriate Agent instances.
− Adroit.ADT_JU_MX_AUT_STRT.value to btnPlantStart
− Adroit.ADT_JU_MX_ALM_RESET.value to btnAlmReset
− Adroit.ADT_JU_MX_OPC_RESET.value to btnResetPlant
3. Create a copy of the ‘Batch Number’ labels as implemented in Exercise 16 by performing a ‘Copy with
Behaviours’ action. Change the object properties as follows.
Property Value
Name cOBatchNumberSP
AutoSize True
BackColor Gray
Text Batches to Run
___________________________________________________________________________________________________________________________
Property Value
Name cOBatchNumberSP2
BackColor Gray
Text Batch to Run
4. Change the display value behaviour to use the Analog Tag:

Adroit.Analog.ADT_JU_MX_BTCH_NUM_SP.value
5. Add an operator action as well to use the ‘Data Entry’ action, also using the
Adroit.Analog.ADT_JU_MX_BTCH_NUM_SP.value Data Element as input.
6. Close and Save, then test the changes.
Notes:
___________________________________________________________________________________________________________________________
Exercise 29 – Execute Command Behaviour
Driving values to a predefined template via the Execute Command.

Objective: Use a Counter Agent.
-
Prerequisites:
1. Navigate to Shapes, Wizards & Examples, Templates, Counter Faceplate Template.

2. Copy this Template and paste into Batching Plant, Templates Folder.
3. From the Toolbox, Vectors click and drop a Button onto the Batching Plant graphic form
Property Value
Name btnCounterFEDA
Text FED_A Counter
4. Size the button manually.

5. Select the Smart Tag ( ) on the button and add an Execute Command behaviour.
Figure 104 Execute Command
6. In the Graphic Form dialog box, browse in the Counter Template from the Templates folder.
7. Click Aliases tab, click the browse button in the Input dialog box and add
Adroit.Counter.ADT_JU_MX_FED_A_DAT
___________________________________________________________________________________________________________________________
8. Manually delete the slot value (in this case .onCount)
Figure 105 Execute Command - Aliases
9. Click Finish.
10. Save and Run the Operator to test.
Figure 106 Operator - Counter Agent
11. Create the button for Fed_B and test on the Operator.
Notes:
___________________________________________________________________________________________________________________________
13. Datalogging
We define data logging in the following way.
Data logging is the process of collecting and storing data over a period in order to analyse specific trends
or record the data-based events/actions of a system, network or IT environment. It enables the tracking
of all interactions through which data, files or applications are stored, accessed or modified on a storage
device or application
Examples of the types of information a data logging system can collect include temperatures, sound
frequencies, vibrations, times, light intensities, electrical currents, pressure and changes in states of
matter.
Adroit provides extensive and powerful historical logging facilities. As with scanning any slot of any Agent
can be configured to have its values historically logged.
When logged, the values are time-stamped and are made available via a DataLog Agent to any client.
Examples of data log clients would be historical Trends, the extract utility, OLE-aware 3rd Party applications
such as external spreadsheets for reports, and more.
Historical values can be stored in one or more data files, each file containing the values of one or more
DataLog Agent. The total amount of disk space required for data logging depends on the number of data
files used, the number of Agents being datalogged and the total number of values logged per Agent, as
well as the sampling time and length of time for which each value is logged.
During logging, each DataLog Agent will write to its own pre-allocated dynamic buffer area in a data file
and will overwrite itself after reaching the end of the buffer. A data log file is composed of many buffers,
one for each DataLog Agent. Being event-based, the speed at which each buffer is written depends on
how often the value in the Agent slot being logged changes according to its dead-band.
The data log file can be periodically archived. Either by using the System DataLog Agent which allows a
user to backup Datalogs to .CSV files on a scheduled or triggered basis, alternatively if necessary by file
copy, so that the historical data can be retrieved later and exported for further analysis as a Comma
Separated Variable (.CSV) file, a format recognised by many commercial spreadsheet and database
packages. If the System DataLog Agent is used, the Graphing utility in the Adroit Utilities folder is used to
display these backed-up files or opened up in Excel.
The Datalog Agent includes three slots:
Slot Type Description Function

The current value is logged to disk every time
LogNow Boolean (0/1) Demand Log
this slot makes the transition.
An optional tag configuration that is monitored
Trigger String (80 Chars) Demand Log Trigger for a zero to non-zero transition. When this
occurs, a log will take place.
A variable to control the mode of operation as
follows:
0 = Normal – change based logging only
Mode Integer (32 Bit) Mode
1 = Demand based logging only
2 = Demand and change based
logging
___________________________________________________________________________________________________________________________
14. Trends/Charts
Charting controls allow a user to report both live and historical data. Typically, the Line, Surface and XYPlot
charting controls are used to trend live data, while the Pie, Bar and Column charting controls are used to
report historical data.
Each charting control displays one or more series:
• BarChart: Each charted series is either a series of horizontal bars representing values or a
series of points that are usually connected to form lines.
• ColumnChart: Each charted series is either a series of vertical columns representing values or
a series of points that are usually connected to form lines.
• LineChart: Each charted series is a series of points that are usually connected to form lines.
• PieChart: Each charted series is a series of slices or segments to form a complete pie or circle.
Typically only one series can be used per chart.
• XYPlotChart: Each charted series is a series of points that are plotted from two sets of values,
one providing the X or horizontal coordinate and the other providing the Y or vertical coordinate
of each point.
Each series can display discreet (single valued), dataset and DataBinder data,
When logged, the values are time-stamped and are made available via a DataLog Agent to any client.
Examples of data log clients would be historical Trends, the extract utility, OLE-aware 3rd Party applications
such as external spreadsheets for reports, and more.
Historical values can be stored in one or more data files, each file containing the values of one or more
DataLog Agent. The total amount of disk space required for data logging depends on the number of data
files used, the number of Agents being datalogged and the total number of values logged per Agent, as
well as the sampling time and length of time for which each value is logged.
During logging, each DataLog Agent will write to its own pre-allocated dynamic buffer area in a data file
and will overwrite itself after reaching the end of the buffer. A data log file is composed of many buffers,
one for each DataLog Agent. Being event-based, the speed at which each buffer is written depends on
how often the value in the Agent slot being logged changes according to its dead-band.
The data log file can be periodically archived. Either by using the System DataLog Agent which allows a
user to backup Datalogs to .CSV files on a scheduled or triggered basis, alternatively if necessary by file
copy, so that the historical data can be retrieved later and exported for further analysis as a Comma
Separated Variable (.CSV) file, a format recognised by many commercial spreadsheet and database
packages. If the System DataLog Agent is used, the Graphing utility in the Adroit Utilities folder is used to
display these backed-up files or opened up in Microsoft Excel.
___________________________________________________________________________________________________________________________
Exercise 30 - Basic Datalogging (.LGD file)
Log an Agent so that the data can be displayed as a historical

Objective: trend.
-
Prerequisites:
1. Open the Agent Configurator window and select the Analog Agent ADT_JU_MX_MIX_TNK_LVL.
2. Click the Log button.
3. Ensure that the value slot is visible in the slot field.
4. Select the Mode that is required, in this case Continuous mode
5. In the Datasource dialog box, adjust the pathing that it reads the following:
C:\ProgramData\Adroit Technologies\Adroit\Configurations\JUICE\Datalogs\Target Temp
6. Select the length button and set it to 1 hour
7. Compression method set to Actual
8. Set the time button set to 1 second.
9. Make sure the start radial button is selected before clicking the OK button
Figure 107 Datalog Agent Configuration
10. Repeat the above process for the following Agents:

− ADT_JU_MX_FED_A_MASS_ACT
− ADT_JU_MX_FED_B_MASS_ACT
− ADT_JU_MX_PMP_MASS_ACT
− ADT_JU_MX_AGIT_TIME_ACT
− ADT_JU_MX_HTR_TEMP_ACT
___________________________________________________________________________________________________________________________
Exercise 31 - Displaying Logged Data in a Trend
Configure and Open a Trend view.

Objective:
An active Agent Server and Designer.

Prerequisites: An Analog that has been datalogged.
1. Create a new graphic form in the Juice/Batching Plant folder called Tank Level Trend.
3. From the toolbox, select the LineChart in the Data Group and place it on the new graphic form. The
Configuration: Line Chart Wizard will automatically display.
Figure 108 LineChart Configuration
4. Select the Values Tab in the series setup. In the Values field browse for the Data Element
___________________________________________________________________________________________________________________________
Figure 109 LineChart - Series Configuration
5. Change the series Title to Tank Level.

6. Click the finish button. To open the Line Chart configuration again, select Smart Tag ( ) and click
on the Edit Chart.
7. Change the Dock property of the LineChart to fill the graphic form.
8. Save and open the Tank Level Trend graphic form in the Operator to test.
9. Run the Batching Simulation OPC Server to see the value change.
Figure 110 Tank Level Trend
10. Open the Batching Plant Graphic Form and place a ‘Execute Command’ behaviour onto the actual tank.
11. The execute command behaviour must use the ‘Open graphic form’ action and then browse for this
‘Tank Level Trend’ graphic form as the form to open.
12. Specify Open As = Modal Form and Position = Center Screen.
13. Click Finish
14. Save and test.
___________________________________________________________________________________________________________________________
Notes:
___________________________________________________________________________________________________________________________
Exercise 32 - Retrieve Logged Data
Retrieving logged data via the Edit Datalog Agent window.

Objective:
-
Prerequisites:
1. Open the Agent Configurator and navigate to the Datalog Agent type (under Type:System), and select
the Agent the would require the information to be retrieved.
2. Edit said Datalog Agent and click the retrieve button
3. Retrieve a new set of data, by altering the period and rate and click the retrieve button
4. Click the export button and save the ensuing *.CSV file in
C:\ProgramData\AdroitTechnologies\Adroit\Configurations\Juice\CSV as Temp Target.csv
5. Run Excel and open the Temp Target.csv file
Notes:
___________________________________________________________________________________________________________________________
15. Wizards & Templates
15.1. Wizards
Wizards allow you to reuse the same graphical object and its assigned behaviours (if any), over and over
again, with different Data Elements, without having to recreate this object from scratch ever time. In other
words, a wizard is a reusable design-time object, much like a Windows control. In addition, wizards have
the facility to update their instances that have been added to graphic forms to their current configuration,
when they are modified after having been used.
A Wizard is a pre-drawn and/or pre-configured skeleton of graphical objects and their assigned behaviours
(if any), which has placeholders {substitutions} for Data Elements, which can simplify and speed up the
task of creating graphic forms. However, instead of directly specifying the values that drive these
behaviours, these are replaced with value or static text placeholders {substitutions}.
Each time a wizard is inserted into a graphic form, a dialog is displayed whereby values must be specified
for all the substitutions that occur within this wizard. For instance, instead of redrawing a pump or a motor,
each time one is required, a wizard can be created and simply inserted wherever a pump or motor is
needed, at which time you link the required Data Elements (values) to its pre-defined substitutions.
The main differences between a wizard and a graphic form:
• Wizards cannot be displayed in the Operator
• Wizards allow you to assign values to substitutions when they are pasted onto a graphic form
(which can be edited later too).
15.1.1. Creating a Wizard

Users can create their own unique wizards, which are drawn in the same way as other Graphics and can
be made up of primitive elements or complex cells. They can be drawn inside Wizard Graphic Forms and
dragged onto a Project graphic form. Wizards can be constructed from existing vectors and controls as
available
___________________________________________________________________________________________________________________________
Exercise 33 - Creating a Basic Dynamic Wizard [Method 1]
Construct a Dynamic wizard – Method 1.

Objective:
-
Prerequisites:
1. Right click on the Wizard sub folder in the Juice Project and select Create Wizard, naming the instance
MyWizard.
Figure 111 Wizards Folder, Juice Project
2. Set the wizards graphic form properties as follows

Property Value
BackColor User Defined
3. Place a windows form button on the screen with the following properties
Property Value
Name btnStart
BackColor Green
Text Start
Cursor Hand
Font Arial,10pt,Bold
Location 3;3
Size 90,44
4. Add a new Operator Action behaviour to the newly created button.

5. In the Data Element dialog box, type {Start Data Element} and set the control action to Set Boolean
True.
Note: {} donates substitution criteria.
___________________________________________________________________________________________________________________________
6. Click finish.
7. Right click on the Start Button and select Copy with Behaviours and paste alongside the original button
and changing the following properties.
Property Value
Name btnStop
BackColor Red
Text Stop
Cursor Hand
8. Edit the Operation Action behaviour on the Stop button, Change the Data Element to
{Stop Data Element} and click finish
9. Click Optimise Graphic Form Size on the graphic form menu as shown below:
Figure 112 Optimise Graphic Form Icon
10. Save and close the Wizard
Notes:
___________________________________________________________________________________________________________________________
Exercise 34 - Creating a Basic Dynamic Wizard [Method 2]
Construct a Dynamic wizard – Alternate method.

Objective:
-
Prerequisites:
1. Navigate to the Batching Plant graphic form, Select Feeder A and it’s Label, right click and select the
option Copy with Behaviours.
2. Create a new wizard called wzdConveyor under the Wizard’s folder within your project and paste the
copied Conveyor and label.
3. Modify the Label’s Text Property to read {EquipmentDesc}
4. Click yes to accept changes.
5. Access the colour behaviour as previously done in Exercise 12 , by browsing the Contents and selecting
Colour, right click for Edit Behaviour.
6. Enter the following substitution into the Data Element dialog box
Adroit.Digital.ADT_JU_MX_{EquipmentName}_{Signal}.value
7. Click Finish.
8. Click Optimise Graphic Form Size on the graphic form menu.
9. Save the Wizard.
10. Navigate back to the Batching Plant graphic form, delete Feeder A and it’s label, and replace the label
and feeder with the newly created wizard. (drag and drop from the Wizard folder), select Paste Wizard
Figure 113 Substitution Assignment
___________________________________________________________________________________________________________________________
Name Value
{EquipmentDesc} Ingredient A
(EquipmentName} FED_A
{Signal} STATUS
11. Repeat the above process for the second feeder

12. Save and test changes
Notes:
___________________________________________________________________________________________________________________________
Exercise 35 - Making use of a User Defined Wizard
Incorporate a User Defined wizard in a Project.

Objective: Wizard only appears when manual mode is active.
Predefined user wizard from either of the previous exercises.

Prerequisites:
1. Return to the Batching Plant graphic form and drag the wizard (MyWizard) that was created as per
the exercise above on to the Batching plant graphic form.
2. In the substation assignment window, browse in the following Data Element.
• Start Data Element: Adroit.Digital.ADT_JU_MX_AGIT_START.value
• Stop Data Element: Adroit.Digital.ADT_JU_MX_AGIT_STOP.value
3. Click Finish.
4. Using the Smart Tag ( ) of the wizard group, attach a visibility behaviour.
5. Link the Data Element Adroit.Digital.ADT_JU_MX_AUT_MAN.value to the behaviour, selecting the
radial button “Visible”.
6. Click Finish and Save the graphic form.
7. Copy the Wizard and apply the applicable Stop and Start Tags for the Water Pump. (only to be visible
in Manual mode)
Notes:
___________________________________________________________________________________________________________________________
15.2. Templates
Templates are reusable graphic forms that can be used at run-time. The fundamental difference between
a graphic form and a Template is that a Data Element within a Behaviour or the spider configuration view
can be driven dynamically by using {} notation, in the following instances:
• When configuring Behaviours: for any Data Element field, you can specify the required name
enclosed in { } braces, which is automatically linked via a Variable Data Element spider to this
Data Element property of this behaviour.
• In the Properties view: for any String or Text properties, you can specify the required name
enclosed in { } braces, which is automatically linked via a String Format spider and a Variable
Data Element spider to this String property.
___________________________________________________________________________________________________________________________
Exercise 36 - Creating a Template [Part 1]
Incorporate a User Defined template in a Project.

Objective: Template only appears when the object is selected.
Link Multiple Templates.
-
Prerequisites:
1. Browse to the Templates folder in the Juice project and create a graphic form called SetPoints and
Targets.
2. Create a Windows Form label with the following properties.
Property Value
Name lblHeading
Font Arial,18,Bold
Text {EquipmentName}
TextAlign MiddleCentre
3. Click Yes
4. Place the Heading label in the top of the graphic form.
5. Below the Heading place 2 x Labels on the left with the following properties.
Property Value
Name lblActMass
AutoSize True
Font Arial,12,Bold
Text Actual
TextAlign MiddleLeft
Property Value
Name lblTgtMass
AutoSize True
Font Arial,12,Bold
Text Target
___________________________________________________________________________________________________________________________
6. On the lblActMass label, place a Display Value behaviour with the following substitution:
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_ACT.agentDescription
Note: For each instance of this template, the { } implies that the actual description will be displayed per device.
7. The label named lblTgtMass requires the following substitution to be added with a Display Value
behaviour:
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_TGT.agentDescription
8. To the right of the 2 Labels, add 2 Textbox objects.
Each text box will have the following properties:
Property Value
Name TBoxActMass
Property Value
Name TBoxTgtMass
9. TBoxActMass will use the substitutions for a Display Value behaviour:

Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_ACT.value
10. TBoxTgtMass will use the following:
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_TGT.value
• Substitutions for a Display Value behaviour
• Operator Action Behaviour with a Data Entry Action Type:
Note: in this case, the String Formatting implies that the word Target will be displayed with the actual values per device.
11. To the right of these Labels place another 2 x Labels with the following properties:
Property Value
Name lblActUnit
AutoSize True
Font Arial,12,Bold
Text unit
Property Value
Name lblTgtUnit
___________________________________________________________________________________________________________________________
AutoSize True
Font Arial,12,Bold
Text unit
12. On the lblActUnit label, place a Display Value behaviour with the following substitution:
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_ACT.unit
13. On the lblTgtUnit label, place a Display Value behaviour with the following substitution:
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_TGT.unit
Note: This substitution implies that the actual unit of measure will be displayed per device.
14. Place 2 x Buttons below with the following Properties:

Property Value
Name BtnTrend
Font Arial,12,Bold
Text Trend
TextAlign MiddleCenter
Size 310, 42
Property Value
Name BtnClose
Font Arial,12,Bold
Text Close
TextAlign MiddleCenter
Size 310, 42
15. Align both buttons as per the image
Figure 114 Actual and Target Template
16. Click Optimise Graphic Form Size on the graphic form menu as shown below
Notes:
___________________________________________________________________________________________________________________________
Exercise 37 - Creating a Template [Part 2] – Display Actual/Target Values
Display Actual/Target for Agitator, Heater and Pump using a single

Objective: Template.
-
Prerequisites:
1. Navigate to the Batching Plant graphic form.

2. Add an Execute Command behaviour to Agitator, linking it to the SetPoints and Targets Template.
3. In the Aliases tab of the Execute Command you would need to enter the following:
• EquipmentName = AGIT
• Signal = TIME
4. Click Finish.
5. Repeat the same process for the Water Pump implementing the correct aliases.
• EquipmentName = PMP
• Signal = MASS
6. Repeat the same process for the Heater implementing the correct aliases.
• EquipmentName = HTR
• Signal = TEMP
7. Save all graphic forms and test within the Operator.
Notes:
___________________________________________________________________________________________________________________________
Exercise 38 - Creating a Template [Part 3] - Trend Button
Display the Trend for Agitator, Heater and Pump using one
-
Prerequisites:
1. Create a graphic form called Trend in the Templates Folder

2. On the graphic form place a trend and in the values tab of trend configuration place the substitution
Adroit.Analog.ADT_JU_MX_{EquipmentName}_{Signal}_ACT.value in the Values dialog box
Figure 115 Trend Values Tab Substitution
3. Browse to Title set up and disable Title style.

4. Browse to Legend set up and disable Legend style.
5. Click finish and optimize graphic form size.
6. Click Save.
7. On the SetPoints and Targets graphic form, link the Trend button via the Execute Command
behaviour to the Trend template.
8. Under the Alias tab of the Execute Command, ensure that the check box Use parent form Alias
values is checked.
9. Click Finish
Notes:
___________________________________________________________________________________________________________________________
Exercise 39 - Creating a Template [Part 4] - Close Button
Close the pop up window for Agitator, Heater and Pump using one
-
Prerequisites:
1. On the SetPoints and Targets graphic form, link the Close button via the Execute Command
behaviour to close the window.
Figure 116 Execute Command Behaviour Configuration
2. Save graphic form and test
Notes:
___________________________________________________________________________________________________________________________
16. System Events
16.1. What is an Event?
Events represent normal system status messages, and do not require an operator response. An event is
defined as a detectable occurrence, which may or may not be associated with an alarm.
Simple example of Event in Industrial automation can be simple logging of Operator with his username to
the SCADA application. The SCADA system can log that event in text file if configured to do so.
Adroit constantly monitors the process to detect undesirable states, process values and the malfunctioning
of Devices. Any significant occurrences are recorded in the Event Log and may be displayed using a Chart.
Each line in the log shows information pertaining to one event
___________________________________________________________________________________________________________________________
Exercise 40 - Adding a Tab Control
To add a Tab Control to the Batching Plant graphic form.

Objective:
-
Prerequisites:
1. Navigate to the Batching plant graphic form

2. From the Windows Forms menu in the Toolbox, select TabControl and draw it at the bottom of the
graphic form.
3. Select to dock the TabControl to the bottom for the graphic form.
4. In the properties, Advanced section, select and browse the property TabPages
5. Add / Modify 2 x TabPages and configure the properties as follows.
Members Name Text

tabPage0 tpgAlarms Alarms
tabPage1 tpgEvents Events
Note: It is also possible to add Trends to this Tab Control
6. Save Graphic From
Notes:
___________________________________________________________________________________________________________________________
Exercise 41 - Event View Window
Open an Event graphic form.

Objective:
-
Prerequisites:
1. In the Enterprise Manager, right click on the Datasources.

2. Add an Event Log Datasource called System Events
3. Test the connection and click Finish
4. From the Toolbox, select the EventViewer (under the Adroit group) and place the control on the tab
page tpgEvents.
5. Dock the event viewer to fill on the Tab Control page called Events
6. Save graphic form and test
Notes:
___________________________________________________________________________________________________________________________
17. Alarms
17.1. What is an Alarm?
According to the EEMUA 191 guidelines, an alarm is an event to which an operator must react, respond
and acknowledge. An alarm system should alert the operator to abnormal situations and assist with the
management of the abnormal situation.
Example could be as follows; Suppose a Tank water level has increased beyond the desired value and that
time SCADA system should give Alarm.
Any Tag in Adroit can be alarmed and individually routed to one or more Alarm Agents. Alarm Agents are
set up to “direct” the alarms to various outputs including but not limited to Alarm Lists, Event Logs,
Databases, Files, Cell phones, Multimedia Files, etc.
These Alarm Lists may be resident on the local machine or on any Adroit networked machine. Further,
the alarms may be routed to other audio or visual alerts can be implemented and configured which will
inform an operator or other Adroit user as to a fault condition:
• By multicolour behaviour in graphical picture elements;
• By multitext messages in picture elements;
• Via displays listing active unacknowledged and acknowledged alarms;
• Directly onto hard copy printout;
• As records within the event log;
• By the activation of audio devices;
• Popping up of a process-specific page of hypertext help.
These visual and audible means of communicating the presence of an alarm condition to the operator are
controlled by Alarm Agents that are linked by the user to those process Agents he wishes to monitor. An
alarm is triggered when one or more of the configured status mask bits in an Alarm Agent match any
status bits in the Agent being monitored.
___________________________________________________________________________________________________________________________
17.2. Alarm Type
Trigger conditions will have been predefined by the user. Together with the process data to be reported
back for each alarm type, which would then have been applied, to the Agent being monitored.
Figure 117 Alarm Type
This information is routed by the Alarm Agent to the relevant output and display mechanisms, whether
this is an alarm list, printer, audio device or event log.
Figure 118 Alarm Server
The alarm type name, which is reported in the Alarm List display can be specified by the user to describe
the alarm condition, which when coupled with the appropriate choice of reported data, will enable the
operator to diagnose the problem easily.
Picture elements may directly display the alarm state of an Agent by reading its status bits directly, without
using the Alarm Agent routing mechanism. The statusAlarmsUnacked and statusAlarmsActive bits will
show the unacknowledged and active states as set by the Alarm Agent. In this way any situations ranging
from plant upsets or process variable excursions to failures within Adroit itself can be monitored.
___________________________________________________________________________________________________________________________
In order to implement an alarm strategy for an application, the user must decide which process values
need to be monitored and which alarm types need to be created to do the monitoring
17.3. Configuring the Alarm Agent Instance

The defaultAlarmAgent Alarm Agent is created by Adroit Ignite HMI when a blank or empty Adroit database
(*.WGP) file is loaded. This Alarm Agent provides 4 alarm routes, which should be used to route the
following incidents:
DO NOT USE route 0 or 1, as these should ONLY be used by Adroit.
Route 0/1: a predefined Adroit system route used for system alarms such as software faults and
communication errors and provides the following alarm destinations: The alarm list of this Alarm Agent,
so these incidents can be viewed in an Alarm List Viewer window that is connected to the
defaultAlarmAgent.
• The default Beeper Agent, aBeeper, which uses the PC speaker to audibly alert users to these
active alarms.
• The default EventLogging Agent, EventLog, which records these active alarms to the Windows
Application event log on the Agent Server computer. These events can be viewed in an Event
Log viewer window on this computer.
Route 2: this route is intended for reporting the active process incidents that need to be responded to,
repaired and acknowledged by the operator e.g. a tank level reaches a high level.
Route 3: this route is intended for reporting the active process events that is provided for information
only e.g. if a set point value has changed.
Route 4: this route is intended for reporting via SMS, the active process incidents that is responded to,
repaired and acknowledged by the operator.
___________________________________________________________________________________________________________________________
Exercise 42 - Configuring Alarm Routes
Create various Alarm Routes according to an Alarming Strategy.

Objective:
-
Prerequisites:
1. Open the Agent Configurator.

2. Select Advanced Agent filter
3. Select Agent Type Alarm.
4. Find and edit the defaultAlarmAgent
Figure 119 Configuration Edit Alarm Agent
5. On Route 2 add a new AlarmList Agent Instance named ADT_JU_MX_ALM_LST_INCIDENTS with

the description Batching Plant Alarms for Route 2
a. Click on the folder with the star in the top left corner
b. Click the Add button
c. And enter the TagName and Description as shown below
d. Click ok and then select the newly created alarm list and click OK again
___________________________________________________________________________________________________________________________
Figure 120 Adding an Agent “on the Fly"
6. Delete the aBeeper.start Tag and add a new instance named: ADT_JU_MX_BEEPER with a
description: Batching Plant Alarms for Route 2
7. Browse for a new Output event to Route 2 of the DefaultAlarmAgent.
8. Add the instance of the EventOutput called ADT_JU_MX_PRINTER and the description as Route 2
Alarm Printer.
Note: set up for the printer would be require if using this EventOutput
Figure 121 Configured Alarm Route
___________________________________________________________________________________________________________________________
9. Select Route 3
10. Add an AlarmList Agent instance named ADT_JU_MX_ALM_LST_EVENTS with a description
Batching Plant Events for Route 3
11. Browse for a new Output event to Route 3 of the DefaultAlarmAgent.
12. Click OK
Notes:
___________________________________________________________________________________________________________________________
17.4. Alarming an Agent Instance
In principle, any Agent can be alarmed. These Agents will typically be collecting information by scanning
front-end Devices or subscribing to the slots of other Agents. To be successfully monitored by an Alarm
Agent, the following must first be determined:
• Decide which alarm type to use and which status bits will flag the alarm condition
• Decide the Agent’s individual alarm priority
• Choose an Alarm Agent to monitor its status bits
• Select the alarm types available in the chosen Alarm Agent
• Select the desired routes defined for the alarm type
• Decide which alarm types are to be acknowledgeable
Agent Alarm Incident Event

Agent Mask Condition
Type Type Route 2 Route 3
Analog ADT_JU_MX_HTR_TEMP_ACT Hi Contents Hot Yes No
Lo Contents Cold No Yes
Analog ADT_JU_MX_MIX_TNK_LVL Hi Mix Tank Full Yes No
Lo Mix Tank Empty No Yes
Counter ADT_JU_MX_PMP_DAT onCount Overrun No Yes
___________________________________________________________________________________________________________________________
Exercise 43 - Setting up Alarm Masks
Alarm Agent instances according to a pre-determined Alarming

Objective: Strategy.
-
Prerequisites:
1. Open the Agent Configuration window.

2. Select the Analog Agent instance called ADT_JU_MX_TEMP_ACT.
3. Click the Alarm button.
Figure 122 Alarm Configuration
4. Ensure that the Alarm Agent instance is correct, defaultAlarmAgent.

5. Create the Alarm Type required by clicking on the add button.
6. Name the new mask, Contents Hot.
7. Check the High check box.
8. From the Reported Data, select the following from the Available list: Value, hi, and Unit slots and make
each Current.
___________________________________________________________________________________________________________________________
Figure 123 Configuring Alarm Types
9. Click the OK button. From the Alarming dialog box, select the Available mask Contents Hot and move
it to the Current side.
10. Ensure that they are associated with Route 2 (as previously configured)
11. Click the OK button.
12. Complete all the Alarm Strategy requirements as per the above Table.
Notes:
___________________________________________________________________________________________________________________________
17.5. Alarm List Viewer Control
This control Adroit Alarm List Viewer window Control: -
• Displays the active alarms within the alarm list of an Alarm or AlarmList Agent.
• Provides the means to acknowledge individual alarms either locally or globally.
• This functionality can also be intentionally disabled (for security reasons).
• Provides the means to limit the number of alarms that are displayed.
• Represents alarms as coloured entries within a list, whose foreground (text) and background colour
combination, represents the state of each alarm.
Figure 124 Alarm Viewer Control
___________________________________________________________________________________________________________________________
Exercise 44 - Setting up Alarm View Windows
Display the Batching Plant Alarms.

Objective: Separate the Incidents from the Events.
A configured Alarm Agent Instance.

Prerequisites: Alarmed Agent Instances.
1. On the Batching Plant graphic form, select the tab page Alarms in the TabControl window.
2. Drag the AlarmViewer, from the Adroit Folder in the Toolbox, onto the tab page
3. Set the properties of the Alarm Viewer as follows:
Property Value
AlarmGlobalAcknowledgedButtonWidth 150
AlarmlocalAcknowledgedButtonWidth 150
Dock Full
4. Select the Alarm Viewer Task Menu via the Smart Tag ( )
Figure 125 AlarmViewer Tasks
5. Click On General Configuration.

6. On the drop down menu for Alarm Type, select AlarmListAgent.
7. Then, browse in the AlarmList ADT_JU_MX_ALM_LST_INCIDENTS
8. Click Finish and Test.
Notes:
___________________________________________________________________________________________________________________________
17.6. What is the difference between Alarms and Events?
Alarm and Event are both Notifiers and are used to notify or inform about any important Alarm or event
that has occurred or is occurring in present in an Industry.
1. Alarm: Alarms represent warning of process conditions that could cause problems and require an
operator response.
a. Example, suppose a Tank Water level has increased beyond the desired value and at that time
the SCADA system should give an alarm
The intention of an alarm is to signal that something has gone wrong, or that a particular stage
of processing has been reached.
2. Event: Events represent normal system status messages, and do not require an operator response.
An event is defined as a detectable occurrence, which may or may not be associated with an alarm
a. Simple example of Event in Industrial automation can be simple logging of Operator with his
username to the SCADA application. The SCADA system can log that event in text file if
configured to do so.
___________________________________________________________________________________________________________________________
18. Navigation
There are several different navigation strategies that can be created.
Every project contains a collection of windows. These windows are the fundamental building blocks for
your projects, containing the hierarchy of components. Components are what we refer to as the visual
elements that range in complexity from a single button and label to the chart and table components.
The first part to consider when setting up navigation for the project is what windows would open on start-
up. This is generally the overview page of the project, as these shall be the first things that the user will
see. In a typical navigation strategy, two windows open on start-up; one docked and one main window
(filling the rest of the space). From these windows, other windows can be opened and closed.
___________________________________________________________________________________________________________________________
Exercise 45 – Navigation [Part 1]
Open and navigate around the graphic forms.

Objective:
-
Prerequisites:
1. Right Click on Landing Folder and select Create Graphic Form (Styled), naming it Landing Page.
Figure 126 Enterprise Manager Project – Landing
2. From the Toolbox menu, select Templates.

3. Select and position a TemplateGONavToolbar on the Landing graphic form.
4. Set the properties of the TemplateGONavToolbar to the following:
Property Value
Name MainNavigation
Dock Fill

6. Select the Smart Tag ( ) to access the available tasks of the TemplateGONavToolbar.
7. Select the appearance option “Browse for Toolbar Graphics Forms”.
8. Select Add Menu.
9. Rename the Toolbar Item Text to DateTime.
10. Click OK.
11. Click Finish.
12. Using the Properties window, select the control mnuTGO_DateTime from the MainNavigation
dropdown box.
___________________________________________________________________________________________________________________________
13. Open the Behaviour ribbon and select the Display Value behaviour on the Menu ribbon.
Figure 127 Behaviour Menu – Display Value
14. Browse for the Input Data Element:

Adroit.AgentGroup.SystemInformation.systemInfo.currentTime
15. Set the String Formatting to {0}
16. Click Finish.
17. Using the Properties window, select the control mnuTGO_DateTime from the MainNavigation dropdown
box.
18. Select the Alignment property from the Advanced Menu and set it to Right.
20. To test, toggle the graphic form from Design to Run mode.
Note: Always refer to the when additional information is required.
Notes:
___________________________________________________________________________________________________________________________
Exercise 46 - Navigation [Part 2] - Adding Menu Items and Graphic Forms
Adding menu items and graphic forms.

Objective:
-
Prerequisites:
1. Via the Smart Tag ( ) of the TemplateGONav, select Browse for Toolbar Graphic Forms
2. Add a menu item and call it Batching Plant.
3. Click Add GF and browse in the Batching Plant graphic form.
4. Browse in the Batching Plant graphic form.
5. Click finish.
6. Select the graphic form in the list and move it accordingly that it sits below the menu item called
Batching Plant. (Highlight the graphic form under the Toolbar Item Text….select Right)
7. Click right, to enable to become an item of the Batching plant Menu
Figure 128 Graphic Form Toolbar Setup
8. Click finish, save graphic form and run.

9. Repeat the process for all graphic forms added.
Notes:
___________________________________________________________________________________________________________________________
Exercise 47 - Navigation [Part 3] - Add a Default Graphic on Home Page
Adding graphic forms to Load.

Objective:
-
Prerequisites:
1. Create a new graphic form named Home in the Landing Folder.

2. Edit the graphic form Home and place a Windows Forms PictureBox on the graphic form with the
following properties.
Property Value
Name Logo
Image User to supply own image or logo
SizeMode AutoSize
3. Save the Home graphic form.
4. Navigate back to the Landing Page graphic form and Via the Smart Tag ( ) of the TemplateGONav,
select the option Browse for Default Graphic Form to Load.
5. Browse in the graphic form Home.
6. Save and Test.
Figure 129 TGONavToolbar in Run Mode
Notes:
___________________________________________________________________________________________________________________________
19. Operator Settings
User Profiles can customize the default display and permitted user interaction within the Operator window.
Browse to:
Right click on Default and select Configure
Figure 130 Adroit Operator Profile Configuration
19.1. Customizable Operators Settings & Configuration

• AllowEditTags: this setting applies, when linking Tags from Adroit datasources to controls and
vectors of graphic forms. In this case, this option determines whether your Operator users have
the ability to edit the exposed Adroit Tags, which are displayed either through the use of Show
(All) Information or the Bad Tag status indicators. For details on these Tag exposing mechanisms
• AlwaysOnTop: to enable or disable the initial display of the Operator window to be above all
other applications. By default, this is disabled (False).
• CanClose: to allow users to close the Operator window (True) or not (False).
___________________________________________________________________________________________________________________________
• DefaultGraphicFormLevel: to select which level is initially displayed by the graphic form,
specified by the DefaultGraphicFormPath setting.
• DefaultGraphicFormPath:to select the default graphic form that is displayed when the
Operator window opens
• DefaultGraphicFormTemplateSet: to select which template set is initially activated in the
graphic form, specified by the DefaultGraphicFormPath setting.
• FullScreen: to display the title bar at the top of the Operator window (False) or not (True).
• ShowContextMenu: to allow users to display the right-click menu in the Operator window
(True) or not (False).
• ShowMaximize: to allow users to maximize the Operator window (True) or not (False).
• ShowMinimize: to allow users to minimize the Operator window (True) or not (False).
• StartupBorderStyle: to specify the window type used for the graphic forms, which determine
how users can interact with each graphic form window.
• FixedToolWindow: Similar to FixedSingle, except it is a dockable window that you are unable
to resize.
• SizableToolWindow: Similar to Sizable, except that it is a dockable window.
• StartupLocation: to MANUALLY set the location of the Operator window on the screen, by
specifying the required position of the top left corner of the window in pixels.
• StartupSize: to set the maximum dimensions of the Operator window on the screen, by
specifying the required window size in pixels.
• StartupWindowPosition: to set the location of the Operator window on the screen, by
selecting one of the pre-set system-dependent start up positions.
• StartupWindowState: to select the initial state of the Operator window - in other words
should this window be maximized, normal or minimized.
___________________________________________________________________________________________________________________________
Exercise 48 - Adding a Default Graphic Form to the Operator
Enable the Operator to start up with a specified graphic form.

Objective:
-
Prerequisites:
1. Via the Enterprise Manager, Management, Profile, access Default by right clicking on it and selecting
the option Configure.
2. On the right-hand pane, select Operator Settings.
3. Click on the dialog box for DefaultGraphicFormPath, and then select the browse button.
4. Browse in the Landing Page graphic form.
5. Click Finish and select Save Server Data in the Home menu.
6. Test by opening the Operator.
Figure 131 The Operator Default Screen with logo and text
Notes:
___________________________________________________________________________________________________________________________
20. Ignite Utilities
Utilities has been added to provide a central location from which the installed utilities can be launched,
instead of installing a host of separate shortcuts for each individual utility. This shortcut is also installed
on the Desktop. This application also describes their supported command line options and by right
clicking the utility you can specify which command line options you want to use when launching the
utility.
Figure 132 Utilities
20.1. Adtech Licensing Utility

The Adtech Licensing Utility allows a user to get, View and/or update your Adroit Ignite HMI product
license. A user can typically launch the Licensing Utility via the Ignite Utilities Icon on the desktop and
then select the utility from the menu.
Only the Agent Server and/or Ignite Server, require a licence, all other applications such as the Designer,
Operator and etc do not.
Figure 133 Adtech Licensing Utility
___________________________________________________________________________________________________________________________
20.2. Agent Browser
The Agent Browser is a utility that allows one to browse the configured Tags within an Agent Server to be
viewed and selected if required for configuration purposes. This also displays status slot names and Tag
(Agent.slot) values and, if the necessary command line option is provided, these Tag values can be
modified.
Figure 134 Agent Browser
20.3. OPC Browser

By launching this utility you can browse and connect to any OPC Server. Very useful to test with and
problem solving.
Figure 135 OPC Browser
___________________________________________________________________________________________________________________________
20.4. OPC Server
The Adroit OPC Server is OPC 2.0 compliant and exposes each Tag in an Agent Server as an I/O to an
OPC client Application. When the OPC Server starts it is added to the system tray, in the bottom right of
the screen.
20.5. Scanning Monitor

This tool monitors the communications to and from front-end devices, such as PLCs, RTU’s etc. (the Adroit
scanning subsystem), obtaining the necessary data, so that the communications can be manually tuned
to achieve optimal performance.
Figure 136 Adroit Scan Configuration Monitor
• The Scanning Monitor utility is designed to provide information on the scanning

(communications) configuration for a particular Agent Server to and from its configured front-
end devices, such as PLCs, RTU’s etc. The provided information can then be used to manually
fine-tune the scanning subsystem to achieve optimal performance.
• This utility consists of following three hierarchically arranged list boxes, each of which expose
increasingly detailed communication information for the selected Agent Server:
• The device list, which displays all the devices that have been configured in the *.WGP file of the
selected Agent Server and will ONLY list the devices, which have been used to scan Tags within
the current project that is running on the Agent Server, even though other devices may have
been added and configured on the machine.
• The scan job list, which displays the scan jobs for the selected device or devices. Scan jobs are
automatically created by Adroit to group the scanned Tags together in such a way as to minimize
scanning load and to maximize throughput.
• The Tag list, which displays the Tags (scan points) grouped within the selected scan job or jobs.
• In addition to these lists, the Servers combo box and the Connect… button can be used to
specify the Agent Server whose scanning configuration is to be monitored.
20.6. Driver Monitor

When troubleshooting potential driver problems, it is essential to understand exactly how the specific
device of an installed driver is communicating between Adroit and the specified front-end device.
Adroit Ignite HMI provides a utility known as the Driver Monitor that is used for just this purpose and one
of its functions allows it to display the Datascope window, which allows you to view and log the exact
communication messages and errors as they occur between Adroit and the specified front-end device.
___________________________________________________________________________________________________________________________
This procedure describes how to create an HTML log file of the communication messages and errors as
they occur between Adroit Ignite HMI and the specified front-end device. So that if you are not a driver
expert, you can email this log file to Adroit support, who will then be able to assist you with your driver
problem.
The advantage of an HTML log file over a text file is that this file format preserves the colour of the
Datascope window, which makes the troubleshooting process easier.
The driver Monitor Launcher can be activated from the Diagnostics & Tools menu in the Designer.
Figure 137 Driver Monitor Launcher
20.7. Scheduler
Commands and utilities can be scheduled to run today, tomorrow, or on a particular day of the week or
month at a specified time using the Scheduler. Typical examples of its use would be printing a report,
archiving a file, starting a backup procedure, extracting logged data or doing a Putslot operation.
Figure 138 Scheduler – All users
___________________________________________________________________________________________________________________________
20.8. Script Editor
This Script Editor is usually launched from the Script Agent so that their VB Script files can be edited.
It allows the concurrent editing of the following script file types: Script Agent VB Script files (*.BAS)
Figure 139 VB Script Editor
___________________________________________________________________________________________________________________________
21. System Backup and Restore
Exercise 49 - Project Backup
Create a Backup of the Project configuration

Objective:
-
Prerequisites:
1. Open the Config Editor, browse to the System Back Up and Restore
2. Select the Backup option.
Figure 140 System Back Up Window
3. Select the destination to save the backup to and give the file a name i.e. Juice_Backup
4. Click the backup button and allow the process to run.
Notes:
___________________________________________________________________________________________________________________________
Exercise 50 - Project Restore
Restoring from a backup.

Objective:
-
Prerequisites:
1. From Configuration in the Ignite Config Editor, Create/select the configuration that you shall be
restoring to.
2. Click the Restore option.
3. Click the browse button to the right of the edit box and specify the required .ZIP backup file.
4. Click the Restore button to OVERWRITE all the currently specified system files and settings, of this
Configuration, with those stored in the backup.
Figure 141 System Restore Project Window
___________________________________________________________________________________________________________________________
Figure 142 System Restore Details
Note: Ensure that the name of the active (currently loaded) Configuration is the SAME as the name of the Configuration that you
have backed up, to minimize the potential for incorrect paths.
5. Click Finish.
Notes:
___________________________________________________________________________________________________________________________
22. Batch Plant I/O Schedules
22.1. Analog Agents
ADT_JU_MX_AGIT_TIME_ACT Actual Mix Time 0 100 0 100 sec 100 100 0 0 ActualMixTime No
ADT_JU_MX_AGIT_TIME_TGT Target Mix Time 0 100 0 100 sec 100 100 0 0 TargetMixTime Yes
ADT_JU_MX_BTCH_NUM Batches per shift 0 100 0 100 100 100 0 0 BatchNumber No
ADT_JU_MX_BTCH_NUM_SP Batches to Run 0 100 0 100 100 100 0 0 NumBatches Yes
ADT_JU_MX_FED_A_MASS_ACT Ingredient A Powder Feeder 0 100 0 100 Kg 85 70 35 20 IngMassA No
ADT_JU_MX_FED_A_MASS_TGT Ingredient A Powder Target 0 100 0 100 Kg 85 75 35 20 IngTargetA Yes
ADT_JU_MX_FED_B_MASS_ACT Ingredient B Powder Feeder 0 100 0 100 Kg 85 70 35 20 IngMassB No
ADT_JU_MX_FED_B_MASS_TGT Ingredient B Powder Target 0 100 0 100 Kg 100 100 0 0 IngTargetB Yes
ADT_JU_MX_HTR_TEMP_ACT Heat Temperature Actual 0 4096 0 45 °C 45 35 15 0 ActualMixTemp No
ADT_JU_MX_HTR_TEMP_TGT Heat Temperature Target 0 4096 0 45 °C 45 35 15 0 TargetTemp Yes
ADT_JU_MX_PMP_MASS_ACT Water Mass Actual 0 100 0 100 Litres 85 70 35 20 IngMassH20 No
ADT_JU_MX_PMP_MASS_TGT Water Mass Target 0 100 0 100 Litres 100 100 0 0 IngTargetH2O Yes
ADT_JU_MX_VLV_RATE Outlet Valve Flow Rate 0 100 0 100 Kg/s 100 100 0 0 DischRate Yes
ADT_JU_MX_VLV_TIME Discharge Time 0 100 0 100 s 100 100 0 0 ActualDischTime Yes
_______________________________________________________________________________________________________________________________________________________________________________
22.2. Digital Agents
OFF ON
Name Description Output Enabled OPC Address
state state
ADT_JU_MX_AGIT_START Agitator Manual Start OFF ON Yes StartAgitatorMan
ADT_JU_MX_AGIT_STATUS Mixer Motor Stopped Running No AgitatorRunning
ADT_JU_MX_AGIT_STOP Agitator Manual Stop OFF ON Yes StopAgitatorMan
ADT_JU_MX_ALM_RESET Reset OPC alarms OFF ON Yes AlmReset
ADT_JU_MX_AUT_MAN Automatic / Manual Automatic Manual Yes ManAuto
ADT_JU_MX_AUT_STRT Start OPC OFF ON Yes AutoStart
ADT_JU_MX_FED_A_STATUS Ingredient A Powder Feeder OFF ON No FeedARunning
ADT_JU_MX_FED_B_STATUS Ingredient B Powder Feeder OFF ON No FeedBRunning
ADT_JU_MX_OPC_RESET Reset OPC OFF ON Yes PlantReset
ADT_JU_MX_PMP_MAN_STP Stop in Manual OFF ON Yes StopPumpMan
ADT_JU_MX_PMP_MAN_STRT Start in Manual OFF ON Yes StartPumpMan
ADT_JU_MX_PMP_STATUS Water Pump OFF ON No PumpRunning
ADT_JU_MX_PMP_TRIP Water Pump Alarm OFF ON No PumpTrip
ADT_JU_MX_VLV_ALM Discharge Valve Alarm OFF ON No DischargeAlm
ADT_JU_MX_VLV_STAT Outlet Valve OFF ON No DischValveOpen
_______________________________________________________________________________________________________________________________________________________________________________
22.3. StringList Agent
Name Description Index String Scan

OPC Address
0 STOPPED
1 BATCHING
2 MIXING
ADT_JU_MX_BTCH_STAT Plant Phase 3 HEATING Status
4 DISCHARGING
5 BATCH COMPLETE
8 OPC ALARM
22.4. Expression Agents

Expression = v1 == 8 ? 1 : 0
ADT_JU_MX_ALM_STAT Alarm Status
Expression = v1 == 3 ? 1 : 0
ADT_JU_MX_HTR_STATUS Heater Status
V04 = ADT_JU_MX_VLV_RATE.value
ADT_JU_MX_MIX_TOTL_MASS Tank level Calculation
22.5. Counter Agents

Name Description Input Tag Triggered Trigger
ADT_JU_MX_AGIT_DAT Agitator Data ADT_JU_MX_AGIT_STATUS.value ✓ systemInfo.second
ADT_JU_MX_FED_A_DAT Ingredient A Feeder ADT_JU_MX_FED_A_STATUS.value ✓ systemInfo.second
ADT_JU_MX_FED_B_DAT Ingredient B Feeder ADT_JU_MX_FED_B_STATUS.value ✓ systemInfo.second
ADT_JU_MX_HTR_DAT Heater ADT_JU_MX_HTR_STATUS.value ✓ systemInfo.second
ADT_JU_MX_PMP_DAT Water Pump ADT_JU_MX_PMP_STATUS.value ✓ systemInfo.second
___________________________________________________________________________________________________________________________
23. Adroit Ignite HMI Competency Test (Optional)
23.1. Introduction
The purpose of this Adroit Ignite HMI Configuration Competency Test is to evaluate your competency
in configuring the basics of the product. Although we are not testing how well you can draw pictures
or prescribing how you should achieve something, we also understand that there is neither a correct
nor an incorrect way of achieving the objective. In the real-world engineers, have different approaches
and philosophies when it comes to engineering a project.
23.2. Procedure, URS and Process Description

1 Add and configure the following Agents as per the supplied IO schedule to the Agent Server.
Refer to the section “Naming Convention.”
Agent Description Agent Type Agent Name

Bottom Filtration Tank level Analog
Top Filtration Tank level Analog
Flow Rate Analog
Valve status Digital
Pump status Digital
Filter status Digital
Bottom Filtration Tank Simulation Expression
Top Filtration Tank Simulation Expression
Process Stop Simulation Expression
2 Design, develop and implement the graphic form below, using static graphics that Adroit Ignite
HMI supplies within the Shape, Wizards and Examples project found in the Enterprise Manager.
3 The bottom tank has a capacity of 1000 litres. Represent this by making use of behaviours and
the Analog Agent.
4 The top tank has a capacity of 650 litres. Represent this by making use of behaviours and the
Analog Agent.
5 The flow rate is adjustable allowing the operator to change the value using a behaviour.
6 Setpoints:
• Minimum Value = 50kgs
• Maximum Value = 100kgs
7 Design or Modify a static graphic that represents a Filter. Animate this object to show the status
and operation. (The Filter should appear to move and become invisible when not in use.)
8 Transferring from Bottom Tank to Top Tank cannot occur unless the valve, filter and pump are
operational.
9 The Trend, Alarm and Event windows to be displayed.
___________________________________________________________________________________________________________________________
Figure 143 Adroit Ignite HMI Configuration Competency Test (Example)
Provision must be made for:

• The levels of both tanks to be logged for 1 hour @ 1 second.
• The levels of both tanks to be trended for 3 minutes with a sample rate of 1 second.
• A 250 litre low alarm on the bottom tank and a 95% high alarm on the top tank.
23.2.1. Certificate of Competency

Please contact our Training Dept for more details on how to submit your project for evaluation. A
Certificate of Competency will be issued if your submission was approved by our adjudication team. Click
Here or send an email to Training Dept.
___________________________________________________________________________________________________________________________

Basic Adroit Ignite Training Manual 2021 - Rev06

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Basic Adroit Ignite Training Manual 2021 - Rev06

Uploaded by

Copyright:

Available Formats

COPYRIGHT

Advanced Worx 112 (Pty) Ltd

Version Date Author Comment Approval

Adroit Ignite HMI supplies the following datasources as standard: -

Figure 1 Adroit Ignite HMI Overview

1.3. How is Adroit Ignite HMI packaged?

On purchasing Adroit Ignite HMI the customer receives the following:

3. A Guide to Best Practices

3.1. Define the end goal of the Automation Solution

3.2. Visualisation and Control Strategy

3.2.1. Three Primary Principles

3.2.2. Graphic Hierarchy

3.2.3. Control Plan

Project Information PLC Address

Motor Physical tag RUNSTOP1 rawValue Digital

Motor Physical tag FAULT1 rawValue Digital

Motor Virtual tag MOTOR_RUNTIME1 onTotalTime Counter

Motor Virtual tag MOTOR_RUNTIME1 offTotalTime Counter

Motor Physical tag SPEED1 rawValue Analog

Motor Virtual tag SPEED_STATS1 average Statistical

Motor Virtual tag MOTOR_CUTOUT1 value Expression

Mimic Control Virtual tag LIST value StringList

Security Virtual tag ENGINEER__SEC_GP value Text

Security Virtual tag CONFIG_SEC_GP value Text

Clock Physical tag TRIGGER rawValue Boolean

3.2.6. Reporting Strategy

3.2.7. Alarming Strategy

A more detailed description of each Datasource is described later however to summarise:

4.1.1. Agent Server

Figure 2 Agents Server

4.2. The Ignite Server

4.3. Presentation Layer

4.3.2. The Operator

Figure 5 Operator - Display example

Figure 6 Adroit Help

5.1.2. Additional Software

For further details, contact your Adroit Ignite HMI representative.

5.2.1. Licensing definitions

5.3. Pre-requisites for installing Adroit Ignite HMI software

Install the latest build of Adroit Ignite HMI onto a workstation.

User with administrator rights to a workstation.

Note: Requires Administrator User name and Password.

2. The following icons will be created and placed on the desktop.

NB This final license is NOT transferrable.

Install the Adroit Ignite HMI License onto a workstation.

User with administrator rights to a workstation.

1. Click on the Ignite Utilities icon.

Figure 8 Adroit Ignite HMI Utilities

Figure 9 Adtech Licensing Utility (ALU)

Launching the Adroit Ignite HMI.

User with administrator rights to a workstation.

On the desktop start the Adroit Ignite HMI Agent Server.

Figure 11 Adroit Ignite HMI Agent Server

Figure 12 Ignite Server

6.1.1. Objective of the Training Course

As with any real-world solution provision must be made for:

Connecting to the Batching Simulation OPC Server.

Figure 13 Batching Plant Overview Drawing

Figure 14 Batching Simulation OPC Server

The Batching simulation has an Auto and a Manual operation.

Figure 16 Changing Setpoints in Batching Simulator OPC Server

Figure 17 Config Editor

Configure an Adroit Ignite HMI Database.