N4019222R2012_RFP_Part_B_Part_2_Specification_01_57_19_03_20_SUPP_TEMP_ENVI_CON_JRM_ESS.pdf
PDF 765 KB Posted
- Solicitation number
- N4019222R2012
About this file
This document provides details for a federal construction contract solicitation. The solicitation is for the design and construction of a 36,139 square foot National Guard Readiness Center in Barrigada, Guam to support training, administrative, and logistical requirements of the Guam Army National Guard. The supporting development includes utilities, a backup emergency generator, paved parking, and other necessary site improvements. The solicitation is issued as an unrestricted procurement by the Department of the Navy Naval Facilities Engineering Command utilizing source selection procedures requiring technical and past performance proposals and price proposals for evaluation. Offerors must submit a bid bond of $3,000,000 or 20% of the bid price, whichever is less. A pre-proposal conference and site visit will be held in May 2022. The price range for the construction project is between $25 million and $100 million. The point of contact is provided for any questions.
View the file
Other files
Show all 50
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
Solicitation No.
N4019222R2012
FY22 MILITARY CONSTRUCTION P-052
NATIONAL GUARD READINESS CENTER
BARRIGADA, GUAM
PART B
PART 2 – SPECIFICATION (SECTION 01 57 19 03 20
- SUPPLEMENTAL TEMPORARY ENVIRONMENTAL
CONTROLS JRM ESS)
FY22 National Guard Readiness Center Barrigada, Guam
WON 1674991
SECTION 01 57 19.03 20 Page 1
SECTION 01 57 19.03 20
SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS
Munitions Response Explosives Safety Submission (MRESS) Guam Construction
Support 4/21
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)
Guam Construction Support Munitions Response Explosives Safety MRESS (Amendment Series) Submission, GUAM CONSTRUCTION SUPPORT
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
SECTION 01 57 19.03 20 Page 2
NOSSAINST 8023.11D Standard Operating Procedures, Development, Implementation, and Maintenance for Ammunition and Explosives
OPNAVINST 3500.39D Department of the Navy OPNAVINST 3500.39D, Operational Risk Management
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
ESS Work Plan; G
Data Collection Results; G
Record of Training; G
Comprehensive Community Relations Plan; G
Installation Commanding Officer (ICO) Notification; G
Geographic Information System (GIS) Work Area Grid; G
Personnel Qualifications and Duties; G
Site Health and Safety Plan (SHSP); G
Data Collection Results; 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
SECTION 01 57 19.03 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 due to late submittals.
Except as specified otherwise, allow review period, beginning with receipt by accepting authority, to include 30 business 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. Latest version of the Guam Construction Support Munitions Response Explosives Safety MRESS, including the project-specific annex.
b. ESS Work Plan
c. NOSSA ltr 8020 Ser N45G/080 of 17 Jan 20 (WebESS ID# 547/ESS 19-24)
d. DDESB memo DDESB-PE of 24 Aug 18 (GG-052MOD)
e. NAVSEA OP 5 (Volume 1)
f. Other previous DDESB approvals
g. DDESB memo DDESB-PE of 24 Jan 20
h. Quality Control Log
i. Safety Meeting Attendance Log
j. Site Visitors Log
k. Safety Inspection Logs
l. Daily Report of MEC Operation
m. MPPEH Accountability Forms
1.4 Anomalies
An anomaly is defined as a metal item with any one dimension equal to the 20 mm projectile, project’s approved Target of Interest (TOI) or larger.
Historic anomaly averages, which may be contained within various references 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.
1.5 Personnel Qualifications and Duties
Personnel shall meet the minimum qualification standards set forth in DDESB TP 18 and the Guam Construction Support MRESS, including training and experience requirements. Personnel requirements and duties are defined in DDESB TP 18 and the Guam Construction Support MRESS.
The team composition and size shall be in accordance with EM 385-1-97.
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
SECTION 01 57 19.03 20 Page 4 seven business days prior to commencing intrusive activities. When submitting the qualifications, include a signed letter to the Contracting Officer certifying that key personnel meet the training and experience requirements for the position(s) held. The letter shall list, by name and position, all key personnel. The letter shall contain the following statement: “I certify that the personnel listed meet or exceed the contract requirements for the function they will perform.”
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 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 ESS work plan.
In the ESS 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 ESS 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 ESS 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 ESS 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.
SECTION 01 57 19.03 20 Page 5
In the ESS work plan, designate a primary SUXOS. The contractor shall not deviate from the identified SUXOS without government notification and
1.5.4 Geophysicist
A qualified geophysicist is required for geophysical classification or when DGM or AGC detection equipment is used. This individual is the project geophysicist-of-record and has overall responsibility for design, implementation, and management of geophysical investigations required for the work effort related to military munitions. The geophysicist is not required to be on-site full time during data collection; however, during DGM and AGC, either the UXOQCS or geophysicist must be on site.
1.5.5 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 and Guam Construction Support MRESS 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.6 Explosive Safety Awareness Training
Explosive safety awareness training shall be performed in accordance with the requirements of DDESB TP-18 for all site workers/personnel working in areas identified by the JRM ESS 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 annually for all site workers.
1.6 ESS Work Plan General Requirements
Submit the ESS Work Plan within 30 calendar days of Contract Award.
The ESS Work Plan shall be project-specific and address any unusual or unique aspects of the project or activity for which it is written. The ESS 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 ESS 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 ESS Work Plans only).
Once accepted by the Contracting Officer, the ESS Work Plan and attachments will be enforced as part of the contract. Only when the ESS Work Plan is accepted shall the contractor be permitted to begin remediation activities.
SECTION 01 57 19.03 20 Page 6
Contractor's failure to execute work in accordance with the approved ESS 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 ESS 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 ESS 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 notify the Contracting Office and Regional Operations Center immediately to begin response efforts. 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 MEC/MPPEH 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 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), traffic control plan, 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 QUALITY CONTROL for guidance on QC Reporting content.
1.9.1 Daily Quality Control (QC) Reports
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
SECTION 01 57 19.03 20 Page 7 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
Detection and positioning equipment calibration shall be in accordance with Chapter 5.3.1 and 5.3.2 of the Guam Construction Support MRESS.
Periodic reports documenting Detection and positioning equipment calibration Quality Control shall be submitted to the Government in accordance with Chapter 5.3.1 of the Guam Construction Support MRESS. The QC Report shall include operational checks of equipment, compliance with the accepted DGM and AGC ESS 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 notify the Contracting Office and Regional Operations Center immediately to begin response efforts. 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), condition (e.g. fuzed, not fuzed, fired, not fired), 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
SECTION 01 57 19.03 20 Page 8 system, method used to isolate the hazard, description of work being performed when MEC/MPPEH item was encountered, name(s) of personnel who found the item and names of the certified personnel that made the MEC/MPPEH determination. 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
AARs shall be submitted to the Contracting Officer within 15 business days of the completion of intrusive activities. AARs shall be provided in accordance with the AAR checklist included as an appendix to this specification section and shall meet the requirements set forth in references NAVSEA OP 5 Volume 1 Ch13-14 and NOSSAINST 8020.15 (Series).
PART 2 PRODUCTS
2.1 Detection Equipment, Methods and Standards
Detection equipment, methods and standards shall be in accordance with Chapter 5.1 of the Guam Construction Support MRESS. Detection equipment calibration shall be in accordance with Chapter 5.3.1 of the Guam Construction Support MRESS.
2.2 Positioning Systems, Methods and Standards
Positioning systems, methods and standards shall be in accordance with Chapter 5.2 of the Guam Construction Support MRESS and the GIS standards included as appendices to this specification section. Positioning equipment calibration shall be in accordance with Chapter 5.3.2 of the Guam Construction Support MRESS.
2.3 Storage of Data Collection
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.
DGM and/or AGC survey data shall be collected, downloaded and imported into the project database for review and reporting.
PART 3 EXECUTION
3.1 Commencing of Intrusive Activities
SECTION 01 57 19.03 20 Page 9
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 ESS 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 Occupancy, Population and Vehicle Survey
The contractor shall conduct the initial Occupancy, Population and Vehicle Survey between three months to two weeks prior to establishing EZs for intrusive activities. Follow on survey counts shall be conducted on a monthly basis thereafter to estimate the vehicular and pedestrian traffic traversing the EZs. Provide the following as part of the Occupancy, Population and Vehicle Survey.
For vehicular and pedestrian traffic, the contractor shall conduct counts of vehicles and personnel travelling in and around the area of interest where EZs are planned. The counts shall be conducted during timeframes similar to the intended work periods by posting personnel on site to perform the counts. At a minimum, the counts of vehicular and pedestrian traffic shall be based on two-day counts of vehicles and personnel travelling in and around the planned EZs during high and low volume traffic periods. Unless recommended or approved otherwise, use 0700-0800 hours for the high volume traffic period and 1800-1900 for the low volume traffic period. Establish monthly estimated counts based on the average daily estimate of vehicular and pedestrian traffic.
For projects with EZs on Department of Defense (DOD) Property, the contractor shall request the occupancy and population for the area of interest from the Public Works Office. The contractor shall also request an access list of Government personnel authorized to remain within buildings inside EZs. Authorized Government personnel are subject to change.
For projects with EZs on non-DOD Property, the contractor shall conduct a survey to determine the occupancy and population for the area of interest.
3.3 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.4 Community Outreach
The contractor shall develop a thorough strategy for community outreach and engagement to ensure all entities impacted by EZs are effectively identified, notified, and informed of anticipated ESS activities and their impacts in a timely manner. Upon Government acceptance of the Contractor’s
SECTION 01 57 19.03 20 Page 10
Comprehensive Community Relations Plan, the contractor shall coordinate regularly with the designated Government Project Team regarding the project-specific community engagement, outreach and public relations efforts.
The overall project community outreach and engagement strategy will be managed by the government. The contractor shall be responsible for drafting the development of documents to include, but not limited to, ICO notifications, written notices to property owners and businesses within EZs, design and implementation of traffic control, flyers, brochures, scripts that may be used for stakeholder briefs, draft public service announcements, draft media releases, coordination with on base activities, and local government, oral and written communication including face-to-face meetings, on-site notices as well as certified mail, and public service announcements using local media outlets, development and maintenance of a project website, and maintain a log book documenting oral and written communication, including face-to-face meetings.
Should any community outreach and engagement efforts require coordination with on base activities and local governments, coordination shall be via the NAVFAC Marianas project construction team and Public Affairs Officer.
Written notice to property owners and businesses within the exclusion zone shall be produced and mailed by the contractor in advance of anomaly investigation that impacts those particular properties after approval by the Government. Written notice shall provide the name of the project and the contractor, give a general statement of work and explosives safety concern, shall include the contractor’s website and the government contact number, and shall be approved by the government prior to issuance. The list of property owners will be provided by the contractor. The contractor shall maintain a complete list of the notices sent, detailing name and address of property, date of EZ impact, and date mailed. Should the contractor’s schedule of execution require that particular properties be impacted by EZ’s at separate times (i.e. in October and again in December), written notice shall be provided by the contractor for each occasion. Notice should also indicate the property owner’s responsibility to inform tenants, residents and/or employees as applicable.
The Contractor shall provide traffic control in the form of signs that shall be posted at least 7 calendar days prior to anomaly investigations to notify drivers of MEC/MPPEH investigative activities. These signs shall remain in place throughout the duration of the work activity.
All proposed Contractor written and oral communications must be approved by a designated Government representative prior to any and all communications with members of the public, stakeholders, etc.
COMMUNITY OUTREACH
ICO Briefs Provide briefing that includes schedule and areas impacted.
45 calendar days prior to intrusive investigations, updated every 30 days for duration of intrusive investigations.
Traffic Control Provide signs to notify drivers of upcoming and on-going work in accordance with approved
7 calendar days prior to start of anomaly investigations and remain in place until
SECTION 01 57 19.03 20 Page 11
Traffic Control Plan. investigation is complete
Advance door to door notices 1
Door to door notifications and all business and property occupants in effected EZ.
Print and post/handout flyers. Complete notification check log.4
7 calendar days prior to start of anomaly investigations that impact those particular properties. Template must be approved by the government.
Written notice to property owners and businesses 2
Print & mail letters to business and property owners and occupants in effected EZ. Complete notification check log.4
30 calendar days prior to start of anomaly investigations that impact those particular properties. Template must be approved by the government.
Door to door notices of imminent evacuation 3
Contractor shall hand-deliver notice to each business and residence and post on door/mailbox/other appropriate location if no one is available.
Notice identifies the start of anomaly investigation and traffic control points. Complete notification check log.4
24 hours prior to start of anomaly investigations that impacts those particular properties.
Template must be approved by the government.
Establish the EZ
At posted time for start of intrusive digging, contractor shall perform visual survey of EZ to ensure the EZ is clear.
Daily, at the start of anomaly investigations
NOTES:
1. The contractor (PR representatives) shall provide Government-approved initial notifications by walking door-to-door to meet with property occupant to explain the upcoming activities and their requested cooperation (i.e. evacuation, expected duration of displacement), prior to commencing intrusive investigations. Consideration of people’s schedules is necessary and notifications may occur outside of normal business hours and on weekends. If the property owner / tenant is not available (i.e. no one answers the door or a minor answers the door), the contractor shall leave a flyer in a visible location.
2. Contractor shall have a certified/registered mailing to landowners and tenants prior to intrusive investigations. The template for this mailing shall contain all pertinent information regarding the MEC schedule and impact and shall be approved by the government.
3. Contractor shall provide notice of imminent evacuation to all property owners / tenants prior to establishment of the EZ. The notice shall be in flyer format, approved by the government, and hand delivered to each property. Should the property owner / tenant not be available, the contractor shall leave the flyer in a visible location.
4. Contractor shall keep a detailed log of all notifications and responses. The contractor shall make full contact with all properties and tenants as detailed in this section. Should corrections (additions
SECTION 01 57 19.03 20 Page 12 or subtractions) to the property list be required, the contractor shall keep a detailed record of those changes. At a minimum the notification log should include the following data:
a. Name (property owner or tenant if name is available)
b. Time and date of each notification
c. Address
d. Telephone number (optional)
e. Response of intent (e.g. concurred to evacuate, refused to evacuate, or no response)
3.5 Enforcement of Exclusion Zones on Department of Defense (DOD) Property
The contractor shall be responsible for coordinating and issuing the notices of evacuation consistent with Section 3.4.
The contractor shall be responsible for providing reasonable levels of verification and enforcement of identified exclusion zones during ESS 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. Government MEC QA providing oversight of projects or enforcement of requirements are considered authorized personnel.
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 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.
SECTION 01 57 19.03 20 Page 13
3.5.1 Enforcement of Exclusion Zones on non-DOD Property
Neither the contractor nor the Government has authority to enforce exclusion zones on non-DOD property. Therefore, the contractor is not required to stop anomaly investigation while unauthorized personnel are within EZs on non-DOD property.
However, the contractor shall conduct Community Outreach in accordance with Section 3.4 of this specification and must specifically provide public notification to pedestrians, residents and motorists at access points to the exclusion zone(s) both before and during intrusive MEC investigations. The notification must be provided by signs a minimum of 7 calendar days prior to anomaly investigations and excavation operations in order to notify residents, drivers, and pedestrians of upcoming excavation operations/MEC investigations and must remain in place until investigation activities have concluded.
The Contractor shall also maintain a log book containing an estimate of vehicular traffic, pedestrians, and residents that traverse or are located within EZs during intrusive operations. At a minimum, the estimate of vehicular traffic, pedestrians, and residents that traverse or are located within EZs during intrusive operations shall be based on a monthly count of vehicles and personnel travelling in and around during high and low volume traffic periods. Unless recommended or approved otherwise, use 0700-0800 hours for the high volume traffic period and 1800-1900 for the low volume traffic period. This documentation shall be submitted to the Government upon completion of intrusive activities or on a monthly basis for activities lasting beyond 30 calendar days.
3.6 Soil Excavation and Removal
Soil excavation and removal shall be in accordance with the Guam Construction Support MRESS and NAVSEA OP 5.
3.7 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.
SECTION 01 57 19.03 20 Page 14
3.8 Bedrock Determinations for Unlikely Consideration
Determinations of a solid rock formation shall be made by a licensed Professional Geologist or Civil Engineer with a Professional Engineer (PE) license. Before the licensed professional makes a determination, the contractor shall fully expose the entire top layer of the solid rock formation over which the determination is being made. The area shall be cleared of all anomalies using full clearance techniques in accordance with the Guam Construction Support MRESS and NAVSEA OP 5. The area shall be physically identifiable at the site with the use of construction markers based on the determined Global Position System (GPS) coordinates.
Determinations shall be made in writing and include the following:
certifying stamp from the licensed individual making the determination;
three dimensional GPS coordinates (grid and depth) outlining the area for which the determination is being made; methods and criteria used to make the determination; and photographs of the area showing the solid rock formation.
A bedrock determination shall only be valid for the area defined. Anywhere outside of the area defined in the determination shall require a separate determination prior to being managed as unlikely.
In the event of a MEC/MPPEH discovery in an area previously classified as unlikely due to a solid rock formation determination, the provisions of Guam Construction Support MRESS with respect to a MEC/MPPEH discovery in an unlikely area shall immediately apply.
3.9 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 Office and Regional Operations Center immediately to begin response efforts. Provide a written notification and initial Spot Report within 24 hours (one business day). Follow the safety reporting procedures of the ESS Work Plan.
The Contractor shall not blow-in-place or counter-charge any MEC/MPPEH encountered.
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.
SECTION 01 57 19.03 20 Page 15
MEC and MPPEH storage, transportation and disposal will be accomplished by military EOD IAW Guam Construction Support MRESS. The Contractor shall notify the Government (Naval Base Guam Command Duty Officer/Andersen Air Force Base Command Post) until positive contact is made to dispatch EOD.
Immediately following this, the contractor shall notify the Government’s point of contact in the following order: Government MEC QA, Construction Manager Engineer, Contracting Officer, Supervisory General Engineer, FEAD/ROICC until positive contact with one or more is made.
Document transfer of MEC/MPPEH to EOD via the DD form 1348-1A.
3.9.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 written notification to the Contracting Officer, include rationale and supporting documentation for the increase, and offer the most cost effective recommendation(s) to maintain the construction schedule. Contractors are advised against providing cost proposals without guidance from the Contracting Officer.
3.10 Quality Control
The UXOQCS shall be responsible for Quality Control in accordance with section 7.1 of the Guam Construction Support MRESS.
3.11 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 an opportunity for Government MEC QA inspection.
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 --
SECTION 01 57 19.03 20 Page 16
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
SECTION 01 57 19.03 20 Page 17
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
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
SECTION 01 57 19.03 20 Page 18 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
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
SECTION 01 57 19.03 20 Page 19
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 during project (None)
(Yes;See ARR for spot reports
(On Going MEC Investigation)
ANOMILIES: Number of anomalies found Integer Long: 1,000,000+
SECTION 01 57 19.03 20 Page 20
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
(If Excavated)
CYREMOVED: Cubic yards of soil removed Integer: Long
Documentation: Record source String: Length 255
SECTION 01 57 19.03 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…
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 .