C0863_Specifications_rev_Apr14_2017.pdf

Shasta and Keswick Powerplant Excitation System Replacements Specifications No. 20-C0863

Table of Contents

00 01 10 - 1

SECTION C - DESCRIPTION / SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 14 10 Use of Site 01 14 30 Interruption of Service 01 31 19 Project Management and Coordination 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 26 Electrical Drawings and Data 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 22 First Aid 01 35 30 Contractor’s Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 51 00 Temporary Utilities 01 54 20 Use of Government Crane 01 55 00 Vehicular Access and Parking 01 56 10 Protection of Existing Installations 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents 01 79 20 Training

DIVISION 02 - EXISTING CONDITIONS

02 82 20 Removal and Disposal of Asbestos Containing Materials 02 83 33 Removal and Disposal of Equipment with Coatings Containing Heavy Metals

DIVISION 03 - CONCRETE

03 62 22 Nonshrink Grout and Grouting Mortar for Equipment and Metalwork

DIVISION 05 - METALS

05 12 10 Structural Steel 05 12 73 Adhesive-Anchored Bolts 05 14 00 Structural Aluminum

Table of Contents

00 01 10 - 2

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 Electrical Conduit 26 05 36 Keswick Removable Cable Tray Systems 26 05 38 Terminal Boxes 26 05 60 Identification, Warning, and Safety Signs 26 05 90 Wiring Checkout and Tests 26 25 10 Metal-Enclosed Bus 26 25 13 Removing and Modifying Existing Equipment

DIVISION 48 - ELECTRICAL POWER GENERATION

48 19 80 Excitation Systems

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 01 Photographs: Keswick Powerplant 51 00 02 Photographs: Shasta Powerplant 51 00 03 Photographs: Spring Creek Powerplant 51 00 04 Keswick Marked Drawings 51 00 05 Keswick Equipment Layout Drawings 51 00 06 Shasta Equipment Layout Drawings 51 00 07 Keswick Existing Cable Schedule and Cable Layout Drawings 51 00 08 Shasta Existing Cable Schedule and Cable Layout Drawings 51 00 09 Keswick Existing SCADA/CVACS Discrete and Analog Input Lists 51 00 10 Shasta Existing SCADA/CVACS Discrete and Analog Input Lists 51 02 83 Asbestos Test Results 51 02 84 Lead Paint Test Results

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. The work is located at Shasta and Keswick Dams. Shasta is adjacent to the City of Shasta Lake and approximately 9 miles northwest of Redding, CA. Keswick is approximately 3 miles northwest of Redding, CA. Both Dams are located in Shasta County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Design, furnish, install, test and commission replacement of existing excitation systems with fully static digital excitation systems for Generator Unit Nos. 1 through 3 at Keswick Powerplant and Unit Nos. 3 through 5 at Shasta Powerplant. Digital Automatic Voltage Regulator (AVR) and Touchscreen Interface/Human Machine Interface (HMI) will be replaced for Shasta Unit Nos. 1 and 2. Touchscreen Interface will be replaced for Shasta Unit Nos. S1 and S2. Work includes:

1. At Keswick Unit Nos. 1 through 3:

a. Remove and dispose of the following equipment:

1) Existing excitation systems, field breakers, and associated equipment.

2) Existing interface cables and conductors.

3) Control and annunciation cables associated excitation systems.

b. Furnish, install, calibrate, program and test/commission:

1) Fully static digital excitation systems.

2) 8-kV medium voltage metal-enclosed bus systems from generator main bus, to excitation Power Potential Transformers (PPTs – high voltage side).

3) PPTs, excitation supply low voltage power circuit breakers, instrument transformers, instrumentation cable and conductors, AVRs, HMI, Direct Current (DC) connection to machine field and other associated equipment.

a) The DC connection shall be Diesel Locomotive Cable (DLO) from the new excitation cabinets to the corresponding existing machine field.

i. The new DLO cable shall be installed in each new removable cable tray system.

01 11 00 - 2

4) 600-Volt power cable systems from the low voltage side of each new PPT to its corresponding new excitation system cabinet.

a) The contractor shall install the new cable systems in new conduit.

c. Design, furnish and install a collector ring swapping device. Implement a practical design of swapping the positive and negative leads of the collector rings.

2. At Shasta Unit Nos. 3 through 5:

a. Remove and dispose of the following equipment:

1) Existing excitation systems, field breakers, and associated equipment.

2) Existing interface cables and conductors.

3) Control and annunciation cables associated with existing excitation systems.

b. Furnish, install, calibrate, program and test:

1) Fully static digital excitation systems.

2) 15-kV metal-enclosed bus extensions for existing generator bus terminals to the new PPTs (high voltage side). The existing 15-kV bus will be reused for each exciter.

3) PPTs, excitation supply low voltage power circuit breakers, instrument transformers, instrumentation cable and conductors, AVRs, HMIs, DC connection to machine field and other associated equipment.

a) 600-Volt metal-enclosed bus extensions for the existing 600-volt metal-enclosed bus from the low voltage side of each new PPT, to its corresponding new excitation system cabinet. The existing 600-volt metal-enclosed bus will be reused for each exciter.

b) 600-Volt metal-enclosed bus extensions for the existing 600-volt DC metal-enclosed bus (DC field connections) from the new excitation system cabinet to the existing generator field pole connections. The existing 600-Volt DC metal-enclosed bus will be reused for each exciter.

c. Design, furnish and install a collector ring swapping device. Implement a practical design of swapping the positive and negative leads of the collector rings.

3. At Shasta Unit Nos. 1 and 2:

a. Remove and dispose of the following equipment:

1) Existing AVRs, HMIs and associated equipment.

01 11 00 - 3

2) Existing interface cables and conductors.

3) Control and annunciation cables associated with existing AVR and HMI systems.

b. Furnish, install, calibrate, program, test and install:

1) AVR and HMI systems.

2) Low voltage power circuit breakers, instrument transformers, instrumentation cable and conductors, and other AVR and HMI associated equipment.

c. The Government will design, furnish and install a collector ring swapping device outside of this contract. The Government will implement a practical design of swapping the positive and negative leads of the collector rings.

4. At Shasta Unit Nos. S1 and S2:

a. Remove and dispose of the following equipment:

1) Existing HMI systems and associated equipment.

2) Existing interface cables and conductors.

3) Control and annunciation cables associated with existing HMI systems.

b. Furnish, install, calibrate, program, test and install:

1) HMI systems.

2) Low voltage power circuit breakers, instrument transformers, instrumentation cable and conductors, and other HMI associated equipment.

c. This contract will not include a collector ring swapping device for Shasta’s Station Service S1 and S2 generators.

B. Design, furnish, install, test/commission uniform AVR (Automatic Voltage Regulator) and touchscreen interface (HMIs) for all units at Shasta (Unit Nos. 1 through 5) and Keswick (Unit Nos. 1 through 3).

1. Design, furnish, install, test/commission uniform touchscreen interface (HMIs) for the station service exciters at Shasta power plant; Unit Nos. S1 and S2. All new HMIs shall be uniform; same make, model and manufacturer.

C. Modify generator terminal taps, unit control boards, and unit protection cabinets where necessary.

D. Electrically isolate existing rotating DC exciters at Keswick Powerplant for generator Unit Nos. 1 through 3. The existing rotating exciters will be abandoned in place, except for the following:

01 11 00 - 4

1. The contractor shall remove the Keswick pilot exciter’s field poles, brushes and associated conductors of Unit Nos. 1 through 3.

E. Provide control and power cable, wire, and associated conduits or cable trays for power, control, protection and alarm circuits. Terminate all cabling required for turn-key installation.

F. Design, furnish and install a removable cable tray system for each Keswick exciter; Unit Nos. 1 through 3.

G. Furnish spare parts as required in applicable sections.

H. Furnish drawings and data: Includes revision to Government drawings external to excitation system to address requirements of turn-key installation.

I. Use the same manufacturer and model for each component with the same function and capacity for all units; Keswick Unit Nos 1 through 3, Shasta Unit Nos 1 through 5 and Shasta’s Station Service Unit Nos. S1 and S2.

J. Factory and field testing of each new excitation systems, PPTs and associated equipment.

K. Train Government personnel in operation and maintenance of new excitation systems.

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 QUALITY ASSURANCE

A. The Basler excitation system, power potential transformer (PPT) and power circuit breaker manufacturers shall be ISO 9001 or 9002 certified.

B. The excitation system, PPT and power circuit breaker manufacturers shall have specialized experience in the design, manufacture and assembly of excitation systems, dry-type power transformers and power circuit breakers for a minimum of 20 years.

C. The prime contractor shall utilize Brand Name Suppliers in regard to the Basler excitation systems.

D. The excitation system and PPT installer(s) must have 5 years of experience installing, interfacing and testing similar excitation systems as what is being installed for this

01 11 00 - 5 project. References and contact information of each past project shall be provided to BOR after Notice to Proceed.

E. The Contractor’s design, installation and testing Electrical Engineer(s) shall have 5 years’ experience minimum, working with excitation systems similar to this project’s requirements.

1.05 REGULATORY REQUIREMENTS

A. Contractor shall be licensed as classification type C-10 by the California Contractors State License Board (CLSB).

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

1.07 ACRONYMS

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

1. CO: Contracting Officer

2. COR: Contracting Officer’s Representative

3. CE: Construction Engineer

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

01 11 00 - 6

This page intentionally left blank.

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 PAYMENT

A. Cost:

1. Include in lump sum price offered in the Price Schedule for Mobilization and Preparatory Work.

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (USBR)

1. Cleaning Manual-2012 Inspection and Cleaning Manual for Equipment and Vehicles to Prevent the Spread of Invasive Species (Technical memorandum No. 86-68220-07-05) 2012 Edition Available online at:

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

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

6) Temporary fences.

b. Describe methods to preserve, protect, and repair, vegetation (such as trees, shrubs, and grass) and other landscape features on or adjacent to

Use of Site 01 14 10 - 2 jobsite, which are not to be removed and which do not interfere with work required under this contract. Include methods to mark work area limits, protect disturbed areas, and prevent erosion.

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

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

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

1.04 PROJECT CONDITIONS

A. Government land as shown on drawings may be used for required construction facilities.

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.

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 construction personnel will not be permitted on Government land, except housing for guards or watchmen as may be approved by COR.

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 PAYMENT

A. Cost:

1. Include prices offered in the Schedule for items of work for which interruption of service (outages) 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: Submit written request to Onsite Government Representative (OGR) at least seven days before date of each proposed outage. Include the following in each request:

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

2. Outline procedures for accomplishing work including:

1. Specific safety precautions to be taken.

2. Type and location of barricades.

3. Warning signs.

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

8. Job Hazard Analysis (JHA) for work to be accomplished during outage.

9. Lockout Tagout (LOTO) of hazardous energy and proper log documentation.

1.03 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with OGR:

1. Coordinate work with Government operations and other Contractors.

2. Interruption of Service scheduling will depend upon power demand requirements and related operating conditions.

01 14 30 - 2

3. Interruption of service may be scheduled during off-peak periods, nights, or weekends.

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

1. OGR has reasonable assurance that materials and equipment required for work will be onsite.

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

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

6. Show construction outages greater than 4 hours in the construction schedule and in the master outage/cutover schedule.

B. Interruption of service window available to Contractor: Government will place the units on clearance to accommodate Contractor-requested and approved interruption of service only during the following intervals.

1. October 15 through April 15.

2. April 15 through October 15 may have availability on a case-by-case basis.

3. Only one unit can be under a clearance (at each powerplant) at a time until commissioned, found acceptable and placed back in normal operation.

C. No specific request for an outage will be considered unless OGR has reasonable assurances that materials and equipment required for work will be on site and Contractor is prepared to perform work on date and during period of time requested for specific outage.

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

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

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

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

E. When work cannot be performed during an approved interruption of service period, notify OGR (at least five working days prior) that interruption of service is not required.

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

01 14 30 - 3

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 14 30 - 4

Project Management and Coordination

01 31 19 - 1

SECTION 01 31 19

PROJECT MANAGEMENT AND COORDINATION

PART 1 GENERAL

1.01 PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedules for other items of work. If the Contractor fails to attend a required meeting, an equitable adjustment may be made to the contract price.

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (USBR)

1. RSHS Reclamation Safety and Health Standards

1.03 SUBMITTALS

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

B. RSN 01 31 19-1, Pre-Design Meeting Notification:

1. Provide confirmation to COR regarding requested date and time of meeting and indicate who will be attending and affiliations.

2. Provide copies of preliminary layout drawings.

C. RSN 01 31 19-2, Excitation System Design Meeting:

1. Confirmation regarding requested date and time of meeting and indicate who will be attending and affiliations.

2. Preliminary drafts of pertinent drawings.

3. System Integration Documentation:

a. Fully static digital excitation systems

b. 15kV and 5kV metal enclosed bus and cable.

c. Power Potential Transformer (PPTs), excitation supply low voltage power circuit breakers, instrument transformers, instrumentation cable and conductors, DC connection to machine field and other associated equipment.

d. Brush swapping design for interface to DC collector rings.

e. Automatic Voltage Regulator (AVR) and touchscreen designs.

D. RSN 01 31 19-3, Review Meetings Notification:

01 31 19 - 2

1. Provide confirmation to COR regarding requested date and time of meeting and indicate who will be attending and affiliations.

E. RSN 01 31 19-4, Crane Use Coordination Meeting Notification:

1. Date and time of meeting and proposed attendees.

2. Preliminary schedule of planned crane usage.

1.04 PROJECT COORDINATION

A. The following meetings are considered significant, but do not relieve the Contractor from the responsibility of attending other meetings required by the specifications. The Preconstruction Conference described in clause 52.236-26 is a separate meeting requirement from the meetings listed in this section.

1. Pre-Design Meeting:

a. Date: No later than 15 days after receipt of Notice to Proceed and prior to performing any work on the required RSNs for the equipment listed below:

1) Excitation Systems.

2) PPTs.

3) AVR and touchscreen interface.

b. Location: Bureau of Reclamation, Shasta Power Plant – Visitor Center, 16349 Shasta Dam Blvd, Shasta Lake, CA 96003; unless otherwise directed by the CO.

c. Meeting Length: Not to exceed 8 hours.

d. Purpose: Review with Government personnel electrical drawings, data, and technical requirements of specifications for the excitation systems in the Shasta and Keswick Power Plants.

e. Attendees: Responsible engineering representatives who have been fully informed of specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete electrical design. Representatives shall include:

1) Project manager and project engineer from contractor.

2) One from prime electrical subcontractor if subcontracting.

f. Within 30 calendar days after conclusion of pre-design meeting, Government will furnish Contractor a letter regarding items discussed at conference with enclosed copies of all pertinent drawings and data marked with Government’s comments.

g. Provide following preliminary information at meeting:

1) Scope of work.

2) Proposed schedule.

01 31 19 - 3

3) Schedule of future Design and Progress Review Meetings. The Contractor shall furnish a schedule of design and progress meetings to USBR for approval.

4) Shipping, delivery, storage, installation, and on site assembly procedures. Include and provide:

a) Name and qualifications of manufacturer’s engineer if applicable to be onsite.

b) Considerations to address prevention of shipping damage.

5) Installation procedures in accordance with all applicable specification sections and drawings.

6) Cabinet and equipment layouts.

2. Excitation System Design Meetings:

a. Location: Teleconference with live data sharing technology; unless otherwise directed by the CO.

b. Meeting Length: Not to exceed 6 hours.

c. Attendees: Responsible engineering representatives informed of specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete electrical design.

Include:

1) Project manager and project engineer from contractor.

2) One prime electrical subcontractor representative responsible for system integration if subcontracting.

d. Purpose: by conference call.

1) Meet weekly with Reclamation designers to review design progress.

2) Review with Government personnel electrical drawings, data, and technical requirements of specifications for system integration of the excitation systems in the Shasta and Keswick Power Plants.

3) Schedule, Progress, and Coordination:

a) Review schedule, project issues, submittals, Request for Information (RFI), and resolution necessary to meet specifications requirements.

b) Review dates that activities were started and completed, remaining duration, and percent complete.

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

4) Discuss design and schedule.

01 31 19 - 4

3. Progress Review Meetings/Weekly Coordination Meetings:

a. Contractor will coordinate with OGR for a weekly coordination meeting time. A teleconference with live data sharing technology; unless otherwise directed by the CO.

b. Meeting Length: Not to exceed 4 hours.

c. Attendees: Responsible engineering representatives fully informed of specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete electrical design.

Representatives shall include:

1) Project manager and project engineer from contractor.

2) One from prime electrical subcontractor.

d. Purpose:

1) Meet weekly with COR to review progress made to the end date of the progress payment period.

2) Review with Government personnel electrical drawings, data, and specification technical requirements of the excitation systems.

3) Schedule, Progress, and Coordination:

a) Review safety, progress made, schedule, project issues, submittals, Request for Information (RFI), and resolution necessary to meet specifications requirements.

b) Review dates that activities were started and completed, remaining duration, and percent complete.

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

d) Three week look ahead.

e) Safety site walk.

f) Project status.

4) Discuss design and schedule.

5) The contractor shall provide a meeting agenda and keep minutes for each teleconference. The contractor shall email the minutes to all attendees and approved by Reclamation.

4. Crane Use Coordination Meeting:

a. Date: Approximately 21 days prior to mobilization.

b. Location: Northern Area Office – Shasta Powerplant, 16349 Shasta Dam Boulevard, Shasta Lake, CA 96019

c. Purpose: Review with Government personnel Crane Use, Crane Use Schedule, and Weekly Coordination Meetings during Construction.

01 31 19 - 5

d. Attendees: Responsible engineering representatives who understand these specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete electrical design.

Representatives shall include:

1) Contractor: 1

2) Subcontractor (if applicable): 1

5. Weekly Coordination Meetings during Construction

a. Contractor shall coordinate with OGR for a weekly coordination meeting time.

1) Meeting will include:

a) Review of schedule, including three week look ahead.

b) Safety site walk.

c) Project status.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

A. Weekly Coordination Meetings during Construction

1. Contractor shall conduct weekly coordination meeting with OGR and other appropriate individuals from Contractor and Reclamation staff.

a. Meeting will include:

1) Review of schedule.

2) Safety site walk.

01 31 19 - 6

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

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 (Government generated document).

g. Value Engineering Proposals.

h. Government Inspection Reports.

i. Contract Schedules.

j. Meeting Agendas and Meeting Minutes.

k. Letters and Memos.

2. PM – Project Manager

3. CO – Contracting Officer

4. COR – Contracting Officer’s Representative

1.03 SUBMITTALS

A. Submit 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 documents uploaded to CDMS.

1.04 QUALIFICATIONS

A. System provider: At least 5 years successful performance in providing required services per this Section.

1.05 SCOPE

A. The CDMS shall generate, store, track, categorize and manage all construction documentation. Construction Documentation includes, but is not limited to: Submittals (typically .pdf files of text documents or drawings); RFIs, RFCs, and RFPs; Contractor Proposals; Value Engineering Change Proposals; Invoices and Progress Payments;

Construction Schedules; Meeting Agendas and Meeting Minutes; Correspondence;

Memos and Deficiency Notices; Contract Modifications and similar documents.

Documentation may be prepared by the Construction Contractor or by Reclamation.

B. Reclamation shall be able to easily access documents and to track when documents were received or returned, as well as determine the status of the documents. Reclamation shall be able to generate reports that list and sort the documents by status as well as generate alerts when documents requiring review exceed allowable review time. Document generation shall include submittals and RFIs, responses, Meeting Minutes, RFCs, RFPs and Contract Modifications, Payments and correspondence.

C. Documents may be generated by either the Contractor or by Reclamation. Each party needs the capability to maintain document security within its organization unless/until it chooses to share it with the other party. Once documents are shared, they shall be secured so that no changes can occur without a record of the changes being made. The CDMS shall be capable of producing a complete and logically organized set of all documents within the CDMS in both .pdf and .xml format. The documents shall be downloadable to ftp sites where Reclamation and other organizations can each access their own data confidentially.

1.06 CDMS REQUIREMENTS

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

01 31 30 - 3

b. MS Word.

c. MS Excel.

d. Oracle Primavera P6 Project Manager.

e. Autodesk AutoCAD 2015.

f. MS Project.

g. Contract Manager.

Documents shall be grouped into separate categories.

3. Reclamation Project Manager (PM) or other authorized user shall be able to create and modify project properties.

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

5. 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, project directory, etc.).

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

7. Ability to link files; examples:

a. Submittal linked to a Specification Section or Drawing.

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

01 31 30 - 4

3. Generate customizable summary reports, examples include:

a. Submittal Turn-around.

b. RFI Turn-Around.

4. Reports shall be printable, exportable as searchable pdf or printer friendly HTML, and exportable to Excel, XML, or CSV.

5. Ability to link from an item in a report directly to 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. Ability to link files.

7. Capable of producing a complete and logically organized set of documents within CDMS in both pdf and xml format.

C. Document Security and Backup:

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

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

a. Show parties that have access to a document.

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

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

d. Tracking of all data changes including who entered or changed data and date change was made.

e. Ability to tell when reviewer has opened/read an item.

f. Project manager for each organization shall have capabilities to assign users within their organization to a project and to assign user rights which control access to documents based on user class and document type.

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.

D. General Tracking and Control:

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

2. CDMS shall track:

01 31 30 - 5

a. When documents were received or returned, as well as status of documents (e.g. Under Review; or Approved, Conditionally Approved, or Not Approved; or 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.

E. 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. Contractor shall be able to enter submittal summary information (required submittal number, title, description, due date, and specification section shall be required fields as outlined in Section 01 33 00 “Submittals”) and then upload submittal data in electronic format.

3. Ability to create multi-item submittal packages with separate per-item review status, transmittals, and re-submittals.

4. Track date received, date response due, date returned, and approval status. Status designations can be modified to fit Reclamation standard designations.

a. Status designations may be modified to fit Government standard designations - A/CA/NA/AC/CAC/NAC (Approved/Conditionally Approved - Resubmit/Not Approved/Accepted/Conditionally Accepted - Resubmit /Not Accepted).

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

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

7. Ability to track the date the submittal/re-submittal was submitted and responded to, with automatic notification after specified number of days without response.

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

G. Contract modifications:

01 31 30 - 6

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

2. Provide ability to upload Reclamation’s standard Contract Modification and RFP forms to enter information.

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

CDMS.

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

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

H. Cost tracking and payment request management:

1. Ability to enter/import payment bid items cost from an Excel spreadsheet.

2. Ability to edit percent complete or payment amount each month. Format to be spreadsheet; for example, 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.

3. Cost tracking and payment requests will be done off line, hard copy submittal.

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

J. Correspondence:

1. Ability to generate letters and memos.

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

b. CDMS shall ability 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.

01 31 30 - 7

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

a. CDMS shall automatically assign sequential meeting numbers.

K. Miscellaneous Tracking and Controls. Ability to:

1. Generate reports tracking RFCs, RFIs, RFPs, Submittals, Payments, Memos, DIR’s, survey requests, plant inspection reports and testing reports.

2. Filter logs based on criteria:

a. Submittals: Specification Section, Days Out, Status (A/CA/NA/AC

/CAC/NAC).

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

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

4. Ability to provide forms to match Reclamation’s Contract Modification form or other forms when needed.

5. Ability to track cost exposure with links to Requests for Information and Change Order Requests.

6. Measure productivity benchmarks on a project such as computing average review days for RFIs, submittals by category, categorize change orders and track total change order percentages by category.

7. Keyword search of documents in database.

8. Ability for CDMS Generated Notification via email to Team Members of:

updates to project information; changes to project information; and alerts.

9. Ability for Reclamation to create Master List of Anticipated Submittals (“Schedule of Submittals”) and require Contractor to pick from that list when submitting submittal.

L. Budget and funding source tracking:

1. Ability to enter multiple budgets to be assigned to projects. The ability to split contracts across multiple budgets.

2. Ability to enter funding sources and assign contract and projects to the funding sources. Contracts shall have the ability to be split across multiple funding sources.

PART 2 PRODUCTS

01 31 30 - 8

PART 3 EXECUTION

3.01 IMPLEMENTATION

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

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

B. Contractor shall input 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/Conditionally Approved - Resubmit/Not Approved/Accepted/Conditionally Accepted - Resubmit /Not Accepted).

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

1. Developing Baseline Schedule: Include in lump sum price offered in the Prices Schedule for Mobilization and Preparatory Work.

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

1.02 DEFINITIONS

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

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

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling Manual, 2004

1.04 SUBMITTALS

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

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

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

01 32 10 - 2

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

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

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

1. Include:

a. Construction Program/Schedule database with activity and milestone data.

b. Definition of project calendars.

c. Primavera layout file (.plf).

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

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

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

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

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

1. This submittal is required for a proper invoice for progress payments in accordance with the clauses at FAR 52.232-27 - Prompt Payment for Construction Contracts and WBR 1452.232-82 - Other Invoice Requirements. 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.

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

01 32 10 - 3 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.

1.06 GENERAL

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

01 32 10 - 4

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.

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.

01 32 10 - 5

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.

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…