Procedures for Detection and Quantitation
Technical Workgroup
Federal Advisory Committee on Detection and Quantitation Approaches and Uses in Clean Water Act (CWA) Programs
Summary of Technical Work Group Conference Call #12
November 9, 2005
1:00 – 3:00 p.m. EDT
- Action Items
- Welcome and Introductions
- Draft Meeting Summary
- EPA Management Update
- Purposes and Objectives of a Pilot Study
- Report from Multi-lab Subgroup
- Report from Single-lab Subgroup
- Discussion of Revisions to Descriptions of Characteristics
- Public Comment
- Wrap-up and Closing
- Attendance
- Back to Technical Workgroup home page
The next Technical Work Group call is scheduled for Wednesday, November 9, from 1:00 - 3:00 PM EDT.
Action Items
Richard Reding will
- Contact the Office of Resource Conservation and Reclamation to confirm there is not a written procedure for quantitation.
- Circulate via email a starter list of analytical methods tconsider for pilot testing.
Jim Pletl will further refine the description of characteristics based on comments from Technical Work Group members and redistribute a draft for discussion next week.
Ken Osborn will send to Triangle a definition for "Reliable Detection Limit" for the glossary of terms.
The Single Lab Subgroup (Richard Burrows - lead, Cliff Kirchmer, Ken Osborn, Brad Venner, David Kimbrough and John Philips) will review the revised purposes and objectives (see below), adding clarifications to #4, if appropriate. The subgroup will also revise its product in preparation for distribution to the federal advisory committee, placing particular emphasis on the policy questions needing discussion at the December 8-9 committee meeting.
The Multi Lab Subgroup (Larry LaFleur - lead, Bob Avery, Jim Pletl, Richard Rediske and Steve Wendelken) will revise its product in preparation for distribution to the federal advisory committee, placing particular emphasis on the policy questions needing discussion at the December 8-9 committee meeting.
Triangle will:
- Send to Technical Work Group members via email the revised purposes and objectives for the pilot study (see below).
- Send to Technical Work Group members via email the revised glossary of terms based on comments from the federal advisory committee and Technical Work Group for discussion at the November 16 meeting.
- Ask David Kimbrough for a definition for "Required or Regulatory Detection Limit" for the glossary of terms.
Welcome and Introductions
Robert Wheeler, facilitator, welcomed participants to the call at 1:00 PM EST. He conducted a roll call of Technical Work Group members and observers, and briefly reviewed the agenda for the meeting. Mr. Wheeler emphasized the purpose of the meeting was to hear an update from EPA regarding internal discussions, updates from the two subgroups on the status of products for the December federal advisory committee meeting, and to discuss modifications to descriptions of characteristics.
Mr. Wheeler confirmed with Richard Rediske that he did want to participate in the Multi-lab subgroup, and Mr. Rediske confirmed that was true.
Draft Meeting Summary
Mr. Wheeler asked for comments to the draft October 19, 2005 Technical Work Group meeting summary. Cliff Kirchmer, representing states, suggested revisions to the second paragraph on page 4. The group agreed that a bullet should be added to the group's discussion of revisions to the descriptions of characteristics indicating that the "Defensibility" category would remain, but would not be evaluated at this time. The group approved the October 19, 2005 summary, with revisions.
EPA Management Update
Richard Reding of EPA reported on feedback from management at EPA regarding the pilot study. He said one of the concerns is that there are currently too many procedures that the group is considering for pilot testing. Although he explained that the number of laboratories participating and the number of samples tested is what really drives the cost, the perception is that since the procedures are so similar there should be an attempt to narrow the procedures to a number that truly tests those that are different.
Purposes and Objectives of a Pilot Study
Members of the Technical Work Group discussed the purposes and objectives of the pilot study, using the list revised by the Multi-lab Subgroup. After considerable discussion, the group agreed to the following list of questions for purposes and objectives of the pilot study.
- Is the procedure clearly written?
- Can the data be easily processed in the laboratory?
- Was the procedure performed correctly?
- [Note: the Technical Work Group discussed at length the intent of this question. Members agreed that it was appropriate to have pre- and post-study questions. This question falls into the latter category. It is an attempt to evaluate the performance of the procedure as it was written. If there is great variation in the analysis of the performance of the procedure, the Technical Work Group agreed that could be due to variation in interpretation of the written procedure and/or that the procedure was poorly written.]
- Does the experimental design unduly influence the outcome of the study?
- Additional clarifying questions from the Multi-lab Subgroup include:
- Type of method (censored, uncensored, etc.)
- Works equally well if analyte recoveries are uniformly low, uniformly high, or highly variable
- Choice of outlier test (not mandated by procedure?)
- Number of different concentrations tested
- Number of replicates per concentration tested
- Magnitude of concentrations tested
- Relative relationship between spikes (0.25x, .5x, x, 2x, 4x, etc.)
- Number of laboratories
- Number of analysts per study or per laboratory
- Number of instruments per study or per laboratory
- Sample preparation
- Number of different days for which analyses are conducted per laboratory
- Time span over which analyses are conducted per laboratory (week, month, quarter, year)
- Number of data points per detection or quantitation limit calculation
- Additional clarifying questions from the Single-lab Subgroup include:
- To be added, if appropriate.
- Additional clarifying questions from the Multi-lab Subgroup include:
- Does the procedure achieve its intended purpose?
- Does the procedure work for all different types of analytical methods?
- Does the procedure work if applied to real world sample matrices? (This may also include a broader question evaluating how the procedure applies to real world matrices.)
Report from Multi-lab Subgroup
Larry LaFleur reported for the Multi-Lab Subgroup reviewing the subgroup progress report sent via email to Technical Work Group members. He identified specific questions the subgroup had for the Technical Work Group; he particularly focused on whether the general concepts for a study design made sense, and whether the step-wise approach appeared feasible.
Report from Single-lab Subgroup
Richard Burrows reported for the Single-Lab Subgroup saying that members had received minutes from the two conference calls the subgroup had. The subgroup started by thinking through the types of analytical methods the subgroup would like evaluated. The subgroup expressed concern with the amount of work involved in a pilot test, but did not go into great detail.
Mr. Burrows posed a priority policy question for the Technical Work Group's, and likely the federal advisory committee's consideration: Should the detection and quantitation procedure identify the absolute lowest possible level that a single lab can detect or quantitate; or should a procedure verify that the lab can actually detect or quantify at their stated detection or quantitation level? Or both?
The second question might also be phrased in the context of a procedure that demonstrates that the lab can achieve a specific (e.g. prescribed MQO) detection or quantitation. Mr. Burrows said these are two very different questions and have significant implications for future discussions.
Mr. Wheeler summarized the discussion and reminded the subgroups that they would need to complete a product for discussion and approval at the November 16 Technical Work Group meeting. The products would then be sent to federal advisory committee members in advance of the December meeting.
Discussion of Revisions to Descriptions of Characteristics
Mr. Wheeler asked Jim Pletl to briefly review the revisions he had made based on the last Technical Work Group conference call, including other comments received since that time. Mr. Pletl identified several revisions he had made based on comments, and asked the group to review a new question posed on page 2 under "Uncertainty Calculated." He asked members to review the revised document and send to him via email any final comments for discussion at the November 16 conference call.
Public Comment
There were no public comments.
Wrap-up and Closing
Mr. Wheeler reminded participants that the dates and times (all are EDT) of future Technical Work Group meetings are as follows:
- Wednesday, November 16 from 1:00 - 3:00 p.m.
- Wednesday, November 30 from 1:00 - 3:00 p.m.
- Wednesday, December 14 from 1:00 - 3:00 p.m.
- Wednesday, January 4, 2006 from 1:00 - 3:00 p.m.
- Wednesday, January 18, 2006 from 1:00 - 3:00 p.m.
Mr. Wheeler briefly noted the action items from the call, and said the agenda for the next call would focus on revisions to the descriptions of the characteristics, finalizing products from the subgroups, and revisions to the glossary of terms. He thanked Technical Work Group members for their time and closed the meeting at 3:00 p.m. EST.
Attendance
Technical Work Group Members
- States: Cliff Kirchmer and Bob Avery
- Environmental Laboratories: Richard Burrows and Steve Bonde
- Environmental Community: Richard Rediske
- POTWs: Jim Pletl and Ken Osborn
- Industry: Larry LaFleur and John Phillips
- US EPA: Richard Reding (Office of Water) and Brad Venner (Office of Enforcement and Compliance Assurance)
- Other Federal:
Triangle Associates: Derek Van Marter and Robert Wheeler
Observers
- Ken Miller (Consultant to EPA Office of Water)
- Gary McAllister
- Steve Wendelken (US EPA Office of Groundwater and Drinking Water)
![[logo] US EPA](http://www.epa.gov/epafiles/images/logo_epaseal.gif)