/ Guide / Multi-site
IT support for multiple locations only works when every location is the same.
Every site that grew up on its own becomes its own IT environment: its own workstations, configurations, security settings, network setup, support procedure and recovery procedure. Multi-location IT support then means learning each site again on every call.
Surya removes the variation first. One released profile per site type, applied at every location, with the same acceptance tests and the same replacement waiting at each site.
/ How it is run
Wes at a plant and Sam at a clinic take the night shift, and one roster covers every site, backed by the supply chain at the Surya RTP Distribution Center and prepared replacements at your sites where in scope. See how the work gets done →
/ The problem
Variation is the cost.
- Workstations
- Peripherals
- Configurations
- Security settings
- Network setups
- Support procedures
- Recovery procedures
- Documentation
- Replacement processes
Each one varies by site, and each variation is paid for as:
- Compliance risk
- Security drift
- Downtime
- Support complexity
- Acquisition complexity
/ How it deploys
Platform first, then one site at a time.
- Qualify: the environment is compared against the released product profiles and every prerequisite is named, with an owner.
- Install: the declared scope is installed to the released standard, with a 30-day installation target once readiness is met.
- Accept: every required element passes its acceptance test, with the evidence recorded.
- Extend: the next site goes on the same standard with the same acceptance tests.
The 30-day installation period is a target. It starts when the readiness prerequisites are met, not at signature, and completes when the acceptance tests pass. Acceptance tests →
Unmet prerequisites move the start, not the finish line. Equipment is staged at the Surya RTP Distribution Center and shipped configured.
/ How support runs across sites
One support path for every location.
The Surya Agent Network takes the first response on every request, at every site. 78% of responses are AI-first, measured across every customer Surya operates over the 90 days to September 2026. Surya engineers work three shifts, 365 days a year. Response commitments for a scope are set in the written proposal.
The person at the site makes the first move. If the device is obviously dead - no power, damaged, will not start - they go straight to the locker and pull the working replacement. If it might come back, they call support and a 30-minute restoration window opens; if it is not working at the end of that window, the replacement comes out of the locker. Either way, the swap is recorded.
Every swap is recorded against the serial number, and each site's locker is replenished from the Surya RTP Distribution Center.
/ Acquisitions and new sites
The next location goes on the same standard.
A new site, an acquired site or a relocated site goes through the same three steps: readiness, installation, acceptance. Nothing about it has to be learned by the support path, because it runs the same released profile as every other site of its type.
/ Recovery at the point of need
Onsite where the site is large enough, from RTP where it is not.
Where your recovery equipment is held
| Site with 15 or more people | Smaller site |
|---|---|
| A prepared locker onsite | Recovery equipment held at the Surya RTP Distribution Center |
| The swap is made by the person you name, from the locker | Shipped under the delivery arrangement in your agreement |
| Surya replenishes the locker | The same package price |
| The 15-minute swap applies here |
The 15-minute swap applies where a prepared replacement is already onsite. Other locations follow the delivery and recovery arrangements in their agreement.
Check fit.
Tell us how many locations you run today, how many are coming, and what stops when one of them loses a device.
Check fit