What’s the score?

What’s the score?

Like the cheerleaders that lost the diss war, “scoreboard, scoreboard” is used to humble teams who’s performance lags behind. In construction, “Schedule, schedule” becomes the jeer towards contactors that don’t keep up with their plan. Of course, in business, it goes beyond high school egos. Contractors don’t get “dragged” with simple put downs; they get fired when they don’t perform.

In sports it’s simple to see who’s winning, hence, “Scoreboard, scoreboard”. But in construction, few job-sites have a functioning scoreboard, so we rely upon Earned Value Management. It promises the score via metrics and indicators. For schedule performance, the math is simple arithmetic, performance = earned / planned, at a certain time. 

That time component is actually a bit trickier, which is probably why scheduling software makes most cringe. Most contracts require the use of Critical Path software to deliver the time element. Most schedules show the earliest date a task could be accomplished. Those are typically used to calculate the “planned value” for a task. If a contractor is falling behind the planned value, it’s indictive that the contractor is underperforming. Since Schedule Performance Indicator (SPI) is earned/planned, the underperforming contractor is expected to have a SPI less than 1.0. Earning less than planned produces a value under 1.0.

Why does any of this matter?

For owners, anything that gets the contractor completed as quickly as possible reduces risk. As a contractor, performing the work in the most efficient manner increases profit. In economics, it’s classic risk and reward, the topic that many PhDs have been earned.  In scheduling terms, the owner manages to the early dates, contractors to somewhere in-between the early and late. Unfortunately (or not), there aren’t many PhDs doing construction scheduling.

However, there are plenty of JDs, MBAs, and CPAs executing contracts. Add a couple PMPs into the mix, and…I’ve now seen my first contract that permits the contract to be terminated if the contractor is at a SPI of 0.9 or less. According to the…earliest dates. Not the latest, nor the sweet spot in-between the early and late dates.

It poses a fundamental question: If the contractor isn’t performing everything as early as they can, are they late? Or, should they be given the opportunity to perform the task at the latest date possible, before being considered late? In this case, the contract only allows production to be 10% less than the most optimistic projection. Is that a tolerable amount of risk for a owner to accept? Or should we give the contractor more leeway in that “sweet spot” between ASAP and LATE.

 Below, it’s that sweet spot is the area with the horizontal pink line.

463 CY 
o 
600 
500 
400 
300 
200 
100 
2,500 
2,000 
1,500 
1,000 
500 
12-Sep 19-Sep 26-Sep 
o 
25-Apr 
æ May 
620 
620 
620 
620 
620 
620 
9_May 
1,097 
577 
1,066 
520 
1,097 
793 
16-May 23-May 30-May 
1 ,482 
148 
1,418 
1 ,290 
1 ,482 
1,354 
1,334 
238 
1,227 
1,127 
1,334 
1,177 
1,498 
16 
1 ,535 
1 ,364 
1,498 
1,450 
6-Jun 
291 
,011 
1,789 
1,780 
13-Jun 
2,022 
232 
2,195 
1783 
2,022 
1,989 
20-dun 
2, 194 
172 
2,290 
1,783 
2, 194 
2,037 
27-Jun 
2,298 
104 
2,416 
1,796 
2,298 
2,106 
4-Jul 
2,334 
36 
2,437 
1,824 
2,334 
2,131 
I l-dul 
2,395 
61 
2,479 
1 ,856 
2,395 
2,168 
18-Jul 
2,461 
66 
2,492 
1 ,968 
2,461 
2,230 
26-Jul 
12 
2,609 
2,032 
2,473 
2,271 
1 -Aug 
66 
2525 
2,076 
2538 
2,301 
37 
2,532 
2,150 
2,576 
2,341 
15-Aug 
4 
2,536 
2,382 
2,579 
2,469 
22-Aug 29-Aug 
CUMULATIVE 
—EARNED WEEKLY 
ZFORECAST WEEKLY 
LY CUMULATIVE 
TE CUMULATIVE 
ORECAST CUMULATIVE 
BASELINE CUMULATIVE 
19 
2536 
2,461 
2599 
2,494 
45 
2,575 
2,462 
2,644 
2,519 
s-sep 
16 
2,576 
2,472 
2,659 
2,524 
7 
2,682 
2,472 
2,666 
2,627 
2586 
2586 
2586

Focusing on 6-Jun (yellow), the contractor could have poured up to 2,011 CY of concrete (early cumulative),  and needed to pour at least 1,548 CY (cumulative late) to keep from potentially delaying the end date of the project. In real life, this gap existed because the compressor foundations needed to cure for 30 days, and the piping wasn’t going to be available to install until late July/early August. The compressor building floor was around 265 CY, which is the bulk of the delta, 465 CY, between early and late.

At that time they had placed 1,789 CY, earning a SPI of….Here’s where it gets tricky-according to the early, 0.889. According to the late curve, 1.15.

Does the contractor deserve to be fired or praised?

What’s the score?

In this case, look at the pink arrow going down. The contractor was aware of his “float” and downsized his crews in a controlled manner (pick of the litter), and caught the early green line by mid-July. Even though this is only a portion of the project, the problem is clear: Using the early planned values for SPI calculations will skew SPI towards a false negative indicator.

TL;DR

Integrating objective measurements is a powerful tool to measure performance. I’m not advocating contractors be allowed to underperform, just given the chance to optimize their profitability while accomplishing the work the owner has been promised. And, when they are jeered to look at the scoreboard, they actually know the score.

Phone: (833) 448-6646
Chatham, IL