Leveling LOE Tasks

[paul]

I'd like to automate level of effort tasks (e.g., program management)
when the resource also contributes to normal tasks. The LOE task
should be interrupted when "real work" ;-) is performed by that
resource.

For instance, Task A, B, and C, linked in sequence (FS) and task B is
done by the manager. Task L, stretching across the whole project
(e.g., from the beginning of task A to the end of task C) is allocated
to the manager at a nominal rate of say 25%. Task L is a low priority
(e.g., 100).

If the duration of L is manually set (such that L and C finish
together), then the resource leveling will conveniently cut out a
block of time for the manager to perform task B. Wonderful except for
the manual adjustment of the duration when the finish of C changes.

I am familiar with hammock tasks and things look as expected when task
L has no resource (or some resource unrelated to A,B, or C). However
as soon as the manager resource is applied to L, the leveling goes
wacky on that task.

Am I asking too much to try to level a hammock task?

Paul

 

[vanita]

Hi Paul

After creating the LOE task as hammock task, you may take the option of
'leveling can create split in remaining task' and also you are taking the
benefit of priority. This should resolve your problem.

But split might be created in other tasks also. So, this would have to be
checked.

I hope it helps.
Vanita

 

[Gérard Ducouret]

Hello Paul,

For me, with 2007 version, it works fine:
I create a hammock (NB duration of task L, the hammock task, is not set but
calculated by Project)
I assigned the manager on a project task and set a high priority to that
task.
The leveling created an interruption on the LOE. I just has to recalculated
the project by [F9]

Gérard Ducouret

 

[paul]

Hello Paul,

For me, with 2007 version, it works fine:
I create a hammock (NB duration of task L, the hammock task, is not set but
calculated by Project)
I assigned the manager on a project task and set a high priority to that
task.
The leveling created an interruption on the LOE. I just has to recalculated
the project by [F9]

Gérard Ducouret

I'd like to automate level of effort tasks (e.g., program management)
when the resource also contributes to normal tasks.  The LOE task
should be interrupted when "real work" ;-) is performed by that
resource.

For instance, Task A, B, and C, linked in sequence (FS) and task B is
done by the manager.  Task L, stretching across the whole project
(e.g., from the beginning of task A to the end of task C) is allocated
to the manager at a nominal rate of say 25%.  Task L is a low priority
(e.g., 100).

If the duration of L is manually set (such that L and C finish
together), then the resource leveling will conveniently cut out a
block of time for the manager to perform task B.  Wonderful except for
the manual adjustment of the duration when the finish of C changes.

I am familiar with hammock tasks and things look as expected when task
L has no resource (or some resource unrelated to A,B, or C).  However
as soon as the manager resource is applied to L, the leveling goes
wacky on that task.

Am I asking too much to try to level a hammock task?

Paul

I just tried with MSP07. I entered this first (Task, duration, start,
finish, predecessor, resource):
A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Fri 3/13/09
I entered the task names, changed durations for A & C, linked, created
the hammock task L and then allocated mgr to B.
Leveling Options: Automatic, "Clear before leveling" checked, Standard
order, "Can adjust assignments" & "Can create splits" checked.

I then set the resource 'mgr' for L and get the following warning:
"You moved Task 4 of 'Project1' to start Fri Feb 29, '09. This is
before the project start date (Fri Feb 29, '09)."
Either "continue" or "cancel" leaves the tasks as follows:

A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Mon 3/16/09 mgr

Yes, there is is a gap in L, but note that the finish is incorrect.
Both recalculating and updating links issue the same warning and same
incorrect Finish date.

If I move A away from the Project Start and then add the resource to
L, no warning is issued, a gap appears in L, but the Start-L is one
day after Start-A and Finish-L is one day after Finish-C.

Any ideas?

Paul

 

[Gérard Ducouret]

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09. This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

Gérard Ducouret.

<[email protected]> a écrit dans le message de (e-mail address removed)...

Hello Paul,

For me, with 2007 version, it works fine:
I create a hammock (NB duration of task L, the hammock task, is not set
but
calculated by Project)
I assigned the manager on a project task and set a high priority to that
task.
The leveling created an interruption on the LOE. I just has to
recalculated
the project by [F9]

Gérard Ducouret

I'd like to automate level of effort tasks (e.g., program management)
when the resource also contributes to normal tasks. The LOE task
should be interrupted when "real work" ;-) is performed by that
resource.

For instance, Task A, B, and C, linked in sequence (FS) and task B is
done by the manager. Task L, stretching across the whole project
(e.g., from the beginning of task A to the end of task C) is allocated
to the manager at a nominal rate of say 25%. Task L is a low priority
(e.g., 100).

If the duration of L is manually set (such that L and C finish
together), then the resource leveling will conveniently cut out a
block of time for the manager to perform task B. Wonderful except for
the manual adjustment of the duration when the finish of C changes.

I am familiar with hammock tasks and things look as expected when task
L has no resource (or some resource unrelated to A,B, or C). However
as soon as the manager resource is applied to L, the leveling goes
wacky on that task.

Am I asking too much to try to level a hammock task?

Paul

I just tried with MSP07. I entered this first (Task, duration, start,
finish, predecessor, resource):
A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Fri 3/13/09
I entered the task names, changed durations for A & C, linked, created
the hammock task L and then allocated mgr to B.
Leveling Options: Automatic, "Clear before leveling" checked, Standard
order, "Can adjust assignments" & "Can create splits" checked.

I then set the resource 'mgr' for L and get the following warning:
"You moved Task 4 of 'Project1' to start Fri Feb 29, '09. This is
before the project start date (Fri Feb 29, '09)."
Either "continue" or "cancel" leaves the tasks as follows:

A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Mon 3/16/09 mgr

Yes, there is is a gap in L, but note that the finish is incorrect.
Both recalculating and updating links issue the same warning and same
incorrect Finish date.

If I move A away from the Project Start and then add the resource to
L, no warning is issued, a gap appears in L, but the Start-L is one
day after Start-A and Finish-L is one day after Finish-C.

Any ideas?

Paul

 

[paul]

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09.  This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task. I have resigned myself
to manually updating the duration of the LOE tasks. None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

 

[vanita]

Hi Paul

Just see if this option 'level only within available slack' option is
checked. If it is ticked, the start date may not go ahead of the project
start date.

I hope it helps.
Vanita

 

[Gérard Ducouret]

Paul,

Check that the Type of your LOE task (L) is not "Fixed Duration". Which
would be antinomic which the elastic hammock
Sometimes the calculation of the hammock duration is a little late. You have
to speed up this calculation by [F9]

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09. This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date
constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task. I have resigned myself
to manually updating the duration of the LOE tasks. None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

 

[glenATmvps.org]

Where did Friday Feb 28 09 come from? It's not a leap year.


Mike Glen
Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09. This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

Gérard Ducouret.

<[email protected]> a écrit dans le message de (e-mail address removed)...

Hello Paul,

For me, with 2007 version, it works fine:
I create a hammock (NB duration of task L, the hammock task, is not set
but
calculated by Project)
I assigned the manager on a project task and set a high priority to that
task.
The leveling created an interruption on the LOE. I just has to
recalculated
the project by [F9]

Gérard Ducouret

I'd like to automate level of effort tasks (e.g., program management)
when the resource also contributes to normal tasks. The LOE task
should be interrupted when "real work" ;-) is performed by that
resource.

For instance, Task A, B, and C, linked in sequence (FS) and task B is
done by the manager. Task L, stretching across the whole project
(e.g., from the beginning of task A to the end of task C) is allocated
to the manager at a nominal rate of say 25%. Task L is a low priority
(e.g., 100).

If the duration of L is manually set (such that L and C finish
together), then the resource leveling will conveniently cut out a
block of time for the manager to perform task B. Wonderful except for
the manual adjustment of the duration when the finish of C changes.

I am familiar with hammock tasks and things look as expected when task
L has no resource (or some resource unrelated to A,B, or C). However
as soon as the manager resource is applied to L, the leveling goes
wacky on that task.

Am I asking too much to try to level a hammock task?

Paul

I just tried with MSP07. I entered this first (Task, duration, start,
finish, predecessor, resource):
A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Fri 3/13/09
I entered the task names, changed durations for A & C, linked, created
the hammock task L and then allocated mgr to B.
Leveling Options: Automatic, "Clear before leveling" checked, Standard
order, "Can adjust assignments" & "Can create splits" checked.

I then set the resource 'mgr' for L and get the following warning:
"You moved Task 4 of 'Project1' to start Fri Feb 29, '09. This is
before the project start date (Fri Feb 29, '09)."
Either "continue" or "cancel" leaves the tasks as follows:

A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Mon 3/16/09 mgr

Yes, there is is a gap in L, but note that the finish is incorrect.
Both recalculating and updating links issue the same warning and same
incorrect Finish date.

If I move A away from the Project Start and then add the resource to
L, no warning is issued, a gap appears in L, but the Start-L is one
day after Start-A and Finish-L is one day after Finish-C.

Any ideas?

Paul

 

[Gérard Ducouret]

Hi Mike
(Fri Feb 29, '09)... It's not a leap year
good point! ;-)

Gérard

Where did Friday Feb 28 09 come from? It's not a leap year.


Mike Glen
Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09. This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date
constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

Gérard Ducouret.

<[email protected]> a écrit dans le message de (e-mail address removed)...

Hello Paul,

For me, with 2007 version, it works fine:
I create a hammock (NB duration of task L, the hammock task, is not set
but
calculated by Project)
I assigned the manager on a project task and set a high priority to that
task.
The leveling created an interruption on the LOE. I just has to
recalculated
the project by [F9]

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...

I'd like to automate level of effort tasks (e.g., program management)
when the resource also contributes to normal tasks. The LOE task
should be interrupted when "real work" ;-) is performed by that
resource.

For instance, Task A, B, and C, linked in sequence (FS) and task B is
done by the manager. Task L, stretching across the whole project
(e.g., from the beginning of task A to the end of task C) is allocated
to the manager at a nominal rate of say 25%. Task L is a low priority
(e.g., 100).

If the duration of L is manually set (such that L and C finish
together), then the resource leveling will conveniently cut out a
block of time for the manager to perform task B. Wonderful except for
the manual adjustment of the duration when the finish of C changes.

I am familiar with hammock tasks and things look as expected when task
L has no resource (or some resource unrelated to A,B, or C). However
as soon as the manager resource is applied to L, the leveling goes
wacky on that task.

Am I asking too much to try to level a hammock task?

Paul

I just tried with MSP07. I entered this first (Task, duration, start,
finish, predecessor, resource):
A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Fri 3/13/09
I entered the task names, changed durations for A & C, linked, created
the hammock task L and then allocated mgr to B.
Leveling Options: Automatic, "Clear before leveling" checked, Standard
order, "Can adjust assignments" & "Can create splits" checked.

I then set the resource 'mgr' for L and get the following warning:
"You moved Task 4 of 'Project1' to start Fri Feb 29, '09. This is
before the project start date (Fri Feb 29, '09)."
Either "continue" or "cancel" leaves the tasks as follows:

A 5 days Fri 2/27/09 Thu 3/5/09
B 1 day? Fri 3/6/09 Fri 3/6/09 1 mgr
C 5 days Mon 3/9/09 Fri 3/13/09 2
L 11 days? Fri 2/27/09 Mon 3/16/09 mgr

Yes, there is is a gap in L, but note that the finish is incorrect.
Both recalculating and updating links issue the same warning and same
incorrect Finish date.

If I move A away from the Project Start and then add the resource to
L, no warning is issued, a gap appears in L, but the Start-L is one
day after Start-A and Finish-L is one day after Finish-C.

Any ideas?

Paul

 

[Gérard Ducouret]

Paul,

If your project is not confidential, could you send it to my email address;
Just REMOVETHIS and THAT.

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...

Paul

The error message : "You moved Task 4 of 'Project1' to start Fri Feb 29,
'09. This is before the project start date (Fri Feb 29, '09)." means that
you probably entered dates constraints (higlighted by a gray label and a
blue or red dot in the Indicators column. Remove all these date
constraints
(Set them to As Soon As possible)
NB : never enter dates in Start and Finish columns.

I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task. I have resigned myself
to manually updating the duration of the LOE tasks. None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

 

[paul]

Paul,

If your project is not confidential, could you send it to my email address;
Just REMOVETHIS and THAT.

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...



I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task.  I have resigned myself
to manually updating the duration of the LOE tasks.  None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

There have been a number of suggestions regarding settings;
unfortunately, I had already tried them. Leveling Options: Automatic,
"Clear before leveling" checked, Standard
order, "Can adjust assignments" & "Can create splits" checked. "Level
within slack" NOT checked.

I will take up Gerard on his generous offer to examine the .mpp file.
We'll see what happens...

Paul

 

[Gérard Ducouret]

<[email protected]> a écrit dans le message de (e-mail address removed)...

Paul,

If your project is not confidential, could you send it to my email
address;
Just REMOVETHIS and THAT.

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...



I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task. I have resigned myself
to manually updating the duration of the LOE tasks. None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

<There have been a number of suggestions regarding settings;
<unfortunately, I had already tried them. Leveling Options: Automatic,
<"Clear before leveling" checked, Standard
<order, "Can adjust assignments" & "Can create splits" checked. "Level
<within slack" NOT checked.

<I will take up Gerard on his generous offer to examine the .mpp file.
<We'll see what happens...

Paul

Hi Paul,

Definitely, there are some problems with this feature in 2003 version, while
I tested it 2 years ago on real projects, without any problem.
In 2007 version, it works quite fine, even if the update of the display is
not "real time" : if you change the duration of one or several project
tasks, you have to Clear the previous leveling in the Resource Leveling
dialog, run again the Leveling, then press the [F9] key so that the LOE task
takes the good duration.
I just change some parameters:
- Leveling calculations: Manual
- Hour by hour basis

Hope this helps,



Gérard Ducouret
Paris - France

 

[paul]

<[email protected]> a écrit dans le message de (e-mail address removed)...

Paul,

If your project is not confidential, could you send it to my email
address;
Just REMOVETHIS and THAT.

Gérard Ducouret

<[email protected]> a écrit dans le message de (e-mail address removed)...

I do appreciate the thought; however the only entries in the date
columns were the links for the hammock task. I have resigned myself
to manually updating the duration of the LOE tasks. None of my tests
were successful at producing the gap in the hammock task L AND
maintaining the Start/Finish dates of L using either MSP 2003 or 2007.

Paul

<There have been a number of suggestions regarding settings;
<unfortunately, I had already tried them.  Leveling Options: Automatic,
<"Clear before leveling" checked, Standard
<order, "Can adjust assignments" & "Can create splits" checked. "Level
<within slack" NOT checked.

<I will take up Gerard on his generous offer to examine the .mpp file.
<We'll see what happens...

Paul

Hi Paul,

Definitely, there are some problems with this feature in 2003 version, while
I tested it 2 years ago on real projects, without any problem.
In 2007 version, it works quite fine, even if the update of the display is
not "real time" : if you change the duration of one or several project
tasks, you have to Clear the previous leveling in the Resource Leveling
dialog, run again the Leveling, then press the [F9] key so that the LOE task
takes the good duration.
I just change some parameters:
 - Leveling calculations: Manual
 - Hour by hour basis

Hope this helps,

Gérard Ducouret
Paris - France

Indeed, there is some critical timing between the leveling and
calculation. (All the below is leveling day-by-day). The MSP2007
behavior is also interesting when Leveling=Automatic and
Calculation=Manual: Pressing F9 once will fill-in the hammock task
(between the appropriate dates), with NO GAP. Pressing F9 again will
insert the gap (and keep the Start/Finish correct). Work also
fluctuates.

Thus behavior with MSP2007 is improved (MSP2003 won't even maintain
the links), but the inconsistency (randomness?) of whether I've
pressed F9 an odd or even number of times is asking for trouble.
Again, this is with Automatic Leveling and Manual Calculation.

It turns out that both MSP2003 and MSP2007 act fairly well with Manual
Leveling and Manual Calculation. (Under 2003, you must update links
with Edit|Links instead of Calculate.)
Perform the following: ClearLeveling, Calc, Level, Calc. I suggest a
macro to make your life easier.

Now that I'm in maintenance mode, I cannot afford to forget to
calculate, so I will stick with the Automatic Leveling and Automatic
Calculation combined with manual adjustment of LOE duration.

My thanks to everyone who took the time to look at this confusing
issue.

Paul