36C24619B0037-005.pdf

658-18-109 Asbestos Abatement Salem VA Medical Center Final Design – For Construction March 2019

01 32 16.13 - 1

SECTION 01 32 16.13

NETWORK ANALYSIS SCHEDULES - MAJOR PROJECTS

PART 1- GENERAL:

1.1 DESCRIPTION:

A. The Contractor shall develop a fully Resource loaded (cost and manpower) Network Analysis System (NAS) plan and computer generated schedule demonstrating fulfillment of the entire contract requirements, shall keep the plan and computer generated schedule up-to-date in accordance with the requirements of this section and shall utilize the plan for scheduling, coordinating, mitigating and monitoring work under this contract (including all activities of subcontractors, equipment vendors and suppliers). The Contractor’s initial NAS Diagram submission will be the basis for their initial project schedule and will be designated as a Day 1 submission. After review and approval by

VA, this schedule will be designated as the approved Baseline Schedule.

B. Conventional Critical Path Method (CPM) Precedence Diagramming Method

(PDM) technique shall be utilized to satisfy both time and cost applications. All schedule data and reports required under this specification section shall be based upon total float, not relative or free float schedules. The approved baseline NAS diagram and the schedule becomes the official project schedule of record governing schedule management, oversight and actions on the corresponding contract.

1.2 CONTRACTOR'S REPRESENTATIVE:

A. The Contractor shall designate a representative on the site who will be responsible for the preparation, timeliness, quality and the accuracy of the network diagram, review and report progress of the project with and to the Contracting Officer's representative.

B. The Contractor's representative shall have direct project control and complete authority to act on behalf of the Contractor in fulfilling the requirements of this specification section and such authority shall not be interrupted throughout the duration of the project.

C. The Contractor’s representative shall have the option of developing the project schedule within their organization or to engage the services of an outside consultant. If an outside scheduling consultant is utilized, Section 1.3 of this specification will apply.

01 32 16.13 - 2

1.3 CONTRACTOR'S CONSULTANT:

A. The Contractor shall submit a qualification proposal to the COR, within

10 days of bid acceptance. The qualification proposal shall include:

1. The name and address of the proposed consultant and Company.

2. Sufficient information to show that the proposed consultant has the qualifications to meet the requirements specified in this specification section.

3. A list of prior construction projects, along with selected PDM network diagram samples on current projects which the proposed consultant has performed complete project scheduling services.

These network diagram samples must show complete project planning for a project of similar size and scope as covered under this contract.

B. The Contracting Officer has the right to approve or disapprove the proposed consultant and will notify the Contractor of the VA decision within seven calendar days from receipt of the qualification proposal.

In case of disapproval, the Contractor shall resubmit another consultant within 10 calendar days for renewed consideration. The

Contractor shall have their scheduling consultant approved prior to submitting any schedule for approval.

1.4 PRIOR TO BASELINE SCHEDULE ACCEPTANCE

A. At the time of the Pre-Construction Conference, prior to the issuance of the project Notice to Proceed, the Contractor and the Contractor’s

Scheduling Consultant shall arrange a separate meeting with the

Contracting Officer and/or his representative to discuss the requirements of this specification.

B. With exception of payment for bonds, approval of the baseline NAS schedule is a condition precedent to:

1. Processing of contractor’s pay request(s) for any construction activities/items of work.

2. Review of any schedule updates.

C. Government review comments on the contractor’s schedule shall not relieve the contractor from compliance with requirements of this specification section and the remaining contract documents.

PART 2 - SCHEDULE CRITERIA / DATA REQUIREMENTS:

2.1 COMPUTER PRODUCED SCHEDULE DEVELOPMENT CRITERIA

A. The computer produced schedule shall be prepared and maintained using

Primavera P6 software.

01 32 16.13 - 3

B. Work activity/event relationships shall be restricted to Finish-to-

Start (FS) and Start-to-Start (SS) only without lead or lag constraints. Note: Some exception may be allowed for lag in SS relationship, but must be approved by the VA’s contracting officer on case by case basis prior to inclusion in the schedule.

C. Activity/event date constraints, not required by the contract, will not be accepted unless submitted to and approved by the Contracting

Officer. The contractor shall make a separate written detailed request to the Contracting Officer identifying these date constraints and secure the Contracting Officer’s written approval before incorporating them into the network diagram. The Contracting Officer’s separate approval of the network diagram shall not excuse the contractor of this requirement.

D. Logic events (non-work) will be permitted where necessary to reflect proper logic among work events, but must have zero duration. The complete computer schedule shall reflect the Contractor's approach to pursuing the entire project.

E. Intermediate Phasing milestones contained in the contract documents shall be clearly shown in the schedule.

F. The Contractor’s Initial Schedule submission, prior to VA review and approval, in its original form shall reflect the original contract scope of work.

G. Early Project Completion or “Short Schedule” – VA will not approve any baseline schedule which shows completion date prior to the contract completion date. Also, there should not be any “filler or

“contingency” type of activities to fill the entire contract duration.

VA has no obligation to accelerate activities to support a proposed early contract completion. However, if the subsequent updates show that early handover is feasible due to “ahead of schedule” situation, VA may accept the facility earlier at no additional cost to the

Government.

H. The Baseline Schedule Critical Path of the project shall be limited to:

1. No more than 20% of the activities shall be on the critical and near-critical path(s). Critical path is defined as activities with zero (0) day total float. Near-Critical path(s) is defined as activities with one (1) to twenty (20) days of total float.

2. Multiple Critical paths will not be allowed.

I. The Contractor shall show activities/events for:

01 32 16.13 - 4

1. Contractor's time required for submittal of shop drawings, templates, fabrication, delivery and similar pre-construction work.

2. Contracting Officer's and Architect-Engineer's review and approval of shop drawings, equipment schedules samples, template, or similar items with time duration of no less than 20 workdays.

3. Shutdowns or Interruption of VA Medical Center utilities, delivery of Government furnished equipment (GFE), and rough-in drawings, project phasing and any other specification requirements.

4. VC/VV Equipment - All significant VC (VA furnished and Contractor installed) and VV (VA furnished and VA installed) equipment shall be clearly shown in the schedule. Any smaller VC and VV Equipment shall also be logically grouped together and shown in the schedule.

5. Test, balance and adjust various systems and pieces of equipment, maintenance and operation manuals, instructions and preventive maintenance tasks.

6. Commissioning (Cx)Activities – Based upon the project specific

Commissioning plan and project specification section 01 91 00, the contractor shall include in the NAS Diagram all the systems commissioning activities (see systems covered in Division 7, 8, 21, 22, 23, 26, 28, 31 and others as specified) such as start up, Pre-functional check list, Pre–test, individual component and system level Functional test, Operator’s training, O.& M. Manuals etc.(including any deficiency correction and re-testing). The majority of commissioning activities should be completed as part of the normal construction schedule and finalized prior to the construction contract completion date. To this end, it is imperative that the Commissioning Agent and the Contractor collaborate to integrate commissioning activities into the

Contractor’s overall construction schedule. All commissioning activities shall be cost loaded as required in the earlier paragraphs. The Commissioning Plan will identify critical commissioning activities and associated construction/start up tasks that must precede these activities to allow for successful execution of the commissioning activities. In order to coordinate these activities with the construction schedule, a Commissioning Duration

Schedule should be provided by the Commissioning Agent to the COR and the Contractor to provide a rational basis for integration of commissioning into the Day 1 NAS diagram and the construction

01 32 16.13 - 5 schedule. The Commissioning Duration Schedule should include the following information:

I. Description of Commissioning Activity II. Prerequisite Construction Tasks Required to Execute the Cx Activity III. Elapsed Time Duration of Each Activity IV. Documentation Associated with Each Task/Document

Responsibility

7. Once the duration schedule is delivered to the Contractor, the

Contractor will collaborate with the Commissioning Agent to integrate all commissioning activities into the fixed duration construction schedule in accordance with VA NAS requirements for scheduling the project. The Baseline Schedule, as approved by the VA at the beginning, may not have all necessary Cx details, but the contractor is required to subsequently update the commissioning activities as more detailed Commissioning Duration Schedule is being developed.

J. VA inspection and acceptance activity/event with a minimum duration of five work days at the end of each phase and immediately preceding any

VA move activity/event required by the contract phasing for that phase.

Schedule these activities/events so that only one phase is scheduled for completion within the same 30 consecutive calendar day period

(except for those phases immediately preceding the final acceptance).

Maintain this scheduling condition throughout the length of the contract unless waived by the Contracting Officer’s Representative in writing.

K. Each activity shall contain as a minimum, but not limited to, activity/event ID, activity/event description, duration, budget amount, early start date, early finish date, late start date, late finish date and total float.

1. Show not only the activities/events for actual construction work for each trade category of the project, but also trade relationships to indicate the movement of trades from one area, floor, or building, to another area, floor, or building, for at least five trades who are performing major work under this contract.

2. Break up the work into activities/events shall have:

a. Duration no longer than 20 work days each, except as to non-construction activities/events (i.e., procurement of materials, delivery of equipment, concrete and asphalt curing) and any other

01 32 16.13 - 6 activities/events for which the Contracting Officer may approve the showing of a longer duration.

b. The duration for VA approval of any required submittal, shop drawing, or other submittals shall not be less than 20 work days.

Refer to drawing CPM-1 for VA approval activities/events which will require minimum duration longer than 20 workdays. The construction time as determined by the CPM schedule from early start to late finish for any sub-phase, phase or the entire project shall not exceed the contract time(s) specified or shown.

c. An activity/event shall only reflect the work of one entity

(subcontract or craft).

d. The activity/event once began can continue unimpeded until the activity/event is complete.

3. Describe work activities/events clearly, so the work is readily identifiable with clear scope for assessment of completion.

Activities/events labeled "start," "continue," or "completion," are not specific and will not be allowed. Lead and lag time activities will not be acceptable (Refer to item 2.1 B above for some exceptions).

4. Uniquely number each activity/event ID with ALPHA-NUMERIC value in ascending order. The network diagram should be generally numbered in such a way to reflect trade discipline, phase or location of the work.

2.2 WORK ACTIVITY/EVENT COST AND TRADE RESOURCE DATA

A. Cost Loading - The Contractor shall cost load all work activities/events except procurement activities. The cost loading shall reflect the appropriate level of effort of the work activities/events.

The cumulative amount of all cost loaded work activities/events

(including alternates) shall equal the total contract price. Prorate overhead, profit and general conditions on all work activities/events for the entire project length. The contractor shall generate from this information cash flow curves indicating graphically the total percentage of work activity/event dollar value scheduled to be in place on early finish, late finish. These cash flow curves will be used by the Contracting Officer to assist him in determining approval or disapproval of the cost loading. In the event of disapproval, the

Contractor shall revise and resubmit in accordance with Article, THE

INITIAL DAY ONE SCHEDULE SUBMITTAL (Item 3.1B below). Negative work

01 32 16.13 - 7 activity/event cost data will not be acceptable, except on VA issued contract changes.

B. The sum of the cost loading for each activity shall equal the value of the item in the Contractors' bid.

E. Work activities/events for Contractor bond shall have a trade code and area code of BOND.

2.3 NETWORK DIAGRAM (NAS) DATA REQUIREMENTS:

A. The initial NAS diagram is the logical plan and forms the basis for contractor’s baseline schedule. Participation and input of key construction personnel from the general contractor and the major subcontractors is a mandatory requirement in the baseline schedule development. The initial NAS diagram in its original form shall reflect the original contract scope of work and contain no contract changes or delays which may have been incurred during the final NAS diagram and baseline schedule development period and shall reflect the entire contract duration as defined in the bid documents. Show on the NAS diagram the sequence and interdependence of work activities/events required for complete performance of all items of work. In preparing the NAS diagram, the Contractor shall:

1. Exercise sufficient care to produce a clear, legible and accurate network diagram, refer to the construction document (CD) drawing, CPM-1 (Sample CPM Network. Computer plotted network diagrams shall legibly display and plot all information required by the VA CPM activity/event legend, otherwise the computer plotted network diagram will not be accepted. If the computer plotted network diagram is not found acceptable by the contracting officer’s representative, then the network diagram will need to be hand drafted and meet legibility requirements. Provide a key plan on each network diagram sheet showing the project area associated with the work activities/events shown on that sheet.

2. Show the following on each work activity/event:

a. Activity/Event ID number.

b. Concise description of the work represented by the location and activity/event.

c. Activity coding – Provide activity coding (five alpha characters or less) for Trades (GEN, MECH, ELEC, CARP, PLAST, or other acceptable abbreviations), Area, Phasing etc. Provide a dictionary of all coding in the front page of the NAS Diagram.

01 32 16.13 - 8

d. Duration (in work days.)

e. Cost (in accordance with Article, ACTIVITY/EVENT COST DATA of this section and less than $9,999,999 per activity).

f. Manpower required (average number of workers per day). Load manpower for each and every activity with proper trade codes in the “resource” field of P6 for ease of generating individual

Trade and overall manpower profile required to plan and complete the project.

g. No open-ended activities with exception of Notice to Proceed and the Final Completion node.

B. To the extent that the network diagram or any revised network diagram shows anything not jointly agreed upon, it shall not be deemed to have been approved by the Contracting Officer. Failure to include any element of work required for the performance of this contract shall not excuse the Contractor from completing all work required within any applicable completion date of each phase regardless of the Contracting

Officer's approval of the network diagram.

C. Compact Disk Requirements and CPM Activity/Event Record Specifications:

Submit to the COR an electronic file(s) containing one file of the data required to produce a Primavera (P6), (PDM) produced schedule, reflecting all the activities/events of the complete project network diagram being submitted.

PART 3 - SUBMITTALS, DELIVERABLES, AND UPDATE PROCESS:

3.1 SUBMITTALS:

A. The independent CPM consultant Submittal: Within 10 calendar days after award of the contract, the Contractor shall submit to the Contracting

Officer for review and approval the qualifications of their proposed independent CPM consultant. The submittal information shall be in accordance with PART 1 GENERAL, ARTICLE 1.3 CONTRACTOR'S CONSULTANT of this Specification.

B. THE INITIAL SCHEDULE SUBMITTAL: Within 30 calendar days after receipt of Notice to Proceed, the Contractor shall submit the initial schedule submittal package for the Contracting Officer's review and approval.

This initial schedule submittal shall consist of:

1. Computerized Schedule;

a. An electronic file in a compressed Primavera (P6) computerized schedule, (PDM) format.

01 32 16.13 - 9

b. Three hard copies of a computer-produced activity/event ID schedule showing all requirements project duration; phase completion dates; and other data, including event manpower and cost. Each activity/event on the computer-produced schedule shall contain as a minimum, but not limited to, activity/event ID, description, duration, predecessor and successor relationships, trade code, area code, budget amount, early start date, early finish date, late start date, late finish date and total float.

The Contracting Officer’s separate approval of the network diagram shall not excuse the contractor of this requirement.

2. Supporting Data, include the following data:

a. The proposed number of working days per week.

b. The holidays to be observed during the life of the contract (by day, month, and year).

c. The planned number of shifts per day.

d. The number of hours per shift.

e. List the major construction equipment to be used on the site, describing how each piece relates to and will be used in support of the submitted network diagram work activities/events.

f. Provide a typed, doubled spaced description, at least one page in length, of the sequencing plan and contractor’s approach to constructing the project.

g. Failure of the Contractor to include this data will delay the review of the submittal until the Contracting Officer is in receipt of the missing data.

C. VA RESPONSE TO INITIAL SCHEDULE SUBMITTAL – BASELINE SCHEDULE:

Within 30 calendar days after receipt of the complete project NAS diagram and initial schedule, the Contracting Officer or his representative will do one or both of the following:

1. Notify the Contractor concerning his actions, opinions, and objections.

2. A meeting with the Contractor at or near the job site for joint review, correction or adjustment of the proposed plan will be scheduled if required. Within 14 calendar days after the joint review, the Contractor shall revise and shall submit three hard copies of the revised network diagram, three copies of the revised computer-produced activity/event ID schedule and a revised electronic P6 file as specified by the Contracting Officer. The

01 32 16.13 - 10 revised submission will be reviewed by the Contracting Officer and, if found to be as previously agreed upon, will be approved.

3. The contractor submitted NAS diagram, the corresponding computer-produced schedule(s) and the submitted supporting data, when approved, shall constitute the official Baseline Schedule until subsequently revised in accordance with the requirements of this section.

D. COMPUTER PRODUCED SCHEDULES SUBMITTALS:

1. The contractor shall submit to the COR, computer-produced time/cost schedules and reports generated from monthly project updates. This monthly computer service will include: electronic file copies of up to five different reports (inclusive of all pages), available within the user defined reports of Primavera (P6) to the contracting officer’s representatives; a hard copy listing of all project schedule changes, and associated data, made at the update; an electronic file of this data in Primavera (P6) format; and the resulting monthly updated schedule reports in a compressed electronic file in Primavera (P6), (PDM) format. These schedule reports must be submitted within 7 calendar days of monthly update meeting, along with the signed (by the contractor and VA) Look ahead report(with % complete progress) made at the previous update meeting; and substantively support the contractor’s monthly payment request. The SRE shall identify the five different report formats that the contractor shall provide based upon the monthly schedule updates.

2. The contractor is responsible for the correctness and timeliness of the computer-produced reports. The Contractor is also responsible for the accurate and timely submittal (within 7 calendar days as noted above) of the updated project schedule and all CPM data necessary to produce the computer reports and payment request that is specified.

E. VA RESPONSES TO COMPUTER PRODUCED SCHEDULE submittals

The VA may report errors in computer-produced reports to the

Contractor’s representative within ten calendar days from receipt of reports, indicating approval or disapproval. In case of disapproval, the Contractor will reprocess the computer-produced reports and associated compact disk(s), when requested by the Contracting Officer’s representative, to correct errors which affect the payment and schedule

01 32 16.13 - 11 for the project. In certain large and complex project, as determined by the Contracting Officer, this monthly reporting shall be formal submittal and approval process; meaning that the next month’s update shall not proceed without timely submittal and approval.

F. FIRST UPDATE SCHEDULE SUBMITTAL:

Within 30 calendar days of VA acceptance of the project baseline schedule, the Contractor shall submit the first update of the schedule.

This update shall contain any progress of the work the contractor wishes to receive payment for from contract notice to proceed. Any changes/delays shall be entered at the first update after the final network diagram has been approved. The Contractor should provide their requests for time and supporting time extension analysis for contract time as a result of contract changes/delays, after this update, and in accordance with Article, ADJUSTMENT OF CONTRACT COMPLETION. These changes/delays shall be entered at the first update after the final network diagram has been approved. The Contractor should provide their requests for time and supporting time extension analysis for contract time as a result of contract changes/delays, after this update, and in accordance with Article, ADJUSTMENT OF CONTRACT COMPLETION.

G. PERIODIC PROGRESS AND PAYMENT SUBMITTALS:

The Contractor is entitled to a periodic progress payment upon approval of the resource loaded project schedule.

1. The contractor shall submit the AIA application and certificate for payment documents G702 & G703 reflecting updated schedule activities and cost data in accordance with the provisions of the following

Article 3.2, PAYMENT AND PROGRESS REPORTING, as the basis upon which progress payments will be made pursuant to Article FAR 52.232 – 5

(PAYMENTS UNDER FIXED-PRICE CONSTRUCTION), and VAAR 852.236 -

83(PAYMENTS UNDER FIXED-PRICE CONSTRUCTION).

2. If the Contractor fails or refuses to furnish to the Contracting

Officer the information and the associated updated Primavera (P6), (PDM) schedule in electronic format, which, in the sole judgment of the Contracting Officer, is necessary for processing the monthly progress payment, the Contractor shall not be deemed to have provided an estimate and supporting schedule data upon which progress payment may be made.

01 32 16.13 - 12

3.2 PAYMENT AND PROGRESS REPORTING – SCHEDULE UPDATES

A. Schedule update meeting - Monthly job site schedule update meeting shall be held on dates mutually agreed to by the Contracting Officer

(or Contracting Officer's representative) and the Contractor.

Contractor and his CPM consultant will be required to attend all monthly update meetings. Presence of Subcontractors during update meeting is optional unless required by the Contracting Officer (or

Contracting Officer's representative). The Contractor shall update the project schedule and all other data required by this section shall be accurately filled in and completed draft (Pencil copy) prior to the monthly update meeting. The Contractor shall provide this information to the Contracting Officer or the VA representative in completed form three work days in advance of the update meeting. The contractor shall use only approved previous month’s schedule to report progress (% complete) in “pencil copy” and shall not change this in any shape or form. Logic or duration changes for future incomplete activities should be entered later and shown in the resulting reports. Job progress will be reviewed to verify:

1. Actual start and/or finish dates for updated/completed activities/events.

2. Remaining duration, required to complete each activity/event started, or scheduled to start, but not completed.

3. Logic, time and cost data for change orders (CO), and supplemental agreements (SA) that are to be incorporated into the network diagram and computer-produced schedule. Submit “Fragnets” for each CO and SA for VA approval. Changes in activity/event sequence and duration should be made pursuant to the provisions of following Article, ADJUSTMENT OF CONTRACT COMPLETION.

4. Percentage for completed and partially completed activities/events.

5. Logic and duration revisions required by this section of the specifications, particularly if the Day 1 logic / sequence have changed significantly, which could potentially alter or impact the critical path of the schedule. Highlight and request VA approval prior to making any logic, durations, manpower and cost loading changes.

6. Activity/event duration and percent complete shall be updated independently, meaning that the Remaining Durations (RD) shall be reviewed for all “in-progress” activities and entered manually based

01 32 16.13 - 13 on realistic remaining work content, and shall not be left to “auto-calculate” by the software.

7. Out of sequence progress – Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence progress) are not allowed except on a rare 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 updated monthly schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the contracting officer. Also, submit complete revised schedule when more than 5% of the remaining activities are out of sequence.

Calculate multiple float paths option is not allowed.

8. Logic changes – Specifically identify and discuss all logic changes pertaining to change orders (see section item 3.2.E below), contractor proposed changes in work plan or sequence, correction to schedule logic for out-of-sequence progress etc. that have been made pursuant to contract provisions. VA will only approve logic revisions in order to keep the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and accurately sequencing the work.

B. Schedule Narrative - The Contractor, in addition to the 5 schedule reports noted earlier, shall submit a narrative report as a part of his monthly update reporting prepared after the update meeting, in a form agreed upon by the Contractor and the Contracting Officer. The narrative report shall be prepared by the contractor’s authorized representatives (Project manager, Superintendent or other responsible official, and not by the CPM consultant); shall include, at a minimum, a description of major construction problem areas; current and anticipated delaying factors and their estimated impact on performance of other activities/events and completion dates; and an explanation of corrective action being taken or proposed. This narrative shall also include 1) any forward Logic Revisions; 2) any added or deleted activities; 3) Any cost loading or budget changes; 4) Any missed major milestones. This monthly schedule narrative should also briefly discuss the potential schedule risks / mitigation effort, as required by the item 3.1.G above. This report is in addition to the daily reports

01 32 16.13 - 14 pursuant to the provisions of Article, DAILY REPORT OF WORKERS AND

MATERIALS in the GENERAL CONDITIONS.

C. Cash Flow S-curve or Schedule Variance Control (SVC) Diagram – With each schedule submission, provide a SVC diagram showing Scheduled and

Actual(earned value) Project cost curve (both incremental and cumulative)based on both projected early and late activity finish dates. Also, revise the Cash Flow S-curve when the contract is modified, or as directed by the Contracting Officer.

D. After completion of the joint review and the Contracting Officer's approval of all entries, the contractor will generate an updated computer-produced calendar-dated schedule and submit to the contracting

Officer’s representative with reports in accordance with the Article, COMPUTER PRODUCED SCHEDULES, specified. These reports shall be submitted within 7 calendar days after the monthly update meeting to the SRE and the VA CPM Schedule analyst simultaneously via electronic media, as noted earlier.

E. Time Impact Analysis – Perform time impact analysis for each change order using the most recent approved monthly schedule update and approved “Fragnet” (Fragments of network or sub-network) logic and durations. The analysis shall only include original workday durations and schedule logic agreed upon by the contractor and the COR for the contract change(s), and shall be submitted as a part of the C.O.

proposal and before any physical C.O. work is performed. Fragnet logic shall include only relevant procurement and physical C.O. work activities. When there is a disagreement on logic and/or durations, the consultant shall use the schedule logic and/or durations provided and approved by the COR. The contractor must also distribute the total CO cost across activities included in the Fragnet. Note: Insertion of any

CO or SA activities into the CPM database with faulty logic ties like

NTP (predecessor) and Project complete (successor) and zero (0)duration will not be accepted. The proper “Fragnet” logic and durations must be used as approved by the COR and tied to the related physical work area of the schedule.

F. Revised NAS Diagram - After VA acceptance and approval of the final NAS diagram and the schedule, and after each monthly update, the contractor shall submit to the Contracting Officer electronic copies of a revised complete NAS diagram showing all completed and partially completed activities/ events, contract changes and logic changes made on the

01 32 16.13 - 15 intervening updates or at the first update on the final diagram. The

Contracting Officer may elect to have the contractor do this on a less frequent basis, but it shall be done when the Baseline schedule is revised, or when requested by the Contracting Officer.

G. Monthly schedule update meetings will be held on dates mutually agreed to by the COR and the Contractor. Contractor and their CPM consultant

(if applicable) shall attend all monthly schedule update meetings. The

Contractor shall accurately update the Project Schedule and all other data required and provide this information to the COR three work days in advance of the schedule update meeting. Job progress will be reviewed to verify:

1. Actual start and/or finish dates for updated/completed activities/events.

2. Remaining duration for each activity/event started, or scheduled to start, but not completed.

3. Logic, time and cost data for change orders, and supplemental agreements that are to be incorporated into the Project Schedule.

4. Changes in activity/event sequence and/or duration which have been made, pursuant to the provisions of following Article, ADJUSTMENT OF

CONTRACT COMPLETION.

5. Completion percentage for all completed and partially completed activities/events.

6. Logic and duration revisions required by this section of the specifications.

7. Activity/event duration and percent complete shall be updated independently.

H. Ownership of Project Float – Project float is the length of time between the contractor’s predicted completion milestone and the contract completion date milestone. Project Float available in the schedule, at any time, shall not be considered for the exclusive use of either the VA or the Contractor.

3.3 RESPONSIBILITY FOR COMPLETION / PROJECT DELAY

A. Whenever it becomes apparent from the current monthly progress review meeting or the monthly schedule update that phasing or contract completion dates will not be met, the Contractor shall execute some or all of the following remedial actions:

1. Increase construction manpower in such quantities and crafts as necessary to eliminate the backlog of work.

01 32 16.13 - 16

2. Increase the number of working hours per shift, shifts per working day, working days per week, the amount of construction equipment, or any combination of the foregoing to eliminate the backlog of work.

3. Reschedule the work in conformance with the specification requirements to recover all of the delay for which the contractor is responsible.

B. Prior to proceeding with any of the above actions, the Contractor shall notify and obtain approval from the Contracting Officer for the proposed schedule changes. If such actions are approved, the contractor shall incorporate this “Recovery schedule” with all the CPM revisions into the next update, at no additional cost to the Government.

3.4 CHANGES TO NETWORK DIAGRAM AND REVISED SCHEDULE:

A. Within 30 calendar days after VA acceptance and approval of any updated computer-produced schedule, the Contractor shall submit a revised network diagram and schedule, the associated compact disk(s), and a list of any activity/event changes including predecessors and successors for any of the following reasons:

1. Delay in completion of any activity/event or group of activities/events; that indicate an extension of the project completion by 20 working days or 10 percent of the remaining project duration, whichever is less. Such delays which may be involved with contract changes, strikes, unusual weather, and other delays will not relieve the Contractor from the requirements specified unless the conditions are shown on the CPM as the direct cause for delaying the project is beyond the acceptable limits.

2. Delays in submittals, or deliveries, or work stoppage are encountered which make rescheduling of the work necessary.

3. The schedule does not represent the actual prosecution and realistic progress of the project, or when more than 5% of the remaining activities are “out of sequence” as noted earlier (Ref.3.2.A.7).

4. When there is, or has been, a substantial revision to the activity/event costs of the network diagram regardless of the cause for these revisions.

B. CPM revisions made under this paragraph which affect the previously approved computer-produced schedules for Government furnished equipment, vacating of areas by the VA Medical Center, contract phase(s) and sub phase(s), utilities furnished by the Government to the

01 32 16.13 - 17

Contractor, or any other previously contracted item, must be furnished in writing to the Contracting Officer for approval.

C. Contracting Officer's approval for the revised NAS diagram and schedule and all relevant data is contingent upon compliance with all other paragraphs of this section and any other previous agreements by the

Contracting Officer or the VA representative.

D. The cost of revisions to the network diagram resulting from contract changes will be included in the proposal for changes in work as specified in Article, FAR 52.243 -4 (CHANGES), VAAR 852.236 – 88

(CHANGES – SUPPLEMENTS), and will be based on the complexity of the revision or contract change, man hours expended in analyzing the change, and the total cost of the change.

E. The cost of revisions to the network diagram not resulting from contract changes is the responsibility of the Contractor.

3.5 ADJUSTMENT OF CONTRACT COMPLETION DATE

A. The contract completion time will be adjusted only for causes specified in this contract. Request for an extension of the contract completion date by the Contractor shall be supported with a justification, CPM data and supporting evidence as the COR may deem necessary for determination as to whether the Contractor is entitled to an extension of time under the provisions of the contract. Submission of proof based on revised activity/event logic, durations (in work days) and costs is obligatory to any approvals. The schedule must clearly display that the

Contractor has used, in full, all the float time available for the work involved in this request. The Contracting Officer's determination as to the total number of days of contract extension will be based upon the current computer-produced calendar-dated schedule for the time period in question and all other relevant information.

B. Actual delays in activities/events which, according to the computer-produced calendar-dated schedule, do not affect the original or extended contract completion dates shown by the critical path in the network, will not be the basis for a change to the contract completion date. The Contracting Officer will within a reasonable time after receipt of such justification and supporting evidence, review the facts and advise the Contractor in writing of the Contracting Officer's decision. The burden of proof to request the time extension is the sole responsibility of the contractor, and the contractor is required to

01 32 16.13 - 18 revise the Time analysis or provide further documentation when requested by the Contracting Officer.

C. The Contractor shall submit each request for a change in the contract completion date to the Contracting Officer in accordance with the provisions specified under Article, FAR 52.243 -4 (CHANGES), VAAR

852.236 – 88 (CHANGES – SUPPLEMENTS). The Contractor shall include, as a part of each change order proposal, a sequence of activities showing all CPM logic revisions (Fragnets), duration (in work days) changes, and cost changes for work in question and its relationship to other activities on the approved network diagram (as specified above in item

3.2.E – Time Impact Analysis).

3.6 ADJUSTMENT OF CONTRACT COMPLETION DATE / TIME EXTENSION DUE TO WEATHER:

Weather Delays - All delays due to non-work activities/events such as

RFI’s, Weather, Strikes, and similar non-work activities/events shall be analyzed on a month by month basis. Any weather related delays claimed by the contractor must be “above and beyond” the “normal weather” pattern (10 year average) and shall be supported by the data shown in the National Oceanic and Atmospheric Administration (NOAA) for the region of the country where the project site is located. The weather delay analysis shall be submitted to the VA within 30 calendar days after the weather event has passed. VA considers Time extension due to the weather is “non-compensable” time only.

- - - E N D - - -