We have built real-time platforms four times.
1988, 1997, 2012, and today. The same team, across every generation of SCADA and HMI.
Aim High. Start Simple. Scale Without Limits.
The team behind FrameworX has built real-time platforms four times: for DOS from 1988, for Windows in 1997, for .NET in 2012, and for AI today. The UniSoft for Windows rewrite shipped in 1996, and in 1997 it became the foundation for InduSoft (now AVEVA Edge). Tatsoft shipped FrameworX (originally deployed as FactoryStudio) in 2012, .NET-native from the first line. FrameworX 10.1 is the fourth generation, AI-Native by architecture. The engineers who wrote that code are still here.
The lineage at a glance
| Company | Tatsoft, founded 2009, Houston, Texas |
|---|---|
| Product | FrameworX, a SCADA, HMI, IIoT and Historian platform |
| First generation | DOS, from 1988, under the UniSoft brand. Hand-written C and C++ against PLC hardware. |
| Second generation | UniSoft for Windows, shipped 1996. In 1997 it became the foundation for InduSoft (now AVEVA Edge). |
| Third generation | FrameworX (originally deployed as FactoryStudio), shipped 2012 by Tatsoft. .NET-native from the first line. |
| Fourth generation | FrameworX 10.1, AI-Native by architecture. Built for AI agents and the Model Context Protocol (MCP) rather than retrofitted. |
| Relationship to InduSoft | Shared founder and some key engineering architects. Completely separate products and companies. |
| Relationship to AVEVA Edge | The former UniSoft and InduSoft products were sold to Schneider Electric, and later incorporated into AVEVA Edge. The current companies and products have no relationship. |
| Deployments | Over 5,000 worldwide, including hundreds of oil and gas sites and FDA-regulated facilities |
| Modules and connectors | All modules included in every edition (UNS, Alarms, Historian, Devices, C# and Python 3 scripting, database connections, Reports, Windows, Web and Mobile UI). More than 100 native connectors, included. Scale by I/O and clients, never by module. |
Learning the problem on the plant floor.
Our founder started in automation on a paint shop project for a global automaker in South America, with DOS PCs talking to Allen-Bradley PLC-2 controllers. From 1988, under the UniSoft brand, the first generation of PC-based SCADA was written by hand, in C and C++, against the hardware limits of the era. Every tag definition and every device mapping was custom code.
That is where the habits come from. Field startup first, platform software second.
Choosing the rewrite over the port.
When object-oriented tooling matured in the mid 1990s, the industry faced a choice. Port the DOS code to Windows and keep shipping, or rewrite the platform from the ground up for the new model.
Our team rewrote it. UniSoft for Windows shipped in 1996, and in 1997 that platform became the foundation for InduSoft (now AVEVA Edge). Derivatives of that 1996 architecture are still running production systems today.
That is the sentence worth pausing on. A rewrite costs a release cycle. A port costs a decade, and the bill arrives later.
The same call again, this time on .NET.
When .NET matured into a platform an industrial runtime could be built on, our team made the same decision again. Tatsoft shipped FrameworX (originally deployed as FactoryStudio) in 2012: .NET-native from the first line, one environment from the machine panel to enterprise SCADA.
The people who were there
Platform lineage is a claim about code. It is only worth anything if the people who wrote the code are still here.
Marc Taccolini
Marc started in automation on that paint shop project, writing first-generation PC-based SCADA in C against DOS and PLC-2 hardware. He built UniSoft from 1988, whose 1996 rewrite for Windows became the foundation for InduSoft (now AVEVA Edge), which he co-founded in 1997. In 2009 he founded Tatsoft to make the same call again on .NET, and he still designs the platform architecture personally, which is why FrameworX 10.1 could be built AI-Native rather than have AI attached to it afterwards.
Four generations, one architect.
Roberto Vigiani
Roberto joined UniSoft as an intern in its first months and stayed through the companies' evolution. He worked training, support, driver development and bug fixing, and became development coordinator. For years he was the only person writing device drivers, which made him the person who knew how the platform actually talked to the plant.
He left with our founder to start Tatsoft, and built the device module that FrameworX still runs on. Along the way: advanced control for oil refineries, in partnership with a national research centre. A hot strip mill furnace system migrated off VMS and C onto .NET, a project that took the better part of two years. An offshore drilling data platform that became a Tatsoft product in its own right.
Since 1988: three companies, four platform generations, one lineage of engineers.
Dave Hellyer
Dave has spent over thirty years in industrial automation, including a year inside InduSoft, and has been with Tatsoft for fifteen of them. He has watched every generation of this technology ship, break and get fixed, which is the experience a buyer is actually buying when they ask how long we have been doing this.
The core development team today is a mix. Engineers who have written this platform since the UniSoft years, including the lead developer who has worked beside our founder for more than three decades, and a newer generation who joined for the .NET and AI eras. The habits pass down inside one team, not through a handover document.
The fourth generation, built for AI.
FrameworX 10.1 is built for this generation rather than retrofitted onto the last one, which is the same call our team made in 1996 and in 2012, and the reason the 1996 work is still standing.
AI-Native by architecture. Three MCP servers plus an in-process AI agent spine, shipped GA. Three MCP servers, one for the Designer, one for headless authoring and one for live runtime data, plus an AI agent inside the runtime that works against a model you host, all released and supported today. An AI client connects to the live Designer with real knowledge of your project and your tags, and to the runtime for your live process data, so it configures against the actual solution. Your engineers review and sign off at every step.
What four generations of this buys you
Over 5,000 deployments worldwide, including hundreds of oil and gas sites and FDA-regulated facilities.
All modules included, in every edition: UNS, Alarms, Historian, Devices, C# and Python 3 scripting, database connections, Reports, and Windows, Web and Mobile UI for process diagrams and responsive dashboards. More than 100 native connectors, included. You scale by I/O and clients, never by module.
Support from engineers who have shipped every generation of this technology and fixed it in the field.
UNS by Design · One Platform. No Limits. · Build Once. Deploy Anywhere.
The platform’s data backbone is a Unified Namespace (UNS): every tag, asset model and event addressable from one place, by engineers and by AI clients alike.
Common questions
Is FrameworX a replacement for InduSoft?
FrameworX can replace InduSoft systems. FrameworX core was written with newer technologies (the InduSoft core is based on the UniSoft for Windows product of 1996). The two are still distinct platforms: product specification and configuration differ, so a move across is a migration and not an upgrade.