Satellite Connectivity for Remote Worksites: A Procurement Guide

Connectivity has quietly become a procurement line item on remote Australian worksites, but it is still specified the way it was a decade ago: as whatever the nearest telco happens to sell. On a site where the office is a demountable and the closest fibre is several hundred kilometres away, that habit is expensive. The choice of satellite connectivity for remote worksites now decides whether telemetry, safety systems, video calls and payroll actually function on the day you need them.

This guide is written for the people who write the specification, not the people who sell the dish. It covers how to turn a vague requirement into measurable criteria you can hold a supplier to, including latency floors, power budgets, mounting standards, spares and handover. It also covers where satellite is the correct answer, and where a terrestrial service still earns its place.

The Real Cost of Treating Connectivity as an Afterthought

Most remote operations do not budget for connectivity as infrastructure. It arrives as a monthly expense on a phone bill, chosen by whoever was setting up the site office that week. The connection then gets judged on price and coverage alone, with no analysis of what the site actually needs to transmit.

That approach holds until it does not. A supervisor cannot approve a purchase order, a crane camera feed drops mid-lift, a compliance report misses its lodgement window, or a lone worker check-in fails to register. Each of those presents as an operational failure but has the same root cause. When you specify connectivity for a worksite, you are really deciding which of those failures your business is prepared to absorb.

A Site Without Connectivity Is a Site Without Data

Modern worksites generate far more data than most people assume. Fleet telematics, fuel and plant monitoring, survey corrections, daily site diaries, safety inductions, timesheets and photographic evidence of completed work all travel over the same connection. None of it is discretionary when the client or the regulator expects a record.

The practical test is not peak speed but sustained usefulness. Ask what the site must be able to do at four in the afternoon on a bad weather day, when the connection is at its worst and the reporting deadline is closest. That is the condition your specification should describe, because that is the condition you will eventually be measured against.

It helps to separate the load into categories. Administrative traffic such as email, invoicing and timesheets is low bandwidth but delay sensitive at payroll cut-off. Video and voice traffic is moderately bandwidth hungry and very delay sensitive. Machine and sensor telemetry is usually low bandwidth but intolerant of dropouts, because a gap in a telemetry record is indistinguishable from an equipment fault.

What Low Earth Orbit Actually Changed

The single most important change in remote connectivity has been orbital altitude. Traditional nbn satellite services such as Sky Muster operate from geostationary satellites roughly 36,000 kilometres above the equator. A signal making that round trip carries a latency penalty that no amount of local engineering can remove.

Low Earth orbit constellations sit far closer to the ground. That shorter path reduces round-trip delay to a level that behaves much more like a terrestrial connection, which is why services built on it can support video calling, remote desktop work and interactive applications that geostationary links handle poorly.

The difference matters most for anything conversational. Voice over IP, video meetings, remote equipment control and live camera monitoring all degrade noticeably as latency rises. Where a geostationary link will comfortably carry email and batch file transfer, a low Earth orbit link can carry a working day.

Where Terrestrial Networks Still Belong

Satellite is not automatically the right answer for every site. Where fixed wireless or a terrestrial service reaches with usable capacity, it is often the more economical monthly option, and it should be assessed honestly rather than dismissed in favour of a new dish.

The useful framing is coverage versus consistency. A terrestrial service that covers the site office but not the pit, the paddock or the laydown yard leaves you needing a mobile solution anyway, and running two services is rarely cheaper than running one that follows the work.

For genuinely remote operations the decision usually comes down to where the work moves. If equipment, vehicles and crews relocate through the day, a transportable terminal that travels with them will outperform a fixed service that anchors them to one spot. That portability, rather than raw speed, is what makes satellite the default answer on most remote sites.

A connectivity specification is not a description of a product. It is a written statement of the minimum conditions under which your operation can still function, and it should be specific enough that a supplier can be held to it.

How to Specify Satellite Connectivity for Remote Worksites

Once you accept that connectivity is infrastructure, the specification writes itself more easily than most people expect. The trick is to express requirements in the units your operation already uses: seconds of delay, watts of draw, millimetres of clearance, and dollars per month across the fleet.

Write the specification so that it can be tested. A requirement that cannot be measured on site will be argued about at the first performance review. Every criterion below can be checked with equipment you already own, which is exactly what makes it enforceable.

Write a Latency Floor, Not a Preference

Latency is the criterion that separates a connection people use from one they quietly avoid. If a site has to run video conferencing, remote machinery support or live camera feeds, state the maximum acceptable round-trip delay explicitly rather than describing the experience you want.

Support the floor with the applications that depend on it. A specification that says "suitable for site communications" invites a cheap answer. A specification that lists the applications, the number of simultaneous users and the acceptable delay for each is far harder to satisfy with an unsuitable service.

Then verify it rather than assuming it. Test the link at the worst time of day, in the worst weather, with the normal number of users connected. A connection that performs at nine in the morning and fails at four in the afternoon has not met the specification, and the test needs to happen before the service is accepted.

Specify the Power Budget in Watts

Power is where remote installations are most often under-designed. A Starlink Mini on a direct 12 volt DC connection typically draws somewhere in the region of 25 to 40 watts in normal use, with idle draw lower and start-up peaks higher as the terminal acquires its satellite.

Those figures need to be multiplied out. A terminal drawing roughly 30 watts consumes about 720 watt hours over a full working day, before you add the router, any switching or telemetry gear, and the inverter losses if you are converting from DC to AC. On an off-grid or vehicle-based installation that is a material load against your battery capacity.

Voltage tolerance deserves equal attention. A 12 volt system in a working vehicle is rarely at 12 volts: it sits higher while the alternator is charging and drops during cold cranking and heavy winching. Specifying a supply with a wide input window avoids the intermittent brownouts that present as unexplained reboots. A unit such as the Starlink Mini 12V to 30V Power Supply (Anderson Plug) exists precisely because nominal system voltages in the field wander well beyond their label.

Specify Mounting and Environmental Envelope

Mounting is the part of the specification most often left to whoever installs it, and it is the part that most often fails. A terminal that is knocked out of alignment by corrugations or a branch will drop its link, and nobody on site will connect the two events.

The specification should name the surfaces the kit will be attached to and the range of vehicles it must fit, because a fleet rarely consists of identical units. A tray-back ute, a light truck and a supervisor's wagon present different mounting opportunities, and a solution that only fits one of them will not be adopted across the fleet.

Environment belongs in the same paragraph. Write down the conditions the installation must survive: dust, corrugations, high ambient temperatures, and the likelihood of being driven through water crossings. A Starlink Mini Roof Rack Mount answers one part of that question by giving the terminal a fixed, elevated position clear of the tray and free of the shading that a roof line or a canopy can cast.

Standardising the Kit Across a Fleet

A single working installation proves the concept. A fleet of them proves the business case, because the savings come from never having to think about it again. Standardisation is what turns a clever one-off into something a site administrator can support without specialist help.

The goal is a kit that any competent tradesperson can install from a written procedure, using parts held in stock, without a phone call to head office. Every deviation from that standard is a future support cost, and those costs accumulate faster than the original purchase price.

One Kit, Many Vehicles

Fleet standardisation starts with accepting that the vehicles are not identical. Rather than specifying a different product for each model, specify a common interface and a small number of adapters, so the same terminal moves between a ute, a truck and a trailer.

Quick-release mounting is worth prioritising for this reason. A Starlink Mini Magnetic Mount and similar quick-fit options let a single terminal be redeployed within a shift to wherever the work has moved, which is often the difference between a connectivity asset that gets used and one that sits in a cupboard.

Standardisation also simplifies training. When every kit in the fleet deploys the same way, an induction can cover it once, and a crew transferring between sites arrives already knowing how to set up. That consistency is worth more on a remote site than a marginal performance gain from a bespoke installation.

Spares, Consumables and Cable Discipline

Remote sites fail on the small things. Cables, connectors and fuses cause more downtime than terminals, because they are the parts that get pulled, pinched and corroded, and they are the parts nobody keeps a spare of.

A procurement specification should therefore list consumables alongside hardware and nominate who holds stock. Fuses, replacement cable runs, connector bodies and cable ties are inexpensive individually and ruinous in aggregate once you account for the trip to town that a missing part triggers.

Cable discipline is a design decision, not an installation detail. Where cables run across a tray or through a bulkhead, specify strain relief and a fixed route. Heat, abrasion and vibration are predictable failure modes, and a cable that is properly routed on the day of installation will outlast several that are simply draped into position.

Asset Registers, Handover and Warranty Evidence

Connectivity hardware is an asset and should be entered in the same register as any other plant. Recording serial numbers, installation date, vehicle assignment and the service plan attached to each unit makes it possible to answer basic questions later: which vehicles are due for renewal, which kit has gone missing, and which units are still under warranty.

Handover deserves the same discipline. When a site demobilises or a vehicle is sold, the terminal should be deactivated, recovered and returned to the register rather than left in a glovebox. Unrecovered hardware is one of the quiet leaks in remote operations, because nobody notices until the next site orders replacements.

Since connectivity now carries safety systems, telemetry and compliance reporting, the register also becomes evidence. Being able to demonstrate what was installed, when it was commissioned and how it was tested is valuable when a client audits your systems or an insurer asks how a site was connected. Treat the records as part of the installation, not as paperwork to be completed afterwards.

Frequently Asked Questions

Is satellite connectivity reliable enough for a commercial worksite?

Low Earth orbit satellite services are now used routinely on remote Australian operations for telemetry, voice, video and administrative systems. Reliability depends less on the technology than on the installation: a well-mounted terminal with a wide voltage tolerance, adequate power and clear sky view behaves predictably. Poor mounting, under-sized power and obstructions cause most of the failures people attribute to the service itself.

How do I compare satellite against an nbn service for a remote site?

Compare them against the work rather than the marketing. Fixed wireless and nbn satellite services generally carry lower monthly costs where they reach with usable capacity, but geostationary satellite services operate from around 36,000 kilometres and therefore carry noticeably higher latency, which affects video and interactive applications. Assess coverage across the whole site, not just the office, and confirm current pricing and plan terms directly with each provider before committing.

What should a connectivity specification include?

At minimum: the applications the site must run, the number of simultaneous users, an acceptable latency ceiling, a power budget in watts with the supply voltage range, the surfaces and vehicles the hardware must fit, the environmental conditions it must survive, the spares to be held on site, and the documentation required at handover. Each of those can be tested on site, which is what makes the specification enforceable.

Making the Specification Stick

Satellite connectivity for remote worksites is no longer a novelty purchase made under pressure when a site goes live. It is infrastructure that carries safety systems, compliance records and the commercial transactions that keep a project moving, and it deserves to be procured with the same rigour as the plant it supports.

The work required is not complex. Decide what the site must be able to do at its worst moment, express those requirements in measurable units, standardise the hardware so it can be supported in the field, and keep records that prove the installation was done properly. A specification written that way survives contact with a real site.

Outcamp supplies the hardware layer for remote Australian installations, from wide-input supplies such as the Starlink Mini 12V to 30V Power Supply (Anderson Plug) and fixed mounting options such as the Starlink Mini Roof Rack Mount, through to wired site networking with the Starlink Mini/Gen 3 Ethernet Adapter (4 Ports). If you are writing a connectivity specification and need help matching hardware to the conditions on your site, our team works with remote operations across Australia.