01 / Capability
Pipeline Surveillance & Protection
A pipeline is only as secure as its least-watched kilometre. We build surveillance around the whole corridor — not just the points that are easy to reach.
Onshore pipelines present a security problem that almost nothing else does: an asset that is hundreds of kilometres long, largely unmanned, crossing terrain that ranges from swamp to farmland to built-up settlement, and valuable enough that interference is organised rather than opportunistic.
The usual failure is not the absence of security. It is coverage that thins out at exactly the points where the corridor is hardest to reach, combined with reporting that arrives too late to act on. Interference is rarely instantaneous — there is almost always a window between the first sign and the loss. Surveillance is worth paying for only if it closes that window.
What this covers
- Route survey and vulnerability mapping across the full right-of-way
- Scheduled and randomised foot and vehicle patrols, with route variation
- Aerial survey of terrain that ground patrols cannot cover reliably
- Fixed and mobile monitoring at valve stations, crossings and high-risk segments
- Third-party interference and encroachment detection
- Incident escalation into a single command point with a defined response path
- Illegal connection and tapping-point identification and reporting
- Written activity, incident and trend reporting on an agreed cycle
Aerial survey
Cover the ground patrols cannot reach.
Long stretches of right-of-way run through swamp, creek and dense bush where a foot patrol is slow, exposed, or simply cannot get to at all. Aerial survey closes those segments and gives the command desk a current picture of terrain, encroachment and third-party activity along the whole corridor.
Method
How we approach it
Four principles that shape every deployment of this capability, whatever the site.
Map the corridor honestly
Before proposing anything, we walk and survey the route and grade it segment by segment: access, visibility, settlement proximity, historical incident points, and how long it would realistically take to get a response team to each one. That map, not a standard package, determines where resources go.
Weight coverage to risk, not to convenience
Uniform patrol density across a whole corridor is a comfortable way to spend money badly. Coverage should be concentrated where the vulnerability assessment says it should be, and it should vary in pattern so that it cannot be timed and worked around.
Shorten the distance between signal and action
A patrol observation, a sensor alarm and a call from a community contact should all land in the same place, be logged the same way, and trigger the same escalation ladder. Where that chain is fragmented, detection is real but response is not.
Report in a form that survives scrutiny
Every patrol, observation and incident is logged and reported. That record is what lets you see whether the arrangement is working, and it is what you will need if an incident is ever investigated or disputed.
Scoping
What we will ask you
These are the questions that shape a serious proposal. If you already know the answers, the first conversation moves a lot faster.
- What is the total length, and which segments have a history of interference?
- Where does the line cross settlements, farmland, waterways or public roads?
- What monitoring already exists, and is any of it currently offline?
- Who currently patrols, on what cycle, and how is it evidenced?
- When something is detected, who is called, and what happens next?
- What is the operational cost to you of an hour of downtime?
At a glance
| Typical assets | Trunk lines, flow lines, delivery lines, valve stations, manifolds, rights-of-way and crossings |
|---|---|
| Terrain | Swamp, creek, farmland, forest and built-up settlement |
| Interfaces | Host communities, regulators, joint task force elements, operator HSE and asset teams |
| Reporting | Daily activity logs, incident reports on occurrence, and periodic trend analysis |
Common questions
Before you ask us
Can you cover a corridor that runs through active communities?
Yes — and that case specifically is why our community-integrated capability is not an optional extra. A corridor through populated land cannot be secured by presence alone; it needs the people living alongside it to have a working reason to raise the alarm early. We would scope the two together.
Do you replace our existing security provider or work alongside them?
Either. Where an operator already has guarding in place, we are frequently more useful adding the surveillance, coordination and reporting layer over it than replacing people who already know the ground.
How quickly can a corridor be brought under coverage?
That depends entirely on length, terrain and what already exists, and any provider who answers that question before surveying your route is guessing. We will give you a schedule after the assessment, not before it.