Hello All, My experiences with purchasing 2 copies of the Estonian standards are similar to those who have replied.
It’s very rare that another person is reading a standard at the same time as I am. As a matter of fact, it is very difficult to get our engineers to take an interest in reading and understanding the standards at all, so it is very unlikely we’ll ever violate the copyright regulations. Best Regards, Brian C. ________________________________ Brian Ceresney Regulatory Lead Delta-Q Technologies Corp. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ________________________________ From: Kunde, Brian [mailto:brian_ku...@lecotc.com] Sent: Wednesday, March 04, 2015 10:53 AM To: EMC-PSTC@LISTSERV.IEEE.ORG<mailto:EMC-PSTC@LISTSERV.IEEE.ORG> Subject: [PSES] Estonian Standards MultiUser License Please forgive me if this is a repeat. Does anyone have experience buying Standards from Estonia using the MultiUser Licence? Do they still use FileOpen to control what computers can open the files like they do with a single user license or do they have a way of limiting how many different computers can open the files at one time? I would like to put the standards files on our Intranet server so those in R&D can reference then when needed. We may have 20 engineers who may reference a standard it would be rare that more than 2 would ever open the files at the same time. I’m trying to figure out how their MultiUser License system works so I can purchase the right number of users. Does anyone have experience with this? Is there a better solution or cheaper source for EN standards? Regards, The Other Brian ________________________________ LECO Corporation Notice: This communication may contain confidential information intended for the named recipient(s) only. If you received this by mistake, please destroy it and notify us of the error. Thank you. - ---------------------------------------------------------------- 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 <emc-p...@ieee.org<mailto:emc-p...@ieee.org>> 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 <sdoug...@ieee.org<mailto:sdoug...@ieee.org>> Mike Cantwell <mcantw...@ieee.org<mailto:mcantw...@ieee.org>> For policy questions, send mail to: Jim Bacher <j.bac...@ieee.org<mailto:j.bac...@ieee.org>> David Heald <dhe...@gmail.com<mailto:dhe...@gmail.com>> - ---------------------------------------------------------------- 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 <emc-p...@ieee.org> 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 <sdoug...@ieee.org> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
