EXHIBIT_1_-_HNC_DIDs_.pdf

HNC-001.02

DATA ITEM DESCRIPTION

Title: Project Planning Documents

Number: HNC-001.02 Approval Date: 20160120 AMSC Number: Limitation:

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

Use/Relationship: Project Planning Documents will be used to describe the goals, methods, procedures, and personnel used for field activities for all Munitions Response remedial or removal responses and other munitions related actions.

Requirements:

1. 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. 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. 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. The contractor shall not place a company logo on Project Planning Documents.

1.4 Each page of the document shall contain a date footer and the Corps of Engineers’ contract/Task Order number.

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 date footer. A dated summary page listing all revised pages shall be submitted with each revision. This summary page shall be identified as such and placed directly behind the title page.

2. 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, Chapter 4 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, section 4.4.5. Standard Operating Procedures shall be organized as described in EM 200- 1-15, Section 4.4.4. Appendices shall be organized as described in EM 200-1-15 with the following exception, Standard Operating Procedures shall be the first Appendix.

2. End of DID HNC-001.02.

HNC-003.02

DATA ITEM DESCRIPTION

Title: Geophysics

Number: HNC-003.02 Approval Date: 20170113 AMSC Number: Limitation:

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 (USAESCH, 2003).

Requirements:

1. 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. 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.

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. 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 USAESCH and as described in Attachment B. Contact the USAESCH 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. 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 USAESCH 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. Data Submittals The Contractor shall furnish all geophysical data, geophysical maps and dig sheets to USAESCH, via internet using USAESCH-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 final report deliverable shall include two copies on CD/DVD of all project data.

6.0 Contractor Minimum Performance And QC Requirements

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

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), latest version as maintained on the DAGCAP webpage on the Military Munitions Response Program page, http://www.denix.osd.mil/mmrp.

8.0 End of DID HNC-003.02.

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 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).

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.

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

Figure B1: DGM Access Database Tables

Figure B2: Analog Access Database Tables

Attachment C

Geophysical Submittals & Due Dates

With Each Submittal

24 hours after collection

24 hours after request by government representative

By the Following Friday

7 days after completed excavations of each grid/transect

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

Intrusive Results Tables X

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

X

HNC-004.01

DATA ITEM DESCRIPTION

Title: Hydrography

Number: HNC-004.01 Approval Date: 20170113 AMSC Number: Limitation:

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 contains instructions for preparing UFP-QAPP Worksheets and data requirements when addressing hydrographic investigations for Munitions Response or other munitions related projects. 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).

Requirements:

1. Hydrographic Survey Plan. The Contractor shall incorporate all aspects of the Hydrographic Investigation 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 hydrographic surveys at Munitions Response or other munitions related 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.

2. Quality Control. The hydrographic sections of the QC plan shall follow guidance provided in EM 1110-2-1003 (see Table 11-2) and be incorporated into the UFP-QAPP for MEC 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 IHO 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.

3. 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. Fledermaus). 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 have all corrections applied needed to correct 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 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.

4. Data Submittals The Contractor shall furnish all hydrographic data, maps and QC records to USAESCH, via internet using USACE-approved 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 QC plan specific tests to document the minimum standards for the hydrographic survey (e.g. IHO Order 1). 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. End of DID HNC-004.01.

DID USERS-TBD

Attachment A

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

X

HNC-005.02

DATA ITEM DESCRIPTION

Title: Munitions Constituents Chemical Data Quality Deliverables

Number: HNC-005.02 Approval Date: 20170105 AMSC Number: Limitation:

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

Use/Relationship: Munitions Constituents (MC) 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 Munitions Response or other munitions related projects.

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.

DEPARTMENT OF DEFENSE

OSD memorandum: DoD Environmental Laboratory Accreditation Program (DoD ELAP), December 24. 2008 (will be rescinded and replaced by a citation in DOD Instruction Number 4715.15)

Uniform Federal Policy for Quality Assurance Project Plans (latest version) (DoD/EPA/DOE joint publication)

DOD Quality Systems Manual for Environmental Laboratories (DoD QSM) (latest version) as referenced in DOD Instruction Number 4715.15

Uniform Federal Policy for Quality Assurance Project Plans (latest version) (DoD/EPA/DoE joint publication) as referenced in DOD Instruction Number 4715.15

Department of Defense Policy and Guidelines for Acquisitions Involving Environmental Sampling or Testing

U.S. ARMY CORPS OF ENGINEERS (USACE)

HQ USACE Memorandum HTRW Chemical Data Quality Management (CDQM) Policy for Environmental Laboratory Testing, September 30, 2004.

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, Latest Version (Provided upon request.)

U.S. ENVIRONMENTAL PROTECTION AGENCY (EPA)

EPA 540-R-99-008 Contract Laboratory Program National Functional Guidelines for Organic Data Review

EPA 540-R-04-004 Contract Laboratory Program National Functional Guidelines for Inorganic Data Review

EPA 530/F-93/004 Test Methods for Evaluating Solid Waste (Rev 0; updates I, II, IIA, (Vol. IA, IB, IC, and II) and new methods published at IIB, III, IIIA, IIIB, IVA, http://www.epa.gov/epaoswer/hazwaste/test/new-meth.htm and IVB)

2.0 SUBMITTALS

In addition to requirements in IG 14-01 (EM 200-1-15), the contractor shall provide the following submittals. Government approval is required for submittals with a "G" designation; submittals not having a "G" designation are for information only. The following shall be submitted in accordance with project-specific statements of work:

2.1 Chemistry Data Package.

The chemistry data package shall be provided to Contracting Agency after each sampling event.

2.2 Electronic Data Deliverable; G.

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 http://www.epa.gov/superfund/programs/clp/sedd.htm. The following software is available upon request to support this task as government furnished software:

Environmental Data Management System (EDMS), MRSPP Wizard, and Forms II Lite. The following software is available for a fee from Laboratory Data Consultants (2071 Loker Ave West, Suite 220, Carlsbad, CA 92010, 760-827-1100, http://www.lab-data.com); Automated Data Software (ADR.NET). Use of the ADR.NET software is mandatory, use of EDMS and Forms II Lite are optional. Use of the MRSPP Wizard is mandatory if MRSPP preparation is part of the SOW/PWS. 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.2.1 For SEDD Stage 2A files, the files shall successfully pass the EPA Stage 2A checker (http://epasmoweb.fedcsc.com/seddchecker/uploadservlet)

2.2.2 For SEDD Stage 2B files, there is no current known checker of this type. If the 2A checker can be used to check those portions of the 2B files, it shall be used.

2.2.3 The reviewed files (PREP files) shall be consistent with flagged data tables provided in the report. If there are manually derived data flags (from hard copy review), they shall be documented in the reviewed data file.

2.2.4 If the task order involves a Formerly Used Defense Site (FUDS) and if required under the Task Order, 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 uploaded file must also contain a table that links the Client Sample ID to the Location ID.

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.

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.

The support from the Government FUDSCHEM contractor is provided at no cost to the Contractors or Laboratories working on USACE FUDS contracts. The contractor shall provide USACE the data validation report via the FUDSCHEM shared Files.

Use and training pertaining to FUDSCHEM shall be provided by the Government FUDSCHEM contractor at no cost to Contractors and Laboratories working on USACE FUDS Projects. Assistance in loading data to the various FUDSCHEM tables/portal will be provided by the Government. FUDSCHEM Contact information can be provided from the Contracting Officer or the Government Project Chemist upon request.

2.2.5 If the task order involves a currently active army or BRAC installation and if required under the Task Order, the laboratory and/or contractor shall import the ADR reviewed laboratory data into the Environmental Restoration Information System (ERIS) web-based database system.

Prior to uploading the data to ERIS, 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 ERIS database for the specific project they are assigned to by the ERIS administrator. The Contractor identified personnel shall also be required to attend training webinars will be available online using IBM's Sametime collaboration tool. There are three separate Webinars, an Overview of ERIS, Batch Upload, and Data Retrieval to satisfy different needs. To register for a Webinar, please contact the USAEC helpdesk at (410) 436-1244.

Contractor and Laboratory personnel are responsible for troubleshooting any data issues/problems or discrepancies concerning the data being uploaded into ERIS. The Contractor and/or Laboratory will work with the Government ERIS contractor to resolve any and all data issues associated with the data deliverable they are uploading into ERIS.

2.2.6 Other DoD services may have different database requirements. These will be specified at the Task Order level. Parameters for these databases will be provided upon request at that time.

3.0 CHEMISTRY DATA PACKAGE

The chemistry data package shall be produced and provided through Contractor to the USACE.

The laboratory shall report all analytical results greater than the Limit of Detection (LOD), which, in the analyst’s professional judgment, are believed to be reliably detected. LOQs shall be at least 3 times LODs for all analytes.

4.0 End of DID HNC-005.02.

HNC-006.02

DATA ITEM DESCRIPTION

Title: Geospatial Data and Electronic Submittals

Number: HNC-006.02 Approval Date: 2010127 AMSC Number: Limitation:

DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-EDC-D (GIS)

Applicable Forms: None

Use/Relationship: The Geospatial Information and Electronic Submittals will be used to describe methods, equipment and accuracy for conducting location surveys and mapping of Military Munitions Response (MMR) projects, and the subsequent development of Geographical Information System (GIS) data to support the mapping and document (paper and electronic) production process as well as the final report electronic data submittal requirements. This Data Item Description contains instructions for: 1.)

Geospatial Data Management Plan (DMP), 2.) Addressing geospatial data accuracy and mapping requirements, 3.) FINAL electronic submittals for geospatial data, related mapping documents, and ALL other electronic project submittals to include plans, photos, qc logs, and reports for all Programs and Projects within USACE HNC, 4.) Geospatial Data Delivery Schedule.

Requirements:

1. General.

1.1 The contractor shall develop a Geospatial DMP, which must be approved and signed by the District/Center’s Geospatial Coordinator as defined in EM 1110-1-2909 prior to site specific field work commencing. The Geospatial DMP will document the expected site-specific data needed to create a holistic geospatial dataset to include survey, mapping, imagery, CADD, BIM, GIS and any other forms of data that can be accessed by or imported into an enterprise GIS. Additional information and a DMP template is provided in EM 1110-1-2909 Appendix H. All geospatial data shall be provided in either metric or English units depending upon the needs of the individual project. Metric is the standard unit, unless otherwise specified by the specific Task Order. All geospatial data shall conform to the Spatial Data Standards for Facilities Infrastructure and Environment (SDSFIE). Samples of minimally acceptable data feature classes, domains, and attributes are available upon request from CEHNC-EDC-D (GIS), if required. The sample will be supplied in ESRI geodatabase format version 10.3, or newer if specified in the project specific task order SOW. Metadata shall be created for all feature classes within the geodatabase, and will be prepared in accordance with Federal Geographic Data Committee (FGDC) metadata standards. Further specifics regarding metadata may be supplied at the task order level.

1.2 Accuracy. Horizontal and vertical control of "Class I, Third Order" or better shall be established for the network of monuments. Horizontal control shall be based on either the English or metric system and referenced to the North American Datum of 1983 (NAD83) and the Universal Transverse Mercator (UTM) Grid System. Vertical control, if required, shall also be based on either the English or metric system and referenced to the North American Datum of 1988 (NAVD88). All surveying and mapping requirements shall meet the minimum standards set forth in EM 1110-1-1004 - Geodetic and Control Surveying. If aerial photographs or orthophotography are used to provide this survey, the aerial targets used for control points shall meet the same horizontal and vertical accuracy and requirements in EM 1110-1-1000 - Engineering and Design - Photogrammetric Mapping. All newly established control points and recovered monuments shall be of a permanent nature for recoverability during future phases of work within the same project. All control points shall be iron or steel pins, concrete monuments, or other permanent construction method. Installation of control points and monuments shall meet minimum standards set forth in EM1110-1-1002 - Survey Markers and Monumentation. A licensed Professional Land Surveyor in the State where the work is being performed shall certify all surveying requirements to include all control points, grid corners, transect points, and boundaries as required by the project. The Northing and Easting (Y, X) for all control points, grid corners, transect points, and any boundaries or closures shall be presented in a certified letter or drawing, along with an electronic submittal of the same to USACE HNC upon completion of the field work.

1.3 Geographic Information Systems (GIS) Incorporation. Spatial data created for each delivery/task order are to be provided in ESRI geodatabase format. Raster data (orthophotography, remote sensing imagery, etc.) are to be provided in Tagged Image File format (TIF) at the completion of the delivery/task order, as well as in either TIF format or MrSID-compliant format during the delivery/task order. The selection of one of these raster data formats will be defined in the task order SOW. Supporting tabular data shall be provided in ANSI SQL language format at the completion of the project, as well as in Microsoft Excel, Microsoft Access, or Oracle database format, dependent upon the storage and performance requirements of the project. The use of one of these proprietary database formats will be defined in the task order SOW. The Final Submittal in electronic format shall contain all task specific Map Documents (.mxd file) conveyed in the Task Specific Final Report. The supporting feature class information shall be conveyed in a single or multiple ESRI GeoDatabase(s) with appropriate Metadata for each feature class, so that all spatial data conveyed for a project is in a concise GeoReferenced data set.

1.4 Plotting. All of the control points (monuments, aerial targets, and property corners) recovered and/or established at the site shall be plotted at the appropriate coordinate points on reproducible electronic or hard copy media for production of planimetric or topographic maps at scales appropriate for the parcel size being described. Parcels less than 10 acres shall be plotted at 1:200. Parcels 10 – 100 acres shall be plotted at 1:600 (1”=50’). Parcels larger than 100 acres will be plotted at 1:2400 (1”=200’). Area maps shall be provided for parcels of 100 acres, and shall show sheet breakdown for subsequent sheets required for the set.

1.5 Mapping. The location, identification, coordinates, and elevations of all the control points recovered and/or established at the site shall be plotted on reproducible media for planimetric or topographic maps at the scale specified in the task order. Each control point shall be identified on the map by its name and number and the final adjusted coordinates and elevations (to the closest 0.001 meter and 0.01 foot.). Each map shall include a grid north, a true north, and a magnetic north arrow with the differences between them in degrees, minutes, and seconds shown. Grid lines or tic marks at systematic intervals with their grid values shall be shown on the edges of the map. Also, a legend showing the standard symbols used for the mapping and a map index showing the site in relationship to all other sites within the boundary lines of the project area shall be shown. The coordinates for the grid corners shall be shown to the closest one-foot (1.0 ft.), but may require greater accuracy to meet geophysical mapping and re-acquisition requirements.

2. Geospatial Data.

2.1 General Design File Requirements. An overall planimetric design file shall be created and shall be digitized into a Microstation ". dgn" file at an elevation of zero. If contours and spot elevations are required, all data shall be digitized into a second Microstation 3D design file with each element (contours and spot elevations) at their correct elevation, and topologically triangulated network (ttn) files shall be created to model the topographic surface.