About this file

N4008518R87160010.pdf

View the file

Other files

File Type Posted
Attachment_F_AMD23.pdf PDF
N4008518R87160023.pdf PDF
N4008518R87160022.pdf PDF
N4008518R87160021.pdf PDF
N4008518R87160020.pdf PDF
N4008518R87160019.pdf PDF
N4008518R87160018.pdf PDF
N4008518R87160017.pdf PDF
N4008518R87160016.pdf PDF
P293_RUBBER_COMPOUNDING_area.dwg DWG drawing
Attachment_F.pdf PDF
N4008518R87160015.pdf PDF
N4008518R87160014.pdf PDF
N4008518R87160013.pdf PDF
N4008518R87160012.pdf PDF
N4008518R87160011.pdf PDF
N4008518R87160009.pdf PDF
N4008518R87160008.pdf PDF
N4008518R87160007.pdf PDF
Site_Visit_Log.pdf PDF
N4008518R87160006.pdf PDF
N4008518R87160005.pdf PDF
JAs_Redacted.pdf PDF
N4008518R87160004.pdf PDF
N4008518R87160003.pdf PDF
Amendment_0002.pdf PDF
SECNAV_5512_DBIDS_Individual.pdf PDF
Amendment_0001.pdf PDF
Local_Visitor_Request_Form.pdf PDF
Attachment_B.pdf PDF
Attachment_C.xls XLS spreadsheet
Attachment_A.docx DOCX document
N4008518R8716.pdf PDF
Show all 33

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to revise the schedule and amend the specifications. The proposal due date of 13 November 2018 remains unchanged.

See SF30 Block 14 Continuation Page

1. CONTRACT ID CODE PAGE OF PAGES

J 1 12

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 26-Oct-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N4008518R8716

X 9B. DATED (SEE ITEM 11)

31-Aug-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

26-Oct-2018

CODE

NAVFAC MID ATLANTIC

ACQUISITION CORE

9324 VIRGINIA AVENUE

NORFOLK VA 23511-3095

N40085 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N4008518R8716

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE (SF 30)

The following have been added by full text:

AMENDMENT 0010

PROPOSED AMENDMENT CONTINUATION SHEET

SECTION 01 44 00.22 ARCHAEOLOGICAL MONITORING (PWD ME)

ADD ‘SCOPE OF WORK PHASE III DATA RECOVERY OF TWO ARCHAEOLOGICAL SITES

PORTSMOUTH NAVAL SHIPYARD, KITTERY MAINE’ to further define the requirements of this section.

-- End of Amendment 0010 –

SCOPE OF WORK

PHASE III DATA RECOVERY OF TWO ARCHAEOLOGICAL SITES

PORTSMOUTH NAVAL SHIPYARD, KITTERY MAINE

I. INTRODUCTION

This proposed project involves completion of a Phase III data recovery of two archaeological sites to be adversely affected by construction of a new building (Building 404). The Phase III to be carried out under this task order consists of five parts: 1) background research and preparation of a research/work plan; 2) physical data recovery during ongoing construction activities; 3) preparation of reports summarizing findings and answering the research questions; 4) curation of artifacts collected in accordance with 36 CFR 79; and 5) preparing and presenting at least two lectures on the findings of the Phase III work.

II. BACKGROUND

Two known NRHP eligible archaeological sites are present within the project area: ME-226-224, an 1820s shipway, and ME -226-225, remains of the Franklin Shiphouse (c. 1838-1936). The remainder of the new facility footprint is located within an area of archaeological potential.

This work is required pursuant to the National Historic Preservation Act of 1966 as amended (NHPA) including Section 106 and will be a stipulation in consultation between the Department of the Navy and the Maine State Historic Preservation Office (SHPO) for the execution of P-293, Paint, Blast, and Rubber Facility Consolidation.

III. OBJECTIVE

The purpose of this scope of work is to mitigate the loss of two archaeological sites through analytical research, data recovery, artifact curation, report preparation, and outreach. Reports prepared will be archived at the Maine State Historic Preservation Office, Augusta, Maine and the Public Works Department, Portsmouth Naval Shipyard, Kittery, Maine.

It is mandated that the contractor hired have personnel who meet the Secretary of the Interior’s Professional Qualifications as a Historic Archaeologist in accordance with 36 CFR Part 61, and in accordance with the standards of the State of Maine. The Phase III to be carried out under this task order consists of five parts:

1) background research and preparation of a research/work plan;

2) physical data recovery during ongoing construction activities;

3) preparation of reports summarizing findings and answering the research questions;

4) curation of artifacts collected in accordance with 36 CFR 79; and

5) preparing and presenting at least two lectures on the findings of the Phase III work.

Artifacts collected during the recordation shall be curated in accordance with 36 CFR 79, at a location to be determined by the Navy and contractor. This Phase III also includes an element of outreach to educate interested personnel and members of the public about the information collected as part of this data recovery effort.

IV. GENERAL TECHNICAL APPROACH AND REPORTS

1. It is mandated that the contractor performing this work meet the Standards of the Secretary of the Interior as a Historic Archaeologist in accordance with 36 CFR Part 61 and on Maine’s Level II approved list.

Field crew may be supervised by someone who is on the Level II list.

2. All work shall adhere to the Maine Historic Preservation Commission’s State Historic Preservation Office Standards for Archaeological Work in Maine (Maine State Rules 94-089, Ch. 812).

3. Research associated with Task One shall be conducted at relevant repositories which include, but are not limited to the following: Public Works Department, Portsmouth Naval Shipyard in Kittery, Maine;

Portsmouth Naval Shipyard Museum in Kittery, Maine; Portsmouth Athenaeum in Portsmouth, New Hampshire; Rice Public Library in Kittery, Maine; University of New Hampshire Special Collections in Durham, New Hampshire; National Archives offices in Washington D.C. and College Park; and National Archives Northeast Regional Office in Waltham, Massachusetts.

4. The data for this task will be collected in accordance with resource grade data as described in the Data Collection Procedures section of Attachment A (NAVFAC MIDLANT EV GIS Data Deliverable Specifications).

V. TASK ONE: BACKGROUND RESEARCH AND PREPARATION OF RESEARCH/WORK PLAN

A. Prior to starting fieldwork, the contractor shall review all available background information, including previous archaeological reports, historic maps, historic photographs, primary/secondary sources and construction drawings (past and proposed) to develop a Phase III data recovery research proposal designed to maximize data recovery.

B. The Phase III data recovery plan will propose what research questions the data recovery will answer. The data recovery techniques proposed must be sufficient to do the best currently possible job recovering as much potential data as possible from the ground for the widest range of research goals. a scientific research proposal designed to maximize data recovery.

C. Prepare a draft, final draft, and final research/work plan. The draft plan shall be provided electronically to the COR for Navy review and comment. Once Navy comments are received, the Contractor will have 15 days to incorporate the comments into the final draft. Two electronic and one hard copy of the final draft research/work plan shall be provided to the COR for Navy, SHPO, and other stakeholder review. Once comments are received and provided to the Contractor, the Contractor shall finalize the plan within 15 days and provide two hard copies and two electronic copies to the COR. No fieldwork may commence without an approved, final, research/work plan.

VI. TASK TWO: PHYSICAL DATA RECOVERY

A. All data recovery efforts will occur in conjunction with ongoing construction activities. The sites are located below paved areas and existing buildings and coordination with the Prime contractor is paramount.

Provide sufficient field crew staff to enable efficient recordation and maintain project schedule.

B. Provide all documentation necessary to capture the widest range of information for future study, including, but not limited to: photographic documentation, measured drawings, artifact collection, soils data (type, profiles, Munsell colors), GPS points, and mapping.

VII. TASK THREE: REPORT PREPARATION

A. Prepare a draft, final draft, and final report summarizing the findings of the physical data recovery and explaining how the information gathered answered the questions posed in the research design. The report shall present the results of all archaeological investigations and actions conducted during the survey to include, but not be limited to, an artifact inventory as an appendix, analysis, data synthesis and interpretation. The draft report shall be 99% complete, and shall be provided electronically to the COR for Navy review and comment. Once Navy comments are received, the Contractor will have 15 days to incorporate the comments into the final draft. Five electronic and five hard copies of the final report shall be provided to the COR for Navy, SHPO, and other stakeholder review. Once comments are received and provided to the Contractor, the Contractor shall finalize the report within 30 days and provide three hard copies and three electronic copies to the COR. At least one hard copy of the report shall be provided on archival paper and one electronic copy shall be provided on an Archival Gold CD. The electronic submissions shall contain all photographs and digital records related to this project.

VII. TASK FOUR: ARTIFACT CURATION

A. The contractor will analyze, stabilize, curate, catalog, and accession all artifacts in accordance with 36 CFR 79, and the standards of the Maine SHPO, and the Standards of the Interior, for ultimate disposition.

However, effort should be made to minimize the amount of archaeological material remains permanently curated by reserving such treatment for diagnostic artifacts and other significant and environmentally sensitive material that will add important information to site interpretation.

B. This contract shall include all costs associated with the preparation of artifacts and records and the initial fees charged by the facility accepting the collection recovered under this Scope of Work. Copies of all records (documents, logs, maps, images and pertinent data) relating to this process will be submitted to the Project Manager at the conclusion of this project.

C. This contract shall include all costs associated with the preparation of artifacts and records and accessing fees charged by the curatorial facility, as well as the cost of transferring the collection to the curatorial facility.

VIII. TASK FIVE: OUTREACH

A. The contractor shall prepare a presentation explaining the archaeological process and findings from the Phase III. The presentation shall be developed in coordination with the PWD-ME Cultural Resources staff.

Provide a draft presentation in PowerPoint to the COR for Navy review and comment. After receiving Navy comments on the draft presentation, the CTR will have 15 days to incorporate comments and prepare a final draft presentation. An electronic copy of the final draft presentation and any accompanying notes will then be provided electronically to the COR for Navy review. Once Navy comments are received, the CTR will have 30 days to incorporate the final changes. Two electronic copies of the presentation shall be provided on CD in PowerPoint and PDF. Copies of all notes to accompany the presentation shall also be provided.

B. The presentation shall be offered in partnership with interested parties in the Kittery/Portsmouth area.

Assume two, hour long, presentations will be required and scheduled at mutually agreeable times. The presentations will be held within fifteen miles of the project location.

V. DESCRIPTION OF MEETINGS

A. Kickoff Meeting: Prior to the submission of the research design/work plan, a kickoff meeting will be held at Portsmouth Naval Shipyard, Kittery, Maine or via teleconference to discuss the logistics, fieldwork and information required for completion of the Phase III recordation.

B. Field Meetings: Assume three formal meetings will be held in the field during data recovery to review findings, strategize solutions, and provide general updates on fieldwork. Meetings will last no more than one hour. Additional ad hoc meetings will occur as required throughout fieldwork.

C. Outreach Meetings: Assume two, two hour meetings will be required with PWD-ME Cultural Resources staff to prepare for the required lecture.

VII. GENERAL REQUIREMENTS

A. Contractor Qualifications: It is mandated that the archaeologists (P.I. and P.A.) contracted meet the professional standards of the Secretary of the Interior as an Archaeologist as required by 36 CFR 61, as well as being listed on the Maine Level III Approved List.

B. Contractor Staff: The contractor shall contact the NAVFAC COR when any change in key personnel (e.g.

Principal Investigator (PI), Principal Archaeologist (PA)) occurs after the initial kick-off meeting and document the reason for the change.

C. Meeting Minutes: The contractor is responsible for recording minutes of all meetings and furnishing a copy of the minutes to the NAVFAC MID-ATLANTIC representative, regardless of attendance, within 15 days, unless otherwise specified by the NAVFAC MID-ATLANTIC representative.

D. Original Materials: Originals of all materials, software, text, maps, photographs, negatives and graphics prepared under this contract or furnished to the contractor are considered to be the property of the United States Government and shall be turned over to the POC upon completion of the Delivery Order. Use of a camera and/or laptop may require permits. Photographs may require review and clearance prior to release.

Clearance of photographs may take between 21-120 days.

E. Map Data: All GIS deliverables will be created and submitted in accordance with the current NAVFAC

MIDLANT EV GIS Data Deliverable Specifications (see Attachment). All data collection, processing, and deliverables should conform to this document.

F. Dissemination of Data: The contractor will not disseminate information, data, reports, recommendations, or any other material of any nature pertaining to the work for which services are performed under the terms of this delivery order unless written permission is obtained from the Contracting Officer.

G. Documents: The contractor shall forward all submissions (e.g. research design, draft and final reports, etc.);

informal documents (field notes); and documentation (original reports, drawings, etc.) directly to the

NAVFAC COR.

H. The contractor shall submit to the NAVFAC COR all documentation (original reports, drawings, etc.) upon completion of work. Documentation shall be provided in editable electronic format (Microsoft Word, Excel, ESRI ArcINFO, etc.) and in PDF upon completion of work.

I. Government Furnished Data: The contractor shall use the Government’s GIS and AutoCAD maps of the installation. All Government existing data, located at the installation and NAVFAC MIDLANT will be made available to the contractor for review. The data shall not be removed from Government offices unless otherwise approved by the NAVFAC COR.

J. All draft reports shall be 99% completed. The drafts shall adhere to the highest standards acceptable in the profession (AAA, SAA) and shall adhere to the ME SHPO guidelines for research and reporting Phase III Data Recovery. All draft and final draft reports shall have line numbers in the margins to provide ease of review.

K. All comments on draft documents shall be provided to the contractor via Comment Matrix; the Contractor shall respond within the Comment Matrix and return it to the Government with each next submission.

L. The contractor shall submit to the NAVFAC MID-ATLANTIC representative all documentation (original reports, drawings, etc.) upon completion of work. Documentation shall be provided in editable electronic format (Microsoft Word, Excel, ESRI ArcINFO, etc.) and in PDF upon completion of work.

VIII. GOVERNMENT FURNISHED INFORMATION

A. Copies of all prior archaeological investigation reports and other scientific reports relevant to the work which are not in the public sector.

B. Existing condition project drawings.

IX. PROJECT MILESTONES

TASK SUBMITTAL DATES

NOTICE-TO-PROCEED TBD

PROJECT KICKOFF MEETING 15 DAYS FROM CONTRACT AWARD

DRAFT RESEARCH DESIGN 30 DAYS FROM CONTRACT AWARD

FINAL DRAFT RESEARCH DESIGN 60 DAYS FROM CONTRACT AWARD

DRAFT REPORT 60 DAYS FROM COMPLETION OF FIELDWORK

FINAL DRAFT REPORT 90 DAYS FROM COMPLETION OF FIELDWORK

FINAL REPORT 120 DAYS FROM COMPLETION OF FIELDWORK

DRAFT LECTURE 150 DAYS FROM COMPLETION OF FIELDWORK

FNALS DRAFT LECTURE 180 DAYS FROM COMPLETION OF FIELDWORK

FINAL LECTURE 210 DAYS FROM COMPLETION OF FIELDWORK

ARTIFACT CURATION COMPLETE 365 DAYS FROM COMPLETION OF FIELDWORK

Attachment: NAVFAC MIDLANT EV GIS Data Deliverable Specifications

Deliverable Requirements:

Geographic Information System Data: Geographic Information System (GIS) data deliverables shall be in a personal geodatabase format that is compliant with ESRI ArcGIS version 10.5, and conform to current Navy adaptation of the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) version 3.03, with the singular exception of stormwater data, which should conform to the Navy adaptation of the SDSFIE version 2.6 model. GIS data that is required but will not conform to this model should be discussed with the Navy COTR and the MIDLANT EV GIS Coordinator during the kickoff meeting. GIS data will be natively collected using the WGS84 (D_WGS_84) datum, in the WGS 1984 geographic coordinate system (GCS_WGS_84), using meters as the standard unit of measurement. All GPS data shall be submitted in both a raw and post-processed form with the final deliverable. Metadata shall be completed and included in an XML format, in accordance with the FGDC Content Standard for Digital Geospatial Data. At a minimum, the following metadata attributes will be populated:

1) Item Description

a) Contact (Details) - contact information for the data steward

i) Person K. Dean Wright

ii) Organization NAVFAC MIDLANT EV

iii) Position GIS Coordinator

iv) Telephone 757-341-0452

v) Email kelly.wright@navy.mil

b) Description – characterization of the data

i) Abstract

ii) Purpose

iii) Keywords

c) Time Period - explains how current the dataset is

i) Currentness Reference

ii) Date

d) Keywords – word/phrase descriptors of the data

2) Data Quality

a) Positional Accuracy – accuracy assessment of the data

i) Horizontal Accuracy Report

ii) Vertical Accuracy Report (if applicable)

b) Source Information – list of sources and a short citation of each

i) Source Citation (Details)

(1) Title

(2) Originator

(3) Publication Date

c) Process Step – an explanation of how/when the data was created

i) Process Description

ii) Process Date

3) Spatial Reference

a) Horizontal Coordinate System

b) Vertical Coordinate System (if applicable) – vertical datum information

i) Datum Name

ii) Distance Units

Data Integrity

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 referencing an established standard such as NMAS or ASPRS.

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

o No erroneous overshoots, undershoots, dangles or intersections in the line work o 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.

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

o No sliver polygons o Digital representation of the common boundaries for all graphic features must be coincident, regardless of feature layer o Geometric network connectivity must be maintained for utility networks.

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.

Data Model

The geodatabase schema shall follow the Navy adaptation of the GIS Data Guide implementation of the SDSFIE data model and data layers will be captured accordingly. General information on the core SDSFIE data model can be found at: http://www.sdsfie.org, and specific information about the Navy adaptation of this data model will be provided by the NTR.

If new data is being created the contractor must 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, MS Word, PDF. Local attributes (meeting SDS experienced level) will require precise schema definitions.

Government Furnished Materials

The Government will provide the contractor access to necessary geospatial data (via personal geodatabase), reports, schematics, or other pertinent information as described in the SOW.

When requesting data from the GRC, the contractor will identify the current SDSFIE feature classes or datasets they require. The government NTR will be contacted prior to the release of any information to verify requirements. A Limited-use/non-disclosure agreement may need to be completed prior to the release of any data.

The contractor must verify with the NTR that they are working with the most recent version of the dataset at the beginning of each contract and must delete any copies of data in their possession at the end of each contract.

Copying of the database is prohibited.

All project GIS data (government furnished and produced as a result of this contract) will be removed from all contractor data storage environments upon the conclusion of the project. This is to prevent inappropriate future use of what may be outdated data, and to prevent data seepage.

Data Collection Procedures

All data collection must include:

Feature Attributes: The contractor shall work with NTR to identify appropriate attributes for the data collected.

Examples include Primary Key field, classification, type, location, ID number, and any other necessary attributes (specified by the Government) for all new/updated/edited features first by field verification and then by existing sources.

Metadata must include an accuracy statement at the 90% or 95% confidence interval. Accuracy statements should include the method of determination, preferably from a recognized standard such as National Standard for Spatial Data Accuracy (NSSDA) (as outlined in “Geospatial Positioning Accuracy Standards, Part 3:

National Standard for Spatial Data Accuracy,” published by the Federal Geographic Data Committee (FGDC), dated July 1998).

Field Collection Where field data collection is stipulated in the contract, the contractor shall utilize conventional and other methods, such as a total station or Global Positioning System (GPS) in accordance with the applicable Geospatial Positioning Accuracy Standards published by the Federal Geographic Data Committee (FGDC).

At a minimum, the contractor shall provide resource grade GPS collection at a horizontal accuracy level of +/- 1m (post-processed) and shall use differential correction to target accuracies of +/- 0.5 m. Recreation grade GPS (Garmin GPS devices, cellular devices such as cell phones or iPads, etc.) may be used for field navigation, but are not acceptable for data collection unless agreed upon by both the NTR and MIDLANT EV GIS Coordinator in advance.

Where appropriate (as stipulated in the contract or as otherwise determined by the Government), the contractor shall use survey grade GPS. 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.

GPS data on the location of utility lines and other features shall be captured at a minimum every 50 ft 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 should 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 will be collected at every vertex of the feature and processed as a polygon.

Linear GIS data that captures directionality of flow (such as linear wetlands or stormwater pipes) will be recorded in a manner that supports this. Specifically, this data shall be captured beginning with the higher elevation first, proceeding to the lower elevation in order, such that symbolizing using “Arrow At End” will properly display flow direction.

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.

All raw and post-processed GPS data will be included with the final deliverable.

Data Deliverables

Unless explicitly listed in the contract as not to be delivered, all survey/inventory contracts are expected to have both survey/inventory data (in all appropriate geometries), as well as data in the appropriate feature classes detailing the results of those surveys/inventories. For example, a deliverable that includes feature classes documenting an inventory for cultural resources shall also have all appropriate feature classes detailing the results of the cultural resource survey (e.g., archaeological sites found, areas of archaeological sensitivity, historic districts, cemeteries, burials, etc.). Similarly, a deliverable that includes feature classes documenting a natural resources inventory shall also have all appropriate feature classes detailing the results of that inventory (e.g., species observed, wetlands delineated, spatial extent of invasive species, forest compartment/stand areas, vegetation, etc.). All feature classes are to be fully attributed and conform to the current version of the Navy Data Model (where appropriate) at the time of the contract award. Joinable tables with data that go beyond the Navy Data Model attribution are permitted, but shall be discussed with the NTR and the MIDLANT EV GIS Coordinator before any deliverables are submitted for review. Any questions about what feature classes are expected to be delivered as part of any contract should be addressed during negotiations or during the kick-off meeting.

All GIS data created, collected, or used in support of the contract effort shall be delivered to the Navy as part of the draft and final data submission. The only exception to this requirement is data that comes from a publicly available GIS external service (such as the ESRI World Imagery service).

GIS data collected from a non-Navy source should be included in the final deliverable, and should be in an unaltered format. For example, if soils data from the United State Geological Survey (USGS) are used in a project, that data will be included in the final deliverable in an as-collected state. GIS data from non-Navy sources should not be loaded into the Navy Data Model unless the contractor is explicitly directed otherwise.

Data Submittal Environments

The contractor will deliver all GIS data in an ArcGIS personal geodatabase that is compliant with ESRI ArcGIS software, version 10.3. Any other data formats, such as shapefiles, must be agreed to by both the NTR and the MIDLANT EV GIS Coordinator during the kickoff meeting. Data submittals must match the current version of the GRC repository (on a project specific basis as discussed in Government Furnished Materials section).

The Contractor will provide three (3) complete sets of the project ArcGIS file geodatabase. Specific transmittal instructions will be provided to the Contractor when the data is ready to be delivered.

Acceptable Delivery Media:

CD-ROM

DVD-ROM

External Hard Drives (only if pre-approved by NAVFAC CIO)

Digital media must have an external label listing a short description of contents, a sequence number if there are multiple volumes, and the date of media creation.

Government Review

The Government shall review the submitted data and documentation upon completion of all stated work. Missing or incomplete items will be documented and forwarded to the contractor for completion. Failure to adhere to any of the stated delivery specifications could result in rejection of deliverables and nonpayment. Contractors shall submit data and documentation samples at 25% and 75% project completion to avoid the rejection of final deliverables.

SECTION 00 21 16 - INSTRUCTIONS TO PROPOSERS

The following have been modified:

ADDITIONAL INFORMATION

Within the overall project schedule, commence and complete the work in phases. Complete each phase of the work within the number of calendar days stated in the following schedule.

a. Schedule start day: The day designated as the beginning of a particular phase; the number listed is the number of calendar days from the award of contract.

b. Duration: The number of days designated for a particular phase; the number listed is the number of calendar days from the start of the phase.

c. Schedule:

Phase Description

Schedule Start Day Duration

1 • Disassemble Building 74A and relocate to a location to be identified by the Contracting Officer.

• Internally move Shop 56 within 96

• Renovate 96 for Shop 71

• Limited site work activities in area of new PBR

• Building 60 Test Pad and Utility Modification

• Building 74 Elevator Replacement (Bid Option) & 2nd Floor Bathroom Reno (Bid Option)

15 FEB 19 290 Calendar Days

2 • Move Shop 71 from 285 to 96

• Demo 285

• Relocate and tie-in 74 utilities

• Demo 74 West Wing

• Continue site work activities

• 8” & 16” Potable and Fire Water Utility Work

19 MAR 19 420 Calendar Days

3 • Construct new PBR (Building 404) 25 FEB 20 785 Calendar Days

4 • Move Shop 71 operations from 18 and 96 to 404

• Move Shop 76 operations from 20, 60, and 362 to

• Final site modifications

20 JAN 22 120 Calendar Days

5 • Renovate 362

• Renovate 60

• Remove temporary facilities from 96 and restore

17 MAR 22 235 Calendar Days

6 • Move Shop 06 from 74 and 55 to 60

• Renovate 74

• Move Shop 71 from 284 to 362 and 74

• Move Shop 76 from 42 to 74

• Renovate 55

8 NOV 22 220 Calendar Days

7 • Move Shop 71 Nuc Paint from 18 to 55

• Move Shop 71 Varnish/Modeling from 64 to 55

• Move Shop 71 from 284 & 18 to 74

• Move Shop 76 from 42, 60 (Lead Vacuum), to 74

• Demolish 151 (Bid Option), 284, 289, 400

• Construct Tree Box Filter

16 JUN 23 168 Calendar Days

d. The work of a particular phase is complete and accepted before the scheduled completion day, immediately begin work on the subsequent phase unless otherwise restricted.

In addition to referring to FAR Clause 52.236-14 Availability and Use of Utility Services, please refer to spec 01 50

00.00 22 Temporary Construction Facilities and Controls (PWD ME).

(End of Summary of Changes)

File details come from the government source that posted it.