How it works

Prepared equipment. Supported operation. Your authority.

Start with the equipment that supports production or care delivery. Choose the platforms and operating profile the site needs, with clear responsibilities for approved changes and recovery.

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.

Clear steps. Clear responsibility.

We agree the equipment, permitted work, checks and response arrangements before service begins. Engineers and approved automation follow those procedures. If an unexpected condition prevents completion, we pause the action and involve the named owner.

Agreeing these procedures is a condition of accepting service at each site.

The OT boundary

OT separated by default. Air-gapped where required. Connected only through controlled interfaces.

This is the condition of entry. Your network owner builds and runs the separation. We work inside it, connected or fully offline.

Minimum standard

The baseline at every site

  • OT in its own zone, apart from corporate IT
  • No flat network and no shared trust between office and floor
  • Nothing crosses unless it is documented and approved

Secure IT/OT convergence

Segmented and connected

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

Air-gapped

No live path to corporate IT, the internet or the cloud. Work happens on site. Updates arrive by an offline transfer you approve.

Fabric within the agreed OT boundary
What each profile does and does not mean
  • Segmented and connected: Explicitly authorized network traffic and vendor access.
  • Segmented and connected: Remote engineers configure and monitor only through approved access paths within the agreed boundary.
  • Segmented and connected: The designated network owner controls approved interfaces; application integration stays with system owners.
  • Air-gapped: Operation, administration and approved automation run locally.
  • Air-gapped: Information and packages move through customer-approved offline transfers.
  • Air-gapped: Changes and monitoring execute locally, with no live remote connection.
  • Air-gapped: Qualification names a local execution and monitoring owner, who carries out offline transfers, the review schedule and the exception handoff.
  • Blocked internet access alone is not an air gap, and an air-gapped site does not also have live IT/OT connectivity. Remote access paths are not part of the air-gapped profile.
  • Air-gapped equipment has no remote real-time monitoring; local checks are reviewed on the agreed schedule. Working through an internet outage is not the same as an air gap.
  • Disconnected operation is confirmed only after supported components, versions, local administration, application and identity dependencies, and offline transfers are qualified. On-premises deployment alone does not establish air-gap capability.

Research Triangle Park, North Carolina

Software vendors send a login. We send equipment and an engineer.

Most of what fails at a site cannot be fixed over a remote session. So we built a distribution center. Replacements are built and checked there, in Research Triangle Park, North Carolina. Field engineers install on site. Remote engineers watch what you have approved them to watch. The equipment is yours, bought on your paper. We run it.

How the delivery works
Exterior of the Surya Technologies facility at 1 TW Alexander Drive, Research Triangle Park, North Carolina
Surya RTP Distribution Center - actual facility exterior
  1. 01

    Prepare

    Built and checked against your approved configuration.

  2. 02

    Stage

    Held in a locker, a locked cage at your site, or at RTP.

  3. 03

    Deploy

    Field engineers install and configure on site.

  4. 04

    Recover

    The prepared replacement and the saved configuration go in. Your engineers and OEMs make the call on return to service.

  5. 05

    Replenish

    What you use, we restock. Every unit tracked.

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.

Illustrative technician preparing network equipment; not Surya staff or premises
Illustrative equipment preparation

Equipment preparation

Preparation is physical work.

Most of what fails at a site cannot be fixed over a remote session. So we built a distribution center. Replacements are built and checked there, in Research Triangle Park, North Carolina. Field engineers install on site. Remote engineers watch what you have approved them to watch. The equipment is yours, bought on your paper. We run it.

Automation supports. People deliver.

Approved automation supports operation within the agreed scope and follows the same approved procedures as engineers. It does not replace the owner's authority over production or care-delivery equipment.

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