octoplant PLC Support: Siemens, Rockwell, Schneider and Other Engineering Software

octoplant PLC support is where most evaluations start, because programmable controllers are the devices every plant knows it has to protect. The short answer is that partner pages list the major PLC platforms and their engineering tools, from Siemens and Rockwell through Schneider, Beckhoff, CODESYS, B&R and Mitsubishi. The longer answer is that “supported” depends on the editor version as much as on the vendor, and that the legacy platforms carry dependencies of their own. This page covers both, as one of the three device pages under octoplant supported devices.

octoplant PLC support by vendor: examples

The table below collects examples from partner pages (iOpen, Adeptly) and AMDT release notes. It is not a support matrix. The official matrix sits behind the myAMDT login as of October 2026, and you should check every version you run against it.

Vendor	Engineering tools named (examples)	What to confirm with AMDT
Siemens	STEP 5, STEP 7, TIA Portal, SIMOTION	Which TIA Portal versions, and whether multiple versions run side by side
Rockwell Automation	RSLogix 5, RSLogix 500, Studio 5000	Which Studio 5000 major revisions, and how the upload reaches the controller
Schneider Electric	Concept, Modsoft, PL7 Pro, Unity / Control Expert, EcoStruxure	Which tool covers which controller generation
Beckhoff	TwinCAT	TwinCAT 2 and 3 handling, and how projects with source control are treated
CODESYS	CODESYS-based IDEs	Which OEM variants of CODESYS are covered
B&R	Automation Studio	Supported versions
Mitsubishi Electric	GX Works2 (added in release 105)	GX Works3 status
Others	Phoenix Contact PC WORX, Emerson (GE) Proficy Machine Edition, Bosch, Pilz, WAGO, Eaton, Hitachi	Model and version detail

Coverage changes with each release. octoplant 105 (August 2025) added GX Works2 and newer EcoStruxure versions, among others (Novotek UK). A list that was accurate last year may already be incomplete in both directions.

What a complete PLC record should hold. Whatever the tool, a usable controller backup is more than the logic. In our view, the record a plant needs on the bad day contains:

1. The program and hardware configuration as uploaded from the running controller.
2. The offline project with comments and descriptions, where the device does not store them.
3. The firmware revision and the editor version needed to open the project.
4. The date, the author of the last approved change, and the reason for it.

Points 3 and 4 are what turn a file into something a technician can restore at two in the morning without guessing.

Why editor versions decide octoplant PLC support in practice

A PLC project is stored in the format of the tool that made it. For a backup system, that creates a dependency the vendor name hides. Partner material notes that support for many devices is built into octoplant itself, so browsing and compare do not need the vendor editor (Adeptly). For device types where the upload or a detailed compare does rely on the vendor’s software or drivers, those components must be installed on the octoplant server or agent that runs the job.

Rockwell shows why this matters. In Logix controllers, the Studio 5000 major revision is tied to the controller firmware, so a plant with controllers at several firmware revisions needs several editor versions to open their projects. Rockwell’s Product Compatibility and Download Center is where the supported pairings of software and firmware are checked, and it is worth running your controller list through it before sizing the backup server. Our page on Studio 5000 project structure explains that coupling. TIA Portal has a similar pattern: projects open in the version that made them or are upgraded to a newer one, which a plant does not always want.

An illustrative scenario. A packaging plant runs controllers at three firmware revisions. The backup server has editors for the two newest. Jobs for the oldest line fail quietly, or store a file nobody can compare, and nobody notices until that line needs a restore.

The TIA Portal performance work

Siemens projects are where job duration bites. TIA Portal projects can be large, and a backup and compare cycle that takes a long time limits how often a job can run across a site. According to AMDT’s release information for octoplant 101.3 (May 2024), TIA Portal compare and backup became between four and sixteen times faster, and TIA Portal V19 support was added. AMDT also lists a TIA Portal Integration service among its offerings.

The plant consequence is detection time. If a full pass across fifty Siemens stations takes most of a night, change detection runs nightly at best. Faster jobs mean shorter intervals between an unrecorded edit and the alert that flags it; see octoplant change detection.

Siemens is also building its own tooling. The TIA Portal Version Control Interface adds Git to the engineering side, and Siemens lists octoplant in its ecosystem (Siemens). The two answer different questions: native Git versions the engineer’s project, while a tool like octoplant reads what is actually running across vendors and compares it with the approved version.

Legacy platforms

The oldest controllers need protection most and are hardest to reach. STEP 5, RSLogix 5 and 500, Concept, Modsoft and PL7 all appear on partner lists. These platforms often depend on old communication drivers, serial or proprietary network adapters, and Windows versions that IT no longer wants on the network.

A verified backup is the precondition for migration. No SLC 500 migration or PLC-5 conversion should start without a known-good copy of what is running, compared against whatever is on the server. If the backup tool cannot reach a legacy controller, that controller needs a manual procedure until it is replaced. Planning that sequence is the core of a PLC migration.

Plants on versiondog or AutoSave should note that those products received no new device or editor support after 2025, per partner end-of-life notices. Newer controller firmware may already be outside their reach; see versiondog and AutoSave end of life.

Where it gets hard

• Editor sprawl. Supporting every firmware revision can mean many editor versions installed and licensed on the backup infrastructure, each with its own operating system needs.
• Online edits in mixed states. A controller with pending or test edits may upload a project that differs from both the approved version and what anyone intended.
• Source-protected logic. OEM machines often ship with protected routines. Ask what a backup and compare can see when logic is locked.
• Projects outside the controller. Comments, descriptions and some configuration live only in the offline project, so an upload from the device is not always the full engineering record.
• Safety controllers. Signatures and safety tasks need their own restore procedure, and a restore that changes a safety signature has consequences beyond the backup tool.

For the comparison side of the same problem, see octoplant Smart Compare, and for the assets around the PLC, continue to robots, CNC and drives. Back to the AMDT hub.