Attachment D_PWS Sea Turtle Nesting Beach Monitoring and Nest Protection on Naval Base Guam_17APRIL2023.pdf

PERFORMANCE WORK STATEMENT (PWS)

SEA TURTLE NESTING BEACH MONITORING AND NEST PROTECTION

AT NAVAL BASE GUAM

04/17/2023

SECTION 1.0 GENERAL

This performance work statement solicits services for performing field surveys to monitor sea turtle nesting activity, nest protection, monitor lizard control, invasive species removal, beach profiling, and invasive vegetation removal at beaches with suitable habitat for nesting sea turtles managed by Naval Base Guam (NBG). Services shall be performed as outlined below. The duration of work under this contract shall not exceed 14 months from the award date, with an option to extend for an additional one year upon availability of funds. This action will be performed in accordance with all appropriate regulations, statues, and laws, including the Endangered Species Act (ESA; 16 USC 1531 et seq.), Sikes Act (16 U.S. Code 670a et seq.), 5 Guam Code Annotated CH.63 Fish, Game, Forestry & Conservation, and Executive Order 13751 Safeguarding the Nation From the Impacts of Invasive Species. Naval Facilities Engineering Command, Marianas will administer this single award basic contract. All work must be performed following applicable and appropriate Department of Defense (DOD) guidance and policy for Sea Turtle Population Protection and Enhancement under the Terrestrial Protected Species management program (2021 JRM INRMP Update) and consider all site documentation and reports to date.

Under this PWS, the following services will be required:

- Locate, protect, and evaluation 100% of sea turtle nests at NBG

- Collect and maintain data on nest success, emergence success, and depredation

- Monitor long-term trends of spatial and temporal distribution of sea turtle nesting activity

- Manually remove invasive vegetation at Spanish Steps beaches

- Control monitor lizards at nesting beaches

- Protect nests

- Conduct beach profiling

- Prepare final report

1.1. PRIMARY OBJECTIVE

1.1.1. The primary objective of this project is to provide monitoring and protection of sea turtles nests to maintain habitat and improve nesting success at Naval Base Guam (Figure 1). The project scope shall include all of the necessary labor and equipment associated with meeting the objective. The Period of Performance is not to exceed 14 months after contract award, with an option to extend for an additional one year upon availability of funds.

1.1.2. The KTR shall obtain final approval of the work required by the Naval Facilities Engineering Command upon completion of these performance objectives as specified in SECTION 7.0

PERFORMANCE MEASUREMENT AND PAYMENT SUMMARY AND OFFER SCHEDULE.

1.2. BACKGROUND

1.2.1. Under this PWS, eight NBG-managed beaches with suitable habitat for nesting sea turtles shall be surveyed (Figure 1). Three beaches have documented nesting activity: Dadi, Spanish Steps and Family Beach. Five beaches have no documented nesting activity: Gab Gab, Polaris Point, San Luis, Tipilao and Reserve Craft Beach. All eight beaches to be surveyed are located within a 3 mile radius. The approximate length of each beach is listed in Table 1.

The entire length of any and all possible sea turtle nesting beaches to be surveyed under this PWS is approximately less than two miles. The total time to survey all eight beaches at once is approximately eight hours.

Figure 1. Location of NBG-managed beaches to be monitored under this PWS.

Family Beach

Reserve Craft Beach

Polaris Point San Luis Gab Gab

Spanish Steps

Tipalao

Dadi

Table 1. Beach location and approximate length (mi).

Survey Location Approximate Length (mi) Figure No.

Family Beach 0.1 Figure 2 Reserve Craft Beach 0.1 Figure 3 Polaris Point 0.17 Figure 4 San Luis 0.1 Figure 5 Gab Gab 0.32 Figure 6 Spanish Steps 0.23 Figure 7 Tipilao 0.21 Figure 8 Dadi Beach 0.6 Figure 9

Figure 2. Family Beach (yellow polygon) along Highway 11.

Figure 3. Reserve Craft Beach (yellow polygon) off Highway 18.

Figure 4. Polaris Point Beach (yellow polygon) at Polaris Point.

Figure 5. San Luis Beach (yellow polygon) west of Clipper's Landing.

Figure 6. Gab Gab Beaches 1 and 2 (yellow and pink polygons, respectively) west of San Luis Beach.

Figure 7. Spanish Steps Beaches 1, 2, 3, and 4 (yellow, pink, blue, orange, and blue polygons, respectively) west of Kilo Wharf.

Figure 8. Tipalao Beach (yellow polygon) on the south side of Orote Peninsula.

Figure 9. Dadi Beach (yellow polygon) south of Tipalao Beach.

1.2.2. Four species of sea turtles have been historically observed in waters around Guam: (1) Green sea turtle (Chelonia mydas), (2) Hawksbill sea turtle (Eretmochelys imbricata), (3) Leatherback sea turtle (Dermochelys coriacea), and (4) Olive Ridley sea turtle (Lepidochelys olivacea). Recently, only the Green and Hawksbill sea turtles have been documented nesting and foraging in nearshore neritic waters of Guam. The Central West Pacific population of green turtles was listed as “endangered” in 2016; hawksbill sea turtles are listed as endangered on Guam.

1.2.3. Green turtles occur throughout Micronesia and are the most abundant sea turtle found in the waters around Guam and throughout the Marianas archipelago. Population abundances for sea turtles on Guam are estimated using data from aerial surveys, dive depth studies, and species composition. The proportion of green turtles in the population was found to be 85%, while that of hawksbills was 15%.

1.2.4. In order to assure compliance with laws, regulations, policies, and executive orders governing sea turtles, beaches on NBG continue to be monitored for nesting activity. The monitoring program and collection of data are utilized to assure compliance for all training activities and construction projects, evaluate effectiveness to protect and recover sea turtles, and develop strategies for managing natural resources on NBG.

SECTION 2.0 WORK ELEMENTS

The contractor shall furnish all labor, materials, tools, supplies, services, equipment, project management, permits, and contract/procurement administration necessary to perform all work in accordance with the PWS. The contractor shall conduct all work in accordance with all pertinent state, local and federal regulations and accepted work plans. The contractor’s work areas and activities at the site shall be subject to inspection without announcement by the Navy. The

Contractor’s proposal should be presented in a format that addresses each work element required for successful completion of the project objectives.

The estimate should include the following Work Elements:

- WORK ELEMENT 1 – PROJECT MANAGEMENT

- WORK ELEMENT 2: PROJECT PLANS

- WORK ELEMENT 3: FIELDWORK

- WORK ELEMENT 4 – RECORDS AND REPORTS

2.1. WORK ELEMENT 1 – PROJECT MANAGEMENT

2.1.1. The KTR shall manage the project in accordance with SECTION 6.0 DELIVERABLES.

2.1.2. Task 1: Kick-off Meeting. The KTR shall organize a kick-off meeting in accordance with

SECTION 6.0 DELIBERABLES. If base access is not approved prior to the kick-off meeting, the meeting may be offsite or virtual via Microsoft Teams. The Kick-off Meeting agenda shall include KTR personnel, PWS work elements, fieldwork schedule, plan of action and milestones (POAM). The KTR shall provide Kick-off Meeting Minutes in accordance with

SECTION 6.0 DELIVERABLES.

2.2. WORK ELEMENT 2 – PROJECT PLANS

2.2.1. Task 1: Permit. The KTR shall provide a copy of a proper permit from the U.S. Fish and

Wildlife Service to conduct all activities to meet the objectives and work elements in this PWS, in accordance with SECTION 6.0 DELIVERABLES. Per the permit, the qualified field biologist (Biologist) should be authorized to independently conduct project activities for the green and hawksbill sea turtles at geographic areas to include the U.S. Department of the Navy – Naval Facilities Engineering Command Joint Region Marianas (JRM) managed lands on Guam.

2.2.2. Task 2: Accident Prevention Plan. The KTR shall develop and submit an Accident Prevention Plan (APP) with an Activity Hazard Analysis (AHA) as an appendix, in accordance with SECTION 6.0 DELIVERABLES. The APP shall be developed in the format provided in Appendix A of the EM385-1-1 (30 Nov 2014) US Army Corps of Engineers Safety and Health Requirements Manual for the “Abbreviated APP for Limited Scope Service, Supply and R&D contracts.” The KTR shall certify to the TPOC and COR that the final APP has been reviewed with each KTR’s and sub-KTR’s employees prior to mobilization and start of fieldwork activities.

2.3. WORK ELEMENT 3 – FIELDWORK

2.3.1. Task 1: Field Surveys. The KTR shall begin Field Surveys within two days of approval to begin work. Survey frequency per beach is listed in Table 2 below. (Note: Nesting and non-nesting seasons are typically from March to August and September to February, respectively.) All field data shall be recorded in the appropriate forms (Appendices A and B). The Biologist shall conduct field methods and collect data in accordance with USFWS Recovery permit TE- 42195A-2 for Joint Region Marianas and the Standard Research Protocols for Nesting Marine Turtles in the Pacific Islands Region. Surveys should be conducted during low tides.

When nesting activities are observed, the Biologist shall determine if the activity is a nest or non-nesting emergence, photograph the occurrence, record its GPS location (3-m accuracy), determine turtle species, and record any observations indicating nest disturbance (e.g. poaching, predators, vehicle tracks, storm erosion). Nest inventories shall be conducted after hatchling emergence (or after 70 days of incubation) to determine clutch size, hatching success, and nesting success.

Table 2. Survey frequency at each beach site on NBG.

Survey Location Survey Frequency Survey Period Spanish Steps (includes 4 beaches) Dadi Beach

(a) Once per week (a) During nesting season or when there are active nests or nesting activity

(b) Every other week (b) Non-nesting season or when there are no active nests or nesting activity

Gab Gab San Luis Tipalao Family Beach Polaris Point Reserve Craft Beach

(a) Once a week (a) When there are active nests or nesting activity (until the nest has hatched)

(b) Every two weeks (b) When there are no active nests or nesting activities

2.3.2. Task 2: Nest Protection. Each encountered nest shall be protected while allowing hatchlings to escape the nest. The nest protection measure shall be proposed by the KTR and accepted by the TPOC. The KTR shall monitor for evidence of predation and disturbance at protected nests with trail cameras. The Government shall provide ten trail cameras and ten SD memory cards to the KTR, who shall return the supplies at the end of the contract period.

The use of ten trail cameras shall be maximized, with at least one trail camera at Dadi Beach if nest activity is observed. The KTR shall review trail camera footage to provide an accurate record on predator type, predation time, and location of nest.

2.3.3. Task 3: Beach Profiling. KTR shall conduct beach profiling at one location on a monthly basis.

The TPOC will advise which beach to conduct profiling. The Emory method, or equivalent method recommended by the KTR and accepted by the TPOC, shall be used. KTR shall develop and use a Beach Profile Log Sheet to record collected data. At minimum, the data collected shall include the team members; date; start time; end time; horizon visibility (scale); general beach condition; beach name; sand elevation at starting point; vertical and horizontal measurements. All data recorded in the Beach Profile Log Sheets shall be transferred and maintained in an Excel spreadsheet (.xlsx).

2.4. WORK ELEMENT 4 – RECORDS AND REPORTS

2.4.1. Task 1: Field Data Sheets. The KTR shall submit field data sheets, including the Sea Turtle

Nest Activity Sheet (APPENDIX A) and Sea Turtle Nest Inventory Sheet (APPENDIX B), in accordance with SECTION 6.0 DELIVERABLES. All field data sheets shall be combined as a single PDF, sorted by beach, nest ID, Nest Activity Sheet, Nest Inventory Sheet. The single, combined PDF shall be added as an Appendix to the Final Report.

2.4.2. Task 2: Beach Profile Log Sheets. All Beach Profiling Log Sheets shall be submitted to the TPOC as a single, combined PDF, in accordance with SECTION 6.0 DELIVERABLES. The Log Sheets shall be sorted by beach, then nest ID, then Nest Activity Sheet, then Nest Inventory Sheet. The single, combined PDF shall be added as an Appendix to the Final Report.

2.4.3. Task 3: Photographs (upon camera pass approval). The KTR shall submit photographs that document work elements to the TPOC in accordance with SECTION 6.0 DELIVERABLES. Title and all rights associated with use of the photographs shall be with the Government.

The KTR shall submit photographs of each beach surveyed. The intent of the photos are to document the survey.

At least two digital, colored photographs shall be submitted with Monthly Reports, which shall document field activities performed during the prior month. (Note: KTR shall provide visual evidence of field surveys at each survey location, with or without nest activity).

Photographs shall be a minimum of 4 x 6 inches with high resolution.

Digital Photographs. All digital photographs shall be submitted in accordance with SECTION

6.0 DELIVERABLES. The images shall be provided as individual JPEGs in an electronic folder.

The file name shall include a date and identifying location, including nest ID when applicable.

Photograph Log. The photographs shall also be combined into a single PDF and submitted in accordance with SECTION 6.0 DELIVERABLES. All photographs shall be uniform in height, width, and quality. Each PDF page shall contain no more than four photographs. The single PDF of photographs shall be submitted as an Appendix to the Final Report.

2.4.4. Task 4: Progress Reports. The KTR shall submit a monthly Progress Report in accordance with SECTION 6.0 DELIVERABLES. The Progress Report template shall include summary data, maps of nest activity, and photographs. The template shall be developed by the KTR and accepted by the TPOC. Each Progress Report shall contain cumulative data, including current and prior reporting periods.

2.4.5. Task 5: Data Workbook. The KTR shall submit a monthly Data Workbook in accordance with SECTION 6.0 DELIVERABLES. The Workbook shall contain all information collected on the Sea Turtle Nest Activity Sheet, Sea Turtle Nest Inventory Sheet, and Beach Profile Log Sheet.

The Workbook shall be developed by the KTR and shall be accepted by the TPOC.

2.4.6. Task 6: FINAL Database. The DRAFT Final Database shall be submitted in accordance SECTION 6.0 DELIVERABLES. The DRAFT Final Database shall contain all data collected during the contract period, including all data in the monthly Data Workbook. The DRAFT Final Database shall contain a sheet that defines all data fields within the Workbook.

The FINAL Database shall incorporate all Government comments, then be submitted to the TPOC in accordance with the deliverables schedule.

2.4.7. Task 7: FINAL Report. The KTR shall submit a DRAFT Final Report in accordance with SECTION 6.0 DELIVERABLES. The DRAFT Final Report shall include current and prior year data in the DRAFT Final Report. The DRAFT Final Report shall be clear, concise, accurate, and well organized with sections, including Abstract, Background, Methods, Results, Discussion and Recommendations. The Discussion shall present an in-depth analysis of the results by incorporating current studies and prior year reports. Recommendations shall include informative actions in support of protecting sea turtles, maintaining habitat, and improving nesting success. The DRAFT Final Report shall include summary tables, figures, and maps that contain current and prior year data. The DRAFT Final Report shall include annual maps that depict nest activity, predation, and inundation at beaches with nesting activity. The Appendices shall include Beach Profile Log Sheets, Field Data Sheets, Photo Repository, and Permits.

The FINAL Report shall incorporate all Government comments, then be submitted to the TPOC in accordance with the deliverables schedule. If comments are not addressed without justification, the FINAL Report will be rejected by the TPOC.

2.4.8. Task 8: Geospatial Information System Data. The KTR shall submit all Geospatial Information Systems in accordance with the deliverables schedule. GIS Data shall adhere to the Geospatial Information Service Requirements (APPENDIX C).

SECTION 3.0 SPECIAL REQUIREMENTS/CONDITIONS

3.1. Base Access. The KTR shall submit all required forms and documentation to request for base access for project personnel, in accordance with SECTION 6.0 DELIVERABLES.

3.2. Camera Pass. The KTR shall submit all required forms and documentation to request for base access for project personnel, in accordance with SECTION 6.0 DELIVERABLES.

3.3. Project Management. The KTR shall meet the following standards and expectations:

3.3.1. The KTR shall provide project oversight and coordination for all associated tasks; maintain budget coordination, tracking, and reporting.

3.3.2. The KTR shall submit Progress Reports in electronic format to the TPOC/COR via email, in accordance with SECTION 6.0 DELIVERABLES.

3.3.3. The KTR shall submit a properly-prepared monthly invoice in electronic format to the TPOC/COR via email, with the submission of each Progress Report.

3.3.4. The KTR shall immediately notify (i.e. within 24 hours) the COR/TPOC of any problems that prevent the scheduled field work; weather conditions, equipment failures, and site conditions can create unforeseen unsafe working conditions. Any problems or concerns encountered at the field sites shall be immediately reported (i.e. within 24 hours) to the

COR/TPOC.

3.4. Quality of Submissions. The KTR shall be responsible for the professional quality and technical accuracy of all work submitted under this contract.

3.4.1. Reports shall be free of typographical errors, grammatical errors, inappropriate “cut and paste” inserts, formatting inconsistencies, and incorrectly labeled tables and figures.

Reports shall provide proper citations for all documents referenced. If, during Government review, more than five of such errors are found, the document will be rejected.

3.4.2. The KTR shall, without additional compensation, correct or revise any errors or deficiencies in its work product and other services that do not meet professional standards. The standard of care required is that the KTR must exercise the necessary degree of skill, ability and judgment that is expected of a member of the profession acting under similar circumstances at the national level.

3.4.3. The KTR shall submit high quality photographs. The KTR shall ensure the graphic, figure, or table matches are accurate. The charts and figure shall match the data recorded in the database.

3.5. External Communication. The KTR shall not make direct contact (e.g. e-mail, phone calls) with any other individuals, commands, military activities, and or regulatory agencies without prior notification and approval by the Government.

3.6. Licensing and Ownership Rights. All technical and scientific data, including but not limited to source files, text files, photographic content, GIS data, and other content developed by the KTR are contemplated to be developed with Government funding and not Private funding. The KTR shall provide all such technical data and computer software deliverables with Unlimited Rights.

SECTION 4.0 GOVERNMENT FURNISHED EQUIPMENT/DATA

4.1. The Government will furnish the following documents:

4.1.1. Prior Year Reports

4.1.2. Prior Year Data

4.2. Aside from response to requests for information, comments on submittals, or other information as described herein, the Government does not intend to furnish additional information. All information gathering is the responsibility of the KTR.

4.3. The Government will not furnish any equipment or facilities for KTR use during this effort. The KTR shall provide the necessary hardware, software, GPS device, personnel, materials, and facilities to perform all work elements specified by this PWS.

SECTION 5.0 POINTS OF CONTACTS

5.1. Technical Point of Contact (TPOC)

Anjelica Perez Natural Resources Specialist, NAVFAC Marianas Public Works Department, Naval Base Guam 671-339-7281 Anjelicaclaire.u.perez.civ@us.navy.mil

5.2. Contracting Officer Representative (COR)

Maria (MarLo) Santos Natural Resources Specialist, NAVFAC Marianas 671-339-5148 Maria.l.santos34.civ@us.navy.mil

5.3. Contract Specialist

Jerica Santos Contract Specialist, NAVFAC Marianas Contracts Support Line, EV Contract Office 671-333-2623 Jerica.a.santos.civ@us.navy.mil

SECTION 6.0 DELIVERABLES

Item Deliverable PWS Reference Paragraph File Type Quantity Due Date

Section 2.1 WORK ELEMENT 1 – PROJECT MANAGEMENT

1 Kick-off Meeting Section 2.1.2 .pdf 1 Within 5 business days of contract award

2 Plan of Action and Milestones

Section 2.1.2 .pdf 1 Within 5 business days of contract award

3 Kick-off Meeting Minutes

Section 2.1.2 .pdf 1 Within 2 days of the kick-off meeting

SECTION 2.2 WORK ELEMENT 2 - PROJECT PLANS

4 Permit (USFWS) Section 2.2.1 .pdf 1 Within 5 days of contract award mailto:Anjelicaclaire.u.perez.civ@us.navy.mil mailto:Maria.l.santos34.civ@us.navy.mil mailto:Jerica.a.santos.civ@us.navy.mil

Item Deliverable PWS Reference Paragraph File Type Quantity Due Date

5 Accident Prevention Plan

Section 2.2.2 .docx .pdf

1 Within 5 business days of contract award

6 Activity Hazard Analysis

Section 2.2.2 .docx .pdf

1 Within 5 business days of contract award

Section 2.4 WORK ELEMENT 4 – RECORDS AND REPORTS 7 Field Data Sheets

(combined PDF) Section 2.4.1 .pdf 1 13 months after contract award 8 Beach Profile Log

Sheets (combined

PDF)

Section 2.4.2 .pdf 1 13 months after contract award

9 Digital Photographs (electronic Folder)

Section 2.4.3 .jpg 1 13 months after contract award

10 Photograph Log (combined PDF)

Section 2.4.3 .pdf 1 With DRAFT and FINAL Report

11 Progress Reports Section 2.4.4 .pdf 1 10th day following the reporting month

12 Data Workbook Section 2.4.5 .xlsx 1 10th day following the reporting month

13 DRAFT Final Database Section 2.4.6 .xlsx 1 13 months following contract award

14 FINAL Database Section 2.4.6 .xlsx 1 Within two weeks from receipt of comments

15 DRAFT Final Report Section 2.4.7 .docx .pdf

1 13 months after contract award

16 FINAL Report Section 2.4.7 .pdf .docx

2 Within two weeks from receipt of comments

17 GIS Data Section 2.4.8 REF:

APPENDIX

C

1 13 months after contract award

SECTION 3.0 SPECIAL REQUIREMENTS/CONDITIONS

18 Base Access Forms Section 3.1 .pdf 1 Within 2 business days of receipt of required forms

19 Camera Pass Forms Section 3.2 .pdf 1 Within 2 business days of receipt of required forms

SECTION 7.0 PERFORMANCE MEASUREMENT AND PAYMENT SUMMARY AND OFFER SCHEDULE

7.1. The contractor shall be responsible for achieving the performance objectives in this PWS and successfully performing all the tasks required for successful performance.

7.2. Payments shall be made to the contractor upon completion of the following:

- Verification that the corresponding performance standards and Acceptable Quality Levels defined below have been satisfactorily achieved, and

- Submission of a properly prepared invoice. Invoices that fail to meet the requirements of this paragraph and/or the invoicing or prompt payment clauses of the contract may be rejected in their entirety.

7.2.1. If a task associated with a work element is eliminated or not necessary for accomplishing project completion, the contract shall be modified and the payment amount associated with that task shall not be paid to contractor.

7.2.2. Failure to demonstrate that the performance objectives are achieved and the work elements are complete may result in non-payment of the final work element and/or a negative evaluation.

Work Element / Task Performance Standard

Acceptable Quality Level (AQL) Assessment Method

Performance Payment and Incentive

SECTION 2.1

WORK ELEMENT

1 – PROJECT

MANAGEMENT

(1) KTR schedules and facilitates a Kick-off Meeting

(2) KTR provides Kick-off Meeting Agenda prior to meeting

(3) KTR submits accurate and detailed Kick-off Meeting Minutes

(4) KTR submits Plan of Action and Milestones (POAM) that incorporates all work elements and deliverables

100% Navy acceptance

(1) Review of Kick-off Meeting Agenda;

Navy acceptance by

COR

(2) Review of Kick-off Meeting Minutes;

Navy acceptance by

COR

(3) Review of POAM;

Navy acceptance by

COR

• Lump sum payable as a percentage of completion of each deliverable under this Work Element.

SECTION 2.2

WORK ELEMENT

2 – PROJECT

PLANS

(1) KTR submits copy of U.S. Fish and Wildlife permit

(2) KTR submits Accident Prevention Plan (APP)

(3) KTR submits Activity Hazard Analysis

(AHA)

• Biologist possesses proper permit

• 100% Navy acceptance

(1) Review of permit;

Navy acceptance by

COR

(2) Review of APP; Navy acceptance by COR

(3) Review of AHA; Navy acceptance by COR

• Lump sum payable as a percentage of completion of each deliverable under this Work Element.

SECTION 2.3

WORK ELEMENT

3 – FIELDWORK

(1) KTR performs field surveys at all beaches in accordance with Table 2

(2) KTR protects all nests observed

(3) KTR monitors for nest predation and disturbance

(4) KTR conducts beach profiling at one location on a monthly-basis

100% Navy acceptance

(1) Announced and unannounced field inspections.

(2) Review of data/photos in all submissions; Navy acceptance by COR

(3) Review of Beach Profile Log Sheets;

Navy acceptance by

COR.

• Lump sum payable as a percentage of completion of each task under this Work Element.

Work Element / Task Performance Standard

Acceptable Quality Level (AQL) Assessment Method

Performance Payment and Incentive

SECTION 2.4

WORK ELEMENT

4 – RECORDS

AND REPORTS

(1) KTR submissions are free from major deficiencies: missing information as specified in the PWS

(2) KTR submissions are free from minor deficiencies:

typographical errors;

grammatical errors;

inappropriate “cut and paste” inserts;

formatting inconsistences; and incorrectly labeled tables and figures

(3) KTR submissions are professional quality and technically accurate

(4) KTR submissions are well-organized, well-written, coherent, cohesive, and can be comprehended by the general public

(5) KTR submissions contain accurate and consistent data

(6) KTR photographs are high-quality images

100% Navy acceptance

(1) Review of all KTR report submissions;

Navy acceptance by

COR

(2) Review of all KTR data, tables, figures, maps; Navy acceptance by COR

(3) Review of GIS data;

Navy acceptance by

COR

(4) No major deficiencies in each KTR submission;

Navy acceptance by

COR

(5) No more than five minor deficiencies in each KTR submission; Navy acceptance by COR

(6) Review of photographs; Navy acceptance by COR

• Lump sum payable as a percentage of completion through submission of each deliverable to Navy with the following milestone limits in the payment schedule:

- 50% of the proposed task cost upon submission of monthly Progress Reports and monthly Data Workbooks

- 30% of the proposed task cost upon submission of the DRAFT Database and DRAFT Report

- 20% of the proposed task cost upon acceptance of the FINAL Database and FINAL Report

SECTION 8.0 REFERENCES

8.1. Endangered Species Act (ESA; 16 USC 1531 et seq.)

8.2. 5 Guam Code Annotated CH.63 Fish, Game, Forestry & Conservation

8.3. Executive Order 13751 Safeguarding the Nation From the Impacts of Invasive Species

8.4. Joint Region Marianas Integrated Natural Resources Management Plan, Update May 2022

8.5. USFWS Recovery permit TE-42195A-2 for Joint Region Marianas

8.6. Standard Research Protocols for Nesting Marine Turtles in the Pacific Islands Region

8.7. EM385-1-1 US Army Corps of Engineers Safety and Health Requirements, 30 Nov 2014

SECTION 9.0 APPENDICES

9.1. Appendix A: Sea Turtle Nest Activity Form

9.2. Appendix B: Sea Turtle Nest Inventory Form

9.3. Appendix C: Geospatial Information Service Requirements

Appendix A Sea Turtle Nest Activity Form

Nest ID Site Biologist Date Time

☐ Activity ☐ No activity GPS Location ☐ Nesting ☐ False crawl UTM N - 55 P

Nest ID Age of Crawl (days) Track width (cm) Habitat

Comments

Site Survey Date Observer Start Time Weather Conditions End Time

☐ Activity ☐ No activity GPS Location ☐ Nesting ☐ False crawl UTM N - 55 P

Nest ID Age of Crawl Track width (cm) Habitat

Comments

Appendix B Sea Turtle Nest Inventory Form

Sea Turtle Nest Inventory Form Sea Turtle Nest Inventory Form

Nest ID Nest ID

Date Nest Observed Date Nest Observed

Nest Protected with Screen ☐ Yes ☐ No Nest Protected with Screen ☐ Yes ☐ No

Site Site Date Date Biologist Biologist

Time Time Camera No. Camera No.

Depth to top of chamber (cm) Depth to top of chamber (cm)

Depth to bottom of chamber (cm) Depth to bottom of chamber (cm)

Total Hatched Total Hatched

Total Unhatched Total Unhatched No. Undeveloped No. Undeveloped

No. Unhatched No. Unhatched

No. Unhatched Term No. Unhatched Term

Total Live Hatchlings Total Live Hatchlings

No. Pipped No. Pipped:

Total Dead Hatchlings Total Dead Hatchlings

No. Dead Pipped No. Dead Pipped

Total Eggs Predated Total Eggs Predated

Predator Suspected Predator Suspected

Comments Comments

Appendix C Geospatial Information Service Requirements

Geospatial Information Service Requirements for Joint Region Marianas

Section 1. Overview All geospatial information shall be generated from spatial data maintained in the most recent version of the Navy Data Model (NDM) geodatabase and corresponding Data Collection Guide (DCG). The NDM is the Navy Installation Geographic Information and Systems (also known as IGI&S) enterprise geodatabase that stores geographic objects as standard data. The NDM is designed to meet Office of the Secretary of Defense geospatial data requirements, total data quality management guidelines, modern business needs, and Navy policies. The NDM schema uses the DCG to define the set of features, attribution, and metadata for enterprise geospatial data collected by or on behalf of the Navy. The DCG is a complement to the NDM. The NDM defines what data to collect, and the DCG defines how it is collected in respects to normalized procedures and attributes.

Section 2. Minimum Geospatial Information Systems Requirements Minimum requirements for spatial data are:

a. Submittals, Government Review and Acceptance:

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

ii. All data, source code (e.g. Python scripts), map files, and other geospatial information under this contract is intellectual property of the U.S. Government, and shall be turned over to the U.S. Navy upon completion of this amendment. All data will be delivered via secured means such as DoD SAFE, or the most recent file transfer methods provided by the NAVFAC Information Technology Center.

iii. All submittals shall be reviewed for accuracy, standards, structure and completeness by a GeoReadiness Center representative before acceptance. Contractors shall submit data and documentation at 30%, 60%, 90% and 100% project completion to avoid the rejection of final deliverables.

iv. All proprietary data (electronic and paper formats) and generated geospatial data and services may be used under these contract conditions ONLY. Furthermore, all data and information regarding this contract must be removed from contractor equipment and possession and returned to the government before the final invoice is approved.

v. Through a GRC Geospatial Data Request Form, the contractor will be provided access to existing Navy GIS data required for the project via secured means such as DoD SAFE, or the most recent methods provided by the NAVFAC Information Technology Center.

vi. All data and information generated is limited to only those with a lawful government purpose and only for the initial intended use. In accordance with the clause at DFARS 252.204-7000, the Contractor or Sub-Contractors shall not make public release of any information relating to any part of this contract, or products/deliverables developed thereunder without prior approval of either the Procurement Contracting Officer or the Administrative Contracting Officer.

vii. All data must ensure the use complies with Controlled Unclassified Information

(CUI) DoD policy when applicable. All involved parties are encouraged to visit www.dodcui.mil for information about safeguarding CUI. Information should be processed on Government Furnished Equipment when the option is available.

viii. When applicable, a representative of the GRC should attend planning charrettes in order to convey important information regarding the NDM, DCG, geospatial requirements, and discuss work induction.

ix. Map projects and geospatial information shall be created using Environmental

Systems Research Institute (ESRI) ArcGIS software.

x. Unless approved by the GRC, all geospatial data shall be in the Geographic Coordinate System: GCS_WGS_1984, Datum: D_WGS_1984.

b. GIS Data Format: NAVFAC’s GIS data is an ERSI Geodatabase format which must be delivered in the most recent version of the NDM and corresponding DCG.

i. Geospatial projects (i.e., MXD, MPK): All project files shall be delivered containing all related source files in a specific project file, including extension, graphics, photos, source code (non-encrypted, Visual Basic) based on the version of ArcGIS Desktop specified for the task order.

ii. Spatial Data (i.e. geodatabase, datasets, features): Spatial data shall be delivered as an ArcGIS file geodatabase according to the most recent NDM version. File geodatabases are relational databases that contain geographic information. File geodatabases contain feature classes and tables. The names of these geodatabases will reflect the location of the geographic information it contains at the appropriate level of detail (region, special area, activity). The general format of file geodatabase names is as follows; where yyyy(year)mm(month)dd(day) is the date the geodatabase was created and amended:

Location_yyyymmdd.gdb

(Example: NAVALBASEGUAM_20230111.gdb, JRM_20230111.gdb, Polaris Point_20230111.gdb, MEC_20230111_.gdb, BASECOMM_20230111.gdb)

c. Data Structure: All data shall be structured according to the current version of the NDM and

DCG; special circumstances must be approved by the GRC. The contractor shall use the DCG to identify the classification, type, location, ID number, and any other necessary attributes for all new/updated/edited features. Information on the NDM and the DCG will be provided through a GRC representative.

i. If new geospatial information is created, the GRC shall provide unpopulated features (i.e. empty NDM geodatabase datasets, with the DCG) to the contractor.

ii. If new data is created and the corresponding data structure does NOT yet exist in the NDM, the contractor shall provide the GRC with a data dictionary identifying all of the NDM 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. New non-spatial data standards compliant attributes (meeting NDM criteria) will require precise schema definitions.

d. Data Integrity: Data accuracy standards for all deliverables will be in accordance with features found in the DCG. The contractor shall employ data quality management standards to ensure geospatial information is topologically correct, accurate, and complete, to include:

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

ii. Point and line features will be snapped together where appropriate to support networks. Line features shall be snapped together where appropriate to support networks. Do not break linear features for labeling or other aesthetic purposes.

iii. Lines will be continuous (no self-intersection) and point features will be digitized as points where appropriate. For example, point features, such as manholes, should not be drawn using only a circle (polygon) to represent its location.

iv. No sliver polygons, illogical gaps, or overlaps. All area type features shall be closed polygons.

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

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

e. Data Quality: The contractor shall take all appropriate and needed data quality measures to ensure data is complete, topologically correct, accurate, structured correctly, and formatted correctly per the scope of work, to include:

i. All data shall be visually inspected before submittal to the government.

ii. As part of the 30%, 60%, 90%, and 100% deliverables, the contractor will provide the GRC representative a copy of the Reviewer Batch Job report for each feature.

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

iv. Per the current DCG, all required and mandatory attributes shall be populated.

v. All domain constraints shall be adhered to prior to submittal.

f. Static Map Productions: Static maps will be legible, non-pixelated, professional in appearance (i.e. no hand drawn features) and sized to ANSI A (8.5x11) or ANSI B (11x17), unless otherwise required. Contractors will use a standard template for all static map product submittals with the following elements when creating printed or static digital maps (e.g. PDF, PNG, JPG).

i. Map Title

ii. Inset Map (if necessary)

iii. Decimal Degree coordinates Map Border (or MGRS when required)

iv. North Arrow

v. Scale Indicator

vi. Legend with consistent symbology

vii. Contractor Logo with date, Contract Number, and/or Map Author

g. Metadata:

i. Feature Level Metadata: Feature-level (record level) attribute metadata is required to be populated for each GIS feature/record, per the current version of the NDM and the DCG.

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

h. Field Collection: Where field data collection is required, 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).

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

ii. When required (as stipulated in the contract or as otherwise determined by the Government), the contractor shall use survey grade GPS, at an accuracy level of +/- 3 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.

iii. All survey-grade data collected shall be provided to the Government in a digital format with an attached Survey Report identifying survey method, equipment list, calibration documentation, survey layout, description of control points, control diagrams, quality control report, and field survey data.

iv. A digital Survey Control Database (consisting of a survey marker database and a survey traverse database) will be produced for all survey control points established under this contract, including the horizontal and vertical order and coordinate location of each point.

v. Digitizing/Conversion: Where Digitizing/Conversion is stipulated in the contract, the contractor shall digitize/convert features from designated sources (including remotely sensed data, hardcopy scans, and vector data) to support various GIS applications. Digitizing/conversion routines will ensure that 90 percent of all features will measure within 0.01 inches when reproduced at the scale of original imagery or data source.

vi. GPS data on the location of line features shall be captured at a minimum at the beginning, end, and at each turn or bend in the line and processed as a line feature type. GPS data on the location of point 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. GPS data on polygon features shall be collected at every vertex of the feature and processed as a polygon.

i. Image Collection: Images captured on base must be approved in advance (usually by installation security) of visiting the base. The Contractor shall identify the personnel designated as image collectors (i.e. photographers) for this contract and shall identify the proposed areas/facilities to be collected and provide installation (via COR) with any required equipment information. It is unlawful to capture images outside the intended purpose of this contract. In most cases, image collection will require a ‘Camera Pass’ from installation security.

All images to be delivered/used in submittals must be geotagged with the UTM of the image location.