26-1306 Note 1.pdf

RFP N62742-26-R-1306

Notice No. 1

April 23, 2026

PRE-PROPOSAL QUESTIONS & ANSWERS

JFY 2022 PROJECT J-875, BATTLE STAFF TRAINING FACILITY,

U.S. NAVSUPPACT MCB CAMP BLAZ, GUAM

NOTE: The following questions and answers are provided for INFORMATION ONLY. The RFP remains unchanged unless it is amended in writing on a Standard Form 30.

1. Reference: Spec Section 01 57 19.03 20

MEC / UXO Requirements. Spec section 01 57 19.03 20 is included in the RFP, which to our understanding is outdated. Please advise if Spec Section 01 57 19.03 21 “Supplemental Temporary Environmental Controls – Secretary of the Navy (SECNAV) Explosive Safety Risk Acceptance Within Joint Region Marianas” would apply to this project, and if so, provide revised spec section for the J-875 project. (See attached from P-678 as reference).

RFI No. 01_01 57

19.03 21 P-678 Supp

ANSWER: Response deferred.

2. Reference: Spec Section 03 42 13.00 10

Plant Precast Concrete Products - Reinforcment. Spec section 03 42 13.00 10 includes reference ASTM listings for epoxy coated reinforcing bars and steel wire and welded wire reinforcement.

As the project site is well above the water table, and local precast manufacturers do not provide epoxy coated reinforcement in their products, we interpret that the epoxy coated reinforcement in not intended for this project.

Please confirm that if epoxy coated reinforcement is not specifically called out for in the product detail in the drawings, it is not required.

DEPARTMENT OF THE NAVY

COMMANDER

NAVAL FACILITIES ENGINEERING SYSTEMS COMMAND PACIFIC

258 MAKALAPA DRIVE SUITE 100

PEARL HARBOR HI 96860-3134

3. We respectfully requests a bid due date extension for the above-referenced project due to impacts caused by Typhoon Sinlaku, which recently devastated Guam.

As a result of Typhoon Sinlaku, a significant portion of the island experienced prolonged outages, including loss of power, potable water, and communication services for at least one week. These conditions materially disrupted normal business operations, access to offices, coordination with subcontractors and suppliers, and preparation of complete and responsive bid submissions.

Given these circumstances, we respectfully request a minimum one (1) week extension of the bid due date, as follows:

• Current Bid Due Date: June 16, 2026 (HST)

• Requested Revised Bid Due Date: June 23, 2026 (HST) Granting this extension will help ensure fair competition and allow offerors adequate time to prepare thorough and responsive bids following the island-wide disruption caused by the typhoon.

ANSWER: The proposal due date will be extended to June 23, 2026 in a forthcoming amendment.

4. Reference: SF1442 Block 13

Because of power outages, water utility outages, flooding and structural damage due to the super typhoon Sinlaku, local subcontractors have been without power or the ability to work for up to a week.

Due to these disruptions and the high volume of current bid activity currently underway, [Prime] and our subcontractors respectfully request that the Government extend the due date by at least 10 days; several areas on the island of Guam are still without power.

ANSWER: Refer to response to Q3.

5. Reference: Factor 1: Experience

RELEVANT CONSTRUCTION PROJECT: For purposes of this evaluation, a relevant construction project is defined as new construction of a multi-story administrative, office, training, or communications facility consisting of cast-in-place reinforced concrete building structure of approximately $30 million or more in dollar value and completed or substantially completed no earlier than ten (10) years from the date of issuance of this solicitation. Building repair, renovation, conversion, and addition work will not be considered as a relevant project.

Question: The contractor requests clarification on whether the Government will consider construction projects in the $20 million range as meeting the definition of a relevant construction project in lieu of the stated $30 million threshold.

6. Section 00 21 16 - Instructions to Proposers > Site Visit; 3rd paragraph

(c) Please submit the applicable information to jennifer.m.hue.civ@us.navy.mil on or before April 17, 2026, 2:00 p.m., Hawaii Standard Time (HST).

Question: Due to the recent typhoon impacting Guam, utilities and communication systems were significantly disrupted during the RFP release period. Notably, both the RFP release date and the due date for the site visit information submittal occurred during this disruption period.

In consideration of these circumstances, we respectfully request a one-week extension to the due date of the site visit information submittal, to be applied following confirmation of an amendment. This additional time will allow for proper review and coordination moving forward.

ANSWER: You may submit the required site visit forms through April 24, 2026, 2:00 p.m., HST. Due to the extenuating circumstances, we will continue to accept site visit forms after this deadline, but please consider VCC processing times and that forms received after the specified due date may not be approved in time to attend the site visit.

End of Notice

P-678 SATELLITE COMMUNICATIONS FACILITY

MARINE CORPS BASE CAMP BLAZ, GUAM

SECTION 01 57 19.03 21 Page 1

SECTION 01 57 19.03 21

SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS

Secretary of the Navy (SECNAV) Explosive Safety Risk Acceptance Within Joint

Region Marianas

07/25

PART 1 GENERAL

1.1 SUMMARY

This construction contract is exempt from explosive safety requirements in Department of Defense Explosive Safety Regulation (DESR 6055.09) and other corresponding Department of Defense and Department of the Navy Policies.

This specification identifies contract requirements conditional to the exemption:

a. UXO Safety Awareness Training (3Rs Training) for personnel conducting ground disturbing activities

b. Protocol to stop work, evacuate and notify if suspected Munitions and Explosives of Concern (MEC) are encountered.

c. Geographic Information System (GIS) Electronic Submittals documenting

- Initial GIS Data File(s) of Project Limits

- Final GIS Data File(s) of Project Limits and lowest ground disturbance

1.2 SUBMITTALS

Government acceptance is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. The following shall be submitted in accordance with Specification Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

MEC Work Plan; G

Initial GIS Data File(s)

SD-11 Closeout Submittals

Final GIS Data File(s)

1.2.1 MEC Work Plan

MEC Work Plan is a concise pre-construction submittal documenting Project Limits, Notification Protocol, 3Rs Training Compliance Plan, and Initial 3Rs Training Log. MEC Work Plan must be Government approved prior to starting ground disturbing activities.

SECTION 01 57 19.03 21 Page 2

a. Project Limits. Graphic depiction of Project Limits that may be reproduced from contract documents. Notify Contracting Officer of discrepancies in ground disturbing work and contract Project Limits.

b. Notification Protocol for suspected MEC encounters. Include names, phone and email contacts. Notification protocol is listed in paragraph 3.3.1, unless directed otherwise by Contracting Officer. To prepare the MEC Work Plan, Contracting Officer will provide point of contact information for Government MEC Quality Assurance (QA) Personnel.

c. 3Rs Training Compliance Plan. See paragraph 1.3 3RS TRAINING REQUIREMENT.

Include relevant sections of the Accident Prevention Plan including:

- Requests and scheduling of Government provided group training by Government MEC QA Personnel

- SSHO controls to ensure 3Rs Training compliance, including controls for annual re-certification and template for the on-site 3Rs Training Log.

d. Initial 3Rs Training Log. Names of personnel anticipated to require 3Rs Training per paragraph 1.3, effective/expiration dates and valid Certificates of Completion for all listed personnel.

1.2.2 Initial GIS Data File(s)

Pre-construction submittal of electronic GIS data file(s) documenting only the Project Limits as indicated in contract. GIS data must conform to “Navy Installation Geospatial Information & Services Specifications for Vector GIS Deliverables,” appended to this specification.

Additional to Specification Section 01 33 00 SUBMITTAL PROCEDURES, email data files(s) directly to NAVFAC Marianas MEC Program Manager. Contracting Officer will provide contact information for the MEC Program Manager.

1.2.3 Final GIS Data File(s)

Provide electronic GIS data file(s) documenting the lowest ground disturbance. Data shall be three-dimensional vector GIS deliverable documenting the extent and depth of ground disturbance. GIS data must conform to “Navy Installation Geospatial Information & Services Specifications for Vector GIS Deliverables,” appended to this specification.

Upon request, Contracting Officer will provide an empty Elevation Contour Feature Class in a file or personal geodatabase as a template for vector GIS data file submission.

Additional to Specification Section 01 33 00 SUBMITTAL PROCEDURES, email data files(s) directly to NAVFAC Marianas MEC Program Manager. Contracting Officer will provide contact information for the MEC Program Manager.

1.3 3RS TRAINING REQUIREMENT

Incorporate UXO Safety Awareness Training (3Rs Training) requirements into the Accident Prevention Plan, under oversight responsibility of the Site Safety and Health Officer (SSHO).

SECTION 01 57 19.03 21 Page 3

3Rs Training Requirement is fulfilled individually by accessing online training at https://www.3Rs.mil, passing the quiz, and receipt of a certificate of completion. Individual online training takes approximately 20 minutes. Alternatively, the Government may provide group 3Rs Training, by Government MEC QA Personnel, at Contractor request and scheduling. Training must be completed annually.

The following personnel are required to take 3Rs Training:

a. Superintendent(s), SSHO, and Quality Control Manager (QCM)

b. All personnel involved in ground disturbing activities. Personnel involved in ground disturbing activities during pre-construction and preparatory phases of work are also subject to this requirement.

c. As designated by SSHO: other personnel that could encounter MEC.

PART 2 PRODUCTS

2.1 GIS DATA COLLECTION

Global Positioning System (GPS) data collection shall be used to produce the final GIS Data File(s) mapping the lowest ground disturbance. Provide professional grade GPS with accuracy level of plus/minus less than 1 m and differential correction to target accuracies of plus/minus 0.5 m.

Contractor may substitute data from higher accuracy survey equipment in lieu of GPS data collection, where higher accuracy survey equipment is used in concert with excavation operations.

PART 3 EXECUTION

3.1 3RS TRAINING CONTROLS

SSHO shall maintain an updated 3Rs Training Log and non-expired certificates of completion for individuals required to take 3Rs Training. 3Rs Training certificates of completion expire; training must be re-taken annually.

Only the Initial 3Rs Training Log must be submitted as part of the MEC Work Plan for Government approval. Updates for the 3Rs Training Log do not require official resubmission, but must be maintained by the SSHO and be available on-site to Government Representatives on-demand (i.e. new personnel not listed in the initial log, 3Rs Training renewals, etc.).

3.2 UPDATE MEC WORK PLAN

Update and resubmit MEC Work Plan for Government approval upon changes to Project Limits, Notification Protocol (i.e. point of contacts, etc.), or 3Rs Training Compliance Plan. Maintain updated MEC Work Plan, available on-site to Government Representatives on-demand. Official resubmission is not required exclusively for updates to the 3Rs Training Log.

3.3 REQUIREMENTS WHEN SUSPECTED MEC IS ENCOUNTERED

If during any phase of the project work, a suspected MEC item is found, immediately stop-work, evacuate and secure area within 1,000 feet of the suspected MEC item.

SECTION 01 57 19.03 21 Page 4

3.3.1 Notification Protocol

For suspected MEC encounters immediately notify:

a. Contracting Officer: to confirm evacuation and securing of area within 1,000 feet of the suspected MEC item.

b. Government MEC Quality Assurance (QA) Personnel: to mobilize for verification of suspected MEC item.

3.3.2 Verification of Suspected MEC

Government will verify suspected MEC items, by Government MEC QA Personnel.

3.3.3 Resumption of Work

Contracting Officer or designated representative will direct resumption of work if item is not MEC.

Should item be confirmed MEC, Contracting Officer or designated representative will provide direction to:

a. Resume work outside the MEC item’s exclusion zone.

b. Resume work within the area of the MEC following removal of MEC by Government Explosive Ordnance Disposal (EOD).

3.4 UNINTENTIONAL EXPLOSIVE EVENT

If during any phase of the project work there is an unintentional explosive event, the exemption under the SECNAV Explosive Safety Risk Acceptance will cease to apply to this contract. All ground intrusive work will stop until new explosive requirements can be established, approved, and implemented.

SECTION 01 57 19.03 21 Page 5

MEC GIS Requirements:

a. Deliver all data collected in the suitable GIS format in conjunction with NAVFAC GeoReadiness Center (GRC) standards

b. The GIS format is as follows:

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

II. 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 the current approved ArcGIS version being used by the Navy

III. MEC does not currently fit in the current NDM. A copy of the current MEC data model implementation shall be provided to the contractor.

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

I. field survey/project areas

II. survey transects III. collected data points, polygons, and lines

All the attribution (data fields) collected about them.

IV. Pictures (must be GeoTagged) and delivered with a the appropriate pathway appended

d. All maps created and used in deliverable reports shall be turned in as a standing MPK file created in the current approved ArcGIS version

e. Data charts shall be delivered in Microsoft excel format (PDF is unacceptable)

f. GPS unit standards for field data collection are required.

I. The contractor shall utilize conventional and other methods, such as a Global Positioning System (GPS) in accordance with the applicable Geospatial Positioning Accuracy Standards published by the Federal Geographic Data Committee (FGDC).

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

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.

g. GIS data shall be submitted monthly (or as directed by the COR) for review before the final submittal.

h. For further guidance on NAVFAC GIS standards guidance please see appendix A & B

MEC Geodatabase Instruction for Construction Projects

(1) Construction Projects

SECTION 01 57 19.03 21 Page 6

(a) MPPEH reports – Contractors shall submit reports via email to the GRC Marianas (GRC_Marianas@fe.navy.mil).

(b) MPPEH and MDAS finds along with current excavation perimeters, depths, and soil movement routes shall be submitted at minimum the last day of each month or at project completion, whichever completes first. This deliverable shall be in the appropriate GIS format in compliance with the DoD SDSFIE and the current NAVFAC MEC data model.

(c) After Action Reports (AAR) – Contractors shall submit MEC AARs with a final GIS geodatabase, as described in the previous paragraph (b).

(2) Reporting requirements

(a) All reports and the GIS deliverables mentioned above shall be sent to the GRC Marianas (GRC_Marianas@fe.navy.mil) for inclusion in the GIS system. The GIS administrator will confirm with the report generator once the data is verified and loaded.

MEC Database

MECEncounter – All MEC finds discovered. Exclude non MEC items

Attribute Description Values

MECEncounterIDFK Unique Identification String: ex. ProjID-GridID-Find# number of the MEC find. J001B-Y34-01

Feature Name Type of MEC noted String: ex. MPPEH, MEC Find

Feature Description Specific details of String: Length 255

MEC object found

Meta Notes: Meta data description String: Length 255 about Find

Creator: Person digitizing feature String: Length 20

Date Created: Date added to database Date: MM/DD/YY

Collection Source: What was the data point String: Length 76(ex MappingGradeGPS)

Collected with

Locational Accuracy: Accuracy of Collection String: Length 50 (ex. +/- 1m)

Media IDFK: Provides the link to String: Length 20 multimedia files

PROJID: Construction Project ID String: Length 50

PROJTITLE: Long Name for Project String: Length 100

MECTYPEID: General category of MEC String: Length 50

(Grenade)

(Fuze)

SECTION 01 57 19.03 21 Page 7

(H.E Projectile >20mm)

(Incendiary)

(Fragmentation Bomb)

(General Purpose Bomb)

(Illumination)

(Mortar Round)

(Mine Land)

(Mine Marine)

(Ordnance Component)

(Practice Round)

(Rocket)

(TNT)

(Torpedo)

(Unknown)

(WP Smoke)

MEC Count: Amount of specific MEC found Integer: Long

OBSERVATION DATE: Date of the MEC find Date: MM/DD/YYYY

DEPTH: Depth and unit of measure Integer: Long

DEPTH UOM: Unit of measure depth String: ex. Feet; Centimeters;

collected in. Meters; Inches

MEC CONTRACTOR: Who is the MEC Contractor String: Length 100

CONTRACT NUMBER: What is the contract number String: Length 50

LocationDescription: Description of where the String: Length 255 object was found

RSPDone: Was render safe procedures Integer Long: 0=No 1=1,2=2,3=3 used by EoD

MECSurveyArea – All areas surveyed for MEC to include grid systems, project footprints and clearance areas. Exclude test sites.

Attribute Description Values

MECSurveyAreaIDFK Unique Identifying number String: ex. ProjectID -GridID

Feature Name Type of feature String: MEC Clearance; Survey Grid

Feature Description Specific details of String: Length 255

SECTION 01 57 19.03 21 Page 8

MEC Clearance or grid

Meta Notes: Meta data description String: Length 255 about Find

Creator: Person digitizing feature String: Length 20

Date Created: Date added to database Date: MM/DD/YY

Collection Source: What was the data point String: Length 76 collected with

Locational Accuracy: Accuracy of Collection String: Length 50 (I.E +/- 1m)

Media IDFK: Provides the link to String: Length 20 multimedia files

PROJID: Construction Project ID String: Length 50

PROJTITLE: Long Name for Project String: Length 100

DEPTH: Depth and unit of measure String: Length 50

MEC CONTRACTOR: Who is the MEC Contractor String: Length 100

CONTRACT NUMBER: What is the contract number String: Length 50

COMPLETIONDATE: Date of excavation complete Date: MM/DD/YYYY

TOISIZE: Soil Screening Size String: Length 50

MECDISC: Was MEC discovered String: Length 100 during project (None)

(Yes;See ARR for spot reports

(On Going MEC Investigation)

ANOMILIES: Number of anomalies found Integer Long: 1,000,000+

CYREMOVED: Cubic yards of soil removed Integer Long: 1,000,000+

Documentation: Record source String: Length 255

MECDisposalSite – Unearthed previous MEC disposal area. Including burn pits.

Attribute Description Values

MECDisposalSiteIDFK Unique Identifying number String: ex. ProjectID-Dump/Burn site#

Feature Name Type of feature String: ex. Dump Site; Burn Pit

Feature Description Specific details of String: Length 255

Site

Meta Notes: Meta data description String: Length 255

SECTION 01 57 19.03 21 Page 9 about Site

Creator: Person digitizing feature String: Length 20

Date Created: Date added to database Date: MM/DD/YY

Collection Source: What was the data point String: Length 76 collected with ex. MappingGradeGPS

Locational Accuracy: Accuracy of Collection String: Length 50 ex. +/- 1m

Media IDFK: Provides the link to String: Length 20 multimedia files

PROJID: Construction Project ID String: Length 50

PROJTITLE: Long Name for Project String: Length 100

DEPTH: Depth and unit of measure String: Length 50

MECKTR: Who is the MEC Contractor String: Length 100

CONTRACTNO: What is the contract number String: Length 50

COMPDATE: Date of end of use or project Date: MM/DD/YYYY

TOISIZE: Soil Screening Size String: Length 50

ANOMILIES: Number of anomalies found Integer: Long

(If Excavated)

CYREMOVED: Cubic yards of soil removed Integer: Long

Documentation: Record source String: Length 255

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

SECTION 01 57 19.03 21 Page 10

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

SECTION 01 57 19.03 21 Page 11

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:

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

http://datacollectionadvisor.com/

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.

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

SECTION 01 57 19.03 21 Page 12

678 SATELLITE COMMUNICATIONS FACILITY

MARINE CORPS BASE CAMP BLAZ, GUAM

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.

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.

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:

SECTION 01 57 19.03 21 Page 13

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 current version are listed in APPENDIX 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.

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

SECTION 01 57 19.03 21 Page 14

b. At a minimum, the contractor shall provide professional 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.

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

SECTION 01 57 19.03 21 Page 15

APPENDIX B: Specifications for GIS Layers and Attributes

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

This section lists:

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

ATTRIBUTE

DEFINITIO

N

MANDAT

ORY

POPULATION

GUIDANCE

DAT

A

TYP

E

FIE

LD

SIZ

E

EXAMPLE

VALUE

***IDPK

Primary Key. A unique, user defined identifie r 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

Tex t 40

CR 66-02-

SECTION 01 57 19.03 21 Page 16

InstallationI D

The official code assigned by the Military Service (includes Washingto n Headquart ers Services) to identify the Headquart ers Services) to identify the site or group of sites that make up an installat ion. For the Navy it is site is site identifie r as represent ed by the iNFADS Site Code. Yes

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

Tex t 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

Tex t 80

Threatened and endangered Species observation

SECTION 01 57 19.03 21 Page 17

FeatureDescri ption

The narrative describin g 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., natureOfConstru ction: 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").

Tex t 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.

Tex t 17

Code: USN Description:

US Navy

SECTION 01 57 19.03 21 Page 18

Creator

The name of the departmen t or contracto r that collected the informati on for the feature for the first time. For example, NAVFAC SE

GRC,

attribute as

NAVFACSEG

RC 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 "Vandelayindust ries".

Tex t 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).

Dat e NA 6/28/1974

CollectionMet hod

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

Populate with the appropriate value from the CollectionMetho d constraint table.

Tex t 28

Code:

HeadsUpImag eryMgGPSVrfy Description:

Heads Up Imagery Mapping Grade GPS Verify

LocationAccur acy

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.

Tex t 50 +/-1m

SECTION 01 57 19.03 21 Page 19

Editor

The contracto r or person that edited the feature attributi on 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 attribute d 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.

Tex t 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).

Dat e NA 6/28/1974

POPULATION GUI

- End of Section –

FY24 MILCON PROJECT P-678, Satellite Comm Facility 1737026 MCB Camp Blaz, Guam

SECTION 01 57 19.03 21

SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS

Secretary of the Navy (SECNAV) Explosive Safety Risk Acceptance Within Joint

Region Marianas 07/25

PART 1 GENERAL

1.1 SUMMARY

This construction contract is exempt from explosive safety requirements in Department of Defense Explosive Safety Regulation (DESR 6055.09) and other corresponding Department of Defense and Department of the Navy Policies.

This specification identifies contract requirements conditional to the exemption:

a. UXO Safety Awareness Training (3Rs - Recognize, Retreat, Report) for personnel conducting ground disturbing activities

b. Protocol to stop work, evacuate and notify if suspected Munitions and Explosives of Concern (MEC) are encountered.

c. Geographic Information System (GIS) Electronic Submittals documenting

- Initial GIS Data File(s) of Project Limits

- Final GIS Data File(s) of Project Limits and lowest ground disturbance

1.2 SUBMITTALS

Government acceptance is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. The following shall be submitted in accordance with Specification Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

MEC Work Plan; G

Initial GIS Data File(s)

SD-11 Closeout Submittals

Final GIS Data File(s)

1.2.1 MEC Work Plan

MEC Work Plan is a concise pre-construction submittal documenting Project Limits, Notification Protocol, 3Rs Training Compliance Plan, and Initial 3Rs Training Log. MEC Work Plan must be Government approved prior to starting ground disturbing activities.

a. Project Limits. Graphic depiction of Project Limits that may be reproduced from contract documents. Notify Contracting Officer of

SECTION 01 57 19.03 21 Page 1 discrepancies in ground disturbing work and contract Project Limits.

b. Notification Protocol for suspected MEC encounters. Include names, phone and email contacts. Notification protocol is listed in paragraph 3.3.1, unless directed otherwise by Contracting Officer. To prepare the MEC Work Plan, Contracting Officer will provide point of contact information for Government MEC Quality Assurance (QA) Personnel.

c. 3Rs Training Compliance Plan. See paragraph 1.3 3RS TRAINING REQUIREMENT. Include relevant sections of the Accident Prevention Plan including:

- Requests and scheduling of Government provided group training by Government MEC QA Personnel

- SSHO controls to ensure 3Rs Training compliance, including controls for annual re-certification and template for the on-site 3Rs Training Log.

d. Initial 3Rs Training Log. Names of personnel anticipated to require 3Rs Training per paragraph 1.3, effective/expiration dates and valid Certificates of Completion for all listed personnel.

1.2.2 Initial GIS Data File(s)

Pre-construction submittal of electronic GIS data file(s) documenting only the Project Limits as indicated in contract. GIS data must conform to “Navy Installation Geospatial Information & Services Specifications for Vector GIS Deliverables,” appended to this specification.

Additional to Specification Section 01 33 00 SUBMITTAL PROCEDURES, email data files(s) directly to NAVFAC Marianas MEC Program Manager. Contracting Officer will provide contact information for the MEC Program Manager.

1.2.3 Final GIS Data File(s)

Provide electronic GIS data file(s) documenting the lowest ground disturbance. Data shall be three-dimensional vector GIS deliverable documenting the extent and depth of ground disturbance. GIS data must conform to “Navy Installation Geospatial Information & Services Specifications for Vector GIS Deliverables,” appended to this specification. Upon request, Contracting Officer will provide an empty Elevation Contour Feature Class in a file or personal geodatabase as a template for vector GIS data file submission.

Additional to Specification Section 01 33 00 SUBMITTAL PROCEDURES, email data files(s) directly to NAVFAC Marianas MEC Program Manager. Contracting Officer will provide contact information for the MEC Program Manager.

1.3 3RS TRAINING REQUIREMENT

Incorporate UXO Safety Awareness Training (3Rs Training) requirements into the Accident Prevention Plan, under oversight responsibility of the Site Safety and Health Officer (SSHO).

3Rs Training Requirement is fulfilled individually by accessing online training at https://www.3Rs.mil, passing the quiz, and receipt of a certificate of completion. Individual online training takes approximately 20 minutes. Alternatively, the Government may provide group 3Rs Training, SECTION 01 57 19.03 21 Page 2 by Government MEC QA Personnel, at Contractor request and scheduling.

Training must be completed annually.

The following personnel are required to take 3Rs Training:

a. Superintendent(s), SSHO, and Quality Control Manager (QCM)

b. All personnel involved in ground disturbing activities. Personnel involved in ground disturbing activities during pre-construction and preparatory phases of work are also subject to this requirement.

c. As designated by SSHO: other personnel that could encounter MEC.

PART 2 PRODUCTS

2.1 GIS DATA COLLECTION

Global Positioning System (GPS) data collection shall be used to produce the final GIS Data File(s) mapping the lowest ground disturbance. Provide professional grade GPS with accuracy level of plus/minus less than 1 m and differential correction to target accuracies of plus/minus 0.5 m.

Contractor may substitute data from higher accuracy survey equipment in lieu of GPS data collection, where higher accuracy survey equipment is used in concert with excavation operations.

PART 3 EXECUTION

3.1 3RS TRAINING CONTROLS

SSHO shall maintain an updated 3Rs Training Log and non-expired certificates of completion for individuals required to take 3Rs Training.

3Rs Training certificates of completion expire; training must be re-taken annually.

Only the Initial 3Rs Training Log must be submitted as part of the MEC Work Plan for Government approval. Updates for the 3Rs Training Log do not require official resubmission, but must be maintained by the SSHO and be available on-site to Government Representatives on-demand (i.e. new personnel not listed in the initial log, 3Rs Training renewals, etc.).

3.2 UPDATE MEC WORK PLAN

Update and resubmit MEC Work Plan for Government approval upon changes to Project Limits, Notification Protocol (i.e. point of contacts, etc.), or 3Rs Training Compliance Plan. Maintain updated MEC Work Plan, available on-site to Government Representatives on-demand. Official resubmission is not required exclusively for updates to the 3Rs Training Log.

3.3 REQUIREMENTS WHEN SUSPECTED MEC IS ENCOUNTERED

If during any phase of the project work, a suspected MEC item is found, immediately stop-work, evacuate and secure area within 1,000 feet of the suspected MEC item.

3.3.1 Notification Protocol

For suspected MEC encounters immediately notify:

SECTION 01 57 19.03 21 Page 3

a. Contracting Officer: to confirm evacuation and securing of area within 1,000 feet of the suspected MEC item.

b. Government MEC Quality Assurance (QA) Personnel: to mobilize for verification of suspected MEC item.

3.3.2 Verification of Suspected MEC

Government will verify suspected MEC items, by Government MEC QA Personnel.

3.3.3 Resumption of Work

Contracting Officer or designated representative will direct resumption of work if item is not MEC.

Should item be confirmed MEC, Contracting Officer or designated representative will provide direction to:

a. Resume work outside the MEC item’s exclusion zone.

b. Resume work within the area of the MEC following removal of MEC by Government Explosive Ordnance Disposal (EOD).

3.4 UNINTENTIONAL EXPLOSIVE EVENT

If during any phase of the project work there is an unintentional explosive event, the exemption under the SECNAV Explosive Safety Risk Acceptance will cease to apply to this contract. All ground intrusive work will stop until new explosive requirements can be established, approved, and implemented.

-- End of Section --

SECTION 01 57 19.03 21 Page 4