Data security and know-how with AI in TIA Portal
Want AI for TIA Portal, but need to know what happens to your project? TIA MCP runs locally on the computer with TIA Portal and works with the project through the official TIA Portal Openness interface. The AI assistant only gets the data it requests. How much of it leaves your computer depends on the model you choose – with a local model, nothing. People stay in control of changes to the project.
How data flows when working with AI in TIA Portal
Three paths, each with clearly defined content. TIA MCP never sends the project or parts of it to anyone on its own.
Your computer with TIA Portal
- backups before objects are changed
- write log
- Git repository with the project export
requests and results of the requested tools
licence, version and counts – no project data
Diagram: TIA MCP sits between TIA Portal and the AI assistant. With a local model, paths 1 and 2 stay entirely within your network.
TIA MCP and TIA Portal
Only on your computer, via TIA Portal Openness. TIA MCP reads and changes the open project just like a script or an Add-In. Backups before writes, the write log and the Git repository are stored on your disk.
TIA MCP and the AI assistant
The AI sends requests and tool calls, TIA MCP returns only their results: for example the code of one block, a list of tags or the HW configuration. Whether this goes to the cloud or stays with you depends on the model you choose.
TIA MCP and benesl-automation.cz
Licence, update check, daily usage statistics and anonymised error reports. Statistics and reports can be switched off. The project, blocks and PLC data are never sent to us.
What is sent and what is not
Overview of the internet communication of TIA MCP according to the code of version 2.20. Apart from this, TIA MCP only communicates in the local network: with TIA Portal, PLCs, PLCSIM and a local model.
| Where | What | When | How to limit it |
|---|---|---|---|
| Cloud AI assistant | your requests and the results of the tools the AI calls: block code, tags, hardware, IP addresses, texts | while working with the AI, under the model provider's terms | local model, smaller tool set, know-how protection of blocks |
| Local model (Ollama, LM Studio, llama.cpp) | the same, but it stays on your PC or a server in your company network | while working with the AI | not needed |
| Benešl Automation licence portal | order code or licence, the computer's Hardware ID, on activation also the computer name, TIA MCP version | activation, licence transfer, renewal before the subscription ends; in a virtual machine at least every 30 days | offline activation with a license.lic file |
| Automatic update check | only a request for the signed version list; the User-Agent header contains the TIA MCP and Windows version. No Hardware ID, licence or project data. | in the background; the version list is downloaded at most once a day | switch on the Data and security page or TIA_MCP_UPDATE_CHECK=0; manual checks and the offline package keep working |
| Error reports to the vendor | your description, TIA MCP errors after anonymisation (without paths, project name, names, IP addresses and argument values), versions, a diagnostics summary, licence details without the key and Hardware ID; e-mail only if you enter it | from version 2.20 the default mode is auto: unexpected errors are sent automatically after anonymisation, without licence and contact details, the same error once a day, at most 10 reports a day. In ask mode only on your request, after a preview of what will be sent. | an option in the installer, ask or Off mode on the Data and security page, or TIA_MCP_ERROR_REPORTS=ask|off; a report can be saved and sent by e-mail |
| Usage statistics | a random installation ID, TIA MCP, TIA Portal and Windows versions, the connected AI client, the licence type with the order number, daily start counts and the number of calls, errors and run time of individual tools. No project, block or tag names, paths, values, error texts, names or Hardware ID. | from version 2.20 once a day in the background, on by default | a checkbox in the installer, a switch on the Data and security page or TIA_MCP_TELEMETRY=0; a preview there shows what is sent |
Additionally, only on your instruction: downloading and installing an update (signed package, SHA-256 and signature check), installing Ollama with a model from the installer, pushing the Git repository to your server and remote access through your tunnel.
Never sent anywhere: the project or its text export, backups before writes, the write log and passwords. TIA MCP reads passwords for protecting blocks, the project and the PLC from a file or an environment variable, not from the chat, and never returns them to the AI. The Git repository with the export only goes where you push it yourself.
The Data and security page in the web interface
Since version 2.19, the TIA MCP web interface has a Data and security page for administrators and IT. Its description matches the code of the installed version and shows the actual state of that computer. Nothing is written to the project from it.
- What leaves this PC. The same table as above, but with the state of your computer: whether the update check is on, which mode error reports are in, whether the licence would be renewed now, where the copilot sends its queries and whether remote access is running.
- Communication settings. Switches for the automatic update check and usage statistics and a choice for error reports: on request only, automatically, or off. Only a person changes them in the web interface; the AI has no tool for it. An environment variable takes precedence, so an administrator can lock the choice.
- Offline operation check. A list of conditions for offline operation with a yes/no answer: copilot without cloud providers, update check and usage statistics off, error reports not sent automatically, licence without online renewal, remote access not running.
- Writes, backups and audit in one place. The write mode with a switch, the AI's permissions for PLC download, writing to a running PLC and approving plans, the latest backups, the latest audit entries and an overview of the know-how protection tools.
What the AI assistant sees and how to protect know-how
The AI works with the project only through the TIA MCP tools. Whatever the tools do not return, the AI does not see.
Only what the AI requests
The AI sees the results of the tools it calls itself – for example one block or one tag table. TIA MCP sends it nothing on its own.
Know-how protected blocks
TIA MCP cannot read the logic of a know-how protected block – Openness only returns the interface. The AI sees inputs and outputs, not your solution. You switch protection on in TIA Portal or with the tia_protect_block tool: without the password, the block code can then be neither viewed nor edited.
Passwords outside the chat
Tools for know-how protection of blocks, project protection, the PLC and the CPU web server read the password from a file or environment variable. The password is not returned to the AI and is not written to the write log. Block write protection (V21) and project protection have their own tools.
A smaller tool set
A profile decides which tools the AI can see at all: PLC only, HMI only, documentation only or read only. In the read-only profile, write tools are not available, not even indirectly.
Web interface on this PC only
The TIA MCP web interface listens only on 127.0.0.1 and every request must carry an access token. It cannot be reached from another computer.
Remote access only on request
For ChatGPT, Claude.ai or Microsoft 365 Copilot you switch it on yourself, through a tunnel with a token or OAuth login. By default the remote client can only read, and writing cannot be unlocked through it.
Changes to the project under control
AI in TIA Portal can also change the project. That is why every change has a safeguard, a backup and a trace.
Read-only mode
In read-only mode no tool can change the project. Both the AI and a person can lock it, only a person can unlock it: by confirming in the AI client, in the web interface or with Unlock_Write.bat.
Backup before an object is changed
Before a block, tag table, UDT, watch table or HMI screen or tags are changed, the object is saved as a snapshot on your disk. The tia_restore_snapshot tool reverts the change. If the object cannot be backed up, the write is not carried out.
Change plan for approval
The AI prepares a larger change as a plan. It is only carried out after approval. You can take approval away from the AI – then only a person approves the plan in the web interface. A plan can also run in a single TIA transaction: either all of it goes through, or everything is rolled back.
Write log
Every write goes to logs/write_audit.jsonl: time, tool, parameters (passwords and tokens hidden), backup ID and result. Changes to the AI's permissions have their own log.
Git and change report
A text export of the project to your Git repository, the diff since the last commit and a readable change report: blocks, safety separately, UDTs, tags and HW. Push only after confirmation, never a force push.
Real PLC only with confirmation
Download to the PLC and writing values to a running PLC are switched off for the AI by default. Only a person can switch them on in the web interface. Even then writing must be enabled, and there is first a preview of the impact, a one-time token valid for 5 minutes, and the user has to type the device name.
TIA MCP changes the engineering project. Check every change before downloading it to the PLC or HMI – by compiling, code review and a test in PLCSIM Advanced simulation.
Local AI without internet
If the project must not leave the company, use TIA MCP with a local model. All work with the AI then stays on your computer or a server in your company network. Cloud models keep working alongside it – the choice is yours.
- Copilot in the web interface. Install Ollama or LM Studio and download a model. TIA MCP finds the local server on this PC by itself (Ollama, LM Studio, llama.cpp). A model on a GPU server in your company network is set up by entering the server address. The TIA MCP installer can install Ollama with a model.
- MCP client with a local model. For example LM Studio, which the installer configures for TIA MCP, or VS Code and Open WebUI. For small models there are the local and local_write profiles with a smaller tool set.
- Installation without internet. A portable distribution with its own Python, a license.lic file activated on another PC, updates as a signed package and a model copied from a computer with internet. The licence is verified offline.
- What to expect. Smaller local models reliably read the project, search and answer questions. They are weaker at generating code and long tasks, and the result has to be checked. Do not entrust a safety program to a small model.
- Virtual machine. In a virtual machine the licence is renewed online at least every 30 days. For isolated virtual machines we offer a custom licence.
You will find the detailed installation procedure in the guide Installing TIA MCP.
TIA MCP in your company: Enterprise
Deploying AI in TIA Portal in a larger team or a secured network? We will prepare a tailored offer and demonstrate TIA MCP online on your project.
- More than 20 computers on one order and one invoice
- Silent installer mode for administrators (/VERYSILENT) and mass roll-out
- Virtual machines and operation without internet by agreement
- Help with deployment: AI clients, a local model on a company server, rules for writes and approvals
- Training for programmers and service staff on your project
Licence prices and terms are on the page TIA MCP licences.
FAQ on data and know-how
The answers apply to TIA MCP 2.19. Do you have another question from IT or security? Write to us.
Is my TIA Portal project sent to the cloud?
TIA MCP does not send the project anywhere; it works with it locally through Openness. Only the data requested by the AI assistant goes to the cloud, and only if you use a cloud model (Claude, ChatGPT, Gemini, Copilot). With a local model, the data does not leave your computer or company network.
Will Benešl Automation see my project?
No. TIA MCP only talks to our server for the licence, the update check, usage statistics and error reports. The statistics contain only versions, the licence type and counts of starts and tool calls; error reports are anonymised. You can switch both off in the installer or on the Data and security page. The project, blocks and PLC data are never sent to us.
Can the AI delete or break something in the project?
Not in read-only mode – and only a person can unlock it. In write mode, a backup is saved before a block, tags or a screen are changed, and every write goes to the write log. The AI prepares larger changes as a plan that is only carried out after approval.
What if the AI makes a mistake?
You revert the change from the backup with the tia_restore_snapshot tool, and a block comparison or Git shows the differences. Check the result like a colleague's work: compile, code review and a test in PLCSIM Advanced. The AI will not download anything to a real PLC without your explicit confirmation.
Can AI in TIA Portal be used completely without internet?
Yes. With a local model (Ollama, LM Studio, llama.cpp) on the computer or a server in your company network, a licence activated with a file and the update check, usage statistics and automatic error reports switched off. The Data and security page shows whether the conditions are met. The exception is a virtual machine, where the licence is renewed online at least every 30 days – for isolated virtual machines we offer a custom licence.
Who sees my data?
You and the AI model provider you choose, under their terms. The copilot in the web interface uses your own API key. With a local model, nobody else. Backups, the write log and the Git repository stay on your disk.
How do I protect the know-how in blocks from the AI?
TIA MCP cannot read a know-how protected block: Openness returns only the interface, not the logic. You switch protection on in TIA Portal or with the tia_protect_block tool using a password from a file or environment variable. For projects that must not leave the company, use a local model.
Siemens, SIMATIC, TIA Portal, WinCC and S7 are trademarks of Siemens AG. TIA MCP is an independent product of Benešl Automation, is not a Siemens product and works with TIA Portal through the official TIA Portal Openness interface. Claude, ChatGPT, Gemini, Copilot and other names are trademarks of their respective owners.