1B.W81XWH-18-Q-0058_PWSAttachment_B.docx
DOCX document 35 KB Posted
- Attached to
- Drinking Water Analysis Services
- Solicitation number
- W81XWH-18-Q-0058
- Issued by
-
Department of the Army Medical Command
About this file
Performance Work Statement's Attachment B
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 0.W81XWH-18-Q-0058-0004_CombinedSynopsisSolicitation.docx | DOCX document | |
| 4.W81XWH-18-Q-0058-0004_Provisions&Clauses_Revised_01.16.2018.docx | DOCX document | |
| 1.W81XWH-18-Q-0058_PWS.pdf | ||
| 3.W81XWH-18-Q-0058_OCI_Certification.pdf | ||
| 0.W81XWH-18-Q-0058_CombinedSynopsisSolicitation.pdf | ||
| 1A.W81XWH-18-Q-0058_PWSAttachment_A.pdf | ||
| 5.SUBCONTRACTING_PLAN_Template.docx | DOCX document | |
| 2.W81XWH-18-Q-0058_Pricing_Worksheet.xlsx | XLSX spreadsheet | |
| 4.W81XWH-18-Q-0058_Provisions&Clauses.pdf |
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 B
REPORTING REQUIREMENTS AND DELIVERABLES
The contractor shall provide reports and other deliverables as part of its sample data package. Contractor data packages shall include the following documentation:
1. Final Data Package (Submitted via PDF) – Data package shall comprise the following items:
0. Invoice for Services Rendered – Contractor shall submit original invoice as a separate attachment from rest of package.
0. Case Narrative – A summary description of the analytical operations that occurred during sample receipt and analyses. Case narrative should include a discussion of quality control outliers and potential impact to the reported results.
0. Analysis report forms – These forms contain the results from measurement of those chemical parameters that are requested and specified in the Pickup Order/Delivery Order. Data are to be identified by the APHC Lab ID and the corresponding field ID.
0. Sample Receipt Documentation – sample receipt logs, temperature logs, pickup order forms, COC forms.
0. Quality Control Data Summary – This section shall include data from laboratory control samples, spikes, duplicates, method blanks, etc.
0. Raw data for all analysis measurements to include the following:
(a) Sample runs (all chromatograms, mass spectra, etc. as applicable), to include target compound identification/verification, dilutions, and manual integrations.
(b) Calibrations, including preparation of standards and standard traceability..
(c) Quality control sample runs (see 6(a) above).
(d) Any ICP, ICP/MS instrument adjustments to include periodic base line adjustments or adjustments in attenuation/sensitivity.
(e) Calculation Sheets to include column headings clearly describing information pertinent to particular analysis (i.e. data calculations, units, final values, etc.)
(f) Copies of the following logbook pages: sample preparation, sample digestion, moisture (if applicable).
(g) Reported data shall be rounded to two significant figures.
Note: All Final report packages shall be archived at last five years after approval of data package by 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 East Standard Time on the due date specified on the Pick-up Order. Naming convention of hard copy file and invoice should at least include APHC Pick-up Order number.
A. Preliminary Sample Analysis Results (pdf scan) – Due one day before Complete Hard Copy Data Package PDF for High and Top Priority Turn Around Time. These Data Results pdf will contain quantitated results in appropriate units, or quantitation limits, for the requested parameters. Sample data shall be identified by APHC lab IDs and field IDs.
B. Electronic Data Deliverable (EDD) - The electronic data deliverable (EDD) and Final PDF report are REQUIRED to use the same information (sample IDs, field IDs, etc) and data (analytical results, units). 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
File Delivery
The EDD file should be emailed to the following address:
usarmy.apg.medcom-aphc.mbx.dls-contract-data@mail.mil
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 Name | Type | Size | Description | ||
| Lab_Code | Text | 4 | APHC queue code for the contract lab which performed the analysis. | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Pickup_Delivery_Order | Text | 6 | Pickup Order to which this sample belongs | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Sample_Number | Text | 13 | The APHC sample number (assigned by APHC) | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| TestCode | Text | 10 | The APHC LIMS Test Code | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Analyte_Code | Text | 15 | The LIMS standard Analyte_Code, typically the CAS# | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Final_Result | Number | (Decimal) | The numeric result (round to the proper sig figs and decimal places) | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Text_Result | Text | 250 | Text result. Not applicable to the results of most contracted Analyte Codes. | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Additional_Qualifiers | Text | 8 | Additional qualifiers, for example any EPA Qualifiers. | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Units | Text | 10 | Units of the results | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Dilution_Factor | Number | (Decimal) | Dilution factor applied to the observed result (already applied) | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Date_Time_Analyzed | Date | mm/dd/yy | Date the analysis was performed. | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| MDL | Number | (Decimal) | Method Detection Limit | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| Lab_Reporting_Limit | Number | (Decimal) | Lab Reporting Limit/Practical Quantitation Limit/Limit of Quantitation | ||
| DELIMITER | Tab character (ASCII 9) is used as field separator, even if proceeding field is null | ||||
| LOD | Number | (Decimal) | Limit of Detection | ||
| LINE TERMINATORS | Each line is terminated by a carriage return (ASCII 13) and a line feed (ASCII 10) |
File details come from the government source that posted it.