The face of the moon was in shadow
Satellite gets specified for one of two reasons. Either there is genuinely no terrestrial option, or there is one and it cannot be relied on. Those are different problems and they lead to different designs, so the first useful step is deciding which you have.
The three situations
No coverage at all. A camp, a conservancy, an exploration site or a construction project outside any cellular footprint. Satellite is the primary link and everything depends on it, so availability matters more than speed.
Coverage that exists but fails. A site with cellular or fibre that drops during rain, at peak, or whenever a backhoe finds the duct. Satellite is a backup, and the design question is how quickly and how automatically it takes over.
Coverage that cannot be trusted for other reasons. Operations where the terrestrial network may be congested, monitored or deliberately interrupted during exactly the period the link is needed. This is the case least often stated in a requirement and the one that most changes the answer.
What actually varies between options
The market is usually presented as a choice of orbit. Orbit matters, but it is not what a buyer feels.
| What varies | Why it decides things |
|---|---|
| Latency | Determines whether interactive use (voice, video, remote control) is comfortable or merely possible |
| Contention | Shared capacity is cheap until everyone uses it at once. Committed capacity costs more and behaves |
| Terminal | Size, power draw, and whether it needs a technician or a person following instructions |
| Power | At an off-grid site the terminal's consumption sets the solar and battery specification |
| Licensing | Terminals and their operation are regulated. Not optional, and not fast if left late |
| Cost shape | Hardware once against airtime monthly. The second is what the budget actually has to survive |
Latency and contention are the two that determine whether users are satisfied. A link that tests well on installation day and is unusable at 09:00 on a Monday is a contention problem, and no amount of retesting the hardware will find it.
The mistake that costs the most
It is sizing the link for the application and forgetting everything else the site will do with it.
A remote camp specifies satellite for operational reporting, sizes it accordingly, and then discovers that thirty people with phones have found the Wi-Fi. The operational traffic (the reason the link exists) is now competing with video streaming, and it loses.
The fix is not a bigger link. It is deciding, before installation, what the link is for and enforcing that in configuration: operational traffic prioritised, staff welfare access permitted within a ceiling, and both monitored. Welfare access matters at remote sites and removing it entirely is neither kind nor sustainable. But it has to be bounded, and the boundary has to be technical rather than a notice on a wall.
The cost shape, which is where budgets fail
Satellite hardware is a one-off number that appears in a capital budget and gets approved. Airtime is a monthly number that lands in an operating budget for as long as the site exists, and it is the one that decides whether the link survives its second year.
Two things distort the comparison at purchase. Promotional airtime pricing that steps up after an introductory period, and allowances that look generous until the site's actual usage is measured rather than estimated. A requirement written as an average monthly figure will be wrong, because remote sites are not average; usage spikes during the incidents and mobilisations that are precisely when the link matters.
Budget for twelve months at the plan you will actually be on, with headroom for the months that are not typical. Then ask what happens if the site is still there in three years, because remote sites usually are.
The first thirty days
Most satellite links that disappoint were commissioned badly rather than specified badly.
Three things are worth insisting on at handover. A baseline performance measurement taken at a busy hour rather than at installation, so there is something to compare against when users say it has got worse. A written record of the terminal's position and alignment, so it can be restored by someone who was not there. And a named person on site who has been shown what to check, in what order, before escalating.
That last one converts a multi-day outage into a twenty-minute one more often than any hardware decision made during procurement.
Satellite and radio are not competitors
At most remote sites both belong, because they solve different problems.
Two-way radio handles communication between people on the site, immediate, group-wide, no dependency on anything beyond the local infrastructure, and it keeps working when the satellite link is down. Satellite handles communication between the site and everywhere else.
The sites that run well treat them as one system rather than two purchases. The radio network works locally, the satellite link carries the site's traffic outward, and where it matters the two are bridged so a person on a radio can reach someone who is not on site at all.
PLACEHOLDER 
AGPO Certified 
