Field data guide

Video analytics: first decide what to count

What to work out when you consider video analytics for stores or sites: questions, camera conditions, privacy standards, and how results are validated and used.

In this guide

When you consider video analytics, it’s easy to start with camera performance or analysis technology. But even with the same video, the camera position, the analysis method, and the data you keep all depend on what you want to know. If you first decide the question you want answered and who will use the results, you can keep the scope small.

Video analytics concept image of an empty corridor model where two sensors light square zones on the floor, a counting line crosses between the zones, and translucent markers collect in a box beside it

01. Write down the question you want answered

Turn a vague curiosity into a question with an answer you can check, such as “How many of the people passing the store come in, by time of day?” or “Did anyone enter the work zone without authorization?” The more specific the question, the clearer it becomes what to count, in which zones, and in what units.

Also decide who will use the results, when, and for which decisions. Processing and screen layout differ depending on whether it’s a report checked every morning or an alert that needs an immediate response.

What to prepare

  • What to count, the zones, and the counting units
  • Who checks the results, and when
  • Whether to view results in reports or receive them as immediate alerts

02. Camera conditions shape the results

The same analysis can give different results depending on camera height and angle, lighting, objects blocking the view, and how much people overlap as they pass. To decide whether existing cameras can be used, check not only image quality and angle but also the purpose they were installed for and the notices posted about them, and assess on site whether they need to be moved or new ones installed.

Review sample footage under different conditions in advance, such as day and night, or busy and quiet hours. Also decide, based on network conditions and retention policies, whether to process video on site or send it to a separate server.

03. Build privacy standards into the design

Video can capture people’s faces and behavior, so the purpose and scope of recording, how people are notified, and the retention period must be set first. Check applicable laws and regulations and your organization’s internal policies, and agree on the standards with the department in charge of personal information.

First consider keeping only the results the purpose requires. Look at setups that reduce the information handled, such as storing only aggregate counts or events by zone instead of the original video, or masking faces on screen.

What to prepare

  • Purpose and scope of recording, and how people are notified
  • Retention periods for original video and analysis results
  • Access permissions and how records are managed

04. Compare against results checked by people

Before using analysis results as they are, compare them with what a person finds when reviewing footage from the same time period. Recording where the results match and where they diverge shows under which conditions they need refining.

Include scenes where results tend to diverge in the evaluation, such as crowded periods, changes in lighting, and people staying in one place for a long time. Decide with the person who set the question whether the results are good enough to base decisions on.

05. Make sure results feed into the work

If counts stay on a screen, the work doesn’t change. Set up reports and alerts around the steps where results are actually used, such as store operations meetings, staff scheduling, and on-site inspections.

Changes to camera positions or the floor layout also affect the analysis results. Set a procedure and an owner for rechecking the results regularly, so they stay reliable during operations.

That’s all you need before a consultation.

If you prepare the items below, we can align on scope more quickly in early discussions. Even if not everything is ready, we can start with your current situation.

  • The question to answer and who will use the results
  • Camera conditions such as position and lighting
  • Standards for recording notices, retention periods, and access permissions
  • How to evaluate results against checks by people
  • Work steps that reports and alerts will feed into

KPS project guide · The specific technical setup and conditions depend on your requirements.

Let’s outline your challenge together.

From the first idea to operations, we’ll think it through with you.