Interactive HTML/JS canvas with live OPC UA data binding for real-time process visualization

AI Canvas

AI-generated code imports directly into TIA Portal — no copy-paste needed

Auto-Import to TIA

Run up to 5 sub-agents in parallel with persistent memory, worktree isolation, and cross-session communication

Multi-Agent System

We use Reddit Pixel for reach measurement. Strictly necessary cookies (session, login, Stripe) are always loaded. Marketing tracking only starts after your consent.

Marketing cookies?

Each developer works on a dedicated branch and commits independently. When a feature is ready, the team reviews it in a pull request and merges it into "main". The project lead sets a release tag for commissioning — the exact state is reproducible at any time.

Three developers, three branches, one project

How the commissioning team pulls a released state onto the laptop, downloads it to the physical PLC, and documents the as-built state back into the repository.

The commissioning engineer opens the repository on the laptop and pulls the released state — for example "release/site-XYZ-v2.1". The exact code is then available locally.

Check out release tag

The TIA Openness Manager imports all blocks, HMI elements, and UDTs in one step. The repository folder structure is recreated 1:1 inside TIA Portal.

Bulk import into TIA Portal

Compile status is visible per block. Errors can be jumped to and fixed directly — before the PLC is even connected.

Compile with live status

The verified state is downloaded from TIA Portal to the physical PLC. Commissioning runs with the code the team approved — no surprises on site.

Download to PLC

On-site adjustments — such as IP addresses, plant parameters, or ad-hoc corrections — are exported back and committed. The as-built state lands in the repository.

Export on-site adjustments

The real commissioning state gets a tag, for example "as-built/site-XYZ". When the plant needs an update two years later, that exact state is reproducible.

Push as-built tag

From repository to PLC — the commissioning flow

TIA Multi-User vs. Git

License Options

Extend beyond Siemens TIA Portal to a second PLC platform — starting with CODESYS 3.5 — through a vendor-neutral abstraction. The existing TIA integration stays intact; CODESYS runs alongside as a parallel path. MVP scope: project open/close, block export/import via PLCopenXML, compile, download.

Multi-vendor PLC support

Headless CLI test runner, xUnit XML + HTML reports compatible with Jenkins, GitHub Actions, and Azure DevOps. Compare-runs UI with side-by-side diff. Block-change detection flagging affected suites.

Unit Testing — CI/CD Integration

Digitally signed PDF reports (EN/DE), requirements-traceability matrix with Polarion / DOORS / Jira CSV import, safety-testing templates for F-CPU, sign-off workflow with immutable audit log, one-click audit-package ZIP.

Unit Testing — Audit Ready

Worst-case execution time profiling with regression alarms, automatic flaky-test quarantine, project-wide template library (Motor DOL/VFD, valve, PID, state machine, timer, counter), parameterized tests with CSV/Excel import, live metrics dashboard.

Unit Testing — Scale & Observability

Event monitoring with severity filters, event log with CSV export, historical trend charts with time-range picker and presets.

OPC UA event subscriptions & history charts

Modal dialog from the address-space context menu. Scalar and 1D-array input editors, output panel with status and error banner.

Method-call dialog with array editors

Inline chat (Ctrl+I) in the suite editor, AI-badge on generated tests, 11 MCP tools, hardened F-CPU safety guard.

AI writes unit tests

Create, start, stop, and download PLCSim instances from the app. Typed read/write for 28 S7 data types.

PLCSim instance manager + tag browser

Send a blocking sub-agent to the background, keep the main chat responsive, resume and review results on your own pace.

Sub-agent backgrounding (Ctrl+B)

Basic

Pro+

Step-by-step installation and setup guide for TIA Openness Manager — system requirements, configuring the Siemens TIA Openness user group, and connecting to TIA Portal for the first time.

for "TIA Openness Manager"

Installation Guide

- Windows 10 or 11 (64-bit)
- Siemens TIA Portal V15, V16, V17, V18, V19, V20 or V21
- RAM: Minimum 4 GB, 8 GB recommended
- Hard disk: 1 GB
- .NET Runtime: not required (a self-contained build is shipped with the installer)
- Internet connection for license validation (at least every 14 days, 14-day offline tolerance)
- Internet connection for the AI Chat function (optional, when an AI provider is configured)
- Administrator rights for installation


1. System Requirements

1. Download the installer
2. Run the installer
3. Choose the installation path
4. Complete the installation
5. Start the software


2. Installation

1. Create an account or sign in at https://www.tiaopenessmanager.ch (email + password)
2. Choose a tier (Basic free, Pro, Pro+) or start a 30-day trial
3. For Pro / Pro+: complete the Stripe Checkout
4. Start the software — sign in with the same account
5. Hardware binding happens automatically on first sign-in
6. The software is activated


3. License Activation

- Configure MCP server
- Check permissions
- Test connection
- Start using


4. TIA Portal Integration

Automatic update check on startup. Updates are downloaded and installed after confirmation.


5. Updates

- Check admin rights
- Temporarily disable firewall (for testing only)
- Check Hardware ID
- Start TIA Portal in the same user context

---

**Disclaimer:**

The software is provided "as is". The provider assumes no liability for damages arising from use or installation. See [EULA](/eula-en) and [Disclaimer](/disclaimer-en) for details.

**© 2025-2026 AnyAutomation.**
