Skip to main content
Pedestrian swing-speed-gate lane and adjacent clear passage (illustration)

Face / QR / RFID Turnstile in Kuching & Sarawak

Link a supported face, QR or RFID decision to an agreed pedestrian-gate passage. HJ checks reader placement, credential expiry, gate timing and event mapping, then tests valid, denied and exception flows; recognition alone does not make the moving lane safe.

System selection and integration guideTurnstile / Pedestrian Access
Pedestrian AccessFace / QR / RFID Turnstile
Face, QR and RFID Turnstile system diagram
  1. 01Face / QR / RFID Turnstile
  2. 02Credential, door hardware and safe release
  3. 03Door, lane or workflow interface
  4. 04grant and deny in both directions
Conceptual Face / QR / RFID Turnstile product and system illustration.
Illustration & scope boundary

Conceptual Face / QR / RFID Turnstile product and system illustration for Pedestrian Access. Final device form, model, interfaces and quantities are confirmed from the assessed scope and approved product data. Conceptual identity and permission path for Face / QR / RFID Turnstile, derived from this page's scope, interfaces and acceptance record.

Conceptual planning path — not an as-built drawing or project photograph.

What Face / QR / RFID Turnstile covers

Link a supported face, QR or RFID decision to an agreed pedestrian-gate passage. HJ checks reader placement, credential expiry, gate timing and event mapping, then tests valid, denied and exception flows; recognition alone does not make the moving lane safe.

It sits in Turnstile / Pedestrian Access under Pedestrian 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.

When to use this page

Gate/controller model, reader/terminal protocol, approach, credential validity, passage timing, visitor authority and approved lane-safety/exit behaviour.

Typical environments to assess

  • Supervised office/lobby pedestrian entrance lanes.
  • Staff entrances with assessed peak demand and accessible routes.
  • Existing gates requiring approved sensor/mechanism and release tests.

Engineering SOP & Handover Checklist

From the initial brief to the handover record: what to prepare, check and confirm with HJ.

01

Operational Purpose & Workflow

Link a supported face, QR or RFID decision to an agreed pedestrian-gate passage. HJ checks reader placement, credential expiry, gate timing and event mapping, then tests valid, denied and exception flows; recognition alone does not make the moving lane safe.

02

Pre-Attendance Evidence

Gate/controller model, reader/terminal protocol, approach, credential validity, passage timing, visitor authority and approved lane-safety/exit behaviour.

03

Diagnostic & Testing Path

Confirm gate mechanism, passage and safety sensors, credential/controller interface, direction and supported timing. Define accessible/exception routes, supervision and the separately approved emergency arrangement; credential acceptance is not lane-safety evidence.

04

System & Responsibility Boundary

Verify allowed/denied passage, supported obstruction/direction cases and the approved release with responsible parties. Document power/network effects and safe management of a faulty lane; no gate is promised to stop every tailgate or to replace supervision.

05

Acceptance & Handover Record

Record lane/model IDs, interface and timing baseline, passage/credential tests, accessible route, release responsibilities, operator handover, faults and approved follow-up. Maintenance frequency, parts and response arrangements are agreed separately.

Engineering Scope, Regulatory & Service Boundaries

Responsibility and evidence boundary

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.

This focused topic remains connected to its complete system owner. Final models, quantities, interfaces and included work are confirmed in the assessed quotation.

Questions before proceeding

Use the answers as a planning boundary; site conditions and written scope remain decisive.

Does a recognised face make the lane safe to open?

Credential approval is only one input. Gate mechanism, passage detection, timing and approved release must work together. Test valid, denied, obstruction and authorised exception cases for the supported installation.

Which interfaces need confirmation for this scope?

Confirm gate mechanism, passage and safety sensors, credential/controller interface, direction and supported timing. Define accessible/exception routes, supervision and the separately approved emergency arrangement; credential acceptance is not lane-safety evidence.

What should be verified and recorded at handover?

Verify allowed/denied passage, supported obstruction/direction cases and the approved release with responsible parties. Document power/network effects and safe management of a faulty lane; no gate is promised to stop every tailgate or to replace supervision. Record lane/model IDs, interface and timing baseline, passage/credential tests, accessible route, release responsibilities, operator handover, faults and approved follow-up. Maintenance frequency, parts and response arrangements are agreed separately.

Planning Face / QR / RFID Turnstile? Tell HJ about your site

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.