|
This thread is carried over and continued in the Current Elsmar Cove Forums |
|
The Old Elsmar Cove Forums
![]() TL 9000
![]() Scope of TL 9000
|
| next newest topic | next oldest topic |
| Author | Topic: Scope of TL 9000 |
|
harvey unregistered |
The Telcos who started TL 9000 are now requiring in contracts that their suppliers are registered - for many types of product. Yet the categories of equipment for which metrics are specified is almost exclusively limited to network element products. Should a supplier of equipment outside the defined categories assume that this equipment will one day be included, and work towards registration? QuEST Forum say they do not intend to repeat the QS9000 situation where every supplier of automobile-related products must be approved. How will TL 9000 reflect the convergence between telecoms and other electronics? IP: Logged |
|
Douglas E. Purdy Forum Contributor Posts: 14 |
I do not know if this is in line with this topic but the questions asked reminded me of something I heard from a Sales & Marketing professional this week. This person said that many of the Telcoms are requiring their suppliers to be registered to QS-9000 as opposed to TL-9000. I was wanting to know how true this statement was? IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
I'd sure like more info as well. Sorry I can't help with the original question in this topic. IP: Logged |
|
Les Lovatt Lurker (<10 Posts) Posts: 2 |
As Quality Manager of a company who supplies into both Auto & Telecom markets I am confused with the QS / TL 9000 issue. Is TL-9000 a phantom or does it really exist?? Can anyone enlighten me or pass some relevant info on. Cheers! IP: Logged |
|
Casana Forum Contributor Posts: 22 |
Les, I recently attended an intro seminar for TL 9000. They said that its still basically in its infancy... there are only 25 or so companies registered to it, and these are driving it down to their suppliers. My personal guess is that it will not hit the smaller suppliers until at least a couple of years from now. But its definitely coming! I posted question similar to yours in the QS forum, you can read the answers I got at http://http://Elsmar.com/ubb/Forum1/HTML/000412.html -Casana IP: Logged |
|
The Fixer Forum Contributor Posts: 18 |
TL9000 Caution ! My company is part of the QUEST Fourm. We service anybody who's anybody in the Telecom world. We have not, however, chosen to register to TL-9000 yet. (We are ISO9001) There is an alarming trend developing. Those customers who have embraced initial TL registration (a dubious distinction at this early stage) are adding service requirements related to the TL metrics. We are having to provide data in quantity and format which the customer needs to support the TL metrics requirements. TL metrics implementation are costly and labor intensive. So, although we are not registered, it seems we are having TL compliance thrust upon us. The previous comments in this thread imply that companies are requiring suppliers to become registered. I can definately see that happening. I don't like the smell of this whole thing. A registered company must report specific data to the UTD (Univ. of Tx at Dallas) which is put into the MRD (Metrics Repository Database). IF the supplier can't provide the supporting data to allow the registered company to input the data, the company's registration is at risk. You figure it out. IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
Thanks for the caution! IP: Logged |
|
harvey unregistered |
It was my underatanding that TL 9000 registered companies need to obtain data from their CUSTOMERS to produce the TL 9000 metrics that are sent to UTD. After all, the metrics are intended to measure the company's success in satisfying its customer, in delivering reliable products, on-time delivery, responsive service, fault-free upgrades, etc. Where does the registered company's supplier have to supply data? IP: Logged |
All times are Eastern Standard Time (USA) | next newest topic | next oldest topic |
![]() |
|
Your Input Into These Forums Is Appreciated! Thanks!
