Skip to main content



This specification describes all aspects of design, development, testing and commissioning of the Inovonics Area Control system into the BluSky environment

Overview of Inovonics Area Control system

Inovonics Area Control system is comprised of an Area Control Gateway (ACG EN 6080) device, signal repeaters, input monitoring transmitters, as well as fixed and mobile duress pendants. ACG is capable of communicating with Mercury EP-series controllers and Mercury SIO board commands. Communications between Mercury controllers and ACG occur via Ethernet

Description of Presentation

No Special presentation needed for Inovonics Gateway, because it can be configured and monitored through the Mercury Configuration, Control and Monitoring tools.

Additional Board type needs to added to the list of Mercury supported boards in the BluSky.

Inovonics Area Control configuration

ACG EN 6080 has embedded WEB server, which allows to configure network parameters as well as connected device settings. It also provides auto-detect feature, which simplifies the latter task

On a BluSKY side ACG should be represented as new type of Mercury SIO. We will also need to create a Mercury monitoring point for each of Input Transmitters and/or Repeaters. The IDs of these devices should be taken from the ACG WEB interface

In addition to a “Fixed Point” input transmitters Inovonics Area Control system has “mobile duress pendants”, which can be triangulated in order to get the alarm location. At this point we are not planning to use the location feature so such devices should be treated like “Fixed Point” inputs


ACG can generate two types of events that are mimicking Mercury transactions:

· When an alarm is triggered by a monitoring point Mercury transaction 7:4 is generated (alarm – activated relay). There are not changes we need to add in order to process this alarm

· When an alarm is generated by a mobile pendant ACG generates a 6:10 transaction (request granted: duress, used) with a card number set to TX ID configured for a given pendant via ACG WEB interface. So, in this case we will need to recognize such transaction (card format value for them is always 127 -TBC) and convert it to an alarm event


ACG reports inputs/monitoring point faults in a same manner as Mercury so there are no additional diagnostic tools required


BluB0X needs a way to prioritize, highlight, and generate audible alerts with alarms.


User Experience

Security Guard is monitoring Control Alarms page.  They can filter the alarms to those alarms that they are responsible for monitoring.  Any alarms that needs special notice or higher response rates can be highlighted with different colors, sounds can play or screen flashes.  To make daily setup easier they will have the ability have Alarms be group together for easier selection.  Grouping only effects views.  There is no intention of modifying or changing all the monitoring points as a group.  There will be a new permission to enable certain people to change the customization of the Alarms.   Just because you have access to the alarms page does not mean you can change the priority, colors, or sounds.


Alarm Customizations are Hierarchical,  If base alarm not set it will get it setting from the next level up, if next level up not defined it will go to the next level. Etc.


Engineering Tasks:

  • UI for editing Alarm configuration
    • UI Similar to Distribution groups - 1 element to many groups.
      • Alarm Configuration List Page






Comment Req.

<Delete Icon>







(-) Red



Exec Office







      • Buttons: Edit, Create
    • Need Screens Create/Edit
      • Pop-Up
        • Alarm point Types - Choose type
        • Alarm Point Picker
        • Color Picker - Customer can choose any color, we store the RGB value.
        • Sound Picker - BluB0X provided, customers will not upload their own sound files.
        • Priority - Select or Text box, limited to numbers.
  • Control UI, need ability to select an alarm and edit its configuration.
    • If no item selected prior to selection of the edit configuration, then go to edit configuration list page.
  • Control Alarm UI
    • Add column for Alarm priority
    • Add tool tip for Alarm Detail pop-up for bookmarks (Instructions, comments…)
    • Columns: Event Date, Metaview (Need PB to define), Source, Type, Description, Priority, Status
  • Control UI Filter:
    • Filter by Priority and Group
    • Finish Alarm selection
      • Issue:  There could be 100's of alarm points to choose from.  Would limiting the Alarm filter to Groups or Priority be enough?  This could be heavy weight, consume resources.
    • Filter by Occupancy - Think about once we have maps and locations.
    • Is there a use case for filtering by Alarm Type?
  • Alarm tab and history tab should have same functionality.
  • New Feature - Automatically clear alarms after XX time.
  • For Rules, need to have a High, Medium, Low settings.
    • Is this set by formula, ex. Low is bottom is 1/3 of range, Top is 1/3 for range
    • Is this set by markers, 75 and higher are low, 25 and lower are High.
  • Need a UI to define canned responses that can be added to the comment for an alarm.  Responses are system level.  Responses are in the DB but no UI currently to create them. 
  • Need to be able define alarm instructions for each security point that went into alarm.






  • When are priorities applied, at time of event or at time of viewing of alarms or events.
    • If priorities are stored in event, can the priority be updated historically? Audit implications???




  • Highlight Events in Alarm Screen
  • Create audible alarm when even occurs
  • Flash Screen when alarm come in.
  • Enable by
    • By Event
    • By Point
    • By IPS Group - Change term IPS group to something else, IPS group  is a Mercury term.
    • By Alarm type
    • By Priority
    • By Customized group.  - Needs to be discussed, could heavy weight.
      • One alarm to many groups.
    • By Facility
    • By System
    • By BluB0X (defaults in case customer does not set)



  • Was this article helpful?