Home › Technical articles

Đọc bằng tiếng Việt

AVEVA OMI vs InTouch HMI: ViewApps, screen profiles, layouts, navigation, web client and window conversion

TDL Industrial Automation · Last updated:

From AVEVA's 2026 documentation: an OMI ViewApp is a Galaxy object built from screen profiles, layouts, panes and apps, with navigation from the Model view and Auto-Fill; InTouch HMI's Replace, Overlay, Popup and frame windows for comparison; desktop and OMI web clients and the AVEVA Web Client limits; converting InTouch windows to Industrial Graphics and what does not convert.

AVEVA OMI (Operations Management Interface) is the visualisation layer of AVEVA System Platform. Operators run ViewApps built from screen profiles, layouts with panes, and content such as graphics and apps, with navigation taken from the Galaxy's asset model. InTouch HMI shows windows drawn in WindowMaker and run in WindowViewer, on their own or managed from a Galaxy. Below, the two side by side from AVEVA's 2026 documentation (OMI, InTouch HMI, System Platform and AVEVA Web Client), and what AVEVA documents for bringing InTouch windows into OMI. Standalone InTouch versus System Platform is covered in InTouch HMI or System Platform.

1. What OMI is

AVEVA's OMI 2026 help describes OMI as a responsive HMI and SCADA visualisation framework that uses the data model of System Platform. It is integrated into Application Server and runs on top of System Platform. Its two core parts are the ViewApp, the runtime application deployed to operator clients, and Industrial Graphics, the graphic building blocks.

A ViewApp is a Galaxy object. It starts as a template derived from the $ViewApp base template in the System Platform IDE, and all editing is done in that derived template with the ViewApp Editor. An instance is created automatically when the template is assigned to a ViewEngine (for the desktop client) or a WebViewEngine (for the browser).

2. Inside a ViewApp

Element What it is Where it is set up
Screen profile the physical screens of a client station and how they are arranged; one icon per screen Screen Profile Editor
Layout one or more rectangular panes separated by dividers, assigned to one screen of the profile; a layout can also be content inside another layout Layout Editor
Pane an area that holds content; single content or multi-content (tabbed), up to 20 panes or tabs by default, configurable up to 50 pane properties in the Layout Editor
Content graphics, layouts, controls and app instances, dragged from the Toolbox or Assets tab Layout Editor or ViewApp Editor
Navigation model the hierarchy of navigation items, the content each one shows and the actions run when it is selected ViewApp Editor

One screen profile can stand for all the monitors in a control room or the single screen of a phone. Content types limit which graphics a pane will show, unless the pane or the graphic accepts any type.

OMI Apps are controls, mostly built with WPF, placed in panes like other content. The default apps include AlarmApp for current and historical alarms and events, NavigationApp with a breadcrumb and a navigation tree, HamburgerApp for slide-in panes on phones and tablets, and apps for maps, PDF files and spreadsheets. Some, such as the Power BI and Scheduler apps, are marked Flex licence only. Custom apps can be built with the OMI SDK.

OMI ViewApp and InTouch HMI application: how each is builtTwo columns. Left, the AVEVA OMI ViewApp, a Galaxy object that runs on System Platform; right, the InTouch HMI application, standalone or managed in a Galaxy. Five rows: 1, built in: the System Platform IDE with a ViewApp derived from $ViewApp, against WindowMaker; 2, screen arrangement: screen profile and layouts, one layout per physical screen, against windows of type Replace, Overlay or Popup and frame windows; 3, content: panes holding graphics, layouts, controls and apps such as AlarmApp, against InTouch symbols, SmartSymbols and Industrial Graphics in windows; 4, navigation: a navigation model from the Model view with Auto-Fill, against ShowWindow and HideWindow links and scripts; 5, runs in: the OMI desktop client through a ViewEngine or the OMI web client through a WebViewEngine, against WindowViewer and the AVEVA Web Client, which shows frame windows only. Bottom row: InTouch windows are converted to Industrial Graphics in WindowMaker and land in the IDE Graphic Toolbox as content for OMI panes; trends, ActiveX controls and the Distributed Alarm Display are not converted. Based on AVEVA's 2026 documentation.OMI ViewApp and InTouch HMI application: how each is builtAVEVA OMI ViewAppGalaxy object, runs on System PlatformInTouch HMI applicationstandalone, or managed in a Galaxy1 · Built inSystem Platform IDEViewApp derived from $ViewApp; Screen Profile,Layout and ViewApp editorsWindowMakerfrom Application Manager (standalone) or fromthe IDE (managed)2 · Screen arrangementScreen profile and layoutsone layout per physical screen; panesbetween dividersWindowsReplace, Overlay or Popup; frame windows forpan and zoom3 · ContentPane contentgraphics, layouts, controls and apps suchas AlarmAppGraphics in windowsInTouch symbols, SmartSymbols,Industrial Graphics4 · NavigationNavigation modeltree from the Model view; Auto-Fill fills the panesLinks and scriptsShowWindow and HideWindow open andclose windows5 · Runs inOMI desktop or web clientViewEngine with Application Manager;WebViewEngine in Chrome or EdgeWindowViewerthe AVEVA Web Client shows framewindows only6 · From InTouch to OMIIDE Graphic Toolboxcontent for OMI panesConvert To Industrial Graphicrun in WindowMakerInTouch windowclosed before conversionNot converted: trends, ActiveX controls, the Distributed Alarm Display, scripts with InTouch orQuickScript functionsBased on AVEVA, OMI 2026, InTouch HMI 2026, System Platform 2026 and AVEVA Web Client 2026documentation (read 15 November 2026). Figure: drawn by TDL.
Figure 1: OMI ViewApp and InTouch HMI application: how each is built. On a phone, swipe sideways to see the whole figure.

3. Navigation from the asset model

AVEVA describes OMI navigation as generated from the plant's object model. The NavTree app shows the navigation items as a tree built from the Model view of object instances, so the areas and equipment engineers build in the Galaxy become the hierarchy operators browse. Custom navigation items need not follow the Model view.

Auto-Fill decides how content lands in panes without configuring every view by hand. The modes are None (custom navigation items only, all content placed by hand), Current only, Current then up (empty panes are filled from parent items) and Current, up, then down (then the first child at each level). Only panes with Use For Auto-Fill set to True take part; the default is False.

For mixed devices, a layout can use responsive mode instead of fixed mode: the device width picks the layout, from mobile (up to 767 pixels) to desktop (1200 and more), on a 12-column grid.

4. InTouch HMI windows, for comparison

In InTouch HMI 2026 a window is a container for one or more graphics, and an application can have any number of windows. The window type sets how it opens at run time: Replace closes the windows it overlaps, Overlay opens on top and lets the windows behind reappear when it closes, and Popup stays on top of all other windows. Frame windows are a second kind that host one Industrial Graphic with pan, zoom and touch, but no ActiveX controls or SmartSymbols.

A standalone application is created in Application Manager, built in WindowMaker and run in WindowViewer. A managed application is a template derived from $InTouchViewApp in the IDE and deployed to nodes that run WindowViewer. The InTouchViewApp object lets application objects on its ViewEngine read the InTouch tags as if they were attributes of the InTouchViewApp object.

5. Clients: desktop, browser and remote sessions

On the desktop, the AVEVA OMI Application Manager lists the ViewApps deployed to a computer or terminal server and starts one, in Read/Write or Read Only mode. System Platform 2026 describes supervisory clients as thick clients with the OMI runtime installed, or through an RDS session or an HTML5 web browser.

In the browser, a ViewApp deployed to a WebViewEngine opens at <node_name>/avevaweb over HTTPS. InTouch applications use the AVEVA Web Client, which in 2026 shows frame windows only, from a built-in web server with no RDP or IIS. The Web Client 2026 help lists what to prepare:

  • System Platform registered with AVEVA Identity Manager, and at least one WebViewEngine deployed.
  • The latest Google Chrome or Microsoft Edge; a security certificate on every remote device; for the OMI web client, domain users only.

The same help lists limits: one screen of a multi-screen layout at a time, no history playback, no secured or verified writes, no multi-Galaxy configurations and no embedded .NET controls. AVEVA recommends testing an existing application before using it with the Web Client in production. The Web Client takes its own session licence, separate from the desktop licence, counted per user per machine, with no demo mode; see AVEVA licensing.

The OMI 2026 release notes state that InTouch Access Anywhere is discontinued as of System Platform 2026.

6. Where AVEVA positions each

The System Platform 2026 page on visualisation clients describes InTouch HMI as an optional visualisation capability built around situational awareness, and OMI as responsive visualisations that arrange content by user device and use the asset model hierarchy for navigation. The documents give no rule for choosing. What they do fix is the dependency: OMI ViewApps are Galaxy objects, while InTouch HMI can run without a Galaxy as a standalone application.

7. Bringing InTouch windows into OMI

The pages we read describe no tool that turns a whole InTouch application into a ViewApp. InTouch HMI 2026 documents the conversion of windows to Industrial Graphics: in WindowMaker the windows are closed, then Convert To Industrial Graphic is chosen and the windows selected. The new graphics appear in the WindowMaker Industrial Graphic Toolbox and in the IDE Graphic Toolbox, and ViewApp content is dragged into panes from the Toolbox and Assets tabs of the OMI editors. The original window is backed up, and a new InTouch window that embeds the new graphic is created.

The rules AVEVA lists:

  • Only the symbols and scripts are converted; the window's colour, type, frame, title bar and Close button are not.
  • InTouch primitives become Industrial Graphic primitives, a SmartSymbol becomes an embedded graphic and an InTouch symbol becomes a group.
  • Real-time and historical trends, ActiveX controls and the Distributed Alarm Display are not converted, and frame windows cannot be converted.
  • InTouch tags in animation links get the prefix InTouch:, the galaxy: prefix is removed from attribute references, and a ShowWindow link becomes an action script with ShowGraphic.
  • Scripts that use InTouch or QuickScript functions are not converted. No warnings are logged during conversion, so AVEVA advises running script validation on the result.

Converted graphics still point at InTouch tags, and the Web Client help states that the OMI web client does not support InTouch-specific references, so it shows no run-time data from InTouch applications.

An existing InTouch application can also be brought into a Galaxy as an InTouchViewApp; its files are copied to a repository and the original is left unchanged. Applications from InTouch 7.11 P07 or later can be migrated to InTouch HMI 2026: see Upgrading Wonderware InTouch.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • We take a Galaxy backup and a copy of each InTouch application folder before anything is converted (Galaxy backup and restore).
  • We record whether a Galaxy exists, its version, and whether each InTouch application is standalone or managed.
  • We list the windows that hold trends, ActiveX controls, the Distributed Alarm Display or QuickScript functions, because these do not convert.
  • We count the screens on each operator station and ask who needs a phone or browser view, which decides screen profiles, responsive layouts and the Web Client limits.
  • We compare the Galaxy's Model view with the way operators actually move through the plant.
  • We ask whether anyone still uses InTouch Access Anywhere.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. Our AVEVA service page lists System Platform and OMI, as well as InTouch HMI, among the AVEVA software we build, extend and maintain, and our project pages show System Platform at Samsung SEHC and Nestlé Tri An. Older Wonderware applications are covered on Wonderware InTouch upgrade.

Frequently asked questions

Does AVEVA OMI need System Platform?

Yes. AVEVA describes OMI as integrated into Application Server and running on top of System Platform, and a ViewApp is a Galaxy object deployed to a ViewEngine or WebViewEngine.

Can existing InTouch windows be reused in OMI?

Partly. WindowMaker can convert windows to Industrial Graphics, which then appear in the IDE Graphic Toolbox. Trends, ActiveX controls, the Distributed Alarm Display and scripts with InTouch or QuickScript functions are not converted.

Does the OMI web client show everything the desktop client shows?

No. The Web Client 2026 help lists limits such as one screen at a time, no history playback, no secured or verified writes and no embedded .NET controls.

What is a screen profile in OMI?

It describes the physical screens of a client station and how they are arranged. Each screen in the profile gets a layout when the ViewApp is built.

Is InTouch Access Anywhere still available?

No. AVEVA's OMI 2026 release notes state that it is discontinued as of System Platform 2026.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
SCADA & historian AVEVA (Wonderware)