Point 3.7.2.4
Started by darsen, Dec 17 2008 11:52 AM
Hi All,
Currently I am updating our BRC system to its new version (5). Today I came a cross point 3.7.2.4; "There should be an documented procedure for updating and verifingen of specifications for each processtep...."
Does anyone know what they mean here. Any body has any example. Are they talking about specification of suppliers of specifications of out product???
I thank you all for youre answers
Currently I am updating our BRC system to its new version (5). Today I came a cross point 3.7.2.4; "There should be an documented procedure for updating and verifingen of specifications for each processtep...."
Does anyone know what they mean here. Any body has any example. Are they talking about specification of suppliers of specifications of out product???
I thank you all for youre answers
Using pH as a Critical Control Point (CCP) for Listeria Control
Record Cut Off Point for auditor checking
Cut off point for production code
SQF: Quick 10-Point Checklist for Managing Risks to Food Safety in a Storage & Distribution Environment
Point 7.1.5 Externally developed elements of the FSMS
[Ad]
Basically just a procedure on how you update specifications. Just document each step.
ex. modify spec, issue new version number, approved by qa manager, customer approves and signs and returns copy.
ex. modify spec, issue new version number, approved by qa manager, customer approves and signs and returns copy.
Thanks soda.
Has anyone else got an angle on this new requirement to share with Darsen?
Has anyone else got an angle on this new requirement to share with Darsen?
Dear Simon,
The relevant section header is -
The last bit is typically BRC ambiguous ! In other words the “specifications” can apply to almost anything. The choice of the word “process” in 3.7.2.4 is perhaps selected to match this ambiguity / generalisation Nonetheless, Soda’s interpretation of the general intent seems to match the statement on BRC website where they summarise changes (BRC call them enhancements ) from ver4 to 5, namely -
The net result seems to be to force any specification documents to be fully (or even more than) compliant with the documentation subclauses of 3.7.1 via a typical “documentation control” type procedure. Another movement towards ISO9000. I suppose everybody is doing this already .
Rgds / Charles.C
The relevant section header is -
3.7.2 Specifications
The company shall ensure that specifications exist for raw materials including packaging,
intermediate / semi- processed and finished products, (where relevant) and any product or service which could affect the integrity of the finished product.
The last bit is typically BRC ambiguous ! In other words the “specifications” can apply to almost anything. The choice of the word “process” in 3.7.2.4 is perhaps selected to match this ambiguity / generalisation Nonetheless, Soda’s interpretation of the general intent seems to match the statement on BRC website where they summarise changes (BRC call them enhancements
3.7.2 Specifications (6 clauses from 4)
• Manufacturing instructions shall comply with recipes and be fully implemented
• Documented procedure for amendment and approval and readily accessible to staff
The net result seems to be to force any specification documents to be fully (or even more than) compliant with the documentation subclauses of 3.7.1 via a typical “documentation control” type procedure. Another movement towards ISO9000. I suppose everybody is doing this already
Rgds / Charles.C
Using pH as a Critical Control Point (CCP) for Listeria Control
Record Cut Off Point for auditor checking
Cut off point for production code
SQF: Quick 10-Point Checklist for Managing Risks to Food Safety in a Storage & Distribution Environment
Point 7.1.5 Externally developed elements of the FSMS
Questions used to determine the critical control point
ISO 8573-1 Compliance-Point of Use
Point of use 0.01 micron compressed air filters
BRCGS V9 point 3.9.3
BRCGS Point 4.5.3, Compressed Air