Siemens TIA Portal
A dedicated Openness runtime behind the 2ot router: local IPC, workspace synchronization, process control and TIA-specific project operations without coupling Siemens dependencies into the compiler core.
Workspace-aware routing
When the workspace is configured for TIA Portal, a script or LLM harness can keep common commands vendor-neutral: 2ot pull, 2ot push, 2ot buildand 2ot status resolve through the Siemens runtime automatically. Explicit2ot tia ... routes remain available for process, project and Openness-specific operations.
The in-IDE Add-In is one possible harness
2ot provides an Add-In inside TIA Portal so teams that prefer to stay in the vendor environment can trigger routed operations from there. The Add-In is one harness surface alongside scripts and LLM agents: the engineer chooses the interface, while 2ot and the Siemens runtime execute the underlying project operations.
Local IPC bridge
Vendor-side Openness calls run behind a dedicated local bridge instead of being coupled directly to the Rust analysis loop. Requests use JSON-RPC-shaped payloads encoded with MessagePack over a local named-pipe transport.
Batched memory-graph prefetch
The bridge exposes batched prefetch operations for traversing TIA engineering objects, composition relationships and runtime members. This reduces repeated API round trips when the analysis side needs a broader view of the project graph.
| Parameter | Effect |
|---|---|
| maxDepth | Caps traversal depth through composition relationships. |
| parallelFanoutDegree | Controls concurrent traversal of sibling branches. |
| trustGraph | Allows cached graph state to be reused when appropriate. |
VCI workspace synchronization
The Siemens integration works with the Version Control Interface to represent project content in text-oriented forms such as SimaticSD and SimaticML. That gives automation and agent harnesses a bridge between source-oriented workflows and the TIA project environment while keeping vendor-specific behavior behind the integration layer.
API knowledge stays on the licensed workstation
2ot can build a version-aware metadata graph from Siemens PublicAPI assemblies and XML documentation installed on the developer machine. Those Siemens-derived graph artifacts are intentionally local: the public site explains the mechanism, but does not publish the API corpus, generated documentation or local version snapshots.