data management plan eureka smelter sites

EE-002693-2177

Data Management PlanEureka Smelter Sites

Assessment

Eureka, Eureka County, Nevada

TDD No.: TO-02-09-12-04-0002Project No.: EE-002693-2177

September 2012

Prepared for:

U.S. ENVIRONMENTAL PROTECTION AGENCYRegion 9 Emergency Response Section

75 Hawthorne StreetSan Francisco, CA.

Prepared by:

ECOLOGY AND ENVIRONMENT, INC.1940 Webster Street

Oakland, CA.

SDMS DOCID#1141234

iii

able of ContentsTSection Page

Executive Summary...............................................................................1-1

1 Purpose and Scope..................................................................1-11.1 Scenario ............................................................................................................ 1-11.2 Special Considerations and Privacy Concerns ................................................. 1-21.3 Summary of Revisions and Updates ................................................................ 1-2

2 Overall Work Flow....................................................................1-12.1 Data Flow and Data Flow Diagram.................................................................. 1-12.2 Roles and Responsibilities ............................................................................... 1-1

3 Data Collection............................................................................13.1 Field Data Collection Methodology.....................................................................1

3.1.1 Equipment and Instruments......................................................................13.1.2 Site-Specific Data Collection Procedures – Initial Entry.........................1

3.2 Data Deliverables .................................................................................................13.3 Data Collection SOPs and Checklists ..................................................................1

4 Data management ....................................................................3-14.1 Data Processing ................................................................................................ 3-14.2 Scribe Import Mapping .................................................................................... 3-14.3 Data Element Dictionary................................................................................. 3-34.4 Entity Relationship Diagram........................................................................... 3-44.5 Geospatial Management...................................................................................... 3-44.6 Critical Linkages between Tabular and Spatial Data ....................................... 3-54.7 Data Management SOPs and Checklists .......................................................... 3-5

5 Data Verification.......................................................................4-15.1 Verification SOPs and Checklists .................................................................... 4-15.2 SQL Verification Queries................................................................................. 4-1

6 Data Analysis and Reporting...................................................5-16.1 Data Users ........................................................................................................ 5-26.2 Reporting Requirements................................................................................... 5-26.3 Reporting SOPs and Checklists........................................................................ 5-26.4 SQL Reporting Queries .................................................................................... 5-26.5 GIS/Spatial Data Visualization Requirements ................................................. 5-2

A Draft Basic Scribe User Instructions ..................................... A-1

Table of Contents (cont.)

Section Page

iv

B Data Element Dictionary ....................................................... B-1

C Entity Relationship Diagram................................................. C-1

D SQL Verifications Queries .................................................... D-1

v

ist of TablesL

ist of Figures

ist of TablesL

L

Error! No table of figures entries found.

Error! No table of figures entries found.

1-1

Executive SummaryThe following Data Management Plan (DMP) is intended to present a framework for thegeneration, validation, and distribution of the removal assessment data and data deliverablesspecific to the Eureka Smelter Sites Removal Assessment. This DMP specifically describes datamanagement procedures for sampling data, field analysis data, laboratory analysis data,photography, global positioning system (GPS) data, field observation data, contact data and otherfield data for activities related to the Eureka Smelter Sites Removal Assessment.

1 Purpose and ScopeThe detailed data use and data quality objectives are described in the site-specific United StatesEnvironmental Protection Agency (U.S. EPA) Emergency Response Section (ERS) andSuperfund Technical Assessment and Response Team (START) Sampling and Analysis Plan(SAP) for Eureka Smelter Sites Removal Assessment, Eureka, Eureka County, Nevada. Thepurpose and scope of this DMP is to provide guidance and instruction for implementing the site-specific SAP in the context of collecting, organizing, verifying, and delivering the data elementsrequired by the site-specific SAP, using the site-specific database management program. Thedatabase management program specific to this DMP is Scribe.

1.1 ScenarioThere is concern as to whether residents of the town of Eureka may be currently exposed to, orhave the potential for exposure to, lead and arsenic contamination in soils from milling andsmelting waste generated by former milling and smelting operations in Eureka. Analytical datagenerated by the U.S. Department of Interior, U.S. Geological Survey (U.S. DOI 1978), U.S.EPA and NDEP sampling from locations throughout Eureka and the vicinity have provideddocumentation that arsenic and lead concentrations in soil exceed U.S. EPA’s respective r-RSLs.Based on this information, the contamination is likely to be present at most public, residentialand commercial properties in and around the town of Eureka. Contamination is also likely toexist in creek sediments downstream from the town and in shallow surface soil downwind of thetown. Arsenic and lead are the primary contaminates of concern for this removal assessment.

The data generated for the project will derived from seven identified areas of investigation orareas of concern (AOCs) within the study area:AOC 1 Public urban parks, playfields and public school properties,AOC 2 Developed urban properties,AOC 3 Undeveloped urban properties,AOC 4 Unpaved urban roads,AOC 5 Areas downwind of the town of Eureka,AOC 6 The creek bedAOC 7 Background areas.

1. Introduction

1-2

The data generated by implementing the SAP and this DMP will be used to: Determine average concentrations of lead and arsenic in the soil at locations within the

town of Eureka. Determine average concentrations of lead and arsenic in the roadway material in unpaved

roads within the town of Eureka. Determine whether a removal action at any of the properties is warranted. Document concentrations of lead and arsenic in the shallow soil downwind of Eureka Document concentrations of lead and arsenic in the creek sediments. Document concentrations of lead and arsenic in the creek surface water. Document background concentrations of lead and arsenic in the soil around Eureka. Document spatial distribution of lead and arsenic in large undeveloped properties within

and around Eureka. Answer site-specific study questions indicated in the DQO and SAP.

1.2 Special Considerations and Privacy Concerns

1.3 Summary of Revisions and Updates

The following table lists the document revision history for this DMP.

Table 1-1 – Document Revision History

Revision Date Section Description of Changes

Initial Draft (V0.1) August 28, 2012

2. Site Background

1-1

2 Overall Work Flow

2.1 Data Flow and Data Flow Diagram

The site-specific DMP incorporates data management tools, data handling procedures, andsupporting documentation to maintain data quality objectives. Figure 2-1 describes the processof data management from data collection through data storage, data verification, data analysis,and field reporting.

2.2 Roles and ResponsibilitiesThe following is a list of project personnel and their responsibilities:

U.S. EPA Task Monitor: The U.S. EPA Task Monitor is FOSC Tom Dunkelman. Mr.Dunkelman is the primary decision-maker and will direct the project, specify tasks, and ensurethat the project is proceeding on schedule and is within budget. Additional duties include gainingaccess to the site, and coordination of communication with the START project manager, the U.S.EPA quality assurance (QA) office, the State of Nevada, and Eureka, Nevada, communityrepresentatives.

NDEP: Mr. Greg Lovato, Mr. Jeff Collins and Mr. Jack Yates of the NDEP are assisting the U.S.EPA FOSC in obtaining access, providing public relations and other with activities to support theRemoval Assessment.

START Project Manager: The START Project Manager (PM) is Mr. Howard Edwards. TheSTART Project Manager is responsible for developing and implementing the SAP, coordinationof project tasks and field sampling, project management, and completion of all preliminary andfinal reporting.

Principal Data Users: Data generated during the implementation of this SAP will be utilized bythe U.S. EPA Task Monitor and NDEP to make decisions regarding removal activities at the site,if necessary.

Analytical Laboratory Support: The U.S. EPA Region 9 Laboratory in Richmond, California,will be utilized for analysis of contaminants of potential concern (COPCs). START will beresponsible for data validation activities.

2. Site Background

1-2

Figure 2-1 Data Management Work Processes

US EPA TM

STARTPM

STARTDM

FieldTeam

RawData

WorkingData

STARTPM

STARTDM

ValidatedWorking

FileArchived

Field Logs

STARTPMUS EPA TM

RequestedData Report

Project Tasking,Data Collection Parameters

Determine Field Data Collection Requirements per US EPA TM

Project Tasking,Data Collection Parameters

Provide Field Data CollectionRequirements to Field Team

PrepareDMP

Collect Raw Field Data

Data Re-FormattedFor Submittal to DM

Data Entered into Project Data Management Database (Scribe)

Data Collection

Data Storage

Data Validation

Data Verification

Data Sorting and Evaluation

Submit DataReport to TM

US EPA TMRequests DataReport

Data Analysis

FieldReporting

STARTDM

Verification of Requested Report Elements

ReportRequest

2. Site Background

1

3 Data Collection

3.1 Field Data Collection Methodology

The following sections summarize the procedures and tools that are used to capture thefield data for this removal assessment.

3.1.1 Equipment and InstrumentsThe equipment and instrument with settings needed to accomplish the data collectionobjectives of this DMP are presented in Table 3-1. Equipment will be operated,calibrated, and maintained in accordance with the manufacturer’s instruction.

3.1.2 Site-Specific Data Collection Procedures – Initial EntryThe general and site-specific field procedures that will be followed to meet the objectivesof this DMP during the data collection events are presented in Table 3-2.

3.2 Data DeliverablesThe key data products generated in the field as required by this DMP are presented inTable 3-3.

3.3 Data Collection SOPs and ChecklistsTable 3-4 describes the specific step-by-step procedures and or protocols that are used tocollect, process, load, and link all data to Scribe. Scribe import procedures will befollowed in accordance with the U.S. EPA Environmental Response Team (ERT) ScribeManual Part 3, Scribe Management and Advanced Features. Scribe procedures will alsobe based on the applicable steps in the Draft Basic Scribe User Instructions (AttachmentA).

2. Site Background

2

Table 3-1 – Site Specific Data Management Plan Equipment RequirementsData Equipment Required Output Parameters of Data

CollectionSpecial Considerations

Elemental analysis XRF Analyzer/Innov-X

Data cable to aPersonal Computer

Instrument parameters,analyte with numericmeasurement withconcentration in mg/kg

Instrument, sample preprequired. MicrosoftActiveSync required onPersonal Computer

Property andSampling

PC Tablets/ Internet Upload orpersonal computer viaa data cable orwireless

Date, time, observationsand measurements

Scribe may need to bemodified prior to use.Field notes and drawingsin log book or fieldsheets also required

Spatial location GPS/ Trimble Data cable to aPersonal Computer

Geographic coordinatesLatitude and longitude,decimal degrees (i.e.,34.1534, -120.2580),WGS 1984 coordinatesystem

Ensure GPS instrument isset in required coordinatesystem (datum) prior todata collection; ensuredata output is set inrequired degree units(i.e., decimal degrees vsdegree-minute-seconds).

Image Digital Camera Data cable to aPersonal Computer ordata card

Digital image Date andtime photo taken, imagesize less than 1 MB,

Set camera calendar andclock to local time priorto data collection; setimage size prior to datacollection.

Motion image Digital Video Camera Data cable to aPersonal Computer ordata card

Date, start time, andstop time video taken

Set video calendar andclock to local time priorto data collection

All FieldGenerated Data

Personal Computer Internet upload,print, archive mediaand print

Internet and ports Scibe, Microsoft AccessMicrosoft ActiveSyncrequired on PC. Cardreader, WiFi and datainput port needed

Notes:XRF= X-ray fluorescence

mg/kg = milligram per kilogram

2. Site Background

3

Table 3-2 – Data Collection Procedures Data CollectionData CollectionObjective

Primary DataCollectionTool

General DataCollection Procedure

Mandatory Minimum DataCollection Information

Data Logging Requirements

Sample identification numberis entered manually intoXRF’s PDA.

XRF Instrument is manuallyinitiated.

Analysis results are generatedand appear on screen and arerecorded.

Data on sample bag will indicateA unique sample identification number,sampling time, and a sampling date. (as aminimum)

Sample must also have a log entry the hasthe Sample identification number,Sampling time,Sampling date, and a reference forsampling location.

Manual Log Sheet or Log book

1) Record XRF serial number,settings and XRF QA data (MDLstudy, correlation study, etc).

2) As data is generated, recordelements concentration data withsample identification number.

3) As data is generated, record QCsample results and calculation.

Analysis results areelectronically archived onXRF PDA.

Each prepared sample in XRF cup musthave a unique sample identificationnumber.

The unique sample identification number isenter into XRF PDA and onto on log sheetor log book.

Instrument Log

1) Daily download CVS file toPC.

2) Daily convert XRF CVS file toxls file.

Analysis ofprepared soilsamples fromspecific decision

units or location todetermine thearsenic and leadconcentrations insoil.

Data is generated inthe field by XRFAnalyzer/ Innov-X

XRF Detector is connected to aPersonal Digital Assistant (PDA)that comes with Innov-X. PDA hasa program that converts detectoroutput to element and concentration,standard deviation for theconcentration.

The daily XRF data isdownloaded to PC.

Results for arsenic and lead on screen aremanually entered on log sheet or log book.

Results for all analytes, instrument setting,and sample name are archived in PDAmemory as a cvs file by date

The cvs file is downloaded from PDA to

PC with Microsoft ActiveSync

Field Reporting

1) Daily printed report in tableformat with sample identificationnumber arsenic and leadconcentration.

Note: * U.S. EPA access agreement must be in place prior to entering property or collecting air samples or monitoring data

2. Site Background

4


Primary DataCollection Tool




Property InformationProperty information isentered manually into tabletPC.

GPS location data andphotographic data can also becollected with a table PC withcamera and GPS capabilities.However, this plan does notaddress the use of the PCtablet for that purpose..

Property Information pre-field, post-field, or in the field

1) Record the Assessor Property Number(APN).2) Record property type (residence, school,business, public building, etc.)3) Record property address, includingstreet, city, state, zip code4) Record whether access agreement exists5) Record property geographic coordinates(lat/long) for property center (GIS primecoordinate).6) Record property owner’s name andaddress, phone number.7) Record principal property occupant’sname and address, phone number.8) Record number of persons living in thehome.9) Record number of persons under the ageof six.10) Record number the number of pregnantwoman in the residence.11) Record how long occupant has beenliving in the residence.12) Record square footage of property(either measure this off the satellite photoor GIS data).


1) Record the Assessor PropertyNumber (APN).

2) Record property address

3) Diagram the property

4) Record unique sampleidentification number, samplingtime, and a sampling date. (as aminimum)

5) Record sampling depth

6) Indicated sampling location onlog diagram.

Documentation ofpropertyinformation andassociated samplinglocation information

Information isdocumented in thefield.

Information is recorded on a tabletPC with Scribe data collectionprogram.

Decision unit Information

Decision unit information isentered manually into tabletPC.

.

Field Decision Unit Information1) Record whether the property hasmultiple decision units or is a singledecision unit2) Describe decision unit if a property hasmultiply decision units.

a) Record square footage of decision unit.b) Provide and record landscaping

information.c) Record photo and photo log reference

number information

Instrument Log

1) Daily download CVS file to PC.2) Daily convert XRF CVS file to

xls file.

2. Site Background

5






Property InformationProperty information isentered manually into tabletPC.

GPS location data andphotographic data can also becollected with a table PC withcamera and GPS capabilities.However, this plan does notaddress the use of the PCtablet for that purpose..

.

Field Property Information1) Record property address or locatedproperty addresses record.2) Confirm that an access agreement exists.3) Confirm property geographic coordinates(lat/long).4) Record or confirm the number of personsliving in the home.5) Record or confirm the number of personsunder the age of six.6) Record or confirm the number ofpregnant woman in the residence.7) Record how long occupant has beenliving in the residence.8) Record or confirm square footage ofproperty.9) Provide and record landscapinginformation.10) Record photo and photo log referencenumber information.

Documentation ofpropertyinformation andassociated samplinglocation information

Information isdocumented in thefield.

Information is recorded on a tabletPC with Scribe data collectionprogram.

Sampling LocationInformation

Sampling locationinformation for each collectedsample is entered manuallyinto tablet PC.

.

Sampling Location Information1) Record GPS location of decision area(s)centerpoint2) Record GPS location of each samplinglocation.3) Record unique sample identificationnumber, sampling time, and a samplingdate. (as a minimum)4) Record sampling depth

Field Reporting

None

2. Site Background

6






Sample identificationnumber, APN or decision unitperimeter name enteredmanually into Trimble GPSunit.

Trimble GPS is manuallyinitiated.

Geographic coordinates aregenerated are recorded.Discrete location may alsoappear on the screen.

File folder is created on the Trimble GPSunit using the date.

File based upon sample identificationnumber, APN or decision unit perimetername is created prior to GPS satellite datacapture.


None

Geographic coordinates areelectronically archived onTrimble GPS unit..

GPS data is archived in folders on TrimbleGPS unit as shape or point files

Instrument Log

3) Daily download GISfiles to PC.

Determine andDocumentgeographiccoordinates(lat/long).For discretesampling locationand boundaries.

Trimble GPS unit will capturelocation and boundaries usingsatellite data.

The daily GPS data isdownloaded to PC.

.The point and shape files are downloadedfrom Trimble to PC using a Trimbleprogram installed on the PC.

Field Reporting

None

2. Site Background

7






Camera is manuallyinitiated.

Image data are generated arerecorded. Time and dateddata is automaticallygenerated. Still photos willalso appear on the screen.

File based upon sequential number isautomatically created as part of the imagecapture.


Photograph and video identificationnumbers can be recorded in a logbook or log sheet.

Photo or video file areelectronically archived ondata card.

Photo files are archived on data card asTIF, JPG, PNG, GIF, Video files: .asf, .avi,.wmv • Movie files: MPEG1, .mpeg, .mpg,.m1v, .mp2

Instrument Log

Daily download files to PC can bemanaged with links on scribe of aspread sheet table.

Photographic andvideodocumentationof samplinglocations, decisionunits, properties,and samplingactivities.

Digital camera and digital videocamera.

The daily photo or video datais transferred to a PC The daily photo or video data is transferred

to a PC via a data card reader.

Field Reporting

None

2. Site Background

8






All property, fieldanalytical, GPS andimagery will be transferredto a laptop PC withprinter.

All field activities will be documented withScribe and an Excel project log file.


Site log book following E & E SOPwill be maintained.

Scribe files will be dailyuploaded to Scribe.Net.

All files will be archive onan USB or external harddrive.

Instrument Log

Daily download files to PC can bemanaged with links on scribe of aspread sheet table.

All field andprojected datalinked in a databasefile.

Information is archived and storedon a laptop PC with Microsoft Exceland Scribe data collection program.

Field Reporting

Field analytical and work summaryreports will be printed anddelivered daily

2. Site Background

9

Table 3-3 – Key Data Products Generated in FieldData Product Data Descriptors FormatsPropertyInformation

Property APNProperty AddressProperty Type (school, residential, commercial)Owner NameOwner AddressOccupant Name (may require multiple fields)Occupant Age (adult or child)Property Access AgreementProperty Access DateOwner or Tenant OccupiedGeographic CoordinatesDecision unit informationLandscape information

Electronic - Table PC on Scribe databaseHard copy – logbook and log sheets

Sampling Sector andor LocationInformation

Sample identification numberSample collection Time and DateSample collection depth

Electronic - Table PC on Scribe databaseHard copy – logbook and log sheets

Arsenic and leadConcentration FieldInformation

Instrument IDInstrument SettingsArsenic and lead Concentration and UnitsComparison to Site-Specific Screening Level

Electronic - CVS file on XRF PDAHard copy – logbook and log sheets

GeographicCoordinateInformation

Longitude, Latitude, DatumSample location identification number

Electronic - .ssf file

PhotographicInformation

Photo Number, Date, Time, Direction,Description

Electronic - jpeg,Hard copy – logbook and log sheets

Video Information Video Subject Location, Date, Stop/Start Time Electronic – video file,Hard copy – logbook and log sheets

Project ManagementReport

Daily work reportPhotographic log

Electronic - .excel file linked with videoand jpeg files.Hard copy – logbook and daily worksummary sheet

Initial ScribeDatabase

Property record fileSample location filesSample data files

Electronic – Scribe/ Acess database fileHard copy – Field data results tables print-outs

Laboratory Report Total arsenic and lead Concentration and units.Bio-Accessible arsenic and lead Concentrationand units.Total California List metal concentration andunits

Electronic – pdf summary data, PDFpackage data, scribe ready EDDHard copy – Summary results andLaboratory raw-data validation package.

Validated Datareport

Tier-2 validated total arsenic and leadConcentration and units.Tier-2 validated Bio-Accessible arsenic and leadConcentration and units.Tier-2 validated Total California List metalconcentration and units

Electronic – pdf validation report andqualified dataHard copy – validation report andqualified data

Final ScribeDatabase

Property record fileSample location filesValidated Sample data files

Electronic – Scribe/ Acess database fileand Scribe.NetHard copy – Final Report

2. Site Background

10

Table 3-4 – STEP-BY-STEP PROCEDURES AND OR PROTOCOLS

THAT ARE USED TO COLLECT, PROCESS, AND LOAD

DATA TO SCRIBE

Data Table General Description ofData Collected

General Data Management Procedures

Create Scribe database onlaptop PC

Collect PropertyInformation from NDEPGIS and county GIS files

1) Assign APN2) Record property address, including street,

city, state, zip code.

Collect Scribe or AccessInformation*

1) Record whether access agreement exists2) Record property owner information if

available (school district or owner ofresidence)

3) Record whether owner or tenant occupied4) Record occupants of property5) Record date property was accessed for

assessment purposes.6) Input the hyperlink to the copy of the access

agreement stored in epaosc.netGenerate START GIS fileInformation

Link GIS file to Scribe file

Initial Property InformationProperty address, owner, andcontact information will be inputinto the Property Info table. Eachrecord within the Property Infotable will include parcel data andaccess information, whereavailable. Hyperlinks to the signedaccess agreements, stored inepaosc.net, will be included in theProperty Info table.

Transfer Scribe databaseinformation to tablet PCs

Property Specific OccupantOccupant information includingany responses to the U.S. EPAquestionnaire will be input into theProperty Occupant table and will berelationally linked to the PropertyInfo table.

Using Scribe of tablet PC.

Collect property specificinformation from propertyresident or occupants.Information on landscapeand decision units

1) Record responses to questionnaire on excelspreadsheet

2) Import completed questionnaire xls files tothe PropertyOccupant table using theOccupantID in Scribe.

Sampling LocationSampling/monitoring location datawill be input into the Location tableand will include geospatialcoordinates, where applicable, andlocation descriptions (building,room, etc.). Location information isrelationally linked to the PropertyInfo table.

Using Scribe of tablet PC.Collect Sampling LocationInformation

1) Assign a unique LocationID in the formatPropertyID-###, where ### is a three digitcode beginning at 001 for each samplingsector for a property. If the property isassessed as a whole (e.g. residential), thenonly one LocationID (001) is assigned. If theproperty is sampled in a grid then the ### is athree digit code beginning at 001 for eachsampling grid node property.

2) Include depth interval, date and time.3) Include a description of the location in the

location description field

2. Site Background

11

Table 3-4 – STEP-BY-STEP PROCEDURES AND OR PROTOCOLS

THAT ARE USED TO COLLECT, PROCESS, AND LOAD

DATA TO SCRIBE

Data Table General Description ofData Collected

General Data Management Procedures

GPS Information Collect GPS data 1) Import dbf exported from GPS unit thatincludes longitude and latitude coordinates inthe NAD83 system, and unique LocationIDfor the sampling/monitoring location. Sampledata shall be collected in decimal degrees tofour significant digits.

2) GIS personnel will identify locationalinformation where a GPS signal is notavailable (e.g. within buildings).

3) Import the GPS to Scribe and input alldescriptive information.

Photo and Video Information Collect PhotographicInformation

1) Collect photos of property2) Record photo log for photos: photo number,

date, time, location, direction, description inspreadsheet.

3) Import the photo to Scribe and input alldescriptive information.

Sample InformationInformation for samples collectedduring the data will be input in theapplicable matrix specific tablewithin Scribe. At a minimum,sample id, associated locationid ordescription, sample collection date,and sample time are required fields.Sample information is relationallylinked to the Location table.

Chain of Custody/ SampleTracking Information forCollected Samples

1) Download Table Scribe data to laptop PC2) Export xls files containing sampling

information3) Generate and print a sample inventory table

from xls file data.

Field Analytical ResultsField XRF results data will beimported into Scribe.

Collect arsenic and leadConcentration Data

1) Import cvs or xls output file of XRF resultsinto the Monitoring table.

2) Ensure that the location descriptioninformation such as building number, roomnumber, property type assessed (residential,personnel, item, vehicle, etc.) is in the sub-location and source fields.

COC InformationSelect samples for confirmation andadditional analysis in Scribe

Generate a Chain ofCustody form and recordfor selected samples

Generate and print a COC form directly fromScribe.

Laboratory Analytical ResultsAnalytical results will be uploadedto the Lab Results table. Theanalytical results are relationallylinked to the Samples table.

Import Laboratory EDDs 1) Import Laboratory EDDs to the LabResultstable in Scribe.

Laboratory Analytical ResultsAnalytical results in Scribe will bequalified as required.

Hard Copy validationreport.

1) Add qualifier and adjust concentration asindicated in validation report.

4. Sampling Rationale and Design

3-1

4 Data management

4.1 Data ProcessingThe specific data elements used for collecting, importing, and managing the field data inScribe is provided in Attachment B. The data tables used for importing data should be in.csv format. The data field formats are specified within the tables providing data fielddescriptions. Individual data fields should be formatted in accordance with the data fielddescriptions (i.e., text, numeric, Boolean, etc.). Conditional requirements (i.e.,TenantOccupied = IIf([OwnerOccupied] = “Y”, “N”, “Y”)) have not been set for the dataelements used in this scenario, but may be developed during implementation of the DMPif the START DM determines they will improve efficiency.

4.2 Scribe Import MappingThis section describes the documentation of how data fields in the processed datadeliverables are mapped to data fields in Scribe.

Property Information Import MapOccupant Info Scribe Fields(Destination) Import Fields (Source)

PropertyInfoDBID PropertyInfoDBID

Site_No Site_No

PropertyID PropertyID

PropertyType PropertyType

PropertyAccessAgreement PropertyAccessAgreement

OwnerOccupied OwnerOccupied

TennantOccupied TennantOccupied

PropertyZone PropertyZone

PropertyTaxID PropertyTaxID

PropertyBlockID PropertyBlockID

PropertyParcelID PropertyParcelID

PropertyFirstName PropertyFirstName

PropertyLastName PropertyLastName

PropertyPhone PropertyPhone

PropertyAddress PropertyAddress

PropertyAddress2 PropertyAddress2

PropertyCity PropertyCity

PropertyState PropertyState

PropertyZip PropertyZip

OwnerLastName OwnerLastName

OwnerFirstName OwnerFirstName

OwnerAddress OwnerAddress

2. Site Background

3-2

Occupant Info Scribe Fields(Destination) Import Fields (Source)

OwnerAddress2 OwnerAddress2

OwnerCity OwnerCity

OwnerState OwnerState

OwnerZip OwnerZip

OwnerPhone OwnerPhone

OwnerAlternateNumber OwnerAlternateNumber

PropertyAccessRequestedDate PropertyAccessRequestedDate

PropertyAccessApprovedDate PropertyAccessApprovedDate

PropertyDate1 PropertyDate1






PropertyX PropertyX

PropertyY PropertyY

PropertyComment PropertyComment

NumberOfOccupants NumberOfOccupants

NumberOfOccupants<6 NumberOfOccupants<6

OccupantPregnancy OccupantPregnancy

OccupancyLengthYears OccupancyLengthYears

PropertyArea PropertyArea

PhotoLogNum PhotoLogNum

LandscapingDesc LandscapingDesc

SampAreaDesc SampAreaDesc

Field Analytical Results Import Map

Laboratory EDDImport Fields (Source)

Lab Results TableScribe Fields(Destination)

Analysis Analysis

Analyte Analyte

Result_Units Result_Units

Samp_No Samp_No

Analytical_Method Analytical_Method

Date_Analyzed Date_Analyzed

Date_Collected Date_Collected

Date_Extracted Date_Extracted

Date_Received Date_Received

Detected Detected

Final_Volume Final_Volume

Final_Volume_Unit Final_Volume_Unit

Lab_Name Lab_NameLab_Result_Qualifier Lab_Result_Qualifier

Lab_Samp_No Lab_Samp_No

2. Site Background

3-3



MDL MDL

MDL_Units MDL_Units

QC_Type QC_Type

Result Result

Result_Qualifier Result_Qualifier

Analytical Lab Results Import Map



Analysis Analysis

Analyte Analyte

Result_Units Result_Units

Samp_No Samp_No

Analytical_Method Analytical_Method

Date_Analyzed Date_Analyzed

Date_Collected Date_Collected

Date_Extracted Date_Extracted

Date_Received Date_Received

Detected Detected

Final_Volume Final_Volume

Final_Volume_Unit Final_Volume_Unit

Lab_Name Lab_NameLab_Result_Qualifier Lab_Result_Qualifier

Lab_Samp_No Lab_Samp_No

MDL MDL

MDL_Units MDL_Units

QC_Type QC_Type

Result Result

Result_Qualifier Result_Qualifier

4.3 Data Element DictionaryThis section lists the data tables, data fields, formatting requirements, conditionalrequirements and valid values that are used to manage data in Scribe to support thisremoval assessment.

The following table lists the data dictionary fields that will be collected as well as asample of valid values. This is the minimum information required for collection in thefield. A field sketch or digitized map will be used to document monitoring locations.

2. Site Background

3-4

Table Field Entry Example/ Valid ValueProperty Info PropertyInfoDBID Database AutoNumber ###, where ### is a sequential number

beginning at 0001.

Site_No Manual Input 20912040002

PropertyID Manual Input ###, where ### is a truncated version ofthe PropertyParcelID

PropertyType Manual InputDescribes the property usage

ResidentialCommercialIndustrialGovernment

'PropertyAccessAgreement

Manual Input Yes/No

OwnerOccupied Manual Input Yes/No

TennantOccupied Manual Input Yes/No

ToWhomImportSurvey Question – If so, to whom?

Location LocationID Import or Manual InputUnique location identifier

PropertyID”-“###, where ### is anincremental number beginning at 001 forthe property.

LocationDescription Import or Manual Input General description of thesampling/monitoring location

Monitoring Source Import or Manual InputDescription of item/locationscreened

e.g. Bedroom #1, Bedroom #2, Kitchen,Room #501, etc.

4.4 Entity Relationship DiagramThe entity relationship diagram for the data tables and data fields used to manage thedata collected in this scenario in Scribe is presented in Attachment C.

4.5 Geospatial ManagementArcGIS will be used to manage all spatial data. The Location field will be used as thelink between data in Scribe and spatial data in GIS. Spatial data will be stored in ageodatabase, and data linkages will occur by exporting from Scribe and joining theexported table via a join from within ArcGIS. Sample and/or monitoring locations willbe described in the Site Specific Sampling Plan and these location identifiers will be thesame in both GIS and in Scribe.

Electronic Geospatial and spatial data from various sources will be collated to prepare abase data set for Eureka Smelter Sites removal assessment. The original source data willbe saved in its original format as an archive. A production geodatabase (ESRI file-basedgeodatabase format) will be established by E & E as the basis for project map productionand analysis. All data sets imported to the geodatabase will be stored in UTM Zone 11,NAD83 projection. Data layers in the production database will be documented with the

2. Site Background

3-5

EPA Metadata Editor. Standard ArcMap templates for project outputs will be stored onE & E network drive.

4.6 Critical Linkages between Tabular and Spatial DataLinkage between Scribe and GIS data will be established prior to field data collection.

4.7 Data Management SOPs and ChecklistsData management SOPs and checklists for removal assessments have not beendeveloped by either E & E or the U.S. EPA.

10. References)

5-1

5 Data Verification

5.1 Verification SOPs and ChecklistsSpecific step-by-step procedures and or protocols that are used to verify the quality andconsistency of the data that is collected and managed in Scribe.

Visual comparison will be conducted to capture obvious data entry errors into theScribe tables.

Download of the data dictionaries will be completed with a sample representativepresent to verify that the data is appropriate and accurate. Data from the datadictionaries is processed into Scribe and the geodatabase where another brief QCcheck will verify that the appropriate data is available.

Data that is not electronic is digitized into Arcmap using the field maps andmeasurements and a spatially referenced representation of the site.

Location Latitude and Longitude are calculated for each of the digitized locationsin NAD83. Other attributes are given to the location include Datum andGeoMethod (NAD83 GCS and Digitized respectively)

These locations are stored in a Geo-database stored separately from Scribe butliked on the Property IDs and Locations table.

The calculated location values associated with the digitized featureclass are thenused to update the location table in Scribe.

Monitoring results and locations are then passed through a series of QA checks toensure the completeness of the data:

5.2 SQL Verification QueriesSQL statements that can be run against the table structure(s) and data element(s)identified in the DED and ERD and used to verify the quality and completeness of thedata that is collected and managed in Scribe. The following SQL Verifications Queriesused specifically for this site are documented in Attachment D:

6 Data Analysis and Reporting

1. Title

5-2

6.1 Data UsersThe principal data users are START, U.S. EPA, NDEP and Eureka County.

6.2 Reporting RequirementsRequirements for field reporting of the data elements will be determined by the U.S. EPATM in coordination with the START PM. The START PM will communicate thereporting requirements to the START DM, who will have responsibility for conductingthe queries necessary to filter and sort the data into the requested report. The specificreporting formats and views will also be determined based upon input from the U.S. EPATM, and may include combining data results with GIS-based map views.

6.3 Reporting SOPs and ChecklistsData reporting procedures can be developed for this scenario in consideration of the keydata elements of concern, such as sampling locations and sampling sub-locations whereconcentration measurements exceed site-specific action levels. These reportingprocedures can be aided by verification queries as referenced in Section 6.3.Additionally, if reporting requirements include the incorporation of geographiccoordinate information in map view with the required data element outputs, specificprotocols relevant to Scribe and GIS-based software should be utilized.

6.4 SQL Reporting QueriesData queries to aid the reporting process can be developed through basic or advancedsorting and filtering actions in Scribe, by using the Query Wizard Tool in MS Access, orby creating SQL statements to run against the collected data elements in a specific tablestructure, as identified in the DED and the ERD. The specific data fields selected forreporting queries should include key data elements such as property information, locationinformation, and concentration results in comparison to site-specific action levels.

A visual presentation of this type of query is presented in Attachment D.

6.5 GIS/Spatial Data Visualization RequirementsGIS visualization requirements have not been established.

A-1

A Draft Basic Scribe UserInstructions

B-1

B Data Element Dictionary

C-1

C Entity Relationship Diagram

D-1

D SQL Verifications Queries

data management plan eureka smelter sites

Documents