Transmission corridors are long, thin and remote by nature. Satellite monitoring watches the entire route at once instead of the sections a crew reached this week.
A network is hundreds of kilometres of servitude crossing ground that belongs to other people, much of it far from any depot. Inspection is periodic by necessity. Fire is not. Continuous thermal monitoring along the whole corridor closes the gap between one patrol and the next, without installing anything on the line.
A trip is measured in customers, not hectares
Smoke and flame under a conductor can trip a line long before anything is damaged. Ionised air and particulate across the phase gap is enough, and the fire does not need to touch the structure to take the feeder out. That is why fire risk on a network is not really a fire problem, it is a supply problem.
The cost of the event is set by what is downstream of the feeder rather than by how much veld burned. A fire that would be unremarkable on a farm is a different matter under a line that carries a town, a mine or a pump station.
You do not control the ignition source
The servitude crosses other people's land. The fires that reach it are usually started by someone else, doing something ordinary and legal, on ground you have no say over. Agricultural burning, a firebreak that ran, a fire on a neighbouring property with its own reasons for being lit.
Which means the useful question is not what is burning on the servitude, it is what is burning near it and moving toward it. Detection across the wider area with spread modelling over the corridor answers that. Detection confined to the servitude itself answers it too late.
Modelled spread over real terrain. Under a line, the question is not where the fire is, it is which way it is going and when it arrives.
Vegetation is the other half of the problem
Fire risk under a line is largely a function of what is growing there and how dry it is. Fire danger forecasting and burn history over the corridor tell you which stretches deserve the next clearing crew, which turns servitude maintenance from a fixed schedule into a prioritised one.
That matters because clearing budgets are finite and servitudes are not. A crew sent to the stretch that burned last season and has come back thick is worth more than the same crew working the schedule in order.
Patrols are already stretched
Line inspection in South Africa competes with conductor theft, vandalism and infrastructure that needs attention for reasons that have nothing to do with fire. Adding a fire patrol to that list is not realistic on most networks, and it would still only cover the corridor at the moment the vehicle passes.
Monitoring from orbit does not compete for the same people. It also removes the temptation to put equipment out on the servitude, which on a rural line is equipment that will not be there in a year.
Into the control room, not another screen
Detections can push through the API into the systems your operators already watch, so a fire near a feeder appears where faults appear rather than in a separate application somebody has to remember to open. The monitored area is defined by your own shapefiles, which for a network means the corridor and a margin either side rather than a rectangle over the province.
How would we know about a fire near the line before it trips?
Detection is on heat, across the corridor and the ground around it, rather than on the fault itself. Combined with spread modelling it gives you a fire that is approaching the servitude rather than a trip that has already happened.
Can we monitor the whole servitude, or only substations?
The whole route. The monitored area follows your shapefiles, so a corridor with a margin either side is a normal shape to monitor, and length is not the constraint it is for patrols.
Can we get alerts per feeder or per region?
Yes. Areas can be split so the alert reaches the team responsible for that section rather than everyone on the network.
Does it help us decide where to clear?
Fire danger forecasting and burn history over the corridor show which stretches carry the load and which have regrown since the last fire, which is a better basis for a clearing programme than working the schedule in order.
Can it feed our existing control room systems?
There is API access for integration into an existing GIS, so detections can appear alongside the rest of your network view rather than in a separate application.
Is there hardware on the servitude?
None. Nothing to install along the route, nothing to power, and nothing worth stealing.
BOOK A LIVE DEMO
See Your Own Ground.
Send us the ground you are responsible for. We will run the platform over your actual coordinates and show you what the last fire season looked like from orbit.