InTouch vs FrameworX: compare and migrate your InTouch application
AVEVA has released InTouch HMI 2026 (Version 26.0.000) [1]. Under AVEVA's lifecycle policy, for a version on Standard-Term Servicing, a new release moves a version still in Full Support to Security-only Support [2]. Which model and dates apply to your version is listed in AVEVA's Technology Matrix [2]. In InTouch HMI 2026, AVEVA states that InTouch Access Anywhere "is not available due to security reasons" [1]. A new InTouch release is a moment to decide where the application goes next. FrameworX is one of the answers, and the assessment that tells you what moving takes is free, with a fixed price after it and nothing to pay unless you accept the result.
Your situation
Standard-Term Servicing gives Full Support for a "maximum of 3 years from the release date" and Security-only Support for a "maximum of 2 years following Full Support"; Long-Term Servicing gives 5 years of Full Support and 2 of Stability Support [2]. The dates for each version sit in AVEVA's Technology Matrix, inside the AVEVA Knowledge and Support Center [2].
Three paths. Upgrade within InTouch: AVEVA states you can migrate applications to InTouch HMI 2026 that were developed with version 7.11 P07 or later [3], and upgrade directly from version 11.1 SP1 or later installed on a 64-bit operating system [4]. Move to AVEVA's subscription offer: AVEVA lists AVEVA Operations Control as "subscription only" [5]. Or move the application to FrameworX. The rest of this page is about the third, with AVEVA's facts cited to AVEVA.
FrameworX 10.1.6 and InTouch HMI 2026, side by side
The dimensions below are the ones where our technical review of record rates FrameworX ahead or level.
| Dimension | FrameworX 10.1.6 | InTouch HMI 2026 |
|---|---|---|
| Platform and runtime | Runtime on .NET 10 for Windows, Linux and Docker. The Designer runs on Windows. | System Platform 2026, which installs InTouch HMI 2026, lists Windows 11 and Windows Server 2022 and 2025 as supported operating systems [6]. All .NET code, including QuickScript .NET scripts, runs under .NET 4.8 [7]. |
| Connectivity | OPC UA server and client, an MQTT broker with Sparkplug B, and 110+ connectors in the base install. | "InTouch can both publish and subscribe using MQTT" [8]. 2026 imports UDTs and derived objects from OPC UA models [9]. |
| Visualization | One display runs on the desktop clients and on the web and mobile clients without modification, with code-behind in C#, VB.NET or JavaScript. Store apps with alarm push. | The 2026 web client "now uses a new web server based on AVEVA's common web framework" [9]. "Remote, mobile access everywhere is supported on any device including tablets and smartphones" [10]. |
| Data model | UserTypes with semantic metadata on every member; ontology import and export in RDF, OWL 2, SKOS, ISA-88, ISA-95 and IOF; a unified namespace at the core. | User Defined Types, with UDT enhancements in 2026 [9]. |
| Historian | Included in every edition with display clients. Storage in SQLite, SQL Server, PostgreSQL, Oracle, MySQL and the historian providers Canary, InfluxDB, MongoDB and QuestDB, several at once in one solution. | AVEVA Historian tags are included by edition: 5,000 in Professional and 500 in Standard [5]. AVEVA Operations Control, subscription only, lists unlimited historian tags [5]. |
| Scripting and engineering | C#, VB.NET and Python 3, side by side. The whole solution exported as JSON for Git. Tag importers for L5K, TwinCAT and Codesys controller exports. | Python and C# method members for UDTs, new in 2026 [9]. Development without Windows administrator rights, new in 2026 [9]. |
| Programmability | Runtime REST API at /api/v1 covering tags, types, historian, alarms and bulk read and write, with an OpenAPI 3.0.3 document. | OPC UA model import [9]; MQTT publish and subscribe [8]. |
| AI | Three MCP servers ship with the platform today: Designer, Console and Runtime. FrameworX ships no language model; you connect your own. | For AVEVA Operations Control 2026, AVEVA describes "an upcoming MCP Server follow-on release later in the year" [11]. |
| Release and lifecycle | A published lifecycle page with three named support phases, and a free upgrade to 10.1.5 for every 10.x customer. | Published lifecycle policy with Standard and Long Term Support phases; per-version dates in the Technology Matrix [2]. |
What carries over from InTouch, and what is rebuilt
An InTouch application is two kinds of thing. The structured records carry over as data: the tagname dictionary, the access names and PLC addressing, the alarm groups and alarm definitions, and the history configuration. The windows, Industrial Graphics and QuickScripts are rebuilt rather than converted: windows become FrameworX displays and symbols, and the scripts become C#, VB.NET or Python 3 on FrameworX.
Every migration is verified stage by stage, from your original application to the running FrameworX client, and a written audit accounts for every part of your application, translated or logged. Nothing is dropped silently.
Repeated equipment becomes templates instanced once per asset, so the migrated application is smaller and easier to change than the one it replaces. A de-identified example report, built from an InTouch application, is available on request.
Migration is a Tatsoft service, with Tatsoft engineers doing the work; it is not a tool we ship. We have migrated applications from more than ten platforms. Integrators keep the customer and the commissioning; we do the platform evolution.
The difference in the rebuild: engineers build with AI agents
Engineers build with AI tools, and plants run with AI assisting, gated and verified. In a FrameworX rebuild the engineer works with an AI agent connected to the Designer MCP server, one of the three MCP servers that ship with FrameworX 10.1.6. The agent reads the assessment report, creates the templates, instances the assets, drafts the displays and the scripts, and the engineer reviews every change in the Designer before it stands. FrameworX ships no language model and no weights: you bring your own local or on-premises model, so your plant data stays yours.
Connected to what you already run
FrameworX connects over OPC UA, Modbus, MQTT and 110+ connectors, with an OPC UA server and client and an MQTT broker with Sparkplug B built in. The controllers under your InTouch application stay where they are.
Licensing
AVEVA lists AVEVA Operations Control as "subscription only" [5], and offers InTouch Unlimited "with a traditional perpetual license" [10]. FrameworX is licensed perpetually, from a published price list. FrameworX Unlimited includes all modules and features, and 110+ connectors. Every Enterprise edition adds unlimited clients. What scales with price is I/O, not features.
Why you can trust the team
Tatsoft was founded by the team that created InduSoft (now AVEVA Edge). The people who build FrameworX have worked on HMI and SCADA since 1997 and have lived through two full generations of industrial software. FrameworX runs in more than 1,000 installations in more than 35 countries. We run FrameworX ourselves in our own internal systems.
Start free
The FrameworX Designer requires no license. The Community Edition runs applications up to 100 I/O points and 1,000 tags, so a first InTouch window can be rebuilt on FrameworX before anyone signs anything.
Start with a free assessment
Send a read-only copy of your InTouch application. In two to five working days you get a written report that reads it back to you object by object: the tag model, the PLC addressing scheme, the alarm organization, the historian configuration and a one-page navigation map of every window and every click. With it comes a fixed price for the migration. Applications sent for assessment are confidential by default. A free assessment, a fixed price, and you pay only if you accept the result.
Aim High. Start Simple. Scale Without Limits.
FAQ
What is a good alternative to AVEVA InTouch HMI? FrameworX by Tatsoft. FrameworX Unlimited includes all modules and features and 110+ connectors, one Designer serves the desktop client, the browser and the iOS and Android apps, and scripts run in C#, VB.NET and Python 3. Tatsoft migrates an InTouch application in-house, with a free assessment and a fixed price.
Can an InTouch application be moved to another platform? Yes. The tagname dictionary, access names and PLC addressing, alarm definitions and history configuration carry over as data. Windows, Industrial Graphics and QuickScripts are rebuilt. Tatsoft engineers do the work and every stage is verified against the original application.
Do you convert InTouch windows automatically? No. Migration is a Tatsoft service, not a tool we ship. The structured records carry over as data; windows and scripts are rebuilt by Tatsoft engineers working with AI agents, and the assessment tells you the size of that rebuild before you commit.
What do I have to send you? A read-only copy of the InTouch application folder as it was delivered. Nothing is installed on your system and nothing running is touched.
How long does the assessment take, and what does it cost? Two to five working days from the point we have a complete copy of the application. It is free. The fixed price comes with the report.
Can my integrator do the migration? Yes. Integrators keep the customer and the commissioning. Tatsoft does the platform evolution and hands the application back.
Is FrameworX sold as a subscription? No. FrameworX is licensed perpetually from a published price list. What scales with price is I/O, not features.
Does FrameworX need a cloud AI service? No. FrameworX ships no language model and no weights. You connect your own local or on-premises model, or the cloud model you already license.
Sources
- InTouch HMI 2026, Version 26.0.000, release notes; InTouch Access Anywhere "is not available due to security reasons", last updated 2026-06-12, https://docs.aveva.com/bundle/intouch-hmi-2026/page/InTouchHMI_ReleaseNotes.html
- Lifecycle phases (STS 3 + 2 years, LTS 5 + 2); a new release moves a Full Support version to Security-only Support; Technology Matrix in the Knowledge and Support Center, Version 2.0.1, April 2026, https://www.aveva.com/content/dam/aveva/documents/legal/policies/AVEVA-Software-Lifecycle-and-Retirement-Policy.pdf
- Applications from InTouch 7.11 P07 or later migrate to 2026, 2026-06-09, https://docs.aveva.com/bundle/intouch-hmi-2026/page/368445.html
- Direct upgrade from 11.1 SP1 or later on a 64-bit OS, 2026-06-09, https://docs.aveva.com/bundle/intouch-hmi-2026/page/368441.html
- AVEVA Operations Control "subscription only" with unlimited historian tags; Historian tags by edition (Professional 5,000, Standard 500), undated page, read 2026-11-03, https://www.aveva.com/en/info/intouch-hmi-pricing/
- Supported operating systems: Windows 11, Windows Server 2022 and 2025, 2026-06-17, https://docs.aveva.com/bundle/system-platform-2026/page/394548.html
- All .NET code, including QuickScript .NET, runs under .NET 4.8, 2026-05-19, https://docs.aveva.com/bundle/intouch-hmi-2026/page/368432.html
- "InTouch can both publish and subscribe using MQTT", posted 2025-11-24, https://www.aveva.com/en/perspectives/blog/unlocking-iiot-connectivity-in-aveva-intouch-hmi-with-mqtt/
- 2026 one-sheet: UDT enhancements, new web server on AVEVA's common web framework, Python and C# scripting, OPC UA model import, development without admin rights, 2026, read 2026-11-03, https://www.aveva.com/content/dam/aveva/documents/perspectives/onesheet/OneSheet_AVEVAInTouchHMI.pdf.coredownload.inline.pdf
- Mobile access on any device; InTouch Unlimited "with a traditional perpetual license", undated page, read 2026-11-03, https://www.aveva.com/en/products/intouch-hmi/
- "an upcoming MCP Server follow-on release later in the year", posted 2026-07-10, https://www.aveva.com/en/perspectives/blog/aveva-operations-control-2026-a-modern-foundation-for-open-connected-and-ai-ready-hmi-scada/
