B0010_Teton_Dam_Overlook_1.pdf

U.S. Department of the Interior SPECIFICATION Bureau of Reclamation Columbia Pacific Northwest Region 9 Boise, Idaho May 2024

Teton Dam 50th Commemoration Overlook Project Teton Basin Project, Idaho

Columbia-Pacific Northwest Region

Solicitation No. 140R1024B0010

This solicitation issued by Contracting Officer

Pacific Northwest Region Bureau of Reclamation

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

TETON DAM

50TH COMMEMORATION OVERLOOK PROJECT

TETON BASIN PROJECT

IDAHO

FOREWORD

Work is located approximately 5 miles northeast of Newdale, Idaho in Fremont County.

A. Work consists primarily of renovating an existing overlook site.

B. Demolish existing asphalt overlook, septic tankage, and associated elements.

C. Install asphalt pavement parking lot with associated elements.

D. Install concrete overlooks.

E. Install new restroom building.

F. Install new picnic tables.

G. Install miscellaneous site improvements including bollards, waste receptacles, a flagpole, and trees.

SEE SECTION L FOR SITE VISIT INFORMATION. ATTENDEES WILL PROVIDE

THEIR OWN PERSONAL PROTECTION EQUIPMENT (PPE) TO INCLUDE: SAFETY

GLASSES, SAFETY BOOTS, HARD HATS, AND SAFETY VESTS.

FOR DATE AND PLACE OF BID OPENING, SEE “SOLICITATION, OFFER, AND

AWARD” STANDARD FORM 1442.

FOR INFORMATION REGARDING BUREAU OF RECLAMATION’S PUBLICATION

“RECLAMATION SAFETY AND HEALTH STANDARDS” INCLUDING REVISIONS

AT https://www.usbr.gov/safety/rshs/index.html WHICH IS APPLICABLE TO WORK

UNDER THIS CONTRACT, SEE CLAUSE AT WBR 1452.223-81 SAFETY AND

HEALTH – BUREAU OF RECLAMATION (OCT 2022)

This page intentionally left blank.

Teton Dam 50th Commemoration Overlook Project Teton Basin Project, Idaho Solicitation No. 140R1024B0010

Price Schedule B - 1

CONTINUATION OF

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

TETON DAM

50TH COMMEMORATION OVERLOOK PROJECT, IDAHO

B.1 PRICE SCHEDULE

(a) Bids will be considered for award on the following Price Schedule, but no bid will be considered for award on only a part of the Price Schedule.

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

(c) Quantities in the Price Schedule are estimated quantities for comparison of bids only.

Except as provided in contract clause at FAR 52.211-18, Variation in Estimated Quantity.

Contract clause at FAR 52.211-18, Variation in Estimated Quantity, does not apply to lump sum items.

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

(e) Definitions:

(1) CLIN – Contract Line Item Number

PRICE SCHEDULE

CLIN Section Supplies or Services Quantity and Unit Unit Price Amount

1 WBR

1452.232-

Mobilization and Preparatory Work

For the lump sum of $

2 01 31 30 Contract Document Management System

For the lump sum of $

3 02 41 00 Demolition For the lump sum of $ 4 03 30 00 Cast-In-Place Concrete 155 yd3 $ $ 5 05 50 00 Miscellaneous Metalwork For the lump sum of $ 6 10 14 00 Wayside Signage For the lump sum of $ 7 13 34 00 Prefabricated Restroom

Building For the lump sum of $

8 31 23 02 Compacted Backfill 410 yd3 $ $ 9 31 23 11 Common Excavation 520 yd3 $ $ 10 31 23 11 Rock Excavation 560 yd3 $ $ 11 31 37 00 Riprap 29 yd3 $ $ 12 32 11 23 Aggregate Base Course 600 yd3 $ $ 13 32 12 22 Asphalt Concrete Pavement 3,500 yd2 $ $ 14 32 15 10 Gravel Surfacing 32 yd3 $ $

Price Schedule B - 2

PRICE SCHEDULE

CLIN Section Supplies or Services Quantity and Unit Unit Price Amount

15 32 30 00 Site Improvements For the lump sum of $ 16 32 33 43 Picnic Tables 7 ea $ $ 17 32 92 20 Seeding and Soil Supplements 0.50 acre $ $

TOTAL FOR PRICE SCHEDULE $_________________

END OF SUPPLIES OR SERVICES AND PRICES/COSTS

TECHNICAL SERVICE CENTER

WRITTEN SPECIFICATIONS SIGNATURE SHEET

Specifications Title:

Project Title:

Region:

Prepared: P.E.

Technical Approval: P.E.

Certified: P.E.

Teton Dam 50th Commemoration Overlook Project

Minidoka Project

Columbia-Pacific Northwest (CPN)

Mark Nance Digitally signed by Mark Nance Date: 2024.04.29 11:24:14 -06'00'

Digitally signed by Bruce Barkey Date: 2024.04.29 11:26:16 -06'00'

NANCY ARTHUR

Digitally signed by NANCY

ARTHUR

Date: 2024.04.29 12:59:52 -06'00'

DIVISION 01 - GENERAL REQUIREMENTS

Summary of Work 01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located approximately 5 miles northeast of Newdale, Idaho in Fremont County.

The site does not have a street address; latitude and longitude coordinates for the existing parking lot are approximately 43 degrees 54 minutes 17.6 seconds north by 111 degrees 32 minutes 24 seconds west (43.904826, -111.539892).

1.02 PRINCIPAL COMPONENTS OF WORK

A. Work consists primarily of renovating an existing overlook site.

B. Demolish existing asphalt overlook, septic tankage, and associated elements.

C. Install asphalt pavement parking lot with associated elements.

D. Install concrete overlooks.

E. Install new restroom building.

F. Install new picnic tables.

G. Install miscellaneous site improvements including bollards, waste receptacles, a flagpole, and trees.

1.03 SPECIFICATIONS REQUIREMENTS

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

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

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

1.04 DEFINITIONS

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

Summary of Work 01 11 00 - 2

1.05 ACRONYMS

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

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedule for other items of work.

1.02 SUBMITTALS

A. In accordance with Section 01 33 00 – Submittals.

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

1. For each Contractor use site on Government land:

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

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

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

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

4) First-aid and medical facilities.

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

6) Location of temporary fences.

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

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

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

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

Use of Site 01 14 10 - 2

1.03 PROJECT CONDITIONS

A. Allowable Work Hours: 7 a.m. to 5 p.m., Monday through Friday, excluding Federal holidays, unless otherwise noted.

1. Work outside of allowable work hours shall be approved by the COR in writing a minimum of 72 hours in advance.

2. Material deliveries 7 a.m. to 5 p.m, Monday through Friday. Material deliveries outside of allowable hours shall be approved by the COR in writing a minimum of 72 hours in advance.

B. Government land shown on Drawing 549-D-60000 may be used for required construction facilities. Government will not be liable for material or equipment stored at this location.

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

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

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

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

1.04 ENVIRONMENTAL CONDITIONS

A. Data Source Location: Saint Anthony, ID, approximately 8 miles from the work site.

1. Altitude: Approximately 4,900 feet above mean sea level.

2. Following monthly summarized data is per https://www.weather.gov/wrh/Climate?wfo=pih, Saint Anthony 1, ID; minimum and maximum daily values may be outside the listed range:

a. Outdoor Ambient Temperature Range from 2004-2023:

1) Minimum: Minus 26 degrees Fahrenheit.

2) Maximum: Plus 98 degrees Fahrenheit.

b. Annual Precipitation from 2004-2023, significant missing data:

1) Minimum: 9.0 inches.

2) Average: 13.7 inches.

3) Maximum: 17.7 inches.

c. Seasonal Snowfall for Winters of 2003-2004 to 2022-2023, significant missing data:

1) Minimum: 0 inches.

https://www.weather.gov/wrh/Climate?wfo=pih

Use of Site 01 14 10 - 3

2) Average: 22.7 inches.

3) Maximum: 74.9 inches.

B. Work Site Altitude: Approximately 5,300 feet above mean sea level.

C. Additional conditions that may be applicable as specified in other sections.

1.05 OTHER CONTRACTS

A. Other contractors or the Government may be performing work in the vicinity of this contract’s work during the course of this contract.

B. Cooperate and coordinate with other contracts’ contractors, including access, use of areas, and scheduling. Comply with the clause at FAR 52.236-8, Other Contracts.

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 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

Coordination Meetings 01 31 22 - 1

SECTION 01 31 22

COORDINATION MEETINGS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost: Include in prices offered in the Price Schedule for other items of work.

1.02 SUBMITTALS

A. In accordance with Section 01 33 00 – Submittals.

B. RSN 01 31 22-1, Weekly Construction Coordination Meeting Agenda and Minutes:

1. Meeting agenda and meeting minutes from the previous weekly meeting.

2. 3-week look-ahead schedule.

3. Work completed to date.

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

a. Date, time, and attendees.

b. Summary of topics discussed.

c. List of action items including:

1) Description of action item.

2) Responsible party.

3) Date to be completed.

1.03 SPECIFICATION DRAWINGS

A. AutoCAD files of drawings may be available to the Contractor:

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

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

1.04 COORDINATION MEETINGS

A. Preconstruction Meeting:

1. Date: No more than 42 days after receipt of Notice to Proceed.

2. Location: Upper Snake Field Office, 470 Roger Avenue, Heyburn, ID 83336.

3. Purpose: Review with Government personnel drawings, data, and technical requirements of specifications.

Coordination Meetings 01 31 22 - 2

4. Attendees: Responsible representatives who understand these specifications with respect to technical requirements, equipment to be furnished, and coordination necessary to complete work. Representatives shall include:

a. Contractor: 1.

b. Civil subcontractor, if applicable: 1.

5. Some Government personnel may attend virtually via Microsoft Teams.

B. Weekly Construction Coordination Meetings:

1. Implement as specified herein.

2. Virtual via Microsoft Teams or Government-approved equal.

3. Review safety, security, environmental, schedule, project issues and concerns, submittals, Contractor Requests for Information (RFI), Requests for Proposal (RFP), pending contract modifications, and other project related items.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 IMPLEMENTATION

A. Coordinate meeting time, place, invite list, notifications, virtual access, and teleconference access with the COR.

B. Prepare and distribute agendas for each meeting.

C. Conduct each meeting.

D. Compile and distribute meeting minutes after each meeting.

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:

a. Specifications.

b. Contract Drawings.

c. Submittals.

d. DIRs: Daily Inspection Reports.

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

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

g. Bureau of Reclamation (Reclamation) Inspection Reports.

h. Contract Schedules.

i. Meeting Agendas and Meeting Minutes.

1.03 SUBMITTALS

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

1. Documents uploaded to CDMS in an electronic format approved by COR.

1.04 QUALIFICATIONS

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

Contract Document Management System 01 31 30 - 2

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

b. Microsoft Word.

c. Microsoft Excel.

d. Microsoft Project.

e. Oracle Primavera P6 Project Manager.

f. Drawing (.dwg).

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

a. Preparing organization shall 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 that 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 shall be prerogative of organizational project manager.

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

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

Examples:

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

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

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

Contract Document Management System 01 31 30 - 3

6. Ability to link files; examples:

a. RFI linked to a submittal.

b. Submittal linked to a Specification 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. RFP Processing Turn-Around.

d. Total RFP Request Exposure.

4. Printable, exportable as searchable .pdf or printer friendly HTML, and exportable to Excel, .xml, or .csv formats.

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:

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 of documents to which an organization has access on a regular

(minimum monthly) basis.

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

Contract Document Management System 01 31 30 - 4

E. General Tracking and Control:

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

2. CDMS shall track:

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

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

c. When a reviewer has opened an item.

F. Submittal Tracking and Control:

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

2. Customizable standard submittal form for entering information. Required information includes required submittal number (RSN), title, description, and specification section. Upload submittal data in electronic format.

3. Track date received, date response due, date returned, and status. 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.

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.

Contract Document Management System 01 31 30 - 5

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. Cost Tracking and Payment Request Management:

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

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.

J. Correspondence:

1. Ability to generate letters and memos:

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

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

2. Ability to generate responses to letters and memos: 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 the minutes. CDMS shall automatically assign sequential meeting numbers.

K. Miscellaneous Tracking and Controls – Ability to:

1. Generate logs tracking RFCs, RFIs, RFPs, Submittals, Payments, Memos, DIRs, survey requests, plant inspection reports and testing reports.

2. 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. Sort logs based on a criterion; e.g., for Submittal, Specification Section, Days Out, Status, or other criteria determined by COR.

4. Provide forms to match Government’s Progress Payment Form or other forms when needed.

5. Track cost exposure with links to RFI requests.

6. Measure productivity benchmarks on a project such as computing average review days for RFIs and submittals.

7. Keyword search of documents in database.

Contract Document Management System 01 31 30 - 6

PART 2 PRODUCTS

2.01 GENERAL

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

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 entries to the Schedule of Submittals before making submittals.

Include:

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

2. Scheduled submittal date.

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

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

1. Required Submittal Number (RSN).

2. Section Title.

3. Submittal Title.

4. Date Submitted.

5. Date of Response.

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

7. Days in Review.

8. Due Date.

D. CDMS shall be operational until final project closeout.

Construction Program 01 32 10 - 1

SECTION 01 32 10

CONSTRUCTION PROGRAM

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Costs:

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

Schedule for Mobilization and Preparatory Work.

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

1.02 DEFINITIONS

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

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

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

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

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling

Manual, 2004

1.04 SUBMITTALS

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

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

Professional Project Management.

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

Construction Program to the CO.

Construction Program 01 32 10 - 2

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

1. Designation of authorized representative to develop and maintain Construction

Program. Include resume with training and experience.

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

1. Include:

a. Construction Program/Schedule database.

b. Definition of project calendars.

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

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.

Construction Program 01 32 10 - 3

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)

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.

Construction Program 01 32 10 - 4

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.

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

Construction Program 01 32 10 - 5 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.

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.

Construction Program 01 32 10 - 6

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

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

1.08 TIME IMPACT ANALYSIS

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

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

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

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

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

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

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

Construction Program 01 32 10 - 7

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

3) Activity duration.

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

c. Data date for impacted schedule used in comparison 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.

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.

Construction Program 01 32 10 - 8

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: Include in prices offered in the Price Schedule for other items of work.

1.02 DEFINITIONS

A. Days: Calendar days.

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

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

1. A - Approval:

a. Government will respond as to adequacy of submittal.

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

2. I - Informational:

a. Government will acknowledge receipt of Informational submittals.

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

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

1.03 REFERENCE STANDARDS

A. American Society of Mechanical Engineers (ASME)

1. ASME Y14.1-20 Drawing Sheet Size and Format

B. National Institute of Building Sciences (NIBS)

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

Submittals 01 33 00 - 2

1.04 SUBMITTAL REQUIREMENTS

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

B. General:

1. Prepare in English.

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

3. Measurement Units: US Customary Units.

4. Provide a unique transmittal number for each submittal.

C. Drawings:

1. Minimum Identification in Title Block:

a. Contract number and title.

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

c. Date.

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

3. Size: ANSI D size (22 inches by 34 inches) in accordance with 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 2023 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.

Submittals 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. Final Electronic Drawings: When final electronic drawings are required:

a. Drawing format: AutoCAD, Version 2023 or later, or as approved by the

COR.

b. Compile using ‘eTransmit’ utility in AutoCAD.

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

Indicate changes by clouding.

8. Electronic Files: On CDMS.

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

1. When requested.

2. Each COR-requested view: Include contract number, name of equipment and view title.

3. Format:

a. Digital photographs on CD, DVD, or in CDMS in jpeg format. Four megapixels minimum. With accompanied prints if requested and of a size requested by the COR.

b. Prints only if specifically requested.

1) Professional quality 8- by 10-inch color.

Submittals 01 33 00 - 4

2) Identify with adhesive labels on back. Do not type directly on back of photograph.

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. Government will select architectural color and pattern after product approval.

1.05 SUBMITTALS PROCEDURES

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

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

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

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

D. Include the following information in transmittal letters:

1. Contract number and title.

2. RSN for each attached submittal.

3. Responsible code.

4. Number of sets for each RSN.

5. Identify submittal as initial or resubmittal.

E. Resubmittal of submittals not approved:

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

2. Describe reasons for significant changes in transmittal letter.

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

Submittals 01 33 00 - 5

4. Requirements for initial submittals apply to resubmittals.

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

1.06 REVIEW OF SUBMITTALS

A. Time Required:

1. Submittal review will require 21 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.

B. Time in Excess of Specified:

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

a. 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 two or more separate submittals or resubmittals will be counted only once in extending the contract completion date.

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

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

a. Approval was required under the contract, and,

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

4. Adjustment will be subject to terms of paragraphs (b) and (c) of the clause at FAR

52.242-14, Suspension of Work, however, no such delay shall be deemed to be a “suspension order” as the term is used in that clause.

C. Return of Submittals:

1. Return of submittals will be by CDMS response or hard copy, as applicable.

2. Approval Submittals: Will be returned either approved, approved with comments, or not approved:

a. Revise and resubmit submittals not approved.

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

Submittals 01 33 00 - 6

3. Informational Submittals: Government will acknowledge Informational submittals:

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

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

D. Provide the CO with a copy of all correspondence and related documents pertaining to this contract that it addresses to representatives of the Government. This does not pertain to the Submittal Requirements as they are outlined herein.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Submittals 01 33 00 - 7

Table 01 33 00A – List of Submittals

* Submittal Types: A – Approval, I – Information.

** Y indicates Yes, the submittal is required to be shown on the construction schedules required in Section

01 32 10 – Construction Program.

*** CDMS indicates Contract Document Management System, CO indicates Contracting Officer, COR indicates

Contracting Officer’s Representative, and TSC indicates Technical Service Center.

RSN

Clause or Section

Title Submittals Required Due date or

Delivery time Type

CP

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

CO COR TSC

1 Release of Claims

(DIAR

1452.204-70)

Release of claims (DI-137) against United States

After completion of work and prior to final payment

A Email to CO

2 Payroll and Basic Records

(FAR 52.222-8)

Certified payrolls Weekly for each week any contract work is performed onsite

I CDMS

3 Labor Standards Data

(FAR 52.222-11)

(1) List of subcontractors

(2) Statement and Acknowledgment Form (SF-1413) for each subcontract

Within 14 days after Notice to Proceed, and within 14 days after award of any subcontract

I CDMS

or

Email to CO

4 Equal Opportunity

(FAR 52.222-26)

Information required by Executive Order

11246 (SF-100)

Within 10 days following Notice to Proceed

I CDMS

or

Email to CO 5 Insurance-Work on a Government Installation

(FAR 52.228-5)

1) Written certification that the required insurance has been obtained

2) Current certification of insurance for each subcontractor

Within 10 days after Notice of Award

A Email to CO

6 Liability Insurance

- Department of the Interior

(DIAR

1452.228-70)

Acceptable Certificate of Liability Insurance

Within 10 days after Notice of Award

A Email to CO

7 Bonds

(FAR 52.228-15)

Performance and Payment Bonds

Within 10 days after Notice of Award

A Email to CO

8 Estimate of Percentage of Recovered Material Content for EPA- Designated Items

(FAR 52.223-9)

Estimate of Percentage of Total Recovered Material Content for EPA- Designated Items Delivered or Used in Contract Performance

On completion of the contract (no later than with submittal of final voucher)

I CDMS

9 Safety and Health

(WBR

1452.223-81)

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

RSHS.

A Y CDMS

10 Safety and Health

(WBR

1452.223-81)

Monthly Accident Summary Report

First day of month. See paragraph 3.8 of RSHS.

I CDMS

Submittals 01 33 00 - 8

Table 01 33 00A – List of Submittals

* Submittal Types: A – Approval, I – Information.

** Y indicates Yes, the submittal is required to be shown on the construction schedules required in Section

01 32 10 – Construction Program.

*** CDMS indicates Contract Document Management System, CO indicates Contracting Officer, COR indicates

Contracting Officer’s Representative, and TSC indicates Technical Service Center.

RSN

Clause or Section

Title Submittals Required Due date or

Delivery time Type

CP

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

CO COR TSC

11 Security

Requirements

(WBR

1452.237-80)

Security Program Submitted and approved before mobilization

A CDMS

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

At least 28 days before use of Government land

A Y CDMS

01 31 22-1 Coordination Meetings

Weekly Construction Coordination Meeting Agenda and Minutes

At least 1 day prior to meeting

I CDMS

01 31 30-1 Contract Document Management System

Approval Data Within 21 days of Notice to Proceed

A CDMS

or

Email to CO 01 31 30-2 Contract Document

Management System

Final Data Within 7 days after completion of work

A CDMS

01 32…