Keep your people productive with ready devices, secure access and meeting rooms that work, and keep control of company access and data through every hire, role change, and departure.

/ Deployment

Your first deployment.

Deployment starts with a defined scope - one component, one site or one group of equipment - rather than the whole estate. Components such as a conference room or a smart locker are deployed and handed over on their own. Within the full workstation and site-network products, Standby provides the prepared physical recovery layer. Endpoint or Fabric is deployed to the released profile when that deeper scope is purchased, at the outset or later. Where Surya Fabric is purchased, Surya provides the network system itself: the equipment, its standard configuration, installation and testing.

1. / 01

   Choose the scope

   The products, the equipment classes, one site or one device group. The scope is written down before anything is installed.

2. / 02

   Compatibility review

   For Standby, the configurations Surya will capture and reproduce, the physical placement and the approvals the replacement workflow needs. For Endpoint, your environment is checked against the released profile, including identity and platform dependencies. For Fabric, the sites, connectivity, cabling and site readiness the Surya-supplied network system needs are checked.

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 the agreed physical arrangement and the prepared replacements, deploys and tests the Surya-supplied network system where Fabric is purchased, and configures any purchased Endpoint scope to the released standard.

5. / 05

   Acceptance tests

   Each 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

• +Surya Standby reproduces the configurations you already run; it does not require your estate to be rebuilt first, and keeping your existing production setup is not a barrier to it.
• +Standby prepares replacements for your existing supported equipment and configurations. Endpoint can retain devices where its released profile permits. Fabric supplies, installs and tests the network system for the agreed sites.
• +Where Endpoint is purchased, configurations inside that purchased scope are brought to the released profile, which can change how some settings are managed today, and replacement preparation then follows that baseline. Where Fabric is purchased, the supported site network runs on the Surya-supplied system and its standard configuration. Equipment and identity models outside the purchased scope are unaffected.
• +Approvals from an accountable owner are required for consequential changes.
• +Providers responsible for adjacent systems, applications or machinery remain responsible for them, and Standby on its own leaves ongoing tenant, endpoint and network administration where it is today.

An illustrative first scope: one site, the agreed equipment classes, the existing configurations captured per role, the prepared replacement positions for them, and the acceptance tests for that scope. Quantities, timing and commercial terms come from the proposal for your environment.

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