Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Ciena (CIEN) -- Ignore unavailable to you. Want to Upgrade?

To: James Fulop who wrote (10594)	3/7/2001 1:40:41 PM
From: James Fulop	Read Replies (2) \| Respond to of 12623

As an addendum to my last post about ISO 9001 Certification, here is a link to more material about it. (courtesy of deep_green_smoke over on the Yahoo thread..) connect.ab.ca Edit: Evidently there may even be more to it per a poster on Yahoo whom I regard highly and who posted the following after reading the above link: >>This sounds more like protocol integration testing. I wish that was all 9001 was. That is the functional testing part of 9001 for communications processors. I think that should be sufficient. But ISO wants to know also how you qualify all your incoming components, what your design methodology is, what your acceptance testing is, if a component is discovered bad, can you track the lot it came from and go back to your supplier, .... Most companies hire in consultants that "gundeck" the paper work for them and prep the employees before an audit. At CS we had all day meetings prior to audits on how to answer auditors questions. To pass, you need your complete process documented and every employee trained in the process and what answers to give the auditors. For highly organized plants dealing mostly with process and hardware, they have most of that already, and it is just an audit. But for small entrepreneurial companies that have a lot of software content, it can be stiflying.<< messages.yahoo.com And: >>European Telcos wont touch equipment that doesnt have ISO approval. Countries over there make it a legal condition. Many US TELCOS also insist on it but make exceptions because to them it isnt a legal issue, it is a test of the vendor. If you dont put in the effort to pass ISO, it says something about your processes. But I havent seen a US TELCO insist on ISO for software, only the hardware. They know their own internally developed OSS systems would fail miserably in an ISO audit. They are almost as bad as banks and insurance companies. They are running code that was originally coded in assembler for machines that havent been manufactured in 2 decades. They keep running the stuff in hardware emulation because the original source code has been lost for 20+ years.<< messages.yahoo.com