Person Readers and Intelligent Edge Devices
Click to download Spec > Person Readers & Intelligent Edge Devices.docx
Section 28 42 00
Person Readers & Intelligent Edge Devices Status:
Draft Version 1 – Consultant Ready
Basis Of Design: BluB0X BluSKY
Specification Division:
- Division 28 – Electronic Safety And Security
- Coordinated With Division 14 – Conveying Equipment (Where Used For Elevators)
Related / Normative References:
- Physical Security Management Platform (PSMP)
- Enterprise Identity, Credentials & Biometrics
- Enterprise Access Control System
- Elevator Destination Dispatch Security (DDE)
- Two-Button Elevator Relay Security
- Hybrid Elevator Security
- Elevator Management & Telemetry
- Elevator Emergency Communications
- SimEYES – Elevator Simulation & Planning
- System Health, Telemetry & Assurance
- Security Power, Resiliency & OTA Lifecycle
Part 1 – General
1.1 Summary
A. This section defines requirements for Person Readers, a class of intelligent, AI-driven edge devices providing identity recognition, access authorization, elevator dispatch, intercom communication, visitor processing, and telemetry.
B. Person Readers shall function as identity-centric computing platforms, not simple credential readers, and shall provide consistent behavior across doors, turnstiles, lobbies, elevator kiosks, and elevator cars.
C. Person Readers shall integrate natively with the Physical Security Management Platform and operate autonomously when required.
1.2 Purpose And Intent
A. Replace static card-reader models with multi-modal, high-assurance identity recognition.
B. Reduce friction while increasing security, auditability, and throughput.
C. Enable unified access, elevator dispatch, visitor management, and intercom functionality in a single device.
D. Future-proof buildings through AI-enabled, OTA-updatable edge computing.
1.3 Definitions
• Person Reader: Intelligent edge device performing identity recognition and access actions
• Multi-Modal Authentication: Use of biometric, mobile, card, and other credential types
• Edge Compute: Local processing and decision execution at the device
• Proof Of Presence: Evidence that a specific person was physically present at an access event
Part 2 – System Description
2.1 Person Reader Overview
A. Person Readers shall function as:
• Primary identity authentication points
• Access control readers
• Elevator dispatch terminals
• Intercom and assistance endpoints
• Visitor self-service devices
• Telemetry and analytics sources
B. Person Readers shall support local decision execution with centralized governance.
2.2 Deployment Contexts
Person Readers shall be deployable in:
• Doorways and portals
• Turnstiles and speed gates
• Elevator lobbies
• Upper-floor access points
• Elevator destination dispatch kiosks
• Elevator cars
• Reception and visitor entry points
Part 3 – Identity And Authentication
3.1 Multi-Modal Identity Recognition
Person Readers shall support, at a minimum:
• Facial recognition (1:1 and 1:N)
• Voice recognition
• Appearance recognition (adaptive, non-static)
• Name or identity lookup
• PIN codes
• QR codes
• Mobile credentials
• Apple Wallet credentials
• Google Wallet credentials
• Bluetooth credentials
• All common proximity card formats
Recognition accuracy shall meet or exceed 99.99% under normal operating conditions.
3.2 Biometric Hardware
A. Devices shall include:
• High-resolution color camera
• IR depth camera for liveness detection
B. Depth sensing shall be enabled to prevent spoofing and hallucination attacks.
3.3 Continuous Learning
A. The system shall automatically capture and evaluate images during normal use.
B. The optimal image shall be selected and associated with the identity.
C. Recognition shall adapt to changes in appearance over time.
D. Learning behavior shall be policy-controlled and auditable.
Part 4 – Credential And Access Control Functions
4.1 Access Control Actions
Person Readers shall:
• Grant or deny access to doors, gates, and turnstiles
• Enforce access schedules and policies
• Coordinate with anti-passback and tailgating detection
• Generate complete access audit events
4.2 Integration Modes
Person Readers shall support:
• Reader-To-Security System integration
• Reader-To-Device (Direct) integration
Credential data shall be normalized regardless of wiring topology.
Part 5 – Elevator Integration
5.1 Destination Dispatch (DDE)
Person Readers shall function as full DDE dispatch terminals, supporting:
• Automatic elevator car assignment
• Default floor dispatch
• Default floor override
• Transfer-floor and multi-stage dispatch
• Visitor and VIP routing
• ADA-aware dispatch
5.2 Two-Button Relay Elevators
Person Readers shall:
• Enable authorized floor buttons
• Disable unauthorized floors
• Support escort and two-card logic
5.3 Hybrid Elevator Environments
Person Readers shall dynamically determine whether to:
• Dispatch deterministically, or
• Enable relay-based floor access based on context, location, and policy.
Part 6 – Visitor And Temporary Access
6.1 Visitor Processing
Person Readers shall support:
• Pre-registered visitor lookup
• QR-based visitor credentials
• On-the-fly visitor verification
• Temporary credential issuance
• Automatic expiration
6.2 Proof Of Presence
A. Person Readers shall capture proof-of-presence imagery or metadata.
B. Proof shall be associated with access, dispatch, or visitor events.
Part 7 – Intercom And Assistance
7.1 Two-Way Communications
Person Readers shall support:
• SIP-based two-way audio
• Two-way video communication (where equipped)
7.2 Assisted Access And Dispatch
Operators may:
• Answer intercom calls
• Assist with access or elevator dispatch
• View contextual information (identity, location, elevator state)
Part 8 – User Interaction And Experience
8.1 Touchless And Natural Language
A. Person Readers shall support:
• Voice commands
• Natural language interaction
• Touchless operation
8.2 Accessibility
A. Devices shall be ADA-compliant.
B. Features shall include:
• Audio feedback
• Visual indicators
• Adaptive UI elements
Part 9 – Edge Compute, AI, And Telemetry
9.1 Edge Processing
Person Readers shall:
• Execute decisions locally
• Continue operation during network outages
• Buffer events for later synchronization
9.2 Telemetry And Events
A. Devices shall generate telemetry including:
• Usage statistics
• Recognition confidence
• Errors and health status
B. Telemetry shall feed System Health and Analytics platforms.
Part 10 – Security, Privacy, And Governance
10.1 Privacy Controls
A. Biometric usage shall be policy-driven.
B. Retention, masking, and redaction shall be configurable.
C. Regional and regulatory compliance shall be supported.
10.2 Auditability
A. All actions shall be logged.
B. Logs shall be searchable and exportable.
C. Test and simulation actions shall be clearly distinguished.
Part 11 – Resilience And Lifecycle
11.1 Power And Network Resilience
A. Devices shall support backup power strategies.
B. Graceful degradation shall occur during outages.
11.2 OTA Updates
A. Firmware and software shall support:
• Secure OTA updates
• Staged deployment
• Rollback capability
Part 12 – Diagnostics And Commissioning
12.1 Device Diagnostics
Person Readers shall support:
• Sensor health checks
• Recognition testing
• Communication diagnostics
12.2 Remote Commissioning
Configuration and testing shall be possible without on-site presence.
Part 13 – Hardware Variants And Form Factors
13.1 Device Classes
Supported form factors shall include:
• Wall-mounted readers
• Turnstile-embedded readers
• Elevator car readers
• Kiosk-style readers
Multiple sizes, colors, and finishes shall be available.
Part 14 – Safety And Operational Boundaries
Person Readers shall not:
• Control elevator motion
• Override OEM safety systems
• Interfere with life-safety operation
Part 15 – Submittals And Close-Out
• Device layouts and mounting details
• Wiring and network diagrams
• Configuration documentation
• Acceptance and test results
Part 16 – Acceptable Manufacturers
16.1 Basis Of Design
BluB0X Person Reader family integrated with BluSKY.
16.2 Acceptable Alternatives
Alternatives shall meet all requirements of this specification.
End Of Section 28 42 00