% complete at Parent WBS showing 11% even project completed more than 100%

Johan,

You asked, "What are the key influences for the forecast finish to reflect an October 2019 date whilst I know for a fact that the activity will be completed before end of June?"

Possible influences on the forecast delay of remaining work for task 2447 are:

1. This task has started out of sequence (i.e. its predecessor was not complete) AND "Split in-progress tasks" Schedule option is checked, AND the incomplete predecessor is delayed until October.  As for all out-of-sequence progress, fix the relationship that you know to be wrong.

2. MFO or FNET constraint in October is applied to the task, OR ALAP constraint is applied to the task.

3. The Resume date of the task has been delayed by one of the following:

     - manual entry or other incorrect update procedure;

     - resource leveling.

4. Resource assignments have been delayed or otherwise modified by user entry or by the resource leveler.

Good luck, tom

Hi,

I have a query with regards to an issue I have experienced in Microsoft Projects.

Below extract contains an activity:   “ Install P02-581-CNV-001 Crusher Discharge Chutes”, Activity ID 2447.  This activity has an Actual Start of 1 April 2019 and progressed to 30%.  What are the key influences for the forecast finish to reflect an October 2019 date whilst I know for a fact that the activity will be completed before end of June?  The schedule is resourced and therefore progress recorded in % Work Complete.

 

ID

Task Name

Remaining Duration

% Work Complete

Actual Start

Actual Finish

Start

Finish

2434

P02-581-CNV-001 Installation SMPP

79.1 days

61%

15 Oct '18

NA

15 Oct '18

10 Jan '20

2435

   P02-581-CNV-001 Steelwork Erection (89.65t)

21.63 days

85%

15 Oct '18

NA

15 Oct '18

26 Aug '19

2436

      Erect P02-581-CNV-001 Grid 1 to 5 Structural Steel

2.1 days

85%

15 Oct '18

NA

15 Oct '18

05 Jun '19

2437

      Erect P02-581-CNV-001 Grid 6 to 9 Structural Steel

2.1 days

85%

26 Oct '18

NA

26 Oct '18

20 Jun '19

2438

      Erect P02-581-CNV-001 Grid 10 to 14 Structural Steel

2.1 days

85%

29 Oct '18

NA

29 Oct '18

29 Jul '19

2439

      Erect P02-581-CNV-001 Grid 15 to 18 Structural Steel

2.1 days

85%

14 Nov '18

NA

14 Nov '18

26 Aug '19

2440

   P02-581-CNV-001 Handrailing and Grating (232m x 273m²)

16.82 days

85%

15 Jan '19

NA

15 Jan '19

03 Sep '19

2441

      Erect P02-581-CNV-001 Grid 1 to 10 Handrailing & Grating

1.5 days

85%

15 Jan '19

NA

15 Jan '19

10 Jul '19

2442

      Erect P02-581-CNV-001 Grid 10 to 18 Handrailing & Grating

1.5 days

85%

30 Jan '19

NA

30 Jan '19

29 Jul '19

2443

      Erect P02-581-CNV-001 Grid 17 to 21 Handrailing & Grating

1.5 days

85%

30 Jan '19

NA

30 Jan '19

14 Aug '19

2444

      Erect P02-581-CNV-001 Grid 21 to 26 Handrailing & Grating

1.5 days

85%

28 Jan '19

NA

28 Jan '19

03 Sep '19

2445

   P02-581-CNV-001 Platework Installation (2.6t)

39.9 days

63%

01 Apr '19

NA

01 Apr '19

29 Oct '19

2446

      Install P02-581-CNV-001 Head Chute

0 days

100%

13 May '19

20 May '19

13 May '19

20 May '19

2447

      Install P02-581-CNV-001 Crusher Discharge Chutes

1.47 days

30%

01 Apr '19

NA

01 Apr '19

23 Oct '19

2448

   P02-581-CNV-001 Mechanical Installation

96.22 days

18%

22 Apr '19

NA

22 Apr '19

28 Nov '19

2449

      Install P02-581-CNV-001 Drive, Gearbox and Pulleys

4 days

0%

NA

NA

29 Oct '19

05 Nov '19

2450

      Install P02-581-CNV-001 Idlers, Free Issue Material

2.4 days

20%

22 Apr '19

NA

22 Apr '19

18 Nov '19

2451

      Configure P02-581-CNV-001 Take Up

0.2 days

90%

22 Apr '19

NA

22 Apr '19

21 Nov '19

2452

      Install P02-581-CNV-001 Belt & Splice

4 days

0%

NA

NA

21 Nov '19

28 Nov '19

 

Thanks,

Johan

Rushikesh,

1. In MSP, with some exceptions concerning milestones, the %Complete for a summary task is computed as the summation of the subtask Actual Durations divided by the summation of the subtask Durations.  Baseline Duration is irrelevant.
2. The 11% Complete value for the project implies that the current schedule (including Durations of the completed subtasks) is substantially different from the Baseline.  Had the first three subtasks been completed exactly as planned (i.e. their Actual Durations matched their Baseline Durations) with no other schedule changes, then the project %Complete would be about 26%.  Absent other schedule changes, the 11% value is consistent with the Actual Durations for the completed works being only about 37% of the Baseline Durations.
3. This example demonstrates that %Complete in MSP – a Duration-only metric – is not at all useful for progress valuation in cost-loaded schedules.  MSP provides separate Earned Value functionality for that purpose.

Good luck, tom