Skip to content

Integration — The Interconnected Ecosystem

Why Integration Is the Real Innovation

Any developer can build individual features. The real challenge — and the real value — is making every feature enhance every other feature. This is what we designed InteriaLib to do.

The Integration Matrix

Every row and column represents a major system we built. A checkmark means there is active data flow between them:

Menu KG Manual Tutorial EWOs Gateway Plant Query Diary
Menu — ✓ ✓ ✓ ✓ ✓ ✓
KG ✓ — ✓ ✓ ✓ ✓ ✓
Manual ✓ ✓ — ✓ ✓ ✓ ✓
Tutorial ✓ ✓ ✓ — ✓ ✓
EWOs ✓ ✓ ✓ — ✓ ✓ ✓ ✓
Gateway ✓ ✓ ✓ ✓ ✓ — ✓ ✓ ✓
Plant ✓ ✓ ✓ ✓ — ✓
Query ✓ ✓ ✓ ✓ —
Diary ✓ ✓ ✓ —

35 active integration pathways between 9 systems — all designed and maintained by our team.

Key Integration Flows

Flow 1: Menu Creation → Documentation → Tutorial

This flow demonstrates the zero-intervention automation that makes InteriaLib unique:

  1. We build a menu in the visual Menu Editor (drag-drop nodes, wire connections)
  2. Menu saved via Gateway → WinCC OA datapoint updated
  3. Knowledge Graph detects change → new MenuItem node indexed with all relationships
  4. Manual Engine triggers → AI generates documentation (screenshot + XML analysis)
  5. Tutorial system re-indexes → operators can now ask "dove trovo [new page]?" and get step-by-step guidance

Steps 2-5 happen automatically. Zero manual work.

Flow 2: Plant Discovery → Query → Dashboard

  1. Plant Editor discovers datapoints matching a pattern
  2. Roles assigned automatically (pressure → monitoring role)
  3. Tables Editor builds SQL pipeline visually
  4. TablePostgre widget displays live query results
  5. IoField widgets show computed values from plant datapoints
  6. AlarmViewer monitors conditions with blinking for unacknowledged states

Flow 3: Incident → Diary → Knowledge

  1. Operator spots anomaly on a plant page
  2. One click → ScreenshotEditor opens with live capture
  3. Annotates and saves → entry appears in Diary timeline
  4. Other operators see it on next auto-refresh (30 seconds)
  5. Documentation references the diary entries as operational evidence

Flow 4: Knowledge Graph → Everything

The Knowledge Graph acts as the connective tissue:

  • Developers use it for impact analysis: "What breaks if we change this DPType?"
  • Operators query via natural language: "Which panels show pump data?"
  • Manual Engine uses it for relationship context
  • Tutorial System queries it as one of 3 parallel search sources
  • Plant System feeds discovered equipment hierarchies into it

The Centralized Approach Advantage

Traditional WinCC OA InteriaLib
Add menu item → manually create panel → manually write docs → manually create tutorial Add menu item in editor → everything updates automatically
Change DPType → manually update all panels → hope docs are current Change DPType → KG detects impact → docs regenerate → tutorials re-index
New operator needs training → write tutorial → hope it stays current Operator types question → real-time tutorial from live system state
Debug conditions → write CTL code per panel Debug conditions → drag a node, set an expression

What This Demonstrates

The Key Message

This project demonstrates that WinCC OA's extensibility model, when fully leveraged with deep platform knowledge and modern engineering practices, can produce results that rival dedicated application development platforms — while maintaining full integration with WinCC OA's core SCADA capabilities.

Every widget, every editor, every algorithm, every integration described in this documentation was conceived, designed, and implemented by our team.

InteriaLib is not a product that was bought off the shelf. It is a custom framework that transforms what WinCC OA can do — and it was built entirely by Andrea Bertorelli at Interial.

InteriaLib — Turning WinCC OA into a modern application platform.