uick Overview This Standard Operating Procedure (SOP) describes the program necessary to ensure that all Deviations are documented, investigated with...
under certain circumstances the Beer Lambert relationship breaks down and gives a non-linear relationship
Diferencias en publicaciones de Op. 85 de Mauro Giuliani
John Cox tells the black side how to play against lesser tries by white.Descripción completa
John Cox tells the black side how to play against lesser tries by white.Descrição completa
SOP Lifting and RiggingFull description
Preparation,Approval and Control of SOP
SOP for iron ore miningFull description
skpDeskripsi lengkap
Modbus Gateway
isi makalah akreditasiFull description
Full description
SOPDeskripsi lengkap
pkmFull description
SELFFull description
sopFull description
Sop Tertib AdministrasiFull description
statement of purpose
Quality Management Documents & Templates
Deviations and non-Conformances
7.5
•
Prevent further deterioration deterioration and / or
•
Correct the event. Corrective Actions
The corrective action is the action necessary to recover the product / process / material / system, affected by the deviation. 7.6
Preventative Action
The preventive action is the action taken to address the root cause of the deviation and prevent reoccurrence of the event. 7.7
Trending of Deviations
Deviations must be trended to detect/predict reoccurrence problems and to monitor the effectiveness of the implementation of the corrective actions. The frequency of the trend analysis and reporting must be at least monthly.
8 8.1
PROCEDURE Deviation occurred
After deviations has occurred discoverer (originator) takes action, where required, in order to contain the effects of the event (immediate action). The originator informs line manager or supervisor. Originator and supervisor determine if the event requires a deviation report. In doubt QA must be consulted. Discoverer (originator) (originator) records the details of the occurrence in the area logbook. 8.2
Details of Deviation Section I (attached form)
The Originator and line manager complete complete section I of the deviation form. All details of the occurrence must be recorded also in the area logbook. This includes the date and time that the observation was made, a description of the event (what happened, where and when). The immediate action that was taken to contain the event must also be documented. Identify all batches affected by the deviation, if applicable. Date and sign Section I (originator and line manager). QA assigns a unique deviation number added added to the top of section I form (QA log file No). 8.3
QA Confirmation Section II (attached form)
QA records the date/time of the observation and a description of the non-conformance, non-conformance, together with any affected batch numbers (if applicable) in the log / database and confirms that in section II.
