Discover the fundamentals of Aveva InTouch to design your first SCADA project. This technical guide explores the software architecture, tag management, and best practices for creating a high-performance operator interface.
Introduction to the Aveva InTouch Universe
In the world of industrial automation, Aveva InTouch (formerly Wonderware) stands out as a benchmark for SCADA (Supervisory Control and Data Acquisition). Used by thousands of factories around the world, this software enables the transformation of raw electrical signals from automation systems into visual information that can be exploited by operators. Whether you work in the food industry, energy, or water treatment, understanding InTouch is a major asset for your career in OT (Operational Technology).
One of InTouch's major strengths lies in its longevity. Projects developed twenty years ago are still running today, thanks to impressive backward compatibility. For a beginner, the first step is to differentiate between the development environment, called WindowMaker, and the runtime environment, WindowViewer. It is in this duo that the magic of industrial supervision takes place.
Understanding the Architecture: Standalone vs System Platform
Before clicking the 'New Project' button, it is crucial to understand where InTouch fits within the Aveva ecosystem. Traditionally, it is used in Standalone mode. In this configuration, each supervision station manages its own database of variables (tags) and its own screens. This is the ideal approach for isolated machines or small production lines, as it is simple to deploy and maintain.
On the other hand, for complex industrial sites, InTouch integrates with the System Platform via ArchestrA technology. Here, the logic is centralized in a Galaxy (configuration database), and InTouch serves only as a visualization layer. For our first steps, we will focus on Standalone mode, which allows us to master the fundamentals without the complexity of object servers. You can consult official resources on the website of Aveva to delve deeper into these concepts.
Tag Management: The Heart of the System
Every SCADA project relies on the Tagname Dictionary. A tag is a variable that represents either physical data (temperature, motor state) or an internal variable (alarm threshold, cycle counter). In InTouch, there are two main types of tags: Memory tags, stored only on the supervision computer, and I/O tags, which are linked to an automation system via a communication server (often an OPC server or a specific driver like OI.Server).
When creating an I/O tag, you must define an Access Name. This is the 'bridge' that tells InTouch how to communicate with the outside world. If you don't have an automation system available for testing, you can use Memory type tags or the internal simulator. A pro tip: always name your tags with a strict convention (e.g., PUMP01_STATUS) to facilitate searching and maintenance when your project includes thousands of variables.
Creating Your First HMI Interface
The human-machine interface (HMI) must be intuitive before being aesthetic. In WindowMaker, you have a palette of tools to draw shapes, import images, or use the Symbol Factory library. To make an object interactive, you use Animations Links. For example, to change the color of a circle based on the state of a motor, you assign an animation of type 'Discrete Value' linked to the corresponding tag.
Don't forget to include clear navigation buttons and a dedicated area for alarms. A modern interface often follows the principles of 'High Performance HMI': use subdued colors (gray, white) for the background and reserve vibrant colors (red, yellow) only for signaling anomalies or critical states. This helps reduce the operator's cognitive fatigue and accelerate their reaction in case of a problem.
Example of a Simple Script
InTouch allows you to add intelligence via the QuickScript language. This is a simple yet powerful language that enables automation of tasks or calculation of values in the background. Here's an example of a script that could be placed on a window (Condition Script) to simulate automatic temperature increase:
IF Temp_Tank < 100 THEN
Temp_Tank = Temp_Tank + 1;
ELSE
Temp_Tank = 0;
ENDIF;Classic Beginner Mistakes and Conclusion
One of the most frequent mistakes is forgetting to configure Runtime Logging. Without this, your alarms and trends will not be recorded on the hard drive, and you will lose all history after a restart. Another mistake is neglecting screen resolution: always develop your project in the native resolution of the target screen to avoid graphic distortions once in the field.
To conclude, mastering Aveva InTouch requires practice, but the basics are accessible to any curious technician. Once you are comfortable with tags and animations, you can explore advanced functions like SQL historization, complex scripts, or networking multiple supervision stations. For more technical information, consult the guides from Schneider Electric who often distribute these solutions.