Alameda Zone 7 PL 84-99_Specifications_Phase 2and3_solicitation.pdf

ALAMEDA ZONE 7 FLOOD CONTROL CHANNELS - PL 84-99 REPAIRS ALAZONE7_P2-P3

PHASE 2 AND PHASE 3 SOLICITATION

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 20 00 PRICE AND PAYMENT PROCEDURES

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 PROJECT IDENTIFICATION

01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL

01 78 00 CLOSEOUT SUBMITTALS

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 21 GEOGRID

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 92 19 SEEDING

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 SUBMITTALS

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

1.2.2 Location

1.3 SITE ACCESS

1.4 EXISTING WORK

1.5 LOCATION OF UNDERGROUND UTILITIES

1.5.1 Notification Prior to Excavation

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

None

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The Alameda Zone 7 PL 84-99 Repair project is an Operations and Maintenance project to repair storm damage to flood control channels in Alameda County.

Damages consisted of erosion and bank failures during a series of atmospheric rivers between December 2022 and March 2023.

Work for this project is noted as "Alameda Zone 7 Flood Control Channels, PL 84-99 Repairs, Phase 2 and Phase 3."

Phase 2 of the project consists of a total of 21 repair sites including four (4) sites on Arroyo de la Laguna / Line B (B-09, B-10, B-11, B-12), four (4) sites along Arroyo del Valle / Line E (E-03, E-04, E-08, E-09), four (4) sites along Alamo Canal/Line F (F-11, F-12, F-13, F-14), eight (8) sites along Arroyo Mocho / Line G (G-03, G-05, G-07, G-08, G-09, G-22, G-24, G-25), and one (1) site along Tassajara Creek / Line K (K-14).

Phase 3 of the project consists of a total of 20 repair sites including sixteen (16) along South San Ramon Creek / Line J (J-01, J-02, J-03, J-05, J-06, J-11, J-12, J-13, J-16, J-17, J-18, J-20, J-21, J-30, J-36, J-38), three (3) sites along Alamo Canal / Line F (F-07, F-31, F-32), and one (1) site on Alamo Creek / Line F (F-04).

The existing flood control channels typically have earthen slopes previously constructed to grades of 2H:1V, with channel heights ranging from 15-30 feet. The damaged sites vary in sizes. Repairs to damaged sites will restore the slopes to original grade prior to the storm damages.

Earthwork will start with excavation of the damaged area, and removing disturbed soil and vegetation within the area. Repairs will consist of placing Rock Slope Protection (RSP) at the waterside slope toe, placing soil-filled RSP up to the 10-year water surface elevation, and restoring the upper portion of the slope with compacted backfill. After the remaining slope is backfilled and compacted above the stone protection, erosion control matting will be installed and hydroseeded.

The plan views of the drawings (C-101 sheets) show the approximate extents of the damaged areas for each site. The cross sections (C-301 sheets) show the planned repair type for each site. Sheet C-500 shows the typical repair details. The summary table on Sheet G-003 shows the design parameters and

SECTION 01 11 00 Page 2 estimated quantities for each site. The G-100 sheets show the haul routes and construction limits of work for accessing the sites.

The environmental work window for in-water work (activities below the top of creek bank) is limited to June 15th to October 15th, with potential to extend. The Phase 2 sites (base contract tasks) are accessible within the 2026 environmental work window. The Phase 3 sites (option contract tasks) are accessible within the 2027 environmental work window.

1.2.2 Location

The work is located as shown on the project drawings, approximately as indicated.

1.3 SITE ACCESS

Before work is started, arrange with the Contracting Officer or designated representative a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches.

1.4 EXISTING WORK

In addition to FAR 52.236-9 Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements:

a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer or designated representative. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

1.5.1 Notification Prior to Excavation

Notify the Contracting Officer or designated representative at least 48 hours prior to starting excavation work, and other notification as required by environmental permits and authorizations.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 3

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SUBMITTALS

1.2 SPECIAL SCHEDULING REQUIREMENTS

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

1.3.1.1 Subcontractors and Personnel Contacts

1.3.2 Working Hours

1.3.3 Work Outside Regular Hours

1.3.4 Exclusionary Period

1.3.5 Construction Site Sequencing

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 14 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel

1.2 SPECIAL SCHEDULING REQUIREMENTS

Permission to interrupt any active roads, railroads, or utility service must be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel become familiar with and obey job site regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear Personal Protective Equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry.

Mark Contractor equipment for identification.

1.3.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.3.2 Working Hours

Regular working hours will consist of a period between 8 a.m. and 5 p.m., Monday through Friday, excluding Government holidays.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer or designated representative approval. Make application 5 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title.

Based on the justification provided, the Contracting Officer or designated representative may or may not approve work outside regular hours. During

SECTION 01 14 00 Page 2 periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.

1.3.4 Exclusionary Period

All construction activities below the top of creek bank will be limited to June 15 to October 15, unless approved by the Contracting Officer.

Phase 2 sites are accessible within the 2026 environmental work window, unless approved by the Contracting Officer. Phase 3 sites are accessible within the 2027 environmental work window, unless approved by the Contracting Officer.

1.3.5 Construction Site Sequencing

Construction will be sequenced so that in-water construction activities occur last on sites with extensive riparian trees, unless approved by the Contracting Officer and in compliance with all permits. This includes Arroyo del Valle for Phase 2, and Alamo Creek for Phase 3. Staging, tree removal, and clearing or grubbing may still occur at these sites.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 3

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 SUBMITTALS

1.2 CONTRACT COST BREAKDOWN

1.3 SINGLE JOB PAYMENT ITEMS

1.3.1 Payments

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 20 00 Page 1

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Contract Cost Breakdown; G

1.2 CONTRACT COST BREAKDOWN

The Contractor must furnish within 15 days after the date of Notice to Proceed, and prior to the submission of its first partial payment estimate, a breakdown of its single job pay item or items which will be reviewed by the Contracting Officer or designated representative as to propriety of distribution of the total cost to the various accounts. Any unbalanced items as between early and late payment items or other discrepancies will be revised by the Contracting Officer or designated representative to agree with a reasonable cost of the work included in the various items. This Contract cost breakdown will then be utilized as the basis for progress payments to the Contractor.

1.3 SINGLE JOB PAYMENT ITEMS

Payment items for the work of this Contract for which Contract job payments will be made are listed in the SCHEDULE and described below. All costs for items of work, which are not specifically mentioned to be included in a particular job or unit price payment item, are included in the listed job item most closely associated with the work involved. The job price and payment made for each item listed constitutes full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, and for performing all work required for which separate payment is not otherwise provided.

1.3.1 Payments

Payments will be made for costs associted with the project site repairs.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 20 00 Page 2

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 VIEW LOCATION MAP

1.4 PROGRESS AND COMPLETION PICTURES

1.5 MINIMUM INSURANCE REQUIREMENTS

1.6 SUPERVISION

1.6.1 Superintendent Qualifications

1.6.2 Minimum Communication Requirements

1.6.3 Duties

1.6.4 Non-Compliance Actions

1.7 PRECONSTRUCTION CONFERENCE

1.7.1 Attendees

1.8 MOBILIZATION

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 30 00 Page 1

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2024) Safety -- Safety and Health Requirements Manual

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map

Progress and Completion Pictures

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Include aerial photographs. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer or designated representative. Submit with the monthly invoice digital photographs of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch as a digital file. Include a date designator in file names. Photographs provided are for unrestricted use by the Government.

SECTION 01 30 00 Page 2

1.5 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by applicable Federal, State, and local laws.

1.6 SUPERVISION

1.6.1 Superintendent Qualifications

Provide project superintendent with a minimum of 10 years' experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer or designated representative may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

1.6.2 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work. The Quality Control (QC) representative must also have fluent English communication skills.

1.6.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.6.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer or designated representative for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion. Furthermore, the Contracting Officer or designated representative may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.7 PRECONSTRUCTION CONFERENCE

Prior to commencing any work at the site, coordinate with the Contracting Officer or designated representative a time and place to meet for the Preconstruction Conference. The purpose of this conference is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value

SECTION 01 30 00 Page 3 report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out.

Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.7.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Office (SSHO), Quality Control Manager and major subcontractors.

1.8 MOBILIZATION

Contractor shall mobilize to the jobsite within 15 calendar days of issuance of Notice To Proceed (NTP). Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 4

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER REQUIREMENTS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Procurement Activities

3.3.4 Mandatory Tasks

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Area of Work Coding (AREA)

3.3.6.4 Modification Number (MODF)

3.3.6.5 Bid Item Coding (BIDI)

3.3.6.6 Phase of Work Coding (PHAS)

3.3.6.7 Category of Work Coding (CATW)

3.3.6.8 Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.7.3 Interim Completion Dates and Constraints

3.3.7.3.1 Start Phase

3.3.7.3.2 End Phase

3.3.8 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

3.3.12 Added and Deleted Activities

SECTION 01 32 01.00 10 Page 1

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

3.3.15 Retained Logic

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Cost Loading of Closeout Activities

3.3.18.1 As-Built Drawings

3.3.19 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data Storage Media

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Schedule Log

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Banding

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

3.8.6 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2017) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER REQUIREMENTS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.

SECTION 01 32 01.00 10 Page 3

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer or designated representative.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the

SECTION 01 32 01.00 10 Page 4 disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer or designated representative directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer or designated representative may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer or designated representative will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Tasks

Include the following activities/tasks in the initial project schedule and all updates.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission and approval of as-built drawings.

c. Contractor's pre-final inspection.

d. Correction of punch list from Contractor's pre-final inspection.

e. Government's pre-final inspection.

f. Correction of punch list from Government's pre-final inspection.

g. Final inspection.

SECTION 01 32 01.00 10 Page 5

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site:

http://rms.usace.army.mil.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer or designated representative. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are

SECTION 01 32 01.00 10 Page 6 not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.6.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

3.3.6.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer or designated representative. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast-track design and construction packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

SECTION 01 32 01.00 10 Page 7

3.3.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer or designated representative for approval on a case by case basis.

3.3.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.3.7.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.7.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.3.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.7.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

SECTION 01 32 01.00 10 Page 8

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs.

Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop seasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Contract Requirements.

Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's or designated representative's approval.

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer or designated representative. Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer or designated representative. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer or designated representative approval.

SECTION 01 32 01.00 10 Page 9

3.3.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer or designated representative.

3.3.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

3.3.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.3.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.3.17 Remaining Duration

Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.3.18 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.18.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.19 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that

SECTION 01 32 01.00 10 Page 10 indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.

3.4.1 Preliminary Project Schedule Submission

Within 7 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP.

Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities.

Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

SECTION 01 32 01.00 10 Page 11

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS.

These updates will enable the Government to assess Contractor's progress.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Data Storage Media

Provide two sets of data compatible with government approved storage media such as DOD Secure Access File Exchange or RMS submittals containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data storage media/files the Narrative Report and all required Schedule Reports. Label each data file indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis. Include the following information as minimum in the Narrative Report:

a. Identify and discuss the work scheduled to start in the next update period.

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

SECTION 01 32 01.00 10 Page 12

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer or designated representative.

Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.5.4 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer or designated representative will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

SECTION 01 32 01.00 10 Page 13

3.5.4.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.5.4.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5.4.4 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer.

Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work.