Attachment_1_Specifications.pdf

U.S. Department of the Interior December 2025

Warren H. Brock Reservoir Gates Replacement

Colorado River Front Work and Levee System Project, California

Lower Colorado Basin Region

Solicitation No.

100% Specifications

This page intentionally left blank.

Warren H. Brock Reservoir Gates Replacement Colorado River Front Work and Levee System Project, California Solicitation No.

Price Schedule B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

WARREN H. BROCK RESERVOIR

GATES REPLACEMENT

COLORADO RIVER FRONT WORK AND LEVEE SYSTEM PROJECT, CALIFORNIA

B.1 PRICE SCHEDULE

See Section B of Solicitation for Contract Price Schedule

Price Schedule B - 2

END OF SUPPLIES OR SERVICES AND COSTS

Table of Contents

00 01 10 - 1

SECTION C - DESCRIPTION / SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 – GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 14 00 Work Restrictions 01 14 10 Use of Site 01 14 30 Interruption of Service 01 31 22 Coordination Meetings 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 26 Electrical Drawings and Data 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 30 Contractor’s Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 46 20 Testing Agency Services 01 51 00 Temporary Utilities 01 55 00 Vehicular Access and Parking 01 56 10 Protection of Existing Installations 01 56 15 Protection of Existing Utilities 01 56 32 Temporary Safety Fence 01 57 20 Environmental Controls 01 57 30 Water Pollution Control 01 60 00 Product Requirements 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents 01 79 20 Training

DIVISION 02 – EXISTING CONDITIONS

02 80 10 General Requirements for Hazardous Materials Abatement 02 83 35 Removal and Disposal of Coatings and Equipment with Coatings Containing

Regulated Metals

DIVISION 03 – CONCRETE

03 20 30 Post-Installed Adhesive Anchors 03 62 20 Nonshrink Grout for Equipment and Metalwork 03 81 10 Concrete Removal

00 01 10 - 2

DIVISION 05 – METALS

05 50 00 Metal Fabrications

DIVISION 09 – FINISHES

09 96 20 Coatings

DIVISION 26 – ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 10 Conductors and Cables 26 05 20 Grounding and Bonding 26 05 30 Raceways, Conduit, and Boxes for Electrical Systems 26 05 90 Wiring Checkout and Tests 26 24 20 Panelboards 26 32 10 Engine-Generator Set 26 36 23 Automatic Transfer Switch 26 42 00 Cathodic Protection General Requirements 26 42 13 Submerged Galvanic Anode Cathodic Protection 26 42 14 Submerged Impressed Current Cathodic Protection 26 51 00 Interior Lighting 26 56 00 Exterior Lighting

DIVISION 28 – ELECTRONIC SAFETY AND SECURITY

28 21 01 Surveillance System

DIVISION 31 – EARTHWORK

31 03 10 Control of Water

DIVISION 33 – UTILITIES

33 09 16 Water Level Measuring Devices

DIVISION 35 – WATERWAY AND MARINE CONSTRUCTION

35 23 11 Slide Gates and Actuators

DIVISION 51 – INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 50 Electronic Media Release 51 00 74 Waste Diversion Table 51 00 90 Photographs 51 02 83 Hazardous Materials Survey and Analytical Results

00 01 10 - 3

DIVISION 52 – DRAWINGS

52 00 00 Drawings

END OF CONTENTS

00 01 10 - 4

Summary of Work

01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located approximately 28 miles east of Calexico, California in Imperial County on the north side of Interstate Highway 8 (I-8). The reservoir site’s latitude and longitude coordinates are approximately 32 degrees 42 minutes 58 seconds north by 115 degrees 2 minutes 8 seconds west (32.7161, -115.0356).

1.02 PRINCIPAL COMPONENTS OF WORK

A. Overview: Work includes replacing 11 slide gates and associated improvements.

B. Replace six 10-foot by 10-foot and two 10-foot by 7-foot cast iron slide gates with new stainless steel gates, including gear boxes, actuators, stem protection, and associated components:

1. Media-blast and recoat existing cast-iron thimbles.

2. Install conduit from the Control Building to each gate.

3. Provide new power wiring from the Control Building to each gate.

4. Connect new gates’ actuators to existing facility control system.

5. Stop log guides.

C. Install new cathodic protection system and conduct functionality test.

D. Install new electrical conduit, conductors, grounding equipment, and associated electrical equipment.

E. Remove and Replace:

1. Three existing level instruments, including radar-type downward facing sensors.

2. Existing exterior sodium light fixtures with LED light fixtures.

3. One existing security camera.

4. One existing 150 kW diesel power generator.

5. Automatic transfer switch.

1.03 SPECIFICATIONS REQUIREMENTS

A. Requirements in Division 1, General Requirements, apply to Divisions 2 through 52.

Summary of Work

01 11 00 - 2

B. Imperative statements in these specifications are Contractor requirements unless otherwise stated.

C. Where specifications are written in streamlined form, the words “shall be” are included by inference where a colon (:) is used within a sentence or phrase.

1.04 DEFINITIONS

A. When specifications use a word or term defined in Federal Acquisition Regulations (FAR), definition of the word or term shall be in accordance with FAR sections in effect at the time solicitation was issued.

1.05 ACRONYMS

A. The following acronyms apply to specifications Divisions 1 through 52:

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Work Restrictions

01 14 00 - 1

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedules for other items of work.

1.02 DEFINITIONS

A. Outage: Reclamation unwatering the facility, including water on both sides of each gate to be replaced.

1.03 WORK RESTRICTIONS

A. Reclamation will perform an Outage from November 1, 2026 to February 28, 2027:

1. If work needs to be completed outside of the outage window, then Cell 2 gates shall be completed before Cell 1 gates.

a. Facility will allow 50 percent use of Brock outside of outage window.

b. March through May 2027 for Cell 2.

c. May through July 2027 for Cell 1.

B. Allowable Work Hours: Monday through Saturday, 24 hours, 6 days a week, excluding Federal holidays, unless otherwise noted:

1. Comply with additional work hour restrictions listed in other sections.

2. Additional work hours shall be requested in writing at least 7 days in advance of need and approved by the CO.

3. Additional shifts shall be requested in writing at least 21 days in advance of need and approved by the CO.

C. Contractor shall maintain public use of roadways throughout the area and shall maintain access to and from the facility during construction.

1.04 ACCESS CONTROL

A. Restrict entrance of personnel and vehicles into project site and existing facilities

B. Coordinate access of Government personnel to jobsite.

C. Maintain continuous log of workmen and visitors and make available to COR upon request.

Work Restrictions

01 14 00 - 2

PART 2 PRODUCTS

PART 3 EXECUTION

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedules for other items of work.

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (Reclamation)

1. Cleaning Manual-2021 Inspection and Cleaning Manual for

Equipment and Vehicles to Prevent the Spread of Invasive Species (Technical memorandum No. 86-68220-07-05), available online at https://www.usbr.gov/mussels/prevention

1.03 SUBMITTALS

A. In accordance with Section 01 33 00 - Submittals.

B. RSN 01 14 10-1, Land Use and Landscape Rehabilitation Plan:

1. For each Contractor use site on Government land.

a. Show use location and extent of impact. Uses include but are not limited to the following:

1) Buildings and service areas including offices, shops, warehouses, storage areas, fuel and oil storage areas, and fabrication yards.

2) Parking areas, temporary roads, and haul routes.

3) Utilities including air, power, and water lines.

4) First-aid and medical facilities.

5) Areas for processing, storing, and disposing of waste materials from construction operations.

6) Temporary fences.

7) Access roads and gates.

8) Staging areas.

9) Proposed extents of clearing, grubbing, and stripping.

10) Measures to secure work area.

01 14 10 - 2

b. Describe methods to preserve, protect, and repair vegetation (such as trees, shrubs, and grass) and other landscape features on or adjacent to jobsite, which are not to be removed and which do not interfere with work required under this contract. Include methods to mark work area limits, protect disturbed areas, and prevent erosion.

c. Describe methods to protect, and repair if damaged, existing improvements and utilities at or near jobsite.

d. Describe methods for removing temporary structures and facilities, cleanup, and rehabilitating site after completion of construction activities.

2. Submit revised drawings of changes in use of Government land made during design and erection stages or after use of Government land is in operation.

1.04 PROJECT CONDITIONS

A. Government land consisting of access roadways adjacent to the reservoir may be used for required construction facilities. Contractor shall propose specific areas for equipment storage and laydown of materials.

B. Only refuel in designated areas shown on drawing 423-D-60238.

C. When private land is used for construction facilities or other construction purposes, make necessary arrangements associated with use of private land.

D. Location, construction, operation, maintenance, and removal of construction facilities on Government land will be subject to approval of COR.

E. Restrict construction equipment to not exceed the following vehicle loading:

1. Front axle loading: 46.4 kip

2. Rear axle loading: 52 kip

3. If a crane is used that requires outriggers, the outrigger loading shall not exceed

90.5 kip on 460-in2 pad, spaced at 24 feet.

a. Outriggers shall not be placed on Pipe Inlet Structure concrete structure.

4. If construction equipment exceeds these loadings, submit proposed equipment loadings for approval.

F. Do not interfere with work of other contractors or the Government in vicinity, or with reservations made by the Government for use of such land.

G. Housing for construction personnel will not be permitted on Government land, except housing for guards or watchmen as may be approved by COR.

01 14 10 - 3

PART 3 EXECUTION

3.01 CLEANING

A. Construction Equipment:

1. Before bringing onsite, clean construction equipment and temporary facilities in accordance with this section to remove dirt, vegetation, and other organic material to prevent introduction of noxious weeds, and invasive plant and animal species.

2. Contractor cleaning procedures shall result in equipment being cleaned as well as or better than the procedures described in Cleaning Manual.

3. COR will inspect construction equipment and temporary facilities following procedures described in Cleaning Manual before allowing equipment onsite.

3.02 RESTORATION

A. Restore Contractor use areas to pre-construction condition.

B. After completion of work, regrade and scarify Government land used for construction purposes and not required for completed installation so that surfaces blend with natural terrain and are in a condition that will facilitate revegetation, provide adequate drainage, and prevent erosion.

01 14 10 - 4

Interruption of Service

01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedule for items of work for which interruption of services are required.

1.02 SUBMITTALS

A. In accordance with Section 01 33 00 – Submittals.

B. RSN 01 14 30-1, Interruption of Service Request:

1. Area where work will be done (by number or other description).

2. Outline procedures for accomplishing work including:

a. Specific safety precautions to be taken.

b. Type and location of barricades.

c. Warning signs.

d. Protective grounds and devices to be used.

3. Commencement time of work.

4. Duration of work.

5. Number of personnel and their classification.

6. Description of equipment to be used.

7. Information indicating that required materials are on site or data indicating shipping dates of materials not on site.

C. RSN 01 14 30-2, Interruption of Service Notification:

1. For individual component, equipment, panel, or similar as approved by the COR.

2. Documentation of COR approval a minimum of 14 business days prior to the interruption of service.

3. Commencement time of work.

4. Duration of work.

Interruption of Service

01 14 30 - 2

1.03 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with COR:

1. Coordinate work with Government operations.

2. No specific interruption of service request will be considered unless:

a. COR has reasonable assurance that materials and equipment required for work will be onsite.

b. Contractor will be prepared to perform work on date and during period of time requested for specific interruption of service.

3. Allowable time and available interruption of service periods will govern interruption of service requests, work scheduling, onsite delivery of materials, and required drawings and data submittals.

4. Interruption of service scheduling will depend upon water demand requirements and related operating conditions:

a. Interruption of services may be scheduled outside of the 4 month outage window.

b. Government reserves right to schedule interruption of services for any period during 24-hour day, any day of week.

c. Contractor will be informed of type of interruption of services available and restrictions prior to start of construction.

B. Notify COR that interruption of service is not required when work cannot be performed during an approved interruption of service period.

PART 3 EXECUTION

Coordination Meetings

01 31 22 - 1

SECTION 01 31 22

COORDINATION MEETINGS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedules for other items of work.

1.02 SUBMITTALS

A. In accordance with Section 01 33 00 - Submittals.

B. RSN 01 31 22-1, Weekly Construction Coordination Meeting Agenda and Minutes:

1. Meeting agenda and meeting minutes from the previous weekly meeting.

2. 3-week look-ahead schedule.

3. Work completed to date.

4. Meeting minutes from the previous weekly coordination meeting to include:

a. Date, time, and attendees.

b. Summary of topics discussed.

c. List of action items including:

1) Description of action item.

2) Responsible party.

3) Date to be completed.

1.03 SPECIFICATION DRAWINGS

A. AutoCAD files of drawings are available to Contractor. With at least 14 days’ notice, Government will make these files available to Contractor.

1.04 COORDINATION MEETINGS

A. The following meetings are considered significant but do not relieve the Contractor from the responsibility of other meetings required by the specifications:

1. Preconstruction Meeting:

a. Date: No more than 14 days after Notice of award. Notify Government of meeting date at least 10 days before meeting.

b. Location: Yuma Area Office, 7301 Calle Agua Salada, Yuma, AZ 85364.

c. Purpose: Review with Government personnel drawings, data, and technical requirements of specifications.

01 31 22 - 2

d. Attendees: Responsible representatives who understand these specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete work. Representatives shall include:

1) Contractor: 1.

2) Mechanical subcontractor, if applicable: 1.

3) Electrical subcontractor, if applicable: 1.

e. Some Government personnel may attend virtually via Microsoft Teams.

2. Progress Review Meetings:

a. Meeting shall be held weekly at the work site project office as well as virtually via Microsoft Teams or Government-approved equal. Prepare agenda and distribute 24 hours before the meeting.

b. Prepare and distribute meeting minutes.

c. Attendees: Responsible representatives who have been fully informed of specifications with respect to technical requirements, and coordination necessary to complete construction. Representatives shall be determined on an as needed basis and typically should include:

1) Project manager from Contractor.

2) Safety representative from Contractor.

3) Field superintendent from Contractor.

4) COR and other Government representatives.

5) Representatives may attend by telephone or by video conference.

d. Purpose:

1) Review, schedule, construction progress, and coordination:

a) Review submittals register, submittals currently in review and approval, and meeting submittals due dates or delivery time frames.

b) Review safety, security, environmental, schedule, project issues and concerns, submittals, Contractor Requests for Information (RFI), Requests for Proposal (RFP), pending contract modifications, and other project related items.

c) Provide 3-week look-ahead schedule at least 2 hours before start of meeting.

d) Review as-built drawings.

e) Provide meeting minutes from the previous weekly meeting.

01 31 22 - 3

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 31 22 - 4

Contract Document Management System

01 31 30 - 1

SECTION 01 31 30

CONTRACT DOCUMENT MANAGEMENT SYSTEM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Contract Document Management System:

1. Payment: Lump-sum price offered in Price Schedule A.

1.02 DEFINITIONS

A. Contract Document Management System (CDMS):

1. Contract Documents include, but are not limited to:

a. Specifications.

b. Contract Drawings.

c. Submittals.

d. RFCs: Request for Change (Contractor-generated document).

e. RFIs: Request for Information (Contractor-generated document).

f. RFPs: Request for Proposal (Government-generated document).

g. CMs: Contract Modifications.

h. Contractor Proposals.

i. Value Engineering Proposals.

j. Government Inspection Reports.

k. Invoices and Progress Payments.

l. Contract Schedules.

m. Meeting Agendas and Meeting Minutes.

n. Letters and Memos.

1.03 SUBMITTALS

A. In accordance with Section 01 33 00 - Submittals.

B. RSN 01 31 30-1, Approval Data:

1. System provider experience, number of systems operating, references.

2. Documentation of system capabilities.

3. Instructions for system use.

01 31 30 - 2

C. RSN 01 31 30-2, Final Data:

1. Documents uploaded to CDMS in an electronic format approved by COR.

1.04 QUALIFICATIONS

A. System Provider: At least 5 years successful performance in providing required services.

1.05 CDMS REQUIREMENTS

A. CDMS shall be capable of generating, storing, tracking, categorizing, and managing Contract Documents.

B. Access:

1. Web-based:

a. Contract Documents are stored and accessed by authorized individuals via an internet site.

b. Compatible with web browsers Apple Safari, Google Chrome, Microsoft Edge, and Mozilla Firefox.

2. Ability to upload Contract Documents and make available for user download in supported file formats, minimum:

a. Autodesk AutoCAD (.dwg).

b. Microsoft Word.

c. Microsoft Excel.

d. Microsoft Project.

e. Oracle Primavera P6 Project Manager.

f. Portable Document Format (.pdf).

3. Allow Contract Documents to be prepared by Contractor or by Government.

a. Preparing organization shall control access of documents. See Document

Security and Backup paragraph below.

4. Contractor and Government shall each have a project manager for CDMS.

a. Each project manager shall have capabilities to assign users within their organization and to assign user rights that control access to documents based on user class and document type.

b. Each organization shall be capable of defining its access hierarchy.

c. Inclusion of users shall be prerogative of organizational project manager.

d. Government shall be able to create and modify project properties (i.e.

Contractor, project location, description, bid amount, project directory, etc.).

01 31 30 - 3

5. Email notifications shall be automatically sent to selectable users when new documents are submitted and available for viewing, or alerts are generated.

Examples:

a. Updates to project information (e.g., entry of a new submittal).

b. Changes to project information (e.g., approval of a submittal).

c. Alerts (e.g., submittal under review for greater than 15 days without action).

6. Ability to link files; examples:

a. RFP linked to a submittal.

b. Submittal linked to a specification or drawing.

C. Reports:

1. Generate reports that list and sort documents by status, examples include:

a. Submittals that have been approved.

b. Invoices paid to date.

c. RFIs under review.

2. Generate alerts when documents requiring action approach or exceed allowable time.

3. Generate customizable summary reports, examples include:

a. Submittal Turn-Around.

b. RFI Turn-Around.

c. RFP Processing Turn-Around.

d. Total RFP Request Exposure.

4. Printable, exportable as searchable pdf or printer friendly HTML, and exportable to Excel, .xml, or .csv formats.

5. Ability to link from an item in a report directly to the item by clicking on it:

a. For example: In a submittal report, clicking on a submittal that is 15 days old takes the user directly to information on that submittal.

6. Capable of producing a complete and logically organized set of documents within

CDMS in both .pdf and .xml format.

D. Document Security and Backup:

1. SSL encryption for secured data exchange between browser and server (secure access to documents and information).

2. Allow document access security until authoring party chooses to share it with others.

a. Show parties that have access to a document.

01 31 30 - 4

b. Extent of document sharing shall be determined by authoring party.

c. Once documents are shared, track documents so that changes cannot occur without a record of changes.

3. Backup/Archiving of documents to which an organization has access on a regular

(minimum monthly) basis.

4. Documents shall be downloadable where Government and other organizations can each access their own data confidentially.

E. General Tracking and Control:

1. Documents shall be grouped into categories (Submittals, RFC, RFI, RFP, CM, Payments, Daily Inspection Reports, and Meeting Minutes).

2. CDMS shall track:

a. When documents were received or returned, as well as status of documents (e.g. Under Review; or Returned, Approved or Rejected, etc.).

b. Document changes including who entered or changed document and date change was made.

c. When a reviewer has opened an item.

F. Submittal Tracking and Control:

1. Ability to create master list of submittals (“Schedule of Submittals”).

2. Customizable standard submittal form for entering information. Required information includes required submittal number (RSN), title, description, and specification section.

3. Upload submittal data in electronic format.

4. Track date received, date response due, date returned, and status. Status designations may be modified to fit Government standard designations - A/AAN/PAR/NA/ACK (Approved/Approved As Noted/Partially Approved - Resubmit/Not Approved/Acknowledged).

5. Supply Submittal Tracking form for Government to enter review comments and action taken. Allow customizing of submittal tracking form.

a. Allow for Government to route submittal to third parties (e.g., consultant, internal design or operations and maintenance groups, etc.) by generating design-review transmittals with each submittal package item, to track status of individual sub-items within submittal package, and to route each sub-item to the appropriate reviewers.

6. Ability to generate automatic notification after specified days without response.

G. RFI Tracking and Control:

1. Supply standard RFI form to enter information.

01 31 30 - 5

2. Ability to create or attach documents to the RFI form or links to other documents within CDMS.

3. Ability for Government to route RFI to appropriate reviewers and for reviewers to enter comments into standard response form.

H. Inspection Reports Tracking and Control:

1. Ability to attach Government standard inspection and report forms into CDMS and ability to create customizable inspection forms in CDMS. Typical forms:

a. Daily Inspection Report.

b. Survey requests.

c. Plant inspection reports.

d. Testing reports.

2. Ability to link or attach photos to forms and link forms to other documents within

CDMS.

I. Contract Modifications:

1. Supply standard Contractor Proposal form with ability to attach documents and link to other documents within CDMS.

2. Supply ability to upload Government’s standard CM form and RFP forms, or create an acceptable alternative, to enter information.

3. Ability to attach documents to these forms, and link to other documents within

CDMS.

4. Ability for Contractor to respond to RFP and CM form with Cost & Time impacts.

5. Ability to track date CM issued and date responded, with automatic notification after specified days without response.

J. Cost Tracking and Payment Request Management:

1. Ability to import payment bid items cost from a Microsoft Excel spreadsheet.

2. Ability to edit percent complete and payment amount each month. Format to be spreadsheet, e.g. items available for editing at once, rather than needing to edit one item at a time, save, open next item and edit that, etc.

K. Correspondence:

1. Ability to generate letters and memos.

a. Ability to attach documents to letters and memos, and to reference other documents within CDMS.

b. Ability to automatically assign sequential numbers to letters and memos.

01 31 30 - 6

2. Ability to generate responses to letters and memos. System automatically generates memo suffixes; e.g., 1st response to Memo 32 to be 32.1, 2nd response to be 32.2, etc.

3. Official correspondence from Government to Contractor shall contain Government’s official letterhead and corresponding logos.

4. Ability to generate meeting agendas and meeting minutes and to attach documents the minutes. CDMS shall automatically assign sequential meeting numbers.

L. Miscellaneous Tracking and Controls:

1. Ability to generate reports tracking RFCs, RFIs, RFPs, CMs, submittals, payments, memos, DIRs, survey requests, plant inspection reports and testing reports.

2. Ability to filter logs based on criteria, e.g., for submittals: Specification Section, Days Out, Status (A/AAN/R&R/ ACK/RWR); for RFIs: Days Out, Status (Open/Closed), Specification Section/Dwg No., and Responsibility/Ball-In-Court.

3. Ability to sort logs based on a criterion, e.g., for Submittal, Specification Section, Days Out, Status, or other criteria determined by COR.

4. Ability to supply forms to match Government’s CM Form and Progress Payment Form or other forms when needed.

5. Ability to track Cost Exposure with links to RFI and CM requests.

6. Ability to measure productivity benchmarks on a project such as computing average review days for RFIs and submittals, categorize CMs, and track total CM percentages by category.

7. Ability to keyword search of documents in database.

8. Allow online Payment Requests by Contractor.

M. Budget and Funding Source Tracking: Ability to enter funding sources and assign contract line items to multiple funding sources.

PART 2 PRODUCTS

2.01 GENERAL

A. Commercially available products having the essential characteristics of Parts 1 and 3.

PART 3 EXECUTION

3.01 IMPLEMENTATION

A. CDMS shall be in place and operating before Contractor transmits Contract Documents to Government, except RSN 01 31 30-1, Approval Data.

01 31 30 - 7

1. CDMS operation includes COR, or other authorized Government representative, having program control to assign users and user rights to Government personnel to access appropriate areas of system.

B. Contractor shall input entries to the Schedule of Submittals before making submittals.

Include:

1. RSNs listed in Table 01 33 00A - List of Submittals.

2. Scheduled submittal date.

C. Contractor shall provide a report of submittal status monthly or as requested by COR.

Submittal status report shall be in a table format and include:

1. Required Submittal Number (RSN).

2. Section Title.

3. Submittal Title.

4. Date Submitted.

5. Date of Response.

6. Approval Status (A/AAN/PAR/NA/ACK).

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

01 31 30 - 8

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

1. Developing Baseline Schedule: Include in lump sum price offered in Price

Schedule A for Mobilization and Preparatory Work.

2. Updating and Using Construction Program: Include as part of Contractor’s overhead.

1.02 DEFINITIONS

A. Schedule: The Critical Path Method (CPM) of planning and scheduling a construction project where activities are arranged based on activity relationships and network calculations determine when activities can be performed and the critical path of the project.

B. Project Calendar(s): Cross reference of numerical work days with calendar days. Project calendars serve as the basis for day/date conversion and assign work days and non-workdays.

C. Resources: Equipment, labor or crews, materials, subcontractors, fabricators, manufacturers, and consultants.

D. Out of Sequence Work: An activity that starts before its predecessor activities are completed.

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling

Manual, 2004

1.04 SUBMITTALS

A. Submit the following in accordance with Section 01 33 00 - Submittals.

1. Furnish database files in format compatible with Oracle Primavera P6

Professional Project Management.

2. Upon request, provide information and data used to develop and maintain the

Construction Program to the CO.

01 32 10 - 2

B. RSN 01 32 10-1, Representative Information:

1. Designation of authorized representative to develop and maintain Construction

Program. Include resume with training and experience.

C. RSN 01 32 10-2, Baseline Schedule:

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Primavera layout file (.plf).

d. Gantt chart (Bar chart) for project on 11 by 17-inch print(s) and in portable document format (.pdf).

e. Activity report including logic constraints consisting of predecessors, successors, and constraint dates.

f. Tabular listings of resources and resource limitations used to produce baseline schedule. Correlate resources with schedule assumptions and offered price. Resource listings may be independent of schedule database.

g. Narrative explanation of project schedule development. Include impacts of resource limitations and weather conditions on project schedule development. Include planned number of work hours per day and hours per day for subcontractors.

D. RSN 01 32 10-3, Updated Schedule Reports:

1. This submittal is required for a proper invoice for progress payments in accordance with the clauses at FAR 52.232-27 - Prompt Payment for Construction Contracts and invoice requirements.

2. Include:

a. Construction Program database with updated activity and milestone data.

b. Definition of project calendars if revised from baseline calendars.

c. Primavera layout file (.plf).

d. Gantt chart for project on 11 by 17-inch print(s) and in portable document format (.pdf).

e. Narrative report specifically stating status of project.

1) When negative float exists, cite specific actions and conditions which caused "behind schedule" condition and provide proposed course of action to complete the project within the specified delivery time. When float changed from previous month’s updated schedule, explain reason for change.

2) List of Contractor-initiated changes to current schedule stating reason for action taken and unresolved issues relating to the

01 32 10 - 3

Construction Program. Government reserves the right to reject Contractor-initiated changes to current schedule which negatively impact Government action which was initiated on the basis of current schedule.

3) Discuss contract milestones and significant activities that were started, continued, or completed during the update period or scheduled during the next update period.

f. Submittal Register:

1) List submittals as listed in Table 01 33 00A.

2) Update Submittal Register monthly to include submittals and revised submittals. Register fields shall include RSN name and number, date submitted, date of response, status (e.g., approved, not approved, resubmittal required).

3) This register document is separate from scheduling database.

E. RSN 01 32 10-4, Time Impact Analysis:

1. Include:

a. Construction Program database with proposed revised activity and milestone data.

b. Proposed revised schedule due to change or delay. Highlight or list added, changed, or deleted activities.

c. Primavera layout file (.plf).

d. Gantt chart for project on 11 by 17-inch print(s) and in portable document format (.pdf).

e. Narrative report explaining results and conclusions.

1.05 QUALIFICATIONS

A. Representative: Experienced in developing and maintaining construction schedules and knowledgeable of activities and progress on-site to develop and maintain accurate and reliable schedules.

1.06 GENERAL

A. Develop, maintain, and use Construction Program to plan, monitor, evaluate, and report accomplishment of work.

1.07 SCHEDULES

A. Prepare construction schedules using Critical Path Method outlined in AGC Manual. Use a computer software program to perform mathematical analysis of scheduling data.

01 32 10 - 4

1. Prepare schedule based on required sequence and interdependence of activities.

Logically sequence activities.

2. Prepare detailed activity network for accomplishing required work organized by Work Breakdown Structure (WBS). Utilize WBS in lieu of activity codes for organization of schedule. If activity codes are utilized in addition to WBS, use unique activity code names assigned as project codes rather than global codes.

3. Activities except “Award” shall have predecessor activities and activities except “Contract Complete” shall have successor activities.

4. Meet contract requirements; milestone(s) in accordance with the clause at FAR 52.211-10, Commencement, Prosecution, and Completion of Work; and relevant clauses and specification sections. Include interim milestone dates, Government interface dates, contract completion date, and other time or seasonal constraints specified in contract documents.

5. Include work of subcontractors, Government interfaces, and contract milestones.

6. Adjust Construction Program/schedule for seasonal weather conditions. Provide a narrative explaining the expected weather and plan for incorporation in schedule.

Consider work influenced by high or low ambient temperatures or precipitation.

Utilize Primavera P6 calendars to depict historical weather days that impact work.

Assign weather calendars to work impacted by weather.

7. Define activities to level of detail resulting in their durations being no greater than 20 workdays.

a. Durations for administrative activities (e.g., submittals and reviews) fabrication, manufacturing, and typical level of effort activities (e.g., dewatering, storm water management) will not be subject to workday duration limitation.

8. Include separate activities for submittal preparation and submittal reviews when submittal addresses work that involves significant quantities, long lead times, is on the critical path or near critical path, or as requested by the COR. Assign Government submittal review activities to a seven-day calendar with durations as specified in Section 01 33 00 - Submittals. Include Required Submittal Number (RSN) in activity description.

9. Include separate activities for fabrication or manufacturing when work involves significant quantities, long lead times, is on the critical path or near critical path, or as requested by the COR

10. Include contract title, contract number, and Contractor’s name on transmittal cover sheet and each sheet of Gantt chart.

11. For each activity on Gantt chart, display activity identification number, activity description, planned or original duration, start date, finish date, total float, and calendar identification. Do not display early start and late start fields.

12. Include table of abbreviations used in the schedule, listed and defined alphabetically.

01 32 10 - 5

13. Use finish to start logic relationships between activities. Do not utilize start to start, finish to finish, or start to finish logic relationships. Do not use negative lead or lag times.

14. Use durations in units of whole workdays.

15. Provide best estimate of time required to complete activity considering quantity of work, work conditions, location of work, and planned resources for activity.

16. Equate durations of Government reviews and other identified actions to maximum number of calendar days specified in their respective paragraphs.

17. Establish workday calendar(s) and use these in the schedule to translate activity's workday duration into calendar dates. Use unique calendar names; do not use software default calendar names. Save calendars as project calendars, not global calendars.

B. Baseline Schedule:

1. Represents Contractor’s as-planned approach to accomplishing the work. Do not include actual start dates, percent completes, or actual finish dates.

C. Updated Schedule:

1. Meet monthly with COR at Government’s project office, or at a location approved by the COR, to review progress made to end date of progress payment period.

Establish dates that activities were started and completed and remaining duration for each activity started but not completed during the period.

a. Discuss and mutually agree upon changes to the schedule.

b. Out-of-sequence activities are not allowed. Revise logic to reflect change in work plan.

c. Finalize updated Construction Program database with mutually agreed upon changes.

2. Following receipt of executed contract modification, incorporate activity data stipulated in modification into current schedule for inclusion in next scheduled progress update. Provide appropriate logic relationships for revised activities.

3. Assign a unique project file name for each schedule update.

1.08 TIME IMPACT ANALYSIS

A. Provide time impact analysis for contract changes (e.g., change order, proposed modification, or value engineering change proposal) to support a claim or request for equitable adjustment to the contract due to delay or accelerated schedule.

B. The CO may use time impact analysis to determine if time extension or reduction to contract milestone dates is justified.

01 32 10 - 6

1. Time impact analysis is required for contract changes whether the Contractor’s current schedule milestone dates are the same as, earlier than, or later than, those required under the contract.

2. Changes, additions, or deletions to activities; activity durations; activity time frames; or activity predecessors and successors will not automatically determine that extension or reduction of contract time is warranted or due the Contractor.

3. Time extensions for performance will be considered only to the extent that the Contractor’s current scheduled milestone dates exceed contract milestone dates.

C. Float is not for exclusive use by or benefit of either the Government or the Contractor.

D. Perform time impact analyses using data in most recent approved schedule update prior to change or delay event.

1. Prepare proposed revised schedule and narrative description describing and highlighting changes or delays.

2. Prepare summary comparing results of two schedule analyses: One using current schedule data from last approved updated schedule prior to event requiring analysis, and one using proposed schedule data incorporating changes or delays.

a. Show contract milestones and activities whose periods of performance have shifted as result of change which affects production and/or manufacture schedules, material orders, construction seasons, and labor and/or equipment utilization.

b. For activities directly affected by change or delay, include the current and proposed items:

1) Activity description.

2) Types and quantities of major pieces of equipment, principal manpower, and pacing materials (materials that affect activity start, duration, or finish).

3) Activity duration.

4) Narrative containing rationale used in developing the proposed logic relationships and activity data.

c. Data date for impacted schedule used in comparison shall be the same as approved updated schedule data date.

d. Base schedule comparisons on status of work and available float at time the CO directs or proposes change to the work, the Contractor submits a value engineering change proposal, or when a delay occurs as shown in approved updated schedule.

1.09 REVIEW AND EVALUATION

A. Baseline Schedule:

1. Within 21 calendar days after receipt of baseline schedule:

01 32 10 - 7

a. CO will approve or not approve proposed baseline schedule.

b. Upon request from the CO, meet with COR for a joint review of proposed baseline schedule.

c. If schedule is not approved, revise and resubmit within 7 calendar days following date of rejection letter.

2. Do not proceed with onsite work, except mobilization and surveying, until baseline schedule has been approved by the Government.

B. Updated schedules:

1. Submit updated Construction Program schedule monthly.

2. Submit updated schedule at least seven days prior to the submission of each invoice request for progress payment.

3. If updated schedule is not approved, revise and resubmit updated schedule within

7 calendar days following date of rejection letter.

C. Failure to include elements of the work in schedules will not release Contractor from completing required work under the contract.

D. Performance will be evaluated by the Government using approved CPM schedules.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 32 10 - 8

Submittals

01 33 00 - 1

SECTION 01 33 00

SUBMITTALS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedules for other items of work.

1.02 DEFINITIONS

A. Days: Calendar days.

B. Required Submittal Number (RSN): Identifies items to be submitted together as a complete submittal.

C. Submittal Types, as listed in Table 01 33 00A - List of Submittals:

1. A - Action:

a. Government will respond as to adequacy of submittal.

b. Action Submittals: Considered “shop drawings” within the terms of the clause at FAR 52.236-21, Specifications and Drawings for Construction.

2. I - Informational:

a. Government will acknowledge receipt of Informational submittals.

b. Government may reject an Informational submittal when the submittal does not comply with the contract requirements. Contractor shall correct mistakes or deficiencies in rejected Informational submittals and resubmit.

c. Informational Submittals: Considered “shop drawings” within the terms of the clause at FAR 52.236-21, Specifications and Drawings for Construction, except that approval by the Government is not required.

1.03 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

1. ASME Y14.1-20 Drawing Sheet Size and Format

B. Bureau of Reclamation (Reclamation)

1. RSHS Reclamation Safety and Health Standards, including revisions, available at https://www.usbr.gov/safety/rshs/index.html

01 33 00 - 2

C. National Institute of Building Sciences (NIBS)

1. NIBS NCS-14 United States National CAD Standard, Version 6

1.04 SUBMITTAL REQUIREMENTS

A. In case of conflict between requirements of this section and requirements included elsewhere in these specifications, requirements included elsewhere take precedence.

B. General:

1. Prepare in English.

2. Label with contract number and title, and RSN.

3. Measurement Units: US Customary Units.

4. Provide a unique transmittal number for each submittal.

C. Drawings:

1. Minimum Identification in Title Block:

a. Contract number and title.

b. Contractor’s or supplier’s title and drawing number.

c. Date.

2. Reserve 3- by 3-inch space next to title block for review stamps.

3. Size: ANSI D size (22 inches by 34 inches) in accordance with ASME Y14.1.

4. Draw to scale using computer drafting or drafting equipment, unless otherwise specified.

a. Computer drafted drawings:

1) In accordance with NIBS NCS.

2) Electronic file format: Compatible with AutoCAD Version 2023 or later.

3) Compile using “eTransmit” utility in AutoCAD.

b. Drawing prepared with drafting equipment, when allowed: Lettering shall be neat.

5. Drawings Designated as “Government Format” in Specifications:

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

c. Title block and sheet format:

1) As shown on Standard Drawing 40-D-7102.

2) Government will provide template.

01 33 00 - 3

3) Government will provide specific title block information to be used.

6. Final Drawings:

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

c. Show as-built changes, including revision dates, made during installation.

Indicate changes by clouding.

7. Electronic Files: On CDMS.

D. Product Data:

1. Mark manufacturer’s data for commercial products or equipment, such as catalog cut sheets, to be used:

a. Identify manufacturer’s name, type, model, size, materials of construction, and characteristics.

b. Instructions for delivery, storage, handling, and installation.

c. Illustrate that product or equipment meets requirements of specifications.

d. Mark items to be furnished in a manner that will photocopy (no highlighter).

e. Strike through items that do not apply.

f. Warranty.

E. Certifications:

1. Certifications by a Registered Professional: Signed and sealed by registered professional.

2. Manufacturer’s Certifications: Signed by authorized representative of manufacturer.

F. Manuals:

1. Copies:

a. Printed copies: Bound and indexed.

b. Electronic copies: Adobe pdf. Bookmark longer files to assist in navigating file.

2. Contents:

a. Parts identification lists, lists of special tools, and accessories.

b. Schematics and wiring diagrams.

c. Detailed instructions for installing, operating, lubricating, and maintaining equipment.

01 33 00 - 4

d. As-built drawings, photographs, and test records or reports if required by the specifications.

G. Photographs:

1. Include contract number, name of equipment, and view title.

2. Format:

a. Digital photographs in .jpeg format. Four megapixels minimum. With accompanied prints if requested and of a size acceptable to the COR.

b. Prints only if specifically requested:

1) Professional quality 8- by 10-inch color.

2) Identify with adhesive labels on back:

a) Include contract number, name of equipment, and view title.

b) Do not type directly on back of photograph.

H. Samples and Color Selection Submittals:

1. Label with complete manufacturer’s product and color identification.

2. Include type and quantity of materials specified in the referenced section in each

“set” of samples.

3. Samples: Representative of product to be installed. Xerographic sheets for color selection are not acceptable.

4. Color Chips: Sample paint chips. Ink color reproductions are not acceptable.

5. Label each sample, sample kit, set of color chips, or color chart with contract number and title.

6. Government will select architectural color and pattern after product approval.

1.05 SUBMITTALS PROCEDURES

A. Submit only checked submittals. Submittals without evidence of Contractor’s approval will be returned for resubmission.

B. Submit complete sets of required materials for each RSN as specified in “Submittals Required” column in Table 01 33 00A - List of Submittals. A complete set includes listed items for RSNs with multiple parts.

C. Submit sets specified in “Sets to be sent:” columns in Table 01 33 00A - List of Submittals. Submittals identified with “CDMS” in the “Sets to be sent” column shall be submitted electronically in accordance with Section 01 31 30 - Contract Document Management System.

01 33 00 - 5

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals not approved:

1. Mark changes such that they are readily identifiable and show revision date.

2. Describe reasons for significant changes in transmittal letter.

3. Resubmit returned submittals no later than 21 days after receiving the comments.

4. Requirements for initial submittals apply to resubmittals.

F. More than one RSN may be submitted under a transmittal letter provided responsible code is same.

1.06 REVIEW OF SUBMITTALS

A. Time Required:

1. Submittal review will require 28 days for review of each submittal or resubmittal, unless otherwise specified.

2. Time required for review of each submittal or resubmittal begins when complete sets of materials required for a particular RSN are received.

B. Time in Excess of Specified:

1. CO may extend contract completion date to allow additional time for completing work affected by excess review time:

a. Time extension will be to extent that excess review time caused delay to contract completion date.

b. Time extension will not exceed time used in excess of specified number of days for review of submittals or resubmittals.

c. Concurrent days of excess review time resulting from review of two or more separate submittals or resubmittals will be counted only once in extending contract completion date.

2. No time extension will be allowed if Contractor fails to make complete action submittals in sequence and within time periods specified.

3. Adjustment for delay will be made only to the extent that:

a. Approval was required under the contract, and, 01 33 00 - 6

b. Requests for approval were submitted as required, submitted in a timely fashion, and were approved.

4. Adjustment will be subject to terms of paragraphs (b) and (c) of clause at FAR 52.242-14, Suspension of Work, however, no such delay shall be deemed to be a “suspension order” as the term is used in that clause.

C. Return of Submittals:

1. Return of submittals will be by CDMS response or hard copy, as applicable.

2. Action Submittals: Will be returned as approved, approved with comments, or not approved.

a. Revise and resubmit submittals not approved.

b. Do not change designs without approval of CO after drawings, documentation, and technical data have been approved.

3. Informational Submittals: Government will acknowledge Informational submittals.

a. Informational submittals will not be returned when they satisfy contract requirements.

b. Informational submittals that do not satisfy contract requirements may be returned for resubmittal or additional information may be requested.

PART 2 PRODUCTS

Not Used

P…