EXHIBIT1-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-002

DATA ITEM DESCRIPTION

Title: Accident Prevention Plan

Number: HNC-002 Approval Date: 20140616 AMSC Number: Limitation:

DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: CEHNC-SO Applicable Forms: ENG Form 3394, Activity Hazard Analysis (AHA) EM 385-1-1, Figure 1-2 Use/Relationship: This Data Item Description contains instructions for preparing an Accident Prevention Plan (APP) for recovered chemical warfare materiel sites.

Requirements:

1.0. The contractor shall develop an Accident Prevention Plan (APP) as the safety and health policy program. The APP shall interface with the contractor’s overall safety and health program. The APP shall be prepared in the format shown and address all the elements in EM 385-1-1, Appendix A. Where a specific element is not applicable, list the element in the plan and state that the element is not applicable with a brief justification for its omission. The APP shall be an implementing document with emphasis on “who” will have each of the specific responsibilities and “how” and “when” each of the applicable requirements will be performed. The prime contractor shall integrate all subcontractor work activities into the APP, make the APP available to all contractor and subcontractor employees, and ensure that all subcontractors integrate provisions of the APP in their work activities.

1.1. SIGNATURE SHEET. Title, signature, and phone number of the following:

1.1.1. Plan preparer (Qualified Person, Competent Person, such as corporate safety staff person, QC);

1.1.2. Plan must be approved, by company/corporate officers authorized to obligate the company;

1.1.3. Plan concurrence (e.g., Chief of Operations, Corporate Chief of Safety, Corporate Industrial Hygienist, project manager or superintendent, project safety professional, project QC). Provide concurrence of other applicable corporate and project personnel (Contractor).

1.2. BACKGROUND INFORMATION. List the following:

1.2.1. Contractor;

1.2.2. Contract number;

1.2.3. Project name;

1.2.4. Brief project description, description of work to be performed, and location; phases of work anticipated (these will require an AHA).

1.3. STATEMENT OF SAFETY AND HEALTH POLICY. Provide a copy of current corporate/company Safety and Health Policy Statement, detailing commitment to providing a safe and healthful workplace for all employees.

The Contractor’s written safety program goals, objectives, and accident experience goals for this contract should be provided.

1.4. RESPONSIBILITIES AND LINES OF AUTHORITIES. Provide the following:

1.4.1. A statement of the employer’s ultimate responsibility for the implementation of his SOH program;

1.4.2. Identification and accountability of personnel responsible for safety at both corporate and project level.

Contracts specifically requiring safety or industrial hygiene personnel shall include a copy of their resumes.

Qualifications shall include the OSHA 30-hour course or equivalent course areas as listed here:

1.4.2.1. OSH Act/General Duty Clause;

1.4.2.2. 29 CFR 1904, Recordkeeping;

1.4.2.3. Subpart C: General Safety and Health Provisions, Competent Person;

1.4.2.4. Subpart D: Occupational Health and Environmental Controls, Citations and Safety Programs;

1.4.2.5. Subpart E: PPE, types and requirements for use;

1.4.2.6. Subpart F: understanding fire protection in the workplace;

1.4.2.7. Subpart K: Electrical;

1.4.2.8. Subpart M: Fall Protection;

1.4.2.9. Rigging, welding and cutting, scaffolding, excavations, concrete and masonry, demolition; health hazards in construction, materials handling, storage and disposal, hand and power tools, motor vehicles, mechanized equipment, marine operations, steel erection, stairways and ladders, confined spaces or any others that are applicable to the work being performed.

1.4.3. The names of Competent and/or Qualified Person(s) and proof of competency/qualification to meet specific OSHA Competent/Qualified Person(s) requirements must be attached. The District SOHO will review the qualifications for acceptance;

1.4.4. Requirements that no work shall be performed unless a designated competent person is present on the job site;

1.4.5. Requirements for pre-task safety and health analysis;

1.4.6. Lines of authority;

1.4.7. Policies and procedures regarding noncompliance with safety requirements (to include disciplinary actions for violation of safety requirements) should be identified;

1.4.8. Provide written company procedures for holding managers and supervisors accountable for safety.

1.5. SUBCONTRACTORS AND SUPPLIERS. If applicable, provide procedures for coordinating SOH activities with other employers on the job site:

1.5.1. Identification of subcontractors and suppliers (if known);

1.5.2. Safety responsibilities of subcontractors and suppliers.

1.6. TRAINING.

1.6.1. Requirements for new hire SOH orientation training at the time of initial hire of each new employee.

1.6.2. Requirements for mandatory training and certifications that are applicable to this project (e.g., explosive actuated tools, confined space entry, crane operator, diver, vehicle operator, HAZWOPER training and certification, PPE) and any requirements for periodic retraining/recertification.

1.6.3. Procedures for periodic safety and health training for supervisors and employees.

1.6.4. Requirements for emergency response training.

> See paragraph 1.9.2. below for a list of requirements that may require emergency response training.

1.7. SAFETY AND HEALTH INSPECTIONS.

1.7.1. Specific assignment of responsibilities for a minimum daily job site safety and health inspection during periods of work activity: Who will conduct (e.g., SSHO, PM, safety professional, QC, supervisors, employees – depends on level of technical proficiency needed to perform said inspections), proof of inspector’s training/qualifications, when inspections will be conducted, procedures for documentation, deficiency tracking system, and follow-up procedures;

1.7.2. Any external inspections/certifications that may be required (e.g., USCG).

1.8. ACCIDENT REPORTING. The Contractor shall identify person(s) responsible to provide the following:

1.8.1. Exposure data (man-hours worked);

1.8.2. Accident investigations, reports, and logs: Report all accidents as soon as possible but not more than 24 hours afterwards to the Contracting Officer/Representative (CO/COR). The contractor shall thoroughly investigate the accident and submit the findings of the investigation along with appropriate corrective actions to the CO/COR in the prescribed format as soon as possible but no later than five (5) working days following the accident.

Implement corrective actions as soon as reasonably possible;

1.8.3. The following require immediate accident notification:

1.8.3.1. A fatal injury;

1.8.3 .2. A permanent total disability;

1.8.3.3. A permanent partial disability;

1.8.3.4. The hospitalization of three or more people resulting from a single occurrence;

1.8.3.5. Property damage of $500,000 or more;

1.8.3.6. Arc Flash Incident/Accident;

1.8.3.7. USACE aircraft destroyed or missing; or

1.8.3.8. Three or more individuals become ill or have a medical condition which is suspected to be related to a site condition, or a hazardous or toxic agent on the site.

1.9. PLANS (PROGRAMS, PROCEDURES) REQUIRED BY THE SAFETY MANUAL. Based on a risk assessment of contracted activities and on mandatory OSHA compliance programs, the Contractor shall address all applicable occupational risks and compliance plans. Using the EM 385-1-1 as a guide, plans may include but not be limited to:

1.9.1. Layout plans (EM 385-1-1, 04.A.01);

1.9.2. Emergency response plans:

1.9.2.1. Procedures and tests (EM 385-1-1, 01.E.01);

1.9.2.2. Spill plans (EM 385-1-1, 01.E.01, 06.A.02);

1.9.2.3. Firefighting plan (EM 385-1-1, 01.E.01, Section 19);

1.9.2.4. Posting of emergency telephone numbers (EM 385-1-1, 01.E.05);

1.9.2.5. Man overboard/abandon ship (EM 385-1-1, 19.A.04);

1.9.2.6. Medical Support. Outline on-site medical support and offsite medical arrangements including rescue and medical duties for those employees who are to perform them, and the name(s) of on-site Contractor personnel trained in first aid and CPR. A minimum of two employees shall be certified in CPR and first aid per shift/site (EM 385-1-1, 03.A.02; 03.D);

1.9.3. Plan for prevention of alcohol and drug abuse (EM 385-1-1, 01.C.02);

1.9.4. Site sanitation plan (EM 385-1-1, 02);

1.9.5. Access and haul road plan (EM 385-1-1, 04.B);

1.9.6. Respiratory protection plan (EM 385-1-1, 05.G);

1.9.7. Health hazard control program (EM 385-1-1, 06.A);

1.9.8. Hazard communication program (EM 385-1-1, 06.B.01);

1.9.9. Process Safety Management Plan (EM 385-1-1, 06.B.04);

1.9.10. Lead abatement plan (EM 385-1-1, 06.B.05 & specifications);

1.9.11. Asbestos abatement plan (EM 385-1-1, 06.B.05 & specifications);

1.9.12. Radiation Safety Program (EM 385-1-1, 06.E.03.a);

1.9.13. Abrasive blasting (EM 385-1-1, 06.H.01);

1.9.14. Heat/Cold Stress Monitoring Plan (EM 385-1-1, 06.I.02)

1.9.15. Crystalline Silica Monitoring Plan (Assessment) (EM 385-1-1, 06.M);

1.9.16. Night operations lighting plan (EM 385-1-1, 07.A.08);

1.9. 17. Fire Prevention Plan (EM 385-1-1, 09.A);

1.9. 18. Wild Land Fire Management Plan (EM 385-1-1, 09.K);

1.9.19. Hazardous energy control plan (EM 385-1-1, 12.A.01);

1.9.20. Critical lift Plan (EM 385-1-1, 16.H);

1.9. 21. Contingency plan for severe weather (EM 385-1-1, 19.A.03);

1.9.22. Float Plan (EM 385-1-1, 19.F.04);

1.9.23. Site-Specific Fall Protection & Prevention Plan (EM 385-1-1, 21.C);

1.9.24. Demolition plan (to include engineering survey) (EM 385-1-1, 23.A.01);

1.9.25. Excavation/trenching plan (EM 385-1-1, 25.A.01);

1.9.26. Emergency rescue (tunneling) (EM 385-1-1, 26.A);

1.9.27. Underground construction fire prevention and protection plan (EM 385-1-1, 26.D.01);

1.9.28. Compressed air plan (EM 385-1-1, 26.I.01);

1.9.29. Formwork and shoring erection and removal plans (EM 385-1-1, 27.C);

1.9.30. PreCast Concrete Plan (EM 385-1-1, 27.D);

1.9.31. Lift slab plans (EM 385-1-1, 27.E);

1.9.32. Steel erection plan (EM 385-1-1, 27.F.01);

1.9.33. Site Safety and Health Plan for HTRW work (EM 385-1-1, 28.B);

1.9.34. Blasting Safety Plan (EM 385-1-1, 29.A.01);

1.9.35. Diving plan (EM 385-1-1, 30.A.13);

1.9.36. Confined space Program (EM 385-1-1, 34.A).

1.10. RISK MANAGEMENT PROCESSES. Detailed project-specific hazards and controls shall be provided by an Activity Hazard Analysis (EM 385-1-1, 01.A.13) for each major phase/activity of work.

2.0 Special Considerations for CWM sites.

2.1 Personal Protective Equipment (PPE). PPE used to protect workers from site-related hazards (explosive ordnance, construction safety and health and contaminant related) shall comply with requirements specified in EM 385-1-1, Section 5. PPE that is used to protect workers against chemical agent must be approved by the Office of the Director of Army Safety (OSASAF) or be NIOSH- approved for chemical, biological, radiological, and nuclear (CBRN) protection in accordance with DA Pam 385-61. The approval process for PPE is found in Section 1.7 and a list of approved protective clothing and equipment is found in Section 4-17.

2.2 Medical Surveillance. All personnel performing on-site work that will result in exposure to contaminate-related health and safety hazards shall be enrolled in a medical surveillance program hat complies with OSHA standards 29 CFR 1910.120, 29 CFR 1926.65(f) and Da Pam 40-173 and/or DaPam 40-8, and the “Interim Guidance on Occupational Health Practices for the Evaluation & Control of Occupational Exposures to Nerve Agents GA, GB, GD, GF and VX and Mustard Agents H, HD, and HT.”

2.4 Medical Support. In section 1.9.2.6 of this DID, include the medical support arrangements made for the treatment of chemical casualties. All medical support arrangements shall be in accordance with the requirements of the “Interim Guidance for Chemical Warfare material (CWM) Responses” dated April 1, 2009. The signed memorandum of Agreement/Contract for the hospital and onsite medical support shall be maintained onsite and available for review. The contractor shall also maintain a roster of the medical support personnel who have been trained in chemical agent casualty care.

2.5 Exposure monitoring/air sampling program. …. An air monitoring summary shall be included in the monitoring section of the SSHP. This table shall include, but is not limited to the following: contaminates of concern (agent and industrial), instrument to monitor, location of instrument, frequency, agency conducting monitoring, action level and actions to be taken.

2.6 Public Safety. The contractor shall include a section on public safety as an addendum to the APP. It shall include a discussion on the maximum credible event (MCE), 1-percent lethality arc, and the public withdrawal distance also known as the inhabited building distance (IBD). The Contractor, based on historical records, shall recommend an MCE. If a site has several operable units, an MCE shall be determined for each site. Documentation

(downwind hazard calculations) will be determined using DDESB approved software that implements the methodology to be used to perform these calculations. The calculated hazard distance is based on the longest distance of the hazardous fragment distance (HFD), IBD for overpressure, or the one percent lethality distance. For siting purposed, the public access exclusion distance (PAED) is analogous to the IBD for explosives; therefore, personnel not directly associated with the operations are not to be allowed within the PAED. Hazard distance calculations shall conform to DDESB Technical Paper 10 and DDESB approved software for the one percent lethality arc for a toxic chemical agent source.

2.7 General. On some projects a site may be determined to be “non-CWM” by determining the probability of encountering CWM in accordance with the requirements in the “Interim Guidance for Chemical Warfare Material (CWM) Response” or may involve CAIS that contains dilute chemical agents or industrial chemicals which are not considered CWM. These sites which have been determined not to be suspect CWM sites may still have chemical agent contamination present. On these sites the Contractor must determine the probability of the worker exposure to chemical agent to make a recommendation as to whether agent monitoring and/or onsite medical support is necessary. If the Contractor is tasked to perform the chemical agent monitoring, they must recommend the type of monitoring to be performed, the instrument(s) to be used.

6. End of DID HNC-002

HNC-003.01

DATA ITEM DESCRIPTION

Title: Geophysics

Number: HNC-003.01 Approval Date: 20150313 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 classification sensors in both dynamic and cued mode where appropriate as approved by the PDT, utilizing personnel with previous advanced classification experience. Currently, advanced classification sensors include TEMTADS, MetalMapper, and MPV, all of which are multi-axis, multi-coil electromagnetic induction (EMI) sensors. New sensors may be developed, but must share several characteristics with these advanced EMI sensors, including a detailed, written description of the sensing modality and analysis approach, ability to predict in advance the signals and characteristics expected from the expected munitions items, and demonstrated performance on a test site or previous project. The Geophysical Classification for Munitions Response Quality Assurance Project Plan (GCMR-QAPP) template produced by the Intergovernmental Data Quality Task Force (IDQTF), current version, shall be utilized for project planning and documentation. Any changes to the black text of the GCMR-QAPP template must be explained and justified.

8.0 End of DID HNC-003.01.

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

DATA ITEM DESCRIPTION

Title: Hydrography

Number: HNC-004 Approval Date: 20140718 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, 2012) 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.

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

DATA ITEM DESCRIPTION

Title: Munitions Constituents Chemical Data Quality Deliverables

Number: HNC-005.01 Approval Date: 20150211 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

IG 14-01 (EM 200-1-15) Technical Guidance for Military Munitions Response Actions

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…