Hi Steve,
That's it. I don't even think the end date is crucial (these things
generally serve the purpose of taking short-term decisions) so she
could
just enter a task with a "reasonable" duration instead of a hammock task,
and it would nicely "Gantt Chart Style" show availability odf the
resource.
Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620
"Steve House [Project MVP]" <
[email protected]>
schreef in bericht Jan, are you sure you mean that? It sounds like she's asking leveling to
create assignments - specifically to see the unused availablility of all
the
resources from day to day and have any unassigned percentage short of
their
maximum allocation to automatically be assigned to a MISC task
(whether
they're booked 100% or something less doesn't matter). That would
require
Project's leveling to actually create the assignments to MISC, which
we
know
it doesn't do.
I figured out a workaround using leveling but it sure seems risky to
me
to
actually use it. Create the project plan with all the resource
assignments
and level it. Add a hammock task for MISC from project start to project
end. Make it non-effort driven, priority zero, and assign all the
resources
to it. Level again using priority, standard order, within available
slack
turned off, can adjust individual assignments turned on, can create
splits
turned on. After leveling the hammock task will extend beyond the
real
project end so we need then to reset the hammock link for the end date to
cut away the excess time on the MISC task.
I don't like that solution because the MISC task is not producing a
quantifiable, defineable, specific deliverable that is a required
component
of the overall Project's final deliverable as such. It's really just
a
vague catch-all task that captures people's non-project related
activities.
As such it is completely outside of the project universe, has no
effect
on
the progress towards project completion, and shouldn't even be a
factor
in
the schedule except in so far its demands reduce the resource's
availability
for project work, something accounted for when setting the resource's
maximum availability in the first place. Further, the strategy requested
says it's a lower priority than project work to begin with, freely
interuptable whenever anything else in the project is going on, so
IMHO
it
should just be completely ignored by the PM, letting the resources
themselves figure out how best to work around the project's demands to
get
their other stuff done. If I have an employee who arrives in the office
at
9am and I'm planning what I need them to get done that day in the office,
I
don't also try to plan for them when they need to leave home in order to
get
to work on-time and what they should bring for lunch.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
"Jan De Messemaeker" <jandemes at prom hyphen ade dot be> wrote in
message
Hi Steve and all,
Just to clarify the point made in my previous note, this is a copy from
a
part of a previous note from Ellebelle:
-----
It automatically defaults back to this
'other/miscellaneious" when they are NOT scheduled on any other tasks.
-----
That is not filling up a gap from 50% to 100%, it is something leveling
can
do.
Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620
"Steve House [Project MVP]"
<
[email protected]>
schreef in bericht Leveling does not make assignments or modify the resource's
assignments
to
a
task in any way. All it does is slip a resource's work onb the
task
later
in the schedule in the event the resource is overallocated at the time
when
the task is originally scheduled to take place. I have Joe
assigned
to
task
8 on Mon for 8 hours. He's also assigned to task B, also on Mon and
also
for
8 hours. He's free for the rest of the week. He only works an 8 hour
day
and so can't do a total of 16 hours work all on Monday as our schedule
calls
for. All resource leveling will do is push one of those tasks to
Tuesday.
Ir won't take him off the task and put someone one, it won't reduce
him
to
50% on both tasks, it does nothing at all except move the lower
prioroty
task to Tuesday. And considering the oppoisite situation. I have
Mary
assigned to 2-day Task X on Monday and Tuesday at 50%, 8 hours
work,
16
hours duration. She's not scheduled for anything else those days and
has
a
max avail in her resource information of 100%. Leveling does nothing
to
her asignment. Project will NOT see she's only used 50% on Monday and
free
the other 50% and will NOT respond by increasing her to 100% and
finishing
the task sooner. It assumes we had our reasons for assigning her like
we
did that is knows nothing about and it doesn't try to second guess us
and
change it.
You example would require it to understand the nature of the work and
to
modify assignments, neither of which it can do. It would require
it
to
see
that they're only used 50% on Task X that you have assigned and
thus
should
put them on task MISC for the other 50%. But these task names are
just
character strings to Project and it doesn't know that MISC is a
catch-all.
As far as it knows, it could be just as technically sophisticated and
require as many special skills as helium arc welding and it has no way
of
knowing whether your resources even have the skills necessary to DO
MISC.
So it leaves the decision to put them on MISC or not strictly up to
you
and
keeps its hands off.
There's simply no way to automate management decision making such
as
resource assignments and resource loading and decision making is what
project managment is all about. MS Project is just a calculation tool
to
help decision makers predict the outcomes of the various options they
might
select but it won't make decisions for you.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
if i create a task called 'other' with prority zero (lower than all
other
tasks), could I use leveling on just that individual task?
:
the task is 'other/miscellaneious" they will do this when i have
not
schedule
them to do anything else. It automatically defaults back to this
'other/miscellaneious" when they are NOT scheduled on any other
tasks.
is it possible?
:
How can it be a task? A task by definition is a block of
physical
work
performed by a resource or resource team. The amount of time
they
are
NOT
working is the remaining allocation. If you had a task that
is
assigned to
both Fred and Ethyl, Fred used 75% and Ethyl 50%, what single
remaining
availabilty number is associated with that task?
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
message
I would like to view it in the gant view as a task.
:
The REsource Usage view has an option to display a row of
remaining
allocation, that is the difference between what they are
allocated
and
what
their maximum allocation is.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
message
Hello,
Is there a tool in MSProject that shows you when a resource
in
NOT
allocated to a task. Ideally this would be displayed as a
separate
task
with
splits.
Thanks