Assess a compatible barrier protective radar for its exact detection role, coverage and controller input. HJ distinguishes protective hold-open detection from an entry trigger, checks the lane and target conditions, and tests the agreed arrangement without treating a radar name as complete safety evidence.
Conceptual Anti-Crush Radar product and system illustration for Safety. Final device form, model, interfaces and quantities are confirmed from the assessed scope and approved product data. Conceptual vehicle journey and lane safety for Anti-Crush Radar, derived from this page's scope, interfaces and acceptance record.
Conceptual planning path — not an as-built drawing or project photograph.
Assess a compatible barrier protective radar for its exact detection role, coverage and controller input. HJ distinguishes protective hold-open detection from an entry trigger, checks the lane and target conditions, and tests the agreed arrangement without treating a radar name as complete safety evidence.
It sits in Barrier Gate / Vehicle Access under Safety. The final deliverable is shaped by the intended outcome, the installed or proposed environment and the interfaces that must be owned, supplied, integrated and tested.
Radar/barrier models, trigger versus protective role, lane geometry, required targets, mounting/coverage, input behaviour and witnessed tests.
From the initial brief to the handover record: what to prepare, check and confirm with HJ.
Assess a compatible barrier protective radar for its exact detection role, coverage and controller input. HJ distinguishes protective hold-open detection from an entry trigger, checks the lane and target conditions, and tests the agreed arrangement without treating a radar name as complete safety evidence.
Radar/barrier models, trigger versus protective role, lane geometry, required targets, mounting/coverage, input behaviour and witnessed tests.
Confirm barrier/arm support, balancing assembly, protective detection, credential/controller interface and operator authority for the actual lane. Trigger detection, access authorisation and protective inputs have different roles; fees and central software are separately scoped.
Verify authorised and denied entry, the agreed detection/protective behaviour and supervised exception route in a safe lane window. Document power/network loss and recovery on the installed system; retain a safe pedestrian route and never bypass a faulty protection.
Record lane/model IDs, arm and detector configuration, approved rules and interfaces, release responsibilities, witnessed tests and follow-up. Keep maintenance, parts and any platform/payment dependencies explicit rather than promising uninterrupted traffic.
HJ coordinates assessment, engineering, installation, integration, testing and lifecycle support only for the scope recorded in the quotation. ISD handles catalogue, model, datasheet, supply and availability enquiries. Customer, consultant, builder and appointed-specialist responsibilities remain explicit.
Final scope, quantities, compatibility, access, programme, availability and responsibility are confirmed during assessment and quotation.
This focused topic remains connected to its complete system owner. Final models, quantities, interfaces and included work are confirmed in the assessed quotation.
See related systems, how HJ installs them, and support for equipment you already have.
Use the answers as a planning boundary; site conditions and written scope remain decisive.
Not necessarily. Confirm the exact supported function, targets, configuration and barrier input. Verify the installed coverage and failure response; one detection device does not establish the safety of the complete entrance.
Confirm barrier/arm support, balancing assembly, protective detection, credential/controller interface and operator authority for the actual lane. Trigger detection, access authorisation and protective inputs have different roles; fees and central software are separately scoped.
Verify authorised and denied entry, the agreed detection/protective behaviour and supervised exception route in a safe lane window. Document power/network loss and recovery on the installed system; retain a safe pedestrian route and never bypass a faulty protection. Record lane/model IDs, arm and detector configuration, approved rules and interfaces, release responsibilities, witnessed tests and follow-up. Keep maintenance, parts and any platform/payment dependencies explicit rather than promising uninterrupted traffic.
Tell us where it will be used, what it needs to do and what equipment you already have. HJ will recommend the right system, explain who is responsible for what, and agree the next step with you.