Draft_SOW_-_East_Park_Boat_Ramp_Improvement_Project_1.pdf

East Park Boat Ramp Improvement Project Orland Project, California Specifications No. 20-C0946

Table of Contents

00 01 10 - 1

SECTION C - DESCRIPTION / SPECIFICATIONS

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 14 10 Use of Site 01 31 22 Coordination Meetings 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 30 Contractor's Onsite Safety Personnel 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 46 20 Testing Agency Services 01 51 00 Temporary Utilities 01 55 00 Vehicular Access and Parking 01 55 20 Traffic Control 01 56 10 Protection of Existing Installations 01 56 15 Protection of Existing Utilities 01 56 20 Existing Fences 01 56 32 Temporary Safety Fence 01 57 20 Environmental Controls 01 57 30 Water Pollution Control 01 57 35 Oil Spill Prevention 01 57 50 Tree and Plant Protection 01 60 00 Product Requirements 01 71 23 Construction Surveying and Staking 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents

DIVISION 02 - EXISTING CONDITIONS

02 41 00 Selective Site Demolition and Salvage 02 84 40 Removal and Disposal of Polychlorinated Biphenyls (PCBs)

DIVISION 03 - CONCRETE

03 30 00 Minor Concrete 03 31 00 Boat Ramp Concrete

DIVISION 10 – SPECIALTIES

DRAFT

Table of Contents

00 01 10 - 2

10 14 00 Recreation Facility signage

DIVISION 26 - ELECTRICAL

26 56 00 Exterior Lighting (Solar Light)

DIVISION 31 - EARTHWORK

31 02 10 Water for Dust Abatement 31 11 00 Clearing and Grubbing 31 13 00 Selective Tree and Shrub Removal and Trimming 31 23 00 Excavation and Embankment 31 37 00 Riprap 31 50 00 Excavation Support and Protection

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 11 00 Base Courses 32 12 00 Flexible Paving 32 15 00 Aggregate Surfacing 32 16 00 Concrete Curbs, Walks, Aprons, and Pads 32 17 00 Paving Specialties 32 31 00 Fences, Gates, and Barriers 32 90 00 Planting and Restoration

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 51 13 Boarding Float System

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 10 Photographs 51 00 20 Records of Geologic Investigations 51 00 50 Electronic Media Release

DIVISION 52 - DRAWINGS

52 00 00 Drawings

END OF CONTENTS

Summary of Work

01 11 00 - 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.01 LOCATION

A. Work is located approximately 36 miles West of Maxwell, California in Colusa County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Demolition:

1. Remove Concrete Pad.

2. Remove Trees.

B. Salvage:

1. Relocate Picnic Tables.

2. Toilet Building (protect in place).

C. Earthwork:

1. Contour site using cut and fill.

2. Provide and install Rip Rap.

D. Drainage:

1. Install a Wide Gravel Filtration Trench with aggregate and filter fabric.

2. Install CMP Culvert.

3. Install Precast Drainage Structure.

E. Boat Ramp Concrete:

1. Construct a Boat Ramp with a Concrete Boat Ramp Apron and Precast Concrete ramp over Aggregate Base.

2. Construct an accessible Concrete Walkway over Compacted Aggregate base over Compacted Soil.

3. Construct a Trash Bin Pad with concrete over aggregate base.

4. Construct an Aluminum Dock System.

5. Construct a Boat Ramp - Concrete Boat Ramp Apron, 6" Aggregate Base, PCC,

6. Construct a Sidewalk, Compacted Subgrade, Rock Slope Protection.

7. Install Boarding Float System.

01 11 00 - 2

F. Parking Area:

1. Install AC Paving with compacted subgrade, HMA paving, and aggregate base.

2. Install a gravel transition to the roadway with a surface course and compacted Aggregate base.

3. Install Concrete Curb.

4. Install an Information Kiosk.

5. Install accessible parking signage, concrete apron project sign, and stop sign.

6. Install a new Solar Light.

G. Painting:

1. Install cross walk striping, pavement striping, and stop bar pavement marking - Type 1.

2. Install arrow pavement marking.

1.03 SECIFICATIONS 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. Use of the work “shall” is to be expressly defined as mandatory and legally having the same connotations, implications, or reference to the word “must” throughout this specification.

1.05 ACRONYMS

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

1. CO: Contracting Officer.

2. COR: Contracting Officer’s Representative.

PART 2 PRODUCTS

Not Used

01 11 00 - 3

PART 3 EXECUTION

Not Used

END OF SECTION

Summary of Work 01 11 00 - 4

This page intentionally left blank. DRAFT

Use of Site 01 14 10 - 1

SECTION 01 14 10

USE OF SITE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 REFERENCE STANDARDS

A. Bureau of Reclamation (Reclamation)

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

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

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

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

01 14 10 - 2 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 the Title Sheet drawing, Location Map, within the Project Area may be used for required construction facilities. Addition Contractor Use Area(s) may be request in writing for approval by the COR.

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

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

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

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

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

01 14 10 - 3

3.02 RESTORATION

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

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

Use of Site 01 14 10 - 4

This page intentionally left blank. DRAFT

Coordination Meetings

01 31 22 - 1

SECTION 01 31 22

COORDINATION MEETINGS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

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

1.02 DEFINITIONS

A. Outage: A Contractor requested temporary suspension or interruption of normal facility operations.

1.03 PRECONSTRUCTION SAFETY MEETING

A. Coordinate preconstruction safety meeting with COR at work site project office before starting onsite work.

B. The meeting shall be scheduled after the Contractor’s Safety Program has been submitted and accepted. The meeting will be coordinated between Contractor project management, COR, and Reclamation Safety Manager. Topics covered will include:

1. Contractor’s Safety Program.

2. Required joint safety policy meetings.

3. Site Security Coordination.

4. Required toolbox safety meetings.

5. Weekly joint safety inspections.

6. Job hazard analyses (JHAs).

7. Site Security.

8. Electrical Equipment.

9. Environment requirements.

1.04 COORDINATION MEETINGS

A. Weekly Coordination Meetings:

1. Contractor shall conduct weekly coordination meeting with Government.

a. Weekly Coordination Meetings do not relieve the Contractor from the responsibility of other meetings required by the specifications.

01 31 22 - 2

2. Purpose: Review work progress, performance, issues, and contract administration with Government representatives.

3. Contractor Attendees shall include the Contractor’s project manager, superintendent, Safety Professional, and other representatives, as needed – who understand the specifications, drawings, work, schedule, technical requirements, components, and contract administration.

4. Reclamation Attendees will include the Construction Office On-site Government Representative and may include the Contract Officer’s Representative (COR);

Construction Office Safety Manager; Construction Office Field Engineer (FE) or Construction Manager (CM), Construction Office Contract Administrator/Manager (CA/M); Contract Specialist (CS); Contract Officer (CO);

Area Manager’s Representative; Field Offices Representative; Regional Engineer’s Design Representatives and/or Technical Service Center’s Design Representatives as determined based on need.

5. The meeting will be convened and led by the Contractor to discuss and provide updates for the following:

a. Work Schedule to include:

1) Submittal status, due dates, delivery time frames, and questions or concerns.

2) Contractor’s progress.

3) Contractor three week look-ahead schedule.

b. Safety issues and Weekly Safety Walk.

c. Drawing questions including the status of shop drawings, as required, and the status of As-built drawings on a weekly basis. The Contractor shall be prepared to present the As-built drawings for review at the meeting or immediately after the meeting.

d. Status of outage requests including dates, durations, if required materials will be on-hand, if staff will be available, future requests, and any other necessary information.

e. Environmental compliance.

1) Activities supporting environmental commitments.

a) Performance of environmental protection measures, installations, and maintenance.

b) Incidental Take Permit (ITP) compliance.

c) Storm Water Pollution Prevention Plan activities.

d) Restoration Areas.

e) Weed Abatement.

f) Road grading and Maintenance.

01 31 22 - 3

g) Water supply and dust abatement.

h) Permit reporting support.

f. Security concerns.

g. Personnel changes or other issues.

h. Contract Administration:

1) Modifications.

2) Requests for Equitable Adjustment (REA’s). (Contractor generated document).

3) Requests for Changes (RFC’s). (Contractor generated document).

4) Requests for Information (RFI’s). (Contractor generated document).

5) Requests for Proposal (RFP’s).

6) Requests for Substitution's (RFS’s). (Contractor generated document).

7) VECP: Value Engineering Change Proposals (Contractor generated document).

8) Quantities and Invoices.

6. Other outstanding issues.

7. New Action Items.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 IMPLEMENTATION

A. Contractor shall coordinate meeting times, place, invitation list, notifications, and teleconference access with the COR for the various required meetings. The Contractor shall allow adequate time for weekly safety walk prior to the Weekly Coordination Meeting.

B. Contractor shall have the capability to conduct meetings via Microsoft TEAMS or Webex Meeting to support weekly coordination meetings, and other meetings as they come up, with attendees from multiple offices at multiple worksites.

C. The contractor shall distribute agendas, 3-week look-ahead schedules, meeting minutes, and revised meeting minutes through CDMS. The contractor may distribute printed hard

01 31 22 - 4 copies of the agendas, 3-week look-ahead schedules, meeting minutes, and revised meeting minutes to the on-site staff.

1. Contractor shall prepare and distribute agendas 1 day before each meeting.

2. Contractor shall provide a 3-week look-ahead schedule at least 2 hours before start of meeting and be prepared to discuss the look-ahead schedule meeting.

3. Contractor shall compile and distribute meeting minutes within 1 day of the meeting.

4. Government reserves the right to comment on and suggest edits to the minutes for clarity and accuracy.

a. The Contractor shall revise meeting minutes within 1 day of receipt of government comments.

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.

a. Payment of the lump sum price offered will be made incrementally throughout the duration of the contract and will not be paid in full until completion of the contract.

b. Only costs directly associated with the CDMS shall be included in this cost.

1.02 DEFINITIONS

A. As-built Drawings are detailed documents that represent the final construction of a project as it was built, including all changes made during the construction process. These drawings are essential for compliance, maintenance, and future renovations, particularly for federal projects.

B. Approval Drawings are submitted by the Contractor for approval or acceptance by the government for work specified in the contract and reflect the conditions actually constructed in accordance with the specification and drawings issued in the contract.

C. Contract Modifications (MODs) refer to any written changes made to the terms and scope of a contract, which can include adjustments to cost, delivery schedules, or other provisions. These modifications can be unilateral, made by the contracting officer alone, or bilateral, requiring agreement from both the contractor and the contracting officer.

D. Contractor Proposals for construction are formal documents, submitted by the contractor, to bid on government construction projects. These proposals outline the contractor's qualifications, project plans, pricing, and compliance with federal regulations as specified in the contract.

E. Contract Schedules are detailed plans, submitted by the contractor, that outline the sequence of tasks, activities, and resources required to complete a construction project within a specified timeframe.

F. Drawings are depictions of the required work or existing conditions issued as part of the awarded contract or as updated by contract modification.

G. Final Drawings refer to the detailed drawings and specifications that outline the construction work to be done, including materials and equipment required for a project.

01 31 30 - 2

H. Invoices and Progress Payments are requests for payment submitted by contractors to the government for goods or services provided under a contract. Progress payments are partial payments made to contractors as work progresses, typically based on costs incurred or specific milestones achieved, helping to manage cash flow during long-term projects.

I. Letters, Memorandums, and Correspondence refers to official communication sent and received by U.S. Government employees or contractors, which can include letters, documents, and other materials related to government business. This type of correspondence is often subject to specific handling and delivery procedures to ensure proper management and security.

J. Meeting Agenda is a structured list of topics and activities to be discussed during a meeting, typically including the date, time, and location, as well as the order of business items. It helps participants prepare for the meeting by outlining what will be addressed and in what sequence 3-week look-ahead schedules, and Meeting Minutes.

K. Meeting Minutes are the official written records of meetings, prepared by the Contractor and submitted to the Government for approval, summarizing the decisions made and actions taken, rather than providing a verbatim account of discussions. They typically include details such as the date, attendees, and key points discussed, serving as important legal documents for the organization.

L. Request for Change (RFC) is a formal request made to modify the terms or conditions of a federal contract, which may include changes in specifications, performance requirements, or other contract elements. This process ensures that any adjustments are documented and agreed upon by both the contracting officer and the contractor.

M. Request for Equitable Adjustment (REA) is a formal request made by a contractor to a contracting officer for a change in the contract price or terms due to unforeseen circumstances that affect contract performance. It aims to compensate the contractor for additional costs or time incurred because of changes ordered by the government.

N. Request for Information (RFI) is a formal document used by the Contractor to gather information from government agencies specification questions, drawing questions, site conditions that require Government clarification.

O. Request for Proposal (RFP) is a formal document issued by the Government to the Contractor based on an RFI, RFC, or in-scope change in a government requirement.

P. Request for Substitution (RFS) is a formal request made by a contractor to substitute a specified material, product, or service in a contract with an equal or superior alternative.

This process ensures that the replacement meets or exceeds the performance and quality standards originally outlined in the contract.

Q. Required Submittal Notice (RSN) is a formal document or sample submitted by a contractor to the Government for review and approval, typically including details about materials, products, or systems to be used in a construction project.

01 31 30 - 3

R. Specifications are mandatory documents issued by the Government that define the essential technical requirements of a construction procurement.

S. Value Engineering Change Proposal (VECP) is a contractor-initiated proposal submitted under the value engineering clause of a contract, aimed at reducing the life-cycle costs of a project while sharing the savings between the contractor and the government. It is part of a systematic approach to improve performance and reduce costs in federal contracts.

1.03 1.03 ACRONYMS

A. CDMS: Contract Document Management System.

B. CMs: Contract Modifications.

C. CO: Contracting Officer.

D. COR: Contracting Officer’s Representative.

E. EPBR: East Park Boat Ramp Improvement Project.

F. ECS: Enterprise Content System.

G. NARA: National Archives and Records Administration.

H. PM: Project Manager.

I. REA: Request for Equitable Adjustment.

J. RFC: Request for Change.

K. RFI: Request for Information.

L. RFP: Request for Proposals.

M. RFS: Request for Substitution.

N. RSN: Required Submittal Notice (AKA: Submittals).

1. Required Submittal Notice response codes:

a. A: Approved.

b. CA: Conditionally Approved – Some parts of the submittal are approved to started work. Noted parts to be corrected, resubmitted, and approved prior to start of work on noted parts.

c. NA: Not Approved – Submittal to be corrected, resubmitted, and approved prior to start of work.

d. Acc: Accepted.

01 31 30 - 4

e. CAcc: Conditionally Accepted – Some parts are accepted to started work.

Noted parts to be corrected, resubmitted and approved prior to start of work on noted parts.

f. NAcc: Not Accepted – Submittal to be corrected, resubmitted, and approved prior to start of work.

O. VECP: Value Engineering Change Proposal.

1.04 REFERENCE STANDARDS

A. National Contract Management Association (NCMA)

1. ANSI/NCMA ASD 1-2019 (R2022) Available at https://www.ncmahq.org/.

B. National Institute of Standards and Technology (NIST)

1. NIST FIPS 140-3-19 Security Requirements for Cryptographic Modules, available at https://csrc.nist.gov/pubs/fips/140-3/final.

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

1. Enable bulk download feature for Contract Manager, Contract Officer Representative, Contract Officer and /or Contract Specialist.

2. Encrypted Hard Drive or Encrypted Flash Drive, meeting FIPS 140-2 requirements for Level 3 Security and chain-of-custody procedures.

a. Password protected.

b. Securely transmit password to Government as approved by COR.

c. Submit with all documents uploaded to CDMS.

1.06 QUALIFICATIONS

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

1.07 CDMS REQUIREMENTS

A. CDMS shall be capable of generating, storing, tracking, categorizing, and managing Contract Documents to include, but are not limited to:

01 31 30 - 5

1. As-built Drawings

2. Approval Drawings.

3. Contract Modifications (CMs).

4. Contractor Proposals.

5. Contract Schedules.

6. Invoices and Progress Payments.

a. Payment requests must be submitted electronically through the U. S.

Department of the Treasury's Invoice Processing Platform System (IPP)in accordance with Section G of this contract.

b. Prior to submitting for payment Contractor shall provide backup calculations, data and information for verification of quantities/materials which will be verified by WCO field and agreed to with the Contractor’s field staff prior to submittal of the invoice. Each invoice should be reviewed and substantiated by WCO field and administration staff.

c. For invoicing/partial payment purposes, Contractor shall provide a breakdown for the LS items in the Bid Schedule for COR and CO review and approval per Section 01 33 00 - Submittals.

7. Letters, Memos and other typical contract correspondence.

8. Meeting Agendas, 3-week look-ahead schedules, and Meeting Minutes.

9. Request for Change (RFC).

10. Request for Equitable Adjustment (REA).

11. Request for Information (RFI).

12. Request for Proposal (RFP).

13. Request for Substitution (RFS).

14. Required Submittal Notice (RSN).

15. Specifications and Drawings.

16. Value Engineering Change Proposal (VECP).

B. Access shall be web-based:

1. Contract Documents to be stored and accessed by authorized individuals via an internet site.

2. Compatible with web browsers MS Edge, Apple Safari, Mozilla Firefox and Google Chrome.

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

a. Adobe Acrobat.

b. MS Word.

01 31 30 - 6

c. MS Excel.

d. MS Project.

e. Oracle Primavera P6 Project Manager.

f. Autodesk AutoCAD Civil 3D.

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

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

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

7. Ability to link files; examples:

a. RFP linked to a CM.

b. Submittal linked to a Specification Section or Drawing.

C. File Naming Conventions:

1. Reclamation is required to retain construction documents at the National Archives and Records Administration (NARA) for prescribed periods after construction.

NARA has adopted an Enterprise Content System (ECS) to preserve this information. The ECS requires data to be placed in the system in a standardized manor to allow for quick retrieval. This part provides guidance on name conventions.

2. The Naming Standard shall be Record Name YYYYMMDD.

a. Do not start the name with a date.

b. The following are examples:

01 31 30 - 7

1) RSN ## ## ##-#-## Record Title YYYMMMDD.

a) Example: Use RSN 01 14 10-1-01 Land Use and Landscape Rehabilitation Plan 20221114 where: RSN 01 14 10-1 is the RSN Number; -01 is a counter staring with 01 for the contractor’s submittal, 02 for Reclamations response, 03 for the contractor’s resubmittal and so on;

Land Use and Landscape Rehabilitation Plan is the title for submittal; 20221114 stands for the date November 14, 2022 -01.

2) RFI ####-## Title YYYMMMDD.

a) Example: RFI 001-01 20221219.

3) Invoice PP-###-## YYYMMMDD.

a) Example: Invoice PP-001-01 20230615.

c. Where# is a numerical value; YYYY is the 4-digit year, MM is the 2-digit month, and DD is the 2-digit day of the month.

3. Do Not use Special Characters such as ! @ # $ % & ; : _ / * + - = in record names’

a. Special characters can cause issues in the electronic records repository and mathematical special symbols are known to cause issues or be incomparable. In example, the dash can be used, while the minus sign on the numerical keypad cannot be used.)

4. Spaces in a record name are Okay.

5. If an element for version or revision control is required, the last most element of the document name should be V or R followed by 3 digits. Record Name YYYYMMDD V001 or R001.

6. Do not use connecting words. Ex: ‘like,’ ‘to,’ ‘the,’ ‘and,’ ‘of.’

7. Do not use ‘Miscellaneous’ or ‘Other’ in the name.

8. The shortest title is preferred, however, a more specific with the file name shall be use when necessary for clarity.

9. Do not create more folder levels. Reclamation is limited to one folder in depth for each project. The following is a list of typical folders preserved for each project and include folders for Reclamation’s and/or Contractor’s information:

a. 01 Solicitation:

1) Reserved for Government use.

b. 02 Amendments:

1) Reserved for Government use.

c. 03 Contract:

1) Reserved for Government use.

01 31 30 - 8

d. 04 Post Award:

1) Reserved for Government use.

e. 05 NTP:

1) Reserved for Government use.

f. 06 Drawings:

1) Reserved for Government use.

g. 07 Specification:

1) Reserved for Government use.

h. 08 Pre-Construction Meetings:

1) INITIALS Pre-construction Meeting Agenda YYMMDD.

2) EPBR Pre-construction Meeting Agenda 20220711.

3) INITIALS Pre-construction Meeting Minutes YYMMDD.

4) EPBR Pre-construction Meeting Minutes 20220711.

5) INITIALS Pre-construction Security Meeting Agenda YYMMDD.

6) EPBRIP Pre-construction Security Meeting Agenda 20220711.

7) INITIALS Pre-construction Safety Meeting Minutes YYMMDD.

8) EPBR Pre-construction Safety Meeting Minutes 20220711.

9) Contractor or Government documents depending on Government requirements for a Pre-Construction Meeting and Contractor’s responsibilities in accordance with Section 01 31 22 Coordination Meetings.

i. 09 Progress Meetings:

1) INITIALS Weekly Coordination Meeting 001 Agenda

YYYYMMDD.

2) EPBR Weekly Coordination Meeting 001 Agenda 20250812.

3) INITIALS Weekly Coordination Meeting 001 Minutes

YYYYMMDD.

4) EPBR Weekly Coordination Meeting 001 Minutes 20250812.

5) Contractor submitted documents, Government corrections, and Contractor resubmissions.

j. 10 Safety:

1) INITIALS Incident Investigation Report Form YYYYMMDD.

2) EPBR Incident Investigation Report Form 20230706.

3) INITIALS MTR Folder 10 Safety YYYYMMDD.

01 31 30 - 9

4) EPBR MTR Folder 10 Safety 20250806.

5) Contractor and/or Government documents not addressed by RSN’s.

k. 11 Environmental:

1) INITIALS FEIS 508 Final YYYYMMDD.

2) EPBR FEIS 508 Final 20200915.

3) Contractor and/or Government documents not addressed by RSN’s.

l. 12 RSN:

1) RSN ## ## ##-#-### SUBMITTAL TITLE YYYYMMDD.

2) RSN 01 14 10-1-001 Land Use and Landscape Rehab Plan 20221213.

3) RSN 01 14 10-1-002 Land Use and Landscape Rehab Plan 20221220.

4) RSN 01 35 20-2 Monthly Accident Summary Report 20230120- Dec 2022.

5) RSN 01 35 30-2 Safety Inspection Report 001 20221213.

6) RSN 03 30 00-7-19 Concrete Test Report 001 20240611.

7) Contractor submitted documents, Government corrections, Contractor resubmissions, and Government approvals or acceptances.

m. 13 RFIs:

1) INITIALS RFI-001 Contractor Use Area 1 Potential Conflict

YYYYMMDD.

2) EPBR RFI-001 Contractor Use Area 1 Potential Conflict 20220926.

3) INITIALS RFI-030 Density Testing Requirements YYYYMMDD.

4) EPBR RFI-030 Density Testing Requirements 20230114.

5) Contractor submitted RFI’s and Government responses.

n. 14 RFC:

1) INITIALS RFC-001 Field Office YYYYMMDD.

2) EPBR RFC-001 Field Office 20221104.

3) Contractor submitted RFC’s and Government Responses.

o. 15 Modifications:

1) INITIALS Contract CONTRACT NUMBER Modification P00001

YYMMDD.

01 31 30 - 10

2) EPBR Contract 140R2022C0018 Modification P00001 20221115.

3) INITIALS Contract CONTRACT NUMBER Modification P00007

YYMMDD.

4) EPBR Contract 140R2022C0018 Modification P00007 20240424.

5) Documents issued by the Government.

p. 16 Verification of Quantities:

1) INITIALS Verification of Quantities 001 140R2022C0018

YYMMDD.

2) EPBR Verification of Quantities 001 140R2022C0018 20230113.

3) INITIALS Verification of Quantities 009 140R2022C0018

YYMMDD.

4) EPBR Verification of Quantities 009 140R2022C0018 20230831.

5) Contract submitted documents and Government prepared documents.

q. 17 Materials Testing:

1) INITIALS RCO Materials Testing Results 001 YYMMDD.

2) EPBR RCO Materials Testing Results 001 20250806.

3) Contractor and Government Materials Testing Results not covered by RSN’s.

r. 18 Photographs:

1) Reserved for Government use.

s. 19 Daily Construction Reports:

1) Reserved for Government use.

t. 20 Final Construction Report:

1) Reserved for Government use.

u. 21 Service Agreement Budget:

1) Reserved for Government use.

v. 22 Monthly Reports:

1) Reserved for Government use.

w. 23 Invoices:

1) INITIALS Pay Estimate and Invoice 001 CONTRACT NUMBER

YYYYMMDD.

2) EPBR Pay Estimate and Invoice 001 140R2022C0018 20230222.

3) INITIALS Pay Estimate and Invoice 006 CONTRACT NUMBER

YYYYMMDD.

01 31 30 - 11

4) EPBR Pay Estimate and Invoice 006 140R2022C0018 20230623.

5) Contractor submitted invoices and Government responses when necessary.

x. 24 Labor Interviews:

1) Reserved for Government use.

y. 25 Certified Payroll:

1) Provided by Contractor via secure method.

2) Reserved for Government use.

z. 26 Closeout:

1) INITIALS Transfer from Accounting AUC Account to Accounting PLANT Account.

2) EPBR Transfer from Accounting AUC Account to Accounting PLANT Account.

3) Contractor release of claims and other Government closeout documents.

aa. 27 Official Communication:

1) Miscellaneous official communications that do not fit into the other 28 folders.

bb. 28 Supporting Reference Documents:

1) Reserved for Government use.

cc. 29 As-Builts:

1) Reserved for Government use.

D. Reports:

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

a. Submittals that have been approved/Accepted.

b. Invoices paid to date.

1)

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.

01 31 30 - 12

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.

E. Document Security and Backup:

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

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

a. Show parties that have access to a document.

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

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

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

a. Backups shall be in pdf format.

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

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

G. Submittal Tracking and Control:

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

01 31 30 - 13

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:

1) A: Approved.

2) CA: Conditionally Approved – Some parts of the submittal are approved to started work. Noted parts to be corrected, resubmitted, and approved prior to start of work on noted parts.

3) NA for Not Approved – Submittal to be corrected, resubmitted, and approved prior to start of work.

4) Acc for Accepted.

5) CAcc for Conditionally Accepted Some parts of the submittal are accepted to started work. Noted parts to be corrected, resubmitted, and approved prior to start of work on noted parts.

6) NAcc – Submittal to be corrected, resubmitted, and approved prior to start of work.

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

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

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

01 31 30 - 14

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.

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

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

L. Correspondence:

1. Ability to generate letters and memos.

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

b. CDMS shall ability automatically assign sequential numbers to letters and memos.

2. Ability to generate responses to letters and memos.

a. System automatically generates memo suffixes, e.g. 1st response to Memo 32 to be 32.1, 2nd response to be 32.2, etc.

3. Official correspondence from Government to Contractor shall contain Government’s official letterhead and corresponding logos.

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

a. CDMS shall automatically assign sequential meeting numbers.

01 31 30 - 15

M. 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/CA/NA/Acc/CAcc/NAcc).

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.

N. Budget and Funding Source Tracking:

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 IMPLEMENTATION

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

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

B. Contractor shall input Schedule of Submittals before making submittals. Include:

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

2. Scheduled submittal date.

01 31 30 - 16

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.

3.02 TRAINING

A. Contractor shall provide at least 4 hours of on-line CDMS training for Contractor and Government employees associated with the project. Training shall be performed by the system provider for Contractor and Government simultaneously at an agreed time prior to system implementation. The total 4 hours training can be provided in a single session or in multiple sessions as recommended by the system provider. A list of up to 10 Government employees that require training will be provided to the Contractor by the COR with approval of RSN 01 31 30-1.

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 Prices Schedule for Mobilization and Preparatory Work.

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

1.02 DEFINITIONS

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

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

E. Work Breakdown Structure (WBS): A project management tool that breaks a project into smaller, manageable components or tasks, organized hierarchically. It helps define the project scope, assign responsibilities, and track progress effectively.

1.03 REFERENCE STANDARDS

A. Associated General Contractors of America (AGC)

1. AGC Manual Construction Planning and Scheduling Manual, 2004

B. National Institute of Standards and Technology (NIST)

1. NIST FIPS 140-3-19 Security Requirements for Cryptographic Modules, available at https://csrc.nist.gov/pubs/fips/140-3/final.

01 32 10 - 2

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.

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. Gantt chart (Bar chart) for project on 11 by 17-inch print(s) and in portable document format (.pdf).

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

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

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

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

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

2. Include:

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

01 32 10 - 3

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

c. Primavera layout file (.plf).

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

e. Narrative report specifically stating status of project.

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

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

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

f. Submittal Register:

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

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

3) This register document is separate from scheduling database.

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

1. Include:

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

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

c. Primavera layout file (.plf).

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

e. Narrative report explaining results and conclusions.

01 32 10 - 4

1.05 QUALIFICATIONS

A. Representative:

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

2. Experience shall include scheduling for at least two other projects of comparable complexity using Primavera P6.

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. Adjust Construction Program/schedule for seasonal weather conditions. Provide a narrative explaining the expected weather and plan for incorporation in schedule.

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

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

Assign weather calendars to work impacted by weather.

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

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

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

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

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

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

12. Include…