Ihab Saad – Example on Schedule Compression

Ihab Saad
Share Page

AI: Summary ©

The speakers discuss the maximum compressible time for a network, using a table and calculations based on various variables. They explain the process of compressing a network and identifying critical and effective activities, emphasizing the importance of starting with the lowest cost activity and compressing all critical paths by the same amount to achieve maximum savings. The speakers also discuss reducing duration by two days while still saving some money, compressing all paths by the same amount, and being still critical. The projects are designed to compress all paths by the same amount, and the projects are still critical.

AI: Summary ©

00:00:05 --> 00:00:09
			Music. Hello again. Now we start
talking about an example on
		
00:00:10 --> 00:00:13
			network compression based on what
we have learned so far about which
		
00:00:13 --> 00:00:17
			activities to compress and how to
achieve time reduction or time
		
00:00:17 --> 00:00:22
			acceleration. So here we have an
example calculate the normal least
		
00:00:22 --> 00:00:26
			cost and crash durations for the
following project, and calculate
		
00:00:26 --> 00:00:30
			the cost associated with each
duration, whereas indirect costs
		
00:00:30 --> 00:00:35
			are $120 per day. So the costs
given here in this table are
		
00:00:35 --> 00:00:38
			basically direct cost for each
activity. It shows the activity,
		
00:00:38 --> 00:00:42
			its immediate predecessor, normal
duration and crash duration, which
		
00:00:42 --> 00:00:46
			which shows the amount of
compressibility that the activity
		
00:00:46 --> 00:00:51
			has, in addition to the cost,
normal cost and crash cost, how
		
00:00:51 --> 00:00:54
			much would it cost to compress
this activity by that amount of
		
00:00:54 --> 00:00:57
			time? So for example, activity A
can be compressed by one day,
		
00:00:57 --> 00:01:01
			which is the difference between
the normal and the crash duration
		
00:01:01 --> 00:01:05
			at an extra cost of $100 which is
the difference between the crash
		
00:01:05 --> 00:01:09
			cost and the normal cost. And we
have that for all the activities.
		
00:01:09 --> 00:01:13
			Notice here, for example, that
activity f has a normal duration
		
00:01:13 --> 00:01:17
			of four days and a crash duration
of also four days, which makes
		
00:01:17 --> 00:01:21
			delta T for activity f equal to
zero. Therefore activity f is
		
00:01:21 --> 00:01:26
			incompressible. If activity f ends
up being a critical activity, it
		
00:01:26 --> 00:01:30
			would be excluded from our efforts
to compress that activity, because
		
00:01:30 --> 00:01:34
			it is, it is incompressible in the
first place. Same thing applies
		
00:01:34 --> 00:01:38
			here to the delta C. It doesn't
have any delta cost because,
		
00:01:38 --> 00:01:42
			again, it cannot be compressed. So
our first step is looking at this
		
00:01:42 --> 00:01:47
			table, first of all, building the
network, and then looking at the
		
00:01:47 --> 00:01:50
			delta t and delta c and the cost
slope for the different
		
00:01:50 --> 00:01:51
			activities.
		
00:01:53 --> 00:01:56
			The total direct cost for this
project can be obtained by adding
		
00:01:56 --> 00:01:59
			the normal cost for all
activities, which is equal to
		
00:01:59 --> 00:01:59
			$4,950
		
00:02:01 --> 00:02:05
			which is basically the sum of
these costs here normal adding
		
00:02:05 --> 00:02:08
			these costs, that's going to add
up to 4950,
		
00:02:10 --> 00:02:13
			the total indirect costs can be
obtained only by solving the
		
00:02:13 --> 00:02:17
			network and multiplying the total
duration by the indirect cost per
		
00:02:17 --> 00:02:18
			day, which again is $120
		
00:02:19 --> 00:02:22
			per day. Therefore we have to
perform the forward pass, backward
		
00:02:22 --> 00:02:27
			pass, and determine the expected
early finish of that network.
		
00:02:27 --> 00:02:31
			Multiply that time, the number of
days by 120 and that will give us
		
00:02:31 --> 00:02:34
			the total indirect cost for this
project before compression.
		
00:02:36 --> 00:02:39
			So here's our network that we have
drawn based on the information
		
00:02:39 --> 00:02:44
			with the IPAS and so on, and it
shows basically
		
00:02:45 --> 00:02:49
			several paths. Here's one path,
here's a second path, here's a
		
00:02:49 --> 00:02:53
			third path, and here's the fourth
path. So we have four paths to
		
00:02:53 --> 00:03:01
			this network, A, B, E, H, A, C, E,
H, A, C, F, G, and ADG. These are
		
00:03:01 --> 00:03:03
			the four different paths to this
network.
		
00:03:05 --> 00:03:07
			So the next step is to perform our
calculations.
		
00:03:09 --> 00:03:13
			And here's a very simple display
of these calculations. It shows
		
00:03:13 --> 00:03:17
			the early start for activity is
zero, duration five days, so the
		
00:03:17 --> 00:03:21
			early finish is zero, is five and
so on. So it's a very simple
		
00:03:21 --> 00:03:25
			calculation of the network time
which shows that this project is
		
00:03:25 --> 00:03:26
			going to end on day 25
		
00:03:27 --> 00:03:31
			therefore this this network
expected to finish on day 25 has
		
00:03:31 --> 00:03:37
			one critical path which is going
to be A, C, E, H, as it appears
		
00:03:37 --> 00:03:41
			from The identical numbers on the
early and late sites,
		
00:03:42 --> 00:03:46
			and the total indirect cost is 25
times 120
		
00:03:47 --> 00:03:51
			25 days times 125 $20 per day.
With a total of $3,000
		
00:03:52 --> 00:03:56
			we had already calculated the
direct cost to be 4950 so the
		
00:03:56 --> 00:04:01
			total cost for this project before
compression is 79 $50
		
00:04:05 --> 00:04:08
			and here it shows the critical
path that we talked about.
		
00:04:11 --> 00:04:16
			So the next step is to draw the
table to show the delta t, the
		
00:04:16 --> 00:04:20
			delta c, the cost slope for the
different activities.
		
00:04:21 --> 00:04:25
			And here's the duration for each
path, A, B, E, h. Now the duration
		
00:04:25 --> 00:04:30
			for each path is assuming that the
other paths do not exist. So if,
		
00:04:30 --> 00:04:35
			for example, C did not exist,
activity c did not exist, then the
		
00:04:35 --> 00:04:39
			start date for activity e would
have been 12. The start date for
		
00:04:39 --> 00:04:42
			activity h would have been 18, and
the completion date would have
		
00:04:42 --> 00:04:48
			been 24 Same thing here, if the
two top paths did not exist, or
		
00:04:48 --> 00:04:53
			three top paths did not exist, and
we had on the ADG, then activity G
		
00:04:53 --> 00:04:58
			would start on day 16 and end on
day 23 and the project would end
		
00:04:58 --> 00:04:59
			on day 23 that's how we.
		
00:05:00 --> 00:05:01
			Determine the length of each path.
		
00:05:06 --> 00:05:11
			Here's the table. Based on the
calculations of the crash and
		
00:05:11 --> 00:05:14
			normal durations and crash and
normal costs, we obtain the cost
		
00:05:14 --> 00:05:17
			slope, which is the difference in
cost divided by the difference in
		
00:05:17 --> 00:05:22
			time. So for the first activity,
100 divided by one for B, 150
		
00:05:22 --> 00:05:26
			divided by two and so on. And we
find, again, we remind that
		
00:05:26 --> 00:05:30
			activity f is incompressible. Now
the ones in red are the critical
		
00:05:30 --> 00:05:33
			activities. So these are our
primary candidates for
		
00:05:33 --> 00:05:39
			compression. They have to be
critical compressible effective
		
00:05:39 --> 00:05:42
			and among the critical,
compressive and effective
		
00:05:42 --> 00:05:46
			activities, we will select the one
with the lowest cost low going
		
00:05:46 --> 00:05:49
			back to this network here, we find
that we do not have any start to
		
00:05:49 --> 00:05:52
			start or any finish to finish
relationships. It's a very simple
		
00:05:52 --> 00:05:56
			network with all finish to start
relationships. Therefore all the
		
00:05:56 --> 00:06:00
			critical activities are effective
in compressing the project
		
00:06:00 --> 00:06:05
			duration, none of the critical
activities are not none is
		
00:06:05 --> 00:06:08
			incompressible. Therefore, again,
all the critical activities are
		
00:06:08 --> 00:06:12
			candidates. So the main criteria
in determining which activity to
		
00:06:12 --> 00:06:14
			start with is going to be the cost
slope.
		
00:06:15 --> 00:06:18
			So looking at this table here, we
look at the critical activities
		
00:06:18 --> 00:06:22
			and the cost slopes. Activity A
has 100 day, $100 per day.
		
00:06:23 --> 00:06:28
			Activity C, $40 per day. E, $50
per day and age, $120
		
00:06:29 --> 00:06:33
			per day. Therefore, looking at
this, we found out, find out that
		
00:06:33 --> 00:06:38
			activity c is the least expensive
to compress, so this is going to
		
00:06:38 --> 00:06:39
			be our primary candidate for
compression.
		
00:06:42 --> 00:06:45
			And that is compression cycle
number one, we're going to conduct
		
00:06:45 --> 00:06:48
			these compressions in different
cycles, as I mentioned several
		
00:06:48 --> 00:06:53
			times before, the time compression
or network compression problem is
		
00:06:53 --> 00:06:56
			not a hard problem at all. The
concept is very simple. It's just
		
00:06:56 --> 00:06:59
			a repetitive calculation of the
forward and the backward paths
		
00:06:59 --> 00:07:03
			after each cycle of compression,
compressing each activity by one
		
00:07:03 --> 00:07:07
			day at a time, and then
recalculating the dates for the
		
00:07:07 --> 00:07:12
			network. So in cycle one compress
activity c by one day. Now we
		
00:07:12 --> 00:07:14
			notice that looking at the network
again,
		
00:07:16 --> 00:07:18
			look at the total float on
activity B,
		
00:07:19 --> 00:07:24
			13 and 12. So the total float for
this activity is only one day,
		
00:07:24 --> 00:07:28
			which means if I reduce the
duration of this activity by one
		
00:07:28 --> 00:07:32
			day, if I end this activity on day
12,
		
00:07:33 --> 00:07:36
			going in the backward pass, we're
going to find out that the late
		
00:07:36 --> 00:07:40
			finish for activity B is going to
become 12, which means activity B
		
00:07:40 --> 00:07:44
			is going to lose its first day, or
its only day of total float, which
		
00:07:44 --> 00:07:47
			is going to make it a critical
activity. So we're going to create
		
00:07:47 --> 00:07:52
			a new critical path going through
A, B, E, H.
		
00:07:57 --> 00:08:02
			So this is the first cycle
activity c is compressed, and B
		
00:08:02 --> 00:08:07
			will become critical with the cost
of compression is going to be $40
		
00:08:07 --> 00:08:11
			therefore, to proceed with the
second cycle, we have to check the
		
00:08:11 --> 00:08:14
			cost slopes of activities to be
compressed. Remember that in order
		
00:08:14 --> 00:08:17
			to achieve an effective
compression of more than one
		
00:08:17 --> 00:08:20
			critical path, we must compress
all critical paths by the same
		
00:08:20 --> 00:08:24
			amount. So if we have multiple
critical paths that need to be
		
00:08:24 --> 00:08:25
			compressed, it's
		
00:08:26 --> 00:08:29
			not enough to compress only one of
them, because if you compress one
		
00:08:29 --> 00:08:32
			and leave the others incompressed
or uncompressed, that would make
		
00:08:32 --> 00:08:35
			them longer, and they would remain
critical, whereas the one that has
		
00:08:35 --> 00:08:38
			been compressed is not critical
anymore. So in order to achieve
		
00:08:38 --> 00:08:42
			that compression, we have to
compress all the critical paths by
		
00:08:42 --> 00:08:45
			exactly the same amount, and this
can be achieved either by
		
00:08:45 --> 00:08:49
			compressing one activity on each
one of these paths by the same
		
00:08:49 --> 00:08:53
			amount, or looking for a common
activity that is shared by all of
		
00:08:53 --> 00:08:56
			these critical paths, and
compressing this activity, which
		
00:08:56 --> 00:09:01
			is going to result in a complete
In a compression for all the
		
00:09:01 --> 00:09:02
			existing critical paths,
		
00:09:05 --> 00:09:10
			the net cost of compression here
is savings of $80 why? Because we
		
00:09:10 --> 00:09:14
			have spent an extra 80 $40 to
compress activity C, but at the
		
00:09:14 --> 00:09:18
			same time, we reduced the total
project duration by one day, which
		
00:09:18 --> 00:09:21
			saved us $120 in indirect costs.
		
00:09:23 --> 00:09:27
			And here's the calculation after
the first cycle of compression.
		
00:09:27 --> 00:09:32
			Notice that each cycle is going to
be done in a different color, so
		
00:09:32 --> 00:09:36
			that we can identify which
activities have been affected and
		
00:09:36 --> 00:09:37
			which dates have changed.
		
00:09:40 --> 00:09:44
			So here, when we compress activity
C from eight to seven, perform the
		
00:09:44 --> 00:09:50
			calculations in the backward pass
here I have activity B with zero
		
00:09:50 --> 00:09:51
			total float.
		
00:09:55 --> 00:09:58
			Therefore now we have a new
critical path in addition to the
		
00:09:58 --> 00:09:59
			old one. So AC.
		
00:10:00 --> 00:10:04
			Eh is still critical and now a, b,
eh has become another critical
		
00:10:04 --> 00:10:04
			path.
		
00:10:14 --> 00:10:19
			Now let's look at the other paths.
We notice here that activity G has
		
00:10:19 --> 00:10:24
			a total float of only one day, so
does activity f and also so does
		
00:10:24 --> 00:10:26
			activity D. Therefore,
		
00:10:27 --> 00:10:31
			any additional compression to this
path more likely is going to
		
00:10:31 --> 00:10:36
			result in these activities
becoming critical, except if we
		
00:10:36 --> 00:10:39
			compress activity A, because
compressing activity A is going to
		
00:10:39 --> 00:10:43
			affect all the paths so the non
critical activities are going to
		
00:10:43 --> 00:10:47
			keep their total float. So now
let's look again at the cost of
		
00:10:47 --> 00:10:52
			compression. In order to compress
this path, these two paths at the
		
00:10:52 --> 00:10:55
			same time by the same amount, we
can either compress activity A by
		
00:10:55 --> 00:10:58
			itself because it's joined between
the two, or we can compress
		
00:10:58 --> 00:11:03
			activity e by itself, or we can
compress activity h by itself,
		
00:11:03 --> 00:11:10
			therefore A or B and C together,
or H by itself, or or E by itself,
		
00:11:10 --> 00:11:13
			or H by itself. Let's look at the
cost for this compression.
		
00:11:16 --> 00:11:19
			So we find that activity c is
still the least expensive,
		
00:11:20 --> 00:11:26
			followed by E, followed by a,
followed by h. Now if I want to
		
00:11:26 --> 00:11:30
			compress C, I have also to
compress B at the same time.
		
00:11:30 --> 00:11:33
			Therefore the cost of compressing
one extra day is going to be 40
		
00:11:33 --> 00:11:38
			plus 75 that would be 115 to
achieve that compression. Or
		
00:11:38 --> 00:11:42
			another option is to compress
activity e by itself, or to
		
00:11:42 --> 00:11:46
			compress activity A by itself, or
activity h by itself. So
		
00:11:52 --> 00:11:55
			based on the information from
cycle one, the least expensive
		
00:11:55 --> 00:11:59
			activity to compress is activity
e, again, from here, from this
		
00:11:59 --> 00:12:03
			table, this activity, this
expensive activity to compress, is
		
00:12:03 --> 00:12:08
			activity e, with a cost of $50
this result in converting all the
		
00:12:08 --> 00:12:11
			activities on the network into
critical activities, because,
		
00:12:11 --> 00:12:14
			again, all their meaning
activities had only one day of
		
00:12:14 --> 00:12:17
			total float. Once we compressed
activity e, all of these non
		
00:12:17 --> 00:12:20
			critical activities will lose that
total float, thus becoming
		
00:12:20 --> 00:12:24
			critical. And the net cost of this
compression is a saving of $70
		
00:12:25 --> 00:12:30
			because again, we spent an extra
$50 we saved 120 so the net is
		
00:12:30 --> 00:12:32
			savings of $70
		
00:12:36 --> 00:12:39
			and now we can see the new
numbers, and it shows clearly that
		
00:12:39 --> 00:12:41
			all the other activities have
become critical.
		
00:12:43 --> 00:12:45
			So here's the original critical
path,
		
00:12:46 --> 00:12:48
			here's the second critical path,
		
00:12:49 --> 00:12:54
			and here's the third critical
path, each one shown in a
		
00:12:54 --> 00:12:58
			different color that shows when
did these activities become
		
00:12:58 --> 00:13:01
			critical? That's very important,
again, as we mentioned before, to
		
00:13:01 --> 00:13:05
			use different colors, so that we
do not lose track of these changes
		
00:13:05 --> 00:13:10
			and which activity was changed at
which cycle and so on and so
		
00:13:10 --> 00:13:10
			forth.
		
00:13:11 --> 00:13:16
			Now the project ends on day 23 so
we have managed to reduce the
		
00:13:16 --> 00:13:20
			duration by two days while still
saving some money, which is good.
		
00:13:24 --> 00:13:25
			Our next step,
		
00:13:26 --> 00:13:28
			again, all the activities now are
critical,
		
00:13:29 --> 00:13:32
			so we need to look at which
activities need to be compressed.
		
00:13:33 --> 00:13:38
			In order to compress this network,
again, the options are, I have to
		
00:13:38 --> 00:13:39
			compress
		
00:13:40 --> 00:13:44
			all the paths by the same amount.
So it's either compressing, for
		
00:13:44 --> 00:13:53
			example, H with G or E with G, or
B and C together with D and G,
		
00:13:53 --> 00:13:57
			because D is on the separate path
from G. So remember that we have
		
00:13:57 --> 00:14:03
			three paths. So it's either B, C,
G and D together, or
		
00:14:04 --> 00:14:10
			E, G and D together, or H, G and D
together, because f is
		
00:14:10 --> 00:14:15
			incompressible. Or maybe looking
at activity A, which is the common
		
00:14:15 --> 00:14:18
			activity in all paths, if we
compress activity A, that might
		
00:14:18 --> 00:14:20
			end up being less expensive.
		
00:14:21 --> 00:14:23
			So looking at the cost A by
itself, is 100
		
00:14:24 --> 00:14:28
			B, C, with any other activity,
that activity that already exceeds
		
00:14:28 --> 00:14:30
			the 100. So that's not our choice.
		
00:14:32 --> 00:14:36
			Therefore, we find out that the
cheapest activity to be compressed
		
00:14:36 --> 00:14:37
			is going to be activity A.
		
00:14:40 --> 00:14:44
			Since we now have four critical
paths, compressing the network
		
00:14:44 --> 00:14:48
			requires compressing all the paths
by the same amount. This can be
		
00:14:48 --> 00:14:51
			achieved by compressing at least
one activity on each path. And
		
00:14:51 --> 00:14:56
			again, here it shows the analysis
of the costs together. So by
		
00:14:56 --> 00:14:59
			compressing activity a one day,
the net cost would.
		
00:15:00 --> 00:15:04
			Be a savings of $20 because the
extra cost is $100 and the savings
		
00:15:04 --> 00:15:05
			of $120
		
00:15:07 --> 00:15:13
			now look at these numbers, 165,
202 70 and so on. That is more
		
00:15:13 --> 00:15:18
			than the 120 that I'm going to be
ending up saving. Therefore, if I
		
00:15:18 --> 00:15:23
			compress, after compressing
activity A, if I try to compress
		
00:15:23 --> 00:15:26
			any other activities, that's going
to be on the more expensive side,
		
00:15:26 --> 00:15:29
			because that's going to end up
costing me more money. So I'm not
		
00:15:29 --> 00:15:32
			saving any money by reducing the
duration. I'm actually spending
		
00:15:32 --> 00:15:33
			more money.
		
00:15:37 --> 00:15:41
			And here, once we have compressed
activity A, all the activities are
		
00:15:41 --> 00:15:43
			still critical,
		
00:15:49 --> 00:15:51
			and now we end the project on day
22
		
00:15:55 --> 00:15:58
			so here it shows the different
compression cycles that We have
		
00:15:58 --> 00:16:01
			done and which activities became
critical when
		
00:16:08 --> 00:16:10
			now the question is, where to
stop? Are we going to keep
		
00:16:11 --> 00:16:14
			compressing this network? Or
should we stop here? And the
		
00:16:14 --> 00:16:18
			answer to this question depends on
what's the objective we need to
		
00:16:18 --> 00:16:22
			achieve if we need to compress the
network to the maximum. It is
		
00:16:22 --> 00:16:27
			still compressible, because again,
we can compress B and C and D and
		
00:16:27 --> 00:16:30
			G, for example, at the same time,
and that's going to result in
		
00:16:30 --> 00:16:31
			another day of compression.
		
00:16:34 --> 00:16:38
			So we can do that, but that's
going to be, as we have already
		
00:16:38 --> 00:16:41
			noticed, it's going to be on the
more expensive side, because we
		
00:16:41 --> 00:16:43
			are not saving any money by doing
that, we are spending more money
		
00:16:44 --> 00:16:47
			if we need to compress the network
until it's not economically wise,
		
00:16:47 --> 00:16:51
			so compress it any further, then
we have to stop here, because
		
00:16:51 --> 00:16:55
			against compressing further is
going to result in more expenses,
		
00:16:55 --> 00:16:59
			and that's not economically
meaning. If we need to compress
		
00:16:59 --> 00:17:02
			the network by a certain number of
days. Let's say we all we wanted
		
00:17:02 --> 00:17:05
			to do is compress the network by
three days. We have already
		
00:17:05 --> 00:17:09
			achieved that. So here we can
stop. So it depends on how the
		
00:17:09 --> 00:17:12
			question is being asked. So the
question can be asked as compress
		
00:17:12 --> 00:17:16
			the network to the maximum
regardless of the cost. In this
		
00:17:16 --> 00:17:19
			case, we would keep compressing or
compressing it. Compress the
		
00:17:19 --> 00:17:22
			network until it's not
economically feasible or
		
00:17:22 --> 00:17:25
			meaningful to compress it any
further, which means we're going
		
00:17:25 --> 00:17:30
			to stop as soon as the savings are
not achieved, which means the cost
		
00:17:30 --> 00:17:34
			of compression exceeds the savings
resulted from reduction in
		
00:17:34 --> 00:17:39
			indirect costs or compressed by a
certain number of days. As soon as
		
00:17:39 --> 00:17:42
			we reach that number of days we
are going to start, we're going to
		
00:17:42 --> 00:17:43
			stop our conversion.
		
00:17:45 --> 00:17:48
			And this is basically a graphical
representation of that concept.
		
00:17:48 --> 00:17:53
			Here we have the direct cost
curve, which shows that the
		
00:17:53 --> 00:17:58
			shorter the duration, the higher
the cost of direct costs. Here's
		
00:17:58 --> 00:18:00
			the indirect cost, which shows the
opposite, the shorter the
		
00:18:00 --> 00:18:04
			duration, the lower the indirect
cost. And then here's the sum of
		
00:18:04 --> 00:18:07
			the two curves together. It's
adding the numbers from the two
		
00:18:07 --> 00:18:09
			curves together. It shows that for
a certain portion,
		
00:18:11 --> 00:18:12
			as you compress,
		
00:18:13 --> 00:18:16
			the total cost goes down, which is
what we have been doing so far,
		
00:18:17 --> 00:18:19
			and then you reach a certain
point, and the cost starts rising
		
00:18:19 --> 00:18:20
			up again.
		
00:18:21 --> 00:18:25
			So this is where we had stopped
originally, right now in this
		
00:18:25 --> 00:18:30
			problem. And this is going to be
called the right side of the total
		
00:18:30 --> 00:18:34
			cost curve. And this is the left
side of the total cost curve. On
		
00:18:34 --> 00:18:39
			the right side of the total cost
curve, the indirect cost is more
		
00:18:39 --> 00:18:44
			effective. So with the reduction,
the total curve trend follows the
		
00:18:44 --> 00:18:47
			same trend as the indirect cost,
which is reduction as you
		
00:18:47 --> 00:18:53
			compress. On the left hand side,
the curve, the total cost follows
		
00:18:53 --> 00:18:57
			the curve or the trend of the
direct cost. As we compress, the
		
00:18:57 --> 00:19:01
			total cost goes up so again, until
we reach a certain point where we
		
00:19:01 --> 00:19:06
			cannot compress anymore. So this
is basically in a nutshell how we
		
00:19:06 --> 00:19:10
			can achieve network compression or
time acceleration.
		
00:19:11 --> 00:19:15
			I hope this helps you understand
the concept and you can practice
		
00:19:15 --> 00:19:18
			on some additional problems. Thank
you and see you later. You.