As for NOTICE, I have seen the exclamation point used as an icon in front of the statement. It seemed to convey the message very well. Based on ISO 3864-2 or ANSI Z536.6 is this allowable?
Rick From: Greg McClure [mailto:[email protected]] Sent: Tuesday, March 03, 2015 8:40 AM To: [email protected] Subject: [PSES] Signal words, definition and usage Looking for input from the group. The definition of the signal words per ISO 3864-2 and ANSI Z535.6 are: DANGER - signal word used to indicate an imminently hazardous situation which, if not avoided, will result in death or serious injury WARNING - signal word used to indicate a potentially hazardous situation which, if not avoided, could result in death or serious injury CAUTION - signal word used to indicate a potentially hazardous situation which, if not avoided, could result in minor or moderate injury NOTICE - indicates information considered important, but not hazard-related (e.g. messages related to property damage). The safety alert symbol shall not be used with this signal word. When a signal word is used for messages relating to property damage, NOTICE is the choice of signal word. [This definition is from ANSI Z535.6, NOTICE does not appear in ISO 3864-2] The signal words are to be used to identify safety messages and property damage messages. In another context, some of the signal words have been used to warn of data loss or damage, which I suppose is a form of property damage. Many standards allow the use/definition of the signal words to be modified, provided they are defined in the documentation provided with the product. In many cases we have seen the severity associated with the words Warning and Caution reversed, or even the mention of injury deleted such that Warning is associated with equipment or property damage only and Caution is used to refer to potential injury. Has anyone had an experience with any agency or test house where the use of signal words was challenged, or any case where the definition had to be defended when it was not strictly in line with the standards? Gregory H. McClure Lexmark Product Safety 859 232 3240<tel:859%20232%203240> office 859 232 6882<tel:859%20232%206882> fax - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]<mailto:[email protected]>> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe)<http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]<mailto:[email protected]>> Mike Cantwell <[email protected]<mailto:[email protected]>> For policy questions, send mail to: Jim Bacher <[email protected]<mailto:[email protected]>> David Heald <[email protected]<mailto:[email protected]>> - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
