1D.ATTACHMENT_4_Reporting_Requirements.docx

DOCX document 30 KB Posted

Attached to
Non-Drinking Water, Soil, Sludge and Sediment Analysis Services
Solicitation number
W81XWH-18-Q-0070
Issued by

About this file

PWS Attachment 4

View the file

Other files

File Type Posted
4.W81XWH-18-Q-0070_Provisions&Clauses_Revised.docx DOCX document
7.Q_and_A_from_Vendors.docx DOCX document
5.SUBCONTRACTING_PLAN_Template.docx DOCX document
1A._Attachment_1_Parameters_and_Methods_19_Jan_2018.docx DOCX document
1.PerformanceWorkStatement.docx DOCX document
1B._Attachment_2_QA_QC.docx DOCX document
2.PricingSheet.xlsx XLSX spreadsheet
0.W81XWH-18-Q-0070_CombinedSynopsisSolicitation.docx DOCX document
6.Quality_Assurance_Surveillance_Plan.docx DOCX document
3.W81XWH-18-Q-0070_OCI_Certification.pdf PDF
1C.Attachment_3_Cpds_and_LOQs_19_Jan_2018.doc DOC document
4.W81XWH-18-Q-0070_Provisions&Clauses.docx DOCX document
Show all 12

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 4

REPORTING REQUIREMENTS AND DELIVERABLES

The contractor shall provide reports and other electronic data deliverables as part of its reporting/data package. Contractor data packages shall include the following documentation:

1. Complete/Final Data Package (Submitted via PDF), to include the following

0. Invoice for Services Rendered – Contractor shall submit original invoice, in a separate PDF from the analytical data package PDF. The invoice should reflect any penalties accrued for late reporting or missed hold times as outlined in the PWS of the contract.

0. All of the analytical report/data package items specified in the DoD QSM version the Contractor is currently accredited to.

0. On the analytical results pages (see Appendix A, DoD QSM v5.0, paragraph 4.0), the samples are to be identified by the APHC Lab ID and the corresponding field ID.

0. In addition to the items listed in Appendix A, DoD QSM v5.0, paragraph 5.0 (Sample Management Records), the data package shall include a copy of the appropriate pickup order form.

0. In the quality control data summary (DoD QSM v5.0, Appendix A paragraph 6.0), ICV and CCV spike concentrations and recoveries are also desired (but not required if not in the laboratory’s standard reporting format).

0. Stage 4 (previously, and equivalent to, Level IV) raw data elements are required in all data packages (see Appendix A, DoD QSM v5.0, paragraph 7.0). Raw calibration data and standards traceability data/information are required in all data packages.

0. Calculations sheets (that show all calculations and factors involved in calculating the final result) and method detection limit (MDL, or detection limit (DL)) summaries (showing individual results and calculated MDLs) must be provided (either in each data package, or in separate files, with updates provided as the information changes).

0. Concentration results are to be reported to 2 significant figures. Please identify any proposed exceptions, with justification, in the proposal.

0. The laboratory must have the capability to report (pdf and EDD) J-flagged estimates for confirmed detections between the method detection limit (MDL, = detection limit, DL) and the LOQ, unless not applicable to the method (e.g., pH). Reporting of J-flagged estimates is required for organic methods (all GC, GC/MS, LC, and LC/MS methods); metals methods (all ICP, ICP-MS, CVAA methods), perchlorate methods (LC/MS and/or IC-MS); and all IC methods. The J-flags will be applied for any positive detection (that meets method requirements for target analyte identification) between the MDL/DL and the LOQ (which is equal to or greater than the lowest calibration standard). J-flag will be defined as an estimated value.

0. For J-flagged detections between the MDL/DL and LOQ to be reported, all method target analyte identification criteria must be met. Examples are 1) the evaluation of the mass spectrum using the same criteria as with a detection at or above the LOQ; and 2) second column confirmation for GC methods, using the same criteria as with the confirmation of a detection at or above the LOQ. Discussions may take place between APHC and the contract lab regarding the usefulness of reporting J-flagged estimates for a particular method.

0. Non-detects are to be reported as “not detected” at the DoD QSM defined limit of detection (LOD), with a “U” flag, if the DoD QSM reporting format is being used for a particular method (will be most methods in this PWS). If LODs are not being used for reporting for a particular method/project, non-detects are to be reported as “not detected” at the LOQ, with a “U” flag. This reporting and flagging approach will be discussed between APHC and the contract lab(s) to ensure agreement on the definitions of reporting terms, and on the reporting and flagging approach.

Note: All Final Reports shall be archived at least five years after approval of the data package by the APHC COR/Technical Representative.

A. PDF Instructions for the Complete “FINAL” Data Package – This PDF document will include the entire data package as described above, minus the invoice. Please provide the invoice via PDF as a separate file from Final report. Final package PDF and invoice PDF are emailed to the following address:

usarmy.apg.medcom-phc.mbx.dls-contract-hardcopies@mail.mil .

These will be due no later than 2:00 PM Eastern Standard Time on the due date specified on the Pick-up Order. Naming convention of hard copy file and invoice should at least include the lab queue (acronym) and the PHC Pick up Order number, both of which will be provided on the documentation.

1. Preliminary Sample Analysis Results (pdf file) – Due one day before Complete Hard Copy Data Package PDF, for High and Top Priority Turn Around Time requests. These prelim PDFs will contain final, numerical results in appropriate units, for the requested parameters. Sample data shall be identified by APHC lab ID and field ID.

1. ELECTRONIC DATA DELIVERABLE (EDD) - The electronic data deliverable (EDD) and Final PDF report are REQUIRED to be derived from the same source. Information (sample ID, field ID, etc) and data (analytical results, units) must match. The process that generates the final report and EDD is REQUIRED to be validated to demonstrate that the process provides identical information and data.

Analytical Contract Lab Electronic Data Deliverables (EDD) Specifications Tab Delimited Text File Format

Electronic Data Deliverable (EDD)

The electronic copy of the Data Package is commonly referred to as the contract Electronic Data Deliverable or EDD.

The electronic data deliverable (EDD) and hardcopy reports are required to use and have the same information (sample numbers, field numbers, etc.) and data (analytical results, units). The process that generates the hard copy and EDD is required to be validated to demonstrate that the process provides identical information and data.

The EDD will contain quantitated results in appropriate units, or reporting limits, for the requested chemical parameters. Sample data shall be identified by US Army PHC lab numbers. Please note that the contractor shall transfer the data electronically from their lab to the US Army PHC lab using the file format described below:

EDD Naming Convention

The database containing the EDD should be named using the following format:

Pickup Order #.txt

Example 1. The EDD for Pickup Order 112 would be as follows:

P112.txt

Contents of the tab delimited EDD file

The following table lists the fields in the tab delimited file along with the data type, the maximum size in characters and a description. Note: The EDD file shall contains only data, DO NOT include a header row consisting of a list of the field names.

Tab Delimited EDD Line Specifications:

Field NameTypeSizeDescription
Lab_CodeText4APHC queue code for the contract lab which performed the analysis.
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Pickup_Delivery_OrderText6Pickup Order to which this sample belongs
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Sample_NumberText13The APHC sample number (assigned by APHC)
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
TestCodeText10The APHC LIMS Test Code
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Analyte_CodeText15The LIMS standard Analyte_Code, typically the CAS#
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Final_ResultNumber(Decimal)The numberic result (reound to the proper sig figs and decimal places)
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Text_ResultText250Text result. Not applicable to the results of most contracted Analyte Codes.
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Additional_QualifiersText8Additional qualifiers, for example any EPA Qualifiers.
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
UnitsText10Units of the results
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Dilution_FactorNumber(Decimal)Dilution factor applied to the observed result (already applied)
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Date_Time_AnalyzedDatemm/dd/yyDate the analysis was performed.
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
MDLNumber(Decimal)Method Detection Limit
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
Lab_Reporting_LimitNumber(Decimal)Lab Reporting Limit/Practical Quantitation Limit/Limit of Quantitation
DELIMITERTab character (ASCII 9) is used as field separator, even if proceeding field is null
LODNumber(Decimal)Limit of Detection
LINE TERMINATORSEach line is terminated by a carriage return (ASCII 13) and a line feed (ASCII 10)

File Delivery

The EDD file should be emailed to the following address:

usarmy.apg.medcom-aphc.mbx.dls-contract-data@mail.mil

Questions or comments regarding this guidance should be addressed to the COR.

File details come from the government source that posted it.