You should be able to manage EV at the portfolio level as well as at job and phase level, even at activity level. It gets better when using multiple WBS structures, say one structure organized by Jobs and another by CSI master format codes. Better if instead of cost EV is based on parameters such as man-hour or a common work measure. When using portfolios you shall create a portfolio baseline, analogous to stand alone baselines.
WBS by Job
WBS by CSI masterformat division, EV for concrete by CY
By the way I do not use EVM unless at gunpoint.
EVM does not distinguish between critical and non-critical activities. Tracking EV variance without taking into account float makes no sense. A project could be late but EVA will not notice this problem if Earned Value exceeds Planned Value.
A firm and stable baseline is a fundamental requirement for EVM. Complex projects often involve unanticipated rework, making them unsuitable for EVM.
The DOD the father of the creature is against the use of EVM in fixed price contracts.
Field supervisors do not speak EVM jargon; ACWP, BAC, BCWP, BCWS, CA, CAM, CPI, CV, CWBS, EAC, EVA, LOE, LRE, OBS, PMB, RAM, SOW, SPI, SV, TAB, WBS, WP... What the heck!
Field supervisors will say if concrete wall pouring crew is 1 crane and 3 laborers the crew should have an estimated production rate of 20 cy/hr; if pouring 30 cy it will take 1.5 hours. So simple!
Get real; if you cannot communicate EVM to the stakeholders, top management and people actually doing the job, then it is of no value.
No EV.
We manage our jobs by paying attention to contract milestones as well as costs and production rates. For most jobs we use deterministic schedules, for more complex jobs we follow probabilities of success for contract milestones and cost.
Rafael- Thank you very much for the help, that was very beneficial. We are planning to use labor hours instead of cost as the metric we track. We are going to try to keep the EVM as simple as possible, so we will see how it goes. I will keep in mind what you said. Thanks again.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Sun, 2020-10-18 10:11
Imagine you are doing EVM for an internal software development job and instead of cost you are tracking EV for man-hours. Then BCWP “Budgeted Cost of Work Performed” is misleading, is unacceptable, it should be BVWP “Budgeted Value of Work Performed”; for cost it should read Cost[BVWP] while for volume of work it should read Volume[BVWP]. For resource hours it should read Resource-hours[BVWP], there is no cost shown in the diagram!
Many people do not realize how wrong it is because they follow the poor selection of terms used by the PERT team who could only think of value in monetary terms. Earned Value origin was long before CPM, at the time it had no flaws. When PERT team tried to tie it to CPM schedules relevant flaws surfaced, most notably the SPI. EVM makes sense under limited conditions, but you do not know at the beginning of a job if these conditions will hold or be broken.
For those still hooked on EVM please be reminded that when using volume of work the units shall be the same, here multiple WBS come handy as it allows you to group the phases by work sharing the same unit without sacrificing the need for other WBS structures.
Best Regards, Rafael Davila (an objector to the use of EVM)
Member for
16 years 3 months
Member for16 years4 months
Submitted by Zoltan Palffy on Wed, 2020-10-14 14:18
Thank you. How would I manage the baseline if I am adding large numbers of activities? My understanding/experience is that I would make a baseline after the schedule for the first bid package was complete. When the schedule was complete for each future bid package, I would then have to Restore the baseline, copy the activities for the new bid package to the baseline, and then recreate all the links between the new bid package and the older bid packages in the baseline. After the baseline was updated, I would then add it back into the schedule. Having to make sure the links in the baseline match the links in the schedule seems like a place where I could make a mistake.
Please let me know if my understanding of the process for managing the baseline when adding bid packages is wrong.
Thank you.
Member for
16 years 3 months
Member for16 years4 months
Submitted by Zoltan Palffy on Wed, 2020-10-07 13:59
Thanks Zoltan, but how could EV be measured across multiple projects and newly added projects (which would change the BAC & and alter EAC each time a proejct was added) in this way in P6?
I am concerned about managing the baseline if I make 1 schedule. My understanding/experience is that I would make a baseline after the schedule for the first bid package was complete. When the schedule was complete for each future bid package, I would then have to Restore the baseline, copy the activities for the new bid package to the baseline, and then recreate all the links between the new bid package and the older bid packages in the baseline. After the baseline was updated, I would then add it back into the schedule. Having to make sure the links in the baseline match the links in the schedule seems like a place where I could make a mistake.
Please let me know if my understanding of the process for managing the baseline when adding bid packages is wrong.
Thank you.
Member for
16 years 3 months
Member for16 years4 months
Submitted by Zoltan Palffy on Tue, 2020-10-06 13:54
Member for
21 years 8 monthsYou should be able to manage
You should be able to manage EV at the portfolio level as well as at job and phase level, even at activity level. It gets better when using multiple WBS structures, say one structure organized by Jobs and another by CSI master format codes. Better if instead of cost EV is based on parameters such as man-hour or a common work measure. When using portfolios you shall create a portfolio baseline, analogous to stand alone baselines.
By the way I do not use EVM unless at gunpoint.
We manage our jobs by paying attention to contract milestones as well as costs and production rates. For most jobs we use deterministic schedules, for more complex jobs we follow probabilities of success for contract milestones and cost.
Best Regards, Rafael
Member for
5 years 1 monthRafael- Thank you very much
Rafael- Thank you very much for the help, that was very beneficial. We are planning to use labor hours instead of cost as the metric we track. We are going to try to keep the EVM as simple as possible, so we will see how it goes. I will keep in mind what you said. Thanks again.
Member for
21 years 8 monthsImagine you are doing EVM for
Imagine you are doing EVM for an internal software development job and instead of cost you are tracking EV for man-hours. Then BCWP “Budgeted Cost of Work Performed” is misleading, is unacceptable, it should be BVWP “Budgeted Value of Work Performed”; for cost it should read Cost[BVWP] while for volume of work it should read Volume[BVWP]. For resource hours it should read Resource-hours[BVWP], there is no cost shown in the diagram!
Many people do not realize how wrong it is because they follow the poor selection of terms used by the PERT team who could only think of value in monetary terms. Earned Value origin was long before CPM, at the time it had no flaws. When PERT team tried to tie it to CPM schedules relevant flaws surfaced, most notably the SPI. EVM makes sense under limited conditions, but you do not know at the beginning of a job if these conditions will hold or be broken.
For those still hooked on EVM please be reminded that when using volume of work the units shall be the same, here multiple WBS come handy as it allows you to group the phases by work sharing the same unit without sacrificing the need for other WBS structures.
Best Regards, Rafael Davila (an objector to the use of EVM)
Member for
16 years 3 monthsok 1 step at a time then
ok 1 step at a time then
Member for
8 years 1 monthZoltan,Thank you, that makes
Zoltan,
Thank you, that makes sense. I am having trouble with update baseline, but I will save that for another post.
Member for
16 years 3 monthsyou would select update
you would select update baseline from the current project
Member for
8 years 1 monthZoltan,Thank you. How would I
Zoltan,
Thank you. How would I manage the baseline if I am adding large numbers of activities? My understanding/experience is that I would make a baseline after the schedule for the first bid package was complete. When the schedule was complete for each future bid package, I would then have to Restore the baseline, copy the activities for the new bid package to the baseline, and then recreate all the links between the new bid package and the older bid packages in the baseline. After the baseline was updated, I would then add it back into the schedule. Having to make sure the links in the baseline match the links in the schedule seems like a place where I could make a mistake.
Please let me know if my understanding of the process for managing the baseline when adding bid packages is wrong.
Thank you.
Member for
16 years 3 monthsthats my whole point u r not
thats my whole point u r not adding projects only activiies
Member for
13 years 3 monthsThanks Zoltan, but how could
Thanks Zoltan, but how could EV be measured across multiple projects and newly added projects (which would change the BAC & and alter EAC each time a proejct was added) in this way in P6?
Member for
8 years 1 monthZoltan,I am concerned about
Zoltan,
I am concerned about managing the baseline if I make 1 schedule. My understanding/experience is that I would make a baseline after the schedule for the first bid package was complete. When the schedule was complete for each future bid package, I would then have to Restore the baseline, copy the activities for the new bid package to the baseline, and then recreate all the links between the new bid package and the older bid packages in the baseline. After the baseline was updated, I would then add it back into the schedule. Having to make sure the links in the baseline match the links in the schedule seems like a place where I could make a mistake.
Please let me know if my understanding of the process for managing the baseline when adding bid packages is wrong.
Thank you.
Member for
16 years 3 monthstoo many schedule is too hard
too many schedule is too hard to manage. Why not make 1 schedule and put each project under its own wbs i.e
MASTER PROJECT
Project #1
Summary #1 here
Details #1 here
Project #2
Summary #2 here
Details #2 here
Project #3
Summary #3 here
Details #3 here