Features

FAQ Platform Features Integration Compliance Company

What does PLC Code Merge do?

PLC Code Merge enables engineers to compare and merge PLC program versions with full diff visualization — similar to Git merge workflows in software development. When multiple engineers work on the same automation program, or when changes need to be rolled back, PLC Code Merge prevents conflicts from silently overwriting production code. It provides a structured, auditable review process before any change is committed to the live system.

What is Browser-Based PLC Editing?

Browser-Based PLC Editing allows automation engineers to view, edit, and review PLC code directly in a web browser — without needing a locally installed engineering tool like TIA Portal or Studio 5000. This reduces setup time, enables remote access, and allows cross-functional teams (including IT, quality, and operations) to review automation code without specialist software licenses.

What is IDEaaS Session Recording?

IDEaaS Session Recording captures the full engineering session when a technician edits automation software — including what was changed, in which tool, by whom, and when. This creates an immutable activity log that supports root cause analysis, compliance audits, and knowledge transfer. It is particularly valuable in regulated industries where change documentation is mandatory.

What is Live Value Sampling?

Live Value Sampling allows engineers to observe real-time data from PLC variables and process signals directly within the SDA platform — without switching to a separate SCADA or monitoring tool. This enables faster debugging, validation of changes, and direct correlation between code edits and live machine behavior, reducing the feedback loop between development and production.

What is the Desktop Sync Client?

The Desktop Sync Client keeps local engineering environments in sync with the SDA platform in the background. Engineers continue working in their familiar tools (TIA Portal, Studio 5000, etc.) while changes are automatically versioned, tracked, and pushed to the central SDA repository. This eliminates the manual step of uploading or checking in files, reducing the risk of unsaved or untracked changes going unnoticed.