Skip to main content
Credential reader and elevator lobby call panel – Floor & Visitor Lift Access in Kuching & Sarawak (illustration)

Floor & Visitor Lift Access in Kuching & Sarawak

Apply approved floor permissions and temporary visitor access through a supported lift interface. HJ checks destination/floor mappings, credential expiry and reception procedures with the lift contractor; access events are not automatically a record of every passenger journey.

System selection and integration guideLift Access
Lift / ElevatorFloor & Visitor Lift Access
Floor and Visitor Lift Access system diagram
  1. 01Floor & Visitor Lift Access
  2. 02Floor permissions and lift interface
  3. 03Door, lane or workflow interface
  4. 04allowed and denied floor selection
Conceptual Floor & Visitor Lift Access product and system illustration.
Illustration & scope boundary

Conceptual Floor & Visitor Lift Access product and system illustration for Lift / Elevator. Final device form, model, interfaces and quantities are confirmed from the assessed scope and approved product data. Conceptual identity and permission path for Floor & Visitor Lift Access, derived from this page's scope, interfaces and acceptance record.

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

What Floor & Visitor Lift Access covers

Apply approved floor permissions and temporary visitor access through a supported lift interface. HJ checks destination/floor mappings, credential expiry and reception procedures with the lift contractor; access events are not automatically a record of every passenger journey.

It sits in Lift Access under Lift / Elevator. 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

Lift/interface model, approved floor map, resident/staff/visitor groups, visitor expiry, reception authority, exception route and lift-contractor coordination.

Typical environments to assess

  • Residential or office lifts with contractor-approved access interfaces.
  • Floor permission and temporary-visitor workflows with tested expiry.
  • Installed access controllers serviced separately from lift machinery.

Engineering SOP & Handover Checklist

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

01

Operational Purpose & Workflow

Apply approved floor permissions and temporary visitor access through a supported lift interface. HJ checks destination/floor mappings, credential expiry and reception procedures with the lift contractor; access events are not automatically a record of every passenger journey.

02

Pre-Attendance Evidence

Lift/interface model, approved floor map, resident/staff/visitor groups, visitor expiry, reception authority, exception route and lift-contractor coordination.

03

Diagnostic & Testing Path

Coordinate the supported credential-to-floor access interface and approved mappings with the lift contractor. Door/visitor links require compatible devices and software; access permissions do not replace lift motion, emergency recall or other safety functions.

04

System & Responsibility Boundary

Test allowed, denied and expired floor permissions with the responsible contractor and authorised users. Document access-layer power/network loss and recovery separately from lift operation; do not bypass lift protections or infer every journey from credential events.

05

Acceptance & Handover Record

Record approved floor/relay mappings, controller and reader versions, user groups/expiry, contractor responsibilities, authorised changes, acceptance cases and event-report limits. Retain the approved lift safety boundary and recovery procedure.

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 lift access event prove a passenger reached that floor?

Not necessarily. An authorisation or floor-selection event is not automatically a complete journey or passenger-location record. Confirm what the installed controller records, test mappings and visitor expiry, and define the limits of any audit report.

Which interfaces need confirmation for this scope?

Coordinate the supported credential-to-floor access interface and approved mappings with the lift contractor. Door/visitor links require compatible devices and software; access permissions do not replace lift motion, emergency recall or other safety functions.

What should be verified and recorded at handover?

Test allowed, denied and expired floor permissions with the responsible contractor and authorised users. Document access-layer power/network loss and recovery separately from lift operation; do not bypass lift protections or infer every journey from credential events. Record approved floor/relay mappings, controller and reader versions, user groups/expiry, contractor responsibilities, authorised changes, acceptance cases and event-report limits. Retain the approved lift safety boundary and recovery procedure.

Planning Floor & Visitor Lift Access? 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.