A21 - 2.0 RTA-SPECS-GROUP1-24-R-W001-FY27AIWW-MD-08.07.26.pdf

NOT ICE: REQUIRES COMPLICANCE WITH THE 15 MARCH 2024 EDITION OF

EM 385-1-1: SAFETY and OCCUPATIONAL HEALTH REQUIREMENTS

AUGUST-2026

Solicitation No. GROUP1-24-R-W001 Contract No. W912PM26XXXXX

FY27 - MAINTENANCE DREDGING,

ATLANTIC INTRACOASTAL

WATERWAY (AIWW),

ONSLOW TO BRUNSWICK COUNTIES,

NORTH CAROLINA.

READY TO ADVERTISE SPECIFICATIONS

FY27 AIWW MAINTENANCE DREDGING AIWWFY27

READY TO ADVERTISE GROUP1-24-R-W001

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 14 00 11/22, CHG 5: 05/25 WORK RESTRICTIONS

01 32 01.00 10 08/23, CHG 1: 08/24 PROJECT SCHEDULE

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

01 35 26 05/24 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS

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

01 45 00.15 10 11/23 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 50 00 11/20, CHG 3: 08/24 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22, CHG 2: 08/25 TEMPORARY ENVIRONMENTAL CONTROLS

DIVISION 02 - EXISTING CONDITIONS

02 21 00 09/22 CONSTRUCTION SURVEYS

DIVISION 31 - EARTHWORK

31 11 00.10 03/19 CLEARING

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 20 23.10 38 08/20 DREDGING

35 20 23.33 38 14 January 2026 NATIONAL DREDGING QUALITY MANAGEMENT

PIPELINE HYDRAULIC DREDGE

-- End of Project Table of Contents --

DOCUMENT PROJECT Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 14 00

WORK RESTRICTIONS

11/22, CHG 5: 05/25

PART 1 GENERAL

1.1 SUBMITTALS

1.2 SPECIAL SCHEDULING REQUIREMENTS

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

1.3.1.1 Subcontractors and Personnel Contacts

1.3.1.2 Installation Access

1.3.1.2.1 Registration for DBIDS

1.3.1.2.2 DBIDS Eligibility Requirements

1.3.1.2.3 DBIDS Notification Requirements

1.3.1.2.4 One-Day Passes

1.3.1.3 No Smoking Policy

1.4 SECURITY REQUIREMENTS

1.5 EMERGENCY UNEXPLODED ORDNANCE (UXO) RESPONSE

1.5.1 3Rs Explosive Safety Education Training Certificate

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 14 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

11/22, CHG 5: 05/25

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. 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

List of Contact Personnel

1.2 SPECIAL SCHEDULING REQUIREMENTS

a. The Contractor shall comply with all special scheduling requirements as described in the attached project description.

b. Permission to interrrupt any Station roads, railroads, and/or utility service shall be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, including delivery vehicles, are clearly identified with their company name.

1.3.1.1 Subcontractors and Personnel Contacts

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

1.3.1.2 Installation Access

Obtain access to Navy installations through participation in the Defense Biometrics Identification System (DBIDS). Requirements for Contractor employee registration, and transition for employees currently under Navy Commercial Access Control System (NCACS), are available at https://www.cnic.navy.mil/Operations-and-Management/Base-Support/DBIDS/ .

SECTION 01 14 00 Page 2

No fees are associated with obtaining a DBIDS credential.

Participation in the DBIDS is not mandatory, and Contractor personnel may apply for One-Day Passes at the Base Visitor Control Office to access an installation.

The following are specific details regarding contractor personnel requirements. For the most up-to-date information regarding Base Access please visit https://www.lejeune.marines.mil/Base-Access/.

1.3.1.2.1 Registration for DBIDS

Registration for DBIDS is available at https://www.cnic.navy.mil/Operations-and-Management/Base-Support/DBIDS/ .

Procedure includes:

a. Present a letter or official award document (i.e. DD Form 1155 or SF 1442) from the Contracting Officer, that provides the purpose for access, to the base Visitor Control Center representative.

b. Present valid identification, such as a passport or Real ID Act-compliant state driver's license.

c. Provide completed SECNAV FORM 5512/1 to the base Visitor Control Center representative to obtain a background check. This form is available for download at https://www.cnic.navy.mil/Operations-and-Management/Base-Support/DBIDS/ .

d. Upon successful completion of the background check, the Government will complete the DBIDS enrollment process, which includes Contractor employee photo, fingerprints, base restriction and several other assessments.

e. Upon successful completion of the enrollment process, the Contractor employee will be issued a DBIDS credential, and will be allowed to proceed to worksite.

1.3.1.2.2 DBIDS Eligibility Requirements

Throughout the length of the contract, the Contractor employee must continue to meet background screen standards. Periodic background screenings are conducted to verify continued DBIDS participation and installation access privileges. DBIDS access privileges will be immediately suspended or revoked if at any time a Contractor employee becomes ineligible.

An adjudication process may be initiated when a background screen failure results in disqualification from participation in the DBIDS, and Contractor employee does not agree with the reason for disqualification.

The Government is the final authority.

1.3.1.2.3 DBIDS Notification Requirements

a. Immediately report instances of lost or stolen badges to the Contracting Officer.

b. Immediately collect DBIDS credentials and notify the Contracting Officer in writing under the following circumstances:

SECTION 01 14 00 Page 3

(1) An employee has departed the company without having properly returned or surrendered their DBIDS credentials.

(2) There is a reasonable basis to conclude that an employee, or former employee, might pose a risk, compromise, or threat to the safety or security of the Installation or anyone therein.

1.3.1.2.4 One-Day Passes

Personnel applying for One-Day passes at the Base Visitor Control Office are subject to daily mandatory vehicle inspection, and will have limited access to the installation. The Government is not responsible for any cost or lost time associated with obtaining daily passes or added vehicle inspections incurred by non-participants in the DBIDS.

1.3.1.3 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.4 SECURITY REQUIREMENTS

Contract Clause "FAR 52.204-2, Security Requirements and Alternate II," "FAC 5252.236-9301, Special Working Conditions and Entry to Work Area," apply.

1.5 EMERGENCY UNEXPLODED ORDNANCE (UXO) RESPONSE

In the event that UXO, as defined in 40 CFR 260 is encountered during the construction activities that are deemed to be a threat to human health or the environment, Camp Lejeune Military Police and EOD professionals shall be immediately contacted to conduct an emergency response. Additionally, immediately contact the Contracting Officer if UXO is encountered. An evaluation of this scenario and procedures, with contract numbers, shall be included in the Health and Safety Plan (HASP) for the fieldwork.

1.5.1 3Rs Explosive Safety Education Training Certificate

All Contractor personnel performing ground disturbing activities must complete contractor awareness training related to recognizing UXO. 3Rs Explosives Safety Education Program training is available at the following website: https://www.denix.osd.mil/uxo/3rs-training/ .

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 14 00 Page 4

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/23, CHG 1: 08/24

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.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

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 Activities

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

3.2.9 Calendars

3.2.10 Open Ended Logic

3.2.11 Default Progress Data Disallowed

3.2.12 Out-of-Sequence Progress

3.2.13 Added and Deleted Activities

3.2.14 Original Durations

3.2.15 Leads, Lags, and Start to Finish Relationships

3.2.16 Retained Logic

3.2.17 Percent Complete

3.2.18 Remaining Duration

SECTION 01 32 01.00 10 Page 1

3.2.19 Early Completion Schedule and the Right to Finish Early

3.3 PROJECT SCHEDULE SUBMISSIONS

3.3.1 Initial Project Schedule Submission

3.3.2 Periodic Schedule Updates

3.4 SUBMISSION REQUIREMENTS

3.4.1 Electronic Scheduling 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.4.2.4 Grouping and Sorting

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 Changes That Do Not Cause Delay

3.6.4 Time Impact Analysis (Prospective Analysis)

3.6.5 Fragmentary Network (Fragnet)

3.6.6 Time Extension

3.6.7 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 RESIDENT MANAGEMENT SYSTEM

3.10 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/23, CHG 1: 08/24

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

AACE 84R-13 (2015) Planning and Accounting for Adverse Weather

AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)

ASCE 67-17 (2017) Schedule Delay Analysis

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

Government approval is required for submittals with a "G" 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

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 Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of similar size and complexity to this contract, using Primavera P6.

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

SECTION 01 32 01.00 10 Page 3

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government uses Primavera P6. Ensure exported schedule files are compatible with the version of P6 used by the Government.

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. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.

2.1.2.2 Other Than Primavera

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. The Contractor shall provide the project schedule in the Precedence Diagram Method (PDM) using the Standard Data Exchange Format (SDEF). 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, dredging)

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

SECTION 01 32 01.00 10 Page 4

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 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.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

In conjunction with the post award conference or pre construction conference the Government and the Contractor will hold a separate and distinct Scheduling Expectations Kickoff Meeting(SEKO). The intent of this meeting is for the Government to review with the contractor the requirements of the scheduling specification, communicate the Government’s expectations regarding schedule development and management, and answer any questions the Contractor may have regarding the schedule requirements.

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

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

- Seasonal Constraints 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 Original Durations (OD) greater than 20 workdays or 30 calendar days.

3.2.3 Procurement Activities

Include in the schedule 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 Activities

Include the following activities/tasks, if applicable, in the initial project schedule and all updates for each respective dredge area or reach.

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 (TAB).

i. Demobilization

SECTION 01 32 01.00 10 Page 6

3.2.5 Government Activities

Show in schedule, 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 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

2 AREA 4 Area of work

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 Government approved acceptance section.

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.

SECTION 01 32 01.00 10 Page 7

3.2.6.4 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Number (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI 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.

Mandatory constraints that ignore or affect 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 Seasonal Constraints) 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 Adverse Weather

Ensure anticipated adverse weather is accounted for in the Project

SECTION 01 32 01.00 10 Page 8

Schedule. AACE 84R-13 provides methodologies for techniques in planning for adverse weather. The preferred methodology is the use of a weather calendar. If a method other than a weather calendar is proposed, discuss the reason during the SEKO meeting.

3.2.9 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, Seasonal Constraints, 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 a weather calendar is used its implementation and execution is to be in accordance with AACE 84R-13

3.2.10 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" is to have no predecessor logic, and the last activity -"End Project" is to have no successor logic. Except as noted above, each activity must have at least a start-to-start or finish-to-start relationship with its predecessor and a finish-to-finish or finish-to-start relationship with its successor.

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

3.2.11 Default Progress Data Disallowed

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

3.2.12 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

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.13 Added and Deleted Activities

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

SECTION 01 32 01.00 10 Page 9

3.2.14 Original Durations

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

3.2.15 Leads, Lags, and Start to Finish Relationships

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

a. Leads (negative lags) are prohibited.

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

3.2.16 Retained Logic

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

3.2.17 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management. Budgeted cost of activity is to be reduced by the amount needed to correct deficiency. The activity referenced in paragraph COST LOADING of CLOSEOUT ACTIVITIES must have its budgeted cost increased by this amount.

3.2.18 Remaining Duration

Update the remaining duration for each activity based on the number of estimated workdays it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete. The remaining duration for unstarted activities are not to be less than its orginal duration.

3.2.19 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 hours) and the Government agreeing that the schedule is reasonable and achievable.

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

SECTION 01 32 01.00 10 Page 10

3.3 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, or other form of electronic submission,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, 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 notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.3.2 Periodic Schedule Updates

Update the Project Schedule with every pay application. Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete. Include employee roster for key personnel (Superintendent, SSHO, and QC) for each shift. Updated information 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 Electronic Scheduling Data

Provide electronic scheduling data containing the current project schedule and all previously submitted schedules 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. Also include the Narrative Report and all required Schedule Reports. The electronic file is to identify the type of schedule (Initial, Update), full contract number, Data Date and schedule file name. Each schedule must have a unique file name contract number and data date.

3.4.2 Network Diagram

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

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

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

3.5 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. 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 for the three-week lookahead. The Contractor shall provide meeting minutes to the Government after each weekly progress meeting.

3.6 REQUESTS FOR TIME EXTENSIONS

ASCE 67-17 provides delay analysis guidelines. If there is a conflict between the contract and guidance provided in ASCE 67-17 , the contract will govern. Provide justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval, within 10 days of a delay occuring. Also prepare a time impact analysis for each Government request for proposal (RFP)to justify time extensions.

3.6.1 Justification of Delay

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

SECTION 01 32 01.00 10 Page 12

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 Changes That Do Not Cause Delay

If it is determined that a change does not constitute a schedule time extension, a fragnet as described in paragraph FRAGMENTARY NETWORK, is to be created and inserted into the Project schedule.

3.6.4 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry recommended practice 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.5 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

SECTION 01 32 01.00 10 Page 13 successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.

3.6.6 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, are not a cause for an extension to the performance period, completion date, or any interim milestone date.

3.6.7 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 workdays, 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

SECTION 01 32 01.00 10 Page 14 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, belongs to the Project and is available for Contractor and Government use. This includes activity and project float. Activity float is the number of workdays 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 "End Project" finish.

3.9 TRANSFER OF SCHEDULE DATA INTO RESIDENT MANAGEMENT SYSTEM

Ensure schedule data is uploaded to RMS. This data is 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 versions of the application for progress payment.

3.10 PRIMAVERA P6 MANDATORY REQUIREMENTS

Ensure Primavera P6 settings provide a schedule capable of fulfilling the requirements of the contract. 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 non-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" un-selected.

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

j. Activity Names must have a verb-noun structure and contain the most defining and detailed description within the first 30 characters.

k. The daily ending hour for all work calendars must be the same.

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:

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

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

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

SECTION 01 33 00 Page 4

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…