Attachment L - Specifications.pdf

WORK ORDER NO. 1697737

LC-UTILITY SYSTEM SCADA

INTEGRATION

At the

JEBLCFS Little Creek – Virginia Beach, VA

DESIGNED BY:

NAVFAC MIDLANT; PWD LITTLE CREEK; FACILITIES ENGINEERING

1450 GATOR BLVD

VIRGINIA BEACH, VIRGINIA 23459-8619

SPECIFICATION PREPARED BY:

Project Manager/Mechanical: Christopher Loney, PE Design Manager/Electrical: Keith Roth, RCDD

SPECIFICATION APPROVED BY:

Lead Discipline Branch Manager: Christopher Loney, PE Project Mgmt & Engineering Director: Frances Franklin, PE

For FESC for Commander, NAVFAC:

Date:

LC-Utility Systems SCADA Integration 1697737

PROJECT TABLE OF CONTENTS

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

00 01 15 02/24 LIST OF DRAWINGS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 02/24 SUMMARY OF WORK

01 14 00 11/22, CHG 3: 08/24 WORK RESTRICTIONS

01 20 00 11/20, CHG 4: 08/24 PRICE AND PAYMENT PROCEDURES

01 30 00 11/20, CHG 4: 08/24 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 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 08/23, CHG 1: 05/24 QUALITY CONTROL

01 50 00 11/20, CHG 3: 08/24 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

01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS

01 78 23 05/23 OPERATION AND MAINTENANCE DATA

01 78 24.00 20 05/23, CHG 1: 11/23 FACILITY DATA WORKBOOK (FDW)

DI VI SI ON 26 - ELECTRI CAL

26 20 00 08/23 INTERIOR DISTRIBUTION SYSTEM

DI VI SI ON 27 - COMMUNI CATI ONS

27 10 00 08/11 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

DI VI SI ON 33 - UTI LI TI ES

33 71 02 08/21 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 04/06 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

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

DRAWING NO. NAVFAC DWG NO. TITLE

G-001 COVER SHEET

E-001 ELECTRICAL LEGEND, NOTES AND

ABBREVIATIONS

E-002 PLC MICRO-CONTROLLER SYSTEM DIAGRAM

AND SPECIFICATION

E-003 LTE RF-TRANSMITTER DIAGRAM AND

SPECIFICATION

ES100 ELECTRICAL OVERALL PLAN

ES101 PARTIAL ELEC. SITE PLAN - PS1166,

WT1553

ES102 PARTIAL ELECTRICAL SITE PLAN - PS1560A

ES103 PARTIAL ELECTRICAL SITE PLAN - SS-WEST

ES104 PARTIAL ELECTRICAL SITE PLAN - PS1501A

ES105 PARTIAL ELECTRICAL SITE PLAN -

PS1516A PS1265A

ES106 PARTIAL ELECTRICAL SITE PLAN - PS2115

ES107 PARTIAL ELECTRICAL SITE PLAN - PS2031

ES108 PARTIAL ELECTRICAL SITE PLAN - PS2063

ES109 PARTIAL ELECTRICAL SITE PLAN - PS3706

ES110 PARTIAL ELECTRICAL SITE PLAN - PS108

ES111 PARTIAL ELECTRICAL SITE PLAN - PS123

ES112 PARTIAL ELECTRICAL SITE PLAN - PS751,

WT752

ES113 PARTIAL ELECTRICAL SITE PLAN - PS751

WT752

DOCUMENT 00 01 15 Page 1

DRAWING NO. NAVFAC DWG NO. TITLE

ES114 PARTIAL ELECTRICAL SITE PLAN -

PS3708D, PS3540A

ES115 PARTIAL ELECTRICAL SITE PLAN -

PS3708D PS3540A

ES116 PARTIAL ELECTRICAL SITE PLAN - PS3879,

SS-EAST

ES117 PARTIAL ELECTRICAL SITE PLAN - PS3893

ES118 PARTIAL ELECTRICAL SITE PLAN - PS3854A

ES119 PARTIAL ELECTRICAL SITE PLAN -

PS-SDVT2-WASHRACK

ES120 PARTIAL ELECTRICAL SITE PLAN -

PS-SDVT2-WASHRACK

ES121 PARTIAL ELECTRICAL SITE PLAN - PS3852,

WT3850, PS3851

ES122 PARTIAL ELECTRICAL SITE PLAN - PS3695

ES123 PARTIAL ELECTRICAL SITE PLAN - PS3818

ES124 PARTIAL ELECTRICAL SITE PLAN - PS3186

ES125 PARTIAL ELECTRICAL SITE PLAN - PS3629,

PS-SEALHERITAGE

ES126 PARTIAL ELECTRICAL SITE PLAN - PS4174,

PS4197

ES127 PARTIAL ELECTRICAL SITE PLAN - PS3400

-- End of Document --

DOCUMENT 00 01 15 Page 2

SECTION 01 11 00

SUMMARY OF WORK

02/24

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

Salvage Plan ; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes connecting existing pump stations, water towers, and substations with fiber or LTE RF system to LP20. This includes PLC's, LTE RF systems, fiber connection enclosures, conduit/fiber, handholes, and connections required to support the SCADA network and incidental related work.

1.2.2 Location

The work is located at the JEB Little Creek , approximately as indicated.

The exact location will be shown by the Contracting Officer.

1.3 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract. Occupancy notifications will be posted in a prominent location in the work area.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.4 EXISTING WORK

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

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.

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

SECTION 01 11 00 Page 1

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

1.5.1 Notification Prior to Excavation

Notify the Contracting Officer at least 15 days prior to starting excavation work.

1.6 NAVY AND MARINE CORPS INTRANET (NMCI) COORDINATION REQUIREMENTS

1.6.1 NMCI Contractor Access

Allow the NMCI Contractor access to the facility towards the end of construction (finishes 90 percent complete, rough-in 100 percent complete, Inside Plant (ISP)/Outside Plant (OSP) infrastructure in place) to provide equipment in the telecommunications rooms and make final connections.

Coordinate efforts with the NMCI Contractor to facilitate joint use of building spaces during the final phases of construction. After the Contracting Officer has facilitated coordination meetings between the two contractors, within one week, incorporate the effort of additional coordination with the NMCI Contractor into the construction schedule to demonstrate a plan for maintaining the contract duration.

1.7 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 confines of the specific Naval Installation (Base) for which the contractor is working

Provide a salvage plan , listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Provide a system for property control in the salvage plan. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.

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/ 22, CHG 3: 08/ 24

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

List of Contact Personnel

SD-07 Certificates

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.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.2.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.2.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/Operations-and-Management/Base-Support/DBIDS/ .

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.2.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:

SECTION 01 14 00 Page 1

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

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

SECTION 01 14 00 Page 2

1.2.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.2.2 Working Hours

Regular working hours will consist of an 8 1/2 hour period established by the Contracting Officer, Monday-Friday or weekends between 7 a.m. and 3:30 p.m., , and 7 a.m. to 3:30 p.m. on Saturday , excluding Government holidays.

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 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.2.4 Occupied Building

The Contractor shall be working in an existing building which is occupied.

Relocate movable furniture approximately 6 feet away from the Contractor's working area , protect the furniture, and replace the furniture in its original locations upon completion of the work.

1.2.5 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 compressed air are considered utility cutovers pursuant to the paragraph WORK OUTSIDE REGULAR HOURS.

d. Operation of Station Utilities: The Contractor must not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer giving reasonable advance notice when such operation is required.

SECTION 01 14 00 Page 3

e. Connection to Existing Sanitary Sewer Line: Provide positive verification that the existing line conveys sanitary sewer; verify line is not incorrectly connected to a storm drain.

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 4: 08/ 24

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

Provide a detailed breakdown of the Contract price, giving quantities for each of the various kinds of work, unit prices, and extended prices.

Indirect activities (e.g., meetings, presentations, submittals, surveys, haul road or storage yard maintenance, dust control, security) will not be cost loaded. Evenly distribute the costs across the associated construction activities. 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.

Additionally, the Schedule of Prices must be separated as follows:

a. Primary Facilities Cost Breakdown:

Defined as work on the primary facilities out to the 5 foot line.

Work out to the 5 foot line includes construction encompassed within a theoretical line 5 foot from the face of exterior walls and includes attendant construction, such as pad mounted HVAC cooling equipment, cooling towers, and transformers placed beyond the 5 foot line.

SECTION 01 20 00 Page 1

b. Supporting Facilities Cost Breakdown:

Defined as site work, including incidental work, outside the 5 foot line.

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

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.

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.

SECTION 01 20 00 Page 2

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.

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.

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, 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. Provide the Contracting Officer with documentation (e.g., Purchase Orders or Material Contracts) to justify payment for materials in advance of installation. When appropriate, include the Defense

SECTION 01 20 00 Page 3

Priorities and Allocations System (DFAS) ratings (e.g., DX or DO) on purchase orders or material contracts to ensure timely delivery.

d. 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 (e.g., paid invoices) and that the title requirements of the clause at FAR 52.232-5 Payments Under Fixed-Price Construction Contracts have been met.

e. Ensure materials are adequately insured and protected from theft and exposure. Provide insurance documentation (e.g., Builder's Risk Insurance) which covers the overall value of the materials to be paid in advance of installation.

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

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

h. Materials in transit to the job site or storage site are not acceptable for payment.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 20 00 Page 4

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/ 20, CHG 4: 08/ 24

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

View Location Map

Progress and Completion Pictures

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, 1600x1200x24 bit true color minimum resolution in JPEG file format 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 different viewpoints selected by the Contractor unless otherwise directed 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. Indicate photographs demonstrating environmental procedures.

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. 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, SECTION 01 30 00 Page 1 during the entire period of performance under this contract. Provide other insurance coverage as required by State law.

1.6 SUPERVISION

1.6.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 Section 01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.6.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.6.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule 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.6.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 for excess costs or damages by the Contractor.

1.7 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

SECTION 01 30 00 Page 2 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.7.1 Attendees

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

1.8 PARTNERING

To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, NAVFAC, PWD, FEAD/ROICC, Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.8.1 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

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.

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

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

SECTION 01 31 23.13 20 Page 3 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 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

SECTION 01 31 23.13 20 Page 4

SUBJECT/NAME REMARKS eCMS APPLI CATI ON

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

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

SECTION 01 31 23.13 20 Page 5

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

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

SECTION 01 31 23.13 20 Page 6

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

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.

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

SECTION 01 31 23.13 20 Page 8

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

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