AMDT helps machine and plant builders deliver automation that remains controlled, recoverable, and serviceable throughout its lifecycle. Octoplant protects and versions the PLC, HMI, robot, drive, CNC, and other configurations behind every machine: from engineering and commissioning to customer operation and long-term service.
Ship more than a machine.
Ship the operational foundation to support it for life.
| The stake | The exposure | AMDT's answer | |
|---|---|---|---|
|
Engineering control | Customer-specific machines create multiple projects, variants, software versions, and configuration states. Without disciplined version control, engineering teams can lose certainty about which state belongs to which machine. | Centralized version management, device-aware comparison, and change histories create a trusted operational record from engineering through commissioning. |
|
|
Customer uptime | When a machine fails at the customer's site, troubleshooting time becomes customer downtime, and quickly turns into service escalation, cost, and commercial pressure. | Trusted backups, historical versions, and change context help service teams identify what changed and determine the appropriate recovery state faster. |
|
|
Lifecycle support | The delivered machine continues to change for years through maintenance, upgrades, component replacement, customer modifications, and third-party service. | Maintain configuration and version history throughout the machine lifecycle, preserving knowledge beyond the original project and engineering team. |
|
|
Cybersecurity & compliance | Customers increasingly expect machine suppliers to demonstrate secure development, controlled changes, vulnerability handling, maintainability, and long-term cybersecurity support. | Configuration traceability, controlled versions, asset context, vulnerability intelligence, and recovery information strengthen the operational foundation behind secure lifecycle management. |
| The commercial relationship doesn't end at acceptance: maintaining a trusted record of what was delivered, what changed, and what can be recovered creates value throughout the machine lifecycle. | |||
A machine’s configuration starts changing before it ever reaches the customer. Engineering iterations, software updates, FAT findings, commissioning changes, site adaptations, maintenance, and upgrades all create new operational states.
Octoplant maintains that history instead of allowing knowledge to fragment across engineering laptops, project folders, customer sites, and individual service engineers.
The result is continuity across the entire lifecycle. The machine changes. Its history stays intact.
ENGINEERING
Projects · Versions · Configuration variants
↓↓↓
FACTORY ACCEPTANCE
Validated state · Documentation · Baseline
↓↓↓
COMMISSIONING
Site-specific changes · Final operational state
↓↓↓
CUSTOMER OPERATION
Backups · Changes · Deviations
↓↓↓
SERVICE & MODERNIZATION
Troubleshooting · Recovery · Upgrades · Lifecycle
After-sales service is one of the most valuable relationships a machine builder has with its customers. But efficient service depends on context: what was delivered, what is running now, what changed, and which previous state is available when something goes wrong.
Octoplant gives OEM service organizations that operational history. Instead of beginning every support case by reconstructing the machine’s past, teams can work from controlled versions, configuration comparisons, backups, and documented changes.
That creates the foundation for higher-value lifecycle services — from structured support and recovery readiness to managed backup and configuration services across the installed base.
“At Bosch we think in terms of end-to-end services. This encompasses the whole life cycle and everything connected to the product, and that goes for the B4M service as well. At the heart of the service is Octoplant.”
— Oliver Müller, Senior Manager, Bosch Digital
A customer reports that the machine stopped working correctly. Was there a hardware problem? A parameter change? A PLC modification? Did maintenance alter something? Did an integrator update the program? Is the machine still running the configuration the OEM delivered?
Version history and SmartCompare give service teams a factual starting point. They can compare configuration states, identify differences, and understand how the machine changed before deciding what action is required.
Start troubleshooting with evidence, not assumptions.
Machine configurations represent years of engineering knowledge: PLC logic, motion parameters, recipes, HMI projects, robot programs, drive settings, and customer-specific adaptations.
As machine variants multiply, that intellectual property can become fragmented across project folders, engineering workstations, service laptops, and customer environments.
Centralized version management creates a controlled history of that engineering data — preserving knowledge beyond individual engineers and making the correct machine-specific configuration easier to identify when it is needed.
Customers increasingly expect cybersecurity to be designed into industrial equipment — and regulation is reinforcing that expectation.
In Europe, the Cyber Resilience Act introduces cybersecurity requirements for manufacturers of products with digital elements, including secure development and lifecycle vulnerability handling. NIS2 simultaneously increases supply-chain scrutiny among many operators of critical and important infrastructure.
For machine builders, this reinforces a larger shift: cybersecurity responsibility increasingly extends beyond commissioning into the supported life of the product.
| Machine-builder environment | What matters | How AMDT helps | |
|---|---|---|---|
|
|
Engineering | Keep customer variants, programs, and configurations controlled as the machine evolves. | Centralized version histories and comparison create a trusted engineering record. |
|
|
FAT & delivery | Establish exactly which operational state was tested and delivered. | Preserve validated configurations and create a clear baseline before shipment. |
|
|
Commissioning | Capture changes made when the machine is adapted to the customer's real production environment. | Document new versions and maintain continuity between factory and field. |
|
|
Operation | Protect the configuration as customers, maintenance teams, integrators, and OEM service modify the machine. | Automated backup and change visibility preserve the machine's operational history. |
|
|
Service | Diagnose problems without reconstructing years of undocumented changes. | Historical versions and comparison provide context for faster troubleshooting and recovery. |
|
|
Modernization | Understand the installed technology before upgrades, retrofits, or component replacement. | Asset, component, software, lifecycle, and vulnerability context supports better planning. |
| Machine builders serve different industries and applications, but the lifecycle challenge is remarkably consistent. Every delivered machine needs a trusted operational history that survives engineering changes, commissioning, customer modifications, service, and modernization. | |||