FINAL_Source_Sought_-_HH_Potable_Water_Conveyance_System_(v2_--_12-1-2023)_3.pdf

SOURCES SOUGHT

140R10-24-B-0001 -- Hungry Horse Potable Water Conveyance System

This is a Sources Sought announcement only. THIS IS NOT A REQUEST FOR PROPOSALS, QUOTATIONS OR BIDS, NOR A PROPOSED SYNOPSIS OF A PROPOSED CONTRACT

ACTION UNDER FAR SUBPART 5.2 and no contract shall be awarded from this notice. No reimbursement will be made for any costs associated with providing information in response to this Sources Sought or any follow up information requests. No solicitation is currently available.

The responses to this Sources Sought will help to shape the acquisition strategy in developing a competitive requirement.

The Columbia-Pacific Northwest (CPN) Regional Office of the U.S. Bureau of Reclamation is conducting market research for a Construction contract. The work is located at Hungry Horse

Dam and Power Plant approximately 20 miles northeast of Kalispell, Montana, 8 miles southeast of Columbia Falls, Montana in Flathead County.

The DRAFT work specifications (500 pages) are attached. No support drawings are currently available for this sources sought notice. Please note this specification package is subject to change prior to future Invitation for Bid (IFB) issuance.

Principle components of work for this Hungry Horse Potable Water Conveyance System essentially includes:

1 Converting test well into a production water well

2 Install new water main from well site location to Hungry Horse Dam

3 Install new water main inside the Hungry Horse Dam and make existing potable water piping connections.

4 Replace existing electrical panels, conductors, and miscellaneous items, appurtenances, and devices incidental to or necessary for a sound, secure, complete, and functional

Potable Water Conveyance System.

The magnitude of this requirement is estimated between $1,000,000 and $5,000,000.

Sources are being sought for firms with a North American Industry Classification System

(NAICS) code 237110 – Water and Sewer Line and Related Structures Construction, PSC code Z2KA and with a Small Business Size Standard of $45 million.

NAICS code 237110 is on the list of codes for Women-Owned Small Business firms. The purpose of this sources sought announcement is to gain knowledge of potentially qualified Small

Business, 8(a), Woman Owned Small Business, Service-Disabled Veteran Owned Small

Business, HUBZone and Indian Small Business Economic Enterprise (ISBEE) contractor sources. Small businesses are highly encouraged to respond to this sources sought notice. After review of the responses to this announcement and if the Government still plans to proceed with this project; a separate IFB solicitation announcement will be published on www.Sam.Gov.

Responses to this announcement are not an adequate response to any future solicitation announcement.

SOURCES SOUGHT

140R10-24-B-0001 -- Hungry Horse Potable Water Conveyance System

Responses are requested to review the attached DRAFT specifications and submit responses to the following. Information shall not exceed a total of 10 (ten) pages:

1. Contact information: Offerors’ name, address, Unique Entity ID (formerly DUNS), CAGE

Code, points of contact with telephone numbers and e-mail addresses.

2. Capabilities Statement: A description of capabilities in providing:

a) Minimum required capabilities described in the attached DRAFT specifications.

b) Experience. Previous procurement(s)/past performance information, including contract numbers, and customers is highly recommend/encouraged.

◼ If submitting past performance/experience on a project in the role of a subcontractor, include the Prime Contractor’s name and a quantifiable amount

(percentage) of the project your company contributed to the overall scope of work.

Prime Contractor experience is preferred but not required.

3. Business Status (based on NAICS 237110): Please indicate the business size and status of your company to include any/all additional designations as Small Business, HUBZone, Woman

Owned, Indian Small Business Economic Enterprise (ISBEE), Service-Disabled Veteran Owned, or Small Disadvantaged Business, etc. shall be indicated on first page of submission.

* Note: Large Business concerns need not respond.

4. General questions(s): If any, relating to the attached DRAFT PWS that need to be clarified prior to release of an Invitation for Bid (IFB).

Please provide the request above information no later than 3:00 PM Mountain Time on

January 31, 2024. Responses will not be returned. No responses will be accepted by facsimile.

In addition, telephonic responses will not be honored. Please respond by email only. Send responses to Contract Specialist, Bill Roberts, at wroberts@usbr.gov

DIVISION 01 - GENERAL REQUIREMENTS

This page intentionally left blank.

Hungry Horse Dam Potable Water Conveyance System Hungry Horse Project, Montana Solicitation No. 140R1024B0001

Summary of Work 01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located approximately 8.0 miles southeast of Columbia Falls, Montana in Flathead County at the Hungry Horse Dam and Field Office.

1.02 PRINCIPAL COMPONENTS OF WORK

A. The work to be done includes the furnishing of all labor, material, transportation, tools, supplies, equipment and appurtenances, unless hereinafter specifically excepted, necessary for the complete and satisfactory construction and testing of a potable water conveyance system to the Hungry Horse Dam and Field Office. The work will be done on a unit rate basis in accordance with the Price Schedule.

B. Due to weather, work outside the facility shall be completed between June and July.

C. Coordination with Engineer and Bureau of Reclamation is required prior to the Contractor mobilizing and demobilizing to the project site. Engineer and Bureau of Reclamation to be contacted if Contractor intends to mobilize any vehicle in excess of 32 kips across the BPA Access Bridge.

D. A test well has been drilled to a depth of approximately 551 feet below ground surface (bgs), with a tested well yield of 35 gallons per minute (GPM). The well shall be fully developed as shown in the Contract Drawings, including but not limited to, installation of new submersible well pump, pitless adapter, discharg piping and valving, and electrical and controls instrumentation.

E. Installation of new 2-inch water main from the well head to the dam, including a horizontal directional drilling portion. Enter the dam near the left abutment with the water main and connect to existing potable system. Installation of pipe support, fittings, pressure reducing valves, flow meter, and hydropneumatic tank as shown in the Contract Drawings.

F. Installation or replacement of electrical panels, conductors, and conduit as shown in the Contract Drawings. Contractor take note that some existing cables contain asbestos. See additional project specifications.

Summary of Work 01 11 00 - 2

1.03 SPECIFICATIONS REQUIREMENTS

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

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

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

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.

B. Engineer

1. When specifications reference Engineer, the term shall refer to the design engineer, HDR Engineering, Inc.

1.05 ACRONYMS

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

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Other Contracts

01 12 10 - 1

SECTION 01 12 10

OTHER CONTRACTS

PART 1 GENERAL

1.01 OTHER WORK

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

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

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

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

E. Cooperate and coordinate with dam operating and maintenance personnel.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Other Contracts

01 12 10 - 2

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 cost of performing work required by this section in:

a. Lump sum price offered in Price Schedule for Water Conveyance System

Installation and Electrical System Replacement.

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) Areas for processing, storing, and disposing of waste materials from construction operations.

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

Use of Site

01 14 10 - 2

6) Temporary fences.

b. Describe methods to preserve, protect, and repair, vegetation (such as trees, shrubs, and grass) and other landscape features on or adjacent to jobsite, which are not to be removed and which do not interfere with work required under this contract. Include methods to mark work area limits, protect disturbed areas, and prevent erosion.

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

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

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

1.04 PROJECT CONDITIONS

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

1. Contractor may use left and/or right abutment of Hungry Horse Dam for staging area when working in the upper portions of dam. Contractor may use employee parking lot beneath Hungry Horse Dam when work is being performed in the powerhouse or the control bay. Contractor to coordinate staging with other ongoing construction work as needed; see Section 01 12 10 – Other Contracts.

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

C. Location, construction, operation, maintenance, and removal of construction facilities on

Government land will be subject to approval of COR.

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

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

F. Contractor work hours on site will be 6:30 AM to 5:00 PM, Monday to Friday. Requests to extend work hours shall be made at least 72 hours in advance.

G. Coordination with Engineer and Bureau of Reclamation is required prior to the

Contractor mobilizing and demobilizing any vehicle in excess of 32 kips across the BPA

Access Bridge. See Section 01 11 00 – Summary of Work.

Use of Site

01 14 10 - 3

PART 2 PRODUCTS

Not Used

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.

B. Seed disturbed areas of Government land used for construction purposes and not required for completed installation with species of native plants, or other approved perennial species, as recommended by an experienced local horticulturist.

Use of Site

01 14 10 - 4

Interruption of Service

01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost of performing work required by this section in:

a. Lump sum price offered in Price Schedule for Water Conveyance System

Installation and Electrical System Replacement.

1.02 SUBMITTALS

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

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

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

2. Outline procedures for accomplishing work including:

a. Specific safety precautions to be taken.

b. Type and location of barricades.

c. Warning signs.

d. Protective grounds and devices to be used.

3. Commencement time of work.

4. Duration of work.

5. Number of personnel and their classification.

6. Description of equipment to be used.

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

1.03 PROJECT CONDITIONS

A. Coordinate and schedule interruption of services with COR:

1. Coordinate work with Government operations.

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

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

Interruption of Service

01 14 30 - 2

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

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

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

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Coordination Meetings

01 31 22 - 1

SECTION 01 31 22

COORDINATION MEETINGS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost of performing work required by this section in:

a. Lump sum price offered in Price Schedule for Water Conveyance System

Installation and Electrical System Replacement.

1.02 SUBMITTALS

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

B. RSN 01 31 22-1, Electrical Equipment Coordination Meeting Notification:

1. Date and time of meeting and proposed attendees.

2. Preliminary layout drawings.

1.03 SPECIFICATION DRAWINGS

A. AUTOCAD files of drawings are available to Contractor. With at least 14 days’ notice, Government will make these files available to Contractor.

1.04 COORDINATION MEETINGS

A. Preconstruction Coordination Meeting:

1. Date: Approximately 21 days following notice of award.

a. Coordinate with Government and Engineer the meeting date at least 10 days before meeting.

2. Location: Bureau of Reclamation Hungry Horse Dam Field Office, Hungry

Horse, MT 59919-0130, or Microsoft Teams for those unable to attend in person meeting.

3. Purpose: Review with Government personnel to establish a working understanding among the parties as to the Work and to discuss the schedules, procedures for handling Shop Drawings, Samples, and other submittals, processing Applications for Payment, electronic or digital transmittals, designate individuals to act as its authorized representative with respect to the services and responsibilities under the Contract, and maintaining required records.

Coordination Meetings

01 31 22 - 2

B. Construction Progress Meetings

1. Date: Recurring weekly progress meetings shall occur during duration of construction activities.

a. Coordinate with Government and Engineer recurring meeting date and time at least 7 days before first meeting.

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

2. Location: Bureau of Reclamation, Hungry Horse Dam Field Office, Hungry

Horse, MT 59919-0130 or Microsoft Teams for those unable to attend in person meeting.

3. Purpose:

a. Review with Government personnel and Engineer construction activities to date, in field observations, and technical requirements of specifications.

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.

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

4) Representatives may attend by telephone and / or video conference.

4. Within 7 calendar days after conclusion of weekly meeting, Engineer will submit meeting notes in CDMS that summarize any discussion and decisions.

PART 2 PRODUCTS

Coordination Meetings

01 31 22 - 3

PART 3 EXECUTION

Contract Document Management System

01 31 30 - 1

SECTION 01 31 30

CONTRACT DOCUMENT MANAGEMENT SYSTEM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Contract Document Management System:

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

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. CMs: Contract Modifications.

g. Value Engineering Proposals.

h. Government Inspection Reports.

i. Invoices and Progress Payments.

j. Contract Schedules.

k. Meeting Agendas and Meeting Minutes.

l. Letters and Memos.

1.03 SUBMITTALS

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

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

1. System provider experience, number of systems operating, references.

2. Documentation of system capabilities.

3. Instructions for system use.

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

Contract Document Management System

01 31 30 - 2

1. DVD or CD of documents uploaded to CDMS.

1.04 QUALIFICATIONS

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

1.05 CDMS REQUIREMENTS

A. CDMS shall be capable of generating, storing, tracking, categorizing, and managing

Contract Documents.

B. Access:

1. Web-based:

a. Contract Documents are stored and accessed by authorized individuals via an internet site.

b. Compatible with web browsers Microsoft Edge, Apple Safari, Mozilla

Firefox and Google Chrome.

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

a. Adobe Acrobat.

b. MS Word.

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

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

d. Government shall be able to create and modify project properties (i.e.

Contractor, project location, description, bid amount, project directory, etc).

Contract Document Management System

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 greater than 15 days without action).

6. Ability to link files; examples:

a. RFP linked to a CM.

b. Submittal linked to a Specification Section or Drawing.

C. Reports:

1. Generate reports that list and sort documents by status, examples include:

a. Submittals that have been approved.

b. Invoices paid to date.

c. RFIs under review.

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

3. Generate customizable summary reports, examples include:

a. Submittal Turn-around.

b. RFI Turn-Around.

c. CM Processing Turn-Around.

d. Total CM costs.

e. Total CM Request Exposure.

4. Reports shall be printable, exportable as searchable PDF or printer friendly

HTML, and exportable to Excel, XML, 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:

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

Contract Document Management System

01 31 30 - 4

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/AAN/PAR/NA/ACK (Approved/Approved As

Noted/Partially Approved - Resubmit/Not Approved/Acknowledged).

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

a. Allow for Government to route submittal to third parties by generating design-review transmittals with each submittal package item, to track

Contract Document Management System

01 31 30 - 5 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.

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.

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.

Contract Document Management System

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. CDMS shall have the 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 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:

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

Contract Document Management System

01 31 30 - 7

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

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

Contract Document Management System

01 31 30 - 8

Construction Program

01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

1. Include cost of performing work required by this section in:

a. Lump sum price offered in Price Schedule for Water Conveyance System

Installation and Electrical System Replacement.

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.

Construction Program

01 32 10 - 2

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

Construction Program to the CO.

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

1. Designation of authorized representative to develop and maintain Construction

Program. Include resume with training and experience.

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

c. Primavera layout file (.plf).

d. Primavera file extension (.xer)

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

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

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

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

Construction Program

01 32 10 - 3

c. Primavera layout file (.plf).

d. Primavera file extension (.xer)

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

f. Narrative report specifically stating status of project.

1) When negative float exists, cite specific actions and conditions which caused "behind schedule" condition and provide proposed course of action to complete the project within the specified delivery time. When float changed from previous month’s updated schedule, explain reason for change.

2) List of Contractor-initiated changes to current schedule stating reason for action taken and unresolved issues relating to the

Construction Program. Government reserves the right to reject

Contractor-initiated changes to current schedule which negatively impact Government action which was initiated on the basis of current schedule.

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

g. Submittal Register:

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

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

3) This register document is separate from scheduling database.

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

1. Include:

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

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

c. Primavera layout file (.plf).

d. Primavera file extension (.xer)

Construction Program

01 32 10 - 4

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

f. Narrative report explaining results and conclusions.

1.05 QUALIFICATIONS

A. Representative: Experienced in developing and maintaining construction schedules and knowledgeable of activities and progress on-site to develop and maintain accurate and reliable schedules. Experience shall include scheduling for at least two other projects of comparable complexity and Primavera P6 training offered by certified instructors.

1.06 GENERAL

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

1.07 SCHEDULES

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

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

Logically sequence activities.

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

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

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

“Contract Complete” shall have successor activities.

4. Meet contract requirements; milestone(s) in accordance with the clause at FAR

52.211-10, Commencement, Prosecution, and Completion of Work; and relevant clauses and specification sections. Include interim milestone dates, Government interface dates, contract completion date, and other time or seasonal constraints specified in contract documents.

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

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

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

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

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

Assign weather calendars to work impacted by weather.

Construction Program

01 32 10 - 5

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

9. Define activities to level of detail resulting in their durations being no greater than

20 workdays.

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

10. Include separate activities for submittal preparation and submittal reviews 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.

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

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

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

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

15. Use finish to start logic relationships between activities. Do not utilize start to start, finish to finish, or start to finish logic relationships. Start to start logic may be utilized on start milestones and finish to finish logic may be utilized on finish milestones only. Do not use positive or negative lead or lag times.

16. Use durations in units of whole workdays.

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

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

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

Construction Program

01 32 10 - 6

B. Baseline Schedule:

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

C. Updated Schedule:

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

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

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

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

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

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

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

1.08 TIME IMPACT ANALYSIS

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

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

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

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

3. Time extensions for performance will be considered only to the extent that the

Contractor’s current scheduled milestone dates exceed contract milestone dates.

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

Construction Program

01 32 10 - 7

D. Prepare a single time impact analysis for modifications issued after Notice to Proceed

(NTP) and prior to approval update.

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

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

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

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

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

1) Activity description.

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

3) Activity duration.

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

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

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

1.09 REVIEW AND EVALUATION

A. Baseline Schedule:

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

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

Construction Program

01 32 10 - 8

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 updated schedule at least seven days prior to the 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.

4. The COR will schedule pre-submittal meeting with the Contractor’s representative each month to review draft updated schedule prior to the

Contractor submitting RSN 01 32 10-3, Updated Schedule.

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

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

1.10 FAILURE TO COMPLY

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

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Submittals

01 33 00 - 1

SECTION 01 33 00

SUBMITTALS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost of performing work required by this section in:

a. Lump sum price offered in Price Schedule for Water Conveyance System

Installation and Electrical System Replacement.

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 are considered to be “shop drawings” within terms of 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 satisfy contract requirements. Contractor shall correct mistakes or deficiencies in rejected Informational submittals and resubmit.

Submittals

01 33 00 - 2

c. Informational submittals are considered to be “shop drawings” within terms of clause at FAR 52.236-21, Specifications and Drawings for

Construction, except that approval by Government is not required.

1.04 SUBMITTAL REQUIREMENTS

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

B. General:

1. Prepare in English.

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

3. Measurement Units: US Customary Units.

4. Provide a unique transmittal number for each submittal.

C. Drawings:

1. Minimum Identification in Title Block:

a. Contract number and title.

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

c. Date.

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

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

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

a. Computer drafted drawings:

1) In accordance with NIBS NCS.

2) Electronic file format: Compatible with AUTOCAD.

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 electronic AutoCAD format template.

c. Title block and sheet format:

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

Submittals

01 33 00 - 3

2) Government will supply template.

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

6. Final Drawings:

a. Computer drafted.

b. Government will supply 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.

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

F. Manuals:

1. Copies:

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

1) Bookmark longer files to assist in navigating file.

2. Contents:

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

b. Schematics and wiring diagrams.

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

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

Submittals

01 33 00 - 4

G. Samples and Color Selection Submittals:

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

2. Include type and quantity of materials specified in the referenced section in each

“set” of samples.

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

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

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

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

1.05 SUBMITTALS PROCEDURES

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

B. Submit complete sets of required materials for each RSN as specified in “Submittals

Required” column in Table 01 33 00A - List of Submittals. A complete set includes all listed items for RSNs with multiple parts.

C. Submit number of sets specified in “No. of sets to be sent to:” columns in Table

01 33 00A - List of Submittals.

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

Document Management System.

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals 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…