Holds the actual .app files, tag databases, alarms, and scripts. This server runs the engine (runtime) or can be configured as a development workstation.

This article has covered the architecture, features, installation, challenges, and migration paths for Wonderware InTouch 2014. Whether you are troubleshooting an alarm server issue, trying to find a compatible OPC server, or building a business case for an upgrade, the insights above provide a roadmap.

While InTouch comes with a basic distributed historian (logging to SQLite or CSV), serious installations use – a separate industrial time-series database that integrates seamlessly.

Use the built-in migration tools to move your 2014 application into the latest version (now rebranded under the AVEVA name).

Need migration services or emergency support for InTouch 2014? Consult a certified Aveva System Integrator. Always test any changes in a non-production virtual environment first.

If a plant had 500 identical pumps, an engineer no longer needed to draw and script 500 separate windows. They could create one Archestra object, and deploy it 500 times. If a change was needed—say, adding a new alarm indicator—it only had to be updated in the template, and the change propagated across the entire system. This drastically reduced development time and maintenance costs.

Visualization is the core of any HMI. Intouch 2014 moved beyond the simple bitmaps of the 1990s.

If your organization is still running InTouch 2014, take these three actions today:

Wonderware Intouch 2014 was not just an incremental update; it was part of the . This version was designed to address three critical needs of the modern plant floor:

the computer when prompted to finalize the configuration. Getting Started with Applications