Ihab Saad – Earned Value Analysis EV

Ihab Saad
AI: Summary ©
The speakers discuss the importance of timely updates and forecasts in managing costs and schedule for project management. They emphasize the need for timely updates and forecasts, as well as updating budgets and budgets weekly. The speakers also discuss the use of "monarch" terms in budgeting processes and the importance of monitoring project performance. They emphasize the need for transparency and understanding of the actual costs and actual costs for each project. They also discuss the use of words to report on the project's performance and the importance of monitoring and identifying actual costs and actual costs over time.
AI: Transcript ©
00:00:04 --> 00:00:05

Music, good afternoon,

00:00:06 --> 00:00:09

and today we're going to talk about a new subject related to

00:00:10 --> 00:00:14

project scheduling, which is measuring the project performance

00:00:14 --> 00:00:16

through a technique called earned value analysis.

00:00:18 --> 00:00:22

In a recent study by the construction industry Institute,

00:00:22 --> 00:00:26

they found out that cost and schedule are two very

00:00:26 --> 00:00:30

representative measures of the Project Health, and they found

00:00:30 --> 00:00:34

that there's a direct correlation between the scheduled performance

00:00:34 --> 00:00:38

and the cost performance as indicators of how the project is

00:00:38 --> 00:00:42

performing in general. So the closer the cost, the actual cost

00:00:42 --> 00:00:46

and schedule are to the planned values, the better the project

00:00:46 --> 00:00:50

performance is and will be at the end. So basically, cost and

00:00:50 --> 00:00:54

schedule are definitely two measures, two active and valuable

00:00:54 --> 00:00:59

measures to gage the Project Health and its performance from

00:00:59 --> 00:01:03

time to time on a regular basis, to try to forecast the end result

00:01:03 --> 00:01:07

for that particular project. However, measuring cost and time

00:01:07 --> 00:01:11

or cost and schedule performance usually have some problems, if not

00:01:11 --> 00:01:14

not done properly. Among these problems is that trying to measure

00:01:14 --> 00:01:18

the schedule and cost performance for the sake of reporting on

00:01:18 --> 00:01:22

general project performance in general project managers sometimes

00:01:22 --> 00:01:26

fall in the trap of comparing apples to oranges, and this

00:01:26 --> 00:01:32

primarily results from comparing two moving targets, or making a

00:01:32 --> 00:01:35

comparison between two moving targets at the same time without

00:01:35 --> 00:01:38

having something to compare to. So for example, if I want to measure

00:01:38 --> 00:01:41

the speed of something that's moving, I have to compare it

00:01:41 --> 00:01:45

either to something that's stationary or to something that's

00:01:45 --> 00:01:49

moving at a certain speed that I already know. So I can measure the

00:01:49 --> 00:01:52

relative speed or the relative difference between the two speeds.

00:01:52 --> 00:01:57

If we do not have such benchmarks, we will not have valid comparisons

00:01:57 --> 00:02:01

when it comes to time and schedule. So successful project

00:02:01 --> 00:02:05

managers at the very beginning should establish agreed upon

00:02:05 --> 00:02:09

baselines related to cost and time, and these are going to be

00:02:09 --> 00:02:12

basically the approved budget at the very beginning of the project

00:02:12 --> 00:02:16

and the approved baseline schedule that in general, the general

00:02:16 --> 00:02:20

contractor submits to the owner for review and approval. Once

00:02:20 --> 00:02:23

these are established, once these are approved, they become our

00:02:23 --> 00:02:26

benchmarks or our measuring lines, and we can start measuring

00:02:26 --> 00:02:31

progress from these fixed benchmarks. We also have to

00:02:31 --> 00:02:36

establish some thresholds to measure our variances. So for

00:02:36 --> 00:02:39

example, we know that sometimes we might be a little bit above

00:02:39 --> 00:02:42

budget, little bit below budget or ahead of schedule or behind

00:02:42 --> 00:02:46

schedule. So we have to establish thresholds, and they can be color

00:02:46 --> 00:02:51

coded, for example. So green is anywhere if we're performing at

00:02:51 --> 00:02:58

schedule or on but on time plus or minus, let's say three to 5% so if

00:02:58 --> 00:03:00

we are in a range, little bit ahead of schedule, little bit

00:03:00 --> 00:03:04

behind schedule or right on schedule, we are fine. So this can

00:03:04 --> 00:03:04

be green.

00:03:05 --> 00:03:11

If the range of variance is greater than or anywhere between

00:03:11 --> 00:03:16

five and seven or 8% for example, it can be yellow. We are

00:03:16 --> 00:03:21

approaching the level of danger or warning. Anything above that is

00:03:21 --> 00:03:24

going to become red. So again, color coding that will go will

00:03:24 --> 00:03:28

show us, just with a visual inspection, how the project is

00:03:28 --> 00:03:31

performing. So we have to establish these thresholds from

00:03:31 --> 00:03:34

the very beginning and monitor the project accordingly.

00:03:36 --> 00:03:40

So what's earned value? Earned value analysis used to also be

00:03:40 --> 00:03:47

known as C slash, SCSC, which is which stands for cost slash,

00:03:47 --> 00:03:51

schedule control systems, criteria, very complicated name

00:03:51 --> 00:03:54

that was invented by the Department of Defense because they

00:03:54 --> 00:03:57

were the first ones to use it to measure the performance on their

00:03:57 --> 00:04:02

projects. So in In brief, we call it earned value analysis, or EV.

00:04:03 --> 00:04:06

It builds on the concept of comparing apples to apples and

00:04:06 --> 00:04:09

oranges to oranges. So again, when we're going to make a comparison,

00:04:09 --> 00:04:13

it has to be a valid comparison, and not just comparing two numbers

00:04:13 --> 00:04:14

that are totally unrelated.

00:04:16 --> 00:04:19

It enables the project managers, through a simple and effective

00:04:19 --> 00:04:24

analysis, to get timely updates and forecasts of projects, time

00:04:24 --> 00:04:28

and cost performance. The key word here is timely, because if you get

00:04:28 --> 00:04:32

the update too late, unfortunately, its value is very

00:04:32 --> 00:04:37

much reduced because you cannot make any corrective actions or any

00:04:37 --> 00:04:40

improvements on the project. So if you get all of these updates at

00:04:40 --> 00:04:44

the end of the project that's past history. It's just a documentation

00:04:44 --> 00:04:47

of the project performance, without the ability to change any

00:04:47 --> 00:04:51

of its outcomes. So we have to do these on a regular basis and in a

00:04:51 --> 00:04:54

very timely fashion. So if we're going to update our schedule on a

00:04:54 --> 00:04:57

weekly basis, for example, we can generate that report or that

00:04:57 --> 00:04:59

analysis on a weekly basis. Same.

00:05:00 --> 00:05:02

Thing, it's very highly recommendable that whenever you

00:05:02 --> 00:05:05

update your schedule, you also update your budget, so you can get

00:05:05 --> 00:05:09

a comparison of time and cost at the same time on a very regular

00:05:09 --> 00:05:09

basis.

00:05:11 --> 00:05:17

So to discuss earned value, let's start by this short story or

00:05:17 --> 00:05:21

example on a project that is under construction.

00:05:23 --> 00:05:28

The president of a company received a call. The CEO of a

00:05:28 --> 00:05:31

large company was contacted by his CFO, the Chief Financial Officer,

00:05:32 --> 00:05:35

usually an accountant, who informed him of the following,

00:05:35 --> 00:05:39

saying that, sir, according to the approved schedule and our accurate

00:05:39 --> 00:05:44

cost estimate, until this morning we should have spent $38.5 million

00:05:45 --> 00:05:49

on the project. So the cost expenditure up till this morning

00:05:49 --> 00:05:55

should have been $38.5 million however, according to my latest

00:05:55 --> 00:05:58

calculations, until this morning, and this is we're talking about an

00:05:58 --> 00:06:01

accountant who's very meticulous, very accurate, until this morning,

00:06:01 --> 00:06:04

we have actually spent $40.3 million

00:06:05 --> 00:06:09

so to the account that it appears that we have a big variance here.

00:06:09 --> 00:06:13

That's a considerable variance, by the way. So he says, Sir, this is

00:06:13 --> 00:06:16

a serious matter that requires your immediate attention. I

00:06:16 --> 00:06:19

recommend you fire the project manager and maybe also the Vice

00:06:19 --> 00:06:22

President for Operations. There's no

00:06:23 --> 00:06:29

love lost between the two. So what do you think if the CEO of the

00:06:29 --> 00:06:33

company listens to that very accurate and meticulous

00:06:33 --> 00:06:36

accountant, Chief Accountant, Chief Financial Officer, what

00:06:36 --> 00:06:39

should they do if you were in that situation? What What would you do?

00:06:39 --> 00:06:43

The question is, do we have enough information to make an educated

00:06:43 --> 00:06:48

decision about something as important as firing someone or

00:06:48 --> 00:06:51

hiring someone or changing the outcome of the project? So let's

00:06:51 --> 00:06:55

see whether these numbers, as accurate as they are, as correct

00:06:55 --> 00:07:00

as they are, really reflect the status of the project, or is there

00:07:00 --> 00:07:04

something missing? And here we're going to start with what we call

00:07:04 --> 00:07:05

the tale of

00:07:06 --> 00:07:07

three fruits.

00:07:08 --> 00:07:12

So basically, through this story, we have not only two fruits,

00:07:12 --> 00:07:17

apples and oranges, but we must also look at the third fruit. So

00:07:17 --> 00:07:20

in the previous report, the CFO made a classical mistake of

00:07:20 --> 00:07:24

comparing an apple to an orange. He looked at two numbers, two

00:07:24 --> 00:07:28

different values, which really represent an apple and an orange.

00:07:28 --> 00:07:30

So there's nothing to compare between an apple and an orange.

00:07:31 --> 00:07:34

We're going to see that in just a second. So the apple,

00:07:35 --> 00:07:39

the apple represents the budgeted cost to be spent on the scheduled

00:07:39 --> 00:07:44

work, the $38.3 million or whatever it was so. And this is

00:07:44 --> 00:07:50

going to be called the budgeted cost for work scheduled. Budgeted

00:07:50 --> 00:07:53

cost because it was based on the estimate for work schedule,

00:07:53 --> 00:07:55

because it was based on the baseline schedule that was

00:07:55 --> 00:08:01

approved by the client. And that number is the value that the CFO

00:08:01 --> 00:08:05

told the owner, until this morning we should have spent. Should have

00:08:05 --> 00:08:09

spent means it was a budgeted cost, and until this morning,

00:08:09 --> 00:08:12

which is the work done to date, according to the schedule, based

00:08:12 --> 00:08:18

on the scheduled performance. And then he told him, yet until this

00:08:18 --> 00:08:22

morning, we have actually spent. So now he's talking about actual

00:08:23 --> 00:08:28

expenditure we have actually spent. It was 40 point something

00:08:28 --> 00:08:32

million dollars. Again, big difference. So the orange

00:08:32 --> 00:08:36

represents the actual cost spent on the actual amount of work

00:08:36 --> 00:08:36

performed,

00:08:38 --> 00:08:44

or actual cost for work performed, AC, WP, so we have two four letter

00:08:44 --> 00:08:50

words, BCWS and acwp. What do we have in common? If we try to split

00:08:50 --> 00:08:55

these words into two parts. In the first part, we have BC, for the

00:08:55 --> 00:08:58

second one, we have AC. They are not common, budgeted costs and

00:08:58 --> 00:09:02

actual costs are quite different. The second half is work schedule,

00:09:02 --> 00:09:07

Ws and work performed. WP again, work scheduled is what we should

00:09:07 --> 00:09:11

have done. Work performed is what we have actually accomplished. So

00:09:11 --> 00:09:14

again, they might be different, so there's nothing

00:09:16 --> 00:09:19

comparable between the two terms. Therefore, what we're going to do

00:09:19 --> 00:09:24

is we're gonna slice this apple into two halves, and we're gonna

00:09:24 --> 00:09:28

slice this orange into two halves, and we're gonna look at the hybrid

00:09:28 --> 00:09:33

fruit that we're gonna call the orpal, or the appenge. Orpal, half

00:09:33 --> 00:09:36

orange, half apple, apench, half apple, half orange. Either term is

00:09:36 --> 00:09:37

fine with me.

00:09:39 --> 00:09:43

So the solution is the average, or the orphan, which looks something

00:09:43 --> 00:09:47

like this, half apple, half orange. When we split this apple

00:09:47 --> 00:09:51

in halves, we took the left half of the apple and the left half of

00:09:51 --> 00:09:55

the Apple was BC budgeted cost. And then when we took the half of

00:09:55 --> 00:09:59

the orange, we took the right half of the orange, which represents

00:09:59 --> 00:09:59

word.

00:15:00 --> 00:15:03

Cost, which means we are performing under budget, which is

00:15:03 --> 00:15:06

having some savings, and that's definitely good. Scheduled

00:15:06 --> 00:15:10

variance, or SV, is equal to the earned value minus the planned

00:15:10 --> 00:15:13

value. Again, negative is bad, because

00:15:15 --> 00:15:16

planned value

00:15:17 --> 00:15:20

is greater than the earned value, which means we are behind

00:15:20 --> 00:15:26

schedule, and positive is good, which means that the earned value,

00:15:26 --> 00:15:29

what we have earned, is greater than the planned value, which

00:15:29 --> 00:15:32

means we have achieved more than what we were supposed to do in the

00:15:32 --> 00:15:35

same period of time, which means that we are ahead of schedule.

00:15:36 --> 00:15:40

The cost performance index, sometimes also called cost

00:15:40 --> 00:15:44

performance ratio. So ratio or index is the same thing, and it

00:15:44 --> 00:15:47

results from the Division of two different terms. And in this case,

00:15:47 --> 00:15:51

instead of subtracting one term from another actual cost from

00:15:51 --> 00:15:56

earned value, we divide earned value by actual cost. So in this

00:15:56 --> 00:16:01

case, we have something to be compared to one under perfect

00:16:01 --> 00:16:05

conditions, the earned value is equal to the actual cost if we are

00:16:05 --> 00:16:08

performing exactly according to budget. So in this case, comparing

00:16:08 --> 00:16:12

to to one, if the earned value is greater than the actual cost,

00:16:12 --> 00:16:16

which means that we have earned more than what we we actually

00:16:16 --> 00:16:21

spent, then greater than one is good and less than one is bad,

00:16:21 --> 00:16:24

because the actual cost is going to exceed the earned value.

00:16:26 --> 00:16:29

Similarly, for the schedule, if the earned value is greater than

00:16:29 --> 00:16:32

the planned value, greater than one is good, because we would be

00:16:32 --> 00:16:35

ahead of schedule. Less than one is bad.

00:16:36 --> 00:16:39

The estimate at completion can be calculated in three different

00:16:39 --> 00:16:43

ways. Either it's the budget at completion divided by the cost

00:16:43 --> 00:16:48

performance index, or it is the actual cost plus the estimate to

00:16:48 --> 00:16:53

complete, or it is the actual cost plus budget at completion minus

00:16:53 --> 00:16:56

earned value. Either one of these three terms can give us the

00:16:56 --> 00:17:01

estimate at completion, the estimate to complete is equal to

00:17:01 --> 00:17:03

estimate at completion minus the actual cost.

00:17:04 --> 00:17:09

Variance at completion is equal to budget at completion, our original

00:17:09 --> 00:17:14

budget minus estimate at completion based on the current

00:17:14 --> 00:17:17

progress. Positive is good, which means that we are saving money.

00:17:17 --> 00:17:22

Negative is bad, which means we're going to finish above budget and

00:17:22 --> 00:17:27

to complete performance index, or TCPI, is budget at completion

00:17:27 --> 00:17:32

minus earned value divided by budget at completion minus actual

00:17:32 --> 00:17:36

cost. Now, from these different terms, the most commonly used

00:17:36 --> 00:17:40

terms are the first four, which are the cost variance, scheduled

00:17:40 --> 00:17:43

variance, cost performance index or cost performance ratio, and

00:17:43 --> 00:17:47

scheduled performance index or scheduled performance ratio. We're

00:17:47 --> 00:17:49

going to see in a minute how to calculate these.

00:17:51 --> 00:17:54

So now let's look at that graph representing the

00:17:55 --> 00:17:58

time on the horizontal axis and cost on the vertical axis. Now

00:17:58 --> 00:18:01

when we look at this curve, this reminds us of what we used to know

00:18:01 --> 00:18:06

as the S curve, or the progress curve, and the final point on that

00:18:06 --> 00:18:10

progress curve is our budget at completion of BAC. Now that dotted

00:18:10 --> 00:18:15

vertical green line represents our cutoff date, as we used to do in

00:18:15 --> 00:18:20

updating, in Project updating, so as of this cutoff date, we have

00:18:20 --> 00:18:26

different values based on our budget and based on our schedule.

00:18:26 --> 00:18:32

Both plans, we should have spent $38.5 million according to that

00:18:33 --> 00:18:36

up to that cutoff date. However,

00:18:38 --> 00:18:44

our actual cost for work performed or actual cost is $40.3 million

00:18:44 --> 00:18:47

and now this is the classical mistake when the CFO made the

00:18:47 --> 00:18:51

comparison between these two moving targets. Notice that this

00:18:51 --> 00:18:55

curve is not continued, because this is actual and we don't know

00:18:55 --> 00:18:59

how are we going to perform in the future. We can, however, forecast

00:18:59 --> 00:19:02

our future based on our current progress. But up to this point,

00:19:02 --> 00:19:07

we're just reporting past history of actual performance, and we have

00:19:07 --> 00:19:11

not projected that into the future yet. And now we're looking for

00:19:11 --> 00:19:16

that third term, something in between these two, which is now

00:19:16 --> 00:19:19

this is the forecast, as you can see, and it's a dotted line that

00:19:19 --> 00:19:22

shows that our estimate at completion here is going to be

00:19:22 --> 00:19:26

above the budget at completion if we keep performing the same way.

00:19:26 --> 00:19:32

So it seems that we're not doing well. Now let's look at the third

00:19:32 --> 00:19:35

number, the orphan that we're looking for, and we're going to

00:19:35 --> 00:19:39

talk later about how to perform to calculate that number. But if that

00:19:39 --> 00:19:44

number were here, bcwp, or earned value, if it was some somewhere

00:19:44 --> 00:19:47

between these two numbers, we're going to look at different

00:19:47 --> 00:19:52

scenarios. What if that point is above both curves? What if it is

00:19:52 --> 00:19:56

below both curves? What if it's in between and what? And what's the

00:19:56 --> 00:19:59

respective order of these points. How does that affect our Calc?

00:20:00 --> 00:20:03

Relations. We're going to talk about that in a minute, but let's

00:20:03 --> 00:20:06

assume for the moment that the budgeted cost forward performed

00:20:07 --> 00:20:09

was calculated equal to 39.8

00:20:10 --> 00:20:13

so now let's look at according to the equations that we discussed on

00:20:13 --> 00:20:17

the previous slide. Let's calculate our variances and our

00:20:17 --> 00:20:24

indices. So the first variance is the comparison of the apple to the

00:20:24 --> 00:20:28

orange, which is equal to the accounting variance. What we call

00:20:28 --> 00:20:31

accounting variance. The reason I did not include it on the previous

00:20:31 --> 00:20:35

slide is that we as project managers and cost engineers and so

00:20:35 --> 00:20:38

on, we should not use that number. This number is sometimes

00:20:38 --> 00:20:43

mistakenly used by accountants, but we as project managers should

00:20:43 --> 00:20:46

not use that number. We should know how it's calculated, but we

00:20:46 --> 00:20:50

should not use it. The accounting variance is equal to actual cost

00:20:50 --> 00:20:54

for rule perform, minus budget, cost for schedule, and here it

00:20:54 --> 00:20:58

shows that we are far above our budget. But again, that's not the

00:20:58 --> 00:21:01

measure that we're looking at, because that does not measure time

00:21:01 --> 00:21:02

in any way.

00:21:04 --> 00:21:08

Now let's start looking at comparable numbers. Here we have

00:21:08 --> 00:21:15

bcwp, which is the earned value, and BCWS, which is the PV or the

00:21:15 --> 00:21:20

planned value. What do they have in common? BC and BC, if we remove

00:21:20 --> 00:21:24

the common half of each one of these words, we end up with word

00:21:24 --> 00:21:27

performed compared to work scheduled.

00:21:28 --> 00:21:31

So if the word performed is greater than the work scheduled,

00:21:31 --> 00:21:36

if we have a positive number from this equation, word performed is

00:21:36 --> 00:21:38

greater than the work schedule, that means that we are ahead of

00:21:38 --> 00:21:44

schedule, ahead of schedule by an amount of work equal to the value

00:21:44 --> 00:21:47

or the difference between these two, which is about $1.3 million

00:21:48 --> 00:21:53

so our scheduled performance is fine. We have achieved more work

00:21:53 --> 00:21:57

than we were supposed to do or we were planned to, up till that

00:21:57 --> 00:22:02

cutoff date. So schedule wise, we're doing well. So this is the

00:22:02 --> 00:22:06

scheduled variance, and then we're going to compare the cost

00:22:06 --> 00:22:12

variance. Again, comparing an or an orpal to an orange, the common

00:22:12 --> 00:22:18

part is the or, which is, in this case, the WP and the WP. So

00:22:18 --> 00:22:23

comparing earned value to actual cost. We're going to remove the

00:22:23 --> 00:22:28

common term WP. So we're comparing BC to AC, budgeted cost to actual

00:22:28 --> 00:22:32

cost. In this case, the actual cost is above the budgeted cost,

00:22:32 --> 00:22:35

which means we're going to get a negative value here. And as we

00:22:35 --> 00:22:39

learned from the previous slide, negative value means bad we are we

00:22:39 --> 00:22:44

are over budget. So in this case, we are over budget by about half a

00:22:44 --> 00:22:48

million dollars, which is difference between 40.3 and 39.8

00:22:49 --> 00:22:52

so basically, if we want to report on the actual status of this

00:22:52 --> 00:22:57

project, we can use just two words to report a general very brief

00:22:57 --> 00:23:04

report. Is it good, good, good, bad, bad, good or bad, bad. So is

00:23:04 --> 00:23:07

the schedule good and the cost good? So it would be good, good,

00:23:07 --> 00:23:11

or the schedule is good and the cost is bad, which is good, bad,

00:23:11 --> 00:23:16

exactly what we have here. Or is it bad, good, the schedule is bad,

00:23:16 --> 00:23:24

but the cost is good or bad, bad, which would be if that bcwp is the

00:23:24 --> 00:23:30

lowest point is below acwp And BCWS. So if the earned value falls

00:23:30 --> 00:23:33

below both other point, the two other points, if it's the lowest

00:23:33 --> 00:23:39

point, then that would be a bad bet. However, if that point is

00:23:39 --> 00:23:43

above both other points. If above the two points, then it would be

00:23:43 --> 00:23:47

good, good, because in this case, we would be ahead of schedule and

00:23:47 --> 00:23:50

below budget, which is which would be a perfect situation.

00:23:52 --> 00:23:56

So the analysis results from the previous graph, we can conclude

00:23:56 --> 00:24:00

the following, the scheduled variance is $1.3 million positive,

00:24:00 --> 00:24:04

so we are ahead of schedule by an amount of work worth $1.3 million

00:24:05 --> 00:24:09

which is good, and the cost variance, we have a negative

00:24:09 --> 00:24:12

number, negative half a million, which means the project is above

00:24:12 --> 00:24:17

budget by point 5 million, which is bad. Therefore the final

00:24:17 --> 00:24:19

situation for this project is good, bad

00:24:21 --> 00:24:26

or bad, good, depending on if you compare the cost first and then

00:24:26 --> 00:24:27

the scheduled second.

00:24:29 --> 00:24:33

The variances, however, however important as they are, do not show

00:24:33 --> 00:24:37

the full picture, because what if, for example, I get a cost variance

00:24:37 --> 00:24:41

of negative half a million dollars. Okay, we are above

00:24:41 --> 00:24:45

budget. But how drastic the situation is, how bad the

00:24:45 --> 00:24:48

situation is. If I were to tell you, for example, that the value

00:24:48 --> 00:24:50

of the project is $1 billion

00:24:51 --> 00:24:54

so half a million compared to 1 billion,

00:24:55 --> 00:24:59

that's negligible, we can recover that covid.

00:30:00 --> 00:30:05

In our schedule is going to be represented by a cost item, cost

00:30:05 --> 00:30:09

center or cost unit. So whenever we report, we're going to report

00:30:09 --> 00:30:10

on time and cost at the same time.

00:30:14 --> 00:30:17

In case of emergency, use the Pareto law 8020

00:30:18 --> 00:30:23

which basically says that 20% of the activities in the project

00:30:23 --> 00:30:28

represent 80% of the cost of the project. So I, if I cannot perform

00:30:28 --> 00:30:33

time and cost control over 100% of the activities, at least, I'm

00:30:33 --> 00:30:37

gonna focus on the 20% of the activities that represent 80% of

00:30:37 --> 00:30:41

the total project cost. And that would give me an acceptable level

00:30:41 --> 00:30:46

of control. It's not perfect, but 80% is not too bad, either,

00:30:46 --> 00:30:50

especially that it's achieved with only monitoring, monitoring 20% of

00:30:50 --> 00:30:55

the activities. And how do we get these 20% of the activities? This

00:30:55 --> 00:30:56

is for another discussion.

00:30:58 --> 00:31:02

Now here, here's an example that shows a very simple example on a

00:31:02 --> 00:31:08

network represented by six activities, A through F. And this

00:31:08 --> 00:31:12

is the duration in weeks for each activity, and this is the

00:31:12 --> 00:31:16

precedence, which means what are the IPAs? So A and B are the

00:31:16 --> 00:31:19

beginning activities for this project. And then we have here the

00:31:19 --> 00:31:23

succession of the different activities, and we also have

00:31:23 --> 00:31:27

budgeted cost per week. And this is obtained from our estimate.

00:31:27 --> 00:31:30

Budgeted cost per week. How much do we expect to spend on this

00:31:30 --> 00:31:36

activity per week according to the estimate? And then here we have a

00:31:36 --> 00:31:39

blank column where we have to calculate the total budget. And

00:31:39 --> 00:31:42

very easily, the total budget is going to be obtained by

00:31:42 --> 00:31:47

multiplying the budgeted cost per week times the duration in weeks.

00:31:47 --> 00:31:50

So basically, for activity A, for example, it would be $690

00:31:52 --> 00:31:55

for activity B, it would be six times 280, and so on and so forth.

00:31:55 --> 00:32:01

By adding these numbers together, what we're going to get is, what

00:32:02 --> 00:32:09

if you said BC WP, if you said BCWS, that would be half correct

00:32:09 --> 00:32:13

and half incorrect, because it would be BCWS only at the end of

00:32:13 --> 00:32:19

the project, not at the time we are measuring BCWS at the end of

00:32:19 --> 00:32:23

the project is basically what we call BAC, or the budget at

00:32:23 --> 00:32:27

completion. Therefore the sum of these numbers is not going to be

00:32:27 --> 00:32:29

used in our equation whatsoever.

00:32:30 --> 00:32:33

Now the problem is, or the question is, at the end of week

00:32:33 --> 00:32:37

nine, which is our cutoff date, our green line, the actual project

00:32:37 --> 00:32:42

status was as follows. These numbers were calculated from the

00:32:42 --> 00:32:45

site, and this progress was reported from the site for

00:32:45 --> 00:32:48

activity, it was 100% complete, so PCT, 100%

00:32:49 --> 00:32:53

therefore it was complete. B, 100% C, 75%

00:32:54 --> 00:32:58

D, 0% E, 60% and F, 50%

00:32:59 --> 00:33:03

and these are the actual costs of each one of these activities,

00:33:03 --> 00:33:09

actual cost, actual cost up to the end of week nine. So actual cost

00:33:09 --> 00:33:13

for the work performed up till the end of week nine. Therefore, if we

00:33:13 --> 00:33:19

add these numbers together, that's going to give us the acwp at the

00:33:19 --> 00:33:20

end of week nine.

00:33:21 --> 00:33:24

Now we need to calculate the earned value. What is the earned

00:33:24 --> 00:33:29

value up till the end of week nine as well. So for each activity

00:33:29 --> 00:33:32

here, we have assumed a linear relationship between cost and

00:33:32 --> 00:33:37

schedule, and that the BCWS is determined from the earliest start

00:33:37 --> 00:33:41

date. So assuming a linear relationship between cost and

00:33:41 --> 00:33:46

schedule, which means that the cost is uniformly distributed

00:33:46 --> 00:33:48

along the duration of the activity. That's why we mentioned

00:33:48 --> 00:33:51

that the cost is the same for each week. This is the assumption that

00:33:51 --> 00:33:56

we need. So the question now is, how are we going to determine

00:33:56 --> 00:34:00

whether this project is ahead of schedule, behind schedule, on

00:34:00 --> 00:34:04

budget, above budget, below budget, and we're going to try to

00:34:04 --> 00:34:06

measure the cost variance, scheduled variance,

00:34:07 --> 00:34:12

and the CPI and the SPI. So what we need to do here is to draw a

00:34:12 --> 00:34:15

cumulative cost curve for this project, showing the duration and

00:34:15 --> 00:34:19

cost, which is basically our s or progress curve. And then we need

00:34:19 --> 00:34:25

on that curve to identify acwp or actual cost BCWS, or planned

00:34:25 --> 00:34:31

value. Bcwp or earned value, CV, cost variance, SV, scheduled

00:34:31 --> 00:34:35

variance on the curve. And we need also to determine the values of

00:34:35 --> 00:34:39

the CPR or CPI cost performance ratio, or cost performance index,

00:34:40 --> 00:34:44

and SPR or SPI schedule performance ratio or scheduled

00:34:44 --> 00:34:49

performance index. And finally, in your expert opinion, what is the

00:34:49 --> 00:34:53

status of this project, schedule wise and cost wise. So are we

00:34:53 --> 00:34:56

ahead of schedule? Behind schedule, above budget, below

00:34:56 --> 00:34:59

budget? Is it good, good, good, bad, bad, bad, good or bad, bad.

00:35:00 --> 00:35:03

Ed, this is what we're going to answer through solving that

00:35:03 --> 00:35:06

example in the next presentation.

Share Page