SOW_Final.pdf

1.0 Preliminary Kick-Off Call

A preliminary kick-of call shall be held via teleconference with the contractor’s team, CO, CS, CORs, and selected park staff within 30 working days of project initiation. The contractor and CORs shall arrange the date and time of the call.

The anticipated agenda for the preliminary kick-off call shall include:

1. Review the scope of services and address any issues with process or deliverables,

2. Establish deadlines and expectations for deliverables,

3. Identify relevant archives and repositories,

4. Discuss refinements to the project approach, discuss field safety protocols,

5. Coordinate the first site visit to the park, and

6. Any additional items the Contractor identifies as needed.

The contractor shall deliver meeting notes to the CORs and park contacts no more than three (3) business days after the call.

Deliverables:

1. At least three (3) full business days in advance of the Preliminary Kick-off call, the contractor shall prepare and share the agenda.

2. Preliminary kick-off call notes shall be submitted for review (electronic version in MS Word format) within 3 business days of meeting completion.

3. Final meeting notes shall be due 3 business days after review comments by NPS are returned to the Contractor.

2.0 Project Status Coordination

The Contractor shall participate in no more than 5 regularly scheduled project status conference calls (duration up to 1 hour) with NPS to discuss and coordinate:

1. Survey scoping,

2. Project schedule,

3. Progress of individual task problems encountered and options for their resolution, and

4. Project milestones.

At least three (3) full business days in advance of the calls the contractor shall prepare the agenda for the conference calls, and written project status meeting notes at least 3 full business days following the conference call. The meeting notes shall document discussion and decisions related to each agenda topic. NPS will maintain the calendar appointments for the call.

Deliverables:

1. Draft agenda shall be shared at least 3 business days before a call, and project status conference call meeting notes shall be submitted (electronic version in MS Word format) within 3 business days for review of meeting completion.

2. Project Status Conference Calls

3. Final meeting notes shall be due 3 business days after review comments by NPS are returned to the Contractor. The Contractor shall upload the final meeting notes to PEPC as an internal document.

3.0 Project Schedule

The contractor shall develop and maintain a detailed project schedule.

The initial draft shall be submitted to the COR no later than three (3) weeks after contract award.

The schedule shall include:

1. Deliverables as identified in the scope of service,

2. Review period for NPS (at least 2 weeks for more complex deliverables), and

3. Other important milestones as identified in the scope of service.

The contractor will make the necessary changes to the draft schedule to produce and submit a final schedule to the COR within two (2) weeks after the Preliminary Kick-off call.

The contractor shall be responsible for updating the schedule on a monthly basis, to reflect changes to the overall project schedule. A Gantt chart format, such as MSProject, is preferable. Changes shall be reviewed during status calls.

Deliverables:

1. The initial detailed project schedule (in MSProject or similar) shall be submitted to the DSC COR within three (3) weeks after the task order being approved.

2. The final schedule is due two (2) weeks after the Preliminary Kick-off call and shall be updated on a monthly basis.

7.0 Project Coordination Schedule of Work

Task Deliverable Date

1.0 At least three (3) full business days in advance of the

Preliminary Kick-off call, the contractor shall prepare and share the agenda.

TBD

Preliminary kick-off call notes shall be submitted for review (electronic version in MS Word format) within 3 business days of meeting completion.

Final meeting notes shall be due 3 business days after review comments by NPS are returned to the Contractor.

2.0 Draft agenda shall be shared at least 3 business days before a call, and project status conference call meeting notes shall be submitted (electronic version in MS Word format) within 3 business days for review of meeting completion.

On-Going

Project Status Conference Calls

Final meeting notes shall be due 3 business days after review comments by NPS are returned to the Contractor.

The Contractor shall upload the final meeting notes to PEPC as an internal document.

On-Going

3.0 The initial detailed project schedule (in MSProject or

similar) shall be submitted to the DSC COR within three

(3) weeks after the task order being approved.

TBD

The final schedule is due two (2) weeks after the Preliminary Kick-off call and shall be updated on a monthly basis.

Compliance BR: Biological Resources The purpose of this task is to assess the presence of biological resources that could potentially occur within the project sites in order to identify impacts and mitigations for compliance. For this project, this is limited to the evaluation of trees within the project area in support of endangered species act compliance.

Specific goals of this task are to

1. Determine the total number of trees with a DBH of equal to or greater than 3 inches within the project area,

2. Determine the species of the trees within the project area,

3. Determine the size of the trees within the project area (caliper diameter at breast height and total height), and

4. Determine canopy size of the trees within the project area

5. Determine the general health of the trees within the project area

The Contractor shall provide all materials, supplies, supervision, coordination, and management necessary to complete the work as and when required. Graphics, photos, maps, charts, etc. must be in a format suitable for reproducing in black and white imagery.

Maps will be provided geo-referenced and in a format compatible with ArcGIS 10.X.

All survey and research methods used shall be finalized by the Contractor and approved by NPS prior to survey start. When practicable, surveys should be conducted concurrently or within the same field site visit for efficiency. Surveys will be scheduled in consultation with the NPS MACA Science and Resource Management staff during the appropriate survey windows.

The survey work, recording, transmittal procedures, and report standards shall meet accepted professional and NPS guidelines and the Secretary of the Interior’s Standards and Guidelines. All work under this task shall be conducted by a botanist, dendrologist, forester, or arborist who has the appropriate knowledge of Western KY trees to speciate, and knowledge of tree diseases

1.0 Surveys and Research

1.1 Tree Survey

The CONTRACTOR shall conduct a field survey of all trees within the project area (See Attachment XX for map). This survey shall include developing the following data for each tree:

1. Species

2. Location (GPS)

3. Overall Health

4. Diameter at Breast Height

5. Height

6. Any other peculiar or notable features

a. Disease,

b. Damage, Deliverables:

1. Completion of Field Surveys.

2.0 Report(s)

2.1 Tree Report

The report shall include a summary, survey methods, dates, field notes, mapped locations, and names and qualifications of principal investigators. A numbering system must be used such that each location identified on the maps can be linked to its corresponding discussion. Data should also correspond in the GIS data files.

The CONTRACTOR shall include as part of the tree report a table of the results of reconnaissance surveys, including species scientific and common name, federal and state status.

Maps will be provided geo-referenced and in a format compatible with ArcGIS 10.X.

Photo-documentation of plant locations are to be geo-referenced to the plan view mapping for the listed plant species maps. The listed plant species maps will be submitted digitally as PDF files and as shapefiles compatible with ArcGIS 10.X.

Deliverables:

1. The Contractor shall submit one (1) electronic copy in both Adobe Acrobat (pdf) format and MS Word format, with lines numbered on each page, of the draft report(s) along with GIS data in an ESRI GIS format and FGDC-compliant metadata for NPS review. The Contractor shall prepare responses to review comments on the report and submit these for approval before incorporating changes into subsequent versions of the document. Following NPS review and approval the Contractor shall revise the draft report per the comments.

2. After NPS comment revisions are completed the Contractor shall submit one (1) copy each in Adobe Acrobat (pdf) format and MS Word format of the final report(s) and GIS data for NPS use.

WR: Waters of the United States (WOUS), Wetlands and other Waters Jurisdictional Delineation and Functional Assessment - Option The purpose of this task is to develop a Wetland Statement of Findings in accordance with NPS Director’s Order 77-1.

The Contractor shall provide all materials, supplies, supervision, coordination, and management necessary to complete the work as and when required. Graphics, photos, maps, charts, etc. must be in a format suitable for reproducing in black and white imagery.

6.1 Waters of the U.S. other Waters, Wetlands and Functional Assessment CONTRACTOR shall prepare a draft Wetlands Statement of Findings (WSOF) in accordance with the methods outlined in the NPS Procedural Manuals 77-1 Wetland Protection (NPS 2016). Wetland delineation and mapping on NPS land need to satisfy both Section 401 and 404 wetland definition (1987 USACE Manual) and the FGDC Wetlands Classification Standard (NPS 2016).

Deliverables:

1. The CONTRACTOR shall submit one (1) electronic copy in both Adobe Acrobat (pdf) format and MS Word format of the draft WSOF. The CONTRACTOR shall for NPS review also submit maps for each site as separate digital PDF files and photos in digital (JPEG compatible) format.

2. The CONTRACTOR shall prepare responses to review comments on the draft WSOF and submit these for approval before incorporating changes into subsequent versions of the document. Following NPS review and approval the CONTRACTOR shall revise the draft WSOF per the comments.

3. After revisions per NPS review comments are completed the CONTRACTOR shall prepare the final WSOF. CONTRACTOR shall submit one (1) copy each in Adobe Acrobat (pdf) format and MS Word format of the final WSOF for NPS use.

Compliance Schedule of Work Task Deliverable Date

BR 1.1 Field Surveys

1.2 Draft Tree Report

1.2 Final Tree Report

CR

WR 6.1 Draft WSOF

Response to Comments

Final WSOF

Deliverables Format Paper format: 8-1/2" x 11" recycled white bond paper (if applicable, 11" x 17" paper shall be fan-folded). Use cover-stock for cover and back page. Include the park name, project name and PMIS number on each map. The cost of the EA shall be printed on the front cover.

A document number for the EA shall be provided by the DSC Natural Resources Technical Specialist COR. The document number shall be placed on the inside back cover along with the date, NPS and Department of the Interior (DOI) logos and statement. A back-page layout shall be provided by the DSC COR.

Section 508 Compliant Documents:

The contractor shall format all documents to be posted to PEPC to meet the accessibility requirements and standards as defined by the United States Access Board in compliance with section 508 of the Rehabilitation Act. The contractor shall also format the digital EA and AOE Report files for printing in an Adobe PDF/X-4 format. The contractor shall run full accessibility and printing pre-flight checks through built-in tools in Adobe Acrobat and remedy all issues found by the automatic check. See the 2015 BLM Handbook for Creating Section 508 Compliant Documents for basic guidance on how to prepare accessible documents. The contractor shall:

Organize and tag elements of the document, including paragraph structure, tables, charts, figures, photos, and lists that makes sense to the user of a screen reader or other text-to-speech tool (i.e., assistive software) knows in what order to read parts of the PDFs. The PDFs shall include navigational aids (links, bookmarks, headings, and a table of contents)

Ensure regularity of tables (no merged/split cells) Add alternative text that fully describes figures and images that can’t be read by a screen reader.

Set the language of the document to English.

Ensure color contrast is appropriate (e.g., high contrast between text and background colors).

Run a full accessibility check through built-in tools in Adobe Acrobat and remedy all issues found by the automated check. Provide the 508 certificate.

GIS Deliverables:

CONTRACTOR are expected to submit all raw data, derived data products, and other supporting materials created or gathered in the course of work. Provide all maps, collected field data (in raw and processed format), all GIS projects (*.mxd), and GIS generated spatial data to NPS.

All GIS products will contain FGDC compliant metadata.

Vector data shall be supplied to the NPS as an ESRI Feature Class located within a

File Geodatabase (.gdb) compatible with ArcGIS v10.1.

All Feature datasets and classes shall contain projection information and conform to the UTM, NAD 83, 17N projection.

Coded and Range domains shall be used where applicable to minimize data-entry error.

Project will contain relative path names.

Data integrity must be ensured and checkable:

Each feature class must have a topology element applied.

Where appropriate, attribute domains must be applied to attribute fields.

The ‘Check Geometry’ and ‘Repair Geometry’ tool must be run on all completed feature classes.

The XY tolerance of a feature dataset will be applied to all the feature classes stored within it.

Feature classes shall have full CSDGM-compliant metadata associated with each file and contain at a minimum the source, scale, date, and methods (i.e., process steps). (See below)

Once editing operations are complete the File geodatabase should be compacted.

The GIS Database must be of sufficient quality to receive approval by NPS Inventory and Monitoring data management staff. All existing and new data compiled shall be compiled into a unique Microsoft Access database which shall be included at the final completion of this contract. The database shall include all of the raw data (spatial, flow, groundwater, vegetation, etc.) which has been corrected and cleaned for accuracy. The raw data shall meet park data standards. The database shall also include all Final/Approved reports and design map packages produced under this contract.

Metadata:

The Federal Geographic Data Committee (FGDC) http://www.fgdc.gov is tasked by Executive Orders to develop procedures and assist in the implementation of a distributed discovery mechanism for national digital geospatial data.

A metadata record is a file of information, usually presented as an XML document, which captures the basic characteristics of a data or information resource. Geospatial metadata commonly document geographic digital data such as Geographic Information System (GIS) files, geospatial databases, and earth imagery but can also be used to document geospatial resources including data catalogs, mapping applications, data models and related websites. Metadata records include core library catalog elements such as Title, Abstract, and Publication Data; geographic elements such as Geographic Extent and Projection Information; and database elements such as Attribute Label Definitions and Attribute Domain Values.

Metadata shall be included as an .xml file for all data types including spatial and tabular data, models, and imagery. Metadata will include detailed descriptions of creation methods, analysis steps, spatial and attribute description and accuracies, complete data dictionaries, as well as use constraints and any other relevant information that could affect interpretation of applicability of these data for any potential purpose.

Maps:

Electronic copies of all maps provided in the report deliverable shall be included as *.pdf’s.

Existing cartographic standards for the NPS shall be incorporated into all GIS mapping deliverables. The following elements shall be incorporated into all GIS generated maps.

All layers represented in the geographic extent must be identified and clearly labeled in the legend.

Symbology in legend should match that in the geographic extent.

Where applicable, include a set of reference maps (e.g. overview maps with plot locations, cities, roads).

Include reference citations for all data layers reproduced in the map.

Map will contain relative path name location of the document within the Project folder.