Alarm Priority moving

Hello I'm involved in a interesting project on a also running  DeltaV Plant.

My job in this project consist to add Alarm priorities and to move existing priority.

Actual:                                                   In the Futur:

CRITICAL (15)                                     S-CRITICAL (15) / Q-CRITICAL (14) / P-CRITICAL (13 )/ CRITICAL(12)

WARNING (11)                                    S-WARNING (11) / Q-WARNING (10) / P-WARNING (9) / WARNING (8)

ADVISORY (7)                                     ADVISORY (7)

This new S-Q-P alarms will first implemented in, for example AREA_A, but in AREA_B we want to keep the 3 actual CRITICAL, WARNING, ADVISORY  prios , with new numbering (12,8,7).

What's  the easiest way to proceed?

Thank you for your help.

1 Reply

  • This isn't an easy process, risky and almost impossible to do 'safely' on a running plant. I would suggest you test on an offline system if you decide to continue in this direction to verify your process and ensure what has been changed or not changed prior to doing the running plant.

    You CANNOT delete/move the highest priority alarm in the system, you can only rename it (either by DeltaV Explorer or FHX import). This means all your alarms in the system that are currently at CRITICAL priority will be moved to the S-CRITICAL priority. This means you may have to update every configured prior CRITICAL alarm in the system which may or may not be what you want.

    The WARNING priority can be moved (only by FHX import) without affecting the alarm configurations in the system if the process is done correctly.

    CAUTION / DISCLAIMER - By doing what you want, you will have created an upgrade/migration nightmare because you will have to replicate this process each time you upgrade (Manually rename CRITICAL, Manually import WARNING to 8, then import the migrated system FHX). If you don't do the process correctly, you will have import errors and COULD end up with a different system configuration after you upgrade than what was configured prior to the upgrade!

    I strongly suggest you try to rename your alarm scheme so that 15 remains CRITICAL and 11 remains WARNING to avoid doing this if at all possible.

    If you still decide you want to proceed with creating this upgrade/migration nightmare and continue with your current alarm name direction, let me know what version you are on and I may be able to give you an import file to move WARNING to 8 (may not have your revision). Then you can manually rename CRITICAL to S-CRITICAL and manually create the others you need BUT REMEMBER that you will need to review EVERY alarm that was assigned the CRITICAL priority as these will now be S-CRITICAL.

    Regards,

    Matt