Attachment D_PWS_N4019222Q5007_Coral and Giant Clam Survey_14JUN2022.pdf

PERFORMANCE WORK STATEMENT

SURVEY FOR CORALS AND GIANT CLAMS AT 10 MONITORING SITES

IN OUTER APRA HARBOR, NAVAL BASE GUAM

June 14, 2022

Attachment D – RFQ N4019222Q5007

ENCLOSURES:

1. Appendix A: NAVFAC Standards For Geographic Information System (GIS)

2. Appendix B: Specifications for GIS Layers and Attributes

Intent The purpose of this Performance Work Statement (PWS) is to provide the Navy with information on marine species warranted for listing under the Endangered Species Act (ESA). The survey data will be used to support Joint Regions Marianas (JRM) Integrated Natural Resources Management Plan (INRMP) goals and objectives for coral habitat enhancement.

Location Under this Performance Work Statement (PWS), 10 locations – previously established (Schils et al.

2017) and last monitored in 2019 (Johnston 2020) – will be surveyed for coral species and giant clam species. These 10 permanent monitoring stations are located on Department of Defense (DoD) submerged lands within Naval Base Guam (Figure 1). The three transect coordinates at each of the 10 monitoring sites are recorded in Table 1 (Johnston 2020).

Figure 1: Location of Outer Apra Harbor, Orote Peninsula and Haputo ERA nearshore waters, Naval Base Guam.

Table 1. Transect coordinates for dive surveys in Outer Apra Harbor.

Transect N Coordinate E Coordinate

AP01_1 13.44566996 144.66876

AP01_2 13.44528004 144.669161

AP01_3 13.44515397 144.669495

AP02_1 13.451587 144.667516

AP02_2 13.45113404 144.667478

AP02_3 13.45069902 144.667425

AP03_1 13.456591 144.665679

AP03_2 13.45617802 144.665703

AP03_3 13.45582799 144.666002

AP04_1 13.45344703 144.661772

AP04_2 13.453686 144.662168

AP04_3 13.45391398 144.66252

AP05_1 13.44739999 144.65866

AP05_2 13.44718298 144.659094

AP05_3 13.44686396 144.659271

AP06_1 13.44987198 144.657132

AP06_2 13.44958498 144.657291

AP06_3 13.44920201 144.6575

AP07_1 13.45142003 144.654548

AP07_2 13.45110403 144.654632

AP07_3 13.45081997 144.654453

AP08_1 13.44367004 144.652245

AP08_2 13.44365202 144.651852

AP08_3 13.44362796 144.651467

AP09_1 13.44373902 144.642568

AP09_2 13.44371698 144.64164

AP09_3 13.44368999 144.641205

AP10_1 13.44864403 144.625942

AP10_2 13.44897696 144.625587

AP10_3 13.449272 144.6251

Background Naval Base Guam is responsible for compliance with requirements in the JRM INRMP as defined by the Sikes Act. The INRMP incorporates inventory, monitoring, and management of natural resources.

This project will determine the coral species and presence/absence of giant clam species at 10 monitoring sites in Outer Apra Harbor.

Scope of Work This project includes both a survey for corals and survey for giant clams at each of the 10 monitoring sites. In terms of corals, the objectives are to determine (1) skewness of colony-size distributions, (2) coral-species richness, (3) Shannon-Weaver evenness, (4) coral cover, and (5) coral heterogeneity. In terms of giant clams, the objectives are to (1) determine the presence or absence of giant clam species and (2) density of giant clam species.

4.1 Task 1. Project Planning and Dive Safety Plan

a. Prior to the start of work, the Contractor shall participate in a kick-off meeting with the following objectives:

Acquaint with the various parties involved with the project;

Review the scope of the proposed work;

Discuss schedule, coordination and work expectations;

Define channels of communication and Points of Contact (POCs);

Present their Plan of Action and Milestones (POAM) for timely completion of the work;

Document meeting discussions.

b. The kick-off meeting will assumedly be held at NAVFAC Marianas but may be held by a conference call.

c. The Contractor shall provide meeting minutes to the Contracting Officer’s Representative (COR) and/or Technical Point of Contact (TPOC) within 5 days of the kick-off meeting (4.1a).

d. The Contractor shall ask any questions related to the successful completion of the work.

e. The Contractor shall submit the dive plan for approval by the TPOC.

f. The Contractor shall submit an Accident Prevention Plan (APP) and Activity Hazard

Analysis (AHA) in accordance with Section 5.0 Deliverables.

• Accident Prevention Plan. The Contractor shall develop and submit an APP with

AHA as an appendix. 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 Contractor shall certify to the TPOC and COR that the final APP has been reviewed with each contractor’s and subcontractor’s employees prior to mobilization and start of fieldwork activities.

The Contractor shall submit a Hazard Analysis and Critical Control Plan (HACCP) in accordance with Section V. Deliverables.

• The Contractor shall develop a HACCP plan to ensure that invasive species are not moved or introduced in association with transplantation, maintenance and monitoring efforts. The Contractor shall prepare and submit a draft HACCP Plan for Government review and comment within 30 calendar days of the kickoff meeting via email. The final HACCP Plan must be approved by the Government prior to the commencement of fieldwork or the field assessment. One hard copy and one digital copy of the final HACCP Plan shall be provided to the TPOC and COR.

g. Throughout the duration of the contract award, the Contractor shall (a) provide project status and schedule updates as necessary, or at least once per month; (b) coordinate field work and deliverables.

4.2 Task 2. Coral Survey and Giant Clam Survey

a. The Contractor shall conduct surveys for corals and giant clams at the 10 monitoring stations within Outer Apra Harbor.

The Contractor shall utilize 10 permanent monitoring transect locations established within Apra Harbor (Schils T. et al. 2017), and deploy three, 50 m transects laid end to end, parallel to the reef margin along one depth contour (~5 m in depth) (Hoot & Burdick 2017). Fifteen replicate, 1 square meter quadrats shall be placed at equal intervals along the transect lines.

Metrics shall be recorded to determine the following:

• Skewness of colony-size distributions

• Coral-species richness

• Shannon-Weaver evenness

• Coral cover

• Coral heterogeneity

• Coral taxonomy

• Presence or absence of giant clam species

• Height, length width of giant clams

• Giant clam taxonomy

• Density of giant clam species

The Contractor shall provide high-quality photographs of any giant clams recorded. Each photograph shall be properly annotated, e.g. location coordinates.

The Contractor shall present the data using various types of illustrations, e.g. density (individuals per m2) per species at each site, if present.

Parameters like latitude, distance to shore, predominant exposure to wind, water temperature, depth and reef zone should be recorded at each monitoring location.

4.3 Task 3. Data Management

a. The Contractor shall record all data collected during field surveys in a database (e.g. Excel spreadsheet). The database format shall be reviewed and approved by the TPOC.

b. The Contractor shall provide at digital maps and dataset in accordance with Section 4.5.

• An overview map (i.e. includes all 10 sites within Outer Apra Harbor) shall depict all occurrences of the giant clam(s).

• A close-up map of any survey sites where giant clams are observed/recorded.

4.4 Task 4. Project Management

a. Under this PWS, the Contractor shall provide project oversight and coordination for all associated tasks; maintain budget coordination, tracking, and reporting.

b. The Contractor shall submit monthly status reports in electronic format to the COR/TPOC.

Status reports shall be submitted no later than the 10th of each month following contract award. The status report will provide a summary of the activities that occurred during the reporting period. A cumulative invoiced budget to date shall be submitted to the COR/TPOC.

c. Work will be conducted according to the schedule agreed upon during the kick-off meeting.

The Contractor shall promptly (i.e. no later than two days) notify 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 (i.e. no later than two days) reported to the

COR/TPOC.

d. The Contractor shall not proceed with any work determined not within the project PWS unless an official modification is approved by the COR.

e. The Contractor shall begin work under this PWS after official notification by the COR.

4.5 Format Requirements for GIS Mapping and Delineations

a. All environmental contracts are required to deliver all data collected in the suitable GIS format in conjunction with NAVFAC GeoReadiness Center (GRC) Environmental standards.

b. The GIS format is as follows:

Spatial Data (GIS Map Themes): Spatial data shall be delivered as an ArcGIS file geodatabase. File geodatabases are relational databases that contain geographic information. File geodatabases contain feature classes and tables.

All GIS/geospatial projects (i.e. MPK) shall be delivered containing all related source files in a specific project file, including extension, graphics, photos, CAD, source code (non-encrypted, Visual Basic) based on ArcGIS version 10.1.

Unless specified otherwise, all data shall be structured according to the current version of the Spatial Data Standards (SDSFIE) in use by NAVFAC. This is version NDM 3.03 as of December 2015. Information on the SDSFIE data model can be found at https://sdsfie.org, and a copy of the current data model implementation shall be provided to the contractor.

https://sdsfie.org/

c. GIS data shall include, but not be limited to, the following:

Field survey/project areas Survey transects Collected data points, polygons, and lines, and all attributes (data fields) collected about them Pictures that must be GeoTagged and delivered with the appropriate pathway appended All maps created and used in deliverable reports shall be turned in as a standing MPK file created in ArcGIS version 10.1.

Data charts shall be delivered in Microsoft Excel format.

GPS unit standards for field data collection are required:

• The Contractor shall utilize conventional and other methods, such as Global

Positioning Systems (GPS) in accordance with the applicable Geospatial Positioning Accuracy Standards published by the Federal Geographic Data Committee (FGDC).

• At a minimum, the Contractor shall provide resource grade GPS collection at an accuracy level of +/- < 1 m and shall use differential correction to target accuracies of +/- 0.5 m. This is a GPS unit with an internal or external GNSS antenna.

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

GIS data shall be submitted at the 25% mark and 75% (or as directed by the COR) for review before the final submittal.

For further guidance on NAVFAC GIS standard guidance, please see Appendix A & B.

4.6 Experience and Qualifications

a. The Contractor shall assign a Principal Investigator (PI) specifically for this contract.

b. The PI must have relevant experience at a comparable level of responsibility in projects of similar size, scope and complexity.

c. The PI must meet the following minimum qualifications:

A bachelor’s degree in Coral Reef Ecology, Benthic Ecology, Marine Biology, or related science.

Three years of experience conducting marine monitoring within the Marianas Archipelago coral reef ecosystems.

Experience planning and executing long-term marine monitoring projects.

Experience with in-water photography and transects.

Experience using GIS for marine mapping resources and location markers.

Possess at least 200 documented dive hours of marine field research and experience preparing dive safety plans.

Ability to identify down to the species level of corals and giant clams.

d. The Contractor and all personnel involved in the project shall have all the necessary skills and equipment pertaining to the requirements as instructed in this PWS.

e. Experience that is not related to the work described in Section 4 of this solicitation should not be included in Key Personnel experience. Key Personnel experience may include experience gained while not employed by the Offeror.

f. An organizational chart of Key Personnel shall be submitted to the TPOC/COR, including their role, contact information, and assigned tasks

DELIVERABLES

5.1 Contractor Deliverables

a. Dive safety plan;

This plan shall be submitted within 30 days of contract award This plan must be approved prior to contract work

b. Final database populated with all data collected during field surveys;

c. Data sheets from all surveys;

d. Monthly progress reports;

Reports should be submitted by the 10th of the month following the reporting period

e. Final analysis report.

This should include, but not be limited to, information provided in Section 3.0 Background and objectives stated in Section 4.0 Scope of Work.

5.2 Related Requirements and Information

a. The Contractor will submit a final database populated with all data collected during field surveys. The database format shall be approved by the TPOC.

b. All data sheets from field surveys will be provided to the TPOC.

c. Four final reports will be delivered: Two hard copies and two digital (DVD) copies.

d. All GIS data will be delivered in electronic format.

e. All GIS data will contain populated metadata, be SDSFIE compliant, and projected in UTM

Zone 55 North, WGS84.

5.3 Performance Standard

The Contractor shall meet the following performance standards:

a. Address all Government comments on the draft submissions (e.g. monthly reports, database, and comprehensive report), e.g. comment matrix.

b. Submit all submittals on time.

c. Include Table of Contents and/or Figures/Tables, and all required sections, in the final report.

d. Include meaningful tables and/or figures in the final report.

e. Insert high quality photos in the final report.

f. Provide the presence/absence of giant clam species at each of the 10 survey sites. Determine the density of giant clams per species at each site, if applicable.

g. The final report shall include a meaningful discussion/conclusion that incorporates project data, previous studies, relevant scientific literature, and regulatory drivers.

h. Standardize all data fields and values and define all terms/variables in the final database.

i. Include all data fields and values recorded on the field data sheets in the GIS map.

5.4 Deliverable Schedule

The contractor shall submit deliverables1 according to the following schedule:

Table 2. Schedule for Project Deliverables.

Deliverables File Extension Quantity Deadline Activity Hazard Analysis

Electronic .docx or .pdf 1 Within 30 days of contract award

Accident Prevention Plan

Electronic .docx or .pdf 1 Within 30 days of contract award

Hazard Analysis and Critical Control Point Plan

Electronic .docx or .pdf 1 Within 30 days of contract award

Dive Safety Plan Electronic .docx or .pdf 1 Within 30 day of contract award

Plan of Action and Milestones

Electronic .pdf 1 Within 30 days of contract award

Kickoff Meeting Minutes

Electronic .pdf 1 Within 30 days of contract award

Monthly Progress Report

Electronic .pdf 1 10th day following the reporting period

Draft Final Database

Electronic .xlsx 1 11 months after contract award

Draft Final Report Electronic .docx 1 11 months after contract award

Final Database Electronic .xlsx 1 Within two weeks from receipt of comments

Final Report Physical Electronic

CD/DVD

.pdf

Within two weeks from receipt of comments

GIS Electronic Refer to Appendices A & B

1 At the same time as Final report

a. Period of Performance

The Period of Performance is not to exceed 12 months after contract award.

1 If electronic deliverable(s) cannot be transmitted via email (e.g. file size), they must be delivered on a DVD.

Submittals and Correspondences

6.1 Format for Deliverables

All documents shall be submitted on 8 1/2 by 11-inch paper, 11 by 17-inch foldout maps/figures are acceptable. All reports shall be double sided. All original documentation will be reproducible by black and white xerography with heavy paper or hard covers and the original unbound copy with hard covers that will allow pages to be easily removed. Where possible, all reports shall be printed on recycled paper and limit “blank” pages. Bindings will include a label identifying the report, author(s), date of completion, and contract number.

6.2 Standard of Quality

The Contractor shall be responsible for the professional quality, technical accuracy, and the coordination of all services furnished by the Contractor under this contract. 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 twenty-five errors are found, or if ten errors over twenty consecutive pages are found, the document will be rejected. All draft deliverables shall include line numbers on each page to facilitate commenting and associated comment response for the Comment Matrix. The Contractor 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 Contractor 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.

6.3 Electronic Deliverables of Records

The data management may include a hand held PDA field device for collecting field data and a web-based electronic media site, including a web GIS. The field PDA will be used to record all field data including: MEC identification, man-hours for completing various tasks, geophysical data, and MD/RRD recovery and processing. The joint use of this system is to facilitate electronic exchange of information, key processes, and overall management of the contract. The electronic version/file of the preliminary/internal draft, draft, and final after comments are addressed shall be submitted in both A) the native format, which Navy prefers be a Microsoft product, and B) Adobe Acrobat PDF (or compatible) format. The PDF version of all final deliverables (other than raw analytical and databases) must be a complete, mirror image of the hardcopy, and include appendices, maps, signature pages, etc. At completion of the project with the Final Report submittals, the Contractor will provide an electronic deliverable with a copy of all reports, meeting minutes, point papers, maps and map databases, and briefings. All electronic submittals will be certified “virus free” and include the statement “virus free” on the disk or transmittal message. The Contractor shall verify, with the RPM, the appropriate data management requirements and electronic data deliverables.

6.4 CD-ROM Requirements

a. PDF files of final documents shall be provided in the following formats:

The entire document shall be provided as one .pdf file. The .pdf file shall have bookmarks for each item identified in the document's table of contents. The bookmark shall use the same description as provided in the table of contents. If the bookmark is lengthy, abbreviate as needed. Bookmark to the second level (i.e., 1.1, 1.2, 1.3, etc.). Do not bookmark signature page, list of acronyms, individual tables, photos, or figures. Each appendix, regardless of size, shall be provided as an individual pdf file. All maps, figures, and pictures shall be provided at a useable resolution. All color maps, figures, and pictures shall be provided in color PDF format.

All files associated with the document, including the laboratory electronic data deliverable, shall be provided in native file format (e.g. Word, Access, CADD) on the RPM and Administrative Record CD copies. In addition, the RPM and Administrative Record CDs shall include the laboratory analytical data packages (e.g. forms, raw data) in pdf format. CDs intended for distribution to other entities shall not include the native files of the laboratory analytical data packages. Note: a hardcopy of the analytical data packages will no longer be archived to the Federal Records Center.

b. The CD jewel case cover (outside front) and CD label shall use the current approved layout and include:

NAVFAC Marianas logo Contract Number Contract Task Order Number Report Title Site Location Date Report finalized

c. Standard CD jewel cases shall be used. The jewel case spine shall identify the report title, site, and location. In the event multiple reports are requested on one CD, the jewel case cover (inside) shall include a list of all reports with the date and file name. The jewel case spine shall use "Various Reports" as the report title and also identify the site and location.

6.5 External Communications

The Contractor 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 to and approval by the TPOC.

6.6 Commenting System and Comment/Response Tables

a. For all Government reviews of the deliverables, the Contractor shall utilize an automated commenting system, if readily available and compatible with all Government reviewers’ computers. The automated comment system shall be approved by the TPOC prior to use. In the event that an automated commenting system is not available, comments will be provided via a Government approved comment matrix.

b. Deliverables submitted or re-submitted after revision to address comments shall be accompanied by an appropriate comment/response table which clearly indicates the comment, actions that were performed in response to the comment, and location of revisions (if any).

6.7 Writing Style

a. The Contractor will ensure that work products are written in accordance with an approved style standard (e.g., Chicago manual of style, Strunk and White Elements of Style, Navy Style Guide, Bluebook, American Psychological Association (APA) style guide).

b. Contractor shall obtain prior government approval for the appropriate standard for use on submittals prior to preparation of submittals. Regardless of approved style standard, Contractor submittals shall follow Wikipedia manual of style/words to watch guidelines:

https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Words_to_watch

c. Graphics, Figures, and Tables match the Text. Before submitting any document containing graphics, figures, or tables, the Contractor will ensure the graphic, figure, or table matches what is described in the text.

6.8 Photographs

a. Digital copies of all photographs taken while in performance of this statement of work shall be provided to the COR/TPOC at the soonest possible time after the photographs are taken.

b. Title and all rights associated with use of the photographs shall be with the government.

Environmental GIS Deliverable Requirement

7.1 All environmental contracts are required to deliver all data collected in the suitable GIS format in conjunction with NAVFAC GeoReadiness Center (GRC) Environmental standards

a. The GIS format is as follows:

Spatial Data (GIS Map Themes): Spatial data shall be delivered as an ArcGIS file geodatabase. File geodatabases are relational databases that contain geographic information. File geodatabases contain feature classes and tables. Bathymetry data that cannot be placed in a geodatabase shall be delivered in a LAZ.

All GIS/geospatial projects (i.e., MPK) shall be delivered containing all related source files in a specific project file, including extension, graphics, photos, CAD, source code (non-encrypted, Visual Basic) based on ArcGIS version 10.3.1

Unless specifically directed otherwise, all vector data shall be structured according to the current version of the Spatial Data Standards (SDSFIE) in use by NAVFAC. This is reflected in the current data model version of the Navy Data Model (NDM). Information on the SDSFIE data model can be found at: https://sdsfie.org, and a copy of the current data model for the NDM database shall be provided to the contractor. The data collection guide can be accessed at: http://datacollectionadvisor.com/

b. GIS data shall include but not be limited to:

Field survey/project areas Survey transects https://en.wikipedia.org/wiki/Wikipedia%3AManual_of_Style/Words_to_watch http://datacollectionadvisor.com/

Biological opinion/Programmatic agreement layers Mitigations boundaries Probability models Collected vector data points, polygons, and lines All the attribution (data fields) collected about them.

Pictures (must be GeoTagged) and delivered with the appropriate pathway appended in the “MediaIDFK” attribute of the appropriate feature class.

Toolbox/Tool kits developed for ArcGIS during the project Python scripts developed for ArcGIS during the project All Raster datasets: to include Bathymetry, LiDAR, Hyperspectral, Thermal, magnatometry, Imagery etc.

c. All maps created and used in deliverable reports shall be turned in as a standing MPK file created in ArcGIS version 10.3.1 Data charts and related tables shall be delivered in Microsoft access or excel format (PDF is unacceptable) When raster data is created or used: Raster datasets shall be delivered post-processed with all native files as well as in the appropriate format to be read in ArcGIS: I.E.

a .LAZ, .Tif, .BIM, etc. Further guidance shall be provided for projects specific to raster data collection.

GPS unit standards for field data collection are required.

• The contractor shall utilize conventional and other methods, such as a Global

Positioning System (GPS) in accordance with the applicable Geospatial Positioning Accuracy Standards published by the Federal Geographic Data Committee (FGDC).

• At a minimum, the contractor shall provide mapping grade GPS collection at an accuracy level of +/- < 1m and shall use differential correction to target accuracies of +/- .5 m. This is a GPS unit with an internal or external GNSS antenna.

• When applicable, 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.

GIS data shall be submitted at the 25% mark and 75% (or as directed by the COR) for review before the final submittal.

For further guidance on NAVFAC GIS standards guidance including metadata, please see the GIS Appendix: NAVFAC Standards for Geographic Information Systems (GIS) and Specifications for GIS Layers and Attributes

Point of Contacts

a. The primary Project Manager (PM) and Technical Point of Contact (TPOC) is Anjelica

Perez, NAVFAC Environmental, (671) 339-7281, anjelica.perez@fe.navy.mil

b. The Contracting Officer Representative (COR) is Maria Santos, NAVFAC Environmental,

(671) 339-5148, maria.santos@fe.navy.mil mailto:anjelica.perez@fe.navy.mil mailto:maria.santos@fe.navy.mil

c. The Project Contract Specialist (CS) is Mark C. Cruz, NAVFAC Acquisitions, (671) 333- 3175, mark.c.cruz@fe.navy.mil

d. The Contractor will designate an individual who is directly responsible for, and is the contact in all technical matters pertaining to this contract award. Arrangements with technical contacts and conferences concerning work shall be made through the COR/TPOC. Direct contact with other departments within NAVFAC Marianas or other commands and/or military activities may be made by the Base Representative only with prior notification and approval by the Project Manager. Keep the COR/TPOC informed of progress and problems encountered.

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

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

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

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

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

9.2 Failure to demonstrate that the performance objectives are achieved and the tasks are complete may result in non-payment of the final invoice and/or a negative evaluation.

mailto:mark.c.cruz@fe.navy.mil

Requirement Description Performance Objective 1. Properly survey corals and giant clams at 10 sites in Outer Apra

Harbor.

2. Develop high-quality maps and provide GIS Geodatabase data collections and delineations.

3. Submit plans, progress, drafts and final reports in a timely manner, as instructed in this PWS.

Performance Standard Complete task requirements in accordance with the objectives prescribed in the PWS. Submission of prescribed deliverables with no significant errors in a timely manner with no or very minimal schedule delays.

Acceptable Quality Level (AQL)

100% Navy acceptance and compliance with all project-specific objectives outlined in the PWS.

Assessment Method 1. Scheduled and unscheduled surveillance of field work, to ensure consistency with prescribed details provided in the PWS.

2. Review of submittals/deliverables for content, quality and adherence to local laws, guidance and regulations and ensure compliance with prescribed schedules.

Performance Payment and Incentive

Payment. Monthly payment on a prorated scale of schedule of value items completed and accepted by the Navy by the method of acceptance. Payment shall be retained until contractor has achieved the AQL and has been accepted by the government and regulatory agencies.

Incentive. Successful performance ratings in the Contractor Performance Assessment Report (CPAR).

Appendix A: NAVFAC Standards for Geographic Information System (GIS)

Overview The GeoReadiness Center (GRC) is the single, authoritative source and distribution point for all geospatial shore installation data within the region. The GRC houses the most current geospatial information for the entire 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.

Basic Deliverable Requirements

2.1 Submittals, Government Review and Acceptance:

a. All data used and developed under contract is intellectual property of the U.S. Government, and shall be turned over to the U.S. Navy upon completion of this amendment.

b. All submittals shall be reviewed for accuracy, structure and completeness by a GeoReadiness representative before acceptance. Contractors shall submit data and documentation samples at 25% and 75% project completion to avoid the rejection of final deliverables.

c. All source code (e.g. Python scripts, html files, etc.) and map files (ESRI ArcGIS .mpk) shall be provided to the government.

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

2.2 GIS Data Format: NAVFAC’s GIS data is ERSI Geodatabase format.

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

Submittal format shall be determined by the COR.

b. Spatial Data (GIS Map Themes): Spatial data shall be delivered as an ArcGIS file geodatabase. File geodatabases are relational databases that contain geographic information.

File geodatabases contain feature classes and tables. The names of these geodatabases should reflect the location of the geographic information it contains at the appropriate level of detail (region, special area, activity). The general format of personal geodatabase names is as follows:

c. Location_yyyymmdd.gdb Location = Location of the geographic information, defined to the appropriate level of detail.

Names begin at the regional level, using the 2-digit country code from iNFADS (e.g.

HI=Hawaii, GQ=Guam, JA=Japan, etc.) and may narrow into an area of interest within the region (e.g. Pearl Harbor, Yokosuka, Apra Harbor, etc.). The location can be further narrowed down to the activity level where the geodatabase can be identified by the activity’s UIC (N68032, N58003, etc.)

d. Yyyymmdd = Date that the geodatabase was created or amended, as expressed in year (yyyy), month (mm), and date (dd).

e. Data Structure: Unless specifically directed otherwise, all data shall be structured according to the current version of the Spatial Data Standards (SDSFIE) in use by NAVFAC. This is the current version of the Navy Data Model (NDM). Information on the SDSFIE data model can be found at: https://sdsfie.org, and a copy of the current data model implementation shall be provided to the contractor. The data collection guide can be accessed at:

http://datacollectionadvisor.com/ If new data is being created and the corresponding SDSFIE data structure exists, the government shall provide unpopulated layers to the contractor structured per current NAVFAC standards.

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.

2.3 Government Source Data: The contractor will be provided access to any GIS data required for the project via a government computer, which will require Contractor Common Access Card (CAC).

Government GIS repository is in an ESRI format. All data shall be returned in this format and structure unless the government specifies otherwise. A completed NAVFAC GIS Data Release form is required prior to data being released to the Contractor if editing is required to be completed on Contractor equipment.

2.4 Attribute Population:

a. The contractor shall consult with the COR before populating attribute tables to ensure the results match the current GeoReadiness interpretation of the SDSFIE.

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

c. For new field collected data, attribution must include the date collected in the following format.

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

Data Type: Date Default Value: null

Data Integrity

3.1 Data accuracy standards for all deliverables will be in accordance with those set forth in the section entitled ‘Data Collection Procedures’. All deliverables should include an accuracy report in the metadata.

3.2 The contractor shall employ appropriate QA/QC standards to ensure that data is topologically correct, accurate and complete (to include):

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

3.4 Point and line features will be snapped together where appropriate to support networks. For example, do not break linear features for labeling or other aesthetic purposes.

3.5 Lines should be continuous and point features should be digitized as points. For example, point features, such as manholes, should not be drawn using only a circle (polygon) to represent its location. Preferably, use an attribute block symbol that has an insertion point in the center of the manhole.

3.6 No sliver polygons

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

3.8 Geometric network connectivity must be maintained for utility networks.

Note: This excludes field collected “walked” survey transect data.

A summary of the methods used to correct inconsistencies and any remaining errors by case should be included in the metadata under the ‘Logical Consistency Report’ and ‘Completeness Report’ sections.

CAD Format Deliverables

4.1 CAD drawings may be accepted as GIS deliverables, if COR approves.

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

4.3 CAD file conversions must have a unique identifier and a related table to link critical attribution normally found in GIS data. I.E: Pipe size, capacity, locational accuracy, etc.

4.4 CAD deliverables shall include AutoCAD (DWG) files. CAD symbols placed within the design/drawing file shall adhere to the A/E/C CAD Standard. CAD symbol libraries can be found on the Tri-Service CAD/BIM Technology Center website. https://cadbim.usace.army.mil/CAD https://www.wbdg.org/ffc/army-coe/cad-bim-technology-center or https://cadbimcenter.erdc.dren.mil/default.aspx?p=a&t=1&i=7.

Coordinate System

5.1 All geospatial data, unless specified otherwise, shall be in the Geographic Coordinate System:

GCS_WGS_1984, Datum: D_WGS_1984.

Metadata

6.1 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 current NDM are listed in APPENDIX B.

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

https://www.wbdg.org/ffc/army-coe/cad-bim-technology-center https://cadbimcenter.erdc.dren.mil/default.aspx?p=a&t=1&i=7 http://www.fgdc.gov/metadata/geospatial-metadata-standards

Quality Control and Quality Assurance.

7.1 The contractor shall take all appropriate and needed QA/QC measures to ensure 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 before submittal to the government.**

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

c. All required attributes (per DCG current version shall be populated).

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

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

f. All area type features shall be closed polygons.

g. Line features shall be snapped together where appropriate to support networks. For example, do not break linear features for labeling or other aesthetic purposes.

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

i. No sliver polygons

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

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

Field Collection

8.1 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).

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

8.3 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 +/- 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.

8.4 GPS data on the location of utility lines and other 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 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.

Data on polygon features shall be collected at every vertex of the feature and processed as a polygon.

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

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

8.7 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 insure that 90 percent of all features will measure within 0.01 inches when reproduced at the scale of original imagery or data source.

Photography

9.1 Photography on-base must be approved in advance of visiting the base, the Contractor shall identify the personnel designated as photographers for this contract and shall identify the proposed areas/facilities to be photographed and provide installation (via COR) with any required photographic equipment information.

9.2 All photographs to be delivered/used in the final report must be geotagged with the UTM of the picture location

APPENDIX B: Specifications for GIS Layers and Attributes

The contractor shall consult with the government points of contact to ensure data is placed into the appropriate layer. Please see http://datacollectionadvisor.com/ for full guidance.

This section lists:

1.1 SDSFIE Required Global Attributes: These must be populated for each record in all layers

1.2 SDSFIE Required Global Metadata Attributes: These must be populated for each record in all layers

1.3 Project Specific GIS Layer and Attribute Descriptions: Specific to the scope of work, the DCG provides the full descriptions of each layer and available attributes. The contractor shall consult with the government points of contact to identify which specific non-required attributes to populate. At minimum the following for and dataset must be populated.

Attribute ***IDPK Definition Primary Key. A unique, user defined identifier for each record or instance of an entity.

Mandatory No Population Guidance Populate with unique ID or ID series agreed upon prior to project start.

Data Type Text Field Size 40 Example Value CR 66-02-1998 Attribute InstallationID Definition The official code assigned by the Military Service (includes Washington

Headquarters Services) to identify the Headquarters Services) to identify the site or group of sites that make up an installation. For the Navy it is site is site identifier as represented by the iNFADS Site Code.

Mandatory Yes Population Guidance Populate with the appropriate value from the SiteCode constraint table based on iNFADS or RPAO guidance.

Data Type Text Field Size 11 Example Value Code: N61755 Description:Navy Base Guam, JRM Attribute FeatureName Definition The name of the feature Mandatory Yes Population Guidance For features that are not stored in iNFADS, populate with a common name of the feature if one exists, using Proper Case.

Data Type Text Field Size 80 Example Value Threatened and endangered Species observation

Attribute FeatureDescription Definition The narrative describing the feature.

Mandatory No Population Guidance For any attribute being populated with the domain value of "other" include the attribute name along with the description, and separate each using a semicolon (e.g., natureOfConstruction: Plastic; purposeType:

Recreation). In addition, where appropriate, populate with text that further describes the feature (e.g., a local common name such as Commercial Gate, or a physical label on a feature in the field such as "Fly Navy").

Data Type Text Field Size 255 Example Value Location of host plant of 30 Dendrobium guamense an epiphytic species listed by USFW and found in a construction footprint J001B.

Attribute Creator Definition The name of the department or contractor that collected the information for the feature for the first time. For example, NAVFAC SE GRC, attribute as

NAVFACSEGRC

Mandatory Yes Population Guidance The name of the federal employee or name of the contracting company that created the information for the feature (e.g., Art Vandelay as "VandelayA" or Vandelay Industries as "Vandelayindustries".

Data Type Text Field Size 20 Example Value PetermanJ Attribute DateCreated Definition The date the feature was created for the first time Mandatory Yes Population Guidance Populate with the date the feature was created (Geometry and Attribute).

Data Type Date Field Size NA Example Value 6/28/1974 Attribute CollectionMethod Definition The method used to collect the geometry of the feature.

Mandatory Yes Population Guidance Populate with the appropriate value from the CollectionMethod constraint table.

Data Type Text Field Size 28 Example Value Code: HeadsUpImag eryMgGPSVrfy Description:

Heads Up Imagery Mapping Grade GPS Verify

Attribute LocationAccuracy Definition The location accuracy for the data that was collected and verified.

Mandatory Yes Population Guidance Populate with the accuracy value followed by a space and then the abbreviation of the unit of measurement in lower case.

Data Type Text Field Size 50 Example Value +/-1m

g. Throughout the duration of the contract award, the Contractor shall (a) provide project status and schedule updates as necessary, or at least once per month; (b) coordinate field work and deliverables.