GC_Crane_Specification_final_0003.pdf

U.S. Department of the Interior JUNE 2023

Glen Canyon Powerplant Powerplant Cranes Modernization Middle River Division – Glen Canyon Unit – Arizona – Utah Colorado River Storage Project, Arizona Upper Colorado – Basin: Interior Region 7

This page intentionally left blank.

GLEN CANYON POWERPLANT

POWERPLANT CRANES MODERNIZATION

COLORADO RIVER STORAGE PROJECT

FOREWORD

Work is located at Glen Canyon Power Plant, approximately 3 miles northwest of Page, Arizona in Coconino County.

A. Principal Components of Work:

1. 300 Ton Capacity Bridge Cranes:

a. Remove and Dispose Existing Equipment:

1) Motors, reduction gearboxes and drives shafts for main and auxiliary hoists, trolleys, and bridge drive systems.

2) All control equipment from crane control cabinet enclosures.

3) Wiring, conductor and collector systems.

4) Equipment enclosures.

5) Operator’s cab and cab controls.

6) Hoist ropes.

7) Main fuse disconnect switch.

b. Furnish and Install New Equipment:

1) Motors, reduction gearboxes and drives shafts for main and auxiliary hoists, trolleys, and bridge drive systems.

2) Variable frequency drive (VFD) controls for all hoists, trolleys, and bridge drives.

3) Cross-bridge cable festoon systems for trolleys.

4) Operators cab and cab controls.

5) Grounding and bonding conductors and other miscellaneous equipment required to complete electrical installation.

6) Equipment enclosures.

7) Hoist ropes.

c. Non-destructive (visual) examination of bridge crane components.

d. Draining, cleaning and re-lubricating bridge crane components.

e. Perform load tests for lifting devices.

f. Perform load tests, and operation and maintenance training.

g. Main fuse disconnect switch.

Glen Canyon Powerplant Cranes Modernization Middle River Division – Glen Canyon Unit – Arizona – Utah Colorado River Storage Project Specification No.

Price Schedule B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND PRICES

GLEN CANYON POWERPLANT

POWERPLANT CRANES MODERNIZATION

COLORADO RIVER STORAGE PROJECT

B.1 PRICE SCHEDULE

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

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

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

(d) 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 01 31 30 Contract Document Management System

For the lump sum of $

3 02 82 20 East Bridge Crane, Removal and Disposal of Asbestos Containing Materials

For the lump sum of $

4 02 82 20 West Bridge Crane, Removal and Disposal of Asbestos Containing Materials

For the lump sum of $

5 26 05 10 Conductors and Cables For the lump sum of $

6 26 05 30 Raceways, Conduit, and Boxes for Electrical Systems

For the lump sum of $

Colorado River Storage Project Specification No.

Price Schedule B - 2

PRICE SCHEDULE

CLIN Section Supplies or Services Quantity and Unit

Unit Price

Amount

7 41 22 14 East Bridge Crane Control Upgrade and Modernization

For the lump sum of $

8 41 22 14 West Bridge Crane Control Upgrade and Modernization

For the lump sum of $

9 41 22 14 East Bridge Crane Load Testing

For the lump sum of $

10 41 22 14 West Bridge Crane Load Testing

For the lump sum of $

11 41 22 21 East Bridge Crane, Removal of Existing Equipment

For the lump sum of $

12 41 22 21 West Bridge Crane, Removal of Existing Equipment

For the lump sum of $

13 41 22 21 Runway Collectors and Molded-case Circuit Breaker East Bridge Crane

For the lump sum of $

14 41 22 21 Runway Collectors and Molded-case Circuit Breaker West Bridge Crane

For the lump sum of $

TOTAL FOR PRICE SCHEDULE $_________________

END OF SUPPLIES OR SERVICES AND PRICES

Colorado River Storage Project Specification No.

Table of Contents 00 01 10 - 1

SECTION C - DESCRIPTION / SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 12 10 Other Contracts 01 14 10 Use of Site 01 14 12 Work Restrictions 01 14 16 Existing Cranes Characteristics 01 14 30 Interruption of Service 01 31 30 Construction Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 26 Electrical Drawings and Data 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 30 Contractor’s Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 51 00 Temporary Utilities 01 55 00 Vehicular Access and Parking 01 56 10 Protection of Existing Installations 01 60 00 Product Requirements 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents

DIVISION 02 – EXISTING CONDITIONS

02 80 10 General Requirements for Hazardous Materials Abatement 02 82 20 Removal and Disposal of Asbestos Containing Materials 02 83 33 Recycling Coated Scrap Metal 02 87 20 Removal and Disposal of Used Oil

DIVISION 09 – FINISHES

09 96 20 Coatings

DIVISION 26 – ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 10 Conductors and Cables 26 05 26 Grounding and Bonding 26 05 33 Raceways, Conduit, and Boxes for Electrical Systems 26 05 90 Wiring Checkout and Tests

Colorado River Storage Project Specification No.

Table of Contents 00 01 10 - 2

DIVISION 41 – MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 14 Crane Upgrades and Modernization 41 22 21 Removal of Existing Bridge Crane Equipment

DIVISION 51 – INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 02 82 Hazardous Material Survey and Analytical Results 51 00 50 Electronic Media Release

DIVISION 52 - DRAWINGS

52 00 00 Drawings

END OF CONTENTS

Colorado River Storage Project Specification No.

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 Glen Canyon Power Plant, approximately 3 miles northwest of Page, Arizona, in Coconino County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. 300 Ton Capacity Bridge Cranes:

1. Remove and Dispose Existing Equipment:

a. Main and auxiliary hoists and motors, trolley drive systems, and bridge drive systems. 41 22 14

b. All control equipment from crane control cabinet enclosures.

c. Wiring, conductors, and collector systems.

d. Equipment enclosures.

e. Operator’s cab and cab controls.

f. Hoist ropes.

g. Main fused disconnect switch.

h. Molded case circuit breaker in substation switchgear 3, DMA breaker 4-3.

2. Furnish and Install New Equipment:

a. Main and auxiliary hoists and motors, trolley drive systems, and bridge drive systems.

b. Variable frequency drive (VFD) controls for all hoists, trolleys, and bridge drives.

c. Cross-bridge cable festoon systems for trolleys.

d. Operators cab and cab controls.

e. Main fused disconnect switches.

3. Runway electrification service fused disconnect switch.

4. Operator cab fused-disconnect switch.

a. Grounding and bonding conductors and other miscellaneous equipment required to complete electrical installation.

b. Equipment enclosures.

Colorado River Storage Project Specification No.

Summary of Work 01 11 00 - 2

c. Hoist ropes.

d. Non-destructive (visual) examination of bridge crane components.

e. Draining, cleaning and re-lubricating bridge crane components.

f. Perform load tests for lifting devices.

g. Perform load tests, and operation and maintenance training.

h. Coordination with the Government and Government force to accomplish principal components of work.

5. See Section 41 22 14 – Crane Upgrades and Modernization.

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, the words “shall be” are included by inference where a colon (:) is used within the sentence or phrase.

1.04 DEFINITIONS

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

B. Quality Assurance: Inspection and tests performed by Government to ensure compliance with the terms of the contract.

C. Quality Control: Activities performed by Contractor to ensure work conforms to contract requirements.

D. Contractor Quality Testing: Specified tests to be performed by the Contractor:

1. The Government may use the test results for Quality Assurance.

2. The Contractor may use the test results as part of Contractor quality control.

a. The Government anticipates that these tests will be part of the Contractor’s quality control program, however the tests do not relieve the Contractor of providing adequate quality control measures.

1.05 ACRONYMS

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

1. CO: Contracting Officer.

Colorado River Storage Project Specification No.

Summary of Work 01 11 00 - 3

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Colorado River Storage Project Specification No.

Summary of Work 01 11 00 - 4

Colorado River Storage Project Specification No.

Other Contracts 01 12 10 - 1

SECTION 01 12 10

OTHER CONTRACTS

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

A. During work under this contract, other work that may be performed in the vicinity of the work by other contractors includes the following:

1. Hydraulic Elevator and Station Service replacement.

B. Cooperate and coordinate with other contractors on access to and use of work areas and contractor use areas. Comply with the clause at FAR 52.236-8, Other Contracts.

C. Cooperate and coordinate with other contractors on use of temporary utilities.

D. Cooperate and coordinate with other contractors on maintaining dust-free operations.

E. Cooperate and coordinate with Glen Canyon Power plant operating and maintenance personnel.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Colorado River Storage Project Specification No.

Other Contracts 01 12 10 - 2

Colorado River Storage Project Specification No.

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 SUBMITTALS

A. Submit the following 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 facilities.

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

b. Describe location for storage of extra materials and spare parts required to be delivered to the Contractor.

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

d. Describe plan for coordinating use of parking areas.

e. Describe methods for removing temporary structures and facilities, cleanup, and rehabilitating site after completion of project 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.

Colorado River Storage Project Specification No.

Use of Site 01 14 10 - 2

1.03 PROJECT CONDITIONS

A. Areas within powerplant as shown on drawings may be used for required project facilities.

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

C. Location, operation, maintenance of the work site will be subject to approval.

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

E. Housing for contractor personnel will not be permitted on Government land, except housing for guards or watchmen as may be approved.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 RESTORATION

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

Colorado River Storage Project Specification No.

Work Restrictions 01 14 12 - 1

SECTION 01 14 12

WORK RESTRICTIONS

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

A. Bureau of Reclamation operates and maintains the Glen Canyon Powerplant.

B. Maintain Government access to the Glen Canyon Powerplant and other facilities at all times.

C. Allowable Work Hours at Glen Canyon Powerplant:

1. Monday through Thursday: 6:30 a.m. to 5:00 p.m.

2. Alternate work schedules, including Fridays and weekend work, shall be submitted in writing, 7-working days in advance of the proposed schedule.

3. Night work is discouraged. Night work shall require a written request, a minimum of 2 calendar weeks advance notice, and may not be granted.

D. No work will be allowed during Federal holidays or Sundays.

E. Contractor shall provide names of all employees for background check. List of employees provided by contractor. ID's issued by Government are to be used by Contractor to access facilities at all times.

F. All onsite contractor employees shall wear PIV. Contact COR to obtain PIV.

G. Access to the powerplant will remain locked outside of allowable working hours.

H. Photographs of the powerplant and equipment are not allowed, unless coordinated with COR in advance.

I. Sequence:

1. Complete Non-Destructive Examination on both cranes first before beginning

Modernization of either crane.

J. Coordinate with the COR for any possible crane work during on site period of performance.

Colorado River Storage Project Specification No.

Work Restrictions 01 14 12 - 2

M. Work including, but not limited to, removal of coatings, coating applications, cutting of welds, and new welding shall not occur when a crane is over a power generator unit.

N. Tunnel dimensions are approximately 22 high and 25 ft wide presently a 2 lane roadway passes through the tunnel. Contractor shall coordinate deliveries with COR.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Colorado River Storage Project Specification No.

Existing Cranes Characteristics 01 14 16 - 1

SECTION 01 14 16

EXISTING CRANES CHARACTERISTICS

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 EXISTING CRANES CHARACTERISTICS

A. Glen Canyon Powerplant two 300 Ton Capacity Bridge Cranes (henceforth referred to as “bridge cranes”):

1. Description: Cab-operated, composed of two separate overhead bridge cranes

(East / West), each with two trolleys (North / South) with 150 Ton capacity main hoists and 30 Ton capacity auxiliary hoists, located in powerplant for maintenance and servicing of the generator and turbine units.

2. Crane Layout: See Section 52 00 00 – Drawings, for informational drawings showing crane layout and crane details.

3. Main Hoist:

a. Capacity: 300 Tons (two 150 Ton capacity hooks that can be operated separately or in tandem).

b. Motors: (2)-40 Hp, DC power.

c. Hoisting speed: 5.8 feet/minute (maximum), 5 speed steps.

d. Hook lift: 80 feet (minimum).

e. Low hook: Elevation 3139.50.

f. High hook: Elevation 3219.5.50 (minimum).

g. Wire rope: 12 parts 1-3/8” 6 X 37 improved plow steel arranged in 6-part double reeving.

4. Auxiliary Hoist:

a. Capacity: 30 Tons (one per trolley).

b. Motors: (2)-40 Hp, DC power.

c. Hoisting speed: 19.1 feet/minute (maximum), 5 speed steps.

d. Hook lift: 100 feet (minimum).

e. Low hook: Elevation 3122.00.

f. High hook: Elevation 3222.00.

Colorado River Storage Project Specification No.

Existing Cranes Characteristics 01 14 16 - 2

g. Wire rope: 4 parts 1” 6 X 37 improved plow steel arranged in 2-part double reeving.

5. Trolleys:

a. Quantity: 4 (2 per bridge crane)

b. Motors (each trolley): One 5 Hp, wound-rotor induction, 460 Volt, 3-phase, 60 Hz.

c. Speed: 35 feet/minute (maximum), 5 speed steps.

d. Rail:

1) Length: 46’-8” feet.

2) Type: 171 pound (U.S. Steel & Bethlehem) crane.

6. Bridge:

a. Quantity: 4 (2 per bridge crane)

b. Span: 71.5 feet.

c. Drive Arrangement: CMAA 70, type A2.

d. Motors: (each bridge): Two 15 Hp, wound-rotor induction, 460 Volt, 3-phase, 60 Hz.

e. Speed: 100 feet/minute (maximum), 5 speed steps.

f. Runway:

1) Length: 588 feet.

2) Top of Crane Rail: Elevation 3222.00.

3) Rail Type: 175 pound (U.S. Steel & Bethlehem) crane.

7. Coupling of Cranes:

a. The four main trolley hoists can be coupled together by means of lifting beams to provide a combined lifting capacity above that of a single crane.

b. Requires one operator to operate all of the main hooks in tandem.

c. Manual mechanical latches between bridges.

1.03 BELOW-THE-HOOK LIFTING DEVICES CHARACTERISTICS

A. 600T Lifting Beam:

1. Used to combine 4 main hoist bridge crane hooks for rotor lifts.

2. See Assembly Drawing 557-M-D-23-53.

3. Lifting capacity: 600 Ton

4. Assembly weight: 67,000-pounds.

Colorado River Storage Project Specification No.

Existing Cranes Characteristics 01 14 16 - 3

1.04 METHOD OF HANDLING

A. Unit Rotor:

1. Use of 600 Ton Lifting Beam.

2. See Assembly Drawing 557-M-D-23-53.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Colorado River Storage Project Specification No.

Existing Cranes Characteristics 01 14 16 - 4

Colorado River Storage Project Specification No.

Interruption of Service 01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost in prices offered in the Price Schedule for items of work for which outages are required.

1.02 SUBMITTALS

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

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

1. Written request for each proposed outage. Include following in each request:

a. Equipment that will be out of service, i.e. east or west crane.

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

c. Outline of work to be performed including but not limited to:

1) Specific safety precautions to be taken.

2) Type and location of barricades.

3) Warning signs.

4) Protective grounds and devices to be used.

d. Commencement time of interruption of service.

e. Duration of interruption of service.

f. Number of personnel and their classification.

g. Description of equipment to be used.

h. Information indicating that required equipment and materials are on site or data indicating shipping dates of equipment and materials not on site.

1.03 PRODUCTS PROJECT CONDITIONS

A. Coordinate and Schedule Outages with COR:

1. Coordinate work with Government operations and other contractors.

2. No specific outage request will be considered unless:

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

Colorado River Storage Project Specification No.

Interruption of Service 01 14 30 - 2

b. Contractor will be prepared to start the work on date and complete all tasks during period of time requested for specific outage.

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

B. When work cannot be performed during an approved outage period, notify COR that the outage is not required.

PART 2

Not Used

PART 3 EXECUTION

Colorado River Storage Project Specification No.

Contract Document Management System (CDMS) 01 31 30 - 1

SECTION 01 31 30

CONTRACT DOCUMENT MANAGEMENT SYSTEM (CDMS)

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Contract Document Management System:

1. Payment: Lump sum price offered in the Price Schedule.

1.02 DEFINITIONS

A. CDMS: Contract Document Management System.

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

a. Specifications.

b. Contract Drawings.

c. Submittals.

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

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

f. RFPs: Request for Proposal (Reclamation generated document).

g. CMs: Contract Modifications.

h. Contractor Proposals.

i. Value Engineering Proposals.

j. Bureau of Reclamation (Reclamation) Inspection Reports.

k. Invoices and Progress Payments.

l. Contract Schedules.

m. Meeting Agendas and Meeting Minutes.

n. 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. System provider experience, number of systems operations, references.

2. Documentation of system capabilities.

3. Instructions for system use.

01 31 30 - 2

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

1. Reclamation provided USB Drive of documents uploaded to CDMS.

1.04 QUALIFICATIONS

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

1.05 CDMS REQUIREMENTS

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

B. Access:

1. Web-based:

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

b. Compatible with web browsers 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. Adobe Acrobat.

b. MS Word.

c. MS Excel.

d. MS Project.

e. Autodesk AutoCAD Civil 3D Version 2021.

f. 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 to assign user rights which 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.).

01 31 30 - 3

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

Examples:

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

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

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

6. Ability to link files; examples:

a. RFP linked to a CM.

b. 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. Reports shall be printable, exportable as searchable .pdf or printer friendly HTML, and exportable to Excel, (.xls, .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. Secure Server Language (SSL) encryption for secured data exchange between browser and server (Secure access to documents and information).

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

a. Show parties that have access to a document.

01 31 30 - 4

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

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

3. Backup/Archiving to FTP site of documents to which an organization has access on a regular (minimum monthly) basis:

a. Backups shall be in pdf format.

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, RFP, CM, Payments, Daily Inspection Reports, and Meeting Minutes).

2. CDMS shall track:

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

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

c. When a reviewer has opened an item.

F. Submittal Tracking and Control:

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

2. Customizable standard submittal form for entering information:

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.

01 31 30 - 5

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.

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. Contract Modifications:

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

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

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

CDMS.

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

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

J. Cost Tracking and Payment Request Management:

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

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

K. Correspondence:

1. Ability to generate letters and memos:

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

01 31 30 - 6

b. CDMS shall 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 Government to Contractor shall contain Government’s official letterhead and corresponding logos.

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

a. CDMS shall automatically assign sequential meeting numbers.

L. Miscellaneous Tracking and Controls:

1. Ability to generate logs tracking RFIs, CORs, COs, Submittals, Payments, Memos, DIR’s, 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 criteria, e.g., for Submittal, Specification Section, Days Out, Status, or other criteria determined by COR.

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

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

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

7. Ability for keyword search of documents in database.

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

M. Budget and Funding Source Tracking:

1. Ability to enter funding sources and assign contract line items to multiple funding sources.

PART 2 PRODUCTS

2.01 SOFTWARE

A. Procore, as manufactured by Procore, www.Procore.com, or equal with the following essential characteristics: Capable of performing requirements of Part 1 and Part 3.

01 31 30 - 7

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

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 prices offered in 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 work days with calendar days. Project calendars serve as the basis for day/date conversion and assign work days and non-workdays.

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling Manual, 2004

1.04 SUBMITTALS

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

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

a. Database files shall have an (.xer ) file extension.

01 32 10 - 2

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

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

1. Designation of authorized representative to develop and maintain Construction Program. Include resume with training and experience.

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Primavera layout file (.plf).

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

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

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

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

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

1. This submittal is required for a proper invoice for progress payments in accordance with the clauses at FAR 52.232-25 - 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. Gantt chart for project on 11 by 17-inch print(s) and in portable document format (.pdf).

e. Narrative report specifically stating status of project.

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.

f. Submittal Register:

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

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

3) This register document is separate from scheduling database.

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

1. Include:

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

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

c. Primavera layout file (.plf).

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

e. Narrative report explaining results and conclusions.

1.05 QUALIFICATIONS

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

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. Adjust Construction Program/schedule for seasonal weather conditions. Provide a narrative explaining the expected weather and plan for incorporation in schedule.

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

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

Assign weather calendars to work impacted by weather.

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

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

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

01 32 10 - 5

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

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

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

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

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

14. Use durations in units of whole workdays.

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

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

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

B. Baseline Schedule:

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

C. Updated Schedule:

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

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

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

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

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

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

01 32 10 - 6

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 will not automatically determine that extension or reduction of contract time is warranted or due the Contractor.

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

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

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

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

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

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

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

1) Activity description.

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

3) Activity duration.

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

01 32 10 - 7

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. CO will approve or not approve proposed baseline schedule.

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

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

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

B. Updated schedules:

1. Submit updated Construction Program schedule monthly.

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

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

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.

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.

01 32 10 - 8

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Colorado River Storage Project Specification No.

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

a. Government will respond as to adequacy of submittal.

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. Contractor shall correct mistakes or deficiencies in rejected Informational submittals and resubmit.

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.

Colorado River Storage Project Specification No.

Submittals 01 33 00 - 2

B. General:

1. Prepare in English.

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

3. Measurement Units: US Customary Units.

4. Provide a unique transmittal number for each submittal.

C. Drawings:

1. Minimum Identification in Title Block:

a. Contract number and title.

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

c. Date.

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

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

2) Electronic file format: Compatible with AUTOCAD, Version

2018 or later.

3) Compile using “eTransmit” utility in AUTOCAD.

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

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

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

c. Title block and sheet format:

1) As shown on standard drawing 40-D-7102.

2) Government will provide template.

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

6. Final Drawings:

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

Colorado River Storage Project Specification No.

Submittals 01 33 00 - 3

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

Indicate changes by clouding.

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

2. Contents:

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

b. Schematics and wiring diagrams.

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

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

G. Photographs:

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

a. Identify with adhesive labels on back.

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

Colorado River Storage Project Specification No.

Submittals 01 33 00 - 4

2) Do not type directly on back of photograph.

2. Include negatives, or digital files on CD or DVD in .jpeg or similar format.

H. Samples and Color Selection Submittals:

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

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

“set” of samples.

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

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

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

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

1.05 SUBMITTALS PROCEDURES

A. Submit only checked submittals.