Hi Mark, If you want to contact me off list I can point you in the direction of = standards for alarm priortisation that I ham implementing at Shell = Brunei.. Regards Ron -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Mark Dumond Sent: 15 March 2006 06:14 To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Recommended practices for assigning Alarm Priorities Hello Group, Does anybody have any good ideas or even "successful" recommended = practices for assigning Alarm Priorities in I/A, that can be categorized? As a simple example, 1=3D Emergency Situations 2=3D Alarms that cause Shutdown 3=3D Alarms, such as motor and valve mismatch 4=3D General Messages 5=3D Other Or is it just better to make a priority assignment on an individual = alarm basis? Any information is greatly appreciated! Thanks in advance, Mark Dumond FeedForward, Inc =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave