VisaRoxy Book a demo

Use cases

Six jobs a camera can be given this month.

Each scenario below is written the same way: the problem as the site experiences it, what a VisaRoxy agent does about it, and what is different once it is running. Pick the one that matches a problem you already have.

Book a live walkthrough See it by industry
Warehouse loading area where workers, a forklift and marked pedestrian routes can be monitored as operational events.
The problem

What the site lives with today, described in the terms the people on shift use.

What VisaRoxy does

The agent, its condition, and the action it triggers. No vague capability language.

What changes

The operational difference, stated as a change in who knows what, and when.

What it needs

Cameras and destinations the scenario assumes, so you can tell if it fits your site.

Scenarios

Problems that already have a camera pointed at them.

Every one of these is a condition a camera can observe and a rule can describe. If your problem needs a measurement the video does not contain, it belongs in a different system.

01 · Logistics

Dock and yard flow

Trailers arrive, wait, get loaded and leave, and nobody knows a lane has stalled until the end-of-shift numbers arrive. The yard marshal is watching four doors at once and cannot be at all of them.

What VisaRoxy does

A dock agent watches each door and the apron in front of it. It measures how long a trailer sits without activity, how long a queue extends, and whether a door is empty during a booked window. When a lane passes its threshold, the agent raises a named event and notifies the marshal with the clip that shows why.

What changes

A stalled lane becomes a fifteen-minute problem instead of a nightly discovery. The end-of-shift review stops being the first time anyone sees the pattern, and the queue numbers come from observation rather than from a clipboard count taken twice a day.

Needs: one camera per dock door with the apron in view, plus an outbound endpoint for the marshal's team.

02 · Safety

Pedestrian and vehicle segregation

Painted walkways are respected most of the time, and the exceptions are exactly the moments that hurt people. Near-misses go unreported because nobody wants to write up a colleague, so the site never learns where the real risk is concentrated.

What VisaRoxy does

A segregation agent watches the walkway polygon and raises an event when a vehicle class is inside it for longer than a set threshold. The event names the zone, the duration and the time, and can escalate to a safety lead if nobody acknowledges. It is a record of a condition, not an accusation about a person.

What changes

The site gets a map of where vehicles actually intrude, at what times, and how long they stay. That is the evidence used to justify a barrier, a rerouted traffic plan or a changed delivery schedule — instead of an argument based on impressions.

Needs: overlapping camera coverage of the walkway, and agreement on which escalation path a safety event should take.

03 · Safety and compliance

Blocked egress and housekeeping

Exit routes, fire doors and extinguisher points get used as temporary storage. The obstruction is usually gone by the time anyone inspects, which makes it invisible in the audit record and permanent in practice.

What VisaRoxy does

An egress agent holds a zone over each route and each door swing. An object that stays in the zone past the threshold opens an event and a ticket in the site's own queue, with the clip attached and a timestamp. Closing the ticket requires the zone to be clear, which the agent verifies.

What changes

Obstructions get cleared during the shift that created them, and the audit trail is generated by the work rather than assembled before an inspection. Repeat locations show up in the event history and get a permanent fix instead of another reminder notice.

Needs: a camera with a clear view of each route, and a ticketing destination the site already uses.

04 · Manufacturing

Idle stations and blocked flow

An operator waits on a part, a machine waits on an operator, or a buffer fills and stops the line upstream. None of it shows up in machine data, because the machine is idle rather than faulted.

What VisaRoxy does

A flow agent watches each station and the buffer between stations. It raises an event when a station is unoccupied for longer than its normal cycle, or when a buffer crosses a fill threshold. The rule is scoped to the shift pattern, so planned breaks do not produce events.

What changes

Supervisors see flow losses while the shift can still absorb them, and continuous improvement teams get a per-shift record of where time is being lost rather than a single-day time study. Comparing shifts becomes a query instead of an exercise.

Needs: a camera view of each station and buffer, and the normal cycle times for the rule thresholds.

05 · Security

Out-of-hours perimeter and yard

Overnight coverage means a guard watching a wall of monitors, or nobody at all. Motion alerts fire on foxes, headlights and weather, so the ones that matter get the same treatment as the ones that do not.

What VisaRoxy does

A perimeter agent watches the fence line and the yard with a rule that names the classes it cares about and a schedule that matches the closed hours. It ignores wildlife and lighting changes by condition rather than by sensitivity, and escalates through a defined path when an event is not acknowledged.

What changes

A small team covers more ground, because attention goes to events that already carry a class, a zone and a duration. Overnight incidents arrive with a clip attached, so the morning review starts from the event rather than from eight hours of footage.

Needs: perimeter cameras with usable night performance, and a decision about which hours the rule is live.

06 · Retail and public space

Floor standards and queue length

Presentation standards and checkout queues are managed by walking the floor. Between walks, nobody knows, and the busiest hours are exactly when nobody has time to walk it.

What VisaRoxy does

A floor agent checks defined zones against conditions the store sets: a checkout queue beyond a length for longer than a threshold, an aisle blocked by a cage, a spill left unattended. Events go to the duty manager rather than to a central inbox.

What changes

Queue length becomes something the store can act on during the rush instead of a complaint afterwards. Standards checks stop depending on who walked the floor and when, and the record shows which conditions recur in which part of the store.

Needs: cameras covering the checkout area and the aisles you want checked, and a privacy zones review before the agent is switched on.

One scenario in full

What the dock agent looks like once it is configured.

The same structure as every other agent: cameras assigned, a rule with four parts, an escalation path, and a record of everything it has raised.

Dock Flow Agent

Docks 01–04 · Yard and apron · Owner: Shift operations

Live

Rule

trailer idle > 12 min queue length > 3 trailers during 06:00–22:00

Actions

alert yard marshal notify Shift operations dedupe 10 min

Monday, 06:00–14:00

  • 13:47 Trailer idle 18 min at D-02 Marshal acknowledged · 13:51
  • 11:05 Queue reached 4 trailers at D-03 Acknowledged · 11:09
  • 09:32 Door empty in booked window · D-01 Closed · carrier rescheduled
  • 07:18 Trailer idle 12 min at D-04 Below escalation · cleared

Illustrative interface with sample data.

Why the rule has four parts and not one

A single condition — "trailer idle" — would fire on every legitimate pause in the yard, including the ones caused by a planned carrier slot. The threshold of twelve minutes is drawn from the site's own unloading cycle, so anything shorter than a normal unload is ignored by definition rather than by luck.

The queue condition is separate because it describes a different failure. A single idle trailer is one lane's problem; four queued trailers means the yard has stopped absorbing arrivals, which needs a different response and a different person.

The schedule keeps the agent quiet outside operating hours, when a stationary trailer is the expected state. The deduplication window means one stalled lane produces one event that stays open and updates, rather than an alert every minute until someone moves it.

What the yard marshal actually receives

An alert naming the door, the duration and the rule that matched, with the clip attached. No dashboard to open, no camera to find. Acknowledging it in the alert closes the loop and writes the response time into the event record, which is what makes the weekly review a lookup instead of a reconstruction.

By role

Who picks which scenario first.

The same platform, approached from four different starting points. Most sites begin with the role that already has budget and a named problem.

Operations and shift management

Starts with dock flow, queue length or idle stations, because those scenarios translate directly into throughput and the team already reviews the numbers daily. The first agent is usually chosen from a lane or a station that has been a known constraint for months.

  • Dock and yard flow
  • Idle stations

Safety, EHS and compliance

Starts with segregation and blocked egress, because both already have a written standard the site is expected to meet. An agent turns a standard that is enforced by occasional inspection into one that is observed continuously and evidenced automatically.

  • Pedestrian segregation
  • Blocked egress

Security and loss prevention

Starts with the perimeter or the yard, where the cost of a missed event is highest and the cost of a false one is a wasted walk. Narrow conditions and a defined escalation path matter more here than anywhere else on this page.

  • Perimeter and yard
  • Out-of-hours movement

Continuous improvement

Starts wherever the site already suspects a loss but cannot prove it. The agent's event history becomes the baseline, and the same measure runs across shifts, days and sites without anyone standing in the aisle with a clipboard.

  • Flow losses
  • Standard work

Fit

When a camera is the wrong instrument.

A vision platform is good at some questions and bad at others. Knowing which is which saves a pilot.

VisaRoxy is a good fit when the condition you care about is visible, recurring, and currently caught by a person looking at a screen or walking a route. Walkway breaches, stalled lanes, blocked routes and unattended stations all qualify, because a camera already sees them and a rule can describe them precisely.

It is a poor fit when the answer is not in the image. Counting stock inside closed cartons, measuring weight, reading a temperature, or knowing whether a machine's internal state is healthy all need data the camera does not have. Those belong in the systems that already hold that data, and VisaRoxy is more useful receiving their events than guessing at them.

It is also a poor fit for identity. VisaRoxy is not a face recognition product and is not designed to determine who a person is. Agents work with classes, zones and durations, which is deliberate: an operations and safety record does not need to know names to be useful.

See how this lands in your sector

Name the scenario. We will configure it live.

Tell us which of the six matches your site and we will walk through the agent configuration on footage like yours — thresholds, schedule, escalation and all.

Book a live walkthrough Check the data handling