A21 - RTASPECS3-W912PM22B0017-MOTSU-DRDGING.pdf

Solicitation No. W912PM22B0017 Contract No. W912PM22XXXXXX

Maintenance Dredging, Military Ocean Terminal (MOTSU), Sunny Point Brunswick County, North Carolina

This project was designed by the Wilmington District of the U.S. Army Corps of Engineers. The initials or signatures and registration designations of individuals appear on these project documents within the scope of their employment as required by ER 1110-1-8152.

RTA Specifications

MAY 2022

Maintenance Dredging MOTSU FY23 MOTSUDREDGING23

RTA

PROJECT TABLE OF CONTENTS

DI VI SI ON 00 - PROCUREMENT AND CONTRACTI NG REQUI REMENTS

00 01 15 02/11 LIST OF DRAWINGS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 10 00.10 38 1/17 SUPPLEMENTARY SPECIAL CONTRACT

REQUIREMENTS

01 32 01.00 10 02/15 PROJECT PROGRESS SCHEDULE

01 33 00 05/11 SUBMITTAL PROCEDURES

01 35 26 11/20, CHG 3: 02/22 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 11/14 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 01/16 QUALITY CONTROL

01 45 00.15 10 11/16 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE(RMS CM)

01 57 19 11/15, CHG 5: 08/21 TEMPORARY ENVIRONMENTAL CONTROLS

DI VI SI ON 35 - WATERWAY AND MARI NE CONSTRUCTI ON

35 20 23 04/06 DREDGING

35 20 23.13 02/22 NATIONAL DREDGING QUALITY MANAGEMENT

PROGRAM - SCOW MONITORING PROFILE

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/11

PART 1 GENERAL

1.1 SUMMARY

1.2 CONTRACT DRAWINGS

1.3 SUPPLEMENTARY DRAWINGS

1.3.1 Reference Drawings

ATTACHMENTS:

Attachment 1 - Index of Drawings

-- End of Section Table of Contents --

DOCUMENT 00 01 15 Page 1

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/11

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project pursuant to contract clause "DFARS 252.236-7001, Contract Drawings and Specifications."

1.2 CONTRACT DRAWINGS

Contract drawings are as indicated in Attachment 1 - Index of Drawings.

1.3 SUPPLEMENTARY DRAWINGS

These supplementary drawings may not be a part of the contract but are included with the drawings for information.

1.3.1 Reference Drawings

The Attached 1 list of reference drawings are intended only to show the original conditions. Drawings are the property of the Government and shall not be used for any purpose other than that intended by the contract.

-- End of Document --

DOCUMENT 00 01 15 Page 2

ATTACHMENT 1 – Index of Drawings

Sheet No. Description

G001 COVER SHEET

GI001 INDEX OF DRAWINGS, PROJECT LOCATION, OVERVIEW AND DISPOSAL AREA

CN100 MILITARY OCEAN TERMINAL AREAS TO BE DREDGED & SHEET LAYOUT

CN101 APPROACH CHANNEL SOUTH ENTRANCE

CN102

SOUTH WHARF TURNING BASIN AND APPROACH CHANNEL SOUTH TO CENTER

WHARF

CN103 CENTER WHARF TURNING BASIN

CN104 APPROACH CHANNEL MIDDLE ENTRANCE (OPTIONAL BID ITEM)

CN105 WILMINGTON OCEAN DREDGED MATERIAL DISPOSAL SITE PLACEMENT ZONE

CN106 MOTSU MAINTENANCE DREDGING PLACEMENT ZONE

Attachment 1

IWATCH Training and Active Shooter Training http://www.dtic.mil/whs/directives/corres/pub1.html http://armypubs.army.mil/

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT PROGRESS SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 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 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.1 Level of Detail Required

3.2.2 Activity Durations

3.2.3 Procurement Activities

3.2.4 Mandatory Tasks

3.2.5 Government Activities

3.2.6 Standard Activity Coding Dictionary

3.2.6.1 Workers Per Day (WRKP)

3.2.6.2 Area of Work Coding (AREA)

3.2.6.3 Modification Number (MODF)

3.2.6.4 Bid Item Coding (BIDI)

3.2.7 Contract Milestones and Constraints

3.2.7.1 Project Start Date Milestone and Constraint

3.2.7.2 End Project Finish Milestone and Constraint

3.2.7.3 Interim Completion Dates and Constraints

3.2.7.3.1 Start Phase

3.2.7.3.2 End Phase

3.2.8 Calendars

3.2.9 Open Ended Logic

3.2.10 Default Progress Data Disallowed

3.2.11 Out-of-Sequence Progress

3.2.12 Added and Deleted Activities

3.2.13 Original Durations

3.2.14 Leads, Lags, and Start to Finish Relationships

3.2.15 Retained Logic

3.2.16 Percent Complete

3.2.17 Remaining Duration

3.2.18 Early Completion Schedule and the Right to Finish Early

3.3 PROJECT SCHEDULE SUBMISSIONS

SECTION 01 32 01.00 10 Page 1

3.3.1 Initial Project Schedule Submission

3.3.2 Periodic Schedule Updates

3.4 SUBMISSION REQUIREMENTS

3.4.1 Data

3.4.2 Network Diagram

3.4.2.1 Continuous Flow

3.4.2.2 Project Milestone Dates

3.4.2.3 Critical Path

3.5 WEEKLY PROGRESS MEETINGS

3.6 REQUESTS FOR TIME EXTENSIONS

3.6.1 Justification of Delay

3.6.2 Time Impact Analysis (Prospective Analysis)

3.6.3 Fragmentary Network (Fragnet)

3.6.4 Time Extension

3.6.5 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

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT PROGRESS SCHEDULE

02/15

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 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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 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 and/or Microsoft Project Professional 2016.

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 or Microsoft Project Professional 2016, that is compliant with this specification, the contractor must request permission from the Government to use the software prior to submission of associated submittals.

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)

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

3.2 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.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 will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

- Dredging sequencing

SECTION 01 32 01.00 10 Page 4

- Dredging plant(s) type, size, and anticipated daily production rate(s)

- Environmental windows to include applicable mobilization and demobilization of equipment to include but not limited to pipeline

- Acceptance Sections (by Reach per contract drawings and/or contractor requested areas approved by the Government)

- Mobilization and demobilization durations

- Minimum of one activity per CLIN

- Disposal Area Work (if applicable)

- Submitted schedule timeline calendar days for each month matches the calendar days per month for the respective year

3.2.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.2.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.2.4 Mandatory Tasks

Include the following activities/tasks, if applicable, in the initial project schedule and all updates f or each r espect i ve dr edge ar ea or r each.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each to include but not limited to QCP, APP, and EPP).

b. Acceptance Sections (as approved by Govt)

c. Disposal Area Survey and Inspections - Pre-Dredge

d. Disposal Area Survey and Inspections - Post-Dredge

e. Mobilization

f. Demobilization

3.2.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, surveys (before dredge (B/D) and after dredge (A/D)) and Notice to Proceed (NTP) for phasing requirements.

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

SECTION 01 32 01.00 10 Page 5 site: http://rms.usace.army.mil .

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 AREA 4 Area of work (Government approved Acceptance Section)

3 MODF 6 Modification Number

4 BIDI 6 Bid Item (CLIN)

*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.2.6.1 Workers Per Day (WRKP)

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

Assign Work Area code to activities based upon the Govt approved Acceptance Section in which the activity occurs.

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

3.2.6.4 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs. An activity can have only one BIDI (CLIN) Code.

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

SECTION 01 32 01.00 10 Page 6

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

3.2.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.2.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.2.7.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates (to include applicable Environmental Windows) 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.2.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.2.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.

3.2.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, Environmental Windows, 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 .

SECTION 01 32 01.00 10 Page 7

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

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

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.2.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. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

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

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

SECTION 01 32 01.00 10 Page 8 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.2.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value or quantity of material dredged.

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.2.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.2.18 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 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.3 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.3.1 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 15 calendar days after the NTP is acknowledged. 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.3.2 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum, and with all requested payment applications per the following:

SECTION 01 32 01.00 10 Page 9

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

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

3.4.1 Data

Provide the current project schedule in the format of the scheduling software (e.g. .xer) and Adobe PDF (e.g. .pdf) via RMS, email, and/or CD/DVD as per arrangement with Project Engineer. Each schedule must have a unique file name and use project specific settings to include contract number and data date.

3.4.2 Network Diagram

The Network Diagram is required for the 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 will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.4.2.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.4.2.2 Project Milestone Dates

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

3.4.2.3 Critical Path

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

3.5 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government and use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.6 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer 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.

SECTION 01 32 01.00 10 Page 10

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.

3.6.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer 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 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, no other changes may be incorporated into the schedule being used to justify the time impact.

3.6.3 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 prior to incorporation into the project schedule.

3.6.4 Time Extension

The Contracting Officer 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.5 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.

SECTION 01 32 01.00 10 Page 11

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 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 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 may result in corrective action directed by the Contracting Officer 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 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 Quality Control System (QCS) and export the QCS data to the Government. This data is considered to be additional supporting data in a form and detail required by the Contracting Officer 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 QCS of the application for progress payment.

SECTION 01 32 01.00 10 Page 12

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

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

05/11

PART 1 GENERAL

1.1 SUMMARY

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

1.2.2 Approving Authority

1.2.3 Delegation of Authority

1.2.4 Work

1.3 SUBMITTALS

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved (G)

1.4.2 Information Only (FIO)

1.5 INFORMATION ONLY SUBMITTALS

1.6 VARIATIONS

1.6.1 Considering Variations

1.6.2 Proposing Variations

1.6.3 Warranting That Variations Are Compatible

1.6.4 Review Schedule Is Modified

1.7 SUBMITTAL REGISTER

1.7.1 Use of Submittal Register

1.7.2 Contractor Use of Submittal Register

1.7.3 Approving Authority Use of Submittal Register

1.7.4 Copies Delivered to the Government

1.8 SCHEDULING

1.9 PREPARATION

1.9.1 Transmittal Form

1.10 GOVERNMENT APPROVING AUTHORITY

1.11 DISAPPROVED SUBMITTALS

1.12 APPROVED SUBMITTALS

1.13 APPROVED SAMPLES

1.14 WITHHOLDING OF PAYMENT

PART 2 PRODUCTS

PART 3 EXECUTION

ATTACHMENTS:

Attachment 1 - Instructions for Contractors Completing ENG FORM 4288 & Project ENG FORM 4288

Attachment 2 - Instructions for Contractors Completing ENG FORM 4025-R & Blank ENG FORM 4025-R

SECTION 01 33 00 Page 1

SECTION 01 33 00 Page 2

SECTION 01 33 00

SUBMITTAL PROCEDURES

05/11

PART 1 GENERAL

1.1 SUMMARY

The Contracting Officer or his/her designated representative may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections.

Units of weights and measures used on all submittals shall be the same as those used in the contract drawings.

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor shall check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as: Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders;

samples; O&M manuals (including parts list); certifications; warranties;

and other such required submittals.

Submittals requiring Government approval are to be scheduled and made prior to the acquisition of the material or equipment covered thereby.

Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's material Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by Submittal Description (SD) numbers and titles as follows:

SD-01 Preconstruction Submittals

Submittals which are required prior to start of construction/dredging (work) or the start of the next major phase of the construction/dredging on a multi-phase contract, includes schedules, tabular list of data, or tabular list including location, features, or other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates of insurance

Surety bonds

List of proposed Subcontractors

SECTION 01 33 00 Page 3

List of proposed products construction/dredging Progress Schedule

Network Analysis Schedule (NAS)

Submittal register

Schedule of prices

Health and safety plan

Work plan

Quality Control(QC) plan

Environmental protection plan

Delegation of Authority

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. Testing must have been within three years of date of contract award for the project.

Report which includes findings of a test required to be performed by the Contractor on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily logs and checklists.

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that product, system or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or Subcontractor through Contractor, the purpose of which is to further quality of orderly progression of a portion of the work by documenting procedures, acceptability of methods or personnel qualifications.

Confined space entry permits.

Text of posted operating instructions.

SECTION 01 33 00 Page 4

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Special requirements necessary to properly close out a construction/dredging contract. For example, Record Drawings and as-built drawings. Also, submittal requirements necessary to properly close out a major phase of construction/dredging on a multi-phase contract.

Interim "DD Form 1354" with cost breakout for all assets 30 days prior to facility turnover.

1.2.2 Approving Authority

Office or designated person authorized to approve submittal.

1.2.3 Delegation of Authority

Provide a signed letter from the contractor's President or equivalent detailing who in the company has the authority to sign contract modifications, pay estimates, and serial letters on behalf of the company.

1.2.4 Work

As used in this section, on- and off-site construction/dredging required by contract documents, including labor necessary to produce submittals , except those SD-01 Pre-Construction Submittals noted above , construction/dredging, materials, products, equipment, and systems incorporated or to be incorporated in such construction/dredging.

1.3 SUBMITTALS

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

submittals not having a "G, A" designation are for for information only.

When used, a designation following the "G, A" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with this section.

SD-01 Preconstruction Submittals

Submittal Register; GA

Delegation of Authority

1.4 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.4.1 Government Approved (G)

Government approval is required for extensions of design, critical materials, deviations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer or his/her designated representative. Within the terms of the Contract Clause entitled, "SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION," they are considered to be "shop drawings."

SECTION 01 33 00 Page 5

1.4.2 Information Only (FIO)

Submittals not requiring Government approval will be for information only.

They are not considered to be "shop drawings" within the terms of the Contract Clause referred to in subparagraph Government Approved (G).

1.5 INFORMATION ONLY SUBMITTALS

Normally submittals for information only will not be returned. Approval of the Contracting Officer or his/her designated representative is not required on information only submittals. The Government reserves the right to require the Contractor to resubmit any item found not to comply with the contract. This does not relieve the Contractor from the obligation to furnish material conforming to the plans and specifications;

will not prevent the Contracting Officer or his/her designated representative from requiring removal and replacement of nonconforming material incorporated in the work; and does not relieve the Contractor of the requirement to furnish samples for testing by the Government laboratory or for check testing by the Government in those instances where the technical specifications so prescribe.

1.6 VARIATIONS

Variations from contract requirements require both Designer of Record (DOR) and Government approval pursuant to contract Clause FAR 52.236-21 and will be considered where advantageous to Government.

1.6.1 Considering Variations

Discussion with Contracting Officer or his/her designated representative prior to submission, after consulting with the DOR, will help ensure functional and quality requirements are met and minimize rejections and re-submittals. When contemplating a variation which results in lower cost, consider submission of the variation as a Value Engineering Change Proposal (VECP).

Specifically point out variations from contract requirements in transmittal letters. Failure to point out deviations may result in the Government requiring rejection and removal of such work at no additional cost to the Government.

1.6.2 Proposing Variations

When proposing variation, deliver written request to the Contracting Officer or his/her designated representative, with documentation of the nature and features of the variation and why the variation is desirable and beneficial to Government, including the DOR's written analysis and approval. If lower cost is a benefit, also include an estimate of the cost savings. In addition to documentation required for variation, include the submittals required for the item. Clearly mark the proposed variation in all documentation.

Check the column "variation" of ENG Form 4025-R for submittals which include proposed deviations requested by the Contractor. Set forth in writing the reason for any deviations and annotate such deviations on the submittal. The Government reserves the right to rescind inadvertent approval of submittals containing unnoted deviations.

SECTION 01 33 00 Page 6

1.6.3 Warranting That Variations Are Compatible

When delivering a variation for approval, Contractor, including its Designer(s) of Record, warrants that this contract has been reviewed to establish that the variation, if incorporated, will be compatible with other elements of work.

1.6.4 Review Schedule Is Modified

In addition to normal submittal review period, a period of 10 working days will be allowed for consideration by the Government of submittals with variations.

1.7 SUBMITTAL REGISTER

Prepare and maintain submittal register, as the work progresses. See Attachment 1 - Instructions for Contractors Completing ENG FORM 4288 & Project ENG FORM 4288. Do not change data which is output in columns entitled "ITEM NO.", "SPEC PARAGRAPH NO.", "DESCRIPTION OF SUBMITTAL", and "TYPE OF SUBMITTAL" as delivered by Government; retain data which is output in columns (Activity No.), (Classification), (Reviewer), and (Contractor Schedule Dates) as approved. A submittal register showing items of equipment and materials for which submittals are required by the specifications is provided as an attachment. This list may not be all inclusive and additional submittals may be required. Maintain a submittal register for the project in accordance with Section 01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE(RMS CM). The Government will provide the initial submittal register in electronic format.

Column "SPEC PARAGRAPH NO.": Lists specification section and paragraph in which submittal is required.

Column "DESCRIPTION OF SUBMITTAL": Lists one principal paragraph in specification section where a material or product is specified. This listing is only to facilitate locating submitted requirements. Do not consider entries in column (Description of Submittal) as limiting project requirements.

Column "TYPE OF SUBMITTAL": Lists each type of submittal, (e.g. Shop Drawings) required in each specification section.

Thereafter, the Contractor is to track all submittals by maintaining a complete list, including completion of all data columns, including dates on which submittals are received and returned by the Government.

1.7.1 Use of Submittal Register

Submit submittal register. Submit with QC plan and project schedule.

Verify that all submittals required for project are listed and add missing submittals. Coordinate and complete the following fields on the register submitted with the QC plan and the project schedule:

Column Activity Number: Activity number from the project schedule.

Column Contractor Submit Date: Scheduled date for approving authority to receive submittals.

Column Contractor Approval Date: Date Contractor needs

SECTION 01 33 00 Page 7 approval of submittal.

Column Contractor Material: Date that Contractor needs material delivered to Contractor control.

1.7.2 Contractor Use of Submittal Register

Update the following fields in the Government-furnished submittal register program or equivalent fields in program utilized by Contractor with each submittal throughout contract.

Column Transmittal Number: Contractor assigned list of consecutive numbers.

Column List date of submittal transmission.

Column List date approval received.

1.7.3 Approving Authority Use of Submittal Register

Update the following fields in the Government-furnished submittal register program or equivalent fields in program utilized by Contractor.

Column Transmittal Number: Contractor assigned list of consecutive numbers.

Column (m) through (p) List Date related to review actions.

1.7.4 Copies Delivered to the Government

Deliver one copy of submittal register updated by Contractor to Government with each payment request.

1.8 SCHEDULING

Schedule and submit concurrently submittals covering component items forming a system or items that are interrelated. Include certifications to be submitted with the pertinent drawings at the same time. Thirty (30) calendar days exclusive of mailing time shall be allowed and shown on the register for review and approval. No delay damages or time extensions will be allowed for time lost in late submittals.

a. Coordinate scheduling, sequencing, preparing and processing of submittals with performance of work so that work will not be delayed by submittal processing. Allow for potential resubmittal of requirements.

b. Submittals called for by the contract documents will be listed on the register. If a submittal is called for but does not pertain to the contract work, the Contractor is to include the submittal in the register and annotate it "N/A" with a brief explanation. Approval by the Contracting Officer or his/her designated representative does not relieve the Contractor of supplying submittals required by the contract documents but which have been omitted from the register or marked "N/A."

c. Re-submit register and annotate monthly with each payment request in subparagraph Copies Delivered to the Government by the Contractor with actual submission and approval dates. When all items on the register

SECTION 01 33 00 Page 8 have been fully approved, no further re-submittal is required.

d. Carefully control procurement operations to ensure that each individual submittal is made on or before the Contractor scheduled submittal date shown on the approved "Submittal Register."

1.9 PREPARATION

1.9.1 Transmittal Form

Use the attached transmittal form (ENG Form 4025-R) for submitting both Government approved and information only submittals in accordance with the instructions on the reverse side of the form (Attachment 2 - Instructions for Contractors Completing ENG FORM 4025-R & Blank ENG FORM 4025-R). These forms will be furnished to the Contractor. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted. Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

1.10 GOVERNMENT APPROVING AUTHORITY

When approving authority is Contracting Officer or his/her designated representative, the Government will:

a. Note date on which submittal was received.

b. Review submittals for approval within scheduling period specified and only for conformance with project design concepts and compliance with contract documents.

c. Identify returned submittals with one of the actions defined in subparagraph entitled, "Contractor Action Codes," of this section and with markings appropriate for action indicated.

Upon completion of review of submittals requiring Government approval, stamp and date approved submittals. Four (4) copies of the approved submittal will be retained by the Contracting Officer or his/her designated representative and one (1) copy of the submittal will be returned to the Contractor.

1.11 DISAPPROVED SUBMITTALS

Contractor shall make corrections required by the Contracting Officer or his/her designated representative. If the Contractor considers any correction or notation on the returned submittals to constitute a change to the contract drawings or specifications; notice as required under the clause entitled, "Changes," is to be given to the Contracting Officer or his/her designated representative. Contractor is responsible for the dimensions and design of connection details and construction/dredging of work. Failure to point out deviations may result in the Government requiring rejection and removal of such work at the Contractor's expense.

If changes are necessary to submittals, the Contractor shall make such revisions and submission of the submittals in accordance with the procedures above. No item of work requiring a submittal change is to be accomplished until the changed submittals are approved.

SECTION 01 33 00 Page 9

1.12 APPROVED SUBMITTALS

The Contracting Officer or his/her designated representative's approval or acceptance of submittals is not to be construed as a complete check, and indicates only that the general method of construction/dredging, materials, detailing and other information are satisfactory.

Approval or acceptance will not relieve the Contractor of the responsibility for any error which may exist, as the Contractor under the Contractor Quality Control (CQC) requirements of this contract is responsible for dimensions, the design of adequate connections and details, and the satisfactory construction/dredging of all work .

After submittals have been approved or accepted by the Contracting Officer or his/her designated representative, no resubmittal for the purpose of substituting materials or equipment will be considered unless accompanied by an explanation of why a substitution is necessary.

1.13 APPROVED SAMPLES

Approval of a sample is only for the characteristics or use named in such approval and is not be construed to change or modify any contract requirements. Before submitting samples, the Contractor to assure that the materials or equipment will be available in quantities required in the project. No change or substitution will be permitted after a sample has been approved.

Match the approved samples for materials and equipment incorporated in the work. If requested, approved samples, including those which may be damaged in testing, will be returned to the Contractor, at his expense, upon completion of the contract. Samples not approved will also be returned to the Contractor at its expense, if so requested.

Failure of any materials to pass the specified tests will be sufficient cause for refusal to consider, under this contract, any further samples of the same brand or make of that material. Government reserves the right to disapprove any material or equipment which previously has proved unsatisfactory in service.

Samples of various materials or equipment delivered on the site or in place may be taken by the Contracting Officer or his/her designated representative for…