R15PS00287 - Section C - Drawings and Specifications.pdf

Trinity Powerplant Generator Rewinds Specifications No. 20-C0841

Table of Contents

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 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 and Medical Services 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 57 20 Environmental Controls 01 60 00 Product Requirements 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents

DIVISION 02 - EXISTING CONDITIONS

02 83 30 Removal and Disposal of Coatings Containing Heavy Metals

DIVISION 03 - CONCRETE

03 62 20 Nonshrink Grout for Equipment and Metalwork

DIVISION 22 - PLUMBING

22 11 85 Generator Air Coolers

DIVISION 26 - ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 20 Conductors and Cables 26 05 33 Electrical Conduit

Table of Contents

DIVISION 48 - ELECTRICAL POWER GENERATION

48 13 25 Thrust Bearing High Pressure Lift System 48 13 62 Armature Winding and Stator Core Removal 48 13 64 Stator Cores 48 13 71 Armature Windings 48 13 73 Field Windings

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 20 Existing Generator Data

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 approximately 8 miles north of Lewiston, California, in Trinity County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Generators:

1. Establish unit centerline for two generators:

a. Provide onsite personnel to take necessary measurements during Government operations of generator disassembly and rotor removal.

2. Furnish new generator air coolers and one spare for two generators.

a. Government will remove the existing air coolers and install the new air coolers.

3. Remove and dispose of existing armature windings and stator cores for two generators.

a. Provide generator work platform for use in the generator bore.

4. Furnish and factory test new armature windings and stator cores for two generators.

a. Replace main and neutral bus inside of the air-housing and replace the current transformers.

5. Install and field test new armature windings and stator cores for two generators.

6. Remove, refurbish, reinstall and test generator rotor poles for two generator rotors.

a. Balance rotor after Government reassembles the generator.

B. Thrust Bearing High Pressure Lift System:

1. Furnish new pump, motor, strainer, piping, fittings, and instrumentation, and install outside of generator airhousing.

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.

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.

3. OGR: Onsite Government Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 SUBMITTALS

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

B. RSN 01 14 10-1, Land Use and Landscape Rehabilitation Plan:

1. For each Contractor use site on Government land.

a. Show use location and extent of impact. Uses include but are not limited to the following:

1) Buildings and service areas including offices, shops, warehouses, storage areas, fuel and oil storage areas, and fabrication yards.

2) Parking areas, temporary roads, and haul routes.

3) Utilities including air, power, and water lines; fire hydrants; and compressor station.

4) First-aid and medical 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 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.

Use of Site 01 14 10 - 2

1.03 PROJECT CONDITIONS

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

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

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

D. Use of Government land will be permitted for Contractor’s equipment staging area, parking, and construction trailer subject to approval of the COR.

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

F. Site is a Government secured area. Contractor is responsible for keeping gate(s) locked at all times except during passage through gates and maintain the existing level of security.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 RESTORATION

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

Interruption of Service

01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost in prices offered in the Price Schedules for items of work for which interruption of services are required.

1.02 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with OGR in writing 6 calendar days before the outage.

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

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

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

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

Interruption of Service

01 14 30 - 2

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.

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Contract Document Management System

01 30 30 - 1

SECTION 01 31 30

CONTRACT DOCUMENT MANAGEMENT SYSTEM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedules 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. CMs: Contract Modifications.

h. Contractor Proposals.

i. Value Engineering Proposals.

j. Government Inspection Reports.

k. Contract Schedules.

l. Meeting Agendas and Meeting Minutes.

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

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

01 30 30 - 2

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.

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

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

f. Autodesk AutoCAD.

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

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

Examples:

01 30 30 - 3

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. Invoices paid to date.

c. RFIs under review.

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

3. Generate customizable summary reports, examples include:

a. Submittal Turn-around.

b. RFI Turn-Around.

c. CM Processing Turn-Around.

d. Total CM costs.

e. Total CM Request Exposure.

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

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. Capable of producing a complete and logically organized set of documents within CDMS in both pdf and xml format.

D. Document Security and Backup:

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

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

a. Show parties that have access to a document.

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

01 30 30 - 4

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

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

a. Backups shall be in pdf format.

4. Documents shall be downloadable to FTP sites where Government and other organizations can each access their own data confidentially.

E. General Tracking and Control:

1. Documents shall be grouped into categories (Submittals, RFC, RFI, RFP, CM, 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 or Rejected, etc.).

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

c. When a reviewer has opened an item.

F. Submittal Tracking and Control:

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

2. 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) 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/AAN/PAR/NA/ACK (Approved/Approved As Noted/Partially Approved - Resubmit/Not Approved/Acknowledged).

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:

1. Supply standard RFI form to enter information.

01 30 30 - 5

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

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

CDMS.

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

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

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 30 30 - 6

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, CMs, Submittals, 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/AAN/R&R/

ACK/RWR).

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. Supply forms to match Government’s CM Form or other forms when needed.

5. Track Cost Exposure with links to RFI and CM requests.

6. 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. Keyword search of documents in database.

L. Budget and Funding Source Tracking:

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

PART 2 PRODUCTS

Not Used

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:

01 30 30 - 7

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-Complete, Approved as Noted - Resubmit, Received, Not Approved).

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

01 30 30 - 8

This page intentionally left blank.

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 schedule for Mobilization and Preparatory Work.

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

1.02 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling Manual, 2004

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

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

1. Furnish schedule and analysis data on CD-ROM disc.

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

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

01 32 10 - 2

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

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

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

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

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. Submit monthly even if not submitting an invoice during the month.

2. Include:

a. Construction Program database with updated activity and milestone data.

b. Definition of project calendars if revised from baseline calendars.

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

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

e. Submittal Register:

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

01 32 10 - 3

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. Gantt chart for project on 11 by 17-inch print(s) and in portable document format (.pdf).

d. Narrative report explaining results and conclusions.

F. The submittals will be Accepted, Conditionally Accepted, or Not Accepted after Government review.

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.

01 32 10 - 4

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.

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.

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

01 32 10 - 5 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 due to delay or accelerated schedule.

B. The CO may use time impact analysis to determine if time extension or reduction to contract milestone dates is justified.

1. Time impact analysis is required for contract changes whether the Contractor’s current schedule milestone dates are the same as, earlier than, or later than, those required under the contract.

2. Changes, additions, or deletions to activities; activity durations; activity time frames; or activity predecessors and successors will not automatically determine that extension or reduction of contract time is warranted or due the Contractor.

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

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

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

01 32 10 - 6

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

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

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

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

1) Activity description.

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

3) Activity duration.

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

c. Data date for impacted schedule used in comparison shall be the same as approved updated schedule data date.

d. Base schedule comparisons on status of work and available float at time the CO directs or proposes change to the work, the Contractor submits a value engineering change proposal, or when a delay occurs as shown in approved updated schedule.

1.09 REVIEW AND EVALUATION

A. Baseline Schedule:

1. Within 21 calendar days after receipt of baseline schedule:

a. CO will accept, conditionally accept, or not accept 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 accepted by the Government.

B. Updated schedules:

1. Submit updated Construction Program schedule monthly.

01 32 10 - 7

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

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

C. Failure to include elements of the work in schedules will not release Contractor from completing required work under the contract.

D. Performance will be evaluated by the Government using approved CPM schedules.

1.10 FAILURE TO COMPLY

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

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 32 10 - 8

Submittals

01 33 00 - 1

SECTION 01 33 00

SUBMITTALS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

1. ASME Y14.1-2012 Decimal Inch Drawing Sheet Size and Format

B. National Institute of Building Sciences (NIBS)

1. NIBS NCS-2011 United States National CAD Standards, Version 5

1.03 DEFINITIONS

A. Days: Calendar days.

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

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.

01 33 00 - 2

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 2013 or later.

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

5. Drawings designated as “Government Format” in specifications.

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

c. Title block and sheet format:

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

2) Government will provide template.

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

6. Final Drawings:

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

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

Indicate changes by clouding.

7. Electronic Files: On CD or DVD discs.

D. Product Data:

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

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

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

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

d. Strike through items that do not apply.

E. Certifications:

1. Certifications by a registered professional: Signed and sealed by registered professional.

01 33 00 - 3

2. Manufacturer’s certifications: Signed by authorized representative of manufacturer.

F. Manuals:

1. Copies:

a. Printed copies: Bound and indexed.

b. Electronic copies: Adobe pdf on CD or DVD discs.

1) Bookmark longer files to assist in navigating file.

2. Contents:

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

b. Schematics and wiring diagrams.

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

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

G. Photographs:

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

a. Identify with adhesive labels on back.

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

2) Do not type directly on back of photograph.

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

H. Samples Submittals:

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

2. Include type and quantity of materials specified in the referenced section in each “set” of samples.

3. Samples: Representative of product to be installed.

4. Label each sample or sample kit with contract number and title.

5. The Government will select architectural color and pattern after product approval.

1.05 SUBMITTALS PROCEDURES

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

B. Submit complete sets of required materials for each RSN as specified in “Submittals Required” column in Table 01 33 00A - List of Submittals. A complete set includes all listed items for RSNs with multiple parts.

01 33 00 - 4

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

1. Submittals identified with “CDMS” in the “Sets to be sent” column shall be submitted electronically in accordance with Section 01 31 30 - Contract Document Management System.

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals other than Approved:

1. Mark changes such that they are readily identifiable and show revision date.

2. Describe reasons for significant changes in transmittal letter.

3. Resubmit returned submittals within 28 days after receiving the comments, unless otherwise directed.

4. Requirements for initial submittals apply to resubmittals.

F. More than one RSN may be submitted under a transmittal letter, provided the responsible code is the same.

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. The CO may extend the contract completion date to allow additional time for completing work affected by excess review time.

a. The time extension will be to the extent that excess review time caused delay to the contract completion date.

b. The time extension will not exceed the time used in excess of the specified number of days for review of submittals or resubmittals.

01 33 00 - 5

c. Concurrent days of excess review time resulting from review of two or more separate submittals or resubmittals will be counted only once in extending the contract completion date.

2. No time extension will be allowed if the 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, and

b. Requests for approval were properly and timely submitted and were approved.

4. Adjustment will be subject to terms of paragraphs (b) and (c) of the clause at FAR 52.242-14, Suspension of Work, however, no such delay shall be deemed to be a “suspension order” as the term is used in that clause.

C. Return of Submittals:

1. With the exception of RSNs 01 32 10-2, 01 32 10-3, and 01 35 20-1, one set of submittals will be returned either approved, approved subject to identified changes, or not approved.

2. RSNs 01 32 10-2, 01 32 10-3, and 01 35 20-1 will be returned either accepted, accepted subject to identified changes, or not accepted.

a. Revise and resubmit submittals not approved or accepted.

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

1.07 HARD COPY TRANSMITTALS

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

1. CE: Construction Engineer, Bureau of Reclamation, P.O. Box 988, Willows, CA 95988-8988, 1140 West Wood Street, Willows, CA 95988-2615.

2. COR: Contracting Officer’s Representative, to be identified post award, Bureau of Reclamation, P.O. Box 988, Willows, CA 95988-8988, 1140 West Wood Street, Willows, CA 95988-2615.

3. OGR: Onsite Government Representative, to be identified post award, Bureau of Reclamation, P.O. Box 988, Willows, CA 95988-8988, 1140 West Wood Street, Willows, CA 95988-2615.

4. RE: Regional Engineer, Bureau of Reclamation, Mid-Pacific Regional Office, 2800 Cottage Way, Sacramento, CA 95825-1898.

5. CVO: Central Valley Operations Office, Operations Chief, Bureau of Reclamation, 3310 El Camino Ave, Suite 300, Sacramento CA 95821.

6. NCAO: Northern California Area Office, Bureau of Reclamation, 16349 Shasta Dam Boulevard, Shasta, CA 96019-8400.

01 33 00 - 6

7. TSC: Technical Service Center, Bureau of Reclamation, Attn: 86-68170, 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 the 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 the responsible code, but show “Sets to be sent” in Table 01 33 00A – List of Submittals.

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

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

1. Submit in accordance with this section.

2. Submit to CE, unless otherwise specified.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 33 00 - 7

Table 01 33 00A. - List of Submittals

* CE indicates Construction Engineer, COR indicates Contracting Officer’s Representative, OGR indicates Onsite Government Representative, RE indicates Regional Engineer, CVO indicates Central Valley Operations Office, NCAO indicates Northern California Area Office, and TSC indicates Technical Service Center. CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Respon-sible Code

No. of hard copy sets to be sent to:*

CE

COR OGR RE CVO NCAO TSC

01 14 10-1 Use of Site Land Use and Landscape Rehabilitation Plan

At least 28 days before use of Government land

CE 3 CDMS

01 31 30-1 Contract Document Management System

Approval Data Within 7 days after Award

CE 3 1 1 1 1 1 1

01 31 30-2 Contract Document Management System

Final Data Within 14 days of completion of work

CE 3 1 1 1 1 1 1

01 32 10-1 Construction Program

Representative Information

Within 7 days after receipt of Notice of Award

CE 3 CDMS

01 32 10-2 Construction Program

Baseline Schedule

Within 21 days after receipt of Notice to Proceed

CE 3 1 5 1 1 1 3

01 32 10-3 Construction Program

Updated Schedule Reports

With monthly requests for progress payments.

CE 3 CDMS

01 32 10-4 Construction Program

Time Impact Analysis

Within 28 days after the CO directs a contract change with schedule impacts.

Or

With proposal for future modification, value engineering proposal, or requestor claim for equitable adjustment to the contract.

01 33 00 - 8

Table 01 33 00A. - List of Submittals

* CE indicates Construction Engineer, COR indicates Contracting Officer’s Representative, OGR indicates Onsite Government Representative, RE indicates Regional Engineer, CVO indicates Central Valley Operations Office, NCAO indicates Northern California Area Office, and TSC indicates Technical Service Center. CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Respon-sible

01 35 10-1 Safety Data Sheets

Complete LHM and SDS

At least 14 days before jobsite delivery of hazardous material

CE 3 CDMS

01 35 10-2 Safety Data Sheets

Updated LHM and SDS

At least 14 days before jobsite delivery of hazardous material not previously listed

CE 3 CDMS

01 35 20-1 Safety and Health

Safety Program Submitted and accepted before commencing onsite work. See Section 3 of

RSHS.

CE 3 CDMS

01 35 22-1 First-Aid First Aid Facilities Plan

At least 28 days before starting onsite work

CE 3 CDMS

01 35 30-1 Contractor‘s Onsite Safety Personnel

Resume Prior to employment

CE 3 CDMS

01 35 30-2 Contractor’s Onsite Safety Personnel

Safety Inspection Reports

At least once each week

CE 3 CDMS

01 54 20-1 Use of Government Crane

Rigger Qualifications

At least 28 days before beginning onsite work

CDMS

01 55 00-1 Vehicular Access and Parking

Preconstruction Video

At least 28 days before beginning onsite work

CE 3 1 1 1 1 1 0

01 56 10-1 Protection of Existing Installations

Plan for Protecting Existing Installations

At least 28 days before start of onsite construction work

CE 3 CDMS

01 74 00-1 Cleaning and Waste Management

Waste Production and Disposal Plan

At least 28 days before start of onsite work

CE 3 CDMS

01 74 00-2 Cleaning and Waste Management

Waste Production and Disposal Records

Within 7 days of waste disposal

01 33 00 - 9

Table 01 33 00A. - List of Submittals

* CE indicates Construction Engineer, COR indicates Contracting Officer’s Representative, OGR indicates Onsite Government Representative, RE indicates Regional Engineer, CVO indicates Central Valley Operations Office, NCAO indicates Northern California Area Office, and TSC indicates Technical Service Center. CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Respon-sible

01 74 00-3 Cleaning and Waste Management

Environmental Consultant Resume

At least 35 days before beginning environmental assessment

CE 3 CDMS

01 74 00-4 Cleaning and Waste Management

Environmental Site Assessment

Within 14 days of completion of work

CE 3 CDMS

01 78 30-1 Project Record Documents

Final As-built Drawings

Within 14 days of completion of work

CE 3 CDMS

1 1 1 1 1 1

02 83 30-1 Removal and Disposal of Coatings Containing Heavy Metals

Resumes At least 28 days before beginning removal and disposal of coatings containing heavy metals

CE 3 CDMS

02 83 30-2 Removal and Disposal of Coatings Containing Heavy Metals

Written Compliance Program for Worker Protection

At least 28 days before beginning removal and disposal of coatings containing heavy metals

CE 3 CDMS

02 83 30-3 Removal and Disposal of Coatings Containing Heavy Metals

Plans At least 28 days before beginning removal and disposal of coatings containing heavy metals

CE 3 CDMS

02 83 30-4 Removal and Disposal of Coatings Containing Heavy Metals

Certificate of Disposal

Within 7 days of disposal

CE 3 CDMS

03 62 20-1 Nonshrink Grout for Equipment and Metalwork

Packaged Nonshrink Grout Data

At least 28 days before use of nonshrink grout

CE 3 CDMS

22 11 85-1 Generator Air Coolers

Approval Drawings and Data

Within 90 days after receipt of Notice to Proceed

86-68410 3 CDMS

01 33 00 - 10

Table 01 33 00A. - List of Submittals

* CE indicates Construction Engineer, COR indicates Contracting Officer’s Representative, OGR indicates Onsite Government Representative, RE indicates Regional Engineer, CVO indicates Central Valley Operations Office, NCAO indicates Northern California Area Office, and TSC indicates Technical Service Center. CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Respon-sible

22 11 85-2 Generator Air Coolers

Final Drawings and Data

Within 30 days after delivery of coolers

86-68410 3 CDMS

1 1 1 1 1 1

26 05 02-1 Basic Electrical Materials and Methods

Resumes Within 90 days after receipt of Notice to Proceed

86-68410 3 CDMS

26 05 20-1 Conductors and Cables

Approval Data Within 140 days after receipt of Notice to Proceed

86-68410 3 CDMS

26 05 20-2 Conductors and Cables

Field Test Reports

Within 30 days after tests are completed

86-68410 3 CDMS

48 13 25-1 Thrust Bearing High Pressure Lift System

Layouts Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 25-2 Thrust Bearing High Pressure Lift System

Data Sheets Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 25-3 Thrust Bearing High Pressure Lift System

Final Data Within 30 days after delivery of equipment

86-68430 3 CDMS

1 1 1 1 1 1

48 13 62-1 Armature Winding and Stator Core Removal

Pre-Teardown Measurements

Within 30 days after measurements are taken

86-68430 3 CDMS

48 13 62-2 Armature Winding and Stator Core Removal

Work Platform Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 62-3 Armature Winding and Stator Core Removal

Removal Plan and Procedures

Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 64-1 Stator Cores Approval Drawings and Data

Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 64-2 Stator Cores Manufacturing and Factory Test Procedures

Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 64-3 Stator Cores Factory Test Reports

Within 30 days after tests are completed

86-68430 3 CDMS

01 33 00 - 11

Table 01 33 00A. - List of Submittals

* CE indicates Construction Engineer, COR indicates Contracting Officer’s Representative, OGR indicates Onsite Government Representative, RE indicates Regional Engineer, CVO indicates Central Valley Operations Office, NCAO indicates Northern California Area Office, and TSC indicates Technical Service Center. CDMS indicates Contract Document Management System.

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Respon-sible

48 13 64-4 Stator Cores Field Assembly and Test Procedures

Within 150 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 64-5 Stator Cores Final Data Within 60 days after installation

86-68430 3 CDMS

48 13 64-6 Stator Cores Field Test Reports

Within 30 days after tests are completed

86-68430 3 CDMS

48 13 71-1 Armature Windings

Approval Drawings

Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 71-2 Armature Windings

Design Data Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 71-3 Armature Windings

Material Sample Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 71-4 Armature Windings

Factory Test Procedures

Within 90 days after receipt of Notice to Proceed

86-68430 3 CDMS

48 13 71-5 Armature Windings

Factory Test Reports

Within 30 days after tests are completed

86-68430 3 CDMS

48 13 71-6 Armature Windings

Installation Procedure

At least 60 days before installation

86-68430 3 CDMS

48 13 71-7 Armature Windings

Field Test Procedures

At least 60 days before installation

86-68430 3 CDMS

48 13 71-8 Armature Windings

Field Test Reports

Within 30 days after tests are completed

86-68430 3 CDMS

48 13 71-9…