Skip to main content
InSource Solutions

InTouch for System Platform Architecture Guide






This document will cover typical architecture for InTouch for System Platform. 



Michael Walker

Publish Date 1/15/2013

Applies to Software

InTouch, System Platform

Applies to Version

10.0 and greater

Applies to System/Module


Article Version





InTouch for System Platform

InTouch for System Platform is configured and licensed to be used as a visualization client in conjunction with the Wonderware System Platform, displaying data from objects defined in a  Wonderware Application Server galaxy.

Managed InTouch Application

A managed InTouch Application is one that is created from within the ArchestrA IDE, and deployed as an object in the Wonderware Application Server application. Creating a managed Application allows use of ArchestrA Symbols. A managed InTouch Application exhibits the same kind of behavior as other objects in the IDE, such as the ability to check out and check in, but opens in an external development environment called WindowMaker. 


The InTouch development environment, where object-oriented graphics are used to create animated, click-sensitive display windows. You can embed ArchestrA graphics in InTouch windows.


The Runtime environment used to display the graphic windows created in WindowMaker.


Application Server

It provides a unified environment for visualization, plant history, device communications and automation application integration.


Application Server’s application, configuration information and project database.

Galaxy Repository

Single computer and software where the Galaxy database is located.




InTouch for System Platform is managed through the development environment of Application Server.  With this comes the capability to use Archestra Graphics and reference data from deployed application objects. The below diagram depicts a typical InTouch for System Platform architecture. 


Intouch for System Platform Architecture.PNG


This architecture could be scaled out adding more visualization nodes and automation object server as needed to meet application specific requirements.