A
4.3.2 says:
"Before submission of a tender, or the acceptance of a contract or order (statement of requirement), the tender, contract or order shall be reviewed by the supplier to ensure that:
a) the requirements are adequately defined and documented;..."
We have a product with a configurable subassembly, which is defined per system. However, this information does not always get here before the order is entered.
We know that we can build all configurations, since the differences are only # and spacing. However, the shop cannot finish building the job without the configuration information.
Question: Does 4.3.2 a) require that this system specific documentation be given before the order is entered, or can we have a "drop dead" date where this must be entered or the ship date wil be pushed out?
Any hints on how to arrange this would also be appreciated, as ramping production seems to lead to less, rather than more, documentation.
Thanks,
AJP
"Before submission of a tender, or the acceptance of a contract or order (statement of requirement), the tender, contract or order shall be reviewed by the supplier to ensure that:
a) the requirements are adequately defined and documented;..."
We have a product with a configurable subassembly, which is defined per system. However, this information does not always get here before the order is entered.
We know that we can build all configurations, since the differences are only # and spacing. However, the shop cannot finish building the job without the configuration information.
Question: Does 4.3.2 a) require that this system specific documentation be given before the order is entered, or can we have a "drop dead" date where this must be entered or the ship date wil be pushed out?
Any hints on how to arrange this would also be appreciated, as ramping production seems to lead to less, rather than more, documentation.
Thanks,
AJP