Manual_for_Electronic_Deliverables_2011_Final.pdf

Prepared By:

U.S. Army Corps of Engineers - Alaska District

Environmental Engineering Branch P.O. Box 6898

Joint Base Elmendorf Richardson, Alaska 99506-0898

Manual for Electronic Deliverables

Requirements for Submittals of Documents, Laboratory Data, and Other Items

October 2011

F10AKxxxxxx_yy.yy_zzzz_a

200-1e

Manual for Electronic Deliverables 2 October 2011

PAGE INTENTIONALLY BLANK

Manual for Electronic Deliverables 3 October 2011

TABLE OF CONTENTS

1. INTRODUCTION

2. TEXT AND TABLES

3. PHOTOGRAPHS, IMAGES, AUDIO, AND VIDEO

4. GEOSPATIAL INFORMATION

4.1 OVERVIEW

4.2 RESOURCES

5. SURVEY

5.1 SURVEY PLANNING

5.2 FEATURES TO BE SURVEYED

5.3 SPATIAL REFERENCE

5.4 SURVEY QUALITY

5.4.1 Documenting Quality

5.5 NEW MONUMENTS

5.6 SURVEY DELIVERABLES

5.6.1 Survey Data Table

6. GIS

6.1 GIS PLANNING

6.2 GEOSPATIAL DATA DELIVERABLES

6.2.1 External Hard Drives

6.2.2 Vector Data

6.2.3 Chemistry Data for GIS

6.2.4 Raster Data

6.2.5 Metadata

6.3 MAPS, FIGURES, AND DRAWINGS

7. CHEMICAL DATA

8. DELIVERY / CD-ROM PRODUCTION GUIDELINE / MEDIA FORMAT

8.1 ORGANIZATION

8.2 SUPPLEMENTAL DATA

8.3 LABEL STANDARDS

8.4 FUDS SPECIFIC DELIVERABLE LABEL STANDARDS

9. MINIMUM *.PDF REQUIREMENTS

9.1 PDF STANDARDS

9.2 DOCUMENT PROPERTIES

9.2.1 Description

9.2.2 Security

9.2.3 Initial View

9.3 SCANNING STANDARDS

Manual for Electronic Deliverables 4 October 2011

10. FUDS SPECIFIC - *.PDF REQUIREMENTS

10.1 FUDS SPECIFIC PDF STANDARDS

10.2 DOCUMENT PROPERTIES

10.2.1 Description

10.2.2 Security

10.3 FILE NAMING CONVENTION

11. MED SUBMITTAL CHECKLIST

12. ATTACHMENTS

13. SUPPLEMENTAL INFORMATION

Manual for Electronic Deliverables 5 October 2011

Acronyms and Abbreviations

ACE-IT Army Corps of Engineers Information Technology AE Architect-Engineer ARIMS Army Records Information Management System CADD computer aided design and drafting CD compact disk CON/HTRW containerized hazardous, toxic, or radioactive waste COR Contracting Officers Representative CORS continuously operating reference station DEM digital elevation model DVD digital video disk EM Engineering Manual FRMD FUDS Records Management Database FUDS Formerly Used Defense Site GCS geographic coordinate system GIS geographic information system GPS global positioning system HTRW hazardous, toxic, or radioactive waste IIS Interagency and International Services IRA interim removal action MED Manual for Electronic Deliverables NAVD88 North American Vertical Datum of 1988 ND not detected NGS National Geodetic Survey NOAA National Oceanic and Atmospheric Administration NPDL North Pacific Division Laboratory OPUS Online Positioning User Service PARVQ parameter value qualifier PDOP position dilution of precision PDF portable document format PID photoionization detector RA removal action RI remedial investigation RTK real time kinematic SDSFIE Spatial Data Standards for Facilities Infrastructure and Environment SI site investigation TIN triangulation irregular network SOW scope of work USACE U.S. Army Corps of Engineers UTM Universal Transverse Mercator UVOST Ultraviolet Optical Screening Tool VVL Valid Value WGS84 World Geodetic System (dating 1984)

Manual for Electronic Deliverables 6 October 2011

1. INTRODUCTION

Alaska District Corps of Engineers Manual of Electronic Delivery (MED) standards is provided to aid Alaska District staff, contractors, and architect-engineer (AE) firms in preparing submittals for the environmental program.

The preferred method of submitting electronic deliverables to the Alaska District (environmental program) is on CD-ROM with a specified directory structure. The draft electronic submittal should contain at a minimum the entire document as an Adobe Portable Document Format (PDF) document and sufficient native files to review the contents of the report (photos, chemistry, survey, figures…). The final electronic submittal should contain at a minimum the following formats: The entire document as a PDF, AND an easily editable version of all the documents components e.g. Microsoft Word, Excel, Access, Autodesk, etc. formats.

Throughout this manual, standards for software are provided by brand name only. All electronic deliverables will be provided in the software version in which the Alaska District has adopted as their own internal standard. Thus, it is imperative that prior to delivery of any electronic deliverable, contractors and architect-engineer firms contact the project manager to determine the current standards being implemented throughout the Alaska District.

All requirements of the MED apply unless otherwise specified in the contract, scope of work (SOW) or task order.

Manual for Electronic Deliverables 7 October 2011

2. TEXT AND TABLES

Text submitted by contractors and AE firms to the Alaska District environmental branch shall be provided in two formats (unless otherwise specified in the SOW or Contract):

• Native file(s) - Microsoft Word, Excel, Publisher, etc…

• Adobe Portable Document Format (PDF)

All Excel tables shall include the equations and inputs that are required to generate the tables.

The minimum PDF standards apply to both draft and final documents. However, Final documents (i.e., the last document that is not intended to be altered or undone) prepared for the Formerly Used Defense Site (FUDS) Program have additional formatting requirements (see Section 10).

Deliverables may also be requested with hyperlinks wherein; text, figures, photos, etc. are linked to one another within the document. This interactive file may be provided as a bookmarked PDF document.

Manual for Electronic Deliverables 8 October 2011

3. PHOTOGRAPHS, IMAGES, AUDIO, AND VIDEO

All photographs taken during the execution of a project shall be provided electronically in one of the following formats:

• Tagged Image File Format (TIFF) or

• JPG

All photos taken during the execution of the project shall be labeled and/or indexed. A photographic log/index shall also be supplied; it shall identify the date, direction and contents of the photo. All photographs shall be provided electronically as Supplemental Data. The Contractor may also wish to incorporate specific photographs into the text of the report or included as a photo log in an appendix.

All digital audio and video files supplied by contractors and AE firms to the Alaska District environmental program will be provided in a Windows Media Video (*.wmv) compatible format.

Manual for Electronic Deliverables 9 October 2011

4. GEOSPATIAL INFORMATION

4.1 OVERVIEW

Survey and geospatial data management play an important role in life-cycle project completion, based on the nature of environmental cleanup work, especially in Alaska. Because of the inherent logistical difficulties of conducting environmental investigation and remediation work in Alaska, each field data collection point carries significant cost. Project phases may extend through multiple years, and even multiple decades. In most cases, data collection locations are revisited during later project work. The cost ramifications of using the data in decision-making for follow-on environmental cleanup efforts are even higher.

The objective of defining standard geospatial data requirements is to move toward a consistent basis to enable long-term viability of geospatial data; thereby reducing costs and supporting the successful completion of environmental projects. The intent is to establish requirements that impart an appropriate level of stringency to meet the big-picture needs of environmental projects in Alaska.

Geospatial data management plays an important role in support of a sizeable multi-disciplinary team of people with a common goal of a successful project. That team may include numerous stakeholders with varying interests, multiple levels of subcontractors, and it may change extensively throughout the stages of an environmental project. The use of geographic information system (GIS) technology enhances project execution by improving communication and data management/evaluation. Primary data collection is a critically important component of project needs and the continuing utilization of professional skills in GIS application is highly encouraged.

4.2 RESOURCES

A compiled list of helpful information includes:

• EM1110-1-1002 Survey Markers and Monumentation (http://140.194.76.129/publications/eng-manuals/em1110-1-1002/toc.htm)

• EM1110-1-1005 Control and Topographic Surveying (http://140.194.76.129/publications/eng-manuals/em1110-1-1005/toc.htm)

• Reference to NOAA Online Positioning User Service (OPUS) http://www.ngs.noaa.gov/OPUS/

• SDSFIE Version 2.6 blank geodatabase shell; http://www.sdsfie.org/

• SDSFIE Version 3.0 blank geodatabase shell; http://www.sdsfie.org/

Note that the geodatabase shells are not intended to limit the geospatial data generated during project work. We encourage data acquisition when the opportunity presents itself, especially with the high costs of conducting remote work in Alaska. If data is generated that is not represented in the geodatabase shell, the Contractor should contact the Project Manager to determine an appropriate format to convey the data.

http://140.194.76.129/publications/eng-manuals/em1110-1-1002/toc.htm� http://140.194.76.129/publications/eng-manuals/em1110-1-1005/toc.htm� http://www.ngs.noaa.gov/OPUS/� http://www.sdsfie.org/�

Manual for Electronic Deliverables 10 October 2011

General questions related to surveying may be directed to CEPOA-EN-GES-SY Section via the Project Manager. General questions related to GIS may be directed to CEPOA-EN-GES-TI Section via the Project Manager.

Manual for Electronic Deliverables 11 October 2011

5. SURVEY

5.1 SURVEY PLANNING

The Contractor shall determine the availability of existing survey control monuments at or near the site during the project planning phase, evaluate the usefulness of this control for meeting the accuracy requirements of the project, and present this information in the planning documents.

Note that some remote Alaska sites may not have existing monuments that meet the project needs. In some cases, monuments may be present that meet horizontal control requirements of the project, but may not have vertical control referenced to North American Vertical Datum of 1988 (NAVD88). An OPUS Solution may need to be obtained at some sites, even where monuments exist.

The Contractor shall determine the survey method(s) to be used to meet the requirements of the contract. The intended survey method(s) and approach shall be described in the Contractors planning documents, including:

• conventional survey versus global positioning system (GPS) survey;

• type, brand, and model of major equipment;

• accuracy capabilities of the equipment as published by the manufacturer;

• monuments available at or near project site, including information about the monuments and their intended use on the project;

• new monuments to be established, if needed;

• collection of tracklog data;

• differential correction approach (real-time, post-process); and

• intended approach for documenting accuracy of surveyed locations.

5.2 FEATURES TO BE SURVEYED

The following features shall be surveyed unless otherwise indicated in the contract or task order:

• soil borings;

• monitoring wells;

• ultra-violet optical screening tool (UVOST) probes;

• investigative field screening locations (excluding PID screening of stockpiles and soil segregation during soil removal);

• sample locations;

• excavation boundaries;

• remediation system components;

• existing monuments found at a project site; and

• new monuments set at a project site.

Other site features that may be visible on aerial photographs and used to georeference aerial photography for use in GIS applications shall be surveyed. These features may include:

• building corners;

• concrete slab corners;

• roads and road intersections;

Manual for Electronic Deliverables 12 October 2011

• trails;

• airstrips;

• antennas;

• berms;

• topographic tops or sharp breaks in slope;

• coastlines, preferably upper beach line;

• locations of distinct surface color or shading; and

• streams, preferably tributary intersections or sharp direction changes.

Tracklog data shall be collected for projects involving reconnaissance-type work. For example, tracklog data shall be recorded for site investigation and remedial investigation efforts involving observation and documentation of site features over a wide area; the tracklog helps document the locations visited and depicts coverage of the effort. Conversely, tracklog data is not required for remedial investigation efforts involving survey and sampling of groundwater monitoring wells, because it is not necessary to document the daily movement of a worker within the limited source area.

5.3 SPATIAL REFERENCE

Survey data shall be provided using the spatial references in Table 5-1 unless otherwise directed by USACE.

TABLE 5-1. SPATIAL REFERENCE

Program Horizontal Datum and Coordinate

System Vertical Datum

Formerly Used Defense Site (FUDS) Projects

GCS WGS 1984 latitude/longitude in decimal degrees

NAVD88 in feet

IIS Projects GCS WGS 1984 latitude/longitude in decimal degrees

NAVD88 in feet

U.S. Air Force Projects WGS84, UTM (applicable zone), in meters

NAVD88 in meters

U.S. Army Projects WGS84, UTM (applicable zone), in meters

NAVD88 in meters

5.4 SURVEY QUALITY

Survey quality shall meet the minimum requirements in Table 5-2 below. Alternative requirements that supersede these requirements may be indicated in the contract or task order.

Manual for Electronic Deliverables 13 October 2011

TABLE 5-2. SURVEY QUALITY

Feature Type Minimum Horizontal

Quality Minimum Vertical

Quality

General Field Data Collection Photograph Location 9.8 feet / 3 meters (standing location); if specifically required in the scope of work

No elevation data required

Features intended for georeferencing imagery

3.3 feet / 1 meter

– e.g.

building corners, antenna, intersections

No elevation data required

Monument Location Found Equal to most stringent accuracy for features surveyed during project. Verify published accuracy of monument meets project needs during project planning.

monument used to evaluate survey accuracy; tie in elevation survey; comparison to published data

Equal to most stringent accuracy for features surveyed during project. Verify published accuracy of monument meets project needs during project planning.

Monument Location New Equal to most stringent accuracy for features surveyed during project. (OPUS Solution may be necessary.)

project monument installed by Contractor (non-published)

Equal to most stringent accuracy for features surveyed during project. (OPUS Solution may be necessary.)

Monument Location New As required by EM 1110-1-

1002 / EM 1110-1-1005

project monument installed by Contractor (published)

As required by EM 1110-1-

1002 / EM 1110-1-1005

Features Not Listed in this table

Establish agreement on approach during negotiation and/or project planning.

Establish agreement on approach during negotiation and/or project planning.

SI Level Field Data Collection Photograph Location 9.8 feet / 3 meters (standing location)

No elevation data required

Sample Location 3.3 feet / 1 meter (SI) – surface soil, subsurface soil, sediment, surface water

No elevation data required

Field Screening Location 3.3 feet / 1 meter (SI)

– e.g. PID

No elevation data required

CON/HTRW Items 3.3 feet / 1 meter – e.g.

transformer, drum, battery etc.

No elevation data required

HTRW feature 3.3 feet / 1 meter – e.g. soil stain No elevation data required Debris Item 3.3 feet / 1 meter, or as needed to find item upon return

– No elevation data required

Debris Pile or Area 3.3 feet / 1 meter with multiple items (4 corners or surrounding polyline)

No elevation data required

Manual for Electronic Deliverables 14 October 2011

TABLE 5-2. SURVEY QUALITY

Feature Type Minimum Horizontal

Quality Minimum Vertical

RI Level Field Data Collection Soil Boring Location 3.3 feet / 1 meter (RI) – auger drilled, hand auger, UVOST probe, ground surface level

0.5 foot / 0.15 meter

Test Pit 3.3 feet / 1 meter (RI) – center, ground surface level

0.5 foot / 0.15 meter

Sample Location 3.3 feet / 1 meter (RI) – surface soil, sediment, ground surface level, subsurface soil

0.5 foot / 0.15 meter

Groundwater Sampling Location

3.3 feet / 1 meter (RI) – monitoring well, microwell, temporary push-point, ground surface and top of casing levels

Close level loop at 0.01 foot per setup or better. Tie elevation survey to existing or new monument.

Field Screening Location 3.3 feet / 1 meter (RI)

– e.g. PID, immunoassay…

No elevation data required

Confirmation Sample (RI) 3.3 feet / 1 meter – e.g. soil sample establishing completion

0.5 foot / 0.15 meter

IRA and RA Level Field Data Collection Confirmation Sample (IRA, RA)

3.3 feet / 1 meter

– e.g. soil sample from excavation establishing completion

0.5 foot / 0.15 meter

Field Screening Location 3.3 feet / 1 meter (IRA, RA) – e.g. PID, PetroFlag, UVOST, etc.

No elevation data required

Remediation System Component

3.3 feet / 1 meter (RA) – e.g. SVE enclosure corner

No elevation data required

Excavation Limits 3.3 feet / 1 meter (IRA, RA)

– for contracts with measurement and payment using tonnage

0.5 foot / 0.15 meter

Excavation Limits Per contract (IRA, RA)

– for contracts with measurement and payment using excavation volume

Per contract

Manual for Electronic Deliverables 15 October 2011

5.4.1 Documenting Quality

As part of the survey deliverable, the Contractor shall provide documentation of the survey quality achieved, and shall provide an explanation of the method used to evaluate quality.

Survey data shall tie to the National Spatial Reference System (NSRS) by one of various methods, potentially including real time kinematic (RTK) navigation, post-processing for differential correction using continuously operating reference station (CORS) reference data, or OPUS resources.

5.5 NEW MONUMENTS

Where a published survey monument is not available at or near the site, the Contractor shall establish a new monument for use on the project. This applies to RI, IRA, and RA project phases. This does not apply to brief site visits and SI phase sampling work. All information needed to publish the new monument with the National Geodetic Survey (NGS) OPUS shall be obtained and provided to USACE. The NGS website is at: http://www.ngs.noaa.gov/

5.6 SURVEY DELIVERABLES

Survey data shall be delivered under the Supplemental Data folder of the deliverable package.

Deliverables shall include the following at a minimum:

• single survey data table;

• survey field notes, sketches, computations, and recordings in .pdf file format;

• raw survey data files in the native file format of the equipment used (including tracklogs);

• documentation of PDOP (position dilution of precision) and number of acquired satellites during survey; and

• differentially corrected GPS data files (including all fields) in the native file format of the

GPS used (including tracklog files).

5.6.1 Survey Data Table

Electronic survey data shall be provided in a single Microsoft Excel spreadsheet or comma-delimited text format file containing the following information.

Column A Location_ID Column B Northing coordinate (Y) Column C Easting coordinate (X) Column D Elevation coordinate (Z) Column E Text descriptor of the survey point Column F Date and time measurement taken

In addition to the file described above, the table of survey data shall be provided in .pdf format.

The .pdf file shall also contain the following information:

http://www.ngs.noaa.gov/�

Manual for Electronic Deliverables 16 October 2011

• survey dates/times;

• survey method (e.g. GPS, total station);

• survey equipment used;

• spatial reference (datum, coordinate system, and units) applicable to the survey data provided in the table; and

• descriptive summary of the Contractor's evaluation of survey quality and its comparison to contract requirements.

Manual for Electronic Deliverables 17 October 2011

6. GIS

6.1 GIS PLANNING

The Contractor shall plan for meeting GIS deliverable requirements and include this topic in their planning documents. The planning documents shall include information such as:

• software to be used to prepare GIS deliverables and maps/figures/drawings;

• spatial data file types to be delivered (feature classes, shapefiles, spreadsheets);

• datasets anticipated to be produced and delivered on the project;

• description of raster data available for project use, and additional raster data needs; and

• anticipated method of delivery (CD, DVD, external hard drive).

6.2 GEOSPATIAL DATA DELIVERABLES

If the Contractor has questions or concerns related to the GIS deliverable requirements of the contract or task order, they should contact the project manager at USACE and request a consultation with USACE GIS representatives.

All GIS data developed during the execution of the project shall be delivered under the Supplemental Data folder of the deliverable package. Geospatial data deliverables shall be compatible for use with ESRI ArcGIS Version 9.3.1 or Version 10 software. The contractor may provide geospatial data as a map package using ArcGIS v.10 *.mpk file type if ArcGIS v.10 is used for the project. The Contractor shall provide geospatial vector data for the features surveyed on the project. The Contractor shall also provide raster data used in the development of project planning and reporting documents.

6.2.1 External Hard Drives

Many times GIS deliverables exceed the capacity of a single DVD disk. In these cases, the Contractor shall provide the GIS deliverable on an external hard drive that is acceptable for use on USACE computers. Contact the Project Manager for consultation with the USACE IT organization (ACE-IT) to determine acceptable brands and models of external hard drives. The external hard drive will serve as a transfer medium between USACE and the Contractor during the life of the project. The Contractor may wish to include the cost of the external hard drive in their price proposal; in which case the hard drive will become the property of the Government at the end of the project.

6.2.2 Vector Data

Vector data shall be delivered in geodatabase format compliant with the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Version 2.6 or Version 3.0 Gold.

Chemistry data is exempted from SDSFIE format. See Section titled Chemistry Data for GIS.

The SDSFIE Version 2.6 and Version 3.0 Gold blank geodatabases are available for download at the SDSFIE website (http://www.sdsfie.org/). The user will need to register and login to the

Manual for Electronic Deliverables 18 October 2011

SDSFIE website to access Version 3.0 information. The SDSFIE Browsing and SDSFIE Validation tools are helpful in using the geodatabases.

Table 6-1 indicates expected vector data deliverables for different types of projects. Table 6-2 indicates expected fields to be populated. These tables reflect the use of SDSFIE Version 3.0 Gold. If the Contractor chooses to submit data in SDSFIE Version 2.6 format, comparable feature classes and fields should be selected by the Contractor, and a cross-walk table shall be provided with the deliverable to communicate proper field mapping for loading to the Alaska District enterprise geodatabase in SDSFIE Version 3.0.

Note that not all feature classes and fields appropriate for a project are necessarily listed in Tables 6-1 and 6-2; these tables provide an example of data commonly generated during environmental investigation and cleanup projects. Each project is different, and USACE expects the GIS expertise of the Contractor to be a service inherent in the contracted work. The Contractor shall evaluate the types of data to be collected under their particular scope of work, and determine which feature classes and fields are appropriate to hold and manage the data.

Exception to SDSFIE Requirement

: Shapefiles and Microsoft Excel spreadsheets will be accepted in lieu of geodatabase feature classes, so long as the file carries the appropriate spatial reference information, and spreadsheets are readily importable to GIS software with no re-formatting. For example, merged cells in a spreadsheet are not readily importable. The Contractor shall also provide a cross-walk table for correlation of field names between the spreadsheet and SDSFIE Version 3.0.

TABLE 6-1. VECTOR DATA DELIVERABLES (SDSFIE Version 3.0 Gold) Project Type Vector Data Feature Classes

Environmental Investigation Typical environmental investigation project involving sample collection and analysis, soil borings, monitoring wells and groundwater sampling, and plume delineation.

: Required: Borehole, EnvironmentalSampleLocation, Well, ControlMonumentPoint, PollutionArea Possible (as applicable):

AboveGroundStorageTank, UndergroundStorageTank, POLUtilitySegment, PotentialEnvHazardSourcePoint, PotentialEnvironmentalSite, WastewaterUtilityNode, GeneralContour (plume), GeneralContour (groundwater), etc.

Environmental Soil Removal Action Typical removal of contaminated soil involving excavation and disposal.

Confirmation sampling in excavation.

: Required: SurveyPoint, GeneralContour (excavation), EnvironmentalSampleLocation, ControlMonumentPoint

Project Planning Project planning efforts involving determination of features related to transportation and logistics.

: Possible: Building, Fence, Well, Tower, WaterFeature (streams, rivers, lakes), Wetland, TransportationRoute (roads), Bridge, Shoreline, ControlMonumentPoint, CulturalRestrictedAccess

Manual for Electronic Deliverables 19 October 2011

TABLE 6-2. REQUIRED FIELDS (SDSFIE Version 3.0 Gold) Subject of Feature Geometry Feature Class Minimum Required Fields

ADMINISTRATIVE

FUDS property boundary polygon DodFormerlyUsedDefense dodFormerlyUsedDefenseIDPK, sdsFeatureName, sdsMetadataID environmental site polygon EnvironmentalRemediationSite envRemediationSiteIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID metadata SDSFIEMetadata sdsMetadataID

GENERAL SITE FEATURES

building location polygon Building buildingIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID fence polyline Fence fenceIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID drinking water well point Well wellPointIDPK, sdsFeatureName, sdsFeatureDescription, wellPurpose, wellResource, sdsMetadataID tower or antennae point Tower towerIDPK, sdsFeatureName, sdsFeatureDescription, towerCondition, towerMaterial, sdsMetadataID

POSSIBLE CONTAMINATION SOURCES

aboveground storage tank point AboveGroundStorageTank aboveGroundStorageTankIDPK, sdsFeatureName, sdsFeatureDescription, storageTankProduct, volume, volumeUoM, sdsMetadataID underground storage tank point UnderGroundStorageTank underGroundStorageTankIDPK, sdsFeatureName, sdsFeatureDescription, storageTankProduct, volume, volumeUoM, sdsMetadataID fuel distribution pipe polyline POLUtilitySegment pOLUtilitySegmentIDPK, sdsFeatureName, sdsFeatureDescription, operationalStatus, sdsMetadataID

Manual for Electronic Deliverables 20 October 2011

Subject of Feature Geometry Feature Class Minimum Required Fields contamination release point point PotentialEnvHazardSourcePoint potentialEnvHazardSourceIDPK , sdsFeatureName, sdsFeatureDescription, sdsMetadataID potential contamination site point or polygon

PotentialEnvironmentalSite potentialEnvironmentalSiteIDPK , sdsFeatureName, sdsFeatureDescription, sdsMetadataID wastewater discharge point WastewaterUtilityNode wastewaterUtilityNodeIDPK, sdsFeatureName, sdsFeatureDescription, networkSubType, operationalStatus, wastewaterNodeType, sdsMetadataID

SITE INVESTIGATION

soil boring point Borehole boreholeIDPK, sdsFeatureName, sdsFeatureDescription, boreholeComments, boreholeType, boringMethod, drillingCompDate, groundSurfaceElevation, horizontalAccuracy, startDate, totalDepth, verticalAccuracy, sdsMetadataID

UVOST probe point Borehole boreholeIDPK, sdsFeatureName, sdsFeatureDescription, boreholeComments, boreholeType, boringMethod, drillingCompDate, groundSurfaceElevation, horizontalAccuracy, startDate, totalDepth, verticalAccuracy, sdsMetadataID piezometer for water level measurement point PiezometerLocation piezometerLocationIDPK, sdsFeatureName, sdsFeatureDescription, horizontalAccuracy, installationDate, piezometerComments, topElevation, tubetipElevation, verticalAccuracy, Manual for Electronic Deliverables 21 October 2011

Subject of Feature Geometry Feature Class Minimum Required Fields sample location -environmental (includes soil, surfacewater, sediment) point EnvironmentalSampleLocation environmentalSampleIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID drinking water sample location from well point Well wellPointIDPK, sdsFeatureName, sdsFeatureDescription, wellPurpose, wellResource, sdsMetadataID monitoring well used for sample collection point Well wellPointIDPK, sdsFeatureName, sdsFeatureDescription, wellPurpose, wellResource, sdsMetadataID

CONTAMINATION PLUMES

contamination plume concentration line polyline GeneralContour generalContourIDPK, sdsFeatureName, sdsFeatureDescription, genContourType, value, valueUOM, sdsMetadataID contamination plume area polygon PollutionArea pollutAreaIDPK, sdsFeatureName, sdsFeatureDescription, contaminantType, matrixType, sdsMetadataID

HYDROLOGY

groundwater contour line polyline GeneralContour generalContourIDPK, sdsFeatureName, sdsFeatureDescription, genContourType, value, valueUOM, sdsMetadataID historic river alignment polyline HistoricRiverAlignment historicRiverAlignmentIDPK, sdsFeatureName, sdsFeatureDescription, alignmentYear, sdsMetadataID shoreline polyline Shoreline shorelineIDPK, sdsFeatureName, sdsFeatureDescription, bankType, collectionDate, shorelineType, sdsMetadataID

Manual for Electronic Deliverables 22 October 2011

Subject of Feature Geometry Feature Class Minimum Required Fields surface water body polygon WaterFeature waterFeatureIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID wetland polygon or polyline

Wetland wetlandIDPK, sdsFeatureName, sdsFeatureDescription, cowardin, hydrogomorphology, jurisdictionalFeature, localName, wetlandArea (polygon), wetlandLength (polyline), sdsMetadataID

LOGISTICS / TRANSPORTATION

road polyline TransportationRoute transportationRouteIDPK, sdsFeatureName, sdsFeatureDescription, sdsMetadataID bridge polyline Bridge bridgeIDPK, sdsFeatureName, sdsFeatureDescription, bridgeType, sdsMetadataID survey control monument point ControlMonumentPoint controlMonumentPointIDPK, sdsFeatureName, sdsFeatureDescription, collectionHorizontalDatum, collectionVerticalDatum, controlMonumentPointType, xLocation, xLocationUOM, yLocation, yLocationOUM, zLocation, zLocationUOM, sdsMetadataID probable cultural area polygon CulturalResourcePotentialArea cultResourcePotentialAreaIDPK, sdsFeatureName, sdsFeatureDescription, potentialType, sdsMetadataID restricted cultural area polygon CulturalRestrictedAccess culturalRestrictedAccessIDPK, sdsFeatureName, sdsFeatureDescription, restrictionDescription, sdsMetadataID cultural survey site

Polygon CulturalSurveyArea culturalSurveyAreaIDPK, sdsFeatureName, sdsFeatureDescription, Manual for Electronic Deliverables 23 October 2011

Subject of Feature Geometry Feature Class Minimum Required Fields

REMEDIAL ACTION / REMOVAL ACTION

survey point location point SurveyPoint surveyPointIDPK, sdsFeatureName, sdsFeatureDescription, elevationUOM, sourceType, surveyPointElev, xLocation, xLocationUOM, yLocation, yLocationOUM, zLocation, zLocationUOM, sdsMetadataID excavation contour polyline GeneralContour generalContourIDPK, sdsFeatureName, sdsFeatureDescription, genContourType, value, valueUOM, sdsMetadataID

MUNITIONS OF EXPLOSIVE CONCERN

munitions disposal area polygon MunitionWasteDisposal munitionWasteDisposalIDPK, sdsFeatureName, sdsFeatureDescription, pitType, sdsMetadataID historic impact area / range polygon MilitaryRange militaryRangeIDPK, sdsFeatureName, sdsFeatureDescription, operationalStatus,

6.2.3 Chemistry Data for GIS (different than requirements set forth in MED Section

7 CHEMICAL DATA)

On projects involving sample collection and laboratory analysis, a separate chemistry data deliverable shall be provided for GIS applications in addition to the chemistry deliverables required elsewhere in the contract. Table 6-3 describes the chemistry data deliverable for GIS, to be provided under a feature class titled: “poaChemistryData”. This deliverable may also be in shapefile or Microsoft Excel spreadsheet format. If shapefile format is used, field names are limited to 10 characters; therefore provide a cross-walk table to communicate field name conversions. Valid values (VVL) to be used in the chemistry data table for GIS are listed in the POA Instructional Set - “POA_IS3_2011.xlsx”. If additional VVLs are needed for a project, the Contractor shall coordinate these with USACE.

Manual for Electronic Deliverables 24 October 2011

TABLE 6-3. CHEMISTRY DATA FOR GIS

Description Field Name Example - Soil Sample from Soil Boring

Example - Groundwater Sample from

Monitoring Well

Example – SI Surface Soil Sample

Field Sample Identification – (Primary Key) Unique identifier for sample.

ClientSampleID 11UMTB205SL 11UMTMW201GW 11UMT243SL

Location Identification – Field surface soil sample ID, soil boring ID, test pit ID, or monitoring well ID.

This information will be consistent with field notes and consistent with information in the survey data table.

LocationID AP-1 MW-2 243SL

Northing coordinate / latitude y_coord 63.0693931 63.0693931 6994881.9

Easting coordinate / longitude x_coord -151.0074172 -151.0074172 600675.9

Unit applicable to x and y coordinates coord_unit (see VVL table) dec_degree dec_degree meter

Horizontal Coordinate System coord_sys (see VVL table)

GCS_WGS_1984 GCS_WGS_1984 UTM_zone_5N

Horizontal Datum datum_H WGS_1984 WGS_1984 WGS_1984

Manual for Electronic Deliverables 25 October 2011

Description Field Name Example - Soil

Sample from Soil Boring

Example - Groundwater Sample from

Monitoring Well

Example – SI Surface Soil Sample

(see VVL table)

Horizontal Survey Method surv_met_H (see VVL table)

GPS GPS conventional

Horizontal Survey Quality surv_qlty_H sub 3.3 feet sub 3.3 feet sub 1 meter

Elevation of Ground Surface spotElev 20320.5 20320.5 6193.5

Elevation of Top of Casing tocElev 20320.73

Elevation of Sample

For split spoon, use top of sample interval.

For water sample, use pump intake elevation or groundwater table as applicable.

sampElev 20315.5 20310.5 6193.5

Unit applicable to elevation elev_UOM (see VVL table) foot foot meter

Vertical Datum datum_V(see VVL table) NAVD88 NAVD88 NAVD88

Vertical Survey Method surv_met_V (see VVL table) level loop level loop GPS

Vertical Survey surv_qlty_V 0.5 foot 0.01 foot 0.5 foot

Manual for Electronic Deliverables 26 October 2011

Description Field Name Example - Soil

Sample from Soil Boring

Example - Groundwater Sample from

Monitoring Well

Example – SI Surface Soil Sample

Project Name - Contact the USACE Project Manager to obtain this information.

projname 2012 AnywhereAK

HTRW

2012 AnywhereAK

HTRW

2012 AnywhereAK

HTRW

Project Number - Contact the USACE Project Manager to obtain this information. For FUDS projects, this will be the FUDS Property Number & Project Number.

projnum F10AKxxxxyy F10AK999902 F10AK999902

Project Location projloc Anywhere, AK Anywhere, AK Anywhere, AK NPDL Work Order Number

ProjectID 12-zzz 12-zzz 12-zzz

Laboratory Sample Identification

LabSampleID 1094199026 1094199026 1094199026

Sample Collection Date and Time

CollectedDate 8/6/2009 14:30 8/6/2009 14:30 8/6/2009 14:30

Analytical Method SamplePlusMethod.ClientMethodID (see VVL table)

SW8270D SW8270D SW8270D

Matrix MatrixID (see VVL table)

Soil Soil Soil

Extraction Method PreparationPlusCleanup.ClientMethodID (see VVL table)

3550C 3550C 3550C

Basis ReportedResult.ResultBasis (see VVL table)

Dry Total Dry

Analyte ReportedResult.ClientAnalyteID (see VVL table)

4-Nitroaniline 4-Nitroaniline 4-Nitroaniline

Result (significant figures match result

ReportedResult.Result

Manual for Electronic Deliverables 27 October 2011

Description Field Name Example - Soil

Sample from Soil Boring

Example - Groundwater Sample from

Monitoring Well

Example – SI Surface Soil Sample reported by laboratory) Result Type ReportedResult.ResultType

(see VVL table) Not_Detected Not_Detected Not_Detected

Laboratory Notes LabQualifiers Limit of Quantitation QuantitiatonLimit (LOQ) (LOQ) (LOQ) Limit of Detection ReportingLimit (LOD) (LOD) (LOD) Detection Limit DetectionLimit (DL) (DL) (DL) Units (consistency between "result", "LOD", and "LOQ")

ResultUnits (see VVL table) mg/kg mg/L mg/kg

Laboratory LabName (see VVL table)

Validator Qualifiers valid_qual (see VVL table)

Validator Remarks valid_remk Qualification of result is based on elevated DL.

VVL – Valid Value VVLs are contained within POA_IS3_2011.xlsx

Manual for Electronic Deliverables 28 October 2011

6.2.4 Raster Data

Raster data deliverables commonly used on environmental projects include:

• imagery (aerial photography and satellite imagery) used in the project planning, analysis, and report preparation efforts;

• TINs (triangulation irregular network), DEMs (digital elevation models), Terrain files; and

• historical scanned map images and other scanned documents used in the effort.

Raster data shall be delivered in a logically structured raster catalog. Raster data may be delivered outside the geodatabase. If raster data is loaded into the geodatabase deliverable, then new raster data acquired during the project, and raster data from sources other than the Alaska District, shall also be delivered in a catalog outside the geodatabase. The purpose of this requirement is to make it readily apparent when new imagery is received that we will want to enter into our enterprise raster catalog. The catalog structure should separate files between raster types, such as "Maps" versus "Aerial Photographs". All raster files used in the preparation of project deliverables shall be provided.

6.2.5 Metadata

Table 6-5 describes metadata deliverable requirements.

TABLE 6-5. METADATA REQUIREMENTS

Geospatial Data File Type Metadata Requirement

Vector Data generated by the Contractor on the project -

Provide metadata compliant with Federal Geographic Data Committee (FGDC) standards.

feature classes and shapefiles

Spreadsheet of vector data Provide a written description of the dataset, including elements required in FGDC metadata. This will enable USACE to generate metadata when the dataset is uploaded to the USACE enterprise geodatabase.

Feature Dataset No metadata required.

Geodatabase Provide general metadata related to the geodatabase as a whole, such as the name of the project, general location, time frame when the geodatabase was developed, intended uses of the geodatabase, etc.

ESRI ArcGIS .mxd file used to develop a deliverable map/figure

No metadata required.

AutoCAD .dwg file used to develop a deliverable map/figure

Spatial reference must be provided in the .dwg file as a note in Model Space at a minimum.

Manual for Electronic Deliverables 29 October 2011

TABLE 6-5. METADATA REQUIREMENTS

Geospatial Data File Type Metadata Requirement

Raster file - aerial photograph or satellite image generated by others

Provide metadata supplied by the generator of the raster file(s).

Provide image date and location at a minimum. Also include pixel resolution, scale, flight line number, print number, etc. if available. If the imagery has been manipulated (e.g.

georeferenced, orthorectified) by the Contractor, then provide description of the process used and modifications made.

Raster file - scanned historical maps or other scanned documents

No metadata required.

Vector Data generated by others, such as data downloaded from Federal, State, and Local agencies and clearinghouses

Include the metadata developed by the generator of the data. At a minimum provide a reference to the source of the data, even if the source does not populate metadata.

6.3 MAPS, FIGURES, AND DRAWINGS

The terms “map”, “figure”, and “drawing” are used interchangeably in this section, indicating a graphical depiction of information used in a project deliverable. The Contractor shall provide all maps, figures, and drawings used in project deliverables (e.g. planning documents, reports) that are developed by the Contractor in native file format, in addition to other requirements for project deliverables in .pdf format. Native format files need not include company names and logos, nor personal names, initials, or contact information.

The following formats are acceptable; please contact USACE for current version requirements:

• ESRI ArcGIS, Version 9.3.1 or 10 (*.mxd, *.mpk);

• Autodesk Civil 3D, Version 2011 and prior (*.dwg);

• Autodesk AutoCAD, Version 2011 and prior (*.dwg); and

• Bentley Microstation, Version XM and V8i (*.dgn)

When Autodesk and Bentley software are used to generate figures, the spatial reference shall be annotated in Model Space and the drawing units shall be consistent with the spatial reference units. Contact the Project Manager regarding acceptability of other software formats. All information required to use or regenerate the maps/figures shall be provided, including but not limited to spatial data, x-references, special fonts, and special pen weights/sets. All links to data files shall be functional as delivered, and shall use relative-path format. For Air Force and Army projects, Autodesk files shall also be provided in .dwf format.

CADD and GIS drawing files (e.g., *.dwg, *.dgn, *.mxd) that are used to show the positions of site-scale features shall be consistent with the survey data and shall be spatially referenced. For example, a figure showing the State of Alaska need not be spatially referenced. However, a figure showing the locations of borings, monitoring wells, and samples relative to a tank location shall be spatially referenced, and the coordinate positions of features contained in the electronic

Manual for Electronic Deliverables 30 October 2011 file shall be consistent with the positions surveyed in the field and reported in the survey deliverable. Survey data shall be included as a separate layer(s) (e.g., soil borings, monitoring wells, excavation corners, buildings, etc.) in the drawing file so that sampling locations and other features represented in the drawing can be easily verified to be consistent with the survey points.

When figures are generated that include annotation labels that are not connected with their associated points, lines, and polygons, the Contractor shall provide separate deliverable file(s) that are in a database/tabular structure that associate the features with their information (e.g. shapefile, feature class, spreadsheet with Northing/Easting fields). An example is a CADD drawing file with soil boring points and separate text labels added to the figure. When the CADD file is loaded into GIS applications, the points appear, however the associated labels of soil boring identifications are not associated with the points.

Manual for Electronic Deliverables 31 October 2011

7. CHEMICAL DATA

All chemical data generated for the project shall be supplied to the Alaska District. The following describes the minimum submittal requirements if electronic chemical data is required by the

SOW:

All chemistry data shall be supported by a Sample Summary Sheet. This document will identify all of the samples collected during the sampling event (and track the samples to the coolers that they were shipped to the laboratory in) and provide the following minimum data.

• Location ID

• Sample Depth

• Sample ID

• Date/Time collected

• Analytical methods

• Matrix

• Container Type/Volume

• QC (TB, QA, QC, MS/MSD, etc…)

• Laboratory

• SDG #

• Field preservation

• Cooler Name

• Sampler Initials

• Turn around time

The Sample Summary Sheet and chemical data tables for all samples shall be presented in an appendix in the report. The data tables shall be set up such that analytes, methods, units, and project action limits appear on the left; results and data flags appear in columns; and sample meta data appears in the headers of the columns. Sample metadata includes the following:

LocationID, ClientSampleID, Sample ID, SDG, Date Collected, and Matrix.

Results in the data tables shall be organized such that the required amount of whitespace is minimized. All results (including nondetects) shall be highlighted if they exceed the project action limits. Data flags applied during the data review shall be included in these tables, and elsewhere in the report wherever these results are referenced. Data flags shall include a flag for the situation in which a nondetect result (LOD and/or LOQ) is above the project action limit.

Data flags shall be defined in the data tables.

Electronic chemical data files shall be supplied in the COELT (Corps of Engineers Loading Tool) Electronic Deliverable Format (EDF) 1.2a and/or the Staged Electronic Data Deliverable (SEDD) Version 5.2 Stage 2A format as defined by the project. All electronic submittals shall be error free and match the hardcopy data deliverable supplied by the laboratory.

The specifics of EDF can be found here: www.edfdata.com. The EDF deliverable shall include a PDF copy of the Electronic Deliverable Consistency Checker (EDCC) 1.2a or 1.2i output. The EDCC output shall be error free.

SEDD version 5.2 Stage 2A shall be used. The specifics of SEDD can be found at the EPA web page http://www.epa.gov/fem/seddspec52.htm. The specific Document Type Definition (DTD) file that was used to generate the deliverable shall accompany each SEDD *.xml file submitted.

SEDD files shall be in compliance with the POA Instructional Set, most current version. SEDD files should pass a SEDD checker. A SEDD 5.2 Checker is available at USACE by request (907-753-2691).

http://www.edfdata.com/� http://www.epa.gov/fem/seddspec52.htm�

Manual for Electronic Deliverables 32 October 2011

A complete copy of the chemical data report must be submitted in PDF. The PDF file shall be searchable, but does not need to comply with the requirements of Sections 9 and 10 of this document. Elements included in this PDF file are specified in Appendix E of the DOD Department of Defense Quality Systems Manual (QSM). A table of contents which categorizes the laboratory data is required in the hardcopy; pdf bookmarks shall be created such that there is a logical organization/presentation of the analytical data. Data shall be organized at least by analytical method, and preferably also by laboratory batch. All required elements for third party data validation are required to be present. Note that laboratory procedures used to generate the chemistry data must also adhere to the most current version of the QSM.

All electronic chemistry submittals shall be provided under the Supplemental Data folder. Data shall be provided in subdirectories according to Sample Delivery Group (SDG), and shall not be further separated (e.g. provide EDF, SEDD, and PDF files in same directory).

Supplemental Data - Chemistry Submittal:

• EDF 1.2a

• SEDD, Version 5.2, Stage 2a

• Analytical Data Packages in PDF (laboratory forms need to be searchable, raw data does not)

• Documentation of the SEDD and/or EDF consistency check. Must be error free or as allowed by documented variances granted in writing by the USACE Project Chemist and approval by USACE Project Manager.

Manual for Electronic Deliverables 33 October 2011

8. DELIVERY / CD-ROM PRODUCTION GUIDELINE / MEDIA

FORMAT

A copy of all files and all project related information developed shall be delivered on electronic digital media for both the Draft and Final deliverables. All submittals shall be provided in both their native electronic digital format (e.g., Microsoft Word, Excel, AutoCAD, JPG, etc) and a complete Adobe PDF document, including all attachments, figures, tables, and text. Submittals shall be provided via email (for files less than ~10 MB) or provided on a CD-ROM, DVD or hard drive. Consult the Contract, USACE PM or COR for the required number of CD-ROMs or DVDs to be submitted.

8.1 ORGANIZATION

Data residing on CD-ROM, DVD or hard drive should be organized in a logical fashion. Sub directories should be used rather than placing all of the data on the root directory. The path length, including sub folder names should not exceed 75 characters. The root directory should be reserved for applications (i.e., viewers, self-extracting executable files, etc.), and the complete PDF of the deliverable. An example file organization is shown below:

TIP: Folder structure should be as simple as possible, so file names are not truncated when copying to USACE network

Manual for Electronic Deliverables 34 October 2011

NoName Airfield

Soil Project HTRW-01

F10AK999901_03.10_0500_a

200-1e

Contract: W911KB-C-11-9999

Task Order 0099

Alaska Contractors

October 2011

Draft Version 2

8.2 SUPPLEMENTAL DATA

Data submittal requirements include (but are not limited to) the following supplemental data that are critical documentation but are not required to be included within the body of the complete PDF report.

• All Photographs (including photo log)

• GIS / ACAD

• Survey

• Chemistry Data – SEDD/COELT/EDCC/Data Packages

• Waste Tracking Information (manifests, tipping receipts, etc)

• Daily QA/QC Reports

• SWPPP Modifications and Monitoring Reports

This data is required to review document submittals and as such needs to be submitted in the Draft and Final CD- ROM deliverables. Supplemental data must be presented in a user-friendly format and naming convention.

8.3 LABEL STANDARDS

The external label for each electronic digital media shall contain, at a minimum, the following information:

• The Contract Number and Delivery/Task Order Number

• The date on the document

• The date of the submittal –re-submittals shall be clearly identified

Manual for Electronic Deliverables 35 October 2011

If multiple documents are submitted on a single disk, the external label shall indicate accordingly and include, at a minimum, the following information:

• The document titles(s)

8.4 FUDS SPECIFIC DELIVERABLE LABEL STANDARDS

In addition to the above requirements the external label for each FUDS deliverable shall contain, at a minimum, the following additional information:

• The FUDS property/project name (e.g., Site Name, HTRW-01)

• The FRMD number of the submitted document(s) (e.g., F10AK999901_xx.xx_yyyy_a)

• The ARIMS number (e.g., 200-1e or 200-1f)

If multiple documents are submitted on a single disk, the external label shall…