J_5_Specs_(_206_pages).pdf

U.S. Department of the Interior SPECIFICATIONS Bureau of Reclamation March 2026 Columbia Pacific Northwest Interior Region 9 Boise, Idaho

Speelyi Beach Shoreline Final Specification

Cle Elum Dam and Reservoir, Yakima Project, Washington

Solicitation Number: 140R1026B0002

This solicitation issued by Contracting Officer

Pacific Northwest Region Bureau of Reclamation

1150 North Curtis Road, Suite 100 Boise ID 83706-1234

SPEELYI BEACH SHORELINE PROTECTION

YAKIMA RIVER BASIN WATER ENHANCEMENT PROJECT - INTEGRATED PLAN

YAKIMA PROJECT - WASHINGTON

FOREWORD

Work is located on Cle Elum Reservoir, approximately 8 miles northwest of Cle Elum, Washington, in Kittitas County. Work is located near the Speelyi Beach Day Use Area. Work is constructing shoreline protection along the edge of the reservoir. Principal components of the work include earthwork, clearing and grubbing, removal and hauling of trees, construction of a temporary access road, trench excavation, installation of geotextile fabric, culvert installation, site grading, riprap placement, selective demolition of structures, in-kind replacement of a fence, and removal of the temporary access road upon completion.

SITE VISIT: SEE SECTION L FOR SITE VISIT INFORMATION. OFFERORS ARE

STRONGLY URGED TO PARTICIPATE IN THE SITE VISIT. FAILURE BY

OFFERORS TO INSPECT THE SITE WILL NOT RELIEVE THEM OF THE

RESPONSIBILITY OF PROPERLY ESTIMATING THE DIFFICULTY OR COST OF

SUCCESSFULLY PERFORMING THE WORK IN ACCORDANCE WITH THE

SPECIFICATIONS AND WITHIN THE ALLOWED TIME. ATTENDEES ARE TO

PROVIDE AND WEAR SAFETY GLASSES, BOOTS, HARD HATS, SAFETY VESTS.

FOR PROPOSAL DELIVERY INFORMATION, SEE "SOLICITATION, OFFER, AND

AWARD," STANDARD FORM 1442.

FOR INFORMATION REGARDING BUREAU OF RECLAMATION'S PUBLICATION

"RECLAMATION SAFETY AND HEALTH STANDARDS" INCLUDING REVISIONS

AT https://www.usbr.gov/safety/rshs/index.html WHICH IS APPLICABLE TO WORK

UNDER THIS CONTRACT, SEE CLAUSE AT "WBR 1452.223-81 SAFETY AND

HEALTH."

END OF SECTION

This page intentionally left blank.

Speelyi Beach Shoreline Protection Cle Elum Dam and Reservoir, Yakima Project Solicitation No. 140R1026B0002

Price Schedule

B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND PRICES

CLE ELUM DAM AND RESERVOIR

SPEELYI BEACH SHORELINE STABILIZATION

YAKIMA PROJECT, WASHINGTON

B.1 PRICE SCHEDULE

(a) Bids will be considered for award on the following Price Schedule, but no bid will be considered for award on only a part of the Price Schedule.

(b) Bids are subject to the terms and conditions of this solicitation.

(c) Quantities in the Price Schedule are estimated quantities for comparison of bids only.

(d) See the contract clause at WBR 1452.232-81, Payment for Mobilization and Preparatory Work, for CLIN 1.

(e) Definitions:

(1) CLIN – Contract Line Item Number

PRICE SCHEDULE

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

1 WBR

1452.232 -81

Mobilization and Preparatory Work

For the lump sum of $

2 02 41 13 Selective Demolition For the lump sum of $

3 13 00 10 Log Structures For the lump sum of $

4 31 11 00 Clearing and Grubbing For the lump sum of $

5 31 23 11 Earthwork For the lump sum of $

6 31 37 00 Riprap For the lump sum of $

7 32 14 40 Stone Paths For the lump sum of $

8 32 92 20 Seeding and Soil Supplements

For the lump sum of $

B - 2

PRICE SCHEDULE

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

9 33 42 30 CMP Culvert For the lump sum of

TOTAL FOR PRICE SCHEDULE $_________________

B.2 OPTIONAL PRICE SCHEDULE A

(a) The Government reserves the right to award or not award Optional Price Schedule A.

(b) The Optional Price Schedule A items are for work as shown on the Drawings within the boundary marking “Optional Site A” site work.

(c) Quantities in the Price Schedule are estimated quantities for comparison of bids only.

(d) See the contract clause at WBR 1452.232-81, Payment for Mobilization and Preparatory Work, for CLIN 1.

(e) The Optional Price Schedule A may be exercised at any point during the Contract period of performance.

B - 3

OPTIONAL PRICE SCHEDULE A

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

1A 02 41 13 Selective Demolition For the lump sum of $

2A 31 11 00 Clearing and Grubbing For the lump sum of $

3A 31 23 11 Earthwork For the lump sum of $

4A 31 37 00 Riprap For the lump sum of $

5A 32 31 29 Wood Fence 60 LF $ $

6A 32 92 20 Seeding and Soil Supplements

For the lump sum of $

7A 33 42 30 CMP Culvert For the lump sum of $

TOTAL FOR OPTIONAL PRICE SCHEDULE A $_________________

GRAND TOTAL FOR PRICE SCHEDULE AND OPTIONAL PRICE SCHEDULE A

END OF SUPPLIES OR SERVICES AND PRICES

COLUMBIA-CASCADES AREA OFFICE

WRITTEN SPECIFICATIONS SIGNATURE SHEET

Specifications No:

Specifications Title: SPEELYI BEACH SHORELINE PROTECTION

Project Title: CLE ELUM POOL RAISE: SPEELYI BEACH SHORELINE PROTECTION

Region: PACIFIC NORTHWEST

Prepared:

Technical Approval: P.E.

AMD/MOD

No.

Technical Approval Signature:

Prepared By Signature:

Revised Specifications

STACEY CARLSON

Digitally signed by STACEY

CARLSON

Date: 2026.02.10 10:40:30 -07'00'

MATTHEW

DEAMICO

Digitally signed by

MATTHEW DEAMICO

Date: 2026.02.24 15:14:34 -08'00'

DIVISION 01 - GENERAL REQUIREMENTS

Summary of Work

01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located on Cle Elum Reservoir, approximately 8 miles northwest of Cle Elum, Washington, in Kittitas County.

B. Work is located near the Speelyi Beach Day Use Area.

1.02 WORK HOURS

A. Allowable work hours: 7:00 am and 6:30 pm Monday through Friday, excluding Federal holidays, unless otherwise noted.

B. Work hours are subject to Industrial Fire Precaution Levels (IFPL). More information can be found at https://www.dnr.wa.gov/ifpl

C. Work outside of allowable work hours and/or holidays shall be approved by the COR in writing a minimum of 72-hours in advance.

D. Material deliveries 7 a.m. to 6:30 p.m, Monday through Friday. Material deliveries outside of allowable hours shall be approved by the COR in writing a minimum of 72-hours in advance.

1.03 PRINCIPAL COMPONENTS OF WORK

A. The work to be performed consists of the following:

1. Water for Dust Control.

2. Construction Access Road. Temporary Erosion Control.

3. Selective Demolition (As shown in the Price Schedule’s).

4. Stone Paths (As shown in the Price Schedule).

5. Clearing and Grubbing for staging areas and slopes to receive riprap (As shown in the Price Schedule’s).

6. Tree Removal.

7. Excavation and reshaping hillside. Common Fill.

8. Beach Fill.

9. Toe Armor.

10. Geotextile.

01 11 00 - 2

11. Riprap (As shown in the Price Schedule’s).

12. Bedding Layer, CMP Culvert culvert installation and site grading (As shown in the Price Schedule’s).

13. Wood Fence (Optional Price Schedule A).

14. Seeding and Soil Supplements (As shown in the Price Schedule’s).

15. Log Structures (Price Schedule).

16. Removal of the Construction Access Road upon completion (Price Schedule).

1.04 SPECIFICATIONS REQUIREMENTS

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

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

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

1.05 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.06 ACRONYMS

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

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

1.07 SEQUENCE OF THE WORK

A. Portions of the work require construction below the high-water line. Perform all work in the dry. Refer to Section 51 10 20 – Historic Water Elevations for data on the water level fluctuations of Cle Elum Reservoir.

1.08 SITE MEASUREMENTS

A. All measurements provided in this Scope of Work are approximate and for reference only. The Contractor shall be responsible for verifying all measurements before starting work, and providing all materials required to meet the shoreline protection extent shown in the Drawings.

01 11 00 - 3

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

01 11 00 - 4

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedule for other items of work.

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (USBR)

1. Cleaning Manual Inspection and Cleaning Manual for

Equipment and Vehicles to Prevent the Spread of Invasive Species 2021 Edition Available online at:

http://www.usbr.gov/mussels/prevention

1.03 SUBMITTALS

A. Submit 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; fire hydrants; and compressor station.

4) First-aid and medical facilities.

5) Aggregate processing. Show sizes, rated capacities, and general features of aggregate processing plant including transporting, storing, screening, and washing facilities; and concrete conveying, placing, and cooling plants.

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

7) Temporary fences.

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 and contractor use areas, 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 preserve and protect infrastructure within the contractor use areas that cannot be removed or altered.

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

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

3. Do not use the existing concrete boat ramp for vehicle access to the work site unless approved by the COR.

a. Construct temporary culverts/stream crossing structures at stream crossings or cross-drainage channels to allow for unimpeded surface drainage.

b. The concrete boat ramp may be used as approved by the COR for initial mobilization of equipment to start construction of the temporary access road, and for final demobilization once the temporary access road is removed.

c. The Contractor shall construct an access road starting adjacent to the boat ramp as shown on the Drawings, without disturbing existing log revetments that are constructed near the north end of the boat ramp.

d. Existing riprap at the boat ramp area shall be stockpiled and replaced at the end of construction, with the site returned to its pre-construction condition.

C. RSN 01 14 10-2, Private Property Access Request:

1. Shall notify the COR a minimum of two weeks in advance for access to private property.

a. Type of work to be performed:

1) Culvert work and grading.

1.04 PROJECT CONDITIONS

A. All Contractor Use Areas are on Government land as shown on drawings and may be used for required construction facilities except where noted otherwise.

B. No additional trees cutting or clearing and grubbing shall occur outside of the disturbed area as shown in drawings.

Use of Site 01 14 10 - 3

C. The Government will have written permissions obtained for use of private land for construction facilities or other construction purposes as shown on the Drawings, which will be shared with the Contractor as necessary.

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

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

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

G. All work shall be performed when the reservoir pool elevation is consistently at or below Elevation 2220, a condition that typically occurs from September 1 through April 1.

H. The boat ramp and day use area will be open to the public during construction.

I. The Contractor shall make a written request to the US Forest Service Cle Elum Ranger District to close the site for public safety if necessary. The request shall be approved by the US Forest Service Cle Elum Ranger District in writing a minimum of 72 hours in advance.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 CLEANING

A. Construction equipment:

1. Before bringing on site, clean construction equipment 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 or better than the procedures described in Cleaning Manual.

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

3.02 RESTORATION

A. Upon completion of the work, the Contractor shall restore all areas used for construction activities to pre-construction condition, including temporary access roads, haul routes, and staging areas.

01 14 10 - 4

B. Restore temporary construction roads to original contours and make impassable to vehicular traffic when no longer required

C. 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 proper drainage, and prevent erosion.

1. Restore any borrow pits after use. All ruts and depressions within the borrow pit shall be filled and slopes within the borrow area shall be no steeper than 5:1 and shall slope towards the reservoir.

D. Seed disturbed areas of Government land used for construction purposes and not required for completed installation in accordance with Section 32 92 20 - Seeding and Soil Supplements. with species of native plants, or other approved perennial species, as recommended by an experienced local horticulturist.

3.03 TEMPORARY ROADWAYS AND PARKING AREAS

A. Between February 28 to July 16 in any calendar year, temporary road crossings shall consist of a steel plate, log corduroy, or similar structure placed to fully span the wetted perimeter of the stream channel.

B. Between July 16 and February 28, in any calendar year, temporary road crossing culverts may be installed and shall be of sufficient size to pass flow and debris occurring during the project and allow crossing to be isolated from the flowing stream..

Project Management and Coordination 01 31 19 - 1

SECTION 01 31 19

PROJECT MANAGEMENT AND COORDINATION

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedule for other items of work.

1.02 SUBMITTALS

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

B. RSN 01 31 19-1, Progress Review Meeting Agenda and Minutes:

1. Includes the following:

a. Meeting shall be held weekly at the work site project office.

b. Prepare agenda and distribute 24 hours before the meeting.

c. Prepare and distribute meeting minutes within 24 hours of each meeting.

d. 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) Field Superintendent from Contractor.

3) COR and other Representatives from Bureau of Reclamation.

4) United States Fish and Wildlife Service staff and others identified by the COR.

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

e. 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), Invitation for Bid (IFB), pending Contract Modifications, and other project related items.

Project Management and Coordination 01 31 19 - 2

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.

1.03 PROJECT COORDINATION

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

1. Progress Review Meetings:

a. Meeting shall be held weekly at the work site project office.

Prepareagenda and distribute 24 hours before the meeting.

b. Contractor to provide virtual call-in option via Microsoft Teams.

c. Prepare and distribute meeting minutes.

d. Attendees: Responsible representatives who have been fully informed ofspecifications with respect to technical requirements, and coordinationnecessary to complete construction. Representatives shall be determinedon an as needed basis and typically should include:

1) Project Manager from Contractor.

2) Field Superintendent from Contractor.

3) COR and other Representatives from Bureau of Reclamation.

4) Representatives may attend by telephone and / or videoconference.

e. Purpose:

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

a) Review submittals register, submittals currently in reviewand approval, and meeting submittals due dates or deliverytime frames.

b) Review safety, security, environmental, schedule, projectissues and concerns, submittals, contractor Requests forInformation (RFI), Invitations for Bid (IFB), pendingContract Modifications, and other project related items.

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

d) Review as-built drawings.

e) Provide meeting minutes from the previous weeklymeeting.

Project Management and Coordination

01 31 19 - 3

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Project Management and Coordination

01 31 19 - 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. Cost:

1. Include cost of Contract Document Management System in the lump sum price offered in the Price Schedule for Mobilization and Preparatory Work.

1.02 DEFINITIONS

A. CDMS: Contract Document Management System.

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

a. Submittals.

b. DIRs: Daily Inspection Reports

c. RFCs: Request for Change (Contractor generated document).

d. RFIs: Request for Information (Contractor generated document).

e. Bureau of Reclamation (Reclamation) Inspection Reports.

f. Contract Schedules.

g. Meeting Agendas and Meeting Minutes.

h. Letters and Memos.

1.03 SUBMITTALS

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

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

1. Documentation of system capabilities.

2. Instructions for system use.

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

1. DVD or CD of documents uploaded to CDMS.

1.04 QUALIFICATIONS

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

01 31 30 - 2

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 Microsoft Edge, Apple Safari, Mozilla Firefox, and Google Chrome.

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

a. Portable Document Format (.pdf).

b. MS Word.

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

f. Drawing (.dwg).

g. Contract Manager.

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

a. Preparing organization will 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 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 will 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.).

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

01 31 30 - 3

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

6. Ability to link files; examples:

a. Submittal linked to a Specification or Drawing.

C. Reports:

1. CDMS shall generate reports that list and sort documents by status; examples:

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. CM Processing Turn-Around.

d. Total CM costs.

e. Total CM Request Exposure.

4. Printable, exportable as searchable .pdf or printer -friendly HTML, and exportable to Excel, XML, or CSV.

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

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 to FTP site of documents to which an organization has access on a regular (minimum monthly) basis.

01 31 30 - 4

4. Documents shall be downloadable to FTP sites 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, RFI, 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:

a. Required information includes:

1) Required submittal number (RSN), title, description, and specification section.

b. Upload submittal data in electronic format.

3. Track date received, date response due, date returned, and status:

a. Status designations may be modified to fit Government standard designations – Approved, approved subject to identified changes, or not approved.

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

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

G. RFI Tracking and Control:

1. Supply standard RFI form to enter information.

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.

01 31 30 - 5

H. Inspection Reports Tracking and Control:

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

a. Daily Inspection Report (DIR).

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. Cost Tracking and Payment Request Management:

1. Ability to import payment bid items cost from MS Excel spreadsheets.

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.

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

2. Ability to generate responses to letters and memos:

a. 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 Reclamation to Contractor shall contain Reclamation's official letterhead and corresponding logos.

4. Ability to generate meeting agendas and meeting minutes and to attach documents to the minutes:

a. CDMS shall automatically assign sequential meeting numbers.

K. Miscellaneous Tracking and Controls:

1. Ability to generate logs tracking RFIs, CORs, COs, Submittals, 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 (approved, partially approved, approved subject to identified changes and resubmit, or not approved.); for RFI's: 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.

01 31 30 - 6

4. Ability to provide forms to match Reclamation'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 for keyword search of documents in database.

8. Ability to allow online Payment Requests (electronic invoicing) by Contractor.

PART 2 PRODUCTS

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

PART 3 EXECUTION

3.01 IMPLEMENTATION

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

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 the 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 (approved, partially approved, approved subject to identified changes and resubmit, or not approved.)

7. Days in Review.

8. Due Date.

01 31 30 - 7

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

Schedule 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, 2015

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 experience and training certificates meeting qualifications.

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. Primavera file extension (.xer)

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

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

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

h. 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. In accordance with subparagraph (a)(i)(A) of the clause at FAR 52.232-27 - Prompt Payment for Construction Contracts, Government disapproval of this submittal will be considered failure of the Contractor to comply with contract requirements and payment due date may be delayed until 14 days after submittal contents are approved.

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. Primavera file extension (.xer)

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

f. Narrative report specifically stating status of project.

01 32 10 - 3

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

g. 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. Primavera file extension (.xer)

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

f. 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. Experience shall include scheduling for at least two other projects of comparable complexity and Primavera P6 training offered by certified instructors.

01 32 10 - 4

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.

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. Schedule activities to occur as early as possible without unwarranted constraints.

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

8. Reference activities to contract line item number (CLIN) and specification section identified in the Schedule using user-defined fields.

9. 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) shall not be subject to workday duration limitation.

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

01 32 10 - 5 specified in Section 01 33 00 - Submittals. Include Required Submittal Number (RSN) in activity description.

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

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

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

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

15. Use finish to start logic relationships between activities. Do not utilize start to start, finish to finish, or start to finish logic relationships. Start to start logic may be utilized on start milestones and finish to finish logic may be utilized on finish milestones only. Do not use positive or negative lead or lag times.

16. Use durations in units of whole workdays.

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

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

19. 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, by remote meeting, 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.

01 32 10 - 6

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.

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 shall 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. Prepare a single time impact analysis for modifications issued after Notice to Proceed (NTP) and prior to approval update.

E. 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 manufacture schedules, material orders, construction seasons, and labor and equipment utilization.

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

1) Activity description.

01 32 10 - 7

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:

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

4. The COR will schedule pre-submittal meeting with the Contractor’s representative each month to review draft updated schedule prior to the Contractor submitting RSN 01 32 10-3, Updated Schedule.

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.

01 32 10 - 8

1.10 FAILURE TO COMPLY

A. Failure to comply with requirements of this Section shall be grounds for determination by the CO that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within specified time.

B. The CO may terminate the Contractor’s right to proceed with the work, or separable part of it, in accordance with default terms of this contract.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Submittals

01 33 00 - 1

SECTION 01 33 00

SUBMITTALS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedule 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 - Approval:

a. Government will respond as to adequacy of submittal.

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

2. I - Informational:

a. The Government will acknowledge receipt of Informational submittals.

b. The Government may reject an Informational submittal when the submittal does not comply with the contract. The Contractor shall correct mistakes or deficiencies in rejected Informational submittals and resubmit as an Approval type submittal for Government approval.

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.

D. Drawings: As used in this Section, means ‘shop drawings’ as defined in Clause FAR 52.236-21, Specifications and Drawings for Construction, excluding incidental device or component drawings intended as, or a part of, the manufacturer’s technical catalog data.

E. CDMS: Construction Document Management System.

1.03 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

01 33 00 - 2

1. ASME Y14.1-12 Decimal-inch Drawing Sheet Size and Format

B. National Institute of Building Sciences (NIBS)

1. NIBS NCS-14 United States National CAD Standards, 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 or supplier’s title and drawing number.

c. Date.

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

3. Print Size: D size (22 inches by 34 inches) as defined by 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.

b. Electronic file format: Compatible with AUTOCAD, Version 2018 or better, or as approved by the COR. Compile using “eTransmit” utility in AUTOCAD.Drawing prepared with drafting equipment, when allowed:

Lettering shall be neat.

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

01 33 00 - 3

d. Electronic files: On CD or DVD discs.

D. Product Data:

1. Mark manufacturer's data for commercial products or equipment, such as catalog cut sheets.

a. Identify manufacturer's name, type, model, size, and characteristics.

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

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

d. Strike through items that do not apply.

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 on CD or DVD discs.

1) Bookmark longer files to assist in navigating files.

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.

d. Schematics and wiring diagrams.

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

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

G. Photographs:

1. When requested.

2. Each COR requested view.

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

01 33 00 - 4

3. Format:

a. Digital Photographs on CD, DVD, or SDHC card in jpeg format. Ten

Megapixels minimum. With accompanied prints if requested and of a size requested by the COR.

b. Prints only: Only if specifically requested.

1) Professional quality 8-inch by 10-inch color for each listed view.

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

1. Label with complete manufacturer's product 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.

4. Label each sample with contract number and title

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 all listed items for RSNs with multiple parts.

C. Submit sets specified in “Sets to be sent:” column in Table 01 33 00A – List of Submittals.

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

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.

01 33 00 - 5

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 within 28 days after…