/ Surya Standby

The person or the site resumes operation.

When a supported device fails at a site, work stops until someone has a working machine again. Surya Standby is the layer that prepares for that in advance, and it can be bought on its own without moving anything else to Surya.

A badge-access smart locker at the site, stocked with replacement devices built to your standard, with authorized issuance, returns, readiness checks and replenishment from the Surya RTP distribution center, so a working replacement is ready before it is needed.

Check Fit →See the product

/ What the element covers

  • Prepared inventory built to the customer's own standard, built by Surya where Surya Endpoint is also in scope
  • Authorized issuance recorded against the serial number
  • Returns, repair routing, certified erasure to NIST 800-88 and retirement
  • Readiness checks and replenishment from the RTP hub
  • A swap runbook the person at the site follows

The first layer, bought on its own.

Standby covers the physical side of recovery: prepared inventory configured to the standard, authorized issuance recorded against the serial number, returns and repair routing, certified erasure to NIST 800-88, readiness checks and replenishment from the Surya distribution center.

Bought on its own, it requires no access to your Microsoft tenant. Endpoint configuration, identity and protected-data recovery belong to Surya Endpoint, the next layer up.

Who owns what.

You purchase and own the devices, including the prepared replacements, and you name the owners who authorize issuance. Surya provides, installs, owns and operates the smart locker it uses at the site, and operates the inventory to the released standard.

/ Adoption

Your first deployment.

Adoption starts on one layer with a defined scope, usually a single site or a single group of devices, rather than the whole estate.

  1. / 01

    Choose one product and a defined scope

    One product, one site or one device group. The scope is written down before anything is installed.

  2. / 02

    Compatibility review

    Your environment is checked against the released profile for the product you selected, including identity and platform dependencies where they apply.

  3. / 03

    Written prerequisites

    Anything that must change first is stated in writing, together with the approvals your organization needs to give.

  4. / 04

    Installation

    Surya installs and configures the supported scope to the released standard.

  5. / 05

    Acceptance tests

    The product is accepted against its own tests, so the result is inspectable rather than asserted.

  6. / 06

    Ongoing operation

    Surya operates the accepted scope, and faults inside it are Surya's to resolve.

What changes in your environment

  • Equipment that already meets the standard can usually remain in place; equipment that does not is named during the review.
  • Configurations inside the purchased scope are brought to the released profile, which can change how some settings are managed today.
  • Approvals from an accountable owner are required for consequential changes.
  • Providers responsible for adjacent systems, applications or machinery remain responsible for them.

An illustrative first scope: one site, a declared group of supported devices, the prepared replacement positions for that group, the named owners who authorize issuance, and the acceptance test for a recorded swap. Quantities, timing and commercial terms come from the proposal for your environment.

Each product has its own prerequisites. Buying Fabric does not automatically require Endpoint. Any dependencies that extend beyond the selected site are identified during qualification.

What it depends on

The customer purchases and owns the devices, including the prepared replacements. Surya provides, installs, owns and operates the locker. Installation, field response and replenishment coverage are confirmed for the proposed sites during qualification.

What it excludes

Supported devices and published logistics terms, not unlimited procurement. A prepared replacement covers device failure, not an application outage, an identity outage, a power loss or every network fault. Standby on its own does not operate the endpoint, the tenant or the network; those are Surya Endpoint and Surya Fabric.

How it is accepted

A person at the site obtains a working replacement through the runbook and returns to the defined working state, with the swap recorded.