Laserfiche WebLink
in the process. It also includes appropriate statements of the DQOs (i .e. , the <br /> acceptable level of uncertainty in the information) . <br /> 2.3 SAMPLE COLLECTION <br /> Sampling procedures, locations, equipment, and sample preservation and <br /> handling requirements should be specified in the QAPjP. Further details on <br /> quality assurance procedures for field operations are described in Section 3 of <br /> this chapter. The OSW is developing policies and procedures for sampling in a <br /> planned revision of Chapter Nine of this manual . Specific procedures for <br /> groundwater sampling are provided in Chapter Eleven of this manual . <br /> 2.4 ANALYSIS AND TESTING <br /> Analytes and properties of concern, analytical and testing procedures to <br /> be employed, required detection limits, and requirements for precision and bias <br /> should be specified. All applicable regulatory requirements and the project DQOs <br /> should be considered when developing the specifications. Further details on the <br /> procedures for analytical operations are described in Section 4 of this chapter. <br /> 2.5 QUALITY CONTROL <br /> The quality ,assurance program should address both field and laboratory <br /> activities. Quality control procedures should be specified for estimating the <br /> precision and bias of the data. Recommended minimum requirements for QC samples <br /> have been established by EPA and should be met in order to satisfy recommended <br /> minimum criteria for acceptable data quality. Further details on procedures for <br /> field and laboratory operations are described in Sections 3 and 4, respectively, <br /> of this chapter. <br /> 2.6 PROJECT DOCUMENTATION <br /> Documents should be prepared and maintained in conjunction with the data <br /> collection effort. Project documentation should be sufficient to allow review <br /> of all aspects of the work being performed. The QAPjP discussed in Sections 3 <br /> and 4 is one important document that should be maintained. <br /> The length of storage time for project records should comply with <br /> regulatory requirements, organizational policy, or project requirements, <br /> whichever is more stringent. It is recommended that documentation be stored for <br /> three years from submission of the project final report. <br /> Documentation should be secured in a facility that adequately <br /> addresses/minimizes its deterioration for the length of time that it is to be <br /> retained. A system allowing for the expedient retrieval of information should <br /> exist. <br /> ONE - 3 Revision 1 <br /> July 1992 <br />