Rule Engine
Here you can find details on how to use the Rule Engine for your customized Scenario Configuration
Last updated
Here you can find details on how to use the Rule Engine for your customized Scenario Configuration
Last updated
With the Rule Engine, you can customize your event triggers. Reducing Big Data to relevant data is possible with just a few clicks: From simple adjustments to only get counts for one direction of the Counting Line to more complex rules to monitor a Region of Interest status when a vehicle crosses a Counting Line.
For rule creation, an event trigger has to be chosen to attach it to. Depending on the type of the event trigger, options are available to set flexible filter conditions.
Name your rule - This name is used to create widgets in Data Analytics, and will be part of the event you receive via MQTT.
Choose the event trigger the rule should be based on Any of your already configured event triggers can be chosen. In case Origin/Destination is selected, all configured zones are used automatically.
You have the option to choose from predefined templates or your individual rules, which you have tagged as your templates yourself. --> See later in this section how to tag a rule as a template.
Set your subconditions With subconditions, you can filter down to only gather the relevant data for this rule. The parameter options for the subconditions are dependent on the chosen event trigger.
For those conditions combined via AND, all conditions need to be fulfilled. In the example above, events are sent, only if a bicycle or person is crossing the Counting Line in the IN direction.
You can create combined conditions for RoI and CL. When they are chosen as an event trigger, the option to add another condition appears below. This subcondition needs to be based on a second RoI or CL. They will then be combined by an AND connection.
Combined rules trigger an event only in case an object is crossing the CL and the rule of the additional CL or RoI is met.
In the example below, the rule sends an event in case a car, bus, truck or motorbike is crossing the speed line at more than 50 km/h and at the same time a person which is longer than 5 sec in the RoI.
Any created rule can be tagged as a template. This provides the option to use the same logic on any camera stream within the same Control Center.
If you are deleting a rule that is tagged as a template, the template will be removed. In case a rule is created on a trigger (e.g.: CL) and the trigger gets deleted, the rule will disappear as well.
After creating a rule, the Scenario Configuration of the camera needs to be saved in order that the rule will be applied accordingly.
In the actions section, you can click on the tag symbol in order to save the rule as a template. If the rule is tagged as such, the symbol will be highlighted .
Rules can be edited by clicking on the edit symbol . This action will open the edit mode of the rule. By clicking on the bin symbol you can delete a rule. A confirmation of the deletion is required to finalize the action.
