I.B.08 EXHIBIT 1 - DIDs 9.14.2020.pdf

HNC-001.03

DATA ITEM DESCRIPTION

Title: Project Planning Documents

Number: HNC-001.03 Approval Date: 20200224 AMSC Number: N/A Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-E Applicable Forms: Various Use/Relationship: Project Planning Documents will be used to describe the goals, methods, procedures, and personnel used for field activities.

Requirements:

1.0 Format. Project Planning Documents shall be printed on standard size (e.g., 8 ½ by 11 inch) white paper, with drawings folded, if necessary, to this size or to fit within pockets of this size. Pages shall be sequentially numbered. Drawings shall be of engineering quality in drafted form with sufficient detail to show interrelations of major features. When drawings are required, data may be combined to reduce the number of drawings. All attachments shall be identified and referenced in the text of the document. The document shall be legible and suitable for reproduction.

1.1 Chapters shall be numbered sequentially. Within each chapter, each page shall be numbered sequentially, starting with the specific chapter number. Each page of the document shall contain a footer with the date, the revision number, the Corps of Engineers’ contract and the Task Order number. Within each chapter, the paragraphs shall be numbered sequentially starting with the chapter number and using a decimal system, with each section and paragraph having a unique decimal designation. Within each chapter, any figures, tables, and charts shall be numbered sequentially starting with the chapter number.

All drawings, figures, tables, and charts shall be identified and referenced in the table of contents.

Documents shall be bound in a three-ring binder. Binders shall hold pages firmly while allowing easy removal, addition, or replacement of pages.

1.2 Appendices shall be lettered alphabetically. Within each appendix, each page shall be numbered sequentially starting with the appendix letter.

1.3 A title sheet will be provided on the front of the binder and also inside the binder which includes the name of the project (site), contractor's name and address, the Corps of Engineers’ contract number, Task Order number, and project number, the date of the document, and the title of the document. The contractor’s name shall not be present on the binder of the document. The title sheet shall identify the contracting agency and shall name the Geographical Corps District where the project is located. The title sheet on the inside of the binder shall identify the company and the Corporate Quality Management representative shall sign the title sheet. The version of the document (i.e., draft, final, etc.) shall be clearly identified on the title sheet.

1.4 When revisions to the document are required, a revision date, revision number, Corps of Engineers’ contract/Task Order and amendment/modification number (if applicable) shall be included in the footer.

A clean copy and a tracked changes copy of the revised document shall be submitted along with the response to comments on Form 7. Revisions made after the document has been accepted as final shall include a dated summary page listing all revised pages. This summary page shall be identified as such and placed directly behind the title page.

1.5 If applicable. Any project changes that occur after field work has begun, will require that a Field Change Request be submitted and accepted prior to changing site plans or procedures.

HNC-001.03

1.6 No Government publication or other Government printed matter, prepared or produced with either appropriated or non-appropriated funds or identified with an activity of the Government, shall contain any advertisement inserted by or for any private individual, firm, or corporation; or contain material which implies in any manner that the Government endorses or favors any specific commercial product, commodity, or service. Neither Draft nor Final documents shall contain Contractor information. The Contractor’s name may be included only in an inconspicuous location as the preparer of the document on the title page. Additionally, no logo or other advertising information shall be displayed in the document.

The Contractors shall not put watermarks on documents. Hyperlinks are prohibited from use.

2.0 Project Planning Documents shall be organized by chapters and or sub plans unless specifically excluded by the Task Order. When an issued Task Order does not require a specific chapter, sub plan or appendix, the chapter, sub plan or appendix heading shall be retained with a declaration that the chapter, sub plan or appendix is not required by the task order. EM 200-1-15 provides description of Uniform Federal Policy – Quality Assurance Project Plan contents. Uniform Federal Policy – Quality Assurance Project Plan content shall be organized as described in EM 200-1-15. Standard Operating Procedures shall be organized as described in EM 200-1-15. Appendices shall be organized as described in EM 200- 1-15 with the following exception, Standard Operating Procedures shall be the first Appendix.

3.0 End of DID HNC-001.03.

HNC-002.02

DATA ITEM DESCRIPTION

Title: Third Party Validation Seeding Work Plan

Number: HNC-002.02 Approval Date: 20200810 AMSC Number: Limitation:

DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-G Applicable Forms:

Use/Relationship: The Third Party Validation Seeding Work Plan will be used to provide details of the approach, methods, personnel and operational procedures to be employed to perform Third Party Blind Seeding for support of Munitions Response or other munitions related project. This Data Item Description contains instructions for preparing work plan chapters.

References:

• Department of Defense Quality System Requirements for Advanced Geophysical Classification

(DoD QSR), latest version

• Engineer Manual (EM) 200-1-15, latest version

• Geophysical System Verification: A Physics-Based Alternative to Geophysical Prove Outs for

Munitions Response, Environmental Security Technology Certification Program (ESTCP), July 2009, Addendum September 24, 2015

• EM 385-1-1, latest version

• EM 385-1-97 including Change 1 and errata, latest version

• DESR 6055.09 Volume 7, latest version

Requirements:

Format. This plan shall follow the formatting of DID HNC-001.03

1.0 Work plans shall be organized by chapters unless specifically excluded by the Task Order. When an issued Task Order does not require a specific chapter, the chapter heading shall be retained with a declaration that the sub plan is not required by the Task Order. Chapters shall be organized as follows:

1.1 Chapter 1. Introduction. At a minimum, the following information shall be included in this chapter or by reference to existing project documents (e.g. Remedial Action Uniform Federal Policy – Quality Assurance Project Plan (UFP-QAPP)):

a. Site Location

b. Expected anomaly density

c. Terrain/Vegetation affecting seeding

d. Potential geology affecting seeding

1.2 Chapter 2. Personnel. This chapter shall document all personnel who will be involved in each task, and shall state their required compliance with Appendix C, Blind Seed Firewall Plan.

1.3 Chapter 3. Seeding Approach. At a minimum, the following information shall be included in this chapter:

a. Seed Items. Shall include the rationale used in determining the quantity, depth, and type of seeds needed to evaluate the quality of a given production unit. Seeds shall consist of representative certified inert seed rounds and/or Industry Standard Objects (ISO) of appropriate dimensions. Each seed item shall be labeled as a validation or QA seed with a unique seed ID.

b. Seeding Methods. Shall include details for burial, including sufficient level of detail to ensure the APP/SSHP provides adequate safety controls for the work to be performed. Shall address anomaly avoidance, how holes will be dug and backfilled to appear unrecognizable, and how seeds will be located to provide required positioning accuracy.

c. Documentation to be recorded (DGM/AGC validation seeding) Shall include the following:

• The x, y, and z coordinates for the center of the seed, with coordinates reported in the approved project coordinate system, and with accuracy of +-10cm.

• The depth of the seed in centimeters, measured as the vertical distance from the bottom of a straight edge placed across the opening of the hole down to the center of the seed.

• Orientation of the seed relative to horizontal (0 degrees)

• Azimuth of the seed relative to North (0 degrees).

• A photograph of the seed, showing its seed ID number. A ruler or similar scale should also be included in the photograph.

d. Documentation to be recorded (Analog/Surface QA seeding) Shall include the following:

• The x, y, and z coordinates for the center of the seed, with coordinates reported in the approved project coordinate system, and with sub-meter accuracy.

• The depth of the seed in centimeters, measured as the vertical distance from the bottom of a straight edge placed across the opening of the hole down to the center of the seed (for subsurface analog seeds).

1.4 Chapter 4. Instrument Verification Strip (IVS) and/or Instrument Test Strip (ITS) Plan. This chapter shall describe the IVS (DGM/AGC) and/or ITS (Analog) to be installed or made available for equipment testing, per the Task Order.

1.5 Chapter 5. Advanced Geophysical Classification (AGC) Data Collection and Analysis. This chapter shall provide a detailed discussion of the AGC equipment, cued data collection and analysis methods to be utilized in order to verify the seeds are detectable and classifiable, and shall include details for selecting and validating background locations. The chapter shall include all necessary quality control and shall reference supporting Standard Operating Procedures (SOPs) in Appendix D and Measurement Quality Objectives (MQOs) in Appendix E. The chapter shall include sufficient level of detail to ensure the APP/SSHP provides adequate safety controls for the work to be performed.

1.6 Chapter 6. Schedule and Deliverables. This chapter shall provide a detailed schedule and briefly describe all deliverables required per the Task Order. This may include, but is not limited to, the following:

a. IVS Memorandum

b. Seed Tracking Log (in Access DB and Geosoft GDB formats)

c. Raw and processed geophysical data (compatible with Oasis Montaj and IAW DID HNC-003.03)

d. Data Usability Assessment

e. Validation Seeding Report

1.7 Chapter 7. References.

1.8 Appendices. The work plan shall contain the following as appendices in the order shown:

• Appendix A. Task Order Scope of Work

• Appendix B. Planned Seed Details (Table with planned item type, depth, orientation, draft location;

and Figure with planned seed locations overlaid on RI density estimates/kriged contours, if available)

• Appendix C. Blind Seed Firewall Plan. Shall include a list of personnel inside the firewall, including signatures, for all personnel with knowledge of the seed details, documenting their adherence to the firewall plan.

• Appendix D. SOPs (all contractor SOPs governing work covered under this plan, such as: Blind Seeding, IVS installation, Cued AGC Data collection, Cued Data Analysis, etc.)

• Appendix E. MR-QAPP Worksheet 22 (MQOs)

• Appendix F. Contractor Forms for collecting and recording the data

• Appendix G. Accident Prevention Plan/Site Specific Health Plan (APP/SSHP)

• Appendix H. Mobilization/Demobilization Plan

2.0 End of DID HNC-002.02

HNC-003.03

Title: Geophysics

Number: HNC-003.03 Approval Date: 20190816 AMSC Number: Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-G

Applicable Forms: Attachment A – Field Data Sheet, Attachment B –Access Database Required Tables, Attachment C - Geophysical Submittals & Due Dates

Use/Relationship: This Data Item Description contains instructions for preparing UFP-QAPP Worksheets and data requirements when addressing geophysical investigations for Munitions Response or other munitions related projects. This DID specifies naming and formatting conventions for data deliverables associated with geophysical activities. This DID shall be used in association with EM 200-1- 15 Chapters 6, 8, 9, 11 & 13. Additional references include the Ordnance and Explosives Digital Geophysical Mapping Guidance - Operational Procedures and Quality Control Manual (CEHNC, 2003).

Requirements:

1.0 Geophysical Investigation Plan. The Contractor shall incorporate all aspects of the Geophysical Investigation Plan (GIP) into the UFP-QAPP for MEC and related SOPs. The plan shall provide details of the approach, methods, and operational procedures to be employed to perform geophysical investigations at Munitions Response or other munitions related projects. The GIP shall describe how the geophysical investigation and related activities will meet the project’s Data Quality Objectives (DQOs). The DQOs shall include statements identifying the specific MEC target objectives, their anticipated or expected burial depths, and the detection and removal objectives for the project. Geophysical data needs and operating procedure requirements shall be identified and specified to support all project DQOs. Digital Geophysical Mapping (DGM) shall preferentially be incorporated into the GIP where appropriate.

Exceptions to using DGM shall have PDT concurrence. Additionally, the following topics shall be addressed in the GIP:

a. Specific Area(s) to be investigated, including a Survey Mission Plan Map.

b. Account for and address all known project specific constraints, adverse conditions or features potentially affecting geophysical investigations (i.e. vegetation, geology, soil type, background geophysical noise, man-made features, site accessibility, etc.)

c. Geophysical Survey type(s), equipment and field procedures (required for both analog and digital detectors)

d. Required field documentation (see Attachment A for a sample Field Data Sheet template)

e. Data processing, corrections and advanced analysis (see EM 200-1-15 section 6.6)

f. Anomaly identification and ranking/prioritization criteria, and dig selection criteria (see EM 200-

1-15 section 6.6.2)

g. Anomaly reacquisition and resolution procedures (see EM 200-1-15 section 6.6.9)

h. Descriptions of final data formats and final map formats.

2.0 Instrument Verification Strip (IVS) Plan & Letter Report. The Contractor shall prepare an IVS Plan to address those elements described in EM 200-1-15 section 6.7 and the Final Report Geophysical System Verification (GSV): A Physics-Based Alternative to Geophysical Prove-Outs for Munitions Response (Final GSV Report, ESTCP, 2009). A Geophysical Prove-Out should be considered when a DGM sensor is not well characterized and sensor response curves can’t be generated. If determined necessary by the PDT, the GPO Plan detailing the size and scope necessary to meet the project needs shall be submitted as described in EM 200-1-15 section 6.7.3. After the IVS or GPO field effort, the Contractor shall prepare an IVS or GPO Letter Report to contain all information required by the PDT to support their selection decisions as described in EM 200-1-15 section 13.6.

A letter report shall be delivered along with the following files:

a. The IVS or GPO Letter Report (Microsoft Word format);

b. All raw and processed geophysical data;

c. Geophysical maps in their native format (Surfer, Geosoft Oasis Montaj, Intergraph, or ESRI

ArcView format) and as raster bit-map images such as BMP, JPEG, TIFF or GIF;

d. Seed item location table (Microsoft Excel or Access format);

e. Microsoft Access Tables in accordance with Attachment B.

f. Table (Microsoft Access format) of all control points, survey points and benchmarks established or used during the Location Surveying task.

2.1 The IVS or GPO Letter Report shall be included in future work plans and reports associated with the survey area. If the contractor proceeds with production geophysical mapping prior to the Government’s acceptance of their IVS or GPO letter report, they will proceed at their own risk. If the Government rejects any portion of the Contractor’s IVS or GPO letter report pertaining to geophysical mapping procedures, quality control or detection capabilities, all data collected by the Contractor at their own risk will be rejected and the Contractor shall re-collect the data at zero cost to the Government.

3.0 Quality Control (QC) Plan. The geophysics sections (digital and analog) of the QC plan shall be developed in accordance with EM 200-1-15 Chapter 11 (see Tables 11-1 to 11-6) and incorporated into the UFP-QAPP for MEC and related SOPs. The quality control plan shall identify meaningful and reasonable QC checking and testing procedures to define and document the quality achieved by the work processes performed and in the data generated. The QC plan shall include procedures for performing root-cause analyses when failures occur. Results of QC tests, numerical and pass/fail, shall be reported in an Access database using the naming and formatting conventions found in the database template provided by CEHNC and as described in Attachment B. Contact the CEHNC Geosciences Branch for the current database template. This database provides the format for reporting common QC tasks, it does not specify QC requirements. The tables are not all-inclusive and additions may be made to support project specific needs. Project specific QC metrics and QC requirements shall be defined and the QC Plan shall specify how they will be calculated and the frequency they will be calculated.

4.0 Data Format Requirements. The formats specified in this paragraph are REQUIRED to be exactly followed, although the Contractor may choose to submit the data in additional formats as well. All geophysical data shall be accompanied by metadata in the form of a read-me file or a database or spreadsheet table documenting the field activities associated with the data, the processing performed, and correlation of data file names to grid names used by other project personnel. Metadata shall be generated for each logical grouping of data (e.g., names and contents of all files generated to map a grid, or names and contents of all files generated from a towed platform during a mapping session.) Metadata shall fully describe all measurements recorded in each data file, and shall include all information necessary to successfully associate all geophysical system measurements to their correct geographical location. At the discretion of the PDT, the metadata can be limited to provide references to where this information is located. Appendix B identifies naming and reporting conventions that shall be used to deliver information associated with geophysical activities, such as function test results, QC assessment information and results, anomaly characteristics, dig lists, reacquisition information and intrusive investigation results.

Separate reporting formats and conventions are provided for analog and digital geophysical activities.

a. Raw Geophysical Field Data Format and Storage. Raw field data will be stored in a logical file directory (folder) structure to facilitate its management and dissemination to PDT members. Raw field data is defined as all digital data generated from the geophysical system, and includes geophysical, positioning, heading, tilt, and any other peripheral or instrument measurements collected or recorded during data acquisition. All raw field data shall have a time stamp associated with each measurement event. At the discretion of the PDT, raw field data may include geophysical system data that has been checked, corrected and processed into ASCII files, either individually by instrument or merged with positioning data. Metadata for raw geophysical data shall include instructions for generating ASCII formatted data from all raw data for use in computer processing systems.

b. Final Processed and Advanced Processed Data Format and Storage. Final and Advanced (as required) processed data shall be produced and presented in ASCII formatted files and native geophysical processing software formats (e.g. Geosoft GDB). Final processed data is defined as data that represents, to the best of the Contractor’s ability, the true potential field that exists at each actual location measured by the geophysical system. Final processed data shall have all corrections applied needed to correct for positioning offsets, instrument bias (including instrument latency), instrument drift, roll-pitch-yaw-angle offsets, and diurnal magnetic variations. Advanced processed data is defined as Final Processed data that has been subjected to additional advanced processing (e.g. filtering) techniques and was used in the anomaly selection process. Final processed data shall conform to field names in the DGM Access Database as applicable (e.g. CH1_final, CH2_final). All corrections and processing steps will be documented. Metadata for final processed and advanced processed data shall include UTM zone and coordinate units (the PDT or PWS may require additional coordinate units and projections be included), and descriptions and units of all “z” values, which are the data associated with each measurement event.

All measurement events shall have a time stamp. Unprocessed, interim-processed, final processed, and advanced processed (if used) “z” values shall be included in a single file. Each data file will be logically and sequentially named so that the file name can be easily correlated with the project-specific naming conventions used by the PDT. Naming conventions of files and data fields shall be included with metadata.

c. Anomaly Table, Dig Selection Table, Reacquisition Table & Intrusive Results Table formats. The Anomaly, Reacquisition & Intrusive Results Tables shall be submitted digitally in a Microsoft Access Database in accordance with Attachment B. The Anomaly Table shall include all anomalies above background or above a basic selection threshold, and shall include entries for all optional columns used in making dig decisions (e.g. Size, SNR, Fit_MagneticMoment, etc). All anomalies that have been selected for intrusive investigation will be marked as such in the Anomaly Table. The Reacquisition and Intrusive Results Tables shall include all information tabulated for each target during those phases. Post-dig verification responses shall be recorded in the Intrusive Results Table to meet the Anomaly Resolution requirement as appropriate. The tables shall be logical and descriptions of intrusive results shall be consistent.

d. Additional QC Table formats. Attachment B lists the tables that are required with each data submittal. The most recent Access Database format provided by CEHNC shall be followed with modifications as agreed to by the PDT.

e. Map Format. For submittals, the contractor shall provide maps in editable form if available (e.g.

Geosoft .map) and map images in a common image format (e.g. JPEG) for viewing without the software used to produce the maps. Additional geospatial files supporting the project and data map creation (e.g.

grid/transect locations, obstacle locations) shall be provided in formats that can be imported into Geosoft and/or ESRI software. Maps will include all the following basic map features in addition to any other necessary site information.

(1) General: All selected anomalies and known features shall be marked with symbols on the map. Map scales should be even multiples of the base units presented in the map. Map sizes should be designed to fit standard printer or plotter sizes. Grid ticks or grid lines should be visible and labeled.

(2) Title block: Include Figure number, the map Title and sub-title (e.g. instrument and type/component) and the location of the information being presented (e.g. site/area name and property/grid ID).

(3) Legend: All objects/symbols shown on the map should be identified in the legend. Map Scale bar, coordinate system and North arrow shall be included. Color scale bars should use a color scheme that clearly differentiates between anomalies and background readings.

Background values should be plotted in white or gray, so as not to distract the viewer. A classic “cold to hot” color scale should be used with negative values plotted in blue and high positive values plotted in red/pink. The range of values should be “fixed” so that the same color scale is utilized across the site. The region of major interest is almost always near the detection/background limit, not the maximum or minimum values of the data set.

(4) Additional Project Information: minimum requirements are to have boxes for the following information: Client, Project, Contractor, Map creator, Map approver, Date created.

5.0 Data Submittals

5.1 The Contractor shall furnish all geophysical data, geophysical maps and dig sheets to CEHNC, via internet using CEHNC-approved FTP, E-mail attachment for small files under 5 Mb, CD/DVD or other approved method, for inspection. Data submittals shall be delivered in a single package (i.e. zip file) and be self-extracting into a consistent file structure as appropriate. All geophysical data shall be accompanied by metadata as described in Section 4. The delivery schedule shall be in accordance with Attachment C, unless otherwise established by the PDT. Analog QC data shall be submitted on a recurring basis during field work, as established by the PDT. The Contractor shall also provide a digital planimetric map in ESRI ArcView, Geosoft, or other approved format, and coincident with the location of the geophysical survey, so that each day's geophysical data set can be registered within the original mission plan survey map. Each data submittal shall include the Attachment B tables to identify the quality of the data and whether it is meeting project objectives. Any QC failures shall be identified and the corrective action that is being taken shall be described. The Government Geophysicist shall be notified of each QC failure within a week. The final report deliverable shall include two copies on CD/DVD of all project data.

5.2 If the Contractor proceeds with any phase of field work (dynamic, cued and intrusive) prior to the Government’s acceptance of their data, they shall proceed at their own risk. Note that quality assurance of field work by an OESS (Ordnance and Explosives Safety Specialist) is in addition to quality assurance by the Government Geophysicist. If the Government finds that the Contractor has failed to meet Data Quality Objectives as defined in their approved QAPP, the Contractor shall re-collect the data at zero cost to the Government.

6.0 Contractor Minimum Performance And QC Requirements.

6.1 The Contractor shall include in their QC plan specific tests as described in Section 3 above and listed references. The values listed in the various requirements (see EM 200-1-15 Tables 11-1 to 11-6) may be adjusted upon request, provided the Contractor supplies supporting documentation and rationales for Government concurrence. Acceptance sampling parameters for anomaly resolution are provided in EM 200-1-15 Table 6-6. All reported QC results from these tests will be reviewed as part of government QA.

In the event a requirement is not met and the contractor submits the data to the Government, the contractor shall provide rationales for accepting them. All such rationales will be reviewed as part of government QA. If the rationales are either insufficient or technically unfeasible, or are attempts to justify non-conformances that should be corrected to meet project needs, the Government will issue a Corrective Action Request to the contractor and the submittal(s) will be rejected. Some performance standards are default values and may be changed by the PDT to suit project needs, potentially as a result of TPP decisions. The database template shall be used; however, the required fields will change based on the final QCP as approved by the PDT.

7.0 Advanced Classification Data

7.1 The Contractor shall use advanced geophysical classification (AGC) in both dynamic and cued mode where appropriate as approved by the PDT. Contractors performing AGC must be accredited IAW the Defense Advanced Geophysical Accrediting Program (DAGCAP) as per the 'Office of the Assistant Secretary of Defense Memorandum, Subject: Department of Defense Geophysical Classification Accreditation Program, April 11, 2016'. AGC work will utilize the Uniform Federal Policy for Quality Assurance Project Plan, Advanced Geophysical Classification for Munitions Response (AGC-QAPP), and/or Munitions Response QAPP Toolkit latest version as maintained on the DAGCAP webpage on the Military Munitions Response Program page, http://www.denix.osd.mil/mmrp.

7.2 Daily AGC raw data along with QC results and field forms shall be provided to the Government QA on a weekly basis or as approved in the Final QAPP. Delivery Units (DUs) and related schedules shall be agreed to prior to field work start. DU submittals shall include a summary of dates and areas included in each DU, status of all related MQOs, and any RCAs/NCRs for MQO failures. It is recommended that each DU submittal includes a Draft Data Usability Assessment (DUA), and the summary of data and MQOs is included as part of the Draft DUA.

8.0 End of DID HNC-003.03.

http://www.denix.osd.mil/mmrp

Attachment A

Field Data Sheet

Project Name: _______________________________ Project Location: ___________________________

Geophysical Contractor: ______________________ Field Team:________________________________

Coordinate System (w/ units): ___________________ Survey Type:_______________________________

Survey Area ID: _____________________________ Date: _____________________________________

Raw Data File Name: _________________________ Repeat Data File Name:______________________

Geophysical Instrumentation: __________________ Serial Number: _____________________________

Navigation Method: ___________________________ Serial Number: ____________________________

Additional Comments:__________________________________________________________________________

Sketch of Survey Area- include North arrow, Approximate scale, brief description of terrain, site conditions, and any surface features potentially affecting the data quality or coverage.

Attachment B

DID_Tables Access Database

This Appendix identifies reporting conventions that shall be used to deliver information associated with geophysical activities. Tables for reporting information are separated by common functions or activities and include reporting specification for MQOs (Measurement Quality Objectives) including function test results, QC assessment information and results, anomaly characteristics, dig lists, reacquisition information and intrusive investigation information. Separate reporting formats and conventions are provided for digital and analog geophysical activities in Figures B1 and B2, respectively. Not all information in the template Access Databases is required; however all information that is necessary to document QC requirements success or failure are mandatory. All

DGM required information shall be kept in the DGM Access Database (Fig. B1) and all analog required information shall be kept in the Analog Access Database (Fig. B2). Separate databases for subcontractor data shall not be accepted unless agreed to by the QA geophysicist.

Where appropriate, a “QCStatus” field is included in a table to indicate whether all associated QC assessments and tests have been performed and accepted or rejected by QC personnel. Site specific

QC metrics and requirements shall be developed by the PDT. Those metrics and requirements can be appended to these tables to simplify reporting and checking activities, and their format and use should be defined collaboratively by the PDT. All changes to the CEHNC database template(s) shall be described either in a README file or the Access database design view Description field.

Note that all units of measurement shall be provided in project coordinate system units (e.g. if project is UTM NAD 83 meters, depth and offsets should also be reported in meters). All number field shall reflect the precision of the measurement being taken. All positions shall be recorded to at least two decimal places for RTK/RTS. All millivolt values shall be reported to at least one decimal place. All numeric fields shall be number data types, not text. Use 99999 for Not/Applicable or Null values. Date fields shall be data type date/time. Fields with lookup tables (e.g. Anomaly_Type) shall not be modified unless approved by the QA Geophysicist. Intrusive Results with multiple items recovered per Target_ID shall use Recovered_Item_Count so that each item has a unique record.

Contact CEHNC for the latest version of the DGM and analog databases.

Figure B1: DGM Access Database Tables

Figure B2: Analog Access Database Tables

Note that Intrusive Results for analog grids/transects shall include at a minimum: dig date(s); dig team(s); number of anomalies; quantity and weights of MEC, MD, NMRD (Non-Munitions Related Debris), quantity of Geo anomalies;

evidence of HE; and maximum depth of MD/MEC.

Attachment C

Geophysical Submittals & Due Dates

With Each Submittal

24 hours after collection

24 hours after request by government representative

By the Following Friday (1 week after data collection)

Per QAPP schedule

CD/DVD With Final Report

ReadMe File X

Index Map X

Updated DID_Tables Access Database

X

QC logs, checklists and associated documentation

X X

First Week’s mapping and QC data

X

Special Request Draft Data X

DGM Data Package for each week’s data collection (raw and final mapping & QC data, Maps, Field Data Sheets, & updated associated database tables)

X

AGC Daily Data (raw, QC data, field forms)

X

AGC Delivery Unit X

Intrusive Results / Anomaly Resolution / Dig Photos and Final Decision Plots (AGC)

X

Response to QA Comments X

Summary of MQOs and any associated RCA/NCR

X

All Raw & Final Digital Data, Maps, Final Access Database, Final QC documentation

HNC-004.02

Title: Hydrography

Number: HNC-004.02 Approval Date: 20200731 AMSC Number: Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-G

Applicable Forms: Attachment A – Hydrographic Data Submittals & Due Dates

Use/Relationship: This Data Item Description will be used to describe the requirements, methods, equipment, and accuracy for conducting hydrographic surveys for Military Munitions Response (MMR) projects, as well as instructions for preparing UFP-QAPP Worksheets and data requirements. This DID specifies naming and formatting conventions for data deliverables associated with hydrographic activities.

This DID shall be used in association with EM 1110-2-1003. Additional references include the National Oceanic and Atmospheric Administration Hydrographic Surveys Specifications and Deliverables (NOAA, 2016) and the International Hydrographic Organization (IHO) Manual on Hydrography, Publication C-13 (IHO, 2011). If references are updated, the contractor shall use the latest version.

Requirements:

1.0 General.

1.1 Hydrographic surveys prior to Digital Geophysical Mapping (DGM) shall be conducted in areas where sensitive habitats exist, particularly where threatened and endangered (T&E) species exist.

Hydrographic surveys shall also be conducted in underwater areas that have unfamiliar bathymetry, potential obstructions, and where there is a risk to damaging DGM equipment and impacting project schedules.

1.2 Methods. Hydrographic survey methods include bathymetric and sonar technologies as described in CH 6 of EM 200-1-15 as well as EM 1110-2-1003. Multibeam bathymetric sensors shall be used to collect swath bathymetry data along planned DGM survey areas. Additionally an imaging technique such as side-scan sonar shall be used to provide an acoustic image of the sea or lake bottom and determine if obstacles are present.

1.3 Accuracy. Hydrographic surveys shall use Real-Time Kinematic (RTK) differential GPS (Global Positioning System) with sub-meter horizontal positioning accuracy. Vertical references should remain consistent between hydrographic survey data and DGM survey data collection. Generally, hydrographic data collected for MMR projects do not require navigational-level survey control. However, if the data will be used for navigation projects in addition to MMR, refer to EM 1110-2-1003, NOAA Hydrographic Surveys Specifications and Deliverables, and IHO Publication C-13 for additional accuracy requirements.

2.0 QAPP. The Contractor shall incorporate all aspects of the Hydrographic Investigation into the UFP- QAPP Worksheet 17 and related SOPs. The plan shall provide details of the approach, methods, and operational procedures to be employed to perform hydrographic surveys in support of MMR projects.

The plan shall describe how hydrographic surveys and related activities will meet the project’s Data Quality Objectives (DQOs). Hydrographic data needs and operating procedure requirements shall be identified and specified to support project DQOs. Additionally, the following topics shall be addressed in the hydrographic survey plan:

a. Specific Area(s) to be investigated, including a Survey Mission Plan Map.

b. Account for and address all known project specific constraints, adverse conditions or features potentially affecting surveys (i.e. endangered species, hazards to navigation, wind/waves.)

c. Hydrographic equipment and field procedures (i.e. Side-scan Sonar, Multibeam Sonar)

d. Required field documentation (e.g. QC checklists)

e. Data processing, corrections and analysis

f. Descriptions of final data formats and final map formats.

3.0 Quality Control. The hydrographic sections of the QC plan shall follow guidance provided in EM 1110-2-1003 (e.g. Table 6-3) and be incorporated into the UFP-QAPP Worksheet 22 and related SOPs.

At a minimum, the quality control plan shall address horizontal and vertical accuracy of the data.

Additional quality control elements may be identified by the PDT dependent on the standards being met to satisfy project needs. The quality control plan shall identify meaningful and reasonable QC checking and testing procedures to define and document the quality achieved by the work processes performed and in the data generated. The QC plan shall include procedures for performing root-cause analyses when failures occur. Results of QC tests and calibrations shall be documented in an Access database, Excel spreadsheet or some other format as determined by the PDT.

4.0 Data Format Requirements. The formats specified in this paragraph are REQUIRED to be exactly followed, although the Contractor may choose to submit the data in additional formats as well. All hydrographic data shall be accompanied by metadata in the form of a read-me file or a database or spreadsheet table documenting the processing performed and data naming conventions. Metadata shall fully describe all measurements recorded in each data file, and shall include all information necessary to successfully associate all hydrographic system measurements to their correct geographical location.

a. Raw Hydrographic Survey Data Format and Storage. Raw survey data will be stored in a logical file directory (folder) structure to facilitate its management and dissemination to PDT members. Raw field data is defined as all digital data generated from the hydrographic system in its native format, and includes any other peripheral or instrument measurements collected or recorded during data acquisition.

All raw field data shall have a time stamp associated with each measurement event. At the discretion of the PDT, raw field data may include hydrographic system data that has been checked, corrected and processed into ASCII files, either individually by instrument or merged with positioning data.

b. Final Processed and Advanced Processed Data Format and Storage. Final and Advanced (as required) processed data shall be produced and presented in ASCII formatted files and native hydrographic processing software formats (e.g. HYPACK/HYSWEEP). Final processed data is defined as data that represents, to the best of the Contractor’s ability, the true nature that exists at each actual location measured by the hydrographic system. Final processed data shall be corrected for positioning offsets, roll-pitch-yaw-angle offsets, sound speed corrections, and tide corrections. Advanced processed data is defined as Final Processed data that has been subjected to additional advanced processing (e.g.

editing) techniques. All corrections and processing steps will be documented in metadata. Metadata for final processed and advanced processed data shall include UTM zone, coordinate units and datum (the PDT or PWS may require additional coordinate units and projections be included). All measurement events shall have a time stamp. Each data file will be logically and sequentially named so that the file name can be easily correlated with the project-specific naming conventions used by the PDT. Naming conventions of files and data fields shall be included with metadata.

c. GIS Format. For final hydrographic data submittals, the contractor shall provide geospatial files in standard ESRI ArcGIS formats; to include point clouds, shapefiles, Geo-Tiffs, ASCII Grids, etc. Map images in a common image format (e.g. JPEG) for viewing without the software used to produce the maps shall also be provided. Maps will include all the following basic map features in addition to any other necessary site information.

(1) General: Map scales should be even multiples of the base units presented in the map. Map sizes should be designed to fit standard printer or plotter sizes. Grid ticks or grid lines should be visible and labeled.

(2) Title block: Include Figure number, the map Title and sub-title (e.g. instrument and type/component) and the location of the information being presented (e.g. site/area name and property/grid ID).

(3) Legend: All objects/symbols shown on the map should be identified in the legend. Map Scale bar, coordinate system and North arrow shall be included. Color scale bars should use a typical color scheme that clearly shows depth variation.

(4) Additional Project Information: minimum requirements are to have boxes for the following information: Client, Project, Contractor, Map creator, Map approver, Date created.

5.0 Data Submittals

5.1 The Contractor shall furnish all hydrographic data, maps and QC records to CEHNC, via internet using USACE-approved File Transfer Protocol (FTP), E-mail attachment for small files under 5 Mb, CD/DVD or other approved method, for inspection. The delivery schedule shall be in accordance with Attachment A, unless otherwise established by the PDT. The Contractor shall also provide a digital planimetric map in ESRI ArcGIS, Geosoft, or other approved format, and coincident with the location of the hydrographic survey, so that each day's data set can be registered within the original mission plan survey map. Any QC failures shall be identified and the corrective action that is being taken shall be described. The final report deliverable shall include two copies on External Hard-drive/DVD of final project data and one copy of the raw data.

6.0 Contractor Minimum Performance and QC Requirements

The Contractor shall include in their SOPs and UFP-QAPP Worksheet 22 specific tests to document the minimum standards for the hydrographic survey. The specific quality metrics may be adjusted upon request provided the Contractor supplies supporting documentation and rationales for Government concurrence. All reported QC results and documentation will be reviewed as part of Government QA. In the event a requirement is not met and the contractor submits the data to the Government, the contractor shall provide rationales for accepting them. All such rationales will be reviewed as part of government QA. If the rationales are either insufficient or technically unfeasible, or are attempts to justify non-conformances that should be corrected to meet project needs, the Government will issue a Corrective Action Request to the contractor and the submittal(s) will be rejected.

7.0 End of DID HNC-004.02.

DID USERS-TBD

Hydrographic Data Submittals & Due Dates

With Each Submittal 24 hours after collection

24 hours after request by government representative

14 days after survey is complete, per survey area

HD/DVD With Final Report

ReadMe File X

Index Map X

Updated QC Access Database / Spreadsheet

X

First Week’s surveying and QC data

X

Special Request Draft Data X

Initial Processed Data Package for each week’s data collection (Geospatial data, Maps, Field Data Sheets, & QC documentation)

X

All Raw & Final Digital Data, Maps, Final QC Access Database, Final QC documentation

HNC-005.03

DATA ITEM DESCRIPTION

Title: Chemical Data Quality Deliverables

Number: HNC-005.03 Approval Date: 20200817 AMSC Number: N/A Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-E Applicable Forms:

Use/Relationship: Chemical Data Quality Deliverables will be used to describe planning and results of sampling and analysis, quality assurance/quality control, laboratory qualification, data acquisition/data reporting, and chain-of-custody when environmental samples are required for projects.

Requirements:

1.0 REFERENCES

The publications listed below form a part of this DID to the extent referenced. The publications are referred to in the text by basic designation only. It is up to the contractor to obtain the latest guidance documents.

DoD Environmental Laboratory Accreditation Program (DoD ELAP)

DOD Quality Systems Manual for Environmental Laboratories (DoD QSM)

Uniform Federal Policy for Quality Assurance Project Plans

EM 200-1-4 Risk Assessment Volumes I and II

EM 200-1-6 Chemical Quality Assurance

ER 200-1-7 Data Quality Management for Hazardous, Toxic, Radioactive Waste

Remedial Activities

EP 75-1-3 Recovered Chemical Warfare Materiel (RCWM) Response

EM 200-1-15 Technical Guidance for Military Munitions Response Actions

Formerly Used Defense Sites Online Chemical Database (FUDSCHEM) User Manual

EMDQ Data Validation Guidelines, all current Modules to include updates located at:

https://denix.osd.mil/edqw/home/

EPA 530/F-93/004 Test Methods for Evaluating Solid Waste SW -846 and updates Hazardous Waste Test Methods

Data Validation Guidelines Modules to include updates located at: https://denix.osd.mil/edqw/home/

2.0 Chemistry Data Package.

2.0.1 All laboratory data for samples analyzed by commercial laboratories shall be submitted in the Staged Electronic Data Deliverable (SEDD) format unless the PWS/SOW states otherwise. Details on the SEDD format are provided in SEDD Version 5.2 (or most recent version) specification located at https://www.epa.gov/clp/sedd-specification-document-52.

2.0.2 Electronic data deliverables for Chemistry Data are required prior to approval of a Final Report.

These deliverables shall be reviewed and must be found acceptable for milestone approval.

2.1 Automated Data Review and Evaluation.

2.1.1 All data shall be fully validated.

2.1.2 Automated Data Review (ADR) is now available free of charge through www.fudschem.com to all FUDS projects and contractors. The Validation must also meet the requirements of the EMDQ Data Validation Guidelines.

2.1.3 SEDD Essentials is a self-inspection tool that allows users to evaluate a Staged Electronic Data Deliverable (SEDD) format Electronic Data Deliverable (EDD) against minimum SEDD structural and completeness requirements. It is method agnostic, and allows inspection at the Stage 2a, 2b, or 3 level.

The resulting report provides information about the EDD, including the errors found and their location within the EDD.

3.0 Reporting

3.1 FUDSCHEM Reporting

3.1.1 If the task order involves a Formerly Used Defense Site (FUDS) the laboratory and/or contractor shall import the ADR reviewed SEDD file with the associated eQAPP file and field data directly into the Formerly Used Defense Site Chemical Database online (FUDSCHEM) at https://www.FUDSCHEM.com. The eQAPP should be generated within FUDSCHEM to the greatest extent possible. The uploaded file must also contain a table that links the Client Sample ID to the Location ID. A Waste Template is available and shall be used to record all waste data. Other field parameters, types of data, and associated tables that the contractor is responsible for uploading include the following: spatial information pertaining to sample locations (northing, easting, and elevation), hydrogeological information and physical parameters (groundwater samples - pH, temperature, conductivity, turbidity), monitoring well construction information such as monitoring point elevations, screen intervals, depth to water and other aspects of well construction (sand pack, bentonite seal, etc.), including soil lithology, logged geologic stratigraphy, environmental monitoring data, and unexploded ordnance (UXO) data are to be loaded into FUDSCHEM pursuant to the Data Management Plan using on-line templates or uploaded directly to FUDSCHEM using comma separated variable (csv) files.

3.1.2 Prior to uploading the data to FUDSCHEM, the contractor will identify one or more individuals who will be responsible for uploading the data. These identified individuals will be given upload/read/write access to FUDSCHEM for the specific project they are assigned to by the FUDSCHEM administrator. The Contractor identified personnel shall also be required to attend training by the Government FUDSCHEM contractor on how to upload various types of data in FUDSCHEM (see below). Contractor and Laboratory personnel are responsible for troubleshooting any data issues/problems or discrepancies concerning the data being uploaded into FUDSCHEM. The Contractor and/or Laboratory will work with the Government FUDSCHEM contractor to resolve any and all data issues associated with the data deliverable they are uploading into FUDSCHEM.