Attachment D_PWS TE surveys Hospital lease site_102621_RFQ.pdf

EVBL PWS FOR BASIC CONTRACTS

1 Version 1.0 – Oct 20

PERFORMANCE WORK STATEMENT (PWS)

ESA-LISTED SPECIES SURVEYS

AT

US NAVAL SUPPORT ACTIVITY ANDERSEN

BARRIGADA N41557 - BA, BARRIGADA GUAM

NAVFAC MARIANAS EV2

[10/26/2021]

SECTION 1.0 - GENERAL

This Performance Work Statement solicits services for performing federally-protected threatened and endangered (T&E) plant, invertebrate, and Mariana fruit bat surveys on Guam at US Naval Support Activity Andersen Barrigada N41557(Figure 1) and shall be performed as outlined below. The duration of work under this contract shall not exceed 6 weeks 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 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 surveys for T&E plant and invertebrate species.

1.1 PRIMARY OBJECTIVE

The primary objective of this project is to provide T&E surveys at US Naval Support Activity Andersen Barrigada N41557 (figure 1). The project scope shall include all of the necessary labor and equipment associated with meeting the objective.

The contractor shall obtain final approval of the work required by 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.

1.2 BACKGROUND

Currently there are 15 plant species listed under the Endangered Species Act (ESA) (16 USC 1531 et seq.) that may be present on JRM AOR on Guam and the CNMI: Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha, 2 Version 1.0 – Oct 20

Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Phyllanthus saffordii, Psychotria malaspinae, Serianthes nelsonii, Solanum guamense, Tabernaemontana rotensis, Tinospora homosepala, Tuberolabium guamense. There is insufficient published data on the abundance and location of most of these species.

JRM lands are habitat for three federally endangered invertebrates including land snail species:

the humped tree snail (Partula gibba), Guam tree snail (Partula radiolata), and the fragile tree snail, (Samoana fragilis), and two endangered butterfly species Mariana eight-spot butterfly (Hypolimnas octocula marianensis) and the Mariana wandering butterfly (Vagrans indica). The butterflies rely on the plants Procris pedunculata, Elatostema calcareum, and Maytenus thompsonii as hosts for eggs and larvae. Little is known of the life history of these plant and invertebrate species such as population, demographic, and habitat data. This information will inform future management and recovery efforts.

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 within two (2) working days prior to the Kick-Off meeting. The POAM will be an electronic submittal via email. The POAM will be updated as required to reflect changes in milestones in monthly progress reports and the revised POAM will be distributed (electronically) five (5) working days following the kick-off meeting.

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 JRM Contracting Officer Representative (COR) within 5 days of the kick-off meeting.

3 Version 1.0 – Oct 20

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

A draft and final APP shall be submitted according to the schedule in Section 6.0. The APP shall be accessible to all site employees at all times during the project and a copy shall be mounted on or placed adjacent next to the contractor’s safety and health bulletin board in an area commonly accessed by workers. If a bulletin board is not practical to have at the site, make the APP available in a vehicle or designated spot utilized for work under this Task Order.

The draft APP with AHA must be submitted to the contracting officer or designated representative for review and acceptance. The contractor will work directly with the COR/TPOC to coordinate review, respond to comments, and obtain final acceptance of the APP.

The Contractor shall forward a copy (with all corrections) of the final APP to the COR prior to start of the work.

2.2.2 Hazard Analysis and Critical Control Point Plan. 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 10 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 digital copy of the final HACCP Plan shall be provided to the COR.

2.3 WORK ELEMENT 3 - Field Work

2.3.1 Conduct transect surveys for ESA-listed plants and invertebrates at US Naval Support Activity Andersen Barrigada N41557

1. The Contractor shall conduct transect surveys for ESA-listed plants, ESA-listed butterfly host plants, ESA-listed invertebrates, and Mariana fruit bat (Pteropus mariannus) following approved protocol in coordination with the Contractor, USFWS, and the COR.

4 Version 1.0 – Oct 20

2. The Contractor will conduct surveys on parallel fixed width (10m) transects for the above mentioned ESA-listed species on a maximum of 48 acres at US Naval Support Activity Andersen Barrigada N41557(Figure 1, Lot 1).

3. Data will be collected on all ESA-listed species encountered.

4. GPS coordinates of transects shall be recorded and all track logs will be recorded. Any ESA-listed species sighted will be identified and GPS coordinates will be recorded with a unit capable of sub-meter accuracy acquired by the Contractor. The data dictionary will be supplied by NAVFAC GIS personnel.

5. All GIS data will be collected as per Navy GIS guidelines (Attachment A).

2.4 WORK ELEMENT 4 – Reports

2.4.1 Progress Reports

Monthly Progress Reports/Meetings

Figure 1 US Naval Support Activity Andersen Barrigada N41557. Surveys to be conducted in Lot 1.

5 Version 1.0 – Oct 20

The Contractor shall submit monthly status reports in electronic format to the COR via email on the 5th of each month following the kickoff meeting. 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 Summary Report

The Contractor shall document all work conducted and findings under this PWS. The COR will compare monthly reports, knowledge gained during in person oversight of the project, and all other QA/QC actions to determine if the project summary 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 within two business days of any problems that occur to prevent the 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 will also immediately report any problems or concerns encountered at the field sites

3.2 Experience requirement – Personnel conducting the surveys shall have prior experience with threatened and endangered plants and snails with similar habitat in the Marianas, including surveys conducted at sites where there is presence of listed plants and snail activity was observed. A list of personnel that will conduct work on this project and their Curriculum Vitae with relevant experience should be submitted for approval by the COR prior to commencement of work.

SECTION 4.0 – GOVERNMENT FURNISHED EQUIPMENT/DATA

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

6 Version 1.0 – Oct 20

SECTION 5.0 – POINTS OF CONTACTS

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 COR. 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 COR. Keep the COR informed of progress and problems encountered.

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

Mario Martinez Natural Resource Specialist NAVFAC Marianas PSC 455 Box 195

FPO, AP 96540-2937

Physical Location: Bldg 4175, Floor 3, Route 5, Santa Rita, Guam Phone: (671) 339-7348 E-mail: mario.martinez@fe.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@fe.navy.mil

7 Version 1.0 – Oct 20

SECTION 6.0 – DELIVERABLES

Task Deliverable Copies Submittal Date/Timing

1. POAM Electronic – pdf via email 2 days prior to kickoff meeting

2. Kickoff meeting notes Electronic – pdf via email 5 business days after kickoff meeting

3. Activity Hazard Analysis, Accident Prevention Plan

Electronic – pdf via email, DoD Safe, or similar.

Draft within two weeks following the kickoff meeting – Final within 10 days following receipt of draft comments

4. Monthly Progress Report

Electronic – pdf via email Monthly following kickoff meeting due first week of month

6. Draft summary report Electronic – pdf via email, DoD Safe, or similar.

No later than 10 days after completion of surveys

7. Final summary report Electronic – pdf via email, DoD Safe, or similar.

10 days after receipt of draft comments

The period of performance is 6 weeks from the award date.

6.0.1. A final database populated with all data collected during surveys. Database will conform to the format approved by COR.

6.0.2. Data sheets from all surveys

6.0.3. Draft summary report shall be submitted no later than 10 days after completion of surveys.

6.0.4. A final report shall be submitted within 10 days after receipt of the COR’s comments shall include:

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

b. summary of methods (including field methods)

c. results

d. discussion summarizing findings from the project

e. GIS maps of surveys

6.0.5. All GIS data (delineation of habitats and any other spatial data) will be delivered on DVD- ROM media.

6.0.6. All GIS data will contain populated metadata, be SDSFIE compliant, and projected in UTM Zone 55 North, WGS84.

6.0.7. Final deliverables will be completed and submitted to COR NLT than POP.

8 Version 1.0 – Oct 20

Any management recommendations based on the survey results shall not be included in the report but mailed 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

9 Version 1.0 – Oct 20 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 COR.

10 Version 1.0 – Oct 20

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 COR 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

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

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.

11 Version 1.0 – Oct 20

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

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

Work Element / Task Performance Standard

Acceptable Quality Level

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 as a percentage of completion of each task.

Work Element 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, standards, and regulations (including the NCP).

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.

Work Element 3 Field Work

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 prorated scale of schedule of value items completed and accepted by the Navy.

Work Element 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 for each site

• background summaries

• maps

• data analysis

• conclusions

Acceptance

Factually accurate and complete with no more than 2 major deficiencies (e.g. missing information) and 5 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.

12 Version 1.0 – Oct 20

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

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

2. Basic Deliverable Requirements:

a. Submittals, Government Review and Acceptance:

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

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

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

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

b. GIS Data Format: NAVFAC’s GIS data is an ERSI Geodatabase format, Check for the

Navy approved current version of ArcGIS.

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

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

Location_yyyymmdd.gdb

iii. Location = Location of the geographic information, defined to the appropriate level of detail. Names begin at the regional level, using the 2-

13 Version 1.0 – Oct 20 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.)

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

c. Data Retention: all proprietary data (electronic and paper formats) must be removed from contractor equipment and possession and returned to the government at the end of the period of performance and before the final invoice is approved.

d. Data Structure:

i. Unless specifically directed otherwise, all data shall be structured according to the current version of the Spatial Data Standards (SDSFIE) in use by NAVFAC. This is the current version of the Navy Data Model (NDM). Information on the SDSFIE data model can be found at: https://sdsfieonline.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/

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

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

Acceptable formats: MS Excel or MS Word. (Adobe PDF is not an acceptable format. New non-SDS compliant attributes (meeting SDSFIE criteria) will require precise schema definitions.

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

f. Attribute Population:

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

SDSFIE.

https://sdsfieonline.org/ http://datacollectionadvisor.com/

14 Version 1.0 – Oct 20

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

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

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

Data Type: Date Default Value: null

3. Data Integrity

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

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

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

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

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

f. No sliver polygons

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

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

15 Version 1.0 – Oct 20

4. CAD Format Deliverables:

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

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

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

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

5. Coordinate System:

All geospatial data, unless specified otherwise, shall be in the Geographic Coordinate System: GCS_WGS_1984, Datum: D_WGS_1984.

6. Metadata:

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

Attributes for the currentversion are listed in ATTACHMENT B

b. Layer Level Metadata: Layer level metadata is required for all deliverables, structured according to the FGDC Content Standard for Digital Geospatial Data (CSDGM). Details on the standard can be found at http://www.fgdc.gov/metadata/geospatial-metadata-standards.

7. Quality Control and Quality Assurance:

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.

https://www.wbdg.org/ffc/army-coe/cad-bim-technology-center 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

16 Version 1.0 – Oct 20

c. All required attributes (per NDM 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.

8. Field Collection

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

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

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

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

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

17 Version 1.0 – Oct 20

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

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

9. Photography.

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

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

18 Version 1.0 – Oct 20

ATTACHMENT 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:

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

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

• 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

DEFINITION MANDATORY

POPULATION

GUIDANCE

DATA

TYPE

FIELD

SIZE

EXAMPLE

VALUE

***IDPK

Primary Key. A unique, user defined identifier for each record or instance of an entity. No

Populate with unique ID or ID series agreed upon prior to project start. DO NOT use the objectID Text 40 CR 66-02-1998 http://datacollectionadvisor.com/

19 Version 1.0 – Oct 20

InstallationID

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

Populate with the appropriate value from the SiteCode constraint table based on iNFADS or RPAO guidance. Text 11

Code: N61755 Description:Navy Base Guam, JRM

FeatureName The name of the feature Yes

For features that are not stored in iNFADS, populate with a common name of the feature if one exists, using Proper Case Text 80

Threatened and endangered Species observation

20 Version 1.0 – Oct 20

FeatureDescription

The narrative describing the feature. No

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"). Text 255

Location of host plant of 30 Dendrobium guamense an epiphytic species listed by USFW and found in a construction footprint J001B.

Owner

The DoD Component or other entity that owns the feature. YES

Populate with the appropriate value from the Owner constraint table. Text 17

Code: USN Description: US Navy

21 Version 1.0 – Oct 20

Creator

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 Yes

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". Text 20 PetermanJ

DateCreated

The date the feature was created for the first time. Yes

Populate with the date the feature was created (Geometry and Attribute). Date NA 6/28/1974

CollectionMethod

The method used to collect the geometry of the feature. Yes

Populate with the appropriate value from the CollectionMethod constraint table. Text 28

Code:

HeadsUpImag eryMgGPSVrfy Description:

Heads Up Imagery Mapping Grade GPS Verify

LocationAccuracy

The location accuracy for the data that was collected and verified. Yes

Populate with the accuracy value followed by a space and then the abbreviation of the unit of measurement in lower case. Text 50 +/-1m

22 Version 1.0 – Oct 20

Editor

The contractor or person that edited the feature attribution or geometry from its original or previous value. This is to be stated as last name of the person and then their first initial. For example, Jane Smith would be attributed as SmithJ. Yes

The name of the federal employee or name of the contracting company that last edited the information for the feature (e.g., Art Vandelay as "VandelayA" or Vandelay Industries as "Vandelay Industries"). If editing within Citrix M&A Spatial Database Engine (SDE) environment, this attribute will be auto populated with the Citrix user name. Text 20 PetermanJ

DateEdited

The date that the feature was edited from its original or previous value. Yes

If editing within the Citrix

M&A SDE

environment, this attribute will be auto populated.

Otherwise, populate with the date the feature was edited (Geometry and/or Attribute). Date NA 6/28/1974

POPULATION GUIDANCE

FIELDALU

3. Data Integrity