Nawiliwili_Harbor_RTA_Specs_2018-09-11.pdf

W9128A-18-B-0004

SPECIFICATIONS

NAWILIWILI HARBOR

PHASE II MAINTENANCE DREDGING

ISLAND OF KAUAI, HAWAII

CONTRACT NO. W9128A-11-D-0004-0010

U.S. Army Corps of Engineers, Honolulu District

Date: September 11, 2018 (Am-0004)

O&M DREDGING: PHASE II NAWILIWILI HARBOR

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 32 00 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00 RMS3 - CONTRACTOR MODE (RMS3/CM)

01 45 04 CONTRACTOR QUALITY CONTROL

01 57 20 ENVIRONMENTAL PROTECTION

01 62 35 RECYCLED / RECOVERED MATERIALS

01 78 00 CLOSEOUT SUBMITTALS

01 90 00 MISCELLANEOUS PROVISIONS

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 20 23 DREDGING

35 20 23.13 NATIONAL DREDGING QUALITY MANAGEMENT PROGRAM SCOW -

ULLAGE PROFILE

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 32 00 Page 1

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

SECTION 01 32 00

PROJECT SCHEDULE

03/17

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

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;

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

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

SD-06 Test Reports

Narrative Report

Schedule Reports

Periodic Schedule Updates

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

SECTION 01 32 00 Page 2

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 intends to use Primavera P6.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required

SDEF file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the native schedule file (or

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 that is compliant with this specification but is other than Primavera P6, the software must be capable of generating a data file in the Standard Data Exchange Format (SDEF) as described in paragraph STANDARD ACTIVITY CODING DICTIONARY.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to

FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path

Method (CPM) of network calculation to generate all Project Schedules.

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

3.2 BASIS FOR PAYMENT AND COST LOADING

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

3.2.1 Activity Cost Loading

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

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

SECTION 01 32 00 Page 3

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer 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.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones, all Definable Features of Work (FOW), 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:

3.3.2 Activity Durations

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

Less than 2 percent of all non-procurement activities may have Original

Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Permit Activities

Include permit activities with the necessary conferences and follow-up actions and design package submission dates.

3.3.4 Procurement Activities

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

3.3.5 Mandatory Tasks

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

a. Submission, review and acceptance of SD-01 Preconstruction Submittals

(individual activity for each).

b. Submission, review and acceptance of features require design completion

c. Submission and approval of as-built drawings.

d. Contractor's pre-final inspection.

SECTION 01 32 00 Page 4

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

f. Government's pre-final inspection.

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

h. Final inspection.

3.3.6 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, environmental permit approvals by State regulators, inspections, utility tie-ins, road closures, Government Furnished Equipment (GFE) and Notice to

Proceed (NTP) for phasing requirements.

3.3.7 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. Additional information is available on the RMS web site:

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

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 30 Feature of work*

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

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

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

SECTION 01 32 00 Page 5

3.3.7.2 Responsible Party Coding (RESP)

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

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and

Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for

USACE). Unacceptable code values are abbreviations of the the names of subcontractors.

3.3.7.3 Area of Work Coding (AREA)

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

Activities cannot have more than one Work Area Code.

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

3.3.7.4 Modification Number (MODF)

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

Number Code.

3.3.7.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item

Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.7.6 Phase of Work Coding (PHAS)

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

Phase of Work code.

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

3.3.7.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes

SECTION 01 32 00 Page 6

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

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

3.3.7.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the

Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 04 QUALITY CONTROL.

An activity can have only one Feature of Work Code.

3.3.8 Contract Milestones and Constraints

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

Mandatory constraints that ignore or 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.3.8.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled

"NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.3.8.2 End Project Finish Milestone and Constraint

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

Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the

"End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate

Government activities to support a Contractor's early completion.

3.3.8.3 Interim Completion Dates and Constraints

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

3.3.8.3.1 Start Phase

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

3.3.8.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the

SECTION 01 32 00 Page 7 finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.9 Calendars

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

Develop calendars to accommodate any contract defined work period such as a

7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop

Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

3.3.10 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP

Acknowledged" may have no predecessor logic, and the last activity -"End

Project" may have no successor logic.

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

3.3.11 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the

Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the

Contractor's schedule.

3.3.12 Out-of-Sequence Progress

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

Narrative Report and in the periodic schedule update meetings.

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

3.3.14 Original Durations

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

3.3.15 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in

SECTION 01 32 00 Page 8

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

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

3.3.16 Retained Logic

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

3.3.17 Percent Complete

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

3.3.18 Remaining Duration

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

3.3.19 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the

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

3.3.19.1 As-Built Drawings

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

3.3.19.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the

Government's acceptance of all O & M manuals.

3.3.20 Anticipated Adverse Weather

Paragraph applicable to contracts with clause S-36.5 TIME EXTENSIONS FOR

UNUSUALLY SEVERE WEATHER (Section 01 90 00). Original durations must account for anticipated adverse weather. All work periods not identified as non-work periods on each calendar will be interpreted as a

SECTION 01 32 00 Page 9

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

Contractor-intended work period.

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

c. The Government shall be exempt from liability for early completion delay damages. No claim shall be made by or allowed to the Contractor for any damages which may arise out of any delay to early completion.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

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

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the

Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for acceptance. The accepted Preliminary

Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project

Schedule to balance the contract award CLINS shown on the Price Schedule.

The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as permitting activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of all other specified

Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility

Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for acceptance within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a

SECTION 01 32 00 Page 10 reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

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

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

a. Update information including Data Date (DD), Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent

Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's

Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .XER). Also include on the data CD/DVDs the Narrative

Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data

Date, Contract ID, and file name. Each schedule must have a unique

Contract ID and file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative

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

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

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

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

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

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

SECTION 01 32 00 Page 11

W9128A-18-B-0004

O&M DREDGING: PHASE II NAWILIWILI HARBOR

changes, and actual start and finish date changes.

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

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain

Activity Numbers, Activity Description, Original Duration, Remaining

Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish

Date, Total Float, Actual Start Date, Actual Finish Date, and Percent

Complete. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

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

3.5.3.3 Total Float Report

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

3.5.3.4 Earnings Report by CLIN

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

Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

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

3.5.4 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic

Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting

Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to

SECTION 01 32 00 Page 12 left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.4.2 Project Milestone Dates

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

3.5.4.3 Critical Path

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

3.5.4.4 Banding

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

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow

S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or

Government. The meeting is a working interactive exchange which allows the

Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer.

Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS together with the monthly progress payment request.

SECTION 01 32 00 Page 13

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC

SCHEDULE UPDATE MEETINGS 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.

3.8 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.8.1 Justification of Delay

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

3.8.2 Time Impact Analysis (Prospective Analysis)

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

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

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

3.8.4 Fragmentary Network (Fragnet)

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

Contracting Officer prior to incorporation into the project schedule.

SECTION 01 32 00 Page 14

3.8.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.8.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.9 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.9.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.9.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for

Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

3.9.3 Recovery Schedule

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

SECTION 01 32 00 Page 15

3.10 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. However, in accordance with paragraph EARLY COMPLETION SCHEDULE AND THE RIGHT TO FINISH EARLY, the

Government is specifically and expressly exempt from liability for early completion delay damages. Activity float (or Free 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 (or Total Float) is the number of work days between the projected early finish and the contract completion date milestone.

3.11 TRANSFER OF SCHEDULE DATA INTO RMS3/CM

Import the schedule data into RMS3/CM (See Section 01 45 00). 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 data in RMS3/CM for the progress payment.

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.XER) from the Government, if one is available, prior to building the schedule. The following settings are mandatory and required in all schedule submissions to the Government:

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

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

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

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

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

8.0 Hour days.

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

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

Logic".

h. Set up cost loading using a single lump sum labor resource. The

Price/Unit must be $1/hr, Default Units/Time must be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

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

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

-- End of Section –

SECTION 01 33 00 Page 1

SECTION 01 33 00

SUBMITTAL PROCEDURES

03/17

PART 1 GENERAL

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections.

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

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

Contractor's Quality Control (CQC) System Manager shall check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed variations from the contract requirements are to be clearly identified and an explanation provided as to why it is being requested. Include within submittals items such as: Contractor's, drawings; descriptive literature including (but not lmited to) diagrams, operating charts or curves; test reports; certifications; warranties; and other such required submittals.

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

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

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

SD-01 Preconstruction Submittals

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

Certificates of insurance

Surety bonds

List of proposed Subcontractors

Network Analysis Schedule (NAS)

Submittal register

Accident Prevention plan

Quality Control(QC) plan

SECTION 01 33 00 Page 2

Environmental Protection Plan

Permits

SD-02 Shop Drawings

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

SD-11 Closeout Submittals

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

Special requirements necessary to properly close out a construction 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.1.2 Approving Authority

Office or designated person authorized to approve submittal.

1.1.3 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, (except those

SD-01 Pre-Construction Submittals noted above), construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.2 SUBMITTALS

Government approval/acceptance is required for submittals with a "G" designation; submittals not having a "G" designation are for information only. The following shall be submitted in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

Submittal Register; G

Monthly Updates

Two copies of the monthly update shall be submitted together with the monthly progress payment request.

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Government Approved (G)

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

Within the terms of the Contract Clause entitled, "Specifications and

Drawings for Construction," they are considered to be "shop drawings."

SECTION 01 33 00 Page 3

1.3.2 Information Only

Submittals not requiring Government approval will be for information only.

1.4 QUANTITY OF SUBMITTALS

1.4.1 Number Copies of Government Approved Submittals: 4

1.4.2 Number of Copies of For Information Only Submittals: 3

1.4.3 Electronic Copies

Provide all material submittals in pdf format on CD or DVD. File names shall include the transmittal and item numbers associated with the materials being submitted.

In addition, each month's progress payment request shall include a CD or

DVD containing a complete set of all submittals made during the period for which payment is being requested in pdf format. The data on the CD/DVD shall include the transmittal memo (ENG 4025) as well as a copy of all material covered by the transmittal; the name of each file shall match the transmittal number and item number, e.g. Transmittal 01 45 00-1, Item 1.

Also include a copy of the Submittal Register identifying the transmittals contained on the CD/DVD.

1.5 APPROVED/ACCEPTED SUBMITTALS

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

Approval or acceptance will not relieve the Contractor of the responsibility for any error which may exist, as the Contractor under the

Contractor Quality Control (CQC) requirements of this contract is responsible for dimensions, the design of adequate connections and details, and the satisfactory construction of all work.

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

1.6 APPROVED SAMPLES

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

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

SECTION 01 33 00 Page 4

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

Samples of various materials or equipment delivered on the site or in place may be taken by the Contracting Officer for testing. Samples failing to meet contract requirements will automatically void previous approvals.

Contractor to replace such materials or equipment to meet contract requirements.

Approval of the Contractor's samples by the Contracting Officer does not relieve the Contractor of his responsibilities under the contract.

1.7 DISAPPROVED OR REJECTED SUBMITTALS

Contractor shall make corrections required by the Contracting Officer. If the Contractor considers any correction or notation on the returned submittals to constitute a change to the contract drawings or specifications; notice as required under the clause entitled, "Changes," is to be given to the Contracting Officer. Contractor is responsible for the dimensions and design of connection details and construction of work.

Failure to point out deviations may result in the Government requiring rejection and removal of such work at the Contractor's expense.

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

1.8 INFORMATION ONLY SUBMITTALS

Normally submittals for information only will not be returned. Approval of the Contracting Officer is not required on information only submittals.

The Government reserves the right to require the Contractor to resubmit any item found not to comply with the contract. This does not relieve the

Contractor from the obligation to furnish material conforming to the plans and specifications; will not prevent the Contracting Officer from requiring removal and replacement of nonconforming material incorporated in the work;

and does not relieve the Contractor of the requirement to furnish samples for testing by the Government laboratory or for check testing by the

Government in those instances where the technical specifications so prescribe.

1.9 GOVERNMENT APPROVING AUTHORITY

When approving authority is Contracting Officer, the Government will:

a. Note date on which submittal was received.

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

c. Identify returned submittals with one of the actions defined in paragraph entitled, "Review Notations," of this section and with markings appropriate for action indicated.

SECTION 01 33 00 Page 5

Upon completion of review of submittals requiring Government approval, stamp and date approved submittals. 1 copy of the submittal will be returned to the Contractor.

1.9.1 Government Review Action Codes

"A" - "Approved as submitted"; "Completed"

"B" - "Approved, except as noted on drawings"; "Completed"

"C" - "Approved, resubmission required"; "Resubmit"

"D" - "Returned by correspondence"; "Completed"

"E" - "Disapproved (See attached)"; "Resubmit"

"F" - "Receipt acknowledged"; "Completed"

"G" - "Other (Specify)"; "Resubmit"

"X" - "Receipt acknowledged, does not comply"; "Resubmit"

1.9.2 Review Notations

Contracting Officer review will be completed within 30 calendar days after date of submission. Submittals will be returned to the Contractor with the following notations:

a. Submittals marked "approved" or "accepted" authorize the Contractor to proceed with the work covered.

b. Submittals marked "approved as noted" "or approved except as noted, resubmittal not required," authorize the Contractor to proceed with the work covered provided he takes no exception to the corrections.

c. Submittals marked "not approved" or "disapproved," or "revise and resubmit," indicate noncompliance with the contract requirements or design concept, or that submittal is incomplete. Resubmit with appropriate changes. No work shall proceed for this item until resubmittal is approved.

d. Submittals marked "not reviewed" will indicate submittal has been previously reviewed and approved, is not required, does not have evidence of being reviewed and approved by Contractor, or is not complete. A submittal marked "not reviewed" will be returned with an explanation of the reason it is not reviewed. Resubmit submittals returned for lack of review by Contractor or for being incomplete, with appropriate action, coordination, or change.

1.10 WITHHOLDING OF PAYMENT

Payment for materials incorporated in the work will not be made if required approvals have not been obtained.

PART 2 PRODUCTS (Not Applicable)

Not Used

SECTION 01 33 00 Page 6

PART 3 EXECUTION

3.1 SUBMITTAL REGISTER

Prepare and maintain submittal register as the work progresses. Use

RMS3/CM (see Section 01 45 00) to create the Submittal register. Complete the columns labeled: Activity Number, Transmittal Number, and Contract

Schedule Dates on the submittal register form.

The completed Submittal Register shall be submitted to the Contracting

Officer for approval within 30 calendar days after Notice to Proceed.

The submit dates and need dates in the submittal register shall be coordinated with the dates in the Contractor's progress schedule.

Updates to the Submittal Register showing the Contractor action codes and actual submittal dates with Government action codes and action…