Ihab Saad – Schedule Updating

Ihab Saad
Share Page

AI: Summary ©

The speakers discuss the process of updating and maintaining a schedule, identifying the cause of deviation from the baseline and addressing mistakes to avoid them in the future. They also discuss the importance of proper actions to prevent future mistakes and the need for continuous monitoring and updating the schedule. The process of planning and executing a project is discussed, including monitoring performance, updating objectives, and tracking progress. The weight of completed activities is measured, and progress is measured by the actual date and the weight of completed activities is various percentages. The sub strengthen completion percentage is calculated, and the payment request is reviewed and resubmitted.

AI: Summary ©

00:00:01 --> 00:00:04
			Hello again, in new in a new
lecture of construction
		
00:00:04 --> 00:00:07
			scheduling, and today we're going
to start talking about schedule
		
00:00:07 --> 00:00:10
			updating. As you remember, when we
discussed the time management
		
00:00:11 --> 00:00:15
			steps, we mentioned six steps. The
first one was activity definition,
		
00:00:16 --> 00:00:20
			the second one was activity
sequencing, followed by resource
		
00:00:20 --> 00:00:24
			estimating and duration
estimating, and then we have
		
00:00:24 --> 00:00:28
			scheduled development, and
finally, scheduled control. So
		
00:00:28 --> 00:00:32
			far, we have talked about maybe
five of these steps, which ended
		
00:00:32 --> 00:00:36
			up with schedule development,
where we have managed to develop a
		
00:00:36 --> 00:00:39
			schedule, calculate the early
start, early finish, late start
		
00:00:39 --> 00:00:42
			and late finish, total float and
free float for different
		
00:00:42 --> 00:00:45
			activities. And now that we have a
schedule, we have to put it to
		
00:00:45 --> 00:00:50
			work, and we have to see whether
it's feasible or not, and we have
		
00:00:50 --> 00:00:53
			to maintain and update the
schedule, as we have already
		
00:00:53 --> 00:00:56
			mentioned in class. We have while
developing the schedule, we have
		
00:00:56 --> 00:01:01
			to develop a schedule maintenance
for management plan. This schedule
		
00:01:01 --> 00:01:04
			management plan basically says,
how often are we going to update
		
00:01:04 --> 00:01:08
			the schedule? How are we going to
update the schedule? In some
		
00:01:08 --> 00:01:11
			cases, this is mandated by the
contract where the contractor has
		
00:01:11 --> 00:01:15
			to submit, at the end of each
month with the progress report, an
		
00:01:15 --> 00:01:18
			updated schedule reflecting the
current status of the project. And
		
00:01:18 --> 00:01:21
			in some cases, the contractor
would take that initiative on his
		
00:01:21 --> 00:01:24
			or her own, because they want to
make sure that the schedule that
		
00:01:24 --> 00:01:28
			they have developed is feasible
and practical at the same time,
		
00:01:28 --> 00:01:31
			and they want to know at each
point in time, at any point in
		
00:01:31 --> 00:01:35
			time, where are they compared to
their baseline or their
		
00:01:35 --> 00:01:39
			established approved schedule. So
the topic today that we're going
		
00:01:39 --> 00:01:44
			to talk about is how to update the
schedule and keep it in a proper
		
00:01:44 --> 00:01:44
			shape.
		
00:01:45 --> 00:01:49
			So schedule development serves two
major tasks. The first one is
		
00:01:49 --> 00:01:52
			planning and control. So we want
to know what are we going to do,
		
00:01:52 --> 00:01:55
			and then while we are performing
the project, we want to know
		
00:01:55 --> 00:01:58
			whether we are doing it as planned
or not. So that's the planning and
		
00:01:58 --> 00:02:02
			control aspects of schedule
development in time planning
		
00:02:02 --> 00:02:06
			schedule is developed to establish
a baseline or benchmark to be
		
00:02:06 --> 00:02:09
			monitored and controlled during
the project execution. This is
		
00:02:09 --> 00:02:12
			what we're going to call the
baseline schedule, which is going
		
00:02:12 --> 00:02:16
			to be an approved document. Once
it's approved by the owner, it
		
00:02:16 --> 00:02:20
			becomes sort of a contractual
document that the contractor and
		
00:02:20 --> 00:02:24
			the owner are going to be bound to
so in project control, the actual
		
00:02:24 --> 00:02:28
			performance is compared to the
baseline. And once we make that
		
00:02:28 --> 00:02:32
			comparison, which is what we call
control monitoring and control,
		
00:02:32 --> 00:02:34
			we're going to monitor the
progress. And then in case of any
		
00:02:34 --> 00:02:39
			deviation from the plan or the
baseline, we need to know how much
		
00:02:39 --> 00:02:43
			is that deviation. Why did it
happen? We have to analyze the
		
00:02:43 --> 00:02:47
			root cause and find out solutions
and try to make sure that the
		
00:02:47 --> 00:02:50
			problems that occurred in the past
do not keep perpetuating and
		
00:02:50 --> 00:02:54
			repeating it themselves in the
future. So the scheduler compares
		
00:02:54 --> 00:02:57
			the actual performance with the
baseline performance to discern
		
00:02:57 --> 00:03:01
			any deviation, not just for
preparation and presentation to
		
00:03:01 --> 00:03:04
			the owner before commencement of
the work, and not just as a
		
00:03:04 --> 00:03:08
			satisfaction of contractual
requirements, but primarily to
		
00:03:08 --> 00:03:12
			keep the project under control and
maintain its major milestones, to
		
00:03:12 --> 00:03:15
			make sure the project is not
slipping gradually.
		
00:03:17 --> 00:03:21
			So in case of deviation from the
baseline, and this is almost
		
00:03:21 --> 00:03:24
			always going to happen. I have
personally not seen any project
		
00:03:24 --> 00:03:28
			finishing exactly as planned.
There's always going to be some
		
00:03:28 --> 00:03:30
			fine tuning to that plan. There's
going to be some deviation from
		
00:03:30 --> 00:03:34
			the plan, whether it's based on
uncontrollable conditions, which
		
00:03:34 --> 00:03:38
			is what we called in class force
majeure, or something beyond the
		
00:03:38 --> 00:03:41
			control of all the contractual
parties, or it might be due to
		
00:03:41 --> 00:03:47
			some mistake or fault, due to
action or inaction by any of the
		
00:03:47 --> 00:03:50
			contractual parties, whether it's
the owner, the contractor or the
		
00:03:50 --> 00:03:54
			Arctic engineer, the construction
manager, subcontractors and so on
		
00:03:54 --> 00:03:58
			and so forth. It could be
unexpected soil conditions, it
		
00:03:58 --> 00:04:01
			could be inclement weather. It
could be Equipment Breakdown, so
		
00:04:01 --> 00:04:05
			many different factors that can
lead to deviation from the
		
00:04:05 --> 00:04:09
			baseline schedule. So the manager,
the project manager, needs to know
		
00:04:09 --> 00:04:12
			where is the deviation in which
activity or which set of
		
00:04:12 --> 00:04:15
			activities, what's the cause of
that deviation, whether it's the
		
00:04:15 --> 00:04:19
			schedule initially was defective
in its initial assessment, or the
		
00:04:19 --> 00:04:23
			performance did not match the
expected production rates. For
		
00:04:23 --> 00:04:27
			example, what is the magnitude of
the deviation? Again, if we're
		
00:04:27 --> 00:04:29
			talking about a three year project
and we have a deviation of three
		
00:04:29 --> 00:04:33
			days, no big deal. We kind of
covered that very easily. But if
		
00:04:33 --> 00:04:37
			we're talking about a project with
a six month duration and we have
		
00:04:37 --> 00:04:40
			three weeks of delay, this is
really considerable.
		
00:04:41 --> 00:04:46
			So once we analyze the deviation
and we know its magnitude, what's
		
00:04:46 --> 00:04:49
			the required corrective action to
be taken? How can we correct that
		
00:04:49 --> 00:04:53
			mistake? Is it through filing a
claim for time extension, for
		
00:04:53 --> 00:04:56
			example? Is it through
acceleration of work, working
		
00:04:56 --> 00:04:59
			another shift or using bigger
equipment, using additional
		
00:04:59 --> 00:04:59
			resources?
		
00:05:00 --> 00:05:03
			So what kind of preventive action
should be taken to avoid
		
00:05:03 --> 00:05:06
			repetition of the causes of that
deviation, just to make sure that
		
00:05:06 --> 00:05:09
			we do not repeat the same
mistakes? And what is the end
		
00:05:09 --> 00:05:13
			forecast, if we keep progressing
at the same pace, are we going to
		
00:05:13 --> 00:05:16
			be able to finish on time? If it's
a non critical activity, are we
		
00:05:16 --> 00:05:19
			within our float so it does not
affect the schedule? If we are in
		
00:05:19 --> 00:05:22
			a critical activity, then
definitely it's going to affect
		
00:05:22 --> 00:05:26
			the schedule, and most
importantly, which is what you can
		
00:05:26 --> 00:05:29
			carry from one project to another,
is what are the lessons learned?
		
00:05:32 --> 00:05:36
			So this is this graph shows
basically a the project control
		
00:05:36 --> 00:05:40
			cycle, where we start planning, we
develop the project objectives, we
		
00:05:40 --> 00:05:44
			implement the project and keep
monitoring the performance, and
		
00:05:44 --> 00:05:50
			then we measure the progress on a
scheduled frequent basis, and then
		
00:05:50 --> 00:05:54
			we find what the root cause is of
any deviation, if any. And then we
		
00:05:54 --> 00:05:57
			implement the controls, whether
it's corrective action or
		
00:05:57 --> 00:06:02
			preventive action. And then we
update the project objectives, and
		
00:06:02 --> 00:06:06
			then we keep repeat the same cycle
again. We do that on a weekly
		
00:06:06 --> 00:06:10
			basis, bi monthly basis, monthly
basis. We need to keep doing that
		
00:06:10 --> 00:06:12
			as long as the project is
progressing.
		
00:06:15 --> 00:06:18
			Control means not only monitoring,
so monitoring is observing and
		
00:06:18 --> 00:06:22
			measuring, but what is the result
of that monitoring and observing?
		
00:06:22 --> 00:06:26
			It's the the decision that we're
going to make. So track. It's
		
00:06:26 --> 00:06:30
			taking the corrective measures
whenever and wherever necessary to
		
00:06:30 --> 00:06:34
			control is to compare. So we have
to have a baseline or a benchmark
		
00:06:34 --> 00:06:38
			to compare to. We have to have a
fixed target, and then we have to
		
00:06:38 --> 00:06:42
			have to have a moving object,
which is the schedule under
		
00:06:42 --> 00:06:46
			progress, we have to compare that
moving object to the to the fixed
		
00:06:46 --> 00:06:49
			target to know exactly how are we
performing.
		
00:06:52 --> 00:06:55
			So the baseline is also known as
the target schedule, as we just
		
00:06:55 --> 00:06:59
			mentioned, and it may be different
with as planned schedule. So we
		
00:06:59 --> 00:07:03
			keep updating that basically due
to contractual changes, for
		
00:07:03 --> 00:07:04
			example, that have
		
00:07:05 --> 00:07:08
			shown after we have signed the
contract and things like that.
		
00:07:08 --> 00:07:11
			It's going to be prepared by the
general contractor, usually to
		
00:07:11 --> 00:07:15
			incorporate all the sub schedule
develop schedules developed by the
		
00:07:15 --> 00:07:19
			subcontractors and suppliers. And
it has to be developed before the
		
00:07:19 --> 00:07:22
			start of the project, because, as
we mentioned in most of the cases,
		
00:07:22 --> 00:07:26
			this is going to be a contractual
document that everyone is going to
		
00:07:26 --> 00:07:29
			be using in the future. It's going
to be used for performance
		
00:07:29 --> 00:07:33
			comparison, and if approved by the
owner, it becomes a part of the
		
00:07:33 --> 00:07:34
			contract documents.
		
00:07:36 --> 00:07:39
			The updated schedule is the
schedule reflecting the actual
		
00:07:39 --> 00:07:42
			performance information. So this
is not the target schedule
		
00:07:42 --> 00:07:45
			anymore. Now we're moving. We're
talking about the moving object
		
00:07:45 --> 00:07:50
			that that vehicle that's moving
along, the project completion. It
		
00:07:50 --> 00:07:54
			includes the time of occurrence of
different activities, amount or
		
00:07:54 --> 00:07:59
			percentage of work completed, what
we call the PCT, and changes to
		
00:07:59 --> 00:08:03
			future work. So as a definition, a
revised schedule reflecting the
		
00:08:03 --> 00:08:07
			project information at a given
data date we're gone. That's the
		
00:08:07 --> 00:08:10
			data date, the measuring date
where we're gonna measure our
		
00:08:10 --> 00:08:14
			performance and decide how we're
doing regarding completed
		
00:08:14 --> 00:08:17
			activities in progress, activities
and changes in the logic, cost and
		
00:08:17 --> 00:08:22
			resources required and allocated
at any activity level, it reflects
		
00:08:22 --> 00:08:25
			the actual start and finish dates
for activities as well as the
		
00:08:25 --> 00:08:29
			percentage of completion PCT. So
these are at least three pieces of
		
00:08:29 --> 00:08:31
			information that we need to
collect during the monitoring
		
00:08:31 --> 00:08:34
			process. For the activities that
have started, what was their
		
00:08:34 --> 00:08:38
			actual start? If the activity is
complete, what was the actual
		
00:08:38 --> 00:08:41
			finish for that activity? And if
the activity has started, but it's
		
00:08:41 --> 00:08:44
			still in progress. It's not
complete yet. What is the percent
		
00:08:44 --> 00:08:47
			complete, or the percentage of
completion of that activity? And
		
00:08:47 --> 00:08:50
			we're going to see different ways
of measuring that percentage of
		
00:08:50 --> 00:08:51
			completion.
		
00:08:53 --> 00:08:57
			So the data date is also known as
the as of date schedule, date
		
00:08:57 --> 00:09:01
			status, date, update, date. All of
these are the same things talking
		
00:09:01 --> 00:09:05
			about the same concept, which is
the date as of which all progress
		
00:09:05 --> 00:09:09
			on the project is reported. It is
not the current date or the time
		
00:09:09 --> 00:09:15
			now, because, for example, today
might be March 10 or March 9, but
		
00:09:15 --> 00:09:20
			I based my schedule on an update
on or a cutoff date on March 5,
		
00:09:20 --> 00:09:21
			for example.
		
00:09:24 --> 00:09:26
			So some of the required
information that we need to
		
00:09:26 --> 00:09:30
			collect are the actual start,
which denotes the actual start
		
00:09:30 --> 00:09:33
			date of the activity obtained from
the construction site or from the
		
00:09:33 --> 00:09:36
			key performer of the activity. If
it's done in a shop by
		
00:09:36 --> 00:09:40
			subcontractor or supplier, they
are going to provide that provide
		
00:09:40 --> 00:09:43
			us with that actual start, and the
actual finish denotes the date by
		
00:09:43 --> 00:09:47
			which the activity is considered
to be complete, whether it's
		
00:09:47 --> 00:09:49
			substantial completion or
practical completion. This is
		
00:09:49 --> 00:09:53
			something to discuss a little bit
later, PCT or percent complete,
		
00:09:53 --> 00:09:56
			which applies to activities that
have an actual start. If it has
		
00:09:56 --> 00:09:59
			not started yet, then the Percent
Complete is zero. If the.
		
00:20:00 --> 00:20:00
			It 100%
		
00:20:01 --> 00:20:08
			if it is not complete, it is 0% so
if it has not started, 0% started
		
00:20:08 --> 00:20:11
			but not yet finished. Either I
give it an arbitrary amount or
		
00:20:11 --> 00:20:15
			start just give it zero or wait
until it's complete. And then in
		
00:20:15 --> 00:20:19
			this case, I'm going to count it
as 100% and this can be very
		
00:20:19 --> 00:20:23
			useful only for very short
activities with a very short
		
00:20:23 --> 00:20:23
			duration.
		
00:20:27 --> 00:20:30
			Another elaboration on the all or
nothing is the incremental
		
00:20:30 --> 00:20:34
			milestones. If I have, for
example, a large slab on grade,
		
00:20:34 --> 00:20:35
			and in that slab on grade, I have
		
00:20:37 --> 00:20:42
			some underground pipes and cables,
and I have rebar, and I have
		
00:20:42 --> 00:20:47
			concrete and so on, and I have
curing of that concrete. So if the
		
00:20:47 --> 00:20:53
			rebar is 50% complete, am I going
to consider it zero and wait until
		
00:20:53 --> 00:20:55
			it's 100% to call, to call, to
count it as 100%
		
00:20:56 --> 00:20:59
			that would be relatively unfair,
because this might be a long
		
00:20:59 --> 00:21:02
			activity with a long duration. So
it's used for activities that
		
00:21:02 --> 00:21:07
			contain a set of tasks or stages.
I can say, for example, that once
		
00:21:08 --> 00:21:12
			the four more for that slab on
grade is done, this is, let's say,
		
00:21:12 --> 00:21:12
			10%
		
00:21:13 --> 00:21:19
			once the underground utilities are
done. This is 50% once the rebar
		
00:21:19 --> 00:21:24
			is done. That's another 30% so
it's a total of 90% or 80% and
		
00:21:24 --> 00:21:28
			then once I have placed the
concrete, that's another 10% and
		
00:21:28 --> 00:21:31
			once I cure the concrete and I
remove the forms, then this is the
		
00:21:31 --> 00:21:35
			remaining amount, and that way I
can measure the progress of that
		
00:21:35 --> 00:21:39
			activity based on which subtasks
have been completed. So each stage
		
00:21:39 --> 00:21:43
			of a given activities assigned a
weight that's approximately equal
		
00:21:43 --> 00:21:47
			to its percentage share in the
effort in the total activity. Then
		
00:21:47 --> 00:21:52
			each stage is treated as all or
nothing. So if the rebar is not
		
00:21:52 --> 00:21:55
			complete, I'm not I'm going to
give it a zero. If it's complete,
		
00:21:55 --> 00:21:58
			I'm going to give it all of the
40% which is the weight of that
		
00:21:58 --> 00:21:59
			rebar and so on.
		
00:22:01 --> 00:22:04
			So here is an example of
incremental milestones a
		
00:22:04 --> 00:22:08
			contractor is installing. 25
doors. Four doors have not yet
		
00:22:08 --> 00:22:11
			been started, so percent complete
is 08.
		
00:22:12 --> 00:22:15
			Doors had their frames erected,
and we consider that the frame
		
00:22:15 --> 00:22:17
			erection for each door is 30% of
the work.
		
00:22:18 --> 00:22:22
			Six doors have been hung. We
consider hanging the doors is 50%
		
00:22:23 --> 00:22:27
			of the work. Four doors after
being hung have been painted, so
		
00:22:27 --> 00:22:31
			we consider that as 70% 75% of the
work. And then the last three
		
00:22:31 --> 00:22:35
			doors had all of the previous
steps completed, plus the hardware
		
00:22:35 --> 00:22:39
			also installed, which is remaining
25% so now these three doors are
		
00:22:39 --> 00:22:44
			100% complete. Now, if I want to
know what's the total progress of
		
00:22:44 --> 00:22:48
			that activity, of hanging these
and installing these 25 doors,
		
00:22:48 --> 00:22:53
			here's the example. So for the
activity not yet started, four
		
00:22:53 --> 00:22:56
			times zero is zero. We can
consider that the total weight is
		
00:22:56 --> 00:23:01
			25 which is 25 doors times 100
points for each door. So a total
		
00:23:01 --> 00:23:06
			is 2500 points. So for the doors
that have not been installed, it's
		
00:23:06 --> 00:23:10
			four times zero. So it's zero. For
the doors that have been
		
00:23:11 --> 00:23:16
			erected or manufactured, it's
eight doors, and that's 30%
		
00:23:18 --> 00:23:25
			so eight times 30, times 30,
that's going to give us 9.6%
		
00:23:26 --> 00:23:31
			or eight times 30, which, which is
240 points, compared to the 2500
		
00:23:31 --> 00:23:35
			points. That's 9.6% the doors that
have been already hung
		
00:23:36 --> 00:23:41
			six doors. So again, six times 50
because that's 50%
		
00:23:42 --> 00:23:47
			so that's a total of 300 points
divided by 2500 that's another 12%
		
00:23:48 --> 00:23:51
			the doors that have been painted
four doors times 75%
		
00:23:52 --> 00:23:58
			which is 75 points. So 300 points
divided by 2500 that's another 12%
		
00:23:58 --> 00:24:01
			and finally, three doors have been
completed. And these are 300
		
00:24:02 --> 00:24:06
			points, because it's 100% for
these three doors. So 300 divided
		
00:24:06 --> 00:24:11
			by 2500 that's another 12% so when
we add that total, it gives us a
		
00:24:11 --> 00:24:14
			percentage of completion for that
activity of installing the 25
		
00:24:15 --> 00:24:16
			doors of 45.6%
		
00:24:22 --> 00:24:25
			method number five is supervisors
opinion, and that's sort of
		
00:24:25 --> 00:24:29
			subjective, because the
supervisors or the superintendents
		
00:24:29 --> 00:24:32
			might have different opinions on
the progress of the activity. They
		
00:24:32 --> 00:24:35
			might think that the hard part has
already passed and what's left is
		
00:24:36 --> 00:24:39
			quite easy work, so they might
give a higher percentage of
		
00:24:39 --> 00:24:44
			completion. No other method can be
suited, it's going to be used if
		
00:24:44 --> 00:24:47
			no other method can be suited,
suitably applied only in this
		
00:24:47 --> 00:24:51
			case, and it relies totally on the
foreman or superintendent's
		
00:24:51 --> 00:24:55
			judgment. So it's most convenient,
because it's easy to obtain, but
		
00:24:55 --> 00:24:59
			it might be the least accurate
because it's, again, a subjective,
		
00:24:59 --> 00:24:59
			uh.
		
00:30:00 --> 00:30:03
			By the fifth day of the month, the
general contractor is going to
		
00:30:03 --> 00:30:07
			list all the activities that had
that had work done on them since
		
00:30:07 --> 00:30:10
			the previous period. We're going
to say this month we have worked
		
00:30:10 --> 00:30:10
			on 12345,
		
00:30:11 --> 00:30:15
			and this is the these are the
actual dates, and these are the
		
00:30:15 --> 00:30:19
			percentage of completion for each
activity that's going to include
		
00:30:19 --> 00:30:22
			the actual start, actual finished,
percent complete and original
		
00:30:22 --> 00:30:26
			budget, cost to this of this
period, cost to date and cost to
		
00:30:26 --> 00:30:28
			complete what's the left, the
remaining cost to complete that
		
00:30:28 --> 00:30:33
			activity, and the general
contractor and the subcontractor
		
00:30:33 --> 00:30:36
			have to concur on percent
complete. So again, if you have a
		
00:30:36 --> 00:30:39
			subcontractor that submitted this
information to you, you have to
		
00:30:39 --> 00:30:43
			agree with the subcontractor. So
only 1% complete is going to be
		
00:30:43 --> 00:30:47
			submitted, and it's usually going
to be on the conservative side. So
		
00:30:47 --> 00:30:51
			if the subcontractor says it's 75%
and you, as a GC, say, No, it's
		
00:30:51 --> 00:30:55
			only 70% what you're going to
submit is the 70% not the 75 the
		
00:30:57 --> 00:31:00
			report is going to be reviewed and
verified by the owner or the
		
00:31:00 --> 00:31:04
			owner's representative, the Arctic
engineer, for example, or the
		
00:31:04 --> 00:31:07
			construction manager for the
owner. And they're going to check
		
00:31:07 --> 00:31:09
			the completed quantity. They're
going to ensure that these
		
00:31:09 --> 00:31:13
			quantities have been completed
properly according to the specs
		
00:31:13 --> 00:31:16
			and they've been accepted. They're
going to review the unit prices as
		
00:31:16 --> 00:31:20
			per the bid price, and the totals
are going to be calculated in the
		
00:31:20 --> 00:31:24
			payment request. The payment
request can be approved as is, if
		
00:31:24 --> 00:31:28
			there's no disagreement between
the client and the contractor, or
		
00:31:28 --> 00:31:31
			approved with some numbers this
approved. So we're gonna hold on
		
00:31:31 --> 00:31:34
			on these numbers. We're not we're
going to investigate them a little
		
00:31:34 --> 00:31:37
			more, but in order not to delay
the whole payment, we're going to
		
00:31:37 --> 00:31:40
			set them aside and give you the
release for the approved amount,
		
00:31:40 --> 00:31:43
			or totally rejected and sent for
resubmit if there are some
		
00:31:43 --> 00:31:47
			erroneous quantities or erroneous
calculations or disagreement on
		
00:31:47 --> 00:31:50
			conceptual issues in that payment,
it might be returned to the
		
00:31:50 --> 00:31:54
			contractor for review and
resubmittal, and the schedule of
		
00:31:54 --> 00:31:58
			values must be updated with the
cost of any change orders to
		
00:31:58 --> 00:32:02
			reflect that the new unit price Is
is this and not the old one in the
		
00:32:02 --> 00:32:03
			bit?
		
00:32:04 --> 00:32:07
			And basically, this is the end of
this lecture talking about
		
00:32:07 --> 00:32:12
			schedule updating. I hope now, by
now, you know what scheduled
		
00:32:12 --> 00:32:15
			updating means and how it's going
to be used to maintain the project
		
00:32:16 --> 00:32:19
			schedule. Thank you and see you in
the next lecture. Bye, bye.