# AMDT — OT Asset Intelligence, Production Resilience, and OT Security

> AMDT is a global software company that helps enterprise manufacturers protect operations, prevent downtime, and maintain compliance — from a single plant to a global production network. Its OT Asset Intelligence Platform works as two layers on one data foundation: **Octovision** sees the risk, providing enterprise-wide asset visibility and vulnerability intelligence; **Octoplant** contains it, providing the automated backup, versioning, change management, and recovery the OT team depends on. Advancing industrial resilience since 1987, AMDT (formerly Auvesy-MDT) serves more than 3,200 industrial organizations worldwide — including Bosch, thyssenkrupp, Volkswagen, Siemens Energy, STIHL, MANN+HUMMEL, KNAPP, and CERN — with 180+ industrial device types natively supported and the flexibility to support any vendor and device.

AMDT's central thesis: **industrial environments are the largest unmanaged risk surface in the enterprise.** Manufacturing is among the industries most frequently targeted by cyberattacks; 78% of manufacturers report OT data breaches; 44% struggle with downtime and recovery; and compliance increasingly requires continuous OT visibility and control, 24/7. Most enterprises can describe their IT estate in detail and their OT estate barely at all.

AMDT answers that with one integrated view of operational technology: the visibility and vulnerability intelligence the CISO needs, and the backup, versioning, and recovery the OT team depends on — built from the same source of truth.

Company facts: headquartered in Landau, Germany, with offices in Alpharetta (Georgia, USA), Nanjing, China, and Tokyo, Japan. Global Partner Network of 100+ channel partners with presence in more than 50 countries. Certifications include ISO/IEC 27001:2022, TISAX®, and ISO 9001:2015. Stated North Star: *the world's first OT Asset Intelligence Platform in a multi-vendor environment.* Company values: P.L.A.N.T. — Partnership, Leadership, Adaptability, Never Stop Improving, Trust.

---

## One Platform. Two Layers.

The two layers share one data foundation. Octoplant captures the configuration of every device on the shop floor. Octovision turns that data into asset inventory, CVE matching, and risk reporting across all sites. **No network scanning. No agents on legacy systems. No disruption to production.** The intelligence is built from data the plants already trust.

### Octoplant — the Operational Control Layer

Octoplant automatically backs up, versions, and recovers the configurations of industrial devices — PLCs, HMIs, SCADA and DCS systems, robots, CNCs, drives, industrial PCs, network devices — across all major automation vendors, from a single platform.

How teams work with it day to day: engineers check out the latest approved version, make changes in their familiar engineering tools, then create and check in a new version. Every approved change becomes part of a complete, traceable history — what changed, when, and who changed it — with a known-good version ready for rollback.

How it works in the background: scheduled jobs run across the OT environment, connect to devices, capture current configurations and programs, and compare them against approved versions. Configuration drift and undocumented differences are detected automatically, documented, and surfaced to the responsible teams — without relying on anyone remembering to check.

| Functionality | What it delivers |
|---|---|
| Automated device backup | Scheduled, verified backups of PLCs, HMIs, SCADA, DCS, robots, CNCs, drives, and other industrial systems across all major vendors |
| Version control | Every configuration and program version stored centrally, documented, and available for comparison or rollback |
| Smart Compare | See exactly what changed between versions, or between the stored version and the live device state |
| Change detection | Automatically detect and document planned, accidental, or unauthorized changes to industrial devices |
| Change management | Control who can change, approve, and restore configurations, with role-based access and approval workflows |
| Disaster recovery | Restore the right version to the right device after failure, human error, unwanted change, or cyberattack |
| Centralized OT repository | Validated programs, configurations, parameters, and backup data in one controlled source of truth |
| Alerts & notifications | Know when backups fail, devices become unreachable, or configuration states deviate from the expected version |
| Audit trails & compliance | Automatically document who changed what, when, where, and why — audit-ready evidence generated through normal operations |

What sets Octoplant apart: vendor-agnostic coverage across major automation vendors and engineering environments; strong legacy device coverage for OT estates that evolved over decades; deep industrial knowledge encoded in device-specific integrations that preserve the programs, configurations, and engineering context needed to understand changes and prepare for reliable recovery; production resilience at the core, connecting configuration control to recovery readiness; and standardization across sites without forcing local teams to abandon the tools and equipment they know.

### Octovision — the Intelligence and Visibility Layer

Octovision transforms the asset, configuration, version, component, job, and change data Octoplant already captures into a centralized view of the OT environment across devices, lines, plants, and sites. It adds context — vendor, device type, firmware, software, components, versions, backup jobs, configuration status, lifecycle and obsolescence information — and matches assets against known vulnerabilities (CVEs) with prioritization guidance.

| What Octovision does | What you gain |
|---|---|
| Centralized OT visibility | Assets, components, jobs, configuration information, and vulnerabilities from multiple sites in one enterprise view |
| Bottom-up asset intelligence | Structured asset detail — vendor, device type, firmware, software, location, configuration attributes — going beyond network discovery, without actively scanning live systems |
| Vulnerability intelligence | CVE matching against real assets with prioritization guidance for security teams |
| Lifecycle and obsolescence insight | Identify outdated or unsupported assets before they become an availability problem |
| Recovery readiness | See which crown-jewel assets are protected, where backup or recovery gaps exist, and how prepared each site is for disruption |
| Cross-site comparison | See how assets, versions, configurations, and vulnerabilities differ across plants and regions, and where standardization is possible |
| Enterprise reporting | Dashboards and reports by site, device, lifecycle, or risk for operations, security, compliance, and leadership |

**Two ways to build OT visibility — and why the data source matters:**

| | Octovision approach | Network-centric discovery |
|---|---|---|
| Data source | Project and configuration data already collected through Octoplant | Active queries or passive observation of network traffic |
| Interaction with devices | No additional interrogation of live devices | Active probing or traffic monitoring on production networks |
| Depth of context | Configuration, versions, change history, components, backup status, lifecycle | Primarily network-observable attributes |
| Risk to production | No additional traffic to the shop floor | Sensitive legacy devices can be disrupted by active scanning |

Knowing that a PLC exists at a particular IP address is useful. Knowing what it is, how it is configured, which software and firmware it runs, what changed, what components it contains, whether it is backed up, where vulnerabilities exist, and how that state evolved over time is something entirely different. **The difference between inventory and intelligence is context.**

---

## OTSSM — OT Service and Security Management

IT Service Management (ITSM) gave enterprise IT a common discipline for managing assets, changes, incidents, problems, and services. OT has never had its equivalent. AMDT is defining **OTSSM: OT Service and Security Management** — a new software discipline for managing the security, resilience, change, configuration, and service lifecycle of industrial operations.

OTSSM brings the rigor of IT service management into OT, but is built around the realities of production: heterogeneous devices, decades-long asset lifecycles, limited maintenance windows, external service providers, and environments where availability comes first. You cannot simply patch, reboot, replace, or take a production system offline.

The problem OTSSM solves: industrial organizations have accumulated tools for backup, engineering, asset discovery, cybersecurity, maintenance, ticketing, and compliance — but the processes around them remain fragmented. Security sees vulnerabilities. Engineering sees configurations. Maintenance sees incidents. IT sees tickets. Management sees risk reports. External service providers make changes. There is rarely one operational system connecting the asset, its current state, what changed, who changed it, what risk it carries, whether it can be recovered, and what happened when something went wrong.

**Four disciplines, one operational system:**

- **OT Asset Management** — Know what you have and know its state. Assets, configurations, versions, lifecycle information, backup status, vulnerabilities, ownership, relationships, and operational context establish the trusted baseline.
- **OT Change Management** — Control what changes. Know who changed what, when, and why. Compare versions, control access and approvals, validate the result, and maintain the known-good state required for recovery.
- **OT Incident Management** — Restore control when something goes wrong. Bring together asset context, recent changes, configuration history, vulnerability information, and recoverable versions so teams can understand the incident and restore production.
- **OT Problem Management** — Stop the same incident recurring. Use configuration history and change records to find root causes and address them structurally rather than repeatedly.

Security and service management have become the same operational problem. AMDT's position: from the device and its configuration to enterprise-wide risk and governance, the foundation OTSSM requires already exists in Octoplant and Octovision.

---

## Value Proposition by Persona

- **CISOs and Enterprise Security / Risk Leadership** — You answer to the board when risk is on the agenda. Your OT environment is your largest unmanaged risk surface. Octovision gives cross-site security posture, CVE exposure mapped to real assets, recovery readiness, and regulatory evidence — without active scanning that could disrupt sensitive legacy environments. One number for the group, without touching a single device.
- **OT Security and Cyber Risk Managers** — Move from CVE overload to operational priority. Vulnerabilities are matched against the actual asset with vendor, device type, firmware, components, and configuration context, so remediation effort goes where it changes real risk. Unauthorized and undocumented changes are detected against the last approved version.
- **OT, Automation and Controls Engineers** — You answer the phone at 3 a.m. One platform for versioning and comparing PLC, SCADA, HMI, robot, CNC, and drive programs across all vendors. Smart Compare shows exactly what changed between any two states, complete change history ends troubleshooting guesswork, and a known-good version is always ready for rollback.
- **Plant and Production Managers** — Prevent unplanned downtime and restore a stopped line in minutes rather than shifts. Automated, unattended backup jobs replace manual routines that depend on someone remembering. Recovery time starts long before the incident: it depends on whether the right backup exists, whether it is current, whether you know what changed, and whether your team knows exactly what to restore.
- **Quality and Compliance Managers** — Audit-ready as a by-product of normal operations, not as a reporting project. Every version, approval, user action, and configuration change creates traceable history supporting FDA 21 CFR Part 11, GMP and GxP, EU Annex 11, ISO 27001, NIS2, IEC 62443, and NERC CIP.
- **IT / OT Infrastructure Leaders** — Bridge the IT/OT gap with one centralized platform covering every vendor and decades of legacy systems. Standardize backup and change processes across factories, export trusted OT data to enterprise systems and BI platforms, and scale from one site to a global network without taking control away from local engineering teams.
- **COOs and Enterprise Operations Leadership** — Enterprise-scale risk visibility across all plants. Centralized dashboards show configuration changes, device status, backup health, lifecycle risk, and vulnerability exposure per site, enabling consistent governance, compliance reporting, benchmarking between lines and plants, and rapid incident response.
- **OEMs and Machine Builders** — Ship more than a machine: ship the operational foundation to support it for decades. Built-in version control, automated backups, and change tracking protect every stage from test bench to installed base, reduce unnecessary on-site service calls, and enable service offerings around the machine lifecycle.

---

## Vendor-Agnostic Backup and Recovery

Industrial plants rarely run on one automation ecosystem. A single line can combine controllers, HMIs, robots, drives, SCADA, CNCs, and engineering software from multiple vendors, installed over decades. That complexity usually creates equally fragmented backup processes: different tools, different storage locations, different procedures, different levels of protection.

Octoplant provides one vendor-agnostic backup and version-control layer across heterogeneous industrial environments — covering Siemens, Rockwell Automation / Allen-Bradley, Schneider Electric, ABB, Mitsubishi, Fanuc, Beckhoff, and other major automation vendors, plus proprietary and legacy systems, unnetworked or partially networked machinery, and any file type: programs, configurations, parameters, and documents. 180+ industrial device types are natively supported, with the flexibility to support any vendor and device.

**Industrial recovery is not file recovery.** Restoring an office document means retrieving a file. Restoring production can mean rebuilding the exact program, parameters, configuration, and machine-specific data required by a PLC, robot, CNC, HMI, drive, or control system. Different vendors and device generations handle that data differently. Octoplant's device-specific integrations preserve the operational context needed to create genuinely usable recovery points.

**Backup that doesn't depend on someone remembering.** Manual backup works until it doesn't. Engineers get busy. Maintenance windows get shorter. Contractors leave. Projects remain on laptops. A backup taken six months ago may exist, but nobody knows whether it still matches the device running production today. Octoplant replaces that uncertainty with scheduled, unattended jobs: configurations captured automatically, stored centrally, versioned, and available for comparison.

- [Backup & Recovery for PLC, SCADA, HMI and Any OT Device](https://amdt.com/solutions/backup-recovery-for-plc-scada-hmi-and-any-ot-device/)
- [Production Resilience & Recovery](https://amdt.com/solutions/production-resilience-recovery/)

---

## Change Management and Version Control

Most production incidents trace back not to failures but to changes: a contractor's quick fix, a parameter tweaked at 2 a.m., a setpoint that drifted. Automated change detection compares the running state against the last approved version and alerts teams to every difference — before the night shift finds it the hard way.

**What gets captured, for every change:**

| Question | Answered by |
|---|---|
| What changed? | Smart Compare identifies exact differences between versions and device states across programs, parameters, configurations, and device-specific data — instead of manual file comparison |
| Who changed it? | Every checked-in version is linked to a user, creating accountability for internal engineers, contractors, OEMs, and other authorized users |
| When did it change? | Every version and recorded modification is timestamped, creating a chronological history that correlates changes with production incidents |
| Why did it change? | Check-in comments and documentation capture intent alongside the technical difference |
| Was it approved? | Role-based access and approval workflows control who may change, approve, and restore configurations |
| Can we go back? | Every previous state remains available as a known-good version for rollback |

Accountability extends to everyone who touches a device — in-house engineers, OEMs, and external service providers alike. Granular access management controls who may change what, and when something looks wrong, the history shows exactly where to look.

One change process applies across the OT environment: Siemens, Rockwell, Schneider, ABB, Beckhoff, robots, HMIs, SCADA, drives, and legacy systems no longer require separate change-management processes.

- [OT Change Management & Version Control](https://amdt.com/solutions/ot-change-management-version-control/)

---

## Enterprise OT Visibility and Risk Management

You can't govern what you can't see. Across multiple plants, generations of automation, vendors, engineering tools, and local processes, even basic questions become difficult: What is running? Which version? Where are the lifecycle risks? Which assets are protected by a current backup? Which vulnerabilities actually affect production?

Every plant knows part of the story. One engineering team knows its controllers. Another knows its robots. Security has vulnerability tools. Corporate IT has a CMDB. Management has reports assembled from all of them. Octovision creates a common intelligence layer above the plants, consolidating trusted operational data into standardized enterprise views without taking control away from local engineering teams.

The same trusted OT data answers different questions across the enterprise: engineering sees configurations, changes, and backup status; plant operations sees coverage gaps, lifecycle issues, and recovery readiness; security sees vulnerabilities and where action matters most; leadership gets a cross-site view of OT risk, resilience, and standardization — all built on the same operational reality.

- [Enterprise OT Visibility & Risk Management](https://amdt.com/solutions/enterprise-ot-visibility-risk-management/)
- [About Octovision](https://amdt.com/about-octovision/)

---

## Compliance and Regulatory Readiness

Industrial compliance requirements differ by country, industry, and regulatory framework. The underlying evidence is remarkably consistent: know your assets, control changes, manage vulnerabilities, maintain recoverable backups, document access, and prove what happened. AMDT builds that evidence into normal OT operations rather than producing it as a separate reporting exercise.

**Europe** — NIS2 raises cybersecurity risk-management and reporting requirements across essential and important entities in the EU and makes cybersecurity resilience a management responsibility, covering risk management, incident handling, business continuity, supply-chain security, access control, and vulnerability management. IEC 62443 provides the globally used framework for industrial automation and control system security. ISO 27001 addresses information-security management. The EU Cyber Resilience Act (CRA) adds cybersecurity obligations for products with digital elements.

**North America** — NIST CSF 2.0 provides a widely applicable cybersecurity risk framework, complemented by CISA's Cybersecurity Performance Goals for critical infrastructure. NERC CIP establishes mandatory cybersecurity requirements in the bulk electric system. FDA 21 CFR Part 11 governs electronic records and signatures in regulated environments.

**Asia-Pacific** — Australia's SOCI Act requires applicable critical-infrastructure organizations to manage risks, report cyber incidents, and maintain evidence, with enhanced requirements introduced in 2026. Singapore's Cybersecurity Act establishes obligations around Critical Information Infrastructure. Japan's METI publishes dedicated cyber/physical and factory-security guidance for manufacturing.

Also supported: GMP and GxP documented change control for every production step, and EU Annex 11 for computerised systems in regulated environments.

What auditors actually ask — and where the answer comes from: an inventory of assets and their configurations (Octovision asset intelligence); evidence that changes are controlled and authorized (Octoplant change management and approval workflows); proof that vulnerabilities are identified and prioritized (Octovision CVE matching); demonstrable recoverability (Octoplant backup and version history); and a traceable record of who did what, when (audit trails generated as a by-product of operations).

- [OT Compliance & Regulatory Readiness](https://amdt.com/solutions/ot-compliance-and-regulatory-readiness/)
- [Trust Center](https://amdt.com/trust-center/)

---

## Data Foundation for Industrial AI

AI doesn't start with the model. It starts with the data. Industrial AI needs more than historian data, sensor readings, and enterprise context. To understand how production actually works, AI needs access to the machine and plant level: configurations, software and firmware, versions, changes, asset relationships, vulnerabilities, lifecycle information, and operational history.

Most of what reaches enterprise analytics and AI platforms comes from the top of the production pyramid — ERP, MES, historians, databases, connected sensors. Deeper in the plant sits another layer of context inside PLCs, robots, HMIs, SCADA systems, DCS, drives, CNCs, and engineering projects. That data has historically been fragmented across vendors, proprietary formats, decades of device generations, inconsistent structures, and sensitive production IP.

**An asset list is not an AI data foundation:**

| Basic OT data | AI-ready operational context |
|---|---|
| Asset exists | Asset identity, vendor, and device type |
| IP address | Engineering and production context |
| Current firmware | Software and firmware version history |
| Current state | Historical configuration states |
| Configuration file | Structured and versioned configuration history |
| Device detected | Components and asset information |
| Change detected | What changed, when, by whom, and how |
| CVE identified | Vulnerability matched to the actual asset |
| Asset age | Lifecycle and support information |
| Backup exists | Backup status and historical recovery points |

The difference isn't more data. It's more context — and history, not just a snapshot.

- [Data Foundation for Industrial AI](https://amdt.com/solutions/data-foundation-for-industrial-ai/)
- [Innovation](https://amdt.com/innovation/): AMDT's approach to AI as a controlled, reusable foundation rather than scattered features — AI is optional, control is not.

---

## Industries

- [Automotive](https://amdt.com/industries/automotive/) — Where a stopped line is measured in millions. New vehicle platforms, electrification, model variants, and software-defined production mean continuous change on the plant floor; connected factories, remote services, and IT/OT integration mean a larger attack surface. Tightly synchronized lines, just-in-time logistics, and takt times measured in seconds leave little tolerance for disruption. In automotive, configuration control is production control.
- [Manufacturing](https://amdt.com/industries/manufacturing/) — Whatever you make, it runs on devices you can't lose. Modern production combines PLCs, robots, HMIs, SCADA, DCS, CNCs, drives, engineering systems, and industrial PCs from different vendors and generations. The challenge isn't standardizing every machine — it's establishing one standard for control across all of them. One plant is an engineering problem; fifty plants are an enterprise problem.
- [Pharma](https://amdt.com/industries/pharma/) — Validated, versioned, audit-ready. A validated production system isn't simply a collection of devices; its configurations, programs, parameters, and software form part of the operational state used to run a controlled process. When that state changes, teams need to know what changed, what existed before, and which state can be trusted. Data integrity has to reach the plant floor.
- [Food & Beverage](https://amdt.com/industries/food-beverage/) — Traceable to the last parameter. Recipes aren't the only thing defining the finished product: PLC logic, process parameters, machine settings, filling systems, and packaging configurations all contribute to repeatable production. Operational traceability — which configuration was running, which version was approved, who changed it — extends traceability beyond the batch. And downtime has a shelf life: a stopped food line can mean spoiled ingredients, discarded work in progress, and interrupted cold chains.
- [Energy & Utilities](https://amdt.com/industries/energy-utilities/) — Recovery time is a public matter. Utilities operate some of industry's longest-lived automation environments; controllers, RTUs, HMIs, SCADA systems, and engineering infrastructure can remain operational for decades alongside newer connected technology. Replacing everything isn't realistic, so visibility, control, and recovery readiness across generations of OT become essential. Water infrastructure in particular has become a cyber frontline.
- [Machine & Plant Engineering (OEM)](https://amdt.com/industries/machine-plant-engineering-oem/) — Build machines your customers can trust for decades. Machine builders rarely deliver identical automation twice; version control turns customization into something manageable. When the machine stops, the OEM's phone rings — trusted versions, backups, and change histories give support teams context before they start diagnosing, reducing escalation and unnecessary on-site work, and turning service knowledge into a service business.

## Use Cases

- [Automotive OEM](https://amdt.com/use-cases/automotive-oem-use-case/) — The model-year changeover that has to be reversible; the battery plant where a bad parameter hides for three weeks; one group-level risk number without touching a single device.
- [Automotive Supplier](https://amdt.com/use-cases/automotive-supplier/) — Tier 1 and Tier 2 plants carrying OEM-grade obligations on supplier-grade margins: the customer assessment that now asks about availability and recovery, the undocumented parameter change that becomes a quality event, and the incident that stops the customer's line.
- [Pharma](https://amdt.com/use-cases/pharma-use-case/) — The change-control burden behind every qualified system, the obsolete controller you are not ready to replace, and enterprise visibility without another tool touching qualified equipment.
- [Food & Beverage](https://amdt.com/use-cases/food-beverage-use-case/) — The recall question answered from records instead of recollection; the fifteen-year-old filler PLC nobody wants to touch; the systems around production whose failure stops production.
- [Consumer Goods](https://amdt.com/use-cases/consumer-goods/) — High speed, thin margins, constant format change: the changeover that reveals what nobody wrote down, the recovery tail nobody budgets for, and machine software entering the compliance conversation.
- [Wastewater & Utilities](https://amdt.com/use-cases/wastewater-utilities/) — Essential infrastructure with aging technology and limited resources; PLC manipulation where the version number may not tell the truth; the utility where one engineer knows almost everything.
- [Transport & Logistics](https://amdt.com/use-cases/transport-logistics/) — Sorters, terminals, and baggage systems where the recovery tail is often longer than the outage, shared platforms many operations wait on, and peak seasons that leave no room to rediscover the recovery plan.

---

## Competitive Positioning

AMDT competes in four different conversations, because the alternative to an OT Asset Intelligence Platform depends entirely on who is asking. Engineering teams compare it to version-control tools. Rockwell-standardised plants compare it to their vendor's own utility. Security teams compare it to network monitoring. And more often than any of these, the real alternative is a manual process nobody has ever tested under pressure.

The honest summary: AMDT is device-centric, vendor-agnostic, and recovery-first. Its history is a restoration path, not an archive. Its intelligence layer is built from configuration data rather than network traffic. Where a competitor is genuinely better suited to a narrower problem, that is stated below.

### 1. vs. Git-based industrial DevOps platforms

**Copia Automation, Software Defined Automation (SDA), and GitHub / GitLab-based workflows.**

This category applies software-engineering discipline to PLC code: repositories, branches, pull requests, diffs, and CI-style review. For teams writing structured text in modern IDEs, it is a genuine improvement over emailing project files.

The structural difference is what gets versioned. **Git-based tools version code. AMDT versions the device.** A Git repository holds whatever an engineer remembered to export and commit. It does not connect to the controller, does not know whether the repository still matches the equipment running production, and cannot tell you that someone changed a setpoint at 2 a.m. without committing anything. Octoplant connects to the device on a schedule, captures its actual configuration, and compares the running state against the last approved version — so drift is detected whether or not anyone documented it.

Scope is the second difference. Git handles text well and binary or proprietary formats poorly, which describes most of the shop floor: robots, CNCs, HMIs, drives, DCS, and generations of vendor-specific project formats that produce no meaningful diff. Octoplant's device-specific integrations understand how each system stores and retrieves its configuration, and Smart Compare surfaces differences in programs, parameters, and device data that a line-based diff cannot represent.

Third, recovery. A commit history tells you what the code looked like. Restoring production means rebuilding the exact program, parameters, configuration, and machine-specific data a device requires — which is why Octoplant stores recovery points rather than snapshots of source.

Vendor notes within the category: **Copia Automation** is the most established, centred on Git-native version control and review workflow for mainstream PLC ecosystems, with backup capability alongside it. **Software Defined Automation (SDA)** is a newer, venture-backed, cloud-first entrant pursuing Industrial DevOps together with a longer-term virtual-PLC and Industrial-Control-as-a-Service vision — an architecturally ambitious bet that assumes a degree of cloud connectivity and modernisation many brownfield plants are not ready to make. **Generic GitHub or GitLab workflows** cost nothing extra and are entirely manual: no device connectivity, no drift detection, no audit trail tied to the equipment, and no answer for the legacy estate.

Who should choose what: teams whose automation is predominantly modern, text-based, and written by software-fluent engineers may prefer a Git-native review experience. Enterprises that must protect and recover a heterogeneous estate — including equipment installed decades ago — need device-level backup, comparison, and recovery, and increasingly the vulnerability and lifecycle intelligence layered on top of it.

### 2. vs. single-vendor and point-solution backup and version tools

**Rockwell FactoryTalk AssetCentre, FTVersionTrak, Plus4Data, Asset Guardian Solutions.**

Every product here is credible inside its own boundary. The boundary is the point.

**Rockwell FactoryTalk AssetCentre** provides asset management, backup, and change detection and is strongest inside a Rockwell / Allen-Bradley ecosystem, where its integration with the vendor's own tooling is an advantage. That advantage inverts the moment a plant also runs Siemens, Schneider, ABB, Beckhoff, robots, CNCs, or drives — which nearly all plants do. Running one backup tool per ecosystem fragments exactly what an enterprise is trying to standardise: change history, recovery procedure, and audit trail. Plants standardised entirely on Rockwell hardware may reasonably choose AssetCentre; mixed-vendor operations and enterprises seeking hardware-independent OT governance choose AMDT.

**FTVersionTrak** (FasTrak SoftWorks) delivers version control and backup for a focused set of PLC platforms. It solves versioning for the devices it covers, but does not extend into enterprise asset intelligence, CVE matching, lifecycle and obsolescence management, or cross-site risk reporting.

**Plus4Data** (eguide4DATA) is a German specialist in OT backup and data security with strong regional presence. Its centre of gravity is backup and data protection rather than the full change-management, approval, enterprise-visibility, and vulnerability-intelligence scope AMDT covers.

**Asset Guardian Solutions (AGS)** offers OT software version control, asset management, compliance, and integrity capability, with notable traction in oil, gas, and process industries. It is a real competitor in that space; the differences buyers weigh are breadth of native device coverage across discrete manufacturing, depth of legacy support, and whether the enterprise intelligence layer is built from configuration data already collected.

What AMDT brings across the whole category: 180+ industrial device types natively supported with the flexibility to support any vendor and device; strong coverage of equipment installed over decades; and Octovision as an intelligence layer above the operational data — CVE matching against real assets, lifecycle and obsolescence insight, backup and recovery readiness, and cross-site comparison. The pattern buyers describe is consolidation: replacing three or four partial tools with one operational standard across plants and regions.

### 3. vs. OT network monitoring and scanning platforms

**Nozomi Networks, Claroty, Dragos, and similar OT/ICS network security platforms.**

This is the comparison most often framed as competition when it is usually complementary, and being straight about that is more useful than pretending otherwise.

Network-centric platforms discover assets by passively observing traffic and, in some configurations, actively querying devices. They are good at what AMDT does not do: network anomaly detection, threat hunting, traffic baselining, segmentation insight, and spotting a device communicating in a way it should not. Organisations with a mature OT security programme frequently need that capability.

What they cannot see is configuration. A network sensor observes packets. It can infer that a PLC exists at an address, often its vendor and sometimes its firmware. It cannot tell you what logic is running inside it, what changed in that logic last Tuesday, who changed it, whether a current backup exists, or whether you could restore the device this afternoon if you had to.

| | Octovision approach | Network-centric discovery |
|---|---|---|
| Data source | Project and configuration data already collected through Octoplant | Active queries or passive observation of network traffic |
| Interaction with devices | No additional interrogation of live devices | Active probing or traffic monitoring on production networks |
| Depth of context | Configuration content, versions, change history, components, firmware, backup status, lifecycle | Primarily network-observable attributes |
| Risk to production | No additional traffic to the shop floor | Active scanning can disrupt sensitive legacy devices |
| Covers offline assets | Yes — unnetworked and partially networked equipment is still backed up and versioned | No — a device that does not talk on the network is invisible |
| Answers "can we recover?" | Yes — backup status and restorable versions per asset | No |

Two further points matter operationally. First, **deployment risk**: active interrogation of sensitive legacy controllers is a real concern in OT, and Octovision adds no traffic to the shop floor because it reuses data Octoplant already holds. Second, **offline assets**: a meaningful share of industrial equipment is unnetworked or intermittently connected, and is therefore invisible to a network sensor while remaining fully managed by Octoplant.

The practical enterprise pattern is both layers: network monitoring for traffic anomalies and threat detection, AMDT for configuration truth, change accountability, and recoverability. Where they overlap is asset inventory and vulnerability management — and there, the differentiator is context. Knowing a PLC exists at an IP address is inventory. Knowing what it is, how it is configured, what changed, what components it contains, whether it is backed up, and how that state evolved is intelligence.

### 4. vs. manual backups, network shares, and tribal knowledge

**The status quo — and the most common alternative AMDT actually displaces.**

The most frequent competitor is not a vendor. It is a process: project files on engineering laptops, a folder on a network share, a USB drive in a drawer, a spreadsheet tracking which version is current, and one engineer who knows how the line was really configured.

This works until it doesn't. Engineers get busy. Maintenance windows get shorter. Contractors leave and take context with them. Projects stay on laptops. A backup taken six months ago may exist, but nobody knows whether it still matches the device running production today — and the moment you find out is the moment you can least afford to.

The specific failure modes:

- **The backup that was never taken.** Manual routines depend on someone remembering during a shift where something more urgent always exists.
- **The backup that is stale.** It exists, it restores cleanly, and it puts the device back into a state three changes out of date.
- **The undocumented change.** Nothing failed and nothing was recorded, so the deviation only surfaces as a quality problem weeks later.
- **The person who left.** Recovery capability that lives in one engineer's memory is a single point of failure with a notice period.
- **The recovery nobody rehearsed.** The first real test of a manual backup process is usually a live outage.
- **The audit.** Reconstructing who changed what, when, and why from file timestamps and recollection is a reporting project, not evidence.

Octoplant replaces the process rather than the intent: scheduled, unattended, verified backup jobs; central storage with version history; automatic comparison against the running device; alerts when a backup fails or a device becomes unreachable; and audit trails generated as a by-product of normal operations. The question changes from *do we have a backup* to *which version do we want*.

The economics are straightforward. Recovery time starts long before the incident — it depends on whether the right backup exists, whether it is current, whether you know what changed, and whether your team knows exactly what to restore. Every minute spent finding the right project, determining what changed, or waiting for specialist support extends the loss.

---

## Customers and Proof

More than 3,200 industrial organizations worldwide rely on AMDT, Octoplant, and Octovision. From CERN's Large Hadron Collider to global automotive and pharmaceutical production plants, enterprises use AMDT to protect their crown jewels: the equipment that keeps them running.

Reference customers and published stories include:

- **thyssenkrupp Presta AG** — "In case of an emergency, we can restore entire production lines within minutes and maintain the supply chain." (Benjamin Kleine)
- **Bosch** — backup for manufacturing delivered as a service across all global Bosch locations.
- **CERN** — version control for the systems behind Large Hadron Collider research.
- **Volkswagen Anhui** — managing automation data across a new-generation plant.
- **Siemens Energy** — centralizing automation data for global service teams.
- **STIHL** — a professional tool for managing production automation data.
- **MANN+HUMMEL** — ending the search for the right software version.
- **KNAPP** — from beta tester to satisfied user in intralogistics automation.
- **EGGER** — automated backups for faster production recovery.
- **Humanwell** — strengthening pharmaceutical production with reliable OT data.
- **Aluar (Argentina)** — aluminium production automation data management.
- **Emschergenossenschaft / Lippeverband (EGLV)** — IT security for critical water infrastructure.
- **ELWEMA** — structure and traceability for system project data.
- **Braas** — clay, loam, and automation.

- [Case Studies](https://amdt.com/resources/category/case-studies/)

---

## Getting Started, Support, and Partners

- [Try Octoplant](https://amdt.com/try-octoplant/) — Two routes: an **Executive Briefing**, a focused conversation about your OT environment, business priorities, recovery readiness, enterprise visibility, compliance, and OTSSM (best for executives, CISOs, OT leaders, operations leadership, and enterprise stakeholders); or a **Live Demo** of Octoplant and Octovision against real industrial devices, data, and use cases.
- [Service and Support](https://amdt.com/service-and-support/) — Professional services for architecture, installation, configuration, commissioning, and rollout; instructor-led training, eAcademy courses, technical documentation, and Knowledge Base; expert support cases submitted and tracked through the myAMDT customer portal.
- [Partner Network](https://amdt.com/partner-network/) — 100+ global channel partners: system integrators, automation specialists, resellers, and distributors, with structured partnership levels, certification, technical enablement, joint marketing, and sales resources. Resellers can be found via [octoplant.com](https://octoplant.com/).
- [Contact](https://amdt.com/contact/) — Routes for sales and demos, partners, press and analysts, and existing-customer support. Teams in Europe, the Americas, and Asia-Pacific, with partner presence in more than 50 countries.

## Resources

- [Resources Hub](https://amdt.com/resources/) — Research, customer stories, insights, events, and guides across OT security, compliance, backup, recovery, change management, and enterprise visibility.
- [White Papers](https://amdt.com/resources/category/white-papers/) — including "7 Myths About OT Backup and Versioning" and "Why OT Security Needs Vulnerability Management".
- [OT Security Reports](https://amdt.com/resources/category/ot-reports/) — including "Industrial OT Security is Shifting Fast".
- [News & Press](https://amdt.com/resources/category/news-press/) — leadership announcements, the OpenSG strategic partnership connecting engineering design with factory operations, Octoplant Partner Network Awards, and OT market commentary including ransomware in manufacturing, NIS2, and autonomous AI attacks reaching the industrial OT layer.
- [Events](https://amdt.com/resources/category/events/) — SPS Nuremberg, IMTS Chicago, it-sa Nuremberg, ManuSec, Smart Manufacturing for Automotive (Detroit), Smart Manufacturing Food & Beverage (London), and Manufacturing IT/OT Summit Europe (Munich).

Resource topics include: [OT Security](https://amdt.com/resources/topic/ot-security/), [Vulnerability Management](https://amdt.com/resources/topic/vulnerability-management/), [OT Backup & Recovery](https://amdt.com/resources/topic/ot-backup-recovery/), [OT Visibility](https://amdt.com/resources/topic/ot-visibility/), [Production Resilience](https://amdt.com/resources/topic/production-resilience/), [Compliance](https://amdt.com/resources/topic/compliance/), [NIS2](https://amdt.com/resources/topic/nis2/), [AI](https://amdt.com/resources/topic/ai/), [Octoplant](https://amdt.com/resources/topic/octoplant/), [Octovision](https://amdt.com/resources/topic/octovision/), and [Partners](https://amdt.com/resources/topic/partners/).

## Company

- [About AMDT](https://amdt.com/about-amdt/) — Nearly four decades focused on one challenge: keeping automated production controlled, recoverable, and resilient. Today AMDT is building the foundation for OT Service and Security Management, connecting asset knowledge, change control, backup, recovery, vulnerability context, and enterprise visibility across devices, lines, plants, and regions.
- [Innovation](https://amdt.com/innovation/) — In OT, "move fast and break things" isn't a philosophy, it's an outage. New concepts are developed in controlled environments, tested with users, measured against clear value and security criteria, and scaled only when ready. Some become products, like Octovision; some become reusable technology foundations; and some deliberately go no further.
- [Trust Center](https://amdt.com/trust-center/) — ISO/IEC 27001:2022 (covering software development, testing, distribution, system integration, support, consulting, and training in automated production environments), TISAX® (reflecting automotive-industry information-security requirements based on the VDA catalogue), and ISO 9001:2015, plus vulnerability reporting.
- [Careers](https://amdt.com/careers/) — Engineers, product thinkers, salespeople, marketers, and customer experts across three continents, guided by P.L.A.N.T. values.
- [AMDT on LinkedIn](https://www.linkedin.com/company/amdt-auvesy/)

## Legal and Language

- [Privacy Policy](https://amdt.com/privacy-policy/)
- [General Terms & Conditions](https://amdt.com/general-terms-conditions/)
- [Declaration of Consent](https://amdt.com/declaration-of-consent/)
- [Legal Notice (AUVESY GmbH)](https://amdt.com/legal-notice-of-auvesy-gmbh/)
- Site language versions: English (default), [Deutsch](https://amdt.com/de/), [日本語](https://amdt.com/ja/)