Alarm & Event Management

Sensys offers a very comprehensive and state of the art alarm & event management system that we claim to be one of the best in business. In manufacturing organizations safety, security and compliance are amongst the key issues faced. These are critical from operations point of view since the objective is to reduce operating costs and maximize profits.

Sensys state of the art Alarm & Event Management system has the capability to combine data from multiple control systems and thus provide a single platform for operators to manage and control. It  enables the organization to store all the key parameters critical to manufacturing/production, monitor these parameters on real-time basis, set limits for variation of these key parameters, generate notification once the limit is reached, prompt necessary action to be taken against these, keep record of the events that occur and log the data for future consideration analysis.


  • Reduced risk of injury and accidents/ Improved safety
  • Reduced operation risks
  • Decrease in unscheduled downtime
  • Improved traceability of faults
  • Reduced maintenance costs
  • Improved operator effectiveness
  • Single operating platform for multiple control systems
  • Prompt action upon notification
  • Improved up-time of manufacturing equipment
  • Continuous visibility


Advanced Alarm Analytics

Alarm & Event management provides a very comprehensive and advanced alarm analytic tool to perform in-depth analysis on the alarms generated and thus find root cause of the problems.

Alarm Filtering 

Alarms can be segregated on the basis of:

  • Severity
  • Count
  • Source
  • Time/ Date
  • Category
  • Area etc.

Alarms Count Over Time

This analytic gives us the alarm rate for all the tags over a specified period of time. Filtering available through History Alarms and Events Control can further facilitate a more elaborative analysis once the alarm rate has been calculated. An engineer can then focus his research on what are the root causes of so many alarms in order to have limited number of alarms as stated by the set guidelines, to be generated on the plant.

Alarms Count by Source

This gives us the count of alarms that occurred for a particular tag. As for the time frame for which the data is being analyzed, it comes from the History Alarms and Events Control that is associated with this analysis. Once the alarm rate has been realized, an engineer can then go on to determine the tag(s) that generated the highest number of alarms, in other words is the problem creator.

Alarm Chattering

Repeating alarms are a nuisance and to some extent are due to an engineering fault. This analysis aids an engineer to realize the tags on which alarms are generated repeatedly. To be more precise, this analysis basically tells us the percentage of the time a particular alarm has been generated within a cluster(s). Once analyzed, an engineer can then re-configure the limits associated with the tags such that their cluster percentage never reaches a 100%.

Standing Alarms Duration

Standing alarms are those alarms that stay in an active state for a long time. According to the EEMUA 191 guidelines, if an alarm stays active for 20 hours or more, it would be classified as a standing alarm. This analysis tells us the duration for which an alarm stays in active state.

Standing Alarms over Time

For more extensive analysis regarding standing alarms, this analytic aids an engineer to see the standing alarms over specified intervals of time. Let us assume that an engineer gives an interval of 10 hours, the analytic would then show him/her the count of standing alarms within intervals of 10 hours each for the set time frame (coming from History Alarms and Events Control).

Operator Response Time

Time taken for an operator to acknowledge an alarm with respect to each tag is shown as a result of this analysis. This analysis in combination with “Operator Response Counts over Time” helps to be a performance calculating technique for the operators.

Operator Response Counts Over Time

This analysis shows us the count of alarms that were acknowledged by an operator in comparison with the total number of alarms that were generated within a specified interval of time. Using the previous mentioned analytic in conjunction with this one, engineers can now determine the performance of the operators in a more comprehensive manner.

Alarm Association

This shows us the alarms generated before and after an alarm is generated for a particular/specified tag (parent tag). User also needs to define the offset or interval of time for which before and after alarms needs to be shown by the analysis.

Alarm Rectification Rates

This basically determines the time taken for an alarm to come from an alarming to normal state. Alarm Analytics is a very vital feature when it comes to analysis. This has been very intelligently incorporated within IntelliMAX. History Alarms and Events Control act as data sources for Analytics. Such data sources having the filtering capabilities to make customizable views of data further allows you to perform analyses on the required parts of data that are of more importance and concern. As for the tool presentation, the charts produced by Analytics are of high quality graphics and you can customize them by choosing from a variety of chart types, defining captions for the axes and their labels, color settings, legends and much more. Now that we have discussed the purpose and advantages of alarm analytics lets move forward and see how to create and configure alarm analytics.

Alarm Logging

Alarm & Event Management allows not only real-time management of the generated alarms and events but also provides logging of these alarms and events so that they can be retrieved at any time and used for analysis and take precautionary measures.

Open Connectivity

Alarm & Event management system has the ability to collect data from multiple sources i.e. different control systems and then combine this data from multiple sources to provide a single interface. This is also beneficial to the operator who now has to manage a single interface as oppose to multiple.