Attachment A -1751868 Specifications.pdf

CONSTRUCT ACCESS ROADS AT

BUILDINGS 428 AND 1348

At the

Naval Weapons Station Yorktown Yorktown, Virginia

DESIGNED BY:

NAVFAC MID-ATLANTIC, PWD YORKTOWN

NAVAL WEAPONS STATION YORKTOWN

YORKTOWN, VIRGINIA

eProject No. 1751868

SPECIFICATION PREPARED BY:

Civil/Structural: Scott Aggerup, P.E.

Date: October 16 2023

SPECIFICATION APPROVED BY:

Engineering Design Director: David Harris, P.E.

Construct Access Roads at Buildings 428 and 1348 eProject 1751868

PROJECT TABLE OF CONTENTS

DI VI SI ON 00 - PROCUREMENT AND CONTRACTI NG REQUI REMENTS

00 01 15 LIST OF DRAWINGS

00 22 13.00 20 SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 20 00.00 20 PRICE AND PAYMENT PROCEDURES

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 31 23.13 20 ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT

MANAGEMENT SYSTEM (eCMS)

01 32 16.00 20 SMALL PROJECT CONSTRUCTION PROGRESS SCHEDULES

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 DEMOLITION

DI VI SI ON 31 - EARTHWORK

31 00 00 EARTHWORK

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS

32 31 13.53 HIGH-SECURITY CHAIN LINK CANTILEVER SLIDE GATE

DI VI SI ON 33 - UTI LI TI ES

33 40 00 STORMWATER UTILITIES

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/ 11, CHG 1: 08/ 14

PART 1 GENERAL

1.1 SUMMARY

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

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

SHEET NAVFAC TITLE

NO. DWG NO.

G-001 12895703 TITLE SHEET

GR501 12895704 PHOTOS

CD101 12895705 DEMOLITION PLAN AT BUILDING 428

C-101 12895706 EARTHWORK PLAN AT BUILDING 428

C-102 12895707 CONSTRUCTION PLAN AT BUILDING 428

C-103 12895708 EARTHWORK PLAN AT BUILDING 1348

C-104 12895709 CONSTRUCTION PLAN AT BUILDING 1348

C-105 12895710 GATE PLAN AT BUILDING 1348

C-301 12895711 EARTHWORK SECTIONS AT BUILDING 428

C-302 12895712 EARTHWORK SECTIONS AT BUILDING 428

C-303 12895713 EARTHWORK SECTIONS AT BUILDING 428

C-304 12895714 EARTHWORK SECTIONS AT BUILDING 428

C-305 12895715 EARTHWORK SECTIONS AT BUILDING 1348

C-306 12895716 EARTHWORK SECTIONS AT BUILDING 1348

C-307 12895717 EARTHWORK SECTIONS AT BUILDING 1348

C-501 12895718 GATE DETAILS AT BUILDING 1348

-- End of Document --

DOCUMENT 00 01 15 Page 1

DOCUMENT 00 22 13.00 20

SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

02/ 14, CHG 3: 11/ 18

PART 1 GENERAL

1.1 CONTRACT LINE ITEMS

The terms Offeror and Bidder and versions thereof (offer/bid) have the same definition as used within this contract.

Provide the Contract Line Item (CLIN) lump sum price for the following items:

CLIN 0001 - BASE PRICE. Price includes the following:

CLIN 0001AA. Price for the entire work in accordance with the drawings and specifications, but excluding work described in Contract Line Items CLIN 0001AB.

CLIN DESCRIPTION TOTAL PRICE

0001AA Construct Access Roads at Buildings 428 & 1348

CLIN 0001AB. Price for VDOT 21A complete in accordance with drawings and specifications and in accordance with the following schedule:

CLIN ITEM UNIT UNIT PRICE NO. UNITS TOTAL PRICE

0001AB VDOT 21A stone Cubic Yards $_______ 40 $__________

1.2 GENERAL BID NOTES

a. Award will be made on the total sum of of Contract Line Item prices 0001AA and 0001AB. If there is a difference between a unit price and the line item total price, the unit price will be held to be the intended bid and the total recomputed accordingly. If an Offeror provides a total but fails to enter a unit price, the total divided by the specified quantity will be held to be the intended unit price.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Document --

DOCUMENT 00 22 13.00 20 Page 1

SECTION 01 11 00

SUMMARY OF WORK

08/ 15, CHG 2: 08/ 21

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes demolition, earthwork, crusher run, chain link slide gate, 6" pvc storm water pipe, asphalt pavement, electrical work and incidental related work.

1.1.2 Location

The work is located at Naval Weapons Station Yorktown, Virginia, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.2 EXISTING WORK

In addition to FAR 52.236-9 Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements:

a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

11/11

PART 1 GENERAL

1.1 SUBMITTALS

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

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel; G

1.2 SPECIAL SCHEDULING REQUIREMENTS

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

b. Do not use radio transmitters without prior approval by Security and Safety. The Contractor must submit written requests for use of all radio transmitters. Safety will provide restrictions and procedures for their use. The Contractor can expect to receive approval for cellular phones.

c. The Contractor will be furnished with a list of fire and safety regulations pertaining to the Weapons Station and must conform to the requirements set forth at all times. In addition, there will be a strict enforcement of "No Smoking" regulations.

d. Permits for hot work must be coordinated with the the Station's Safety Office.

e. The Contractor must conduct his operations so as to cause the least possible interference with normal operations of the activity.

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 appropriate personal protective equipment (PPE)in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.

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, SECTION 01 14 00 Page 1 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 https://www.cnic.navy.mil/om/dbids.html . 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

Registration for DBIDS is available at https://www.cnic.navy.mil/Operations-and-Management/Base-Support/DBIDS/ .

Procedure includes:

a. Present 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 https://www.cnic.navy.mil/Operations-and-Management/Base-Support/DBIDS/ .

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.

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 disqualification 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

SECTION 01 14 00 Page 2

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 Installation or anyone therein.

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 installation, 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

Regular working hours must consist of an 8 1/2 hour hour period established by the Contractor Officer, Monday through Friday, excluding Government holidays.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 5 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.3.4 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, and

SECTION 01 14 00 Page 3 compressed air are considered utility cutovers pursuant to the paragraph WORK OUTSIDE REGULAR HOURS.

1.4 SECURITY REQUIREMENTS

Contract Clause FAR 52.204-2 Security Requirements and Alternate II and the following apply:

1.4.1 Naval Weapons Station, Yorktown, VA

a. Personnel information. A minimum of 5 working days prior to start of work, the Contractor will furnish to the Naval Weapons Station (NWS), Yorktown, Security Department, via the Contracting Officer, the following information for Contractor and subcontractor personnel required to enter the station:

(1) Name of company

(2) Name of the employee

(3) Social Security Number

(4) Proof of U.S. citizenship

(5) Completed Contractor/Vendor Criminal History Record Request

(6) Completed application for gate badge

b. Proof of citizenship. Proof of citizenship must consist of copies of birth certificate, military dependent identification card (ID), or naturalization papers, which will be returned once entered into the security computer system. The Security Department will run a criminal history check on Contractor employees and, as a condition of employment, each employee must willingly sign an authorization form allowing the Security Department to conduct the criminal history check. Subject authorization form must be maintained on file by the Security Officer. Based on proof of U.S. citizenship and results of the criminal history check, the Security Officer will or will not grant entry to the station. If entry is denied, the Contractor will be immediately notified.

c. Contractor responsibility for employees. The Contractor is responsible for employees under his employment. Ensure that employees are familiar with and obey station traffic, safety, and security regulations.

d. Motor vehicle operation. Ingress and egress of personnel are subject to the security regulations of the station. Motor vehicles operated within the NWS, Yorktown, must comply with the vehicle codes of Virginia which are incorporated into NWS Instruction 5510.5G, "Security and Traffic Regulations." Copies may be obtained from the Resident Officer in Charge of Construction, NWS, Yorktown, VA.

e. All Contractor construction vehicles must report to Truck Control Inspection at Gate 3, including vehicles going to Cheatham. For additional information regarding security procedures, contact the Contractng Officer.

SECTION 01 14 00 Page 4

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 5

SECTION 01 20 00.00 20

PRICE AND PAYMENT PROCEDURES

11/ 20, CHG 3: 02/ 23

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" designation.

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. Schedule of Prices must have cost summarized and totals provided for each construction category. Provide a detailed breakdown of the Contract price, giving quantities for each of the various kinds of work, unit prices and extended prices. Contractor overhead and profit including salaries for field office personnel, if applicable, must be proportionately spread over all pay items and not included as individual pay items.

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, equipment use rates must be based upon the applicable provisions of the EP 1110-1-8 .

SECTION 01 20 00.00 20 Page 1

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. The requests for payment must include the documents listed below.

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 Contractor and Quality Control (QC) Manager.

b. The Estimate for Voucher/ Contract Performance Statement on NAVFAC Form 4330/54 furnished by the Government, showing in detail: the estimated cost, percentage of completion, and value of completed performance. Use NAVFAC Form 43300/54 on NAVFAC contracts when a Monthly Estimate for Voucher is required.

c. Updated Project Schedule and reports required by the contract.

d. Contractor Safety Self Evaluation Checklist.

e. Other supporting documents as requested.

f. Updated copy of submittal register.

g. Invoices not completed in accordance with contract requirements will be returned to the Contractor for correction of the deficiencies.

1.5.2 Submission of Invoices

If DFARS Clause 5252.232-7006 is included in the contract, provide the documents listed in paragraph CONTENT OF INVOICE in their entirety as attachments in Wide Area Work Flow (WAWF) for each invoice submitted. The maximum size of each WAWF attachment is two megabytes, but there are no limits on the number of attachments. If a document cannot be attached in WAWF due to system or size restriction, provide it as instructed by the Contracting Officer.

1.5.3 Final Invoice

a. A final invoice must be accompanied by the certification required by DFARS 252.247.7023 Transportation of Supplies by Sea, and the Contractor's Final Release. If the Contractor is incorporated, the Final Release must contain the corporate seal. An officer of the corporation must sign and the corporate secretary must certify the Final Release.

b. For final invoices being submitted via WAWF, the original Contractor's Final Release Form and required certification of Transportation of Supplies by Sea must be provided directly to the respective Contracting Officer prior to submission of the final invoice. Once receipt of the original Final Release Form and required certification of Transportation of Supplies by Sea has been confirmed by the Contracting Officer, the Contractor must then submit final invoice and attach a copy of the Final Release Form and required certification of Transportation of Supplies by Sea in WAWF.

SECTION 01 20 00.00 20 Page 2

c. Final invoices not accompanied by the Contractor's Final Release and required certification of Transportation of Supplies by Sea will be considered incomplete and will be returned to the Contractor.

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.503-6 Suspension or Reduction of Payments:

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 provide up to date record drawings not current as stated in Contract Clause "FAC 5252.236-9310, Record Drawings."

1.6.2 Payment for Onsite and Offsite Materials

Progress payments may be made to the contractor for materials delivered on the site, for materials stored off construction sites, or materials that are in transit to the construction sites under the following conditions:

a. FAR 52.232-5(b) Payments Under Fixed Price Construction Contracts.

b. Materials delivered on the site but not installed, including completed preparatory work, and off-site materials to be considered for progress payment must be major high cost, long lead, special order, or specialty items, not susceptible to deterioration or physical damage in storage or in transit to the construction site. Examples of materials acceptable for payment consideration include, but are not limited to, structural steel, non-magnetic steel, non-magnetic aggregate, equipment, machinery, large pipe and fittings,precast/prestressed concrete products, plastic lumber (e.g., fender piles/curbs), and high-voltage electrical cable. Materials not acceptable for payment include consumable materials such as nails, fasteners, conduits, gypsum board, glass, insulation, and wall coverings.

c. Materials to be considered for progress payment prior to installation must be specifically and separately identified in the Contractor's estimates of work submitted for the Contracting Officer's approval in accordance with Schedule of Prices requirement of this contract.

Requests for progress payment consideration for such items must be supported by documents establishing their value and that the title

SECTION 01 20 00.00 20 Page 3 requirements of the clause at FAR 52.232-5 Payments Under Fixed-Price Construction Contracts have been met.

d. Materials are adequately insured and protected from theft and exposure.

e. Provide a written consent from the surety company with each payment request for offsite materials.

f. Materials to be considered for progress payments prior to installation must be stored either in Hawaii, Guam, Puerto Rico, or the Continental United States. Other locations are subject to written approval by the Contracting Officer.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 20 00.00 20 Page 4

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/ 20, CHG 3: 08/ 23

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 (2014) Safety and Health Requirements Manual

1.2 SUBMITTALS

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

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map; G

Progress and Completion Pictures; G

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

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

SECTION 01 30 00 Page 1

1.6 SUPERVISION

1.6.1 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.6.2 Superintendent Qualifications

The project superintendent must have 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 routine projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00.10 20 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.6.2.1 Duties

The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project.

The superintendent is required to attend NAVFAC 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.6.3 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 insure 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 for excess costs or damages by the Contractor.

1.7 PRECONSTRUCTION MEETING

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, and clear expectations of the "Interim DD Form 1354" Submittal. Major subcontractors who will engage in the work must also attend.

SECTION 01 30 00 Page 2

1.8 FACILITY TURNOVER PLANNING MEETINGS (NAVFAC Red Zone - NRZ)

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

1.8.1 NRZ Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the NRZ Checklist template prior to 75 percent completion.

b. Prior to 75 percent completion add/delete critical activities to the NRZ Checklist template as necessary to match the project scope, and schedule critical activities and insert planned completion dates in the NRZ checklist for each critical activity. Present the NRZ Checklist to COTR and review during a regularly scheduled QC Meeting.

1.8.2 Meetings

a. Upon Government acceptance of the NRZ Checklist, the Project Superintendent is required to lead regular NRZ 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 determine the frequency of the meetings, which is expected to increase as the project completion draws nearer.

c. Using the NRZ 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. Coordinate with the COTR any upcoming activities that require Government involvement.

e. Maintain the NRZ Checklist by documenting the actual completion dates as work is completed and update the NRZ Checklist with revised planned completion dates as necessary to match progress. Distribute copies of the current NRZ Checklist to attendees at each NRZ Meeting.

1.9 PARTNERING

To most effectively accomplish this contract, the Government requires the formation of a cohesive partnership within the Project Team whose members are from the Government, the Contractor and their Subcontractors. Key personnel from the Supported Command, the End User (who will occupy the facility), the Government Design and Construction team and Subject Matter Experts, the Installation, the Contractor and Subcontractors, and the Designer of Record will be invited to participate in the Partnering process. The Partnership will draw on the strength of each organization in an effort to achieve a project that is without any safety mishaps, conforms to the Contract, and stays within budget and on schedule.

The Contracting Officer will provide Information on the Partnering Process and a list of key and optional personnel who should attend the Partnering

SECTION 01 30 00 Page 3 meeting.

1.9.1 Informal Partnering

The Contracting Officer will organize the Partnering Sessions with key personnel of the project team, including Contractor personnel and Government personnel.

The Initial Partnering session should be a part of the Pre-Construction Meeting. Partnering sessions will be held at a location agreed to by the Contracting Officer and the Contractor (typically a conference room provided by the PWD FEAD/ROICC office or the Contractor). The Initial Informal Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by the Contracting Officer. The Partners will determine the frequency of the follow-on sessions, at no more than 3 to six month intervals.

1.10 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats. Multiple email addresses are not allowed.

It is the Contractor's responsibility to make timely distribution of all Contracting Officer initiated e-mail with its own organization including field office(s). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 4

SECTION 01 31 23.13 20

ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT MANAGEMENT SYSTEM

(eCMS) 08/23

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 COR or 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" classification.

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.

Provide the following information:

Company Name

SECTION 01 31 23.13 20 Page 2

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.

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.

SECTION 01 31 23.13 20 Page 3

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 APPLI CATI ON

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

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

SECTION 01 31 23.13 20 Page 4

SUBJECT/NAME REMARKS eCMS APPLI CATI ON

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

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

SECTION 01 31 23.13 20 Page 5

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

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

SECTION 01 31 23.13 20 Page 6

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

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 the government's No Cost [and][or] No Schedule impact determination, the contractor has 14 calendar days to notify the COR and Contracting Officer in writing.

SECTION 01 31 23.13 20 Page 7

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

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)

SECTION 01 31 23.13 20 Page 8

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

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.

SECTION 01 31 23.13 20 Page 9

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.

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.