A multi-site satellite project succeeds when people at each location can complete their work and someone can keep the service running. Start with site-level workloads and operating conditions, then design shared capacity and support. Buying a terminal for every building is only one part of the network.
Build a site inventory that exposes differences
For each school or branch, record location, working hours, concurrent users, essential applications, expected downloads and uploads, and local power. Include room layout, existing cabling and Wi-Fi, storage for equipment, site access and the person who can assist remote support.
Group sites by actual needs. A school showing one downloaded lesson to a classroom differs from a room where every student streams independently. A branch sending small transactions differs from one backing up large images. Keep those distinctions in the procurement brief.
Use the satellite connection path to mark the parts owned by the provider and those owned locally. Confirm address-level eligibility and installation conditions for every site, rather than assuming one successful pilot proves every location suitable.
Budget simultaneous traffic in both directions
Estimate the busiest representative period and then measure it in a pilot. For each application, multiply simultaneous sessions by an observed or documented useful rate. Add background traffic and a justified allowance. Calculate upload separately; a class video call can be constrained by either direction.
Ask the supplier how sites share capacity and data allowances, whether simultaneous demand is supported, and what happens when a site or the group exceeds an allowance. Ask for the simultaneous capacity commitment separately from the sum of peak terminal rates.
Design the local network alongside the satellite link
Scroll the table horizontally on small screens. Keyboard users can focus the table region and use the arrow keys.
| Area | Decision | Pilot evidence |
|---|---|---|
| Wi-Fi and wired access | Access-point placement, room coverage, cabling and device capacity. | Actual activity works in the intended rooms under normal occupancy. |
| Traffic management | Essential classes of traffic and scheduled bulk work. | Calls and important transactions remain usable during downloads. |
| Identity and administration | Separate guest, student or staff access as appropriate; assign administrators. | Access policies and recovery work without sharing administrator credentials. |
| Updates and content | Approved update windows and reusable offline materials. | Data use stays within the plan and required materials remain available. |
| Monitoring | What is measured and who receives actionable incidents. | A local failure can be distinguished from a satellite outage. |
Cisco's video QoS tutorial explains why application quality depends on more than raw bandwidth. Prioritize traffic at the points you control and coordinate with the provider. A local policy may not be honored beyond your network, so verify the outcome rather than relying on a configured label.
Estimate energy and test the whole power path
List the terminal, router, switches and access points with their normal and peak loads. Include the equipment that people need to complete the task. A powered satellite terminal is of little use if the local access point has shut down.
Have the power system designed for the actual equipment and site. Test the promised runtime under a representative load and document the restart sequence. For solar-powered sites, generation through unfavorable weather and the charging arrangement require their own assessment; the arithmetic above does not size a solar installation.
Pilot the busiest normal day before scaling
- Select sites that represent different workloads, power conditions and installation constraints.
- Run a real teaching or branch-work day, including simultaneous users and scheduled updates.
- Measure application outcomes, traffic, data consumption, latency and interruptions with timestamps.
- Test a local power interruption and link recovery through an approved procedure.
- Have the local contact report a staged fault using the support instructions.
- Revise the design, budget and training before copying it to more sites.
A successful acceptance record includes what users did, where they did it and under what load. “Internet works” is too vague to guide expansion. Retain failed cases and their fixes so the next installation benefits from them.
Give each site an owner and a sustainable budget
Budget recurring service, installation, data extras, power, replacement equipment, travel, staff time and training. Maintain an asset list and current configuration references. Give the local contact a short triage sheet: check power, report terminal indicators, describe the affected rooms or applications, and call the named support route.
Use the remote-site planning worksheet for every location and a separate consolidated capacity review. For contractual guarantees and failover acceptance, see enterprise satellite service evaluation.
Sources and further reading
Source links reviewed September 28, 2026. Check current service terms, equipment documents and operational notices when applying the guide.