Wonderware Intouch Compatibility Matrix Site

She looked at the test bench. The InTouch graphics glowed steady. The tags read true. The bourbon line’s virtual mash was cooking perfectly.

Marta let out a breath she didn’t know she’d been holding. wonderware intouch compatibility matrix

She scrolled the Matrix. No mention of historian issues. That meant it was either a new problem or an undocumented one. She called an old colleague—Dominic, who now worked at a Wonderware (no, AVEVA, she corrected herself) integrator in Baton Rouge. She looked at the test bench

Three: The new edge servers she’d just unboxed ran Windows 11 IoT Enterprise. The bourbon line’s virtual mash was cooking perfectly

But Marta had a screenshot. Blurry, watermarked, and dated 2019. It showed a table: rows for InTouch versions 10.0 through 2023, columns for operating systems, SQL editions, DAServer protocols, and—crucially—the cursed “Known Anomalies” section.

She applied the fix. Then she exported the InTouch application from the Windows 7 machine—a sprawling, 8,000-tag monstrosity controlling fermenters, cookers, and the new CIP system. She imported it into a virtual machine container she’d spun up on the Windows 11 edge server. The container ran a simulated Windows 7 environment. It was ugly. It was unsupported. But the Compatibility Matrix had a second footnote: “Legacy applications may function within Type 1 hypervisors if network stack isolation is enabled.”

The InTouch startup screen appeared. Alarms initialized. Tags went live. The bourbon aging line’s simulated temperature curve rose smoothly on the trend chart.