ArcadianAI

Have more questions? Submit a request

ArcadianAI

Logo-ArcadianAI.jpg

Supports Standards

This manufacturer's devices support standards for receiving SMTP/Email alarms

 

Standards Based - Features

  • Alarms
    • ResponseCode Matching
    • EventType Matching
    • ExtraText Decoding
    • Location Decoding

Standards Based- Manufacturer License Requirements

N/A No additional Manufacturer License Required

 

Standards Based - Alarm Configuration

First Time Configuration

Create the ArcadianAI - SureView Standard Decoder

This decoder is usually pre-configured in your SureView Account. These instructions are here in case it needs to be added manually or edited. Please contact SureView Support before making changes to the Standard Decoder

  1. Login to SureView and navigate to the "Alarms" setup screen
  2. Click on the "Alarm Decoder" Tab
  3. Click "Add Alarm Decoder" and complete the following values

    Title: ArcadianAI
    SureViewResponseCode:\s*(?<rc>[^\r\n]+)
    Event Regex
    SureViewEventTypeCode:\s*(?<ec>[^\r\n]+)
    Extra Text Regex
    SureViewExtraText:\s*(?<et>[^\r\n]+)
    Default Area:

    Select the are you would like any non-matched alarms to be sent to. 

     

    Recommended: Select your top level area
    (Normally this will be our SureView Organisation Account Name)

    Default Action Plan: Select your preferred Action Plan or leave blank
    Default Grouping: Select your preferred Default Grouping
    Recommended "By Area"
    Default Priority Enter your preferred default priority
    Recommended: 0

Add the ArcadianAI Event Types

ArcadianAI allows for custom event types and are unique for each organisation's account. Once you have your list of ArcadianAI Event Types you can add them to SureView for automatic alarm matching. 

The basic matching can be configured in the Decoder setup screen or for more advanced options please go to the Event Types setup screen 

Decoder Setup 

  • Login to SureView and navigate to the "Alarms" setup screen
  • Click on the "Alarm Decoder" Tab
  • Edit the "SureView Standard Decoder"
  • Add the required event types as listed in AcadianAI Setup (examples below)
    Note: The Event Type Name, Default Priority and Default Grouping can be customised to your requirements but the "Event Code" must match exactly (including case) for compatibility with ArcadianAI

    Event Type Name Event Code Default Priority Default Grouping
    UnknownAlarm UnknownAlarm 50 Inherit
    Alarm Alarm 100 Inherit

Adding Alarm Points

Once your decoder has been configured you will be able to create any necessary alarm points in SureView. You will normally need one alarm point per alarming ArcadianAI Camera 

  1. Login to SureView and navigate to the "Alarms" setup screen
  2. Go to the "SMTP alarms" tab 
  3. Click "Add Alarm"
  4. Fill in the fields as required (see example table below) and press Add
Field Description
Alarm Name
(Required)
The friendly name for this alarm. This is the name that will be shown to the operator when it is triggered.
Area
(required)
What Area is this alarm associated with.
Linked Cameras
(Optional)
You can link this alarm with specific cameras so that the cameras you choose pop-up automatically when an Operator opens this alarm. (See Video Device Setup)
Action Plan
(Optional)
An alarm can (optionally) be associated with an Action Plan. This will provide the operator with a set of instructions that they will be required to follow when processing this alarm.
Alarm Decoder Select your ArcadianAI decoder 

Explained in the "First Time Configuration-  Create the ArcadianAI - SureView Standard Decoder" section of this support page
Response Code Add the Alarm Point / Camera GUID that can be found on ArcadianAI

e.g. cb10333b-13ab-4c9e-83f5-349ba1a67c4a
Priority

This is an indication of how important this alarm is. The higher the number, the more important the alarm. 

If you leave the priority as 0 it will instead use the default priority for the incoming alarm event type that you configured in the decoder setup.

Note: Priority 1000 (one thousand) and above should be reserved for your most serious alarms that require immediate attention from your operators

Grouping
(Required)

This allows you to decide how you want multiple instances of this alarm to be grouped when it goes into the Alarm Processing QueueThe options are:

  • By Area
    Multiple separate alarms that are triggered for the same Area will be grouped together for the operator to process as a single event.

    This Recommended for Area / Sites that are physically small in size where any alarm generated would be likely related to each other.
     
  • By Alarm
    Multiple instances of this specific alarm will will be grouped together for the operator to process as a single event.

    This is recommended for larger Area / Sites where individual alarm points may be completely unrelated to each other due to distance.
     
  • Not Grouped
    This alarm will never be grouped with any other. Each time it's triggered it will come into the Alarm Processing Queue as a separate, individual alarm event.

    This is only recommended for very specific alarms that should be handled individually (such as a Panic button or a Fire Alarm) as it can lead to large alarm queues with lots of single alarm events.
Auto Handle

This allows you to set an alarm point to be Auto Handled - Where the alarm will be received and logged in the history but not shown to the operators.

Most alarm points should be set to "No"

 

Auto Handling is usually reserved for alarms that may be useful to have in the history for reporting purposes (such as certain technical alerts) but not alarms that you would expect an operator to have to make any actionable decisions with.

Expected Frequency (minutes)

How often you would expect to receive an alarm from this alarm point. If an alarm isn't received in that time a "NOT RECEIVED" alarm will be triggered into the alarm queue and the alarm point will be shown as unhealthy in SureView Status.

Leave this field blank to disable any expected frequency monitoring.

Service Level Agreement (SLA) in Seconds: If this alarm point as a specific SLA value that operators need to meet this can be entered here.  If it's left blank then the alarm will using your Organisation's default SLA rule (configured in Organization Settings screen)

 

Example Alarms

Below are screenshots of example test alarms being received from ArcadianAI into SureView

2025-12-01 11_54_15-SureView Operations — Mozilla Firefox.png
2025-12-01 11_54_45-.png

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.