A21 - RTA-SPECS-W912PM23B0016-AIWW-Combined.pdf

FY24 AIWW MAINTENANCE

DREDGING

RTA SPECIFICATIONS

01-JUNE-2023

Solicitation No. W912PM23B0016 Contract No. W912PM23XXXXX

Atlantic Intracoastal Waterway Dredging Contract FY24 - North AIWWFY24NORTH

RTA W912PM23B0016

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 32 01.00 10 02/15 PROJECT PROGRESS SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

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

REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 11/16, CHG 2: 11/21 QUALITY CONTROL

01 45 00.15 10 11/16, CHG 2: 08/19 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 50 00 11/20, CHG 2: 08/22 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 21 00 09/22 CONSTRUCTION SURVEYS

02 41 00 03/19 DEMOLITION

DI VI SI ON 03 - CONCRETE

03 31 29 02/19 MARINE CONCRETE

DI VI SI ON 05 - METALS

05 05 23.16 08/18 STRUCTURAL WELDING

05 12 00 08/18, CHG 2: 05/21 STRUCTURAL STEEL

05 50 13 05/17, CHG 1: 08/18 MISCELLANEOUS METAL FABRICATIONS

DI VI SI ON 06 - WOOD, PLASTI CS, AND COMPOSI TES

06 10 00 08/16 ROUGH CARPENTRY

DI VI SI ON 31 - EARTHWORK

31 01 00 034/19 DIKE EMBANKMENT

31 11 00.10 03/19 CLEARING

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 92 19 10/06 SEEDING

DI VI SI ON 33 - UTI LI TI ES

33 40 02 03/19 SPILLWAY SYSTEM

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

35 20 23 08/20 DREDGING

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

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 Extensions for Unusually Severe Weather

3.6.3 Time Impact Analysis (Prospective Analysis)

3.6.4 Fragmentary Network (Fragment)

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

The Contractor shall 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 (or later).

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

Pursuant to the Contract Clause FAR 52.236-15, SCHEDULES FOR CONSTRUCTION CONTRACTS, a project schedule as described in this paragraph PROGRESS SCHEDULE shall be prepared and submitted. The Contractor shall provide the project schedule in the Precedence Diagram Method (PDM) using the Standard Data Exchange Format (SDEF). The project schedule shall be used to measure progress of the work, to evaluate potential time extensions and to provide a basis for all progress payments. It shall be in sufficient detail to properly monitor and manage the work and as a minimum shall include the following:

a. the work shall be divided into activities by acceptance section and phase of work (e.g. preconstruction structure and property condition surveys, blasting, dredging)

b. separate activities shall reflect each mobilization and demobilization of each major plant

c. activities shall be identified by associated bid item

d. all required and proposed submissions shall be included in the progress schedule

e. Government and other agency activities that could impact progress shall be shown (e.g. Government surveys, navigation aid relocations, etc.)

The schedule shall extend from NTP to the established contract completion date.

The initial progress schedule shall be included with the solicitation proposal and demonstrate that the proposed plant and resources are capable

SECTION 01 32 01.00 10 Page 4 of performing the work as scheduled. 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. Periodic schedule updates shall be provided monthly with each payment request, and whenever there is a change in logic or time extension. Each submission shall include the data disks containing the project schedule adhering to the SDEF format specified in ER 1-1-11, Appendix A; the earnings report indicating monthly and cumulative earnings; a narrative report with a description of the activities identifying the critical path(s), current or anticipated problems of delays and their impact, and proposed corrective actions; and the schedule reports containing activity number, activity description, original duration, remaining duration, early start date, early finish date, late start date, late finish date and total float. The schedule reports shall be sorted as activity report, logic report listing preceding and succeeding activities for each activity, total float report listed in ascending order by early state date, early state sort and earning report.

A network diagram shall be submitted with the initial submission and each update. The network diagram shall depict the order, sequence and interdependence of activities, shall clearly indicate milestone dates and projected early and late earnings.

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

- 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

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

SECTION 01 32 01.00 10 Page 5

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. Environmental Windows (start to finish)

c. Acceptance Sections (as approved by Govt)

d. Placement Area & Spillway Survey and Inspections - Pre-Dredge

e. Placement Area & Spillway Survey and Inspections - Post-Dredge

f. Beach Placement Inspection w/ Agencies - Pre-Dredge

g. Beach Placement Inspection w/ Agencies - Post-Dredge

h. Mobilization

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

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

SECTION 01 32 01.00 10 Page 6

Field Activity Code Length Description

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.

SECTION 01 32 01.00 10 Page 7

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.

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.

SECTION 01 32 01.00 10 Page 8

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 Supplementary Special Contract Requirements. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

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

SECTION 01 32 01.00 10 Page 9

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

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

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

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

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 concurrences of delay. A time extension and the schedule fragment becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.6.2 Time Extensions for Unusually Severe Weather

(a) This provision specifies the procedure for determination of time extensions for unusually severe weather in accordance with the contract clause entitled "DEFAULT (FIXED-PRICE CONSTRUCTION)." In order for the Contracting Officer to award a time extension under this clause, the following conditions must be found to be satisfied in the sole discretion of the Contracting Officer:

(1) The weather experienced at the project site during the contract period must be found to be unusually severe, that is, more severe than the adverse weather anticipated for the project location during any given month.

(2) The unusually severe weather must actually cause a delay to the completion of the project. The delay must be beyond the control and without the fault or negligence of the Contractor.

(b) Upon acknowledgment of the Notice to Proceed (NTP) and continuing throughout the contract, the Contractor shall record on the daily CQC report, the occurrence of adverse weather and resultant impact to normally scheduled work. Actual adverse weather delay days must prevent work on critical activities for 50 percent or more of the Contractor's scheduled work day.

(c) The number of actual adverse weather delay days shall include days impacted by actual adverse weather (even if adverse weather occurred in previous month), be calculated chronologically from the first to the last day of each month, and be recorded as full days. The Contracting Officer will convert any qualifying delays to calendar days, giving full consideration for equivalent fair weather work days, and issue a modification in accordance with the contract clause entitled "DEFAULT

(FIXED-PRICE CONSTRUCTION)."

3.6.3 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer

SECTION 01 32 01.00 10 Page 12 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.4 Fragmentary Network (Fragment)

Prepare a proposed fragment 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 fragment is to be tied into the project schedule including all predecessors and successors to the fragment activities. The proposed fragment must be approved by the Contracting Officer prior to incorporation into the project schedule.

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

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

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.

SECTION 01 32 01.00 10 Page 14

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 15

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/ 18, CHG 4: 02/ 21

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

1.1.2 Project Type

1.1.3 Submission of Submittals

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 For Information Only

1.5 PREPARATION

1.5.1 Transmittal Form

1.5.2 Submittal Format

1.5.2.1 Format of SD-01 Preconstruction Submittals

1.5.2.2 Format for SD-02 Shop Drawings

1.5.2.2.1 Drawing Identification

1.5.2.3 Format of SD-03 Product Data

1.5.2.3.1 Product Information

1.5.2.3.2 Standards

1.5.2.3.3 Data Submission

1.5.2.4 Format of SD-04 Samples

1.5.2.4.1 Sample Characteristics

1.5.2.4.2 Sample Incorporation

1.5.2.4.3 Comparison Sample

1.5.2.5 Format of SD-05 Design Data

1.5.2.6 Format of SD-06 Test Reports

1.5.2.7 Format of SD-07 Certificates

1.5.2.8 Format of SD-08 Manufacturer's Instructions

1.5.2.8.1 Standards

1.5.2.9 Format of SD-09 Manufacturer's Field Reports

1.5.2.10 Format of SD-11 Closeout Submittals

1.5.3 Source Drawings for Shop Drawings

1.5.3.1 Source Drawings

1.5.3.2 Terms and Conditions

1.6 QUANTITY OF SUBMITTALS

1.6.1 Number of SD-01 Preconstruction Submittal Copies

1.6.2 Number of SD-04 Samples

1.7 INFORMATION ONLY SUBMITTALS

1.8 PROJECT SUBMITTAL REGISTER

1.8.1 Submittal Management

1.8.2 Preconstruction Use of Submittal Register

SECTION 01 33 00 Page 1

1.8.3 Contractor Use of Submittal Register

1.8.4 Approving Authority Use of Submittal Register

1.8.5 Action Codes

1.8.5.1 Contractor Action Codes

1.8.6 Delivery of Copies

1.9 VARIATIONS

1.9.1 Considering Variations

1.9.2 Proposing Variations

1.9.3 Warranting that Variations are Compatible

1.9.4 Review Schedule Extension

1.10 SCHEDULING

1.11 GOVERNMENT APPROVING AUTHORITY

1.11.1 Review Notations

1.12 DISAPPROVED SUBMITTALS

1.13 APPROVED SUBMITTALS

1.14 APPROVED SAMPLES

1.15 WITHHOLDING OF PAYMENT

1.16 CERTIFICATION OF SUBMITTAL DATA

PART 2 PRODUCTS

PART 3 EXECUTION

ATTACHMENTS:

ENG Form 4025-R

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

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

-- End of Section Table of Contents --

SECTION 01 33 00 Page 2

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/ 18, CHG 4: 02/ 21

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

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

1.1.2 Project Type

The Contractor's Quality Control (CQC) System Manager are to check and approve all items before 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.

1.1.3 Submission of Submittals

Schedule and provide submittals requiring Government approval before acquiring the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

SD-01 Preconstruction Submittals

Submittals that are required prior to or at the start of construction (work) or the next major phase of the construction on a multiphase contract.

Preconstruction Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials, equipment, or components to be used in the work.

SECTION 01 33 00 Page 3

Certificates Of Insurance

Surety Bonds

List Of Proposed Subcontractors

List Of Proposed Products

Construction/Dredging Progress Schedule

Baseline Network Analysis Schedule (NAS)

Submittal Register

Schedule Of Prices Or Earned Value Report

Accident Prevention Plan

Work Plan

Quality Control (QC) plan

Environmental Protection Plan

Delegation of Authority

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-05 Design Data

Design calculations, mix designs, analyses or other data pertaining to a part of work.

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

SECTION 01 33 00 Page 4 requirements. Unless specified in another section, testing must have been within three years of date of contract award for the project.

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

Report that 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 the 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 document purpose is to further promote the 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

SD-11 Closeout Submittals

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

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

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

1.2.2 Approving Authority

Office or designated person authorized to approve the 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 of behalf of the company.

SECTION 01 33 00 Page 5

1.2.4 Work

As used in this section, on-site and off-site construction required by contract documents, including labor necessary to produce submittals, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction. In exception, excludes work to produce SD-01 submittals.

1.3 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or “S” classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Submittal Register; G

Delegation of Authority

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved (G)

Government approval is required for extensions of design, critical materials, variations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Government.

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, submittals are considered to be "shop drawings."

1.4.2 For Information Only

Submittals not requiring Government approval will be for information only. Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are not considered to be "shop drawings."

1.5 PREPARATION

1.5.1 Transmittal Form

Use the ENG Form 4025-R transmittal form for submitting both Government-approved and information-only submittals. Submit in accordance with the instructions on the reverse side of the form. These forms or similar forms will be furnished to the Contractor and are included in Attachment 2 - Instructions for Contractors Completing ENG Form 4025-R & Blank ENG Form 4025-R. 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.

SECTION 01 33 00 Page 6

1.5.2 Submittal Format

1.5.2.1 Format of SD-01 Preconstruction Submittals

When the submittal includes a document that is to be used in the project, or is to become part of the project record, other than as a submittal, do not apply the Contractor's approval stamp to the document itself, but to a separate sheet accompanying the document.

Provide data in the unit of measure used in the contract documents.

1.5.2.2 Format for SD-02 Shop Drawings

Provide shop drawings not less than 8 1/2 by 11 inches nor more than 30 by 42 inches, except for full-size patterns or templates. Prepare drawings to accurate size, with scale indicated, unless another form is required.

Ensure drawings are suitable for reproduction and of a quality to produce clear, distinct lines and letters, with dark lines on a white background.

a. Include the nameplate data, size, and capacity on drawings. Also include applicable federal, military, industry, and technical society publication references.

b. Dimension drawings, except diagrams and schematic drawings. Prepare drawings demonstrating interface with other trades to scale. Use the same unit of measure for shop drawings as indicated on the contract drawings. Identify materials and products for work shown.

1.5.2.2.1 Drawing Identification

Include on each drawing the drawing title, number, date, and revision numbers and dates, in addition to information required in paragraph

IDENTIFYING SUBMITTALS.

Number drawings in a logical sequence. Each drawing is to bear the number of the submittal in a uniform location next to the title block. Place the Government contract number in the margin, immediately below the title block, for each drawing.

Reserve a blank space, no smaller than 1 inches on the right-hand side of each sheet for the Government disposition stamp.

1.5.2.3 Format of SD-03 Product Data

Present product data submittals for each section. Include a table of contents, listing the page and catalog item numbers for product data.

Indicate, by prominent notation, each product that is being submitted;

indicate the specification section number and paragraph number to which it pertains.

1.5.2.3.1 Product Information

Supplement product data with material prepared for the project to satisfy the submittal requirements where product data does not exist. Identify this material as developed specifically for the project, with information and format as required for submission of SD-07 Certificates.

Provide product data in units used in the Contract documents. Where

SECTION 01 33 00 Page 7 product data are included in preprinted catalogs with another unit, submit the dimensions in contract document units, on a separate sheet.

1.5.2.3.2 Standards

Where equipment or materials are specified to conform to industry or technical-society reference standards of such organizations as the American National Standards Institute (ANSI), ASTM International (ASTM), National Electrical Manufacturer's Association (NEMA), Underwriters Laboratories (UL), or Association of Edison Illuminating Companies (AEIC), submit proof of such compliance. The label or listing by the specified organization will be acceptable evidence of compliance. In lieu of the label or listing, submit a certificate from an independent testing organization, competent to perform testing, and approved by the Contracting Officer. State on the certificate that the item has been tested in accordance with the specified organization's test methods and that the item complies with the specified organization's reference standard.

1.5.2.3.3 Data Submission

Collect required data submittals for each specific material, product, unit of work, or system into a single submittal that is marked for choices, options, and portions applicable to the submittal. Mark each copy of the product data identically. Partial submittals will not be accepted for expedition of the construction effort.

Submit the manufacturer's instructions before installation.

1.5.2.4 Format of SD-04 Samples

1.5.2.4.1 Sample Characteristics

Furnish samples in the following sizes, unless otherwise specified or unless the manufacturer has prepackaged samples of approximately the same size as specified:

a. Sample of Equipment or Device: Full size.

b. Sample of Materials Less Than 2 by 3 inches: Built up to 8 1/2 by 11 inches.

c. Sample of Materials Exceeding 8 1/2 by 11 inches: Cut down to 8 1/2 by 11 inches and adequate to indicate color, texture, and material variations.

d. Sample of Linear Devices or Materials: 10 inch length or length to be supplied, if less than 10 inches. Examples of linear devices or materials are conduit and handrails.

e. Sample Volume of Nonsolid Materials: Pint. Examples of nonsolid materials are sand and paint.

f. Color Selection Samples: 2 by 4 inches. Where samples are specified for selection of color, finish, pattern, or texture, submit the full set of available choices for the material or product specified. Sizes and quantities of samples are to represent their respective standard unit.

SECTION 01 33 00 Page 8

g. Sample Panel: 4 by 4 feet.

h. Sample Installation: 100 square feet.

1.5.2.4.2 Sample Incorporation

Reusable Samples: Incorporate returned samples into work only if so specified or indicated. Incorporated samples are to be in undamaged condition at the time of use.

Recording of Sample Installation: Note and preserve the notation of any area constituting a sample installation, but remove the notation at the final clean-up of the project.

1.5.2.4.3 Comparison Sample

Samples Showing Range of Variation: Where variations in color, finish, pattern, or texture are unavoidable due to nature of the materials, submit sets of samples of not less than three units showing extremes and middle of range. Mark each unit to describe its relation to the range of the variation.

When color, texture, or pattern is specified by naming a particular manufacturer and style, include one sample of that manufacturer and style, for comparison.

1.5.2.5 Format of SD-05 Design Data

Provide design data and certificates on 8 1/2 by 11 inch paper.

1.5.2.6 Format of SD-06 Test Reports

By prominent notation, indicate each report in the submittal. Indicate the specification number and paragraph number to which each report pertains.

1.5.2.7 Format of SD-07 Certificates

Provide design data and certificates on 8 1/2 by 11 inch paper.

1.5.2.8 Format of SD-08 Manufacturer's Instructions

Present manufacturer's instructions submittals for each section. Include the manufacturer's name, trade name, place of manufacture, and catalog model or number on product data. Also include applicable federal, military, industry, and technical-society publication references. If supplemental information is needed to clarify the manufacturer's data, submit it as specified for SD-07 Certificates.

Submit the manufacturer's instructions before installation.

1.5.2.8.1 Standards

Where equipment or materials are specified to conform to industry or technical-society reference standards of such organizations as the American National…