# MOBOTIX CLOUD - Real-time Video Monitoring and Insight

**URL:** <https://community.mobotix.com/t/mobotix-cloud-real-time-video-monitoring-and-insight/7111>\
**Category:** MOBOTIX CLOUD - Best Practises\
**Created:** [July 26, 2023, 8:04am UTC](https://community.mobotix.com/t/mobotix-cloud-real-time-video-monitoring-and-insight/7111 "2023-07-26T08:04:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mx-NicoG](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@Mx-NicoG](https://community.mobotix.com/u/Mx-NicoG)\
**Post date:** [July 26, 2023, 8:04am UTC](https://community.mobotix.com/t/mobotix-cloud-real-time-video-monitoring-and-insight/7111/1 "2023-07-26T08:04:58Z")

</div>

**Introduction**  
The **MOBOTIX VMS analytics** can be used for both real-time monitoring and to mine insights from historic video. Real-time monitoring detects objects, people and movements as they occur in the environment. Mobotix offers **five** different analytics; **People Counting** , **Line Crossing** , **Intrusion**  **Detection** , **Loitering** , and **Camera Tampering**.

Analytics are available for any camera connected to a Bridge (except analog cameras  
on hybrid Bridges). All **five** analytics can be activated at the **same time** (costs  
associated with each). It’s important to note that the stream used for analytics is MJPEG  
(secondary stream) and 12fps is recommended for best results.

Analytics are available to **all Editions** of the VMS (Standard, Professional, Enterprise)

### 

**Background**  
Each analytic serves its own purpose and is described below:

1. **Counting** : Used to count objects crossing a line in either direction. For the highest accuracy counting people, use a dedicated camera mounted with a top-down view in which people remain the same size as they travel through the image. For the object to be counted, at least **50%** of it must **cross the line** and you can only **configure one line** per camera.

2. **Line Crossing** : When an **object**  **crosses** a specified **line** in the selected direction, an **alert** can be **generated**. Just like with ‘Counting’, **50%** of the object must **cross the line** and only **one line can be configured** per camera.

3. **Intrusion Detection** : If an **object enters a forbidden area** , an **alert** can be **generated**. There’s **no limitation** to **how many areas** can be defined in the camera view.

4. **Loitering** : If an **object remains** in a defined region **longer than a specified time** (between 1 second and 2 minutes), an **alert** can be **generated**. Just like with ‘Intrusion Detection’, there are **no limits** on the **number of areas** that can be defined per camera.

5. **Tampering** : Tampering detection is used to **generate an alert** when someone is **trying to block** the camera’s **view** or the **image is greatly altered**.

### 

**Functionality**  
Analytics **have to be configured on each camera** and the menu can be found within the camera settings window as shown below:

 ![Analytics 1](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/8/8987bfe943ccf0298f3f79099cfdd9afd76734c9.png)

From within this menu, activate any of the **five analytics** that the MOBOTIX CLOUD VMS provides. If required, activate all analytics for each camera.

 ![Analytics 2](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/3/3beff67a2049a154f09a767ea038dc3a82becf60.png)

When activating Analytics, it’s important to select and check the following:

- ● Resolution menu → Preview Video → Quality → set to Analytics (normally, this is done  
automatically). This adjusts from 8fps to the preview stream, which uses 12fps. By clicking on  
one analytic, it becomes enabled and new tabs appear depending on how many  
analytics are enabled (remember, each analytic carries a subscription cost).

 ![Analytics 3](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/e/e8393cfdfa0acb1823e8d0759ed8850c0b54992e.png)

Separate tabs allow the user to configure each Analytic.

For all Analytics except “Tampering,” it’s important to note that the configuration of the “Object Detection Settings” will be applied for the camera view, meaning that the minimum and maximum size for the object detection will be the same for **ALL** Analytics being utilized.

 ![Analytics 4](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/b/be02acc2bcae7163815fffe151012452a13d50f0.png)

### 

**Couting**  
Draw a line on the camera view and **choose the direction** that the object will enter. Only draw **one line per camera**. A top-down view for the camera is also necessary to ensure the best results, as shown in the picture below.

- **Note** : For best results, place the line in the center of the field of view and **allow as much space as possible to either side**. A proper configuration should allow the analytic to identify an object fully in view and track its motion clearly over the line. **Avoid** placing analytic regions or lines **near the edge of view**.

 ![Analytics couting](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/8/8950d2d91e6780b6bc76d77f6a11f037617f8f8b.png)

Full statistics are available from analytic graphing which can be found on the Dashboard next to the camera icons and as seen below:

 ![Analytics 6](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/e/e685f3776021024907b1f84644b26576b487dd7f.png)

The data can be exported in several formats (XLS, CSV, PDF, JPEG, etc.), are **available** via the Mobotix Networks API, and can be **extracted** to be analyzed at a later date or injected into **3rd party systems** to be combined with additional data for better management of business KPIs, for example.

**Line Crossing**  
Configuration is similar to the “Counting” analytic. Draw a line in the view to detect objects crossing it. Remember, only **one line per camera** and 50% of the object must cross it to be detected.

- **Note** : It’s best to draw the line in the **middle of the view** so the system can detect the object easier. **Avoid** putting the line **near the edge of the camera view.**

 ![Analytics Line crossing](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/f/f72921bbaaa52743fda6f70454660fe296cb640c.png)

**Intrusion Detection**  
Configuration is done by creating areas in the camera view. There’s **no limit** to **how many**  **areas** can be created but careful consideration should be used when implementing.

- **Note** : Try to **avoid** creating areas **at the edge of the camera view** and if possible, try extending the area so the object can be caught before going out of the area and view.

 ![Analytics intrusion](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/a/a14a1f6d0caca8b65aa5e60beb07b27b40bf0df1.png)

In this configuration, any person that enters the room will **trigger an alert**. As can be seen from the example above, options for **where to place the area** within the camera view **may be limited**.

**Loitering**  
Configuration is similar to “Intrusion Detection” where areas are drawn within the camera view. However, in this case the **alert will be triggered only** when an **object stays in an area longer than the time specified**. As can be seen from the example below, there is a parameter called “Dwell time” and any dwell time can be chosen (from 1 second up to 2 minutes).

- **Note** : Try to create an **area** that **covers a bit more than what is required** to get the **best results** , especially with people as there tends to be a lot of movement.

 ![Analytics Loitering](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/0/097d98e6c726e93ee96b1e08340b52b1285bddd9.png)

**Camer Tampering**  
For camera tampering analytics, sensitivity is the only parameter to change depending on how you want alerts to be sent when there are changes to the initial view.

- **Note:**  **Leave the parameter as it is** to perform initial testing and **adjust as necessary** depending on the **alert level** you **require**.

 ![Analytics 10](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/8/8db63d683f31508cb298cd69e70a2b5e2f9f5f9a.png)

### 

**Usage**  
There are a variety of uses for MOBOTIX CLOUD VMS analytics. Knowing that existing IP cameras already installed at a customer site can be used, there is no need for a large up-front capital expenditure on cameras to optimize operations through the use of business analytics. Additionally, this helps reduce bandwidth usage as the system can be implemented to record on Event Only if desired.

1. **Counting**

- Counting people is a useful tool and provides great data for every customer looking to better track quantities of people at a location. Retail customers utilize People Counting to link entrances with sales using the MOBOTIX CLOUD VMS API by injecting data **into 3rd party solutions** to **better track KPIs**.
- Covid-19 has forced businesses to control their occupancy levels. Having such data easily available can be **crucial to compliance and regulatory operations**.
- **Transit Flow** helps determine how people move around in a location. Analytics can be used to determine where to **focus resources**. For example, in regards to where **security personnel** or **housekeeping should focus**.
- Receive **notifications** when workforce **arrives on-site** and for **departures** as well.
- **Customer flows** are also **important to understand** in the Transportation sector.

1. **Line Crossing**

- Line Crossing can be used **to track vehicles** as they **enter** and **exit** designated areas, or for **situational awareness** when **monitoring crowds** or **temporarily restricted areas**.
- Line Crossing **tracks** an **object’s movement** over a **specified line** and results in an **alert and event recording** so that **notifications** always occur when a person or object crosses a line.
- More focused on security, Line Crossing analytics will help to detect in **real-time** when an object is **crossing a restricted threshold** and can provide **alerts** to this activity **if desired.**

1. **Intrusion Detection**  
Using Areas, Intrusion Detection allows for the monitoring of certain locations within a camera’s view and for various purposes such as the following:

- **Protecting** an **asset** in a specific location
- Parking spaces
- Restricted area bypassing a door (this is an example of why an area can be more useful than a line)
- **Detection** of people **near a fence** or going **over a fence**
- **Setup**  **different levels of alerts** with different areas.

1. **Loitering**  
Just like with Intrusion Detection, we can use several areas in camera views to monitor different places. Loitering can be used to:

- **Help** detect **suspicious behavior** near an **office**. For example, **people hanging out** or **standing in certain areas**
- **Identify** cars that have been **parked longer than expected** in a **particular space** or **location**
- **Identify** people **lingering in a certain area** when they **shouldn’t be**
- **Help detect**  **long wait lines/queues** as they **grow** so that **actions can be taken** to **improve the situation** (cashier, banks, lobby, etc.)

1. **Camera Tampering**  
Camera Tampering **allows for the monitoring of a camera view** to help determine if it is **blocked** or if the **view changes**. This is important on specific, high profile cameras **when monitoring important assets** or **areas** and for ensuring that the cameras have the **correct view** as installed.