Skip to content
Focient

Enterprise and commercial · 18:30

Your sites, after hours

Motion alerts for anything that moves.

Name a zone, then set a time-in-zone rule and a schedule.

An example alert rule, as the rule editor shows it. It is an event rule for camera 03, the loading dock. It matches events tagged after hours and door, and carries a plain-language check: Confirm the side door is open. The data is fictional.

Screens on this page show fictional data.

At 20:15

An alert, marked useful

Each alert can be marked useful or not by an operator.

An example event, as the event detail shows it: a snapshot of the side door at the loading dock at 02:47:13, marked Verified, the written description that the rule's check read, and a question asking whether the alert was useful, with Useful and Not useful buttons. The data is fictional. In this example the operator has marked the alert Useful.

At 22:05

Unusual for this camera

Once a camera has enough history, deviations are flagged.

The patterns part of the same example daily report: under Patterns, what repeated for a camera, a day of the week and an hour, and under Anomalies, where a camera departed from its usual. The data is fictional.

At 23:10

The day's report

It counts the day's events and alerts.

An example daily report: the period, the day's event and alert counts, a summary that names cameras, highlights, the peak hour and a list of the most significant events. The data is fictional.

What goes in the report

A report is written for your organisation once a day, automatically, and it sums up highlights, patterns and anomalies.

The reports page of an example organisation: three reports, newest first. Two are daily reports and one is a custom report that was run on demand for a week. Each shows its type, its period, its title, its event and alert counts and the day it was generated. The data is fictional.
  • On demand

    You can also run a report on demand, for any period up to 31 days.

  • Patterns

    Each camera's baseline is kept by day of week and hour, and repeats are grouped.

  • Cases

    A case holds a timeline across cameras.

How reports are built

Rules and alerts at each site

Alerts go out by email, by WhatsApp or to a system your administrator connects.

The alert rules page of an example organisation. One suggested rule waits for review, with the reason it was suggested. Below it are three rules, each with its scope and filters and a quality line that counts the alerts operators agreed with, disagreed with and the alerts dispatched. No percentage is shown. The data is fictional.
  • Suggested rules

    Suggested rules wait for review.

  • Quality score

    Every rule keeps a quality score.

  • What a rule says

    A rule or a label describes what happened on camera.

How alerts are set up

Questions operations teams ask

Do we need new cameras?

Focient works with the RTSP cameras you already run, with no new hardware, and a connection test runs before a camera is saved.

Does it replace our recording system?

Focient is a video intelligence platform, and it does not replace a recording system.

How are people on camera treated?

How people on camera are treated is set out on the Trust page.

Where does it run?

Questions about deployment, networks and data flow are answered in the first conversation, under NDA.

Talk to us about your sites

Tell us what each site checks overnight and who reads the result.

Request a demo

We show you the console on recorded footage.