A prison anti-drone solution should detect likely delivery routes, verify activity around restricted perimeters and give trained operators enough time to coordinate an authorized response.
Contraband delivery flights are often low, fast, short and timed to exploit blind areas, shift changes or nighttime conditions. The architecture must support persistent coverage, reliable evidence and coordination between control room, perimeter teams and external authorities.
Executive Decision Summary
Prison projects should prioritize:
- Persistent detection around high-risk fence sectors and internal delivery areas.
- Rapid verification that separates drones from birds, vehicles, maintenance activity and authorized flights.
- Direction, track and evidence information that supports patrol coordination and investigation.
- Night operation, secure networking, controlled data access and audit-ready incident records.
- An authorized response plan that does not create unacceptable risk to staff, inmates or neighboring communities.
Prison Threat and Operating Model
Translate incident history and perimeter geometry into testable scenarios.
| Operational concern | Why it matters | Information the buyer should define |
|---|---|---|
| Contraband delivery over a fence | The target may cross the boundary quickly and release a small payload. | Likely launch roads, crossing sectors, delivery yards, warning time and patrol dispatch objective. |
| Low flight near buildings or walls | Structures can hide targets from a single sensor and cause multipath or clutter. | Building heights, courtyards, towers, line-of-sight constraints and preferred sensor mounting points. |
| Night or poor-visibility operation | Operators require verification and evidence when visual observation is difficult. | Lighting, thermal conditions, camera policy, retention period and identification threshold. |
| Remote pilot relocation | Launch and control positions can move between incidents. | Direction-finding objective, off-site cooperation, patrol boundaries and evidence handoff process. |
| Repeated probing and false alarms | Alarm fatigue can undermine trust and delay real responses. | Acceptable nuisance-alarm workflow, tuning responsibility, allow-list policy and performance review cycle. |
The concept of operations should state who receives the first alarm, who verifies it, who can dispatch a team and who holds authority for any active measure.
Layered Counter-UAS Architecture
A dependable project is designed as a sequence of functions rather than a single appliance. Each layer should have a documented input, output, interface and operator responsibility.
| Layer | Required function | Procurement evidence |
|---|---|---|
| 1. Detect | Discover activity using RF sensing, radar or another approved sensor appropriate to the threat profile. | Supported target classes, frequency scope, update rate, coverage assumptions and known limitations. |
| 2. Verify | Correlate alerts with EO/IR, track history, operator observations and other approved data sources. | Day/night performance, slew-to-cue workflow, recording format and false-alarm handling. |
| 3. Command | Present tracks, alarms, health status and evidence in a controlled operating interface. | Map layers, user roles, audit logs, API or SDK documentation and cybersecurity controls. |
| 4. Decide | Apply the approved concept of operations and escalation rules. | Alarm priorities, operator permissions, decision records, notification paths and response time objectives. |
| 5. Respond | Use authorized non-kinetic, security or law-enforcement actions appropriate to the incident. | Legal authority, spectrum permission, safety interlocks, human authorization and post-event reporting. |
Prison Perimeter and Internal Coverage Zones
A prison is better modeled as several linked security rings than as one circular coverage claim.
| Zone | Recommended coverage objective | Typical design consideration |
|---|---|---|
| Outer observation area | Detect likely approach or launch activity before the target reaches the fence. | Neighboring roads, privacy limits, terrain, public areas and law-enforcement coordination. |
| Fence and wall crossing sectors | Maintain track continuity at the physical security boundary. | Wall height, razor wire, towers, lighting, occlusion and maintenance access. |
| Internal delivery zones | Verify targets and preserve evidence around yards, roofs and service areas. | Camera fields of view, inmate areas, building shadow, target altitude and dispatch routes. |
| Staff response routes | Provide actionable location and track information to mobile teams. | Radio integration, map accuracy, safe approach, incident priority and handoff. |
| Control room and evidence store | Manage alarms, video, track history and post-event reporting. | User roles, secure export, retention, time synchronization and chain of custody. |
Recommended JianHong Product Roles
The following products are starting points for configuration discussions. Final quantities, frequency coverage, interfaces and installation formats must be confirmed from a site survey and an approved concept of operations.
| Product | Role in this solution | When to shortlist it |
|---|---|---|
| P4 Fixed Drone Detection System | Permanent RF-based awareness around defined sectors. | Use where supported control links and persistent perimeter monitoring are primary requirements. |
| BWR-A15 Low-Altitude Surveillance Radar | Additional tracking for targets that may not expose a supported RF link. | Use in open sectors or layered designs with clear radar placement. |
| H8 Portable Anti-Drone Jammer | Portable active-response capability for specifically authorized teams. | Only shortlist after authority, bands, safety interlocks and operator procedures are confirmed. |
| D7 Shield-Type Anti-Drone Jammer | Directional handheld response option for trained authorized users. | Use where mobility and controlled aiming are operationally required and lawful. |
| K100 Fixed Ku-Band Anti-Drone Jammer | Fixed active-response component for a defined integration architecture. | Consider only for approved end users with a site-specific authorization and interference assessment. |
Technical Requirements to Put in the RFQ
A useful request for quotation describes the operating outcome and acceptance method, not only a product name. Ask bidders to respond against the same requirement matrix.
| Requirement group | Buyer input | Evidence requested from supplier |
|---|---|---|
| Threat definition | Drone types, links, likely routes, operating altitude, speed and autonomy concerns. | A compliance matrix explaining what is detectable, conditionally detectable or outside scope. |
| Coverage | Protected boundary, warning zones, terrain, structures, line of sight and required warning time. | Coverage drawing, sensor placement assumptions, blind-zone analysis and expansion options. |
| Environment | Temperature, rain, dust, wind, salt, vibration, lightning and power quality. | Environmental ratings, installation limits, thermal design and maintenance requirements. |
| Performance | Required alert latency, track continuity, direction finding, classification and evidence retention. | Test method, representative evidence, confidence conditions and documented limitations. |
| Integration | VMS, PSIM, GIS, command platform, network, time source and third-party interfaces. | Protocol list, API documentation, data ownership, cybersecurity architecture and version policy. |
| Lifecycle | Operating hours, support response, spares, training, warranty and expected service life. | Maintenance plan, remote diagnostics, spare-parts list, upgrade policy and support SLA. |
| Compliance | Destination, end user, import requirements, spectrum rules and operational authority. | Export screening, certificates, authorization dependencies and a clear division of responsibilities. |
Deployment and Integration Plan
Deployment should combine security operations, facilities, IT, legal, spectrum and external response stakeholders.
- Review incidents, likely launch areas, fence crossings, delivery zones, patrol routes and response timelines.
- Survey building shadow, tower positions, RF conditions, camera views, power and secure network paths.
- Model overlapping coverage at high-risk sectors and document expected blind areas.
- Define alarm priorities, visual verification, dispatch, evidence handling and escalation authority.
- Pilot with approved routes representing low, fast, nighttime and obscured approaches.
- Tune thresholds against birds, vehicles, staff equipment and authorized activity without hiding real targets.
- Complete acceptance, staff training, maintenance handover and scheduled scenario drills.
Changes to fencing, buildings, nearby construction, radio systems or incident patterns should trigger a new survey and tuning review.
FAT and SAT Acceptance Framework
Acceptance criteria should be agreed before manufacturing and installation. The project team should separate factory verification from performance testing at the real site.
| Test area | Factory acceptance test (FAT) | Site acceptance test (SAT) |
|---|---|---|
| Configuration | Verify models, quantities, interfaces, firmware, accessories and documentation before shipment. | Confirm installed assets, coordinates, calibration, network configuration and as-built drawings. |
| Detection workflow | Demonstrate sensor outputs and alarm processing with controlled inputs or representative targets. | Run agreed routes and scenarios across priority zones, including repeat passes and edge conditions. |
| Operator workflow | Verify user roles, alarm acknowledgement, evidence export and escalation logic. | Measure real operator actions, notification timing, handover and incident reporting. |
| Integration | Test documented APIs, data fields, time synchronization, health reporting and fault states. | Validate end-to-end exchange with the buyer’s operational systems and network policies. |
| Reliability | Conduct burn-in, restart, power recovery and component health checks. | Observe defined continuous operation, communications recovery and environmental behavior. |
| Training and handover | Review manuals, maintenance tools, spares and training materials. | Complete operator and maintainer training, competency checks and signed handover records. |
Record the test geometry, target type, route, altitude, weather, RF conditions, software version and operator actions. A single maximum-range demonstration is not a complete acceptance test.
Information to Send for a Project Proposal
Providing the following information helps engineering teams return a useful architecture instead of a generic equipment list:
- Perimeter map, walls, towers, buildings, yards, high-risk delivery areas and adjacent public roads.
- Incident patterns, likely drone types, control links, flight heights, times and payload behavior.
- Warning-time objective from first approach to fence crossing or delivery point.
- Day, night, weather and seasonal visibility requirements.
- Control-room workflow, patrol dispatch, radio, VMS, PSIM, mapping and evidence requirements.
- Privacy, retention, user-access and chain-of-custody policies.
- Power, network, installation, lightning and vandal-resistance constraints.
- Authority and safety scope for any active response.
- Training, spares, support and preventive-maintenance requirements.
- FAT/SAT target routes and the metrics that determine acceptance.
Where security rules prevent sharing an exact drawing, provide an anonymized site plan with approximate distances, terrain, protected zones and installation constraints.
Common Procurement Mistakes
- Placing one sensor at the center of the facility without modeling walls and buildings.
- Ignoring low-altitude blind zones at fence crossings and internal yards.
- Selecting active response before defining legal authority and safe operator procedures.
- Failing to plan evidence retention, time synchronization and incident chain of custody.
- Accepting a daytime demonstration when nighttime delivery is the primary risk.
- Using alarm count alone instead of measuring warning time and operator outcome.
Related Procurement Guides
Frequently Asked Questions
How early can a prison detect an approaching drone?
Useful warning depends on the target, frequency link, terrain, structures, sensor placement and site RF conditions. The RFQ should specify an operational warning-time objective and a test method.
Can the system locate the drone pilot?
Some RF configurations may provide direction or location-related information for supported links, but capability and accuracy depend on the signal, geometry and product configuration. Verify this through site testing.
Is radar required for every prison?
No. Radar can strengthen coverage for non-cooperative targets, but the decision depends on threat scope, site geometry, clutter, budget and required performance.
Can prison staff use a drone jammer?
Only when the organization and operator have the necessary legal and spectrum authority and approved safety procedures. The rules depend on the jurisdiction and end user.
What should prison SAT include?
Test high-risk approach routes, fence crossings, internal delivery areas, day and night conditions, operator notification, evidence export, fault recovery and agreed integrations.
How often should a prison system be reviewed?
Review performance after incidents, construction, RF changes, procedure changes and at scheduled intervals. Repeat representative scenarios to confirm coverage has not degraded.
Official Planning References
For projects connected to civil aviation or U.S. operations, review the FAA counter-UAS legal and policy resources and the FAA airport detection and mitigation guidance. International airport stakeholders can also consult the ICAO UAS intrusion protection material. These references do not replace local legal, spectrum, aviation, import or operational review.
Plan a Prison Perimeter Counter-UAS System
Share an anonymized perimeter plan, high-risk sectors, warning-time target and control-room requirements for a layered architecture and acceptance checklist.
