Insight 04 · Remote sites

The site nobody visits, run from one screen.

A telecom tower, a pumping station, a repeater on a hill: powered by the grid when it’s there, by a generator when it isn’t, and visited by a technician with a jerrycan. For decades the only way to know a site’s state was to drive to it. This page is about how remote-site operations grew from the drive-by to the dashboard, what is moving now, the market in a few figures, how a modern site is run, and what that returns.

1990sdiesel + a logbook2000salarm outputs2010shybrid power + fuelLate 2010stower companies2020sthe site reports itself
How it evolvedFive eras, one line

Every decade took one more question off the drive.

First the site’s state was whatever the last visit said. Then failures came in as alarms, then fuel and power became measured quantities, then someone was paid by the litre. The question each time was the same: what can the site tell us before anyone gets in the truck?

1990s

Diesel generators and lead-acid batteries; a scheduled visit; a logbook at the site.

The site’s state was whatever the last visit said.

2000s

Rectifiers and generator controllers with alarm outputs; dial-up or SNMP alarms to a network operations centre.

Failures were reported, at least the ones the controller knew about.

2010s

Site controllers reading power, fuel and environment together; hybrid solar–battery–diesel; lithium batteries; fuel sensors in the tank.

The generator ran less and ran on purpose; fuel became a measured quantity.

Late 2010s

Tower companies took over the sites; energy as a service; power as a line in a contract.

Someone is now paid by the litre and the hour of uptime, so both are counted.

2020s

Renewables at a quarter of operator electricity; remote monitoring as the norm; fuel theft and overlap detected from the readings.

The site reports its own grid, generator, battery, fuel and door; the visit is planned from the data.

What’s moving nowThe last three years
01

Diesel under scrutiny.

The world’s hundred largest tower companies run about four million sites and burned more than two billion litres of diesel in 2024; the pressure to cut it comes from cost, regulators and the operators’ own targets. The sector’s operational emissions fell 13 % from 2019 to 2024; its science-based pathway needs a 45 % cut by 2030.

GSMA · Mobile Net Zero 2026 · 14 Jul 2026
02

Renewables on site.

Solar and batteries at the site, with the generator as backup, are now the design, not the exception. Renewables gave operators 10 % of their electricity in 2019; in 2024 they gave about 70 TWh, and about 70 % of it in Europe, 50 % in North America and 45 % in Latin America.

GSMA · same report
03

Autonomy as a number.

How long the batteries hold a site after the grid fails is measured from the site’s own outages, not taken from a datasheet.

04

Fuel as evidence.

A tank sensor and a delivery record together show where fuel goes — run hours, theft, a leaking line — which used to be a guess.

05

The generator’s own words.

Controllers speak Modbus; their fault codes, run hours and alarms are read directly instead of through an alarm wire.

The market in figuresEach figure with its source
About 4 million

sites run by the 100 largest tower companies in 2024.

GSMA · Mobile Net Zero 2026 · 14 Jul 2026
24 %

of mobile operators’ electricity came from renewables in 2024.

GSMA · same report
About 115 Mt CO₂e

the mobile sector’s operational emissions in 2024.

GSMA · same report
How a modern remote site is runThen → now, by function
Grid and generator
Known at the next visit
Grid present or not, generator running or not, read every minute; each outage an episode with its start, end and what carried the load
Fuel
A dipstick and a delivery note
Level from the tank sensor, use per run hour, days to empty, the next refill planned by the reading; a drop with no run is a theft alarm
Battery
Replaced when it failed
Charge and discharge per outage; autonomy learned from the site’s own history; a battery that holds less than it did flagged
Generator health
Fault code read on site
Run hours, starts, failures to start, overlap with the grid, read from the controller
Access and environment
A padlock
Door open without a planned visit, temperature in the shelter, each an alarm
Visits
A route, fixed
Planned from the data: fuel due, a fault to fix, a door to check
Portfolio
A spreadsheet
Every site on a map by state: on grid, on generator, silent, needs fuel; worst first
Reporting
By hand, monthly
Grid availability, generator hours, fuel per site and per region, uptime, by day
What it returnsMechanisms, not promises
01

The generator runs on purpose.

Overlap with the grid, long runs and failed starts show in the record, and each is a thing to fix.

02

Fuel accounted for.

Litres delivered, litres burned per hour and litres missing are three different numbers, finally.

03

Fewer wasted visits.

The technician goes where the site needs them, with the part, instead of on a round.

04

Outages understood.

How long the batteries actually held, this site, this year — so the next outage isn’t a surprise.

05

A portfolio view.

A hundred sites read as a list, worst first, instead of a hundred phone calls.

06

Silence noticed.

A site that stops reporting is itself a finding, traced to the link, the power or the controller.

These are the mechanisms; the size of each depends on the sites and their grid. We don’t publish savings figures.

Where to startThe usual order · each step uses what the one before it installed
  1. 01

    Grid, generator and fuel

    Three readings from a controller and a tank sensor, for every site, on whatever link it has. The portfolio map pays for itself in the first week.

  2. 02

    Battery and environment

    What each outage drew, the door, the shelter’s temperature.

  3. 03

    The rules

    Refill due, overlap with the grid, a door without a visit.

  4. 04

    Generator control

    From the office, last, and only with a written reason per site.

Where we come in

Forty minutes, free, about your sites.

You leave with the five questions answered for one site and our view, in writing, on whether an assessment is worth doing. If you ask, you see the platform running; if you don’t, you won’t. Chirp Technologies advises site operators and tower companies on this — which controllers can be read, which link suits a site with no fibre, how to count fuel honestly — and built HOLOIN, which runs on your own servers, for operators who want every site’s power, fuel and access on one map.

The five questions are on the Solution design page →

Sources on this pageGSMA · Mobile Net Zero 2026 · 14 Jul 2026The full register →