My understanding is that NRTL marks are supposed to have equal value for adherence to National Electrical Code and OSHA requirements. In other words,-- this is O.K. for end-use applications only. However, this is as far as it goes. Nowhere does it state that NRTL X has to accept NRTL's Y marked equipment, especially when incorporated into a composite system that NRTL X is evaluating and where their mark will "bless" the complete system. My recommendation is, if you have other NRTL marked equipment than the one you are dealing with, call your NRTL first before springing such a surprise on them. Depending upon the agency, they may or may not accept part of the report from the other NRTL. Did you know that some 10 years ago, the German VDE safety agency would NOT necessarily accept the also German TUV Rheinland test reports of components (such as fans, filters, power supplies) that were incorporated in your equipment?????? Much to my chagrin, I found that out. (We quickly replaced fans!)
Tania Grant, [email protected] Lucent Technologies, Switching Solutions Group Intelligent Network and Messaging Solutions -----Original Message----- From: John Juhasz [mailto:[email protected]] Sent: Tuesday, October 24, 2000 6:58 AM To: '[email protected]'; [email protected] Subject: RE: Got another beef about an NRTL.... Duncan, I've had the scenario with my end product (very simple product - metal enclosure, SELV printed circuit, 150W Recognized component Power Supply, Recognized Input module. That's it.) I had it listed with NRTL B. Market pressure forced me to get NRTL A's listing mark - to the same standard. NRTL A would not accept ANY data (not just test data, even part number info - I had to send the complete package again). While I don't like to pay twice for the same thing, and while I was exposed to what amounted to be different interpretations (between the NRTLs) of the specifications causing great frustration . . . I looked at it from a different point of view. Don't get me wrong, I do sympathize with you, and I wish they had an MRA between them - it would save a lot of time, money, and frustration . . . but I can see NRTL A's point. If a customer came to me with a product and wanted it listed with my mark, before I put MY mark on it (which, historically, most consumers consider a quality indicator) I would make damn sure that the product was compliant, lest I incur the wrath if it fails. I wouldn't take anyone's word for it (report or not) and rubber stamp it. John Juhasz Fiber Options Bohemia, NY -----Original Message----- From: [email protected] [ mailto:[email protected] <mailto:[email protected]> ] Sent: Tuesday, October 24, 2000 6:58 AM To: [email protected] Subject: Got another beef about an NRTL.... Group, What about another scenario that I have been in with two NRTL's. For the sake of embarrassment,lets call them 'NRTL A' and 'NRTL B' Firstly any components or equipment recognised or listed by an NRTL are deemed 'acceptable' to OSHA so long as it is used as prescribed in its conditions of acceptability or use. so can I presume that as OSHA accepts any NRTL mark they are all of equal standing. Why is it then that NRTL A will not accept a power supply approved by NRTL B. The latter is true for NRTL B who will accept NRTL A's mark with no problems (in all cases the conditions of acceptability are followed) So long as the conditions of acceptability are followed and there are no engineering reasons for NRTL A to reject NRTL B's approval then what happens next. Is there any recourse or would we have to go to one NRTL and get the whole lot retested. If there is no engineering reason, can an NRTL reject anothers recognition just because it distlikes it or maybe sees it as competition! Has anyone else had a similar experience, if so what did you do to resolve it without paying out for more NRTL approvals on an already recognised component. Any comments would be greatly recieved. Regards, Duncan Hobbs, Product Safety Engineer Snell and Wilcox Ltd. ------------------------------------------- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. To cancel your subscription, send mail to: [email protected] with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Jim Bacher: [email protected] Michael Garretson: [email protected] For policy questions, send mail to: Richard Nute: [email protected] ------------------------------------------- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. To cancel your subscription, send mail to: [email protected] with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Jim Bacher: [email protected] Michael Garretson: [email protected] For policy questions, send mail to: Richard Nute: [email protected]
