A camera sees, but it does not know when to raise the alarm. A scenario decides that: "where, what happens, when, and what do we do". We turn a rule you describe in your own words into a working scenario.
What a scenario is
Every scenario has three parts: the condition (what must happen in the picture), the time and place (which camera, which zone, which hours) and the reaction (who is notified, what is triggered). For example: "if a person enters the warehouse back-door zone between 22:00 and 06:00 — send security a WhatsApp alert with a frame".
Scenarios we write
Zone entry
A person, vehicle or machine entering a restricted area, or an area closed at certain hours.
Line crossing and counting
How many pass an entrance and in which direction; people entering and leaving a shop.
Loitering
A person or vehicle staying longer than allowed — for example in a no-parking area.
Left or removed objects
A bag or box left behind, or an item taken from its place.
Queue and occupancy
People waiting at a till, the occupancy limit of a room or car park.
Door and zone state
A door left open at night, movement in an area that should be shut.
Work safety
Missing protective clothing, entry into a hazard zone, approaching machinery.
Time measurement
Measuring service or waiting time and reporting the average.
What the reaction can be
- A WhatsApp, push or email alert — with the event frame attached
- A siren, light or barrier triggered (through a relay)
- An event log and daily or monthly reports
- A link to your CRM, stock system or alarm monitoring
- The responsible person follows your duty roster; with no answer it passes to the next one
How it works
If the camera has analytics of its own, we read its events through a standard interface. If not, the video stream is processed on a local computer at your site — the footage does not leave the premises. For ready-made sector scenarios we have camera analytics; this page is for your own custom rule.
Stated plainly: video analysis is not 100% accurate. The result depends on camera position and angle, lighting, distance and image quality; we test and tune each scenario on real footage, but occasionally there will be a false alarm or a missed event. The camera detects a person, it does not identify who they are — identifying individuals is a separate matter that requires consent. These scenarios do not replace a fire alarm or a guarding service. Cameras must be placed in line with the rules on recording people, with warning signs displayed.
How we work
- Writing the requirement. You describe the scenario in your own words — no technical language needed.
- Checking the cameras. Whether position, angle, light and image quality are enough for your rule — we tell you in writing.
- Writing the scenario. Zone, time, condition and reaction are defined precisely.
- Testing. Recorded footage first, then a live pilot — false alarms are reduced.
- Support. New scenarios, rule changes and a monthly report.
Frequently asked questions
Are our existing cameras suitable?
Often yes. Position, angle, lighting and image quality must fit your rule. We check this at the start and tell you in writing; new cameras are recommended only when really needed.
Can we change the scenario ourselves?
Simple parameters such as hours, days and who gets alerted are changed from the panel. For a new condition or zone, you contact us.
Will there be false alarms?
They cannot be removed entirely. We reduce them during testing on real footage, and afterwards the report shows repeated false alarms so the rule can be refined.
Does the footage leave our premises?
Processing can run on a local computer at your site, which is the standard route; footage is not sent to a cloud. Only the frame you choose is attached to an alert.
Can a camera recognise people?
The scenarios detect the presence, movement and number of people, not who they are. Identifying individuals is biometric data and needs separate consent and rules.
