Giving the responsebility to the IT manager who links the document to the operating system can't be hold responseble if the system doesn't distribute it correctly, or can he?
If it is the IT manager's responsibility to ensure distribution and the system fails, the IT manager is responsible. Need more specifics to say for sure.
How can the buyer or planner verify that all information reaches the supplier correctly?
You can ask for a 'return receipt', however many times these are not returned. Use some 'common sense' here -- if a trial run shows the data was transmitted, go with that and use history to show that the transmission is 'highly reliable' -- from this you may not need a confirmation every time. A FAX is pretty reliable, for example, as is e-mail. Some people do call to confirm 'important' FAXes, but thats not 'the rule'.
QS does ask more than ISO - so you may be doomed to requiring a confirmation.
What you have to do is take a close look at your systems and determine what the exact failure modes are.
If your complaint is that you brought online some systems which were once pen and paper and since then there have been many system failures (or audit problems), then you did not adequately 'spec' and design the systems in the beginning -- and your testing was not comprehensive. This is not unusual - but it is often extremely expensive and difficult to 'fix' as it's after the fact and many people are now 'burned' (and thus not very trusting).
The most important parts of bringing 'new technology' online are planning, understanding requirements, understanding the current systems, etc. And then, adequate testing prior to implementation.
The extreme case is bringing an ERP system (like Peoplesoft, BAAN or SAP) online. Less difficult is bringing something online such as document control.
[This message has been edited by Marc Smith (edited 09 July 2000).]