TIA Portal projects utilizing Local User authentication are now supported in Copia. Now a repository administrator can store the project's Local User username and password in Settings › Project File Secrets, and every protected project file in that repository opens and shows differences like any other project.

Supports TIA Portal V15 and later. If you don’t see Project File Secrets in your repository settings, contact Copia support to have it enabled for your organization. Read the docs here.

Hey there,

We're upgrading our TIA Portal support - Copia now renders and diffs SIMOTION inside a TIA Portal v14 to v20 zap files. 

Supported project items

• ST source
• Technology objects
• Symbols
• Tasks
• I/Os
• ITO CAM Graphs

For our DeviceLink customers, we are excited to share our newest feature with you: an organization-level dashboard that aggregates DeviceLink performance metrics and visualizes the effectiveness of your backup strategy in real time.

Recovery Point Objective monitoring

In this update, we are introducing a first-of-its-kind organization-wide Recovery Point visualization, allowing you to see at a glance whether your organization is meeting its RPO targets. This visualization shows the age of the most recent backup for every project at your site. If you needed to restore all of your backups today, this visualization shows how old your most recent restore points would be. It is a real-time monitor of how well your backup strategy is protecting you.

Visualizing your environment by criticality level

In a recent update, we launched device criticality labeling, allowing you to label your Devices with criticality levels. On this dashboard, we are introducing the ability to facet views by criticality level. Both the Recovery Point Distribution chart and the Last Backup Status chart can be faceted by criticality level.

Criticality levels are set on Devices, but Projects inherit the criticality level of their linked Device(s). For Projects with multiple linked Devices, they inherit the criticality level of the most critical linked Device.

These views can be especially useful to compare the backup performance of your critical Devices against the rest of your Device inventory.

Additional Visualizations

The new DeviceLink dashboard also contains a number of additional visualizations, including:

• an organization-wide job status graph, 
• a chart aggregating the most recent backup status per project,
• an organization-wide agent utilization table, and
• a breakdown of Devices by vendor and type.

Read the full description in our documentation to learn more about the DeviceLink Dashboard.

Your workflow runs just got a massive improvement: Copia is now rendering enriched job summaries, including aggregating and displaying test results directly in the workflow run details. See the steps your workflows are taking, where they failed, and any outputs that the workflow renders, easily. 

The job summaries support markdown and mermaid chart rendering so you can render exactly the output needed for your runs.

In order to help our DeviceLink users develop targeted disaster recovery strategies, we are introducing a "Device Criticality" field to DeviceLink Devices. You can now label each of your Devices in Copia with a criticality level (Low, Medium, or High). The field is optional and is blank by default.

Device Criticality is shown as a label on Device cards and as a field in our Public API. In the future, we will be announcing additional functionality and data visualization options based on Device Criticality.

Now, in addition to our Source Control product, we happy to bring Siemens TIA Portal v21 for DeviceLink automated backups. 

See our documentation for more information on supported file types. 

Copia Actions is now available — a workflow engine built directly into Copia that lets you automate the repetitive tasks your team has been running by hand.

What's new

Copia Actions lets you define workflows that live alongside your code in Copia. Lightweight, self-hosted workflow runners execute those workflows based on triggers like commits, pull-requests, issues, or DeviceLink backup events. Results and artifacts can be stored directly in your repo for audit-worthy change tracking and management.

How it helps

If your team is manually running mirror scripts, rebuilding compliance reports from git logs, or doing drift audits by hand, Actions can help automate the cycles. You can standardize the operations and share as part of a repo template to make sure every repo you create in Copia inherits your quality.

Learn More

We're happy to announce that Copia now supports Siemens TIA Portal v21 for Source Control rendering. Support for DeviceLink automated backups is planned soon.

No user action is required in Copia to start version controlling Siemens TIA Portal v21 project files. See our documentation for more information on supported file types. 

At Copia, protecting the OT networks our customers rely on is a core responsibility. The DeviceLink Agent runs inside some of the most sensitive parts of your industrial infrastructure, and we hold that trust seriously. That's why we're announcing an important security improvement to how the DeviceLink Agent handles Script backup jobs.

What Changed

Previously, Script backup jobs could pull any script file stored in a Copia repository and execute it directly on the host running the DeviceLink Agent — without any additional controls on the agent side. While this required write access to Copia's web application to configure, it still meant that a script stored in Copia could run with the full privileges of the agent process on a machine sitting inside your OT network.

Starting today, every script that a backup job attempts to execute must be pre-approved in an allowlist file on the host running the agent. This allowlist can only be modified by an administrator account on the agent host. If a script's path is not in the allowlist, the backup job will fail immediately and the script will not run. This moves control of what can execute on your OT servers from the Copia web application to the server itself, where your IT and OT security teams have direct authority.

Who Needs to Take Action

If you are currently running Script backup jobs, in order to ensure operational continuity, we have automatically generated a script allowlist for you based on the scripts you have already configured in Copia. You should verify that the allowlist file exists on each host running the DeviceLink Agent and that it contains the paths of your authorized scripts.

If you are setting up new Script backup jobs, you will need to create the allowlist file manually before those jobs will execute successfully.

Our documentation contains detailed instructions on how to create and use the script allowlist.

Why This Matters for OT Security

The principle of "defense in depth" is foundational to OT cybersecurity: every additional step taken towards hardening your security is cumulative. By requiring scripts to be explicitly approved on the agent host, we ensure that no change to a Copia repository, whether accidental or malicious, can cause arbitrary code to execute on a machine inside your OT network without the explicit approval of the team managing that server.

We will continue to invest in security improvements like this one to protect your OT infrastructure. If you have questions about this change or need help with your existing script backups, please reach out to our support team.

We're excited to announce enhancements to our Advanced Merge Tool in Source Control, designed to give you even greater flexibility when merging Siemens TIA Portal projects.

What's New?

Available now, our latest update introduces deeper merge capabilities for Structured Text (SCL) routines in TIA Portal projects. Building on the DB and Tag Table merge support we released last year, the Advanced Merge Tool now provides line-level merge resolution for SCL files. This means you can resolve conflicts with greater precision, choosing specific lines within an SCL routine instead of being limited to accepting an entire file from one branch.

How This Helps:

• Reduced Rework: No more overwriting a colleague's changes just because you both modified the same SCL file. Pick and choose the exact lines you need.
• Improved Collaboration: Merge code changes from multiple contributors to the same Structured Text routines with confidence and ease.
• Enhanced Accuracy: Maintain code integrity and minimize the risk of errors during complex merges — especially for large SCL files where only a few lines have actually changed.
• Increased Speed: Spend less time manually reconciling changes outside of Copia, and more time shipping code.

This enhancement is part of our ongoing commitment to provide you with the most powerful and user-friendly Industrial DevOps platform. We continuously strive to meet the evolving needs of our customers and improve your experience.

Learn More:

For detailed information and examples of SCL Line-Level Merge in action, please visit our updated documentation.