Get clear answers before you choose the first operating question.

AnyVidi is a Physical Operations Intelligence Platform. In controlled pilots, it uses suitable CCTV and IP camera views to create anonymous spatial evidence about how a physical space operates.

Managers can review completed periods, see supported current conditions and compare what was observed after a change they selected.

It is the shared physical reference where supported spatial evidence is placed. Movement, completed journeys, waiting, queues, interactions and use of areas or assets can be understood in the context of the same site.

It is not a decorative 3D model, a video archive or a claim that uncovered areas are live.

AnyVidi relates suitable camera views to the mapped physical site and validates their position, overlap and coverage. Compatible cameras can be positioned automatically, while AnyVidi continues to lead the audit and validation.

The result is one operating view of the same place rather than a set of disconnected camera feeds.

Where approved camera coverage supports the question, AnyVidi may measure entries, exits, footfall, occupancy, density, dwell, waiting, queues, mapped movement, anonymous journeys, transitions, physical interactions, area or asset use and nearby team coverage.

The Spatial Audit selects only the measurements the operating question needs and the camera views can support.

AnyVidi can be configured for showrooms, fashion and grocery stores, furniture and specialty retail, shopping centres and hospital operations when suitable coverage supports the operating question.

The platform stays the same, but the mapped areas, questions, conditions and approved evidence change with the sector.

Suitable existing CCTV and IP-camera views can often remain in use. Suitability depends on the operating question, angle, stability, image quality, lighting, obstructions, overlap, coverage, frame rate, compression and usable scene depth.

Not every camera or view supports every measurement. A Spatial Audit confirms what can be used and where a real gap remains.

Yes, when the views are suitable and their relationship can be validated. Supported views are placed in the same physical reference so managers can understand connected areas without treating each feed as a separate world.

No. The core setup uses depth-aware computer vision to relate suitable 2D camera observations to the shared 3D reference. It does not require LiDAR or a dedicated depth sensor.

This is spatial operating context, not a claim of LiDAR-equivalent, survey-grade or centimetre accuracy.

The mapped site may include the full physical space, but live observation stops where suitable camera coverage stops. AnyVidi does not invent movement inside blind or uncovered areas.

If the operating question depends on a confirmed gap, the audit may recommend repositioning a camera or adding targeted coverage.

Distance and proximity may be used when geometry, calibration and visibility are suitable. Controlled pilots may also provide anonymous aggregate estimates of height and general physical dimensions when the view, privacy boundaries and acceptance criteria are defined.

This does not mean exact individual body measurement or automatic clothing-size selection.

REVIEW lets managers look back at completed operating periods in the same spatial context. It can show supported routes, journeys, dwell, waiting, queues, area use and coverage relationships after the period has ended.

LIVE shows current supported conditions such as movement, waiting, queues, congestion, pressure on an area and nearby team coverage. A configured condition may produce a live operational alert in supported pilot deployments.

Not every observation automatically becomes an alert.

IMPROVE compares the evidence before one manager-selected change with a later observation. The manager chooses the change and decides how to respond to the comparison.

AnyVidi does not predict the result, apply the change automatically or prove that the change caused a business outcome.

AnyVidi configures conditions and alert rules with the customer for the approved pilot scope. In supported deployments, a live operational alert may be sent to the available team responsible for that area.

A team member may choose to accept the alert and take responsibility for it. This is not automatic individual assignment, an SLA or employee scoring.

No. AnyVidi can surface supported conditions, alerts and suggestions for manager review. It is not presented as autonomously directing employees, applying layout changes or replacing management judgment.

Configured pilot locations, regions and equivalent time periods may be compared under the same customer-approved definitions. The comparison may use supported evidence about journeys, waiting, service pressure and nearby team coverage.

It is not an individual employee ranking. Sales, revenue or service-outcome comparisons require the relevant authorized business records.

In supported pilot deployments, anonymous operational data may be used to update each location's configured baseline. This lets the site be assessed in the context of its own recurring conditions rather than treating every location as identical.

The system may surface location-specific conditions or suggestions for manager review. It does not apply changes automatically or combine separate customer locations into one shared baseline.

No. AnyVidi does not require facial recognition, biometric identity or a persistent profile across visits. Temporary, non-identifying journey continuity may be used only within an approved mapped area and time window.

The purpose is to understand the operation, not to identify a person.

No. AnyVidi may show team coverage by role, area or time period, but it does not turn that evidence into an individual employee score or ranking.

In supported pilot configurations, camera images used for inference are processed on an AnyVidi Edge PC or equivalent customer-site infrastructure. Continuous raw video is not uploaded to the cloud for standard inference.

The approved deployment defines any customer-side video handling separately.

The agreed purpose defines who can access the data and how long it is kept. In supported deployments, temporary anonymous operating data and identifiers are deleted automatically at the configured end-of-day boundary.

This statement does not create a universal retention rule for customer-owned video or separately connected business records.

Anonymous operational metadata may be synchronized when the agreed service requires it. Required KPIs, service status, control and synchronization data, together with approved integration outputs, may also use the network connection.

AnyVidi avoids continuous raw-video transport. This is a low-WAN approach, not a zero-bandwidth promise.

They are tied to the approved area, operating question and time window rather than a named person. Access, review and retention boundaries are agreed for the deployment, and temporary identifiers are deleted at the configured end of day in supported deployments.

Camera evidence can describe supported movement, routes, dwell, waiting, queues, zones, spatial relationships and use of areas or assets. It does not by itself establish a sale, purchase, basket, SKU, inventory state, appointment, completed test drive, service outcome, motive, intent or causal business result.

Those recorded facts must come from an authorized business system.

CRM, DMS, POS, inventory, appointment and service systems may add separately authorized context when the use case needs it. The required connection must be scoped, approved and implemented for that deployment.

AnyVidi does not imply that every named connector is already available or deployed.

AnyVidi accesses business records only when the customer has approved the purpose, access and connection, and the implemented integration supplies the required record. Camera-based physical understanding works without treating those records as camera observations.

A Spatial Audit starts with one practical operating question and checks whether the existing camera views, relevant areas and deployment conditions can answer it reliably. It reviews coverage, genuine gaps, processing, privacy and any separately authorized business context.

It is not an automatic certification or a guarantee that every camera and area is suitable.

Bring the operating question you want to answer first, the areas it concerns and the decision or response it should support. A current camera inventory, site or floor plan when available, network constraints and any required business-system context help define the scope.

The audit identifies useful camera views, measurable areas, blind spots, confirmed coverage gaps, the shared spatial reference, the first measurement set, privacy boundaries, manual steps and required integrations.

When the site and question are suitable, the next step is a clearly scoped pilot plan with agreed definitions and acceptance criteria.

When the Spatial Audit confirms the existing cameras are suitable, the only new AnyVidi hardware required on site is the Edge PC. LiDAR, a dedicated depth sensor or a replacement camera system is not required for the core setup.

The audit defines the approved Edge configuration. The deployment agreement confirms whether AnyVidi supplies it or approved customer-site infrastructure is used.

The behavior depends on the approved deployment design and the services involved. AnyVidi does not make a universal promise about offline continuity, delayed synchronization or automatic recovery.

The Spatial Audit and deployment plan define what remains available locally, what pauses and how service is restored for the actual site.

Timing depends on site size, camera count, network readiness, Edge infrastructure, coverage gaps and required integrations. The Spatial Audit defines that scope before a realistic plan is agreed.

Software and model update handling is defined in the approved maintenance and access process for each deployment. AnyVidi does not publish one universal update schedule for every site.