SD-WAN Deployment, Site by Site, Across the 48 contiguous states, Alaska, and Hawaii.
Your platform owner supplies the approved design and configuration. SRS scopes readiness, staging, CPE mounting, equipment-side power, cabling, port records and physical checks, with named carrier and platform contacts for the authorized change window.
SRS coordinates the assigned field work and kit handoff across the program. The customer network team owns overlay configuration, security policy, traffic changes and service acceptance; installation records preserve the checks performed and open exceptions.
SD-WAN deployment is the field execution half of an SD-WAN program: site surveys, edge appliance staging and customer configuration handoff, shipping and install sequencing, assigned carrier coordination, approved work windows, physical checks and customer-owned acceptance records, with any legacy removal released separately. The design and the platform decision sit upstream of it. The field work follows the released site plan; technical change decisions and service release stay with the named specialists. Record schedule dependencies and unaccepted items.
SRS Networks is a nationwide network deployment contractor headquartered in South San Francisco, California, executing multi-site SD-WAN rollouts for retail chains, healthcare systems, restaurant groups, and distributed enterprises across the 48 contiguous states, Alaska, and Hawaii since 1996. Our companywide enterprise infrastructure delivery includes 900+ programs across 10,000+ deployed sites from six offices with in-house W-2 field leads, West and East Coast staging facilities, and every site tracked live in our Project Command Center. If you are still choosing an architecture rather than installing one, start with our SD-WAN and multi-site networking overview and come back here when the estate is ready to roll.
SD-WAN Rollouts Fail in the Field, Not in the Design
Architecture, carrier readiness, logistics and access decisions have separate owners. Keep the approved field package, open dependencies and release authority visible before scheduling a site.
300 Appliances Drop-Shipped to 300 Addresses
Confirm a receiving contact, address, storage and kit identifiers before shipment. Our published historical benchmark observed roughly one-in-six first-attempt failures across several hundred direct-to-site shipments over twelve months; it is not a prediction for a new program.
Carrier Ready Dates That Move
A circuit readiness change can block a planned visit. Name the carrier/order contact, record the actual handoff evidence and agree whether to resequence or remobilize before releasing field work.
Cutover Windows Across Four Time Zones
Each location needs an authorized window based on its operating requirements and technical-owner availability. Confirm the permitted interruption and site prerequisites before assigning a crew.
No Rollback When the Tunnel Drops at 3am
The customer platform owner must decide whether a fallback is feasible and what equipment, remote support or return visit it needs. Record that procedure and authority before the change; retained equipment alone does not guarantee reversal without an outage.
A Repeatable Per-Site Deployment Runbook.
Use a repeatable approved process while recording each site's kit, access, circuit and acceptance differences. The program plan identifies which tasks can proceed and which need a new decision. It runs alongside our multi-site network deployment and internet provider coordination work when the circuits are changing too.
Six Phases, Repeated at Every Location
Agree the site sequence, prerequisites and approval checkpoints before release. Record the evidence and exceptions for each task; a missing technical approval is not implied by a completed physical checklist.
Survey Every Site
We document the demarc type and location, the existing router or firewall make and model, the RU or wall space available, the outlets and UPS capacity, the cable path from demarc to rack, and the LTE or 5G signal at the exact spot the antenna will sit. Sites that need remediation get flagged now, not on install day.
Stage and Kit the Edge
Appliances land at our West or East Coast facility. Each one is serialized to a site ID and port-labeled, then kitted with the approved power supply, mounting hardware, patch cords, optics, antenna and site-specific install sheet. Your platform owner completes licensing, controller enrollment, firmware, configuration and SIM readiness before the installation handoff.
Coordinate the Circuits
When carrier coordination is assigned, track the order owner, ticket access, handoff and readiness evidence. The provider and customer platform owner authorize activation and technical changes. Record the approved physical checks and any included backup-device or signal observations.
Ship and Sequence
Agree the delivery date, receiving contact, storage and confirmed kit receipt before releasing the installation window. Sequence sites against actual readiness, access and available field resources; a delay can require another visit or revised wave dates.
Cut Over and Turn Up
Inside the approved work window, SRS executes the physical patching and customer-directed installation checklist. Your platform owner controls traffic migration, tunnel and routing checks, QoS, DHCP, DNS, VLANs and application acceptance. Disruptive failover requires their approved test plan and rollback authority; results and exceptions are recorded for signoff.
Document, Soak, Decommission
Reconcile equipment and connection identifiers, approved installation photos and the checks actually performed. Customer specialists supply and accept platform/service records and decide any observation or fallback plan. Release legacy removal and reverse logistics separately; retained hardware does not guarantee reversal without interruption or another dispatch.
Scope of an SD-WAN Deployment Engagement
Assign readiness, staging, physical installation and closeout separately, with legacy removal released only where included and authorized.
Site Survey & Readiness
Agree which sites require a survey or current readiness record. Record the demarc, existing edge, rack or wall position, available connections and any backup-device checks required by the approved plan.
Staging, Kitting & Configuration Handoff
Where staging is assigned, receive and serialize equipment to the site kit and approved installation sheet. The customer platform provider owns licensing, enrollment, firmware, SIM activation and configuration readiness.
Install, Cutover & Turn-Up
SRS mounts, connects and labels the approved edge equipment during the released window. The customer platform owner controls transport activation, traffic migration, policy, failover and operational acceptance.
Validation, Docs & Decommission
Agree the physical inventory, photos and checks to be recorded. The platform owner supplies its configuration and service results and approves exceptions. Any observation period, fallback assistance, legacy removal or return shipment needs an assigned scope.
You Picked the Vendor. We Install It.
We are the hands, not the resale channel. Whatever platform your team standardized on, we install to your approved design and record the acceptance steps directed by your platform owner.
VMware VeloCloud
Your platform provider activates the edges and assigns the Orchestrator profile. SRS handles approved mounting, power and patching, then records the provider-witnessed installation handoff.
Cisco Meraki MX
Your platform provider owns dashboard enrollment, templates and AutoVPN policy. The field crew installs the approved appliance and assists their authorized acceptance checklist.
Fortinet Secure SD-WAN
Your platform provider owns FortiManager or FortiCloud registration, firmware, SD-WAN rules and SLA probes. SRS installs the approved hardware and documents customer-directed acceptance tasks.
Cato, Prisma, EdgeConnect
For these platforms, the customer provider owns tenant enrollment, configuration and its acceptance procedure. SRS stages and installs the approved physical kit and records the field tasks and witnessed results assigned to the project.
Rollouts Break on Logistics. That's What We Own.
Anyone can bolt an appliance to a wall. Doing it at 300 addresses on a schedule, with carriers slipping and every site keeping different hours, is a logistics discipline. We built the staging facilities and the PM structure around that problem.
What a 300-site SD-WAN rollout actually looks like.
Illustrative planning scenario: a 300-store program has an approved platform and target dates. Confirm the demarc, rack or wall position, equipment-side power and cable path for each released location, plus any specified backup-device signal checks. Record electrical or mounting blockers with the responsible parties; a target date does not establish site readiness.
Where staging is included, receive equipment at the West or East Coast facility and serialize the approved kit to the site. The customer platform owner retains licensing, firmware, enrollment, SIM activation and configuration release. Confirm the specified supply, mounts, cords, optics and antenna against the installation sheet. Our published historical shipment benchmark is a rounded operating observation; it does not predict receipt or prevent every crew delay.
If carrier coordination is assigned, identify the order owner, ticket access and readiness evidence before the field window. The provider and customer platform team authorize activation or technical changes. Confirm delivery, storage and the named recipient before crew release. A blocked circuit or missing kit can change a visit or wave date; record the approved resequencing and any remobilization scope.
Cutover runs on the site's clock, not ours — pre-open for retail, after last patient for clinics, third-shift changeover for distribution. Your platform owner controls traffic migration, tunnels, routing, security policy and application acceptance. SRS executes the physical patching and their approved field checklist. Disruptive failover requires that owner's test plan, work window and rollback authority; installation records preserve the results and open exceptions.
Agree the physical inventory, cable and port identifiers, approved photos and performed checks before dispatch. Platform specialists provide their service results and accept any open exceptions. The customer decides feasible fallback steps, observation periods and any return visit; retained equipment does not guarantee reversal without interruption. Release old-equipment removal separately to your authorized reverse-logistics provider or our network decommissioning process. Throughout, you watch site status roll up live in the Project Command Center instead of asking for a spreadsheet on Fridays. One PM, one standard, one PO across the 48 contiguous states, Alaska, and Hawaii.
Explore More from SRS Networks
SD-WAN Deployment FAQs
The questions IT directors and network managers ask us before handing over a multi-site SD-WAN rollout.
Send Us the Site List. We'll Send Back a Schedule.
Send the locations, approved physical scope, platform-owner contacts and proposed dates. SRS can identify field readiness and coordination needs across the 48 contiguous states, Alaska, and Hawaii. Agree surveys, staging, carrier tasks, work windows and receiving records before releasing the program.
