InteriaLib — Advanced Application Framework for WinCC OA¶
Designed and developed by Andrea Bertorelli — Interial Built on SIEMENS WinCC Open Architecture · February 2026
What is InteriaLib?¶
InteriaLib is a complete application framework that we designed and built from scratch to transform WinCC OA from a traditional SCADA configuration tool into a modern, integrated, no-code industrial platform.
Every component described in this documentation — every widget, every editor, every algorithm, every integration — was conceived, architected, and implemented by our team. The standard WinCC OA platform provides only the base runtime; everything you see here is custom work that pushes the platform far beyond its intended capabilities.
The Core Idea
Build once, connect everything. Every feature in InteriaLib is aware of every other feature. Menus know about documentation, documentation knows about datapoints, tutorials know about menus, and a knowledge graph connects them all — automatically.
At a Glance¶
| What We Built | Scale |
|---|---|
| Custom C++ Widgets (EWO) | 14 production-grade components |
| REST API Endpoints | 60+ across 5 functional domains |
| Visual Node Editors | 3 complete editors (Menu, Plant, SQL) |
| Knowledge Graph | Real-time project intelligence with 129 nodes, 164 edges |
| AI Documentation | Parallel generation with conflict management — 22 pages, 100% coverage |
| Intelligent Tutorial | Multi-agent search — 2ms cached response |
| Application Gateway | 1 server bridging 6 backends with smart proxying |
| Operator Diary | Annotated screenshot audit trail with timeline viewer |
The Integration Philosophy¶
In a traditional WinCC OA project, every feature lives in its own silo. Adding a menu item is one task. Creating the page is another. Writing documentation is another. Training operators is yet another. None of these systems talk to each other.
InteriaLib changes this completely.
When we add a page in the visual Menu Editor:
- The live application menu updates instantly (no restart)
- The Knowledge Graph indexes the new entity and its relationships
- The Manual Engine can auto-generate documentation for it
- The Tutorial System can guide operators to it via natural language
- The Debug Monitor starts watching its conditions and propagating badges
All of this happens automatically, from a single action in the editor.
How This Document Is Organized¶
| Section | What You'll Learn |
|---|---|
| Architecture | The distributed microservice design and how the 4 servers coordinate |
| Custom Widgets | The 14 EWO widgets we built from scratch in C++ |
| Menu Editor | The visual node editor that generates live menus with debug monitoring |
| Tables Editor | The visual SQL pipeline builder |
| Knowledge Graph | Real-time project intelligence mapping every entity and relationship |
| Manual Engine | AI-powered parallel documentation generation |
| Operator Diary | Screenshot annotation and audit trail system |
| Application Gateway | The custom server that bridges web and WinCC OA |
| Integration | How all these systems reinforce each other |
"The best framework is one where adding a feature in one place automatically enriches every other part of the system."