How do I build my own solution? (Builder)

Build the best solution for your use-case

Besides using pre-definded Solutions, we provide you with the Builder. You can combine all different Models and Types to mirror your own use-case.


The model reflects the engine the Perception Box works with.

Swarm Analytics uses the metric system for measurements. We appreciate there are other length measurements out there. Most common, besides metres are surely feet: 1m = 3,28 ft



Camera height

Distance of camera and objects

Person Full Body

full body of people

1m - 3m

1m - 10m

Traffic Standard

classes of dynamic road users

3m - 6m

max. 25m

Traffic Large

classes of static road users

6m - 15m

10m - 35m

Traffic Fisheye

classes of road users

2,5m - 4m

max. 25m

Person Head

head of people

1m - 3m

1m - 10m

While detecting and tracking people, we never do any face recognition. There will be no sensitive personal information being processed at all. Do not hesitate to contact us with any doubts or questions around this topic.





Region of Interest. Used for counting objects in this specfic region.


Counting Line. Everytime the object's center passes the line, it will be counted.


Virtual Door. Virtual door a more complex than the CLs and designed for counting at entrances.


Zones are used for counting objects appearing in one zone, moving to another.

Heat Maps

Heatmaps track objects over time. Heatmap mode will disable all other types.

Creating a solution

To create your own solution, select a model for your solution and then place your type (or select heatmap mode).

When a type is active, left-click an hold the white circles to move the single corner points. You can create any tetragon (four-sided polygon). To move the entire type, left-click and hold anywhere on the type.

ROI - Region of Interest

ROIs are used for counting objects. This type also includes a parameter called "dwellTime", which tells you how long the object has been in this region. You do have two trigger values to choose from. Either a time intervall (of 10 seconds) or an occupancy change. Typically you would use the time intervall to regularely check a region for a total number of objects in it, while you would use the occupancy change e.g. for single parking spaces.

CL - Counting Line

Counting Lines are best for top-down views, as the center of the object needs to hit and pass the line. You may toggle IN and OUT at any time.

VD - Virtual Doors

They cover the need of having 3D counting lines. The object needs either to move into the field and then vanish or appear within the field and move out. Objects appearing and disappearing within the field, as well as objects passing the field are not counted.

OD Zones

OD stands for "Origin - Destination". You will need at least two of them in your solution. Counts will be generated, if an object appears first in OD 1 and then in OD 2. This is useful, if you want to know, where objects are moving to.


Sample Solution: Intersection

This is how a solution for an intersection could look like.

  • The CLs count all people entering the intersection from South-East and South-West

  • The VD covers the store entry in the North-West

  • In the center the ROI checks the occupancy. If this part of the intersection is occupied longer, there is a high chance, something is wrong in this intersection (traffic jam, accident, etc.)

  • Finally the ODs track the traffic. E.g.: How many cars coming from west driving north