Hi Dojo,
we recently got the requirement to offer the possibility in Dataminer to mask specific alarms ahead of time. In our example there is a protocol that has multiple gateways in one table and we would like to mask a specific gateway at a predefined time in the future to ensure during a maintenance the NOC does not receive any false alarms. I did take a look at the Planned Maintenance Module but did not get it to work properly and the documentation for this is unfortunately not really comprehensive.
Do you have any suggestions how that could be implemented?
Thanks in advance!
Best regards
Manuel
As this question has now been inactive for a long time, I will close it. If you still want more information about this, could you post a new question?
Hello Manuel,
I am not sure if you can mask specific alarms ahead of time, but you can mask the element ahead of time. You can use the scheduler module to run a script at a specific time and the script can mask/unmask the element.
If this does not work for you, then you can have a correlation rule to capture the specific alarms for the specific elements, send that alarm information to an automation script, and the script can mask those alarms. This of course, would require processing of each alarm for the gateway that you would like to mask. Please let me know if this helps.
Hi Manuel,
Instead of masking alarms, a possible option is to schedule when an alarm template can be applied.
Hope it helps.
Hi Miguel,
thanks for you input. I’m not sure scheduling alarm templates will be very user friendly or maintainable since in a table there could be potentially countless possibilities of combinations which of the different rows need to be alarmed and which one not. I believe this option would only be helpful if you have a reoccurring schedule but i am searching for a possibility which the operator can define and that can handle some variety in the Schedule
Hi Manuel,
– Masking an alarm implies that the alarm must exist in the first place. If I understood correctly you would like to avoid alarms being generated.
– You can create as many alarm templates required to cover your requirements. Keep in mind that alarm templates can be assigned through automation script/schedule tasks as well. Here you can cover more complex use cases
– Since you are referring to tables, keep in mind that you can assign different severities to rows:
https://docs.dataminer.services/user-guide/Basic_Functionality/Protocols_and_templates/Alarm_templates/Configuring_alarm_templates/Configuring_normal_alarm_thresholds.html#configuring-alarm-thresholds-for-dynamic-table-parameters
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer that has been most helpful for you (using the ✓ icon)?