I am not aware of regulatory requirement that HW and SW numbers must be somehow synchronized, even for functional safety. However, whatever numbering scheme you choose must be traceable to the model and shipped serial number. This is becoming even more important a companies start using more of this for functionality that presents a risk of hazard. It is especially important when dealing with networked equipment and homeland security or NERC CIP.
My recommendation is to treat FW/SW revisions on your BOMs in exactly the same way you handle HW revisions. If you revise the part number, you do not necessarily roll a revision change all the way up to the top level model number. The exception may be if your software is somehow part of the factory configurable features. Then your people in the service department or configuration control may require this. In short this is mainly an internal matter for the company to sort out. Doug Douglas E Powell http://www.linkedin.com/in/dougp01 http://www.linkedin.com/in/dougp01 -----Original Message----- From: Brian Oconnell <oconne...@tamuracorp.com> Date: Fri, 9 Nov 2012 10:17:39 To: <EMC-PSTC@LISTSERV.IEEE.ORG> Reply-To: oconne...@tamuracorp.com Subject: Re: [PSES] Revisions The requirement to duplicate version numbers for hardware to software releases is an internal corporate decision, where the only relevance for compliance is that the character string used for the version number be identifiable and unique. Over the years MS, Apple, Cisco, etc have published software version numbering papers and some have even published internal corporate standards, but am not aware of any formal international standard. That is, code version numbering is whatever your company wants to do and how your internal libraries support parsing of version strings. These will get you started. http://semver.org/ http://en.wikipedia.org/wiki/Software_versioning Brian -----Original Message----- From: emc-p...@ieee.org [mailto:emc-p...@ieee.org]On Behalf Of Amund Westin Sent: Friday, November 09, 2012 12:04 AM To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: Revisions When making a HW change, the product top level revision number is stepping up. So, when a SW revision is introduced, how to avoid top level revision to be changed? SW revision is more likely than HW, and even SW update happens when product is placed on the marked (via GSM link) Any good ideas? #Amund - ---------------------------------------------------------------- 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://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <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://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
