Production continuity
Manufacturing
Supported PLC, HMI and industrial configurations backed up and versioned, changes made visible, and plant OT assets and security alerts monitored within the agreed scope.
Manufacturing continuityConfiguration protection and OT security
Every configuration we cover is backed up on a schedule and kept by version. You see what changed and when. You get an inventory of what is on the operational network, and an engineer who reads the alerts and sends each one to the person who owns it.
Capabilities
Where it applies
Production continuity
Supported PLC, HMI and industrial configurations backed up and versioned, changes made visible, and plant OT assets and security alerts monitored within the agreed scope.
Manufacturing continuityCare-delivery continuity
Supported care-delivery and edge configurations protected and versioned, operational assets visible and platform alerts routed to named owners within the agreed scope.
Healthcare continuityQualification
One site to start. Equipment we support. A named owner who can approve changes. A network owner who has separated the floor from the office. We do not start until all four are in place.
Delivery
Field engineers deploy the tools on site, and remote engineers monitor only through connections you have approved; air-gapped sites are worked locally. Your engineers and OEMs approve return to service.
Where one platform's capabilities are included in another platform's scope, they are not sold or charged a second time.
Start with one site and a defined equipment scope. Before accepting work we confirm supported equipment and software versions, licensed capabilities, dependencies, permitted changes, an approved procedure with verification and a safe stop or rollback where it applies, coverage and escalation, recovery, stock and access arrangements, and responsible owners including the designated network owner. If any of these is missing, the work is not accepted until it is in place. Additional sites are qualified individually. Equipment or tasks outside supported configurations are not part of the offer and stay with your IT team or MSP, your engineering team, the OEM or a specialist you retain.
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.
The OT boundary
This is the condition of entry. Your network owner builds and runs the separation. We work inside it, connected or fully offline.
Minimum standard
Secure IT/OT convergence
Traffic crosses only where your network owner has opened a path. Our remote engineers use those paths and no others.
Where the site requires it
No live path to corporate IT, the internet or the cloud. Work happens on site. Updates arrive by an offline transfer you approve.
Working alongside IT
The replacements and the supply chain behind them. The configuration backups. The OT inventory. The operating PCs.
Email, identity, business applications, employee laptops, and the network. Not our business, and we will not quote it.
The process, the logic, the calibration, and the call on return to service. Always.
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.
How it works
01
Choose Standby, Endpoint or Fabric around the equipment that supports production or care delivery.
02
Confirm supported equipment, licensed capabilities, permitted changes and the connected or air-gapped profile with your network owner. Agree coverage and escalation before work starts.
03
RTP prepares compatible replacements. Field engineers deploy and configure supported tools and endpoints and perform assigned replacement work. Your network owner provides the agreed connectivity and separation.
04
Remote engineers configure and monitor supported tools and endpoints where approved connectivity permits. Standby supports assigned equipment recovery; network, engineering and OEM owners approve return to service within their responsibilities.
Your next step
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.