9. Disinfection
9.13 TROUBLESHOOTING BACTERIA PROBLEMS
When troubleshooting for bacteria problems, it is important to find
the source and cause of the problem, not just treat the symptoms.
Use a systematic approach when troubleshooting. Don't attack the
problem randomly. Don't change components because they are
suspected, or the new components could also be contaminated.
Also, there could be more than one source or cause of
contamination. They all must be found and eliminated one by one
to prevent recontamination.
Contaminated upstream systems and components will contaminate
downstream. To troubleshoot properly, start analysis at the
furthest downstream point and work upstream, but take correct
actions starting at the front end of the system and working
downstream. This prevents recontamination downstream.
Before starting troubleshooting, gather all the data available about
maintenance techniques, procedures, quality control, and any
recent changes. Take water samples and have them assayed for
indications of the extent of the contamination.
The goal is to find the cause of the problem, correct it, and make
sure it does not happen again.
To troubleshoot properly, you must:
• Gather all test data and maintenance records.
• Identify all the systems that can contribute to bacteria
growth.
• Examine the symptoms.
• Analyze all the information.
• Locate the source and cause of the contamination.
• Take corrective action.
9.13.1 Gather Data
Maintenance records can point out faulty or missing procedures
and document activities as they take place. For instance, if a filter
was supposed to be replaced monthly and the records show this
was not done, then the filter could be the main source of the
problem.
Previous test results can display potential problem areas so you can
go back and test these areas again to see if levels at these points
157-1278-916, Rev A 9-43
March 2004
To Next Page
Loading...
