Use agreed employee or tenant identity and entitlement as the starting point.
Workplace and smart buildings integration
Make secure storage part of the connected building experience.
Carry identity, arrival and location context into an allocated Vpod locker journey—then use agreed activity data to inform workplace and estate decisions.
- One joined-up arrival
- Credential-led storage
- Stronger estate visibility
Match storage to arrival, booking, zone and available locker capacity.
Bring agreed locker events into workplace and property reporting.
The integration opportunity
Move lockers from a separate utility into the tenant experience.
Smart Spaces currently presents a mobile workplace experience alongside its Smart Building OS, including building access, desk and room booking, visitor experiences, analytics and connected-building visibility. A Vpod workflow can be designed around the relevant identity and location context so storage feels like part of arrival—not another system to find.
This connects flexible workplace lockers to the employee journey. Where a building also receives employee parcels, parcel lockers can remove collections from reception and parcel rooms without confusing the two operational workflows.
The connected building journey
From “I’ve arrived” to “my storage is ready”.
The building recognises the person and their context. Vpod turns that into a clear physical storage experience, then returns the agreed evidence.
- 01 · IDENTITY
Recognise the person
An agreed employee or tenant identity establishes who is arriving.
- 02 · CONTEXT
Understand the visit
Arrival, booking, building, floor, zone and timing shape the requirement.
- 03 · ALLOCATION
Select suitable storage
Configured rules match eligible capacity to the user and location.
- 04 · CREDENTIAL
Continue with one identity
Mobile, wallet, badge or another agreed method provides locker access.
- 05 · EXPERIENCE
Open, use and release
Directions and status make secure storage easy to find and reuse.
- 06 · INSIGHT
Return agreed evidence
Allocation, opening, release and timeout events can inform estate insight.
When arrival does not follow the plan
Changed buildings, no capacity, expired access or credential failure route to defined operational owners.
Across the building portfolio
Common identity, naming, reporting and support principles can coexist with local zones and building rules.
Illustrative solution-design journey only. Screen labels and example data do not represent a live Smart Spaces or Vpod deployment.
Designed for shared building ownership
One experience, four operational viewpoints.
Workplace Experience
Make storage feel like a natural part of arrival, booking and the working day.
Connect workplace lockers to the employee experience →Property Managers
Use locker demand and activity alongside wider building and tenant insight.
Position smart storage within the connected workplace estate →Facilities Managers
Reduce local allocation tasks, key handling and avoidable support activity.
Explore locker priorities for Facilities Managers →IT Directors
Define identity, resilience, system ownership, data direction and governance.
Review connected locker considerations for IT Directors →Remove building friction
Resolve the gaps between digital workplace plans and physical storage.
Compare operating models
Isolated locker software versus a connected smart-building experience.
See connected operations in action
Extend building intelligence into the physical storage journey.
The Smart Estate Logistics Platform video shows the wider Vpod principle: connect people, storage events and operational visibility rather than adding another isolated application.
Watch Smart Estate Logistics Platform
Solution design checklist
Confirm the digital and building rules together.
Trigger and context
Confirm which identity, booking, arrival or access event begins the locker journey.
Identity and entitlement
Define the authoritative user source, eligibility rules and credential method.
Allocation and experience
Agree location, capacity, accessibility, directions, release and timeout rules.
Events and data direction
Specify which locker events move where, when and for what operational purpose.
Exceptions and governance
Assign support ownership, fallback, privacy, retention, audit and change control.
Multi-site operation
Standardise identity, naming and reporting while recording local building differences.
Integration availability, supported triggers, data direction and delivery scope must be confirmed during solution design. This page does not assert a certified native integration, customer deployment or commercial partnership. Product names and trademarks belong to their respective owners.
Start with the building journey
Show us how people enter, work and move through the building.
Bring the identity model, arrival and booking journey, building hierarchy, credential rules and current locker operation.
Book an integration workshop







