RF Apex · Prison Solution
Seal the Airspace Above the Facility and Cut Off Contraband Drops
Drones dropping drugs, phones, blades and other contraband into prisons have become a serious and growing threat. RF Apex builds a detection and countermeasure barrier over the secure estate: an approaching drone is detected, verified and dealt with before it can release its payload, closing the aerial delivery route for good.
Send an Enquiry
Executive Decision Summary
A prison project is won on warning time and response discipline. Get these five decisions right at the same time:
Threat and Operating Model
Requirements should distinguish a contraband drop, reconnaissance of the estate, an escape-support flight and innocent overflight from the surrounding area.
| Operating Concern | Why It Matters | What the Buyer Should Define |
|---|---|---|
| Contraband delivery by drone | Drugs, phones and weapons dropped into yards or onto roofs directly undermine security and order inside | Likely drop zones, approach routes, required warning time, payload recovery and evidence procedure |
| Reconnaissance of the estate | Drones photograph walls, yards, staff routines and blind spots to plan drops or escapes | Observation points to protect, incident logging, pattern analysis, police reporting |
| Escape support | A drone can deliver tools or distract staff during an escape attempt | Escalation procedure, coordination with perimeter security, night readiness |
| Launch sites outside the wall | Operators launch from nearby streets, car parks and housing — outside the facility's control | Direction-finding needs, operator location evidence, police handover procedure |
| Innocent and media overflight | Neighbouring homes, press and hobby flyers create alerts that are not attacks | Alert classification, response thresholds, community and privacy considerations |
Detection data supports the control room picture, but an alert alone does not prove a drop was attempted. Verification and evidence handling decide whether an incident stands up afterwards.
Layered Counter-UAS Architecture
A prison system is a short chain with no slack: detect early, verify fast, respond within the law, and recover the evidence. Each layer needs a named owner in the control room.
| Layer | Functional Requirement | Procurement Evidence |
|---|---|---|
| 1. Detect | Find approaching drones with fixed RF detection covering the estate and its surroundings | Frequency coverage, target types including small FPV drones, update rate, known limitations |
| 2. Verify | Corroborate alerts with cameras, track history and officer observation before committing staff | Camera cueing workflow, day/night performance, recording format, false-alarm handling |
| 3. Command | Present tracks and alerts in the control room with yard and wall-sector mapping | User roles, audit logs, integration with the existing security management system, evidence export |
| 4. Decide | Act under the facility's incident procedure: observe, lock down a yard, or authorize a countermeasure | Alert prioritization, decision authority, decision records, response-time targets |
| 5. Respond | Apply spoofing or jamming as authorized, recover payloads, and hand operator evidence to police | Legal authority, spectrum permission, safety interlocks, human authorization, incident reporting |
Important: Detection, identification and countermeasures are three separate decisions. Prisons sit inside communities, so any active response must stay within national law and spectrum rules and be proportionate to the surrounding area.
Coverage Zones and Sensor Placement
Model coverage by security zone. Walls, roofs and neighbouring buildings shape detection and response options very differently across a compact estate.
| Zone | Coverage Objective | Typical Design Considerations |
|---|---|---|
| Exercise yards and open areas | Earliest possible warning of an inbound drop | Sight lines over roofs, camera coverage of drop zones, staff response routes |
| Accommodation blocks and roofs | Detect drones approaching windows and roof spaces | Roof-level sensor placement, building shadowing, payload recovery access |
| Perimeter wall and sterile zone | Detect crossings and loitering before a drop run begins | Wall geometry, external roads and housing, patrol access, power and networking |
| Visits, reception and gate areas | Awareness over the public-facing side of the facility | Public proximity, privacy rules, alert prioritization |
| Control room and evidence zone | Correlate alerts, direct the response and preserve incident records | Time synchronization, retention policy, integration with CCTV and security systems |
System Priorities
The prison configuration concentrates detection and response over the estate and the wall line, so a delivery drone gets no unobserved window.
Detection and countermeasures cover the whole estate and the wall line, day and night.
Approach warning plus fast response is tuned specifically against the drop profile — low, slow and hovering.
Alerts reach the control room in seconds, with spoofing preferred where it safely ends the flight.
RF detection works in darkness and poor weather, when drops are most often attempted.
Project Architecture
Every prison project follows the same process, so coverage, verification and response authority are fixed before the system goes live.
Map the estate layout, wall line, yards, roofs and the surrounding streets and buildings.
Network fixed detection with spherical detection-and-jamming units (APX-DJF-7B) over the estate.
Confirm the drone type and track at the command layer and cue cameras onto the predicted drop zone.
Apply fixed jamming under orders, or guide the drone away with spoofing (APX-DSF-GNSS); patrol officers verify with the F13M.
Typical Applications
One system architecture, applied to the areas where a drone incident costs the most.
A detection and countermeasure barrier covers the entire airspace above the facility.
The wall and sterile zone are watched closely against close-in launches and wall-hugging approaches.
Priority protection over the areas where people gather — and where drops are aimed.
RF detection is unaffected by darkness, so the night shift gets the same picture as the day shift.
Information to Prepare
With these six items ready, RF Apex can fix the detection positions and response methods and prepare a tailored proposal.
Related Equipment and Systems
Spherical detect-and-jam units, fixed detection, fixed spoofing and handheld patrol units seal the airspace above the estate.
Technical Requirements for the RFQ
A useful RFQ describes operational outcomes and acceptance methods, not just a product name. Ask bidders to respond against the same requirement matrix.
| Requirement Group | Buyer Input | Evidence Required from the Supplier |
|---|---|---|
| Threat definition | Drop profiles: drone sizes, FPV types, approach heights, night operations, payload release behaviour | Compliance matrix stating detectable, conditionally detectable or out of scope |
| Coverage | Estate boundary, yards, roofs, wall sectors, required warning time before a drone is overhead | Coverage map, siting assumptions, blind-spot analysis, expansion options |
| Environment | Urban RF congestion, weather exposure, rooftop installation limits, power quality | Environmental ratings, installation limits, maintenance requirements |
| Performance | Alert latency, track continuity to the drop point, direction finding to the operator, evidence retention | Test methods, representative evidence, confidence conditions, documented limitations |
| Integration | CCTV/VMS, security management system, control room displays, police reporting format | Protocol list, API documentation, data ownership, cybersecurity architecture |
| Lifecycle | 24/7 duty cycle, support response, spares, staff training, expected service life | Maintenance plan, spares list, upgrade policy, support SLA |
| Compliance | National rules on jamming and spoofing, spectrum permission, privacy obligations toward neighbours | Certificates, authorization dependencies, division of responsibilities |
Deployment and Integration Plan
Deployment inside a secure facility runs under escort, permits and controlled test windows — plan it as a security project, not a delivery.
Form a stakeholder group: security management, control room, estates, IT, legal and the local police liaison.
Document past incidents, likely drop zones and launch areas, protected assets and required warning time.
Complete RF, line-of-sight, structural, power and network surveys at candidate rooftop and wall positions.
Produce the coverage and integration design, defining sensor roles, blind spots, alert routing and failure behaviour.
Run a pilot with approved test drones in controlled windows, including night runs over the yards.
Tune thresholds, camera cueing, the operator interface and the incident procedure from pilot evidence.
Install, complete FAT/SAT, train control room staff and officers, and schedule recurring scenario exercises.
Any change to buildings, yard use or surrounding development should trigger a review of coverage and procedures.
FAT and SAT Acceptance Framework
Acceptance criteria should be agreed before manufacture and installation. Separate factory verification from performance testing at the real site.
| Test Item | 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 output and alert handling with controlled inputs or representative targets | Run agreed drop-profile scenarios over yards and wall sectors, including night and repeat passes |
| Operator workflow | Verify user roles, alert acknowledgement, evidence export and escalation logic | Measure control room actions, yard lockdown timing, payload recovery and incident reporting in practice |
| Integration | Test documented APIs, data fields, time synchronization, health reporting and fault states | Verify end-to-end exchange with CCTV and the security management system |
| Reliability | Burn-in, restart, power-loss recovery and component health checks | Observe specified continuous operation, communications recovery and environmental behaviour |
| Training and handover | Check manuals, maintenance tools, spares and training materials | Complete operator and maintainer training, competency checks and signed handover records |
Record test geometry, target type, route, altitude, weather, RF conditions, software version and operator actions. A single daytime demonstration is not a complete acceptance test for a threat that mostly arrives at night.
Common Procurement Mistakes
Frequently Asked Questions
Yes. Wideband detection covers 300 MHz–13.4 GHz, including the links used by FPV and racing-type drones commonly used for drops.
No. Jamming targets drone control and navigation bands only and is activated under orders; where collateral impact is a concern, GNSS spoofing provides a lower-impact response.
Yes. RF detection does not depend on light, and night performance is part of the site acceptance testing — because that is when most drops are attempted.
Direction finding on the control link indicates where the operator is located, and the evidence package supports a police handover.
Only the authority named in your incident procedure. The system logs the alert, the verification and the authorizing decision for later review.
That depends on siting and terrain, which is why the RFQ should specify a required warning time and the SAT should measure it on real approach routes.
Official Planning References
For planning context, consult the official sources below. They do not replace national corrections policy, spectrum authorization or legal review.
Tell us your estate layout, wall configuration and incident procedure, and RF Apex will prepare a tailored proposal.
Send an Enquiry