Separate a plate or RFID read failure from denied authorisation, a controller output problem or a barrier fault. HJ checks permitted credentials, lane mapping and supported interfaces, then verifies the correction through recognition, decision, safe release and the configured event record.
Conceptual planning path — not an as-built drawing or project photograph.
Tell us the fault and your location. Diagnostic attendance, repairs, parts and any travel charges are confirmed with you before work.
Survey, repair & outstation arrangements →Separate a plate or RFID read failure from denied authorisation, a controller output problem or a barrier fault. HJ checks permitted credentials, lane mapping and supported interfaces, then verifies the correction through recognition, decision, safe release and the configured event record.
It sits in Barrier Gate Service under Vehicle Access. 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.
Camera/reader and controller models, affected plate/tag, authorised test users, read/decision events, interface map and barrier/detection condition.
From the initial brief to the handover record: what to prepare, check and confirm with HJ.
Separate a plate or RFID read failure from denied authorisation, a controller output problem or a barrier fault. HJ checks permitted credentials, lane mapping and supported interfaces, then verifies the correction through recognition, decision, safe release and the configured event record.
Camera/reader and controller models, affected plate/tag, authorised test users, read/decision events, interface map and barrier/detection condition.
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.
Identity, image, credential and movement data require an authorised controller, lawful access, proportionate collection, retention rules and recorded administrator responsibility.
Installed platform, authorised ownership, parts compatibility and serviceability are checked before any repair or restoration outcome is proposed.
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.
Recognition, permission, output and barrier readiness are separate stages. Trace the authorised event and supported interface through each stage; a read result is not proof that release is permitted or that the lane is safe.
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 what the system is, what is going wrong or what you want checked. HJ will confirm the work needed, explain who is responsible for what, and agree the next step with you before any work starts.