tia-openness-roadmap

Goal

Route the task to the correct implementation path and load the right skill files.

Mandatory policy

1. Prefer TIA Portal MCP for interactive, single-step read/write operations when the MCP server is available.
2. Prefer TIA Scripting Python for scripted or multi-step automation.
3. Use C# TIA Portal Openness only if Python is insufficient.
4. Do not invent Python wrapper methods.
5. For multi-domain tasks, select all required skills.

Implementation paths

MCP path

Direct tool calls — no code generation. Use when the TIA Portal MCP server is available.

Python path

Single skill owns all Python implementation:

tia-python contains its own reference file table that routes to the correct references/*.md file based on the task domain (PLC, HMI, library, project, portal).

C# path

Always starts with the common foundation skill, then domain skill(s):

Add-In path

Standalone skill for TIA Portal Add-In development (always C#, VS Code workflow):

Routing rules

MCP vs Python vs C# decision rule

Choose MCP when:

• the task is a single read or targeted write (one block, one device, one compile check)
• the user wants to explore or inspect a project interactively
• no looping, no bulk changes, no code generation is needed
• the tia-portal MCP server is available (check mcp__tia-portal__* tools)

Choose Python when the exact required operation exists in the tia-python reference files. Choose C# when:

• the required operation is absent from the Python reference catalogue
• the task needs low-level object model traversal
• the task needs topology/network object manipulation
• the task needs drive-specific APIs
• the task needs advanced online/security/session/event APIs
• the task needs Teamcenter, VCI, advanced multiuser, or unsupported safety/Unified features

Multi-skill execution order

1. project / portal
2. device selection
3. domain work
4. import/export
5. compile / compare / download / validation

Required response format

Use this exact structure:

• Use skill(s): ...
• Implementation path: MCP or Implementation path: Python or Implementation path: C# Openness
• Reason: ...
• Execution order: ...

Post-routing action — MANDATORY

If MCP: read skills/tia-portal-mcp/SKILL.md. Use the MCP tools directly — no code generation.

If Python: read skills/tia-python/SKILL.md, then load the reference file(s) it points to for the task domain. Do NOT load domain skills — they are for C# only.

If C#:

1. Read skills/tia-csharp-common/SKILL.md first — always, for every C# task.
2. Read the SKILL.md and reference_catalogue.md of each selected domain skill. Use the file paths from the C# domain skills table above.

If Add-In: read skills/addin-operations/SKILL.md. No other skills needed.

Do NOT write code based solely on the routing response — always load the skill files first.

Escalation rule

If implementation starts in Python and the required call is not documented:

• stop
• switch to the corresponding C# domain skill
• load tia-csharp-common first, then the domain skill
• keep the same task decomposition

Hard escalation triggers (always C#)

• device item slot/subslot operations
• subnet/node/IO-system/port/channel/address manipulation
• Teamcenter / ConnectSSO
• VCI / advanced multiuser
• advanced PLC online/security services
• advanced Unified internals
• drive-specific engineering
• diagnostics / event handlers / self-description APIs