Attachment_1_Specifications.pdf

U.S. Department of the Interior SPECIFICATIONS Bureau of Reclamation Technical Service Center Denver, Colorado JUNE 2017

San Juan Lateral Block 9-11

Navajo-Gallup Water Supply Project New Mexico

U.S. Department of the Interior SPECIFICATIONS Bureau of Reclamation Technical Service Center Denver, Colorado JUNE 2017

This page intentionally left blank.

San Juan Lateral – Block 9-11 Solicitation No.

Table of Contents

00 01 10 - 1

SECTION C - DESCRIPTION/SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 14 10 Use of Site 01 31 19 Project Management and Coordination 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 22 First Aid 01 35 30 Contractor's Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 46 20 Testing Agency Services 01 51 00 Temporary Utilities 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 20 Existing Fences 01 56 32 Temporary Safety Fence 01 57 10 Cross Drainage 01 57 20 Environmental Controls 01 57 30 Water Pollution Control 01 57 40 Pesticides 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 82 20 Removal and Disposal of Asbestos Containing Materials

DIVISION 03 - CONCRETE

03 11 10 Concrete Forming 03 20 00 Concrete Reinforcement 03 30 00 Cast-In-Place Concrete

00 01 10 - 2

03 48 10 Pre-Cast Concrete Manholes 03 63 00 Epoxy Grout

DIVISION 05 - METALS

05 50 00 Metal Fabrications

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 20 Spray-On Insulation 07 21 60 Insulation Jacket

DIVISION 09 - FINISHES

09 96 20 Coatings

DIVISION 10 - SPECIALTIES

10 14 26 Utility Markers

DIVISION 23 – HEATING, VENTILATING, AND AIR-CONDITIONTING (HVAC)

23 33 13 Draft Control Damper

DIVISION 26 - ELECTRICAL

26 42 10 Cathodic Protection and Corrosion Monitoring Systems

DIVISION 31 - EARTHWORK

31 02 10 Water for Dust Abatement 31 02 30 Dust Palliative 31 03 33 Removal of Water from Excavation 31 11 00 Clearing and Grubbing 31 14 10 Stripping, Stockpiling, and Placement 31 23 02 Compacting Earth Materials 31 23 22 Pipe Trench Earthwork 31 23 39 Disposal of Excavated Materials 31 23 70 Controlled Low Strength Materials (CLSM) 31 31 30 Soil-Applied Herbicide

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 15 10 Gravel Surfacing 32 91 60 Erosion Control Blanket

00 01 10 - 3

DIVISION 33 - UTILITIES

33 05 21 Bored Utility and Road Crossings 33 05 23 Maintained and Un-Maintained Road Crossings 33 11 10 Pipeline General Requirements 33 11 12 Steel Line Pipe 33 11 13 Ductile Iron Pipe 33 11 16 PVC Pressure Pipe 33 11 18 HDPE Pressure Pipe 33 11 19 Fiberglass Pipe 33 21 95 Metal Piping for Line Pipe Installations 33 22 15 Valves and Equipment

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 42 35 Bank Protection

DIVISION 51 – INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 10 Crossing Agreements 51 00 20 Surveys

DIVISION 52 - DRAWINGS

52 00 00 Drawings

DIVISION 53 - GEOLOGIC INVESTIGATIONS AND RECORDS

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

END OF SECTION

00 01 10 - 4

Summary Of Work 01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located approximately between 12-40 miles north of Gallup, New Mexico, in San Juan and McKinley Counties, parallel to US 491.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Provide: Approximately 28 miles of 42- to 48-inch water transmission pipe.

1. Valves, air valves, and blowoffs.

2. Wash crossings.

3. Jack and Bore Crossings

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, the words “shall be” are included by inference where a colon (:) is used within the sentence or phrase.

1.04 DEFINITIONS

A. When specifications use a word or term defined in the Federal Acquisition Regulations (FAR), definition of 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

Summary Of Work 01 11 00 - 2

PART 3 EXECUTION

Use Of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (Reclamation)

1. Cleaning Manual 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. Use site on ROW or easements.

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

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

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

3) Utilities including gas, air, power, and water lines; fire hydrants;

and compressor station.

4) First-aid and medical facilities.

5) Concrete, CLSM 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 concrete washouts.

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

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

01 14 10 - 2

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, 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 Federal land made during design and erection stages or after use of Federal land is in operation.

1.04 PROJECT CONDITIONS

A. ROW or Easements as shown on drawings may be used for required construction facilities.

1. Refer to Staging Area drawing 1695-529-60163 for approved location of construction trailers.

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

1. Prior to using land outside of ROW, obtain cultural and environmental approvals in accordance with Section 01 31 19 - Project Management and Coordination.

C. Location, construction, operation, maintenance, and removal of construction facilities on ROW or Easements will be subject to approval of COR.

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

E. See 01 51 00 – Temporary Utilities

F. Housing for construction personnel will not be permitted.

G. Natural Conditions:

1. Ambient Temperature Range: minus 30 degrees C to 40 degrees C.

2. Annual Average Precipitation: 8- to 12-inches

3. Altitude: 6,000 feet.

4. Wind:

a. Maximum sustained: 60 knots.

b. Maximum gust: 75 knots.

01 14 10 - 3

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 CLEANING

A. Construction Equipment:

1. In accordance with Cleaning Manual.

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

3. Contractor cleaning procedures shall result in equipment and vehicles being cleaned as well or better than procedures described in Cleaning Manual.

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

3.02 RESTORATION

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

B. Restore temporary construction roads to original contours and make impassable to vehicular traffic when no longer required.

C. After completion of work, regrade and scarify Easements and ROWs 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

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

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (Reclamation)

1. RSHS Reclamation Safety and Health Standards, including revisions posted at:

www.usbr.gob/ssle/safety/RSHS/rshs.html

1.03 SUBMITTALS

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

B. RSN 01 31 19-1, Written Summary:

1. Written weekly summary of upcoming work, traffic plans and progress meeting minutes.

C. RSN 01 31 19-2, Off ROW Land Use Coordination:

1. Show expanded use location and extent of impact.

2. Request cultural approvals.

a. In accordance with Section 01 57 90 - Preservation of Historical and Archeological Data.

3. Request or revise Environmental Permits. In accordance with:

a. Section 01 57 20 – Environmental Controls.

b. Section 01 57 30 – Water Pollution Control.

c. Section 01 57 50 – Tree and Plant Protection.

d. Section 01 57 60 – Protected Species.

4. Do not use proposed land until approved by COR.

a. Approvals may require up to 6 months.

5. Requirement does not apply to existing commercial facilities.

http://www.usbr.gov/ssle/safety/RSHS/rshs.html

01 31 19 - 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 GENERAL

A. No time extension shall be granted for Contractor’s use of land outside Construction Easement.

3.02 PROJECT COORDINATION

A. Coordinate work with COR, other Bureau of Reclamation (Reclamation) staff, Bureau of Indian Affairs, and other local, state and Federal Agencies as needed.

1. Navajo Nation Water Code Administration and Navajo Nation Environmental Protection Agency.

2. City of Gallup

3. Oil and Gas Companies.

4. Electric Companies.

5. Environmental Services Contractor.

6. Navajo Tribal Utility Authority.

7. Navajo Nation Department of Fish and Wildlife.

8. Cultural Resources Contractor.

B. Facilitate on-site work with above listed agencies.

C. 48-Hour Look Ahead Notification:

1. Provide COR, via email, and phone with a 48 hour notice when Cultural Resource Contractor is required. Contact information will be provided at preconstruction meeting.

3.03 MEETINGS

A. Following meetings are considered significant, but do not relieve Contractor from responsibility of other meetings required by contract.

1. Preconstruction Meeting.

a. Meet with Government prior to start of construction. Provide, as a minimum, Project Manager or Project Superintendent for Preconstruction Meeting. Review will include, but may not be limited to:

1) Use of premises by Contractor, Government, and public.

01 31 19 - 3

2) Construction facilities and controls.

3) Access to work and haul routes.

4) Temporary utilities.

5) Survey layout.

6) Security.

7) Housekeeping procedures.

8) Schedules and sequence of work.

9) Procedures for testing.

10) Procedures for maintaining record documents.

11) Special Site Requirements.

a) Archeological: Refer to Section 01 57 90 - Preservation of Historical and Archaeological Data.

b) Biological: Refer to Section 01 57 60 - Protected Species.

c) Environmental: Refer to:

i. Section 01 57 20 - Environmental Controls.

ii. Section 01 57 30 - Water Pollution Control.

12) Roles and responsibilities:

a) Government organization and personnel.

b) Contractor organization and personnel.

c) Subcontractors.

d) Proposed work schedule.

13) Contract requirements:

a) Progress payments.

b) Invoices.

c) Differing site conditions.

d) Changes.

e) Superintendence by Contractor.

f) Payment for mobilization and preparatory work.

g) Submittal procedures.

h) Emails, faxes, and telephone calls.

2. Preconstruction Safety Meeting:

a. Meet with COR prior to start of construction.

b. Review will include:

01 31 19 - 4

1) Safety requirements.

2) Monthly joint safety policy meetings.

3) Weekly toolbox safety meetings.

4) Safety program.

5) Job hazard analysis.

6) Required safety inspections.

7) Government will monitor Contractor’s operations for compliance with RSHS.

3. Progress Meetings:

a. Meet weekly with Government to review:

1) Progress made.

2) Review As-built drawings.

3) Difficulties in performing work.

4) Resolution necessary to meet specifications requirements.

5) Status of contract documents (RFI’s, submittals, etc.).

6) Three week look ahead.

7) Updating of progress reports.

8) Other items as determined by COR.

b. Develop meeting agenda and minutes, may be used as Written Summary.

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

1.02 DEFINITIONS

A. CDMS: Contract Document Management System.

1. Contract Documents include, but are not limited to:

a. Specifications.

b. Contract Drawings.

c. Submittals.

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

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

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

g. CMs: Contract Modifications.

h. Contractor Proposals.

i. Value Engineering Proposals.

j. Bureau of Reclamation (Reclamation) Inspection Reports.

k. Invoices and Progress Payments.

l. Contract Schedules.

m. Meeting Agendas and Meeting Minutes.

n. Letters and Memos.

1.03 SUBMITTALS

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

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

1. Documentation of system capabilities.

2. Instructions for system use.

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

01 31 30 - 2

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, and Mozilla Firefox, Google Chrome.

2. Ability to upload Contract Documents and make available for user download in supported file formats, minimum:

a. Adobe Acrobat.

b. MS Word.

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

f. Autodesk AutoCAD Civil 3D.

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 to assign user rights which control access to documents based on user class and document type.

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

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

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

01 31 30 - 3

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

Examples:

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

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

c. Alerts (e.g., submittal under review for >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. 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 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:

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.

01 31 30 - 4

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

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

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

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.

01 31 30 - 5

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 a MS Excel spreadsheet.

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.

01 31 30 - 6

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, DIR’s, 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 criteria; 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

Procore, as manufactured by Procore, www.Procore.com, or equal with the following essential characteristics: Capable of performing requirements of Part 1 and Part 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 entrees 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.

http://www.procore.com/

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

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

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

1.02 DEFINITIONS

A. Schedule: 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 critical path of project.

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

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual-04 Construction Planning and Scheduling Manual 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. Furnish schedule and analysis data on DVD or USB drive.

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

01 32 10 - 2

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

1. Designation of authorized representative and COR 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 layout file (.plf).

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

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

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

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

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.

2. Include:

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

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

c. Primavera layout file (.plf).

d. Gantt chart for project on 11- by 17-inch prints 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 project within specified delivery time.

When float changed from previous month’s updated schedule, explain reason for change.

01 32 10 - 3

2) List of Contractor-initiated changes to current schedule stating reason for action taken and unresolved issues relating to Construction Program. Government reserves right to reject Contractor-initiated changes to current schedule which negatively impact Government action which was initiated on 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 submittal. Register fields shall include RSN name and number, date submitted, date of response, status (e.g., approved, partially approved, approved subject to identified changes and resubmit, or not approved).

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 added, changed, or deleted activities.

c. Primavera layout file (.plf).

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

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

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

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

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

01 32 10 - 6

1.08 TIME IMPACT ANALYSIS

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

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

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

C. Float is not for exclusive use by or benefit of either Government or 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.

01 32 10 - 7

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

1.09 REVIEW AND EVALUATION

A. Baseline Schedule:

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

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

b. Upon request from 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 Government.

B. Updated Schedules:

1. Government will require 21 calendar days after receipt of each monthly updated schedule to review and approve or not approve updated schedule.

2. Submit updated schedule at time of submission of each invoice request for progress payment.

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

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

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

1.10 FAILURE TO COMPLY

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

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

PART 2 PRODUCTS

01 32 10 - 8

PART 3 EXECUTION

Submittals 01 33 00 - 1

SECTION 01 33 00

SUBMITTALS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 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

1.03 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 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 submittal does not comply with contract. 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.

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.

a. 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. Print 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 2015 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. Computer drafted.

b. Government will provide an electronic AutoCAD format template.

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

Indicate changes by clouding.

7. Electronic Files: On CD or DVD discs.

D. Product Data:

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

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

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

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

d. Strike through items that do not apply.

E. Certifications:

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

a. Not required for non-design work.

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

F. Manuals:

1. Copies:

a. Printed copies: Bound and indexed.

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

1) Bookmark longer files to assist in navigating file.

2) Electronic files may be submitted as separate parts of a manual.

After each separate electronic file is approved, compile each approved electronic file to assemble an entire manual which shall be consistent with a single final manual submittal.

2. Contents:

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

b. Schematics and wiring diagrams.

01 33 00 - 4

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

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

G. Photographs:

1. Include negatives, or digital files on CD or DVD in .jpeg or similar format.

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 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 “Sets to be sent” column shall be submitted electronically in accordance with Section 01 31 30 - Contract Document Management System.

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals 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 comments, unless otherwise directed.

4. Requirements for initial submittals apply to resubmittals.

1.06 REVIEW OF SUBMITTALS

A. Time Required:

01 33 00 - 5

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

2. Time required for review of each submittal or resubmittal begins when complete sets of materials required for a particular RSN are received and extends through return mailing postmark date.

B. Time in Excess of Specified:

1. CO may extend contract completion date to allow additional time for completing work affected by excess review time.

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

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

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

2. No time extension will be allowed if Contractor fails to make complete action submittals in sequence and within time periods specified.

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

a. Approval was required under the contract, and,

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

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

5. Government will review a submittal and the first resubmittal at no charge.

a. Review of subsequent submittals for the same RSN will be at Contractor’s expense.

b. At the sole discretion of CO, a non-refundable amount equal to the review charges will be deducted from contract price.

c. Currently, charges vary between $74 and $116 per hour, depending upon complexity of submittal and level of expertise required to perform review.

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, partially approved, approved subject to identified changes and resubmit, or not approved.

01 33 00 - 6

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 comply with specifications.

b. Informational submittals that do not comply with specifications may be returned for resubmittal or additional information may be requested.

c. Informational submittals that affect the critical path shown on the baseline schedule may be returned for resubmittal or additional information may be requested.

1.07 HARD COPY OF TRANSMITTALS

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

1. Contracting Officer, Bureau of Reclamation, Attn: UC-840, 125 South State St, Room 6107, Salt Lake City, UT 84138-1147.

2. Construction Engineer, Bureau of Reclamation, 1235 La Plata Hwy, Farmington, New Mexico, 87401.

3. Technical Service Center, Bureau of Reclamation, Attn: 86-68170, PO Box 25007, Denver CO 80225-0007; Express Mail Sixth and Kipling, Building 67, Room 152.

B. Send original transmittal letter with appropriate number of sets to office listed in “Responsible Code” column in Table 01 33 00A - List of Submittals.

1. Responsible codes starting with “86-6” are located in the Technical Service Center. Send these submittals to the TSC address shown above.

C. Send copy of transmittal letter with appropriate number of sets to offices that are not responsible code, but show “Sets to be sent” in Table 01 33 00A - List of Submittals.

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

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

1. Submit in accordance with this section.

2. Submit to CE unless otherwise specified.

01 33 00 - 7

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 33 00 - 8

Table 01 33 00A - List of Submittals

* Submittal types A - Action, I - Information ** CO indicates Contracting Officer, CE indicates Construction Engineer, TSC indicates Technical Service

Center

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Type

Respon-sible code

No of sets to be sent to **

CO CE TSC

I-1 Safety and Health (WBR 1452223-81)

Safety program Submitted and accepted before commencing onsite work See section 3 of

RSHS

A CE CDMS

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

At least 28 days before use of Federal land

A CE CDMS

01 31 19-1 Project Management and Coordination

Written Summary Monthly once on-site construction begins

I CE CDMS

01 31 19-2 Project Management and Coordination

Off ROW Land Use Coordination

At least 6 months prior to use of land

I CE CDMS

01 31 30-1 Contract Document Management System

Approval Data 7 days of after Award

A TSC

86-68510

0 1 1

01 31 30-2 Contract Document Management System

Final Data Within 14 days of completion of work

A CE 0 2 2

01 32 10-1 Construction Program

Representative Information

Within 7 days after receipt of Notice of Award

I CE CDMS

01 32 10-2 Construction Program

Baseline Schedule Within 21 days after receipt of Notice to Proceed

A TSC

86-68510

CDMS

01 32 10-3 Construction Program

Updated Schedule Reports

Monthly or with Progress Payments

A TSC

86-68510

CDMS

01 33 00 - 9

Table 01 33 00A - List of Submittals

* Submittal types A - Action, I - Information ** CO indicates Contracting Officer, CE indicates Construction Engineer, TSC indicates Technical Service

Center

RSN

Clause or

Section Title

Submittals required

Due date or delivery time

Type

Respon-sible code

No of sets to be sent to **

CO CE TSC

01 32 10-4 Construction Program

Time Impact Analysis

Within 28 days after CO directs a contract change,…