SOW_isotope_analysis_1.docx

1. GENERAL INFORMATION

1. Introduction / Background

The US Geological Survey California Water Science Center requires chemical analytical laboratory services for the analysis of lithium (total, 7Li, 6Li), boron (total, 10B, 11B), strontium (total, 86Sr, 87Sr) (hereinafter referred to as the “constituents”), in produced- water samples, which may contain up to ~50% oil and TDS up to 70,000 mg/L, and quality control samples through the year 2029. The laboratory analysis of produced-water samples is essential to generating the final products for this project.

1. Scope

The USGS expects to submit as many as 120 Sr, B, or Li samples per year; the number of samples may be as low as three samples per year, with at least one Sr, B, and Li isotope sample analyzed per year. Samples will be collected throughout the contract period and submitted to the Contractor for analysis. The samples are to be collected by USGS staff at multiple locations. Samples will be analyzed in the Contractor's laboratory within the holding times required by analytical methods. The USGS has established data-quality objectives (DQOs) that must be met to ensure that water-quality data can be used with confidence to assess the quality ground-water resources in the State of California.

1. WORK REQUIREMENTS

1. Technical Requirements and Criteria for Acceptance.

0. Analytical Methods: Methods selected for the analysis of the constituents in produced- water samples must be recognized by state or federal regulatory agencies (California State Water Resources Control Board Division of Drinking Water or U.S. Environmental Protection Agency), and must be documented, have undergone peer review, and published in a peer reviewed scientific journal. Each bid proposal must include the references for the proposed methods and published results. The contract laboratory shall document any modifications that are made to a method and demonstrate that the results provide equivalent or better performance than the unmodified method. The contract laboratory shall provide citable references for each analytical method used.

The methods in the table below would be acceptable for this contract, provided that the results satisfy the USGS data quality objectives and quality assurance requirements in this statement of work. USGS advises potential contractors that analytical methods may require modification or optimization to meet these requirements.

Statement of Work

Analyte Suggested analytical method

Reference and link

Initial Demonstration of Proficiency

Prior to analyzing environmental samples for the USGS, the contract laboratory shall show initial proficiency in each method on the basis of historical analytical data for each analyte. Proficiency will be judged on an evaluation dataset consisting of at least 15 blanks and 15 concentrations above the method reporting limit. The laboratory shall submit any data they deem relevant to this demonstration with their offer in response to this solicitation. Blank, spike, and replicate sample results that were blind to the analyst are preferred.

During the period of this contract, if the contract laboratory chooses to change equipment or analytical methods, the initial demonstration of proficiency must be repeated at the contract laboratory’s expense, prior to analyses of environmental samples.

0. Criteria for acceptance: USGS Program Data Quality Objectives (DQOs)

In addition to the QA/QC measures described later in this document, the USGS has established data-quality objectives (DQOs) that must be met to ensure that water-quality data can be used with confidence to assess ground-water chemistry in the State of California relative. These DQOs pertain to the required concentration range, laboratory bias, variability, and analyte recoveries listed below.

Concentration range. The required reporting limits for this contract are listed in the table below; these method reporting limits (MRLs) were selected based on human-health benchmarks for drinking water used by the US EPA and the State Water Resources Control Board. The precision or analytical uncertainty that the contract laboratory is required to achieve is also listed. The Contractor can use MRLs that have been determined to be equal to or higher than method detection limits (MDLs) calculated using 40 CFR 136 Appendix B, or a more robust method. The analytical precision of the contract laboratory must be established and published in peer reviewed literature.

Analyte

Units

Method Reporting limit Precision or reproducibility

1. Bias. The objective is that laboratory bias be less than the MDL for each target analyte, based on laboratory blank results.

1. Variability. The objective is that the laboratory variability be less than 20 percent relative standard deviation, based on daily continuing calibration checks and replicate spike analyses in clean matrices.

1. Analyte recoveries. The objective is that in laboratory spikes of reagent water, recoveries of target analytes must be within the control limits specified in the respective analytical methods.

Quality Assurance / Quality Control: USGS personnel will submit quality control (QC) samples in addition to environmental samples; each type of field QC sample will constitute up to 10 percent of all samples analyzed. These QC samples will include field blanks and replicate samples. Other quality control samples may be submitted as needed to meet the USGS objectives. The contract laboratory shall analyze all QC samples using the same procedures and methods as for the environmental samples.

Samples shall be analyzed by the contract laboratory within holding times required by analytical methods. Sample bottles and preservatives provided by the contract laboratory will be quality- control checked by the contract laboratory.

Laboratory capability must be demonstrated on a continuing basis through initial and continuing calibration, annual MDL study, annual precision and accuracy study, annual analysis of performance-evaluation samples, and laboratory reagent blank and spike analysis. The laboratory shall document these activities and maintain a schedule to assure that each requirement is fulfilled annually. In addition to these measures, routine QA/QC must also include monitoring of surrogate recoveries where applicable and the analysis of environmental samples spiked with the target analytes by the contract laboratory.

· Initial calibration. For initial calibration, the contract laboratory shall use a minimum of 3 standards of differing concentrations. Calibration procedures shall follow established analytical protocols and be consistent with recommendations of the instrument manufacturer. The contract laboratory shall perform an initial calibration each time the instrument undergoes set up, major disruption, or installation of new materials that could affect analyte recoveries. The full calibration shall be verified or redone any time that a routine calibration check fails to meet the control limits specified in the analytical method.

· Continuing calibration. Continuing calibration checks, consisting of a low-range or mid- range standard, shall be analyzed once at the beginning of each analytical day or once at the beginning of each batch of analyses, whichever is more frequent. If recoveries of continuing calibration check standards fall outside of the control limits specified in the analytical method, corrective action shall be taken before continuing to analyze environmental samples.

· Annual MDL study. The contract laboratory shall determine or verify the method detection limit (MDL) for each analyte at least annually through the analysis of at least seven low- concentration replicates analyzed over at least a 3-day period, following EPA-accepted methods described in 40 CFR 136 Appendix B, or using any other published method that has been accepted by the USGS technical representative for these analyses in water samples.

· Annual precision and accuracy study. The contracting laboratory shall provide to USGS a compilation of the quality-control data at least annually and summarize method performance by indicating the precision (expressed as percent relative standard deviation or other appropriate metric) and accuracy (as mean percent recovery or other appropriate metric) for each analyte.

· Annual analysis of a third-party PT sample. The contract laboratory shall provide the results of third-party blind proficiency testing (PT) for the target analytes at least annually; at least one of the PT samples for each analyte must be in the range of expected environmental concentrations.

· Laboratory Reagent Blanks. The contract laboratory shall prepare laboratory reagent blanks (LRBs) using an appropriate matrix that has no concentrations of target analytes above the MDL. A LRB shall be analyzed once at the beginning of each analytical day or once at the beginning of each batch of analyses, whichever is more frequent. The initial LRB results must be below the MDL or corrective action shall be taken before continuing to analyze environmental samples. Additional LRBs shall be analyzed, numbering one for every 20 analyses. If a target analyte is detected and identified in an LRB, quantitation of that same analyte in the environmental samples in that batch must be qualified. If the time needed for corrective action will cause samples to exceed holding times, the USGS must be contacted immediately.

1. Deliverables. USGS expects to submit as many as 120 samples per year; the number of samples may be as few as 3 sample per year including one Li, one Sr, and one B isotope analyses.

USGS personnel will collect and ship environmental and quality control samples by overnight delivery to the contract laboratory, Monday through Friday. The contract laboratory must be able to receive samples on those days. Samples will be shipped on ice, in coolers supplied by the contract laboratory. The USGS will pay for the cost of shipping the samples to the contract laboratory. USGS will provide the environmental samples and the source water used for field blanks only.

To be supplied by contract laboratory:

· Electronic version of an Analytical Request or Chain-of-Custody form to be sent in with samples that includes the contractor’s description of the analyses being requested and the USGS sample identification information and appropriate field information.

· All reagents and equipment needed to complete the contract analyses. All reagents must be ACS grade or better.

Liaison

A company representative/project manager shall be assigned to this contract. This person will serve as a Point Of Contact familiar with USGS requirements and procedures. This POC shall trouble shoot discrepancies in analytical requests forms, analytical requests, and sample information, make corrections, adjustments and updates to the contractor’s records at USGS request, and troubleshoot and catch errors prior to issuance of the final data package. The POC must respond to USGS inquiries, either by phone or email, within 1 business day.

Timeliness

Samples shall be analyzed within the holding times designated by the analytical methods, or within thirty (30) days of the sampling date, whichever is shorter. Hard copy data package and sample results and the electronic data in USGS format described below shall be sent to designated USGS personnel within thirty (30) days of analysis.

Data Delivery

The contracting laboratory shall provide the data deliverables in both hard copy and electronic format. The hard copy deliverable (data package) will include all results of sample analyses, including quality-control data (field blanks, source solution blanks, laboratory reagent blanks, , replicate analyses,), which will be reported as values of concentration or percent recoveries, identifying samples by contract laboratory sample numbers and USGS identification information (USGS site number, sample date, and sample time). The electronic deliverable will be sent in the format described in Attachment 1 to designated USGS project personnel; this format may change as needed by the USGS. The contract laboratory will work with USGS representatives to resolve any problems in the reporting format between the contract laboratory and the USGS. Results will be considered acceptable if the quality-control data listed above are provided with the sample results and after all data are reviewed by USGS project staff.

1. SUPPORTING INFORMATION

2. Place of Performance. Contractor’s Laboratory

2. Period of Performance: From Date of Award for Five Years

2. Government Furnished Property (GFP): No government property shall be furnished for this procurement.

2. Special Considerations. The contract laboratory shall comply with the Department of Interior Information Security Requirements (Attachment 2).

Attachment 1. Electronic Data Deliverable Requirement for Contracting Labs QWDATA tab-delimited batch-file format Data transmittal for automated data loading into the U.S. Geological Survey’s Water-Quality System (QWDATA) is done through the use of batch files. The batch processing utilizes two files: a sample-level batch file and a result-level batch file. In general, the sample-level file contains information about the sample-collection activity, such as the site identification number, sample collection date and time, and sample medium. The result-level file contains information about the individual analytical results. Each row in the result table contains the analytical result for one chemical constituent. The relationship between the two files is one-to-many; that is, a row of sample-level data may be related to many rows of result-level data.

The batch-format files are tab-delimited ASCII text files that require specific information to be displayed in specific fields. Each attribute must be separated from the previous attribute with a <tab>. Missing attributes must have a <tab> inserted. Padding with blank characters to create fields with full-length entries is not necessary. The files are related through a surrogate primary key called the sample integer (SINT). The description of the format of the sample-level and result-level files follows.

Sample-level batch file:

The format of the sample-level batch file is defined in table 1. The contract laboratory shall supply the data fields identified as mandatory fields in table 1. The tab-delimited format is designed to accommodate 22 attributes for a row of data. Many of these attributes are specific to field-collection activities and are not required for the batch processing of laboratory data.

Therefore, these attributes do not need to be stored in a laboratory’s database and will not have values transmitted in the batch files. However, the positions must be held in the file, so a <tab> must be inserted to separate these fields. The file containing the sample information is usually named ‘qwsample.date.time’. The date.time tag on the file name should be identical to the date.time tag on the paired result-level batch file. The date.time tag is usually the creation date.time of the batch files.

Table 1: Sample-level batch file format

Column order

Attribute name

Description

Integer(18)

Yes

LAB

Further information for the sample-level attributes follows:

Column 1: Sample integer (Mandatory, Primary Key) The laboratory must generate the sample integer. This integer is critical for linking the sample- level data to the result-level data. The maximum length for this integer is 18 digits and they must be in sequential order in the file. This field is used only for batch processing and is not stored in QWDATA.

Column 2: User code Leave blank, but it must be separated with a <tab>.

Column 3: Agency code

Leave blank, but it must be separated with a <tab>.

Column 4: Station number (Mandatory) Station number is an 8-digit or 15-digit number assigned to a sampling site. The field contains only numeric characters. The USGS personnel must supply the station number to the laboratory when samples are submitted for analysis.

Column 5: Begin date and time (Mandatory) Begin date and begin time describe when the sample was collected (or the begin time for a sample that is collected over a range of dates and/or times). The date format is yyyymmdd. The time format is hhmm. These fields are concatenated together (not separated by a <tab>). The USGS personnel must supply this information to the laboratory when samples are submitted for analysis.

Column 6: End date and end time Leave blank, but it must be separated with a <tab>.

Column 7: Medium code (Mandatory) Medium code is the medium from which the sample was collected (i.e. surface water, ground water, sediment, tissue). This field has a valid domain in the QWDATA software. The USGS personnel will supply a valid value for the medium code to the laboratory when samples are submitted for analysis.

Column 8: Lab number (NWQL) Leave blank, but it must be separated with a <tab>.

Column 9: Project number Leave blank, but it must be separated with a <tab>.

Column 10: Aquifer code Leave blank, but it must be separated with a <tab>.

Column 11: Sample type Leave blank, but it must be separated with a <tab>.

Column 12: Analysis status Leave blank, but it must be separated with a <tab>.

Column 13: Hydrologic condition Leave blank, but it must be separated with a <tab>.

Column 14: Hydrologic event

Leave blank, but it must be separated with a <tab>.

Column 15: Analysis source Leave blank, but it must be separated with a <tab>.

Column 16: Tissue sample identifier Leave blank, but it must be separated with a <tab>.

Column 17: Body part code Leave blank, but it must be separated with a <tab>.

Column 18: NWQL Lab sample comment Leave blank, but it must be separated with a <tab>.

Column 19: Field sample comment Leave blank, but it must be separated with a <tab>.

Column 20: Time-zone code Leave blank, but it must be separated with a <tab>.

Column 21: Time-datum reliability code Leave blank, but it must be separated with a <tab>.

Column 22: Sample collecting agency code Leave blank, but it must be separated with a <tab>.

Result-level batch file:

The result-level file includes analytical results and metadata for each analytical result. The contract laboratory shall supply the data fields identified as mandatory or conditional fields in table 2. The tab-delimited format is designed to accommodate 20 attributes for a row of data. The format of the result-level batch file is defined in table 2. The file containing the results information is usually named ‘qwresult.date.time’. The date.time tag on the file name should be identical to the date.time tag on the paired sample-level batch file. The date.time tag is usually the creation date.time of the batch files.

Table 2. Result-level batch file format Column order

Column name

Description

Format

Yes

LAB

result_cm_tx (where result_cm_tp = L)

Laboratory result comment

Varchar (300)

Conditional

LAB

result_cm_tx (where result_cm_tp = F)

Field result comment

Varchar (300)

3. LOOK-UP TABLE WILL BE PROVIDED BY USGS (SEE BELOW)

3. INFORMATION WILL BE PROVIDED BY USGS AND POPULATED BY CONTRACT LAB

Column 1: Sample integer (Mandatory) The laboratory must generate the sample integer. This integer is critical for linking the result-level data to the sample-level data. The maximum length for this integer is 18 digits and the integers must be in sequential order in the file.

Column 2: Parameter code (Mandatory) Each analytical result value must be reported with a parameter code that defines the constituent name, phase, reporting form, and reporting units. USGS personnel will provide a look-up table for use by the contract laboratory for the needed parameter codes.

Column 3: Result value (Mandatory) The result value is a numeric value produced by an analytical method for a constituent. The field is stored as float. The contract laboratory must put the method reporting limit in this field if the result is a non-detect. The ‘#’ sign can be used to tell the software that the value is “null” (missing) if appropriate. The contract laboratory must supply a null value qualifier code if the contract laboratory sends a null value.

Column 4: Remark code (Only mandatory if result value is a non-detect, or null and null- value qualifier code is not supplied) Remark codes provide additional information about the magnitude (or absence) of a value. A remark code is not required on every value; it is only required where it is needed to avoid misinterpretation of a value. If a remark is supplied, the remark code is viewed with the value for publication or data dissemination. A remark code of “<” is required for a non-detect. If the laboratory chooses to transmit null values, the laboratory must also provide a null value qualifier code (column 12) to identify why the value is missing. The remark codes are case sensitive. The remark codes are listed in table 3.

Table 3: Remark codes

Column 5: Quality-assurance code Leave blank, but it must be separated with a <tab>.

Column 6: Method codes (Mandatory) An analytical method is coded in the database by use of a five-character alphanumeric code in the method code field. The USGS personnel will supply the contract laboratory with a look-up table of the parameter code-method code pair that defines the chemical constituent and analytical method. When reported, method codes are all upper case.

Column 7: Result rounding code Leave blank, but it must be separated with a <tab>.

Column 8: Value-qualifier codes (Preferred) Value-qualifier codes provide additional qualifying information about the value. Up to three value qualifiers can be stored with any single result. The value qualifiers are case sensitive (all lower case). If a contract laboratory supplies more than one value qualifier code, the individual codes are concatenated (not separated by <tab>s). Value-qualifier codes are not mandatory. The value- qualifier codes are listed in table 4.

Table 4. Value-qualifier codes Value- qualifier codes

Description

Raised reporting Level

Method Problems

Rerun

Other

Column 9: Report level (Mandatory)

The report level is associated with the analytical method. This is usually the minimum value that is reported for the laboratory method at the time the sample is analyzed, based on some sort of statistical analysis of the method. If a value falls above this value, usually the value is reported without a remark code. If a report level is included in a batch file, a report-level type code must also be present. The USGS will confer with the contract laboratory liaison to make sure that this field is correctly populated.

Column 10: Report-level type code (Mandatory) The report-level type code identifies the type of report level used for the method that is associated with the report level. If a report level type code is included in a batch file, a report level must also be present. The domain for the report level type code is shown in table 5. The USGS will confer with the contract laboratory liaison to make sure that this field is correctly populated.

Table 5. Report level type codes

MRL

Blank

A blank report-level code should only be stored when no reporting level is stored. If a report level value is entered, a report level code must also be stored.

Column 11: Data-quality indicator code Leave blank, but it must be separated with a <tab>.

Column 12: Null-value qualifier code (Only mandatory if result value is null and a null value remark code is not supplied)

The laboratory has the ability to transmit null results for a given parameter code. A null result means that a requested analytical procedure was not performed or the result was not quantified. If the laboratory chooses to transmit null values, the laboratory must also provide a null-value qualifier code or a null value remark code (M, Table 3) to identify why the value is missing. The one-character code is case sensitive (lower case). The domain for the null-value qualifier code is listed in table 6.

Table 6: Null-Value Qualifiers

Null-Value Qualifiers

Description

Column 13: Preparation set identifier (Preferred if applicable) Preparation set identifier is a field used to store the set identification code of the preparation set at the laboratory. The field can be variable in length, up to a maximum of 12 characters. The field can contain mixed numeric and alpha characters. The preparation set identifier is not mandatory.

Column 14: Analysis set identifier (Preferred if applicable) Analysis set identifier is a field used to store the set identification code of the analysis set at the laboratory. The field can be variable length, up to a maximum of 12 characters. The field can contain mixed numeric and alpha characters. The analysis set identifier is not mandatory.

Column 15: Analysis date (Preferred if applicable) The analysis date field is used to identify the date when an analysis was performed at the laboratory. The format of the date is yyyymmdd. The analysis date is not mandatory.

Column 16: Preparation date (Preferred if applicable) The preparation date field is used to identify the date when a sample was prepared for analysis at the laboratory. The format of the date is yyyymmdd. The preparation date is not mandatory.

Column 17: Laboratory result comment (Only mandatory if appropriate) Result lab comment is a free-form text field to hold information from the lab about a result that cannot be defined by the coded information in the system. This field is reserved for laboratory use. Laboratories can send text up to 300 characters in length.

Column 18: Field result comment Leave blank, but it must be separated with a <tab>.

Column 19: Laboratory standard deviation Leave blank, but it must be separated with a <tab>. Column 20: Analyzing entity (Mandatory) The agency, organization, group, or company that analyzes the result is known as the analyzing entity. This is an eight-character field used to identify the entity that analyzed the value for the parameter and method code listed. The USGS personnel must supply the laboratory with the appropriate code for the analyzing entity.

The following examples are provided to illustrate how the sample-level batch file (table 7) and the result-level batch file (table 8) look with test data populated in the fields.

Table 7: Sample-level batch file format example

Sample integer (SINT)

User code

Agen cy code

Site #

Sample begin date/time

Sampl e end date/ time

Mediu m code

Lab # Pr oje ct co de

Aqui fer code

Sam ple Type code

Analy sis status code

-logic conditi on code

Hydro -logic event code

Tissu e ID

0200100

46244810430 200105211

WG

0200100

WS

0200100

WG

Table 8: Result-level batch file format exampleSample integer (SINT)

Parameter code

Result value

Remark code

QA

code

QW

method code

Rounding code

Value qualifiers

Report level Report level code

DQI

code Null value qualifier code

Preparation set number

Analytical set number

Analysis date

Preparation date Laboratory result comment Field result comm 0200100376 00940

IC022

0.08

200114801

AKTO01150A

20010530 20010528

0200100376

00945

IC022

0.11

20010530

20010528 Instrument run by KRM

0200100376 01020

IP107

20010530 20010528

0200100945 00631 0.020

COL41

0.005

200115903 1200101162A 20010611 20010608

00666 0.06

KJ005

s 0.06

00677 0.03

PHM04

0.01

0200100946 49258

GC095

0.10 r 200115903

GCMS162A

39350 0.2

GC096

0.10

GCMS162A

39371 0.08

GC054

xiz 0.01

GCMS162A

Attachment 1 - Information Technology Security Requirements Summary

1. Background Investigation: Not applicable.

1. Non-disclosure Agreement: Not applicable.

1. Training: Not applicable.

1. Personnel Changes: Not applicable.

1. Contractor Location: Not applicable.

1. Applicable Standards: Not applicable.

1. Asset Valuation: Not applicable.

1. Property Rights: Not applicable.

1. Independent Verification and Validation (IV & V): Not applicable.

1. Certification & Accreditation: Not applicable.

1. Internet Logon Banner: Not applicable.

1. Incident Reporting :

Contractor employees must report any computer security incidents (viruses, intrusion attempts, system compromises, offensive e-mail, etc.) which may affect Government data or systems in accordance with the DOI Computer Incident Response Guide. Report computer security incidents to the USGS Point Of Contact.

1. Quality Control (Malicious Code) :

All electronic data files shall be free of malicious code.

1. Self Assessment: Not applicable.

1. Vulnerability Analysis: Not applicable.

1. Logon Banner: Not applicable.

1. Security Controls :

The Contractor shall be responsible for Information Technology security for all non-government- owned systems used in the development of and systems intended for eventual delivery to the USGS/DOI in fulfillment of contract requirements. This includes information technology, hardware, software, databases, networks, and telecommunications systems.

1. Contingency Plan: Not applicable.