01_32_01.pdf

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01

PROJECT SCHEDULE (NAU)

05/19

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

1.4 CORRESPONDENCE AND TEST REPORTS

1.5 DEFINITIONS AND TERMINOLOGY

1.5.1 Change

1.5.2 Revision

1.5.3 Update

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Design Activities (Design-Build Projects)

3.3.4 Permitting and Approval Activities

3.3.5 Long Lead Activities

3.3.6 Mandatory Tasks

3.3.7 Government and Host Nation Activities

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 Construction Completion Milestone and Constraint

3.3.8.3 End Project Finish Milestone and Constraint

3.3.8.4 Interim Completion Dates and Constraints

3.3.8.4.1 Start Phase

3.3.8.4.2 End Phase

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

3.3.13 Added and Deleted Activities

3.3.14 Original Durations

SECTION 01 32 01 Page 1

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remaining Duration

3.3.19 Cost Loading of Closeout Activities

3.3.19.1 As-Built Drawings

3.3.19.2 O & M Manuals

3.3.20 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Schedule Updates

3.4.4 Changed or Revised Schedule

3.4.4.1 Detailing of Construction Activities During Design

3.4.4.2 Payment

3.5 SUBMISSION REQUIREMENTS

3.5.1 Electronic Data

3.5.2 Narrative Report

3.5.3 Network Diagram

3.5.3.1 Preliminary, Initial, Revised Schedules

3.5.3.2 Periodic Schedule Updates

3.5.3.3 Continuous Flow

3.5.3.4 Project Milestone Dates

3.5.3.5 Critical Path

3.5.3.6 Banding

3.5.3.7 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

3.8.6 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS-CM

3.11.1 Standard Activity Coding Dictionary

3.11.1.1 Workers Per Day (WRKP)

3.11.1.2 Responsible Party Coding (RESP)

3.11.1.3 Area of Work Coding (AREA)

3.11.1.4 Modification Number (MODF)

3.11.1.5 Bid Item Coding (BIDI)

3.11.1.6 Phase of Work Coding (PHAS)

3.11.1.7 Category of Work Coding (CATW)

3.11.1.8 Feature of Work Coding (FOW)

3.11.2 Manual Entry of Schedule Information

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

SECTION 01 32 01 Page 2

SECTION 01 32 01

PROJECT SCHEDULE (NAU)

05/19

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. When used, a designation following the "G" designation 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 Preliminary Project Schedule; G Initial Project Schedule; G

SD-07 Certificates Schedule Updates; G Revised Schedule; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

1.4 CORRESPONDENCE AND TEST REPORTS

All correspondence (e.g., letters, Requests for Information (RFI's), SECTION 01 32 01 Page 3 e-mails, meeting minute items, QC Daily Reports, material delivery tickets, photographs) and test reports (e.g., concrete, soil compaction, weld, pressure)must identify or otherwise reference the applicable existing activity(ies) in the schedule.

1.5 DEFINITIONS AND TERMINOLOGY

1.5.1 Change

A change to the project schedule refers to any of the following:

a. Alterations to activity logic (predecessor or successor activities, lag or lead durations)

b. Combining or dividing activities

c. Creation or deletion of activities, including via modifications.

Activity ID and description changes are considered new activities.

d. Adjustments in scheduled duration or amount

e. Any other modification to the schedule which alter the planned execution of the works.

No changes shall be made to the approved project schedule without either the express written direction of the Contracting Officer, or their prior approval. All changes must be provided via a formal submittal and shown on the submittal register. Any changes not specifically authorized by the Contracting Officer may result in disapproval of the entire schedule and the rejection of any requests for partial payment.

1.5.2 Revision

A revision to the project schedule is equivalent to a change in the project schedule. See Change.

1.5.3 Update

An update to the project schedule refers to information associated with an activity that reflects actual progress, and is limited to:

a. The entry of actual start and finish dates for activities

b. Updated scheduled start and finish dates of an activity without any changes in logic, resource assignment, or original duration resulting from entering actual start and finish dates of dependent activities

c. Recording of progress on an activity to represent work completed, including expected/planned finish date based on actual progress

d. Completion of a milestone or other event in the schedule

PART 2 PRODUCTS

2.1 SOFTWARE

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

SECTION 01 32 01 Page 4

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.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, 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, 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, including design activities (when the contractor is responsible for design) and all construction is required. Scheduling is the responsibility of the Contractor.

Contractor management personnel must actively participate in its development. The contractor is responsible for coordinating the schedule with their subcontractors, suppliers, and where design is being performed by the contractor, their designers to ensure the Project Schedule remains accurate. 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 01 Page 5

Negative values for activity costs are prohibited. If existing requirements are reduced or removed via modification, reduce the value of existing activities.

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 or reject the pay request in its entirety until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer 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 construction activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

Design, Review, and Approval activities may have longer durations to reflect the actual requirements of the activity.

3.3.3 Design Activities (Design-Build Projects)

Include design activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period.

Provide at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. Also include review and correction periods associated with each item.

3.3.4 Permitting and Approval Activities

Include activities for submission, review, and approval of any required permits from Host Nation authorities at any level (National, State, Local, etc.) which could impact the schedule. Ensure appropriate logic ties to documents required to be generated and include adequate review periods for Host Nation authorities, including any required conferences.

This requirement does not include recurring approval activities which extend throughout the performance period, such as vetting of workers or host nation installation access requirements.

SECTION 01 32 01 Page 6

3.3.5 Long Lead 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 activities are those with an anticipated duration of at least 25 calendar days.

3.3.6 Mandatory Tasks

Include the following activities/tasks in the initial project schedule and all updates unless the activity/task is not required elsewhere in this contract.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission, review and acceptance of design packages or features requiring design completion (extensions of design). Preparation and review shall be separate activities.

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

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

g. Submission and approval of DD1354 data and installed equipment lists.

h. Submission and approval of testing and air balance (TAB).

i. Submission of TAB specialist design review report.

j. Submission and approval of fire protection specialist.

k. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Controls testing plan submission.

o. Controls testing.

p. Performance Verification testing.

q. Other systems testing, if required.

r. Contractor's pre-final inspection.

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

SECTION 01 32 01 Page 7

t. Government's pre-final inspection.

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

v. Final inspection.

3.3.7 Government and Host Nation Activities

Show Government and Host Nation activities that could impact progress.

These activities include, but are not limited to: approvals, acceptance, design reviews, permits, , inspections, utility connection or tie-in, move-in or move-out of facilities, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.8 Contract Milestones and Constraints

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

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer 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 Construction Completion Milestone and Constraint

The last activity required to be completed prior to acceptance of the project by the Government must be a finish milestone titled "Required Completion."

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 "Required Completion" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "Required Completion" milestone float calculation reflects negative float on the longest path.

3.3.8.3 End Project Finish Milestone and Constraint

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

Activities which are not required to be completed prior to acceptance should be linked to this milestone, rather than the "Required Completion" milestone. Typical activities may include completion of as-built drawings, final O&M manuals, etc. The Government retains right to direct activities to be linked to the "Required Completion" milestone.

The "End Project" milestone represents the completion of all physical work at the project site and acceptance or approval of all contractor required

SECTION 01 32 01 Page 8 deliverables. It normally coincides with the contractors submission of final payment.

3.3.8.4 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.4.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.4.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.9 Calendars

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

Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop seasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it shall be assigned to a calendar showing non-work weather days on a monthly basis, with the non-work weather days selected at random across the weeks of the calendar. Assign non-work days over the actual work week. If the contract includes baseline weather days in Section 00 74 01 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER, the number of non-work weather days in the monthly calendar shall match the number of baseline weather days in that section.

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.

SECTION 01 32 01 Page 9

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

SECTION 01 32 01 Page 10

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

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 approval of all O & M manuals.

3.3.20 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data 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 approval. The approved 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

SECTION 01 32 01 Page 11 performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 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 approval within 42 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.

Include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences; permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Include the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone,including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. Constrain construction activities by Government acceptance of associated designs.

As the design proceeds and design packages are developed, fully detail the remaining construction activities. To prevent delays in processing payments, do not add construction activities to schedule updates but submit as a Revised Schedule as described elsewhere in this specification.

No payment will be made for work items not fully detailed in the Project Schedule.

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

Schedule Updates shall be submitted as a resubmittal of the approved project schedule.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

SECTION 01 32 01 Page 12

3.4.4 Changed or Revised Schedule

When it becomes necessary to change or revise (not update) the approved schedule, prepare a detailed narrative identifying all changes to the project schedule by activity ID and activity name, including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

Submit the revised schedule, narrative, and all documents schedule reports identified in paragraph SCHEDULE REPORTS as a new transmittal, not a resubmittal of a previously approved submittal.

3.4.4.1 Detailing of Construction Activities During Design

Update the schedule to include detailed construction activities as the design progresses, but not later than the submission of the final un-reviewed design submission for each separate design package. The Contracting Officer may require submission of detailed schedule activities for any distinct construction that is started prior to submission of a final design submission if such activity is authorized.

All construction activities dependent on design must be detailed in a Revised Schedule submitted no later than the date of the 100% (Final) design for the associated work, otherwise the schedule shall be deemed unacceptable for the purposes of evaluating progress and making payment.

3.4.4.2 Payment

Payment will not normally be made on any revised schedule prior to approval by the Government. Payment will continue to be made based on updates to the previously approved schedule.

Notwithstanding the above, the Government may allow payment to be made on an unapproved revised schedule which shows actual progress to date. Such allowance shall be made in writing by the Contracting Officer. This shall not be construed as approval of the schedule nor the acceptability of the contractors plan for completing the work.

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 Electronic Data

Provide via electronic means the current project schedule in the format of the scheduling software (e.g. .xer). Also include pdf copies of the Narrative Report and all required Schedule Reports. Each schedule must have a unique file name and use project specific settings. Files shall be submitted through RMS-CM as attachments to a submittal. E-mail will also be used for attachments up to 10 MB in size.

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

SECTION 01 32 01 Page 13 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. With the exception of Periodic Schedule Updates (where none of this information is changed) 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, and resource changes.

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

3.5.3 Network Diagram

A Network Diagram shall be included with every schedule submission, update, and revision. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Network Diagram shall show the name and description of all activities with their duration and total float.

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

3.5.3.1 Preliminary, Initial, Revised Schedules

Two Network Diagrams shall be submitted:

a. A GANTT chart including Start and Finish Dates, total float, logic, and duration.

b. A standard Activity on Node CPM chart showing early start, early finish, late start, and late finish, along with all logic.

3.5.3.2 Periodic Schedule Updates

The Network Diagram for schedule updates shall be of a GANTT Chart style and include: Baseline Start and Finish Dates, current planned Start and Finish Dates, total float, and duration. The chart shall show the baseline and actual/planned bars.

3.5.3.3 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

SECTION 01 32 01 Page 14 earned value on the diagram.

3.5.3.4 Project Milestone Dates

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

3.5.3.5 Critical Path

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

3.5.3.6 Banding

Organize activities using the Work Breakdown Structure (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.3.7 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 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 Schedule Updates of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.

SECTION 01 32 01 Page 15

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 RFI's, RFP's 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 01 Page 16

3.8.5 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis via a modification to the contract 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 ("Construction Completion" 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 01 Page 17

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. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

3.11 TRANSFER OF SCHEDULE DATA INTO RMS-CM

Import the schedule data into RMS-CM. 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 RMS data for the application for progress payment.

Data may be imported into RMS-CM only if the scheduling software allows activity coding in the Standard Data Exchange Format (SDEF) as described below. If the scheduling software does not allow importing into RMS-CM using SDEF, the information must be manually loaded in RMS-CM by the contractor.

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

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 20 Feature of work*

SECTION 01 32 01 Page 18

Field Activity Code Length Description

*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.11.1.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.11.1.2 Responsible Party Coding (RESP)

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

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities which are the responsibility of any Host Nation or foreign (non-US) Government agency at any level, including, but not limited to: reviews, permit approvals, and clearances must have a Host Nation Responsibility Code assigned.

c. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); GOVT (for USACE); and HONA (for Host Nation).

d. The Prime Contractor MUST have a Responsibility Code of "PRIM".

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

SECTION 01 32 01 Page 19 by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.11.1.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.11.1.6 Phase of Work Coding (PHAS)

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

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

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

3.11.1.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to design, design submittal, design reviews, review conferences, permits, construction submittals, 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.11.1.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

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

An activity can have only one Feature of Work Code.

3.11.2 Manual Entry of Schedule Information

If the scheduling software is not able to create a SDEF file, the contractor shall manually enter the following schedule information in RMS-CM for each activity:

a. ID (Number)

b. Description

c. Duration

d. Amount

e. CLIN

f. All other information identified in Paragraph STANDARD ACTIVITY CODING

STRUCTURE

SECTION 01 32 01 Page 20

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. All resources applied to an activity must NOT have "auto compute actuals" and "calculate costs from units" selected.

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

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

-- End of Section --

SECTION 01 32 01 Page 21