NG-Key
NG-Key
Elevators

Building stacks and elevator profiles tied to people

Treat lifts as governed mobility paths – not as isolated OT subsystems separated from access policy.

NG-Key models elevator groups alongside doors, ensuring vertical routing respects the same permissions, schedules, and exceptions your teams already work with.

Profiles attach cleanly to people and cohorts – contractors, residents, and campus staff inherit stable behavior across floors without custom spreadsheets.

Security reviews gain clarity: who may traverse which layer under which time profiles, with traceability comparable to perimeter readers.

Spotlight

Why Stacks Belong in the Facility Hub

  • Door Equivalent Rigor – Elevator Destinations Inherit Policy Stance Instead of Informal Badge Overrides.
  • Portfolio coherence – campus-wide templates reduce one-off configurations per tower.
  • Operational clarity — incidents reference elevator decisions with the same identifiers used at lobby readers.
  • Fewer emergency gaps — temporary exceptions spread predictably instead of living in local controllers.
  • Cleaner audits — vertical routes connect horizontal access proofs for regulators and insurers.
Minimal elevator bank scene — NG-Key Facility marketing tile

Depth

Functional coverage

Stack Modeling

Represent banks, cars, and calling semantics at the abstraction operators that actually speak.

Group orchestration

Keep sibling shafts consistent – upgrades propagate without rediscovering hardware peculiarities.

People Linkage

Attach elevator eligibility to identity cohorts — visitors, employees, and service providers remain distinguishable.

Temporal Windows

Blend maintenance holds and exception shifts without altering firmware narratives.

Compliance Posture

Demonstrate Controlled Vertical Mobility alongside Perimeter Controls – a Governance Language.

Traceability

Correlate Lobby Reader Choices with Vertical Continuation – Fewer Ambiguous Handovers During Investigations.

Motion

Delivery Sequence

01

Blueprint Stacks

Define Elevator Reality – Banks, Floors Served, and Operational Nuances per Campus.

02

Attach Policy

Map access grants and schedules to stacks without inventing parallel permission semantics.

03

Pilot cohorts

Roll out with bounded groups — observe behavior before activating campus-wide.

04

Operate & Refine

Tune exceptions with audit trails instead of making local controller changes.

Measured improvements

Reduced lift exceptions managed outside the access platform.

Faster incident explanations when vertical routing logic is questioned.

Portfolio teams reuse templates instead of rediscovering each tower.

Procurement sees elevator governance within the same security narratives as doors.

Product Preview

Chapter Walkthrough

Short Cinematic Clip for This Chapter About the Facility – Silent, Repeated in the Page, Players Follow Your Motion Settings Elsewhere on the Page.

Continue Exploring

Switch to Workspace Governance or Edge Operations – or Back to Platform Core.