N4019220R1300_Amendment 0005_31JUL2020.pdf
PDF 916 KB Posted
- Solicitation number
- N4019220R1300
About this file
This is a solicitation for construction services to repair and modernize Lima Wharf and appurtenances at Naval Base Guam. The work includes replacement of steel sheet pile bulkhead, mooring systems, fender systems, electrical substation, and wharf utilities. It also includes construction of a bilge oily water treatment system. The NAICS code is 237990 and size standard is $39.5 million. The estimated cost is $100-250 million. The solicitation uses tradeoff source selection and evaluation of technical proposal, past performance, and price. Offerors must submit a $3 million bid bond or 20% of bid price. The pre-proposal conference and site visit details will be provided later. Foreign nationals attending the site visit must submit passport copies. The point of contact is Janeen Bais at Janeen.Bais@fe.navy.mil.
View the file
Other files
Show all 20
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
FY21 SPECIAL PROJECT RM 14-1420, Repair Lima Wharf, Naval Base Guam
See Continuation Page.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 2
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 31-Jul-2020
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 N4019220R1300
X 9B. DATED (SEE ITEM 11)
16-Jun-2020
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
31-Jul-2020
CODE
COMMANDING OFFICER - NAVFAC MARIANAS
MAR MCON
PSC 455, BOX 195
FPO AP 96540-2937
N40192 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N4019220R1300
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 0005
A. In accordance with FAR 52.252-3 Alterations in Solicitation (APR 1984), portions of this solicitation are altered as follows:
1. Incorporate the following revision to NAVFAC Specifications WON 1383711:
a. SECTION 01 57 19.01 20 SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS
Replace specification section 01 57 19 01 20 in its entirety with the revised specification section 01 57
19.01 20 SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS Lima Mike November Wharves Apra Harbor, Naval Base Guam, Water Areas Explosives Safety Submission (ESS) to include the Pre-Draft Water Areas Explosives Safety Submission Repair of Lima Mike November Wharves, Apra Harbor (Pre-Draft Water Areas ESS) and provided herein as Enclosure (1).
Bids should be based on the information included in the revised specification section and Pre-Draft Water Areas ESS.
B. Notice 5 is provided in response to requests for information and is provided herein as Enclosure (2). Notice 5 is provided for INFORMATION ONLY. The solicitation remains unchanged unless it is amended in writing.
C. The date for receipt of proposals remains unchanged at August 31, 2020 at 4:30pm local time.
D. Offerors shall acknowledge this amendment in Block 19 of the Standard Form 1442 with their proposals.
(End of Summary of Changes)
FY21 Special Project RM 14-1420 Repair Lima Wharf Naval Base Guam
1383711
SECTION 01 57 19.01 20 Page 1
SECTION 01 57 19.01 20
SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS
Lima Mike November Wharves Apra Harbor, Naval Base Guam, Water Areas Explosives Safety Submission (ESS 7/30/2020
PART 1 GENERAL
1.1 REFERENCES
The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only. Contractor shall comply with all local Government requirements. When local and federal requirements conflict, the most stringent shall apply. For all references listed below, the most recent version at time of award of the construction contract or task order shall apply.
JOINT REGION MARIANAS (JRM)
Lima Mike November Wharves Apra Harbor, Naval Base Guam, Water Areas ESS (here after referred to Apra Harbor Water ESS)
NAVFAC Standards for ERSI Geodatabase format, version 10.1 as of Geographic Information System May 2014
DEPARTMENT OF DEFENSE (DOD)
EM-385-1-1 Safety and Health Requirements Manual, US
Army Corp of Engineers (USACE)
NOSSAINST 8020 (Series) Naval Ordnance Safety and Security Activity, Explosives Safety Review, Oversight, and Verification of Munitions Responses (U)
NAVSEA OP 5 (Volume 1) Naval Sea Systems Command, Ammunition and
Explosives Safety Ashore
DoDI 4140.62 Department of Defense Instruction 4140.62, Material Potentially Presenting an Explosive Hazard
DDESB TP-15M Department of Defense Explosives Safety Board
TP-15M Approved Protective Construction
DDESB TP-16 Department of Defense Explosive Safety Board, Technical Paper 16, Buried Explosive Module
(BEM)
DDESB TP-18 (Series) Department of Defense Explosive Safety Board, Technical Paper 18, Qualifications for UXO Technicians
1383711
SECTION 01 57 19.01 20 Page 2
NOSSAINST 8023.11B Standard Operating Procedures, Development, Implementation, and Maintenance for Ammunition and Explosives
OPNAVINST 3500.39D Department of the Navy OPNAVINST 3500.39D, Operational Risk Management
CNO Exemption E1-16B Chief of Naval Operations Explosives Safety
Exemption E1-16B dated 05 JAN 17
EM 385-1-97 Explosive- Safety and Health Requirements
Manual, US Army Corp of Engineers (USACE)
NOTE: Where the requirements provided in NAVSEA OP 5 and EM 385-1-97 are in conflict, NAVSEA OP 5 shall govern.
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
Record of Training; G
Installation Commanding Officer (ICO) Notification; G
Geographic Information System (GIS) Work Area Grid; G Personnel Qualifications and Duties; G
Personnel Qualifications and Duties; G
Site Health and Safety Plan (SHSP); G
Occupancy, Population and Vehicle Survey; G
SD-06 Test Reports
QC Report; G
Munitions and Explosives of Concern (MEC)/Material Potentially Presenting an Explosive Hazard (MPPEH) Spot Report; G
Bedrock Determinations; G
SD-11 Closeout Submittals
GIS Data; G
After Action Report (AAR); G
1383711
SECTION 01 57 19.01 20 Page 3
1.2.1 Submittal Schedule
Schedule and submit concurrently submittals covering component items forming a system or items that are interrelated. No delay damages or time extensions will be allowed for time lost in late submittals.
Except as specified otherwise, allow review period, beginning with receipt by accepting authority, to include 30 working days for submittals for Contracting Officer or Installation Commanding Officer approval. Period of review for submittals requiring Government approval begins when the Government receives the submittal from the QC organization.
The review period for each resubmittal is the same as for the initial submittal.
1.3 Documentation
Maintain a copy of the following documents on site and available to Government representatives upon request:
a. NOSSA ltr 8020 Ser N45G/080 of 17 Jan 20 [WebESS ID# 547/ESS 19-24]
b. DDESB memo DDESB-PE of 24 Aug 18 [GG-052MOD]
c. NAVSEA OP 5 (Volume 1)
d. Other previous DDESB approvals
e. DDESB memo DDESB-PE of 24 Jan 20
f. Lima Mike November Wharves Apra Harbor, Naval Base Guam, Water Areas
ESS
g. ESS Work Plan
1.4 Anomalies
An anomaly is defined as a metal item with any one dimension equal to the 20 mm projectile or larger.
Historic anomaly averages contained within the E-16B memo incorporated into this contract do not reflect conditions at the project site. Contractor assumes the risk that the number of anomalies encountered at the project site may differ from historic averages reflected in the E-16B memo.
1.5 Personnel Qualifications and Duties
Personnel shall meet the minimum qualification standards set forth in DDESB TP 18 and the Apra Harbor Water ESS, including training and experience requirements. Personnel requirements and duties are defined in DDESB TP 18 and the Apra Harbor Water ESS.
The team composition and size shall be in accordance with Apra Harbor Water ESS. Skill and composition of the team(s) will be appropriate to the task being performed; this is to include Quality Control and Safety.
The contractor shall provide the qualifications of all personnel at least three working days prior to commencing intrusive activities.
1.5.1 Unexploded Ordnance Safety Officer (UXOSO)
The UXOSO shall be responsible for implementing the Site Health and Safety Plan (SHSP) and the Accident Prevention Plan (APP). UXOSO must be on site, within the Exclusion Zone(s) or transiting between different teams, during
1383711
SECTION 01 57 19.01 20 Page 4 anomaly investigation or any activity covered under the SHSP and APP.
The UXOSO may also perform duties of the UXOQCS. This position may be combined with the UXOQCS when there are fewer than fifteen (15) personnel on site. If this is done, it shall be designated in writing in the MEC work plan.
In the MEC work plan, designate a primary UXOSO. The contractor shall not deviate from the identified UXOSO without government notification and acceptance.
1.5.2 UXO Quality Control Specialist (UXOQCS)
The UXOQCS shall be responsible for implementing the approved Quality Control Plan. The UXOQCS may also perform duties of the UXOSO when there are fifteen (15) or fewer people on site. If this is done, it shall be designated in writing in the MEC work plan. The UXOQCS shall not report to the SUXOS. The UXOQCS is responsible to ensure that the three phases of quality control (preparatory, initial, and follow-up) are properly implemented and shall inspect each definable feature of work by phase.
If the MEC work plan identifies use of Digital Geophysical Mapping (DGM) and/or Advanced Geophysical Classification (AGC) detection equipment, either the UXOQCS or Geophysicist must be on site during data collection or activities covered in the QC Plan.
The UXOQCS is responsible for insuring proper implementation of the Geophysical System Verification process, installing an Instrument Verification Strip (IVS), and emplacing blind seeds. IVS shall be installed on a site-specific basis taking into account such factors such as; proximity to powerlines, roads, electromagnetic emitting towers and soil conditions.
In the MEC work plan, designate a primary UXOQCS. The contractor shall not deviate from the identified UXOQCS without government notification and
1.5.3 Senior UXO Supervisor (SUXOS)
The SUXOS is responsible to oversee all munitions response work. The SUXOS shall not operationally manage MEC/MPPEH efforts as part of another project while the UXO team is mobilized for this project. The SUXOS shall not perform any other role.
In the MEC work plan, designate a primary SUXOS. The contractor shall not deviate from the identified SUXOS without government notification and
1.5.4 UXO Technicians
UXO Technicians shall be provided by the contractor as needed based on site and project conditions. Training and experience shall be in accordance with DDESB TP 18, Apra Harbor Water ESS S and be commensurate with their assigned duties. A copy of the qualifications for all UXO Technicians shall be maintained on-site during all MEC/MPPEH-related work activities.
1.5.5 Explosive Safety Awareness Training
1383711
SECTION 01 57 19.01 20 Page 5
Explosive safety awareness training shall be performed in accordance with the requirements of MEC Work Plan and Apra Harbor Water ESS for all site workers/personnel working in areas designated as ‘‘likely’’ of encountering MEC regardless of whether they are engaged in intrusive activities or not.
Submit a Record of Training for all site workers to the Contracting Officer.
The safety briefings shall be completed prior to site workers being allowed to enter the project site. Explosive safety awareness training must be renewed for all site workers annually.
1.6 MEC Work Plan General Requirements
The MEC Work Plan shall be project-specific, and address any unusual or unique aspects of the project or activity for which it is written. The MEC Work Plan shall interface with the Contractor’s overall safety, health, and quality control programs. The Government considers the Prime Contractor to be the “controlling authority” for all work site safety, health, and quality control implementation of the subcontractors. Contractors are responsible for informing their subcontractors of the safety and quality provisions under the terms of the contract and the penalties for noncompliance, coordinating the work to prevent one craft from interfering with or creating hazardous working conditions for other crafts, and inspecting subcontractor operations to ensure that accident prevention and quality control responsibilities are being carried out. The contractor shall implement the three phases of quality control. The MEC Work Plan shall be signed by the project superintendent, the project QC Manager, the project SSHO, the UXOSO, UXOQCS, SUXOS, and geophysicist (DGM or AGC MEC Work Plans only).
Once accepted by the Contracting Officer, the MEC Work Plan and attachments will be enforced as part of the contract. Only when the MEC Work Plan is accepted shall the contractor be permitted to begin remediation activities.
Contractor's failure to execute work in accordance with the approved MEC Work Plan will be cause for non-compliance with the contract. Any costs or delays associated with full resolution will be the contractor's responsibility.
Once work begins, changes to the accepted MEC Work Plan shall be made with the knowledge and concurrence of the Contracting Officer and Government MEC Quality Assurance Specialist (QA), project superintendent, QC Manager, SSHO, UXOSO, UXOQCS, SUXOS, and geophysicist (DGM and AGC MEC Work Plans only).
Should imminent danger become evident, stop work in the area, secure the area, remove the exposure and control the hazard. In the event MEC/MPPEH is encountered, the contractor shall make every effort to notify the Contracting Officer and Government MEC QA via telephone within four (4) hours of discovering the MEC/MPPEH item. In the interim, take all necessary action to restore and maintain safe working conditions in order to safeguard onsite personnel, visitors, the public, and the environment. Written notification and initial SPOT report within 24 hours (one business day).
1.7 Installation Commanding Officer (ICO) Notification
MEC/MPPEH remediation work which impacts an installations operations (residents and tenant commands), traffic patterns or quality of life will require approval from the Installation Commanding Officer (ICO) prior to the start of remediation work. At a minimum the ICO will require 45 calendar days to review and approve the proposed plan that will cause disruptions to normal operations. Contractors shall submit ICO notifications to the
1383711
SECTION 01 57 19.01 20 Page 6 assigned Contracting Officer for each contract. The submission shall contain, at a minimum, the following information; location and details of the exclusion zone (s) (EZ), and impacted buildings. Additionally, include;
an aerial picture identifying the affected facilities and extents of EZ, identify the dates, times, and duration of anomaly investigation and identify the lead government and contractor point of contact for the on-site work.
1.8 Geographic Information System (GIS) Work Area Grid
The contractor shall perform location recording and mapping using the WGS 1984 UTM Zone55 North coordinate system. The contractor shall determine the work area boundaries and use these coordinates and the GIS to determine the grid/sector distribution for the work area. Data must be provided in accordance with the GIS standards included as appendices to this specification section. Submit the GIS Work Area Grid to the Contracting Officer at least ten calendar days before commencing intrusive activities.
1.9 QC Report
Refer to specification section 01 45 00.00 20 QUALITY CONTROL for guidance on QC Reporting content.
1.9.1 Daily Quality Control (QC) Reports
The QC Report shall include an accounting of QC inspections on performed definable features of work in the MEC work Plan. The QC Report shall include the WGS 1984 UTM Zone55 North coordinate system used, elevation, description of grids/area included in the report, depth of clearance, number of anomalies investigated, weight in pounds of debris recovered, number of MEC found, number of MPPEH found, number of blind seeds placed, number of blind seeds recovered and IVS results. The report must indicate if the QC inspection passed/failed, schedule of requested Government MEC QA inspections and must be signed by the UXOQCS and the Prime Contractor QC Officer (if different). In map format, identify the area included in the QC Report relative to the entire project footprint, grids, anomalies Left in Place, MEC/MPPEH, and blind seeds. If MEC/MPPEH is found, include a tabular list of the grid, quantity, depth below the original surface elevation, weight, type (MEC/MPPEH), disposition, mark/model, Military Grid Reference System (MGRS) coordinates, and any other applicable information. For blind seeds recovered, include a tabular list of the grid, MGRS coordinates, quantity, depth, size (S, M, L), description, and any other relevant information. For items Left in Place, include a tabular list of the grid, MGRS coordinates, and elevation. All locational information / map products shall be in the WGS 1984 UTM Zone 55N coordinate system. Each complete QC Report shall be submitted to the Government for review.
Upon government review of the QC Report and passing Government MEC QA inspection from the government, the footprint included within that QC Report may have construction activities proceed in the depicted area. It is anticipated that multiple QC Reports will be required and the number will vary based on project and site conditions. The contractor is responsible for maintaining oversight of intrusive activities to ensure that construction activities that disturb the earth stay within designated areas which have passed QC and Government MEC QA inspections.
1.9.2 Detection and Positioning Equipment QC Reports
1383711
SECTION 01 57 19.01 20 Page 7
Detection and positioning equipment calibration shall be in accordance with Section 5.3.1 and 5.3.2 of the Apra Harbor Water ESS.
Periodic reports documenting Detection and positioning equipment calibration Quality Control shall be submitted to the Government in accordance with Section 5.3.1 of the Apra Harbor Water ESS. The QC Report shall include operational checks of equipment, compliance with the accepted DGM and AGC MEC Work Plans, identify any non-compliant work and resulting re-work, and document the three phases of control.
The report must indicate if the QC inspection passed/failed, and must be signed by the UXOQCS and the Prime Contractor QC Officer (if different).
1.10 MEC/MPPEH Spot Report
MEC/MPPEH Spot Reports are required in any situation where MEC/MPPEH is encountered. In the event MEC/MPPEH is encountered, the contractor shall make every effort to notify the Contracting Officer and Government MEC QA via telephone within four (4) hours of discovering the MEC/MPPEH item. An intermediate written report is due to the Contracting Officer, Government MEC QA and MEC Data Exchange by the next business day. A close-out report is due to the Contracting Officer, Government MEC QA and MEC Data Exchange 30 calendar days from the day when the MEC/MPPEH was encountered. The initial voice MEC/MMPPEH Spot report shall include a brief description of the positively identified MEC/MPPEH and its disposition. The intermediate written report shall include, but is not limited to, the description of the positively identified MEC/MPPEH item(s), photograph of item(s) (if possible next to an measuring device for reference), depth from surface item(s) was found, map with MGRS coordinates indicating location of found MEC/MPPEH item(s) based on the WG1984 UTM Zone 55 North coordinate system, method used to isolate the hazard, description of work being performed when MEC/MPPEH item was encountered and names of personnel who found the item.
The close-out report shall have all the same information as in the intermediate report and any additional subsequent information. If the MEC/MPPEH encountered was not anticipated as part of intrusive investigation, close-out report shall also include a root cause analysis as to why a MEC/MPPEH item was encountered when it was not detected.
1.11 GIS Data
GIS Data shall be submitted in accordance with the GIS standards included as appendices to this specification section.
1.12 After Action Report (AAR) General Requirements
The After Action Reports shall be signed by the project superintendent, the project QC Manager, the project SSHO, the UXOSO, UXOQCS, SUXOS, and geophysicist (DGM and AGC AAR only).
AARs shall be submitted to the Contracting Officer and MEC Data Exchange within 15 days of the completion of intrusive activities. AARs may require up to 30 working days for review and acceptance by the Naval Ordnance Safety and Security Activity (NOSSA), and Final AARs may require up to 45 working days for review and acceptance by the Department of Defense Explosive Safety Board (DDESB).
1383711
SECTION 01 57 19.01 20 Page 8
AARs shall follow, at a minimum, the guidance as depicted in references NAVSEA OP 5 Volume 1 Ch13-14 and NOSSAINST 8020.15 (Series). AARs not formatted in accordance with NOSSAINST 8020.15 (Series) shall include a crosswalk of the contents of the AAR to the information required by NOSSAINST 8020.15 (Series).
a. At a minimum, AARs shall contain the following elements:
b. A brief description of the site.
c. A request to cancel any EZ or site approval established in the Apra
Harbor Water ESS.
d. A summary of the MEC and/or MPPEH found.
e. A description of the relative effectiveness and any limitations of the technologies used during the munitions response and the effects on residual risk relative to that originally projected.
f. A summary of the QC and QA reports for the response.
g. Maps showing:
i. Areas from which MEC and/or MPPEH was removed.
ii. Areas within the site where response actions were not performed and the rationale for not addressing those areas.
iii. The known or reasonably anticipated end use of each area.
h. A summary of the land use controls that were implemented, if any, and the areas to which they apply.
i. A summary of provisions for long-term management.
j. Include a separate appendix providing:
i. Certification documentation, transfer documentation, and disposal certificates regarding MD/MDAS as detailed in NAVSEA OP 5 Volume 1 Ch13.
ii. Summary/depiction of areas (horizontal and vertical dimensions) cleared/converted to low probability within the project site.
iii. Additional supporting documents as appropriate to include, but not limited to, field logs, weekly SITREPs, bedrock determinations, compiled GIS Files (native format), MEC/MPPEH Spot Reports, daily activity reports, QC/QA Reports, IVS and blind seed data, NOSSA audits, photographs, Government MEC QA documentation and the OSHA DART rate for the Contractor’s MEC personnel in accordance with Specification Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS. GIS Files shall be submitted in accordance with the GIS standards included as appendices to this specification section.
PART 2 PRODUCTS
2.1 Detection Equipment, Methods and Standards
Detection equipment, methods and standards shall be in accordance with Section 5.1 of the Apra Harbor Water ESS. Detection equipment calibration shall be in accordance with Section 5.3.1 of the Apra Harbor Water ESS.
2.2 Positioning Systems, Methods and Standards
Positioning systems, methods and standards shall be in accordance with Section 5.2 of the Apra Harbor Water ESS. Positioning equipment calibration shall be in accordance with Section 5.3.2 of the Apra Harbor Water ESS.
2.3 Storage of Data Collection
1383711
SECTION 01 57 19.01 20 Page 9
Initial data collection storage shall be a rugged Personal Digital Assistant (PDA), using pull-down menus, to include digital photos of recovered objects (e.g., MEC and MPPEH items are photographed specifically, while grid debris is photographed collectively by grid or lot of grids). As a back-up to PDA systems, a logbook shall also be kept. Alternative storage methods may be authorized by the Contracting Officer.
PART 3 EXECUTION
3.1 Commencing of Intrusive Activities
Submittals required by this specification shall not cause delay, limit, or halt the start or progression of the design work and shall be developed in parallel to the design work.
The MEC Work Plan, Comprehensive Community Relations Plan, ICO notification, GIS Work Area Grid, qualifications for all personnel and IVS results shall be submitted by the contractor and accepted by the Government prior to the commencing of intrusive activities.
3.2 Work Schedule for Intrusive Activities
Review the proposed work schedule and identify site specific issues and working hours of the EZ at the Post Award Kickoff Meeting.
The contractor shall schedule work appropriately to mitigate, to the greatest extent practicable, the impacts to base operations and the general public. Scheduling shall include phasing as well as night and weekend work as necessary.
3.3 Traffic Control
The Contractor shall provide traffic control in the form of signs that shall be posted 7 days prior to anomaly investigations to notify drivers of MEC investigative activities.
3.4 Enforcement of Exclusion Zones on Department of Defense (DOD) Property
The contractor shall be responsible for coordinating and issuing the notices of evacuation.
The contractor shall be responsible for providing reasonable levels of verification and enforcement of identified exclusion zones during MEC clearance activities.
Reasonable verification is defined as observations of the exclusion zone prior to commencing intrusive investigations.
Should unauthorized personnel be observed in the exclusion zone, the contractor shall verbally inform them of the scheduled work and request that they leave the EZ. Verbal contact is intended to remind the impacted occupants of the evacuation requirements and the time and duration when intrusive activities will commence.
Reasonable enforcement is defined as verbal notification and request to evacuate to any unauthorized individual observed inside the EZ limits during anomaly investigation. The contractor is required to stop anomaly investigation while unauthorized personnel are within EZs. Should
1383711
SECTION 01 57 19.01 20 Page 10 unauthorized personnel remain within the EZ after they have been verbally informed of the scheduled work and request to vacate, the contractor shall immediately notify the government point of contact in order of, Construction Management Engineer, Contracting Officer, Supervisory General Engineer, or FEAD/ROICC until positive contact with one or more is made. The contractor has no authority to detain or escort people out of the EZ.
EZ control shall be implemented by using entry control points (ECPs) to block access to the EZ during intrusive operations. ECPs along roads and sidewalks shall be sufficiently barricaded (e.g., road barriers, security/construction fencing) to block unauthorized access to the site during MEC operations. Signs shall be posted at each ECP with the point of contact information for the MEC Contractor’s Senior UXO Supervisor (SUXOS) and UXOSO. If a roadway or waterway located within the EZ cannot be blocked, spotters shall be used to alert the UXOSO and SUXOS to cease MEC operations when non-essential personnel enter into the EZ. Operations shall not be allowed to resume until nonessential personnel leave the EZ. All personnel working within the EZ shall stop work in the event that an unauthorized individual encroaches into the EZ.
Upon completion of the anomaly investigation activities in the established EZ, the contractor shall notify the Government and evacuees as soon as possible that they may return. Notification may be made by phone, text, social media, or other appropriate notification.
3.5 MEC Support Activities
The following subsections detail the explosives safety support requirements.
The Contractor shall execute all explosives safety requirements in accordance with the MEC Work Plan and the Apra Harbor Water ESS.
3.5.1 On-Call UXO Construction Support
The land areas of the project site are considered to have an “Unlikely” determination of containing MEC and or MPPEH. Therefore, On-Call Construction Support, per Apra Harbor Water ESS, is required for land-based repair/construction activities.
3.5.2 MEC Support to In-Water Operations
A MEC Support Team consisting of (at a minimum) one (1) SUXOS, one (1) dual-hatted UXOQCS/SO, one (1) UXO Technician III, and one (1) UXO Technician II shall be on site at all times to monitor dredging operations as described in Section 35 20 23.
During intrusive in-water operations, provide accommodations for Marine Resources Monitoring in accordance with specification section 01 57 19.01 20
SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS.
The MEC Support Team shall establish, coordinate, and enforce the required explosives safety related EZs for dredging operations established by the MEC Work Plan and the Apra Harbor Water ESS. During dredging operations, the MEC Support Team shall ensure that the dredge scow is fitted with a 3-inch screen to capture large debris. All material not passing through the scow screen shall be visually inspected by the MEC Support Team to ensure no MEC and or MPPEH is present.
Dredging materials passing through the 3-inch scow screen shall be transported (as described in the Apra Harbor Water ESS) to the identified screening area where materials shall be staged in a manner to facilitate the drying process.
1383711
SECTION 01 57 19.01 20 Page 11
Dredge materials shall not be released for disposal until inspected by the MEC Support Team in accordance with the requirements of the Apra Harbor Water ESS.
During dredging and subsequent screening operations, the contractor shall anticipate encountering significant quantities of various sizes of debris, including, but not limited to, steel, iron, aluminum, rope, plastic, wood, rocks, boulders, coral, rubber, tires and foam.
3.5.3 Mechanical Screening Operations in the Screening Area
Dried dredge materials (less than 3 inches) shall be transported to the screening area and shall undergo a subsequent screening process to remove MEC and MPPEH, down to 20 mm in size, prior to its release for disposal. As the dredging materials are reduced to 3-inches or less, there will be a reduction in the required operational EZs, per the Apra Harbor Water ESS which will allow the use of mechanized heavy equipment to facilitate the MEC/MPPEH screening process. The contractor shall assume that the materials will be transported to the screening processing area at an inconvenient time of day, e.g. night and/or weekend.
Mechanized heavy equipment for the MEC/MPPEH screening process may include tracked excavator, front end loaders, and a mobile screening plant with a final screen size of ¾-inches. Heavy equipment shall be outfitted with required DDESB approved shielding for operator protection per the Apra Harbor Water ESS.
Mechanical screening operations shall be conducted within the boundaries of the established temporary laydown area. The MEC Support Team shall be present at all times to support the mechanical screening of the 3-inch minus dredge materials and will inspect all material not passing the ¾-inch screen size. Intermittent screen sizes may be allowed, however passing material will still require screening down to the ¾-inch screen size to ensure MEC/MPPEH 20 mm and large is not present.
The MEC Support Team shall follow the inspection process detailed in the Apra Harbor Water ESS to visually insect and document the explosives status of all material prior to its release for disposal.
3.6 Imported Soils
The Contractor shall ensure that all imported soils are free of MEC/UXO/MPPEH items or metallic materials.
The Contractor shall afford Government representatives an opportunity to visit and view the source for any imported soils at the Government’s request.
3.7 Requirements When MEC/MPPEH is Encountered
Stop all work immediately if any material or object believed to be MEC/MPPEH is encountered and execute first response protocols immediately. Notify the UXO Technician III, UXOSO or SUXOS for a determination of MEC/MPPEH. Notify the Contracting Officer and Government MEC QA via telephone within 4 hours of discovery. Provide a written notification and initial Spot Report within 24 hours (one business day). Follow the safety reporting procedures of the MEC Work Plan.
The Contractor shall not blow-in-place or counter-charge any MEC/MPPEH encountered.
1383711
SECTION 01 57 19.01 20 Page 12
Both the SUXOS and UXOSO shall make a joint decision on whether the item is safe to move.
If MEC/MPPEH encountered is determined by the SUXOS and UXOSO to be safe to move and does not pose a threat to human health or the environment, it may be moved and temporarily stored on site in a secure location for the appropriate Government response team for further disposition. If MEC/MPPEH is not retrieved by the Government by the end of the same business day, the contractor shall provide services to guard the MEC/MPPEH, overnight if necessary, until retrieved.
If MEC/MPPEH encountered is determined by the SUXOS and UXOSO to be unsafe to move, poses a threat to human health and the environment or represents an imminent and substantial endangerment to human health and the environment, execute first response protocols immediately. The Contractor shall also coordinate as soon as possible with the appropriate Government Representative so that the appropriate EOD response team is dispatched by the Government for further disposition.
MEC and MPPEH storage, transportation and disposal will be accomplished by military EOD IAW the Apra Harbor Water ESS. The Contractor shall notify the Government to contact EOD. The contractor shall attempt to notify the Government point of contact in the following order: Construction Manager Engineer, Contracting Officer, Supervisory General Engineer, FEAD/ROICC, or Naval Base Guam Command Duty Officer / Andersen Airforce Base Command Post until positive contact with one or more is made.
Document transfer of MEC/MPPEH to EOD via the DD form 1348-1A.
3.7.1 Requirements When MEC/MPPEH is Encountered Greater than the Largest Approved Contingency
If while executing a munitions response, the contractor identifies a MEC item which has a greater maximum fragment distance-horizontal (MFD-H), hazardous fragment distance (HFD), or K328 distance than the approved MGFD;
the contractor shall cease all intrusive activities and notify the Contracting Officer. Intrusive work may recommence after putting in place either increased protection required by the item found or the contingency MGFD. If either represents a changed contract condition, the contractor shall immediately submit a written Request for Information to the Government and include the Contractor’s recommendation(s) to maintain the construction schedule.
3.8 Quality Control
The UXOQCS shall be responsible for Quality Control in accordance with Section 7 of the Apra Harbor Water ESS.
3.9 Government MEC Quality Assurance Specialist (QA)
The Contractor shall afford the Government an opportunity to complete the required Government MEC QA inspection prior to the area or soil being used for any construction activity. The Contractor shall identify MEC QC intrusive and soil processing activities on the project schedule and allow for two full business days to complete the required Government MEC QA inspection. For unplanned MEC QC activities not identified on the project schedule, the Contractor shall notify the Contracting Officer two full business days in advance of intrusive and/or soil processing activities and allow for two full business days to complete the required Government MEC QA inspection.
1383711
SECTION 01 57 19.01 20 Page 13
All anomalies recovered that are not MEC/MPPEH shall be collected and remain on-site for up to 10 business days or until the Government MEC QA has had an opportunity to perform a quality assurance check to ensure there is no MEC/MPPEH or MD/MDAS comingled with what would otherwise be considered scrap metal and/or debris.
-- End of Section --
1383711
SECTION 01 57 19.01 20 Page 14
MEC GIS requirement:
a. All MEC contracts are required to 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).
1383711
SECTION 01 57 19.01 20 Page 15
II. 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. 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
SECTION 01 57 19.01 20 Page 16
MEC Geodatabase Instruction for Construction Projects
(1) Construction Projects
(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 ESS 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
1383711
SECTION 01 57 19.01 20 Page 17
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)
(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
1383711
SECTION 01 57 19.01 20 Page 18
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
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
1383711
SECTION 01 57 19.01 20 Page 19 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 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
1383711
SECTION 01 57 19.01 20 Page 20
(If Excavated)
CYREMOVED: Cubic yards of soil removed Integer: Long
Documentation: Record source String: Length 255
1383711
SECTION 01 57 19.01 20 Page 21
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.
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
1383711
SECTION 01 57 19.01 20 Page 22
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:
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…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .