Re: Resource Assignment vs Work Input Sequence

Hi,

Just for the sake of precision, quote:
levelling will delay tasks before changing assignment
units.

Levelling DOES NOT, never ever, change assignment units. It only delays
assignments.
Hope this helps,

--
Jan De Messemaeker, Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
For FAQs: http://www.mvps.org/project/faqs.htm
"St Dilbert" <pgaitzsch@xxxxxxxxxxxx> schreef in bericht
news:1154420359.162867.69590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ok - my mistake. In first trying to reproduce I always "assigned at
75%" instead of "assigning somebody with max 75% availability".

Sorry to report that now I can see the same behavior you do and I
haven't found a combination of options that changes it.

So apparently Project first spreads an assignment over a working day
calculating units necessary and only starts changing duration when
assigning at max units can't finish the work in one day. I tried
playing with the leveling options ("minute by minute" instead of "day
to day"; Word can change individual assignments and so on) but to no
avail.

This is a new discovery for me and I sifted through some of my older
plans -> apparently this has been happening to me all the time
unnecessarily stretching some of my plans out for a few fractions of
days.

This went unnoticed thus far because I rarely have assignments with
less than one day and I don't even try to optimize resource usage
within a day - in systems integration I'm happy to see the weekly
workload close enough to our contracted 38 hours. But I imagine in a
more precise environment like power plant maintenance this "feature" of
project would wreck my nerves. Right now I can't see any value in this,
especially since levelling will delay tasks before changing assignment
units.

hmmm.. so my projects that finished early were actually scheduled lazy
;-) ?


peter.weinstein wrote:
St Dilbert, thank you for the reply. I am running Project Prof 2003 SP2
as
well. Here are my Calendar Options

Week starts on: Sunday
Fiscal year start in: July
Default start time: 9:00 AM
Default end time: 5:00 PM
Hours per day: 7
Hours per week: 35
Days per month: 20

Here are my Schedule Options

Show scheduling messages: Checked
Show assignment units as a: Percentage
New tasks: Start On Project Start Date
Duration is entered in: Hours
Work is entered in: Hours
Default task type: Fixed Work
New tasks are effort driven: Disabled and Checked
Autolink inserted or moved tasks: Checked
Split in-progress tasks: Checked
Tasks will always honor their constraint dates: Checked
Show that tasks have estimated durations: Checked
New tasks have estimated duration: Checked

Here are my Calculation Options

Calculation Mode: Automatic
Calculate: All open projects
Updating task status updates resoure status: Checked
Move end of completed parts after status date back to status date:
Unchecked
Move start of remaining parts before status date forward to status date:
Unchecked
Edits to total task % complete will be spread to the status date:
Unchecked
Inserted projects are calculated like summary tasks: Checked
Actual costs are alsways calculated by Microsoft Office Project: Checked
Default fixed cost accrual: Prorated
Calculate multiple critical paths: Unchecked
Tasks are critical if slack is less than or equal to: 0 days

Also, my Standard (Project Calendar) weekday working time is Nondefault
working time with the hours

From: 9:00 AM
To: 12:00 PM
From 1:00 PM
To: 5:00 PM

Do the Options above match your own?



.