00_00_01_Specifications_GC_FIre_sytem_Replacement.pdf

U.S. Department of the Interior AUGUST 2023

Glen Canyon Powerplant Fire Alarms Systems Modernization Glen Canyon Power Plant

Colorado River Storage Project, Arizona-Utah

Upper Colorado Basin Region

This page intentionally left blank

Glen Canyon Power Plant Fire Alarm Systems Modernization Glen Canyon Power Plant Glen Canyon Unit – Arizona – Utah Solicitation No.

GLEN CANYON POWER PLANT FIRE ALARM SYSTEMS MODERNIZATION

GLEN CANYON POWER PLANT

COLORADO RIVER STORAGE PROJECT, AZ

FOREWORD

Work is located approximately 3 miles northwest of Page, Arizona, in Coconino County.

Principal components of work include removal and disposal of existing equipment and components, furnishing, installing, and testing the new fire alarm control panel, fire alarm notification equipment, fire alarm signaling and control devices and new laptop computer compatible with system.

PRE-BID SITE VISIT: SEE SECTION L FOR SITE VISIT INFORMATION.

ATTENDEES ARE TO PROVIDE AND WEAR SAFETY BOOTS, HARD HATS, AND

SAFETY VESTS.

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.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Price Schedule 00 00 50 - 1

SECTION B - SUPPLIES OR SERVICES AND PRICES / COSTS

GLEN CANYON POWER PLANT FIRE ALARM SYSTEMS MODERNIZATION

GLEN CANYON UNIT - ARIZONA - UTAH

COLORADO RIVER STORAGE PROJECT

B.1 PRICE SCHEDULE

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

(1) Offerors shall complete Price Schedules A and B. Offers for less than the total of

Schedules A, and B will be considered nonresponsive and will not be evaluated for award.

(2) Offers will be evaluated based on the total of Price Schedules A, and B. Award will be made to responsible Offeror with the lowest responsive offer for the total of all Price Schedules.

(3) The Government may award Price Schedule A, or Price Schedules A, and B;

depending on available funds.

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

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

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, "Payment for Mobilization and Preparatory Work" which applies to CLIN 1.

(e) Definitions:

(1) CLIN - Contract Line Item Number.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Price Schedule 00 00 50 - 2

PRICE SCHEDULE A

CLIN Section Supplies or Services Quantity and Unit Unit Price

Amount

A-1

WBR

1452.232 -81

Mobilization and Preparatory Work

For the lump sum of $

A-2 01 31 30 Construction Document Management System For the lump sum of $

A-3 01 78 30

As-Builts, Final Drawings, and Operations & Maintenance (O&M) Manuals

A-4 01 79 20 Training For the lump sum of $

A-5 01 91 13 Commissioning For the lump sum of $

A-6 26 05 10 Conductors and Cables For the lump sum of $

A-7 26 05 33 Raceways and Boxes For the lump sum of $

A-8 28 31 00 Fire Alarm System For the lump sum of $

A-9 28 31 75 Remote Station Monitoring System For the lump sum of $

TOTAL FOR SCHEDULE A $_________________

OPTIONAL PRICE SCHEDULE B

CLIN Section Supplies or Services Quantity and Unit Unit Price

Amount

B-1 21 25 00 Hybrid Water Mist Fire Suppression System

For the lump sum of $

TOTAL FOR PRICE SCHEDULE B $_________________

TOTAL FOR PRICE SCHEDULES A AND B $_________________

END OF SUPPLIES OR SERVICES AND PRICES / COSTS

llaughbon Cross-Out

Glen Canyon Unit – Arizona – Utah Coloarado River Storage Project Solicitation 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 11 22 Construction Sequencing 01 12 10 Other Contracts 01 14 10 Use of Site 01 14 30 Interruption of Service 01 31 30 Construction Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 28 Fire Alarm 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 51 00 Temporary Utilities 01 55 00 Vehicular Access and Parking 01 56 10 Protection of Existing Installations 01 57 20 Environmental Controls 01 60 00 Product Requirements 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents 01 79 20 Training 01 91 13 Commissioning

DIVISION 21 – FIRE-SUPPRESSION

21 25 00 Hybrid Water Mist Fire Suppression System

DIVISION 26 - ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 10 Conductors and Cables 26 05 20 Grounding and Bonding 26 05 33 Raceway and Boxes 26 05 90 Wiring Checkout and Tests

Glen Canyon Unit – Arizona – Utah Coloarado River Storage Project Solicitation No.

Table of Contents

00 01 10 - 2

DIVISION 28 – ELECTRONIC SAFETY AND SECURITY

28 31 00 Fire Detection and Alarm 28 31 75 Remote Station Monitoring

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 10 Photographs 51 00 20 Interface Information 51 00 50 Electronic Media Release

DIVISION 52 - DRAWINGS

52 00 00 Drawings

END OF CONTENTS

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. Remove, dispose and replace existing fire detection and alarm systems.

B. Remove the existing interconnection wiring for the fire detection and alarm system.

C. Design, furnish, and install a new fire detection and alarm system.

1. At three locations, the Glen Canyon Powerplant, Carl Hayden Visitor Center, and the Facility Workshop Building.

2. New laptop computer compatible with and, able to operate and monitor system.

3. Communicate and Integrate alarm signals from the fire alarm panels at the

Government Project Warehouse Building, Carl Hayden Visitor Center, and the Facility Workshop.

D. Design, furnish, and install a hybrid water mist fire suppression system in the powerplant computer room.

E. Modify 120 volt distribution systems to accommodate new fire detection and alarm equipment.

F. Integrate new fire alarm system with existing elevators, stairwell pressurization system, generator CO2 release system, transformer deluge system, and heating, ventilation, and air conditioning systems.

G. Test and commission the systems.

H. Plan and sequence work to eliminate or minimize Interruptions of Service to critical station loads within plant.

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.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Summary of Work 01 11 00 - 2

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

PART 3 EXECUTION

Not Used

END OF SECTION

Construction Sequencing

01 11 22 - 1

SECTION 01 11 22

CONSTRUCTION SEQUENCING

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 SUBMITTALS

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

B. RSN 01 11 22-1, Work Sequence Plan:

1. Describe sequencing and how work is to be accomplished for the fire alarm system replacement, which includes: new FACP, NAC and SLC circuits, annunciation panel, integration with existing duct detectors and elevators at the powerplant, new fire alarm system at the administration building/work shop, and addition and integration of communication paths to the fire alarms at the project warehouse and administration building/work shop.

a. How each main component of the fire alarm system is de-energized and removed.

b. Installing new equipment, testing, and placing new equipment in service.

c. Method of keeping existing fire alarm in place until new system is tested and ready to be put in service.

d. List any concerns or expectations for actions to be performed by the

Government in the plan.

1.03 PROJECT CONDITIONS

A. Proposed work sequence requirements:

1. Coordinate and perform the work so that the powerplant has continuous fire alarm coverage throughout the construction.

2. Ensure annunciation of the fire alarm system is clear to plant personnel at all times.

3. Restrictions or limitations on when work can be performed are noted below:

a. Project office to supply.

Construction Sequencing

01 11 22 - 2

1.04 ADMINISTRATIVE REQUIREMENTS

A. Coordination:

1. Coordinate work with other ongoing contracts in accordance with Section 01 14

10 - Use of Site.

B. Scheduling:

1. Proposed schedule for installing new equipment, cutting over existing equipment and removing equipment in accordance with Section 01 32 10 - Construction Program.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Glen Canyon Unit – Arizona – Utah Solicitation 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 Price Schedules 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 Reclamation and other contractors includes the following:

1. Hydraulic Elevator.

2. Crane Modernization.

3. GCFD POWERPLANT UPS (SCADA EACCS)

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.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Glen Canyon Unit – Arizona – Utah Solicitation No.

Other Contracts 01 12 10 - 2

Glen Canyon Unit – Arizona – Utah Solicitation 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 Price Schedules for other items of work.

1.02 PROJECT CONDITIONS

A. For Contractor supplied equipment to be stored on Government land, coordinate with COR for delivery and storage.

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

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

1. Locations of contractor laydown area, parking and dumpster placement to be coordinated with COR.

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

E. Coordinate materials shipment arrival dates and times and storage with COR prior to material arrival.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 RESTORATION

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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Use of Site 01 14 10 - 2

Glen Canyon Unit – Arizona – Utah Solicitation 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 Price Schedules 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: 7:00 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 and may not be granted.

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.

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

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

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

I. Work in the Server Room shall be observed by the COR or authorized Government escort at all times. See Section 01 74 00 – Cleaning and Waste Management, 3.01 B.

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

Work Restrictions

01 14 12 - 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

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 in prices offered in Price Schedule A for items of work for which

Interruption of Service are required.

1.02 SUBMITTALS

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

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

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

2. Outline procedures for accomplishing work including:

a. Specific safety precautions to be taken.

b. Type and location of barricades.

c. Warning signs.

d. Protective grounds and devices to be used.

3. Commencement time of work.

4. Duration of work.

5. Number of personnel and their classification.

6. Description of equipment to be used.

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

1.03 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with COR:

1. Coordinate work with Government operations.

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

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

b. Be prepared to perform work on date and during period-of-time requested for specific interruption of service.

Interruption of Service

01 14 30 - 2

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

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

a. Interruption of services may be scheduled during off-peak periods, nights, or weekends.

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

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

B. When work cannot be performed during an approved interruption of service period, notify COR that interruption of service is not required.

C. Show construction interruption of services greater than 4 hours in construction schedule.

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

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

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 operating, references.

2. Documentation of system capabilities.

3. Instructions for system use.

01 31 30 - 2

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

1. DVD or CD of all 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 MS Internet Explorer, 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. Microsoft Word.

c. Microsoft Excel.

d. Microsoft Project.

e. Oracle Primavera P6 Project Manager.

f. Autodesk AutoCAD Civil 3D.

3. Allow Contract Documents to be prepared by the 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 greater than 15 days without action).

6. Ability to link files; examples:

a. RFP linked to a CM.

b. Submittal linked to a specification section or drawing.

C. Reports:

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

a. Submittals that have been approved.

b. RFIs under review.

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

3. Generate customizable summary reports; examples include:

a. Submittal turnaround.

b. RFI turnaround.

4. Reports shall be printable, exportable as searchable Portable Document Format (PDF) or printer-friendly HTML, and exportable to Excel, XML, or CSV.

5. Ability to link from an item in a report directly to item by clicking on it. 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 Sockets Layer (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.

01 31 30 - 4

3. Backup/archiving to File Transfer Protocol (FTP) site of documents to which an organization has access on a regular (minimum monthly) basis. 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, RFC, RFI, RFP, Daily

Inspection Reports, 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, Conditionally Approved, Not Approved, Accepted, Conditionally Accepted, or Not Accepted).

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. Supply standard submittal form for entering information. CDMS shall allow customizing of standard submittal form.

a. Contractor shall be able to enter submittal summary information (required submittal number, title, description, due date, and specification section shall be required fields) and then upload submittal data in electronic format.

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

a. Status designations may be modified to fit Government standard designations A/CA/NA/Acc/CAcc/NAcc (Approved/Conditionally Approved/Not Approved/Accepted/Conditionally Accepted/Not Accepted).

4. Supply Submittal Tracking form for Government to enter review comments and action taken. CDMS shall allow customizing of submittal tracking form.

a. Allow for Government to route submittal to third parties 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 appropriate reviewers.

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

G. RFI Tracking and Control:

01 31 30 - 5

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 Government 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. Provide ability to upload Reclamation’s standard CM form and RFP forms, or create an acceptable alternative, to enter information.

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

CDMS.

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

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

J. Cost Tracking and Payment Request Management:

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

2. Ability to edit percent complete and payment amount each month. Format to be spreadsheet, e.g. all 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. first response to

Memo 32 to be 32.1, second 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 minutes. CDMS shall automatically assign sequential meeting numbers.

L. Miscellaneous Tracking and Controls. Ability to:

1. Generate reports tracking REAs, RFCs, RFIs, RFPs, RFSs, CMs Submittals, Memos, DIRs, survey requests, plant inspection reports, and testing reports.

2. Filter logs based on criteria:

a. Submittals: Specification Section, Days Out, Status (A/CA/NA/Acc/CAcc/NAcc).

b. RFIs: Days out, Status (Open/Closed), Specification Section/Dwg No., Responsibility/Ball-In-Court.

3. Sort logs based on a criterion, e.g. for Submittal, Specification Section, Days Out, Status, or other criterion determined by the COR.

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

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

01 31 30 - 7

PART 3 EXECUTION

3.01 IMPLEMENTATION

A. The Contractor shall be the administrator of the CDMS site.

1. The Contractor shall maintain and manage CDMS services directly with the software provider.

2. All data and stored information shall belong to the Contractor who has sole responsibility for the CDMS solution.

B. The Contractor shall share access to CDMS site and data with the Government for Contract purposes as described herein.

C. In accordance with Reclamation Directive and Standard RCD 05-01, all information received, created, or compiled by Reclamation officials, employees, contractors, and other staff (employees) is the property of the Federal Government and must be maintained in accordance with established standards.

1. The CDMS shall not be considered as storage of official records or correspondence.

D. CDMS shall be in place and operating before Contractor transmits 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 system.

E. Contractor shall input Schedule of Submittals before making submittals. Include:

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

2. Scheduled submittal date.

F. 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/Conditionally Approved, Not Approved, Accepted, Conditionally Accepted, Not Accepted).

7. Days in review.

01 31 30 - 8

8. Due date.

G. CDMS shall be operational until final project closeout.

3.02 TRAINING

A. Provide the following training sessions:

1. One 30-minute minimum project scoping session for Contractor and USBR personnel to ensure the CDMS system is set up correctly to perform everything necessary for the contract.

2. One 60-minute minimum personalized administrator training session for those administering the CDMS system. Includes both Contractor and USBR personnel.

3. One 60-minute minimum personalized basic user training session for Contractor and USBR personnel.

a. Include the process of receiving and responding to RSNs and RFIs.

B. Coordinate timing, location, and personnel to attend each session with COR.

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

Schedule A for Mobilization and Preparatory Work.

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

1.02 DEFINITIONS

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

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

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual-04 Construction Planning and Scheduling

Manual

1.04 SUBMITTALS

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

1. Database files in format compatible with Oracle Primavera P6 Professional

Project Management or Microsoft Project 2010.

2. Schedule and analysis data on CD-ROM or DVD disk.

3. Information and data used to develop and maintain Construction Program to CO.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Construction Program 01 32 10 - 2

B. RSN 01 32 10-1, Baseline Schedule:

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Primavera layout file (.plf) or Microsoft Project.

d. Gantt chart (Bar chart) for project on 11 by 17-inch prints 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.

C. RSN 01 32 10-2, Updated Schedule Reports:

1. This submittal is required for a proper invoice for progress payments Government disapproval of this submittal will be considered failure of Contractor to comply with contract requirements and payment due date may be delayed until 14 days after submittal contents are approved. 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) or Microsoft Project.

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

e. Narrative report specifically stating status of project.

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

2) List of Contractor-initiated changes to current schedule stating reason for action taken and unresolved issues relating to the Construction Program. Government reserves the right to reject

Glen Canyon Unit – Arizona – Utah Solicitation No.

Construction Program 01 32 10 - 3

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.

1.05 QUALIFICATIONS

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

1.06 GENERAL

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

1.07 SCHEDULES

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

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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Construction Program 01 32 10 - 4

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 COR. Assign Government submittal review activities to a seven-day calendar with durations as specified in Section 01 33 00 - Submittals. Include Required Submittal Number (RSN) in activity description.

9. Include separate activities for fabrication or manufacturing when work involves significant quantities, long lead times, is on the critical path or near critical path, or as requested by 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.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Construction Program 01 32 10 - 5

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. Include appropriate logic relationships for revised activities.

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

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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Construction Program 01 32 10 - 6

4. Schedule pre-submittal meeting with Contractor’s representative each month to review draft updated schedule prior to Contractor submitting, Updated Schedule Reports.

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 Government using approved CPM schedules.

1.09 FAILURE TO COMPLY

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

B. CO may terminate 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

Glen Canyon Unit – Arizona – Utah Solicitation 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 Price Schedules for other items of work.

1.02 DEFINITIONS

A. Days: Calendar days.

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

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

1. A - Action:

a. Government will respond as to adequacy of submittal.

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

2. I - Informational:

a. Government will acknowledge receipt of Informational submittals.

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

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.03 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

1. ASME Y14.1-2020 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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 2

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.

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. Also in accordance with Section 01 33 28 – Fire Alarm Drawings and

Data.

b. Computer drafted.

c. Government will provide an electronic AutoCAD format template.

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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 3

6. Final Drawings:

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

Indicate changes by clouding.

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.

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.

G. Photographs / Images:

1. Format: .jpeg or similar format, 10 megapixel, minimum.

1.05 SUBMITTALS PROCEDURES

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

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 4

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

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

4. Requirements for initial submittals apply to resubmittals.

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.

1.06 REVIEW OF SUBMITTALS

A. Time Required:

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

2. Time required for review of each submittal or resubmittal begins when complete sets of materials required for a particular RSN are received 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.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 5

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 action submittals in sequence and within time periods specified.

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

a. Approval was required under the contract,

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. Submittals: One set of submittals required for will be returned either approved, approved subject to identified changes, or not approved.

a. Revise and resubmit submittals not approved.

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

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

1.07 ELECTRONIC TRANSMITTALS

A. Except as noted, transmit electronically through Government supported CDMS Site.

Contact information will be provided to the Contractor after award.

B. CDMS submittal shall meet the requirements of Article 1.05 Submittal Procedures.

C. Only one complete set shall be submitted with each CDMS submittal.

D. Each submittal shall be submitted separately.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 6

E. Electronic file size shall not exceed 40 Megabytes (MB). Electronic files in excess of 40 MB must be transmitted as hard copy transmittals on Government approved storage medium.

F. Submit data in required format; e.g., survey data ASCII, electronic drawings AutoCAD .dwg.

G. Where format is not specified, preferred format is searchable portable document format (.pdf).

H. The Government, at the discretion of the COR, may require the Contractor to resubmit as hardcopy any transmittals which appear unclear or illegible in their electronic format.

I. Time required for review of each submittal or resubmittal begins on the next business day after transmittal of a complete set and ends the day the response is transmitted.

J. CDMS submittals will be responded to through CDMS.

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

1. Submit in accordance with this section.

2. Submit to COR, unless otherwise specified.

1.08 HARD COPY TRANSMITTALS

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

1. Contracting Officer, Bureau of Reclamation, Attn: UC-846, 125 South State

Street, Salt Lake City UT 84138-1147.

2. Contracting Officer’s Representative, Bureau of Reclamation, Glen Canyon Field

Division, Attn. GC-200, 805 Bureau Street, PO Box147, Page, AZ 86040-1477.

3. Technical Service Center, Bureau of Reclamation, Attn: 86-68160, P.O. Box

25007, Denver CO 80225-0007; Express Mail: Sixth and Kipling, Building 67, Room 152.

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.

1. Responsible codes starting with “86-6” are located in Technical Service Center.

Send these submittals to the TSC address shown above.

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.

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 7

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

1. Submit in accordance with this section.

2. Submit to COR, unless otherwise specified.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Glen Canyon Unit – Arizona – Utah Solicitation No.

Submittals 01 33 00 - 8

Table 01 33 00A. - List of Submittals

* Submittal Types: A - Action, I - Information ** CO indicates Contracting Officer, COR indicates Contracting Officer’s Representative, and TSC indicates Technical Service Center.

RSN

Clause or

Section Title

Submittals required

Due date or delivery…