Amendment 0007_Lee Sherman Section 01 32 00 Scheduling.pdf

Lee and Sherman Barracks Upgrades Project 23 August 21 US Military Academy, West Point, NY Amendment #5

Section 01 32 01.00 10 Page 1 Aug 13, 2021 - 11:37 AM

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G, RO

Preliminary Project Schedule; G, RO

Initial Baseline Project Schedule; G, RO

Periodic Schedule Update; G, RO

Narrative Report; G, RO

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.

Include a copy of the candidate's resume with qualifications. The Contracting Officer may remove the Designated Project Scheduler, and require replacement, if the scheduler does not effectively fulfill their duties in accordance with this Contract requirements.

Section 01 32 01.00 10 Page 2 Aug 13, 2021 - 11:37 AM

1.3.1 Project Scheduler Qualifications and Requirements

The authorized project scheduler must have a minimum of three years of experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this Contract specifications. The scheduler must have a comprehensive knowledge of CPM scheduling, principles application and obtain the skill/knowledge on following and adhering to this Contract, specification and drawing. The Designated Project Scheduler must have prepared and maintained at least five previous construction schedules of similar size and complexity to this Contract, utilizing the most recent version of Oracle Primavera P6.

During the entire Contract duration, the Government will require the Project Scheduler to be present at the project site office/trailers as often as needed to maintain and provide the Government with a fully completed status-to-date 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.

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

Utilize the most recent version of Oracle Primavera P6. Provide the "xer" export file in a version of P6 importable by the Government systems.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

The Contractor is prohibited from beginning work on-site prior to Government approval the Project Baseline Schedule. Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the detailed proposed sequence to perform the work and dates with for starting and completing all schedule activities. A detailed schedule of the entire project is required.

The schedule development, details, maintenance and to-date status of the entire schedule is the responsibility of the Contractor and will required Government approval on a monthly basis. Failure in receiving the Government approval may result in rejection of payment in full or for partial amount.

Section 01 32 01.00 10 Page 3 Aug 13, 2021 - 11:37 AM

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 and detailed Project Schedule. Provide a schedule that is a forward planning, a project monitoring tool and a schedule the Contractor and Sub Contractors are to follow on a daily basis and be held responsible and accountable. 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.1.1 Project Schedules

It is to the Government's discretion of Contractor to submit separate Preliminary, Initial, Baseline and Monthly Project Schedules for each structure: 740 (Lee) and Sherman Barracks.

3.1.3 Approved Project Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions, and to provide the basis of all progress payments. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments.

When Contractor fails to submit schedules within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.4 Schedule Status Reports

Provide a Schedule Status Report(s) on at least a weekly and monthly basis.

If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor must take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant,planned, resources and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.5 Default Terms

Failure of the Contractor to comply with the requirements of this Contract will be grounds for a determination by the Contracting Officer that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the Contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the Contract.

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

Section 01 32 01.00 10 Page 4 Aug 13, 2021 - 11:37 AM 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 cost documentation within 48 hours to demonstrate reasonableness, when directed by the Contracting Officer. Commissioning and Close-Out activities will be paid at 100 percent complete, and not partially paid.

Do not include field overhead positions as individual pay items. Evenly disperse overhead costs and profit to each activity over the duration of the project.

It is the discretion of the Government of which activities are to be cost loaded.. Cost of activities will be approved by the Government. When directed by the Government, Contractor must reallocate activity cost appropriately with or without Contractor Documentation.

3.2.2 Layout Activity Cost Loading

"Layout" activities will have zero cost. ("Layouts" have been captured on project drawings and paid by the Government at the completion of Design.)

3.2.3 Schematic Diagram/Drawing Activity Cost Loading

"Schematic Diagram/Drawing" activities will have zero cost. ("Schematic Diagram/Drawing" are supplied by the manufacturer and paid at the Government verification of material delivery and or install.)

3.2.4 Cost Loading of Submittal

"Submittal" Activities will zero cost. Government does not allow cost loading of submittals. Cost loading of submittals is prohibited.

3.2.5 Mobilization and Demobilization Cost

Under a separate WBS for each Mobilization and Demobilization include detail activities with reasonable cost. Front-end loading is prohibited. Provide the Government with detail documentation and cost of Mobilization and Demobilization, prior to submitting a Preliminary Schedule.

3.2.6 Cost Loading of Commissioning Activities

The value of all "Government Approval Received of Test Reports…." activities of commissioning systems are not be less than 10 percent of the total costs for procurement and construction activities of each commissioned system (Total Commissioned System Cost). Work performed on Testing, Checklist, Reports, Plans, Procedures, Manual's type activities are paid once "Government Approval Received" of the final document, only if cost are applicable and cost loading is approved by the Contracting Officer.

The activity(ies) for “Government Approval Received Final Commissioning Report” shall be valued at no less than 5% of the total commissioned system cost. The balance of the 10% shall be spread across any other “Government Approval Received...” activities for preliminary Commissioning testing reports (TAB, DALT, Start Up Testing, etc).

Section 01 32 01.00 10 Page 5 Aug 13, 2021 - 11:37 AM

3.2.7 Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and rejection of payment request 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 Project Contract, Specifications, Drawings with major milestones, and to allow for satisfactory project planning and execution. Include quantity and unit of measure on the Activity Name, ex: 50CY, 100Tons, 1000LF and others.

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. Activities are to have Duration 20 Workdays or less. Up to 1 percent of all non-procurement activities may have Original Durations (OD) greater than 20 workdays or 30 calendar days. Activities with Durations less than 20 Workdays must be reasonable and Achievable. Default, unreasonable and excessive durations are prohibited and will not be approved or accepted.

3.3.3 Procurement Activities

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

3.3.4 Baseline Schedule Activity Updates

Baseline activities neglected, overlooked, left-out of the Initial baseline schedule will be added, and the baselines schedule will be re-submitted, reviewed, and approved. Logic, Relationships, Durations, and schedule data of the initial baseline schedule is not to change. The Contractor must discuss and receive Government approval of added activities prior to the resubmission. No time extension and cost will be issued for neglected, overlooked, left-out activities.

3.3.5 Modification Obligatory Activities

Add Obligatory Activities leading to Modification(s) within 10 days of discovering the modification. The Contractor must meet, discuss and receive

Section 01 32 01.00 10 Page 6 Aug 13, 2021 - 11:37 AM

Government approval prior to schedule incorporation. Separate modification and activities by a dedicated WBS. Activities must be detailed. Capture and include all activity-associated data.

3.3.6 Mandatory Tasks

Include the following activities/tasks in the initial baseline 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 mechanical/electrical/information systems layout drawings.

d. Long procurement activities

e. Submissions, Reviews and approval of O & M manuals.

f. Submissions, Reviews and approval of as-built drawings.

g. Submission and approval of DD1354 data and installed equipment lists, draft and final.

h. Submissions, Reviews and approval of testing and air balance (TAB).

i. Submissions, Reviews and Approvals of TAB specialist design review report.

j. Submissions, Reviews and approval of fire protection specialist.

k. Submissions, Reviews and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems as defined in Section 01 91

00.15 10 TOTAL BUILDING COMMISSIONING. 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.00 10 Page 7

t. Government's pre-final inspection.

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

v. Final inspection.

w. Coordination With DPW Utility Privatization Contractors.

x. Detail Activities of all Sub Contractor Buyouts.

y. Submissions, Reviews and Approvals of all Mobilization and Demobilization.

z. Submission, Review-Approval of Preliminary Schedule

aa. Submission, Review-Approval of Initial Baseline Schedule

3.3.7 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-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.8 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the RMS CM web site:

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

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

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

9 CX 2 Commissioning & Commissioning Dependent Activities http://rms.usace.army.mil/

Section 01 32 01.00 10 Page 8 Aug 13, 2021 - 11:37 AM

Field Activity Code Length Description

10 BLDG 4 Barracks Name or Building Number

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

Assign Workers per Day for all field construction or direct work activities.

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.3.8.2 Responsible Party Coding (RESP)

Assign a unique responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity. Activities cannot have more than one Responsibility Code.

b. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements. Apply DOR (for the designer of record); and GOVT (for USACE); PRIM (for Prime Contractor) as RESP coding.

c. Utilize four unique characters in length where the first character identifies the trade (ex: “E” for Electrical, “M” for Mechanical, others as-required) and where the next three characters Identify the Sub-contractor. Examples of unique acceptable activity code values are: EACM (“ACME Electrical Company”); EXYZ (“XYZ Electrical Company”); MACM “ACME Mechanical Company,” MAIR (“Air Mechanical Company”).

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

Work Area Codes are to be applied on the following Work Breakdown Structure (WBS) and Activities: Mobilization/Demobilization, Deliveries, Laydown, Storage, Construction, Commissioning, and Closeout.

Section 01 32 01.00 10 Page 9 Aug 13, 2021 - 11:37 AM

3.3.8.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.8.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.8.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are preconstruction, procurement, construction, commissioning and closeout.

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.3.8.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 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.8.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.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.3.8.9 Commissioning Activities (CX)

Assign Activity Code "CX" to Commissioning and Commissioning Dependent Activities. Capture Submittals, Reviews, Approvals, Approvals Received, Meetings, Plans, Reports, Start-Ups, TABs, Procedures, Test, Re-Test, O and M Manuals, Checklist, Certificates, Logs, Seasonal, Packages, Training, and others. Include commissioning activities specified by the Government, Commissioning Agent(s), GC, and Sub Constrictors.

3.3.8.10 Barracks Name or Building Number

Section 01 32 01.00 10 Page 10 Aug 13, 2021 - 11:37 AM

Identify and Separate 740 (Lee) and Sherman Project Activities. Assign Activity Code "740" (Lee), "SHER" (or building number) to all activities.

An activity can only have one code.

3.3.9 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.9.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 by the Contractor.

3.3.9.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone, with a hard constraint, 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.9.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.9.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.9.3.2 End Phase

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

3.3.10 Calendars

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

Develop calendars to accommodate Contract defined work periods such as a 7-day calendar for Government Acceptance activities, concrete cure times, others as required. Develop the default Calendar to match the physical work

Section 01 32 01.00 10 Page 11 Aug 13, 2021 - 11:37 AM plan with non-work periods identified including weekends and holidays.

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

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-workdays selected at random across the weeks of the calendar, using the anticipated adverse weather delay workdays provided in Time Extension paragraph. Assign non-workdays over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather-related non-workdays to fall on weekends.

Minimum Calendars Required: 5-day work with applicable days off, five-day workweek with Weather days and applicable days off, seven-day workweek, six-day workweek with applicable days off, and six-day work week with weather days and an applicable day off.

3.3.11 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.12 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 activities 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.13 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.14 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.15 Original Durations

Section 01 32 01.00 10 Page 12 Aug 13, 2021 - 11:37 AM

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.16 Leads, Lags, and Start to Finish Relationships

Lags are not to be used unless approved by the Government on a case-by-case basis prior to incorporating the schedules. 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.17 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(ies) starts and the predecessor activity(ies) 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.18 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.19 Remaining Duration

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

3.3.20 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) (numerous CO activities may exist) 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.20.1 As-Built Drawings

If there is no separate Contract line item (CLIN) for as-built drawings, cost load the "Government Approval Received of as-built drawings" activity not less than $35,000 or 1 percent of the present Contract value, whichever is greater, up to $200,000. Activity will be paid when declared 100 percent complete upon the Government's approval.

Section 01 32 01.00 10 Page 13 Aug 13, 2021 - 11:37 AM

3.3.20.2 O & M Manuals

Cost load the final "Government Approval Received of O & M manuals" activity not less than $50,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.21 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial baseline Project Schedule (IPS) that indicates all scope and activities 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 reviewing, agreeing and approving the schedule is reasonable and achievable.

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

3.3.22 Activity Grouping, Lumping, Combining, Nesting

Activities are prohibited from Grouping, Lumping, Combining, and Nesting.

Refrain from listing a single high-level activity in place of two or more activities.

3.3.23 Activity IDs

1. Beginning with the Preliminary Schedule, Activity IDs are prohibited from changes.

2. The first character for Activities IDs of 740 (Lee) will begin with the letter “L,” and Sherman Barracks activities IDs cannot begin with the letter “L.”

3. The first character for Activities IDs of Sherman Barracks will begin with the letter “S,” and 740 (Lee) activities IDs cannot begin with the letter “S.”

3.3.24 Activity Usage and Separation

Activities cannot be interchangeable and or multi-purpose use between 740 (Lee) and Sherman Barracks.

All 740 (Lee) activities will be separated from Sherman Barracks activities and all Sherman Barracks activities will be separated from 740 (Lee) activities.

3.3.25 WBS and Activities

WBS (Work Breakdown Structure) is to be detailed. Ten activities are to lie under a single WBS. Greater than ten activities will require Contracting Officer Approval and are not to exceed fifteen activities.

Section 01 32 01.00 10 Page 14 Aug 13, 2021 - 11:37 AM

3.3.26 Activity Original Durations

Activities Original Durations from the Approved Baseline schedule are to be achieved.

3.3.27 Activity Excessive Actual Durations

Activity Actual Duration greater than Original Duration from the Approved baseline schedule must be divided into separate activities. Divide activity cost and, when applicable associated activity data. Newly separated activities are to be added to the Approved Baseline schedule. Resubmit Baseline schedule for Contracting Officer approval.

3.3.28 Activity Actual Start - Material Cost

Refrain from the Actual Start of activities for the sole purpose of collecting the cost of the material. Material is paid once the Government verifies and approves delivery or installation.

3.3.29 Activity Early Start and Late Start

Notify the Government of Early Start(s). Prior to an early start, the activity must have all resources readily available. Activity early start does not extend the original duration and must maintain the baseline schedule original durations.

Regardless of Free Float, notify the Government of Late Start(s). Prior to a late start, the activity must have all resources readily available.

Activity late start does not extend the finish calculated by the original duration. The activity must maintain the baseline schedule's original duration.

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. During the 15 days of developing the Preliminary Project Schedule, the Contractor, Contractor's scheduler, and the Government are to conduct a one-hour meeting once a week for adherence to project Contract, specification, and drawings. 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 or detailed for the remaining performance period. It must be early start and late finish

Section 01 32 01.00 10 Page 15 Aug 13, 2021 - 11:37 AM constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Baseline 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 planned construction activities. Activity code, 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). No payment will be made until the Government approves a fully detailed 90-day Preliminary Project Schedule, with exception of Payment of Bond and insurance.

3.4.2 Initial Baseline Project Schedule Submission

Submit the Initial Baseline Project Schedule for approval within 42 calendar days after notice to proceed is issued. During the 42 days of developing the Initial Baseline Project Schedule, the Contractor, Contractor's scheduler, and the Government conduct a one-hour meeting once a week to adhere to the project Contract, specification, and drawings. Include all activity coding and cost loading. The entire project schedule must be submitted fully completed in detail.

The schedule details must demonstrate a reasonable and realistic sequence of activities representing all work through the entire Contract performance period. Onsite work, not included in the Preliminary Project Schedule, will not start, and no payment will be made for such workuntil the Government Approves a fully detailed Initial Baseline Project Schedule.

3.4.3 Periodic Schedule Updates

Update the Project Schedule every week on the last workday of each week.

Provide a draft Periodic Schedule Update for review weekly and at the scheduled update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess the Contractor's progress.

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

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

Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial baseline 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 .xer and sdef format of the

Section 01 32 01.00 10 Page 16 Aug 13, 2021 - 11:37 AM scheduling software. 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 and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. Four copies of the schedules showing codes, values, categories, numbers, and other items, etc., as required. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for 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. List and provide all activity details and description of Negative Total

Float: Causes and effects.

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

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

f. 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 changes, and actual start and finish date changes.

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

3.5.3 Schedule Reports

The format, layout(s), 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, Actual Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Free Float, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. Provide five set(s) of hardcopy reports. The following lists typical reports that must be delivered:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

Section 01 32 01.00 10 Page 17 Aug 13, 2021 - 11:37 AM

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 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, Contract required interim completion dates, and Contract completion dates.

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 / Work Breakdown Structure (WBS)

Section 01 32 01.00 10 Page 18 Aug 13, 2021 - 11:37 AM

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. Activities listed under a WBS will be limited to ten.

3.5.4.4.1 Work Breakdown Structure (WBS)

Group all activities and milestones within appropriate detail WBS categories, including the following and additional WBS categories are to be added as required:

a. Project Milestones:

1. Management Milestones

2. Project Administrative Meetings

3. Permits

b. Pre-Construction Phase:

1. Submittals and Reviews

2. Procurement

3. Mobilization

c. Construction Phase: Create multiple sub-sections in accordance with project-specific categories of work, including in WBS descending order as follows:

1. General Area

(a) Type of Work Item

2. Location

d. Commissioning & Testing:

1. Specific area/locations of commissioning

2. Commissioning System

3. Final Testing

4. Training

e. Project Closeout: Include activity items such as Punchlist, Demobilization, and As-built Drawings.

f. Modifications: Create a sub-category of Conformed and Non-Conformed under Modification WBS. Create multiple sub-sections as the project progresses identified by issue, and Fragnet placed in Conformed for modifications issued prior data date, or non-Conformed for issues not modified to Contract prior data date.

Section 01 32 01.00 10 Page 19 Aug 13, 2021 - 11:37 AM

g. Add a WBS Removed Activities: Place all removed activities remaining within the logic sequence and changing to Finish Milestone. Actualize finish date to date activity removed from the schedule and provide reason(s) for removal explained in Activity Notebook.

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

Throughout the entire project duration, the Contractor must submit a complete status Monthly Project Schedule on the First of each month.

Conduct periodic schedule update meetings to address Government analysis, questions, comments, issues, 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 that 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 up to 8 hours per day, with adjacent days as-required. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of five workdays in advance of the meeting. The Contractor's Project Manager, Superintendents/Foreman, Quality Control Manager and Scheduler must attend the meeting in-person with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend in-person and remain in the meeting, for its entirety as required, addressing subcontract project schedule, activities and work. Authorized representatives of the Government will be in attendance.

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 not later than three workdays after the periodic schedule update meeting.

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

Section 01 32 01.00 10 Page 20 Aug 13, 2021 - 11:37 AM status of weekly activities of the project as compared to the as planned progress and to review planned activities for the previous weeks, current week, and 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, project schedule, and Submittals.

Require physical attendees: Government, Contractor Project Manager, QC Manager, and Superintendents/Foreman. Additional required attendees, as directed by the Government.

The Contractor must include the following:

a. Use the current Approved Baseline, Last Approved, and Current Status

Schedules.

b. Forward an electronic file (PDF) of updated activity statuses on previous, current, and upcoming Two-Weeks Look Ahead Schedule to the Contracting Officer no later than 11 a.m. each Monday.

c. P6 Layout must include (in order of) Activity ID, Activity Name, Activity Type, Physical % Complete, Calendar, Original Duration, BL Project Start, Start, BL Project Finish, Finish, Free Float, Total Float, and Gantt chart. The Layout is at the discretion of the Government. As required, the Government will direct the Contractor to provide layout editing and resubmissions. Use the Project Baseline Schedule for "BL" column data and Gantt chart bar display.

d. Include upcoming outages, closures, preparatory meetings, and initial meetings, testing, and inspections.

e. Identify longest path activities on the Two-Week Look Ahead Schedule.

Include a key or legend that distinguishes longest path activities.

Include all Longest Path activity start/finish dates exceeded and occurring during this period.

f. The detailed work plans are derived from but maintained separately from the Project on an electronic spreadsheet program and printed on 11 by 17-inch landscape sheet(s) or as directed by the Government.

g. Activities must not exceed five working days in duration unless authorized by the Government, sized and have sufficient detail to assign crews, tools, and equipment required to complete the work.

3.8 WEEKLY ACTIVITY STATUS AND DATA

Project activities are to be status (d) on a weekly basis at end of the last workday of each week. On each Monday, by 11 a.m., extract the following data from P6 and forward to the Government field team (P6 layout with headers/columns in order of left to right): Activity ID, Activity Name, Activity Type, Physical Percent Complete, Calendar, Original Duration, Remaining Duration, Start, Finish, Free Float and Total Float.

3.9 REQUESTS FOR TIME EXTENSIONS

Section 01 32 01.00 10 Page 21 Aug 13, 2021 - 11:37 AM

Provide a justification of delay to the Contracting Officer in accordance with the Contract provisions and clauses for approval within 10 calendar days of a delay or impact occurring. Also prepare a time impact analysis for each Government request For Proposal (RFP) to justify time extensions.

3.9.1 Justification of Delay

Within 10 calendar days of a delay and or impact occurring 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 concurrences of delay. A schedule time extension fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer. Additional project schedule fragnet/activities becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer. Failure to provide Justification of delay/impact will deem the delay and or impact invalid and will be dismissed/omitted by the Government.

3.9.2 Time Impact Analysis (Prospective Analysis)

Within 10 calendar days of a delay/impact occurring, 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.