The platform allows for the configuration of multiple alerts to ensure timely notifications if any cameras from a customer's account go offline. Two options are available, either of which can be used individually or together, depending on the specific needs. Option 1: Daily Report Alert A Daily Report Alert is generated once every 24 hours and includes information about all cameras that were offline during the past 24-hour period. The Daily Report can be activated at either the Integrator level or the Customer level, depending on which user should receive it. If the alert is intended for a user at the Customer level, it should be activated through the Customer Alerts Menu. For a user at the Integrator level (such as the integrator owner or a manager), the Daily Report should be activated from the Integrator level Alerts Menu. When configuring the report at the Integrator level, it is possible to select one or multiple customers to be included in the report. Option 2: System Events Alert If receiving a daily update is insufficient and there is a need for more immediate notifications regarding specific cameras, a System Events Alert can be configured. This alert provides real-time notifications as issues arise. Similar to the Daily Report, the System Events Alert can be set up at either the Integrator or Customer level, depending on who should receive the notification. The main difference between the two options is that the System Events Alert allows for the selection of specific cameras and provides more flexibility in the timing of the alerts.

To delete a Customer or Integrator along with all associated cameras, users, alerts, and archives, access the Account Profile menu for the relevant customer and select Delete. Confirm the deletion in the pop-up window to complete the process. This procedure is the same regardless of the customer's size or number of locations. Warning: Deleting a Customer or Integrator is permanent and cannot be undone. Once completed, all archives for the customer’s cameras will be permanently deleted and cannot be recovered. Note: Deleting an Integrator account will also delete all associated customers and their cameras.

To delete a site from a multi-site customer, each camera and user associated with that site must be deleted manually. Step 1 Delete cameras from the site to be removed. Navigate to Customers from the main menu and select the Cameras tab. Here, cameras can be sorted by column headers or searched using a unique site identifier in the Camera name search bar. Step 2 Click on the camera name to open its properties and navigate to the Delete tab. In the provided field, type "Delete" and click the Delete button to remove the camera from the system. Step 3 (Optional) If necessary, delete users associated with the site being deleted. Open the Users tab for the customer, sort the table, or search for users using the column headers. To delete a user, click on their name in the table, navigate to the Delete tab, and click Delete to remove the user. Note: Deleting users is optional, but doing so can help keep the customer account organized. Even if users are not deleted, they will no longer have access to any cameras, as those cameras are now deleted. Step 4 (Optional) Delete any roles associated with this site. Open the Roles menu and either sort the list or search for role-specific information in the column headers. Ensure that the role is not assigned to any users; if it is, click on the user's name in the right column to unassign them, or click Deselect All to remove all users from the role. Next, click the Delete tab and press Delete to remove the role from the system. Step 5 (Optional) Delete any alerts or webhooks created for the site. To remove alerts, open the Alerts menu, sort or search for the alerts linked to the site. Click on the alert name, navigate to the Delete tab, and click Delete to remove the alert from the system.

Prerequisites This Standard Operating Procedure applies if the following conditions are met: The customer has multiple locations, or plans to add more in the future. The number of cameras can vary from one per location to thousands per location. Security guard monitoring services are not provided or planned to be provided for this customer. The customer does not intend to resell the service in the future. The customer may have a mix of equipment, including different brands of IP cameras, NVRs, and other H.264 video streaming devices. The customer requires full separation of their cameras and users from other customers. Step 1: Create a New Customer Log into the Admin portal using the primary integrator account or an operational manager account. After logging in, verify that "Integrator" is displayed in the top-right corner above the username. If "Customer" is displayed, the wrong user level has been used. Navigate to the Customers menu and click Add to start the process of creating a new customer. Step 2: Integrate Customer Cameras Depending on the type of equipment the customer has, different integration procedures must be followed: ONVIF-Compliant Cameras: If the camera is not from the supported P&P list but is ONVIF-compliant, it can be added via the AVYCON Cloud bridge or using the ONVIF option, which requires configuring port forwarding on the router. Non-ONVIF Cameras: For devices that are not ONVIF-compliant, the Generic option can be used, which only requires the RTSP stream URL from the device. However, this method does not allow for device control from the Admin portal or activation of server-side analytics. It's important to include a unique identifier in the camera name to differentiate cameras across customer sites. This identifier helps in sorting the camera list to show only cameras from a specific site, improving organization and ease of management. Step 3: Configure Event Detection Determine the appropriate event detectors for each camera and whether server-side analytics are required. For ONVIF-compliant detectors, go to the Analytics tab of each camera to configure parameters such as areas, lines, sensitivity, etc. Test the configuration for a few hours or days to minimize false positives while ensuring that critical events are not missed. It is recommended to slightly over-sensitize cameras to avoid missing important events, but extreme sensitivity should be avoided, as this can generate continuous events and make it difficult to identify distinct incidents. To filter out false events, enable server-side analytics. For guidance on configuring these, consult the relevant documentation. Step 4: Add Additional Users Create users as needed. Multiple users can be assigned to a single location or multiple locations. Users can be created at the beginning of the service or added later as the customer expands. Step 5: Create Roles Roles must be created to manage access levels for different users. An unlimited number of roles can be configured to control access to video streams. Each user can be assigned to multiple roles, and each role can be assigned to multiple users. It is recommended to create separate roles for each location to simplify access management. This ensures that groups of users can easily be granted access to cameras from a specific location. Step 6: Create Alerts To leverage the full capabilities of the cloud, create sensor alerts for monitoring. This enables real-time notifications based on pre-set conditions, ensuring prompt action when events occur. Step 7: Create Layouts and Layout Categories To streamline the process for users and guards, create Navigation Layouts and Categories. Layouts can be designed to accommodate a specific number of camera cells, though performance may vary depending on the device and internet connection. For optimal performance, layouts with up to 9 cameras can generally be viewed on any device. For larger layouts, a dedicated graphics card and high-speed internet connection are required. Select the layout design based on the desired number of camera cells and assign cameras to the appropriate cells. Layouts can be created for individual locations or combined to meet monitoring needs. To organize layouts in the Navigation menu, create categories and sub-categories. For instance, a category could represent a region, and sub-categories could represent specific customer sites. Layouts can be dragged and dropped into these categories for easy access. Step 8: Provide Training to End-Users While the system is designed to be intuitive, some users may benefit from additional guidance to fully understand how to navigate the video portal. Many users may not be aware of all the features available, which could lead to inefficiency in reviewing archives or waiting for clips to download. It is recommended to walk through the system with each new customer, focusing on the tools most relevant to their needs. Understanding how each user intends to use the system will help determine which features to emphasize: For users who only need occasional camera monitoring (e.g., while on vacation), demonstrate how to use the mobile app and review footage received through alerts. For users focused on incident investigation, highlight features such as thumbnail grids, event menus, timeline navigation, and clip creation/download options.

Prerequisites This Standard Operating Procedure applies if the following conditions are met: The customer has only one location and does not intend to add more locations in the future. The number of cameras that can be connected is flexible. Security guard monitoring services are not provided or planned to be offered to the customer in the future. The customer does not plan to resell the service in the future. The customer has a mix of equipment, including different brands of IP cameras, NVRs, and other H.264 video streaming devices. The customer requires that their cameras and users be fully separated from those of other customers. Step 1: Create a New Customer Log into the Admin portal using the main integrator account or an operational manager account. Once logged in, "Integrator" should appear in the top-right corner, above the username. If "Customer" is displayed, the wrong user level has been selected. Navigate to the Customers menu and click on the Add button to begin creating a new customer. Step 2: Integrate Customer Cameras The integration procedure will vary based on the customer's equipment: ONVIF-Compliant Cameras: If the camera is ONVIF-compliant but not listed in the supported P&P devices, it can be integrated via the Raspberry Pi bridge. Alternatively, ONVIF-compliant cameras can be added directly using the ONVIF option, though this will require setting up port forwarding rules on the router. Non-ONVIF Cameras: If the camera is not ONVIF-compliant, use the **Generic option, which requires only the RTSP stream URL from the device. However, this option does not allow control of the device from the Admin portal or enable server-side analytics. Step 3: Configure Event Detection Determine which type of event detector or detectors will be most suitable for each camera and whether server-side analytics are necessary. For ONVIF-compliant detectors, go to the **Analytics** tab of the camera to adjust settings like area, lines, sensitivity, and other parameters that will help detect events. Test the configuration for several hours or days, depending on activity, and make adjustments to minimize false positives while ensuring no important events are missed. It is generally recommended to err on the side of slightly higher sensitivity to avoid missing critical events, though excessive sensitivity should be avoided as it could create continuous events. Step 4: Add Additional Users For smaller customers, such as individual homeowners, this step may be skipped, and the homeowner can be assigned the main account (owner user). This user is automatically created when a new customer is set up. To modify the access level of the owner user, navigate to the Account Profile page. Step 5: Create Alerts To take full advantage of the cloud platform, sensor alerts can be created. These alerts can provide timely notifications based on predefined triggers, ensuring that any important events are promptly flagged for attention. Step 6: Provide Training to End-Users While the system is designed to be user-friendly, some individuals may still find it challenging to navigate all the features independently. Many users may not explore every function, which can lead to inefficiencies, such as spending unnecessary time reviewing archives or waiting for clips to download. A walkthrough with the customer is recommended, focusing on the tools that will be most useful for their specific needs. Understanding how the customer plans to use the system will help identify which features to emphasize: For customers who will only monitor cameras occasionally (e.g., while on vacation), demonstrate how to use the mobile app and review footage triggered by alerts such as email or push notifications. For customers who primarily use the system for incident investigation, it is more beneficial to focus on features like the thumbnail grid, event menu, timeline navigation, and clip creation/download options.