C05_03_-_J_2__Specifications__Hungry_Horse_Cavitation_Repair.pdf

U.S. Department of the Interior Bureau of Reclamation

SPECIFICATION

May 2026

Columbia Pacific Northwest Interior Region 9 Boise, Idaho

Hungry Horse Power Plant Turbine Runner Cavitation Repair

Hungry Horse Dam Hungry Horse Project, Montana

Solicitation Number: 140R1026B0003

This solicitation issued by Contracting Officer

Pacific Northwest Region Bureau of Reclamation

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

HUNGRY HORSE POWER PLANT

TURBINE RUNNER CAVITATION REPAIR

Hungry Horse Dam Hungry Horse Project, Montana

FOREWORD

Work is located at Hungry Horse Dam in Flathead County, Montana.

Principal components of work to be performed under these specifications include inspection, weld preparation, welding, and grinding.

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

STRONGLY URGED TO PARTICIPATE IN THE SITE VISIT. FAILURE BY BIDDERS

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 BID DELIVERY INFORMATION, SEE "SOLICITATION, BID, 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."

This page intentionally left blank.

Hungry Horse Power Plant Turbine Runner Cavitation Repair Solicitation No. 140R1026B0003

Price Schedule

B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND COSTS

HUNGRY HORSE POWER PLANT

TURBINE RUNNER CAVITATION REPAIR

HUNGRY HORSE PROJECT, MONTANA

B.1 PRICE SCHEDULE

(a) Bids will be considered for award on the following Price Schedules, but no bid will be considered for award on only a part of a 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.

Except as provided in the contract clause at Section H. Clause Title Variation in Estimated Quantity, no claim shall be made against the Government for overruns or underruns.

(d) See the contract clause at WBR 1452.232-81 Alt III, Payment for Mobilization and Preparatory Work, for CLIN 1 of applicable Price Schedules.

(e) Definitions:

(1) CLIN – Contract Line Item Number

B - 2

PRICE SCHEDULE A

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

A-1 WBR

1452.232 -81

G1 Mobilization and Preparatory Work

For the lump sum of $

A-2 48 13 13 G1 Welding Repair of Turbine Runner

250 pounds $ $

A-3 48 13 13 G1 Finish Grinding of Hydraulic Profile for Turbine Runner

50 hours $ $

A-4 48 13 13 G1 Removal of Turbine Runner Blade Extensions

For the lump sum of $

TOTAL FOR PRICE SCHEDULE A $__________________

B - 3

PRICE SCHEDULE B

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

B-1 WBR

1452.232 -81

G2 Mobilization and Preparatory Work

For the lump sum of $

B-2 48 13 13 G2 Welding Repair of Turbine Runner

250 pounds $ $

B-3 48 13 13 G2 Finish Grinding of Hydraulic Profile for Turbine Runner

50 hours $ $

TOTAL FOR PRICE SCHEDULE B $__________________

B - 4

PRICE SCHEDULE C

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

C-1 WBR

1452.232 -81

G3 Mobilization and Preparatory Work

For the lump sum of $

C-2 48 13 13 G3 Welding Repair of Turbine Runner

250 pounds $ $

C-3 48 13 13 G3 Finish Grinding of Hydraulic Profile for Turbine Runner

TOTAL FOR PRICE SCHEDULE C $__________________

B - 5

PRICE SCHEDULE D

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

D-1 WBR

1452.232 -81

G4 Mobilization and Preparatory Work

For the lump sum of $

D-2 48 13 13 G4 Welding Repair of Turbine Runner

250 pounds $ $

D-3 48 13 13 G4 Finish Grinding of Hydraulic Profile for Turbine Runner

TOTAL FOR PRICE SCHEDULE D $__________________

B - 6

PRICE SCHEDULE E

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

E-1 01 31 30 G1-G4 Contract Document Management System

For the lump sum of $

TOTAL FOR PRICE SCHEDULE E $__________________

END OF SECTION

Signature Sheet / Certification of Technical Specifications

Project Title: Hungry Horse Power Plant Turbine Runner Cavitation Repair

Region: Columbia Pacific Northwest Interior Region 9

Technical Specifications Project Title: Hungry Horse Power Plant Turbine Runner Cavitation Repair

Prepared by: ___________________________________ Date: _______________________

Technical Approval: _____________________________ Date: _______________________

1. The person signing the specifications package as “Prepared by” shall have developed or assembled the written specifications.

2. The person signing the specifications package for “Technical Approval” shall have been in responsible charge of the overall design including developing or assembling the specifications. This person will typically be the design team leader. In cases where the designs described by the specifications meet the criteria for preparation by a registered engineer or architect, this person shall be registered with the applicable professional designation after their signature, such as P.E. for professional engineer or R.A. for registered architect. By this signature, this person is certifying the written specifications convey the design intent as portrayed on the drawings included therein. For specifications package containing designs from multiple disciplines, it is the signing individual’s responsibility to ensure (using procedures defined by his/her organization) that the technical information prepared by other professions and disciplines and depicted in the document is compatible with the overall design intent and that the documents used to depict that information (e.g., drawings) include signatures with appropriate professional registration designations.

3. Revisions to designs after drawings and written specifications are originally signed will be reviewed by a design team representative (typically the design team leader). The review of written specifications revisions must be documented on a signature sheet included with the revised written specifications (see below).

AMD/MOD

No.

Technical Approval Signature:

Prepared By Signature:

Revised Sections:

STACEY CARLSON Digitally signed by STACEY CARLSON Date: 2026.04.30 09:54:27 -06'00'

DAVID CHRISTENSEN

Digitally signed by DAVID

CHRISTENSEN

Date: 2026.04.30 13:22:45 -06'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 at Hungry Horse Dam in Flathead County, Montana.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Inspecting turbine runner.

B. Metal removal.

C. Welding.

D. Grinding.

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

Summary of Work

01 11 00 - 2

PART 3 EXECUTION

Work by Government

01 11 16 - 1

SECTION 01 11 16

WORK BY GOVERNMENT

PART 1 GENERAL

1.01 GENERAL

A. The Government shall perform customary tasks to assist the Contractor with gaining access for the work. The Government makes no guarantee as to the condition of completed tasks. Contractor shall accept the conditions “as-is” and improve conditions as required to complete the work.

B. Prior to the start of work, Government will:

1. Drain and open unit waterway.

2. Install vane axial fan.

3. Install draft tube platform.

4. Install string of lights around the periphery of the stay ring.

C. Upon completion of the work, Government will:

1. Remove and store vane axial fan.

2. Remove and store draft tube platform.

3. Remove and store string of lights around the periphery of the stay ring.

4. Close and fill waterway in preparation for the unit to return to service.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Work by Government

01 11 16 - 2

Work Restrictions

01 14 00 - 1

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.01 WORK RESTRICTIONS

A. Perform work during Government’s scheduled maintenance outages:

1. The Government makes no guarantee as to the number of units scheduled for maintenance within a 12-month period:

a. Unit to be repaired will be issued at the Task Order Level.

b. For information only, this outage schedule is subject to change:

2. Turbines will be available for repair for a portion of the outage duration.

B. Allowable working hours:

1. Monday through Thursday, 6:30AM to 5:00PM.

C. Allowable delivery hours:

1. Monday through Thursday, 7:00AM to 3:00PM.

D. Do not exceed the safe working capacity of the elevator.

1. When necessary to move components in excess of the safe working capacity of the elevator and to floors inaccessible by elevator, Government-owned crane will be available to move components between floors using existing hatches. Provide all necessary labor and equipment to move the component to and from the existing floor hatches. Comply with requirements of Section 01 54 20 – Use of Government Crane.

PART 2 PRODUCTS

Not Used

Unit Start Date End Date Purpose

4 2/1/2027 4/15/2027 Quadrennial Maintenance

3 8/7/2028 3/1/2029 Quadrennial Maintenance and Exciter Replacement

2 8/13/2029 10/25/2029 Quadrennial Maintenance

1 8/19/2030 10/18/2030 Quadrennial Maintenance

4 2/10/2031 3/20/2031 Quadrennial Maintenance

Work Restrictions

01 14 00 - 2

PART 3 EXECUTION

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 bid in the Price Schedules for other items of work.

1.02 SUBMITTALS

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

B. RSN 01 31 19-1, Pre-Work Meeting Agenda:

1. Date and time of meeting and proposed attendees.

C. RSN 01 31 19-2, Progress Review Meeting Agenda:

1. Date and time of meeting and proposed attendees.

2. 3-week look-ahead schedule.

D. RSN 01 31 19-3, Progress Review Meeting Minutes.

1.03 COORDINATION MEETINGS

A. Pre-Work Meeting:

1. Date: At least 28 days before each mobilization:

a. Submit meeting agenda at least 7 days before meeting.

2. Location: Hungry Horse Dam.

3. Purpose: Review with Government personnel the existing condition of unit including the sequencing of work activities and technical requirements from the specifications.

4. Minimum Meeting Attendees:

a. Prime contractor.

b. Foreman or other job lead for crews who will perform welding.

c. Contractor’s quality control representative.

d. Contractor’s safety lead.

e. Third-party welding inspector.

B. Progress Review Meetings:

Project Management and Coordination

01 31 19 - 2

1. Meeting shall be held weekly at the work site project office and virtually.

2. Submit meeting agenda at least 2 days before the meeting. Include 3-week look-ahead schedule.

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

a. Project Manager from Contractor.

b. Field Superintendent from Contractor.

c. Representatives may attend by telephone or video conference.

4. Purpose:

a. Review schedule, work progress, and coordination:

1) Review meeting minutes from the previous Progress Review meeting.

2) Review status of submittals.

3) Review recently completed work forms:

a) Form B-1: Unit Summary of Runner Damage Records.

b) Form B-2: Runner Damage Record.

4) Review safety, security, environmental, technical concerns, Requests for Information (RFI), Requests for Proposals (RFP), contract modifications, and other project related items.

5. Submit meeting minutes within 24 hours after the meeting.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

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. G1-G4 Contract Document Management System:

1. Payment: lump sum price bid in the Price Schedule E.

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. Damage Records (Reclamation and Contractor generated document).

g. Contract Schedules.

h. Meeting Agendas and Meeting Minutes.

i. 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. USB flash drive of documents uploaded to CDMS.

1.04 QUALIFICATIONS

A. System provider: At least 5 years of 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. 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. 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 for the duration of the contract through 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 bid in the Price

Schedules 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 workdays with calendar days. Project calendars serve as the basis for day/date conversion and assign workdays 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 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. 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 bid 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-inch 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 Section H. Clause titled 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. Following receipt of executed task order award, incorporate activity data stipulated in task order into current schedule for inclusion in next scheduled progress update. Provide appropriate logic relationships for revised activities.

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

01 32 10 - 7

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:

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 bid in the Price Schedules for other items of work.

1.02 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

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.03 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 approval required before the Contractor proceeds with the applicable portion of the work.

b. Government will respond as to adequacy of submittal.

c. 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. Government will acknowledge receipt of Informational submittals.

b. Government may reject an Informational submittal when the submittal does not satisfy contract requirements. Correct mistakes or deficiencies in rejected Informational submittals and resubmit.

01 33 00 - 2

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

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. Government Forms:

1. Fill in all requested data on forms electronically or by hand.

2. Handwritten data on forms shall be neat and legible.

3. Forms with handwritten data shall be scanned to create high-resolution electronic files.

4. Retain all forms with handwritten data and submit complete set of hardcopies at the completion of each task order.

5. Submit complete set of electronic files on a USB flash drive at the completion of each task order.

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.

01 33 00 - 3

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.

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.

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 7 days after receiving the comments, unless otherwise directed.

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.

G. For submittals requiring Government approval, Table 01 33 00A provides:

1. Deadline for approval:

a. Submit within appropriate timeframe to meet deadline for approval.

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.

01 33 00 - 4

2. Time required for review of each submittal or resubmittal begins when complete sets of materials required for a particular RSN are received and extends through return mailing postmark date.

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

b. Requests for approval were properly and timely submitted 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 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. Approval Submittals: 1 set of submittals required for approval will be returned either 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.

01 33 00 - 5

1.07 HARD COPY TRANSMITTALS

A. Addresses for codes listed in Table 01 33 00A - List of Submittals:

1. Contracting Officer (CO), Bureau of Reclamation, Attn: CPN-7300, 1150 N.

Curtis Rd, Boise, ID 83706-1234.

2. Construction Field Manager (COR), Bureau of Reclamation:

a. Request address after task order award.

B. Send original transmittal letter with appropriate number of sets to office listed in “Responsible Code” column in Table 01 33 00A - List of Submittals.

C. Send copy of transmittal letter with appropriate number of sets to offices that are not responsible code, but show “Sets to be sent” in Table 01 33 00A - List of Submittals.

D. When “Sets to be sent” is 0, send a copy of transmittal letter to that office.

E. Submittals required by specifications, but not listed in Table 01 33 00A - List of Submittals:

1. Submit in accordance with this section.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 33 00 - 6

Table 01 33 00A - List of Submittals

* Submittal Types: A - Approval, I – Information ** Y indicates Yes, the submittal is required to be shown on the Schedule – see Section 01 32 10 – Construction Program *** CO indicates Contracting Officer, COR indicates Contracting Officer Representative, and CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required Deadlines Type

CP

Respon-sible code

Sets to be sent: ***

CO COR

I-1 Release of Claims (1452.204-70)

Release of claims (DI-137) against the United States

Submitted after completion of work and prior to final payment

I CO

1 0

I-2 Payrolls and Basic Records (52.222-8)

Certified payrolls Submitted weekly for each week any contract work is performed

I COR CDMS

I-3 Subcontracts (Labor Standards) (52.222-11)

1) List of subcontractors

2) Statement and Acknowledgement Form (SF-1413) for each subcontract

Submitted within 14 days after task order award, and within 14 days after any subcontract award

I COR 1 0

I-4 Equal Opportunity (52.222-26)

Information required by Executive Order

11246 (SF-100)

Submitted within 28 days following task order award

I COR 1 0

I-5 Bonds (52.228-15)

Performance and payment bonds

Approval required before starting on-site work

Submitted within 10 calendar days after task order award

A CO 1 0

I-6 Liability Insurance (1452.228-70)

Acceptable evidence showing that insurance has been obtained

Approval required before starting on-site work

Submitted within 10 calendar days after task order award

A CO 1 0

I-7 Security Requirements

(WBR

1452.237-80)

Security Program Approval required before starting on-site work

Submitted within 7 days after the task order work starts or another period approved by the Contracting Officer

A COR CDMS

01 33 00 - 7

Table 01 33 00A - List of Submittals

* Submittal Types: A - Approval, I – Information ** Y indicates Yes, the submittal is required to be shown on the Schedule – see Section 01 32 10 – Construction Program *** CO indicates Contracting Officer, COR indicates Contracting Officer Representative, and CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Respon-sible code

Sets to be sent: ***

CO COR

I-8 Security Requirements

(WBR

1452.237-80)

List of onsite employees

Submitted within 7 days after the task order work starts or another period determined by the Contracting Officer

I COR CDMS

01 31 19-1 Project Management and Coordination

Pre-Work Meeting Agenda

Approval required 28 days before mobilization

Submit within appropriate timeframe to meet deadline for approval

A Y COR CDMS

01 31 19-2 Project Management and Coordination

Progress Review Meeting Agenda

Submitted at least 2 days before the meeting

I COR CDMS

01 31 19-3 Project Management and Coordination

Progress Review Meeting Minutes

Submitted within 24 hours after the meeting

I COR CDMS

01 31 30-1 Contract Document Management System

Approval Data Approval required before starting other work

Submitted within 7 days after task order NTP

A COR 0 1

01 31 30-2 Contract Document Management System

Final Data Approval required before contract closeout

Submitted within 14 days of completion of work

A COR CDMS

01 32 10-1 Construction Program

Representative Information

Approval required before mobilization

Submitted within 10 days after task order

NTP

01 33 00 - 8

Table 01 33 00A - List of Submittals

* Submittal Types: A - Approval, I – Information ** Y indicates Yes, the submittal is required to be shown on the Schedule – see Section 01 32 10 – Construction Program *** CO indicates Contracting Officer, COR indicates Contracting Officer Representative, and CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Respon-sible code

Sets to be sent: ***

CO COR

01 32 10-2 Construction Program

Baseline Schedule Approval required before mobilization

Submitted within 10 days after task order

A Y COR CDMS

01 32 10-3 Construction Program

Updated Schedule Reports

Submitted and approved monthly, with progress payments, and within 14 days after award of a task order

01 32 10-4 Construction Program

Time Impact Analysis

Approval required to request a time extension

Submitted within 28 days after the CO directs a contract change with schedule impacts

Or

With proposal for future modification, value engineering proposal, or request or claim for equitable adjustment to the contract when time is requested

01 35 20-1 Safety and Health

Safety Program Approval required 28 days before mobilization

Submitted within 28 days after task order

NTP

A Y COR CDMS

01 35 20-2 Safety and Health

Job Hazard Analysis List

Approval required 28 days before mobilization

Submitted within 28 days after task order

01 33 00 - 9

Table 01 33 00A - List of Submittals

* Submittal Types: A - Approval, I – Information ** Y indicates Yes, the submittal is required to be shown on the Schedule – see Section 01 32 10 – Construction Program *** CO indicates Contracting Officer, COR indicates…