Redwood City Channel_FY23_Specs_(For Solicitation) 2023-09-15 (002).pdf

Redwood City Channel FY23 Maintenance Dredging

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 32 01.00 10 PROJECT SCHEDULE

01 32 23 HYDROGRAPHIC SURVEY

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENT SAFETY REQUIREMENTS (DREDGING)

01 45 00.00 10 QUALITY CONTROL

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

01 50 00 TEMPORARY FACILITIES AND CONTROLS

01 57 19.01 43 TEMPORARY ENVIRONMENTAL CONTROLS FOR DREDGING IN SAN

FRANCISCO BAY

01 57 19.99 43

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 20 23 DREDGING

35 20 23.13 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM SCOW -

MONITORING PROFILE

35 20 24 AQUATIC DISPOSAL

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

ATTACHMENT LIST

SECTION SUBPART

01 11 00 DMMO Suitability Determination

01 33 00 Submittal Register 01 35 26

1.5

Summary of Worker Compensation Claims 01 35 26 1.12.3 USACE Summary of Contractor Work-Related

Injuries and Illnesses 01 35 26 1.12.3 Summary Guide for Completing USACE

Contractor Monthly Summary Record of Injuries/Illnesses & Work Hour Exposure

35 20 23 1.3.1.1 DDLS

35 20 23 1.3.1.2 DMDSL logs

01 57 19.99 43 3.1 Biological Observation Log

ATTACHMENT

HERRING SPAWNING OBSERVERS

1.3

01 32 23 1.1.1

Survey QC Log

W912P723B0012

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

SUMMARY OF WORK

08/11

PART 1 GENERAL

1.1 PROJECT DESCRIPTION

1.1.1 Requirements

1.1.2 Constraints

1.2 MEETINGS

1.2.1 Preconstruction Conference

1.3 CONTRACTOR PERFORMANCE EVALUATIONS

1.4 PERMITS

1.5 PUBLIC SAFETY

1.5.1 General

1.6 PUBLIC UTILITIES AND PRIVATE IMPROVEMENTS

1.7 SAFETY OF STRUCTURES

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

08/11

PART 1 GENERAL

1.1 PROJECT DESCRIPTION

The work includes maintenance dredging of the federal navigation channel in Redwood City Harbor, which cannot begin before 1 June in any year.

1.1.1 Requirements

a. Dredge Redwood City Harbor Channel to -30.0-ft MLLW as stated in Section 00 10 00 Pricing Schedule and Plan Sheet ID G-02: General Notes for acceptance.

b. Dredging and disposal shall be in accordance with environmental schedule constraints included in these contract requirements.

c. All placement at Eden Landing Nearshore Site shall be in accordance with all site specific requirements included in these contract requirements.

d. Scow Certification is required for ocean disposal operations.

1.1.2 Constraints

Hopper dredging is prohibited for this project.

1.2 MEETINGS

1.2.1 Preconstruction Conference

After award of contract, a preconstruction conference will be held at such time and location as determined by the Contracting Officer or delegated representative for purposes of discussing and developing mutual understanding between the Contracting Officer or delegated representative and the Contractor's Representatives regarding the terms, conditions, and requirements of the contract. Members of the conference from the Government will include the quality assurance staff, the Contracting Officer or delegated representative, construction staff, and environmental staff. Members from the Contractor shall include the dredge master, chief hydrographic surveyor, and the quality control staff. The discussion will include, but will not be limited to, the following:

-Contractor supervisory and quality control project staff

-Correspondence procedures

-Accident Prevention Plan

-Environmental Protection Plan and Pollution control program

-Quality Control and Hydrographic Surveying

SECTION 01 11 00 Page 2

-Project scheduling and payment procedures

-Resident Management System (RMS-QC)

-Other subjects that may be of interest to the contracting parties

-Schedule of Weekly Meeting

1.3 CONTRACTOR PERFORMANCE EVALUATIONS

The Contractor's performance shall be evaluated using the Construction Performance Assessment Reporting System (CPARS) in accordance with Subpart

36.201 (Evaluation of Contractor Performance) of the Federal Acquisition Regulation and Engineering Regulation 415-1-17. The Contractor may access, review, and comment on the evaluation for a period of 60 days. Accessing and using CPARS requires Public Key Infrastructure (PKI) certification.

The certification is a Department of Defense requirement and was implemented to provide security in electronic transactions. This certification is purchased from an External Certificate Authorities (ECA) vendor. Contractor access to CPARS is required for Contractor to participate in the performance evaluation process. PKI certification is the sole responsibility of the Contractor. Current information about the PKI certification process and known PKI vendors can be found at the following link: http://www.cpars.gov/.

1.4 PERMITS

The Contractor shall obtain and comply with all licenses and permits required by Federal, State, and local laws, codes, and regulations unless otherwise specified in these contract documents. The Government has provided the requirements of the 2020-2024 Water Quality Certification in accordance with the Clean Water Act, the requirements of the 2020-2024 Coastal Zone Management Act (CZMA)Consistency Notification, and the LTMS Biological Opinion and Essential Fish Habitat consultation. The Contractor shall comply with these requirements and provisions in these contract specifications included in Sections 01 57 19.01 43 TEMPORARY ENVIRONMENTAL CONTROLS FOR DREDGING IN SAN FRANCISCO BAY and 35 20 23 DREDGING. The Water Quality Certification, CZMA Consistency Notification and the following permits for Eden Landing Nearshore Site are available upon request.

(1) National Historic Preservation Act Section 106 Concurrence

(2) Endangered Species Act Not likely to Adversely Affect Concurrence and Magnuson-Stevens Essential Fish Habitat Conservation Recommendations

(3) Fish and Wildlife Coordination Act Planning Aid Letter

(4) Clean Water Act Section 401 Water Quality Certification

(5) Coastal Zone Management Act Letter of Agreement

(6) National Environmental Policy Act Environmental Assessment and Finding of No Significant Impact

SECTION 01 11 00 Page 3

1.5 PUBLIC SAFETY

1.5.1 General

The Contractor shall provide guard personnel as required to provide protection in the interest of public safety. Whenever the Contractor's operations create a condition hazardous to the public, he shall furnish at their own expense and without cost to the Government, such guards as are necessary to give adequate warning to the public of any dangerous conditions to be encountered, and he shall furnish, erect, or maintain such lights, signs, barricades or fences, and other devices as are necessary to prevent accidents and to avoid damage or injury to the public. Flagmen and guards, while on duty and assigned to give warning to the public that the dredging is being accomplished, and of any dangerous conditions to be encountered as a result thereof, shall be equipped with appropriate safety equipment and a red flag. Signs, flags, lights, and other warning and safety devices shall conform to applicable city, county, and state requirements. Should the Contractor appear to be negligent in furnishing adequate warning and protective measures, the Contracting Officer or delegated representative will direct attention to the existence of a hazard, and the necessary warning and protective measures shall be furnished and installed by the Contractor without additional cost to the Government. The installation of any general illumination shall not relieve the Contractor of their responsibility for furnishing and maintaining all devices necessary to provide protection to all parties concerned. As part of the best pracictces, the contractor is highly encouraged to hold a safety meeting, open to the general public, at a venue frequented by the boating community to proactively inform and receive feedback from the public of the upcoming dreging work and task timelines.

1.6 PUBLIC UTILITIES AND PRIVATE IMPROVEMENTS

The Contractor shall take care to preserve and protect any existing utilities or features improvements from injury or damage during construction operations. All damages shall be promptly repaired or replaced by the Contractor. The Contractor shall notify the Contracting Officer or delegated representative immediately if any utility or structure has been damaged by the Contractor. The Contractor shall assume full responsibility for reimbursing the owners for any damage to thei properties, utilities, or improvements, or interference with their services caused through the dredging operations. The Contractor is not relieved from the responsibility set forth in "FAR 52.236-3, Site Investigation and Conditions Affecting the Work" except as provided above.

1.7 SAFETY OF STRUCTURES

The Contractor shall use reasonable and proper care in the execution of the work to assure the stability of piers and other structures lying on or adjacent to the site of work, insofar as they may be jeopardized by the dredging operations and on account of moving or mooring of equipment. The Contractor shall make good all damages resulting from the moving and mooring of equipments and from dredging operations insofar as such damages may be caused by variations in locations and/or depth of dredging below that ordered by the Contracting Officer or delegated representative.

SECTION 01 11 00 Page 4

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 5

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 PAYMENT

1.3 SUBMITTALS

1.4 PROJECT SCHEDULER QUALIFICATIONS

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 Activity Code Structure

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (RESP)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase Work Coding (PHAS)

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestones and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

3.3.8.3.1 Start Phase

3.3.8.3.2 End Phase

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out of Sequence Progress

3.3.13 Added and Deleted Activities

SECTION 01 32 01.00 10 Page 1

3.3.14 Original Durations

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remained Duration

3.3.19 Cost Loading of Closeout Activities

3.3.20 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 Electronic Files

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 REQUEST FOR TIME EXTENSIONS

3.6.1 Justification of Delay

3.6.2 Time Impact Analysis (Prospective Analysis)

3.6.3 Forensic Schedule Analysis (Retrospective Analysis)

3.6.4 Fragmentary Network (Fragnet

3.6.5 Time Extension

3.6.6 Impact to Early Completion Schedule

3.7 FAILURE TO ACHIEVE PROGRESS

3.7.1 Artificially Improving Progress

3.7.2 Failure to Perform

3.7.3 Recovery Schedule

3.8 OWNERSHIP OF FLOAT

3.9 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

3.10 PRIMAVERA P6 MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

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

1.2 PAYMENT

Separate payment will not be made for providing and maintaining an effective project schedule, and all associated costs will be included in applicable bid schedule prices.

1.3 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Preliminary Project Schedule; G, 01 32 01.00 10-3.4.1

Initial Project Schedule; G, 01 32 01.00 10-3.4.2

Periodic Schedule Updates; G, 01 32 01.00 10-3.4.3

1.4 PROJECT SCHEDULER QUALIFICATIONS

Each schedule submittal shall identify the Project Scheduler who was responsible for the preparation of the schedule submittal and all required updating and production of reports. The Project Scheduler 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

Contractor shall furnish two scheduling software licenses, two computers, and training for two Government employees in the use of the software if the contractor chooses to use software other than Primavera P6. 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, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates completed for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling is the responsibility of the Contractor. Contractor management personnel must actively participate in development and maintenance of 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 delegated 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 delegated representative directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer or delegated 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 delegated 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, review and acceptance of features require design completion Submission, review and acceptance of design packages.

c. Submission of mechanical/electrical/information systems layout drawings.

d. Long procurement activities

e. Submission and approval of as-built drawings.

f. Contractor's pre-final inspection.

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

SECTION 01 32 01.00 10 Page 5

h. Government's pre-final inspection.

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

j. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, acceptance, design reviews, 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 Activity Code Structure

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 RMS CM web site: http://rms.usace.army.mil.

The SDEF format is as follow:

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.7 Standard Activity Coding Dictionary

The Contractor shall develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer or delegated representative, will result in its disapproval. The Contracting Officer or delegated representative will consider, but is not limited to, the

SECTION 01 32 01.00 10 Page 6 following characteristics and requirements to determine appropriate level of detail:

3.3.7.1 Workers per Day (WRKP)

Assign Workers per Day for all field or direct work activities, if directed by the Contracting Officer or delegated 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.7.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 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.7.3 Area of Work Coding (RESP)

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.7.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 delegated representative. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.7.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.7.6 Phase Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are

SECTION 01 32 01.00 10 Page 7 design phase, 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.7.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, design, design submittal, design reviews, review conferences, permits, construction submittals, 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.

3.3.7.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.8 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 delegated representative for approval on a case by case basis.

3.3.8.1 Project Start Date Milestones 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.8.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

SECTION 01 32 01.00 10 Page 8 longest path.

The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

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

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

3.3.10 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 or delegated representative's approval.

3.3.11 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 (Dredge Daily Report) will result in disapproval of the Contractor's schedule.

3.3.12 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 delegated representative. Propose logic corrections to eliminate out of

SECTION 01 32 01.00 10 Page 9 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.13 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 delegated representative. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer or delegated representative approval.

3.3.14 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 delegated representative.

3.3.15 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.16 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.17 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.18 Remained 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.19 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

SECTION 01 32 01.00 10 Page 10

Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.20 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that 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 man-hours) 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, reports, and network diagrams required for each submission are contained in paragraph

3.5 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 30 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 30 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 30 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 30 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW). Submit the Initial Project Schedule for approval within 21 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.

SECTION 01 32 01.00 10 Page 11

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 21 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.

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 Electronic Files

Provide one set of data in electronic format in RMS containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include in the data electronic file, 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

SECTION 01 32 01.00 10 Page 12 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.

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer or delegated 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

SECTION 01 32 01.00 10 Page 13

Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer 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.

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 REQUEST FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer or delegated representative in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.6.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer or delegated representative.

SECTION 01 32 01.00 10 Page 14

3.6.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer or delegated representative based on industry standard AACE 52R-06. Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer or delegated representative determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer or delegated representative, no other changes may be incorporated into the schedule being used to justify the time impact.

3.6.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer or delegated representative based on industry standard AACE 29R-03 .

3.6.4 Fragmentary Network (Fragnet )

Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer or delegated representative prior to incorporation into the project schedule.

3.6.5 Time Extension

The Contracting Officer or delegated representative must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.6.6 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.7 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer or delegated representative may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding

SECTION 01 32 01.00 10 Page 15 additional crews, longer work hours, extra work days, etc.

3.7.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.7.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer or delegated representative pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

3.7.3 Recovery Schedule

Should the Contracting Officer or delegated representative find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

3.8 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

3.9 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Import the schedule data into the Resident Management System Contractor Mode (RMS CM) and export the RMS CM data to the Government. This data is considered to be additional supporting data in a form and detail required by the Contracting Officer or delegated representative pursuant to FAR 52.232-5 - Payments under Fixed- Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 - Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and matching electronic export from RMS CM of the application for progress payment.

3.10 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. The

SECTION 01 32 01.00 10 Page 16 following settings are mandatory and required in all schedule submissions to the Government:

a. Activity Codes must be Project Level, not Global or EPS level.

b. Calendars must be Project Level, not Global or Resource level.

c. Activity Duration Types must be set to "Fixed Duration & Units".

d. Percent Complete Types must be set to "Physical".

e. Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to 8.0 Hour days.

f. Set Schedule Option for defining Critical Activities to "Longest Path".

g. Set Schedule Option for defining progressed activities to "Retained Logic".

h. Set up cost loading using a single lump sum labor resource. The Price/Unit must be $1/hr, Default Units/Time must be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

i. Activity ID's must not exceed 10 characters.

j. Activity Names must have the most defining and detailed description within the first 30 characters.

-- End of Section --

SECTION 01 32 01.00 10 Page 17

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 23

HYDROGRAPHIC SURVEY

PART 1 GENERAL

1.1 INTRODUCTION

1.2 PAYMENT

1.3 REFERENCE STANDARDS

1.4 SUBMITTALS

1.5 EQUIPMENT DATA

1.6 SOFTWARE

1.7 SURVEY DOCUMENTATION SUBMITTAL

1.7.1 Depth Elevation Measurements

1.7.2 Electronic Copies of Surveys

1.7.3 Volume Computations

PART 2 PRODUCTS

PART 3 EXECUTION

3.1 SURVEYING PROCEDURES

3.1.1 Horizontal Positioning Procedures and Accuracies

3.1.2 Reference Horizontal Control Data

3.1.3 Depth Measurement Procedures and Calibratione

3.1.3.1 General

3.1.3.2 Technology

3.1.3.3 Depth measurement precision/accuracy

3.1.3.4 Manual Depth Measurements

3.1.3.5 Acoustic depth measurement

3.1.3.6 Acoustic calibration requirements

3.1.3.7 Onsite Vessel-to-Vessel Calibration

3.1.4 Tidal Monitoring

-- End of Section Table of Contents --

SECTION 01 32 23 Page 1

SECTION 01 32 23

HYDROGRAPHIC SURVEY

03/19

PART 1 GENERAL

1.1 INTRODUCTION

This section provides procedural, technical, and quality requirements for hydrographic surveying to be performed under this contract. Unless otherwise indicated in this contract, each required service shall include field-to-finish effort performed in accordance with the standards and specifications in EM 1110-2-1003.

1.2 PAYMENT

Work included in this section of the specifications for which no specific contract line item is included in the Pricing Schedule of the contract shall be considered an associated subsidiary obligation. No separate payment will be made for associated subsidiary obligations.

1.3 REFERENCE STANDARDS

The publications listed below form a part of this specification.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 1110-2-1003 (Nov 2013) Engineering and Design -- Hydrographic Surveying

EM 1110-1-2909 (2012) Engineering and Design -- Geospatial Data and Systems

ER 1110-2-8164 (2017) Policies, Guidance, and Requirements For Hydrographic Surveying and Mapping Digital Products

1.4 SUBMITTALS

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

Submittals not having a "G" designation are for information only. The following shall be submitted in accordance with the submittal requirements of these specifications.

SD-01 Preconstruction Submittals

Equipment Data; Equipment offset survey and maintenance log

Software

SD-06 Test Reports

Survey Documentation Submittal; G

SECTION 01 32 23 Page 2

1.5 EQUIPMENT DATA

Prior to the start of dredging operations, Contractor shall submit data on the surveying equipment.