EPA Region 5 Electronic Data Deliverable (EDD) Comprehensive Manual Version 4.3 EQuIS Professional version 7 EDD format version 3.0.17 February, 2020

* Q \

vagi

PRO^tC

EPA Region 5

11 West Jackson Blvd. Chicago, IL 60604

Electronic Data Deliverable (EDD)

Comprehensive Manual Version 4.3

V

February, 2020

EQuIS Professional version 7 t EDD format version 3.0.17

-------
THIS PAGE LEFT BLANK INTENTIONALLY

Region 5 EDD Comprehensive Specification Manual	United States

Version 4.3	2	Environmental Protection Agency

-------
ACKNOWLEDGEMENTS

This document was originally prepared for EPA Region 5 by the John A. Volpe National Transportation
Systems Center (Volpe Center). This document was reviewed and edited by David Wilson and Mary
Tierney of EPA Region 5; William Halloran and Joseph Monaghan of the Volpe Center; and John
Hennessy and Ellen Baptiste-Carpenter of Battelle Laboratories, Inc. Other technical reviewers from
EPA include Patricia Scott, Chemist, EPA Region 5; Douglas Yeskis, Geologist, EPA Region 5; Luanne
Vanderpool, Geologist, EPA Region 5; Anthony Kahaly, EPA Region 5, RCRA Division; and Andy
Crossland, Hydrogeologist, EPA, Region 2. Other reviewers include Steve Losier of the Volpe Center;
Janet Magurn, Scot Weaver and Dave Abercrombie of EarthSoft, Inc.; Rosanna Buhl of Battelle
Laboratories, Inc.; and Izak Maitin of the New Jersey Department of Environmental Protection.

EarthSoft Inc. developed the Electronic Data Processor (EDP) and reviewed the EDD format to assure its
technical accuracy.

This documentation was reviewed and updated by Diann Cox-Tramel (Region 2), and John Canar, Region
5 and updated on January, 2020 to meet the standards and requirements of EPA Region 5.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	i

United States
Environmental Protection Agency

-------
DISCLAIMER OF ENDORSEMENT

Reference herein to any specific commercial products, process, or service by trade name, trademark,
manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or
favoring by the United States Government. The views and opinions of authors expressed herein do not
necessarily state or reflect those of the United States Government, and shall not be used for advertising or
product endorsement purposes.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	ii

United States
Environmental Protection Agency

-------
EXECUTIVE SUMMARY

The purpose of this specification manual is to provide detailed instructions on how to report
environmental data electronically to the United States Environmental Protection Agency (EPA) Region 5.
The types of data can be reported electronically include, for example, data generated during site
characterization and investigation phases, data recorded when installing monitoring wells, and monitoring
data that is routinely collected from a variety of media. This manual describes the procedural and
formatting requirements you need to know to submit your Electronic Data Deliverable (EDD) to the EPA
Region 5 Superfund Division.

This EDD Comprehensive Specification manual describes the requirements for reporting all current and
future environmental data to EPA Region 5. EPA recognizes that some information about data collected
in the past may not be readily available and, by reducing the requirements for electronic basic data, is
endeavoring to strike a balance between minimizing the amount of effort involved in inputting
information and maximizing the ability to document remedy progress. Environmental data collected and
analyzed prior to the initial use of this EDD Comprehensive specification manual should be reported
using the EPA Region 5 "Basic Manual for Historic Electronic Data". The reporting requirements of the
"Basic Manual for Historic Electronic Data" are a subset of this comprehensive EDD Comprehensive
specification manual.

The EPA Region 5 EDD is comprised of five groups: Field. Lab. Basic. Vapor Intrusion and Facility.

The first group of the EDD is the Field, which contains the data for the point of contact, site information,
Locations, alternation Position for locations, Location Parameter, as well as drilling activities, lithology,
well installation, well construction and well segment, geotechnical sample information, water levels,
water table, downhole logging methods, Extraction and Injection wells, Soil Gas survey data, and a
Sample Parameter. Those files are:

Field- the folloing three files can be submitted once unless there are new/ additional locations to the site

¦	Data Provider (named as "EPAR5DATAPROVIDER_v3" is the point of contact for EDD and
file providing the information)

¦	Subfacility (named as "EPAR5SUBFACILITY_v3", which is the general information about the
site)

¦	Location (named as "EPAR5LOC_v3", which is the information regarding the sampling
locations)

This time we added two optional sections below the EPAR5LOC_v3 section:
EPAR5AlternatePosition_v3 and EPAR5LocParam_v3.

¦	Alternate position (named as "EPAR5 AlternatePosition_v3", which is the alternate position of the
sampling locations).

¦	Location Parameter (named as "EPAR5LOCPARAMV3", which is the location parameter of the
sampling locations).

The following files are included in the Field section, which contains the field data, please submit the data
when they are available:

¦	Drilling Activity (named as "EPAR5DRA_v3", which is the information about drilling activities
resulting form the soil borings.)

¦	Lithology (named as "EPAR5LTH_v3", which is the lithology information for the borings.)

¦	Well (named as "EPAR5EPAR5WEL_v3", which contains the monitoring well information
related to well instruction)

¦	Well Construction (named as "EPAR5WSG_v3", which contains the well construction details
and well segment data.)

Region 5 EDD Comprehensive Specification Manual
Version 4.3	iii

United States
Environmental Protection Agency

-------
¦	Geology Sample (named as "EPAR5GSMP_v3", which contains the geotechnical sample
information)

¦	Water Level (named as "EPAR5GWTR_v3", which contains the information on water levels
measured from the soil borings or wells.)

¦	Water Table (named as "EPAR5TBL_v3", which contains the information pertaining the water
table)

¦	Downhole Logging (named as "EPAR5DHP_v3", which contains the data from downhole
logging methods such as Cone Penetrometer Tests and geophysics.)

¦	Extraction and Injection Wells (named as "EPAR5EIW_v3", which contains the data about
extraction and Injection wells)

¦	Soil Gas (named as "EPAR5EPAR5SoilGas_v3", which contains the imports soil gas survey
data.)

¦	Sample Parameter (named as "EPAR5SAMPLEPARAM_v3", which contains the samples
information.)

In most cases, the vast majority of the electronic data submitted over the life of the project, and that will

be submitted on a reoccurring, routine basis, will be lab data.

Lab

The Lab EDD files contain data related to chemistry field measurements, sample collection information,

sample tests and result QC. The Lab EDD files are the:

•	Sample (named as "EPAR5SMP_v3", which contains the information about sample collection)

•	Test Result (named as "EPAR5TRS_v3", which contains the information concerning analytical
tests and lab results performed on samples.)

•	Test Result QC (named as "EPAR5TRSQC_v3", which contains the information about the
analytical test performed on samples with quality control data elements)

•	Batch (named as "EPAR5BAT_v3", which contains the data that related the individual samples to
the batch identifier.)

Basic Submittals

The Basic EDD files contain historical operation and maintenance (O&M) data. The EDD files are the:

•	Basic Location (named as "EPAR5_BasicLOC_v3", which contains the information about
sampling locations from historical data)

•	Basic Water Level (named as "EPAR5_BasicWTR_v3", which contains the information
regarding groundwater level measurements)

•	Basic Chemistry Sample (named as "EPAR5_BasicChem_v3", which contains the information
about sample collection)

•	Basic Geology (named as "EPAR5_BasicGEO_v3", which contains the information about
geology data)

Vapor Intrusion

¦	Building Address (EPAR5_VI_BLDG_Address_v3)

¦	Building Inspection (EPAR5_VI_Bldg_Inspection_v3)

¦	Building Parameter (EPAR5_VI_Bldg_Parameter_v3)

¦	Vapor Intrusion Location (EPAR5_VI_LOCATIONS_V3)

¦	Vapor Intrusion Outdoor Locations (EPAR5_VI_Outdoor_Locations_v3)

¦	Vapor Intrusion Samples (EPAR5_VI_Samples_V3)

¦	Vapor Instrusion Test Results (EPAR5_VI_TestResultsQC_v3)

¦	Vapor Instrusion Batches (EPAR5_VI_Batches_v3)

Region 5 EDD Comprehensive Specification Manual
Version 4.3	iv

United States
Environmental Protection Agency

-------
F aciltiv

The facility data includes an electronic base map of the site property, one file containing general
information about the site and about the point of contact for the EDD, and a file containing data
pertaining to site sampling locations.

¦ Files (named as "Files_v3", which contains any supplementary information about site such as a
base map, a cover letter about the data, data provider, or the site sampling information.)

Of the files listed above, the Lab and Field files that most data providers will submit will be the Well,
Water Level, Extraction Injection Wells, Sample, Test/Result QC files. The Test Result with QC and
Batch files will only be submitted in those rare cases where EPA requires QA/QC data in electronic
format. The Extraction/Injection Well file will only need to be submitted for sites with extraction or
injection wells.

The process for creating Field, Lab, and/or Facility EDDs are shown in Figures E-l and E-2, respectively.
The process begins by identifying the software tool that will be used. Many software tools, such as text
editors, word processors, spreadsheets, and databases, are capable of creating EDDs. Because
spreadsheets and databases are designed to enter and manage data, however, they are generally preferred
for creating EDDs. The production of the data tables will normally be a collaborative effort between
laboratories and environmental contractors. The laboratories will typically produce the test/result tables
while the contractors normally will produce all of the other tables.

As shown in Figures E-l and E-2, decision points are included in the EDD creation process to ensure that
Field EDD files have been submitted for a site, as well as to prevent redundancy when getting ready to
submit Lab EDDs. For example, one of the Field EDDs called the SUBFACILITY file, which contains
data describing the site and site contact information, should generally only be reported once (unless, as
previously noted, a change occurs). Similarly, another Field EDD file, the Location file, which contains
locational data, typically only needs to be reported once. The only time a Location EDD file would be
resubmitted is if the data changed in some way. For example, if settling occurs at a site over time, a
resurvey of site monitoring wells may be warranted. If the survey results show changes in the elevations
of the monitoring wells, the Location file would have to be resubmitted.

The final step before submitting an EDD to EPA Region 5 is to check it using the Electronic Data
Processor (EDP) software application that is currently provided on the EPA Region 5 website (located at
https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission). This software
application will identify any formatting errors in the files that must be corrected prior to submitting the
EDD.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 v

United States
Environmental Protection Agency

-------
Figure E-l Process flow diagram for the creation and checking of Field, and Lab EDD files

Region 5 EDD Comprehensive Specification Manual
Version 4.3	vi

United States
Environmental Protection Agency

-------
Figure E-2 Process flow diagram for the creation and checking of Field EDD files

Region 5 EDD Comprehensive Specification Manual
Version 4.3	vii

United States
Environmental Protection Agency

-------
THIS PAGE LEFT BLANK INTENTIONALLY

Region 5 EDD Comprehensive Specification Manual	United States

Version 4.3	viii	Environmental Protection Agency

-------
TABLE OF CONTENTS

EXECUTIVE SUMMARY	iii

1.	INTRODUCTION TO THE EPA REGION 5 ELECTRONIC DATA DELIVERABLE (EDD)	1

2.	GENERAL HDD REPORTING REQUIREMENTS	3

2.1	File Formats	3

2.2	Field Data Submittals	3

2.3	Lab Data Submittals	7

2.4	Vapor Intrusion	7

2.7	File Naming Convention	9

2.8	Data Integrity Rules	12

2.9	Definition of a Facility, Site, and Location	14

2.10	Reporting Null Values	14

2.11	Valid Values	15

2.12	Reporting Re-Tests	16

2.13	Reporting Non-Detects	16

2.14	Reporting Tentatively Identified Compounds	17

2.15	Data Types	17

2.16	Data Entry Tools Provided to Create the EDD Files	18

2.17	Using the Electronic Data Processor to Check EDD Formatting	20

2.18	Submitting Your EDD to EPA Region 5	20

2.19	Examples of Field, and Lab EDD Files	23

3.	FORMATS FOR Facility Files and Field Files	30

3.1 Facility EDD Files	30

3.2. Field Files-DATAPROVIDER	31

3.3	SUBFACILITY EDD File	31

3.4	Location EDD File (EPAR5LOC_v3)	32

3.5	Alternate Position	37

3.6	Location Parameter	39

3.7	Drill Activity EDD File	40

3.8	Lithology EDD File	41

3.9	Well EDD File	42

3.10	Well Construction EDD File	44

3.11	Geology Samples EDD File	46

3.12	Water Levels	48

3.13	Water Table EDD Files	51

3.14	Geology Down Hole Point Data EDD File	53

3.15	Extraction - Injection Well (EPAR5EIW_v3) EDD File	53

3.16	Soil Gas Data EDD File	55

3.17	SAMPLE PARAMETER	56

4.	FORMATS FOR LAB FILES	57

4.1	Lab Sample EDD File	57

4.2	Lab Test Results EDD Files	60

4.3	Lab Test/Result with QC Data EDD File	64

4.4	Lab Batch Data (EPAR5BAT_v3) EDD File	71

5.	VAPOR INTRUSION	72

5.1	Vapor Intrusion Building Address EDD File	72

5.2	Vapor Intrusion Building EDD Files	73

5.3	Vapor Intrusion Building Parameters EDD File	75

5.4	Vapor Intrusion Locations EDD file	76

5.5	Vapor Intrusion Outdoor Locations EDD file	78

Region 5 EDD Comprehensive Specification Manual
Version 4.3	ix

United States
Environmental Protection Agency

-------
5.6	Vapor Intrusion Sample EDD file	79

5.7	Vapor Intrusion Test Result QC	81

5.8	Vapor Intrusion Batch EDD File	90

6. TECHNICAL SUPPORT	92

Region 5 EDD Comprehensive Specification Manual
Version 4.3	x

United States
Environmental Protection Agency

-------
LIST OF TABLES

Table 2-1 General information on the files that comprise the first three files in the Field EDD section	3

Table 2-2 General information on the files that comprise the field files in the Field EDD section	5

Table 2-3 General information on the files that comprise the Chemistry EDD	7

Table 2-4 General information on the files that comprise the Vapor Intrusion EDD	8

Table 2-5 EDD File Naming Formats	11

Table 2-6 Examples of how to report null values	14

Table 2-7 Cross-reference between the valid value tables in appendix and the EDD files	15

Table 2-8 Example of reporting re-tests	16

Table 2-9 Example of reporting non-detects	17

Table 2-10 Example nomenclature for TIC reporting	17

Table 2-11 Datatype descriptions	17

Table 2-12 Instructions for producing tab-delimited text files from some software packages	19

Table 3-1 Files (Files_v3) structure	30

Table 3-2 Data Provider (EPAR5DataProvider_v3) File Structure	31

Table 3-3 SUBFACILITY (EPAR5SUBFACILITY_v3) data file structure	32

Table 3-4 Location Data (EPAR5LOC_v3) File Structure	33

Table 3-5 Alternate Position (EPAR5AlternatePosition_v3) file data structure	37

Table 3-6 Location Parameter	39

Table 3-7 Drill activity (EPAR5DRA_v3) file data structure	40

Table 3-8 Lithology (EPAR5LTH_v3) file data structure	41

Table 3-9 Well (EPAR5WEL_v3) file data structure	42

Table 3-10 Well construction (EPAR5WSG_v3) file data structure	44

Table 3-11 Geology samples (EPAR5GSMP_v3) file data structure	46

Table 3-12 Water Level (EPAR5GWTR_v3) file data structure	49

Table 3-13 Water table (EPAR5TBL_v3) file data structure	52

Table 3-14 Geology Downhole Point (EPAR5DHP_v3) File Data Structure	53

Table 3.14a Example of downhole point data file	53

Table 3-15 Extraction-Injection Well (EPAR5EIW_v3) file data structure	54

Table 3-16 Soil Gas (EPAR5SoilGas_v3) Survey file data structure	55

Table 3-17 Sample Parameter (EPAR5SAMPLEPARAM_v3) Survey file data structure	56

Table 4-1 Lab sample (EPAR5SMP_v3) file data structure	57

Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure	60

Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure	65

Table 4-4 Lab batch file (EPAR5BAT_v3) data structure	71

Table 5-1 Vapor Intrusion Building Address data structure	72

Table 5-2 Vapor Intrusion Building data structure	74

Table 5-3 Vapor Intrusion Building Parameters data structure	75

Table 5-4 Vapor Intrusion Location data structure	76

Table 5-5 Vapor Intrusion Outdoor Locations data structure	79

Table 5-6 Vapor Intrusion Samples data structure	79

Table 5-7 Vapor Intrusion Test Result QC file data structure	81

Table 5-8 Vapor Intrusion Batches file data structure	90

LIST OF FIGURES

Figure E-l Process flow diagram for the creation and checking of Field, and Lab EDD files	vi

Figure E-2 Process flow diagram for the creation and checking of Field EDD files	vi

Region 5 EDD Comprehensive Specification Manual
Version 4.3	xi

United States
Environmental Protection Agency

-------
Figure 2-1 Relationships between Lab file data structures	13

Figure 2-2 Facility component definitions	14

Figure 2-3. Example Field EDD ready for conversion to text file	23

Figure 2-4. Example Lab EDD ready for conversion to text file	23

Figure 2-5. Examples of QC data fields in a Chemistry EDD	24

Figure 2-5. Examples of QC data fields in a Chemistry EDD (continued)	26

Figure 2-6. Example Field EDD ready for conversion to text file	27

Extraction Injection Wells	29

Region 5 EDD Comprehensive Specification Manual
Version 4.3	xii

United States
Environmental Protection Agency

-------
THIS PAGE LEFT BLANK INTENTIONALLY

Region 5 EDD Comprehensive Specification Manual	United States

Version 4.3	xiii	Environmental Protection Agency

-------
1. INTRODUCTION TO THE EPA REGION 5 ELECTRONIC DATA DELIVERABLE (EDD)

The EPA Region 5 Superfund Division has developed an electronic data management system to improve
how environmental data from Superfund sites are acquired and managed. The system will accelerate the
review of environmental data submittals, improve service to the regulated community, and enhance the
protection of the environment and the public. A vital element in the electronic transfer of environmental
data is the submittal of data in a standardized, "computer-friendly" format. The specifications and
formatting requirements for the EPA Region 5 EDD were developed to facilitate the transfer of data from
data providers to the EPA.

NOTE: This EDD Comprehensive Specification manual describes the requirements for reporting all
current and future environmental data to EPA Region 5. Environmental data collected and analyzed
prior to the initial use of this EDD specification manual should be reported using the EPA Region 5
"Basic Manual for Electronic Data". EPA recognizes that some information about data collected in the
past may not be readily available and, by reducing the requirements for electronic historical data, is
endeavoring to strike a balance between minimizing the amount of effort involved in inputting
information and maximizing the ability to document remedy progress.

The EPA Region 5 EDD is in part based on standard EDDs used in applications developed by EarthSoft,
Inc. However, the format is designed to be software-independent and easy to achieve. Any spreadsheet,
database, or text editor can be used to create the EDD files. Examples of applications that can be used to
create Region 5 EDDs include Access, FoxPro®, Excel, and Notepad.

Basically, the EDD is a series of files used to report data. For example, one file is used to report location
data while another is used to report samples collected at a location. Multiple files are used to eliminate
the need to report redundant data. For example, the data for a location (e.g., coordinates and elevations)
are reported once in the location (EPAR5LOC_v3) file. Many years of sampling and analytical data may
be reported for that location without having to submit the LOC file again.

This specification manual includes examples of EDD files populated with data. In addition, several EDD
templates are currently available on the EPA Region 5 E-Data website
(https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission') for loading data into the
EDD format. The website also contains a no-cost software program, the Electronic Data Processor (EDP)
that needs to be used to check EDD files before they are submitted to EPA Region 5. The EDP is a single
application that checks all EDD files and provides a much easier user interface for identifying and
correcting errors.

This EDD Comprehensive Specification Manual discusses EDD submittals in three separate sections:

• General reporting requirements and submission process are discussed in Section 2.

• The Facility and Field file structures (i.e.data provider, subfacility, location, water level) are defined
in Section 3.

• The Lab file structures are defined in Section 4. In most cases, lab data accounts for the majority of
data that is reported.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 1

United States
Environmental Protection Agency

-------
Each file must be reported exactly as defined in these sections. Any deviations will result in loading
errors.

EPA Region 5 expects all fields referred to as "Required", "Not required" or "If available" to be filled in.
If data for fields referred to as "If available" meaning the data can be reported when available, such as the
result values and the unit. If users reported the result values, it is preferred to repor the unit as well. Data
fields indicated as "Not required" meaning the fields are not required fields. These fields were only
included so that other EPA regions or states could use the same EDD but have slightly different data type
requirements.

Currently, EPA is working to finalize EDD requirements that would be national standards for Superfund
data for all 10 EPA Regional offices. When this national Superfund EDD is finalized, data providers who
have already begun submitting data according to the EPA Region 5 format will be given time to transition
to any national format changes.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	2

United States
Environmental Protection Agency

-------
2. GENERAL EDD REPORTING REQUIREMENTS

2.1 File Formats

With the exception of the electronic base map, all data from the EPA Region 5 data providers must be
reported as text files. Each data field must be separated either by tabs (tab-delimited) (indicated by the
suffix "txt" on the file name) or comma-delimited (indicated by the suffix "csv" on the file name). One
other option is to enclose each field in double quotation marks (") (indicated by the suffix "txt" on the file
name). However, because using double quotation marks to delineate fields is typically more time
consuming (unless the data are already in this format), it is anticipated that this method will not be widely
used. Data fields containing no information should not be simply omitted. Instead they should be
represented by the delimiter of choice, e.g., by two tabs in tab-delimited files or two commas in comma-
delimited files (see example in Section 2.16). The maximum length of each text field is indicated in
parentheses in the EDD tables shown in Sections 3 and 4. If the information is less than the maximum
length, there is no need to add spaces to the record to ensure that all spaces are used. Maximum length
requirements imply that the field can be no longer than the specified number of characters. However, it is
completely acceptable to fill the field with fewer characters than the maximum number. Each record ~
which is the term used for each line of information ~ must be terminated with a carriage return/line feed
(created by pressing the "Enter "key in a text editor).

2.2 Field Data Submittals

The Field data submittal consists of the initial data submittal and the field data including: Data Provider
(DataProvider), Subfacility, and the Location (Location) file including facility center point in latitude
longitude coordinate, and the field data including drilling activities, lithology, well installation, well
construction and well segments, geotechnical sample information, water levels, water table, downhole
logging methods, extraction and injections wells, and Soil gas survey data. The first three files in the
Field submittals provide information pertaining to the site, the site EDD contact, and site sampling
locations. These files generally only need to be submitted once at the beginning of the project. These files
only need to be resubmitted if any changes occur. Examples of changes that would require resubmittal
include changes in site contact information or location data that changes after being resurveyed. New
sampling locations established after the initial Location file submittal will require a new submittal with
data only pertaining to the new locations. Table 2-1 provides general information on the first three files
in the Field EDD section, sometimes; data provider will submit a cover letter or base maps in the Files_v3
in the Facility secion. Table 2-2 provides general information on the field data files in the Field EDD
section.

Table 2-1 General information on the files that comprise the first three files in the Field EDD
section

File Type

File Name

Created By

Contents

What makes a
row of data
unique?

Dependenc
e of other
files on
these data

Data
Provider

EPAR5DATAPROVIDER
_v3.txt (or csv)

Data
Provider

Information about the
data provider

DataProvider

Not

applicable

Region 5 EDD Comprehensive Specification Manual
Version 4.3 3

United States
Environmental Protection Agency

-------
File Type

File Name

Created By

Contents

What makes a
row of data
unique?

Dependenc
e of other
files on
these data

Subfacility

(Section 3.3)

EPAR5 SUBFACILITY^
3.txt (or csv)

Data provider

One-time definition of
site including EPA
Region 5 data
providers' contact
information.

Facilitycode,
subfacilityname

subfacility_task_
code... etc

The location

file cannot

be loaded

without

properly

referenced

subfacility

(facilitycod

e).

Location

(Section 3.4)

EPAR5LOC_v3.
txt (or csv)

Data provider's
surveyor

One entry for each
location on a site
including a facility
center point. Contains
elevation, coordinate
and general locational
data. Facility center
point is required for
the initial submittal.
Data should only be
reported once for a
location.

sysloccode

Sample,
water levels,
field

measuremen
ts, and
extraction
well data
can only be
reported for
locations
that are
defined in
this file.

Alternate
Position

EP AR5 AlternatePo sition

Data Provider's
surveyor

The entries for the
alternate coordinates
from EPAR5LOC_v3
are moved to this
section, and it is an
optional section.

Sysloccode

Location
Parameter

EPAR5LOCPARAMV3

Data Provider's
surveyor

Location parameter
entries, optional

Sysloccode

Data provider, Subfacility, and location files are generally only need to be submitted once at the
beginning of the project, along with the Files_v3 file in the Facility section.

What makes a

Dependence

File Type

File Name

Created by

Contents

row of data

of other

unique?

files on

these data

Region 5 EDD Comprehensive Specification Manual
Version 4.3 4

United States
Environmental Protection Agency

-------
File Type

File Name

Created by

Contents

What makes a
row of data
unique?

Dependence
of other
files on
these data

File_v3

The site's base map in
Lat/Long and the file
format must be in .dxf or
drawing (.dwg) or ArcGIS
Shape files.

Another file type can be
documents or pdf, such as
cover letter or any kind of
documents.

Data provider

#1. Basemap of sites
in (.dxf), drawing
(.dwg), or ArcGIS
Shape File.

#2. Cover letter or any
documents in .pdf or
doc files

Not applicable

Not

applicable.

Field EDD submittals contain data obtained during subsurface investigations at the site. When submitting
the Field EDD, all field EDD files for which information is available should be submitted. The Field
EDD includes files for Drilling Activity (EPAR5DRA_v3), lithology data (EPAR5LTH_v3), general well
information (EPAR5EPAR5WEL_v3), well construction information (EPAR5WSG_v3), geology sample
data (EPAR5GSMP_v3), general information about the water table (EPAR5GWTR_v3), Water Table
(EPAR5TBL_v3), downhole logging methods point data (EPAR5DHP_v3), extraction and injection well
(ExtractionlnjectionWells), soil gas survey data (SoilGas). Unlike the Lab EDD, where submittals are
typically submitted on a cyclic basis, in most cases the Geology EDD is submitted only once. Additional
Geology EDDs are submitted only if new geology data are collected.

Sites reporting data from monitoring wells installed or from geology-related activities completed more
than one year prior to the date of data submittal are not required to submit the Field EDD files - unless
the monitoring wells are being used for operation and maintenance (Q&M) monitoring. However, for all
newly installed monitoring wells or current geology data collection efforts (i.e., within one year from the
date of data submittal), data providers must submit all applicable Field files as detailed in Section 3.

Table 2-2 provides general information on the files that make up the field files in the Field EDD. Detailed
instructions for creating the Field EDD files are provided in Section 3, "Formats for Field Files".
Instructions for submitting your EDDs to EPA Region 5 are presented in Section 2.15.

Table 2-2 General information on the files that comprise the field files in the Field EDD section

File Type

File Name

Created By

Contents

What makes a row of
data unique?

Dependence
of other files
on these data

Drilling
Activity

(Section 3.5)

EPAR5DRA_v3.
txt (or csv)

Data

provider's
geologist

General Information
regarding soil
borings.

sysloccode
drillevent

None.

Lithology

(Section 3.6)

EPAR5LTH_v3.txt
(or csv)

Data

provider's
geologist

Lithology data for
the borings.

sysloccode
startdepth

None.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 5

United States
Environmental Protection Agency

-------
File Type

File Name

Created By

Contents

What makes a row of
data unique?

Dependence
of other files
on these data

Well

(Section 3.7)

EPAR5 WEL_v3.
txt (or csv)

Data

provider's
geologist

General information
regarding well
installation.

sysloccode

Well

construction
and water
level data can
only be
reported for
wells that are
defined in
this file.

Well

Construction

(Section 3.8)

EPAR5WSG_v3.txt
(or csv)

Data

provider's
geologist

Well construction
details recorded
during well
construction and
well segments.

sysloccode

segmenttype

startdepth

enddepth

material_type_

code

depth unit

None.

Geology
Samples

(Section 3.9)

EP AR5 GSMP_v3.
txt (or csv)

Data

provider's
geologist or
laboratory

Contains

geotechnical sample
information

Sysloccode,
geosamplecode

None.

Water Level
(Section 3.10)

EP AR5 G WTR_v3. tx
t (or csv)

Data

provider's
field
sampling
team(s)

Contains water
levels measured
from he soil borings
or wells

sysloccode
measurementdate

None.

Water
Table

(Section 3.11)

EPAR5TBL_v3.
txt (or csv)

Data

provider's
geologist

General information
pertaining to water
table.

sysloccode
type

None.

Downhole
Point (CPT)
Data

(Section 3.12)

EPAR5DHP_v3.
txt (or csv)

Data

provider's
geologist

Results of all
downhole logging
such as CPT,
resistivity, or other
geophysical logs.

sysloccode

depth

param

None.

Extraction-
Injection Well
(Section 3.13)

EPAR5EIW_v3.
Txt (or csv)

Data

provider's
field
sampling
team(s)

Data that relates to
any extraction wells
that are operating as
part of the remedial
action and injection
wells.

sysloccode

startmeasurementdate

endmeasurementdate

None.

Soil Gas
(Section 3.14)

EP AR5 SoilGas_v3.
Txt (or csv)

Data

Provider's
geologist

Results of
information
regarding the soil
gas

sysloccode

None

Sample
parameter

EPAR5 S AMPLEP A
RAMV3

Data
Provide's
sampling
team(s)

Define the sample
parameter

Syssamplecode



Region 5 EDD Comprehensive Specification Manual
Version 4.3	6

United States
Environmental Protection Agency

-------
2.3 Lab Data Submittals

Lab EDDs are submitted after each round of sampling and include the following types of files: chemistry
sample information (EPAR5SMP_v3), Test Result (EPAR5TRS_v3), test/results with QC
(EPAR5TRSQC_v3), batch information (EPAR5BAT_v3).

Table 2-3 provides general information on the files that make up the Lab EDD files. Detailed instructions
for creating the Lab EDD files are provided in Section 4, "Formats for Lab EDD Files". Instructions for
submitting your EDDs to EPA Region 5 are presented in Section 2.15.

Table 2-3 General information on the files that comprise the Chemistry EDD

File Type

File Name

Created
By

Contents

What makes a row
of data unique?

Dependence of
other files on
these data

Sample

(Section 4.1)

EP AR5 SMP_v3.
txt (or csv)

Data

provider's
field
sampling
team(s)

One row for
each sample
collected at the
site.

syssamplecode

samplematrixcode

sampletypecode

samplesource

sampledate

Tests/results QC
and batch data can
only be reported
for samples that
are defined in this
file.

Test Result
(Section 4.2)

EPAR5TRS_v3.txt
(or csv)

Data

provider's
field
sampling
team (s)

Contains data
concerning
analytical tests
and results
performed on
samples.

Syssamplecode

Labanlmethodna

me

Analysisdate

None

Test/ Result
with QC
Data

(Section 4.3)

EPAR5TRSQC_v3.tx
t (or csv)

Data

provider's
contractor
lab(s)

Test/Result file
with additional
fields for QC
data.

syssamplecode
lab_anl_method_
name

analysisdate

analysistime

totalordissolved

testtype

casrn

None.

Batch

(Section 4.4)

EPAR5BAT_v3.
txt (or csv)

Data

provider's
contractor
lab(s)

Data that relate
the individual
samples to the
batch identifier

syssamplecode
lab_anl_method_
name

analysisdate

analysistime

totalordissolved

testtype

test batch type

None.

2.4 Vapor Intrusion

Test Result QC (VITestResultQC), and Batch (VI Batch) data are only for Vapor Intrusion data. If the
data is collected for Vapor Intrusion, then it is not required to submit the same Sample (Sample), Test
Result QC (TestResultQC), and Batch (Batch) data in the Chemistry group. Table 2-4 provides general
information on the Vapor Intrusion EDD files. Detailed instructions for creating the Vapor Intrusion
EDD files are provided in Section 5, "Format for Vapro Intrusion Files".

Region 5 EDD Comprehensive Specification Manual
Version 4.3	7

United States
Environmental Protection Agency

-------
Table 2-4 General information on the files that comprise the Vapor Intrusion EDD

File Type

File Name

Created By

Contents

What makes a row of
data unique?

Dependenc
e of other
files on
these data

Vapor
Intrusion
Building
Address

EPAR5_VI_Bldg_A
ddress_v3

Data
provider's

Vapor
Intrusion
team (s)

Address and contact
information for the
building

Buildingcode
Buildingname

None

Building data

EPAR5_VI_Bldg_In
spection_v3

Data
Provider's

Vapor
Intrusion
team (s)

Building specific
data

Buildingcode
Buildingname

None

Vapor
Intrusion

Task
Parameters

EPAR5_VI_Bldg_Pa
rameters_v3

Data
Provider's

Vapor
Intrusion
team (s)

Additional
Sampling
parameters collected
in the field and not
analized in the lab

Taskcode
Paramcode

None

Vapor
intrusion
Locations

EPAR5_VI_Location

s_v3

Data
Provider's

Vapor
Intrusion
team (s)

Sampling location
data

Sysloccode



Vapor
intrusion
Outdoor
location

EPAR5_VI_outdoor_
locations_v3

Data
Provider's

Vapor
Intrusion
team (s)

Outdoor location
data

Sysloccode



Vapor
Intrusion
Samples

EPAR5 VI Samples

_v3

Data
Provider's

Vapor
Intrusion
team (s)

Sampling
Information for
Vapor Intrusion

Data provider
Sys loc code
Sys sample code
Sample matrix code
Task code

Sampling company cod
e

Sample start date

Tests/results

QC and
batch data
can only be
reported for
samples that
are defined
in this file.

Vapor
Intrusion Test
Result QC

EPAR5 VI TestRes
ultsQC_v3

Data
Provider's

Vapor
Intrusion
team (s)

Test Result

Sys sample code
Lab anl method name
Analysisdate
T otalordissolved
Columnnumber
Test type

None

Vapor
Intrusion
Batches

EPAR5 VI BATCH
ES_V3

Data
Provider's

Vapor
Intrusion
team (s)

Batches

Syssamplecode
Labanlmethodname
Analysisdate
T otalordissolved
Columnnumber
Testtype
Test batch type
Test batch id

None

Region 5 EDD Comprehensive Specification Manual
Version 4.3	8

United States
Environmental Protection Agency

-------
2.7 File Naming Convention
-Sign and Submit

After using the tools outlined above to resolve all of the issues in a set of Data Files the data is ready to be
submitted for loading into the EQuIS 7 database. The Sign and Submit tool was designed to facilitate
submittal of data to EQuIS Enterprise EDP. Sign and Submit option packages the data files with the
correct naming convention which allows easy submittal of data packages. Use of the Sign and Submit
feature requires a user name and password which can be obtained from the EPA Region 5 database
administrator. Please email to canar.iohn@epa.gov for the information.

To use the "Sign and Submit" feature, after data files have been loaded and all of the errors have been
resolved,

1. Select Sign and Submit from the Application Menu. This will open the Sign and Submit window.

Sign and Submit
User Name:
Password:
Facility ID

Save Passv.'ord

¦E3-

Save

Figure 13: Sign and Submit Window

2.	Enter your User Name and Password, and select the facility ID from the drop down that applies to the
data package being submitted. If the Facilty ID does not exist, users can send a request to Region 5
contact to add it to the list.

3.	Click the Save button, and verify if the facility you selected is corrected:

Region 5 EDD Comprehensive Specification Manual
Version 4.3	9

United States
Environmental Protection Agency

-------
Sign and Submit

£3

EPAR5 Sign And Submit

Are you sure this is the correct facility?

Yes

Figure 14: verify the facility

4. Click "Yes". Users will be prompted to provide a filename and location where you would like to save
the file. The Sign and Submit feature will save an archived ("zipped") file named with the current date,
a period, the Facility ID, a period and the Format File name used to create the EDDs. (Example file
name: '20160811. MID000000001 EPAR5.zip"). The contents of the Zipped file include text files named
for the sections of the format used to create them.

5. Select Save. Once the zipped EDD Package has been saved the following screen will appear.

er Name: username

EQuIS Professional

J!
IC

EDD Signed and Saved

Figure 15: saved the EDD file

6. Select OK

After the zipped file has been created the EDD Package is ready to be submitted to your regulator for
loading into EQuIS Professional EDP or EQuIS Enterprise EDP.

-Each EDD file naming convention

Each file, except the base map file, must be named according to the following convention:

EDDFileFormat_v3.txt (or .csv)

This is the same file name as it is shown in th EPA Region 5 EDD fomat. The name of the site base map
file should include the site name and EPAID and be saved in .dxf format.

Table 2-4 describes the naming formats and for the various Initial, Chemistry and Geology EDD files.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 10

United States
Environmental Protection Agency

-------
Table 2-5 EDD File Naming Formats

File
Type

File Contents

EDD File Name

Submittal
Type

Facility

File

Sitename.DXF, *.dwg, or shape files from ArcGIS, or
Sitename.doc files from MS WORD for cover letters

Non-
Recurring

Field

Data Provider

EPAR5DataProvider v3.txt

Initial

Field

Subfacility

EPAR5 Subfacility v3.txt

Initial

Field

Location

EPAR5LOC v3.txt

Initial

Field

Drill Activity

EPAR5DRA v3.txt

Non-
Recurring

Field

Lithology

EPAR5LTH v3.txt

Non-
Recurring

Field

Well

Wel_v3 .txt

Non-
Recurring

Field

Well

Construction

EPAR5WSG_v3.txt

Non-
Recurring

Field

Geotechnical
Sample

EPAR5GSMP_v3.txt

Non-
Recurring

Field

Water Level

EPAR5GWTR v3 .txt

Recurring

Field

Water Table

EPAR5TBL v3.txt

Non-
Recurring

Field

Down Hole
Point (CPT)
Data

EPAR5DHP_v3.txt

Non-
Recurring

Field

Extraction -
Injection Well

EPAR5EIW_v3.txt

Recurring

Field

Soil Gas Data

EPAR5SoilGas v3.txt

Non

Recurring

Lab

Sample

EPAR5SMP v3.txt

Recurring

Lab

Test Result

EPAR5TRS v3.txt

Recurring

Lab

Test/Results
QC

EPAR5TRSQC_v3.txt

Recurring

Lab

Batch

EPAR5BAT v3 .txt

Recurring

Vapor
Intrusion

VI Bldg
address

EPAR5 VI BLDG ADDRESS V3

Non

Recurring

Vapor
Intrusion

VI Bldg
Inspection

EPAR5 VI BLDG INSPETION V3

Non

Recurring

Vapor
Intrusion

VI Bldg
Parameters

EPAR5 VI BLDG PARAMETERS V3

Non

Recurring

Vapor
Intrusion

VI Locations

EPAR5 VI LOCATIONS V3

Non

Recurring

Vapor
Intrusion

VI Outdoor
Locations

EPAR5 VI OUTDOOR LOCATIONS V3

Non

Recurring

Vapor
Intrusion

VI Samples

EPAR5VISAMPLESV 3

Non

Recurring

Region 5 EDD Comprehensive Specification Manual
Version 4.3	11

United States
Environmental Protection Agency

-------
Table 2-5 EDD File Naming Formats

File
Type

File Contents

EDD File Name

Submittal
Type

Vapor
Intrusion

VI Test Results
QC

EPAR5_VI_TestResultsQC_v3

Non

Recurring

Vapor
Intrusion

VI Batches

EPAR5 VI Batches v3

Non

Recurring

2.8 Data Integrity Rules

Data providers are responsible for running three types of integrity checks on their data.

• Validity: All codes used in a data set must be valid. Valid values for all coded fields are either
provided in the description columns of the tables in Sections 3, and 4 or in the tables in the Appendix
of this manual. For example, sample matrix information is inputted in the samplematrixcode field
of the sample file and must be reported using one of the values provided in Table A-l in the
Appendix.

• Row Uniqueness: Row uniqueness must be verified using the guidance provided in Tables 2-1, 2-2,
and 2-3. Row uniqueness is assured when no two rows in a file contain the same values for all the
fields listed under the heading "What makes a row of data unique?" In database terminology this is
called a primary key. For example, no two rows in the sample file can contain the same
sys sample code (commonly called a sample identifier). In addition, no two rows ever reported for a
single site can contain the same sys_sample_code. Each sys_sample_code must be unique for a site.

Files that have a primary key consisting of multiple fields, such as the water level file, must have a
different value in at least one of the prmary key fields. For example, no two rows in the water level
file can have the same sys_loc_code, measurement_date. For example, two rows with sys_loc_code
of "SB-01", measurement_date of "05/02/2000 00:00:00" would violate row uniqueness. However,
row uniqueness would not be violated if one row had a sys loc code of "SB-01", measurement date
of "05/02/2000 00:00:00" and the other row had sys_loc_code of "SB-01", measurement_date of
"06/12/2000 00:00:00".

• Row Integrity: The relationship between rows within the files of the EDD must be assured by
enforcing the "referential integrity" rules discussed in Tables 2-1, 2-2, and 2-3 under the column
labeled "Dependence of other files on these data." For example, the values in the sys_sample_code
field in the Test/Result file must match with the corresponding fields in the Sample file. Logical
relationships between the various Lab EDD files are shown in Figure 2-1. The lines connecting the
files show which column(s) (or field(s)) are related in the two files. The file on the side with the "1"
at the end of the connecting line contains one row that is related to more than one row in the related
file on the other side. For example, one row in a SUBFACILTY EDD file may correspond to many
rows in a LOCATION EDD file because there are always more than one, and in most cases many
locations, designated at a site. The logical relationship between the FIELD EDD files is limited to the
requirement that all entries in the sys loc code fields appear in the LOCATION EDD file.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 12

United States
Environmental Protection Agency

-------
Figure 2-1 Relationships between Lab file data structures.



Location



Sample

Subfacility





1

Data_provider





subfacility _code





Facility _code





sys_sample_code





sys_loc_code





sample_name







x_coord





sample_matrix_code

subfacility _name





ycoord
surfelev





sampletypecode
sample_source

subfacility _task_code
subfacility _desc 1





elevunit

coord_type_code

observation_date





parent_sample_code

sample_delivery_group

sample_date

subfacility _desc2





identifier





sample_time





horz_collect_method_code



*

sys_loc_code

contact_name





horz_accuracy_value

00

start_depth





horz_accuracy_unit



end_depth

addressl





horz_datum_code
elev_collect_method_code



depth_unit
chain_of_custody

address2





elev_accuracy_value



sent_to_lab_date

city





elev_accuracy_unit



sample_receipt_date





elev_datum_code



sampler

state
zip code





source_scale



sampling_company_code





subcontractor_name_code
verification_code



sampling_reason
sampling_technique

phone numbeer





reference_point



task_code

alt_phone_number





geometric_type_code
rank



collectionquarter
composite_yn

fax_numbeer





loc_name



composite_desc







loc_desc



sample_class

email address





locjype



custom_field_l





loc_purpose



custom_field_2





primary _site_code



custom_field_3





witliin_facility_yn



comment





loc county code
loc_district_code















00

loc_state_code







loc_major_basin







loc_minor_basin







remark







total_depth







depth_to_bedrock







depth_to_top_of_screen







depth_to_bottom_of_screen







top_casing_elev







datum_value







datum_unit







step_or_linear







datum_collection_method_code







datum_desc







datum_start_date













Test Result QC

sys_sample_code

lab_anl_method_name

analysis_date

total_or_dissolved

column_number

test_type

lab_matrix_code

aiialysis_location

basis

container_id

dilution_factor

prep_method

prep_date

leachate_method

leachate_date

lab_name_code

qc_level

lab_sample_id

percent_moisture

subsample_amount

subsample_amount_unit

analyst_name

instrument_id

comment

preservative

fmal_volume

fmal_volume_unit

cas_m

chemical_name

result_value

result_error_delta

result_type_code

sys_l°

detect_flag

lab_qualifiers

validator_qualifiers

interpreted_qualifiers

validated_yn

method_detection_limit

reporting_detection_limit

quaiititation_limit

result_unit

detection_limit_unit

tic_retention_time

minimum_detectable_conc

counting_error

uncertainty

critical_value

validation_level

result comment

Shaded fields are required to have data. Blue fields define row uniqueness for the specified file.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	13

United States
Environmental Protection Agency

-------
2.9 Definition of a Facility, Site, and Location

To submit and error-free EDD, it is important to understand how EPA Region 5 defines facility, site, and
location for the purposes of this EDD Specification Manual. Each facility (facility id) will be identified
with its EPA ID number (see Table A-22 in the Appendix.) As EPA requirement, a facility center point
must be populated with the latitude and longitude centroid of the facility (*). The site (site code) will be
the operable unit identifier. There will always be at least one operable unit per facility. The way the
location term is used is that each site can contain one or more locations, as long as they are distinct points
defined by X and Y universal transverse Mercator (UTM) coordinates Examples of locations include soil
borings, monitoring wells, and sampling locations. Each location identifier (sys_loc_code) must be
unique for a facility.

Figure 2-2 provides a diagram of the facility components.

Figure 2-2 Facility component definitions

Facility ID = EPA ID #

Site = Site Operable Unit = site_code Must be unique at a Facility
Location= sample location = sys loc code Must be unique at a Facility

2.10 Reporting Null Values

When a field is not listed as required in Sections 3, and 4 and the data is not available or applicable, a null
or blank may be appropriate. However, tabs or commas must still delimit the blank value. In other words,
the number of fields is always the same, whether or not the fields include data. So a blank field in a tab-
delimited file would appear as """ and a blank field in a comma-delimited file would
appear as ""..".Table 2-5 shows a number of examples.

Table 2-6 Examples of how to report null values

Example

Comment

"data_one""data_two" "data_three"
"data one","data two","data three"

O.K. All fields populated, one tab or comma
between fields.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 14

United States
Environmental Protection Agency

-------
Table 2-6 Examples of how to report null values

Example

Comment

"data one" "data_three"
"data one"„"data three"

O.K. Optional field not populated, 2 tabs or 2
commas between first and third field.

"data_one" "data_three"
"data one","data three"

Not O.K. Optional field omitted, only 1 tab or
comma between first and third field.

2.11 Valid Values

Valid values, also known as reference values or code lists, govern the contents of some fields in the
EDDs. In other words, some fields may only be populated with data that matches a value listed in the
EPA Region 5 list of valid values. The lists of valid values are provided in the "Valid Values Table
Reference Manual". A list of all the data fields that must contain valid values is presented in Table 2-6
(below). This list is also cross-referenced to the EDD file(s) the field appears in. If data providers need
to enter a value not already in the Region 5 list in the Appendix, they can request the proposed addition to
the valid value list in the EDD cover letter. The data provider should explicitly state the valid value that
she/he would like added, provide a description of the value, and explain why the addition is necessary. In
the case of requesting a new aboratory code, the data provider should include the full name of the
laboratory and its address. When requesting an addition of an analyte, the data provider must include the
appropriate CAS number or ERPMS code along with a description of the analyte.

Table 2-7 Cross-reference between the valid value tables in appendix and the EDD files

Valid Value Table
Name

Table
Number

Field Name

EDD File

Matrix

A-l

samplematrixcode, labmatrixcode

Chemistry

Samples,

Test/Results

Geometric type

A-2

Geometric type code

Location

Horizontal Collection
Method

A-3

horzcollectionmethodcode

Location

Horizontal Accuracy
Unit

A-4

horzaccuracyunit

Location

Horizontal Datum

A-5

horz datum code

Location

Elevation Collection
Method

A-6

elev_collect_method_code

Location

Elevation Datum

A-l

elev datum code

Location

Material

A-8

Material type

Basic Geology

Location Type

A-9

loc type

Location

Qualifier

A-10

lab qualifiers, validator qualifiers

Test/Results

Result Type

A-ll

result type code

Test/Results

Sample Type

A-12

sample type code

Chemistry Samples

Geologic Unit

A-13

Geologic_unit_code

Geotechnical
Samples

Standard Preparation
Method

A-14

lab_prep_meth

Test/Results

Analyte

A-15

cas rn, chemical name

Test/Results

Lab Analysis Method
Name

A-16

labanlmethodname

Test/ Results

Region 5 EDD Comprehensive Specification Manual
Version 4.3	15

United States
Environmental Protection Agency

-------
Valid Value Table
Name

Table
Number

Field Name

EDD File

Laboratory

A-17

lab name code

Test/Results

Unit

A-18

various unit fields throughout all files

All Files

Geology Soil Materials

A-19

materialtype

Lithology, Geology
Samples

Well Segment and
Materials

A-20

segment_type, material_type_code

Well Construction

Hydrologic Unit Codes
(HUC)-Basin

A-21

locmajorbasin

Location

EPA Facility IDs

A-22

facility id, site name

Site

Company code

A-23

Data_provider

Location, Sample,
Test Result, Data
Provider

Total or dissolved

A-24

T otalordissolved

Test Result, Test
Result QC, Batch

Test Type

A-25

Test_type

Test Result, Test
Result QC, Batch

Test Batch Type

A-26

Test batch type

Batch

Reference Point

A-31

reference point

Location

Source scale

A-32

Source scale

Location

2.12 Reporting Re-Tests

For initial tests, all analytes should be reported. In the case where retests are performed on a sample, the
result that is considered the reportable result should indicate a "Y" (for "yes") in the reportable_result
field. The initial test, and any retest result not considered reportable will have reportable_result set to
"No". Table 2-7 provides examples of reporting re-tests.

Table 2-8 Example of reporting re-tests

Test
Type

Chem
Name

Cas rn

Result
Value

Detect
Flag

Lab
Qualifiers

Reportable
Result

Result Comment

Initial

Benzene

71-43-2

1000

Y

E

No

too concentrated to
quantitate

Initial

Toluene

108-88-3

5

N

U

Yes

not detected

Initial

Xylenes

1330-20-7

5

N

U

Yes

not detected

dilution 1

Benzene

71-43-2

780

Y



Yes

Quantitated

2.13 Reporting Non-Detects

Non-detects must be reported as shown in the example below. Each non-detect row must show an "N" in
the detect_flag field, must have an actual value entered in the reporting_detection_limit and
detectionlimitunit fields, and must contain a null in the resultvaluefield. The
reporting_detection_limit cannot be negative unless one of the radiological fields (including
minimum_detectable_conc, counting_error, uncertainty, critical_value) are populated. Table 2-8 presents
examples of how to report non-detects.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	16

United States
Environmental Protection Agency

-------
Table 2-9 Example of reporting non-detects

Cas rn

Result
Value

Detect
Flag

Reporting
Detection
Limit

Detection
Limit Unit

Resultcomment

Laboratory_
qualifiers

108-88-3

.15

.005

ug/ml

108-88-3

.005

ug/ml

not detected

2.14 Reporting Tentatively Identified Compounds

Tentatively Identified Compounds (TICs) should be reported when available. The naming of TICs should
be applied in a cascade fashion. The TIC should be identified to analyte name if possible. If this is not
possible, then the class of the TIC should be entered. If neither an analyte name nor a class can be
identified, the TIC should be identified as Unknown. The EPA Region 5 EDD only allows for reporting
up to 10 TICs. Only the 10 most concentrated or most relevant TICs should be reported. Table 2-9
shows examples of the nomenclature for TICs. As an example, if a sample has three Unknown
Hydrocarbons, then the TICs are labeled UnkHydrocarbl, UnkHydrocarb2, and UnkHydrocarb3. TIC
names are to be reported in the cas_rn field, Pos #31, of the Test/Result file (Tables 4-3 and Table 4-4).
In addition, the result type code, Pos # 35 in the Test/Result file should have "TIC" for all TIC records.

Table 2-10 Example nomenclature for TIC reporting

TIC Name

Number for TIC

Reported Name in cas rn

Unknown

1-10

Unknown 1 - Unknown 10

Unknown Hydrocarbon

1-10

UnkHydrocarbl - UnkHydrocarbl0

Unknown PAHs

1-10

UnkPAHl - UnkPAHIO

Unknown Aromatics

1-10

UnkAromaticl - UnkAromaticlO

Unknown VOA

1-10

UnkVOAl - UnkVOAlO

Unknown SV

1-10

UnkSVl -UnkSVIO

2.15 Data Types

The table below describes the data types used in the chemistry and geology file descriptions. In addition
to the types listed below, certain fields have single and double data types. The single data type stores
numbers from -3.402823 x 1038 to -1.401298 x 10"45 for negative values and from 1.401298 x 1045 to
3.402823 x 1038 for positive values, with a decimal precision of up to 7 digits. The double data type
stores numbers from -1.79769313486231 x 10308 to

-4.94065645841247 x 10"324 for negative values and from 1.79769313486231 x 10308 to
4.94065645841247 x 10"324 for positive values, with a decimal precision of up to 15 digits.

Table 2-11 Data type descriptions

Type

Description

Decimal
Precision

Comments

Integer

Stores numbers from -32,768 to 32,767 (no
fractions).

None

'Y' or TNT

Boolean field used to indicate yes or no to a
question. Enter either Y orN.

Time

Time in 24-hr (military) HH:MM:SS format.

Text (8) is standard
length for time.

Date

Date format is MM/DD/YYYY.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 17

United States
Environmental Protection Agency

-------
Type

Description

Decimal
Precision

Comments

Text

Stores characters and numbers.

NA

Length restrictions are
indicated in
parentheses.

2.16 Data Entry Tools Provided to Create the EDD Files

EDD files can be produced using any software with the capability to create text files. These files are
especially easy to create using spreadsheet or database software packages. However, if these are
unavailable, the files can be created using a word processor or text editor. Table 2-12 provides
instructions for creating tab-delimited text files from some widely-used software packages.

Region 5 EDD Comprehensive Specification Manual
Version 4.3	18

United States
Environmental Protection Agency

-------
Table 2-12 Instructions for producing tab-delimited text files from some software packages

Package

Type

Instructions

Access

Database

1. Create tables using file structures in Sections 3 and 4.

2. After data are entered, close table.

3. Click on table name (under table tab) and then select
"File," "Save As," from the top menu. Save to an external
file or database. Change "Save as Type" to a text file.
Change the file extension from "txt" to "tab." Press OK.
This will start the export wizard.

4. In the export wizard, select "Delimited," then press the
"Next" button. Select "Tab" as the delimiter type and " as
the text qualifier. Press the "Next" button. Select a
destination and name for the file. Press the "Finish"
button.

Excel

Spreadsheet

1. Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Text (Tab Delimited)" file. Press the
"Save" button.

Quattro® v8

Spreadsheet

1. Select "File," "Save As," from the top menu. Change the
"File Type" to "ASCII Text (Tab Delimited)." Press the
"Save Button."

Word

Word
Processor

[Note: A word processor is not the best tool for the job! A
large paper size will have to be selected to prevent wrapping
for most files. ] [wrapping?]

1. Enter data into a table in Word. Any text entered must be
contained within double quotes.

2. Select "Table," "Select Table," from the top menu. When
the table is highlighted, select "Table," "Convert to Text,"
"Separate Text with Tabs."

3. Select "File," "Save As," from the top menu. Change
"Save as Type" to "MS DOS Text (*.txt).

Lotus 1-2-3

Spreadsheet

1. Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Comma Separated Value (CSV)"
file. Provide file name. Press the "Save" button.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 19

United States
Environmental Protection Agency

-------
2.17 Using the Electronic Data Processor to Check EDD Formatting

The Electronic Data Processor (EDP) can be used by Data Providers to check EDD files prior to submittal
to EPA Region 5. The EDP is a no-cost application that performs a series of formatting checks on the
files and then identifies any records that have errors along with a description of the errors. This allows
the Data Provider to correct the errors before sending the files to EPA Region 5. EDD files that pass
through the EDP error-free should also result in error-free import at EPA Region 5.

EDP is currently available as a no-cost download from the EPA Region 5 website located at at
https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission. Instructions on how to
install and use the EDP are also provided on the website.

2.18 Submitting Your EDD to EPA Region 5

Each EDD must be checked using the EDP and the most updated EDD format before submitting to EPA
Region 5. Please follow the three steps below to submit your EDD data:

Got to EOuIS enterprise to set up your own username and password:

In order to use the Sign and Submit process in the EDP to create a EDD zip data package, you need to go
to EQuIS Enterprise https://epar5.equisonline.com/, then follow the steps below to set up your username
and password:

1. Select the "Get Started" link below the "Forgot your password?" link to register yourself as a
new user, (image below)

-------
Please provide the following information to register for a new account. All fields are required.

User Name * Email Address *

Check your inbox for an email from EQulS with your confirmation code. Copy and paste the confirmation code into the field below.

Email Confirmation Code'

Confirm Password'

Company Name •

City Name'

Q CANCEL © GET NEW CODE Q REGISTER

5. Fill in the form with your First Name, Last Name, Password, Cofirrn Password, Company Name,
City Name, and Postal Code

6. Click "Register" or if you don't receive your confirmation code, click "GET New Code"

7. Once you are successfully "Registered", you should receive the following:

ost widely used environmental data management software in the world

US EPA Region 5

EQulS™ Enterprise

Password'

Stay signed in ~

You have successfully registered for an account. You will
receive an email when your account has been activated.

8. EPA Region 5 database manager John Canar (canar.iohn@epa.gov) will receive your
registeration request, and assign your role and approve your request.

9. Once you are approved with your assigned role, you should receive a email to ask about the
site(s) names that you are going to submit data for.

10. Now you should be able to use your username and password in the Sign and Submit process.

The Sign and Submit process allows data provider to save the EDD in their preferred folder or directory.
The EDD zip package should be named using the naming convention that was shown in section 2.4.

Email to EPA Region 5 EQulS Enterprise Database:

Region 5 EDD Comprehensive Specification Manual
Version 4.3 21

United States
Environmental Protection Agency

-------
- Once the EDD zip file has been created, the EDD is ready to be emailed to EPA EQuIS
Enterprise processor. Please follow the following 2 steps:

1. Change the file extention from ".zip" to "".edd". In other words, your EDD is zipped in EDP,
such as "20190811. MID000000001.EPAR5.zip", you need to change the file extention to ".edd",
meaning the file name will become "20160811. MID000000001.EPAR5.edd"

2. Send the ".edd" file to to EP AR5 @EOuISOnline.com

Notify EPA Region 5 when the data is sent to the EPA Region 5 EQuIS Enterprise database:

Please notify the EDD database adminstrator canar.iohn@epa.gov for each EDD that has been
emailed to the EPA Region 5 EQuIS Enterprise database.

EDD submittal types

There are three possible EDD submittal types: an original submittal, an error correction resubmittal, and
an update submittal. These three EDD types are described below.

¦ Original Submittal: An original EDD submittal contains data being submitted for the first time
to EPA Region 5. EPA Region 5 will process and check the EDD. If there are no errors in any of
the EDD files, EPA will import the data to the permanent database. EPA Region 5 can only
import and accept the EDD submittal if all files in the submittal are error-free. If any of the files
on the EDD contain errors, EPA will send the data provider a letter specifying the errors that
need to be corrected.

¦ Correction Resubmittal: In the case where an original EDD submittal contains errors, the
entire EDD submittal will be returned to the data provider along with an error report explaining
the problems identified. The data provider should then correct the errors, check the files again
with the EDP, and then resubmit the entire EDD. A response is required within 30 days. It is
important that the resubmitted EDD contain all of the files and the SAME FILE NAMES (i.e.,
use the same site name and submittal date in the file name as was used in the original submittal)
as those in the original submittal. Thus, the EDD resubmittal will be identical to the original
submittal in everyway except the errors are corrected.

¦ Update Submittal: This type of submittal updates data that has previously been accepted by
EPA Region 5. The files of an update submittal should contain only data for the records being
updated. For example, say a data provider submits an EDD in 2014 that includes a location file
(e.g., EPAR5LOC_v3.txt) that contains ten locations, and the EDD is accepted by EPA Region 5
and loaded into the EPA database. If, in 2016, the site is resurveyed, and it is discovered that
three of the locations" coordinate information has changed due to increased accuracy, a new
location file containing data for only those three locations would need to be submitted as an
update submittal. The update submittal would be included in a cover letter and name the file
correctly. Note: All required fields need to be populated for the three locations regardless of
whether or not these fields were updated. The reason for the update submittal and the records
that have been changed must be clearly indicated in the cover letter accompanying the updated
EDD.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 22

United States
Environmental Protection Agency

-------
2.19 Examples of Field, and Lab EDD Files

Examples of Field and Lab EDD files with the first few rows of the EDD populated with a typical data set are presented in Figures 2-3, 2-4, 2-5,
and 2-6. These examples were produced using Excel worksheets. To submit these files, the data provider would save the files as text delimited
files (txt) or comma separated files (csv), check the files using the EDP, and then send the error free files to Region 5. In order to fit the examples
on one page, not all of the fields (i.e., columns) were included for certain files (e.g., Subfacility, Location, and Sample). The notation "Additional-
Fields " has been inserted where, for purposes of these examples, one or more fields have been omitted. It should be noted that all fields must
appear in the EDD files you submit regardless of whether or not the field is populated (see Section 2.7 regarding reporting blanks, or "null"
values). Special cases discussed in previous sections of this manual, as well as more standard types of data, are illustrated below.

Figure 2-3. Example Field EDD ready for conversion to text file

Subfacilty File (EPAR5SUBFACILITY v3):

subfacility_co
de

subfacility_na
me

subfacility _task_c
ode

subfacility_des
cl

subfacility_de
sc2

contact_name

addressl

Facility Name

John Smith

23 Main Street

email address

abc(S?abd.com

Location File (EPAR5LOC v3):

Dataprovid
er

Facilitycod

sys_l°c_c°de

X_coord

Y_coord

surf_elev

elev_
unit

coordtypeco
de

observatio
n date

ABD

MID0000001

MW01

573535.16

46185.25

120.2

UTM Zone 16

02/21/2015

ABD

MID0000001

SB-01

571535.28

46185.22

126.3

UTM Zone 16

02/23/2015
9

ABD

MID0000001

MW03

571525.28

47558.33

130.1

UTM Zone 16

02/22/2015

ABD

MID0000001

MW04

561528.33

46004.25

130.1

UTM Zone 16

02/22/2015

comment

Sample File (EPAR5SMP v3):

Figure 2-4. Example Lab EDD ready for conversion to text file

Data_provider

sys_sample_
code

sample_
name

sample_
matrix code

sample_type_
code

sampleso
urce

parentsample
code

sampledelivery
group

sample_
date

sys_l°c_c°de

ABD

MW-

01 20150401

Field

04/01/201512
:00:00

MW01

ABDE

MW-

02 20150401

Field

04/01/2015
12:00:00

MW02

Additional
Fields

Region 5 EDD Comprehensive Specification Manual
Version 4.3 23

United States
Environmental Protection Agency

comment

-------
Test Result QC File (EPAR5TRSQC v3):

sys_sample_

lab anl

Additional

total or

column

test

lab matrix

analysis_

basis

code

method_
name

Fields

dissolved

number

type

_code

location

MW-

SW8240

Initial

Wet

01 20150401

MW-

SW8240

Initial

Wet

01 20150401

MW-

SW8240

Reanalysis

Wet

01 20150401

dilution_
factor

lab_
name_
code

qc_

level

lab_
sample
id

1.0

ABC

quant

LAB01

1.0

ABC

quant

LAB02

10.0

ABC

quant

LAB02R

Additional
Fields

Test Result QC (EPAR5TRSQC v3) (Continue):

casrn

chemical_
name

result_
value

result_
error_
delta

result_

type_

code

reportable
_result

detect_flag

lab_
qualifiers

Validate
d_yn

Methoddet
ection_limit

reporting_
detection
limit

Quantitation
_limit

result_
units

71-43-2

BENZENE

TRG

Yes

ug/ml

108-88-3

TOLUENE

TRG

Yes

ug/ml

1330-20-7

XYLENES

TRG

Yes

ug/ml

result_
comment

Figure 2-5. Examples of QC data fields in a Chemistry EDD

QC fields in a normal field sample (i.e., sample type code = N, TB, etc.)

casrn

result_value

qcoriginal
_conc

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

qc_dup_
original_
cone

qc_dup_
spike_
added

qc_dup_
spike_
measured

qc_dup_
spike_
recovery

93-76-5

1.56

94-75-7

3.17

94-82-6

2.31

Region 5 EDD Comprehensive Specification Manual
Version 4.3 24

United States
Environmental Protection Agency

-------
QC fields in a normal field sample with surrogates (i.e., sampletypecode = N, TB, etc.)

The following table shows some of the fields in the test/result file (TRS) for a normal field sample. Notice that QC fields are blank except in rows
related to surrogate samples. . Many data providers will only need to populate the recovery field data; the spike-added and spike-measured fields
will not be needed in most situations.

Casrn

result_value

result_unit

result_type_
code

qc_original_
cone

qc_spike_added

qc_spike_
measured

qe_spike_
recovery

93-76-5

1.56

mg/1

TRG

94-75-7

3.17

mg/1

TRG

PHEN2F

mg/1

SUR

12.5

12.9

103

QC fields in a laboratory method blank sample (i.e., sample type code = LB)

The following table shows some of the fields in the test/result file for a laboratory method blank sample. Notice that all QC fields are blank.

casrn

result_
value

lab_
qualifier

qc_

original_
cone

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

qc_dup_
original_
cone

qc_dup_
spike_
added

qc_dup_
spike_
measured

qc_dup_
spike_
recovery

93-76-5

94-75-7

94-82-6

0.01

Region 5 EDD Comprehensive Specification Manual
Version 4.3 25

United States
Environmental Protection Agency

-------
Figure 2-5. Examples of QC data fields in a Chemistry EDD (continued)

QC fields in a matrix spike (i.e., sampletypecode = MS)

The following table shows some of the fields in the test/result file for a matrix spike sample. Notice that all "dup" QC fields are blank and that the
result_value field is not needed. Also, the qc_rpd field would be blank for these rows. Many data providers will only need to populate the

calculated recovery fie

d (qc spike recovery).

casrn

result_
value

qc_
original_
cone

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

Qc_rpd

qc_dup_
original_
cone

qc_dup_
spike_
added

qc_dup_
spike_
measured

qc_dup_
spike_
recovery

93-76-5

1.56

4.18

5.36

90.9

94-75-7

3.17

4.18

7.15

95.2

94-82-6

2.31

4.22

5.66

79.3

QC fields in a matrix spike duplicate (i.e., sample type code = SDj

The following table shows some of the fields in the test/result file for a matrix spike duplicate sample. Notice that all "dup" QC fields are filled in
and that the result_value field is not needed. Also, the qc_rpd field would be completed for these rows. Many data providers will only need to

casrn

result_
value

qc_

original_
cone

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

Qc_rpd

qc_dup_
original_
cone

qc_dup_
spike_
added

qc_dup_
spike_
measured

qc_dup_
spike_
recovery

93-76-5

1.56

4.23

5.70

97.8

94-75-7

3.17

4.23

7.62

105

94-82-6

2.31

4.13

5.33

73.1

QC fields in a matrix spike/matrix spike duplicate (i.e., sample type code = MSD)

The following table shows some of the fields in the test/result file for a matrix spike/matrix spike duplicate considered as a single sample . (Note:
Matrix spike and matrix spike duplicate samples can be reported either this way or as two separate samples as shown above). Notice that all QC
fields are filled in and the result_value field is not needed. Also, the qc_rpd field would be completed for these rows. Many data providers will
only need to populate the calculated recovery fields (qc spike recovery and qc dup spike recovery).

casrn

result_
value

qc_

original_
cone

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

Qc_rpd

qc_dup_
original_
cone

qc_dup
spike_
added

qc_dup
spike_
measured

qc_dup
spike_
recovery

93-76-5

1.56

4.18

5.36

90.9

1.56

4.23

5.70

97.8

94-75-7

3.17

4.18

7.15

95.2

3.17

4.23

7.62

105

94-82-6

2.31

4.22

5.66

79.3

2.31

4.13

5.33

73.1

Region 5 EDD Comprehensive Specification Manual
Version 4.3 26

United States
Environmental Protection Agency

-------
QC fields in a LCS (i.e., laboratory control sample, blank spike, sampletypecode = BS)

The following table shows some of the fields in the test/result file for an LCS sample. The qc_rpd field would be blank for these rows. Many data
providers will only need to populate the calculated recovery field (qc spike recovery). LCS duplicate samples (i.e., sample type code = BD) and
LCS/LCSD samples (i.e., sample type code = BSD) follow the patterns similar to the SD and MSP samples described above.

casrn

result
_value

qc_original
_conc

qc_spike_
added

qc_spike_
measured

qc_spike_
recovery

qc_dup_
original_
cone

qc_dup_
spike_
added

qc_dup_
spike_
measured

qc_dup_
spike_
recovery

93-76-5

5.00

5.26

105

94-75-7

1.00

1.02

102

94-82-6

12.5

12.9

103

Figure 2-6. Example Field EDD ready for conversion to text file

Drill Activity File:

sys_l°c_c°de

drill_event

start_depth

end_depth

drill_date

diameter

W-4A

07/12/1999

W-6B

110

07/14/1999

Additional
Fields

purpose

Advanced well additional 40 feet to reach lower aquifer

Advanced well 55 feet to reach bedrock.

Litholog

y File:

sys_loc_
code

start_
depth

material_
type

geo_unit_l

W-1A

Glacial

W-1A

Outwash

W-1A

Outwash

W-2A

Alluvial

Additional
Fields

Remark 1

grayish brown clay, trace fine sand, med strength, med plastic, rapid dilatancy ,some brick
fragments

med dense, 50% fine to coarse brown sand, 30% gravel, dry, trace clay

dense, 70% coarse brown sand, 20% gravel, poorly graded, rounded, moist

Dark brown silt with little fine sand, low strength, nonplastic, rapid dilatancy

Additional
Fields

odor

Well File:

sys_l°c_c°de

W-1A
W-2A

Additional
Fields

top_casing_elev

datum_value

datum_unit

datum_desc

122.0

top of casing of well

122.3

top of casing of well

Additional
Fields

geologic_unit_
code

remark

outwash

alluvial

Region 5 EDD Comprehensive Specification Manual
Version 4.3 27

United States
Environmental Protection Agency

-------
Figure 2-6. Example Field EDD for new monitoring wells or direct push samples ready for conversion to text file (continued)
Well Construction File

sys_l°c_c°de

segment_type

material_type_code

start_depth

end_depth

depth_unit

inside_diameter

W-1A

surface plug

concrete

1.5

4.5

W-1A

annular backfill

neat cement grout

1.5

2.375

W-1A

annular Seal

Bentonite pellets

2.375

W-1A

Filter Pack

sand pack

23.1

2.375

W-1A

Protective Casing

steel

-2.2

3.2

W-1A

Casing

stainless steel 304

-2.1

W-1A

Screen

stainless steel 304

W-2A

protective casing

steel

-2.0

3.0

W-2A

surface plug

concrete

1.5

4.5

W-2A

annular backfill

neat cement grout

1.5

2.375

Additional
Fields

remark

Geology Sam

pie File:

sys_l°c_c°de

Geo_sample_code

sample_name

sample_top

samplejbottom

sample_date

Additional
Fields

sample_method

material_type

Additional
Fields

organiccarbon
units

W-1A

ABCD-1

04/23/1999
00:00:00

split spoon

W-1A

ABCD-2

04/23/1999
00:00:00

split spoon

W-2A

DEFG-1

04/24/1999

split spoon

Region 5 EDD Comprehensive Specification Manual
Version 4.3 28

United States
Environmental Protection Agency

-------
Figure 2-6. Example Geology EDD for new monitoring wells or direct push samples ready for conversion to text file (continued)
Water Table File:

sys_l°c_c°de

Type

sequence

Depth

flowing_yn

measurement_method

capped_pressure

cappedpressure
unit

MW01

Unconfmed

stable

21.2

electric sensor

MW02

Unconfmed

stable

21.0

electric sensor

Additional
Fields

temperature
unit

Downhole Point File:

sys_l°c_c°de

Depth

param

param_value

MW01

10.8

Tip Stress

612

MW01

11.2

Tip Stress

624

MW01

10.8

Sleeve Stress

6.1

MW01

11.2

Sleeve stress

5.8

MW02

9.5

Resistivity

510

MW02

10.1

Resistivity

521

MW02

11.0

Resistivity

489

Water Level File:

sys_l°c_c°de

measurement
date

historical_ref_elev

water_level_depth

w ater_level_elev

corrected_elev

MW01

05/10/1999
13:10:00

31.1

89.1

MW02

05/10/1999
13:45:00

34.1

89.0

Additional
Fields

remark

Extraction

njection Wells

sysjoe
_code

Start_
measurement
date

end measure
date

avg pump rate

pumprateunit

EX-01

05/12/2000 11:23:00

06/12/2000
11:30:00

2.5

mgd

EX-02

11/12/2000 12:00:00

12/12/2000
13:10:00

1.75

mgd

Additional
Fields

remark

Region 5 EDD Comprehensive Specification Manual United States

Version 4.3 29 Environmental Protection Agency

-------
3. FORMATS FOR Facility Files and Field Files

This section contains information regarding the base map and the two files included in the Facility EDD.
These files need to be submitted prior to, or in conjunction with, the first Field EDD submittals These
files only need to be submitted once unless information in the files changes or additional information,
such a new sampling location, needs to be added. Columns marked "Required" must be reported for
each row in the file. If these fields are not reported, errors will be identified in the EDD and the EDD will
need to be resubmitted. Columns marked "If available" should also be reported if possible.

3.1 Facility EDD Files

Site Base Maps in the file section (Files_v3)

Site base maps can be submitted in CAD files in a DXF interchange format, or drawing (.dwg) file, or
Shapfiles generated from ArcGIS. The maps should include all well locations, waste management units,
landfills, buildings, and roads. Do not include any groundwater contours, contaminant contours, or
other temporal type information. If the CAD file is available in real world locational coordinates,
provide the coordinates along with a brief text description of the type of projection and datum used.
(Note: UTM NAD 83 is the data type preferred by EPA Region 5). Also include text descriptions of the
units and scale of the base map. The site base map file should be named according to the following
example:

SiteName.DXF (or dwg, or shape files)

The file section allows you to load supplementary information into EQuIS, such as Map, drawing files.
The naming convention of the File_v3 is:

File_v3.txt (or .csv)

Table 3-1 Files (Files_v3) structure

Pos#

Column Name

Data type

Required

Description

Valid Values In
Appendix

File name

Text (255)

Yes

Name of the file

Filetype

Text (20)

Yes

Type of the file

Filedate

Date time

If available

Date of the file

Title

Text (255)

If available

Title of the file

Author

Text (255)

If available

Author of the file

Confidential _yn

Text (1)

If available

Whether or not the file is
confidential

Remark

Text (255)

If available

Remark for the file

Placetype

Text (50)

If available

Type of the place tis file
is associated with

Placecode

Text (50)

If available

Code/identifier of the
place this file is associate
with

Placesubcode

Text (50)

If available

Subcode/ identifier of the
place this file is
associated with

Content

Content of the file

Region 5 EDD Comprehensive Specification Manual
Version 4.3 30

United States
Environmental Protection Agency

-------
3.2. Field Files-DATAPROVIDER

This section contains tables that define the file structures for the FIELD EDD. The file structures include
the first three initial EDD files: Data Provier, Subfacility, and Locations, also the drilling activity,
lithology, well, well construction, geotechnical samples, water levels, Water Table, downhole point,
extraction injection wells, and Soil Gas data. The columns marked "Required" must be reported for each
row in the file. If an EDD is submitted with one or more "Required" fields not filled in, EPA will not be
able to load the EDD into its database, and the EDD will have to be returned to the data provider for
correction(s). The columns marked "If available" should also be reported whenever possible. Examples
of the EDD files that make up the Field EDDs are provided in Figure 2-6, section 2.16.

Data Provider (EPAR5DATAPROVIDER_v3)

The Data Provider EDD file provides general information about the data provider who is the contact for
the data on the site.

EPAR5DataProvider_v3.txt (or .csv)

Table 3-2 Data Provider (EPAR5DataProvider_v3) File Structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

DataProvider

Text(20)

Required

This is the name of the company who is
responsible for providing the site data.

A-23

DataContact
Person

Text(30)

Not

Required

This is the name of the contact person
who is responsible for providing the site
data.

DataContact
Addressl

Text (40)

Not

required

Data Provider address 1

DataContact
Address2

Text (40)

Not

required

Data Provider address 2

DataContact
City

Text (30)

Not

required

Data Provider city

DataContact
State

Text(5)

If Available

Contact state

DataContactzi
pcode

Text(10)

Not

required

Contact zip

DataContact
email

Text(60)

Required

Contact email address

DataContact
Phone

Text(30)

Not

Required

Contact phone number

3.3 SUBFACILITY EDD File

The SUBFACILITY EDD file provides general information about a site and provides the name, e-mail
address, and other contact information for the main EDD data contact for the site. An example of a
Subfacility file is provided in Figure 2-3, section 2.16. NOTE: If the SUBFACILITY EDD file was
previously submitted, including as part of a "Historic Data EDD", as described in the Region 5 "EDD
Manual for Historical Data", you DO NOT need to resubmit the file again.

Each SUBFACILITY file must be named according to the following convention:

Region 5 EDD Comprehensive Specification Manual
Version 4.3 31

United States
Environmental Protection Agency

-------
EPAR5SUBFACILITY_v3.txt (or .csv)

Table 3-3 SUBFACILITY (EPAR5SUBFACILITY v3) data file structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

SUBFACILITYc
ode

Text(20)

Required

Code indicating the site operable unit
for which the data is collected, or
area of concern (AOC). Typically
the code is "01" unless there is a
second or third operable unit at
facility. Codes of "02" and "03"
should be used for second and third
operable units, respectively. Contact
the EPA RPM if unsure of proper
code.

subfacility name

Text(60)

Required

Name of site

Table A-22

sitetaskcode

Text(40)

Required

Code used to associate individual
samples to a specific sampling event.
The format for this field is XX-P#, XX
is the type of task required and P# is
the phase.

subfacility descl

Text(255)

If available

General description of the site.

subfacility_desc2

Text(255)

If available

Additional description of site, if
necessary.

contactname

Text(50)

Required

Name of person to contact if EPA
Region 5 has any questions about the
EDD.

addressl

Text(40)

Required

Site address, part one.

address2

Text(40)

Not required

Site address, part two. Default to null
if information is not needed

City

Text(30)

Required

Site city.

State

Text(2)

Required

Site state.

Zipcode

Text(10)

Required

Site zip code.

phone number

Text(30)

Required

Site contact phone number.

alt_phone_number

Text(30)

If available

Alternate phone number for site
contact. Default to null where the
data are not available.

faxnumber

Text(30)

If available

Fax number of site contact. Default
to null where the data is not
available.

email address

Text(lOO)

Required

Site contact e-mail address.

3.4 Location EDD File (EPAR5LOC_v3)

The primary purpose of the Location EDD file is to define the sampling locations for a site. Each EPA ID
must have a center point identified. The location section will be used to enter the center point. This file
is referred to as one of the Initial EDD files because it needs to be submitted ~ and error-free ~ before
EDD files that contain chemistry and geology data can be used. Each row of the Location file contains
the definition of a unique sampling location. Do not create any records (i.e., rows) for any samples not
associated with a specific sampling location, such as field blanks and trip blanks. In the case of multiple
wells located in one borehole, each well in the borehole must have a unique sampling location identifier
(sys_loc_code).

Each sampling location should only be reported once for a site. The only time data a previously reported
location should be resubmitted is if some information about the location changes, such as when a location

Region 5 EDD Comprehensive Specification Manual
Version 4.3 32

United States
Environmental Protection Agency

-------
is resurveyed after settling has occurred or after a resurvey using an instrument or methodology with
higher accuracy. When resubmitting changes to the Location file, the file should contain rows pertaining
to the affected locations only. As in a typical EDD submittal, all "required" fields should be populated
when updating data. Changes in the resubmittal should be described in the cover letter accompanying the
EDD, and the EPA RPM should receive a copy of the letter or should be otherwise notified. See section
2.15 "Submitting Your EDD to EPA" for more information regarding submitting updated data files.

The data structure of the LOCATION EDD file includes fields (Table 3-4 below) to collect data
requirements of EPA's Locational Data Policy (LDP). LDP requires geographic coordinates and
associated method, accuracy, and description (MAD) codes for all environmental measurements collected
by EPA employees, contractors, and grantees. A key premise of the LDP policy is that secondary use of
these data in geographic information systems (GIS) and statistical mapping programs are significant to the
overall mission of the Agency. To facilitate the integration of data, EPA has established the LDP to
standardize the coding of geologic coordinates and associated attributes. Therefore, in addition to location
coordinates being reported in UTM meters, Region 5 requests that coordinates be reported in latitude and
longitude, along with associated attributes, if the data is available. An example of a Location file is
provided in Figure 2-3, section 2.16.

Each Location file must be named according to the following convention:

EPAR5LOC v3.txt (or .csv)

Table 3-4 Location Data (EPAR5LOC_v3) File Structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Data Provider

Text(20)

Required

Data Prodiver company code

A-23

Facility code

Text (20)

Required

Facility ID

A-22

sysloccode

Text(20)

Required

Location ID, such as MW-01,
A24, SW12, or SB-2S, for all
samples collected, including
groundwater samples,
hydropunch samples, surface
water/sediment samples, and
soil samples. For facility
center point, sys loc code =
"FAC CENTER POINT"

Xcoord

Number
w/decimal
precision
up to 15

Required

Sampling location numeric x
UTM NAD83 coordinate in
meters.

Ycoord

Number
w/decimal
precision
up to 15

Required

Sampling location numeric y
UTM NAD83 coordinate in
meters.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 33

United States
Environmental Protection Agency

-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

surfelev

Number
w/decimal
precision
up to 15

Not Required

Elevation of the ground
surface, or if location is for
surface water samples, water
surface elevation.

For water surface elevation,
use the average annual
elevation. Note: Subsequent
water surface elevations
should be obtained during the
surface water sampling period
and reported in the Water
Level EDD file (see sections
4.2 and 4.4).

elevunit

Text(15)

Required

Unit of measurement for
elevations.

Units must be in
ft/m

coordtypecode

Text(20)

Required

Sampling location coordinate
system description. Must be
'UTM Zone nn'

observationdate

DateTime

Not required

Date observation or site
survey was made.

horzcollectmethodc
ode

Text(2)

If available

Method used to determine the
latitude/longitude
measurements. Horizontal
Collection Method.

Table A-3

horzaccuracyvalue

Text(20)

Not required

Accuracy range (+/-) of the
latitude and longitude. Only
the least accurate
measurement should be
reported, regardless if it is for
latitude or longitude.

horzaccuracyunit

Text(l)

If available

Unit of the horizontal
accuracy value.

Table A-4.
Enumeration list
contains the
codes and
description

horzdatumcode

Text(l)

If available

Reference datum of the
x coord and y coord

Table A-5

elevcollectmethodc
ode

Text(2)

If available

Method used to determine the
ground elevation of the
sampling location.

Table A-6

elevaccuracyvalue

Text(20)

Not required

Accuracy range (+/-) of the
elevation measurement.

elevaccuracyunit

Text(8)

Not required

Unit of the elevation accuracy
value.

Table A-18.
Enumberation
list contains the
codes and
description.

elevdatumcode

Text(l)

If available

Reference datum for the
elevation measurement

Table A-7

Region 5 EDD Comprehensive Specification Manual
Version 4.3 34

United States
Environmental Protection Agency

-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sourcescale

Text(2)

Not required

Scale of source used to
determine the x coord and
y coord.

Table A-32

subcontractornameco
de

Text(20)

If available

Code used to distinguish
subcontractor name.

Table A-23

verificationcode

Text(l)

Not required

This field is only to be used by
EPA Region 5 personnel.
Please leave blank.

reference_point

Text(2)

Not required

Describes the place at which
coordinates were established.
Use codes from Table A-2 in
the Appendix.

Tabel A-31
Enumeration list
is available in
this field.

geometrictypecode

Text(20)

If available

Value: 'POINT'

A-2

Rank

Numeric

Not required

This field is for by EPA
Region 5 future use. Please
leave blank.

loc name

Text(40)

Not required

Sampling location name.

loc desc

Text(255)

Not required

Sampling location description.

loctype

Text(10)

If available

Description of sampling type,
such as direct push, extraction
well, or sediment. Use
"CENTROID" to identify
facility center point. Use codes
from Table A-9 in the
Appendix.

Table A-9

loc purpose

Text(20)

Not required

Sampling location purpose.

Primarysubfacilityco
de

Text(20)

Required

Unique code for site or area.
Must match subfacility code
field from Table 3-3:
Subfacility File Data
Structure.

within_facility_yn

Text(l)

Required

Indicates whether this
sampling location is within
facility boundaries, "Y" for
yes or "N" for no.

loccountycode

Text(20)

Not required

Location county code;
controlled vocabulary using
FIPS (Federal Information
Processing Standard) codes.
FIPS codes can be found via
the internet at

https://www. eoa.gov/envir
o/state-fips-code-listing

locdistrictcode

Text(20)

Not required

Use the EPA region code

'005'

locstatecode

Text(10)

If available

Location state code; controlled
vocabulary using FIPS codes.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 35

United States
Environmental Protection Agency

-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

locmajorbasin

Text(8)

If available

Location major basin;
controlled vocabulary using
HUC (hydrologic unit codes

Table A-21

locminorbasin

Text(20)

Not required

Location minor basin;
controlled vocabulary using
HUC codes. Any digits after
the 8th (first 8 are reported in
loc major basin) should be
reported here.

Remarks

Text(255
)

Not required

Location specific comment.

totaldepth

Number

w/decima

precision
up to 15

Not required

Total depth below ground
surface of boring, in feet.

depthtobedrock

Number

w/decima

precision
up to 15

Not required

Depth below ground surface
of bedrock in feet.

depthto topofscreen

Number

w/decima

precision
up to 15

Not required

Depth in feet below ground
surface to the top of the well
screen. This information is
required to obtain the vertical
location from which the
groundwater sample was
taken.

Leave null if well is not at
this location.

depthtobottomofsc
reen

Number

w/decima

precision
up to 15

Not required

Depth in feet below ground
surface to bottom of well
screen. This information is
required to obtain the vertical
location from which the
groundwater sample was
taken.

Leave null if well is not at
this location.

topcasingelev

Number
w/decimal
precision
up to 15

Not required

Elevation of the top of casing
in feet.

Leave null if well is not at
this location.

datumvalue

Number
w/decimal
precision
up to 15

Not required

Datum value

datum unit

Text (15)

If available

Datum unit

Table A-18

Region 5 EDD Comprehensive Specification Manual
Version 4.3 36

United States
Environmental Protection Agency

-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

steporlinear

Text (6)

Not required

This field is for by EPA
Region 5 future use. Please
leave null.

Value: 'Step', 'Linear'

datumcollectmethod
code

Text (2)

Not required

Datum collect method

datum desc

Text(70)

Not required

Datum description

Datum start date

DateTime

Not required

Datum start date

3.5 Alternate Position

Table 3-5 Alternate Position (EPAR5AlternatePosition_v3) file data structure
EPAR5AlternatePosition (EPAR5AlternatePosition_v3.txt (or .csv)

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Sysloccode

Text(20)

Required

Unique Station or Well ID.
Required for mapping.

Coordtypecode

Text (20)

Required

Unique identifier describing
coordinate system in which
this location is referenced
(WGS 1984).

Identifier

Text(20)

Required

Text identifier that
facilitates unique
representation of the
coordinate system. Unless
this is a second set of LAT
LONG coordinates, enter
"PRIMARY".

observation_date

Date

Date observation or
subfacility survey was
made.

Altxcoord

Text(20)

Longitude of sampling
location in decimal degrees,
(dd.xxxxxxxx). Eight
decimal places are desired
but must have at least 6
decimal places.

Alt_y_coord

Text(20)

Latitude of sampling
location in decimal degrees,
(dd.xxxxxxxx) Eight
decimal places are desired
but must have at least 6
decimal places.

Elev

Text(20)

Alternate elevation.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 37

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Elevunit

Text(15)

Unit of measurement for
elevations. Units must be f
for feet or m for meters.

Horz collect method
_code

Text(20)

Use codes in horizontal
collection method valid
value table in appendix.
Method used to determine
the latitude/longitude.

Horzaccuracyvalue

Text(20)

Accuracy range (+/-) of the
latitude and longitude.

Only the least accurate
measurement should be
reported, regardless if it is
for latitude or longitude.

Horzaccuracyunit

Text(15)

Use values in unit valid
value table in appendix.
Unit of the horizontal
accuracy value.

Horzdatumcode

Text(20)

Use codes in horizontal
datum valid value table in
appendix. Reference datum
of the latitude and
longitude.

Elev_collect_method_
code

Text(20)

Use codes in elevation
collection method valid
value table in appendix.
Method used to determine
the ground elevation of the
sampling location.

Elevaccuracyvalue

Text(20)

Accuracy range (+/-) of the
elevation measurement.

Elevaccuracyunit

Text(8)

Use values in unit valid
value table in appendix.
Unit of the elevation
accuracy value.

Elevdatumcode

Text(20)

Reference datum for the
elevation measurement.
Must use valid value from
elevdatum table in
appendix.

Source_scale

Text(2)

Scale of the source used to
determine the latitude and
longitude. Must be a valid
code from the source_code
table from appendix. If
GPS is used scale does not
apply and 'N' should be
entered.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 38

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Subcontractor_name_
code

Text(20)

Code used to represent the
subcontractor or party
responsible for providing
coordinate information.

V erification_code

Text(20)

Code that represents the
process used to verify the
coordinate information.

Reference_point

Text(2)

Use codes in Reference
point valid value table in
appendix. Describes the
place at which geologic
coordinates were
established.

Geometric_type_code

Text(20)

Please enter POINT. If you
have coordinates that are
not specific to a point,
please email EPA for an
addition.

Remark

Text(255)

remark.

Rank

Numeric

Enter a rank if you are or
have submitted more than
one set of coordinates.

3.6 Location Parameter

Table 3-6 Location Parameter

EPAR5LOCPARAM V3

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sys loc code

Text(20)

Unique Location Name

parameter_code

Text(20)

Code used to identify
parameter being measured,
observed, or attribute being
described

parameter_value

Text(255
)

Value of parameter

parameter unit

Text(15)

Parameter unit

measurement_date

DateTim

Date of parameter
measurement or observation

measurement method

Text(20)

Measurement method

remark

Text(200

Remark

task_code

Text(40)

Code used to identify the
task under which the field
sample was taken.

activity type

Text(40)

required for EDGE

Region 5 EDD Comprehensive Specification Manual
Version 4.3 39

United States
Environmental Protection Agency

-------
3.7 Drill Activity EDD File

The drill activity (DRA) EDD file contains general information pertaining to the drilling activities
resulting from the soil boring. Each drill activity file must be named according to the following
convention:

EPAR5DRA_v3.txt (or .csv)

Table 3-7 Drill activity (EPAR5DRA_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text (20)

Required

Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in the
sys loc code field of the location EDD file
(Table 3-4) submitted in the current or
previous EDD.

drillevent

Text (20)

Required

Used to identify drilling event. Examples of
drilling events could be "initial" for initial
drilling or "second" for a subsequent
drilling at the same sys loc code.

startdepth

Number
w/decimal
precision
up to 7

Not

required

The start depth, in feet below ground
surface, of the drilling.

enddepth

Number
w/decimal
precision
up to 7

Not

required

End depth, in feet below ground surface of
the drilling.

drilldate

Date Time

Not

required

Date drilling began

MM/DD/YYYY
format.

Diameter

Number
w/decimal
precision
up to 7

Not

required

Diameter of boring.

diameterunit

Text (15)

available

Unit corresponding to measured diameter.
See Table A-18 in the Appendix for
appropriate value.

Table A-18

drillmethod

Text (50)

Not

required

Method used to drill boring.

fluid

Text (50)

Not

required

Description of fluid used during drilling.

viscosity

Text (50)

Not

required

Viscosity of drilling fluid.

hammerwt

Text (50)

Not

required

Weight of hammer, in pounds, used for
sampling.

hammerfall

Text (50)

Not

required

Distance of hammer fall during sampling in
inches.

liftmechanism

Text (50)

Not

required

Type of mechanism used to lift hammer.

new_Yn

Text (1)

Not

required

This field is to indicate whether this is a
new boring. Enter "Y" for yes or "N" for
no.

Y = yes
N= no

Region 5 EDD Comprehensive Specification Manual
Version 4.3 40

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

repair_yn

Text (1)

Not

required

Is this drilling event to repair an existing
boring? "Y" for yes or "N" for no.

Y = yes
N= no

deepen_yn

Text (1)

Not

required

Is this drilling event to deepen an existing
boring? "Y" for yes or "N" for no.

Y = yes
N= no

abandon_yn

Text (1)

Not

required

Has the boring been abandoned? "Y" for
yes or "N" for no.

Y = yes
N= no

replace_yn

Text (1)

Not

required

Is this boring event to replace an existing
boring? "Y" for yes or "N" for no.

Y = yes
N= no

public_yn

Text (1)

Not

required

Is well being install for a public use? "Y"
for yes or "N" for no.

Y = yes
N= no

Purpose

Text (70)

Not

required

Describe the purpose of the boring event.

3.8 Lithology EDD File

The lithology (LTH) EDD file contains all the lithology data for soil borings. For each lithologic unit, 16
fields are available for populating with data about the boring. Optional comments can be recorded in the
remark 1 and remark2 fields to describe depth-specific observations within a lithologic unit. Each
lithology EDD file must be named according to the following convention:

EPAR5LTH_v3.txt (or .csv)

Table 3-8 Lithology (EPAR5LTH_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Valued
In Appendix

sysloccode

Text(20)

Required

Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in
the sys loc code field of the location
EDD file (Table 3-4) submitted in the
current or previous EDD.

startdepth

Number
w/decimal
precision
up to 15

Required

The start depth, in feet below ground
surface, of the lithologic unit.

materialtype

Text(40)

available

The type of material that composes the
lithologic unit. See Table A-19 in the
Appendix for appropriate values.

Table A-19

geounitcodel

Text(20)

available

The data provider's interpretation of the
hydrogeologic unit present at this
lithologic unit, e.g., aquifer 1, aquitard 1,
aquifer 2, upper clay unit. See Figure A-
2 in the Appendix for examples.

geo_unit_code_2

Text(20)

available

Alternate geologic unit grouping. This
can be a sub-classification of
geologic unit code l or a layer used for
groundwater flow/transport computer
modeling that contains the lithologic unit.
See Figure A-2 in the Appendix for
examples.

remarkl

Text(255)

Not

required

Comments (if any) on the lithologic unit.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 41

United States
Environmental Protection Agency

-------
Table 3-8 Lithology (EPAR5LTH_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Valued
In Appendix

remark_2

Text(255)

Not

required

Additional comments on the lithologic
unit.

Moisture

Text(l)

Not

required

Was any moisture detected within the
lithologic unit? "Y" for yes or "N" for no.

Y = yes
N=No

Permeable

Text(20)

Not

required

Description of the permeability of the
lithologic unit such as "impervious,"
"semi," "pervious," or "very."

consolidatedyn

Text(l)

Not

required

Was lithologic unit consolidated? "Y" for
yes or "N" for no.

Y=yes
N=no

Color

Text(20)

Not

required

Color of the lithologic unit.

Observation

Text(255)

Not

required

General field observations of the
lithologic unit.

Consistency

Text(20)

Not

required

Description of the consistency of the soil,
such as "very soft," "soft," "firm," "hard"
or "very hard."

Sorting

Text(20)

Not

required

Geologic description of the grain size
distribution of the lithologic unit. Use
"poor" for soil with a wide range of
particle sizes or "well" for soil with a
narrow range of particle sizes.

Grainsize

Text(20)

Not

required

Description of grain size.

Odor

Text(20)

Not

required

Description of odor from the soil.

3.9 Well EDD File

The well (EPAR5WEL_v3) EDD file contains general information relating to well installation. Each well
file must be named according to the following convention:

EPAR5WEL_v3.txt (or .csv)

Table 3-9 Well (EPAR5WEL_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Value
In Appendix

sysloccode

Text(20)

Required

Well installation location Must be a valid
code for the facility and must match one of
the reported values in the sys loc code
field of the location EDD file (Table 3-4)
submitted in the current or previous EDD.

Alternate Well
id

Text(30)

Not required

Well identification number

welldescriptio
n

Text(30)

Not required

Used for additional well description if
necessary.

well owner

Text(30)

Not required

Name of entity that owns the well.

well_purpose

Text (20)

Not required

Purpose of well.

well status

Text (20)

Not required

Current status of well.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 42

United States
Environmental Protection Agency

-------
Table 3-9 Well (EPAR5WEL_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Value
In Appendix

top_casing_
elev

Number
w/decim
al

precision
up to 15

Not required

Elevation of the top of well casing.
Elevation must be in feet.

datumvalue

Number
w/decim
al

precision
up to 15

Required

Elevation of datum used to reference
measurement of water level depths. (EPA
normally uses top of well casing for datum.)

datum unit

Text(15)

Required

Unit of measure for the well datum..

Table A-18

datumdesc

Text (70)

Required

Description of the datum, such as "top of
well casing."

steporlinear

Text (6)

Not required

Use only for re-surveys of well elevations.
If a section of the well casing was removed
or added use "step" as the value. If nothing
was added or removed from the last survey,
use "linear" as the value.

Datumstartda
te

DateTim
e

Required

Date that datum was first used to take
measurements.

MM/DD/YYYY
format.

datum_collect_
methodcode

Text (2)

If available

Method used to determine the datum
elevation. Use codes from Table A-6 in the
Appendix

Table A-6

depthofwell

Number
w/decim
al

precision
up to 15

Not required

Depth below ground surface of the well
bottom.

depth unit

Text (15)

If available

Unit of measurement for depth.

Table A-18

depth_measure_
method

Text (20)

Not required

Method of measuring depth of well.

stickup height

Text (8)

Not required

Height of casing above ground surface.

stickup unit

Text (15)

If available

Unit of measure for the stickup height

Table A-18

sump length

Text (20)

Not required

Length of sump.

sump unit

Text (15)

If available

Unit of measure for the sump length.

Table A-18

Installationdat

Date

Not required

Date of well installation

MM/DD/YYYY
format.

construct_start_
date

DateTim
e

Not required

Date well construction began

MM/DD/YYYY
format.

constructcomp
lete date

DateTim
e

Not required

Date well construction was completed

MM/DD/YYYY
format.

construct_
contractor

Text (20)

If available

Name of contractor that installed well.

pumptype

Text (20)

Not required

Type of pump used at well such as
centrifugal, propeller, jet, helical, rotary,
etc.

pump capacity

Text (6)

Not required

Capacity of pump.

pumpunit

Text (15)

If available

Unit of measure for the pump capacity and
yield.

Table A-18

pump yield

Text (6)

Not required

The yield of the pump.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 43

United States
Environmental Protection Agency

-------
Table 3-9 Well (EPAR5WEL_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Value
In Appendix

pump_yield_
method

Text (20)

Not required

Method used for pump yield.

weephole

Text (1)

Not required

Is there a weep hole? "Y" for yes or "N" for
no.

Y=yes
N=No

headconfigurat
ion

Text (50)

Not required

Description of the well-head.

access_port_yn

Text (1)

Not required

Is there an access port? "Y" for yes or "N"
for no.

Y=yes
N=No

casing J ointty
pe

Text (50)

Not required

Type of casing joint, such as "threaded,"
"flush," or "solvent-welded."

Perforatorused

Text (50)

Not required

Description of well perforation, such as
"slotted," "drilled," or "wound."

intakedepth

Number
w/decim
al

precision
up to 15

Not required

Depth in feet below ground surface of the
well intake.

Feet

Disinfectedyn

Text (1)

Not required

Was well disinfected? "Y" for yes or "N"
for no.

Y=yes
N=No

historical_
referenceelev

Number
w/decim
al

precision
up to 15

Not required

Leave null.

geologicunitc
ode

Text (20)

If available

Geologic unit in which the well intake is
installed.

Remark

Text
(255)

Not required

Available for general remarks.

3.10 Well Construction EDD File

The well construction (WSG) file contains information relating to well construction and well segments.
Information is required for all well segments within each well, including surface plug, protective casing,
well casing, annular backfill, annular seal, screen, and filter pack. In order to obtain the depth of
groundwater samples, it is particularly important that the depths of the top and bottom of the well screen
be submitted for each well. Each well construction EDD file must be named according to the following
convention:

EPAR5WSG_v3.txt (or .csv)

Table 3-10 Well construction (EPAR5WSG_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Value
In Appendix

sysloccode

Text(20)

Required

Well installation location. Must be a valid
code for the facility and must match one
of the reported values in the sys loc code
field of the location EDD file (Table 3-4)
submitted in the current or previous EDD.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 44

United States
Environmental Protection Agency

-------
Table 3-10 Well construction (EPAR5WSG_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Value
In Appendix

segmenttype

Text(20)

Required

Type of segment within well (e.g.,
protective casing, well casing, screen,
etc.).

Table A-20

material_type_
code

Text(20)

Required

Material description of well segment. Use
values.

Table A-20

startdepth

Number
w/decimal
precision
up to 15

Required

Depth, in feet below ground surface, of
the top of the described segment.

enddepth

Number
w/decimal
precision
up to 15

Required

Depth, in feet below ground surface, of
the bottom of the described segment.

depth unit

Text(15)

Required

The unit of depth measurements.

Table A-18

innerdiameter

Number
w/decimal
precision
up to 15

Not

required

The inside diameter of the described
segment.

outerdiameter

Number
w/decimal
precision
up to 15

Not

required

The outside diameter of the described
segment.

diameterunit

Text(15)

available.

The unit of diameter measurements

Table A-18

Thickness

Number
w/decimal
precision
up to 15

Not

required

Thickness of the described well segment.

thicknessunit

Text(15)

available

The unit of measurement for thickness.

Table A-18

slottype

Text(20)

Not

required

Type of slots in screen segment such as
bridge, shutter, and continuous.

slotsize

Number
w/decimal
precision
up to 15

Not

required

Width of slots.

slotsizeunit

Text(15)

available

The unit of measurement for slot size..

Table A-18

perflength

Number
w/decimal
precision
up to 15

Not

required

Length of perforated portion of screen in
feet.

screentype

Text(15)

Not

required

Type of screen.

materialquant
ity

Text(20)

Not

required

Quantity of material used in pounds.
Applicable to annular seal/fill material.

materialdensi
ty

Text(20)

Not

required

Density of the annular seal material in
lbs/ft3.

Remark

Text(255)

Not

required

Remarks regarding the segment.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 45

United States
Environmental Protection Agency

-------
3.11 Geology Samples EDD File

The Geology Samples (GSMP) EDD file contains geotechnical sample information. (Samples results
related to chemical analyses should be reported using the Lab EDD.) Each Geology sample EDD file
must be named according to the following convention:

EPAR5GSMP_v3.txt (or .csv)

Table 3-11 Geology samples (EPAR5GSMP_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text(20)

Required

geo_sample_
code

Text(40)

Required

Unique sample identifier. Considerable
flexibility is given in the methods used to
derive and assign unique sample
identifiers, but uniqueness throughout the
database is the only restriction enforced.

samplename

Text(50)

Not

required

Use to provide a name or description of
sample. Does not have to be a unique
throughout database.

sampletop

Number
w/decimal
precision
up to 15

Required

Depth, in feet below ground surface, to
top of sample.

sample_
bottom

Number
w/decimal
precision
up to 15

Required

Depth, in feet below ground surface, to
bottom of sample.

Sampledate

DateTime

Not

required

Date sample was collected.

MM/DD/YYYY

HH:MM:SS

format

sample_
method

Text(30)

available

Method used to obtain sample, e.g., split
spoon or Shelby tube.

materialtype

Text(40)

available

Material type of geologic sample. .

Table A-8

sampledesc

Text(255)

Not

required

General description of the sample or
sampling activities.

geologic_
unit code

Text(20)

available

Code used to identify the geologic unit of
the sample.

liquidlimit

Number
w/decimal
precision
up to 7

Not

required

Liquid limit (LL) of the sample.

plasticlimit

Number
w/decimal
precision
up to 7

Not

required

Plastic Limit (PL) of the sample.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 46

United States
Environmental Protection Agency

-------
Table 3-11 Geology samples (EPAR5GSMP_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

slirinkage_
limit

Number
w/decimal
precision
up to 7

Not

required

Shrinkage limit of the sample.

flowindex

Number
w/decimal
precision
up to 7

Not

required

Flow index of the sample.

plasticity_
index

Number
w/decimal
precision
up to 7

Not

required

Plasticity index of the sample.

Activity

Number
w/decimal
precision
up to 7

Not

required

Activity of the sample.

Number
w/decimal
precision
up to 7

Not

required

Void ratio of the sample.

emax

Number
w/decimal
precision
up to 7

Not

required

Maximum void ratio of the sample.

emin

Number
w/decimal
precision
up to 7

Not

required

Minimum void ratio of the sample.

Number
w/decimal
precision
up to 7

Not

required

Porosity of the sample.

specific_
gravity

Number
w/decimal
precision
up to 7

Not

required

Specific gravity of the sample.

Number
w/decimal
precision
up to 7

Not

required

Water content of the sample.

optw

Number
w/decimal
precision
up to 7

Not

required

Optimum water content.

Number
w/decimal
precision
up to 7

Not

required

Degree of saturation of the sample.

Number
w/decimal
precision
up to 7

Not

required

Hydraulic conductivity of the sample.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 47

United States
Environmental Protection Agency

-------
Table 3-11 Geology samples (EPAR5GSMP_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

Kunit

Text(15)

available.

Unit of measure for K.

Table A-18

unitwt

Number
w/decimal
precision
up to 7

Not

required

Unit weight of the sample.

satunitwt

Number
w/decimal
precision
up to 7

Not

required

Saturated unit weight of the sample.

dryunitwt

Number
w/decimal
precision
up to 7

Not

required

Dry unit weight of the sample.

dry_unit_wt_
max

Number
w/decimal
precision
up to 7

Not

required

Maximum dry unit weight of the sample.

dry_unit_wt_
min

Number
w/decimal
precision
up to 7

Not

required

Minimum dry unit weight of the sample.

densityunit

Text(15)

available

Unit of measure for the densities of the
sample.

Table A-18

reldensity

Number
w/decimal
precision
up to 7

Not

required

Relative density of the sample.

rel_

compaction

Number
w/decimal
precision
up to 7

Not

required

Relative compaction of the sample.

Consistency

Text (20)

Not

required

Description of the consistency of the soil
sample such as very soft, soft, firm, hard
or very hard.

organic_
carbon

Number
w/decimal
precision
up to 7

Not

required

Organic carbon content of sample.

organic_
carbonunit

Text (15)

available

Unit of measurement of organic content.
Use values from Table A-18 of the
Appendix.

3.12 Water Levels

Region 5 EDD Comprehensive Specification Manual
Version 4.3 48

United States
Environmental Protection Agency

-------
The Water Level (EPAR5GWTR_v3) EDD file contains information on water levels measured during
sampling activities. Groundwater levels and surface water elevations should be reported using this file;
however, in most cases, the file will be used to report groundwater levels. When surface water samples
are collected, however, this EDD file should be used to record water surface elevations at the time the
samples were collected. Surface water elevations reported in this file will be used as the reference
elevation for surface water sample depths (i.e., start_depth, field 11, and end_depth, field 12 in the lab
Sample (EPAR5SMP_v3) EDD file. See Table 4-1). When using the Water Level EDD file for reporting
surface water data, only the first six fields (fields 1 through 6) and the "remark" field (field 17) should be
populated. All fields in the Water Level EDD file, however, should be populated for groundwater
elevation data (if data is available). An example of a Water Level file is provided in Figure 2-4, section
2.16. Each water level file must be named according to the following convention:

EPAR5GWTR_v3.txt (or .csv)

Table 3-12 Water Level (EPAR5GWTR_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text(20)

Required

Water level measurement
location. Must be a valid
code for the facility and
must match one of the
reported values in the
sys loc code field of the
location EDD file (Table 3-
4) submitted in the current
or previous EDD.

Measurement
date

DateTime

Required

Date of water level
measurement
If exact date is not known,
enter the best estimate for
the date of sampling. If an
estimated date is entered,
note this and provide an
explanation for how the
estimate was made in both
the EDD cover letter and in
the comment field in this
file (field 10).

MM/DD/YYYY

HH:MM:SS

format

Region 5 EDD Comprehensive Specification Manual
Version 4.3 49

United States
Environmental Protection Agency

-------
Table 3-12 Water Level (EPAR5GWTR_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

historical_
referenceelev

Number
w/decimal
precision
up to 15

Required

For groundwater samples,
the value in this field should
be the elevation, in feet
above mean sea level, of the
reference point used to take
measurements of the water
level depth. Typically the
reference point for
groundwater measurements
is the top of the well casing.

For surface water samples,
the value in this field should
be the elevation of the
surface water in feet above
mean sea level.

If elevation is given in units
other than feet above mean
sea level, please indicate the
unit used in the remarks
field (field 17).

waterlevelde
pth

Number
w/decimal
precision
up to 7

Required

For groundwater, the value
in this field should be the
depth of ground water
below the elevation defined
in historical reference elev
field (field 5).

For surface water, the value
in this field should be the
default value of "0"

waterlevelel
ev

Number
w/decimal
precision
up to 7

Not required

Elevation of water level.
Elevation must be in feet.

Feet

corrected dept
h

Number
w/decimal
precision
up to 7

Not required

Depth of water level after
any necessary corrections,
e.g., if free product was
encountered.

correctedelev

Number
w/decimal
precision
up to 7

Not required

Corrected water level
elevation that corresponds
to the corrected depth.
Elevation must be in feet.

feet

measureddept
h_

ofwell

Number
w/decimal
precision
up to 7

Not required

The depth below ground
surface to the bottom of the
well.

depthunit

Text (15)

If available

Unit used for depth
measurements. See Table A-
18 in the Appendix for
appropriate values.

Table A-18

Region 5 EDD Comprehensive Specification Manual
Version 4.3 50

United States
Environmental Protection Agency

-------
Table 3-12 Water Level (EPAR5GWTR_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

Technician

Text (30)

Not required

Name of technician
measuring water level

dry_indicator_
yn

Text (1)

Not required

This field is used to indicate
whether or not a well is dry
-- "Y" for yes or "N" for no.

Y= yes
N=No

measurement
method

Text (20)

Not required

Method used to make water
level measurements.

batchnumber

Text (10)

Not required

Batch number of group of
measurements.

diporelevati
on

Text (10)

Not required

Use either "elevation" or
"dip." Use "elevation" if
water level measurement is
above the datum (i.e.,
artesian well) or "dip" if
water level is below datum.

Elevation
Dip

Remark

Text (255)

Not required

Any necessary remarks
related to groundwater or
surface water information
provided in this EDD file.

Lnaplcasrn

Text (15)

If applicable

Analyte code of the light
non-aqueous phase liquid
(lnapl) present in the well.
Use appropriate valid value
from Table A-15 in the
EDD Specification Manual
Valid Value Appendix.

Table A-15

Lnapldepth

Text

Number

with

precision
of up to 7

Not required

Depth to the top surface of
the lnapl in feet below the
reference elevation.

Dnaplcasrn

Text (15)

If applicable

Analyte code of the dense
non-aqueous phase liquid
(dnalp) present in the well..

Table A-15

Dnapledepth

Number
with

precision
of up to 7

Not required

Depth to the top surface of
the dnapl in feet below the
reference elevation

Taskcode

Text(40)

Required

Code used to associate
individual samples to a
specific sampling event. The
format for this field is XX-P#,
XX is the type of task
required and P# is the
phase.

3.13 Water Table EDD Files

The water table (EPAR5TBL_v3) EDD file stores data pertaining the water table and is used to record
groundwater data during drilling activities. Each water table EDD file must be named according to the
following convention:

Region 5 EDD Comprehensive Specification Manual
Version 4.3 51

United States
Environmental Protection Agency

-------
EPAR5TBL v3.txt (or .csv)

Table 3-13 Water table (EPAR5TBL_v3) file data structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text (20)

Required

Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in
the sys loc code field of the location
EDD file (Table 3-4) submitted in the
current or previous EDD.

Type

Text (20)

Required

Aquifer designation, such as unconfinedl,
confinedl, or confined2.

Sequence

Text (20)

Required

Designation of when water level
measurement was taken. Use
"unstabilized" if measurement was taken
before water stabilized and use
"stabilized" if measurement taken after
stabilization.

Depth

Number
w/decimal
precision
up to 15

Required

Depth of water table, in feet, below
reference point.

Feet

flowing_yn

Text (1)

Not

Required

Is the water table flowing? "Y" for yes or
"N" for no.

1/3 O

ii ii
^ £

measurement
method

Text (50)

Not required

Method of measuring water table depth.

capped_pressu
re

Number
w/decimal
precision
up to 15

Not required

Hydrostatic pressure of confined aquifer.

capped_pressu

re_

unit

Text (15)

If available

Unit of measure for capped pressure. Use
values from Table A-18 in the Appendix.

Table A-18

reference_poin
t

Text (50)

Not required

Description of reference point from which
depth measurements were taken.

referenceelev
ation

Number
w/decimal
precision
up to 15

Required

Elevation of the reference point from
which depth measurement were taken.
Elevation must be in feet.

Temperature

Number
w/decimal
precision
up to 15

Not required

Temperature of water in the water table.

temperatureu
nit

Text (15)

If available

Unit of temperature. Use values from
Table A-18 in the Appendix.

Table A-18

Region 5 EDD Comprehensive Specification Manual
Version 4.3 52

United States
Environmental Protection Agency

-------
3.14 Geology Down Hole Point Data EDD File

The Geology downhole point data (DHP) EDD file stores data from down hole logging methods such as
Cone Penetrometer Tests and geophysics. All down hole logging data should be submitted electronically.
Report the parameter being measured in the "param" field, such as resistivity, and report the measured
value at the depth of the measurement. Table 3.14a presents the DHP EDD file structure.

Each Geology downhole point data EDD file must be named according to the following convention:

EPAR5DHP_v3.txt (or .csv)

Table 3-14 Geology Downhole Point (EPAR5DHP_v3) File Data Structure

Pos#

Column
Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text(20)

Required

Depth

Number
w/decimal
precision
up to 15

Required

Depth of measurement below ground surface
in feet.

Param

Text(20)

Required

The parameter being measured, such as tip
stress, resistivity, or pore pressure.

paramvalue

Number
w/decimal
precision
up to 15

Required

The measured value of the parameter.

Paramunit

Text(15)

Required

Measured unit of the parameter

Table 3.14a Example of downhole point data file

Sysloccode

Depth

Param

ParamValue

MW01

10.8

Tip Stress

612

MW01

11.2

Tip Stress

624

MW01

10.8

Sleeve Stress

6.1

MW01

11.2

Sleeve stress

5.8

MW02

9.5

Resistivity

510

MW02

10.1

Resistivity

521

MW02

11.0

Resistivity

889

3.15 Extraction - Injection Well (EPAR5EIW_v3) EDD File

The Extraction-Injection Well (EIW) EDD file should be submitted on a regular (e.g., quarterly) basis for
all sites where extraction and/or injection wells are a part of the remedial action at the site. The purpose
of the EIW EDD file is to provide EPA Region 5 with designed pumping rates as well as the actual
pumping rates for each well during a particular reporting period. This information will be useful for
determining if the remedial system is successfully capturing the contaminant plume. An example of an

Region 5 EDD Comprehensive Specification Manual
Version 4.3 53

United States
Environmental Protection Agency

-------
Extraction-Injection Well file is provided in Figure 2-4, section 2.16. Each Extraction-Injection Well
EDD file must be named according to the following convention:

EPAR5EIW v3.txt (or .csv)

Table 3-15 Extraction-Injection Well (EPAR5EIW_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sysloccode

Text(20)

Required

Well installation location. Must be a
valid code for the facility and must
match one of the reported values in the
sys loc code field of the location EDD
file (Table 3-4) submitted in the current
or previous EDD.

startmeasuredate

DateTime

Required

Date that the pumping rate
measurements began.

MM/DD/YYYY
HH:MM:SS format

endmeasuredate

DateTime

Required

Date that the pumping rate
measurements concluded in
MM/DD/YYYY HH:MM:SS format.

MM/DD/YYYY
HH:MM:SS format

avg_pump_rate

Number
w/decimal
precision
up to 15

Required

Average pumping rate. Recommended
method is to use volume pumped
divided by the reported date span, i.e.,
from the (start measurement date to
end measurement date)

pumprateunit

Text(15)

Required

Unit of measure for the pumping rate.
Use values from Table A-18 in the
Appendix.

Table A-18

pctoperatingtime

Text(3)

Not required

Percentage of the measurement time
interval during which the well was
operating. Use a value from 0 to 100
(do not include the percent symbol,

"%").

operating_
mode

Text(14)

Required

Mode in which well was operating
during the reported interval.

EXTRACTION,
INJECTION,
RECIRCULATION,
PULSE, DEVEL,
UNUSE.

designrate

Text(14)

Required

Pumping rate as specified in the
approved remedial design report for
fully capturing site groundwater
contamination.

designrateunit

Text(14)

Required

Unit of measure for the design pumping
rate. Use values from Table A-18 in the
Appendix.

Table A-18

ratemeasurementt
ype

Text(14)

Not required

Type of measurements used for
averaging.

TOTALIZER
(totalizing flow
meter), MANIFOLD
(estimated from total
manifold flow),
ESTIMATE
(estimate from prior
values), AVERAGE
(average of
instantaneous
measurements

Region 5 EDD Comprehensive Specification Manual
Version 4.3 54

United States
Environmental Protection Agency

-------
Table 3-15 Extraction-Injection Well (EPAR5EIW_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

suction

Text(14)

Not required

Vacuum in well (e.g., wellpoint
vacuum) or well casing (e.g., vacuum
well), reported in equivalent feet of
water.

remark

Text(255)

Not required

Remarks regarding the pumping rate
measurements.

3.16 Soil Gas Data EDD File

The soil gas (EPAR5SoilGas_v3) data file contains soil gas survey data.

Each Soil Gas data EDD file must be named according to the following convention:

EPAR5SoilGas_v3.txt (or .csv)

Table 3-16 Soil Gas (EPAR5SoilGas_v3) Survey file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values

In Appendix

sys loc code

Text(20)

Required

Sample collection location

N/A

survey date

Datetime

Required

Sample survay date

N/A

Parametercode

Text(20)

Required

Parameter measured by soil gas
survey

N/A

Readingdepth

Text(8)

Not required

Depth of soil gas survey
measurement

N/A

Reading unit

Text(15)

If available

Parameter measured by soil gas
survey

N/A

Reading

Text(8)

Not required

Soil gas survey measurement

N/A

Depthunit

Text(15)

If Available

Unit of measure of soil gas survey
measurement

N/A

Sampling method

Text(10)

Not required

Sampling method

N/A

Instrument type

Text(15)

Not required

Instrument type

N/A

East

Text(14)

Not required

Easting coordinate of soil gas
survey measurement

N/A

North

Text(14)

Not required

Northing coordinate of soil gas
survey measurement

N/A

Secondaryeast

Text(14)

Not required

Secondary easting coordinate of
soil gas survey measurement

N/A

Secondary north

Text(14)

Not required

Secondary easting coordinate of
soil gas survey measurement

N/A

Lithology code

Text(10)

Not required

Lithology code

N/A

Area desc

Text(70)

Not required

Discription of area

N/A

Equipment code

Text(60)

Not required

Equipment_code

N/A

Boreholedrillmet
hod

Text(10)

Not required

Drilling method

N/A

Technician

Text(50)

Not required

Technician

N/A

Remark

Text(255)

Not required

remark

N/A

Region 5 EDD Comprehensive Specification Manual
Version 4.3 55

United States
Environmental Protection Agency

-------
3.17 SAMPLE PARAMETER

EPAR5SAMPLEPARAM_v3.txt (or .csv)

Table 3-17 Sample Parameter (EPAR5SAMPLEPARAM_v3) Survey file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values

In Appendix

sys_sample_code

Text(40)

Unique sample identifier. Each
sample must have a unique value,
including spikes and duplicates.
Laboratory QC samples must also
have unique identifiers. The
laboratory and the EQuIS user
have considerable flexibility in
the methods they use to derive
and assign unique sample
identifiers, but uniqueness
throughout the database is the
only restriction enforced by
EQuIS.

N/A

measurement_dat
e

DateTim

Measurement date and time

N/A

param code

Text(20)

Parameter code

N/A

paramvalue

Text(255
)

Parameter value

paramunit

Text(15)

Unit of measure for parameter
value

measurement_me
thod

Text(20)

Measurement method

remark

Text(200

Remark

Region 5 EDD Comprehensive Specification Manual
Version 4.3 56

United States
Environmental Protection Agency

-------
4. FORMATS FOR LAB FILES

This section contains tables that define the file structures for the Chemistry EDD. The file structures
include chemistry sample, sample parameter, test/result QC, and Batch file. Please notice that some
columns are labeled as "Reserved for future use." These columns should simply be reported as null
values and are only needed to comply with standard EQuIS® reporting formats. Columns marked
"Required" must be reported for each row. If an EDD is submitted with one or more "Required" fields
not filled in, EPA will not be able to load the EDD into its database, and the EDD will have to be returned
to the data provider for correction(s). Columns marked "If available" should be filled in if at all possible.

4.1 Lab Sample EDD File

The Chemistry Sample EDD file contains data for samples collected at a site and location. The unique
identifier for each sample is recorded in the sys_sample_code. For trip blank samples, please record the
sys sample code as "TB" plus the date on which the sample was collected in MMDDYY format. For
example a trip blank collected on April 5, 2000 would have a sys_sample_code of TB040500. A
sys sample code of 'Trip Blank' is unacceptable because it cannot be distinguished from another trip
blank labeled the same way. For samples that are not associated with a specific sampling location, such
as trip blanks or field blanks, leave the sys_loc_code field (field 10) null. For surface water samples,
record the sample depths, start_depth (field 11) and end_depth (field 12), as depth below the water
surface elevation. The water surface elevation at the time of the sampling should be recorded in the
Water Level file (see Section 4.3). An example of a Lab Sample file is provided in Figure 2-4, section
2.16.

Each Lab Sample file must be named according to the following convention:

EPAR5SMP v3.txt (or .csv)

Table 4-1 Lab sample (EPAR5SMP_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Data provider

Text (20)

Required

Date provider company code

A-23

syssamplecode

Text(40)

Required

Unique sample identifier. Each sample at a
facility must have a unique value, including
spikes and duplicates. You have
considerable flexibility in the methods used
to derive and assign unique sample
identifiers; however, uniqueness throughout
the database is required.

samplename

Text(50)

Not required

Additional sample identification
information as necessary. Is not required to
be unique (i.e., duplicates are OK). Can be
the same value as in the sys sample code
field.

samplematrixcode

Text(3)

Required

Code that identifies the matrix being
sampled, such as soil, groundwater, or
sediment. For acceptable valid values, see
Table A-l in the Appendix.

Table A-l

Region 5 EDD Comprehensive Specification Manual
Version 4.3 57

United States
Environmental Protection Agency

-------
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sampletypecode

Text(3)

Required

Code that distinguishes between different
types of samples, such as normal field
samples versus laboratory method blank
samples. For acceptable valid values see
Table A-12 in the Appendix.

Table A-12

samplesource

Text(10)

Required

Identifies where the sample originated. Use
either "Field" or "Lab". Use "Field" for all
samples originating from the field and use
"Lab" if sample originated from the
laboratory.

Field
Lab

parentsamplecode

Text(40)

Required for
field
duplicate
samples

Unique identifier of the original sample
from which the current sample was derived,
i.e. the "parent" sample. Required for
samples with a sample type code of "BD",

"FD", "FR", "FS", "LR", "MS", "MSD" or
"SD."

sample_delivery_
group

Text(10)

Not required

EPA and most EPA Reigon 5 data providers
are accustomed to using the Contract
Laboratory Program (CLP) document
definition of the sample delivery group
(SDG). However, the CLP definition of an
SDG relates to a lab payment group which
is not what is being asked for in this field.
For the purposes of this field in this EDD,
the value entered should correspond more to
the "sampling event/ matrix" with which the
sample is associated. For example, the
SDG for ground water samples should be
different from that for surface water
samples. This will prevent flags associated
with surface water matrix effects from
being propagated to ground water results

sampledate

DateTime

Required

Date sample was collected in
MM/DD/YYYY HH:MM:SS format.

MM/DD/YYYY

HH:MM:SS

format.

sysloccode

Text(20)

Required*

Sample collection location. Must be a valid
code for the facility and must match one of
the reported values in the sys loc code
field of the location EDD file (Table 3-4)
submitted in the current or previous EDD.
* Field should be null if sample is not
associated with a specific location, such as
QC samples (e.g., field blank, trip blank)
and this code cannot be the same as
sys sample code

startdepth

Number
w/decimal
precision
up to 15

Not required

Beginning depth (top) of sample in feet
below ground surface for Soil or
Groundwater sample. Only use for
groundwater samples if discrete samples are
taken at different depth elevations from a
single well, i.e. multiple well packer
samples.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 58

United States
Environmental Protection Agency

-------
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

enddepth

Number
w/decimal
precision
up to 15

Not required

Ending depth (bottom) of sample in feet
below ground surface for Soil or
Groundwater sample. Only use for
groundwater samples if discrete samples are
taken at different depth elevations from a
single well, i.e. multiple well packer
samples.

depthunit

Text(15)

If available

Unit of measurement for the sample
beginning and end depths. For valid values,
see Table A-18 in the Appendix.

Table A-18

chainofcustody

Text(15)

Not required

Chain of custody identifier. A single sample
may be assigned to only one chain of
custody.

senttolabdate

DateTime

Not required

Date sample was sent to lab in
MM/DD/YYYY format.

samplereceiptdate

DateTime

Not required

Date that sample was received at laboratory
in MM/DD/YYYY format.

sampler

Text(30)

Not required

Name or initials of sampler.

samplingcompanyc
ode

Text(10)

Required

Name or initials of consulting company
performing sampling. (This field does not
have a controlled vocabulary, i.e., there is
no table of valid values for this field.)

sampling reason

Text(30)

Not required

Reason for Sampling

sampling technique

Text(40)

If available

Sampling technique.

taskcode

Text(40)

Required

Code used to associate individual samples
to a specific sampling event. The format for
this field is XX-P#, XX is the type of task
required and P# is the phase.

collection quarter

Text(5)

Not required

Report as null.

composite_yn

Text(l)

Required

Is sample a composite sample? Enter "Y"
for yes or "N" for no.

Y= Yes
N=No

compositedesc

Text(255)

Not required

Description of composite sample. If sample
is not a composite, leave this field null.

sampleclass

Text(10)

Not required

Report as null.

custom field 1

Text (20)

Not required

Report as null.

custom_field_2

Text(50)

Not required

Report as null.

custom field 3

Text(50)

Not required

Report as null.

comment

Text(255)

Not required

Any comments regarding the sample.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 59

United States
Environmental Protection Agency

-------
4.2 Lab Test Results EDD Files

The Lab Test Results EDD files contain data relating data concerning analytical tests and results
performed on samples.

Each Lab Test Results EDD file must be named according to the following convention:

EPAR5TRS v3.txt (or .csv)

Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

syssamplecode

Text(40)

Required

Sample identifier of the sample that was
tested and analyzed. Must match one of
the reported values in the
sys sample code field of the
EPAR5SMP_v3 file submitted in the
current or previous EDD.

lab_anl_method_
name

Text(20)

Required

Laboratory analytical method name or
description. For acceptable valid values,
see Table A-16 in the Appendix. Default
to "Unknown" if data is unavailable.

Table A-16

analysisdate

DateTim
e

Required

Date of sample analysis in
MM/DD/YYYY HH:MM:SS format.
May refer to either beginning or end of
the analysis. For measurements taken in
the field (e.g., pH, dissolved oxygen),
use the same date as sample date

totalordissolved

Text(l)

Required

Must be either "D" for dissolved or
filtered [metal] concentrations, and "T"
for every other case.

A-24

columnnumber

Text(2)

Not required

Report as null.

test type

Text(10)

Required

Type of test

A-25

labmatrixcode

Text(3)

If available

Code that identifies the matrix, such as
soil, groundwater, and sediment, being
sampled... The matrix of the sample as

analyzed may be different from the
matrix of the sample as retrieved (e.g.,
leachates), so this field is available at
both the sample and test level.

Table A-l

analysislocation

Text(2)

Required

Must be either "FI" for field instrument or
probe (i.e, "in the field" measurements
such as pH, temperature, conductivity,
and dissolved oxygen), "FL" for mobile
field laboratory analysis, or "LB" for an
analysis done at a fixed-based laboratory.

FI = Field
Instrument
FL = Mobile

Field lab
LB = Fixed
based lab

Region 5 EDD Comprehensive Specification Manual
Version 4.3 60

United States
Environmental Protection Agency

-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Basis

Text(10)

Required

Must be "Wet" for wet-weight basis
reporting, "Dry" for dry-weight basis
reporting, or "NA" for tests for which this
distinction is not applicable. EPA prefers
that results are reported on the basis of
dry weight where applicable.

Wet= wet-weight
Dry= dry weight
N/A = not
applicable

container id

Text(30)

Not required

Report as null.

dilution factor

Number

Not required

Effective test dilution factor.

w/decim
al

precision
up to 7

prepmethod

Text(20)

If available

Laboratory sample preparation method
name or description. Must use valid value
from Table A-14 in the Appendix.

Table A-14

prepdate

DateTim
e

Not required

Beginning date of sample preparation

MM/DD/YYYY
HH:MM:SS
format

leachatemethod

Text(15)

Not required

Laboratory leachate generation method
name or description. The method name
should be sufficient to reflect the
operation methodology used by the
laboratory (see analysis method
discussion).

leachatedate

DateTim
e

Not required

Beginning date of leachate preparation

MM/DD/YYYY
HH:MM:SS
format

labnamecode

Text(20)

If available

Unique identifier of the laboratory as
defined by the EPA. Controlled
vocabulary..

[Note: If the lab you are using does not
appear in Table A-17, you may propose a
valid value for the lab for addition to the
EPA Region 5 list. Please provide
information about the lab in the cover
letter accompanying your EDD
submittal.]

Table A-17

qclevel

Text(10)

Not required

Not limit to "Screen" or "Quant", visit
Appendix B in the

https://semspub.epa.aov/work/HO/17
6101 .pdf for more values

labsampleid

Text(20)

Not required

Laboratory LIMS sample identifier. If
necessary, a field sample may have more
than one LIMS lab sample id (maximum
one per each test event).

Region 5 EDD Comprehensive Specification Manual
Version 4.3 61

United States
Environmental Protection Agency

-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

percentmoisture

Text(5)

Not required

Percent moisture of the sample portion
used in this test; this value may vary from

test to test for any sample. Numeric
format is "NN.MM," i.e., 70.1% could be
reported as "70.1" but not as "70.1%."

subsample_
amount

Text(14)

Not required

Amount of sample used for test.

subsample_
amountunit

Text(15)

If available

Unit of measurement for subsample
amount. Must use valid value from Table
A-18 in the Appendix.

Table A-18

analyst name

Text(30)

Not required

Report as null.

instrument id

Text(50)

Not required

Report as null.

comment

Text(255
)

Not required

Comments about the test as necessary.

preservative

Text(20)

If available

Sample preservative used.

finalvolume

Numeric

Not required

The final volume of the sample after
sample preparation. Include all dilution
factors.

finalvolumeunit

Text(15)

If available

The unit of measure that corresponds to
the final amount.

cas rn

Text(15)

Required

Analyte code..

Table A-15

chemical name

Text(75)

Required

Chemical name..

Table A-15

resultvalue

Numeric

Not required

Analytical result reported at an
appropriate number of significant digits.

resulterrordelta

Text(20)

Not required

Error range applicable to the result value;
typically used only for radiochemistry
results.

resulttypecode

Text(3)

Required

Must be either "TRG" for a target or
regular result, "TIC" for a tentatively
identified compound. Use "TRG" for
measurements taken from the field (e.g.,
pH, dissolved oxygen)

TRG = Target or

regular
TIC = Tentative
identified

reportableresult

Text(10)

Required

Must be either "Yes" for results that are
considered to be reportable, or "No" for

other results. This field has many
purposes. For example, it can be used to

distinguish between multiple results
where a sample is retested after dilution.
It can also be used to indicate which of
the first or second column result should
be considered primary. The proper value
of this field in both of these two examples
should be provided by the laboratory
(only one result should be flagged as
reportable).

Yes
No

Region 5 EDD Comprehensive Specification Manual
Version 4.3 62

United States
Environmental Protection Agency

-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

detectflag

Text(2)

Required

Maybe either "Y" for detected analytes or
"N" for non-detects. "Y" should be used
for detected target compounds and TICs
only (i.e. result type code is "TRG" or
"TIC").

Also use "Y" for estimated (above
detection limit but below the quantitation
limit) or ">" and "<" for tests such as
flash point. Note that "<" must not be
used to indicate non-detects.

Y = detected
N = non-detects

lab qualifiers

Text(10)

Not required

Qualifier flags assigned by the laboratory.

validatorqualifiers

Text(10)

Not required

Qualifier flags assigned by the person
who validates the laboratory data. The
interpret qualifier is required if
lapqualifer or validator qualifier are
populated

Interpretedqualifier

Text(20)

If available/
Required

Interpreted qualifier flag assigned by the
data provider. The interpret qualifier is
required if lap qualifer or validator
qualifier are populated

Table A-10

Validated yn

Text (1)

Required

Indicates if the result has been validated

organicyn

Text(l)

Required

Must be either" Y" for organic
constituents or "N" for inorganic
constituents. Use "Y" for measurements
taken from the field (e.g., pH, dissolved
oxygen)

Y= organic
N= inorganic

method_detection_
limit

Text(20)

Not required

Report as null. The minimum
concentration of an analyte that can be
measured and reported with 99%
confidence that the analyte concentration
is greater than zero, as determined for a
specific procedure.

reporting_detection_
limit

Numeric

Not required

Must be reported if sample result is "non-
detect." The minimum concentration of
an analyte that can be measured and
reported with 99% confidence that the
analyte concentration is greater than zero,
as determined for a specific procedure,
which is equal to or greater than the
MDL.

quantitationlimit

Text(20)

Not required

Concentration level above which results
can be quantified with confidence. The
value must reflect conditions such as
dilution factors and moisture content, and
must be sample-specific.

resultunit

Text(15)

If available

Units of measurement for the result. Must
use valid values from Table A-18 in the
Appendix.

Table A-18

Region 5 EDD Comprehensive Specification Manual
Version 4.3 63

United States
Environmental Protection Agency

-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

detectionlimitunit

Text(15)

If available

Units of measurement for the detection
limit(s). Must use valid value from
Table A-18 in the Appendix.

Table A-18

tic retention time

Text(8)

Not required

Report as null.

resultcomment

Text(255
)

Not required

Result specific comments.

4.3 Lab Test/Result with QC Data EDD File

The Lab test/results with QC (TRSQC) EDD file contains data from analytical tests performed on
samples along with quality control data.

Each Chemistry test/results with QC EDD file must be named according to the following convention:

Region 5 EDD Comprehensive Specification Manual
Version 4.3 64

United States
Environmental Protection Agency

-------
EPAR5TRSQC_v3.txt (or .csv)

Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

syssamplecode

Text(
40)

Required

Sample identifier of the sample that
was tested and analyzed. Must match
one of the reported values in the
sys sample code field of the
EPAR5SMP_v3 file submitted in the
current or previous EDD.

lab_anl_method_
name

Text(
20)

Required

Laboratory analytical method name or
description. For acceptable valid
values. Default to "Unknown" if data
is unavailable.

Table A-16

analysisdate

DateT
ime

Required

Date of sample analysis in
MM/DD/YYYY HH:MM:SS format.
May refer to either beginning or end of
the analysis. For measurements taken
in the field (e.g., pH, dissolved
oxygen), use the same date as sample
date

T otalordissolved

Text(

Required

Enumeration list contains the values

A-24

columnnumber

Text(
2)

Not required

Column number, if null, "NA" will be
placed in this field

testtype

Text(
10)

Required

Type of test.

A-25

labmatrixcode

Text(
3)

If available

Code that identifies the matrix, such as
soil, groundwater, and sediment.

The matrix of the sample when it is
analyzed may be different from the
matrix of the sample when it is
collected (e.g. leachates), so this field
is available at both the sample and test
level.

Table A-l

analysislocation

Text(
2)

Required

Must be either "FI" for field instrument
or probe (i.e, "in the field"
measurements such as pH, temperature,
conductivity, and dissolved oxygen),
"FL" for mobile field laboratory
analysis, or "LB" for an analysis done
at a fixed-based laboratory.

FI = Field
Instrument
FL = Mobile
Field lab
LB = Fixed
based lab

Basis

Text(
10)

Required

Must be either "Wet" for wet-weight
basis reporting, "Dry" for dry-weight
basis reporting, or "NA" for tests for
which this distinction is not applicable.
EPA prefers that results are reported on
the basis of dry weight where
applicable.

Wet= wet-
weight
Dry= dry
weight
N/A = not
applicable

containerid

Text(
30)

Not required

Report as null.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 65

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

dilutionfactor

Nume
ric

Not required

Effective test dilution factor.

prepmethod

Text(
20)

If available

Laboratory sample preparation method
name or description. Must use valid
value from Table A-14 in the
Appendix.

Table A-14

prepdate

DateT
ime

Not required

Beginning date of sample preparation.

MM/DD/YY
YY

HH:MM:SS
format

leachatemethod

Text(
15)

Not required

Laboratory leachate generation method
name or description. The method name
should be sufficient to reflect the
operation methodology used by the
laboratory (see analysis method
discussion).

leachatedate

DateT
ime

Not required

Beginning date of leachate preparation

MM/DD/YY
YY

HH:MM:SS
format

labnamecode

Text(
20)

If available

Unique identifier of the laboratory as
defined by the EPA. Controlled
vocabulary; see the lab valid value
table in appendix.

Table A-17

qclevel

Text(
10)

Not required

Not limit to "Screen" or "Quant",
visit Appendix B in the

httDs://semsDub.eDa.eov/work/H
O/176101.Ddf for more values

labsampleid

Text(
20)

Not required

Laboratory LIMS sample identifier. If
necessary, a field sample may have
more than one LIMS lab sample id
(maximum one per each test event).

percentmoisture

Text(
5)

Not required

Percent moisture of the sample portion
used in this test; this value may vary
from test to test for any sample.
Numeric format is "NN.MM," i.e.,
70.1% could be reported as "70.1" but
not as "70.1%."

subsampleamount

Text(
14)

Not required

Amount of sample used for test.

subsample_amount_
unit

Text(
15)

If available

Unit of measurement for subsample
amount. Must use valid value from
Table A-18 in the Appendix.

Table A-18

analystname

Text(
30)

Not required

Report as null.

instruments

Text(
50)

Not required

Report as null.

Comment

Text(
255)

Not required

Comments about the test, if necessary.

Preservative

Text(
20)

If available

Sample preservative used.

Table A-27

Region 5 EDD Comprehensive Specification Manual
Version 4.3 66

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

finalvolume

Nume
ric

Not required

The final volume of the sample after
sample preparation. Include all dilution
factors.

finalvolumeunit

Text(
15)

If available

The unit of measure that corresponds to
the final amount.

Table A-18

casrn

Text(
15)

Required

Analyte code..

Table A-15

chemicalname

Text(
75)

Required

Chemical name.

Table A-15

Resultvalue

Nume
ric

Not required

Analytical result reported at an
appropriate number of significant
digits. May be blank for non-detect
results.

Resulterrordelta

Text(
20)

If available

Error range applicable to the result
value; typically used only for
radiochemistry results.

Resulttypecode

Text(
10)

Required

Must be either "TRG" for a target or
regular result, "TIC" for a tentatively
identified compound, "SUR" for
surrogates, "IS" for internal standards,
or "SC" for spiked compounds. Use
"TRG" for measurements taken from
the field (e.g., pH, dissolved oxygen).
'CAL' for calculated pore water
concentrations.

Table A-11

reportableresult

Text(
10)

Required

Must be either "Yes" for results that are
considered to be reportable, or "No" for
other results. This field has many
purposes. For example, it can be used
to distinguish between multiple results
where a sample is retested after
dilution. It can also be used to indicate
which of the first or second column
result should be considered primary.
The proper value of this field in both of
these two examples should be provided
by the laboratory.

Yes
No
Y
N

detectflag

Text(
2)

Required

Maybe either "Y" for detected analytes
or "N" for non-detects. "Y" should be
used for detected target compounds and
TICs only (i.e. result type code is
"TRG" or "TIC").

Also use "Y" for estimated (above
detection limit but below the
quantitation limit) or ">" and "<" for
tests such as flash point. Note that "<"
must not be used to indicate non-
detects.

Y= detected
N = non-
detects

Labqualifiers

Text(
10)

Not required

Qualifier flags assigned by the
laboratory.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 67

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

validatorqualifiers

Text(
10)

Not required

Qualifier flags assigned by the person
who validates the laboratory data.

Interpretedqualifier
s

Text(
10)

If available

Interpreted qualifier flag assigned by
the validator. When the validated_yn =
N (no, meaning the data is not validated
by validator), the interpret qualifier is
required if labqualifier or validator
qualifier are populated. If the
validated_yn = Y (yes, meaning the
data has been validated and the
validator agreed witht eh lab qualifier),
then they should populate the
validator qualifier and the
interpreted qualifier. If the
validated_yn = Y (yes, but the validator
does not agree with the lab qualifier),
then the validator will leave the
qualifier NULL and the final qualifier
is also NULL. When populating th e
interpreted qualifier, please use the
qualifier in the Valid Value in A-10
with the description that can closely
match with the lab qualifier.

A-10

Validated_yn

Text

(1)

Required

Must be either" Y" for validate or "N"
for not validate.

Indicated if
the result has
been
validated

Organic_yn

Text(

Required

Must be either Y' for organic
constituents or 'N' for inorganic
constituents.

methoddetectionli
mit

Text(
20)

If available

Report as null. The minimum
concentration of an analyte that can be
measured and reported with 99%
confidence that the analyte
concentration is greater than zero, as
determined for a specific procedure.

reporting_detection_
limit

Nume
ric

Not required

Must be reported if sample result is
"non-detect." The minimum
concentration of an analyte that can be
measured and reported with 99%
confidence that the analyte
concentration is greater than zero, as
determined for a specific procedure,
which is equal to or greater than the
MDL.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 68

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

quantitationlimit

Text(
20)

Not required

Quantitation limits refer to a
minimum concentration of an
analyte that can be measured
within specified limits of precision
and accuracy. They are generally
5-10 times the detection limit.

Thus, when quantitation limits are
used as reporting limits, the
laboratory is saying that the analyte
is not present in a sufficient amount
to be reliably quantified (i.e., at a
concentration above the
quantitation limit).

It may be present and even
positively identified or "seen" at a
lower concentration.

Resultunit

Text(
15)

If available

Units of measurement for the result.
Must use valid values from Table A-18
in the Appendix.

Table A-18

detection_limit_
unit

Text(
15)

If available

Units of measurement for the detection
limit(s). Must use valid value from
Table A-18 in the Appendix.

Table A-18

ticretentiontime

Text(
8)

Not required

Report the value and time when the
result type is TIC.

Resultcomment

Text
(255)

Not required

Result specific comments

qcoriginalconc

Nume
ric

Not required

The concentration of the analyte in the
original (unspiked) sample. Might be
required for spikes and spike duplicates
(depending on user needs). Not
necessary for surrogate compounds or
LCS samples (where the original
concentration is assumed to be zero).

qcspikeadded

Nume
ric

Not required

The concentration of the analyte added
to the original sample. Might be
required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample (depending on user
needs).

qcspikemeasured

Nume
ric

Not required

The measured concentration of the
analyte. Use zero for spiked
compounds that were not detected in
the sample. Might be required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample (depending on user needs).

Region 5 EDD Comprehensive Specification Manual
Version 4.3 69

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

qcspikerecovery

Nume
ric

Not required

The percent recovery calculated as
specified by the laboratory QC
program. Always required for spikes,
spike duplicates, surrogate compounds,
LCS and any spiked sample. Report as
percentage multiplied by 100 (e.g.,
report "120%" as "120").

qc_dup_original_
cone

Nume
ric

Not required

The concentration of the analyte in the
original (unspiked) sample. Might be
required for spike or LCS duplicates
only (depending on user needs). Not
necessary for surrogate compounds or
LCS samples (where the original
concentration is assumed to be zero).

qc_dup_spike_
added

Nume
ric

Not required

The concentration of the analyte added
to the original sample. Might be
required for spike or LCS duplicates,
surrogate compounds, and any spiked
and duplicated sample (depending on
user needs). Use zero for spiked
compounds that were not detected in
the sample. Required for spikes, spike
duplicates, surrogate compounds, LCS
and any spiked sample. Also complete
the qc-spike-added field.

qc_dup_spike_
measured

Nume
ric

Not required

The measured concentration of the
analyte in the duplicate. Use zero for
spiked compounds that were not
detected in the sample. Might be
required for spike and LCS duplicates,
surrogate compounds, and any other
spiked and duplicated sample
(depending on user needs). Also
complete the qc spike measured field.

qc_dup_spike_
recovery

Nume
ric

Not required

The duplicate percent recovery
calculated as specified by the
laboratory QC program. Always
required for spike or LCS duplicates,
surrogate compounds, and any other
spiked and duplicated sample. Also
complete the qc spike recovery field.
Report as percentage multiplied by 100
(e.g., report "120%" as "120").

qcrpd

Text(
8)

Not required

The relative percent difference
calculated as specified by the
laboratory QC program. Required
for duplicate samples as
appropriate. Report as percentage
multiplied by 100 (e.g., report
"30%" as "30").

Region 5 EDD Comprehensive Specification Manual
Version 4.3 70

United States
Environmental Protection Agency

-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

qcspikelcl

Text(
8)

Not required

Lower control limit for spike recovery.
Required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample. Report as percentage
multiplied by 100 (e.g., report "60%" as
"60").

qcspikeucl

Text(
8)

Not required

Upper control limit for spike recovery.
Required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample. Report as percentage
multiplied by 100 (e.g., report "120%"
as "120").

qcrpdcl

Text(
8)

Not required

Relative percent difference control
limit. Required for any duplicated
sample. Report as percentage
multiplied by 100 (e.g., report "25%" as
"25").

qcspikestatus

Text(
10)

Not required

Used to indicate whether the spike
recovery was within control limits. Use
the character to indicate failure,
otherwise leave blank. Required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample.

qc_dup_spike_
status

Text(
10)

Not required

Used to indicate whether the duplicate
spike recovery was within control
limits. Use the character to indicate
failure, otherwise leave blank. Required
for any spiked and duplicated sample.

qcrpdstatus

Text(
10)

Not required

Used to indicate whether the relative
percent difference was within control
limits. Use the character to indicate
failure, otherwise leave blank. Required
for any duplicated sample.

4.4 Lab Batch Data (EPAR5BAT v3) EDD File

The Lab Batch (EPAR5BAT_v3) EDD file contains data that relate the individual samples to the
laboratory batch identifier. For the most part, as with the TestResultQC EDD file, the BATCH EDD file
will only need to be submitted by EPA contractors that are submitting quality data elements with their
reports. The purpose of this EDD file is so laboratory quality control samples can be associated with the
correct field samples with which they were processed and analyzed. This EDD file has been structured to
allow samples to have different batch IDs for various phases of analysis (e.g., preparation phase, analysis
phase). The majority of samples will only have one batch ID assigned by the laboratory. It is important
that the values in the sys_sample_code, lab_anl_method_name, analysis_date, analysis_time,
total or dissolved and test type fields match those found in the TestResultQC EDD files. Each
Chemistry batch file must be named according to the following convention:

EPAR5BAT_v3.txt (or .csv)

Table 4-4 Lab batch file (EPAR5BAT_v3) data structure

Region 5 EDD Comprehensive Specification Manual
Version 4.3 71

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data type

Required

Description

Valid Values
In Appendix

syssamplecode

Text(40)

Required

Sample identifier of the sample that was
tested and analyzed. Must match one of
the reported values in the
sys sample code field of the
EPAR5 SMP_v3 file (Table 4-1)
submitted in the current or previous EDD.

lab_anl_method_
name

Text(20)

Required

Laboratory analytical method name or
description. For acceptable valid values,
see Table A-16 in the Appendix. Default
to "Unknown" if data is unavailable.

Table A-16

analysisdate

Datetime

Required

Date of sample analysis. May refer to
either beginning or end of the analysis.

MM/DD/YYYY

HH:MM:SS

format.

totalordissolved

Text(l)

Required

Enumeration list contains the values

A-24

columnnumber

Text(2)

Not

required

Report as null.

testtype

Text(lO)

Required

Type of test.

A-25

testbatchtype

Text(lO)

Required

Lab batch type.

This is a required field for all batches.

A-26

test batch id

Text(20)

Required

Unique identifier for all lab batches.

5. VAPOR INTRUSION

FORMATS FOR VAPOR INTRUSION FILES

Vapor Intrusion data submittals contain data of sampling taken inside of the contaminated sites or
buildings.

5.1 Vapor Intrusion Building Address EDD File

The Vapor Intrusion Building Address (EPAR5_VI_BLDG_ADDRESS_V3) contains address and
contact information for the building.

Each Vapor Intrusion file must be named according to the following convention:

EPAR5 VI_BLDG_ADDRESS_V3
Table 5-1 Vapor Intrusion Building Address data structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

buildingcode

Text (20)

Required

Unique code that identifies the
building within the facility (i.e.
B001,B002, etc.)

Region 5 EDD Comprehensive Specification Manual
Version 4.3 72

United States
Environmental Protection Agency

-------
2

Subfacilitycode

Text (20)

Required

Code indicating the subfacility
operable unit (OU) for which the
data is collected or area of concern
(AOC). Use the code 'OU1' unless
there are additional operable units
at a facility. In the case of
additional operable units, use codes
of'OU2', 'OU3', etc.,
respectively.Must match the code in
the Subfacility_v4 EDD file
submitted in the current or previous
EDDs.

Taskcode

Text (40)

Required

For soil vapor intrusion sampling
and building inspection information
enter "SVI".

contactname

Text (50)

Required

Building Contact Name: This
should be populated with the EPA
Project Manager name. Occupant or
Owner personal information (Name,
telephone numbers, and address)
are NOT to be included for SVI
Building Information.

address 1

Text (40)

Required

Building address, part one.

address2

Text (40)

Building address, part two

city

Text (30)

Required

Building city

state

Text (2)

Required

Building state

zipcode

Text (10)

Required

Building zipcode

county

Text (50)

available

Building county

phone number

Text (30)

Required

Building contact phone number

alt_phone_number

Text (30)

Alternative site phone number

fax_number

Text(30)

Building contact fax number.

email_address

Text(100)

Required

Building contact email address.

remark

Text(2017)

Remark

Remark_2

Text(2017)

Remarts

5.2 Vapor Intrusion Building Inspection EDD Files

The Vapor Intrusion Building (EPAR5_VI_BLDG_INSPECTION_V3) contains specific data about the
building.

Each Vapor Intrusion building file must be named according to the following convention:
EPAR5 VI_BLDG_INSPECTION_V3

Region 5 EDD Comprehensive Specification Manual
Version 4.3 73

United States
Environmental Protection Agency

-------
Table 5-2 Vapor Intrusion Building Inspection data structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

buildingcode

Text(20)

Required

Unique code that identifies the
building within the facility (i.e.
B001, B002, etc.)

Inspectiondate

DateTime

Required

Enter the date the building
inspection was conducted (in
MM/DD/YYYY HH:MM format).

Taskcode

Text(40)

Required

For soil vapor intrusion sampling
and building inspection information
enter "SVI".

buildingname

Text(255)

Required

Building name (i.e. Denison Medical
Building)

building_type

Text(20)

Required

Type of building (i.e. Residential,
Industrial, etc.)

Building_use_type

Text(20)

Required

Enter the building's use type such
as Dry Cleaner, Day Care if
commercial or Ranch Home if
Residential.

building_size

Text(20)

Size of building (Small, Medium,
Large)

num_floors

Numeric

Number of floors in the building

construct_year

Numeric

Year of construction

foundation_depth

Numeric

Foundation depth (below ground
surface)

foundation_depth_
unit

Text(15)

Foundation depth unit

foundation_type

Text(20)

Required

Foundation type (i.e. Basement,
crawlspace, ect.)

foundation_wall_m
aterial

Text(20)

Foundation wall material

fou ndation_floor_m
aterial

Text(20)

Foundation floor material

foundation_wall_thi
ckness

Numeric

Foundation wall thickness

fou ndation_floor_th
ickness

Numeric

Foundation floor thickness

foundationjtiickne
ss unit

Text(15)

Foundation thickness units

attached_garage_y
n

Text (1)

Existance of an attached garage
(Y/N)?

radon_mitigation_y
n

Text (1)

Existance of radon mitigation
system (Y/N)?

heat_fuel_type

Text(255)

Type of heating fuels (i.e. Natural
gas)

heat_system_type

Text(255)

Type of heating system (i.e. Forced
hot air)

centra l_air_yn

Text (1)

Existance of central air system
(Y/N)?

Region 5 EDD Comprehensive Specification Manual
Version 4.3 74

United States
Environmental Protection Agency

-------
23

sump_yn

Text (1)

Existance of sump pump (Y/N)?

voc_mitigation_yn

Text (1)

VOC mitigation flag (Y/N)?

remark

Text(2017)

Building remarks

custom_field_l

Text(255)

custom_field_2

Text(255)

custom_field_3

Text(255)

custom_field_4

Text(255)

custom_field_5

Text(255)

5.3 Vapor Intrusion Building Parameters EDD File

The Vapor Intrusion Building Parameters (EAR5_VI_BLDG_PARAMETERS_v3) contains additional
sampling parameter collected in the field and not analyized in the lab.

Each Vapor Intrusion Task Parameter file must be named according to the following convention:

EPAR5 VI_BLDG_PARAMETERS_V3

Table 5-3 Vapor Intrusion Building Parameters data structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

Building_code

Text(20)

Required

Unique code that identifies the
building within the facility (i.e.
B001, B002, etc.) For additional
information, please refer to the EDD
Manual.

param_code

Text(20)

Required

A unique parameter code designed
for buildings such as the Soil Vapor
Intrusion Building Inventory Form
parameters found on
rt_su bfacil ity_pa ra meter_type.

task_code

Text(40)

Required

For soil vapor intrusion sampling
and building inspection information
enter "SVI."

measurement_date

DateTime

Required

The specific date the measurement
was collected. For Soil Vapor
Intrusion form data, the date
should be the building inspection
date (in MM/DD/YYYY HH:MM)

param_value

Text(255)

Required

The value related to the parameter
code used.

param_unit

Text(15)

The corresponding unit that relates
to the parameter value used.

Enumeration list

remark

Text(2017)

A comment or other free text to
further describe the parameter code
or parameter value.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 75

United States
Environmental Protection Agency

-------
5.4 Vapor Intrusion Locations EDD file

The Vapor Intrusion Location (EPAR5 VI LOCATIONS V3) contains locations information.

Each Vaport Intrustion Locaiton file must be named according to the following convention:

EPAR5 VI LOCATIONS_V3
Table 5-4 Vapor Intrusion Location data structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

data_provider

Text(20)

Required

Data provider for location data.

Must be the valid code for the data
provider for this subfacility and
match the data_provider field of the
DataProvider EDD file submitted in
the current or previous EDDs.

A-23

sys_loc_code

Text(20)

Required

Location identifier of sample
collection. Use sample location ID.
Must be unique for each OU or
Building. Example: RESIDENT01-
BSMT for a sample location type
(Basement) contained within
building code RESIDENT01.
Additional informaiton is provided in
the EDD Manual. Non alpha-
numeric characters (save for the
underscore _ and the dash -
characters) are prohibited in the
sys_loc_code.

building_code

Text(20)

Required

Must be the valid code for a
building and match the
building_code field in the
VI_Bldg_Address_v4 EDD file
submitted in the current or previous
EDD.

latitude

Numeric

Required

Latitude of sampling location in
decimal degrees (dd.xxxxxx). Must
contain a minimum of 6 six
significant figures. Example:
43.020295 Note: Multiple
sys_loc_codes can share the same
coordinates if a centroid point is
used to represent sample locations
in a building.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 76

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

longitude

Numeric

Required

Longitude of sampling location in
decimal degrees. Must be negative
for western hemisphere (-
ddd.xxxxxx). Must contain a
minimum of 6 six significant figures.
Example: -73.740476 Note:

Multiple sys_loc_codes can share
the same coordinates if a centroid
point is used to represent sample
locations in a building.

coord_sys_desc

Text(20)

Required

Sampling location coordinate
system description. Must be
Latitude and Longitude based on
World Geodetic System 1984
(WGS84) datum. Valid Value is:
Lat/Long.

observation_date

DateTime

Date observation or site survey was
made (in MM/DD/YYYY HH:MM
format).

alt_x_coord

Text(20)

x-Coordinate in alternate system.

alt_y_coord

Text(20)

y-Coordinate in alternate system.

a lt_coord_type_cod
e

Text(20)

Must reference alternate coordinate
system type code. SP designates
State Plane.

altjdentifier

Text(20)

If providing alternate coordinates in
state plane, UTM Zone 17, or UTM
Zone 18, enter PRIMARY.

horz_collect_metho
d_code

Text (3)

Required

Method used to determine
latitude/longitude. Example: SI is
for NYS Licensed Professional Land
Survey.

horz_accuracy_valu
e

Text(20)

Required

Accuracy range (+/-) of the latitude
and longitude. Use "0.1" for
professional survey, "100" for site
centroid, or "10" for all other
methods.

horz_accuracy_unit

Text(15)

Required

Unit of the horizontal accuracy.

horz_datum_code

Text (3)

Required

This is the reference datum for the
original survey coordinates.
Example: If the latitude and
longitude were calculated from a
NAD83 survey, the code would be
"002". If the coordinates are
directly from a GPS survey, enter
"003" for WGS84.

source_scale

Text (2)

If coordinates were derived from a
published map, enter the scale of
the map source (e.g. 1 inch = 100
feet).

Region 5 EDD Comprehensive Specification Manual
Version 4.3 77

United States
Environmental Protection Agency

-------
Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

subcontractor_nam
e code

Text(20)

Required

Code used to distinguish
subcontractor name.

verification_code

Text(20)

The verification code should
indicate how the survey
coordinate/elevation reference point
was verified.

reference_point

Text(50)

If coordinates and elevations were
surveyed using a traditional survey
method in the field without a GPS,
a description of the reference point
used as the survey benchmark,
(e.g. NYSDOT bridge footing, or
Hydrant at station 00+01 elevation
25).

loc_name

Text(40)

Provide a more detailed name for
sample location. 40 characters.
For example, "Laundry Room Soil
Vapor Sample Location."

loc_desc

Text(255)

Sampling location detailed
description. Example: "Laundry
room sample collected 4 feet above
ground surface to capture breathing
zone."

loc_type

Text(20)

Requied

Sampling location type. Use codes
in loc_type valid values table for
Soil Vapor Intrusion. Options
include: BASEMENT, CRAWLSPACE,
FIRST FLOOR, OUTDOOR,

SUBSLAB, and UPPER FLOOR.

loc_purpose

Text(20)

Sampling location purpose.
Example: "Odors detected in
basement," "Visible Floor
Penetrations."

within_facility_yn

Text (1)

Required

Indicates whether this sampling
location is within facility boundaries,
'Y' for yes or 'IN' for no.

loc_county_code

Text(20)

If availabe

Location county code is found
within the Valid Values Table.

loc_district_code

Text (3)

Use EPA Region number 002.

loc_state_code

Text (2)

If available

Location state code; controlled
vocabulary using FIPS codes.

remark

Text(255)

Location specific comment.

5.5 Vapor Intrusion Outdoor Locations EDD file

The Vapor Intrusion Outdoor Locations (EPAR5_VI_OUTDOOR_LOCATIONS_V3) contains samples
information.

Each Vapor Intrusion Outdoor Locations must be named according to the following convention:

Region 5 EDD Comprehensive Specification Manual
Version 4.3 78

United States
Environmental Protection Agency

-------
EPAR5 VI_OUTDOOR_LOCATIONS_V3
Table 5-5 Vapor Intrusion Outdoor Locations data structure

Pos#

Column Name

Data Type

Required

Description

Valid Values
In Appendix

Sysloccode

Text (20)

Required

Location identifier of sample
collection. Use sample location
ID. Must be unique for each OU
or Building. Example:
RESIDENT01-A for a sample
location contained within
building code RESIDENT01.
Additional informaiton is
provided in the EDD Manual.

Buildingloctyp
e code

Text (10)

Required

The default building loc type
should be OUTDOOR.

Buildingcode

Text (20)

Required

Must be the valid code for a
building and match the
building code field in the
VI Bldg Address EDD file
submitted in the current or
previous EDD.

5.6 Vapor Intrusion Sample EDD file

The Vapor Intrusion Sample (EPAR5VISAMPLESV3) contains samples information.

Each Vapor Intrusion Sample file must be named according to the following convention:

EPAR5 VI_SAMPLES_V3
Table 5-6 Vapor Intrusion Samples data structure

Pos

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

data_provider

Text(20)

REQUIRED

Data provider name

sys_sample_code

Text(40)

REQUIRED

Unique sample identifier

Sample_name

Text(50)

Required

Additional sample identification
information as necessary. Is not
required to be unique (i.e.,
duplicates are OK). Can be the
same value as in the
sys_sample_code field.

sample_matrix_code

Text (3)

REQUIRED

Code which distinguishes between
different type of sample matrix

Table A-l

Region 5 EDD Comprehensive Specification Manual
Version 4.3 79

United States
Environmental Protection Agency

-------
Pos

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

Sample_type_code

Text(20)

Rquired

Code that distinguishes between
different types of samples. Use
code from

rt_sample_type.sample_type_code
valid values table. Example:

Normal field samples are coded "IN",
laboratory method blank samples
are coded "LB", etc.

Sample_source

Text(10)

Required

This field identifies where the
sample originated. Samples
collected in the Field are entered as
"FIELD," samples originating in the
Lab are entered as "LAB."

Parent_sample_code

Text(40)

If the sample is a duplicate,
MS/MSD, blind dup, lab dup, etc,
input the parent sample
"sys_sample_code." For example:
A field duplicate "FD" (coded in
sample_type_code) is collected for
sample MW-001-20010606;
therefore, MW-001-20010606 is
input into this field. This field is left
null for all non-duplicate samples.
This field is Required when the
sample type code contains "BD,"
"FD," "FR," "FS," "LR," "MS,"
"MSD," or "SD" entries. Additional
information may be found in the
EDD Manual.

Sample_delivery_gro
up

Text(20)

This is the laboratory sample
delivery group.

sample_start_date

DateTime

REQUIRED

Sample start date and time

sys_loc_code

Text(20)

Location identifier of sample
collection

chain_of_custody

Text(40)

Chain of custody identifier. Note: A
single sample may be assigned to
only one chain of custody.

sent_to_lab_date

DateTime

Shipping date sample was sent to
lab (in MM/DD/YYYY HH:MM
format).

Sample_receipt_date

DateTime

Date that sample was received at
laboratory (in MM/DD/YYYY HH:MM
format).

sampler

Text(50)

Person taking sample.

sampling_company_c
ode

Text(20)

REQUIRED

Name or initials of sampling
company.

sampling_reason

Text(30)

Reason for sampling

sampling_method

Text(40)

Sampling method

task_code

Text(40)

Sampling task code

Region 5 EDD Comprehensive Specification Manual
Version 4.3 80

United States
Environmental Protection Agency

-------
Pos

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sample_end_date

DateTime

Sample end date and time

sample_du ration

Text(20)

The sampling duration

sa mple_d u ration_u n it

Text(15)

Sample duration units

Table A-18

floor_material

Text(20)

Lowest level floor material at
sample location

slab_thickness

Text(20)

Slab thickness at sample location
(in inches)

subfloor_material

Text(20)

Material found below the foundation
floor

subfloor_moisture

Text(20)

Moisture content at subslab sample
location (i.e. Dry, Damp, Saturated)

seal_type

Text(20)

Type of seal used during sampling
(i.e. Beeswax, Clay, Teflon Tape)

seal_adequate_yn

Text (1)

Did the sample probe seal pass the
tracer test (Y/N)?

purge_yn

Text (1)

Was the sample equipment purged
in accordance with work plan
(Y/N)?

purge_pid

Numeric

PID instrument reading

purge_pid_unit

Text(15)

PID instrument reading units (i.e.
PPb)

vac_gauge_initial

Numeric

Vacuum gauge reading immediately
after start

vac_gauge_final

Numeric

Vacuum gauge reading immediately
before end

vac_gauge_unit

Text(15)

Vacuum gauge instrument units
(i.e. inches of water)

vapor_loc_desc

Text(255)

Soil vapor intrusion location
description

remark

Text
(2017)

Remark

T racer_test_cond ucte
d_yn

Text (1)

Required

Enter a Y to indicate that the
helium tracer tests were conducted
and passed for any sub slab
samples.

5.7 Vapor Intrusion Test Result QC

The Vapor Intrusion Test Result QC (EPAR5 VI TESTRESULTSQC V3) contains data concerning
analytical tests performed on samples with quality control data elements.

Each Vapor Intrusion Test Result QC file must be named according to the following convention:

EPAR5 VI_TESTRESULTSQC_V3

Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data

Required

Description

Valid Values

Type

In Appendix

Region 5 EDD Comprehensive Specification Manual
Version 4.3 81

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sys_sample_code

Text(40)

REQUIRED

Unique sample identifier. Each
sample at a facility must have a
unique value, including spikes and
duplicates. You have considerable
flexibility in the methods used to
derive and assign unique sample
identifiers, but uniqueness
throughout the database is the only
restriction enforced by EQuIS®.

lab_anl_method_na
me

Text(35)

REQUIRED

Laboratory analytical method name
or description. A controlled
vocabulary column, valid values can
be found in the appendix in table
lab anl method name.

analysis_date

DateTime

REQUIRED

Date and time of sample analysis in
'MM/DD/YYYY HH:MM'format. May
refer to either beginning or end of
the analysis as required by EPA.

fraction

Text(10)

REQUIRED

Must be either 'D' for dissolved or
filtered [metal] concentration, or T
for everything else. If fraction =
'TCLP', then leachate_method and
leachate_date is required.

column_number

Text (2)

REQUIRED

Report as null.

test_type

Text(10)

REQUIRED

Type of test. Valid values include
'Initial', 'Reextractl', 'Reextract2',
'Reextract3', 'Reanalysis',

'Dilutionl', 'Diluton2', and 'Diluton3'.

lab_matrix_code

Text (3)

REQUIRED

Code which distinguishes between
different type of sample matrix. For
example, soil samples must be
distinguished from ground water
samples, etc. See matrix valid value
table in the appendix. The matrix of
the sample as analyzed may be
different from the matrix of the
sample as retrieved (e.g.
leachates), so this field is available
at both the sample and test level.

analysisjocation

Text (2)

REQUIRED

Must be either 'FI' for field
instrument or probe, 'FL' for mobile
field laboratory analysis, or 'LB' for
fixed_based laboratory analysis.

basis

Text(10)

REQUIRED

Must be either 'Wet' for wet_weight
basis reporting, 'Dry' for dry_weight
basis reporting, or 'NA' for tests for
which this distinction is not
applicable. The EPA prefers that
results are reported on the basis of
dry weight where applicable.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 82

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

containerjd

Text(30)

Report as null.

dilution_factor

Numeric

REQUIRED

Effective test dilution factor. If
value is less than 1, then you need
to put 'concentration factor' in the
comment column.

prep_method

Text(20)

AVAILABLE

Laboratory sample preparation
method name or description. A
controlled vocabulary (i.e., see
Prep_mthd_var valid values in the
appendix).

Table A-14

prep_date

DateTime

Beginning date and time of sample
preparation in 'MM/DD/YYYY
HH:MM' format.

lab_name_code

Text(20)

Unique identifier of the laboratory
as defined by the EPA. Controlled
vocabulary, see lab valid value table
in the appendix.

Table A-23

qcjevel

Text(10)

May be either 'screen' or 'quant'.

lab_sample_id

Text(40)

Laboratory LIMS sample identifier.
If necessary, a field sample may
have more than one LIMS
lab_sample_id (maximum one per
each test event).

percent_moisture

Text (5)

Percent moisture of the sample
portion used in this test; this value
may vary from test to test for any
sample. Numeric format is
'NN.MM', i.e., 70.1% could be
reported as '70.1' but not as
'70.1%'.

subsample_amount

Text(14)

Amount of sample used for test.

subsample_a mount
_unit

Text(15)

Unit of measurement for subsample
amount. Controlled vocabulary, see
Unit valid values table in appendix.

analyst_name

Text(30)

Report as null.

instrumentJd

Text(50)

Report as null.

comment

Text(255)

Comments about the test as
necessary.

preservative

Text(20)

Sample preservative used.

final_volume

Numeric

The final volume of the sample
after sample preparation. Include
all dilution factors.

final_volume_unit

Text(15)

The unit of measure that
corresponds to the final_volume.

cas_rn

Text(15)

REQUIRED

Use values in analyte valid value
table.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 83

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

chemical_name

Text(75)

REQUIRED

Use the name in the analyte valid
value table.

result_value

Numeric

Analytical result reported at an
appropriate number of significant
digits. May be blank for
non detects.

Result_unit

Text(15)

If available

result_error_delta

Text(20)

Error range applicable to the result
value; typically used only for
radiochemistry results.

result_type_code

Text(10)

REQUIRED

Must be either 'TRG' for a target or
regular result, 'TIC' for tentatively
identified compounds, 'SUR' for
surrogates, 'IS' for internal
standards, 'SC' for spiked,
compounds, 'CAL' for calculated
pore water concentrations.

reportable_result

Text(10)

REQUIRED

Must be either 'Yes' for results
which are considered to be
reportable, or 'No' for other results.
This field has many purposes. For
example, it can be used to
distinguish between multiple results
where a sample is retested after
dilution. It can also be used to
indicate which of the first or second
column result should be considered
primary. The proper value of this
field in both of these two examples
should be provided by the
laboratory.

detect_flag

Text (2)

REQUIRED

Maybe either 'Y' for detected
analytes or 'N' for non_detects. Use
'Y' for estimated (above detection
limit but below the quantitation
limit) or '<' and '>' for tests such as
flash point. Note that '<' must not
be used to indicate non_detects
(use 'N' for non_detects instead).

lab_qualifiers

Text(10)

Qualifier flags assigned by the
laboratory.

validator_qualifiers

Text(10)

Qualifier flags assigned by the
validation firm.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 84

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

i nterpreted_q ua 1 if ie
rs

Text(10)

Interpreted qualifier flag assigned by
the validator. When the validated_yn =
N (no, meaning the data is not validated
by validator), the interpret qualifier is
required if lab qualifier or validator
qualifier are populated. If the
validated mi = Y (yes, meaning the
data has been validated and the
validator agreed witht eh lab qualifier),
then they should populate the
validator qualifier and the
interpreted qualifier. If the
validated_yn = Y (yes, but the validator
does not agree with the lab qualifier),
then the validator will leave the
qualifier NULL and the final qualifier
is also NULL. When populating th e
interpreted qualifier, please use the
qualifier in the Valid Value in A-10
with the description that can closely
match with the lab qualifier. EPAR
region 2 is not going to add any more
qualifiers.

Table A-10

validated_yn

Text (1)

REQUIRED

Indicates if the result has been
validated.

Y= "Yes"
N= "No"

Region 5 EDD Comprehensive Specification Manual
Version 4.3 85

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

method_detection_l
imit

Text(20)

Lowest concentration that can be
detected by an instrument with
correction for the effects of sample
matrix and method-specific
parameters such as sample
preparation.

MDLs are explicitly determined as
set forth in 40 CFR Part 136. They
are defined as three times the
standard deviation of replicate
spiked analyses. This represents
99% confidence that the analyte
concentration is greater than zero.
The organic methods in the EPA
500 series, EPA 600 series, and
Standard Methods all give typical
MDLs for clean water samples.
Generally these clean-water MDLs
(corrected for %moisture, sample
size, and dilution) are used for
reporting limits,

but the laboratory may use MDLs
that they have generated. MDLs
generated by the laboratory using
the sample matrix of interest are
the most reliable. If the clean-water
MDLs are used, remember that they
do not include all of the upward
correction

necessary to account for the effects
of sample matrix. This is important
to remember especially for risk
assessments and highly
contaminated samples.

reporting_detection
Jimit

Numeric

Concentration level above which
results can be quantified with
confidence. It must reflect
conditions such as dilution factors
and moisture content.

Required for all results for which
such a limit is appropriate. The
reporting_detection_limit column
must be reported as the sample
specific detection limit.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 86

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

quantitationjimit

Text(20)

Quantitation limits refer to a
minimum concentration of an
analyte that can be measured
within specified limits of precision
and accuracy. They are generally
5-10 times the detection limit.

It may be present and even
positively identified or "seen" at a
lower concentration.

detection_limit_unit

Text(15)

Units of measurement for the
detection limit(s). Controlled
vocabulary, see Units valid value
table in the appendix. This field is
required if a

reporting_detection_limit is
reported.

tic_retention_time

Text (8)

Report as null.

minimum_detectabl
e_conc

Numeric

Minimum detectable concentration
or activity. This value should be in
the same units as the result value.

counting_error

Numeric

Counting error as reported by the
laboratory. This value should be in
the same units as the result value.

uncertainty

Text(10)

The uncertainty of the counting
error, valid values include "1 sigma"
or "2 sigma" This field is required if
the counting_error field is
populated.

critica Lvalue

Numeric

Critical value as reported by the
laboratory.

validationjevel

Text(20)

If available

If Validated_yn = Yes, then
validationjevel is required

result_comment

Text(255)

Result specific comments.

qc_original_conc

Numeric

The concentration of the analyte in
the original (unspiked) sample.
Might be required for spikes and
spike duplicates (depending on user
needs). Not necessary for surrogate
compounds or LCS samples (where
the original concentration is
assumed to be zero).

Region 5 EDD Comprehensive Specification Manual
Version 4.3 87

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

qc_spike_added

Numeric

The concentration of the analyte
added to the original sample. Might
be required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample
(depending on user needs).

qc_spike_measured

Numeric

The measured concentration of the
analyte. Use zero for spiked
compounds that were not detected
in the sample. Might be required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample (depending on user needs).

qc_spike_recovery

Numeric

The percent recovery calculated as
specified by the laboratory QC
program. Always required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"120%" as "120").

qc_dup_original_co
nc

Numeric

The concentration of the analyte in
the original (unspiked) sample.
Might be required for spike or LCS
duplicates only (depending on user
needs). Not necessary for surrogate
compounds or LCS samples (where
the original concentration is
assumed to be zero).

qc dup spike adde
d

Numeric

The concentration of the analyte
added to the original sample. Might
be required for spike or LCS
duplicates, surrogate compounds,
and any spiked and duplicated
sample (depending on user needs).
Use zero for spiked compounds that
were not detected in the sample.
Required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample. Also
complete the qc-spike-added field.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 88

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

qc_dup_spike_mea
sured

Numeric

The measured concentration of the
analyte in the duplicate. Use zero
for spiked compounds that were not
detected in the sample. Might be
required for spike and LCS
duplicates, surrogate compounds,
and any other spiked and
duplicated sample (depending on
user needs). Also complete the qc-
spike-measured field.

qc_dup_spike_reco
very

Numeric

The duplicate percent recovery
calculated as specified by the
laboratory QC program. Always
required for spike or LCS duplicates,
surrogate compounds, and any
other spiked and duplicated sample.
Also complete the qc-spike-recovery
field. Report as percentage
multiplied by 100 (e.g., report
"120%" as "120").

qc_rpd

Text (8)

qc_spike_lcl

Text (8)

Lower control limit for spike
recovery. Required for spikes,
spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"60%" as "60").

qc_spike_ucl

Text (8)

Upper control limit for spike
recovery. Required for spikes,
spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"60%" as "60").

qc_rpd_cl

Text (8)

Relative percent difference control
limit. Required for any duplicated
sample. Report as percentage
multiplied by 100 (e.g., report
"25%" as "25").

Region 5 EDD Comprehensive Specification Manual
Version 4.3 89

United States
Environmental Protection Agency

-------
Table 5-7 Vapor Intrusion Test Result QC file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

qc_spike_status

Text(10)

Used to indicate whether the spike
recovery was within control limits.
Use the "*" character to indicate
failure, otherwise leave blank.
Required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample.

qc_dup_spike_statu
s

Text(10)

Used to indicate whether the
duplicate spike recovery was within
control limits. Use the "*" character
to indicate failure, otherwise leave
blank. Required for any spiked and
duplicated sample.

qc_rpd_status

Text(10)

Used to indicate whether the
relative percent difference was
within control limits. Use the "*"
character to indicate failure,
otherwise leave blank. Required for
any duplicated sample.

lab_SDG

Text(20)

Lab Sample Delivery Group (SDG)
identifier. A single sample may be
assigned to multiple Sample
Delivery Group (SDG) based on
different analysis.

5.8 Vapor Intrusion Batch EDD File

Each Vapor Intrusion Batch file must be named according to the following convention:

EPAR5 VI BATCHES V3

Table 5-8 Vapor Intrusion Batches file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

sys_sample_code

Text(40)

REQUIRED

Unique sample identifier. Each
sample must have a unique value,
including spikes and duplicates.
Laboratory QC samples must also
have unique identifiers. The
laboratory and the EQuIS®
Chemistry user have considerable
flexibility in the methods they use
to derive and assign unique sample
identifiers, but uniqueness
throughout the database is the only
restriction enforced by EquIS®
Chemistry.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 90

United States
Environmental Protection Agency

-------
Table 5-8 Vapor Intrusion Batches file data structure

Pos#

Column Name

Data
Type

Required

Description

Valid Values
In Appendix

lab_anl_method_na
me

Text(35)

REQUIRED

Laboratory analytical method name
or description. A controlled
vocabulary column, valid values can
be found in the appendix in table
ab anl method name.

Table A-16

analysis_date

DateTime

REQUIRED

Date and time of sample analysis in
'MM/DD/YYYY HH:MM' format. May
refer to either beginning or end of
the analysis as required by EPA.

fraction

Text(10)

REQUIRED

For soil vapor intrusion samples,
enter "NA" for 'Not Applicable.' Must
match one of the reported values in
the fraction field of the
VI_TestResultsQC EDD table
submitted in the current EDD.

column_number

Text (2)

REQUIRED

Column number, if null, "NA" will be
placed in this field

test_type

Text(10)

REQUIRED

Type of test. Valid values include
'Initial', 'Reextractl', 'Reextract2',
'Reextract3', 'Reanalysis',

'Dilutionl', 'Diluton2', and 'Diluton3'.

test_batch_type

Text(10)

REQUIRED

Lab batch type. Valid values include
'Prep', 'Analysis', and 'Leach'. This is
a required field for all batches.

test_batch_id

Text(20)

Unique identifier for all lab batches.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 91

United States
Environmental Protection Agency

-------
6. TECHNICAL SUPPORT

EPA Region 5 provides technical support for users of this Comprehensive EDD Specification Manual.
For questions concerning data, data formats, and EDD submittal procedures, please contact EDD EQUIS
Coordinator. For more general questions, relating to the site, please contact the EPA RPM assigned to
the site.

Region 5 EDD Comprehensive Specification Manual
Version 4.3 92

United States
Environmental Protection Agency

-------