17.12.2012 Views

Membrane and Desalination Technologies - TCE Moodle Website

Membrane and Desalination Technologies - TCE Moodle Website

Membrane and Desalination Technologies - TCE Moodle Website

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

346 N.K. Shammas <strong>and</strong> L.K. Wang<br />

prior regulatory approval. For the purposes of regulatory compliance, product-specific<br />

demonstration of Cryptosporidium removal efficiency is accomplished during challenge<br />

testing, although microbial monitoring may be conducted during a pilot study for additional<br />

verification of membrane performance at the discretion of the utility or if required by the<br />

state. Although additional microbial testing can be conducted for any pathogen of concern<br />

during piloting, typically, coliform bacteria, <strong>and</strong> sometimes heterotrophic plate count (HPC)<br />

are used as an indicator for microbial removal efficiency.<br />

2.3.4. Integrity Testing<br />

The importance of integrity testing necessitates that greater emphasis be placed upon<br />

integrity testing during piloting for applications of membrane filtration intended for<br />

regulatory compliance. For direct integrity testing, the membrane manufacturer should<br />

use a method approved or m<strong>and</strong>ated by the state. The st<strong>and</strong>ard direct integrity test<br />

sequences intended for the full-scale system should be incorporated into the pilot unit.<br />

Direct integrity testing should be conducted at least as frequently as required by the<br />

state for the full-scale facility. In the absence of a particular state requirement, it is<br />

generally recommended that direct integrity testing be conducted on a daily basis. If an<br />

integrity breach occurs during the piloting testing, then diagnostic testing <strong>and</strong> membrane<br />

repair techniques may also be practiced. Continuous indirect integrity monitoring can<br />

usually be accomplished using data that are collected during a typical pilot test program<br />

(e.g., turbidity or particle count data). However, any state requirements regarding data<br />

that must be collected for the purposes of continuous indirect integrity monitoring for<br />

the full-scale facility should also be implemented during the pilot test, <strong>and</strong> may be<br />

required by the state in any case.<br />

Note that because the number of membrane modules to which an integrity test is applied<br />

affects the sensitivity of the test (for both direct integrity testing <strong>and</strong> continuous indirect<br />

integrity monitoring), any control limits established for a full-scale system will generally not<br />

be applicable to a pilot unit, which typically utilizes only a small fraction of the number of<br />

modules in a full-scale membrane unit. Guidance on establishing full-scale system control<br />

limits for both direct integrity testing <strong>and</strong> continuous indirect integrity monitoring for the<br />

purposes of regulatory compliance are provided in Chap. 7.<br />

2.4. Report Development<br />

After the pilot test is complete, a report should be prepared to summarize the procedures<br />

<strong>and</strong> the test results. The pilot study report should contain sufficient detail to establish design<br />

parameters for the full-scale plant to the extent for which the testing was intended. Flux,<br />

chemical cleaning, backwashing, <strong>and</strong> integrity testing, should be addressed, where applicable.<br />

Collected water quality data should also be included with emphasis given to unanticipated<br />

test results. Details on the operational parameters for each filter run (i.e., between<br />

chemical cleanings) should be summarized. The state may also have specific requirements for<br />

the report if the piloting is required.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!