K.D. - ow, you just caused me a nightmare, had a flashback to being in your shoes this time last year. We also had over 100 QS9000 procedures and when we sat down to do TS decided to take a long hard look at all those procedures to see if we could dump, combine or whatever. We ended up doing a combination of dumping some procedures (for instance, we had procedures for some processes ALONG WITH control plans, and we killed the procedures and kept the control plans) - combining others - and outright eliminating a few. We went from over 100 to about 40. Kept some even though they were not required by TS for reasons cited in earlier post above - they were useful to our system, and the absence of them could result in non-conformances or just plain sloppy behavior on some people's part.
TS uses the "hey, you only need 7 procedures!" thing as a selling point, but I've yet to run across anyone who really operates with that few. Keep what is useful, dump it if it's something you ONLY had because QS required it, and make sure the procedures required by TS are included.
Interestingly, one of the things we ended up dumping was our Quality Manual, at least in the traditional sense. QS required the "traditional" Quality Manual where you spit back every element and make a brief statement about how you comply with it - TS lists various things that must be included in your "quality manual" but really DOESN'T say it has to be one of those QS type manuals. We declared (successfully, I might add) the entirety of our procedures, flow charts, controlled docs, etc as our "Quality Manual." We maintain one hardcopy of all that anyway, as backup to our electronic versions, so that one hard copy is our "Quality manual." I cite this example just to say when you start the process of figuring out what to keep and what to toss it's helpful to back up a few steps and get out of the QS9000 mindset - try to look at the standard fresh, as if you'd never seen one before, and put the QS9000 thinking out of your head temporarily.
Hope that helps
