Diagnose enrolment, matching or credential-read problems on the installed face, fingerprint or RFID equipment. HJ distinguishes a failed credential from denied permissions or a door fault, uses authorised access and verifies the agreed alternative credential after correction.
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 →Diagnose enrolment, matching or credential-read problems on the installed face, fingerprint or RFID equipment. HJ distinguishes a failed credential from denied permissions or a door fault, uses authorised access and verifies the agreed alternative credential after correction.
It sits in Door Access Service under Access Control. 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.
Device/reader models, affected credential type, authorised test users, enrolment history, permission settings, biometric-data responsibility and alternative entry method.
From the initial brief to the handover record: what to prepare, check and confirm with HJ.
Diagnose enrolment, matching or credential-read problems on the installed face, fingerprint or RFID equipment. HJ distinguishes a failed credential from denied permissions or a door fault, uses authorised access and verifies the agreed alternative credential after correction.
Device/reader models, affected credential type, authorised test users, enrolment history, permission settings, biometric-data responsibility and alternative entry method.
Confirm the reader or terminal decision path, controller protocol, lock output, door contact, exit devices, power and supported software. Attendance, intercom or alarm links require a documented interface and responsible owner; a working credential does not prove the complete door is safe.
Test valid and denied entry, ordinary exit and the approved emergency release with responsible parties. Network loss, power loss and backup affect different components; document the actual installed behaviour without assuming fail-safe means every escape requirement is satisfied.
Record opening IDs, device/firmware labels, credentials and user groups, permitted schedules, administrative ownership, power/release dependencies, acceptance results and unresolved limits. Keep personal data, retention, revocation and later changes under the owner policy.
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.
Reading or matching a credential is separate from granting permission to that door at that time. Review authorised user rules, expiry and the controller/lock path. Do not change permissions or enrolment without the responsible administrator.
Confirm the reader or terminal decision path, controller protocol, lock output, door contact, exit devices, power and supported software. Attendance, intercom or alarm links require a documented interface and responsible owner; a working credential does not prove the complete door is safe.
Test valid and denied entry, ordinary exit and the approved emergency release with responsible parties. Network loss, power loss and backup affect different components; document the actual installed behaviour without assuming fail-safe means every escape requirement is satisfied. Record opening IDs, device/firmware labels, credentials and user groups, permitted schedules, administrative ownership, power/release dependencies, acceptance results and unresolved limits. Keep personal data, retention, revocation and later changes under the owner policy.
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.