--- title: "Pipeline - Filter on Alarm Associated Data" --- # Pipeline - Filter on Alarm Associated Data > :::note > The examples in this section assume you have an [alarm](platform/alarming/configuring-alarms/configuring-alarms.md), [alarm associated data](platform\alarming\configuring-alarms\alarm-associated-data\alarm-associated-data.md), a [notification profile](../../alarm-notification.md), and an existing [on-call roster](../../on-call-rosters/on-call-rosters.md) configured. > ::: ## How to Filter on Alarm Associated Data Once associated data is added to an alarm, you can easily filter for associated data in an alarm pipeline. It’s possible to add associated data that can be either static or dynamic. Below is an example of how to filter a notification pipeline based on associated data added to an alarm. A WriteableFloat1 Tag is used for this example. 1. In the **Tag Browser**, double-click on **WriteableFloat1** to open the Tag Editor. 2. Scroll down to **Alarms**. 3. Click on the **Edit** ![]() icon to view the alarms. This example has three alarms set up: Fault1, High Alarm, and Low Alarm. ![](2020-04-03_10-16-37.png) 4. Expanding the High Alarm configuration shows the Associated Data called Group, and a value of either "Group A" or "Group B". We are going to use this associated data to filter the alarm notification pipeline. ![](2020-04-03_12-11-06.png) 5. For this example, drag in the **Switch block** to your pipeline, and connect the **Start block** to the **IN** of the Switch block. There are two blocks that can be used for filtering, either the Switch block or the Expression block. The Switch block allows you to switch on a value and do something different for Group A and Group B. The Expression block does the same thing, but only returns values of True or False. ![](pipeline-filter-on-alarm-associated-data-step-5.png) 6. In the **Pipeline Property Editor**, you have to manually enter the expression because you will not find any of the associated data properties in the dropdown list. Enter the name of the associated data property in curly braces, such as `{Group}`. The **Group** associated data property acts as a placeholder for the real values. ![](pipeline-filter-on-alarm-associated-data-step-6.png) 7. Next, you need to add some values to the expression. You can add as many values that you have values for. Click on the **Add** ![](add-icon.png) icon and add two values: **Group A** and **Group B**. Once you enter both values, you will have outputs in the Switch block for **Group A**, **Group B**, and by default, **Catch-all**. Now you can notify a different list of people based on each Group. ![](pipeline-filter-on-alarm-associated-data-step-7.png) 8. Drag a Notification block into your pipeline, and connect the output of **Group A** in the Switch block to the **IN** of the Notification block. 9. In the Pipeline Block Editor, under the Notification tab, choose **Email Notification** as your notification type. 10. In the **Contacts** tab, under the **On-call Roster** icon, select the roster you want to notify (i.e., Operators). ![](pipeline-filter-on-alarm-associated-data-step-10.png) 11. Drag a second Notification block to your pipeline, and connect **Group B** from the Switch block to the **IN** on the second Notification block. 12. Choose **Email Notification** as your notification type, and specify a different On-call Roster to notify a different group of people. We will be using the Managers roster in this example. ![](pipeline-filter-on-alarm-associated-data-step-12.png) Now, you are notifying people based on Group A (Operators) and Group B (Managers) by filtering on alarm associated data.