Attachment E - Dredging at JEBLCFS SPECS.pdf

eProjects WO#: 1840734

FY26 DREDGING AT:

JEBLC Fuel Pier, JEBLC Anzio Beach

Sandbar and JEBFS Utah Beach Sandbar, Virginia Beach, VA

DESIGNED BY:

NAVFAC MID-ATLANTIC - PDC CORE

Hydrographic Team (PDC45C)

9080 VIRGINIA AVE

NAVAL STATION NORFOLK, BLDG CEP-188

NORFOLK, VIRGINIA 23511

Date: February 25, 2026

SPECIFICATION PREPARED BY: James S. Georgo, P.E.

SPECIFICATIONS APPROVED BY:

Project Manager: Jeffrey L. Parrish

Chief Engineer: Jonathan W. Jarrett, P.E.

Lead Discipline Team Manager:

James S. Georgo, P.E. Date

James E. Donahue, R.A. Date

For Commander, NAVFAC MID-ATLANTIC:

Design Production Director Capital Improvements Core

JEBLC_FuelPier_Dredging_Anzio_Utah_Beach_Dredging 1840734

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 01 15 02/24 LIST OF DRAWINGS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 02/24, CHG 1: 05/25 SUMMARY OF WORK

01 14 00 11/11 WORK RESTRICTIONS

01 20 00 11/20, CHG 5: 02/25 PRICE AND PAYMENT PROCEDURES

01 30 00 11/20, CHG 5: 02/25 ADMINISTRATIVE REQUIREMENTS

01 31 23.13 20 08/23, CHG 1: 02/24 ELECTRONIC CONSTRUCTION AND FACILITY

SUPPORT CONTRACT MANAGEMENT SYSTEM

(eCMS)

01 32 16.00 20 08/18, CHG 1: 08/20 SMALL PROJECT CONSTRUCTION PROGRESS

SCHEDULES

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 35 26 05/24, CHG 1: 05/25 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 08/23, CHG 2: 05/25 QUALITY CONTROL

01 50 00 11/20, CHG 2: 08/22 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 20 23 04/06 DREDGING

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/24

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project pursuant to contract clause "DFARS 252.236-7001, Contract Drawings and Specifications."

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

SHEET NO. NAVFAC# SHEET TITLE

1 12921841 V-001 TITLE SHEET

2 12921842 V-002 DETAILS

3 12921843 V-101 FUEL PIER DREDGING PLAN

4 12921844 V-102 FUEL PIER DREDGING SAND BERM PLAN AND DETAILS

5 12921845 V-103 ANZIO BEACH SANDBAR DREDGING PLAN

6 12921846 V-104 UTAH BEACH SANDBAR DREDGING AND DUNE REPAIR PLAN

7 12921847 V-105 JEBFS PUBLIC WORKS COVE SAND FILL PLAN

-- End of Document --

DOCUMENT 00 01 15 Page 1

SECTION 01 11 00

SUMMARY OF WORK

02/24, CHG 1: 05/25

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Dredging Plan; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes Dredging of the JEB Little Creek Fuel Pier, JEB Little Creek Anzio Beach Sandbar and JEB Fort Story Utah Beach along with incidental related work as shown on plans.

All material excavated shall be disposed on-site by creating new and/or adding to existing sand berms as shown on drawings.

1.2.2 Location

The work is located atJoint Expeditionary Base - Little Creek and Joint Expeditionary Base - Fort Story, Virginia Beach, VA, as indicated on plans.

1.3 LOCATION OF UNDERGROUND UTILITIES

Contact local within sufficient time required. Existing underground utilities are shown on drawings. Locations shall be field confirmed and marked by the contractor prior to excavating sand berms.

companies and location work shall be borne by the contractor.

1.4 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the [Government designated] storage area.

SECTION 01 11 00 Page 1

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/11

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Pier Parking Authorization; G

Personnel List; G

Vehicle List; G

Dredge Plans; G

Dredge plans to show progressive positioning of dredge crane barge(s), scows, tender boats, etc... at the dredging site.

1.2 SPECIAL SCHEDULING REQUIREMENTS

a. COMMENCMENT OF WORK: Once the contract has been awarded the execution schedule shall be coordinated between the government and the contractor with a notice to proceed to be issued within approximately 90 days or less from the contract award date. Once the notice to proceed has been issued the contractor shall commence with mobilization and dredging no later than 30 days after Notice to Proceed.

b. The piers, waterfront, training beaches and navigation channel(s) at JEB Little Creek and JEB Fort Story shall remain in operation during the entire dredging period. The Contractor shall conduct operations so as to cause the least possible interference with normal operations of the activity. Government shall notify Contractor 48 hours in advance as to any ship movements in the area dredging is being conducted.

c. Contractor shall coordinate with the Contracting Officer prior to start of dredging to determine order of work. The Government reserves the right to change the order of work at any time.

d. Permission to interrupt any Activity roads, railroads, and/or utility service must be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

SECTION 01 14 00 Page 1

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.3.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.3.1.2 Installation Access

Obtain access to Navy installations through participation in the Defense Biometrics Identification System (DBIDS). Requirements for Contractor employee registration, and transition for employees currently under Navy Commercial Access Control System (NCACS), are available at . No fees are associated with obtaining a DBIDS credential.

Participation in the DBIDS is not mandatory, and Contractor personnel may apply for One-Day Passes at the Base Visitor Control Office to access an installation.

1.3.1.2.1 Registration for DBIDS

All Contractor personnel shall obtain access to the installation through enrollment and registration into the Defense Biometric Identification System (DBIDS). Procedure includes:

a. Presnet a letter or official award document (i.e. DD FORM 1155 or SF 1442) from the Contracting Officer, that provides the purpose for access, to the base Visitor Control Center representative.

b. Present valid identification, such as a passport or Real ID Act-compliant state driver's license.

c. Provide completed SECNAV FORM 5512/1 to the base Visitor Control Center representative to obtain a background check. This form is available for download at .

d. Upon successful completion of the background check, the Government will complete the DBIDS enrollment process, which includes Contractor employee photo, finger prints, base restriction and several other assessments.

e. Upon successful completion of the enrollment process, the Contractor employee will be issued a DBIDS credential, and will be allowed to proceed to worksite.

SECTION 01 14 00 Page 2

1.3.1.2.2 DBIDS Eligibility Requirements

Throughout the length of the contract, the Contractor employee must continue to meet background screen standards. Periodic background screenings are conducted to verify continued DBIDS participation and installation access privileges. DBIDS access privileges will be immediately suspended or revoked if at any time a Contractor employee becomes ineligible.

An adjudication process may be initiated when a background screen failure results in disqualificatoin from participation in the DBIDS, and Contractor employee does not agree with the reason for disqualification.

The Government is the final authority.

1.3.1.2.3 DBIDS Notification Requirements

a. Immediately report instances of lost or stolen badges to the Contracting Officer.

b. Immediately collect DBIDS credentials and notify the Contracting Officer in writing under the following circumstances:

(1) An employee has departed the company without having properly returned or surrendered their DBIDS credentials.

(2) There is a reasonable basis to conclude that an employee, or former employee, might pose a risk, compromise, or threat to the safety or security of the Installatoin or anyone therin.

1.3.1.2.4 One-Day Passes

Personnel applying for One-Day passes at the Base Visitor Control Office are subject to daily mandatory vehicle inspection, and will have limited access to the installation. The Government is not responsible for any cost or lost time associated with obtaining daily passes or added vehicle inspections incurred by non-participants in the DBIDS.

1.3.1.3 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installatoin, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.3.2 Working Hours

Normal duty hours for work shall be 24 hours a day Sunday through Saturday.

1.4 SECURITY REQUIREMENTS

Contract Clause FAR 52.204-2 Security Requirements and Alternate II," "FAC 5252.236-9301, Special Working Conditions and Entry to Work Area," and the following apply:

1.4.1 JEB Little Creek, Virginia Beach, VA

a. Contractor registration. Register with the Base Security.

SECTION 01 14 00 Page 3

b. Storage and office trailer registration. Register storage and office trailers to be used on base with the truck investigation team. Trailers must meet State law requirements and must be in good condition.

(1) Trailers shall be lockable and must be locked when not in use.

(2) Trailers shall have a sign in the lower left hand corner of left door of trailer with the following information: Company name, address, registration number of trailer or vehicle identification number, location on base, duration of contract or stay on base, contract number, local on-base phone number, off-base phone number of main office, and emergency recall person and phone number.

c. Equipment markings. Equipment owned or rented by the company shall have the company name painted or stenciled on the equipment in a conspicuous location. Rented equipment is to be conspicuously marked with a tag showing who rented the equipment. Register the equipment with the truck investigation team.

d. Procedure information. For additional information regarding registration procedures, contact the Officer in Charge of Construction at (757) 445-1463 or Base Police at (757) 444-8856.

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

SECTION 01 14 00 Page 4

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

11/20, CHG 5: 02/25

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.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EP 1110-1-8 (2021) Engineering and Design -- Construction Equipment Ownership and Operating Expense Schedule

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

[Schedule of Prices]; G

1.3 [SCHEDULE OF PRICES]

1.3.1 Data Required

Within 15 calendar days of notice of award, prepare and deliver to the Contracting Officer a Schedule of Prices (construction contract) as directed by the Contracting Officer. Provide a detailed breakdown of the contract price, giving quantities for each of the various kinds of work, unit prices, and extended prices therefore in accordance with the bid schedule. Costs shall be summarized and totals provided for each construction category.

1.3.2 Payment Schedule Instructions

Payments will not be made until the [Schedule of Prices] has been submitted to and accepted by the Contracting Officer.

1.4 CONTRACT MODIFICATIONS

In conjunction with the Contract Clause DFARS 252.236-7000 Modification Proposals-Price Breakdown, and where actual ownership and operating costs of construction equipment cannot be determined from Contractor accounting records, base equipment use rates upon the applicable provisions of the

SECTION 01 20 00 Page 1

EP 1110-1-8 .

1.5 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

1.5.1 Content of Invoice

Requests for payment will be processed in accordance with the Contract Clause FAR 52.232-27 Prompt Payment for Construction Contracts and FAR 52.232-5 Payments Under Fixed-Price Construction Contracts. Invoices not completed in accordance with contract requirements will be returned to the Contractor for correction of the deficiencies. Include the documents listed below in the requests for payment.

a. The Contractor's invoice, on NAVFAC Form 7300/30 furnished by the Government, showing in summary form, the basis for arriving at the amount of the invoice. Form 7300/30 must include certification by Quality Control (QC) Manager as required by the Contract.

b. The [Estimate for Voucher/ Contract Performance Statement on NAVFAC Form 4330/54 furnished by the Government. Use NAVFAC Form 4330, unless otherwise directed by the Contracting Officer, on NAVFAC Contracts when a Monthly Estimate for Voucher is required. ][Earned Value Report from the cost-loaded NAS.]

c. Contractor's Monthly Estimate for Voucher and Contractors Certification (NAVFAC Form 4330) with Subcontractor and supplier payment certification. Other documents, including but not limited to, that need to be received prior to processing payment include the following submittals as required. These items are still required monthly even when a pay voucher is not submitted.

d. Monthly Work-hour report.

e. Updated Construction Progress Schedule and tabular reports required by the contract.

f. Contractor Safety Self Evaluation Checklist.

g. Updated submittal register.

h. Solid Waste Disposal Report.

i. Certified payrolls.

j. Updated testing logs.

k. Other supporting documents as requested.

1.5.2 Submission of Invoices

Monthly invoices and supporting forms for work performed through the anniversary award date of the Contract must be submitted to the Contracting Officer within 5 calendar days of the date of invoice. For example, if Contract award date is the 7th of the month, the date of each monthly invoice must be the 7th and the invoice must be submitted by the 12th of the month.

SECTION 01 20 00 Page 2

1.6 PAYMENTS TO THE CONTRACTOR

Payments will be made on submission of itemized requests by the Contractor which comply with the requirements of this section, and will be subject to reduction for overpayments or increase for underpayments made on previous payments to the Contractor.

1.6.1 Obligation of Government Payments

The obligation of the Government to make payments required under the provisions of this Contract will, at the discretion of the Contracting Officer, be subject to reductions and suspensions permitted under the FAR and agency regulations including the following in accordance with FAR

32.103 Progress Payments Under Construction Contracts:

a. Reasonable deductions due to defects in material or workmanship;

b. Claims which the Government may have against the Contractor under or in connection with this Contract;

c. Unless otherwise adjusted, repayment to the Government upon demand for overpayments made to the Contractor; and

d. Failure to maintain accurate "as-built" or record drawings in accordance with FAR 52.236.21 and the contract.

e. Failure to submit accurate monthly schedule updates in accordance with the contract.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 20 00 Page 3

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 5: 02/25

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.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements

1.2 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by [State ]law.

1.3 SUPERVISION

1.3.1 Superintendent Qualifications

Provide project superintendent with a minimum of [10][_____] years experience in construction with at least [5][_____] of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.3.2 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work. In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.

1.3.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule

SECTION 01 30 00 Page 1 adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.3.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time or excess costs or damages by the Contractor.

1.4 PRECONSTRUCTION MEETING

prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction Meeting . The purpose of this meeting is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.4.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.5 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled Red Zone Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:

1.5.1 Red Zone Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.

b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.

SECTION 01 30 00 Page 2

1.5.2 Meetings

a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.

b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.

At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.

c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.

d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.

e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.

Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.

1.6 MOBILIZATION

Mobilize to the jobsite within [30 calendar days of GOVERNMENT ISSUANCE OF NOTICE TO PROCEED. Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.

] PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 30 00 Page 3

SECTION 01 31 23.13 20

ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT MANAGEMENT SYSTEM

(eCMS)

08/23, CHG 1: 02/24

PART 1 GENERAL

1.1 CONTRACT ADMINISTRATION

Utilize the Naval Facilities Engineering Systems Command's (NAVFAC's) Electronic Construction and Facility Support Contract Management System (eCMS) for the transfer, sharing, and management of electronic technical submittals and documents. The web-based eCMS is the designated means of transferring technical documents between the Contractor and the Government. Paper media or email submission, including originals or copies, of the documents are not permitted unless identified within the contract.

All government contracting specialist/officer, legal, and command communications will remain the same.

1.2 USER PRIVILEGES

The Contractor's key staff may be provided access to eCMS. Contact the COR for eCMS account access. Project roles and system roles will be established to control each user's menu, application, and software privileges, including the ability to create, edit, or delete objects.

Additional project roles may be assigned for workflow. The COR makes the final decision on roles for the project. User's ability to view, edit documents may be lowered at the discretion of the COR.

Only one eCMS user account is required regardless of the number of user's projects. Notify the COR within seven calendar days if a contractor user is no longer associated with company or project so they can remove them from any open record and inactivate them from the project.

1.2.1 eCMS Subcontractor Users

If the contractor's user is a subcontractor, the subcontractor must be registered under the name of their company and email. For example it is common for contractors to contract Quality Control Managers. The QC Manager's account should be under their company's name and email reducing the number of eCMS accounts required.

1.2.2 Users with Multiple Roles

Users may have multiple roles associated with their account within eCMS.

Roles are used in workflow. When a user is added to the project, they will be assigned the default role when the user was created. Contact the COR to change or add roles to the user for the project.

1.2.3 Loss of Privilege

Users may lose privilege to access eCMS at the discretion of the Contracting Officer. The eCMS is a collaborative system that allows flexibility of use and does not restrict all inappropriate user actions.

User activities are logged into eCMS in visible and background data

SECTION 01 31 23.13 20 Page 1 collection. Users found to use eCMS in an inappropriate action may have their eCMS access revoked. Examples include, but not limited to, fraudulent representations, sharing user accounts with others, and changing approved records without the consent of the COR. Depending on the severity of the infraction, the users can lose eCMS access for a period of time, permanently for the project, or lose eCMS access for any project. The contractor may appeal the suspension in writing to the contracting officer within 14 calendar days of notice. The appeal must identify the infraction, supporting information, and steps to ensure the infraction will not happen in the future.

1.3 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contractor's Personnel; G

For Division 1 government approved Pre-Construction submittals, combine into a single Pre-Construction Submittal Package.

Annotated with SD Type of SD-01. Pre-Construction submittal package approval date will be used as a KPI.

1.4 SYSTEM REQUIREMENTS AND CONNECTIVITY

1.4.1 General

NAVFAC eCMS requires a web-browser (platform-neutral) and Internet connection. For best results, recommend using browser in InPrivate/Incognito mode; Internet speeds greater than 40mbps when uploading files, computers with high RAM and Solid State Drives, "White List" eCMS website, Zip or Split files for better uploading. Non-NAVFAC Users are not to use VPN when using eCMS per NAVFAC IT.

The use of eCMS is required by the Contractor and all associated costs and time necessary to utilize eCMS will be borne by the Contractor with no allowance for time extensions and at no additional cost to the government.

1.4.2 Contractor Personnel List

Within 20 calendar days of contract award, provide to the Contracting Officer a list of Contractor's personnel who will have the responsibility for the transfer, sharing and management of electronic submittals, RFIs, daily reports, and other files and will require access to the eCMS.

Project personnel roles which must be filled as applicable in the eCMS, include, at a minimum, the Contractor's Project Manager (KTR-PM), Superintendent (KTSUPT), Quality Control (QC) Manager (KTR-QC), Principal (KTR-PRIN), and Site Safety and Health Officer (KTR-SSHO). Notify the COR immediately of any personnel changes to the project. The Contracting Officer reserves the right to perform a security check on all potential users.

Internal design deliberations under a D-B contract are managed outside of eCMS. Besides the D-B DOR Representative, D-B design team members are neither required nor encouraged to create user accounts in eCMS. Users

SECTION 01 31 23.13 20 Page 2 are highly recommended to take eCMS live or online training prior to use.

See https://www.navfac.navy.mil/Business-Lines/Design-and- Construction/About-Us/Design-and-Construction-Documents/Electronic- Construction-Management-System-eCMS/ for eCMS useful information

Provide the following information:

Company Name

Name (First, Last)

Email Address

Project Role (CQM, SSHO, Superintendent, CM, PM, Principal)

Existing or New eCMS User

1.5 SECURITY CLASSIFICATION

In accordance with Department of Navy guidance, all military construction contract data are unclassified, unless specified otherwise by a properly designated Original Classification Authority (OCA) and in accordance with an established Security Classification Guide (SCG). Refer to the project's OCA when questions arise about the proper classification of information.

In conformance with the Freedom of Information Act (FOIA), DoD INSTRUCTION 5200.48 CONTROLLED UNCLASSIFIED INFORMATION (CUI), and DoD requirements, any unclassified project documentation uploaded into the eCMS must be designated either "U - UNCLASSIFIED" (U) or "CUI - CONTROLLED UNCLASSIFIED INFORMATION" (CUI).NAVFAC eCMS must only be used for the transaction of unclassified information associated with construction projects. Controlled Unclassified Identification (CUI) documents may be loaded into eCMS with the appropriate markings.

1.5.1 Markings on CUI Documents

Contractor's proprietary information, or documents determined by the originator in accordance with CUI guidance, should be marked CUI.

Proprietary information not marked CUI can be released under the Freedom of Information Act (FOIA). Apply the appropriate markings before any document is uploaded into eCMS. Markings are not required on Unclassified U documents.

1.6 eCMS UTILIZATION

Establish, maintain, and update data and documentation in the eCMS throughout the duration of the contract. Utilize eCMS to transfer all submittals, RFIs, daily reports, and other files required by contract to be forwarded to the government.

Full eCMS use is required. All Submittals/Information to use eCMS Modules including, but not limited to, RFIs, Daily Reports, Meeting Minutes, Communications, Issues, Punch Lists, Checklists, and Flysheets, unless otherwise directed by the COR or Contracting Officer.

The eCMS as an Electronic File Repository is authorized for projects under $1M. Upload all files using the appropriate eCMS module or as directed by the COR. Bulk uploads of RFIs, Submittals, Daily Reports, Issues, Meeting

SECTION 01 31 23.13 20 Page 3

Minutes or Communications records into eCMS modules are allowed. For RFIs, group files by specification number, RFP Part number, or sheet number. For Submittals, group files by specification number. For Daily Reports, group by date range(s), Issues by date range(s), Meeting Minutes by date range(s), and Communications by Type.

1.6.1 Restricted Information

Personally Identifiable Information (PII) transmittal such as credit card, driver's license, passport, social security, and payroll number are not permitted in eCMS. Name, address, and email are permitted.

Pre-negotiation information such as cost estimates that require formal negotiations are not allowed. For example, proposed changes over the SAP level of $250k require formal negotiations. Cost estimates for LEAN, ULTRA LEAN, and Design Changes under the SAP level are at the discretion of the COR's or Contract Specialist/Officer's direction. The eCMS must only be used for the transaction of unclassified information associated with construction projects. Controlled Unclassified Identification (CUI) documents may be loaded into eCMS with the appropriate markings.

Uploading of files directly into the Documents folder is not allowed. All documents must be uploaded using an eCMS module.

1.6.2 Naming Convention for Files

Titles of files uploaded are to be descriptive of the purpose and content of the file. For example RFI_ROOF_Leak.doc or for submittals, SUB_LIGHT_FIXTURE.pdf. Titles of file to be uploaded must only contain uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_) and periods (.). Use of any other characters is not allowed and may create an error. When practicable, adding the record number to the title is desired. For example RFI_XYZ12345_ROOF_Leak.doc. Uploading files with the same title will create a new revision in eCMS. Original revision is Rev 0, the first revision is Rev 1. Uploaded files are to use the default file location regardless of the module used unless directed by the COR.

Table 1 also identifies which eCMS application is to be used in the transmittal of data (these are subject to change based on the latest software configuration).

Table 1 - Project Documentation Types

SUBJECT/NAME REMARKS eCMS APPLICATION

As-Built Drawings Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals

SECTION 01 31 23.13 20 Page 4

SUBJECT/NAME REMARKS eCMS APPLICATION

Building Information Modeling (BIM)

Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals

Construction Permits Refer to rules of the issuing activity, state or jurisdiction

Submittals

Construction Schedules (Activities and Milestones)

Submittals

Construction Schedules Submittals

Construction Schedules (3-Week Look ahead)

Import the schedule file into the scheduling application, and select "Approve" to establish a new schedule baseline

Meeting Minutes

DD 1354 Transfer of Real Property

When applicable, required for final billing.

Submittals

Daily Production Reports

Provide weather conditions, crew size, man-hours, equipment, and materials information

Daily Report

Daily Quality Control (QC) Reports

Provide QC Phase, Definable Features of Work Identify visitors

Daily Report

Designs and Specifications

Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals

Environmental Notice of Violation (NOV), Corrective Action Plan

Refer to rules of the issuing activity, state or jurisdiction

Submittals

Environmental Protection Plan (EPP)

Submittals

Invoice (Supporting Documentation)

Applies to supporting documentation only. Invoices are submitted in Wide-Area Workflow (WAWF)

Submittals

SECTION 01 31 23.13 20 Page 5

Jobsite Documentation, Bulletin Board, Labor Laws, SDS

Redact any PII information when loaded into eCMS

Submittals

Meeting Minutes Meeting Minutes

Modification Documents Provide final modification documents for the project. Upload into Modifications RFPs folder

Communications

Operations & Maintenance Support Information (OMSI/eOMSI), Facility Data Worksheet

1. Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

2. Design reviews will be performed in existing "Dr Checks"

Submittals

Photographs Subject to base/installation restrictions Submittals

QCM Initial Phase Checklists

Meeting Minutes or Checklists

QCM Preparatory Phase Checklists

Meeting Minutes or Checklists

Quality Control Plans Submittals

QC Certifications Submittals

QC Punch List Punch Lists

Red-Zone Checklist Punch List or Checklists

Rework Items List Punch Lists

Request for Information (RFI) Post-Award

RFIs

Safety Plan Submittals

SECTION 01 31 23.13 20 Page 6

Safety - Activity Hazard Analyses (AHA)

Submittals

Safety - Mishap Reports Daily Report

Shop Drawings Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals

Storm Water Pollution Prevention (Notice of Intent - Notice of Termination)

Refer to rules of the issuing activity, state or jurisdiction

Submittals

Submittals and Submittal Register

Submittals

Testing Plans, Logs, and Reports

Submittals

Training/Reference Materials

Submittals

Training Records (Personnel)

Redact any PII information if storing in eCMS

Submittals

Utility Outage/Tie-In Request/Approval

Submittals

Warranties/BOD Letter Submittals

Quality Assurance Reports

Checklists (Government initiated)

Non-Compliance Notices Non-Compliance Notices (Government initiated)

Other Government-prepared documents

GOV ONLY

SECTION 01 31 23.13 20 Page 7

Letters to government contracting, claims, REAs, and other contracting officer communications eCMS is not the primary tool to use in contracting officer communications. eCMS can only store documents or letters after the submission to the contracting officer is made.

Communications

All Othere Documents Refer to FOIA guidelines and contact the FOIA official to determine whether exemptions exist

As applicable

1.6.3 RFIs Module

Create contractor RFIs using eCMS RFIs module. The contractor must confirm the numbering convention with the COR if different than eCMS default.

If the government (GOV) Response has "No" Cost or Schedule Impact, this reply is given with the expressed understanding that it does not constitute a basis for any change in the amount or time of subject contract. Information provided in this response does not authorize work not currently included in the contract. If GOV Response is "Yes" or "Potentially" then this response may require a change to the contract. If the contractor disagrees with either the government's No Cost determination or No Schedule impact determination, or both, the contractor has 14 calendar days to notify the COR and Contracting Officer in writing.

1.6.4 Submittals Module

Create contractor submittals using eCMS Submittals module. The contractor must confirm the numbering convention with the COR if different than eCMS default.

1.6.5 Submittal Packages Module

Create submittal packages using the eCMS Submittal Packages module in lieu of or in addition to Related Objects. Submittal Packages track completion of the packaged submittals and is used in NAVFAC HQ's KPIs.

1.6.6 Communications Module

Create communications using the eCMS Communications module. The Communications module is used to create or document communications that are not a part of other eCMS modules. Use of Communications module will memorialize information into an eCMS record file. The following are Types of Communications:

Email

Memo to File

Face to Face

Telephone

SECTION 01 31 23.13 20 Page 8

Web Collaboration

Photos

Other Documents

Other

Unless directed by the COR, upload documents or files that do not have a corresponding eCMS module. Choose "Photos" Type for Photos and "Other Documents" for all other documents.

1.6.7 Issues Module

Create or respond to issues using the eCMS Issues module. Respond to CPARS issues using the Issues module.

1.6.8 Meeting Minutes Module

Create or respond to Meeting Minutes using the eCMS Meetings module.

Document required contractual meetings. Dates of meetings are used in NAVFAC KPIs. Minimum meetings in eCMS include the following:

Post Award Kickoff (PAK)

Pre-construction (Pre Con)

Initial and Preparatory Three Phases of Control

Quality Control (QC)

1.6.9 Potential Change Items Module

Not used.

1.6.10 Daily Report Module

Create Daily Reports using the eCMS Daily Report Module. The contractor must confirm the numbering convention with the COR if different than eCMS default.

1.6.11 Punchlists Testing Logs (Legacy)

Punchlist Testing Logs is a legacy program that is being replaced by the Punch Lists Module. This module is to be used for reference of past projects. Use the Punch Lists Module for all future work.

1.6.12 Punch Lists Module

The eCMS Punch Lists module is useful more than just for Punchlists. The module includes the capability of batch editing, create items from Optical Character Recognition (OCR) plans, assign tasks and track completion of individual items.

Create the following using the Punch Lists module:

Rework Items List

SECTION 01 31 23.13 20 Page 9

DFOW List

Punch-Out Inspection

Pre-Final Punchlist Inspection

Final Punchlist Inspection

Testing Logs

1.6.13 FWD UltraLean COAR RFP Module

Not used.

1.6.14 Non-Compliance Notices (NCN) Module

Respond to Non-Compliance Notices listed in the Non-Compliance Notices module.

1.6.15 Checklists

Use Checklist listed in the contractor's eCMS menu and as directed by the COR. Checklists capture data and is used in dashboards and KPIs.

1.6.15.1 Partnering Team Health Survey Checklist

Contractor must use the eCMS checklist to document the partnering team health survey. Partnering Team Health Survey is in accordance with the Partnering Specification of this contract.

1.6.16 Flysheets

Use Flysheets listed in the contractor's eCMS menu, if available, and as directed by the COR. Flysheets allow the contractor to print out information from other systems and upload into eCMS. The eCMS will use OCR to capture the information as data. Flysheets capture data and used in dashboards and KPIs.

1.6.17 eCMS Outage

In the case where eCMS is unavailable for 8 hours or more, paper or email may be used in the interim to maintain project schedule.

Once the system is operational, all final records are required to be recreated using the appropriate module. Subject/title of the record to include the type of record i.e., RFI/Submittal/Daily Report/Communication/Other, the identification number(s), and the statement "Processed Outside of eCMS". Example, "RFI 001 Processed Outside of eCMS".

1.6.18 User Account Activity

NAVFAC eCMS captures user data and activities that are directly related to the user's account. The user agrees through the use of eCMS, their account activities will be captured and can be displayed on eCMS printed reports.

SECTION 01 31 23.13 20 Page 10

1.7 QUALITY ASSURANCE

Requested Government response dates on Submittals must be in accordance with the terms and conditions of the Contract unless previously agreed by the COR. Requesting response dates earlier than the required review and response time, without concurrence by the Government COR, may be cause for rejection.

Incomplete submittals will be rejected without further review and must be resubmitted. Required Government response dates for resubmittals must reflect the date of resubmittal, not the original submittal date.

All submittals and associated attachments must be transmitted to the Government via the COR. Transmittals are no longer required when using eCMS since approval status is tracked on the submittal. Transmittal forms can be attached to submittals if approved by the COR. Submittals requiring government approval are "Transmitted For" "Approval".

Submittals requiring contractor approved submittals, including those designated for Contractor Quality Control approval or Information Only, are "*Transmitted For" "Information Only" in the Submittal Module.

Provide and sign the QC certification or approving statement on the attachment per submittal specification section. When Submittal Packages are required, use eCMS Submittal Packages after creating individual submittals. Importing Submittals from the Submittal Register is optional. Contact the COR for the data conversion requirements.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 31 23.13 20 Page 11

SECTION 01 32 16.00 20

SMALL PROJECT CONSTRUCTION PROGRESS SCHEDULES

08/18, CHG 1: 08/20

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Baseline Construction Schedule; G

SD-07 Certificates

Monthly Updates

1.2 PRE-CONSTRUCTION SCHEDULE REQUIREMENT

Prior to the start of work, prepare and submit to the Contracting Officer a Baseline Construction Schedule in the form of a Bar Chart Schedule in accordance with the terms in Contract Clause FAR 52.236-15 Schedules for Construction Contracts, except as modified in this contract. The approval of a Baseline Construction Schedule is a condition precedent to:

a. The Contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoice(s) for construction activities/items of work.

c. Review of any schedule updates.

Submittal of the Baseline Construction Schedule, and subsequent schedule updates, is understood to be the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents, represents the Contractor's plan on how the work will be accomplished, and accurately reflects the work that has been accomplished and how it was sequenced (as-built logic).

1.3 SCHEDULE FORMAT

1.3.1 Bar Chart Schedule

The Bar Chart must, as a minimum, show work activities, submittals, Government review periods, material/equipment delivery, utility outages, on-site construction, inspection, testing, and closeout activities. The Bar Chart must be time scaled and generated using an electronic spreadsheet program.

1.3.2 Schedule Submittals and Procedures

Submit Schedules and updates in hard copy and on electronic media that is

SECTION 01 32 16.00 20 Page 1 acceptable to the Contracting Officer. Submit an electronic back-up of the project schedule in an import format compatible with the Government's scheduling program.

1.4 SCHEDULE MONTHLY UPDATES

Update the Construction Schedule at monthly intervals or when the schedule has been revised. Keep the updated schedule current, reflecting actual activity progress and plan for completing the remaining work. Submit copies of purchase orders and confirmation of delivery dates as directed by the Contracting Officer.

a. Narrative Report: Identify and justify the following:

(1) Progress made in each area of the project;

(2) Longest Path: Include printed copy on 11 by 17 inch paper, landscape setting;

(3) Date/time constraint(s), other than those required by the contract;

(4) Listing of changes made between the previous schedule and current updated schedule including: added or removed activities, original and remaining durations for activities that have not started, logic (sequence, constraint, lag/lead), milestones, planned sequence of operations, longest path, calendars or calendar assignments, and cost loading.

(5) Any decrease in previously reported activity Earned Amount;

(6) Pending items and status thereof, including permits, changes orders, and time extensions;

(7) Status of Contract Completion Date and interim milestones;

(8) Current and anticipated delays (describe cause of delay and corrective actions(s) and mitigation measures to minimize);

(9) Description of current and future schedule problem areas.

For each entry in the narrative report, cite the respective Activity ID and Activity Name, the date and reason for the change, and description of the change.

1.5 3-WEEK LOOK AHEAD SCHEDULE

Prepare and issue a 3-Week Look Ahead schedule to provide a more detailed day-to-day plan of upcoming work identified on the Construction Schedule.

Key the work plans to activity numbers when a NAS is required and update each week to show the planned work for the current and following two-week period. Additionally, include upcoming outages, closures, preparatory meetings, and initial meetings. Identify critical path activities on the Three-Week Look Ahead Schedule. The detail work plans are to be bar chart type schedules, maintained separately from the Construction Schedule on an electronic spreadsheet program and printed on 8-1/2 by 11 inch sheets as directed by the Contracting Officer. Activities must not exceed 5 working days in duration and have sufficient level of detail to assign crews, tools and equipment required to complete the work. Deliver three hard

SECTION 01 32 16.00 20 Page 2 copies and one electronic file of the 3-Week Look Ahead Schedule to the Contracting Officer no later than 8 a.m. each Monday, and review during the weekly CQC Coordination or Production Meeting.

1.6 CORRESPONDENCE AND TEST REPORTS:

Correspondence (e.g., letters, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) must reference Schedule Activities that are being addressed. Test reports (e.g., concrete, soil compaction, weld, pressure) must reference Schedule Activities that are being addressed.

1.7 ADDITIONAL SCHEDULING REQUIREMENTS

Any references to additional scheduling requirements, including systems to be inspected, tested and commissioned, that are located throughout the remainder of the Contract Documents, are subject to all requirements of this section.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 32 16.00 20 Page 3

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/18, CHG 4: 02/21

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

SD-01 Preconstruction Submittals

Submittals that are required prior to or commencing with the start of work on site.

Government approved Division 01 preconstruction submittals that are required prior to or commencing with the start of work must be submitted within 30 calendar days of contract award unless specified elsewhere in the specifications.

Preconstruction Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials,…