SOW Carderock Stream Construction CA 2018.docx.pdf

Title: Naval Support Facility Carderock - Stream Restoration Construction 23 May, 2018

Cooperative Agreement:

Scope of Work

Location: Naval Support Facility Carderock, MD

Title: Stream Restoration Construction

Period of Performance: 18 months after contract award, plus two 1-year options

Project Manager/ Technical Point of Contact (PM/TPOC): Carolyn Woods 202-685-3062

Contracting Officer: Blake Wittmann, NAVFAC Washington 202-685-1257

Station Point of Contact(s) (SPOCs):

Jennifer Pipe

301-227-4850

1. BACKGROUND:

The Naval Support Facility Carderock (NSF Carderock) encompasses 186.8 acres along the Potomac River in western Bethesda, Montgomery County, Maryland and is approximately 12 miles northwest of Washington D.C. The installation is located south of MacArthur Boulevard, north of the Clara Barton Parkway and the Chesapeake and

Ohio (C&O) Canal, and west of Interstate-495. There are 15 streams and 10 non-tidal wetlands located on the installation. The southern and western portions of the installation drain south off the property to culverts under the C&O Canal, which drains to the

Potomac River, a tidal, navigable interstate tributary of the Chesapeake Bay. The eastern portion drains east off the property to Rock Run, a lower perennial stream, and into the Potomac River. The total length of waters is 7,797 linear feet of jurisdictional waters, and 4.66 acres of wetlands. Weather events and previous installation actions and practices have resulted in degradation of water quality of onsite streams. Many degraded areas are located on slopes along and surrounding perennial streams and have resulted in negatively affected drainage patterns, encouraged soil erosion and increased the sediment loading of runoff. These changes in drainage patterns have resulted in localized flooding, erosion of outfalls and unintended bypass of drainage systems and ditches.

If this project is not implemented, the impacts to the mission at NSF Carderock include further degradation of slopes along and surrounding perennial streams, negative increases in drainage patterns, soil erosion and sediment loading of runoff. Continued changes in drainage patterns will result in localized flooding, erosion of outfalls and unintended bypass of drainage systems and ditches. This effort supports the requirement of the Sikes Act and the NSF Carderock Integrated Natural Resources Management Plan (INRMP) to mitigate soil erosion. INRMPs offer a coordinated approach for incorporating ecosystem management efforts into the management of natural resources at DoD installations.

2. OBJECTIVE: The purpose of the Cooperative Agreement is to implement construction that focuses on stream restoration, re-establishment of stable stream geometry and elimination of bank erosion. The goal of this construction will create a natural, self-sustaining channel capable of supporting native stream flora and fauna.

3. ENVIRONMENTAL SETTING: NSF Carderock is comprised mainly of developed land including buildings, parking lots, paved areas, landscaped areas, and mowed grass areas. It also contains approximately 30 acres of mature deciduous woodlands, 4.66 acres of wetlands and

7,797 linear feet of streams. Some stream channels are currently unstable with moderate to severe bank erosion. This erosion delivers excess sediment to downstream reaches, which contributes to poor water quality and degraded in-stream habitat.

A SITE VISIT BEFORE PROPOSAL SUBMISSION IS REQUIRED. The pre-award site visit will provide the opportunity to evaluate jobsite conditions, and to obtain clarification of project requirements. The design and permits will be provided to the Cooperator prior to the site visit.

4. SPECIFIC REQUIREMENTS:

TASK 1: The purpose of this Cooperative Agreement is to implement the Carderock Stream

Restoration Construction Design dated March 2018.

a. The requirements of this stream restoration construction include: 1) Reach 1 – remove sedimentation and vegetation to increase capacity and improve conveyance. 2) Reaches 2 and

3 – reduce bank erosion using natural material revetments, and create a natural, self-sustaining channel capable of supporting native stream flora and fauna. In addition, the design includes aspects that improve riparian habitat for wildlife use without requiring excessive long-term maintenance, the removal of invasive species, and the use of native non-invasive species.

b. The project will restore intermittent and perennial stream channels by permanently impacting a total of 20,184 square feet along 2,910 linear feet of stream channel by grading and removing sediments from 2,370 linear feet, installing riffle grade controls along 43 linear feet, installing step pools along 219 linear feet, constructing cascades along 26 linear feet and placing outfall riprap scour protection along 65 linear feet of stream channel to remove accumulated sediments, increase capacity and conveyance, reduce bank erosion and create a natural, self-sustaining stream channel.

c. No in-stream work shall be conducted during the period of March 1 through June 15, unless a waiver is obtained from the water management administration of the Maryland Department of the Environment.

d. The Cooperator shall not be responsible for obtaining any of the required permits for this project. However, the Cooperator will be responsible for complying with the terms and conditions of all permits required for this project.

e. The Cooperator shall be responsible for determining the locations of all utilities, structures, plant materials, erosion and sediment control features and limits of disturbance.

f. In addition to using any government or utility company locating services available (i.e.

Miss Utility), the Cooperator shall utilize a qualified private utility locating service company to locate all underground utilities in the work area. Any markings made during the utility investigation must be maintained throughout the duration of the work. The Cooperator must physically verify underground utility locations by hand digging using wood or fiberglass handled tools when any adjacent exploration, excavation or construction work is expected to come within three (3) feet of the utility. Utility relocation may be necessary to accomplish the work. Relocation design will be provided by the Cooperator to the Navy for approval prior to relocation work. All work will be in accordance with all federal and state regulations.

g. Work shall not be conducted during a rain event, within 24 hours after a significant rain event has ended (equal to or greater than 0.5” over a 24-hour period), or when the soil is frozen or excessively wet.

h. The Cooperator must continuously measure the channel and all structures during construction to ensure that the proposed grades, structures, elevations, and slopes are consistent with the design. Unless otherwise noted, all elevations, grades, dimensions and structures shall be constructed within 0.2 feet of what is shown on the design.

i. The Cooperator shall make all reasonable attempts to minimize disturbance to vegetation and soil within the work areas. Vegetation that is not slated for removal that is scarred, nicked, or otherwise damaged shall be pruned to the satisfaction of Navy personnel. All vegetation that is to be removed shall be flush cut using a chain saw or other cutting device. It shall not be scraped or pushed over.

j. All disturbed stream banks within the level of disturbance (LOD) shall be permanently stabilized with seed and soil stabilization matting.

k. All flow must be diverted and removed from the work areas during construction.

Dewatering of the work area is required.

l. The Cooperator shall be responsible for the repair or replacement of all features and property which are damaged as a result of this restoration project. Determination of whether a repair or replacement is acceptable shall be made by the Navy.

m. Sediment controls may only be removed with the approval of Navy personnel.

n. Following the completion of construction, the Cooperator shall be responsible for removing all debris, trash, and other materials brought to the site.

o. Due to the dynamic nature of streams, site conditions may change, therefore, the topographic data provided may not reflect current conditions. It is the responsibility of the Cooperator to verify existing conditions prior to construction to provide for full completion of the project.

p. A post-construction inspection will be performed within 7 days following completion of work to inspect the work products. Structures, grades, materials, seeding and plants will be inspected for compliance with the plans. Any work or material found to be deficient or otherwise non-compliant with the plans, for any reason, shall be repaired or replaced by the

Cooperator at his/her expense within 7 days of the post construction inspection. All repair work shall be performed to the satisfaction of the Navy and/or agency representative.

q. The Cooperator must submit a draft and final report/as-builts at the conclusion of this project.

OPTION 1 TASK 2: Monitor the project site for 1 year after construction completion and maintain a warranty of 85% success rate for all seedlings and plants. (This option shall be awarded at the discretion of the Navy.)

OPTION 2 TASK 3: Monitor the project site for a second year after construction completion and maintain a warranty of 85% success rate for all seedlings and plants. (This option shall be awarded at the discretion of the Navy.)

5. KICK-OFF MEETING/SITE VISITS

Neither the Contractor nor any Subcontractor shall be onsite without proper coordination and notification to the SPOC and TPOC. At least one (1) week prior coordination is required before conducting a site visit or kick-off meeting.

a. Kick-Off Meeting: A kick-off meeting between the Cooperator, Contracting Officer, the

TPOC, and the SPOC shall be arranged by the Cooperator within 10 days (or earlier) from the date of award of this Agreement. The Cooperator shall present a proposed milestone schedule, including a site visit schedule, and proposed working dates for discussion. The Cooperator shall provide meeting minutes within 5 business days of the kick-off meeting.

b. Site Visits. Site visits shall be arranged by the Cooperator as needed to complete the tasks under this Agreement, or as requested by the TPOC.

c. Progress Meetings. The Cooperator shall be available throughout the Agreement period to the TPOC in matters regarding the tasks to be completed under this Agreement.

6. SCHEDULE AND SUBMITTALS

a. Safety Plan: All field work requires a safety plan. The Cooperator shall submit (by email) the draft safety plan to the TPOC and SPOC within 20 days or less of

Agreement award and at least 3 weeks prior to the projected start of any field activities. The

Safety Plan must be approved by the Installation Safety Office prior to the start of any fieldwork (review time averages 1 week). The SPOC will provide the Cooperator with specific information on the required format and content of the Safety Plan. This may include an EM-385 compliant Safety Plan. The Safety Plan may also include personal protective equipment (PPE) requirements, installation emergency point of contact and any conditions that would require an immediate work stoppage and a site evaluation by installation safety personnel (e.g., unexploded ordnance (UXO)t).

b. Work Plan/Work Schedules: The Cooperator shall provide a draft project schedule and draft work plan to the TPOC and SPOC within 20 days or less of Agreement award and at least

3 weeks prior to the projected start of any field activities. Cooperator shall submit a final work plan/work schedule to the TPOC and SPOC within 5 days of Navy comment receipt.

c. Monthly Reports: Monthly progress reports are due to the TPOC by the seventh

(7th) day of the following month or the next workday if the 7th falls on a weekend, for work performed the previous month, for the duration of the Agreement. The progress report shall include, at a minimum, the Agreement number, report date, report period, project name, names of investigators, meeting minutes (minutes shall include the date/time/location the meeting was held, attendees, relevant discussion notes, etc.), work performed during the reporting period, problems encountered and recommendations to resolve issues, work anticipated for the next reporting periods and project status.

i. Meeting minutes – Please note Cooperator shall submit draft meeting minutes to the TPOC within seven days of the meeting occurrence. The TPOC will provide comments within seven days of receipt of draft minutes. Final meeting minutes may be included in the monthly progress report submittal.

d. Draft/Final Report (including as-builts): The Cooperator shall submit one (1) hard copy and one (1) CD each of the draft report to the TPOC and SPOC upon completion of the project. The draft report shall include text tables, figures, color photos, and the as-builts shall be concurrently submitted, in a format readable by Microsoft Word. The TPOC and SPOC will submit comments, if applicable, to the Cooperator within fifteen (15) days upon receipt of the

Draft documents. The Cooperator shall incorporate any comments and submit one (1) hard copy and one (1) CD each of the final report to the TPOC and SPOC. All electronic source files for tables and figures shall be labeled and submitted. All digital photographs shall be labeled with at least the following information: (1) subject/activity, (2) location (specific place), (3) date, and (4) name of photographer. As-builts must meet Navy GIS standards identified in Appendix one (A).

7. GENERAL REQUIREMENTS

a. The Cooperator shall manage the total work effort and assure full and timely completion of services required under this Scope of Work. Included in this function shall be a full range of management duties including, but not limited to, planning, scheduling, inventory, analysis, and quality control.

b. The Cooperator shall comply with all applicable laws and regulations pertaining to the provision of a safe workplace and to provide a work environment free of harassment and intimidation for such party’s own employees and third parties.

c. The Cooperator and its employees, contractors, subcontractors, etc., shall comply with all applicable federal and state laws, such as, but not limited to, the Sikes Act, the Clean Water

Act, Coastal Zone Management Act, Endangered Species Act and the Migratory Bird and

Treaty Act. In addition, the Cooperator ensures all staff or personnel working under the

Agreement shall not violate the Archeological Resources Protection Act, National Historic

Protection Act or the Endangered Species Act while completing work required under the

Agreement. Any contact/discussion in regards to this project with regulatory agencies shall be initiated/conducted by the TPOC.

d. If applicable, the Cooperator shall conduct literature review, field investigations and interviews with experts and authorities as necessary to accomplish the work described within this Scope of Work. The Cooperator shall, in particular, attempt to contact and utilize information from the local U.S. Navy offices and other professionals who are experienced in technical requirements under this Scope of Work.

e. Installation Permits. In addition to any regulatory required permits, the Cooperator shall coordinate with the SPOC to obtain any installation specific permits (i.e., Hot Work, Utilities, Outages, etc.) required prior to the initiation of any field work. Please be aware that permits may take up to 14 days for approval and will be coordinated by the SPOC.

f. The Cooperator shall ensure that the data obtained under the Agreement be scientifically defensible and suitable for publication. Methods of data collection and/or analyses shall be provided in the Cooperator’s required Work Plan. The U.S. Navy, at its discretion, may subject work plans, draft reports or draft manuscripts to external peer review.

g. The Cooperator shall inform, in writing (by email), the Contracting Officer (via TPOC and copy SPOC) intent to publish or present any data or findings resulting from activities/research completed under this Agreement. In addition to approval from the Contracting Officer, permission from the installation Public Affairs Office must also be obtained prior to such publication or presentation. Communications will be by email unless specified otherwise.

References to data include both paper documents and computer files. Electronic copies shall be sent by email unless specified otherwise.

h. The Cooperator shall inform the TPOC and copy the SPOC of any unusual activity observed while conducting work in the field (e.g., trespassers or person in unauthorized areas).

Information should include location, date, time and detailed facts regarding the activity. In addition, information regarding trespassers should be reported to the Installation Security

Office by telephone, as soon as possible via the SPOC. Unexploded ordnance (UXO) may be encountered while conducting fieldwork. The Cooperator shall not touch or attempt to pick-up any suspected ordnance. The Cooperator shall place flagging in the general area of the ordnance and notify the SPOC via telephone of the exact location of the ordnance as soon as possible.

i. The Cooperator shall allow, throughout the term of the Agreement, the TPOC and the SPOC the opportunity to periodically observe the Cooperator’s field activities, to review computer or paper files of raw data, prepared data (such as data analyses, summaries, maps, figures, tables, etc.), or any record deemed appropriate by the Contracting Officer in establishing the

Cooperator’s performance in fulfilling the requirements of the Agreement.

j. The Contracting Officer, via the TPOC, may request updated data (presented on maps, figures and/or tables) whenever the U.S. Navy’s need to obtain this information is before the next Monthly Report. The Cooperator shall forward the requested data electronically within ten

(10) days from the date of request. If the requested data cannot be provided within this time frame, the Cooperator shall forward electronically the most updated raw data to the

Contracting officer, via the TPOC. The U.S. Navy understands that facilitating the requested most updated data may reduce the amount of work that would normally be accomplished during the period of time required to complete the request. The Cooperator shall document the amount of efforts and its translated cost estimate that would have been incurred by the

Cooperator to complete the request for updated data. This document shall be electronically forwarded to the Contracting Officer (via TPOC) to review so that the U.S. Navy will have a good grasp on the amount of work displaced that would have normally been accomplished during the period of time required to complete the request.

k. The Government will not be responsible for the loss of or damage to property of the

Cooperator, or for personal injuries to the Cooperator arising from or incident to the use of

Government facilities or equipment.

l. The Cooperator shall indemnify and hold harmless the Government, its officers, agents, servants and employees from all liability under the Federal Tort Claims Act (28 U.S.C. Sec

2671 et seq.) or otherwise, for death or injury to all persons, or loss or damage to the property of all persons resulting from the use of the premises by the Cooperator. This covenant shall survive the termination of the Agreement.

m. In the event of damage, including damage by contamination, to any Government property by the Cooperator, its officers, agents, servants, employees, or invitees, the Cooperator, at the election of the Government, shall promptly repair, replace, or make monetary compensation for the repair or replacement of such property to the satisfaction of the Government.

n. The Cooperator must obtain $250,000 of comprehensive general liability (CGL) insurance.

All insurance required by the Agreement shall be in such form, for such periods of time, and with such insurers as the Contracting Officer may require. A certificate of insurance or a certified copy of each policy of insurance taken out hereunder shall be provided to the

Contracting Officer’s local representative prior to use of the premises and facilities. The

Cooperator agrees that not less than thirty (30) days prior to the expiration of any insurance required by the Agreement, it will deliver to the Contracting Officer’s local representative a certificate of insurance or a certified copy of each renewal policy to cover the same risks.

Cooperator shall furnish the insurance specified as follows and each policy of insurance covering bodily injuries and third party property damage shall contain an endorsement reading substantially as follows:

i. The insurer waives any right of subrogation against the United States of

America which might arise by reason of any payment made under this policy.

ii. NAVFAC Washington shall be given thirty (30) days written notice prior to making any material change in or the cancellation of the policy.

iii. The United States of America (Dept. of the Navy) is added as an additional insured in operations of the policy holder at or from premises designated under the Agreement and owned by the United States.

iv. This insurance certificate is for use of facilities under the Agreement.

v. Loss, if any, under this policy shall be adjusted with the Cooperator and the proceeds, at the direction of the Government, shall be payable to the

Cooperator, and proceeds not paid to the Cooperator shall be payable to the

Treasurer of the United States of America.

o. The Cooperator shall guarantee that an 85% survival rate of the plantings two years after the initial planting. This survival rate will be reviewed and approved of by the TPOC and SPOC prior to completion of this task order and issuance of final payment.

p. The Cooperator shall coordinate the work to be accomplished with the SPOC in the specified work area.

q. If archeological resources or potential archeological resources are inadvertently discovered, the cooperator must STOP WORK and contact Jennifer Pipe via telephone at (301)227-4850.

and cc the TPOC.

r. The Cooperator shall comply with all security rules, regulations, requirements, and day-to-day operational changes thereto. Unannounced changes to day-to-day operational procedures may, at times, prohibit the Cooperator access to the project area. The primary use of the

Installation is for its military mission. Without prior notice, designated areas may become closed to the activities of the Cooperator. In some cases, due to operations or other circumstances, it may be necessary to deny the Cooperator access to the Installation for short periods of time. In such cases, the Cooperator will reschedule this work to the maximum extent possible. Should the U.S. Navy require the Cooperator to leave the Installation for a period greater than thirty (30) days (such as in the case of a national emergency), the Agreement may be terminated by either party unless an alternative agreement is reached between the

Cooperator and the U.S. Navy through a formal amendment of the Agreement. If the

Agreement is terminated, the Cooperator shall not bill for work not completed subsequent to the termination date of the Agreement.

s. Photography is restricted on the Installation. The Cooperator is required to obtain permission from the U.S. Navy prior to taking any photographs on the Installation. Only photographs of

Agreement related activities will be permitted.

t. Access. The Cooperator (with the assistance of the Government), at its own expense, will be required to obtain access passes or long-term badges that will remain active for the duration of the project. The Cooperator must complete and submit a vetting form for all that will access the base to the SPOC at least 5 business days prior to the kick-off meeting and field activities, as applicable, for base Security review and approval. If approved, a visitor pass will be issued for up to 30 days before renewal is required. Failure to do so will result in denial of base access.

u. In order for personnel to access U.S. Government property in an automobile, a valid driver’s license, vehicle registration and proof of insurance are required. Copies of these documents shall be provided to the installation Security Office. All employees assigned to this job must be

U.S. citizens.

8. SECURITY

No classified information shall be presented in any document prepared under this Task

Agreement. The Cooperator shall not release any information regarding the project, particularly the results developed under this Task Agreement, to any Federal, State or local

(public or private) agencies or organizations without permission of the U.S. Navy.

9. DOCUMENT REQUIREMENTS

a. Document Standards – The Contractor shall conduct reviews as needed to ensure that all deliverables are of high technical quality, meet Federal government and Navy standards for formatting, and are free of grammatical/spelling errors. All deliverables shall adhere to Navy instructions.

Draft Reports – Draft reports are considered “drafts” only in the sense that they have not been reviewed and approved by the Government.

i. In all respects, draft reports shall be complete, free of grammatical/typographical errors, and coherently written.

ii. Printed on both sides of at least 25% post-consumer recycled paper with maximum spacing of 1.5 lines.

iii. Documents shall display numbered lines

iv. Logos properly displayed

v. Table of Contents

vi. References, including copies of applicable standards and regulations

vii. Glossary and acronym/abbreviation definitions

viii. Sections of the report shall be properly tabbed and organized

ix. Text on drawings and figures shall be legible

x. The draft report should be in both hard copy and CD copy in the original format (ie.

Microsoft Word, Microsoft Excel, etc) in addition to PDF format.

xi. Diagrams and drawings should be in the original, executable format (ie. AutoCAD, GIS) in addition to PDF format.

xii. Include all official Government correspondence to date, including but not limited to:

scope of work, meeting minutes, memorandums, and contract documents.

xiii. Bound in a single, durable, hard cover notebook

xiv. State and explain all assumptions.

Final reports – The reports should incorporate all items listed under “Draft reports” and include Government comments with Contractor responses

Submittal Distribution List – Deliverables shall have separate deliveries to the TPOC and

SPOC.

GIS Deliverables – The Contractor shall develop GIS compatible layers for all data collected in association with the requirements for this project. The Contractor shall submit the GIS data in accordance with the Naval District Washington Standards for

Geographic Information System (GIS) Deliverables (Appendix A). Additionally, the

Contractor shall coordinate with the installation GIS POC to ensure all data will be compatible with the NAVFAC GIS database.

Documents Required by Cooperator:

All documents referenced in this SOW or other requested documents will be provided as needed to the Cooperator for purposes of completing proposal, initiating work, or for other reasons found necessary by the NAVFAC Washington Project Manager.

10. DATA: All databases containing raw data and all associated electronic data summary and analytical files shall be formatted in Excel, Word, Dbase IV, or any compatible Microsoft database software and submitted to the TPOC and SPOC (on a CD-ROM). Microsoft ACCESS files shall include all queries, reports, tables, etc.

11. SCHEDULE: Project tasks shall be completed in accordance with the following schedule:

The period of performance shall not exceed 18 months from the signature date of this

Cooperative Agreement. No in-stream work shall take place between March 1st and June

15. Depending on the award of this Cooperative Agreement, the schedule may change accordingly.

Milestone

Cooperative Agreement Award

Kick Off Meeting

Draft Safety Plan to Navy

Draft Work Plan to Navy

Navy Comments Draft Safety Plan

Navy Comments Draft Work Plan

Final Safety Plan to Navy

Final Work Plan to Navy

Construction-Implementation Completion

Draft Report/As-Builts to Navy

Navy Review Draft Report/As-Builts inal Report/As-Builts to Navy

Date Due

CAA

CA + 10 days

CA + 20 days

CA + 20 days

CA + 25 days

CA + 25 days

CA + 30 days

CA + 30 days

CA + 210 days

CA + 270 days

CA + 285 days

CA + 300 days

Milestone

OPTION 1

Year 1 Monitoring for 85% Plant Mortality

OPTION 2

Year 2 Monitoring for 85% Plant Mortality

Date Due

1 year from signature of Option 1

Cooperative Agreement Modification

1 year from signature of Option 2

Cooperative Agreement Modification

12. DATA AND PUBLICATIONS

a. The Cooperator acknowledges that information and data gathered or received pursuant to the Agreement may have regulatory and national security significance and that the unauthorized dissemination or use of this information might prejudice the interests of the

U.S. Navy and Department of Defense. Therefore, the Cooperator agrees not to disclose or use any information or data directly or indirectly acquired through activities associated with the Agreement to any person, organization or entity who is not a party to the Agreement, and to prohibit disclosure or use of the same by the Cooperator’s personnel, representative, agents or associates unless disclosure is compelled by process of law, or the Navy authorizes disclosure or use in accordance with this Section of the Agreement. The terms “data”, “information”, “use”, and “disclose” (and its forms and derivatives) will be interpreted very broadly. Limitations on disclosure encompass all forms of dissemination including the spoken word, written word and electronic media. “Use” includes, but is no limited to, inclusion in academic papers, professional presentations and incorporation in other research not associated with the Agreement. All products, reports, filed notes, filed data forms, photographs or other information or other records or documents, including slide presentations produced using any information obtained under the Agreement are the property of the Department of the Navy.

b. The Cooperator may disclose or use data and information only with the prior written approval of the U.S. Navy and per the terms of that approval. The Cooperator will submit a written request to disclose or use information or data to the Contracting Officer (cc TPOC) explaining what information is to be disclosed or used, the reason for the disclosure or purpose for which the information or data will be used and to whom the information will be disclosed.

c. The U.S. Navy recognizes that the Cooperator may want to use information and data acquired through the Agreement in professional and academic manuscripts, publications and presentations and that such use may benefit not only those with an academic or professional interest in the information or data, but the general public as well. If authorization is given for such use, the Navy retains the right to review any manuscripts, publication or presentation in advance of publication or presentation for the purpose of ensuring the accuracy and releasability of the information or data presented. The Cooperator agrees that any manuscript, publication or presentation will include a statement as to the origin of the information or data obtained through the Agreement. Authorization for the use of information or data in one context is not to be construed as authorization for subsequent uses or purposes. The Cooperator shall submit at least two (2) hard copies of published manuscripts, and at least one (1) electronic copy of slides, and/or slide or poster presentations to the Navy, at no extra cost to the Navy.

d. Recognizing the significant technical contributions of the Cooperator and U.S. Navy

TPOC and SPOC in the development of the Agreement’s scope of work, its goals, objectives, experimental sampling design, data interpretation, review of technical reports, etc., the U.S. Navy TPOC and SPOC shall be accorded, if appropriate, joint-authorship credit for any publication of manuscript and technical presentation that is based upon the full use or partial use of the technical information, data, or interpretation of data produced under the Agreement. Appropriate joint-authorship credit means credit commensurate with the amount of work and technical contributions provided by the U.S. Navy TPOC and SPOC, and fair with reference to credit given by the primary author (Cooperator) to other joint authors of the manuscript and technical presentation. Appropriateness of joint authorship is to be determined by reference to applicable authority, for example, the code of ethics, rules, regulations, or guidance set forth by institutions or other recognized venues on the publication of manuscripts and technical presentations.

e. The Cooperator shall be responsible for ensuring all personnel, representatives, agents and associates participating in activities under the Agreement have read and acknowledged the provisions of this Section of the SOW.

13. RELEASE OF PUBLIC INFORMATION

The Cooperator shall not respond to any third party inquiries concerning the Agreement or concerning data and information obtained under the Agreement. All third party inquiries received by the Cooperator shall be directed to the Contracting Officer (thru the TPOC) for response.

14. PAYMENTS

a. The Cooperator shall request reimbursement on a monthly basis

b. Advance payments may be requested by the Cooperator. Requests for advance payment shall be submitted on SF-270, “Request for Advance or Reimbursement.” The form can be downloaded from the internet at http://www.whitehouse.gov/omb/grants/sf270.pdf .

c. The Cooperator shall maintain advances of federal funds in an interest bearing account. The

Cooperator shall remit, at least quarterly, to the Navy interest earned on advances. The

Cooperator may keep interest amounts up to $100 per year for administrative expenses. The

Cooperator shall submit a SF-272 “Federal Cash Transactions Report” along with interest earned. The form can be downloaded from the internet at http://www.whitehouse.gov/omb/grants/sf272.pdf.

d. Partial payments equal to the amount of work accomplished may be made monthly from http://www.whitehouse.gov/omb/grants/sf270.pdf http://www.whitehouse.gov/omb/grants/sf272.pdf date of award. An amount not to exceed ten (10) percent of the total Agreement funds will be withheld until the final report, electronic data, and photographic information have been received (by the TPOC) and approved by the Contracting Officer.

e. Any requirement for the payment or obligation of funds, under the terms of the

Agreement, shall be subject to the availability of appropriated funds, and no provision herein shall be interpreted to require obligation or payment of funds in violation of the Anti-

Deficiency Act, 31 U.S.C. §1341 et seq. Nothing in the Agreement shall be construed, as implying that Congress will, at a later time, appropriate funds sufficient to meet deficiencies.

f. The provisions of this Cooperative Agreement, including the requirement to remit interest earned on advances, shall be applied to sub-recipients/sub-grantees performing substantive work under the Cooperative Agreement. Sub-recipients and sub-grantees are defined below.

i. A Sub-recipient is the legal entity to which a sub-award is made and which is accountable to the recipient for the use of the funds provided.

ii. A Sub-grantee is the government or other legal entity to which a sub-grant is awarded and which is accountable to the grantee for the use of the funds provided.

iii. A sub-award is an award of financial assistance in the form of money, or property in lieu of money, made under an award by a recipient to an eligible sub-recipient or by a sub-recipient to a lower tier sub-recipient. The term includes financial assistance when provided by any legal agreement, even if the agreement is called a contract. It should be noted that sub-awards are for the performance of substantive work under awards, and are distinct from contracts for procuring goods and services.

iv. A sub-grant is an award of financial assistance in the form of money, or property in lieu of money, made under a grant by a grantee to an eligible sub-grantee. The term includes financial assistance when provided by any legal agreement, even if the agreement is called a contract. It should be noted that sub-grants are for the performance of substantive work under awards, and are distinct from contracts for procuring goods and services.

15. GEOGRAPHIC INFORMATION SYSTEM (GIS) DELIVERABLES

a. Mapping requirements:

i. All GIS data must adhere to the standards in Appendix A and the requirements listed here.

ii. Construction drawing deliverables shall be reviewed for accuracy and completeness by a NFWASH GIS POC before acceptance.

iii. Where possible, the Cooperator will utilize source GIS data provided by NAVFAC

Washington.

a) A completed NAVFAC Washington GIS data release form is required.

b) The Cooperator shall be provided a copy of any GIS data required meeting mapping deliverables in ESRI format (TBD shapefile or Personal Geodatabase).

That data shall be structured according to the current version of the Spatial Data

Standards (SDSFIE) in use by NAVFAC (version 2.6 as of October 010), and all data shall be returned in this format and structure.

c) The GIS data provided shall be extracted from the Navy’s GIS data Maintenance and Analysis (M&A) environment. This copy of the data will include existing populated layers, and non-populated layers. The non-populated layers are provided to ensure the data is returned in the required NAVFAC Washington GIS data model structure.

iv. The Cooperator shall consult with the government GIS POC before populating the attribute tables to ensure the population matches the current NDW interpretation of the SDSFIE. Layer-level metadata updates are required for all updated or new layer deliverables and the Cooperator shall consult with the government GIS POC to identify the specific metadata content requirements.

b. GIS Deliverable Requirements:

i. Format is to be determined by the government project manager and the Cooperator project manager.

a) The GIS deliverable shall delivered on disc (CD-ROM or DVD) to the government for Quality Assurance (QA), and the government will have two weeks to QA the data and then the Cooperator will have two weeks to make any corrections and produce the final deliverable.

or:

b) The Cooperator will be required to deliver a copy of all data into the appropriate geodatabase schema within the NDW GeoRepository, located in the Maintenance and Analysis environment (accessible via web access and Citrix). All data will be placed into a geodatabase editing version for government review, before acceptance and publishing. All completed and published data will be recorded in the NDW tracking table located in the M&A environment.

ii. Reporting: The Cooperator shall provide a document (Microsoft Word format) that lists all layers developed or updated for the task.

iii. Maps: In addition to any hardcopy or softcopy maps delivered, all source map files

(ESRI ArcGIS (mxd)) for these maps shall be provided to the government.

APPENDIX : A

NAVFAC Washington - Procedures and Specifications for Geographic Information System

(GIS) Deliverables:

1. Overview:

The GeoReadiness Center (GRC) is the single, authoritative source and distribution point for all geospatial shore installation data within the NDW region. The GRC houses the most current geospatial information for the entire NDW region and provides access to the comprehensive data set and analysis tools to Regional and DOD decision makers/managers, sponsored contractors, and other sponsored individuals via a secure government Internet site.

2. Basic Requirements:

a. Submittals, Government Review and Acceptance:

i. All submittals shall be reviewed for structure and adherence to the required standards by an NDW GeoReadiness Program GIS Analyst before acceptance.

1. Review for accuracy and completeness according to the scope of work is the responsibility of the Project Manager or other designated subject matter expert personnel. NDW GeoReadiness, as part of the NAVFAC Asset Management Business Line, is not responsible for the accuracy and completeness of data acquired by other NAVFAC Business Lines, Navy organizations and commands.

ii. The government shall have two weeks to assess the submittal; the contractor shall then have two weeks to make any corrections and submit the final deliverable.

iii. All source code (ex. Python scripts, html files) and map files (ESRI

ArcGIS (mxd)) shall be provided to the government.

iv. Failure to adhere to any of the stated delivery specifications could result in rejection of deliverables and nonpayment.

v. Contractors should, at a minimum, submit data and documentation samples at 25% and 75% project completion to avoid the rejection of final deliverables.

b. Data Retention: All data (electronic and paper formats) must be removed from the contractor’s site and returned to the government at the end of the task order period of performance and before the final invoice is approved.

c. Data Structure:

i. Unless specifically directed otherwise, all data shall be structured according to the current version of the Spatial Data Standards (SDSFIE) in use by NAVFAC. A copy of the current data model implementation

(specific GIS layers and any required associated tables) shall be provided to the contractor.

ii. If new data is being created and the corresponding data structure does

NOT yet exist, the contractor shall provide the GRC with a data dictionary identifying all of the SDSFIE Entity Types, attributes, and/or domain values associated with the new feature(s), the geographic area(s) covered by the data and Spatial extent information prior to the creation/editing of

GIS data. Acceptable formats: MS Excel or MS Word. Adobe PDF is not an acceptable format. New non-SDS compliant attributes (meeting

SDSFIE criteria) will require precise schema definitions.

d. Government Source Data:

i. The contractor shall be provided a copy of any GIS data required for the project from the government repository in an ESRI format.

ii. All data shall be returned in this format and structure unless the government specifies otherwise.

iii. A completed NAVFAC Washington GIS Data Release form is required prior to data being released to the contractor.

iv. NDW GIS data shall only be released by, or with the written concurrence of NDW GeoReadiness personnel.

e. Attribute Population:

i. The contractor shall consult with the government GIS POC before populating attribute tables to ensure the results match the current

NFWASH interpretation of the SDSFIE.

ii. The contractor shall identify the classification, type, location, ID number, and any other necessary attributes (specified by the Government) for all new/updated/edited features.

f. GIS Data Format: NAVFAC’s GIS data is ERSI Geodatabase format, version

10.3.1 as of October 2016. Unless specified otherwise by NDW GeoReadiness, all ESRI format data submittals must also be in a version compatible with 10.3.1.

Submittal format shall be determined by the government project manager and the contractor project manager.

3. CAD Format Deliverables:

a. CAD drawings may be accepted as GIS deliverables, but only when specified as such in the scope of work.

b. All files must be accurately georeferenced and adhere to the requirements regarding the coordinate system, metadata, and the specified data Quality Control and Quality Assurance requirements.

c. The government shall specify whether files are to adhere to either the SDSFIE or

A/E/C CAD standard.

4. Coordinate System and Projection:

All geospatial data, unless specified otherwise, shall be in the delivered in:

NAD_1983_StatePlane_Maryland_FIPS_1900_Feet

Projection: Lambert_Conformal_Conic

5. Metadata:

a. Feature Level Metadata: Feature-level (record level) attribute metadata is required to be populated for each GIS feature/record, per the current SDSFIE version.

Attributes for version 3.01 are:

i. Name: editor

1. Description: Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, Jane Smith would be attributed as SmithJ.

2. Data Type: String (20)

ii. Name: dateEdited

1. Description: Date that the feature was edited from its original or previous value.

2. Data Type: Date

iii. Name: collectionSource

1. Description: Describes how the data was collected and verified.

(Example: GPS Field Collected – Mapping Grade).

2. Data Type: String (75)

3. Domain: CollectionSource

iv. Name: locAccy

1. Description: Describes the location accuracy of the data that was collected and verified.

2. Data Type: String (50)

v. Name: metaNotes (** use only if needed)

1. Description: Describes other details about what was created or edited and why.

2. Data Type: String (255)

b. Layer Level Metadata: Layer level metadata is required for all deliverables, structured according to the FGDC Content Standard for Digital Geospatial Data

(CSDGM). Details on the standard can be found at http://www.fgdc.gov/metadata/geospatial-metadata-standards.

These elements are to be populated within the Description tab in ArcCatalog:

Under Overview -> Item Description section

i. Title: Current SDS version layer name

ii. Credits: Contract #, Task Order Title, Company Name

iii. Description (Abstract): SDS 3.0 layer definition http://www.fgdc.gov/metadata/geospatial-metadata-standards

iv. Summary (Purpose): Describe briefly in simple terms, methods used to acquire the data and populate the GIS layer.

1. Example: “This data was received in various formats which included ESRI Shapefile, ESRI Coverage, and AutoCAD format.

The data was converted to ESRI Personal Geodatabase format for the analysis, translation, and QA processes, and copied into an

ESRI Enterprise Geodatabase (Oracle) as the final step.

2. Example: “Wetlands Delineation collected via GPS, imported to an ESRI File GeoDatabase where additional attributes were populated”

v. Use Limitation: “For Official Use Only”

Under Overview -> Topics Keywords section

vi. Content Type: Change to Map Files

vii. Theme Keywords: Common feature name, current version SDS Layer name and Data Set name.

viii. Place Keywords: Region, NAVFAC Washington, all applicable site names. Example; Naval District Washington, NAVFAC Washington, Indian Head, Stump Neck

Under Overview -> Citation section

ix. Dates Published: Final deliverable date, after gov’t QA & Acceptance

Under Resources -> References

x. Aggregate Information: Populate if applicable for derived data;

information about omissions, selection criteria, generalization, definitions used, and other rules used to derive the data set.

6. Quality Control and Quality Assurance:

The contractor shall take all appropriate and needed QA/QC measures to ensure that data is complete, topologically correct, accurate, structured correctly, and formatted correctly per the scope of work and complete (to include):

a. **All data shall be visually inspected by the contractor before submittal to the government.**

b. The contractor shall add an attribute text field named “QA” to all GIS layer deliverables, and populate each with “Add”, “Modify”, or “Delete” as appropriate. This is necessary for the government to accurately and quickly evaluate the work.

c. The numbers of records for all joined tables shall match, or the specific unmatched records shall be identified and explained to the satisfaction of the government.

d. All required attributes (per SDSFIE version 3.01) shall be populated.

e. All domain constraints shall be adhered to, unless approved by the government, prior to submittal.

f. No erroneous overshoots, undershoots, dangles or intersections in the line work.

g. All area type features shall be closed polygons.

h. Line features shall be snapped together where appropriate to support networks.

For example, do not break linear features for labeling or other aesthetic purposes.

i. Lines shall be continuous and point features shall be digitized as points. For example, point features, such as manholes, shall not be drawn using only a circle

(polygon) to represent its location.

j. No sliver polygons

k. Digital representation of the common boundaries for all graphic features must be coincident, regardless of feature layer

l. Geometric network connectivity shall be maintained for utility networks, where specified by the scope of work.

7. Field Collection

a. Where field data collection is stipulated in the contract, the contractor shall utilize conventional and other methods, such as a total station, or Global Positioning

System (GPS) in accordance with the applicable Geospatial Positioning Accuracy

Standards published by the Federal Geographic Data Committee (FGDC).

b. At a minimum, the contractor shall provide, resource grade GPS collection at an accuracy level of +/- < 1m and shall use differential correction to target accuracies of +/- .5 m.

c. Where appropriate (as stipulated in the contract or as otherwise determined by the

Government), the contractor shall use survey grade GPS, at an accuracy level of

+/- 2 cm. Global Positioning System (GPS) data collection activities will be based on a post-processed environment using an accurately sighted base station. Base station files for post processing acquired locally (off-site CORS Continuous

Operating Reference Station) will be verified for accuracy.

d. GPS data on the location of utility lines and other features shall be captured at a minimum every 50ft and at each turn or bend in the line and processed as a line feature type. GPS data on the location of utility points and other features shall be captured at the centroid of the feature unless signal obstruction or access prohibits; otherwise points will be captured at a uniform distance and direction from the centroid and the offset captured in the metadata for that feature.