Learning outcomes
- Explain the key principles of wonderware/intouch application development.
- Carry out a structured practical check or configuration task.
- Recognise common faults, risks and evidence needed for diagnosis.
Module 12 · Lesson 2
Wonderware/InTouch application development
Build consistent Wonderware InTouch windows, symbols, navigation, scripts and reusable objects.
Before you begin
Wonderware development environment or approved training system.
Safety: Use site procedures, approved test equipment and competent supervision. Never bypass a protection or interlock without formal control.
Step-by-step learning
- Create a project using the site resolution and naming standard.
- Build a reusable motor or pump symbol with command, feedback, mode and alarm indication.
- Use indirect tags or templates carefully and document object interfaces.
- Test navigation, permissions and loss-of-data behaviour.
Ian's practical tips:
- Operators need clear process state, not decorative animation.
- Use consistent symbols and colours so meaning does not change from screen to screen.
Fault-finding questions
- What should be happening, and what evidence proves it?
- Where is the last known correct signal, voltage, state or process condition?
- What changed immediately before the fault?
- Can the system be divided into smaller testable sections?
Practical activity
Create a one-page test record for this lesson. Include expected values, measured results, equipment used, risks controlled, defects found and the final proven condition.