• Not Answered

EM Operator Prompt

Hi Experts,

I was going through the standard or non-PCSD EM class template and wondering the way to put operator acknowledge prompt in the command driven EM.

Can anyone suggest a way to generate the prompt ?

Configuration as follows:

DeltaV v14.3.1

EM will run independently and will not be controlled by higher entity i.e. Phase or Unit module.

Thanks in advance,

Curious DeltaV Explorer

1 Reply

  • This could be as simple as setting a parameter True, logic would wait for the parameter to be false and build an operator interface that would allow the operator to click a button which would set the parameter False. You could also have an alarm for this type but I would suggest determine the priority of this alarm appropriately. I suggest having these type alarms be "hidden" by filtering these priorities out and have an indication on the interface if any of these type alarms are active.

    Here is a screen capture of what this looks like (with a couple prompts active) which is just a alarm list object filtered for the prompt priority/category and only showing the Module Tag and scrollable list so more than what can be displayed can be seen.

    To Filter the Alarm List and Alarm Banner:

    • Operate - Update the Standard/UserSettings.grf vba script for CFixPicture/Initialize (if you are using workstation specific you will need to modify these as well) to change the Variables PROCESS_THRESHOLD_DEFAULT to the highest priority number you want hidden. You may have to uncomment this logic as well as enable the logic that is setting the INIT_ALARM_THRESHOLD to 1
    • Live - Update the Standard Variable S_ProcAlmThresh to a highest priority you want hidden and the standard location for this is Library/Standards/Emerson/Common/AlarmPriority. Note: these are loaded and used from the Layout OnOpen script so ensure your layout has this logic or you can modify the logic their instead of using standard values but be careful doing this as there are some GEMs that might be using these variables and may not work properly if you don't use the variables.

    We typically create an "ALERT" priority that is 4 and use Alarm Type that sets the Category to PROMPT (or other types to do filtering) so we can use the AlarmList object filtering to create these "lists" very easily (Prompts, Simulation, Bypass, etc)

    If you have more than just acknowledge prompts then you will need to design all the methods and will be more than just a parameter described earlier.