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.

<strong>Membrane</strong> Filtration Regulations <strong>and</strong> Determination of Log Removal Value 141<br />

of membrane filtration. Examples of processes that would not be considered membrane<br />

filtration devices for the purposes of LT2ESWTR compliance include bag filters <strong>and</strong> cartridge<br />

filters using a fibrous filtration medium.<br />

3.3.2. Challenge Testing<br />

Since there are no uniform design criteria that can be used to assure the removal efficiency<br />

of a membrane process, challenge testing is required to demonstrate the ability of a treatment<br />

process to remove a specific target organism. The removal efficiency demonstrated during<br />

challenge testing establishes the maximum removal credit that a membrane process would be<br />

eligible to receive, provided that this value is less than or equal to the maximum LRV that can<br />

be verified by the direct integrity test, as described in the following section. The LT2ESWTR<br />

only requires product-specific challenge testing; once the removal efficiency has been<br />

demonstrated, additional testing is not required unless the product is significantly modified.<br />

Data from challenge studies conducted prior to promulgation of this regulation can be<br />

considered in lieu of additional testing at the discretion of the state. However, the prior<br />

testing must have been conducted in a manner that demonstrates removal efficiency for<br />

Cryptosporidium equivalent to or greater than the treatment credit awarded to the process.<br />

Challenge testing is discussed in detail in Sect. 4.<br />

3.3.3. Direct Integrity Testing<br />

While challenge testing can demonstrate the ability of an integral membrane process to<br />

remove the target organism, integrity breaches can develop in the membrane during routine<br />

operation that could allow the passage of microorganisms. In order to verify the removal<br />

efficiency of a membrane process during operation, direct integrity testing is required for all<br />

membrane filtration processes used to comply with LT2ESWTR. A direct integrity test is<br />

defined as a physical test applied to a membrane unit to identify <strong>and</strong> isolate integrity breaches<br />

(8–11). The rule does not m<strong>and</strong>ate the use of a specific type of direct integrity test, but rather<br />

performance criteria that any direct integrity test must meet. These criteria include requirements<br />

for resolution, sensitivity, <strong>and</strong> frequency (3):<br />

1. Resolution: The direct integrity test must be applied in a manner such that a 3-mm hole contributes<br />

to the response from the test.<br />

2. Sensitivity: The direct integrity test must be capable of verifying the LRV awarded to the<br />

membrane process.<br />

3. Frequency: The direct integrity test must be applied at a frequency of at least once per day.<br />

A control limit must also be established for a direct integrity test, representing a threshold<br />

response which, if exceeded, indicates a potential integrity problem <strong>and</strong> triggers subsequent<br />

corrective action. For the purposes of LT2ESWTR compliance, this threshold response must<br />

be indicative of an integral membrane unit capable of achieving the Cryptosporidium<br />

removal credit awarded by the state.<br />

3.3.4. Continuous Indirect Integrity Monitoring<br />

Because currently available direct integrity test methods require the membrane unit to be<br />

temporarily taken out of service, or are either too costly or infeasible to apply continuously,

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

Saved successfully!

Ooh no, something went wrong!