DRAFT_Anderson_Ranch_Specs_1.pdf

U.S. Department of the Interior November 2021

Anderson Ranch Powerplant Turbine Modernization and Runner Replacement

Boise Project, Idaho

Columbia-Pacific Northwest Region

Solicitation No. 140R1022R0002

DRAFT

This solicitation issued by Contracting Officer

Columbia Pacific Northwest Interior Region 9 Bureau of Reclamation

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

Phone inquiries regarding this solicitation should be made to Regional Acquisition Management Officer

Telephone Number: (208) 378-5364 DRAFT

Columbia-Pacific Northwest Region Boise Project, Idaho

FOREWORD

Work is located at the Anderson Ranch Powerplant on the South Fork Boise River, approximately 20 miles northeast of Mountain Home, Idaho, in Elmore County. Work includes turbine modernization, refurbishment, and runner replacement.

This page intentionally left blank.

Boise Project, Idaho Solicitation No. 140R1022R0002

Price Schedule

B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND PRICES

ANDERSON RANCH POWERPLANT

TURBINE MODERNIZATION AND RUNNER REPLACEMENT

BOISE PROJECT, IDAHO

B.1 PRICE SCHEDULES

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

(1) Offerors shall complete Price Schedules A and B. Offers for less than the total of Schedules A and B will be considered nonresponsive and will not be evaluated for award.

(2) Offers will be evaluated based on the total of Price Schedules A and B.

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

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

Except as provided in the contract clause at FAR 52.211-18, Variation in Estimated Quantity, no claim shall be made against the Government for overruns or underruns. The contract clause at FAR 52.211-18, Variation in Estimated Quantity does not apply to lump sum items.

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

(e) Definitions:

(1) CLIN – Contract Line Item Number.

B - 2

PRICE SCHEDULE A - UNIT 2

CLIN Section Supplies or Services Quantity and Unit

Unit Price Amount

A-1 1 WBR

1452.232-81

Mobilization and Preparatory Work

For the lump sum of $

A-2 01 31 30 Contract Document Management System

For the lump sum of $

A-3 48 13 00 Turbine Modernization and Runner Replacement

For the lump sum of $

TOTAL FOR PRICE SCHEDULE A $_________________

PRICE SCHEDULE B - UNIT 1

CLIN Section Supplies or Services Quantity and Unit

Unit Price Amount

B-1 2 WBR

1452.232-81

Mobilization and Preparatory Work

For the lump sum of $

B-2 48 13 00 Turbine Modernization and Runner Replacement

For the lump sum of $

TOTAL FOR PRICE SCHEDULE B $_________________

TOTAL FOR PRICE SCHEDULE A+B $_________________

B.2 WARRANTED CHARACTERISTICS

(a) The Offeror warrants that each turbine with new runner shall:

(1) Meet or exceed the weighted efficiency furnished below.

(2) Meet or exceed the power furnished below.

(b) Weighted efficiency:

(1) A: Guaranteed peak efficiency at net head 260 feet ...................... ______percent

a. Weighting factor for full gate efficiency: 30 percent

(2) B: Guaranteed peak efficiency at net head of 300 feet................... ______percent

a. Weighting factor for peak efficiency: 50 percent

(3) C: Guaranteed peak efficiency at net head of 330 feet................... ______percent

B - 3

a. Weighting factor for peak efficiency: 20 percent

(4) D: Warranted weighted efficiency = A x 0.3 + B x 0.5 + C x 0.2... ______percent

a. Minimum warranted weighted efficiency: 93.0 percent

(c) Guaranteed power at B ............................................................................ __________hp

(d) Guaranteed minimum net head for which one turbine will produce 27,500 hp ................................................................................... _________feet

(e) Failure to furnish the required values will result in an incomplete offer, which will not be considered.

(f) The efficiency of turbines with replacement runners installed will be determined from field test data acquired in accordance with the clause in Section E entitled “Performance Tests - Horsepower and Efficiency.”

(g) The contract price will be adjusted in accordance with the clause at WBR 1452.246-81, Failure to Meet Performance Warranties.

END OF SUPPLIES OR SERVICES AND PRICES

B - 4

TECHNICAL SERVICE CENTER

WRITTEN SPECIFICATIONS SIGNATURE SHEET

Specifications Title:

Project Title:

Region:

Prepared: P.E.

Technical Approval: P.E.

Certified: P.E.

Anderson Ranch Powerplant Turbine Modernization and

Runner Replacement

Boise Project

Interior Region 9: Columbia-Pacific Northwest

JESSE BASINSKI

Digitally signed by JESSE

BASINSKI

Date: 2021.08.23 09:33:35 -06'00'

MARK KUMMET

Digitally signed by MARK

KUMMET

Date: 2021.08.23 13:15:31 -06'00'

GERALD HORTON

Digitally signed by GERALD

HORTON

Date: 2021.08.24 16:12:27 -06'00'DRAFT

DIVISION 01 - GENERAL REQUIREMENTS

Summary of Work

01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Anderson Ranch Powerplant is located on the South Fork Boise River, approximately 20 miles northeast of Mountain Home, Idaho, in Elmore County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Vertical Francis Turbine Runner and Wicket Gate:

1. Hydraulic design, computational fluid dynamics (CFD) analysis, hydraulic transient analysis, and report.

2. Furnish and install stainless steel vertical Francis turbine runners, nose cones, and appurtenant components for new runner.

3. Furnish and install stainless steel wicket gates and appurtenant components for new wicket gate.

B. Overhaul Turbine Components:

1. Perform unit signature readings and disassemble.

2. Refurbish embedded components by onsite machining.

3. Refurbish discharge ring, bottom ring, headcover, packing box, operating ring, generator and turbine bearings, gate levers and links, servomotors, brakes, and bearing brackets.

4. Furnish and install new stationary wear and seal rings, wicket gate and operating mechanism bushings and bearings, shear and linkage pins, facing plates and end seals, cooling coils, critical connection fasteners, and shaft sleeves.

5. Rebabbitt turbine and generator bearings.

6. Reassemble and assist commissioning.

1.03 SPECIFICATIONS REQUIREMENTS

A. Requirements in Division 1, General Requirements, apply to Divisions 2 through 52.

B. Imperative statements in these specifications are Contractor requirements, unless otherwise stated.

C. Where specifications are written in streamlined form, words “shall be” are included by inference where a colon (:) is used within sentence or phrase.

Summary of Work

01 11 00 - 2

1.04 DEFINITIONS

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

1.05 ACRONYMS

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

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

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

A. Bureau of Reclamation (Reclamation)

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 https://www.usbr.gov/mussels/prevention/in dex.html

1.03 SUBMITTALS

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

DRAFT

https://www.usbr.gov/mussels/prevention/index.html https://www.usbr.gov/mussels/prevention/index.html

Use of Site 01 14 10 - 2

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.

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

3.01 RESTORATION

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

Work Restrictions and Limitations

01 14 12 - 1

SECTION 01 14 12

WORK RESTRICTIONS AND LIMITATIONS

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 SITE ACCESS

A. Refer to Section 01 55 00 – Vehicular Access and Parking and Section 01 55 20 – Traffic Control.

1.03 ALLOWABLE WORK HOURS

A. Monday through Friday, 7:00 am to 5:00 pm, excluding Federal holidays.

1. May be approved by the COR 72 hours in advance if outside of allowable hours.

2. The Contractor shall only be allowed on site when an authorized Government representative (i.e., Government inspector) is present.

B. Material deliveries and removal of materials, excluding Federal holidays.

1. Restricted to Monday through Friday, 7:00 am to 5:00 pm.

2. May be approved by the COR 72 hours in advance if outside of allowable hours.

3. Inspected by Government before allowed onsite. Coordinate deliveries with COR 24 hours in advance to avoid unanticipated delays.

C. Access gate to the site shall remain locked outside of allowable working hours.

1.04 OTHER CONTRACTS

A. During work under this contract, other work may be performed in vicinity of work by Reclamation and other contractors.

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

C. Do not interfere with work of other contractors or Government in vicinity of work.

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

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

Work Restrictions and Limitations

01 14 12 - 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

Interruption of Service

01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedules for items of work requiring interruption of services.

1.02 SUBMITTALS

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

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

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

2. Outline procedures for accomplishing work including:

a. Specific safety precautions to be taken.

b. Type and location of barricades.

c. Warning signs.

d. Protective grounds and devices to be used.

3. Commencement time of work.

4. Duration of work.

5. Number of personnel and their classification.

6. Description of equipment to be used.

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

1.03 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with COR:

1. Coordinate work with Government operations.

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

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

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

Interruption of Service

01 14 30 - 2

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

4. Interruption of service window available to Contractor: Government will unwater penstocks to accommodate Contractor-requested and approved interruption of service only during the following intervals:

a. Unit 2: September 3, 2024 through May 1, 2025.

b. Unit 1: September 2, 2025 through May 1, 2026.

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

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

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

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

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

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

Project Management and Coordination

01 31 19 - 1

SECTION 01 31 19

PROJECT MANAGEMENT AND COORDINATION

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 PROJECT COORDINATION

A. The following meetings are considered significant, but do not relieve the Contractor from the responsibility of other meetings required by the specifications.

1. Progress Review Meetings:

a. Meeting shall be held weekly at the work site project office. Prepare agenda and distribute 24 hours before the meeting.

b. Prepare and distribute meeting minutes.

c. Attendees: Responsible representatives who have been fully informed of specifications with respect to technical requirements, and coordination necessary to complete construction. Representatives shall be determined on an as needed basis and typically should include:

1) Project Manager from Contractor.

2) Field Superintendent from Contractor.

3) COR and other Representatives from Reclamation.

4) Representatives may attend by telephone or video conference.

d. Purpose:

1) Review, schedule, construction progress, and coordination.

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

b) Review safety, security, environmental, schedule, project issues and concerns, submittals, contractor Requests for Information (RFI), Requests for Proposals (RFP), pending Contract Modifications, and other project related items.

c) Provide 3-week look-ahead schedule at least 24 hours before start of meeting.

d) Review as-built drawings.

Project Management and Coordination

01 31 19 - 2

e) Provide meeting minutes from the previous weekly meeting.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

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

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. DIRs: Daily Inspection Reports

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

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

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

h. CMs: Contract Modifications.

i. Contractor proposal cover page only, submit proprietary information directly to the CO.

j. Value Engineering Proposals.

k. Bureau of Reclamation (Reclamation) Inspection Reports.

l. Invoices and Progress Payments after they have been successfully approved in the Invoice Processing Platform (IPP).

m. Contract Schedules.

n. Meeting Agendas and Meeting Minutes.

o. Letters and Memos.

1.03 SUBMITTALS

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

B. RSN 01 31 30-1, Approval Data:

01 31 30 - 2

1. Documentation of system capabilities.

2. Instructions for system use.

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.

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. Portable Document Format (.pdf).

b. MS Word.

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

f. Drawing (.dwg).

g. Contract Manager.

3. Allow Contract Documents to be prepared by Contractor or by Government.

a. Preparing organization will control access of documents. See Document

Security and Backup paragraph below.

4. Contractor and Government shall each have a project manager for CDMS:

a. Each project manager shall have capabilities to assign users within their organization and assign user rights that control access to documents based on user class and document type.

b. Each organization shall be capable of defining its access hierarchy.

01 31 30 - 3

c. Inclusion of users will be prerogative of organizational project manager.

d. Government shall be able to create and modify project properties (i.e., Contractor, project location, description, bid amount, project directory, etc.).

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

Examples:

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

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

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

6. Ability to link files; examples:

a. RFP linked to a CM.

b. Submittal linked to a Specification or Drawing.

C. Reports:

1. CDMS shall generate reports that list and sort documents by status; examples:

a. Submittals that have been approved.

b. Invoices paid to date.

c. RFIs under review.

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

3. Generate customizable summary reports; examples include:

a. Submittal Turn-around.

b. RFI Turn-Around.

c. CM Processing Turn-Around.

d. Total CM costs.

e. Total CM Request Exposure.

4. Printable, exportable as searchable .pdf or printer -friendly HTML, and exportable to Excel, XML, or CSV.

5. Ability to link from an item in a report directly to the item by clicking on it:

a. For example: in a submittal report, clicking on a submittal that is 15-days old takes you directly to information on that submittal.

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

D. Document Security and Backup:

01 31 30 - 4

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

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

a. Show parties that have access to a document.

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

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

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

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

E. General Tracking and Control:

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

2. CDMS shall track:

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

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

c. When a reviewer has opened an item.

F. Submittal Tracking and Control:

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

2. Customizable standard submittal form for entering information:

a. Required information includes:

1) Required submittal number (RSN), title, description, and specification section.

b. Upload submittal data in electronic format.

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

a. Status designations may be modified to fit Government standard designations – Approved, approved subject to identified changes, or not approved.

4. Supply Submittal Tracking form for Government to enter review comments and action taken. Allow customizing of submittal tracking form:

01 31 30 - 5

a. Allow for Government to route submittal to third parties (e.g., consultant, internal design or operations and maintenance groups, etc.) by generating design-review transmittals with each submittal package item, to track status of individual sub-items within submittal package, and to route each sub-item to the appropriate reviewers.

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

G. RFI Tracking and Control:

1. Supply standard RFI form to enter information.

2. Ability to create or attach documents to the RFI form or links to other documents within CDMS.

3. Ability for Government to route RFI to appropriate reviewers and for reviewers to enter comments into standard response form.

H. Inspection Reports Tracking and Control:

1. Ability to attach Reclamation standard inspection and report forms into CDMS and ability to create customizable inspection forms in CDMS. Typical forms:

a. Daily Inspection Report (DIR).

b. Survey requests.

c. Plant inspection reports.

d. Testing reports.

2. Ability to link or attach photos to forms and link forms to other documents within

CDMS.

I. Contract Modifications:

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

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

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

CDMS.

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

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

J. Cost Tracking and Payment Request Management:

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

01 31 30 - 6

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

K. Correspondence:

1. Ability to generate letters and memos:

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

b. Ability to automatically assign sequential numbers to letters and memos.

2. Ability to generate responses to letters and memos:

a. System automatically generates memo suffixes; e.g., 1st response to Memo

32 to be 32.1, 2nd response to be 32.2, etc.

3. Official correspondence from Reclamation to Contractor shall contain Reclamation's official letterhead and corresponding logos.

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

a. CDMS shall automatically assign sequential meeting numbers.

L. Miscellaneous Tracking and Controls:

1. Ability to generate logs tracking RFIs, CORs, COs, Submittals, Payments, Memos, DIRs, survey requests, plant inspection reports, and testing reports.

2. Ability to filter logs based on criteria, e.g., for Submittals: Specification Section, Days Out, Status (approved, partially approved, approved subject to identified changes and resubmit, or not approved.); for RFI's: Days out, Status (Open/Closed), Specification Section/Dwg No., and Responsibility/Ball-In-Court.

3. Ability to sort logs based on a criterion, e.g., for Submittal, Specification Section, Days Out, Status, or other criteria determined by COR.

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

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

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

7. Ability for keyword search of documents in database.

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

M. Budget and Funding Source Tracking:

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

01 31 30 - 7

PART 2 PRODUCTS

A. Commercially available products having essential characteristics of Parts 1 and 3.

PART 3 EXECUTION

3.01 IMPLEMENTATION

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

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

B. Contractor shall input entries to the Schedule of Submittals before making submittals.

Include:

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

2. Scheduled submittal date.

C. Contractor shall provide a report of submittal status monthly or as requested by COR.

Submittal status report shall be in a table format and include:

1. Required Submittal Number (RSN).

2. Section Title.

3. Submittal Title.

4. Date Submitted.

5. Date of Response.

6. Approval Status (approved, partially approved, approved subject to identified changes and resubmit, or not approved.)

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

01 31 30 - 8

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

1. Developing Baseline Schedule: Include in lump-sum price offered in the Price Schedules 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. CLIN: Contract Line Item Number

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

1.04 SUBMITTALS

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

1. Furnish database files in format compatible with Oracle Primavera P6 Professional Project Management (release 6.2 or newer).

01 32 10 - 2

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

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

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

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Gantt chart (Bar chart) for project in portable document format (.pdf).

d. Primavera layout file (.plf).

e. Cash flow reports.

f. Activity value report.

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

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

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

1. This submittal is required for a proper invoice for progress payments.

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 (Bar chart) for project in portable document format (.pdf).

e. 30-day look-ahead report listing activities and milestones that are scheduled to start, finish, or continue during the next 30-day period.

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

g. Submittal Register:

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

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

3) Update Submittal Register monthly to include submittals and revised submittals.

4) This register document is separate from scheduling database.

h. Cash flow reports.

i. Activity value report.

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 (Bar chart) for project 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. Experience shall include scheduling for at least two other projects of comparable complexity and Primavera P6 training offered by certified instructors.

01 32 10 - 4

1.06 GENERAL

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

1.07 SCHEDULES

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

1. Prepare schedule based on required sequence and interdependence of activities.

Logically sequence activities.

2. Prepare detailed activity network for accomplishing required work organized by Work Breakdown Structure (WBS). Utilize WBS in lieu of activity codes for organization of schedule. If activity codes are utilized in addition to WBS, use unique activity code names assigned as project codes rather than global codes.

3. Activities except “Award” shall have predecessor activities and activities except “Contract Complete” shall have successor activities.

4. Meet contract requirements; milestone(s) in accordance with the clause at FAR 52.211-10, Commencement, Prosecution, and Completion of Work; and relevant clauses and specification sections. Include interim milestone dates, Government interface dates, contract completion date, and other time or seasonal constraints specified in contract documents.

5. Include work of subcontractors, Government interfaces, and contract milestones.

6. Schedule activities to occur as early as possible without unwarranted constraints.

7. Adjust Construction Program/schedule for seasonal weather conditions. Provide a narrative explaining the expected weather and plan for incorporation in schedule.

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

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

Assign weather calendars to work impacted by weather.

8. Reference activities to contract line item number (CLIN) and specification section identified in the Schedule using user-defined fields.

9. Define activities to level of detail resulting in their durations being no greater than 20 workdays unless otherwise accepted by CO.

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.

10. Include separate activities for submittal preparation and submittal reviews as identified by Required Submittal Number (RSN) as listed in the Submittal Requirements for submittals identified by “Yes” in column labeled “CP” of the table. Assign Government submittal review activities to a seven-day calendar

01 32 10 - 5 with durations as specified in Section 01 33 00 - Submittals. Include RSN in activity description.

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

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

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

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

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

16. Use durations in units of whole workdays.

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

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

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

B. Baseline Schedule:

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

C. Updated Schedule:

1. Meet monthly with COR at Government’s project office, 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 or percent complete for each activity started but not completed during the period.

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

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

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

01 32 10 - 6

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

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

1.08 TIME IMPACT ANALYSIS

A. Provide time impact analysis for contract changes, proposed modifications, or value engineering change proposals to support a claim or request for equitable adjustment to the contract due to a 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. Prepare a single time impact analysis for modifications issued after Notice to Proceed (NTP) and prior to approval update.

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

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

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

a. Show contract milestones and activities whose periods of performance have shifted as result of change which affects production and/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.

01 32 10 - 7

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 is 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. Upon request from the CO, meet with COR for a joint review of the proposed baseline schedule.

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

B. Updated schedules:

1. Submit updated schedule monthly.

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

3. If the updated schedule is disapproved, revise and resubmit updated schedule within seven days following the date of the rejection letter.

4. The Contractor shall schedule a pre-submittal meeting with the COR each month to review a draft updated schedule prior to the Contractor submitting RSN 01 32 10-3, Updated Schedule.

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

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

PART 2 PRODUCTS

Not Used

01 32 10 - 8

PART 3 EXECUTION

Not Used

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 DEFINITIONS

A. Days: Calendar days.

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

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

1. A - Action:

a. Government will respond as to adequacy of submittal.

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

2. I - Informational:

a. Government will acknowledge receipt of Informational submittals.

b. Government may reject an Informational submittal when the submittal does not comply with the contract requirements. Contractor shall correct mistakes or deficiencies in rejected Informational submittals and resubmit.

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

1.03 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

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

B. National Institute of Building Sciences (NIBS)

1. NIBS NCS-14 United States National CAD Standards, Version 6

01 33 00 - 2

1.04 SUBMITTAL REQUIREMENTS

A. In case of conflict between requirements of this section and requirements included elsewhere in these specifications, requirements included elsewhere take precedence.

B. General:

1. Prepare in English.

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

3. Measurement Units: US Customary Units.

4. Provide a unique transmittal number for each submittal.

C. Drawings:

1. Minimum Identification in Title Block:

a. Contract number and title.

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

c. Date.

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

3. Size: D size (22 inches by 34 inches) as defined by ASME Y14.1.

4. Draw to scale using computer drafting or drafting equipment, unless otherwise specified.

a. Computer drafted drawings:

1) In accordance with NIBS NCS.

2) Electronic file format: Compatible with AUTOCAD, Version

2021 or later.

3) Compile using “eTransmit” utility in AUTOCAD.

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

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

a. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

c. Title block and sheet format:

1) As shown on Standard Drawing 40-D-7102.

2) Government will provide template.

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

01 33 00 - 3

6. Final Drawings:

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

Indicate changes by clouding.

b. File Format: Portable document format: PDF.

7. Final Electronic Drawings: When final electronic drawings are required.

a. Drawing format: AUTOCAD, Version 2021 or later, or as approved by the COR.

b. Compile using ‘eTransmit’ utility in AutoCAD.

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

Indicate changes by clouding.

D. Product Data:

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

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

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

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

d. Strike through items that do not apply.

E. Certifications:

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

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

F. Manuals:

1. Copies:

a. Printed copies: Bound and indexed.

b. Electronic copies: Adobe pdf.

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

01 33 00 - 4

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

G. Photographs:

1. When requested.

2. Each COR requested view.

a. Include contract number, name of equipment and view title.

3. Format:

a. Digital Photographs in jpeg format. Four Megapixels minimum. With accompanied prints if requested and of a size requested by the COR.

b. Prints: Only if specifically requested.

1) Professional quality 8- by 10 inch color.

2) Identify with adhesive labels on back.

a) Do not type directly on back of photograph.

H. Samples and Color Selection Submittals:

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

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

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

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

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

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

1.05 SUBMITTALS PROCEDURES

A. Submit only checked submittals. 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.

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.

01 33 00 - 5

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals not approved:

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

2. Describe reasons for significant changes in transmittal letter.

3. Resubmit returned submittals within 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 responsible code is 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. CO may extend the contract completion date to allow additional time for completing work affected by excess review time.

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

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

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

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

01 33 00 - 6

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. Return of submittals will be by CDMS response or hard copy, as applicable.

2. Action Submittals: 1 set of submittals required for action will be returned either approved, approved subject to identified changes, or not approved.

a. Revise and resubmit submittals not approved.

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

3. Informational Submittals: Government will acknowledge Informational submittals.

a. Informational submittals will not be returned when they satisfy contract requirements.

b. Informational submittals that do not satisfy contract requirements may be returned for resubmittal or additional information may be requested.

1.07 HARD COPY TRANSMITTALS

A. Transmit hard copies of transmittals when required by Table 01 33 00A - List of Submittals…