Building stacks and elevator profiles tied to people
Treat lifts as governed mobility paths — not isolated OT subsystems disconnected from access policy.
NG-Key models elevator groups alongside doors so vertical routing respects the same grants, schedules, and exceptions your teams already operate.
Profiles attach cleanly to people and cohorts — contractors, residents, and campus employees inherit stable behaviour across floors without bespoke spreadsheets.
Security reviews gain clarity: who may traverse which stack, under which schedule windows, with traceability comparable to perimeter readers.
Spotlight
Why stacks belong in the facility hub
- Door-equivalent rigor — elevator destinations inherit policy posture instead of informal badge overrides.
- Portfolio coherence — campus-wide templates reduce one-off lift configurations per tower.
- Operational clarity — incidents reference elevator decisions with the same identifiers used at lobby readers.
- Fewer emergency gaps — temporary exceptions propagate predictably instead of living in local controllers.
- Cleaner audits — vertical routing joins horizontal access evidence for regulators and insurers.
Depth
Functional coverage
Stack modelling
Represent banks, cars, and calling semantics at the abstraction operators actually speak.
Group orchestration
Keep sibling shafts consistent — upgrades propagate without rediscovering hardware quirks.
People linkage
Attach elevator eligibility to identity cohorts — visitors, staff, and vendors stay distinguishable.
Temporal windows
Blend maintenance holds and exception shifts without rewriting lift firmware narratives.
Compliance posture
Demonstrate controlled vertical mobility alongside perimeter controls — one governance language.
Traceability
Correlate lobby reader choices with vertical continuation — fewer ambiguous handoffs during investigations.
Motion
Delivery sequence
Blueprint stacks
Define elevator reality — banks, floors served, and operational nuances per campus.
Attach policy
Map grants and schedules to stacks without inventing parallel credential semantics.
Pilot cohorts
Roll out with bounded groups — observe behaviour before campus-wide activation.
Operate & refine
Tune exceptions with audit trails instead of local controller edits.
Measured improvements
Reduced lift exceptions maintained outside the access platform.
Faster incident explanations when vertical routing is questioned.
Portfolio teams reuse templates instead of rediscovering each tower.
Procurement sees elevator governance inside the same assurance narrative as doors.
Product preview
Chapter walkthrough
Short cinematic clip for this facility chapter — muted, looped in-page players follow your motion preferences elsewhere on the site.
Facility hub
Every facility capability at a glance
Open a chapter for full narrative and product video — maps, vertical mobility, visitors, parking, lockers, contractors, and credential media.
Maps & indoor
Routing graphs, analytics-ready indoor data, and guest wayfinding from one editor.
Open
Elevators
Building stacks and elevator profiles tied to people and policy.
Open
Visitors
Invitations, reception workflows, and indoor directions for guests.
Open
Parking
Lots and vehicle-aware operations next to identity decisions.
Open
Locker banks
Smart locker walls aligned with facility hierarchy and audit.
Open
Contractors
Time-bound, auditable vendor access instead of shadow credentials.
Open
Card creator
NFC and card artefacts prepared next to the same reader fabric.
OpenContinue exploring
Switch to workspace governance or edge operations — or return to the platform core.