Configuration protection / part of Surya Fabric
Octoplant
Backup, version history and change detection for supported PLC, HMI and industrial configurations within the agreed Octoplant license and deployment. Device families, software versions, access and any disconnected operation are qualified before deployment.
Know what changed. Keep recovery ready.
- Supported configuration backup
- Version history and change detection
- A documented recovery procedure
Defined scope
A fixed-scope starter deployment: one agreed plant scope, a qualified device and version list, access prerequisites, backup jobs, version history, change detection and a documented handover. Acceptance criteria are written into the proposal. Commercial terms are quoted after qualification.
Support is limited to the qualified licensed configuration, not every module, device family or integration. Surya reviews backup results and recorded versions and flags failed jobs or differences to the named owner. Retrieving a backup is not independently restoring a PLC, validating machinery or returning a plant to production. Recovery steps must be expressly assigned and authorized.
Delivered as part of Surya Fabric
Every operational configuration we cover, backed up and versioned. You see what changed and when. You see every device on the operational network.
Octoplant is one component Surya can use inside Surya Fabric. Surya configures and operates only the supported components and licensed capabilities agreed for each platform. Modules, device families, integrations and disconnected features are qualified, not automatically included.
Explore Surya FabricWorking alongside IT
Who owns what.
Surya
The replacements and the supply chain behind them. The configuration backups. The OT inventory. The operating PCs.
Your IT team or MSP
Email, identity, business applications, employee laptops, and the network. Not our business, and we will not quote it.
Plant engineering, clinical engineering and your OEMs
The process, the logic, the calibration, and the call on return to service. Always.
How an asset comes into scope
An asset comes into scope when it supports the site's production or care delivery and matches a supported Surya configuration. Changes to running equipment follow the designated owner's approvals and the agreed maintenance and change process. Network ownership is named at qualification; platform visibility does not transfer network enforcement or operation to Surya.
Your next step
We do not take every site.
Tell us what yours runs on. If we can stand behind it, you get a scope and a clear line on who owns what. If we cannot, we will say so.