Standardized Reusable Components
Across Every TIA Portal Project
T-IA Connect exposes 15 MCP tools covering the full TIA Portal library stack. Create master copies, version library types, and distribute standardized components across your project portfolio - all scriptable via REST API or AI agent.
Two Approaches to Reusability
TIA Portal offers two distinct library mechanisms - each with different tradeoffs for versioning, scope, and update management
Master Copies
Snapshot - No Version LinkA master copy is a frozen snapshot of a block, UDT, or tag table stored in a library. When you instantiate it into a project, you get an independent copy. There is no ongoing link to the source - changes to the original do not propagate. Master copies are ideal for templates that rarely change and where independent customization per project is expected.
- Instantiated once - no version tracking
- Works with blocks, UDTs, tag tables, and screen objects
- Can be stored in project library or global library
- Fast to use, no consistency enforcement
Library Types
Versioned - Link MaintainedA library type maintains a versioned lineage. Each version is immutable once released. A default version can be set and all project instances know which version they are based on. T-IA Connect lets you compare library type versions and detect which projects are running outdated instances - enabling a standardization pipeline.
- Multiple versions, each immutable once created
- Default version propagates to new instantiations
- Version comparison detects drift across projects
- Used for safety-critical and regulated components
Library Management Capabilities
15 MCP tools covering every aspect of TIA Portal library operations
Master Copies
Create master copies from existing blocks and UDTs, organize them in folders, instantiate them into any project, and delete obsolete ones. Full CRUD lifecycle via API.
Library Types
Create new library types, add new versions, set the active default version, compare two versions side by side, and delete deprecated types. Version history is preserved.
Project Library
Each TIA Portal project contains a built-in project library scoped to that project. T-IA Connect exposes the full project library tree so you can inventory, export, and replicate its contents.
Global Libraries
Global libraries are standalone .al20 files shared across projects and teams. T-IA Connect can open, close, save, create, and archive global libraries, and retrieve their full content tree.
Creating and Deploying Reusable Components
A repeatable process from design to fleet-wide distribution
Design the Component in TIA Portal
Build your reusable block or UDT in a reference project. Test it thoroughly against real or simulated hardware before promoting it to a library.
Create a Master Copy or Library Type Version
Use T-IA Connect to create a master copy for snapshot distribution, or create a new library type version for versioned, tracked deployment. Set the new version as the default if applicable.
Store in a Global Library
Promote the component from the project library to a global library that is accessible to all engineers. T-IA Connect handles opening, writing, and saving the global library file.
Distribute Across the Project Fleet
Iterate over your project portfolio. For each project, T-IA Connect instantiates the component from the library. Master copies are inserted once; library types create linked instances.
Audit and Update
Use the version comparison tool to detect which project instances are running older library type versions. Generate a drift report, then trigger updates selectively or across the entire fleet.
Version Tracking Across Your Fleet
Library types give you the audit trail that master copies cannot provide
In regulated industries, knowing exactly which version of a safety interlock or motor control template is deployed on each machine is a compliance requirement, not a nice-to-have. TIA Portal library types carry version metadata, but checking them manually across dozens of projects is impractical.
T-IA Connect's compare_library_type_versions tool lets you diff two versions of a library type programmatically. Combined with get_project_library_tree and get_global_library_tree, an AI agent or CI script can iterate over every project in your fleet, retrieve the library type version in use, and flag any deviation from the expected baseline.
The result is a standardization pipeline: a script that runs on a schedule, detects drift, and either reports it or - with the create_from_library_type tool - automatically upgrades the instances across the fleet.
MCP Tools Reference
15 tools covering project libraries, global libraries, master copies, and library types
Project & Global Library Tree
get_project_library_tree and get_global_library_tree return the full folder and item hierarchy of any library. Use as the starting point for inventory or audit scripts.
Master Copy Operations
get_master_copies, create_master_copy, create_master_copy_folder, delete_master_copy, and create_from_master_copy cover the full master copy lifecycle. Instantiate into any open project.
Library Type Operations
get_library_types, create_library_type_version, set_library_type_default_version, delete_library_type, compare_library_type_versions, and create_from_library_type. Full versioned lifecycle.
Global Library File Management
open_global_library, close_global_library, save_global_library, create_global_library, archive_global_library, and list_global_libraries. Manage shared .al20 files as part of your pipeline.
Frequently Asked Questions
What is the difference between a master copy and a library type in TIA Portal?
A master copy is a static snapshot - once instantiated into a project, there is no link back to the library. A library type maintains versioning and a live reference: you can track which version is deployed in each project and compare versions programmatically. Use master copies for independent templates and library types when version consistency across projects matters.
Can T-IA Connect instantiate library types into multiple projects automatically?
Yes. The create_from_library_type tool instantiates a versioned library type into any open project. A script or AI agent can open each project in sequence, call the tool, save, and close - distributing a component across an entire fleet without manual TIA Portal interaction.
Can global libraries be shared across engineers on a team?
Yes. Global libraries are standalone .al20 files that can be placed on a shared network drive. T-IA Connect can open, read, modify, and save global libraries. Multiple engineers can access the same file, though concurrent write access should be coordinated - the same constraint that applies to any shared file.
How does version comparison work?
The compare_library_type_versions tool takes two version identifiers for the same library type and returns a diff of their interfaces and properties. This lets a CI script or AI agent detect whether the version deployed in a project matches the expected baseline, and report or remediate the discrepancy automatically.