Shopping centres · Physical Operations Intelligence

Where does centre traffic become operational pressure across configured zones?

In a controlled pilot, supported common-area views can show where configured traffic, occupancy, waiting, and facilities demand build across mapped junctions. Location comparison is limited to calibrated sites and aligned definitions.

Plan a Spatial Audit

First, we verify which camera views can reliably support each entrance, junction, doorway, and shared area.

Evidence boundaryA camera can describe pass-by, entry, waiting, and physical continuation. Tenant sales and revenue require an approved tenant or POS connection. Cleaning completion and work-order state require the approved facilities workflow.

Illustrative shopping-centre operating view with entrances, corridor junctions, storefronts, vertical transport, shared areas, and anonymous flow. — Illustrative operating view. No customer or performance result is shown.

Camera-native shopping-centre scope

Build the common-area operating view from camera-verifiable signals.

This is a representative scope, not a fixed metric ceiling. A useful KPI starts with the entrances, junctions, shared areas, service rules, and operating question that matter to your team.

Traffic and property flow

Entry, exit, footfall, occupancy, and density
Floor, wing, corridor, and vertical movement
Anonymous groups, peaks, mapped journeys, and drop-off
Mapped routes and a supporting 2D heatmap

Storefront and campaign

Storefront pass-by and covered doorway entry
Pass-by to entry continuation where both lines are supported
Campaign and event area dwell
Campaign or event continuation to a linked storefront

Shared areas and transport

Food-court and common-area load
Corridor, lift-lobby, and escalator pressure
Queue, estimated waiting, and configured thresholds
Role-level facilities and security coverage

Facilities and response

Restroom entry and exit counts at the entrance boundary
Manually configured facilities-review conditions
Configured pilot conditions with location, threshold, priority, and reviewed action
Centre, region, event, and period comparison

Dashboard action signalsPortfolio comparisonDashboardAPIsTenant, POS, and facilities context

Inside the shopping centre

At which configured junction does common-area flow begin to wait or build pressure?

Keep the physical centre fixed. Change the question to see how entrances feed floors and wings, where corridor movement reaches a storefront, when shared spaces build pressure, and when facilities demand needs a response.

Centre question

Comparison view

Corridor and covered storefront doorway

Read the selected question inside one mapped shopping centre.

At which covered storefront does corridor movement pause before entry?

Compare pass-by, pause, and covered doorway entry. A storefront transition does not prove a sale.

What the camera can read

Corridor pass-by
Pause at the storefront
Covered doorway entry and physical drop-off

Camera reads

Suitable views can read entry and exit, footfall, anonymous groups, mapped movement, area dwell, corridor and lift-lobby pressure, storefront pass-by and doorway continuation where coverage supports both lines, shared-area load, restroom entry and exit counts at the entrance boundary, waiting, and team coverage by role.

Connected systems confirm

A tenant or POS system confirms sales, revenue, transactions, and recorded campaign outcomes. A facilities or work-order system confirms cleaning completion, task state, incidents, and the approved reset of a use-count rule.

Journeys remain anonymous and bounded to the configured visit window. Cameras stay outside the restroom and read only its entrance boundary. The page does not identify visitors or rank individual employees.

Configured pilot condition

Selected corridor and covered doorwayConfigured continuation windowAttention

Corridor pass-by and storefront pause are active while covered doorway entry remains below the configured continuation threshold.

Manager-reviewed action

Review wayfinding, frontage orientation, and shared-area coverage while the corridor window remains active.

Location-specific learning

Keep each centre’s configured operating context distinct.

In a standard deployment, camera images are processed on the on-site Edge PC. Continuous raw video is not sent over the WAN. Required anonymous operational metadata may synchronize to the cloud so model weights can learn recurring entrance, corridor, storefront, shared-area, and facilities patterns for this centre.

Learns local patterns

Keeps recurring flow, pressure, and service patterns specific to this centre.

Presents a recommendation

Layout and operating recommendations go to manager review. Nothing is applied automatically.

Start with camera suitability

Map the flow and facilities question you need to understand.

A Spatial Audit identifies usable views, blind areas, entrance and doorway lines, corridor junctions, vertical-transport and shared zones, facilities rules, live conditions, connected-system requirements, and the first operating question worth measuring.

Plan a Spatial Audit

All six centre questions remain available without interaction

How does observable traffic distribute across configured entrances, floors, and wings?Read entry and exit, first mapped direction, and movement between levels without identifying the visitor. Entry and exit by covered entrance · First floor or wing reached · Mapped movement between levels One entrance is feeding an active floor or wing beyond its configured distribution range while adjacent routes remain underused. Review wayfinding and available common-area coverage while the arrival window remains active.
At which covered storefront does corridor movement pause before entry?Compare pass-by, pause, and covered doorway entry. A storefront transition does not prove a sale. Corridor pass-by · Pause at the storefront · Covered doorway entry and physical drop-off Corridor pass-by and storefront pause are active while covered doorway entry remains below the configured continuation threshold. Review wayfinding, frontage orientation, and shared-area coverage while the corridor window remains active.
Where does configured flow build around lifts or escalators?Read arrivals, waiting, and movement between levels around covered lift lobbies and escalator approaches. Lift or escalator approach · Lobby queue and estimated waiting · Movement to the next level Arrivals continue beyond the configured duration while lobby pressure grows and movement to the next level remains limited. Review wayfinding, available support, and the affected vertical route before pressure spreads into the corridor.
When does configured shared-area load remain without visible service coverage?Read active occupancy, dwell, queue pressure, and nearby facilities or security coverage by role. Food-court or shared-area load · Queue and waiting pressure · Facilities or security coverage by role Shared-area load remains above the configured threshold while the required service role is not present nearby. Review moving available facilities or security coverage to the active shared area while the condition remains live.
When does the restroom entrance count reach the manually configured review condition?Cameras stay outside the restroom. They count entries and exits at the entrance boundary and can surface a manually configured facilities-review condition. Restroom entrance and exit count · Count since an approved reset · Configured facilities-review threshold Entrance counts since the approved reset have reached the configured facilities-review threshold. Review the facilities condition. Reset the count only through an approved workflow or staff and manager confirmation.
Does physical movement continue from the campaign or event area to a covered storefront?Read event or campaign-area dwell and physical continuation to the covered storefront. Tenant sales and revenue require connected data. Campaign or event area dwell · Mapped route to the linked storefront · Covered doorway continuation and physical drop-off Campaign or event attention is active while continuation to the linked covered storefront remains below the configured threshold. Review event orientation, wayfinding, and the route to the linked storefront while the campaign window remains active.

Centres, regions, events, and equivalent periods can be compared under the same selected operating question.

How does the same flow and service question change across centres? Select an entrance, corridor, covered storefront, vertical-transport zone, shared area, facility rule, event, or operating window. Compare the same camera-observed evidence across centres, regions, and equivalent periods.

Camera reads: Suitable views can read entry and exit, footfall, anonymous groups, mapped movement, area dwell, corridor and lift-lobby pressure, storefront pass-by and doorway continuation where coverage supports both lines, shared-area load, restroom entry and exit counts at the entrance boundary, waiting, and team coverage by role.

Connected systems confirm: A tenant or POS system confirms sales, revenue, transactions, and recorded campaign outcomes. A facilities or work-order system confirms cleaning completion, task state, incidents, and the approved reset of a use-count rule.

Build the common-area operating view from camera-verifiable signals. Entry, exit, footfall, occupancy, and density · Floor, wing, corridor, and vertical movement · Anonymous groups, peaks, mapped journeys, and drop-off · Mapped routes and a supporting 2D heatmap · Storefront pass-by and covered doorway entry · Pass-by to entry continuation where both lines are supported · Campaign and event area dwell · Campaign or event continuation to a linked storefront · Food-court and common-area load · Corridor, lift-lobby, and escalator pressure · Queue, estimated waiting, and configured thresholds · Role-level facilities and security coverage · Restroom entry and exit counts at the entrance boundary · Manually configured facilities-review conditions · Configured pilot conditions with location, threshold, priority, and reviewed action · Centre, region, event, and period comparison

You define the operating question. We shape the KPI with you. Define the important areas and the decision you need to make. We combine camera-verifiable signals into a tailored KPI and add approved tenant, POS, or facilities context when the question needs it.

Location-specific learning: In a standard deployment, camera images are processed on the on-site Edge PC. Continuous raw video is not sent over the WAN. Required anonymous operational metadata may synchronize to the cloud so model weights can learn recurring entrance, corridor, storefront, shared-area, and facilities patterns for this centre.