20 Stories
Zone-level occupancy across a rooftop restaurant, bar and terrace.
20 Stories, nineteen floors above Manchester's Spinningfields district — fine dining, a cocktail bar and an open-air terrace. Counted zones are the restaurant, grill, bar and terrace. Installation dates are not published.
Project at a glance
Customer
Hospitality · Rooftop venue occupancy
Deployment scope
See the installation account below
Measurement focus
Scope or reporting capability, not a verified uplift
Delivery partner
Published deployment account
The initial problem
A multi-space venue at height is not a single front door. The operator needs to hold safety, fire compliance and evacuation planning together with the sense of space a premium guest expects, and a high-rise terrace with restricted exit routes carries more overcrowding risk than a ground-floor room. Rooftop trade also moves with the weather, which makes fixed staffing assumptions weak. Discretion matters to the clientele, so the measurement method itself is a constraint.
Read the published account ↗What SUS installed
SUS installed the Pro3 AI people counting system. The Pro3 acts as a central AI processing hub rather than a simple entrance counter: one unit connects up to seven additional cameras, covering the restaurant, grill, bar and terrace without extra processing hardware. It uses 3D stereoscopic depth sensing, with privacy masking and anonymised GDPR-compliant outputs; the published account states that no faces or personally identifiable images are captured or stored and no real footage is retained. Segregated CPU, GPU and NPU subsystems and a partitioned operating system keep device monitoring alive if the analytics layer fails.
Read the published account ↗How the reporting was used
The published account describes live occupancy visibility across the restaurant, grill, bar and terrace, alongside zone-level dwell time and peak-hour insight. This reporting supports questions about entry pacing, expected covers and demand-led staffing. Those applications are described uses of the system, not evidence of a particular rota change or measured service improvement.
Read the published account ↗The operational change
The documented reporting change is a zone-level view of occupancy and visitor behaviour across the venue. Waste reduction, faster service and better-aligned rotas are intended benefits in the source, not measured outcomes for 20 Stories.
Read the published account ↗What the evidence supports
Published multi-zone deployment and reporting account. No dated operational decision, quantified waste reduction, service result or compliance outcome is supplied.
Sources, approvals and measurement standard
Evidence detail
The account describes deployment scope and qualitative use. No usable before-and-after measurement record has been supplied for this page.
Standard for newly validated outcomes
A future result will be labelled “Measurement record available” only when its KPI definition, baseline, comparison period, site scope, counting exclusions, calculation and source records have been reviewed and publication approved. This is the acceptance standard, not a claim that every existing figure has passed it.
Legacy figures and qualitative accounts
Previously published supplier figures remain labelled as such, with missing measurement details stated. Installation facts, reporting capabilities and qualitative operational changes are not commercial uplift. None of the figures here is presented as independently verified.
Turn visitor evidence into better operational decisions.
Tell SUS what you need to understand, where you need coverage and which decision better data should inform. Send it through the SUS enquiry form and mention this customer story.
Request an occupancy/site survey ↗View matching deployment →