LofE tasks are not considered critical because by choosing that type of task, you are saying that the said activity duration is dependent on the activites within the plan that it has relationships with.
If for example, you are putting a task in to show you have 1 PM who will be 100% utilised over the whole project, you can add the LofE, call it Project Management and link it SS to the earliest starting project activity and FF to the latest finishing project activity. Then you can assign the resource.
If there is a delay in the tasks between the earliest and latest task this will extend you overall project duration, as expected. As your Project Management task directly relates to the earliest and latest tasks it will extend in duration also.
If there is no delay and you are trying to show you are on track to meet the baseline finish, then you will have to input the progress against the normal tasks to make the overall duration of the current plan match the overall duration of the baseline plan. Once you have done this you will notice that the LofE task has calculated its own performance. i.e if you are half way through the overall duration of your plan and are on target to meet the baseline finish date, then your LofE will show 50% performance.
If you are using EVM, then your EV (BCWP) for PM costs would be 100% of the planned value(BCWS). Your SPI would be 1 for PM activities.
Member for
18 years 9 months
Member for18 years10 months
Submitted by Dieter Wambach on Wed, 2008-10-22 10:09
’A level of effort activity’s duration is dependent on its predecessor and/or successor activities.’
If you use this for PM/overhead type activities it will extend and contract in-line with the activities it is associated to.
A LofE automatically claims performance based on elapsed time, but the overall duration of the LofE can change in line with the dynamics of the schedule.
Ok - that does the trick although I believe that LoE activities arent considered on the critical path.
Updating Progress on other activities, regardless of duration type, pushes the finish date out if resources are assigned (although the resource finish dates do not move!). So I have to manually reduce the remaining duration down to pull it back to the baseline finish.
A level of effort activity’s duration is dependent on its predecessor and/or successor activities.
If you use this for PM/overhead type activities it will extend and contract in-line with the activities it is associated to.
A LofE automatically claims performance based on elapsed time, but the overall duration of the LofE can change in line with the dynamics of the schedule.
Im not sure if I understand your response: Are you saying that updating as scheduled progresses activities in accordance to the baseline schedule rather than the current?
Id looked at LoE activities before and have just had a try. Its converting the resource effort to actuals as planned, but is still pushing back the finish of the activity. Any ideas what Im doing wrong?
Activity is LoE, Fixed Duration and U/T, %complete Duration. Im using Update Progress with the new data date a week after the current one.
The specific example you gave, of accruing a resource on a per diem way is best handled in Primavera using an LoE, or sometimes a WBS activity type. Its really what those activity types are for, but you do need the correct duration type to select between a "hammock" which is spreading a lump sum, or as in your example, accruing a per diem resource (e.g. Fixed U/T).
An Auto compute activity should only require that Auto Compute Actuals is run with the new data date BEFORE the project is re-scheduled to work properly.
The "Update Progress" option in the "Tools" pull down does "update as scheduled"
Member for
18 years 6 monthsRE: Update as scheduled
LofE tasks are not considered critical because by choosing that type of task, you are saying that the said activity duration is dependent on the activites within the plan that it has relationships with.
If for example, you are putting a task in to show you have 1 PM who will be 100% utilised over the whole project, you can add the LofE, call it Project Management and link it SS to the earliest starting project activity and FF to the latest finishing project activity. Then you can assign the resource.
If there is a delay in the tasks between the earliest and latest task this will extend you overall project duration, as expected. As your Project Management task directly relates to the earliest and latest tasks it will extend in duration also.
If there is no delay and you are trying to show you are on track to meet the baseline finish, then you will have to input the progress against the normal tasks to make the overall duration of the current plan match the overall duration of the baseline plan. Once you have done this you will notice that the LofE task has calculated its own performance. i.e if you are half way through the overall duration of your plan and are on target to meet the baseline finish date, then your LofE will show 50% performance.
If you are using EVM, then your EV (BCWP) for PM costs would be 100% of the planned value(BCWS). Your SPI would be 1 for PM activities.
Member for
18 years 9 monthsRE: Update as scheduled
Jim
Try in the view "Projects" for your project(s):
1. Tab "resources" --> mark "Drive activity dates by default". This will align dates for activities and resources assignments.
2. Tab "Calculations" --> mark "Subtract actual from at completion" should keep your duration.
Hope this helps.
Dieter
Member for
17 years 1 monthRE: Update as scheduled
’A level of effort activity’s duration is dependent on its predecessor and/or successor activities.’
If you use this for PM/overhead type activities it will extend and contract in-line with the activities it is associated to.
A LofE automatically claims performance based on elapsed time, but the overall duration of the LofE can change in line with the dynamics of the schedule.
Ok - that does the trick although I believe that LoE activities arent considered on the critical path.
Updating Progress on other activities, regardless of duration type, pushes the finish date out if resources are assigned (although the resource finish dates do not move!). So I have to manually reduce the remaining duration down to pull it back to the baseline finish.
Member for
19 years 1 monthRE: Update as scheduled
Jim,
Exactly! (when doing it automatically). Just tell me when you encounter a project (schedule) that you automatically update your current schedule.
cheers
Member for
18 years 6 monthsRE: Update as scheduled
Jim,
A level of effort activity’s duration is dependent on its predecessor and/or successor activities.
If you use this for PM/overhead type activities it will extend and contract in-line with the activities it is associated to.
A LofE automatically claims performance based on elapsed time, but the overall duration of the LofE can change in line with the dynamics of the schedule.
Member for
17 years 1 monthRE: Update as scheduled
Hi Anoon,
Im not sure if I understand your response: Are you saying that updating as scheduled progresses activities in accordance to the baseline schedule rather than the current?
Cheers
Jim
Member for
19 years 1 monthRE: Update as scheduled
Jim,
1. first, back-up your schedule.
2. Use the maintain baseline, assign baseline, restore baseline functions.
3. make sure you work only on your Baseline Schedule.
4. this has nothing to do with your Current Schedule (update as scheduled!).
Member for
17 years 1 monthRE: Update as scheduled
Thanks David,
Id looked at LoE activities before and have just had a try. Its converting the resource effort to actuals as planned, but is still pushing back the finish of the activity. Any ideas what Im doing wrong?
Activity is LoE, Fixed Duration and U/T, %complete Duration. Im using Update Progress with the new data date a week after the current one.
Cheers
Jim
Member for
21 yearsRE: Update as scheduled
The specific example you gave, of accruing a resource on a per diem way is best handled in Primavera using an LoE, or sometimes a WBS activity type. Its really what those activity types are for, but you do need the correct duration type to select between a "hammock" which is spreading a lump sum, or as in your example, accruing a per diem resource (e.g. Fixed U/T).
An Auto compute activity should only require that Auto Compute Actuals is run with the new data date BEFORE the project is re-scheduled to work properly.
The "Update Progress" option in the "Tools" pull down does "update as scheduled"