Emerson Exchange 365

• Not Answered

Alarm Acknowledgement and Electronic signature

Dear Engineer,

I'm actually fighting with Alarm Acknowledgement for a specific Project. Our Customer wants to implement specific alarm Priority, with specific Acknowledgement rights.

That means in the AI block I added a Alarm Block with 6 new alarm level and higher Priorities. This alarm level are enabled/disabled via faceplate, one Check box per level (HI, HI_HI...) and one push button to active the monitoring.

This works well, but the customer wants to use Electronic signature to Acknowledge ONLY this new alarms.

I've added a new Signature Policy with Field Confirmation / Field Name: NALM / Signature Required: Confirm and Verify.

But this Policy is applied to  the whole AI Block. Is it possible to assign a Policy to a specific Alarm ?

I've found no help in BOL.

If somebody knows where I could find useful information about Electronic signature, with different Examples and screenshots....

Regardless of the question above, is it possible to Acknowledge one single alarm eg: PT100_HIHI with a push button on the display. A vba code example is welcome

Thanks a lot.

LostEngineer0

• 27 Aug 2015 11:20 AM
• Cancel

10 Replies

• LostEngineer0

  

  • 2 Sep 2015 5:44 AM

  No idea?

  • Cancel
• Nikki Bishop

  

  • 2 Sep 2015 1:53 PM

  Ben Bishop Can you answer this one?

  Nikki Bishop, PE |  Director, Global Turnaround Program Nikki.Bishop@Emerson.com

  • Cancel
• Matt Stoner

  

  • 2 Sep 2015 7:15 PM

  I think the only thing that you can do is enable the E Signature on the 'new' alarm name(s), hopefully they are unique, and not on the NALM field. I believe that this mean that any update of that alarm (Enable, Suppression, Priority, etc) would have that Confirm and Verify apply but since the system is global based on the parameter name or field, this is about all you can do with the current system.
  
  Regards,
  Matt

  • Cancel
• LostEngineer0

  

  • 16 Sep 2015 6:53 AM

  In reply to Matt Stoner:

  Thank you.

  I simply added in the new  alarm name in the tab "Parameter Confirmation" in my ES Policy, with  "Confirm and Verify " as signature required.

  That works fine, but a new problem appears

  Example:

  5  alarms which require confirmation are active.

  The Operator acknowledge them through "Acknowledge All" Button on Alarm Summary Display.

  The confirmation pop up appears only one time, and not 5 time how I expect.

  I need one confirmation per Alarm (which require confirmation) , how could I resolve this problem?

  Thank you for your help.

  • Cancel
• István Orbán

  

  • 16 Sep 2015 8:46 AM

  In reply to LostEngineer0:

  Since using the ack all button is one action, you will only get one confirmation popup, no way to configure this differently.
  One way to solve this is to remove the Acknowledge All button from all your faceplates, forcing the operator to acknowledge each alarm individually.

  • Cancel
• LostEngineer0

  

  • 6 Jul 2016 6:21 AM

  In reply to István Orbán:

  Hello,

  we've implemented the E-Sig as describe above.

  We are facing a dicrepancy.

  1) HI_HI_Alarm is Active

  2) The Operator Acknowledge via Acknowledge All onnfaceplate

  3) The E sif Pop Up appears.

  4) The operator write a comment and confirm with ID and PW, but the PW is wrong.

  5) We expected that the aknowledgement is not confirmed.....But it is not the case.

  Please could somebody explain me the logic?

  Thank you for your help
  

   

  E-Sig config:

  • Cancel
• LostEngineer0

  

  • 6 Jul 2016 6:29 AM

  In reply to LostEngineer0:

  Hello,

  we've implemented the E-Sig as describe above.

  We are facing a dicrepancy.

  1) HI_HI_Alarm is Active

  2) The Operator Acknowledge via Acknowledge All on faceplate

  3) The E sif Pop Up appears.

  

  4) The operator write a comment and confirm with ID and PW, but the PW is wrong.

  

  5) We expected that the aknowledgement is not confirmed.....But it is not the case.

  

  Please could somebody explain me the logic?

  Thank you for your help

   

  E-Sig config:

  

  • Cancel
• Andre Dicaire

  

  • 6 Jul 2016 6:15 PM

  In reply to LostEngineer0:

  What you describe above looks like an issue that you should report to the GSC. I suggest that you create or use a different user than ADMINISTRATOR and see if the same thing happens. You can create a new user with all the administration privileges. The Specific default ADMINISTRATOR user has some special capabilities around security that any other user created on the system will not have. Emerson recommends that you not use the default ADMINISTRATOR user and to disable this account. It should only be used for administering the system.
  
  If you create a new ADMINISTRATION user and everything works as expected, and the acknowledgement does not occur when the password is wrong, you should still log the call with the GSC. Maybe this has been fixed in a later release, but if it all works correctly with a different user, you have a relatively simple fix (i.e. disable the Administrator account and create a new one for your system).

  Andre Dicaire

  • Cancel
• LostEngineer0

  

  • 6 Jul 2016 7:09 PM

  In reply to Andre Dicaire:

  Hello André,

  thank you for your help.

  This problem happens on the plant (with Operator capabilities).

  I've made the print screens on my test station, that's why the user is ADMINISTRATOR.

  
  I've tested an other way to acknowledge, instead of using the "Ack all" button on the Faceplate, I've simply click on the single alarm, on the Alarm Summary on the face plate.

  An  E-Sig pop up appears with another design (the same as if you write directly the  variable in Control studio), and if I press OK with a bad password nothing happens!

  The Alarm is still UNACK, that is what we need.

  The system also  react differently with  "Ack All" and the single Alarm Ack (Faceplate on Alarm Sum.).

  I will contact our Emerson Support. If somebody knows something thank you for sharing your information.

  Kind regards

  Christophe.

  • Cancel
• LostEngineer0

  

  • 11 Jul 2016 10:49 AM

  In reply to LostEngineer0:

  Hello,
  If somebody is facing this problem check : NK-1400-0523
  "ALARMS" have to be added as parameter with requiered Signature.
  Kind regards

  • Cancel