I agree with you in principal Ken but technology in some fields is changing so fast that I don't think it is practical to say a standard should not need amending before 5 years..This could be limiting to new technologies and result in forced design compromises to meet obsolete requirements.
It takes so long to write many of these standards in the first place some are practically obsolete upon release! I have been involved in a committee trying to update a standard where we spent half a day wordsmithing sentences. This was a standard for a very simple product type and it has taken over a year and we are still not done so getting a standard released is no easy task................... Also many of the revisions end up being clarifications and not major changes. The committees cannot foresee every question which may come up when writing the standards so some sections are written very in very general terms and need further clarification as comments or questions are received as a result of real world use. This results in some of the amendments which are released I think.... In an ideal world I agree with you but in the real world I don't think it is possible............. From: [email protected] [mailto:[email protected]] On Behalf Of Ken Javor Sent: Wednesday, January 11, 2006 1:20 PM To: [email protected] Subject: Re: Making Standards Free, different take In 1992 MIL-STD-461D/462D were developed as revisions of MIL-STD-461C (1967 - 1986) and MIL-STD-462 (1967 - 1971). The long period with little or no change caused a lot of problems over the years. Since 1992 a "sunset" type of rule is in place that says a review process (not necessarily a revision) is necessary every five years to prevent obsolescence. I suggest that the opposite of that rule is necessary in the commercial worlds. No more than one revision every five years. If the thing has to be constantly updated and amended, it doesn't have the stature to be called a standard in the first place. - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] 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 [email protected] Mike Cantwell [email protected] For policy questions, send mail to: Jim Bacher: [email protected] David Heald: [email protected] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] 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 [email protected] Mike Cantwell [email protected] For policy questions, send mail to: Jim Bacher: [email protected] David Heald: [email protected] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc
