RD = 0, but % Complete is not 100. How to resolve?

I totally agree it makes no difference using hours or days. In a recent shutdown project, I had similar problems. Being told we’ve virtually finished this activity; ie 90-99% complete but the minimum unit is 1 hour. On a 4 hour activity are you really 99% complete? It’s safer to say you need the one hour remaining and let the system calculate you are only 75% complete.



What do you do when your baseline activity has 4 hours against it and you find out that this is 50% complete and you ask how long this will take to finish and they say about 2 hours but we can’t finish it off until another 4 hour task is complete? Obviously this activity has been mis-planned but I would correct this situation by making it 0% complete, 6 hours remaining and a FF with -2 hour lag with the other activity! Any comments?

You can probably deselect ’Link remaining duration and shedule percent complete’ option-and try following global change :



PCT GT 0

and PCT LT 100



then &T EQ OD * PCT

RD EQ &T / 100



Before this you can identify and those activities which dont follow this rule and exclude from this globe change. or later manually change remaining duration of those few activities which is not proportional to % complete.



for which remaining duration is between 0 and 1 day and showing 0 days when percent complete not 100%



if PCT NE 100

and RD EQ 0



then RD EQ 1





Taqi Hasan

have you reschedule it after update?

Gents



There is a principle problem here -



An activity cannot be 90% and RD is 0. So it seem that either you updated % or RD incorrectly.



Check whether your activity is Resource Driven. That mean if you do not have any remaining unit to finish the activity - of course your activity should be 100% complete and RD is 0. On the other hand if the activity is 90% complete, it should have some remaining resource to finish the job. that mean at least RD = 1 Day.



This should not be affected by whether you are using hr or day as planning unit.



Auto-cost rule is like identify whether you want the computer calculate base on some of constant you entered to work out other variable. Like remaining duration, units, costing, % complete. All of these can be a variable/constant and can be unrelated and progressed individually.



HTH



Alex

If you don’t want to convert to hours then:



Disconnect RD and PCT in the autocost rules.



Record percent complete as normal



Recalculate RD using Global Change, this will let you leave the RD as 1 for durations less than a day.....

Granted, using hours does provide greater granularity and iron out a lot of these issues; but for some users in certain sectors, days work just fine, as long as you understand why the software is doing what it is.

Are there STILL people out there using P3 with a planning unit of "days" rather than "hours" - this is just one of many problems if you use "days". Convert to "hours" using the "Tools:project utilities:Copy" dialog!

Alexey,



As you noted, the crux of the issue is the remaining duration of less than 12 hours (or, more accurately, half a day).



This means that any FS successor wil be able to start, in theory, in the morning of the following day.



In your case this means that the successor to your activity will be able to start on the morning of the data date.



In order to reflect this, the predecessor (at 90%) will be shown as finishing at the end of the previous day.



not ideal though, is it?