W912DW19R0027_Technical_Exhibits_1-6,_12Sep19.pdf
PDF 2 MB Posted
- Solicitation number
- W912DW19R0027
About this file
Technical Exhibits 1-6
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PART 7
Technical Exhibits
Technical Exhibit 1 - Performance Requirements Summary
Technical Exhibit 2 - GIS Data Standards
Technical Exhibit 3 - Invasive Species Prevention Measures
Technical Exhibit 4 - Report Standards
Technical Exhibit 5 - Inadvertent Discovery
Technical Exhibit 6 – Maps, Survey Areas at HAHD, MMD
TECHNICAL EXHIBIT 1
Performance Requirements Summary (PRS)
The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.
Performance Objective Standard Performance Threshold
Method of Surveillance
PRS Milestone 1: The Contractor shall complete survey and monitoring of identified survey areas.
100% completion of objectives
1000 acres surveyed or identified as unsurveyable with COR agreement.
Periodic progress inspection: COR examination of incidental reports by email, telephone and/or informal quarterly reports.
PRS Milestone 2: The Contractor shall submit progress report(s).
100% completion of objectives
Zero deviation from the standard
100 percent inspection: Receipt by COR of reports by email.
PRS Milestone 3: The Contractor shall submit the draft and final report, final GIS geodatabase, final site forms, final photodocumentation, field notes, and project records on schedule.
100% completion of objectives
Zero deviation from the standard
100 percent inspection: Receipt by COR of draft report package / final report package materials and required documentation by the due date
The surveillance methods listed below will be used in the administration of this QASP:
100% Inspection
At the completion of all task (contract line items), performance will be evaluated by inspecting 100% of all tasks and deliverables (e.g., document review). The Government will document performance for each completed task/deliverable prior to payment, as described in PWS, paragraph 1.8.18.
Periodic Progress Inspection
At the Government’s discretion, periodic teleconferences and/or site visits may be conducted to evaluate progress toward key milestones and deliverables. These meetings will be at no additional cost to the Government. The KO or COR may call a teleconference if perceived deficiencies exist that must be addressed prior to milestone/deliverable completion. The KO or COR will assure that any such request does not create a claim by the Contractor. While corrective action or re-performance will be required if necessary, the Contractor will not be financially penalized for unacceptable performance recorded in periodic progress reports, provided that final performance evaluation of the milestone/deliverable is deemed acceptable.
TECHNICAL EXHIBIT 2
GIS Specifications
1. GPS/GIS STANDARDS FOR ARCHAEOLOGICAL FIELD INVENTORY
The Corps seeks assistance to use GPS (global positioning system) to collect cultural resource Site, Survey, Documentation Methods, and Cultural Material locations within the Location of Work, as defined in the main body of the PWS. The Contractor will collect, edit, and differentially correct GPS files, and then transmit projected ESRI geodatabase feature classes with tabular information and FGDC metadata as a deliverable. See Attachment 1: GIS data dictionary for a list of required fields, field definitions, and values. This data dictionary is not intended to represent all of the possible information collected in the field.
1a GPS data collection The Contractor will load a Data Dictionary or XML to the GPS unit. The Data Dictionary or XML file must match the Bonneville Power Administration (BPA) Federal Columbia River Power System Cultural Resource Program specifications1 for Feature Class Names, Field Names, Data Types/Lengths, and Field Definition and Values (Domains). If the Contractor is unable to use the BPA’s XML data dictionary or geodatabase template, the contractor will create the data dictionary using the information provided in Attachment 1: GIS Data Dictionary.
1b GIS Data Formatting GIS Deliverable requirements:
Geodatabase Format: Tabular fields will be populated with information as specified in the Attachment 1: GIS Data Dictionary. All feature class names, field names, and value choices must match the naming conventions in Attachment 1: GIS Data Dictionary. The deliverable will include one geodatabase containing all deliverable feature classes. The deliverable will include one feature class for each type of feature. For example, all survey polygons will be in the Survey_Poly feature class. GIS features of the same type stored as individual features or individual shapefiles will not be accepted.
Spatial Reference: All GIS data will be correctly projected. Questions about appropriate projection should be directed to the COR.
GIS Metadata Format:
There are twelve feature classes in Attachment 1: GIS Data Dictionary. Each feature class in the GIS deliverable will have metadata. The required metadata format is ESRI ArcCatalog Metadata using the FGDC standard: North American Profile (NAP) of ISO 19115 2003. The ESRI ArcCatalog Metadata will have these fields populated; Tags, Summary, Description, Credits, Citation Contact(s), Resource Citation Date(s).
1c Review GIS deliverables will be reviewed to ensure that they meet the requirements described above 1a and 1b. The Contractor must remedy missing or incorrect requirements by submission of the final report and accompanying data.
1 Note that BPA maintains two separate Data Dictionaries: one for the jointly managed FCRPS Cultural Resource Program, and one for cultural resource compliance in support of transmission and fish and wildlife projects.
Attachment 1
GIS Data Dictionary
Field definitions for cultural resource geodatabase. Highlighted fields should be filled out while field work is being conducted.
Site Feature Classes; Site_Poly, Site_Pt, Site_Ln
(Used to define site boundary during initial documentation and subsequent updates associated with condition assessment monitoring and /or resurvey. Also used to document evaluation field methods. Use “Cultural Materials” feature class to document features and artifacts.)
Field Name Alias Data
Type Field Size
Field Definition and Values
Smith_Numb Smith Number Text 30 Smithsonian Trinomial if applicable (8 digit string)
Temp_Site_No Temporary Site Number Text 40 Temporary site number used by contractor
Site_Name Site Name Text 50 Known site name
Visit_Hist Visitation History Text 10 Distinguish between newly recorded sites and revisitation associated with site condition monitoring – Values: New, Monitoring
Field_Date Field Date Date - mm/dd/yyyy
Contractor Contractor Text 50 Name of contracting company, agency, or tribe
Title Report Title Text 255 Full title of report
Site_Type Site Type Text 50 General type of site- Values:
burial/grave/cemetery, camp, feature, quarry, rockshelter/cave, scatter, village/community, historic, homestead, structure, multicomponent, unknown, other
Cult_Period Cultural Period Text 100 Cultural period in which site was utilized- Values: unknown, Paleo (10,500 BP or earlier), Archaic (Specific period not established), Early Archaic (10,500 BP- 7,000 BP), Middle Archaic (7,000 BP-2,000 BP), Late Archaic (2,000 BP-Contact), Contact period, Historic, 19th Century, Early 20th Century (1900-1930), Depression/WWII (1929-1950), Recent (post1950), Multicomponent (Historic & Prehistoric), Multicomponent (Prehistoric Only), Multicomponent (Historic Only), Prehistoric (undetermined pre-contact)
Nreg_Status National Register Status Text 35 Status of National Register of Historic Places- Values: Eligible, Evaluation Testing Recommended, Not Eligible, Listed, Nominated, Recommend Eligible, Recommend Not Eligible, Unevaluated, Unknown
Site_Condition Site Condition Text 30 Site condition observed during this visit- Values: Unknown [no data or condition unknown], Excellent [<5% damage], Good [between 5% and 40% damage], Fair
[between 40% and 60% damage], Poor [between 60% and 95% damage], Destroyed [>95% damage]
Site_Impact Site Impact Text 40 Impact to site- Values: bioturbation, erosion (wind, sheet wash), grazing, recreation, reservoir erosion, undisturbed, vandalized
Min_Elevation Minimum Elevation Text 15 Elevation of site in meters at lowest point
Max_Elevation Maximum Elevation Text 15 Elevation of site in meters at highest point
Data_Der Data Derived Text 25 How was data derived? Values: GPS, digitized, report narrative, personal communication
Lnd_Man Land Manager Text 30 Responsible land management party- Values:
United States Army Corps of Engineers, Bureau of Reclamation, National Park Service, Forest Service, Tribal, Private, and Unknown
Comment Comment Text 255 Open field for additional information
Survey Feature Classes; Survey_Poly, Survey_Pt, Survey_Ln
(Used to document new survey and resurvey transects.)
Field Name Alias Data Type
Field Size
Field Definition and Values
Field_Date Field Date Date - mm/dd/yyyy
Survey_Tp Survey Type Text 20 Type of survey conducted – Values: New [area not previously surveyed using systematic transect intervals], Re-survey [area previously surveyed using any methods], Reconnaissance [area surveyed, but not using systematic transect intervals]
Contractor Contractor Text 50 Name of contracting company
Title Report Title Text 255 Full title of report
Dt_Report Date of Report Text 4 Date report was completed; Stored as year
Data_Der Data Derived Text 30 How was GIS data derived? Values: GPS, digitized, report narrative, personal communication
Interval Transect Interval Text 20 Interval of survey in meters (use “N/A” for reconnaissance survey)
Comment Comment Text 255 Open field for additional information
Documentation Methods and Control Points; Doc_Poly, Doc_Pt, Doc_Ln
(Used to document methods employed to document and evaluate cultural resources, including excavation and condition monitoring.)
Field Name Alias Data
Type Field Size
Field Definition and Values
Smith_Numb Smith Number Text 30 Smithsonian Trinomial if applicable (8 digit string)
Temp_Site_No Temporary Site Number Text 40 Temporary site number used by contractor
Field_Date Field Date Date - mm/dd/yyyy
Contractor Contractor Text 50 Name of contracting company
Title Report Title Text 255 Full title of report
Cont_Pt_Tp Control Point Type Text 50 Type of control point(s) used for NR determination and/or condition monitoring- Values: Site Datum(s), Erosion Control Point, Photo Point, Shovel Test Probe, Excavation Unit/Trench, Surface Collection Unit (no excavation), Disturbed Area, Waterline, Cutbank, Other
Cont_Pt_Nm Control Point Name Text 30 Name of control point (examples: “Datum- 1”, “STP-3”, “Disturbance Area-2”). A corresponding description of each control point must be included in field notes (Example: “Disturbance Area-3 measures 8m N-S by 6m E-W and ranges from 3cm to 20cm deep. Artifact context has been altered by ATV use in area, which has churned sediments).
Cultural Materials Feature Classes; CulturalMaterial_Poly, CulturalMaterial_Pt, CulturalMaterial_Ln
(Used to record cultural materials within or outside a site boundary during initial documentation, or subsequent monitoring - artifacts collected, diagnostic artifacts, features, site datum, photo points, erosion station points, etc.)
Field Name Alias Data Type
Field Size
Field Definition and Values
Smith_Numb Smith Number Text 30 Smithsonian Trinomial if applicable (8 digit string)
Temp_Site_No Temporary Site Number Text 40 Temporary site number used by contractor
Field_Date Field Date Date - mm/dd/yyyy
Contractor Contractor Text 50 Name of contracting company
Title Report Title Text 255 Full title of report
Obj_Type Object Type Text 25 What is being recorded? – Values: Artifact, Feature, Loci (artifact concentration), Isolate (use only if object is outside site boundary)
Obj_Type_Nm Object Type Name Text 100 Name of data being collected (example:
Feature-1, Projectile Point-3, Ground Stone- 13, Locus-2, etc.) Object Type Name and description must be included in the field notes/monitoring form (Example: Ground Stone-13 is a basalt hammerstone 13cm x 6cm x 8cm with use wear on one end)
Art_Collect Artifact Collected Text 5 If Object is an artifact, was it collected?
Values: Yes, No
Art_TCM Artifact Temporary Catalog Number
Text 20 If Object is a collected artifact, what is the temporary field catalog number?
Contract Specifications from the U.S. Army Corps of Engineers, Seattle District
The U.S. Army Corps of Engineers, Seattle District has implemented special regulations to prevent contaminating waters within the District with invasive species, particularly zebra mussels (Dreissena polymorpha). Zebra mussels can be transported by boats, trailers, outboard motors and other equipment such as tractors, bulldozers, water pumps, ropes and nets that are used in areas that zebra mussels inhabit. In Seattle District, zebra mussels have been found in several lakes and river systems. If equipment is not properly inspected and treated to prevent the spread of zebra mussels and other aquatic nuisance species, they can be introduced into areas not currently infested. To assist in preventing the introduction and spread of aquatic nuisance species as a result of work contracted by the U.S. Army Corps of Engineers, the following precautions shall be taken:
Prior to transporting, visually inspect all equipment for zebra mussels and other aquatic nuisance species. All trash, mud, vegetation, and suspected zebra mussels should be removed, place in plastic bags and properly disposed of in land-based receptacles.
All construction equipment and supplies intended for use in Seattle District waters that has been exposed to other lake or stream water shall be thoroughly washed with a power washer or be allowed to dry an appropriate length of time. Water being used for power washing must be at least 160 degrees Fahrenheit when leaving the spray nozzle and 140 degrees Fahrenheit when contacting the equipment being decontaminated. All contaminated runoff must be adequately contained and disposed of properly. The appropriate length of drying time is dependent upon when the work is scheduled to begin.
Pumps, equipment and supplies that cannot be thoroughly drained, cleaned and dried shall be treated with a 200 ppm bleach solution for 20 minutes, deactivated with sodium thiosulfate and rinsed according to the table below.
A Corps of Engineers representative will conduct an onsite inspection of all vessels, equipment, pumps and supplies to be used in or around the water before work begins.
The date and time of this onsite inspection must be coordinated with the contract representative in advance.
Vessels and equipment shall be inspected upon removal from any Seattle District body of water. Hulls, anchors, moorings, trailers, etc. must be clean of all mud, vegetation and any noticeable attached zebra mussels before leaving the facility. Any suspected zebra mussels must be removed, reported to the invasive species coordinator (816) 389-3651 or Corps contract representative and contained for verification.
All vessels and construction equipment being removed from Seattle District waters currently infested with zebra mussels or other aquatic invasive species must also be washed or appropriately dried as described above.
Disinfectant Amounts to Make Needed Concentrations
Disinfectant 1 gallon 2 gallons 5 gallons 20 gallons gallons
TECHNICAL EXHIBIT 3
Invasive Species Prevention Measures
Contract Specifications from the U.S. Army Corps of Engineers, Seattle District
200 ppm Chlorine (household bleach, 5.25% Chlorine)
0.5 ounce (15 ml)
1.0 ounce (30 ml)
2.5 ounces (75 ml)
11.0 ounces (300 ml)
6 1/3 cups (1.5 L)
800 ppm Sodium Thiosulfate
0.1 ounce (3 g)
0.2 ounce (6 g)
0.5 ounce (15 g)
2.1 ounces (60 g)
10.6 ounces (300 g)
Notes:
1. Zebra mussel juveniles, called veligers, are microscopic and invisible to the naked eye.
2. Air drying and hot water are most effective when used in conjunction with each other because their effectiveness is highly dependent upon ambient temperatures and contact times.
3. Household bleach (5.25% chlorine) and vinegar can be purchased from grocery or convenience stores. Sodium Thiosulfate can be purchased at pool supply stores or chemical companies.
4. All bilges and hidden areas under boat decks must be thoroughly treated as described above.
5. For instructions on cleaning and decontaminating specific types of equipment use the following link to access the Inspection and Cleaning Manual for Equipment and Vehicles to Prevent the Spread of Invasive Species;
https://www.usbr.gov/mussels/prevention/docs/EquipmentInspectionandCleaningManual 2010.pdf
TECHNICAL EXHIBIT 4
Report Standards
Final Report
The Contractor shall submit a report of all work performed under this contract to the Government according to the performance and deliverable schedule. The Government will review the draft final report, and may provide written comments. The Government will review reports editorially and substantively for organization, clarity, compliance with the contract, documentation, and adherence to the standards of the profession. The Contractor shall address any written comments. The Contractor shall incorporate changes in the draft report suggested by the Government. The Contractor shall note changes that it does not believe should be included in the report, and shall discuss these changes in the written reply to the Government comments. The Contractor shall insert an appropriate qualifying statement onto the title page of the report indicating that the report findings do not necessarily reflect the views or concurrence of the sponsor. After receiving the review comments, the Contractor shall submit original and review copies of final reports to the Government. Review conferences may be held at appropriate stages during the review process to discuss comments and necessary changes. Deliverables include a draft and final report. Reports shall include, but not be limited to:
Title Page with contract number, Draft or Final, and reference to funding
Acknowledgements of contributions by Contractor’s staff and others including a list of all Contractor staff involved in the project
Recommendations for further work
Brief summaries of activities during the reporting period
A bibliography listing all literature and documents examined
A list of any persons or organizations contacted
A description of the equipment used during survey and monitoring. This shall include, but is not limited to, make, model, and unique features of the auger, GPS unit, and screen utilized.
Report content shall match the requirements the Washington State Department of Archaeology and Historic Preservation standards as defined in the latest version of the Washington State Standards for Reporting of Cultural Resources Reporting, available online.
While historic structures are not expected, if encountered, the Contractor will follow the Washington State Department of Archaeology and Historic Preservation standards for intensive survey data reporting as defined in the latest version of the Washington State Standards for Reporting of Cultural Resources Reporting.
While Washington State does not require that all cultural resource reporting data fields be completed for cultural isolates, under this contract, the Government requires that the Washington State data standards for sites should also be applied to isolates.
The report shall be written in such a way to meet all Washington State requirements for both archaeological resources and historic structures.
GIS data accompanying the report must include polygons indicating the area surveyed, lines depicting placement of transects within the area surveyed, point data indicating auger test locations and differentiating between positive and negative tests, polygons or points as appropriate indicative of sites and/or structures encountered.
Photographs used within the report and accompanying site forms shall be submitted digitally as .tif and .jpg files (See 1.9.3). All photographs need to be labeled in such a way that they can easily be matched to figures within the report or to the site forms with which they are associated. In addition to all state requirements, include at least two overview photographs per cultural resource encountered and photographs of diagnostic artifacts. Include an accompanying photolog to detail photograph file name, description of the photograph content, compass direction in which the photographer was facing, and the date the photograph was taken.
Any required consultation under the National Historic Preservation Act will be conducted by the Government.
Progress Reports
The Contractor shall inform the COR about work progress regularly by telephone and electronic mail. The Contractor shall submit brief written progress reports to the COR. The Contractor shall identify in these reports any problems encountered in work performance.
TECHNICAL EXHIBIT 5
Inadvertent Discovery
In the event that the Contractor discovers human remains, the Contractor will cease work immediately and contact the COR. The Contractor shall remain onsite, securing the area until informed to do otherwise. A Corps representative will contact the King County or Pierce County coroner and law enforcement as appropriate. After initial discovery, the Contractor will not move, disturb, further uncover, or otherwise interact with the remains. No photography of the remains shall be permitted. No discovery of human remains is anticipated.
Sources: Esri, HERE, Garmin, Intermap, increment P Corp., GEBCO, USGS, FAO, NPS, NRCAN, GeoBase, IGN, Kadaster NL, Ordnance Survey, Esri Japan, METI, Esri China (Hong Kong), (c) OpenStreetMap contributors, and the
GIS User Community
Technical Exhibit 6 - Howard A. Hanson Dam Project Area Proposed Survey Area
Sources: Esri, HERE, Garmin, Intermap, increment P Corp., GEBCO, USGS, FAO, NPS, NRCAN, GeoBase, IGN, Kadaster NL, Ordnance Survey, Esri Japan, METI, Esri China (Hong Kong), swisstopo, © OpenStreetMap contributors, and the GIS User Community
Mud Mountain Dam Project Area Cultural Resources Survey Status
Winter 2019
DISCLAIMER - While the United States Army Corps of Engineers, (hereinafter referred to USACE) has made a reasonable effort to insure the accuracy of the maps and associated data, its should be explicitly noted that USACE makes no warranty, representation or guaranty, either express or implied, as to the content, sequence, accuracy, timeliness or completeness of any of the data provided herein. The USACE, its officers, agents, employees, or servants shall assume no liability of any nature for any errors, omissions, or inaccuracies in the information provided regardless of how caused.
The USACE, its officers, agents, employees or servants shall assume no liability for any decisions made or actions taken or not taken by the user of the maps and associated data in reliance upon any information or data furnished here. By using these maps and associated data the user does so entirely at their own risk and explicitly acknowledges that he/she is aware of and agrees to be bound by this disclaimer and agrees not to present any claim or demand of any nature against the USACE, its officers, agents, employees or servants in any forum whatsoever for any damages of any nature whatsoever that may result from or may be caused in any way by the use of the maps and associated data.
enumclaw Legend
Proposed Survey 2019 Mud Mountain Dam Project Area Areas Surveyed: Subsurface Areas Surveyed: Historic Structure Areas Surveyed: Pedestrian
0 1 2 3 40.5
Miles
Technical Exhibit 6 -
280 acres
Sources: Esri, HERE, Garmin, Intermap, increment P Corp., GEBCO, USGS, FAO, NPS, NRCAN, GeoBase, IGN, Kadaster NL, Ordnance Survey, Esri Japan, METI, Esri China (Hong Kong), (c) OpenStreetMap contributors, and the GIS User Community
Mud Mountain Dam Proposed New Survey Area
0 0.55 1.1 1.65 2.20.275
Miles
New Survey Area 280 acres
| Technical Exhibits 1-5 (final), HAHD MMD.pdf |
| Technical Exhibit 6, Survey Map HAHD.pdf |
| Technical Exhibit 6, Survey Map MMD.pdf |
| SurveyatMMDWinter2018.pdf |
| MMD 280 acres.pdf |
File details come from the government source that posted it.