Weird Fixed Duration Calculation!

[Simon]

Since Project sometimes seems to have a mind of its own, I would be
grateful if anyone can shed some light on exactly what it is doing in
the following fixed-duration task creation scenario. It seems to
happen on all standalone versions of MSP from 98 upwards and, in all
cases, the software is 'as installed'.

On a new project, create a single Fixed-Duration, non-effort-driven
task with a duration of 32hr and a PSD of 1/8/05. The task is
automatically given a PFD of 4/8/05 which, seems correct. Then use
split to show the 'Resources & Predecessors' form and add a single
resource CFITT with Units=2 and Work =64hr. Pressing OK accepts this
information unchanged (as would expected, from the standard scheduling
equation).

Now create a new task but, instead of initially creating it on the
task sheet, create it via the 'Resources & Predecessors' form. Enter
Task name, Duration (32hr), PSD (1/8/05), Task type (Fixed-Duration),
Resource name (CFITT) Units (2), Work (64hr) and press OK. I would
have expected this to behave in the same way as the first task.
However, although the same PFD (4/8/05) is generated and the Duration
stays the same, Units become 8 and Work becomes 256hr! Although this
still equates to a Duration of 32 hr, why on earth has it ramped the
figures up from 2 and 64hr, respectively?

All enlightenment gratefully received since this has my Project-using
colleagues and myself more than somewhat baffled.

 

[Jan De Messemaeker]

Hi,

This must be a bug. There is no reason.
It probably was never discovered as probably nobody creates tasks in the
Task Form.
HTH

 

[Steve House [MVP]]

As Jan said, probably a bug. But if you leave out manually entering the
duration, and just put in the assignment units and the work required it will
calculate duration correctly.

 

[Simon]

Guys
Thanks for the input; it's a relief to know that we aren't missing
something! We're currently integrating MSP and a work management
system, and the whole data input situation seems a minefield. As seen
from my original post, not only can you get different 'task placement'
via manually inputting the same data in different ways but, if you go
for 'automation loads', you can get even more variations on how the
same data set is 'placed'.

As Jan says, generally, nobody manually creates tasks via the
Resources form but, based on our work to-date, when automatically
loading multiple resource tasks via coding, the Resource form appears
to be the only method which gives stable, reproducible results which
conform with project management expectations! Oh well, all part of
life's rich tapestry (or something)

Simon

 

[Jan De Messemaeker]

Hi,

What do you mean by "automatically"??
When entering data in Project, you don't use any form or view, you directly
use Project's objects such a tasks, assignments, resources, etc.
HTH