Skip to main content

Commercial Buildings

Vision Copilot for Commercial Buildings

Map cameras to the places your team manages and ask Vision Copilot about tenant-facing common areas and recurring service pressure. OrionAlerts analyses scenes over time to surface alerts, recommendations and operational scores that help you decide what to review today and what to improve next.

Illustrative photograph — not a verified customer deployment

Coordinate a response across shared spaces.

Multi-tenant buildings have overlapping activity at reception, lifts, parking and service entrances. Security may see an event without knowing which facilities or tenant team should act. Define the purpose and response owner for each monitored area. Common-area visibility should not become unrestricted access to every tenant's activity.

A reference deployment covers lobbies, lift lobbies, parking entries and service corridors, typically on the building's own network segment rather than tenant IT. Set retention against the property's privacy and lease obligations, and route each alert type to the correct owner: facilities for service and common-area events, security for access and incident review. Where an access-control or BMS integration exists, align review with its logs rather than treating video as the only record of who entered a space and when.

Ask your building what needs attention. OrionAlerts maps cameras to your sites, buildings, floors, zones and rooms, analyses scenes over time, and brings the results into Vision Copilot. Search in everyday language, review alerts and recommendations, and use operational scores to guide daily decisions and improvement priorities.

Building intelligence

Your operation, mapped

Organise views around the places the team recognises. Select the location to establish the context for scene observations and Copilot questions. This example uses the shared hierarchy; map the actual site rather than inventing rooms or camera coverage.

See your operation in the structure your team uses. Organise sites, buildings, floors, zones and rooms, then map cameras to their locations. A question about reception, a loading bay or a production area starts with a recognisable place and its available camera context.

Site

Site

Building

Office Building

Floor

Floor

Zone

Reception Zone

Room

Lobby

Cameras are mapped to the selected lobby or common zone so questions about ground-floor reception start from recognisable operational context.

Vision Copilot

Ask Vision Copilot

Ask what happened. Find where it happened. Decide what to review next. Vision Copilot lets you type questions and search available visual observations in everyday language. Use the mapped location and a relevant period to focus the conversation on the operation you manage.

Illustrative example

Question

Find observations from the ground-floor reception this week.

Five ways teams use this

Use cases for your operation

01Core capability

Bring the right location into the decision

Connect tenant-facing common areas and recurring service pressure to the building tree and its mapped cameras. The team can start with a named operational area instead of trying to remember which camera covers it, making observations easier to interpret and discuss.

02Core capability

Search visual observations in everyday language

Ask Vision Copilot, “Find observations from the ground-floor reception this week.” Use the location and review period to focus the search on relevant available observations. The purpose is to reach useful context without manually working through unrelated camera views.

03Core capability

Identify recurring conditions across scenes

Ask, “Which floors or common zones show recurring congestion?” Ongoing scene analysis supports review of patterns across the available observations. Use the recurring condition to frame the next investigation rather than treating one isolated alert as the whole operational picture.

04Core capability

Turn analysis into an improvement decision

Ask, “What should the facilities team prioritise in today's building review?” Review the recommendation alongside the underlying observations and the team's operating knowledge. The example below shows a practical next step; it is a suggested action for human consideration, not an automatic instruction to change equipment or procedures.

05Core capability

Use scores to structure the next review

Use 0–100 scores to organise attention across building floors and common zones where equivalent coverage and score definitions exist. Review the contributing observations and coverage before acting. The proposed dimensions for this industry are Common-Area Readiness, Reception Flow and Service-Area Access Practices; use the approved product methodology when demonstrating actual values.

Illustrative decision story

From scenes to decisions

Illustrative decision story — not a customer result. Observe: Lobby congestion repeatedly coincides with overlapping visitor and service activity. Ask: “What should the facilities team prioritise in today's building review?” Suggested recommendation: Review reception guidance and service scheduling with facilities, then compare similar operating windows. Decide: The responsible team reviews the evidence and agrees an action. Follow up: Revisit the same area and comparable period to assess observations, coverage and score movement. A subsequent change is not proof of causation.

Cameras are mapped to the places your teams manage. Ongoing scene analysis brings observations and alerts into that location context. Use Vision Copilot to ask what happened and what needs attention, review recommendations, and decide on the next action. Return to the same scope and a comparable period to assess the observations and scores after a change.

01Map
02Observe
03Ask
04Prioritise
05Act
06Review

Observed

Lobby congestion repeatedly coincides with overlapping visitor and service activity.

Recommendation

Review reception guidance and service scheduling with facilities, then compare similar operating windows.

Follow up

Revisit the same area and comparable period to assess observations, coverage and score movement.

Operational scores

See what needs attention—and what changes after action.

Bring tenant-facing common areas and recurring service pressure into a structured review with operational scores out of 100. Use the score alongside the location, period and contributing observations to decide where to focus. Compare building floors and common zones where equivalent coverage and score definitions exist only when the assessment basis is consistent.

Proposed score names and formulas are design recommendations. Demonstrate only approved product values or clearly labelled illustrative states. If no valid opportunities exist, show Not assessed — never invent a flattering percentage.

Readiness/orderliness

Common-Area Readiness

Not assessed

Proposed dimension · proposal-3.2

A mapped common pathway or staging space is clear according to an agreed observable criterion.

Flow

Reception Flow

Not assessed

Proposed dimension · proposal-3.2

A sampled visible lobby or reception presence stays within the agreed operational threshold.

Access practices

Service-Area Access Practices

Not assessed

Proposed dimension · proposal-3.2

Reviewed entry into a configured service or restricted area follows the agreed schedule or access rule.

Score presentation context

Period
Comparable operating window
Scope
Selected floors and common zones with mapped cameras
Coverage
Monitoring Coverage shown separately when assessment windows are defined
Evaluated checks
Not assessed — awaiting approved product dataset

Deployment

Start with the cameras, conditions and decisions that matter.

A useful deployment starts with a defined problem. Review camera coverage, operating hours, lighting, network capacity and who will respond to an alert. Select a small set of observable events, agree how to assess them and expand after the pilot demonstrates useful results. Separate common and tenant-controlled areas. Agree permissions, notice, retention and incident-sharing responsibilities. Test daylight changes through glass entrances and crowded lobbies.

  • Mapped hierarchy for pilot common areas and service zones
  • Agreed purpose and response owner per monitored area
  • Permission, notice and retention rules for tenant-facing views
  • Representative testing across daylight, crowding and after-hours windows
  • Defined network segmentation between building and tenant systems, and alignment with access-control or BMS logs where those integrations exist

Standards boundary

Standards and procurement considerations

Consider premises and fire planning alongside privacy obligations for building monitoring. Video can help review conditions; it does not grant fire approval, occupancy permission or building certification.

  • National Building Code / premises and fire planning

    Video can help review visible conditions; it does not grant fire approval, occupancy permission or building certification.

    Authoritative source
  • Digital Personal Data Protection Act / Rules

    Define monitoring purpose, authorised users and retention with legal/privacy owners before deployment.

How to evaluate a pilot

What to measure in a pilot

Pilot results depend on scene conditions and event definitions. Compare reviewed alerts with representative ground-truth observations, including missed events. Track nuisance alerts and response times before setting a wider rollout target. The measures shown here are evaluation criteria, not guaranteed improvements.

Useful after-hours alerts

Confirmed relevant after-hours zone entries divided by reviewed alerts for the defined service areas, using an agreed review rubric and schedule.

Source of truth: Schedules, sampled footage and supervisor review log

Sampled queue/count error

Difference between camera-derived aggregate occupancy or queue estimates and manual samples for the same lobby window.

Source of truth: Manual lobby samples and camera-derived counts

Incident retrieval time

Time for an authorised reviewer to locate the correct common-area clip from a defined starting input such as time window and lobby.

Source of truth: Timed investigation exercises

Common questions

Frequently asked questions

Can each tenant access only its authorised views?

Verify the required permission model in the selected configuration before rollout.

Can occupancy estimates control HVAC?

That requires a separately assessed BMS integration and validated measurements. It is not assumed in this scope.

Can video prove an exit is legally compliant?

No. A visual obstruction observation is only one input to the building's safety process.

What is Vision Copilot?

Vision Copilot is OrionAlerts' conversational interface for asking questions and searching available visual observations. It uses the mapped operational context to help teams review what needs attention and consider relevant next steps.

Why map cameras to a building tree?

A camera becomes more useful when its view is connected to a place the team recognises. The hierarchy connects sites, buildings, floors, zones and rooms with their cameras, giving searches and operational reviews a consistent location context.

What do scores out of 100 mean?

Scores help organise review of observed conditions. Read each score with its stated assessment basis, location, period and supporting observations. A score is not a certificate of safety or compliance, and missing observations do not prove that conditions are satisfactory.

Can recommendations guide property improvements?

Recommendations can help your team identify issues to inspect and changes to assess, such as staging arrangements, access practices or camera coverage. Review the evidence and operational constraints before deciding on a change; outcomes are not guaranteed.

Can we use our existing CCTV cameras?

Compatible IP camera streams may be reused after a technical assessment. Camera position, image quality, supported stream formats, network access and available compute determine which use cases are practical. Confirm the selected cameras and deployment architecture before rollout.

How should video access and retention be planned?

Define the purpose of monitoring, authorised users, retention period and incident-review process before deployment. Discuss the required access, storage and privacy controls during the assessment and verify what the selected configuration supports. Apply your organisation's policies and the requirements relevant to your location and people being recorded.

Ask Vision Copilot about your commercial buildings.

See how Vision Copilot connects a mapped area with visual search, recommendations and scores for commercial buildings.

Illustrative commercial office building photograph used for industry context