Perimeter Security Analytics Public preview

perimeter security analytics is the latest offering for iris+ customers, providing a completely new detection pipeline for customers optimized for detecting trespassing and perimeter breaches at long distances in challenging conditions the guide below will help you set up perimeter security for your needs this version of perimeter security is a public preview release this means we consider the functionality stable and ready to use, but there may still be some rough edges please note that our guarantees outlined at irisity service level agreement do not apply to preview functionality if you're interested in participating, please submit a support request or reach out to our support team at support\@irisity com before you begin be sure to get in touch with sales or support to ensure that you have the preview feature, the perimeter security module, enabled on your customer account for this preview to run optimally, you will need at least one healthy and stable edge device this typically includes no ongoing issues on the edge device such as high ram consumption, high cpu consumption, and/or low frame rate support will assist in picking and choosing the best device(s) as a candidate for this preview note that the camera type supported for this version of perimeter security is only for ccd cameras this means that this feature currently does not support fisheye cameras thermal cameras 360 cameras ensure the edge device is up to date the new perimeter security analytics requires that the edge device running the camera has been updated to a version released may 13, 2025, or later note that this edge release is also in public preview we recommend reaching out to support to update your edge device for compatibility with the perimeter security preview set up perimeter security in iris+ because this is a preview of perimeter security, we highly recommend not running a perimeter security rule on a camera with standard rules on an edge device in production this preview may cause unexpected behaviors that might result in poor performance or unintended results just like any rule in iris+, setting up perimeter security will require you to access a camera from the camera tree going to the administration module and selecting the camera from the camera tree will then display the new perimeter security option in the nested tabs next to the dashboard tab you can now see that the new perimeter security module is available in the system in the perimeter security module, you can create, edit, and delete perimeter security rules note that this module is not attached to regular rules, so you can only create and adjust perimeter security rules from this module create a new rule by clicking on the +add a new rule button when creating a new perimeter security rule, both detection object types, person and vehicle, will be selected you can choose to select both or one when creating the rule in the middle is the live camera view, which allows you to view the camera stream and adjust the area of interest this area of interest behaves and applies the same way as you would with alarm zones from other rules on the right panel are rule settings rule name the name of the perimeter security rule detection options the mode of when the rule should be active always active the rule is always on and triggers events when the subject is detected deactivated the rule is inactive it exists but it will not trigger any events when the subject is detected at any time managed by a schedule the rule is only active based on the time ranges set by a schedule if there are no schedules available, no events will be generated if this option is selected minimum time between events this is a cooldown time, which sets the minimum between each motion detected event triggered by this rule generally, the more you lower the cooldown threshold, the more events you will generate because perimeter security only supports detecting people and vehicles, the cooldown threshold set in this rule will not impact the time in between events generated from other standard rules note that the calibration functionality will only work with standard rules alarm options select event severity level and area of interest color the area of interest acts like the alarm zone from other types of rules outgoing id the relevant integration id to send events to this open beta supports only one integration id at a time create image creates an image of the intrusion activity that was detected create clip create a video clip of the intrusion activity that was detected once you click save, the perimeter security rule will be created and shown in the module rule of thumb for alarm frequency the field option minimum time between events dictates how many true alarm events are generated at every interval in perimeter security, the default is set to 5 seconds this means that when the object is detected in an alarm zone, it will generate an alarm on the detection every 5 seconds typically the minimum time between events should be set reasonably where an alarm generates when an object moves through an alarm zone in some circumstances, this can generate too many true alarms, which can flood the monitor view with too many of the same alarms in the example above, you will see that each video frame with an intrusion will generate an alarm if the cooldown is set to 3 seconds this can potentially be problematic, as the monitor tab will show an influx of the same true alarms repeatedly if there is a preference to reduce the number of true alarms, tweaking the cooldown threshold could reduce this concern the example above shows how the alarms are now generated when the cooldown is set to 9 seconds instead of 3 seconds while the intrusion activity is still detected in each frame, the alarm cooldown prevents the system from generating any additional alarms in between that is less than 9 seconds so what's the best cooldown for my site? different cases can benefit from different cooldown settings here are some examples the site is a busy space with higher levels of human and vehicle traffic because the alarm zone of this site is expected to have higher levels of activities normally, it may be best to slowly try and bring up the cooldown threshold to prevent an influx of true alarms generated repeatedly the site is a quiet space that tends to not have people or vehicles entering or exiting because the alarm zone of this site expects very little activity, it is best to keep the cooldown threshold as low as possible so the intrusion will properly track and always generate an alarm in a timely manner we recommend consulting with our support to best help you determine what might be the best cooldown time to set for your monitoring needs monitoring for perimeter security events once the perimeter security rule is active, the rule will wait for a person or vehicle to trigger an event on the monitoring site when the event is generated, it will display and show in the monitor module, the same way as other rules normally would in this view, you can still classify and handle events like you normally would, setting events to either true or false clicking on the rule title of a perimeter security rule will not take you to the rules tab but to the same perimeter security rule page from earlier handling perimeter security events clicking on the event will show you the details of the event this event window shows the details of the event that has occurred it's divided into three detailed tabs event shows the video clip of the event that has occurred live video shows the live video details show the details of the event, which include information such as status account name folder name rule name rule type timestamp of the event all relevant ids that the event is generated and stored with technical detail, which shows the log of the event in a json output there are additional buttons below that allow the user to flag the event as true or false additionally, the user can skip over to the next alarm in this view report events from perimeter security lastly, perimeter security events can be exported with other alarm events from the reports module you can find the perimeter security events in the reports listed as perimeter security moving in an area public preview limitations since this is an open beta version of perimeter security, there are some known limitations to this version that should be noted while we work on them perimeter security events can only integrate with one integration id at a time it currently does not support multi id functionalities reporting currently does not show the severity of the perimeter security event we recommend running 7 cameras on a single edge device edge 10, edge 220, and edge 320 for a more stable experience perimeter security only supports detecting people and vehicles as objects, meaning that setting this rule against other classes of objects will not generate alarms on them attempting to change camera mode while running perimeter security may cause the camera and some services to restart there is currently no option for a test alarm in this version of perimeter security, the functionality will only show and work for legacy rules no anonymization offering is available yet for this version of perimeter security if you attempt to use anonymization on cameras with mixed perimeter security and legacy rules, anonymization will also not work any camera with perimeter security as a rule may exhibit dropped frames in live view it is not recommended to run both perimeter security and legacy motion detection rules on a single camera, but if you must, we recommend limiting it to having one camera running it on an edge device note that the calibration functionality will only work with the legacy rules bounding boxes may behave unexpectedly in certain event integrations for customers who only operate on the core, they will still see the option to convert their rules from moving in an area to perimeter security, but will be highly advised against doing so unless they have the proper edge version the team at irisity is currently working to resolve the limitations before officially launching this module to production