DRAFT_Specifications_No__20-C0942_1.pdf

Folsom Warehouse – Bridge Crane Replacement American River Division Folsom Unit - Central Valley Project, California Specifications No. 20-C0942

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 12 10 Other Contracts 01 14 10 Use of Site 01 14 12 Work Restrictions 01 14 30 Interruption of Service 01 31 22 Coordination Meetings 01 31 30 Contract Document Management System 01 32 10 Construction Program 01 33 00 Submittals 01 33 26 Electrical Drawings and Data 01 35 10 Safety Data Sheets 01 35 20 Safety and Health 01 35 30 Contractor’s Onsite Safety Personnel 01 35 50 Site Security 01 42 10 Reference Standards 01 46 00 Quality Procedures 01 51 00 Temporary Utilities 01 55 00 Vehicular Access and Parking 01 56 10 Protection of Existing Installations 01 56 15 Protection of Existing Utilities 01 57 20 Environmental Controls 01 57 30 Water Pollution Control 01 60 00 Product Requirements 01 74 00 Cleaning and Waste Management 01 78 30 Project Record Documents 01 79 20 Training

DIVISION 02 - EXISTING CONDITIONS

02 80 10 General Requirements for Asbestos Abatement 02 80 11 General Requirements for Coatings Containing Regulated Metals Abatement 02 82 20 Removal and Disposal of Asbestos Containing Materials 02 83 33 Recycling of Scrap Metal with Coatings Containing Hazardous Materials 02 87 20 Recycling and Disposal of Used Oil

DIVISION 03 – CONCRETE

03 62 20 Non-shrink Grout for Equipment and Metalwork

DRAFT

Folsom Unit - Central Valley Project, California Specifications No. 20-C0942

Table of Contents 00 01 10 - 2

DIVISION 09 – FINISHES

09 96 20 Coatings

DIVISION 25 – INTEGRATED AUTOMATION

25 00 01 Automation Control System 25 12 10 Programmable Logic Controller

DIVISION 26 - ELECTRICAL

26 05 02 Basic Electrical Materials and Methods 26 05 10 Conductors and Cables 26 05 20 Grounding and Bonding 26 05 33 Raceways and Boxes 26 05 60 Identification, Warning and Safety Signs 26 05 90 Wiring Checkout and Tests 26 08 00 Commissioning of Electrical Equipment 26 24 42 Distribution Panelboards 26 43 13 Surge Protection Devices for Electrical Circuits

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 13 Removal of Existing Crane 41 22 14 Bridge Crane 41 22 15 Bridge Crane Electrical Components 41 22 16 Crane Motors

DIVISION 51 - INFORMATION AVAILABLE TO OFFERORS

51 00 00 Information Available to Offerors 51 00 10 Photographs 51 00 50 Electronic Media Release 51 02 82 Hazardous Materials Survey and Analytical Results

DIVISION 52 - DRAWINGS

52 00 00 Drawings

END OF CONTENTS

Folsom Unit - Central Valley Project, California Specifications No. 20-C0942

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 2-miles north of Folsom, California, in Sacramento County.

1.02 PRINCIPAL COMPONENTS OF WORK

A. Design, build, furnish and install one 30 ton bridge crane to replace the existing bridge crane in the Folsom Dam Warehouse.

B. Principal Components of work include:

1. Existing crane removal and disposal.

a. Asbestos and other hazardous materials are present.

2. New crane design, fabrication, and installation.

3. New crane power supply up to the main power disconnect.

4. Perform a rail survey and optionally repair or replace existing rail system.

5. Perform commissioning tests and load test.

6. Perform operation and maintenance training.

7. Coordination with the Government to accomplish principal components of work.

1.03 SPECIFICATIONS REQUIREMENTS

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

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

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

1.04 DEFINITIONS

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

Summary of Work

01 11 00 - 2

1.05 ACRONYMS

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

1. CCAO (AO): Central California Area Office.

2. COR: Contracting Officer Representative.

3. TSC: Technical Service Center.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTION

Other Contracts

01 12 10 - 1

SECTION 01 12 10

OTHER CONTRACTS

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include cost of coordinating with other Contractors in the prices offered in the Price Schedule for other items of work.

1.02 OTHER WORK

A. During work under this contract, other work that may be performed in the vicinity of the work by Reclamation and other contractors. Coordinate with COR at NTP meeting.

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

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

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

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

F. Cooperate and coordinate with other contractors on the use of Government owned cranes.

G. Cooperate and coordinate with other contractors on the use of staging areas.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

Other Contracts

01 12 10 - 2

This page intentionally left blank.

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:

www.usbr.gov/mussels/prevention

1.03 SUBMITTALS

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

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

1. For each Contractor use site on Government land.

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

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

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

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

4) First-aid and medical facilities.

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

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.

C. RSN 01 14 10-2, Permit to Work:

1. Includes all requirements in 1.04 A through E.

1.04 PROJECT CONDITIONS

A. Before beginning onsite work, obtain Permit to Work from Bureau of Reclamation, Central California Area Office (CCAO):

1. Comply with CCAO permit requirements as shown below.

2. Permit will not be issued until the following submittals have been received and approved/accepted by Government:

a. RSN 01 14 10-1; Land Use and Landscape Rehabilitation Plan.

b. RSN 01 32 10-2; Baseline Schedule.

c. RSN 01 32 10-3; Updated Schedule required for issuing of permit as specified in Section 01 32 10 – Construction Program.

d. RSN 01 35 20-1; Safety Program.

e. RSN 01 35 50-1; Security Program.

B. Comply with all security requirements as indicated in Section I – Contract Clauses of Solicitation and these specifications prior to accessing/mobilizing to site, or as directed by COR.

C. Comply with Bureau of Reclamation and CCAO Hazardous Energy Control Program requirements. Any work under clearance will require a Special Work Permit that must be issued to Contractor prior to beginning work requiring interruption of service. See Section 01 14 30 – Interruption of Service for additional information.

D. Access to site is limited to Monday through Friday, 6:00 AM until 6:00 PM, excluding Federal holidays, unless a written request, 96-hours in advance is approved by COR.

E. Government land may be used for required construction facilities, coordinate land use with COR.

01 14 10 - 3

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

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

H. Cooperate and coordinate with other Contractors on use of access and haul routes, staging areas, and stockpile areas; maintaining roads; maintaining dust-free operations, and abiding by all applicable safety regulations, especially during hauling operations.

I. Consult with COR for coordination efforts.

J. Housing for Contractor personnel will not be permitted on Government land.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 RESTORATION

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

01 14 10 - 4

Work Restrictions

01 14 12 - 1

SECTION 01 14 12

WORK RESTRICTIONS

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 WORK RESTRICTIONS

A. Allowable work hours are 6:00 am to 6:00 pm, Monday through Friday, unless otherwise approved by COR.

B. Alternate work schedules including weekends and holidays may be allowed as approved by COR. Provide COR a written notice 14 working days in advance of proposed alternate work schedule for review and approval.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

END OF SECTIONDRAFT

Work Restrictions

01 14 12 - 2

Interruption of Service

01 14 30 - 1

SECTION 01 14 30

INTERRUPTION OF SERVICE

PART 1 GENERAL

1.01 MEASUREMENT AND PAYMENT

A. Cost:

1. Include in prices offered in the Price Schedule for items of work for which interruption of services are required.

1.02 SUBMITTALS

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

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

1. Area where work will be done annotated onsite plan drawing showing pertinent features.

2. Show construction outage greater than 2-hours in construction schedule.

3. Commencement time of work.

4. Duration of work.

5. Number of personnel and their classification.

6. Description of equipment to be used.

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

8. Provide Job Hazard Analyses (JHAs) or written procedure for isolating and removing each hazard source through lockout and tagout procedures for approval.

9. List any impacts to power system operating conditions.

10. Coordinate use of Warehouse and list areas that will be occupied at different parts of the project.

1.03 PROJECT CONDITIONS

A. Schedule and coordinate interruption of services with COR who shall coordinate work and approvals with Operations and other Government entities as necessary.

B. Any interruption of service shall be minimized to extent possible:

1. Contractor shall have approved Design drawings, Materials and Installation/Demolition Plans prior to approval of Interruption of Service Request, and any work occurring under an interruption of service.

01 14 30 - 2

2. All materials/fabrications for installation shall be approved and readily available prior to start of interruption of service.

C. No specific request for an interruption of service will be considered unless COR has reasonable assurances that materials and equipment required for work will be on site and Contractor will be prepared to perform work on start date and during period of time requested for specific interruption of service.

D. An interruption of service period starts when equipment and systems are de-energized or otherwise affect normal intended operation of equipment and system in any way because of work required under these specifications:

1. Interruption of service period ends when Government accepts work and equipment/system is restored to normal operation.

2. See Facilities Instructions, Standards, and Techniques (FIST) Volume 1-1 for interruption of service requirements:

a. COR or local Government representative shall be final authority in interpreting FIST 1-1 and applicability of any interruption of service deemed necessary.

E. Special work Permit must be issued to Contractor prior to any work starting under an interruption of service.

F. The following requirements must be met before beginning onsite work associated with interruption of service:

1. Coordinate with COR to obtain Special Work Permit per Hazardous Energy Control Program (HECP) requirements from an authorized Bureau of Reclamation representative/Job Supervisor:

a. Special Work Permit will not be issued until the following requirements have been met:

1) Proposed work is described and in compliance with Bureau of Reclamation and CCAO’s HECP and FIST 1-1, copies of which can be made available to Contractor upon request.

2) Interruption of service request is approved.

3) Mandatory: Minimum 1-hour HECP familiarization for all Contractor personnel working onsite prior to entering areas under interruption of service. Coordinate with OGR a minimum of 3 working days in advance to schedule training.

4) CCAO Operations implements approved Interruption of Service Request via actual lockout/tagout therefore isolating hazardous energy.

01 14 30 - 3

G. Work not associated with an interruption of service can be accomplished after CCAO Permit to Work is issued in accordance with Section 01 14 10 – Use of Site.

H. When work cannot be performed during an approved interruption of service period, notify COR that interruption of service is not required, and requires rescheduling as applicable:

1. Interruption of service may be scheduled during off-peak periods, nights, or weekends, with required 96-hour advance notice.

2. Government reserves the right to schedule interruption of services for any period during 24-hour day, any day of the week.

3. Contractor’s request for interruption of services, work scheduling, and delivery of materials on site will be governed by available time and interruption of service periods.

I. Provide temporary power for critical loads as may be required by specific work plan.

Temporary power for these loads is only required if Contractor is disconnecting or removing the permanent power source from the load:

1. Critical loads include the following:

a. Cranes.

b. Station lighting and receptacles.

c. Station Battery and UPS System.

d. Life Safety Systems (including fire related systems and smoke control systems).

e. Security Systems.

f. Facility control components.

g. Sump pumps.

2. Maximum outage for critical loads: 4-hours or as limited by applicable national, State or local code, whichever is more restrictive.

J. Outages for electrical distribution equipment that does not impact critical loads limited to a maximum of 5-days.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

01 14 30 - 4

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. Interruption of Service: A Contractor requested temporary suspension or interruption of normal facility operations including blocking or closing roads, temporary disconnection of utilities, draining systems of water for access, reduction of stopping pumping activities, locking out of electrical systems or equipment, disconnection of fire alarm systems, or other activities that prevent normal activities of a facility. May also be known as an Outage.

1.03 REFERENCE STANDARDS

A. Bureau of Reclamation (Reclamation)

1. RSHS Reclamation Safety and Health Standards including revisions posted at www.usbr.gov/ssle/safety/RSHS/rshs.html.

1.04 PRECONSTRUCTION SECURITY MEETING

A. The preconstruction security meeting shall be scheduled before the Contractor’s Site Security Plan has been submitted and accepted. The meeting will be coordinated between Contractor project management and COR. Topic covered will include:

1. Contractor’s Site Security Program.

2. Site Security Coordination.

1.05 PRECONSTRUCTION SAFETY MEETING

A. Coordinate preconstruction safety meeting with COR at work site project office before starting onsite work in accordance with RSHS 1.03 2.C, 1.03 6.a and 1.03 2.b.

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

a. Site-specific hazards for the major phases of the work:

01 31 22 - 2

1) The meeting will cover site-specific hazards for the major phases of the work including requirements for the specific operations, equipment, inspections, qualifications, and other job specific requirements.

2) A simple reading of the Contractors safety program shall not be considered adequate and is not intended for the meeting.

2. Required joint safety policy meetings.

3. Required toolbox safety meetings.

4. Weekly joint safety inspections.

5. Job hazard analyses (JHAs).

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

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 Construction Manager, Contract Specialist (CS), Contract Officer (CO), Area Manager’s Representative, Field Offices Representative, and Regional Engineer’s and 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.

01 31 22 - 3

d. Outages.

e. Environmental compliance.

f. Security.

g. Personnel.

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) Quantities and Invoices.

6. Other outstanding issues.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 IMPLEMENTATION

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

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

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

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

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

01 31 22 - 4

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

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 (CDMS):

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. CDMS: Contract Document Management System.

B. CO: Contracting Officer.

C. COR: Contracting Officer’s Representative.

D. PM: Project Manager.

E. RFC: Request for Change.

F. RFI: Request for Information.

G. RFP: Request for Proposals.

1.03 SUBMITTALS

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

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

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

2. Documentation of system capabilities.

3. Instructions for system use.

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

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

01 31 30 - 2

2. Submit via:

a. Electronic storage device approved by Government, of all documents uploaded to CDMS or,

b. Use IronKey, by Kingston Technology, or approved equal, Encrypted Hard Drive or Encrypted Flash Drive, meeting FIPS 140-2 requirements for Level 3 Security and chain-of-custody procedures. Submit with all documents uploaded to CDMS.

1) All passwords and access shall be sent via United States Postal Service using Express Mail or equal.

1.04 APPLICATION

A. CDMS: Contract Document Management System:

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

a. Specifications.

b. Contract Drawings.

c. Submittals.

d. Approval Drawings (Contractor generated document).

e. Shop Drawings (Contractor generated document).

f. Final Drawings (Contractor generated document).

g. As-built Drawings (Contractor generated document).

h. REA: Request for Equitable Adjustment (Contractor generated document).

i. RFC: Request for Change (Contractor generated document).

j. RFI: Request for Information (Contractor generated document).

k. RFP: Request for Proposal (Government generated document).

l. RFS: Request for Substitution (Contractor generated document).

m. MOD: Contract Modification.

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

o. Government Inspection Reports.

p. Contract Schedules.

q. Meeting Agendas and Meeting Minutes.

r. Letters, Memos, and other typical contract correspondence.

01 31 30 - 3

1.05 QUALIFICATIONS

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

1.06 CDMS REQUIREMENTS

A. CDMS shall be capable of generating, storing, tracking, categorizing, and managing construction contract documents. Construction Contract Documentation includes:

Submittals (typically .pdf files of text documents or drawings); RFIs, RFCs, and RFPs;

Contractor Proposals; Value Engineering Change Proposals; Invoices and Progress Payments; Construction Schedules; Meeting Agendas and Meeting Minutes;

Correspondence; Memos and Deficiency Notices; Contract Modifications and similar documents. Documentation may be prepared by the Construction Contractor or by Reclamation.

B. Reclamation shall be able to easily access documents and to track when documents were received or returned, as well as determine the status of the documents. Reclamation shall be able to generate reports that list and sort the documents by status as well as generate alerts when documents requiring review exceed allowable review time. Document generation shall include submittals and RFIs, responses, Meeting Minutes, RFCs, RFPs, and correspondence.

C. Documents may be generated by either the Contractor or by Reclamation. Each party needs the capability to maintain document security within its organization unless/until it chooses to share it with the other party. Once documents are shared, they shall be secured so that no changes can occur without a record of the changes being made. The CDMS shall be capable of producing a complete and logically organized set of all documents within the CDMS in both .pdf and .xml format. The documents shall be downloadable to ftp sites where Reclamation and other organizations can each access their own data confidentially.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.01 IMPLEMENTATION

A. Document Access:

1. Web-based document storage where all project construction documents are stored and may be accessed by authorized organizations and individuals via an internet site.

01 31 30 - 4

2. Accessed via Web Browser from any computer including remote sites with internet access. Compatible with Apple Safari, Mozilla Firefox, and Internet Explorer.

3. Ability to upload documents in a variety of formats including but not limited to Word, Excel, Adobe Acrobat, MS Project, Primavera 6.0 or higher, AutoCad 2020 or higher, and Contract Manager, and make them available to users for download. Documents shall be grouped into separate categories.

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

a. Adobe Acrobat, Portable Document Format (.pdf).

b. Microsoft Word; Microsoft Word 97-2003 Document (.doc), Word Document (.docx).

1) With a copy provided in Adobe Acrobat, Portable Document Format (.pdf).

c. Microsoft Excel; Microsoft Excel 97-2003 Worksheet (.xls), Excel Workbook (.xlsx).

1) With a copy provided in Adobe Acrobat, Portable Document Format (.pdf).

d. Oracle Primavera P6 Project Manager, XML and XER file Extension (.xml and .xer) and P6 layout file (.plf).

1) With a copy provided in Adobe Acrobat, Portable Document Format (.pdf).

e. Autodesk Drawing File AutoCAD 2023 (.dwg) or later.

1) With a copy provided in Adobe Acrobat, Portable Document Format (.pdf).

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

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

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

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

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

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

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

01 31 30 - 5

7. 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 new submittal);

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

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

8. Ability to link files; examples:

a. RFP linked to Modification.

b. Submittal linked to Specification Section or Drawing.

9. Ability for Government to perform bulk downloads of CDMS Data. Bulk downloads will be used to download Final CDMS data, shop drawings and other large sets of CDMS data.

10. Data shall be preserved for a period of 3 months after completion of Contract to allow Government time to completely download all necessary documents and final data stored in the CDMS System.

11. No Cost Time Extension:

a. If the Contractor agrees to a No-Cost Time Extension the contractor shall maintain the CDMS service during the of the period of the No-Cost Time Extension in addition to other requirements.

B. Reports:

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

a. Submittals that are approved or are not approved.

b. 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. Modification processing Turn-Around.

d. Total Modification costs.

e. Total Modification 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.

01 31 30 - 6

a. For example: in submittal report, clicking on 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.

C. Document Security and Backup:

1. Secure Sockets Layer (SSL) encryption for secured data exchange between browser and server to enable 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 File Transfer Protocol (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.

D. General Tracking and Control:

1. Documents shall be grouped into categories (Submittals, REA, RFC, RFI, RFP, RFS, Modification, Daily Inspection Reports, Meeting Minutes, etc.).

2. CDMS shall track:

a. When documents were received or returned, as well as status of documents (e.g. Under Review; or Returned Approved, Conditionally Approved, Not Approved, Accepted, Conditionally Accepted or Not Accepted, and resubmittal requirement in accordance with Section 01 33 00 – Submittals, Part 1.06 – Review of Submittals).

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

c. When a reviewer has opened an item.

E. Submittal Tracking and Control:

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

2. Supply standard submittal form for entering information. CDMS shall allow customizing of standard submittal form. Contractor shall be able to enter submittal summary information (required submittal number, title, description, due

01 31 30 - 7 date, and specification section shall be required fields) and then upload submittal data in electronic format.

3. CDMS shall track date received, date response due, date returned, and approval status:

a. Status designations may be modified to fit Government standard designations – A, CA, NA, Acc, CAcc, NAcc (Approved, Conditionally Approved, Not Approved, Accepted, Conditionally Accepted, Not Accepted in accordance with Section 01 33 00 – Submittals, Part 1.06 – Review of Submittals.).

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.

F. RFI Tracking and Control:

1. Supply standard RFI form to enter information.

2. Ability to create or attach documents to 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.

G. Inspection Reports Tracking and Control:

1. Ability to attach Government standard inspection and report forms into CDMS and ability to create customizable inspection forms in CDMS. Typical forms:

a. Daily Inspection Report (DIR).

b. Survey requests.

c. Inspection reports.

d. Testing reports.

2. Ability to link or attach photos to forms and link forms to other documents within

CDMS.

H. Contract Modifications:

1. Provide standard Contractor Proposal form with ability to attach documents and link to other documents within CDMS.

2. Provide ability to upload Government’s standard Modification form and RFP forms, or create an acceptable alternative, to enter information.

01 31 30 - 8

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

CDMS.

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

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

I. 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 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. first response to Memo 32 to be 32.1, second 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.

J. Miscellaneous Tracking and Controls.

1. Ability to generate reports tracking REAs, RFCs, RFIs, RFPs, RFSs, Modifications, Submittals, Memos, DIR’s, survey requests, plant inspection reports, and testing reports.

2. Ability to filter logs based on criteria:

a. Submittals: Specification Section, Days Out, Status (Approved {A}, Conditionally Approved {CA}, Not Approved {NA}, Accepted [Acc], Conditionally Accepted {CAcc}, Not Accepted {NAcc}).

b. RFI’s: Days out, Status (Open/Closed), Specification Section/Dwg No., Responsibility/Ball-In-Court.

3. Ability to sort Logs based on a criterion, e.g. for Submittal, Specification Section, Days Out, Status, or other criterion determined by COR.

4. Ability to provide forms to match Reclamation’s Contract Modification form and Progress Payment form or other forms when needed.

5. Ability to track cost exposure with links to Requests for Information and Change Order Requests.

01 31 30 - 9

6. Ability to measure productivity benchmarks on a project such as computing average review days for RFIs and submittals, categorize Modifications, and track total Modification percentages by category.

7. Ability for keyword search of documents in database.

8. Ability for CDMS Generated Notification via email to Team Members of:

updates to project information; changes to project information; and alerts.

9. Ability for Reclamation to create Master List of Anticipated Submittals (“Schedule of Submittals”) and require Contractor to pick from that list when submitting submittal.

K. Administration:

1. Contractor shall be administrator of CDMS site. Contractor shall maintain and manage CDMS services directly with software provider. All data and stored information shall belong to Contractor who has sole responsibility for CDMS solution. At the end of the project all information stored in the CDMS shall be transferred to the Government by the Contractor.

2. The Contractor shall provide administrator rights to Government administrator(s) for Government access and sharing of CDMS data within the Government.

Government administrator(s) may include:

a. Contract Manager,

b. Contract Officer’s Representative,

c. Field Engineer, and/or

d. Contract Officer/Specialist.

L. Contractor shall share access to CDMS site and data with Government for Contract purposes as described herein.

M. In accordance with Reclamation Directive and Standard RCD 05-01, all information received, created, or compiled by Reclamation officials, employees, contractors, and other staff (employees) is property of Federal Government and must be maintained in accordance with established standards.

1. CDMS shall not be considered as storage of official records or correspondence.

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

O. Contractor shall input complete Schedule of Submittals before making submittals.

Include:

01 31 30 - 10

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

2. Submittal due dates from Table 01 33 00A.

P. Contractor shall provide a report of submittal status weekly for review at weekly coordination meetings or as otherwise requested by COR. Submittal status reports shall be in table format and include:

1. Required Submittal Numbers (RSN).

2. Section Titles.

3. Submittal Titles.

4. Dates Submitted.

5. Dates of Responses.

6. Approval status (listed above).

7. Days in review.

8. Due dates.

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

END OF SECTION DRAFT

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.

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. Furnish schedule in CDMS.

01 32 10 - 2

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

1) With a copy provided in Adobe Acrobat, Portable Document Format (.pdf).

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.

a. Include:

1) Construction Program database with updated activity and milestone data.

2) Definition of project calendars if revised from baseline calendars.

3) Primavera layout file (.plf).

01 32 10 - 3

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

5) Narrative report specifically stating status of project.

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

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

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

6) Submittal Register:

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

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

c) 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: Experienced in developing and maintaining construction schedules and knowledgeable of activities and progress on-site to develop and maintain accurate and reliable schedules.

1.06 GENERAL

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

1.07 SCHEDULES

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

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

Logically sequence activities.

2. Prepare detailed activity network for accomplishing required work organized by Work Breakdown Structure (WBS). Utilize WBS in lieu of activity codes for organization of schedule. If activity codes are utilized in addition to WBS, use unique activity code names assigned as project codes rather than global codes.

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

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

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

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

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

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

Assign weather calendars to work impacted by weather.

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

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

8. Include separate activities for submittal preparation and submittal reviews when submittal addresses work that involves significant quantities, long lead times, is on the critical path or near critical path, or as requested by the COR. Assign

01 32 10 - 5

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 table of abbreviations used in the schedule, listed and defined alphabetically.

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

14. Use durations in units of whole workdays.

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

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

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

B. Baseline Schedule:

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

C. Updated Schedule:

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

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

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

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

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

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