Attachment D_PWS seabirds v231115.pdf

EVBL PWS Seabird Surveys on the Tinian Military Lease Area

PERFORMANCE WORK STATEMENT

Seabird Surveys on the Tinian Military Lease Area

NAVFAC MARIANAS EV2

[11/15/2023]

Section 1.0 – GENERAL This Performance Work Statement (PWS) solicits services for performing visual searches and counts of seabirds protected under the Migratory Bird Treaty Act (MBTA) on the Tinian Military Lease Area (MLA) and shall be performed as outlined below. The duration of work under this contract shall not exceed 12 months from the award date.

This action will be performed in accordance with the legislative purposes of the Sikes Act (P.L. 86-797, as amended, 16 USC§ 670), to include the requirement that the Secretary of each military department manage the natural resources of each military reservation under their jurisdiction "so as to provide multipurpose uses of those resources." Compliance with this legal mandate for stewardship of natural resources can be truly accomplished only through a multi-disciplinary approach in assembling the natural resources professionals and projects essential to the well-being of the natural resources and support of the military mission. Naval Facilities Engineering Systems Command Marianas (NAVFAC) will administer this contract. All work must be performed following applicable and appropriate Department of Defense (DOD) guidance and policy.

Under this PWS, the following services will be required: field searches and counts of MBTA-protected seabirds.

1.1 PRIMARY OBJECTIVE

The primary objective of this project is to locate and count aggregations of seabirds on the Tinian MLA (Figure 1). The project scope shall include all the necessary labor and equipment associated with meeting the objective.

The Contractor shall obtain final approval of the work required by the Contracting Officer Representative (COR) or Contracting Officer (KO) upon completion of these performance objectives as specified in Section [7]: PERFORMANCE MEASUREMENT AND

PAYMENT SUMMARY AND OFFER SCHEDULE.

Figure 1. Location of the Tinian Military Lease Area, Tinian, Commonwealth of the Northern Mariana Islands. Reprinted from 2019 JRM INRMP.

1.2 BACKGROUND

The overall intent of this contract is to address the following strategy and action from the 2019 JRM INRMP:

Strategy: Improve understanding of MBTA-listed bird habitat use on JRM leased lands and bird/mission interactions to avoid and/or minimize effects of takes on MBTA-listed birds.

Action: Identify MBTA-listed bird species of concern (referred to as Mission Sensitive Species) on Tinian and determine interrelatedness between these species and mission activities. These data will be used to provide refinements to monitoring protocols and whether additional management actions for MBTA-listed birds are necessary on JRM leased lands.

The specific intent of this contract is to identify the locations and status of aggregations of MBTA-protected seabirds on the Tinian MLA. Although Tinian-specific records are unavailable, a variety of MBTA-protected seabird species have been documented as breeding within the Commonwealth of the Northern Mariana Islands (CNMI) and may nest on Tinian (Table 1). Searches and counts of these potentially nesting seabird species are the priority for this contract, but observations of rare MBTA-protected species and incidental observations of nests of other native bird species made during seabird searches will also be recorded.

SECTION 2.0 – WORK ELEMENTS

The Contractor shall furnish all labor, materials, tools, supplies, services, equipment, project management, permits, contract/procurement administration, etc. 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 approved work plans.

The Contractor’s work areas and activities at the site shall be subject to inspection without announcement by the Navy and their representatives.

2.1 WORK ELEMENT 1 – Project Management

2.1.1 Kick-off Meeting

The Contractor shall participate in a kick-off meeting prior to the start of work to become acquainted with the various parties involved with the project; to discuss the scope of the proposed work including scheduling and coordination; and to define channels of communication and points of contact.

2.1.1a. The Contractor shall establish milestones/deadlines and a proposed schedule (POAM) for all project activities. A draft POAM will be submitted by email at least three (3) working days prior to the kick-off meeting. The Final POAM will incorporate Government comments received and be submitted electronically within five (5) working days following the kick-off meeting.

Updates to the POAM to reflect changes in milestones will be submitted with progress reports.

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

2.1.1c. The Contractor shall be responsible for documenting the discussions (meeting minutes). Meeting minutes shall be provided to the Technical Point of Contact (TPOC) within 5 days of the kick-off meeting.

2.2 WORK ELEMENT 2 – Project Plans

2.2.1 Safety Plans (Accident Prevention Plan and Activity Hazard Analysis)

The Contractor shall develop and submit an Accident Prevention Plan (APP), including an Activity Hazard Analysis (AHA) as an appendix. The APP with AHA shall be developed in the format provided in Appendix A of the EM 385-1-1, 15 Sep 2008, or latest edition with updates, US Army Corps of Engineers’ Safety and Health Requirements Manual and shall address each of the elements and sub-elements in the outline.

The Contractor shall prepare and submit electronically for government review and comment the draft APP with AHA at least five days before the kickoff meeting. The final APP with AHA must be approved by the Government prior to the commencement of fieldwork. One digital copy of the final APP with AHA shall be provided to the COR/TPOC.

2.2.2 Hazard Analysis and Critical Control Point Plan (HAACP)

The Contractor shall develop a HACCP to ensure that invasive species are not moved or introduced in association with any work elements of the PWS. The Contractor shall prepare and submit electronically a draft HACCP for Government review and comment at least five days before the kickoff meeting. The final HACCP must be approved by the Government prior to the commencement of fieldwork or the field assessment. One digital copy of the final HACCP shall be provided to the COR/TPOC.

2.3 WORK ELEMENT 3 – Field Data Collection

2.3.1 Searches

a. The Contractor shall conduct one visual ocean-based search for aggregations of MBTA-protected seabirds. The Contractor shall use a boat with captain to travel around the MLA coastline paying particular attention to cliffs where tropicbirds or noddies may nest. The Contractor should plan for one 8 hour or longer field day during favorable weather/water conditions to complete the ocean-based search.

b. The Contractor shall use a vehicle to conduct a visual land-based search for aggregations of MBTA-protected seabirds on the Tinian MLA. The Contractor should plan for a minimum of three 8 hour or longer field days (that do not have to be consecutive) to complete the land-based search. The Contractor shall conduct searches along all publicly-accessible drivable roads on the MLA. At no time should the Contractor pass through gates or fences, or otherwise enter areas that appear to be leased for ranching or other private purposes.

c. Drivable roads are defined as publicly-accessible and passable by a sedan without getting stuck or causing major vehicle scratches such as occur on road stretches where tree branches simultaneously scratch both sides of the vehicle.

Minor scratches to the vehicle are expected. Tinian rental car companies may charge a fee of $50-75 or more when returning a vehicle with minor scratch damage. If using a rental car, the Contractor may want to research Tinian rental car company damage policies and budget for minor scratch damage fees, or plan for an alternative mode of transportation (e.g. personal vehicle, bicycle, walking, etc).

d. Search dates will be coordinated with the TPOC and will be scheduled during typical seabird breeding season (May-Sep). Land-based search dates scheduled across the seabird breeding season are preferred but not required.

e. The GPS track of each search day shall be recorded.

f. Seabirds with documented breeding in the CNMI are the primary target species for searches and counts (Table 1). Regardless, an aggregation of any MBTA-protected species should be recorded.

Table 1. MBTA-protected seabirds with documented breeding in the CNMI. Modified from Wiles 2005.

English Name Scientific Name Wedge-tailed Shearwater Ardenna pacifica Red-tailed Tropicbird Phaethon rubricauda White-tailed Tropicbird Phaethon lepturus Masked Booby Sula dactylatra Red-footed Booby Sula sula Brown Booby Sula leucogaster Great Frigatebird Fregata minor Little Tern Sternula albifrons Gray-backed Tern Onychoprion lunatus Sooty Tern Onychoprion fuscatus Black Noddy Anous minutus Brown Noddy Anous stolidus White Tern Gygis alba

2.3.2 Counts

If a visual search results in detection of an aggregation of an MBTA-protected species, the contractor shall:

a. Record the GPS coordinates of the vantage point from which a count is made, and estimate or measure the distance to the aggregation in meters. The Contractor shall maintain an adequate distance to avoid aggregation disturbance.

b. Count the total number of adults and sub-adults in the aggregation, distinguishing by life stage if possible.

c. Estimate and map the spatial extent of the aggregation.

d. Record a general description of the occupied habitat and weather conditions during the count.

e. Describe any evidence of breeding observed, including a count of the number of nests, chicks, etc.

g. A seabird aggregation is defined as a group of six or more adults/sub-adults of the same species within close proximity. Aggregations may involve nesting, roosting, or both. Counts of groups smaller than six are not required.

h. In addition, the Contractor shall record and report the location and number of any seabird nests or chicks found on the MLA outside of an aggregation.

2.3.3 Other Species Reporting

Information about other native bird species will be collected opportunistically during seabird searches. Many other MBTA-protected species have been documented to occur in the CNMI, and rarities may arrive on Tinian that have not yet been documented.

a. The Contractor shall record and submit a complete checklist in taxonomic order of all bird species seen on the MLA during field activities.

b. The identity and location of any nest observations of other MBTA-protected and/or native resident bird species shall be recorded (Table 2).

c. The Contractor will provide descriptions of any interesting or rare species observations.

d. The Contractor will note observations of any species protected under the Endangered Species Act, both bird and non-bird taxa. Observations of ESA-listed species will not be included in the Final Report. Rather, the Contractor will communicate the location (lat/long) and observation description to the TPOC via email.

Table 2. Other MBTA-protected and/or native resident breeding species on Tinian. Any nests shall be recorded.

English Name Scientific Name MBTA Yellow Bittern Ixobrychus sinensis Y Pacific Reef-Heron Egretta sacra Y

Mariana Common Moorhen Gallinula chloropus Y White-throated Ground Dove Pampusana xanthonura Y Mariana Fruit-Dove Ptilinopus roseicapilla Y Mariana Kingfisher Todirhamphus albicilla Y Rufous Fantail Rhipidura rufifrons N Tinian Monarch Monarcha takatsukasae N Bridled White-Eye Zosterops conspicillatus N Micronesian Myzomela Myzomela rubratra N Micronesian Starling Aplonis opaca guami N

Table 3. Other MBTA-protected species documented from the CNMI. Any interesting or rare observations shall be recorded. Modified from Wiles 2005. V=vagrant; M=migrant;

P=pelagic, primarily offshore; S=pelagic, potentially nearshore or on land; R=resident

English Name Scientific Name Status Tundra Swan Cygnus columbianus V Eurasian Wigeon Mareca penelope M Falcated Duck Mareca falcata V Gadwall Mareca strepera M Mallard Anas platyrhynchos M Northern Pintail Anas acuta M Garganey Spatula querquedula M Northern Shoveler Spatula clypeata M Eastern Spot-billed Duck Anas zonorhyncha V Green-winged Teal Anas crecca M Common Pochard Aythya ferina M Tufted Duck Aythya fuligula M Greater Scaup Aythya marila M Lesser Scaup Aythya affinis V Red-breasted Merganser Mergus serrator V Laysan Albatross Phoebastria immutabilis P

White-necked Petrel Pterodroma cervicalis P

Bonin Petrel Pterodroma hypoleuca P

Black-winged Petrel Pterodroma nigripennis P

Bulwer's Petrel Bulweria bulwerii P

Streaked Shearwater Calonectris leucomelas P

Short-tailed Shearwater Ardenna tenuirostris P

Christmas Shearwater Puffinus nativitatis P

Townsend's Shearwater Puffinus auricularis P

Audubon's Shearwater Puffinus lherminieri P

Leach's Storm-Petrel Hydrobates leucorhous P

Band-rumped Storm-Petrel Hydrobates castro P

Matsudaira's Storm-Petrel Hydrobates matsudairae P

Little Pied Cormorant Microcarbo melanoleucos V

Great Cormorant Phalacrocorax carbo V

Lesser Frigatebird Fregata ariel S

Gray Heron Ardea cinerea M

Great Egret Ardea alba M

Medium Egret Ardea intermedia M

Little Egret Egretta garzetta M

Eastern Cattle Egret Bubulcus coromandus M

Black-crowned Night-Heron Nycticorax nycticorax M

Osprey Pandion haliaetus M

Black Kite Milvus migrans M

Chinese Sparrowhawk Accipiter soloensis M

Eurasian Kestrel Falco tinnunculus M

Peregrine Falcon Falco peregrinus M

Eurasian Coot Fulica atra V

Pacific Golden-Plover Pluvialis fulva M

Black-bellied Plover Pluvialis squatarola M

Kentish Plover/Snowy Plover Anarhynchus alexandrinus M

Siberian Sand-Plover Anarhynchus mongolus M

Greater Sand-Plover Anarhynchus leschenaultii M

Little Ringed Plover Charadrius dubius M

Black-winged Stilt Himantopus himatopus M

Black-tailed Godwit Limosa limosa M

Bar-tailed Godwit Limosa lapponica M

Little Curlew Numenius minutus M

Whimbrel Numenius phaeopus M

Bristle-thighed Curlew Numenius tahitiensis M

Far Eastern Curlew Numenius madagascariensis M

Eurasian Curlew Numenius arquata M

Marsh Sandpiper Tringa stagnatilis M

Common Greenshank Tringa nebularia M

Greater Yellowlegs Tringa melanoleuca V

Wood Sandpiper Tringa glareola M

Green Sandpiper Tringa ochropus V

Terek Sandpiper Xenus cinereus M

Common Sandpiper Actitis hypoleucos M

Gray-tailed Tattler Tringa brevipes M

Wandering Tattler Tringa incana M

Ruddy Turnstone Arenaria interpres M

Great Knot Calidris tenuirostris M

Sanderling Calidris alba M

Red-necked Stint Calidris ruficollis M

Little Stint Calidris minuta V

Temminck's Stint Calidris temminckii V

Long-toed Stint Calidris subminuta M

Pectoral Sandpiper Calidris melanotos M

Sharp-tailed Sandpiper Calidris acuminata M

Dunlin Calidris alpina M

Ruff Calidris pugnax M

Long-billed Dowitcher Limnodromus scolopaceus M

Swinhoe's Snipe Gallinago megala M

Common Snipe Gallinago gallinago M

Red-necked Phalarope Phalaropus lobatus V

Laughing Gull Leucophaeus atricilla V

Herring Gull Larus argentatus V

Black-headed Gull Chroicocephalus ridibundus M

Great Crested Tern Thalasseus bergii S

Common Tern Sterna hirundo M

Black-naped Tern Sterna sumatrana S

White-winged Tern Chlidonias leucopterus M

Whiskered Tern Chlidonias hybrida M

Pomarine Jaeger Stercorarius pomarinus P

Long-tailed Jaeger Stercorarius longicaudus P

Short-eared Owl Asio flammeus M

Pacific Swift Apus pacificus M

Mariana Swiftlet Aerodramus bartschi R

Mariana Crow Corvus kubaryi R

Barn Swallow Hirundo rustica M

Saipan Reed-Warbler Acrocephalus hiwae R

Dusky Thrush Turdus eunomus V

Gray Wagtail Motacilla cinerea V

White-cheeked Starling Spodiopsar cineraceus V

2.4 WORK ELEMENT 4 – Reports

2.4.1 Progress Reports

The Contractor shall submit progress reports in electronic format to the TPOC/COR via email due the 7th day of the month following any month in which field work was conducted. The progress report will provide a summary of the activities, including but not limited to: % complete of each task, work performed during the period, current problems or issues, significant events scheduled for the following period, and cumulative invoiced budget to date.

As necessary, meetings may be held in person or via teleconference to discuss progress and/or issues.

2.4.2 Draft and Final Project Report

The Contractor shall document all work conducted and findings under this PWS. The TPOC will compare progress reports, knowledge gained during in-person oversight of the project, and all other QA/QC actions to determine if the project report contains sufficient detail and incorporates all work conducted under the PWS.

SECTION 3.0 – SPECIAL REQUIREMENTS/CONDITIONS

3.1 Related Requirements and Information

If unforeseen conditions warrant any deviations from these methods the Contractor must consult with COR before altering field methods.

Work shall be conducted according to the schedule agreed during the kick-off meeting.

The Contractor shall notify the Contracting Officer immediately of any problems encountered resulting in possible delays of scheduled field work. It is recognized that weather conditions, equipment failures and site conditions can interfere with fieldwork and create unforeseen unsafe working conditions. The Contractor shall immediately report any problems or concerns encountered at the field sites.

All field notes, field data forms, photographs, etc. produced as parts of this PWS are the property of the U.S. Government. These data will not be used, in whole or in part, in any professional, scientific or non-scientific report, paper or note, published or unpublished or be part of any technical or non-technical presentation without review and written pre-authorization by the installation representative.

3.2 Experience Requirements

The Contractor shall assign a Project Manager (PM) specifically for this project. The PM must have expertise and relevant experience at a comparable level of responsibility in projects of similar size, scope and complexity and must have the following minimum qualifications: a bachelor’s degree with an emphasis in biology, ecology or a related science, and previous experience with seabird surveys in the tropical Indo-Pacific region.

The Curriculum Vitae of the PM shall be provided for approval by the COR/TPOC prior to commencement of work.

SECTION 4.0 – GOVERNMENT FURNISHED EQUIPMENT/DATA

The Government will provide relevant reports and GIS data (boundaries, historical species data if available) pertaining to the areas to be surveyed.

SECTION 5.0 – POINTS OF CONTACT

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

The Technical Point of Contact (TPOC)/Contracting Officer’s Representative (COR) is:

Jill Liske-Clark Natural Resource Specialist NAVFAC Marianas PSC 455 Box 195

FPO, AP 96540-2937

Physical Location: Saipan, MP Phone: (671) 687-0600 E-mail: jill.j.liske-clark.civ@us.navy.mil

The Contracting Officer for this contract is Mark C. Cruz.

Contractual correspondence shall be sent to:

Mark C. Cruz (CON3) NAVFAC Marianas PSC 455 Box 195

FPO, AP 96540-2937

Physical Location: Bldg 4175, Floor 3, Route 5, Santa Rita, Guam Phone: (671) 333-3175 E-mail: mark.c.cruz.civ@us.navy.mil

SECTION 6.0 – DELIVERABLES

Task Deliverable Copies Submittal Date/Timing

1. Draft/Final

POAM

Draft, electronic – MS Word via email. Final, electronic – pdf via email.

Draft, minimum of 5 business days prior to kick-off meeting. Final, within 5 business days after kick-off meeting.

2. Kickoff meeting minutes

Electronic – pdf via email Within 5 business days after kick-off meeting

3. Draft APP w/AHA; HAACP

Electronic – MS Word via email

Drafts minimum of 5 business days prior to the kick-off meeting mailto:jill.j.liske-clark.civ@us.navy.mil mailto:mark.c.cruz.civ@us.navy.mil

Task Deliverable Copies Submittal Date/Timing

4. Final APP w/AHA; HAACP Electronic – pdf via email Submitted and approved prior to any field work

5. Progress Report Electronic – pdf via email Due the 7th of the month following any month in which field work is conducted

6. Draft Report Electronic – MS Word via email or DoD SAFE

Due 11 months after contract award

7. Final Report 2 copies, pdf on 2 CDs; 2 hard copies

Within 2 weeks of receipt of Government comments

8. Photos and GIS data

2 copies, on each final report CD

Concurrent with Final Report

The period of performance is 12 months from the award date.

6.0.1. All data sheets and photos collected during field work will be submitted in a format approved by the TPOC.

6.0.2. Draft report shall be submitted no later than 11 months after contract award.

6.0.3. A final report shall be submitted within two weeks of receipt of the TPOC’s comments and shall include:

a. background information identifying the survey area, previous relevant surveys (if any), and other appropriate information

b. summary of methods

c. results

d. discussion summarizing findings from the project

e. maps and photos of searches and findings

6.0.4. All GIS data (search tracks, aggregation locations, and any other spatial data) and photographs will be delivered on DVD-ROM media.

6.0.5. All GIS data will contain populated metadata, be SDSFIE compliant, be projected in UTM Zone 55N, WGS84 and conform to the requirements in Attachment A.

6.0.6. Final deliverables will be completed and submitted to TPOC/COR no later than the end of the performance period.

Any management recommendations based on the survey results shall not be included in the report but submitted as a separate document in an email to the COR.

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), and the date of completion.

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

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.

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

• The word “UNCLAS” 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

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

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

6.7.1. The Contractor will ensure that work products are written in accordance with the 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).

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

6.8 PHOTOGRAPHS

6.8.1 Digital copies of all photographs taken while in performance of this statement of work shall be provided to the TPOC.

6.8.2 Title and all rights associated with use of the photographs shall be with

NAVFAC.

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:

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

2) 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 the 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

Assessment Method

Performance Payment and Incentive

Work Element 1 Project Management

Accurate and timely cost and schedule management and administrative support to keep the project on scope, schedule and budget.

100% Navy acceptance

Review project progress reports. Navy acceptance by Contracting Officer (KO) or task order

COR.

Lump sum payable monthly pro-rated as a percentage of completion of each task.

2 Project Plans

Completion and distribution of all planning materials including agenda, handouts, figures, schedule, PowerPoint presentation, and meeting minutes.

Accurate and timely support, attendance and technical support at the meetings.

Navy acceptance of deliverables.

This task includes, health and safety plan, accident prevention plan, hazard analysis and critical control point plan. The AHAs, and APPs must be accepted by COR and comply with all applicable codes, 100% Navy acceptance

Review of meeting minutes, deliverables, and customer feedback.

Navy acceptance by Contracting Officer (KO) or task order

COR.

Lump sum payable pro-rated as a percentage of meeting completion schedule.

/ Task Performance Standard

Acceptable Quality Level

Assessment Method

Performance Payment and Incentive standards, and regulations (including the NCP).

Work Element 3 Field Data Collection

Complete field work as specified in the Project Plans and other requirements of this PWS with no health and safety incidents. Survey and sample data collection should occur in a timely manner with no or very minimal schedule delays.

Acceptance

Announced and unannounced field inspections, schedule, check lists, review of field logs. Navy acceptance by KO or task order COR.

Monthly payment on a pro-rated scale of schedule of value items completed and accepted by the Navy.

4 Reports

Document is organized, well written and can be comprehended by the general community.

Document reviewed by an editor and includes persuasive discussions.

Document includes

• background summaries

• maps

• data analysis

• conclusions

Acceptance

Factually accurate and complete with no major deficiencies (e.g. missing information) and 8 minor deficiencies (e.g. spelling, format, wrong date).

Payment for this work element shall be retained until contractor has achieved the AQL and has been accepted by the government.

ATTACHMENT A: Geospatial Information Service Requirement for Joint Region Marianas

ATTACHMENT A: 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), provided by the GeoReadiness Center (GRC). 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.