Attachment_6_-_Analytical_Contract_Lab_Electronic_Data_Deliverables_(EDD)_Specifications.pdf

Attachment 6: 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 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 numberic result (reound 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 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.

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