octoplant Release Notes: Release History from 101.3 to Spring Release 107

octoplant release notes are published in full only inside AMDT’s myAMDT customer portal, so most people evaluating the platform see fragments: a press item here, a partner summary there. This page puts the public releases in one table, as of October 2026, says what each changed for the people who use the tool, and sets out how a plant should handle an upgrade.

For what the platform does, see the parent page on octoplant. For the company and its products, see the AMDT hub.

octoplant release notes at a glance

Date	Release	What changed for users	Source
2022	octoplant launch	Successor to versiondog and AutoSave, combining the two after the AUVESY-MDT merger	Novotek
May 2024	101.3	TIA Portal compare and backup reported as 4 to 16 times faster; TIA Portal V19 support	AMDT knowledge base (behind myAMDT login)
8 Aug 2025	105	First web interface, REST export API, standardised Asset Inventory format, PostgreSQL 17, Outpost24 pen-test fixes, new device and editor support	Novotek
6 Oct 2025	octovision launch	A new intelligence layer over octoplant data: multi-site assets, CVEs, backup status	AMDT
7 Apr 2026	Spring Release 107 (“Built to Bloom”)	Project Integrator Tool, Asset Lifecycle view, octovision Export API to ITSM, AI chat (Companion), security updates, wider device support	AMDT
Summer 2026	octovision Summer Release (“Built to See”)	CSV import of external assets, managed vs unmanaged coverage, criticality classification, false-positive handling, automatic CVE updates	octoplant.com

Version numbers between these releases are not covered in the public sources we used. Treat the table as the headline changes, not a complete changelog.

What the octoplant release notes mean in plant terms

101.3: faster work on Siemens projects

Large TIA Portal projects are slow to upload and compare, and a compare that takes too long gets run less often. A reported 4 to 16 times speed-up on TIA Portal compare and backup, with V19 support, matters most to Siemens-heavy sites with many large projects. We could not confirm this release from a public page; it comes from AMDT knowledge-base material, so verify it with AMDT.

105: a browser, an API and a security pass

Release 105 is the one that changed how people outside controls engineering touch octoplant:

• The first web interface. According to Novotek, users can view components, download ZIP files and launch preconfigured jobs from a browser. Maintenance leads and managers no longer need a desktop client to check status.
• A REST export API for sending data to external systems, the start of the integration story covered in export API.
• Security. Fixes following an independent penetration test by Outpost24.
• Platform. PostgreSQL 17 and 7-Zip 25.00. A database version change is the kind of upgrade that needs a tested backup first.
• Device and editor support. Fanuc Ladder III 9.6, FactoryTalk View, SEW MOVI-C and GX Works2, plus newer zenon, EcoStruxure and SINUMERIK ONE versions.

octovision and the 2026 releases: from backup tool to asset intelligence

The October 2025 octovision launch and Spring Release 107 moved the platform beyond backup and versioning. Release 107, per AMDT, added:

• Project Integrator Tool, which AMDT says cuts deployment tasks “that previously took days or weeks” to “within hours.” This matters most when onboarding a new plant or migrating from versiondog or AutoSave.
• Asset Lifecycle view, to “identify outdated components and plan updates or migrations before they become urgent.” See lifecycle and obsolescence.
• Export API to ITSM platforms, with ServiceNow named.
• AI chat, answering questions from operational data. See AI Companion.

The octovision Summer Release then let plants import assets octoplant does not manage, by CSV from discovery tools, CMMS or spreadsheets, and see the gap between managed and unmanaged assets.

The release cadence

Three patterns are visible in the public record:

1. More releases than are announced. Publicly announced releases fall in May 2024, August 2025 and April 2026, but the numbering runs from 101 to 107 in that period, so several releases were not publicised. Read the full notes in myAMDT rather than relying on announcements.
2. Named seasonal releases from 2026 (“Built to Bloom”, “Built to See”), which suggests a more regular, marketed rhythm.
3. Two products releasing in step. octoplant and octovision now share releases and features, so an upgrade decision on one may affect the other.

Legacy products are on a different clock. versiondog and AutoSave run end-of-life phases to the end of 2026. Sites on them are not choosing whether to upgrade but when to migrate; see versiondog and AutoSave.

How a plant should handle an octoplant upgrade

A backup and recovery tool is part of your recovery plan. Upgrading it carelessly can leave you without a working restore at the moment you need one. A procedure that works for this class of software:

1. Read the full release notes in myAMDT, including known issues and dropped support, not only the announcement.
2. Check your device and editor matrix. Confirm every device family and engineering software version you rely on is still supported, and note what is new.
3. Check component compatibility. Server, clients and agents usually need matching versions; plan to upgrade them together. See architecture.
4. Back up the server, repository and database off the server, and confirm the backup restores.
5. Test in a non-production environment with a copy of real data: run jobs, compares and one full device restore.
6. Schedule the production upgrade outside critical production and away from planned shutdowns, when engineers are not relying on the tool.
7. Verify after the upgrade: jobs run, alerts arrive, the web interface and APIs respond, and one restore works.
8. Keep a rollback until you are satisfied, including the pre-upgrade database backup.

Validated environments add steps. In pharma and other GxP settings, the tool is part of a validated system. An upgrade is a change under your change control: assess its impact, update the validation documents and re-execute the relevant qualification tests. AMDT offers IQ/OQ services; see 21 CFR Part 11. This is also where the factory acceptance test discipline used for control systems carries over well.

Where it gets hard

Release notes are gated. Without myAMDT access, an evaluator cannot see known issues or dropped support. Ask for the last two releases’ full notes during evaluation.

Engineering software moves too. A new TIA Portal or Studio 5000 version may need a newer octoplant release before uploads and compares work. Coordinate the two upgrade plans.

Skipping releases. Jumping several versions, especially across the database change in 105, needs an upgrade path from AMDT, not a guess.

Nobody owns the upgrade. The tool runs quietly for years, and the server falls behind. Put the upgrade in the maintenance plan with a named owner.

For what each edition includes, see editions and licensing.