Perimeter security guide
Perimeter intrusion detection systems made in India
Gandeevan Technologies designs and builds Prachir, a MEMS fence-sensing perimeter intrusion detection system (PIDS), in Bengaluru, India. The hardware, the firmware and the on-node event classification are ours, and so is the control-room software they report to.
“Made in India” is claimed loosely in perimeter security, and it is worth knowing which version you are being offered, because it determines who can actually help you when a site misbehaves.
The practical question is not patriotic. It is whether the people who wrote the firmware are reachable, whether a sensor can be adapted to conditions your site turns out to have, and whether a spare takes two days or two months to arrive.
Three things “made in India” can mean
They are not equivalent, and only one of them puts engineering judgement within reach.
- Designed and built here. The circuit design, the firmware and the detection logic originate with the supplier, and the boards are manufactured and assembled in India. Changes to behaviour are possible because somebody local owns the source.
- Assembled here. Imported modules or a licensed design are put into an enclosure locally. The product is Indian-assembled; the engineering decisions are not local, and neither is the ability to change them.
- Badged here. An imported product is relabelled and supported by a local distributor. Nothing about it is Indian except the warranty paperwork, which still matters, but is a different thing.
What Gandeevan designs and builds in Bengaluru
Prachir is a fence-mounted MEMS vibration sensing system: N100 sensing nodes on the fence, linked over CAN to an M100 master controller. Each node classifies on-device, reporting climb, cut, drilling and hammer impact as separate events while rejecting rain, vehicle traffic and animal movement before they reach the control room. It is available today.
Sanchalan is the command, control and video management software the perimeter devices report to — events on a map, associated camera views, and event clips retained separately from continuous recording. Also available today.
Abhedya L100, intensity-based fibre optic intrusion detection, is in field trials, and we will not quote a general availability date until those are complete. Abhedya D100, a distributed acoustic sensing system, is in design and has no hardware to trial yet.
The design, the firmware and the classification work are done by the same Bengaluru team that answers the phone. That is the whole point of the arrangement rather than a selling line: the person who can tell you why a node behaved oddly on your fence is the person who wrote the code that made it behave that way.
What we do not offer
Stated plainly, so you do not spend a meeting finding out.
- Taut wire. Not in the range. Where it is the right answer — typically a new-build regular boundary where weather immunity outweighs retrofit cost — it is the right answer, and we will say so.
- Video analytics as a detection technology. We do not sell cameras or scene-analysis software as a sensor. Sanchalan integrates CCTV you already have so that perimeter events arrive with footage attached.
- Detection on rock walls. Prachir is qualified for fencing, brick and masonry. Vibration does not transfer through rock predictably enough to classify reliably, so we exclude it rather than hope.
- A published false-alarm rate. It would depend on your fence, your weather and your traffic, so our number would not predict yours. We publish the alarm and reject classes instead, which you can test on site.
How to verify a “made in India” claim
Ask these of us and of anyone else on your shortlist. The answers are quick to give if they are true.
- Who holds the schematic and the firmware source — you, a licensor, or an overseas principal?
- Where is the firmware written, and can we speak to somebody who wrote it?
- Where are the boards fabricated and assembled?
- Can we visit, and see the product being tested rather than demonstrated?
- Is the stated ingress rating tested or inherited from an enclosure datasheet?
- What is the lead time on a replacement node, and does it come from stock in India?
- Which nuisance sources are explicitly rejected, and is that decision made on the sensor or at a server?
Why the answer matters after the purchase order
Perimeter systems are judged over years, by whether operators still trust them. Trust is lost the first week a system cries wolf in a storm and nobody can change anything about it.
A locally owned design means the detection behaviour can be revisited for a site that turns out to be unusually exposed, or unusually busy with traffic, or home to a determined population of monkeys. A badged import means a support ticket and a wait. That is the difference the phrase should be describing.