Axis Object Analytics (AOA) is a suite of analytics for certain enabled cameras from Axis Communications that supports detecting people and vehicles, as well as supporting different scenarios to trigger alerts. This article will cover the use of Scenarios and how to use that to enhance the Arcules experience with Rules and with Status Displays.

The best resource for determining if your camera is compatible is to reference the Axis website: https://www.axis.com/products/axis-object-analytics#compatible-products

The Axis camera you are trying to enable Axis Object Analytics on, must have a firmware of 10.2.x or 10.3.x or higher.

Now that the AXIS Object Analytics App is running on the camera, Scenarios must be created for the events you want Arcules Rules to trigger on.

This is a list of currently supported Axis Object Analytics Scenarios

When you set up an Object in area scenario, the application detects objects that move inside a defined area. The defined area is called an include area.

When you set up a Line crossing scenario, the application detects objects that cross a virtually defined line.

With the scenario Time in area, you can set a time limit for how long an object is allowed to stay inside the include area before the application triggers an action. When an object enters the include area, the time counter starts. If the object leaves the include area before the set time limit is reached, the counter resets. It’s the object’s point of detection that must be inside the include area for the counter to keep counting. The time in area feature is suitable for areas where humans or vehicles are only supposed to stay for a short while, like tunnels or school yards after hours.

With the Crossline counting scenario, the application detects and counts the objects that cross the virtual line, and you can see the accumulated count in a table.

When you set up an Occupancy in area scenario, the application estimates how many objects that are inside the include area at any given time. An object counter displays the estimated number of objects currently in the include area. When an object enters or leaves the area, the object counter adjusts. Occupancy in area is suitable for areas where you would want to get an estimated count of one or several object types, such as parking lots.

When you select a Motion in area scenario, the application doesn’t classify objects. Instead, it detects any object that moves in the scene. It can, for example, be animals, swaying foliage, flags, or shadows. To ignore small objects, swaying objects, or objects that only appear for a short time, you can use filters

When you select a Motion line crossing scenario, the application doesn’t classify objects. Instead, it detects any object that crosses the virtual line. To ignore small objects or objects that only appear for a short time, you can use filters.

Axis has provided documentation for best practices in configuring each of the above documented Scenarios here: https://help.axis.com/en-us/axis-object-analytics#get-started

If the camera has not been added in Arcules, please refer to this guide for step-by-step instructions on adding a camera.

For an overview of the general Rules setup for Arcules, please review this article:

https://help.arcules.com/en/articles/2042893-rules

You can either use the shortcut on the Analytics tab to generate the rule for he specific Scenario result as shown below

or, you can go to the Rules page in the portal and manually create the rule per the article referenced above.

There are generally two types of triggers you can use, each applies to different scenario outputs.

This trigger type is used by the Scenario types that perform detection as listed below:

This supports triggering on the following values for the sensor

In the below shown example, this is a rule set to trigger on the AOA Object Detect Scenario (Object in Area) where the specified object type(s) have been detected within the region configured on the camera.

This trigger type is used by the Scenario types that perform counting as listed below:

This supports the following operators for evaluation of the current count

In the below shown example, this is a rule set to trigger on the AOA Down the Block Scenario (Crossline Counting) where there are more than 5 people detected

You can view the current values for the configured Scenarios from the Devices tab. Once you select the desired camera, you can click on the Status tab, and see the current status for the scenario sensors/counts.