Yes, objecting on Principle
Hello Sidney:
You are correct. I am questioning the validity of the direction given to us by our registrar. They stated we *must* include sales in our scope statement. Where is that requirement documented? Says who? I want to know if this requirement, benficial or not, is made up or if there is really proof. I want to know about the integrity of our registrar.
So why not require the follwoing too? Marketing, HR, training, finance, product engineering, process engineering, package engineering, test engineering, test (for crying out loud), wafer sort, shipping, QA, quality engineering, feild engineering, legal, failure analysis, demoboards, mark & pack, tape & reel, marketing communications, customer service (!!!!!), order entry, samples, literature, assembly, fabrication,
Why aren't ALL of these required to be in the scope statement on our certificate.
Do I need to go on? Why is it that *sales* must be in our scope statement but none of the above things I have listed have to be in our scope statement? And what good is sales without revenue recognition, order entry, etc. We could have the best sales team but if we don't get paid for our sales, who cares?
I don't think it is a good idea to have sales in a scope statement. I think a scope statement should be a general statetment of capabilities and not specific departments. If your organizaiton provides a sales service, then I can understand. But in the TS world, we are all making parts. So why is Sales more improtant than anything else?
Is there anything else that MUST be listed in our scope statement on our TS certificate?
I can't wait until TS goes away (but it may never.... too bad!)
Regards,
Dirk