Allocation of maintenance tasks

J

jdonbavand

Has anyone got any ideas as to the best way to allocate on-going
maintenance tasks such that they are visible and consume a percentage
of a resource's time, but without being burdensome to maintain?

Any ideas would be appreciated.

Thanks

Janet
 
J

John

Has anyone got any ideas as to the best way to allocate on-going
maintenance tasks such that they are visible and consume a percentage
of a resource's time, but without being burdensome to maintain?

Any ideas would be appreciated.

Thanks

Janet

Janet,
You basically have what is known as a level of effort (LOE) activity.
There are several ways to handle LOE tasks. I'll give you a couple of
choices and maybe someone else will throw in their 2 cents.

One method is to set up a single task that spans the length of the
project, or however long the LOE activity spans. Assign the resource(s)
and enter the estimated work content. For example, let's say the project
spans 12 months and one resource is performing LOE at a level of 10% of
their time. The actual number of hours per standard working month varies
of course but the accepted average is approximately 160 hours per month.
At a rate of 10%, that amounts to 12 x 160 x 0.1 = 192 hours for the
year. Maintaining the LOE task is easy because credit is taken based on
the passage of time, not on how much effort may or may not be expended.
So if the project is statused once a month, each month you would enter,
n/12 in the % Complete field (where n is the month, n=1 for first month,
n=2 for second month, etc.).

However, an even easier way to set up the LOE task is by creating
separate individual LOE tasks for each status period. So for the same
example where the project is 12 months in duration and it is statused
each month, create 12 LOE tasks, one for each month. At the status date
simply set the % Complete for that month's LOE task at 100%.

Hope this helps.
John
Project MVP
 
J

jdonbavand

Thanks John,

I will have a go with one of those suggestions and see how it goes; it
seems very sensible.

Can you also suggest how to deal with tasks that finish early or move
up the schedule, so they still show but no longer consume resource and
push back work which can actually now commence?

Most of the literature assumes that tasks finish later than planned,
rather than earlier!

Thanks
 
J

jdonbavand

Thanks Jan,

I've also prioritised tasks to use with the resource leveller, which is
all very well until something happens like a task is cancelled, when it
seems to interleave lower priority tasks amongst higher level ones
where I would have expected them to be left until the end of the plan.
Also if a low priority task has been started and is, say, 30%
completed, the remaining uncompleted work seems to be treated as the
highest priority, even if the task is listed as low priority and there
are more important tasks.

What can I do to remedy this?

Many thanks for all help and advice.

Janet
 
J

Jan De Messemaeker

Hi,

If you re-level with the "priority, Standard" option, this interleaving
shouldn't occur.
Do you have the option "leveling can split tasks" on?
If the file isn't too large, I'm always willing to look at specific
idiosyncrasies if you send it to jandemesATprom-adeDOTbe.
 
J

John

Thanks John,

I will have a go with one of those suggestions and see how it goes; it
seems very sensible.

Can you also suggest how to deal with tasks that finish early or move
up the schedule, so they still show but no longer consume resource and
push back work which can actually now commence?

Most of the literature assumes that tasks finish later than planned,
rather than earlier!

Thanks

Janet

Janet,
You're welcome. It looks like Jan picked up the trail on your other
question so I'll let him run with that.

John
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top