1. Cutsforth Support
  2. InsightCM™ Software
  3. InsightCM™ Legacy Documentation
  4. Operation

Configuring a Trend Alarm Rule

Follow

Related Products:

EMMK-101, EMMK-102, EMMK-103

Related Documents:

ISCM-0380, ISCM-0385

Type:

Operation

Keywords/Labels:

severity, hysteresis, on and off delay, data collection

Summary:

This article describes the configuration procedures used to configure a trend alarm rule.

Configuring a Trend Alarm Rule

Configure a trend alarm rule for an equipment asset.

Before you begin, assign at least one feature to the asset for which you are configuring a trend alarm rule.

A trend alarm rule is a group of settings that causes InsightCM to set an alarm based on trend behavior. In most cases, you will configure trend alarm rules for each sensor asset, but you configure trend alarm rules directly on MCSA equipment assets. To set a trend alarm rule, define levels of severity for data that will set the alarm. You can manually configure these levels or auto-configure them using a baseline of data.

  1. Click the Configuration button (noloc_env_config.png) to navigate to the Asset Configuration page.

  2. In the right side configuration panel, select the Trend Alarms tab.

  3. Click Add to display the Trend Alarm Rule dialog.

  4. In the top left corner of the dialog box, use the pull-down menu to choose a feature you want to apply.

  5. In the adjacent pull-down, specify whether this alarm trips for trend values that are greater than or less than the compared value.

  6. Using the Operating State pull-down menu, choose whether the rule applies to all operating states or to one specific operating state.

    Note

    If you select All for the Operating State pull-down menu, you can not auto-configure levels from the baseline since the average data will differ for each feature type.

  7. Use one of the following two methods to define severity levels for the trend alarm rule.

    Methods

    Instructions

    Define levels based on a comparison value that you set.

    1. Click the Add button in the Levels section to display the Trend Alarm Rule dialog box.

    2. Specify the urgency of the level in the Severity pull-down menu.

    3. Specify the threshold you want the Cutsforth monitoring device to compare trend values against in the Compare To field.

    4. Check the Send Email checkbox to enable email options for the web application to use when the alarm trips.

    5. If there is more than one level that you want to set for a trend alarm rule, repeat these steps as needed.

    Auto-configure levels based on a value that InsightCM calculates from previously acquired data.

    Note

    To use auto-configure, you must have already acquired data.

    1. Check the Auto-configure level from baseline checkbox and a new Edit button should appear.

    2. Click the Edit button that appears next to the checkbox label to display the Auto-Configure Alarm Rule dialog box.

    3. In the Calculation pull-down menu, specify how you want the Cutsforth monitoring device to calculate the compare value.

    4. Click Add to display the Trend Alarm Rule Level dialog box.

    5. Specify the urgency of the level in the Severity pull-down menu.

    6. In the Compare To field, specify the initial value that the web application uses to calculate the threshold.

    7. Check the Send Email checkbox to enable email notifications to be sent when the alarm trips.

  8. If you use auto-configured levels, set a baseline.

    1. Click the Calendar button to bring up the Select Date Range dialog.

    2. Define a range of dates in the Start and End text fields with data you want to use to calculate a baseline. Click OK. Narrow the data set by clicking and dragging to zoom into a portion of the timeline. Double-click the graph to zoom out again.

    3. Click Set Baseline.

      Note

      If you do not set a baseline, InsightCM does not auto-configure levels.

trend alarm rule

Severity for Alarm Rules

Severity is a user-defined value that can be useful for setting the priority of an alarm condition. Use low severity for conditions that are outside normal operating parameters but still within acceptable limits. Use high severity for conditions where an analyst should review the data as soon as possible.

When an alarm is triggered, the server retains the data sets from that event. The server keeps track of the maximum severity for the alarm instance. Whenever a new maximum severity is tripped, the server retains the corresponding data sets. However, when an alarm transitions between severities, the server only retains the trend point data.

Table 1. Alarm Rules with Differing Severities

Feature

Condition

Set Point

Severity

Send Email?

True Peak

Above

0.2

1
unsupport.gif

True Peak

Above

0.4

2
support.gif

Auto-Configuring Severity Levels

Use trend baselines to auto-configure severity levels for an alarm rule.

Before you begin, collect data from the asset for which you are configuring an alarm rule.

  1. Click the Configuration button (noloc_env_config.png) and select a sensor-level asset.

  2. In the configuration pane, select the Trend Alarms tab.

  3. Find and select an alarm and click Edit.

  4. Select a feature and operator combination you want to auto-configure severity levels for.

  5. Select an operating state using the Operating State pull-down menu.

    Note

    If you select All, you will not have the option to auto-configure levels from a baseline.

  6. Check the Auto-configure levels from baseline checkbox to activate a new Edit button.

  7. Click the Edit button.

  8. Choose a calculation type using the corresponding pull-down menu.

  9. Add severity levels and click OK.

  10. Below the table of severity levels, click the calendar button to use data collected within a certain date range as your baseline.

  11. Click OK to select the date range and to activate the Set Baseline button.

  12. Click Set Baseline and OK to save your changes.

The alarm you have just modified now has severity levels that InsightCM has configured based on collected data.

Trend Baseline Minimum Data Ranges

Determine the minimum range of data that the web application should use to calculate a baseline.

Option

Description

Minimum Trend Points

Specifies the minimum number of trend points used to calculate a baseline.

Minimum Days

Specifies the minimum number of days over which data must be collected before calculating a baseline.

Minimum Standard Deviation

Specifies a standard deviation to replace the actual standard deviation of the baseline if the actual standard deviation goes below this value.

Configuring Hysteresis

Specify a threshold above or below the severity level that sets an alarm to reduce alarm instances from a noisy signal.

Note

This functionality only applied to features calculated on the device.

Before you begin, configure a trend alarm rule.

Configuring hysteresis is useful for preventing an alarm from clearing immediately after it is set. To learn more about hysteresis, refer to Conditions of Setting and Clearing Alarms. Specify an offset value from the Compare To value that clears an alarm.

  1. Click the Navigation menu and go to Alarms > Trend Rules.

  2. Find and select the trend rule for which you want to configure hysteresis.

  3. Click Edit to bring up the Trend Alarm Rule dialog.

  4. Below the sample of data in the dialog, configure the hysteresis value in the Hysteresis text field.

  5. Click OK.

The alarm rule that you have modified now clears an alarm when trend values cross the threshold for the hysteresis you specified.

If you want to refine the conditions for setting an alarm further, consider configuring an on and off delay.

Configuring On and Off Delay

Specify a time delay before InsightCM sets or clears an alarm to reduce alarm instances from a noisy signal.

Before you begin, configure a trend alarm rule. Configure hysteresis before configuring Off Delay.

On Delay specifies the amount of time that trend values must remain above the Compare To value before InsightCM sets an alarm. Off Delay specifies the amount of time that trend values must remain below or above the Compare To, or at the hysteresis value, before InsightCM clears the alarm. To learn more about On Delay and Off Delay values, refer to Conditions for Setting and Clearing Alarms.

Complete the following steps to set an On Delay or Off Delay value for an alarm.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select Alarms > Trend Rules.

  2. Find and select the trend rule to configure its delays.

  3. Click Edit to bring up the Trend Alarm Rule dialog.

  4. Below the sample of data in the dialog, configure the delay values in seconds using the corresponding spin boxes.

  5. Click OK.

The alarm rule that you have modified will now delay the setting and/or clearing of an alarm instance by the amount of time you specified.

On DelayOff Delay

Specifying a File Length for Data Collection

Specify file lengths for data that you want your monitoring devices to collect when asset conditions set a higher severity alarm.

Before you begin, configure a trend alarm rule.

InsightCM uses the value you specify for the file length to determine the size of the data collection when asset conditions set an alarm and cross a higher severity threshold.

Note

This option will override the collection settings determined by the operating state.

Complete the following steps to specify a file length for the data collected for an alarm.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select Alarms > Trend Rules.

  2. Find and select the trend rule to configure its custom file length.

  3. Click Edit to bring up the Trend Alarm Rule dialog.

  4. At the bottom of the dialog, uncheck the Use default collection length checkbox to activate the File Length text field.

  5. Use the File Length text field to specify how many seconds of data InsightCM will collect when conditions set a higher severity alarm.

  6. Click OK.

The alarm rule you have just modified now collects trend data files for the length of time you specified for File Length.

Specifying a Pre-Trigger Length for Data Collection

Delay the start of data collection when asset conditions set a higher severity alarm.

Before you begin, configure a trend alarm rule.

InsightCM uses the value you specify for the pre-trigger length to determine how long after asset conditions set an alarm and cross a higher severity threshold to wait before collecting data.

Note

This option will override the collection settings determined by the operating state.

Complete the following steps to specify a pre-trigger length for an alarm.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select Alarms > Trend Rules.

  2. Find and select the trend rule for which you want to specify a pre-trigger value.

  3. Click Edit to bring up the Trend Alarm Rule dialog.

  4. At the bottom of the dialog, uncheck the Use default collection length checkbox to activate the Pre-Trigger text field.

  5. Use the Pre-Trigger text field to specify how many seconds InsightCM will wait after asset conditions set a higher severity alarm before collecting data.

  6. Click OK.

The alarm rule you have modified now waits the length of time you specified for the pre-trigger before collecting data.

Defining a Trend Alarm Rule for Asset Types

Define a trend alarm rule for all assets of a certain type.

Edit an asset definition to configure a trend alarm rule for all assets of a certain type.

Note

The changes you make to the definition of an asset type will apply to all applicable current and future assets.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select Systems > Asset Definitions.

  2. Select a definition to edit and click the Trend Alarm Rules tab.

  3. Click Add to display the Trend Alarm Rule dialog box.

  4. Choose the feature you want the rule to apply to from the pull-down menu in the dialog box.

    Note

    Only features that have been toggled to default in the Features tab for this asset type will be available options in this pull-down menu.

  5. In the adjacent pull-down, specify whether this alarm triggers for trend values that are greater than or less than the compare value.

  6. Choose the operating state to which you want this trend alarm to apply using the Operating States pull-down menu.

    Note

    If you choose to make the trend alarm active in all operating states, you will be unable to auto-configure levels from the baseline because baselines will differ for each state.

  7. Use one of the following two methods to set levels for the trend alarm rule.

    Methods

    Instructions

    Set levels based on a set Compare value that you define.

    1. Click Add in the Levels section to display the Trend Alarm Rule Level dialog box.

    2. Specify the urgency of the level using the Severity pull-down menu. Spectral alarm rules are only calculated on the server.

    3. Specify the multiplier to which you want the web application to compare trend values in the Compare To spin box.

    4. Check the Send Email checkbox to enable email options for the web application to use when the alarm trips.

      Note

      If you have not configured an address group and a specific email template for an alarm type, you may do so for the default group and email template that the web application already has loaded.

    5. When prompted about applying the alarm rule to all the assets of this type, select Yes or No.

    Set levels based on a value calculated from previously acquired data.

    1. Check the Auto-configure level from baseline checkbox and a new Edit button should appear.

    2. Click the Edit button that appears next to the checkbox label to display the Auto-Configure Alarm Rule dialog.

    3. In the Calculation pull-down menu, specify how you want the web application to calculate the Compare To value.

    4. Click Add to display the Trend Alarm Rule Level dialog.

    5. Specify the urgency of the level in the Severity pull-down menu.

    6. In the Compare To field, specify the initial value that the web application uses to calculate the compare value for the level.

    7. Place a checkmark in the Send Email checkbox to enable email options for the web application to use when the alarm trips.

  8. If available, use the following options to override the collection settings determined by an operating state.

    • User default collection length—Uncheck this option to enable the File Length and Pre-Trigger Length options. InsightCM uses the values you set for these options when the alarm condition is triggered and when the alarm severity changes.

    • File Length—Specify how many seconds of data to collect while the alarm rule is active.

    • Pre-Trigger Length—Specify how many seconds of data to collect before the event that triggers the alarm rule.

Do you need more help?

Submit your questions or requests using the Support Ticket Submission form.

trend alarm ruleOn DelayOff Delay
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more