Dedicated operational endpoints

Surya Endpoint

The Windows PCs that run a line or a clinic day are not office laptops, and we do not treat them like office laptops. We inventory them, check them against the configuration you approved, and patch them in your maintenance window. If something unexpected turns up, we stop and call the owner.

Your operating PCs. Your approved changes.

Capabilities

  • Check supported Windows inventory
  • Check approved configurations and record differences
  • Deploy approved packages and patches in maintenance windows
  • Record deployment results and operational status
  • Local execution within a qualified air-gapped profile

Where it applies

Production continuity

Manufacturing

Supported Windows operator stations and industrial PCs on the line or in inspection, inventoried and checked against their approved configuration.

Manufacturing continuity

Care-delivery continuity

Healthcare

Qualified dedicated care-delivery workstations, inventoried and checked against their approved configuration.

Healthcare continuity

Qualification

What it takes to work with us.

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.

  • Qualification defines the supported profiles
  • Any customer identity or application dependencies are named at qualification
  • A named site owner for change approval

Delivery

How it is delivered

Field engineers set up the PCs on site, and remote engineers work only through connections you have approved. Changes go in on your approval and in your window, and your owner approves return to service.

Where one platform's capabilities are included in another platform's scope, they are not sold or charged a second time.

Scope boundaries
  • Endpoint does not guarantee device security or availability.
  • Endpoint is not general employee computing or a joiner and leaver service; those stay with your IT team or MSP.
  • Surya does not own your enterprise tenant, clinical applications, medical device function or machine process.
  • Not every device at a site is OT; only supported dedicated Windows endpoints are in scope.

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.

Working 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.

How it works

From site scope to supported operation.

  1. 01

    Define the site scope

    Choose Standby, Endpoint or Fabric around the equipment that supports production or care delivery.

  2. 02

    Confirm the boundary

    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.

  3. 03

    Prepare and configure

    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.

  4. 04

    Operate and recover

    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

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.

Keep my site running