Attachment_1_140R4024R0020_Specifications_90_.pdf

U.S. Department of the Interior 90% SPECIFICATIONS Bureau of Reclamation Technical Service Center Denver, Colorado September 2024

Hyrum Dam Spillway Replacement

Hyrum, Utah

U.S. Department of the Interior 90% SPECIFICATIONS Bureau of Reclamation Technical Service Center Denver, Colorado September 2024

This page intentionally left blank.

HYRUM DAM SPILLWAY REPLACEMENT

HYRUM PROJECT

UPPER COLORADO REGION, UTAH

FOREWORD

Work is for constructing a new spillway at Hyrum Dam. Work is located on Little Bear River just south of Hyrum City, Utah.

Principle features of work include: construction of a new spillway and radial gates, a new stilling basin, two new siphons, and a new precast concrete beam bridge.

Hyrum Dam Spillway Replacement Hyrum Project, Utah

Price Schedule

B - 10

Table of Contents

00 01 10 - 1

SECTION C - DESCRIPTION / SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 14 10 Use of Site 01 14 12 Work Restrictions and Limitations 01 31 19 Project Management and Coordination 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 26 Electrical Drawings and Data 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 30 Contractor’s Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 46 20 Testing Agency Services 01 51 00 Temporary Utilities 01 52 10 Field Office 01 55 00 Vehicular Access and Parking 01 55 20 Traffic Control 01 56 10 Protection of Existing Installations 01 56 15 Protection of Existing Utilities 01 56 32 Temporary Safety Fence 01 57 20 Environmental Controls 01 57 30 Water Pollution Control 01 57 50 Tree and Plant Protection 01 57 60 Protected Species 01 57 90 Preservation of Historical and Archeological Data 01 60 00 Product Requirements 01 71 20 Surveying 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents

DIVISION 02 - EXISTING CONDITIONS

02 41 07 Removal and Disposal of Existing Features 02 83 33 Removal and Disposal of Equipment with Coatings Containing Regulated Metals

DIVISION 03 - CONCRETE

03 11 10 Concrete Forming

00 01 10 - 2

03 15 12 PVC Waterstops 03 20 00 Concrete Reinforcing 03 30 00 Cast-In-Place Concrete 03 30 39 Full-Depth Precast Concrete Deck Panels 03 41 33 Precast Pretensioned Bridge Beams 03 62 20 Nonshrink Grout for Equipment and Metalwork 03 81 10 Concrete Removal

DIVISION 05 - METALS

05 50 00 Metal Fabrications

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 20 Extruded Polystyrene Rigid Foam Insulation 07 41 13 Insulated Metal Roof Panels 07 42 13 Pre-Insulated Metal Wall Panels 07 92 00 Joint Sealants

DIVISION 08 - OPENINGS

08 11 10 Steel Doors and Frames 08 31 20 Floor Access Hatches 08 51 10 Aluminum Windows 08 71 00 Door Hardware

DIVISION 09 - FINISHES

09 96 20 Coatings

DIVISION 10 – SPECIALTIES

10 44 20 Fire Extinguishers

DIVISION 13 - SPECIAL CONSTRUCTION

13 34 20 Metal Building System

DIVISION 26 - ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 10 Conductors and Cables 26 05 20 Grounding and Bonding 26 05 33 Conduit 26 05 90 Wiring Checkout and Tests 26 22 16 Transformer Load Center

00 01 10 - 3

26 24 20 Panelboards 26 27 30 Wiring Devices 26 28 20 Service Disconnect Switch 26 32 10 Diesel Engine-Generator Set 26 36 22 Manual Transfer Switch 26 42 13 Submerged Galvanic Anode Cathodic Protection 26 51 00 Interior Lighting 26 56 00 Exterior Lighting

DIVISION 31 - EARTHWORK

31 02 10 Water for Dust Abatement 31 03 23 Cofferdam Construction 31 03 33 Removal and Control of Water 31 09 10 Abandoning Existing Piezometers 31 09 26 Measurement Points 31 11 00 Clearing and Grubbing 31 14 10 Stripping 31 23 00 Compacting Earth Materials 31 23 22 Pipe Trench Earthwork 31 23 30 Excavation 31 23 51 Sand Filter 31 23 52 Gravel Drain 31 23 54 Miscellaneous Fill 31 23 56 Structural Fill 31 23 70 Controlled Low Strength material 31 24 10 Impervious Fill 31 24 20 Embankment Construction 31 32 26 Aggregate Piers 31 32 32 Geotextile 31 32 52 Inspection Wells 31 37 00 Riprap 31 37 10 Riprap Bedding 31 41 16 Steel Sheet Piles 31 56 20 Cutoff

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 12 00 Roads 32 15 10 Gravel Surfacing 32 31 10 Chain Link Fence 32 31 30 Wire Fence 32 91 19 Placing Topsoil 32 91 60 Topsoil Erosion Control Matting 32 92 20 Seeding

DIVISION 33 - UTILITIES

00 01 10 - 4

33 05 31 Precast Concrete Pressure Manholes 33 05 33 Spillway Stilling Well 33 11 10 Pipeline General Requirements 33 11 14 Reinforced Concrete Pressure Pipe 33 11 16 PVC Pressure Pipe Hyrum Feeder Pipeline 33 46 36 Drain Pipes 33 46 42 Perimeter Drain Weir Boxes

DIVISION 34 – TRANSPORTATION

34 71 10 W-Beam Guardrails

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 21 20 Stoplog Guides 35 23 50 Spillway Radial Gates 35 69 20 Safety Cable with Floats

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 32 Radial Gate Hoists

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 02 82 Hazardous Materials Survey and Analytical Results

DIVISION 52 - DRAWINGS

52 00 00 Drawings

DIVISION 53 - GEOLOGIC INVESTIGATIONS AND RECORDS

53 20 00 Geologic Investigations 53 30 00 Records of Geologic and Subsurface Investigations

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 on the Little Bear River immediately south-west of Hyrum City, Utah.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Construction includes:

1. Re-grade reservoir rim between the spillway and the dam

2. Excavation for a new spillway

3. Construction of a cofferdam for the new spillway

4. Constructing a new spillway

5. New gates and hoists

6. New hoist enclosure

7. New spillway chute and stilling basin

8. Embankment dike

9. Dewatering system

10. Aggregate pier foundation treatment

11. Two new siphons

12. New precast concrete beam bridge

13. County road realignment construction

14. Rerouting two access roads

15. Mechanical and electrical equipment

16. Construction of a cofferdam for existing spillway removal

17. Excavation and removal of existing spillway

Summary of Work

01 11 00 - 2

1.03 SPECIFICATIONS REQUIREMENTS

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

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.

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

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 (USBR)

1. Cleaning Manual-2012 Inspection and Cleaning Manual for

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

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

1.03 SUBMITTALS

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

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

1. For each Contractor use site on Government land.

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

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

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

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

4) First-aid and medical facilities.

5) Concrete and aggregate plants. Show sizes, rated capacities, and general features of aggregate processing plant including transporting, storing, screening, and washing facilities; concrete batching and mixing plant; and concrete conveying, placing, and cooling plants.

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

01 14 10 - 2

6) Areas for processing, storing, and disposing of waste materials from construction operations.

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

1.04 PROJECT CONDITIONS

A. Government land as shown on drawings may be used for required construction facilities, as approved by the COR.

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. Areas on Government land which will be obliterated by permanent construction or inundated by reservoir may be used where use of such land will be discontinued and construction facilities, materials, equipment, and rubbish and waste materials will be removed to avoid interference with work in such areas or with filling of reservoir.

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

01 14 10 - 3

PART 3 EXECUTION

3.01 CLEANING

A. Construction equipment:

1. Before bringing on site, clean construction equipment to remove dirt, vegetation, and other organic material to prevent introduction of noxious weeds, and invasive plant and animal species.

2. Contractor cleaning procedures shall result in equipment being cleaned as well or better than the procedures described in Cleaning Manual.

3. COR will inspect construction equipment following procedures described in Cleaning Manual before allowing equipment onsite.

3.02 RESTORATION

A. Restore Contractor use areas to pre-construction condition or as approved by COR.

B. After completion of work, regrade and scarify Government land used for construction purposes and not required for completed installation so that surfaces blend with natural terrain and are in a condition that will facilitate revegetation, provide proper drainage, and prevent erosion.

01 14 10 - 4

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

1.02 WORK RESTRICTIONS AND LIMITATIONS

A. Construction Requirements:

1. Reservoir rim excavation with 3:1 slope shall occur when the reservoir is below the lowest point of the excavation.

2. New Spillway Cofferdam sheet piles shall be in place to the lines and grades shown on drawings and sand drains shall be installed to the lowest elevation shown on drawings prior to excavating spillway foundation soils below elevation 4675 feet between new spillway station 5+00 and cofferdam alignment.

a. Slope protection riprap and cofferdam berm shall be in place prior to

January 1 of the calendar year following sheet pile installation.

3. The outlet channel downstream of the existing stilling basin Station 12+60 shall not be constructed until the new spillway stilling basin is complete and approved by COR.

4. New siphon for the East Field Canal must be connected during the non-irrigation season unless otherwise approved by COR.

5. New siphon for the Hyrum Feeder Canal must be connected during the non-irrigation season unless otherwise approved by COR.

6. Existing Spillway Demolition and Dike Construction:

a. Existing spillway shall remain operational during entire duration of construction of the new spillway. Do not begin demolition without approval by CO.

b. The new spillway and channel shall be fully operational before any work on the existing spillway excavation, modifications and embankment dike construction can begin.

c. A Contractor designed cofferdam to remove the existing spillway in accordance with Section 31 03 23 – Cofferdam Construction may be required depending on the Contractors means and methods.

01 14 12 - 2

d. Removal of the existing spillway and dike construction from station 2+77 to the Existing Stilling Basin shall be completed prior to any demolition of the existing spillway crest structure or gates.

e. Protect dike construction from reservoir water and wave action until dike completion to the lines and grades shown on drawings.

f. Contractor may attempt to sequence items of the work specified below Top of Active Conservation when the reservoir is low but Government makes no guarantee of reservoir levels outside of restrictions stated in Section 01 14 20 – Reservoir Operations for additional requirements and limitations.

7. Sloping concrete floor slab panels between stations 11+25 (beginning location) and 3+73 must be placed consecutively from downstream to upstream.

a. Stilling basin floor slab panels between station 11+25 and 11+47.50 must be placed before starting sloping concrete floor panels directly upstream of those stilling basin floor panels.

b. Additional beginning locations, Slab Junctions (SJ), for placement of the sloping concrete floor slab panels will be allowed as follows at the request of the Contractor:

1) Sloping concrete floor slab panels working from these SJ’s must be placed consecutively working in the upstream direction only.

2) The cutoff walls at each SJ location must be constructed before adjacent slab placements can begin, including:

a) Impervious fill directly downstream of the cutoff wall.

b) Drain pipe, sand and gravel materials, and polystyrene insulation downstream of the cutoff wall of sufficient length to tie into for placement of the closure section slab.

c) Mud mat downstream of the cutoff wall of sufficient length to protect materials listed in a) and b) above.

3) SJ’s are allowed at joints at station 4+63.00 and station 6+34.50.

4) Closure section slabs, directly downstream of an SJ, may only be placed once the sloping concrete floor slabs have been placed sequentially upstream such that this slab is the last of these panels to be placed.

5) Use of one or both of the SJ’s as outlined must be requested included in RSN 03 30 00-2, Concrete Placement Drawings and RSN 03 30 00-3, Concrete Placement Schedule.

8. Installation of drainage and mudmat within each panel shall be completed prior to concrete placement.

01 14 12 - 3

9. Contractor shall provide access to the existing stilling basin and downstream property for Reclamation employees and downstream landowner during the entirety of construction.

10. If reservoir ice loading occurs on the New Spillway Cofferdam above elevation 4669 feet an emergency berm shall be constructed abutting the sheet piles as shown on the drawings before any portion of ice abutting the sheet piles reaches 12-inches in thickness.

B. Allowable Work Hours: 7 am to 10 pm, 7 days a week unless otherwise approved by the

COR.

C. Prior to closing the road on the crest of Hyrum Dam and Dike, install the detour signs in accordance with Section 01 55 20 – Traffic Control.

D. Access to and from the Disposal site is restricted to routes shown on the Drawings.

E. Reservoir operations are limited and will not be adjusted to lower reservoir elevations to accommodate construction activities.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 14 12 - 4

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

A. The Government anticipates other contractors working in the same general site location.

1. Includes removal of existing overhead power lines and replacement with new underground electrical conductor, as shown on drawings and described in Section 26 05 06 – Electrical Project Coordination.

B. The Contractor shall coordinate work with the Government, other contractors, and other agencies in the vicinity in accordance with WBR 1452.236-8 Other Contracts.

1.03 SUBMITTALS

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

B. RSN 01 31 19-1, Weekly Coordination Meeting Documentation:

1. Provide meeting agenda.

2. 3-week look-ahead schedule covering construction review items and tasks.

3. Work completed to date.

4. Meeting minutes from the previous weekly coordination meeting to include:

a. Date, time, and list of attendees.

b. Summary of topics discussed.

c. List of action items including:

1) Description of action item.

2) Responsible party.

3) Date to be completed.

1.04 SPECIFICATION DRAWINGS

A. AutoCAD files of specification drawings are available to the Contractor.

1. Contractor shall provide a written request with the requested drawing numbers.

01 31 19 - 2

2. Government will make these files available to Contractor within 21 days after the request is received.

1.05 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. Pre-Construction Readiness Review Meeting:

a. Six weeks after Award, an in-person Readiness Review Meeting will be held in Cle Elum, Washington to review the contract requirements and associated pre-mobilization tasks.

b. The meeting is expected to begin at 8:00 A.M. local time, include a site visit, and last the entire day.

c. An agenda, including proposed dates, will be provided by the Government within 2 weeks of Award.

d. Environmental awareness training will be provided to all in attendance.

e. At a minimum, the following personnel will attend:

1) Contractor’s personnel:

a) Owner or Owner’s Representative.

b) Project Manager.

c) Project Engineer or responsible engineering representative who understands these specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete work.

d) On-site Superintendent(s).

e) Key Subcontractor personnel.

f) Additional personnel that Contractor considers necessary.

2) Government personnel:

a) Contracting Officer.

b) Contracting Officer’s Representative.

c) Design Engineer(s).

d) Project Manager.

e) Environmental, Biological, and/or Cultural Specialists.

f. The meeting will be recorded for contractual purposes and meeting minutes published for review.

2. Weekly Construction Coordination Meetings:

01 31 19 - 3

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 a meeting agenda

c. Prepare and distribute meeting minutes.

d. 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 Bureau of Reclamation.

e. Representatives may attend by telephone and / or video conference.

f. Purpose: Review, schedule, construction progress, and coordination

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

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

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

4) Review as-built drawings.

5) Provide meeting minutes from the previous weekly meeting.

6) Review data that activities were started and completed, remaining duration, and percent complete.

3. Environmental Awareness Meetings and Training:

a. Environmental awareness training is required for all employees, contractors, and site visitors to educate on-site personnel about sensitive resources.

1) Reclamation’s qualified professional along with the Contractor will conduct training.

2) Contractor must provide a one week notice to Reclamation in advance of holding training.

3) Training shall be held on site unless Reclamation makes other arrangements.

b. This program will include, but not be limited to, special status species information and conservation; worker compliance responsibilities;

01 31 19 - 4 noncompliance penalties or significant risks of litigation; and best management practices (BMPs) and conservation measures described in this section, such as project speed limits, weed control, avoidance of wildlife buffers, species reporting, debris control, hazardous waste management, wetland protection, hazardous waste and spill containment, and permit stipulations; cultural resource protocols and protection, and historic built environment requirements.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

A. Cooperate and coordinate use of access routes, water supplies, staging areas; maintaining roads, dust-free operations; complying with environmental requirements; complying with permit requirements and abiding by applicable safety regulations.

Contract Document Management System

01 31 30 - 1

SECTION 01 31 30

CONTRACT DOCUMENT MANAGEMENT SYSTEM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Contract Document Management System:

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

1.02 DEFINITIONS

A. Accepted RSNs: A copy of the Contractor’s transmittal sheet marked “Accepted” is enclosed and returned to the Contractor. Accepted comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of the Contractor’s responsibility for the accuracy, completeness and correctness of details, nor of complying with the contract requirements. Acceptance shall not relieve the Contractor of the Contractor’s responsibility for compliance with Federal Acquisition Regulation 52.236-21, Specifications and Drawings for Construction. This completes all of the requirements under this Submittal. Proposed changes to accepted submittals shall be submitted and accepted before being implemented.

B. Approved RSNs “A”: A copy of the Contractor’s transmittal sheet marked “Approved” is enclosed and returned to the Contractor. Approval comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of their responsibility for the accuracy, completeness, and correctness of details, nor of complying with the contract requirements. Approval shall not relieve the Contractor of their responsibility for compliance with Federal Acquisition Regulation 52.236-21, Specifications and Drawings for Construction.

1. Rarely an RSN will be returned with comments. The comments are intended to clarify specific interpretations or RSN language and shall not direct the Contractor’s work and shall not relieve the Contractor of their responsibility for the accuracy, completeness, and correctness of details, nor of complying with the contract requirements. Approval with comments shall not relieve the Contractor of their responsibility for compliance with Federal Acquisition Regulation 52.236-21, Specifications and Drawings for Construction.

C. Conditionally Accepted RSNs: A copy of the Contractor’s transmittal sheet marked “Conditionally Accepted” is enclosed and returned to the Contractor with comments.

Conditionally accepted comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of the Contractor’s responsibility for the accuracy, completeness and correctness of details, nor of complying with the contract requirements. Conditional acceptance shall not relieve the Contractor of responsibility for compliance with Federal Acquisition Regulation 52.236-21, Specifications and Drawings for Construction.

01 31 30 - 2

D. Conditionally Approved RSNs: A copy of the Contractor’s transmittal sheet marked “Conditionally Approved” is enclosed and returned to the Contractor with comments.

Conditionally approved comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of the Contractor’s responsibility for the accuracy, completeness and correctness of details, nor of complying with the contract requirements. Conditional approval shall not relieve the Contractor of responsibility for compliance with Federal Acquisition Regulation 52.236-21, Specifications and Drawings for Construction.

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

j. Government Inspection Reports.

k. Invoices and Progress Payments.

l. Contract Schedules.

m. Meeting Agendas and Meeting Minutes.

n. Letters and Memos.

F. Not Accepted RSNs: A copy/Copies of the Contractor’s transmittal sheet/sheets marked “Not Accepted” is/are enclosed. Comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of the Contractor’s responsibility for the accuracy, completeness, and correctness of details, nor of complying with the contract requirements.

G. Not Approved RSNs: A copy/Copies of the Contractor’s transmittal sheet/sheets marked “Not Approved” is/are enclosed. Comments and conditions are not intended to direct the Contractor’s work and shall not relieve the Contractor of the Contractor’s responsibility for the accuracy, completeness and correctness of details, nor of complying with the contract requirements.

1.03 SUBMITTALS

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

01 31 30 - 3

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:

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 or Oracle Primavera P6 Project Manager.

e. Autodesk AutoCAD Civil 3D.

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

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

Security and Backup paragraph below.

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

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

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

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

01 31 30 - 4

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 greater than 15 calendar 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, or CSV.

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

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

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

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.

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, Payments, 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/CAR/NA/Acc/CAcc/NAcc (Approved/Conditionally Approved, Resubmit/Not Approved, Accepted, Conditionally Accepted, Not Accepted).

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

01 31 30 - 6

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.

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.

a. Submittals: Specification Section, Days Out, Status

(A/CAR/NA/Acc/CAcc/NAcc).

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

CDMS.

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

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

J. Cost Tracking and Payment Request Management:

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

01 31 30 - 7

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

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

a. CDMS shall automatically assign sequential meeting numbers.

L. Miscellaneous Tracking and Controls. Ability to:

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

2. Filter logs based on criteria:

a. Submittals: Specification Section, Days Out, Status (A/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 and Progress Payment 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.

8. Allow online Payment Requests by Contractor.

M. Budget and Funding Source Tracking:

01 31 30 - 8

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:

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

2. Scheduled submittal date.

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

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

1. Required Submittal Number (RSN).

2. Section Title.

3. Submittal Title.

4. Date Submitted.

5. Date of Response.

6. Approval Status (Approved/Conditionally Approved, Resubmit/Not Approved, Accepted, Conditionally Accepted, Not Accepted).

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

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

Schedule A for Mobilization and Preparatory Work.

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

1.02 DEFINITIONS

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

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

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling

Manual, 2004

1.04 SUBMITTALS

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

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

Professional Project Management.

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

Construction Program to the CO.

01 32 10 - 2

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

1. Designation of authorized representative to develop and maintain Construction

Program. Include resume with training and experience.

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Primavera P6 layout file (.plf).

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

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

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

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

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

1. This submittal is required for a proper invoice for progress payments in accordance with the clauses at FAR 52.232-27 - Prompt Payment for Construction Contracts and WBR 1452.232-82 - Other Invoice Requirements. In accordance with subparagraph (a)(i)(A) of the clause at FAR 52.232-27 - Prompt Payment for Construction Contracts, Government disapproval of this submittal will be considered failure of the Contractor to comply with contract requirements and payment due date may be delayed until 14 days after submittal contents are approved.

2. Include:

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

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

c. Primavera P6 layout file (.plf).

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

e. Narrative report specifically stating status of project.

1) When negative float exists, cite specific actions and conditions which caused "behind schedule" condition and provide proposed course of action to complete the project within the specified

01 32 10 - 3 delivery time. When float changed from previous month’s updated schedule, explain reason for change.

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

3) Discuss contract milestones and significant activities that were started, continued, or completed during the update period or scheduled during the next update period.

f. Submittal Register:

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

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

3) This register document is separate from scheduling database.

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

1. Include:

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

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

c. Primavera P6 layout file (.plf).

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

e. Narrative report explaining results and conclusions.

1.05 QUALIFICATIONS

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

1.06 GENERAL

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

01 32 10 - 4

1.07 SCHEDULES

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

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

Logically sequence activities.

2. Prepare detailed activity network for accomplishing required work organized by

Work Breakdown Structure (WBS). Utilize WBS in lieu of activity codes for organization of schedule. If activity codes are utilized in addition to WBS, use unique activity code names assigned as project codes rather than global codes.

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

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

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

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

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

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

Assign weather calendars to work impacted by weather.

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

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

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

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

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

01 32 10 - 5

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

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

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

14. Use durations in units of whole workdays.

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

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

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

B. Baseline Schedule:

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

C. Updated Schedule:

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

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

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

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

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

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

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

1.08 TIME IMPACT ANALYSIS

A. Provide time impact analysis for contract changes (e.g., change order, proposed modification, or value engineering change proposal) to support a claim or request for equitable adjustment to the contract due to delay or accelerated schedule.

01 32 10 - 6

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

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

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

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

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

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

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

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

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

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

1) Activity description.

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

3) Activity duration.

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

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.

01 32 10 - 7

1.09 REVIEW AND EVALUATION

A. Baseline Schedule:

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

a. CO will approve or not approve proposed baseline schedule.

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

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

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

B. Updated schedules:

1. Submit updated Construction Program schedule monthly.

2. Submit…