WEBVTT

00:02:32.718 --> 00:02:36.670
<v Amy>Off the list so that we shouldn't have</v>

00:02:36.670 --> 00:02:40.660
any potential risks and
the need for a PSPS here.

00:02:40.660 --> 00:02:44.860
And so I think the PSPS
specific plan, hopefully,

00:02:44.860 --> 00:02:47.030
kind of guided or could guide you

00:02:47.030 --> 00:02:49.920
or give you insight into
our thought process there.

00:02:49.920 --> 00:02:51.603
I would say on the flip side,

00:02:53.658 --> 00:02:56.330
as far as whether or not
our grid hardening initiatives

00:02:56.330 --> 00:02:58.820
and how far we are along
and where we've deployed them

00:02:58.820 --> 00:03:00.233
impacts the decision-making.

00:03:01.787 --> 00:03:04.120
And I think the goal is to always mitigate

00:03:04.120 --> 00:03:07.240
the potential for PSPS as much as possible.

00:03:07.240 --> 00:03:11.010
And when we do have, once we've completed

00:03:11.010 --> 00:03:14.023
all the different grid
hardening activities in an area,

00:03:15.750 --> 00:03:18.770
the goal is to not need
the PSPS events anymore.

00:03:18.770 --> 00:03:22.190
Obviously, as things change
and our risk modeling changes,

00:03:22.190 --> 00:03:25.820
and climate changes, it doesn't
mean it always goes away,

00:03:25.820 --> 00:03:29.330
but at least the way we
know it now it should go away.

00:03:29.330 --> 00:03:32.620
Until you get to that point,
until we can make sure

00:03:32.620 --> 00:03:34.370
all the boxes are checked, if you will,

00:03:34.370 --> 00:03:36.350
and we've mitigated all
the different risk drivers

00:03:36.350 --> 00:03:40.080
in an area, it's challenging
to say you don't need it.

00:03:40.080 --> 00:03:43.780
And so that is where we start
to rely on our PSPS protocols.

00:03:43.780 --> 00:03:46.100
And I think there's a
decent amount of information

00:03:46.100 --> 00:03:47.940
in the filing and the other filings.

00:03:47.940 --> 00:03:49.990
But that's where a lot of
those weather thresholds

00:03:49.990 --> 00:03:54.280
come into play, is we are kind of looking,

00:03:54.280 --> 00:03:56.280
when we evaluate the
decision, we are looking at

00:03:56.280 --> 00:03:59.057
how far along are we in
our hardening activities?

00:03:59.057 --> 00:04:01.030
Are we complete? Are we not?

00:04:01.030 --> 00:04:02.623
Do risks still exist?

00:04:04.010 --> 00:04:05.630
So I'm hoping that kind of answered

00:04:05.630 --> 00:04:07.130
your two-fold question, Andie.

00:04:10.060 --> 00:04:11.557
<v Andie>Yeah, that was great.</v>

00:04:11.557 --> 00:04:12.390
Thank you so much.

00:04:12.390 --> 00:04:14.880
If we could get a response from Liberty,

00:04:14.880 --> 00:04:17.040
and also, specifically for Liberty is,

00:04:17.040 --> 00:04:19.760
I was wondering how you identified

00:04:19.760 --> 00:04:24.123
where to locate resiliency corridors as well.

00:04:25.910 --> 00:04:26.743
<v Dylan>Yeah. Thanks.</v>

00:04:26.743 --> 00:04:27.680
Those are good questions.

00:04:27.680 --> 00:04:30.030
So I'll address your
first two questions first.

00:04:31.430 --> 00:04:32.930
Primarily a lot of the initiatives

00:04:32.930 --> 00:04:35.404
that we're undertaking are brand new.

00:04:35.404 --> 00:04:38.670
We've got a couple of years of experience

00:04:38.670 --> 00:04:42.160
under our belt with how these
can really affect our system.

00:04:42.160 --> 00:04:45.710
What level of resiliency do you really get

00:04:45.710 --> 00:04:49.320
and risk prevention do you
really get from these initiatives

00:04:49.320 --> 00:04:52.200
is still really being evaluated.

00:04:52.200 --> 00:04:56.233
So, the PSPS risk isn't necessarily

00:04:56.233 --> 00:04:58.870
something that we've quantified yet.

00:04:58.870 --> 00:05:02.023
So I'm still speaking at a fairly high level.

00:05:02.960 --> 00:05:05.460
However, speaking at a high level,

00:05:05.460 --> 00:05:09.150
we do look to increase
initiatives that reduce

00:05:10.050 --> 00:05:15.050
both the scope and the
duration of PSPS events.

00:05:16.500 --> 00:05:19.003
For example, adding
increased sectionalization,

00:05:21.180 --> 00:05:24.570
increased weather stations
for situational awareness

00:05:24.570 --> 00:05:27.270
of actual weather conditions is

00:05:27.270 --> 00:05:30.000
something we're really working on.

00:05:30.000 --> 00:05:32.450
But we haven't really quantified

00:05:32.450 --> 00:05:35.660
what level of PSPS reduction that

00:05:35.660 --> 00:05:40.563
that can actually have yet
just because this is so new.

00:05:41.570 --> 00:05:46.100
And then conversely, how
does grid hardening initiatives

00:05:46.100 --> 00:05:49.407
inform our decision-making for PSPS?

00:05:49.407 --> 00:05:54.407
And I would kind of echo
PacifiCorp's response here,

00:05:55.300 --> 00:05:58.933
it's hard to say, without all
these initiatives complete,

00:06:00.800 --> 00:06:03.420
that you don't need the PSPS.

00:06:03.420 --> 00:06:07.515
So, you try and mitigate most effectively

00:06:07.515 --> 00:06:11.880
the most risk reduction
you can get in an area,

00:06:11.880 --> 00:06:13.980
but maybe there's still a piece of hardware

00:06:13.980 --> 00:06:17.130
or something that gives
you pause about an area.

00:06:17.130 --> 00:06:21.210
And without having that full blanket,

00:06:21.210 --> 00:06:25.157
entire risk reduction, it's hard to say

00:06:25.157 --> 00:06:30.157
how much we can really
reduce the PSPS events,

00:06:30.530 --> 00:06:32.473
in the near future at least.

00:06:33.800 --> 00:06:38.700
And then lastly, on
resiliency corridor selection.

00:06:38.700 --> 00:06:41.010
So for the first project
that we actually proposed

00:06:41.010 --> 00:06:43.730
in our 2020 wildfire mitigation plan,

00:06:43.730 --> 00:06:46.440
we kind of had a slam dunk project.

00:06:46.440 --> 00:06:49.680
We've got 12 megawatts of diesel generation

00:06:49.680 --> 00:06:52.870
in our Kings Beach area.

00:06:52.870 --> 00:06:56.230
And that, with a short
span of covered conductor,

00:06:56.230 --> 00:06:59.070
we can get from that diesel generator

00:06:59.070 --> 00:07:02.547
to the downtown Kings Beach area.

00:07:02.547 --> 00:07:05.760
And we don't like running
the diesel generators

00:07:05.760 --> 00:07:07.420
all the time, but in a PSPS event,

00:07:07.420 --> 00:07:09.220
it's certainly called for.

00:07:09.220 --> 00:07:13.027
And so just to have that,
islanded microgrid style area

00:07:15.410 --> 00:07:17.750
is really, really pretty low risk for us.

00:07:17.750 --> 00:07:21.655
So that's the only project we for sure

00:07:21.655 --> 00:07:25.810
have going on right now, but we're expanding

00:07:25.810 --> 00:07:27.943
some analysis to other areas,

00:07:29.190 --> 00:07:31.240
maybe something like battery banks

00:07:31.240 --> 00:07:34.580
or smaller mobile generators
or something of that sort,

00:07:34.580 --> 00:07:38.338
to see if we can do similar projects in,

00:07:38.338 --> 00:07:41.163
like our South Lake Tahoe area, for example.

00:07:46.390 --> 00:07:48.240
<v Andie>Thank you so much, Dylan.</v>

00:07:48.240 --> 00:07:51.193
And then to move on to Bear Valley with Paul.

00:07:52.090 --> 00:07:52.923
<v Paul>Yeah.</v>

00:07:53.931 --> 00:07:55.633
So, in grid hardening,

00:07:57.797 --> 00:08:01.173
sectionalization is a quick way

00:08:02.040 --> 00:08:07.040
to reduce the impact on PSPS.

00:08:08.578 --> 00:08:11.283
And so that's something
that we did right away.

00:08:16.033 --> 00:08:19.020
So, that doesn't really solve the issue

00:08:19.020 --> 00:08:23.273
for those on the downstream
end of that switch.

00:08:24.200 --> 00:08:29.200
And so projects that are, the
covered conductor projects,

00:08:31.160 --> 00:08:36.160
the fuse replacement
projects, pole hardening,

00:08:37.170 --> 00:08:41.917
getting the wood poles
replaced that are strengthened,

00:08:42.810 --> 00:08:47.753
making sure it all poles
meet our requirements.

00:08:48.870 --> 00:08:52.860
Those all are grid
hardening factors that go into

00:08:52.860 --> 00:08:57.390
getting rid of the PSPS
or the need to have one.

00:08:57.390 --> 00:08:59.413
So those areas are prioritized.

00:09:00.710 --> 00:09:03.810
And then the other thing
is more of a dynamic thing

00:09:03.810 --> 00:09:06.713
that looks at, we look at how many,

00:09:07.870 --> 00:09:10.320
for each circuit, we evaluate how many

00:09:10.320 --> 00:09:14.980
outstanding level two
discrepancies are there per,

00:09:14.980 --> 00:09:19.980
as defined in G.O. 95, and
that contributes to the risk

00:09:20.825 --> 00:09:25.093
for if you do have any, we
shouldn't, that's our goal.

00:09:25.990 --> 00:09:27.293
We don't want to enter the fire season

00:09:27.293 --> 00:09:28.893
with a bunch of level twos.

00:09:29.780 --> 00:09:34.440
And we also, you lose, it elevates the risk

00:09:34.440 --> 00:09:37.350
if you have level ones,
that should always be zero,

00:09:37.350 --> 00:09:40.213
since those are immediate fix items.

00:09:41.430 --> 00:09:43.950
And they're either fix them or get them

00:09:43.950 --> 00:09:46.440
to a point where they're level twos.

00:09:46.440 --> 00:09:49.740
But, it is an input to our
model so that we have

00:09:49.740 --> 00:09:54.740
that dynamic on the actual
condition of the circuit.

00:10:00.030 --> 00:10:02.313
<v Andie>Okay. Thank you so much, Paul.</v>

00:10:03.870 --> 00:10:07.923
With that, I'm going to
move to the stakeholders.

00:10:09.480 --> 00:10:14.312
I see that neither Greg nor Zoe,

00:10:14.312 --> 00:10:16.400
neither of you have your hand raised.

00:10:16.400 --> 00:10:18.133
Did GPI have any questions?

00:10:21.210 --> 00:10:22.043
<v Zoe>Thanks. Sure.</v>

00:10:22.043 --> 00:10:23.750
I can go real quick here.

00:10:23.750 --> 00:10:26.460
This is Zoe Harrold with
Green Power Institute.

00:10:26.460 --> 00:10:31.090
So my question is, for the SMJUs,

00:10:31.090 --> 00:10:36.090
do they have a sense of kind
of a grid hardening threshold

00:10:36.230 --> 00:10:39.580
or end goal that needs to be reached

00:10:39.580 --> 00:10:41.030
for these different mitigations?

00:10:41.030 --> 00:10:45.060
So like covered conductor, say, 80% coverage,

00:10:45.060 --> 00:10:50.060
to be able to raise the PSPS threshold,

00:10:51.110 --> 00:10:54.260
or a threshold for sectionalizing,

00:10:54.260 --> 00:10:58.010
that they kind of have this
as an end goal in mind?

00:10:58.010 --> 00:10:58.843
Thank you.

00:11:02.644 --> 00:11:05.490
<v Amy>Sure, that's a great question.</v>

00:11:05.490 --> 00:11:09.960
I think, as it pertains to the PSPS zones

00:11:09.960 --> 00:11:13.310
for covered conductor,
realistically what we're trying to do

00:11:13.310 --> 00:11:16.740
is within those, I'm gonna say
electrically connected areas,

00:11:16.740 --> 00:11:21.720
things that we can isolate,
the goal is within there,

00:11:21.720 --> 00:11:24.580
and by isolate, I mean kind of thinking about

00:11:24.580 --> 00:11:27.070
circling the PSPS areas, the high risk areas,

00:11:27.070 --> 00:11:29.800
and saying everything
in here is really high risk.

00:11:29.800 --> 00:11:33.553
The goal there is to have
covered conductor everywhere.

00:11:34.670 --> 00:11:36.160
But then once you get outside an area

00:11:36.160 --> 00:11:38.550
where you can sectionalize,
maybe you don't need it.

00:11:38.550 --> 00:11:40.650
So I think for PSPS, we're looking

00:11:40.650 --> 00:11:44.120
to kind of include the entire thing.

00:11:44.120 --> 00:11:45.440
But now that doesn't translate

00:11:45.440 --> 00:11:47.130
to the entire service territory.

00:11:47.130 --> 00:11:48.890
So that's something very different.

00:11:48.890 --> 00:11:53.380
And once you get past, I'll
say, the extreme risk area,

00:11:53.380 --> 00:11:55.540
if you think about the way we're deploying

00:11:55.540 --> 00:11:57.270
our grid hardening initiatives,

00:11:57.270 --> 00:11:59.468
once we get past that
first extreme risk area,

00:11:59.468 --> 00:12:01.987
I don't think we know the answer yet.

00:12:01.987 --> 00:12:04.107
I think we're waiting
to evolve our risk model

00:12:04.107 --> 00:12:06.630
a little bit more to say that,

00:12:06.630 --> 00:12:09.210
past that first step do
we need it everywhere?

00:12:09.210 --> 00:12:12.350
Is it 80%, like you talked about, is it 10%,

00:12:12.350 --> 00:12:14.840
is it a combination of different initiatives?

00:12:14.840 --> 00:12:16.290
I think that's where it's tough to say

00:12:16.290 --> 00:12:17.740
what the future holds.

00:12:17.740 --> 00:12:20.010
But for us right now, within those extreme,

00:12:20.010 --> 00:12:22.360
extreme risk zones, which are our PSPS zones,

00:12:22.360 --> 00:12:25.500
we're looking to include covered conductor

00:12:25.500 --> 00:12:26.733
everywhere within there.

00:12:36.368 --> 00:12:38.070
<v Dylan>This is Dylan with Liberty.</v>

00:12:38.070 --> 00:12:40.763
That's a good response, Amy.

00:12:42.257 --> 00:12:46.310
I'd say, largely our bottom line goal is,

00:12:46.310 --> 00:12:50.890
what is the most cost
effective and overall effective

00:12:51.800 --> 00:12:55.120
mitigation solution for any given area.

00:12:55.120 --> 00:12:58.590
To us, the answer may
not be covered conductor

00:12:58.590 --> 00:13:00.870
all the time in our highest risk areas.

00:13:00.870 --> 00:13:03.653
For example, there are some areas

00:13:03.653 --> 00:13:07.330
where micro grids might make a lot of sense.

00:13:07.330 --> 00:13:10.067
If you can say, for example, we've got

00:13:10.067 --> 00:13:12.540
four miles of uncovered distribution line

00:13:12.540 --> 00:13:15.563
going through a very high fire threat area,

00:13:16.930 --> 00:13:19.430
but you can, the loads
at the end of the line,

00:13:19.430 --> 00:13:22.190
you can take that four
miles out or decommission it

00:13:22.190 --> 00:13:24.540
or de-energize it during fire season

00:13:24.540 --> 00:13:28.600
and just do a microgrid
at the end of that line,

00:13:28.600 --> 00:13:30.250
that might end up being cheaper

00:13:30.250 --> 00:13:33.510
than covering the
conductor of the entire area.

00:13:33.510 --> 00:13:36.900
So that's a big feasibility analysis.

00:13:36.900 --> 00:13:39.483
we're undergoing at the moment,

00:13:41.270 --> 00:13:44.540
with the end goal of just,

00:13:44.540 --> 00:13:48.523
we don't want to subject
our customers to PSPS.

00:13:50.550 --> 00:13:54.760
It's probably a point of diminishing returns.

00:13:54.760 --> 00:13:59.760
Like you can get 90% of
the mitigation for X dollars,

00:14:02.880 --> 00:14:06.320
but you can probably get
a 100% for two X dollars.

00:14:06.320 --> 00:14:11.320
And what is that threshold
that's worth spending?

00:14:11.670 --> 00:14:14.260
What return on investment are we getting

00:14:14.260 --> 00:14:15.463
for the customers there?

00:14:16.943 --> 00:14:18.760
And I think the bottom line here is still

00:14:18.760 --> 00:14:23.760
our risk modeling is still
in its infancy, definitely.

00:14:24.170 --> 00:14:28.350
And as we continue to
gather more data, quantify

00:14:28.350 --> 00:14:31.780
the effectiveness of these
various mitigation numbers,

00:14:31.780 --> 00:14:34.740
I think we'll have a much, much better idea

00:14:34.740 --> 00:14:37.983
of what a fully baked solution looks like.

00:14:46.770 --> 00:14:49.870
<v Paul>So, I think if,</v>

00:14:49.870 --> 00:14:53.580
like, for example, covered
conductor would definitely

00:14:54.870 --> 00:14:59.560
bring the threshold level
to extremely unlikely,

00:14:59.560 --> 00:15:02.013
I think I would say, that we'd do a PSPS.

00:15:04.020 --> 00:15:08.941
And I think we can tell customers that,

00:15:08.941 --> 00:15:13.583
that we'd get covered conductor.

00:15:13.583 --> 00:15:17.370
Now we're really only
looking at scenarios where

00:15:17.370 --> 00:15:20.810
the three second gust threshold

00:15:20.810 --> 00:15:25.440
exceeds the design of the system.

00:15:25.440 --> 00:15:29.947
And those designs are set in G.O. 95

00:15:29.947 --> 00:15:32.660
and our own company standards.

00:15:32.660 --> 00:15:35.490
Those are uncontrollable events,

00:15:35.490 --> 00:15:39.420
but if we were to get those,
those would be extremely rare.

00:15:39.420 --> 00:15:42.011
'cause the design margins are set that

00:15:42.011 --> 00:15:44.853
we shouldn't really experience those,

00:15:45.872 --> 00:15:48.980
but those would be the only cases where

00:15:48.980 --> 00:15:51.400
I think we would be deep concerned

00:15:52.240 --> 00:15:54.440
if we were expecting that kind of situation.

00:15:58.950 --> 00:16:01.987
<v ->Thanks so much.</v>
<v ->Thank you, everyone.</v>

00:16:01.987 --> 00:16:04.533
<v Andie>So, yeah, did that answer your question, Zoe?</v>

00:16:05.790 --> 00:16:07.090
<v Zoe>It did, thank you.</v>

00:16:08.490 --> 00:16:09.323
<v Andie>I did have one</v>

00:16:09.323 --> 00:16:11.984
clarification question for PacifiCorp.

00:16:11.984 --> 00:16:15.650
I was wondering when
you've mentioned installing

00:16:15.650 --> 00:16:17.645
covered conductor on all of it,

00:16:17.645 --> 00:16:22.645
when you talk about the
threshold for that, is it like,

00:16:22.926 --> 00:16:25.040
would you consider a higher wind speeds

00:16:25.040 --> 00:16:26.280
before considering a PSPS?

00:16:26.280 --> 00:16:29.413
Or is it excluding it from
PSPS consideration at all?

00:16:31.680 --> 00:16:34.913
<v Amy>I think that's a good
clarification question, Andie.</v>

00:16:37.390 --> 00:16:39.520
I think at this time, our expectation is that

00:16:39.520 --> 00:16:42.543
it will influence the threshold.

00:16:43.550 --> 00:16:46.940
And then, I think as
Liberty kind of described it,

00:16:46.940 --> 00:16:49.350
we want to get a little
experience under our belt

00:16:49.350 --> 00:16:53.510
before we say, oh, and now
it's gone from higher threshold

00:16:53.510 --> 00:16:55.360
to I don't need it at all.

00:16:55.360 --> 00:16:57.810
And one thing, and I probably
should have clarified this

00:16:57.810 --> 00:17:00.010
when I was speaking before,
when we're talking about

00:17:00.010 --> 00:17:01.160
installing covered conductor,

00:17:01.160 --> 00:17:03.540
it's not just the covered conductor,

00:17:03.540 --> 00:17:05.907
it's kind of the full suite
of the hardening initiatives

00:17:05.907 --> 00:17:08.010
and the way they pair
together and they stack,

00:17:08.010 --> 00:17:11.630
that they match with all of our risk drivers.

00:17:11.630 --> 00:17:13.550
So there's that component as well.

00:17:13.550 --> 00:17:15.190
So when I'm saying covered conductor,

00:17:15.190 --> 00:17:17.130
I'm thinking all the
bells and whistles I need

00:17:17.130 --> 00:17:19.480
on that circuit to mitigate

00:17:19.480 --> 00:17:21.120
all of the different risk drivers.

00:17:21.120 --> 00:17:24.760
But I do think it's, there's
probably an intermediate step

00:17:24.760 --> 00:17:27.550
where we say, hey now we're
looking at different thresholds.

00:17:27.550 --> 00:17:28.790
Now we're getting more confident

00:17:28.790 --> 00:17:30.550
that the results are really coming back

00:17:30.550 --> 00:17:32.713
that these risk events are disappearing.

00:17:33.790 --> 00:17:36.060
We feel as though it is very low,

00:17:36.060 --> 00:17:38.360
and then I think you
do move to don't need it.

00:17:39.210 --> 00:17:41.103
I don't have the crystal ball on what exactly

00:17:41.103 --> 00:17:44.180
that looks like or when,
but I do think that has to be

00:17:44.180 --> 00:17:46.330
kind of the vision and our eventual target.

00:17:49.760 --> 00:17:51.260
<v Andie>Thanks so much, Amy.</v>

00:17:52.560 --> 00:17:56.823
Going into Cal Advocates'
question, with Henry Burton.

00:18:00.820 --> 00:18:02.720
<v Henry>Hi, thank you.</v>

00:18:02.720 --> 00:18:05.283
So I have a question for all three utilities.

00:18:07.080 --> 00:18:10.510
We haven't talked a lot about
inspection in this session,

00:18:10.510 --> 00:18:15.510
but I wanted to ask, are
you doing aerial inspections,

00:18:16.660 --> 00:18:18.790
either by drone or helicopter,

00:18:18.790 --> 00:18:22.213
for your distribution
infrastructure in HFTD areas?

00:18:23.210 --> 00:18:27.600
Or do you foresee starting
to do aerial inspections?

00:18:27.600 --> 00:18:30.410
And just talk a little
bit about your thinking

00:18:30.410 --> 00:18:33.160
on the relative value of aerial

00:18:33.160 --> 00:18:35.260
versus detailed ground inspections.

00:18:35.260 --> 00:18:36.093
Thanks.

00:18:41.840 --> 00:18:43.037
<v Amy>Sure. Hi, Henry.</v>

00:18:43.037 --> 00:18:46.690
<v Henry>Just to clarify, I'm
talking about distribution.</v>

00:18:46.690 --> 00:18:48.550
<v Amy>Just distribution, okay.</v>

00:18:48.550 --> 00:18:49.870
That's helpful.

00:18:49.870 --> 00:18:52.300
So for distribution right now,

00:18:52.300 --> 00:18:56.565
we don't do any
programmatic aerial inspections.

00:18:56.565 --> 00:18:58.240
We do on the transmission side,

00:18:58.240 --> 00:19:00.550
but not on the distribution side.

00:19:00.550 --> 00:19:02.780
I know we've dabbled around in it a bit

00:19:02.780 --> 00:19:04.560
and the company does have,

00:19:04.560 --> 00:19:08.090
they've set up kind of a
drone management program.

00:19:08.090 --> 00:19:10.963
We haven't yet thought
about it in a programmatic way.

00:19:11.800 --> 00:19:13.740
And one of the reasons is, right now,

00:19:13.740 --> 00:19:15.320
not to say things can't change,

00:19:15.320 --> 00:19:18.020
we tend to see more ground line failures.

00:19:18.020 --> 00:19:22.690
We tend to see more conditions and flaws

00:19:22.690 --> 00:19:25.000
that can be viewed from the ground.

00:19:25.000 --> 00:19:27.500
We don't tend to have a
ton of the pole top failures

00:19:27.500 --> 00:19:31.467
at this point, not to say
that trends can't change,

00:19:31.467 --> 00:19:33.743
but there just hasn't
been a strong justification

00:19:33.743 --> 00:19:37.500
at this time to stand
up an aerial inspection.

00:19:37.500 --> 00:19:39.730
But obviously we all know
the risk landscape is changing,

00:19:39.730 --> 00:19:42.460
and as electric companies,
we have to change as well.

00:19:42.460 --> 00:19:44.520
And so I know that is something
we're starting to consider,

00:19:44.520 --> 00:19:46.100
is are there drone applications

00:19:46.100 --> 00:19:51.100
on a more routine basis
that could benefit us.

00:19:51.130 --> 00:19:52.989
But I just don't quite have
the answer for you yet,

00:19:52.989 --> 00:19:55.406
but we are thinking about it.

00:19:58.570 --> 00:20:00.920
<v Dylan>Yeah, Liberty's largely the same.</v>

00:20:00.920 --> 00:20:03.840
We've investigated doing
some drone level inspections

00:20:03.840 --> 00:20:05.923
on distribution level voltages,

00:20:06.910 --> 00:20:11.910
but we haven't programmatically
deployed anything to date.

00:20:12.150 --> 00:20:16.100
We really focused this
past year on just improving

00:20:16.100 --> 00:20:18.540
our traditional ground-based inspections,

00:20:18.540 --> 00:20:21.993
and we feel that we've made
great strides in that area.

00:20:23.140 --> 00:20:28.062
And additionally, with some
of the aerial inspections,

00:20:28.062 --> 00:20:30.400
just getting a drone in the right place

00:20:30.400 --> 00:20:35.297
with lots of vegetation in
the area can be difficult.

00:20:36.930 --> 00:20:40.579
So yeah, bottom line is we're
exploring it and do not have

00:20:40.579 --> 00:20:44.563
an aerial distribution
inspection program to date.

00:20:49.790 --> 00:20:52.100
<v Paul>So for Bear Valley, like I said,</v>

00:20:52.100 --> 00:20:55.000
we did beef up our ground patrols.

00:20:55.000 --> 00:20:56.390
We did implement LiDAR.

00:20:56.390 --> 00:20:59.560
We've done now, in 2019 and 2020,

00:20:59.560 --> 00:21:01.830
we did complete LiDAR surveys.

00:21:01.830 --> 00:21:06.830
Those use both ground mounted
LiDAR devices and some drones.

00:21:09.270 --> 00:21:14.270
And we just, last week, put
out a RFP for a UAV program,

00:21:17.410 --> 00:21:20.823
to do an annual UAV
survey before the fire season.

00:21:22.219 --> 00:21:27.219
We're looking at the HD imagery
as well as thermal imaging.

00:21:29.452 --> 00:21:33.170
Our team had an opportunity about a year ago

00:21:33.170 --> 00:21:37.040
to visit Southern California
Edison's, one of their centers,

00:21:37.040 --> 00:21:41.120
where they showed us the value of the UAVs.

00:21:41.120 --> 00:21:42.480
I do see a lot of value there,

00:21:42.480 --> 00:21:45.505
it's just how much we can do at once.

00:21:45.505 --> 00:21:47.930
And now we're at the point
where we can certainly,

00:21:47.930 --> 00:21:50.849
I think, go to that next level with the UAVs.

00:21:50.849 --> 00:21:54.130
It gives you a good geo
location and it gives you,

00:21:54.130 --> 00:21:57.610
it's incredible what you
can't see from the ground up,

00:21:57.610 --> 00:22:02.610
when you look, compared to
what you see from the sky down.

00:22:04.740 --> 00:22:07.398
And so we do see a lot of value there

00:22:07.398 --> 00:22:11.343
and we're looking forward
to doing the aerial surveys.

00:22:16.600 --> 00:22:17.520
<v Henry>Great. Thank you.</v>

00:22:17.520 --> 00:22:18.353
That's helpful.

00:22:22.610 --> 00:22:25.173
<v Andie>Okay, so next up we have Will Abrams.</v>

00:22:29.918 --> 00:22:31.860
<v ->Thanks very much.</v>

00:22:31.860 --> 00:22:36.090
I had some questions around
quality assurance processes,

00:22:36.090 --> 00:22:38.090
'cause I didn't see that touched on

00:22:38.090 --> 00:22:40.130
too much during the presentation.

00:22:40.130 --> 00:22:42.680
So I was hoping you could talk to

00:22:42.680 --> 00:22:45.480
what are your current
quality assurance processes?

00:22:45.480 --> 00:22:49.740
What are the current quality control tools

00:22:49.740 --> 00:22:54.740
that you use to ensure your work?

00:22:55.280 --> 00:22:57.310
And if you can also talk to sort of

00:22:57.310 --> 00:22:59.980
your staffing limitations around that as well

00:22:59.980 --> 00:23:02.010
and how that's structured.

00:23:02.010 --> 00:23:07.010
Do you have a quality assurance department?

00:23:07.276 --> 00:23:12.276
What's the training and what's the level

00:23:13.520 --> 00:23:17.743
of the subject matter experts
that you have in those areas?

00:23:19.730 --> 00:23:21.180
<v Andie>All right, so before you answer,</v>

00:23:21.180 --> 00:23:23.620
Will, I just wanted to clarify,
did you want the ATOs

00:23:23.620 --> 00:23:27.460
to respond to that as
well, or just the SMJUs?

00:23:28.850 --> 00:23:29.683
<v ->I'm open.</v>

00:23:29.683 --> 00:23:33.607
I think, to whatever degree
folks feel that they have

00:23:33.607 --> 00:23:37.623
answers to that question,
to the entire group.

00:23:42.510 --> 00:23:46.340
<v Amy>Okay. I'll go ahead
and start off for PacifiCorp.</v>

00:23:46.340 --> 00:23:48.930
I know we touched on
it a little bit in the slide.

00:23:48.930 --> 00:23:51.750
It has been a focus area for us this year,

00:23:51.750 --> 00:23:54.280
based on some feedback received,

00:23:54.280 --> 00:23:56.010
to make sure that we're reporting on

00:23:56.010 --> 00:23:59.700
and talking about and presenting
on our QA QC processes.

00:23:59.700 --> 00:24:04.140
So for our inspections, we've
got a couple of different ways

00:24:04.140 --> 00:24:06.680
we introduce these controls.

00:24:06.680 --> 00:24:09.350
So the first is, we actually have built into

00:24:09.350 --> 00:24:11.260
some of the contractor work we do,

00:24:11.260 --> 00:24:15.101
that they have a staff person
who does quality controls,

00:24:15.101 --> 00:24:18.480
QA QC of their inspections, so by the time

00:24:18.480 --> 00:24:21.230
the inspection results make it to PacifiCorp,

00:24:21.230 --> 00:24:22.680
there's already a decent level

00:24:22.680 --> 00:24:26.320
of quality assurance that happens in there.

00:24:26.320 --> 00:24:29.490
So then the records make it into our system

00:24:29.490 --> 00:24:32.890
and we've got kind of two areas we attack.

00:24:32.890 --> 00:24:35.700
One is the physical site auditing,

00:24:35.700 --> 00:24:38.274
so where we're going out
and trying to understand,

00:24:38.274 --> 00:24:40.780
do our inspectors understand?

00:24:40.780 --> 00:24:43.450
Are they capturing violations correctly?

00:24:43.450 --> 00:24:46.660
Are they categorizing fire threats correctly?

00:24:46.660 --> 00:24:48.760
Are we giving them the right priority

00:24:48.760 --> 00:24:51.400
to make sure we work
the correction correctly?

00:24:51.400 --> 00:24:53.150
So there's the physical side.

00:24:53.150 --> 00:24:55.740
And then there's, I'm gonna
call it the administrative side,

00:24:55.740 --> 00:24:59.240
so making sure that when
we get records coming in,

00:24:59.240 --> 00:25:02.093
that they match policy, that they match,

00:25:02.093 --> 00:25:04.820
because we have a way
that we categorize findings.

00:25:04.820 --> 00:25:07.490
And so we're making sure
the categories make sense,

00:25:07.490 --> 00:25:09.910
'cause those categories
dictate how we plan and do work.

00:25:09.910 --> 00:25:12.120
And so where the data comes in wrong

00:25:12.120 --> 00:25:13.360
it means that we have the potential

00:25:13.360 --> 00:25:15.700
to get off track on how we correct them.

00:25:15.700 --> 00:25:17.250
So those are the two fronts we attack

00:25:17.250 --> 00:25:20.070
after the kind of pre-qualified
inspections come in.

00:25:20.070 --> 00:25:22.360
And I think I touched on in the presentation,

00:25:22.360 --> 00:25:26.650
the field audits, the physical
piece usually sits around 5%.

00:25:26.650 --> 00:25:28.080
I think last year we
were a little bit higher,

00:25:28.080 --> 00:25:31.260
actually 7% is what we were able to audit.

00:25:31.260 --> 00:25:33.530
And then the desktop audits combined

00:25:33.530 --> 00:25:37.223
with the contractor and internal,
we tend to sit around 50%.

00:25:38.366 --> 00:25:40.123
There's a third layer that is new

00:25:40.123 --> 00:25:44.090
that we've introduced a kind
of a weekly tool that we have

00:25:44.090 --> 00:25:46.610
that looks for, I'm gonna
say data mismatches,

00:25:46.610 --> 00:25:49.890
but it looks for a record
that doesn't match policy,

00:25:49.890 --> 00:25:53.013
or a priority that doesn't make sense.

00:25:53.013 --> 00:25:55.470
And that's kind of a third
element we've implemented

00:25:55.470 --> 00:25:58.970
on a weekly basis to kick
records back to the inspectors

00:25:58.970 --> 00:26:01.520
to make sure there isn't
something deeper going on.

00:26:02.550 --> 00:26:04.770
The nice thing about
packaging all of this as a program

00:26:04.770 --> 00:26:07.530
is we're feeding it into our annual training,

00:26:07.530 --> 00:26:09.400
which has been really helpful.

00:26:09.400 --> 00:26:12.420
And especially with that
weekly report we're able

00:26:12.420 --> 00:26:15.190
to actively train throughout
the year on our inspectors

00:26:15.190 --> 00:26:17.744
to make sure they
understand the requirements.

00:26:17.744 --> 00:26:19.150
So that's kind of,

00:26:19.150 --> 00:26:20.460
it's kind of a couple of different fronts.

00:26:20.460 --> 00:26:24.258
I hope that touches on kind
of our QA QC processes.

00:26:24.258 --> 00:26:27.070
As far as the people involved,

00:26:27.070 --> 00:26:30.158
so I think I kinda mentioned
we have some that are,

00:26:30.158 --> 00:26:32.520
ones that are integrated into our contract.

00:26:32.520 --> 00:26:36.020
We also have a team
called field inspection support

00:26:36.020 --> 00:26:40.190
and we've got strategic
folks placed all around

00:26:40.190 --> 00:26:45.070
our service territory that
do the follow up field audits.

00:26:45.070 --> 00:26:47.390
They're experts in electrical code.

00:26:47.390 --> 00:26:51.120
They really closely manage those contractors.

00:26:51.120 --> 00:26:54.340
And so that's a large function
of what that team does.

00:26:54.340 --> 00:26:55.950
And then we have a central team,

00:26:55.950 --> 00:26:58.120
asset management and work planning,

00:26:58.120 --> 00:27:00.740
that do the more kind of desktop work

00:27:00.740 --> 00:27:03.420
to make sure corrections get facilitated.

00:27:03.420 --> 00:27:06.750
So it's not one specific department which is,

00:27:06.750 --> 00:27:08.690
can be challenging for
us with these programs.

00:27:08.690 --> 00:27:11.500
We don't have a specific QA QC department.

00:27:11.500 --> 00:27:13.690
We've got kind of some resources

00:27:13.690 --> 00:27:16.440
within all of the different
functions that play a part.

00:27:17.500 --> 00:27:19.400
Hopefully that answered your question.

00:27:20.712 --> 00:27:22.103
<v ->Thanks very much.</v>

00:27:22.103 --> 00:27:27.103
And are those folks that are
trained in quality assurance

00:27:27.160 --> 00:27:29.720
or are they sort of folks that have

00:27:29.720 --> 00:27:32.700
the electrical engineering experience?

00:27:32.700 --> 00:27:33.814
<v ->That one.</v>

00:27:33.814 --> 00:27:35.400
<v ->And sort of executing on the QA,</v>

00:27:35.400 --> 00:27:39.090
as opposed to a quality assurance

00:27:39.090 --> 00:27:41.923
or risk management
professional that would be,

00:27:42.810 --> 00:27:44.253
is that how that works?

00:27:45.170 --> 00:27:46.040
<v ->Correct. Yes.</v>

00:27:46.040 --> 00:27:48.410
Yeah. We don't have an on-staff,

00:27:48.410 --> 00:27:51.030
kind of quality control or
risk assessment person.

00:27:51.030 --> 00:27:54.370
It's more folks that are trained
in electrical components,

00:27:54.370 --> 00:27:57.750
electrical code, experience
in program management,

00:27:57.750 --> 00:27:59.340
things like that.

00:27:59.340 --> 00:28:03.010
The expertise tends to be on
the technical component side,

00:28:03.010 --> 00:28:04.010
if that makes sense.

00:28:06.360 --> 00:28:10.300
<v ->Thank you.</v>
<v ->Yep.</v>

00:28:10.300 --> 00:28:12.550
<v ->So, for Bear Valley, likewise,</v>

00:28:12.550 --> 00:28:16.053
we don't have a QA
department or QC department.

00:28:17.170 --> 00:28:20.773
It depends on the type of work being done.

00:28:23.554 --> 00:28:24.387
In the next section,

00:28:24.387 --> 00:28:25.970
we're gonna talk about vegetation management.

00:28:25.970 --> 00:28:29.851
We do have a formal vegetation QC program

00:28:29.851 --> 00:28:32.996
where all supervisors, managers,

00:28:32.996 --> 00:28:37.590
including myself and certain
other designated people

00:28:37.590 --> 00:28:40.874
who understand what they're
looking at and are trained,

00:28:40.874 --> 00:28:45.524
go out and do, we do six QCs per month.

00:28:45.524 --> 00:28:49.086
So it gets everybody out in the field

00:28:49.086 --> 00:28:53.363
and keeps our contractor on its toes.

00:28:54.430 --> 00:28:57.680
And so to me, that's essential.

00:28:57.680 --> 00:29:01.070
So that program, and it
has very specific attributes

00:29:01.070 --> 00:29:05.803
that they look for in completing that QC.

00:29:08.397 --> 00:29:12.033
For T and D type construction,

00:29:13.420 --> 00:29:17.920
it's actually part of our
invoicing procedure.

00:29:17.920 --> 00:29:20.360
So we have a field inspector who goes out

00:29:20.360 --> 00:29:25.360
and verifies the work is
completed per the work plans.

00:29:27.160 --> 00:29:31.162
And the material that was
pulled was actually used

00:29:31.162 --> 00:29:36.162
per the work order or for the specifications

00:29:36.330 --> 00:29:40.040
before that invoice
proceeds to the next level.

00:29:40.040 --> 00:29:44.683
So, QC sort of happens that
way for those types of projects.

00:29:45.600 --> 00:29:47.240
And then when you get some more complicated,

00:29:47.240 --> 00:29:50.320
like a substation, we
do bring in a third party

00:29:50.320 --> 00:29:52.910
to do testing and commissioning.

00:29:52.910 --> 00:29:55.970
So that it's not the
company that constructed it,

00:29:55.970 --> 00:29:59.670
but it's an independent testing
and commissioning group.

00:29:59.670 --> 00:30:01.973
So we get the QC there.

00:30:05.490 --> 00:30:06.323
<v ->Thank you.</v>

00:30:09.950 --> 00:30:11.660
<v ->This is Dylan, with Liberty.</v>

00:30:11.660 --> 00:30:14.018
I'll jump in really quick.

00:30:14.018 --> 00:30:18.010
So we do have, we're going
back through our system inventory

00:30:18.010 --> 00:30:21.597
and inspection records with
our own internal inspectors

00:30:23.070 --> 00:30:25.790
who are qualified, trained linemen,

00:30:25.790 --> 00:30:27.830
very familiar with line construction

00:30:28.770 --> 00:30:31.970
to make sure that the
contractors that we're using

00:30:34.200 --> 00:30:36.000
didn't miss anything crucial.

00:30:36.000 --> 00:30:38.550
We're not going through every record,

00:30:38.550 --> 00:30:41.453
as any audit would not do,

00:30:42.320 --> 00:30:45.717
but we are performing a
level of QA and QC there.

00:30:45.717 --> 00:30:50.130
And so that's done by a
qualified and trained workforce.

00:30:50.130 --> 00:30:53.540
But we are certainly
seeing workforce limitations

00:30:53.540 --> 00:30:56.750
within that department and willing to expand

00:30:56.750 --> 00:31:00.403
with a set of qualified contractors.

00:31:01.690 --> 00:31:04.760
And then secondly, Bear
Valley kind of mentioned this,

00:31:04.760 --> 00:31:09.760
but we have started
implementing a G.O. 95 checklist

00:31:10.320 --> 00:31:12.840
for new construction and making sure

00:31:12.840 --> 00:31:17.373
that everything is built to
the design and built to code.

00:31:18.620 --> 00:31:20.940
So, that's another approach we're taking

00:31:20.940 --> 00:31:25.650
as far as QA QC within
our grid hardening initiatives,

00:31:25.650 --> 00:31:27.420
as well as the inspections.

00:31:27.420 --> 00:31:28.253
Thank you.

00:31:29.870 --> 00:31:30.750
<v ->Thanks.</v>

00:31:30.750 --> 00:31:35.750
And I guess given the
limitations around resources,

00:31:35.883 --> 00:31:38.450
I'm wondering if folks have explored

00:31:38.450 --> 00:31:42.581
the possibility of a mutual
assistance agreement

00:31:42.581 --> 00:31:45.790
or things like that to sort of help with,

00:31:45.790 --> 00:31:50.643
I guess, getting that specific
QA subject matter expertise

00:31:53.880 --> 00:31:55.480
more in house, have you explored

00:31:56.557 --> 00:31:58.533
sort of collaborative
ways to fill those gaps?

00:31:59.410 --> 00:32:02.110
Sorry, I don't know if
that's a follow-up question

00:32:02.110 --> 00:32:05.563
that's allowed, but that's
throwing it out there.

00:32:08.198 --> 00:32:10.540
<v ->I'm sorry, Will, I may ask
you to repeat it a little bit.</v>

00:32:10.540 --> 00:32:13.740
So it's around kind of sharing the resource

00:32:13.740 --> 00:32:17.290
amongst utilities or having kind of

00:32:17.290 --> 00:32:19.820
backup contractors ready to go or?

00:32:19.820 --> 00:32:21.320
<v ->Right. Yeah.</v>

00:32:21.320 --> 00:32:25.250
No, I just, I understand,
that there are limitations.

00:32:25.250 --> 00:32:30.007
You have more resource
constraints then the larger IOUs

00:32:31.609 --> 00:32:36.609
and therefore don't have sort
of a bank of QA professionals

00:32:36.904 --> 00:32:39.670
and a lot of structure around that.

00:32:39.670 --> 00:32:42.000
And so, I guess I'm just wondering

00:32:42.000 --> 00:32:46.430
if there are ways to
collaboratively fill that gap,

00:32:46.430 --> 00:32:48.520
through like a mutual assistance agreement,

00:32:48.520 --> 00:32:51.385
where you have some shared resources

00:32:51.385 --> 00:32:56.385
or sort of can build some of that expertise.

00:32:56.490 --> 00:33:01.490
And if you've explored ways to do that,

00:33:01.770 --> 00:33:04.410
sort of I guess more creatively than actually

00:33:04.410 --> 00:33:08.113
just hiring QA professionals which might be

00:33:08.113 --> 00:33:12.053
more cost prohibitive than for others.

00:33:13.570 --> 00:33:15.550
<v ->Okay. Yeah, that helps clarify.</v>

00:33:15.550 --> 00:33:17.360
I would say at this point I don't know

00:33:17.360 --> 00:33:20.090
that we've investigated specifically

00:33:20.090 --> 00:33:21.390
what you're talking about.

00:33:23.891 --> 00:33:25.400
Where we benefit, at PacifiCorp,

00:33:25.400 --> 00:33:29.090
is our California service
territory is very small.

00:33:29.090 --> 00:33:32.630
But we do have a larger
workforce that we can rely on

00:33:32.630 --> 00:33:35.180
in times like this where
you have significant peaks

00:33:35.180 --> 00:33:37.940
and troughs in the requirements.

00:33:37.940 --> 00:33:40.375
And I can say specifically
in the inspections realm,

00:33:40.375 --> 00:33:42.350
we have had to pull resources in

00:33:42.350 --> 00:33:44.926
from the other states where we work.

00:33:44.926 --> 00:33:46.967
So I think because we have that kind of,

00:33:46.967 --> 00:33:50.080
almost a natural built-in pipeline,

00:33:50.080 --> 00:33:51.537
we haven't had to do
what you're talking about.

00:33:51.537 --> 00:33:53.327
Not to say there wouldn't be value

00:33:53.327 --> 00:33:56.147
in what you're talking
about, in collaborating,

00:33:56.147 --> 00:33:58.230
whether it's just throughout the industry

00:33:58.230 --> 00:34:02.260
with other utilities to have
this extra resource to rely on.

00:34:02.260 --> 00:34:04.580
I don't think we've experienced that,

00:34:04.580 --> 00:34:06.000
that significant shortage yet,

00:34:06.000 --> 00:34:08.640
just because of the unique position we're in.

00:34:08.640 --> 00:34:11.173
But that is certainly something
we should be thinking about.

00:34:12.160 --> 00:34:12.993
<v ->Thanks.</v>

00:34:19.021 --> 00:34:20.220
<v ->That's a good question.</v>

00:34:20.220 --> 00:34:23.060
I don't think Liberty
has specifically explored

00:34:23.060 --> 00:34:24.920
that as a possibility.

00:34:24.920 --> 00:34:28.750
I can certainly see the
benefit of sharing resources

00:34:28.750 --> 00:34:31.010
where they are constrained,

00:34:31.010 --> 00:34:32.760
maybe not with the people in the room

00:34:32.760 --> 00:34:37.150
but with neighbors potentially
to our east and west.

00:34:37.150 --> 00:34:41.620
So we'll take that as a potential follow up

00:34:41.620 --> 00:34:44.420
and see if there's merit
within that suggestion.

00:34:44.420 --> 00:34:45.253
Thank you.

00:34:46.700 --> 00:34:47.533
<v ->Thanks.</v>

00:34:47.533 --> 00:34:50.156
<v ->Yeah. So it sounds like a good idea.</v>

00:34:50.156 --> 00:34:53.860
There are challenges to execution.

00:34:53.860 --> 00:34:56.623
We're in very different geographic locations.

00:34:57.560 --> 00:35:00.430
There would also have to be some very careful

00:35:00.430 --> 00:35:04.090
cost allocations, so Liberty's ratepayers

00:35:04.090 --> 00:35:07.263
aren't paying for Bear
Valley work and vice versa.

00:35:09.540 --> 00:35:12.500
So there are some challenges
that would need to be resolved.

00:35:12.500 --> 00:35:15.010
I'm sure those could be surmounted

00:35:15.010 --> 00:35:17.871
if the benefits certainly outweighed the,

00:35:17.871 --> 00:35:20.653
all that has to be done.

00:35:24.460 --> 00:35:25.293
<v ->Thank you.</v>

00:35:32.821 --> 00:35:36.810
<v Andie>Did Horizon West or Trans Bay Cable</v>

00:35:36.810 --> 00:35:39.870
want to speak to their quality assurance,

00:35:39.870 --> 00:35:41.120
quality control programs?

00:35:44.590 --> 00:35:47.280
<v Alona>Hi, this is Alona Sias with Horizon West.</v>

00:35:47.280 --> 00:35:50.150
So we don't have quite the
same resource constraints,

00:35:50.150 --> 00:35:51.510
given our footprint.

00:35:51.510 --> 00:35:53.220
So specifically for Horizon West,

00:35:53.220 --> 00:35:56.830
for inspections we have dedicated operations

00:35:56.830 --> 00:35:59.420
and dedicated highly
trained operations personnel

00:35:59.420 --> 00:36:01.230
who conduct those inspections.

00:36:01.230 --> 00:36:04.343
And then in addition to that, we have

00:36:04.343 --> 00:36:08.130
our senior director of operations review

00:36:08.130 --> 00:36:10.430
and monitor and audit
those inspections results,

00:36:10.430 --> 00:36:14.541
just given that we have only one asset.

00:36:14.541 --> 00:36:17.513
So we're able to do that,
given our scope and our staffing.

00:36:20.930 --> 00:36:23.430
<v Lenneal>And this is Lenneal
Gardner for Trans Bay Cable.</v>

00:36:23.430 --> 00:36:27.880
Similar to Horizon West,
TBC maintains a workforce

00:36:29.170 --> 00:36:32.320
of operators and engineers that are skilled

00:36:32.320 --> 00:36:36.620
and trained on conducting similar inspections

00:36:36.620 --> 00:36:39.940
for our limited footprint of facilities.

00:36:39.940 --> 00:36:43.750
And there's an operations
director and engineering director

00:36:43.750 --> 00:36:46.603
who have that overall QC responsibility.

00:36:51.030 --> 00:36:51.863
<v Andie>Thank you so much.</v>

00:36:51.863 --> 00:36:53.902
Yes, it's definitely a lot easier

00:36:53.902 --> 00:36:55.402
when you have less facilities.

00:36:56.860 --> 00:36:59.647
With that, Ryan, did we have
any questions from the chat?

00:36:59.647 --> 00:37:01.810
I know I see the one from Leigh.

00:37:01.810 --> 00:37:03.560
I'm not sure if you got any others?

00:37:04.430 --> 00:37:07.350
<v Ryan>Yeah. That's it, Andie.</v>

00:37:07.350 --> 00:37:10.305
And I'm happy to happy to read it out.

00:37:10.305 --> 00:37:13.000
<v Andie>Sure, yeah, that'd be great.</v>

00:37:13.000 --> 00:37:14.549
<v Ryan>Great.</v>

00:37:14.549 --> 00:37:17.063
So again, this is from Leigh Kammerich.

00:37:17.920 --> 00:37:20.900
Will Liberty develop or explore
an undergrounding program

00:37:20.900 --> 00:37:23.310
outside of Rule 20A projects?

00:37:23.310 --> 00:37:25.863
Rule 20A primarily focuses on beautification

00:37:25.863 --> 00:37:29.560
and is not initiated for safety purposes.

00:37:29.560 --> 00:37:32.820
The WMP acknowledges there are RSCs in place,

00:37:32.820 --> 00:37:34.490
but undergrounding is not included

00:37:34.490 --> 00:37:39.083
as a mitigation initiative or
objective goal for the future.

00:37:42.630 --> 00:37:44.393
<v ->Yeah. So I can speak to that.</v>

00:37:45.490 --> 00:37:50.414
In general, we don't have one today.

00:37:50.414 --> 00:37:54.350
You've read the WMP and you can see that.

00:37:54.350 --> 00:37:56.933
So what we found with undergrounding projects

00:37:56.933 --> 00:38:00.930
is we run into significant,
significant permitting issues

00:38:00.930 --> 00:38:04.990
with local agencies in our area,

00:38:04.990 --> 00:38:08.230
and it just becomes cost
and timeline prohibitive

00:38:08.230 --> 00:38:10.830
to the majority of these projects.

00:38:10.830 --> 00:38:15.590
The Rule 20A ones we are
doing under that Rule 20 program,

00:38:15.590 --> 00:38:19.330
but even within those, we have
a handful of pending projects

00:38:19.330 --> 00:38:24.300
that we have tried to permit
for two, three, four years,

00:38:24.300 --> 00:38:27.550
and just hit significant roadblocks.

00:38:27.550 --> 00:38:30.390
So it's really not something we've explored

00:38:30.390 --> 00:38:35.390
at a grand scale because
it's so difficult to accomplish.

00:38:35.820 --> 00:38:40.820
What we've found is covered
conductor is much easier

00:38:40.890 --> 00:38:44.672
to implement, reusing
existing right away ways

00:38:44.672 --> 00:38:46.272
and in some ways, in some cases,

00:38:47.180 --> 00:38:48.385
you can reuse existing poles.

00:38:48.385 --> 00:38:50.790
It's much more efficient to deploy

00:38:50.790 --> 00:38:53.713
and cost-effective as well.

00:38:59.492 --> 00:39:02.100
<v Andie>Okay. Thank you so much, Dylan.</v>

00:39:02.100 --> 00:39:05.623
To sign back off with
wildfire safety division,

00:39:05.623 --> 00:39:09.143
this is again, mostly for the SMJUs.

00:39:10.303 --> 00:39:12.890
And I know you touched on this a bit

00:39:12.890 --> 00:39:14.946
during your presentations,

00:39:14.946 --> 00:39:16.280
but just wanted to get more specifics

00:39:16.280 --> 00:39:18.200
on how increased inspections differ

00:39:18.200 --> 00:39:21.470
from routine inspections
in scope and content?

00:39:21.470 --> 00:39:24.060
And also was wondering how you were measuring

00:39:24.060 --> 00:39:26.690
the effectiveness of
utilizing increased inspections

00:39:26.690 --> 00:39:29.373
in comparison to routine inspections?

00:39:32.900 --> 00:39:36.630
<v ->Sure. Another good question, Andie.</v>

00:39:36.630 --> 00:39:39.790
I think, so for increased inspections,

00:39:39.790 --> 00:39:42.370
maybe I'll clarify, I'm assuming you mean

00:39:42.370 --> 00:39:44.200
enhanced inspections or inspections

00:39:44.200 --> 00:39:46.060
we weren't historically performing,

00:39:46.060 --> 00:39:49.373
not just a volume uptick
of standard inspections?

00:39:50.610 --> 00:39:52.410
Did I get that right?

00:39:52.410 --> 00:39:55.380
<v Andie>I was looking specifically for anything</v>

00:39:55.380 --> 00:39:58.190
outside of the G.O. 165 requirements.

00:39:58.190 --> 00:39:59.700
<v ->Okay.</v>

00:39:59.700 --> 00:40:00.780
Okay, great.

00:40:00.780 --> 00:40:03.290
Then I think for us our best example,

00:40:03.290 --> 00:40:04.780
we probably have a few,

00:40:04.780 --> 00:40:07.160
our best example would
be the I.R. inspections.

00:40:07.160 --> 00:40:10.648
So there was a half
slide on, so not very much.

00:40:10.648 --> 00:40:13.480
There is a section in the
WMP that does provide

00:40:13.480 --> 00:40:15.592
a bit more information
if folks are looking for

00:40:15.592 --> 00:40:18.140
details of the program evolution,

00:40:18.140 --> 00:40:20.393
what is the scope, what are the objectives.

00:40:21.460 --> 00:40:24.250
A key component for us there is making sure

00:40:24.250 --> 00:40:25.780
we set up that program management,

00:40:25.780 --> 00:40:28.020
which was a pretty big effort in 2020.

00:40:28.020 --> 00:40:31.210
So that now in 2021, we can track things,

00:40:31.210 --> 00:40:34.460
like when exactly did we find conditions?

00:40:34.460 --> 00:40:36.200
What were the conditions like?

00:40:36.200 --> 00:40:38.870
We're assigning them
kind of different data fields

00:40:38.870 --> 00:40:41.200
in our system so we can extract them.

00:40:41.200 --> 00:40:43.030
How many line miles did we fly?

00:40:43.030 --> 00:40:44.960
And so what we're able to do now,

00:40:44.960 --> 00:40:46.782
which I think is what you're getting at,

00:40:46.782 --> 00:40:47.920
is how do I measure effectiveness

00:40:47.920 --> 00:40:49.730
or measure if it's working,

00:40:49.730 --> 00:40:51.350
is we're at a point where we can say,

00:40:51.350 --> 00:40:53.590
how many line miles did I inspect?

00:40:53.590 --> 00:40:56.910
How many things did I find
that potentially pose risks?

00:40:56.910 --> 00:40:57.870
What were the costs?

00:40:57.870 --> 00:41:00.405
And we actually look at cost per finding

00:41:00.405 --> 00:41:04.050
and cost per mile
associated with that program.

00:41:04.050 --> 00:41:06.680
And then we can compare
to our traditional programs

00:41:06.680 --> 00:41:08.908
and at least show, yes, there's value.

00:41:08.908 --> 00:41:13.597
If there is value, is it
more, is it about the same?

00:41:13.597 --> 00:41:15.750
And also kind of tie that value back

00:41:15.750 --> 00:41:18.220
to the risk drivers that
Heide presented this morning.

00:41:18.220 --> 00:41:20.347
So making sure that the things we're finding

00:41:20.347 --> 00:41:23.516
are the things that tend
to get us in other areas.

00:41:23.516 --> 00:41:26.040
And so that's kind of, that's
probably my best example

00:41:26.040 --> 00:41:28.790
to provide on how we're implementing

00:41:28.790 --> 00:41:30.561
these enhanced or additional inspections

00:41:30.561 --> 00:41:32.673
and then how we're tracking effectiveness.

00:41:39.140 --> 00:41:40.590
<v ->Thank you for the question.</v>

00:41:41.490 --> 00:41:45.000
So as of today, Liberty is not proposing

00:41:45.000 --> 00:41:49.860
increased inspection
timelines on any of our assets.

00:41:49.860 --> 00:41:52.427
However, it is something
we are strongly considering.

00:41:52.427 --> 00:41:56.510
I would like to point again
to the really important strides

00:41:56.510 --> 00:42:00.250
we made in 2020 in refining
our inspection process.

00:42:00.250 --> 00:42:01.710
And we did actually inspect

00:42:01.710 --> 00:42:05.300
the entire overhead system within 2020.

00:42:05.300 --> 00:42:08.193
So, in some regards there, we actually did

00:42:08.193 --> 00:42:11.700
perform inspections with increased frequency,

00:42:11.700 --> 00:42:14.863
'cause some of those circuits
were just inspected last year.

00:42:16.056 --> 00:42:21.030
But I think we're kind of
waiting for our risk mapping

00:42:21.030 --> 00:42:22.940
and modeling to really identify,

00:42:22.940 --> 00:42:27.940
is there increased benefit
in inspecting the circuits,

00:42:28.490 --> 00:42:31.770
for example, within high
or very high fire threat areas

00:42:31.770 --> 00:42:33.543
with an increased frequency?

00:42:34.820 --> 00:42:37.080
And what does that buy us, exactly?

00:42:37.080 --> 00:42:39.430
And then past that, as
far as new technologies

00:42:39.430 --> 00:42:41.810
we're investigating for inspections,

00:42:41.810 --> 00:42:45.410
we are actively investigating both drone

00:42:45.410 --> 00:42:47.080
and infrared technology,

00:42:47.080 --> 00:42:51.490
integrating that into our
G.O. 165 inspections.

00:42:51.490 --> 00:42:52.323
Thank you.

00:42:57.550 --> 00:43:02.277
<v ->So, I think inspection is actually low cost</v>

00:43:02.277 --> 00:43:06.583
when you compare it to what
you're potentially preventing.

00:43:07.900 --> 00:43:12.060
For example, for us, a LiDAR or a UAV

00:43:12.060 --> 00:43:16.130
or a second ground patrol
is probably on the order

00:43:16.130 --> 00:43:20.883
of about 100,000.00 per
year per type of inspection.

00:43:22.260 --> 00:43:26.340
That's fairly low cost to
compare to a major failure

00:43:28.355 --> 00:43:30.930
or a, God forbid, a wildfire.

00:43:30.930 --> 00:43:35.530
So definitely worth doing, worth pursuing.

00:43:35.530 --> 00:43:39.788
I think as all the utilities
have gone through this process

00:43:39.788 --> 00:43:44.710
and we've all sort of matured
on the inspection front,

00:43:44.710 --> 00:43:48.230
I would say that pretty soon,

00:43:48.230 --> 00:43:52.280
the G.O. 165 is probably ripe for a revisit

00:43:53.320 --> 00:43:55.410
on what the minimum requirements are.

00:43:55.410 --> 00:43:56.710
I think everybody would agree

00:43:56.710 --> 00:44:00.675
that if you were just doing
what G.O. 165 specifically says,

00:44:00.675 --> 00:44:05.675
you're not anywhere close
to where you should be.

00:44:06.301 --> 00:44:10.360
So there is a lot of value in bringing

00:44:10.360 --> 00:44:14.703
all these inspections together and certainly,

00:44:15.720 --> 00:44:19.803
it helps avoid issues that
you just don't want to develop.

00:44:24.870 --> 00:44:25.703
<v Andie>Thank you.</v>

00:44:25.703 --> 00:44:26.620
Just for clarification,

00:44:26.620 --> 00:44:29.740
does Bear Valley currently do anything,

00:44:29.740 --> 00:44:31.963
outside of the G.O. 165 requirements?

00:44:33.290 --> 00:44:34.470
<v ->Yeah, we do LiDAR.</v>

00:44:34.470 --> 00:44:37.363
We do a second ground patrol inspection.

00:44:38.420 --> 00:44:40.549
And we're adding UAVs, HD imaging.

00:44:40.549 --> 00:44:43.551
We've done thermography.

00:44:43.551 --> 00:44:48.551
So we go beyond what's the
minimum requirement there.

00:44:50.690 --> 00:44:53.560
And now we're looking at
also increasing the periodicity

00:44:53.560 --> 00:44:58.303
of detailed inspections
on higher risk circuits.

00:45:01.965 --> 00:45:03.165
<v Andie>Thanks so much</v>

00:45:05.650 --> 00:45:09.863
Back to GCI, it looks like
Zoe has another question.

00:45:11.660 --> 00:45:12.710
<v Zoe>Yeah, thanks.</v>

00:45:13.555 --> 00:45:17.436
So for the SMJUs, can
you talk a little bit about

00:45:17.436 --> 00:45:20.385
if and how you're proactively assessing

00:45:20.385 --> 00:45:22.690
and replacing aging equipment?

00:45:22.690 --> 00:45:24.620
And if that process is informed

00:45:24.620 --> 00:45:27.773
by data or risk driven assessments?

00:45:32.260 --> 00:45:33.504
<v ->Sure.</v>

00:45:33.504 --> 00:45:36.371
So I would say right now we do mainly,

00:45:36.371 --> 00:45:39.370
I'm gonna call it
condition-based replacement.

00:45:39.370 --> 00:45:43.020
So driven more by field inspections,

00:45:43.020 --> 00:45:45.760
on-site work, noticeable changes

00:45:45.760 --> 00:45:49.319
in the quality of the power potentially,

00:45:49.319 --> 00:45:53.243
due to outage
investigations, things like that.

00:45:54.980 --> 00:45:57.020
We are exploring ways to do more,

00:45:57.020 --> 00:45:58.740
I would say predictive modeling.

00:45:58.740 --> 00:46:02.910
So whether it's through some
sort of asset health assessment

00:46:02.910 --> 00:46:07.440
or a carry over from the
wildfire risk modeling efforts

00:46:07.440 --> 00:46:09.610
that are ongoing, is there a way to get

00:46:09.610 --> 00:46:12.360
ahead of the game a
little bit and catch things

00:46:12.360 --> 00:46:14.882
before there's noticeable deterioration?

00:46:14.882 --> 00:46:17.070
I know that that is certainly something

00:46:17.070 --> 00:46:19.100
as a company we want to do.

00:46:19.100 --> 00:46:20.830
I just don't think we're quite there yet,

00:46:20.830 --> 00:46:23.200
to say that I know exactly when to replace

00:46:23.200 --> 00:46:26.714
that widget on that line
because data tells me.

00:46:26.714 --> 00:46:30.380
But I think we're working
on incorporating things

00:46:30.380 --> 00:46:32.932
like inspection findings, power quality,

00:46:32.932 --> 00:46:37.932
age, manufacturer, applications,
how am I operating it?

00:46:39.290 --> 00:46:41.200
To try and get us eventually to some sort

00:46:41.200 --> 00:46:42.790
of predictive model.

00:46:42.790 --> 00:46:44.813
I just don't think we're quite there yet.

00:46:45.870 --> 00:46:49.086
Hopefully that answers your question.

00:46:49.086 --> 00:46:51.253
<v Zoe>It did. Thank you.</v>

00:46:54.570 --> 00:46:59.400
<v ->So, yeah, we're largely in
the same boat as of today.</v>

00:46:59.400 --> 00:47:04.000
All of our asset replacement is done

00:47:04.000 --> 00:47:06.800
based on inspections, essentially.

00:47:06.800 --> 00:47:10.530
We do have in the past year
really started prioritizing that

00:47:10.530 --> 00:47:13.005
with our risk mapping and modeling,

00:47:13.005 --> 00:47:17.939
all of the condition
codes for different failures,

00:47:17.939 --> 00:47:21.163
not failures, but issues with equipment,

00:47:22.180 --> 00:47:27.180
has an associated fire
risk zone as well as HFTD.

00:47:28.290 --> 00:47:31.593
And we are prioritizing
based on that information.

00:47:32.600 --> 00:47:36.920
And then lastly, as far as
the asset health evaluation,

00:47:36.920 --> 00:47:40.350
with the DFA technology,
we are really hoping that

00:47:40.350 --> 00:47:43.463
that's kind of at least
part of the answer there.

00:47:45.009 --> 00:47:47.440
That's pretty tough stuff to evaluate

00:47:47.440 --> 00:47:50.363
the condition of every piece of equipment,

00:47:52.610 --> 00:47:55.400
based on anything other
than a visual inspection.

00:47:55.400 --> 00:47:59.240
But, yeah, the distribution
fault anticipation technology

00:47:59.240 --> 00:48:02.880
should be able to identify
some of those incipient failures

00:48:02.880 --> 00:48:06.100
and help prioritize that work as well.

00:48:06.100 --> 00:48:10.784
Thank you.

00:48:10.784 --> 00:48:15.784
<v ->I think we're condition-based
for replacement of assets.</v>

00:48:18.760 --> 00:48:23.760
I don't really know of any
age based type programs.

00:48:24.710 --> 00:48:26.750
I do know that when we do go out

00:48:26.750 --> 00:48:30.510
and work on a system or a series of poles,

00:48:30.510 --> 00:48:33.543
we may bring that whole system up-to-date,

00:48:37.146 --> 00:48:39.110
so that we don't have to keep going back

00:48:39.110 --> 00:48:40.760
out to that one particular area.

00:48:40.760 --> 00:48:42.990
It's more efficient to do it that way.

00:48:42.990 --> 00:48:46.100
But we don't say, oh, we're
gonna target these items

00:48:46.100 --> 00:48:49.973
because it hits this value in age.

00:48:54.976 --> 00:48:58.354
<v Zoe>Great. Thank you, everyone.</v>

00:48:58.354 --> 00:49:01.560
<v Andie>So we've got around five minutes left.</v>

00:49:01.560 --> 00:49:04.930
So I think enough time for one more question.

00:49:04.930 --> 00:49:07.693
Henry with Cal Advocates,
you had another one.

00:49:08.910 --> 00:49:10.480
<v ->Yeah, that'd be great.</v>

00:49:10.480 --> 00:49:13.140
So this question was mainly
intended for PacifiCorp.

00:49:15.375 --> 00:49:19.320
At PacifiCorp it looks
like was not able to install

00:49:19.320 --> 00:49:21.417
as many miles of covered conductor

00:49:21.417 --> 00:49:24.800
and as many pole replacements in 2020

00:49:24.800 --> 00:49:28.227
as had been forecast last year.

00:49:28.227 --> 00:49:32.033
Can you discuss how the 2020 fire season

00:49:32.033 --> 00:49:36.990
affected your system hardening work

00:49:36.990 --> 00:49:41.150
and how you've built that type of issue

00:49:41.150 --> 00:49:43.290
into your planning going forward?

00:49:43.290 --> 00:49:48.290
How have you accounted for disruption due

00:49:49.510 --> 00:49:51.921
to fire season or other
kinds of natural disasters

00:49:51.921 --> 00:49:53.523
in your wildfire mitigation planning?

00:49:55.550 --> 00:49:56.383
<v ->Sure.</v>

00:49:57.300 --> 00:49:59.050
There's kind of, it sounds
like there's two components

00:49:59.050 --> 00:50:00.620
you're interested in, the pole replacements,

00:50:00.620 --> 00:50:03.920
as well as the implementation
of covered conductor.

00:50:03.920 --> 00:50:06.540
And so first I'll take the pole replacements.

00:50:06.540 --> 00:50:09.260
I think in previous years of the plan

00:50:09.260 --> 00:50:12.370
we had been a little bit
light on a full scoping,

00:50:12.370 --> 00:50:15.300
so weren't sure the specific details.

00:50:15.300 --> 00:50:19.360
And so a lot of our annual
phasings were estimates,

00:50:19.360 --> 00:50:21.640
very educated estimates, but estimates.

00:50:21.640 --> 00:50:24.370
We have actually made
a shift change in that area

00:50:24.370 --> 00:50:27.290
where we are targeting pole replacements

00:50:27.290 --> 00:50:29.950
coincident to covered conductor programs,

00:50:29.950 --> 00:50:32.140
and waiting to phase in the pole replacements

00:50:32.140 --> 00:50:35.890
in lower risk areas later,
which is kind of why,

00:50:35.890 --> 00:50:38.250
if you saw on the slide,
you see the pole placements

00:50:38.250 --> 00:50:41.370
are kind of light and
then they ramp up later.

00:50:41.370 --> 00:50:44.310
So that one's a little
bit of a program shift,

00:50:44.310 --> 00:50:47.270
as well as a little bit
more of a program shift,

00:50:47.270 --> 00:50:49.354
I would say, and a philosophy shift,

00:50:49.354 --> 00:50:51.430
than a lagging of completion.

00:50:51.430 --> 00:50:53.320
On the covered conductor, I think, honestly,

00:50:53.320 --> 00:50:56.100
I think our main hiccup
there is, you are correct,

00:50:56.100 --> 00:50:58.749
we have not done as much as
we'd hoped for or planned for.

00:50:58.749 --> 00:51:03.740
I think for us, we underestimated
some of the challenges

00:51:03.740 --> 00:51:07.240
and they're the types of
challenges Liberty brought up,

00:51:07.240 --> 00:51:11.100
the challenges with engineering
and designing a new spec,

00:51:11.100 --> 00:51:13.920
the challenges with how are we gonna maintain

00:51:13.920 --> 00:51:17.300
this new equipment,
especially when it's deployed

00:51:17.300 --> 00:51:20.120
so regularly throughout.

00:51:20.120 --> 00:51:22.170
It's that change management piece.

00:51:22.170 --> 00:51:26.420
And what that's done is it's
really changed the pipeline

00:51:26.420 --> 00:51:29.270
that it takes and the timeline
to deliver those projects.

00:51:31.100 --> 00:51:35.393
And so that was an
unfortunate hurdle, I would say,

00:51:35.393 --> 00:51:37.043
we didn't see coming in that way.

00:51:38.090 --> 00:51:40.130
Changes that we've made,

00:51:40.130 --> 00:51:43.870
I think the big part is recognizing that.

00:51:43.870 --> 00:51:46.940
We have brought on more engineering resources

00:51:46.940 --> 00:51:48.710
to help with the engineering and the scoping

00:51:48.710 --> 00:51:50.110
and the startup efforts to really

00:51:50.110 --> 00:51:51.773
get those projects kicked off.

00:51:52.620 --> 00:51:54.610
We're requiring, it's a fairly linear process

00:51:54.610 --> 00:51:56.814
before we get to where we're actually

00:51:56.814 --> 00:51:58.440
procuring materials and constructing.

00:51:58.440 --> 00:51:59.680
And I would say the positive is,

00:51:59.680 --> 00:52:02.010
I do believe right now we're forecasting

00:52:02.010 --> 00:52:04.060
that we can catch up this year.

00:52:04.060 --> 00:52:06.290
So while we weren't able to do what we wanted

00:52:06.290 --> 00:52:09.510
to do last year, right now,
we're planning to play catch up

00:52:09.510 --> 00:52:12.673
and trying to deliver just
over 80 miles this year.

00:52:13.550 --> 00:52:14.830
And that is what we've brought on

00:52:14.830 --> 00:52:17.170
those engineering
resources for, to play catch up.

00:52:17.170 --> 00:52:19.532
So I think for us, it was as much of a,

00:52:19.532 --> 00:52:23.531
really fully understanding
the process and what it takes

00:52:23.531 --> 00:52:25.647
to put these new projects in.

00:52:25.647 --> 00:52:28.823
And I think we underestimated
that effort, to be honest.

00:52:29.970 --> 00:52:31.960
Certainly we had some
other disruptions throughout

00:52:31.960 --> 00:52:34.370
the year that that made
us change some things.

00:52:34.370 --> 00:52:35.990
But I think really the core issue

00:52:35.990 --> 00:52:39.035
is understanding what it takes.

00:52:39.035 --> 00:52:40.885
I think we underestimated that a bit.

00:52:47.540 --> 00:52:48.500
<v ->Okay. Thanks.</v>

00:52:48.500 --> 00:52:51.460
And if we have just a moment, real quickly,

00:52:51.460 --> 00:52:55.610
it looks like from your
plan, the cost per mile

00:52:55.610 --> 00:52:58.420
for your covered conductor program

00:52:58.420 --> 00:53:03.420
is around 180,000.00 to $230,000.00 per mile,

00:53:03.970 --> 00:53:05.970
if I'm looking at the numbers correctly.

00:53:06.970 --> 00:53:07.803
Is that correct?

00:53:07.803 --> 00:53:09.730
That's much lower than
what the larger utilities

00:53:09.730 --> 00:53:13.293
are expecting as unit
cost for covered conductor.

00:53:15.187 --> 00:53:19.143
<v ->I'd have to pull up the plan that,</v>

00:53:20.260 --> 00:53:22.220
it sounds like the right order of magnitude.

00:53:22.220 --> 00:53:24.680
I'm not sure of the specifics.

00:53:24.680 --> 00:53:27.230
So I might to check with some folks.

00:53:27.230 --> 00:53:29.850
It does sound less than what
the other utilities put forth.

00:53:29.850 --> 00:53:34.220
I'm trying to remember if
we've done that full calculation.

00:53:34.220 --> 00:53:36.190
It could be slightly different scope though.

00:53:36.190 --> 00:53:37.023
So I would want to,

00:53:37.023 --> 00:53:39.690
before I commit to this being exactly it,

00:53:39.690 --> 00:53:42.365
I would want to do some
checking to not lead you astray.

00:53:42.365 --> 00:53:46.340
It could be that our covered
conductor replacement

00:53:46.340 --> 00:53:49.560
doesn't always include full pole replacement,

00:53:49.560 --> 00:53:50.430
but then always include

00:53:50.430 --> 00:53:53.580
some of the other bells and whistles.

00:53:53.580 --> 00:53:55.870
As kind of similar to what
Liberty is talking about,

00:53:55.870 --> 00:53:59.250
the reason it's a nice
technology to deploy quickly is

00:53:59.250 --> 00:54:01.510
that sometimes you can
use existing structures.

00:54:01.510 --> 00:54:04.150
But I'm not sure is if
that's driving the difference,

00:54:04.150 --> 00:54:07.603
but that could be a driver
of the difference in unit cost.

00:54:09.611 --> 00:54:11.840
And I think maybe, I think around, for us,

00:54:11.840 --> 00:54:14.180
we see about 10 to 15% pole replacements,

00:54:14.180 --> 00:54:19.180
where some utilities may
require 100% or 80% or 50%.

00:54:20.080 --> 00:54:23.460
But that certainly can make an impact.

00:54:23.460 --> 00:54:24.293
<v ->Okay. Yeah.</v>

00:54:24.293 --> 00:54:25.260
That could be a factor.

00:54:25.260 --> 00:54:28.530
But just the order of
magnitude sounds correct to you

00:54:28.530 --> 00:54:30.490
that you're talking about
something on the order

00:54:30.490 --> 00:54:35.053
of like 200, less than half
a million dollars per mile?

00:54:36.130 --> 00:54:38.280
I do think that seems like
the right order of magnitude.

00:54:38.280 --> 00:54:39.900
I want to check and make sure.

00:54:39.900 --> 00:54:41.852
But less than half a million makes sense.

00:54:41.852 --> 00:54:43.623
Yeah, mm hm.

00:54:44.470 --> 00:54:45.370
<v ->Okay. Thank you.</v>

00:54:47.940 --> 00:54:48.773
<v Andie>Okay, and with that,</v>

00:54:48.773 --> 00:54:52.070
we'll go ahead and take a break

00:54:52.070 --> 00:54:54.671
and catch back up with
Vegetation Management after.

00:54:54.671 --> 00:54:58.441
Just wanted to give a
thank you to all the panelists.

00:54:58.441 --> 00:55:00.620
This has been extremely informative.

00:55:00.620 --> 00:55:03.070
And also a thank you to stakeholders

00:55:03.070 --> 00:55:06.423
and for asking great questions.

00:55:08.210 --> 00:55:10.103
So we'll resume at 2:30.

00:55:16.145 --> 00:55:18.728
(upbeat music)

00:55:24.658 --> 00:55:27.241
(upbeat music)

00:59:49.430 --> 00:59:50.773
<v ->My name is Colin Lang.</v>

00:59:52.104 --> 00:59:53.320
I am the Environmental Scientist

00:59:53.320 --> 00:59:55.200
with the Wildfire Safety Division.

00:59:55.200 --> 00:59:58.223
I have the pleasure to
moderate our discussion

00:59:58.223 --> 01:00:00.680
this afternoon, concerning
Vegetation Management.

01:00:00.680 --> 01:00:02.930
Vegetation management can both reduce

01:00:02.930 --> 01:00:05.620
wildfire ignition and consequence risk.

01:00:05.620 --> 01:00:07.360
It involves planning for both

01:00:07.360 --> 01:00:10.170
the canopy surrounding overhead lines

01:00:10.170 --> 01:00:13.313
and the understory in and
around the right-of-way.

01:00:14.530 --> 01:00:17.230
Landscape structures modified by colonization

01:00:17.230 --> 01:00:19.010
and our changing climate have made

01:00:19.010 --> 01:00:22.080
vegetation management efforts challenging

01:00:22.080 --> 01:00:24.250
and require land managers and utilities

01:00:24.250 --> 01:00:27.320
to constantly adjust to the present,

01:00:27.320 --> 01:00:29.503
sometimes unprecedented, conditions.

01:00:30.740 --> 01:00:33.110
In the past few years,
utilities have increased

01:00:33.110 --> 01:00:35.900
the scale and scope of their
vegetation management programs

01:00:35.900 --> 01:00:37.133
to address these issues.

01:00:39.076 --> 01:00:41.712
Just like before, in round three,

01:00:41.712 --> 01:00:46.712
we'll hear from the PacifiCorp,
Liberty, and Bear Valley

01:00:47.420 --> 01:00:49.660
about their vegetation management plans.

01:00:49.660 --> 01:00:52.720
And then we'll have a
short five minute break,

01:00:52.720 --> 01:00:57.108
followed by a question and
answer panel with our presenters.

01:00:57.108 --> 01:01:01.590
So first up is PacifiCorp.

01:01:10.450 --> 01:01:12.490
<v Brian>Hi, this is Brian King with PacifiCorp.</v>

01:01:12.490 --> 01:01:17.070
I think the presentation
that is showing is different.

01:01:17.070 --> 01:01:19.120
It is not the Pacific Power presentation.

01:01:22.450 --> 01:01:24.330
There we go. Thank you.

01:01:24.330 --> 01:01:26.700
So again, this Brian King

01:01:26.700 --> 01:01:28.473
I'm the Director of Vegetation Management

01:01:28.473 --> 01:01:30.230
with Pacific Power.

01:01:30.230 --> 01:01:34.150
I'll provide a very high level overview

01:01:34.150 --> 01:01:38.540
of our vegetation management
accomplishments in 2020

01:01:38.540 --> 01:01:41.580
with respect to our wildfire mitigation plan,

01:01:41.580 --> 01:01:45.483
as well as general vegetation
management program,

01:01:46.510 --> 01:01:50.368
as well as some areas of opportunity,

01:01:50.368 --> 01:01:54.280
areas that we're looking into
to implement improvements

01:01:54.280 --> 01:01:58.330
and investigate further,
including additional technologies.

01:01:58.330 --> 01:02:02.010
And Heide Caswell will speak
to some of the pilot projects

01:02:02.010 --> 01:02:03.930
that we are currently implementing

01:02:03.930 --> 01:02:06.733
or have implemented
with respect to technology.

01:02:07.895 --> 01:02:09.173
Next slide.

01:02:17.980 --> 01:02:20.820
In 2020, Pacific Power conducted

01:02:20.820 --> 01:02:22.450
what I'm calling readiness patrols.

01:02:22.450 --> 01:02:27.450
So these are patrols that are
incremental to our inspections

01:02:27.720 --> 01:02:32.290
in support of our scheduled
routine maintenance work.

01:02:32.290 --> 01:02:35.410
We conducted these readiness
patrols on over 1,100 miles

01:02:35.410 --> 01:02:39.967
of transmission and
distribution lines within HFTD

01:02:40.830 --> 01:02:43.113
prior to the height of the fire season.

01:02:44.030 --> 01:02:48.120
So this is a large effort in addition

01:02:48.120 --> 01:02:51.563
to our routine maintenance
activities that we completed.

01:02:52.588 --> 01:02:55.450
We continue to work on reducing

01:02:55.450 --> 01:02:58.520
our high risk tree inventory.

01:02:58.520 --> 01:03:00.600
So we continue to identify and address

01:03:00.600 --> 01:03:04.273
our high risk trees along
our power line corridors.

01:03:05.220 --> 01:03:08.690
In 2020, as an area for opportunity,

01:03:08.690 --> 01:03:12.230
we started to identify trees
that we call cycle busters,

01:03:12.230 --> 01:03:14.370
or those are the very fast growing trees

01:03:14.370 --> 01:03:17.720
that may not hold for an entire cycle.

01:03:17.720 --> 01:03:20.490
And in collecting that information,

01:03:20.490 --> 01:03:25.490
which we can utilize in
the future for opportunities

01:03:26.665 --> 01:03:30.680
or identifying future
management opportunities

01:03:30.680 --> 01:03:32.090
with respect to cycle busters.

01:03:32.090 --> 01:03:35.720
So we just started collecting
that information in 2020

01:03:35.720 --> 01:03:37.973
and are starting to build that database.

01:03:41.280 --> 01:03:44.564
We cleared vegetation around poles,

01:03:44.564 --> 01:03:47.920
incremental to our regulatory mandated

01:03:49.212 --> 01:03:54.040
pole clearing projects, so
over 2,000 additional poles

01:03:54.040 --> 01:03:59.040
were cleared within high risk fire areas.

01:04:00.370 --> 01:04:04.770
We continue to apply herbicides
and tree growth regulators.

01:04:04.770 --> 01:04:07.630
So this is an integral part of
our vegetation management

01:04:07.630 --> 01:04:11.160
to control tall growing
and fast growing species,

01:04:11.160 --> 01:04:13.610
respectively, as part of

01:04:13.610 --> 01:04:16.313
the integrated vegetation management.

01:04:16.313 --> 01:04:21.224
And we also, in addition to
conducting the inspections,

01:04:21.224 --> 01:04:26.090
those readiness patrols,
for over 1,100 miles,

01:04:26.090 --> 01:04:30.808
we conducted and addressed
any correction activities,

01:04:30.808 --> 01:04:33.650
so corrected and addressed

01:04:33.650 --> 01:04:35.660
those vegetation management conditions

01:04:35.660 --> 01:04:38.720
that were identified during
the readiness patrols,

01:04:38.720 --> 01:04:43.720
in addition to our routine
maintenance corrective actions.

01:04:44.920 --> 01:04:49.710
And we also conducted
post-audits of all work conducted,

01:04:49.710 --> 01:04:52.270
as identified in the routine maintenance

01:04:52.270 --> 01:04:54.860
detailed inspections, as
well as readiness patrols,

01:04:54.860 --> 01:04:59.420
to ensure all work was completed
to company specification,

01:04:59.420 --> 01:05:03.263
and that adequate clearances were achieved.

01:05:05.103 --> 01:05:08.750
Areas where we're looking for improvement,

01:05:08.750 --> 01:05:11.375
or opportunity areas.

01:05:11.375 --> 01:05:15.750
We've implemented, in
2020, the rollout of a new

01:05:15.750 --> 01:05:19.233
electronic planning, mapping,
record keeping system.

01:05:20.192 --> 01:05:24.020
This is so our folks out in the field

01:05:24.020 --> 01:05:28.460
can utilize handheld
tablets to record information,

01:05:28.460 --> 01:05:31.300
the work, identifies the work
that needs to be conducted,

01:05:31.300 --> 01:05:34.810
and then our tree contractors
who perform the work

01:05:34.810 --> 01:05:38.850
also can then record work
completed utilizing tablets.

01:05:38.850 --> 01:05:41.950
And so we have an improved tracking system.

01:05:41.950 --> 01:05:44.683
We're continuously fine tuning our system.

01:05:45.690 --> 01:05:48.360
As mentioned in 2020, we started identifying

01:05:48.360 --> 01:05:51.199
cycle buster trees as well
and have the opportunity

01:05:51.199 --> 01:05:54.550
to collect different types of data.

01:05:54.550 --> 01:05:57.590
So we're continually refining our approach

01:05:57.590 --> 01:06:00.290
and how we're using that
data and collecting that data

01:06:01.311 --> 01:06:06.311
to help inform additional
components of our program,

01:06:07.900 --> 01:06:10.433
for example, tree growth regulators,

01:06:10.433 --> 01:06:14.460
as well as identifying tree cycle busters.

01:06:14.460 --> 01:06:17.520
We can then have an inventory

01:06:17.520 --> 01:06:20.450
where we can potentially identify

01:06:21.380 --> 01:06:23.240
the use of tree growth regulators

01:06:23.240 --> 01:06:25.820
on those cycle buster trees to better manage

01:06:25.820 --> 01:06:28.333
those fast growing tree species.

01:06:29.190 --> 01:06:31.790
We continue to partner
with our local agencies

01:06:31.790 --> 01:06:33.720
for fuel reduction.

01:06:33.720 --> 01:06:34.927
This year, we coordinated with

01:06:34.927 --> 01:06:37.180
the Dunsmuir Wildfire Safety Council

01:06:37.180 --> 01:06:40.440
to assist on a fuel reduction project

01:06:40.440 --> 01:06:42.503
between the I-5 and Dunsmuir.

01:06:43.609 --> 01:06:47.180
And we had distribution
lines in the project area

01:06:47.180 --> 01:06:48.500
and partnered with the community

01:06:48.500 --> 01:06:50.910
to safely remove vegetation around

01:06:50.910 --> 01:06:52.970
and adjacent to our facilities.

01:06:52.970 --> 01:06:55.410
And we continue to look for opportunities

01:06:55.410 --> 01:06:59.843
to partner with agencies
with respect to fuel reduction.

01:07:01.670 --> 01:07:06.027
We're implementing additional means

01:07:08.620 --> 01:07:11.580
of identifying how to prioritize our work.

01:07:11.580 --> 01:07:16.580
So we are developing,
in addition to utilizing

01:07:17.210 --> 01:07:20.300
just the HFTD, for example, and using that

01:07:20.300 --> 01:07:22.520
as a means to prioritize work,

01:07:22.520 --> 01:07:25.729
we're looking at more granularity

01:07:25.729 --> 01:07:29.660
to refine within the HFTD other areas,

01:07:29.660 --> 01:07:32.598
circuits, or segments
of circuits that would be

01:07:32.598 --> 01:07:36.150
of higher ignition risk than other areas

01:07:36.150 --> 01:07:38.190
or have a higher consequence,

01:07:38.190 --> 01:07:40.913
to help us prioritize our work.

01:07:41.820 --> 01:07:44.084
And we're utilizing additional technology,

01:07:44.084 --> 01:07:49.084
such as remote sensing, LiDAR, and so forth,

01:07:49.170 --> 01:07:52.310
and conducting pilot projects

01:07:52.310 --> 01:07:54.590
with respect to this technology,

01:07:54.590 --> 01:07:58.703
Heide Caswell will give
you a high level overview on.

01:08:00.180 --> 01:08:01.013
Next slide.

01:08:10.100 --> 01:08:12.070
<v Heide>So this is Heide Caswell.</v>

01:08:12.070 --> 01:08:14.640
Just adding in some pieces

01:08:14.640 --> 01:08:17.870
to Brian's discussion around vegetation.

01:08:17.870 --> 01:08:22.870
We've been using some of the
advanced analytics capabilities

01:08:24.890 --> 01:08:28.900
to try and bolster our understanding

01:08:28.900 --> 01:08:33.900
of the vegetation risks that
exist around our facilities.

01:08:34.860 --> 01:08:36.120
And doing this through

01:08:36.120 --> 01:08:38.670
a couple of different pilot approaches.

01:08:38.670 --> 01:08:43.223
They're described in our
WMP in, I think, Section 4.1.1,

01:08:44.570 --> 01:08:47.220
where we talk about the
different pilot activities.

01:08:47.220 --> 01:08:50.680
But this, I'll go into some detail here

01:08:50.680 --> 01:08:54.763
to try to provide some context.

01:08:56.030 --> 01:09:00.430
We have done some remote
sensing vegetation pilot work.

01:09:00.430 --> 01:09:03.820
and this has been largely focused

01:09:03.820 --> 01:09:08.820
on various aspects of LiDAR and using LiDAR,

01:09:09.726 --> 01:09:13.300
as Amy spoke previously about.

01:09:13.300 --> 01:09:17.750
as an input to equipment failure, modeling,

01:09:17.750 --> 01:09:20.080
pole strengths, those sorts of things.

01:09:20.080 --> 01:09:24.200
The same datasets
were used to try to identify

01:09:25.410 --> 01:09:29.380
certain aspect features that
are valuable for vegetation.

01:09:29.380 --> 01:09:32.670
So trying to leverage the cost of putting

01:09:32.670 --> 01:09:37.131
a helicopter up in the air and
the amount of post-processing

01:09:37.131 --> 01:09:41.190
that goes with it, in order to understand

01:09:42.914 --> 01:09:47.680
the environment around the utility equipment.

01:09:47.680 --> 01:09:51.010
So you see on the right side,

01:09:51.010 --> 01:09:54.160
some of the different
graphics that exist there.

01:09:54.160 --> 01:09:56.590
Historically what we had focused on

01:09:56.590 --> 01:09:59.494
in our vegetation program was

01:09:59.494 --> 01:10:03.160
an understanding of every circuit

01:10:03.160 --> 01:10:05.750
and how many miles that circuit was,

01:10:05.750 --> 01:10:07.950
whether it was overhead or not,

01:10:07.950 --> 01:10:10.080
and obviously the overhead being the one

01:10:10.080 --> 01:10:12.540
we were working on the clearance for.

01:10:12.540 --> 01:10:16.290
And then kind of the run
rate associated with paying

01:10:16.290 --> 01:10:21.290
for the vegetation work
that was delivered there.

01:10:23.410 --> 01:10:26.560
So in order to start to develop

01:10:26.560 --> 01:10:31.530
a more comprehensive
inventory we started looking at

01:10:31.530 --> 01:10:35.010
the conventionally
available datasets that exist

01:10:35.010 --> 01:10:39.230
and used the National Land Cover data

01:10:39.230 --> 01:10:44.230
to try to build basically
a proxy for an inventory,

01:10:45.740 --> 01:10:50.740
which was used in our risk modeling tool

01:10:50.930 --> 01:10:52.540
that I spoke about earlier,

01:10:52.540 --> 01:10:55.460
where we then come up
with a zonal canopy amount.

01:10:55.460 --> 01:10:58.650
That is also information that's informative

01:10:58.650 --> 01:11:03.300
for the forester, but it isn't
as much as they need to have.

01:11:03.300 --> 01:11:08.300
So what we piloted was
the use of the LiDAR flights

01:11:09.300 --> 01:11:14.300
in order to do a certain amount
of vegetation segmentation

01:11:16.140 --> 01:11:18.360
so that we'd know what was coniferous,

01:11:18.360 --> 01:11:23.007
what was deciduous and
how many trees of what sort

01:11:25.060 --> 01:11:30.007
were within distance
of our utility equipment.

01:11:31.654 --> 01:11:36.654
We've had several different efforts on that.

01:11:37.230 --> 01:11:42.230
And while it is, we've had
good results with them,

01:11:45.610 --> 01:11:47.330
it is not necessarily something

01:11:47.330 --> 01:11:50.180
that is broadly applicable,

01:11:50.180 --> 01:11:52.693
just with the large footprint that we cover.

01:11:53.530 --> 01:11:56.450
I know that Paul's said several times

01:11:56.450 --> 01:11:59.203
that Bear Valley is 32 square miles.

01:12:00.372 --> 01:12:02.839
We are 11,000 square miles.

01:12:02.839 --> 01:12:07.170
And so getting that kind of LiDAR coverage

01:12:07.170 --> 01:12:09.160
for our service territory would come

01:12:09.160 --> 01:12:10.730
at an extremely high price.

01:12:10.730 --> 01:12:13.880
So instead, what we've been working with

01:12:15.836 --> 01:12:19.287
is enhanced satellite data that Salo,

01:12:22.241 --> 01:12:27.241
one of the subcontractors
to the Pyrogence Project,

01:12:27.310 --> 01:12:31.950
has been developing across California.

01:12:31.950 --> 01:12:34.740
We've been using that dataset.

01:12:34.740 --> 01:12:36.760
And I think that you can
see, or hopefully you can see

01:12:36.760 --> 01:12:41.760
in the lower, or in the
graphics to the right side,

01:12:42.750 --> 01:12:45.330
you can see what we're dealing with

01:12:45.330 --> 01:12:49.250
in terms of the pixelation that exists there.

01:12:49.250 --> 01:12:53.400
On the next slide you actually start to see

01:12:53.400 --> 01:12:57.100
some of the features that the enhanced

01:12:57.100 --> 01:12:59.650
satellite technology delivers.

01:12:59.650 --> 01:13:01.970
And this is a discussion about the,

01:13:01.970 --> 01:13:05.350
or the next slide shows
you what we're intending

01:13:05.350 --> 01:13:08.483
on doing in a two phase pilot.

01:13:10.510 --> 01:13:14.810
The first phase is very
focused around trees that,

01:13:17.460 --> 01:13:19.670
with terrain considered,

01:13:19.670 --> 01:13:22.420
and the height of that particular tree,

01:13:22.420 --> 01:13:26.180
have a strike potential to our assets.

01:13:26.180 --> 01:13:29.920
And that's what's shown
with the little red dots

01:13:29.920 --> 01:13:34.920
is those trees that have sufficient elevation

01:13:36.010 --> 01:13:39.820
that if they were to fall

01:13:39.820 --> 01:13:42.130
from whatever their position is today.

01:13:42.130 --> 01:13:44.760
So, they could be on
the side of a hill or not,

01:13:44.760 --> 01:13:48.500
if they would fall into
the line, they are a risk,

01:13:48.500 --> 01:13:52.430
then that provides
information for Brian's team

01:13:52.430 --> 01:13:57.430
to go out and validate
the health of the falling risk.

01:13:59.113 --> 01:14:04.113
Also in that particular
pilot, what we're focused on

01:14:04.370 --> 01:14:08.780
is understanding the change in the vegetation

01:14:08.780 --> 01:14:13.780
from a 2016 kind of benchmark
year to 2020 satellite values

01:14:17.870 --> 01:14:19.520
in order to start to understand

01:14:19.520 --> 01:14:22.280
whether there's some capability in phase two

01:14:22.280 --> 01:14:25.690
to do some growth rate calculations,

01:14:25.690 --> 01:14:28.830
which then helps to feed into

01:14:28.830 --> 01:14:31.483
perspective encroachment modeling.

01:14:32.350 --> 01:14:34.490
And again, putting one more tool

01:14:34.490 --> 01:14:37.063
in the hands of the forester.

01:14:39.860 --> 01:14:44.750
So that is the short term
pilot that we're targeted.

01:14:44.750 --> 01:14:49.750
And it really is, again, trying to augment

01:14:49.960 --> 01:14:53.920
that legacy vegetation management data

01:14:53.920 --> 01:14:58.920
that's been, so far, with the handheld tool,

01:15:00.380 --> 01:15:02.990
enhanced with the data
that we're collecting there.

01:15:02.990 --> 01:15:05.580
And this creates just one more,

01:15:05.580 --> 01:15:09.153
kind of more comprehensive
look at the entire landscape.

01:15:12.520 --> 01:15:14.483
And if there are any questions later,

01:15:15.590 --> 01:15:17.440
Brian and I will take them, obviously

01:15:19.670 --> 01:15:21.020
<v Brian>Thank you, Heide.</v>

01:15:23.273 --> 01:15:24.470
If you'd move to the next slide.

01:15:24.470 --> 01:15:26.845
I would believe that would be,

01:15:26.845 --> 01:15:29.037
this concludes our high-level overview.

01:15:29.037 --> 01:15:29.873
<v ->Yes.</v>
<v ->Thank you very much.</v>

01:15:32.790 --> 01:15:33.623
<v Colin>All right.</v>

01:15:33.623 --> 01:15:35.240
Thank you both so much.

01:15:35.240 --> 01:15:38.033
We will move right along to Liberty.

01:15:42.260 --> 01:15:44.160
<v Peter>Hello. My name is Peter Stoltman.</v>

01:15:44.160 --> 01:15:47.520
I'm the Manager of Vegetation
Management for Liberty.

01:15:47.520 --> 01:15:52.010
And I'll be providing a update
on progress we've made

01:15:52.010 --> 01:15:55.317
since filing our 2020
wildfire mitigation plan.

01:15:55.317 --> 01:15:58.480
On the next slide slide we'll show

01:16:00.488 --> 01:16:04.050
the programs and initiatives
I'm gonna highlight today.

01:16:04.050 --> 01:16:06.430
At Liberty, we've maintained

01:16:06.430 --> 01:16:08.770
growth in our existing initiatives.

01:16:08.770 --> 01:16:12.960
And we've also piloted and
implemented new VM initiatives,

01:16:12.960 --> 01:16:14.970
which I'm gonna discuss today,

01:16:14.970 --> 01:16:17.160
including implementing our first

01:16:17.160 --> 01:16:19.520
Forest Resilience Corridors project,

01:16:19.520 --> 01:16:21.310
establishment of fuel management

01:16:21.310 --> 01:16:23.520
and biomass removal projects,

01:16:23.520 --> 01:16:26.450
and new vegetation inspection initiatives,

01:16:26.450 --> 01:16:29.960
which are ground patrols of our Tier 3

01:16:29.960 --> 01:16:31.590
High Fire Threat District area

01:16:31.590 --> 01:16:35.193
and piloting the use of LiDAR
for vegetation inspections.

01:16:36.190 --> 01:16:37.810
On the next slide I'll discuss

01:16:37.810 --> 01:16:39.753
our Forest Resilience Corridors.

01:16:41.300 --> 01:16:44.260
What these are are
multi-jurisdictional efforts

01:16:44.260 --> 01:16:47.270
focused on tree removal and forest health.

01:16:47.270 --> 01:16:50.070
We work with large public
and private landowners

01:16:50.070 --> 01:16:52.490
to remove hazard trees and
reduce stand density along

01:16:52.490 --> 01:16:54.860
along our utility corridors.

01:16:54.860 --> 01:16:57.440
And for that, we established
three treatment zones

01:16:57.440 --> 01:17:00.400
for the areas surrounding
our utility right-of-ways.

01:17:00.400 --> 01:17:04.350
And Zone 1 is the area
typically about 15 feet

01:17:04.350 --> 01:17:06.486
from each side of the power line,

01:17:06.486 --> 01:17:09.110
commonly referred to as the wire zone.

01:17:09.110 --> 01:17:12.630
And in this area Liberty
will remove all vegetation

01:17:12.630 --> 01:17:15.420
with the potential to
grow into our facilities,

01:17:15.420 --> 01:17:17.500
as well as larger shrubs that would

01:17:17.500 --> 01:17:19.853
add to the fuel load in the wire zone.

01:17:21.090 --> 01:17:25.280
Zone 2 encompasses an area up to 175 feet

01:17:25.280 --> 01:17:27.500
outside that immediate wire zone.

01:17:27.500 --> 01:17:30.260
And we're focusing on removal of hazard trees

01:17:30.260 --> 01:17:33.601
with strike potential and additional thinning

01:17:33.601 --> 01:17:37.790
and fuel reduction efforts
to reduce the stand density.

01:17:37.790 --> 01:17:40.990
And in this area, the
work is typically performed

01:17:40.990 --> 01:17:44.110
as a joint effort between
Liberty and the landowner.

01:17:44.110 --> 01:17:48.650
And in Zone 3 is a broader area extending

01:17:50.204 --> 01:17:55.204
175 feet up to 1,000 feet on either side

01:17:55.320 --> 01:17:57.780
of that right-of-way,
where additional thinning

01:17:57.780 --> 01:18:01.190
and fuel reduction may be
performed by the landowner.

01:18:01.190 --> 01:18:03.820
So typically on these projects,

01:18:03.820 --> 01:18:06.610
we're looking at Liberty being responsible

01:18:06.610 --> 01:18:09.070
primarily for that Zone 1 work,

01:18:09.070 --> 01:18:11.700
sharing the workload in Zone 2,

01:18:11.700 --> 01:18:15.640
and then Zone 3 work being performed

01:18:15.640 --> 01:18:19.040
at the discretion of the landowner.

01:18:19.040 --> 01:18:23.740
So in 2020 Liberty worked
with the U.S. Forest Service,

01:18:23.740 --> 01:18:27.460
Northstar California Resort
and Sierra Pacific Industries

01:18:27.460 --> 01:18:29.720
to implement the first of these projects

01:18:29.720 --> 01:18:33.930
on about 15 miles of the
60 KV transmission line.

01:18:33.930 --> 01:18:36.930
And this line is a
particularly critical piece

01:18:36.930 --> 01:18:39.022
of infrastructure for
Liberty because it serves

01:18:39.022 --> 01:18:43.830
as a backup feed to our
Northern service area.

01:18:43.830 --> 01:18:46.350
So if one of our other
transmission lines were to go

01:18:46.350 --> 01:18:50.350
out of service, this line
would pick up those customers.

01:18:50.350 --> 01:18:54.590
And the picture on the
slide here is one such area

01:18:54.590 --> 01:18:59.003
where we did some zone work on our 625 line.

01:19:01.030 --> 01:19:03.670
One of the biggest
challenges in getting this work

01:19:03.670 --> 01:19:06.890
started and kicked off was permitting.

01:19:06.890 --> 01:19:09.520
It's very complex and challenging due

01:19:09.520 --> 01:19:13.050
to dealing with multiple
landowners and agencies

01:19:13.050 --> 01:19:14.990
and even sometimes different departments

01:19:14.990 --> 01:19:17.202
within a single agency that need to review

01:19:17.202 --> 01:19:20.340
and approve our vegetation management work.

01:19:20.340 --> 01:19:22.040
So we're working really closely,

01:19:22.040 --> 01:19:24.090
specifically with the U.S. Forest Service,

01:19:24.090 --> 01:19:26.418
to streamline the permitting process

01:19:26.418 --> 01:19:29.960
and to hopefully avoid future project delays

01:19:29.960 --> 01:19:34.960
as we continue with our Forest
Resilience Corridor projects.

01:19:35.500 --> 01:19:38.280
Also in 2020, we were fortunate to work

01:19:38.280 --> 01:19:41.120
with the National Forest Foundation,

01:19:41.120 --> 01:19:45.490
and they are a congressionally
chartered nonprofit

01:19:45.490 --> 01:19:47.970
that works specifically on national forests

01:19:47.970 --> 01:19:50.534
and national grasslands to perform

01:19:50.534 --> 01:19:53.782
and carry out land management projects.

01:19:53.782 --> 01:19:57.490
And they had a large
scale fuel reduction project

01:19:57.490 --> 01:19:59.450
occurring on the Tahoe National Forest

01:19:59.450 --> 01:20:03.120
where we have about three
miles of transmission line

01:20:03.120 --> 01:20:08.120
that crossed their timber harvest area.

01:20:08.710 --> 01:20:12.470
So we were able to work with them to inspect

01:20:12.470 --> 01:20:16.640
for additional hazard
trees in the Zone 2 area.

01:20:16.640 --> 01:20:19.890
And then we had our line
clearance qualified contractors

01:20:19.890 --> 01:20:24.890
go in, remove trees that
were adjacent to the lines,

01:20:25.640 --> 01:20:27.880
or just that their timber
operator may not have been

01:20:27.880 --> 01:20:31.350
comfortable with felling due to proximity

01:20:31.350 --> 01:20:33.240
to our our high voltage lines.

01:20:33.240 --> 01:20:34.770
And that was a big success.

01:20:34.770 --> 01:20:37.188
So we're looking at more
opportunities to partner

01:20:37.188 --> 01:20:40.120
with the National Forest Foundation

01:20:40.120 --> 01:20:43.773
on other similar projects
within the Lake Tahoe Basin.

01:20:45.360 --> 01:20:47.780
On the next slide, we'll talk about

01:20:47.780 --> 01:20:51.270
some fuel management
projects we have going on.

01:20:51.270 --> 01:20:56.270
And so Liberty has kind
of four types of projects

01:20:56.660 --> 01:21:01.010
focused on fuel reduction
and biomass removal.

01:21:01.010 --> 01:21:04.700
Our community fuel
reduction projects focus on

01:21:04.700 --> 01:21:07.760
additional vegetation management activities

01:21:07.760 --> 01:21:09.736
after our typical routine

01:21:09.736 --> 01:21:13.940
vegetation management work is done.

01:21:13.940 --> 01:21:18.940
And so what we'll do after
our routine work is done,

01:21:19.400 --> 01:21:23.040
we will go back and remove additional trees

01:21:23.040 --> 01:21:25.810
under and adjacent to the lines

01:21:25.810 --> 01:21:28.950
that could cause future growing issues.

01:21:28.950 --> 01:21:32.430
We'll perform brush clearing
around all the utility poles,

01:21:32.430 --> 01:21:35.660
regardless of whether
they're a subject pole or not.

01:21:35.660 --> 01:21:40.100
And then we remove all the
biomass from that project area.

01:21:40.100 --> 01:21:44.480
In 2020, we completed
three of these types of projects

01:21:44.480 --> 01:21:48.610
and removed over 376 tons of biomass.

01:21:48.610 --> 01:21:53.063
And we're looking to greatly
expand that program in 2021.

01:21:54.700 --> 01:21:56.530
The California Tahoe Conservancy

01:21:56.530 --> 01:21:59.680
is a large landowner in the Lake Tahoe Basin.

01:21:59.680 --> 01:22:02.220
They do have large
properties, but they also have

01:22:02.220 --> 01:22:06.230
several small parcels
scattered throughout the area.

01:22:06.230 --> 01:22:11.230
And with the amount of
increase of work that we're doing

01:22:11.920 --> 01:22:14.240
from our vegetation management activities,

01:22:14.240 --> 01:22:16.290
we're starting to create
an increased workload

01:22:16.290 --> 01:22:19.240
for the Conservancy crews.

01:22:19.240 --> 01:22:21.710
Typically they'd be able to go in

01:22:21.710 --> 01:22:24.350
and handle any wood left after our projects.

01:22:24.350 --> 01:22:28.050
But, since we have been
doing so much more work,

01:22:28.050 --> 01:22:31.410
it started to create too
much workload for them

01:22:31.410 --> 01:22:35.460
and taking away from their
larger land management projects.

01:22:35.460 --> 01:22:38.010
So, we worked with them
to create a scope of work

01:22:38.010 --> 01:22:43.010
for treating wood and debris
left behind from our projects

01:22:43.773 --> 01:22:48.470
and using our own internal
resources to treat that wood.

01:22:48.470 --> 01:22:51.940
So, we started that in
the fourth quarter of 2020

01:22:51.940 --> 01:22:54.970
and were able to treat 33 parcels

01:22:54.970 --> 01:22:56.600
in that short amount of time.

01:22:56.600 --> 01:23:00.370
And again, that is a program
that's proved very successful

01:23:00.370 --> 01:23:04.840
and we're going to continue
with that moving forward.

01:23:04.840 --> 01:23:07.970
We also work with local
fire protection agencies

01:23:07.970 --> 01:23:11.230
to manage wildfire risk
on Liberty owned property.

01:23:11.230 --> 01:23:13.700
And so we completed defensible space projects

01:23:13.700 --> 01:23:15.503
at two of our substations.

01:23:17.120 --> 01:23:19.850
And these projects focus
on removing hazard trees

01:23:19.850 --> 01:23:22.780
with potential to impact our facilities

01:23:22.780 --> 01:23:25.680
and then removing small diameter trees,

01:23:25.680 --> 01:23:27.430
dead and dying brush and branches

01:23:27.430 --> 01:23:31.193
surrounding the substation to
maintain the defensible space.

01:23:32.670 --> 01:23:35.683
And fourthly, wood hauling projects.

01:23:36.840 --> 01:23:40.490
Historically we would remove everything

01:23:40.490 --> 01:23:42.380
up to four inches in diameter

01:23:42.380 --> 01:23:45.360
and everything greater
than four inches in diameter

01:23:45.360 --> 01:23:50.360
was left onsite for
property owners to handle.

01:23:50.981 --> 01:23:54.730
We realized that that's not always feasible.

01:23:54.730 --> 01:23:57.801
And sometimes that property owner

01:23:57.801 --> 01:23:59.970
doesn't necessarily do anything.

01:23:59.970 --> 01:24:04.970
So in order to not contribute
to additional fuel loading,

01:24:05.597 --> 01:24:08.981
we're working on a more extensive approach

01:24:08.981 --> 01:24:11.620
to remove wood from project areas

01:24:11.620 --> 01:24:14.840
that may have otherwise been left onsite

01:24:14.840 --> 01:24:18.913
to benefit the community
and reduce wildfire risk.

01:24:20.580 --> 01:24:22.820
And on the next slide, I'll talk about

01:24:22.820 --> 01:24:26.783
some new inspection initiatives.

01:24:28.154 --> 01:24:32.240
In our 2020 wildfire mitigation plan,

01:24:32.240 --> 01:24:34.780
Liberty established annual inspections

01:24:34.780 --> 01:24:38.320
of our Tier 3 High Fire
Threat District areas,

01:24:38.320 --> 01:24:40.930
which equates to about 50 miles

01:24:40.930 --> 01:24:42.963
of overhead primary conductor.

01:24:43.870 --> 01:24:47.830
And in 2020, we did complete
the ground-based inspection

01:24:47.830 --> 01:24:51.240
and completed all vegetation management work

01:24:51.240 --> 01:24:54.270
that was generated from those inspections.

01:24:54.270 --> 01:24:56.210
However, after the filing

01:24:56.210 --> 01:24:59.750
of our 2020 wildfire mitigation plan

01:24:59.750 --> 01:25:02.402
we received a deficiency due to concerns

01:25:02.402 --> 01:25:04.230
about the effectiveness

01:25:04.230 --> 01:25:07.733
of our reported vegetation
inspection frequencies.

01:25:09.870 --> 01:25:12.780
We were using a cycle based approach,

01:25:12.780 --> 01:25:14.920
with a three year inspection cycle,

01:25:14.920 --> 01:25:17.130
with the exception of
those annual inspections

01:25:17.130 --> 01:25:20.710
of the Tier 3 High Fire
Threat District areas.

01:25:20.710 --> 01:25:23.880
And our service
territory, I should point out,

01:25:23.880 --> 01:25:26.630
is 92% High Fire Threat District.

01:25:26.630 --> 01:25:30.380
So we really treat our
entire service territory

01:25:30.380 --> 01:25:31.780
as High Fire Threat Districts.

01:25:31.780 --> 01:25:36.733
We don't really change scope
of work for that remaining 8%.

01:25:39.145 --> 01:25:44.050
So in last year, Liberty
performed a LiDAR inspection

01:25:44.050 --> 01:25:49.050
of 330 miles, which is almost
half of our service territory.

01:25:49.880 --> 01:25:52.880
And the point of that was
to explore the use of LiDAR

01:25:52.880 --> 01:25:57.348
for increasing our vegetation
inspection frequency.

01:25:57.348 --> 01:26:00.250
And we compared the ground-based inspections

01:26:00.250 --> 01:26:03.398
to the LiDAR inspections to
determine what the method

01:26:03.398 --> 01:26:07.100
would be for moving from
a three year inspection cycle

01:26:07.100 --> 01:26:09.830
to an annual inspection cycle.

01:26:09.830 --> 01:26:11.830
Ultimately, we selected LiDAR

01:26:11.830 --> 01:26:15.200
as the preferred method, for a few reasons.

01:26:15.200 --> 01:26:17.710
One is the speed at which those inspections

01:26:17.710 --> 01:26:19.240
could be performed.

01:26:19.240 --> 01:26:22.640
So, for comparison, that Tier 3 inspection

01:26:22.640 --> 01:26:26.650
that was ground-based, it took us two months

01:26:26.650 --> 01:26:30.210
to inspect those 50 miles.

01:26:30.210 --> 01:26:34.070
The 330 miles that we inspected using LiDAR,

01:26:34.070 --> 01:26:36.820
that data was acquired in two days.

01:26:36.820 --> 01:26:38.980
And then we received our initial deliverables

01:26:38.980 --> 01:26:40.800
of all that data within the first month,

01:26:40.800 --> 01:26:42.980
that we can start taking action

01:26:42.980 --> 01:26:47.470
on the data that we acquired from the vendor.

01:26:47.470 --> 01:26:52.470
Additionally, the LiDAR
has extremely high accuracy.

01:26:54.780 --> 01:26:58.310
And so, technology isn't always perfect,

01:26:58.310 --> 01:27:00.228
but it definitely eliminates

01:27:00.228 --> 01:27:03.890
the factor introduced by human error.

01:27:03.890 --> 01:27:05.380
And so that was another benefit

01:27:05.380 --> 01:27:09.210
that we considered with using LiDAR.

01:27:09.210 --> 01:27:11.530
And then we also have the ability

01:27:11.530 --> 01:27:15.050
to inspect without access issues.

01:27:15.050 --> 01:27:17.040
There's a lot of gates.

01:27:17.040 --> 01:27:21.050
Sometimes our locks get cut
off or other locks get placed on

01:27:21.050 --> 01:27:23.620
and we end up having to chase down access

01:27:23.620 --> 01:27:26.840
to get to the property
where our lines are at times.

01:27:26.840 --> 01:27:30.890
And we also have extremely
rugged terrain in areas.

01:27:30.890 --> 01:27:33.840
And actually in that picture, that is some

01:27:33.840 --> 01:27:37.420
of the point cloud that we
received from the LiDAR data.

01:27:37.420 --> 01:27:40.080
And in the top right corner you could see

01:27:40.080 --> 01:27:43.200
a line of detections going up into the right.

01:27:43.200 --> 01:27:45.090
And essentially that's one of our lines

01:27:45.090 --> 01:27:46.850
that goes up the side of a mountain,

01:27:46.850 --> 01:27:50.070
and that's not uncommon
for our service territory.

01:27:50.070 --> 01:27:53.390
So although it may not be inaccessible,

01:27:53.390 --> 01:27:57.670
it's very challenging
to patrol on the ground.

01:27:57.670 --> 01:28:00.680
And so again, LiDAR eliminates that issue

01:28:00.680 --> 01:28:02.913
that we see from ground-based patrols.

01:28:04.280 --> 01:28:06.900
And lastly, with LiDAR,
we're able to efficiently

01:28:06.900 --> 01:28:11.230
direct resources where
needed to maintain clearances.

01:28:11.230 --> 01:28:13.680
So, once we get those detections back,

01:28:13.680 --> 01:28:18.640
we can know where the worst
conditions on our system are.

01:28:18.640 --> 01:28:21.200
We can prioritize our work based on

01:28:21.200 --> 01:28:23.700
the detections that we receive

01:28:23.700 --> 01:28:27.449
and then be much more
targeted in our approach

01:28:27.449 --> 01:28:31.393
to maintaining clearances
throughout the system.

01:28:32.240 --> 01:28:34.085
So with that being said,

01:28:34.085 --> 01:28:37.779
Liberty is going to expand the use of LiDAR.

01:28:37.779 --> 01:28:41.560
We saw a lot of success
in this pilot program.

01:28:41.560 --> 01:28:44.430
And so we're now going to use LiDAR

01:28:44.430 --> 01:28:48.450
for our system-wide annual
vegetation inspections

01:28:48.450 --> 01:28:52.900
beginning in 2021, so this year.

01:28:52.900 --> 01:28:55.695
So generally speaking, I'd say at Liberty,

01:28:55.695 --> 01:28:58.380
we're really willing to take a close look

01:28:58.380 --> 01:29:01.840
at our historical practices
and explore new opportunities

01:29:01.840 --> 01:29:04.120
to mitigate wildfire
risk in our service area.

01:29:04.120 --> 01:29:08.700
I think this shift from a three year cycle

01:29:08.700 --> 01:29:12.120
to using LiDAR technology
for annual inspections

01:29:12.120 --> 01:29:16.033
is one way that really
demonstrates that point very clearly.

01:29:17.650 --> 01:29:19.563
And thank you for your time.

01:29:23.600 --> 01:29:25.560
<v Colin>And thank you for the presentation</v>

01:29:27.890 --> 01:29:30.393
Last and certainly not least, Bear Valley.

01:29:34.930 --> 01:29:35.763
<v ->Okay.</v>

01:29:37.160 --> 01:29:42.160
So vegetation management is, I would say,

01:29:42.340 --> 01:29:45.273
it's probably the top program today,

01:29:46.703 --> 01:29:50.383
the top mitigation to
preventing wildfire, in my view.

01:29:52.886 --> 01:29:57.058
And therefore it's an
incredibly important program.

01:29:57.058 --> 01:29:58.953
Can we go to the next page.

01:30:02.853 --> 01:30:07.853
Our program consists of
preventative vegetation management.

01:30:08.057 --> 01:30:10.400
And so it's basically a cycle where

01:30:11.700 --> 01:30:15.507
the vegetation management contractor visits,

01:30:18.595 --> 01:30:22.280
on a periodic basis, every facility

01:30:24.210 --> 01:30:28.093
throughout our service area on a cycle basis.

01:30:28.950 --> 01:30:31.940
There's also corrective vegetation clearance

01:30:31.940 --> 01:30:35.870
needs or actions that are identified

01:30:38.192 --> 01:30:41.790
by inspections, the LiDAR surveys,

01:30:42.905 --> 01:30:47.905
or other type of
discrepancies are identified.

01:30:49.530 --> 01:30:52.433
And then there's emergency
vegetation clearance.

01:30:53.473 --> 01:30:55.793
So if you have a big storm event,

01:30:57.360 --> 01:31:01.143
we do have a lot of vegetation to be cleared.

01:31:02.430 --> 01:31:06.203
And after you clear all
that, the obvious ones,

01:31:07.200 --> 01:31:10.950
because sort of everything
shifted due to the storm,

01:31:10.950 --> 01:31:13.750
so you've gotta go through the service area

01:31:13.750 --> 01:31:16.120
and take a hard look to see

01:31:16.120 --> 01:31:20.693
if what you thought was
good is now no longer good.

01:31:22.270 --> 01:31:25.623
So, those are the three
elements of our program.

01:31:27.510 --> 01:31:31.330
We have, like I said, we're at 7,000 feet.

01:31:31.330 --> 01:31:33.100
Our trees are snow laden.

01:31:33.100 --> 01:31:37.040
So over the years those branches become

01:31:37.040 --> 01:31:40.060
more susceptible to breaking and falling.

01:31:40.060 --> 01:31:42.890
Or the trees themselves become susceptible

01:31:42.890 --> 01:31:44.093
to falling and breaking.

01:31:45.290 --> 01:31:48.810
And we have icing conditions and so forth.

01:31:48.810 --> 01:31:53.810
So we go beyond the minimum
clearance standards of G.O. 95

01:31:57.431 --> 01:32:02.431
in order to accommodate
those more severe conditions.

01:32:06.340 --> 01:32:09.420
And then another element,
I sort of talked about it

01:32:09.420 --> 01:32:12.690
in the Q and A, is quality control checks.

01:32:12.690 --> 01:32:16.370
That is a very important
aspect of our program.

01:32:16.370 --> 01:32:21.370
It gets our supervisors,
managers, out in the field

01:32:22.540 --> 01:32:26.293
looking at this very critical program.

01:32:27.175 --> 01:32:32.175
And I think it's really paid dividends.

01:32:33.856 --> 01:32:38.650
It really stresses the importance
of vegetation management.

01:32:40.230 --> 01:32:44.170
And in a world of constrained resources

01:32:44.170 --> 01:32:46.269
there's a lot of things I wouldn't do

01:32:46.269 --> 01:32:51.040
before starting to look at
vegetation management.

01:32:51.040 --> 01:32:54.680
It's just an area you can't cut, pardon that,

01:32:54.680 --> 01:32:58.653
but you just can't dial back
on vegetation management.

01:32:59.863 --> 01:33:04.377
One thing that we are
doing now in our program,

01:33:04.377 --> 01:33:09.377
and we just, we talked
about it in our 2020 plan.

01:33:09.650 --> 01:33:13.980
We finally have a forester
onsite to provide us,

01:33:15.900 --> 01:33:17.810
a contracted forester, to provider us,

01:33:17.810 --> 01:33:21.010
kind of a third party, so
we're not only relying on

01:33:21.010 --> 01:33:25.390
our vegetation management
contractors, arborists,

01:33:25.390 --> 01:33:30.330
but now we have our own
independent expert onsite

01:33:30.330 --> 01:33:35.330
to help advise us on our
program, help us to target areas,

01:33:37.842 --> 01:33:40.813
and come up with special
projects and so forth.

01:33:45.550 --> 01:33:50.550
On the inspection side,
as I mentioned before,

01:33:51.120 --> 01:33:56.120
we do the annual G.O. 165 ground patrols.

01:33:57.312 --> 01:33:59.460
We do a detailed inspection.

01:33:59.460 --> 01:34:01.570
That's done every five years.

01:34:01.570 --> 01:34:05.060
We do a second annual
G.O. 165 on ground patrol

01:34:05.060 --> 01:34:08.293
by a third party, we do the LiDAR.

01:34:10.883 --> 01:34:15.883
We also have implemented the Forester program

01:34:17.620 --> 01:34:21.283
and now we're doing a,

01:34:22.750 --> 01:34:27.750
we'll be doing a UAV fly over
and imaging thermal surveys.

01:34:30.160 --> 01:34:31.523
Go to the next slide.

01:34:34.821 --> 01:34:38.010
LiDAR, we've done this for two years now,

01:34:38.010 --> 01:34:41.030
and it really does help quite a bit.

01:34:41.030 --> 01:34:46.030
It gives you a great
picture of what locations

01:34:46.110 --> 01:34:48.203
you need to go have a look at,

01:34:49.820 --> 01:34:52.093
get the contractor out to those areas.

01:34:53.480 --> 01:34:56.320
It almost gives you good, what I would call

01:34:56.320 --> 01:35:01.083
objective quality evidence
of how clear your lines are,

01:35:02.330 --> 01:35:03.433
which is important.

01:35:05.290 --> 01:35:09.810
And it also kind of gives us a good focus

01:35:09.810 --> 01:35:12.850
of where to go right before fire season

01:35:14.651 --> 01:35:15.901
to make sure we're ready.

01:35:18.260 --> 01:35:21.867
And the UAV, like I said, we issued an RFP,

01:35:22.948 --> 01:35:27.948
and we hope to get a survey
done before the fire season.

01:35:28.234 --> 01:35:31.620
And we think that inspection will complement

01:35:31.620 --> 01:35:36.503
our vegetation management program.

01:35:38.893 --> 01:35:39.726
Go to the...

01:35:41.840 --> 01:35:44.953
Final slide, I think that's just questions.

01:35:44.953 --> 01:35:49.953
But on the removal of biomass and so forth,

01:35:51.720 --> 01:35:56.123
our contractor removes all waste, wood waste.

01:35:57.960 --> 01:35:59.823
It doesn't matter what diameter.

01:36:01.233 --> 01:36:03.963
That's our contractual
requirement with the contractor,

01:36:05.340 --> 01:36:09.920
to remove and dispose
of it in accordance with

01:36:11.750 --> 01:36:14.713
applicable ordinances and laws.

01:36:16.410 --> 01:36:21.270
We are looking at, the community does have

01:36:21.270 --> 01:36:25.540
some fuels management programs,

01:36:25.540 --> 01:36:29.410
primarily run by the Big
Bear Fire Department,

01:36:29.410 --> 01:36:32.833
so we're looking to partner
with them, see how we can help.

01:36:33.890 --> 01:36:35.580
We're also looking to reach out

01:36:35.580 --> 01:36:37.120
with the U.S. Forestry Service

01:36:38.139 --> 01:36:42.173
and see how we can help
in their fuels management.

01:36:43.823 --> 01:36:45.323
That's all I have.

01:36:47.880 --> 01:36:49.710
<v Colin>Great, thanks so much, Paul.</v>

01:36:49.710 --> 01:36:52.603
And thank you to all of our presenters.

01:36:53.610 --> 01:36:58.610
I have us coming back from break at 3:40.

01:37:02.450 --> 01:37:04.530
So we have quite a bit of time,

01:37:04.530 --> 01:37:09.530
but I will see you all
at 3:40 for the Q and A.

01:37:20.321 --> 01:37:22.904
(upbeat music)

01:37:26.410 --> 01:37:28.510
Perhaps go outside and look at some trees.

01:37:30.030 --> 01:37:34.973
I want to make sure that
everyone is still with us.

01:37:39.130 --> 01:37:40.080
But, I...

01:37:41.584 --> 01:37:43.400
Can I just get an acknowledgement

01:37:43.400 --> 01:37:47.513
from PacifiCorp, Liberty, and
Bear Valley that you are here?

01:37:48.549 --> 01:37:50.149
<v Brian>This is Pacific Power.</v>

01:37:52.950 --> 01:37:55.500
<v Peter>Hi, this is Peter with Liberty. I'm here.</v>

01:37:56.600 --> 01:37:58.560
<v Paul>I'm here, Bear Valley.</v>

01:37:58.560 --> 01:38:00.440
<v ->Great. Cool.</v>

01:38:00.440 --> 01:38:01.363
Thank you all.

01:38:03.040 --> 01:38:07.840
So we will start out just like
the other Q and A sessions.

01:38:07.840 --> 01:38:09.797
I'll ask a question for WSD

01:38:09.797 --> 01:38:12.380
and then we'll move on to the stakeholders

01:38:12.380 --> 01:38:15.113
and go in sort of a round robin that way.

01:38:16.066 --> 01:38:21.066
So, as my first question...

01:38:23.290 --> 01:38:28.240
My first question is in
regards to contractors.

01:38:28.240 --> 01:38:32.470
All of you, either to a
large degree or exclusively,

01:38:32.470 --> 01:38:35.740
rely on contractors to do your
vegetation management work,

01:38:35.740 --> 01:38:37.330
if I'm not mistaken.

01:38:37.330 --> 01:38:40.840
And so I just wanted
to hear from each utility

01:38:40.840 --> 01:38:45.351
about the best practices for
oversight of these contractors,

01:38:45.351 --> 01:38:49.963
particularly when issues
arise, how they are remedied.

01:38:50.890 --> 01:38:54.610
And I'd also like a short discussion

01:38:54.610 --> 01:38:59.610
about how you ensure
contractors are effective bases

01:39:02.226 --> 01:39:06.060
for the utilities out in public,

01:39:06.060 --> 01:39:07.780
particularly when communicating

01:39:07.780 --> 01:39:11.200
with land owners and customers.

01:39:11.200 --> 01:39:12.753
As we all know, vegetation is

01:39:12.753 --> 01:39:16.933
a very visible part of wildfire mitigation.

01:39:19.883 --> 01:39:22.733
So we can start with, why
don't we start with PacifiCorp?

01:39:23.855 --> 01:39:24.688
<v Brian>Yes.</v>

01:39:24.688 --> 01:39:26.643
So I guess one of the best ways

01:39:26.643 --> 01:39:29.830
that we oversee our contractors

01:39:29.830 --> 01:39:33.660
is through our internal staff.

01:39:33.660 --> 01:39:36.720
So in 2020, over the past couple of years,

01:39:36.720 --> 01:39:41.720
2019 into 2020, we hired
four additional utility foresters.

01:39:42.266 --> 01:39:45.810
and those foresters have
the primary responsibility

01:39:45.810 --> 01:39:47.820
of conducting post-audits.

01:39:47.820 --> 01:39:50.130
So one of the most effective ways

01:39:50.130 --> 01:39:52.190
that I mentioned to oversee our contractors

01:39:52.190 --> 01:39:53.480
is through our internal staff

01:39:53.480 --> 01:39:56.050
and having their presence out in the field

01:39:56.050 --> 01:39:59.437
reviewing the work
conducted by our contractors.

01:39:59.437 --> 01:40:03.550
So they're out as closely
behind the contractors

01:40:03.550 --> 01:40:07.920
as feasible and efficient
to conduct post-audits

01:40:07.920 --> 01:40:12.920
of the contractors' work,
identify issues that may arise

01:40:12.930 --> 01:40:17.380
with respect to the contractors'
quality of work, et cetera,

01:40:17.380 --> 01:40:22.110
efficiencies, things of that nature.

01:40:22.110 --> 01:40:25.290
And then coordinate those findings

01:40:25.290 --> 01:40:28.356
with the contractors general foreperson,

01:40:28.356 --> 01:40:32.659
to address any issues or build upon what is

01:40:32.659 --> 01:40:35.640
working appropriately and
working well in those areas.

01:40:35.640 --> 01:40:39.960
So post-audit work and being out in the field

01:40:39.960 --> 01:40:42.270
and reviewing the work has been

01:40:42.270 --> 01:40:47.270
one of the more efficient
ways to oversee our contractors.

01:40:48.080 --> 01:40:51.140
It does take a lot of
resources to do that work,

01:40:51.140 --> 01:40:54.530
obviously, to be out in
the field that much as well.

01:40:54.530 --> 01:40:59.360
And as far as the customer
communications and so forth,

01:40:59.360 --> 01:41:02.739
it goes hand in hand with
what I mentioned previously,

01:41:02.739 --> 01:41:05.140
as far as our our foresters
being out in the field,

01:41:05.140 --> 01:41:08.220
communicating, having that
one-on-one conversations,

01:41:08.220 --> 01:41:10.830
with our contractors, with
the general forepersons,

01:41:10.830 --> 01:41:14.750
on how to handle and
manage customer interactions,

01:41:14.750 --> 01:41:17.330
concerned customers.

01:41:17.330 --> 01:41:22.250
And so it does take a bit of that one-on-one

01:41:22.250 --> 01:41:26.108
constant communication
and a little bit of training

01:41:26.108 --> 01:41:30.660
with respect to our contractors
on the proper approaches,

01:41:31.700 --> 01:41:35.360
proper procedures of coordinating

01:41:35.360 --> 01:41:38.030
with our customers appropriately.

01:41:38.030 --> 01:41:41.310
And we have a process in place where

01:41:41.310 --> 01:41:45.790
if the contractor cannot
resolve a customer concern

01:41:45.790 --> 01:41:50.188
it's elevated to our foresters
and they interject themselves

01:41:50.188 --> 01:41:55.188
to work to resolve a customer
concern in that manner.

01:41:59.110 --> 01:42:01.120
<v Colin>Can you also speak to</v>

01:42:01.120 --> 01:42:04.023
how issues with contractors are remedied?

01:42:07.040 --> 01:42:08.870
<v Brian>Issues with contractors are remedied?</v>

01:42:08.870 --> 01:42:12.350
So it's, at first, identifying that issue

01:42:12.350 --> 01:42:14.720
in a timely manner, as quickly as possible,

01:42:14.720 --> 01:42:16.590
bringing that light to the contractor

01:42:16.590 --> 01:42:19.917
and having that open
transparent conversation.

01:42:19.917 --> 01:42:22.700
I like to view ourselves as a partnership

01:42:22.700 --> 01:42:25.750
with our contractors in
building that partnership.

01:42:25.750 --> 01:42:28.556
And where we have that strong
partnership, in many cases,

01:42:28.556 --> 01:42:33.556
they'll offer remedies as well to any issues.

01:42:33.890 --> 01:42:38.890
We have had leadership issues or concerns

01:42:40.820 --> 01:42:42.710
with respect to our contractors.

01:42:42.710 --> 01:42:46.907
And they have taken our concerns very heavily

01:42:49.600 --> 01:42:52.450
and made leadership changes on their own.

01:42:52.450 --> 01:42:57.059
So by having that partnership
with the contractors,

01:42:57.059 --> 01:42:59.540
I've found that they are becoming

01:42:59.540 --> 01:43:04.540
more amenable and responsive to our concerns

01:43:06.020 --> 01:43:08.133
and to concerns that we raise with them.

01:43:12.480 --> 01:43:14.880
<v Colin>Right. Thank you so much.</v>

01:43:14.880 --> 01:43:15.713
Liberty.

01:43:17.690 --> 01:43:18.523
<v Peter>Yeah.</v>

01:43:18.523 --> 01:43:23.440
Our process is quite similar
to what PacifiCorp lined out.

01:43:24.900 --> 01:43:29.620
We have a group of contract foresters

01:43:29.620 --> 01:43:31.660
who go out and do patrolling

01:43:31.660 --> 01:43:35.110
and pre-inspection of our
lines to generate work orders.

01:43:35.110 --> 01:43:37.410
And then we have a separate contractor

01:43:37.410 --> 01:43:40.150
that actually performs that tree work.

01:43:40.150 --> 01:43:44.620
And our internal arborists audit

01:43:44.620 --> 01:43:47.260
a lot of that work after it's inspected

01:43:47.260 --> 01:43:49.990
and before it's completed by the tree crews.

01:43:49.990 --> 01:43:53.450
And then they'll also do
follow-up post-work audit

01:43:53.450 --> 01:43:55.850
on the work that's performed
by the tree contractors

01:43:55.850 --> 01:43:58.660
to, again, make sure that
everything's being done

01:43:58.660 --> 01:44:02.613
according to our work
scope and specifications.

01:44:04.000 --> 01:44:05.640
So there's a little bit
of checks and balances

01:44:05.640 --> 01:44:06.923
we have in place there.

01:44:07.810 --> 01:44:11.310
And we're also developing
third-party specifications

01:44:13.670 --> 01:44:15.710
for auditing to supplement that work

01:44:16.833 --> 01:44:20.600
and have additional resources to do

01:44:20.600 --> 01:44:23.760
more post-work and post-inspection auditing

01:44:23.760 --> 01:44:26.530
of our vegetation management program.

01:44:26.530 --> 01:44:29.730
And when it comes to
communication with customers,

01:44:29.730 --> 01:44:33.264
typically throughout the permitting process,

01:44:33.264 --> 01:44:36.770
the contract foresters who
are doing the pre-inspection

01:44:36.770 --> 01:44:39.830
have a lot of interaction with customers.

01:44:39.830 --> 01:44:42.660
We're in very frequent
communication with them

01:44:42.660 --> 01:44:44.760
if there are issues that come up.

01:44:44.760 --> 01:44:48.520
And then when the tree crews
are out there performing work,

01:44:48.520 --> 01:44:50.030
if there are any customer issues,

01:44:50.030 --> 01:44:52.200
we have kind of a chain of command,

01:44:52.200 --> 01:44:55.660
where the tree crews will work

01:44:55.660 --> 01:44:57.410
with the customers to resolve an issue.

01:44:57.410 --> 01:44:59.410
If that doesn't work, they may reach out

01:44:59.410 --> 01:45:01.940
to the pre-inspector who
permissioned the work.

01:45:01.940 --> 01:45:04.810
Maybe there's some
clarification that needs to be done.

01:45:04.810 --> 01:45:08.900
and then it'll get escalated
to our internal arborists,

01:45:08.900 --> 01:45:13.080
or myself if needed, to resolve any issues.

01:45:13.080 --> 01:45:16.810
And in addition to that,
we host monthly meetings

01:45:16.810 --> 01:45:18.830
with all of our contractors.

01:45:18.830 --> 01:45:20.600
So every month we'll meet with them,

01:45:20.600 --> 01:45:23.471
discuss what's currently going on,

01:45:23.471 --> 01:45:26.000
if there are any issues
that need to be addressed

01:45:26.000 --> 01:45:29.170
and kind of just really maintaining

01:45:29.170 --> 01:45:30.770
that open line of communication

01:45:30.770 --> 01:45:33.300
between Liberty and its contractors

01:45:33.300 --> 01:45:35.630
to make sure we're all on the same page.

01:45:35.630 --> 01:45:40.187
But, yeah, we have a pretty
good working relationship

01:45:40.187 --> 01:45:43.626
with our contract resources.

01:45:43.626 --> 01:45:47.300
And honestly, if there is a contractor

01:45:47.300 --> 01:45:52.041
that's not meeting the needs,
most customers aren't shy

01:45:52.041 --> 01:45:55.780
about reaching out to us
directly to express a concern.

01:45:55.780 --> 01:45:59.170
And then that is also another
way that identifies issues,

01:45:59.170 --> 01:46:01.220
if we need to address them at that point.

01:46:05.220 --> 01:46:07.496
<v Colin>Great. Thanks for that answer.</v>

01:46:07.496 --> 01:46:09.273
Bear Valley, Paul.

01:46:13.830 --> 01:46:15.055
<v ->Yeah.</v>

01:46:15.055 --> 01:46:18.000
Similar, we provide contractor oversight

01:46:18.000 --> 01:46:20.373
through a number of methods.

01:46:21.230 --> 01:46:23.940
One is our vegetation management QC,

01:46:23.940 --> 01:46:27.500
which we talked about, where
managers and supervisors

01:46:27.500 --> 01:46:29.950
go out in the field to do
at least six per month.

01:46:31.354 --> 01:46:36.354
Second area is, we do require our contractor

01:46:36.880 --> 01:46:39.610
provide us before and after pictures

01:46:39.610 --> 01:46:43.443
of their trimming activities so
that we have good evidence.

01:46:45.220 --> 01:46:50.220
And then, we also have a forester now

01:46:51.560 --> 01:46:56.560
who will report to us
and will be out in the field

01:46:56.687 --> 01:46:58.773
evaluating the contractors.

01:47:06.617 --> 01:47:10.110
<v Colin>Paul, can you briefly speak to how issues</v>

01:47:10.110 --> 01:47:12.093
with the contractor are remedied?

01:47:14.850 --> 01:47:15.683
<v ->Yeah.</v>

01:47:15.683 --> 01:47:20.230
So we have a weekly requirement

01:47:20.230 --> 01:47:22.460
for a weekly meeting with the contractor.

01:47:22.460 --> 01:47:25.500
So, the contractor to talk to us about

01:47:26.560 --> 01:47:29.510
where they're gonna be so
that we can alert the community

01:47:29.510 --> 01:47:32.240
via our website and social media,

01:47:32.240 --> 01:47:34.840
where tree trimming's gonna take place.

01:47:34.840 --> 01:47:37.767
Also, so we have situational awareness

01:47:37.767 --> 01:47:39.690
of where they're trimming trees

01:47:39.690 --> 01:47:42.303
in case something happens
to a circuit in that area.

01:47:43.610 --> 01:47:47.600
We also coordinate any clearances

01:47:47.600 --> 01:47:52.460
or covering of wire
required for their services.

01:47:52.460 --> 01:47:56.403
And then we also coordinate
any customer issues.

01:47:57.630 --> 01:48:02.372
So there is a regular
scheduled coordination meeting.

01:48:02.372 --> 01:48:07.372
If there is a discrepancy that we find

01:48:07.500 --> 01:48:10.870
we issue a vegetation order

01:48:10.870 --> 01:48:15.120
and we monitor the number of
vegetation orders being issued.

01:48:15.120 --> 01:48:18.017
And we'll talk to the
contractor if we're finding

01:48:18.017 --> 01:48:23.017
that the number of vegetation
orders are increasing.

01:48:24.830 --> 01:48:29.087
That could be indicative of
them not doing a proper job.

01:48:31.099 --> 01:48:36.099
There's also a daily
contact with the contractor

01:48:37.690 --> 01:48:40.390
just to make sure we are keenly aware

01:48:40.390 --> 01:48:42.440
of where they are in the service area.

01:48:42.440 --> 01:48:46.470
So then if any customer issues come up,

01:48:46.470 --> 01:48:48.490
we prefer to resolve them ourselves

01:48:48.490 --> 01:48:52.273
rather than having the
contractor speak for us.

01:48:54.690 --> 01:48:58.710
The contractors do
obviously identify themselves

01:48:58.710 --> 01:49:01.523
as working for Bear Valley Electric Service,

01:49:01.523 --> 01:49:04.940
but we do most of the interactions ourselves

01:49:04.940 --> 01:49:05.963
for the customers.

01:49:12.763 --> 01:49:15.585
<v Colin>That's great. Thank you for that.</v>

01:49:15.585 --> 01:49:19.760
Okay, we will move on to the stakeholders.

01:49:19.760 --> 01:49:21.560
And for the sake of switching it up,

01:49:22.510 --> 01:49:24.510
Henry, I see that your hand is raised.

01:49:24.510 --> 01:49:25.953
Henry with Cal Advocates.

01:49:29.250 --> 01:49:30.770
<v ->Hi, thank you.</v>

01:49:30.770 --> 01:49:34.660
Okay, so I'll start with a
straightforward question.

01:49:34.660 --> 01:49:38.870
What is your approach
to vegetation clearances?

01:49:38.870 --> 01:49:42.860
Obviously there's a minimum in General Orders

01:49:42.860 --> 01:49:47.440
of four feet at the time of trim

01:49:47.440 --> 01:49:49.530
plus enough growth to keep it at,

01:49:49.530 --> 01:49:53.860
enough room to keep it at
four feet until the next trim.

01:49:53.860 --> 01:49:57.060
But I know some utilities
are trimming to 12 feet.

01:49:57.060 --> 01:50:02.060
Some are trimming up
to the sky above the wires.

01:50:02.410 --> 01:50:06.550
So, can you explain, each of you,

01:50:06.550 --> 01:50:08.603
what your clearance distances are?

01:50:15.270 --> 01:50:17.962
<v ->Yes, this is--</v>
<v ->Start with PacifiCorp.</v>

01:50:17.962 --> 01:50:19.386
<v Brian>Sorry. Yes.</v>

01:50:19.386 --> 01:50:21.900
So in general, yes, we, Pacific Power,

01:50:21.900 --> 01:50:24.980
we trim our trees to maintain that

01:50:24.980 --> 01:50:26.940
four minimum clearance distance

01:50:26.940 --> 01:50:30.240
and additional needed clearance

01:50:30.240 --> 01:50:35.240
so that the tree will hold that
clearance through the cycle.

01:50:35.860 --> 01:50:40.025
So we conduct our work on a four year cycle

01:50:40.025 --> 01:50:44.830
and halfway through that
cycle we conduct an interim work

01:50:44.830 --> 01:50:47.680
to address any of those fast growing species

01:50:47.680 --> 01:50:50.940
that may not hold through
an entire four year cycle,

01:50:50.940 --> 01:50:52.590
such as a cycle buster.

01:50:52.590 --> 01:50:57.590
So we're ensuring we,
post-work, post-pruning work,

01:50:58.500 --> 01:51:02.213
our post-prune clearances are well beyond

01:51:03.880 --> 01:51:08.880
the four feet range, out to
12 feet for side clearance,

01:51:11.950 --> 01:51:15.330
13 feet under clearance,
and 10 feet overhang,

01:51:15.330 --> 01:51:18.070
or for distribution on a fast growth species.

01:51:18.070 --> 01:51:22.290
So we categorize our trees from a slow,

01:51:22.290 --> 01:51:24.560
moderate, and fast growing species,

01:51:24.560 --> 01:51:28.300
and then prune to achieve
certain clearance distances

01:51:28.300 --> 01:51:30.810
based off of a tree species' growth rate

01:51:30.810 --> 01:51:33.563
in order to maintain
that four foot clearance.

01:51:39.556 --> 01:51:40.389
<v Peter>Yeah.</v>

01:51:40.389 --> 01:51:45.320
At Liberty, we achieve
12 feet minimum clearance

01:51:46.950 --> 01:51:49.703
at time of work throughout our system.

01:51:50.630 --> 01:51:55.630
And then on transmission we
do work to remove all overhangs.

01:51:56.800 --> 01:52:01.437
So we have kind of ground to
sky clearances on transmission.

01:52:01.437 --> 01:52:04.660
We do allow overhang on distribution.

01:52:04.660 --> 01:52:06.590
But generally speaking, we're getting

01:52:06.590 --> 01:52:09.200
a minimum of 12 feet
of clearance at all times

01:52:09.200 --> 01:52:11.073
whenever we're performing work.

01:52:22.850 --> 01:52:24.360
<v Brian>This is Brian with Pacific Power.</v>

01:52:24.360 --> 01:52:26.980
If I may interject, just to clarify,

01:52:26.980 --> 01:52:31.610
I gave the post-work
clearances that I had mentioned

01:52:31.610 --> 01:52:34.670
are for our interim work that we conduct.

01:52:34.670 --> 01:52:37.980
So similar to what was
just said, we do post-work,

01:52:37.980 --> 01:52:42.070
achieve a 12 foot clearance
on a minimum for our cycle work.

01:52:42.070 --> 01:52:43.840
Just to clarify. Thanks

01:52:50.994 --> 01:52:55.744
<v ->So, at Bear Valley, we
maintain, for the high voltages,</v>

01:52:56.680 --> 01:52:59.333
the voltages that we operate at,

01:53:00.380 --> 01:53:05.220
we strive to achieve a 72
inch radio clearance zone.

01:53:05.220 --> 01:53:08.420
And when we make a
decision to trim, in other words,

01:53:08.420 --> 01:53:13.340
if we think the limb is within the 72 inches

01:53:13.340 --> 01:53:17.460
or is going to be within 72
inches before the next visit,

01:53:17.460 --> 01:53:20.980
we would trim it out to at
least 12 feet, maybe further,

01:53:20.980 --> 01:53:23.933
depending on whether it's a
fast growing species or not.

01:53:29.370 --> 01:53:30.483
<v ->Great.</v>

01:53:30.483 --> 01:53:33.822
And if I could follow
up, PacifiCorp mentioned

01:53:33.822 --> 01:53:36.973
rating trees by rate of growth.

01:53:37.890 --> 01:53:40.880
What's your basis for categorizing trees?

01:53:40.880 --> 01:53:43.533
Who develops that schema?

01:53:43.533 --> 01:53:48.533
How do you categorize trees
into buckets by rate of growth?

01:53:51.540 --> 01:53:55.610
<v Brian>So that's the pre-inspector,</v>

01:53:55.610 --> 01:53:58.430
the person who is
identifying the work to be done

01:53:58.430 --> 01:54:01.080
based off of their professional
judgment and experience,

01:54:01.080 --> 01:54:06.080
will identify, bucketize
those growth rates by trees.

01:54:07.290 --> 01:54:10.920
And so, yeah, to identify
whether it's a slow,

01:54:10.920 --> 01:54:12.570
moderate, or fast growth species.

01:54:15.540 --> 01:54:16.553
<v ->I see. Okay.</v>

01:54:23.640 --> 01:54:26.253
<v Colin>All right. Thank you
for your question, Henry.</v>

01:54:27.383 --> 01:54:30.743
I think now we'll move onto GPI.

01:54:34.520 --> 01:54:35.353
<v Zoe>Thanks.</v>

01:54:35.353 --> 01:54:38.040
So PacifiCorp mentioned using

01:54:38.040 --> 01:54:39.690
herbicides and growth inhibitors.

01:54:39.690 --> 01:54:43.590
Are any of the other SMJUs
using these treatments?

01:54:43.590 --> 01:54:47.810
And then two other parts of that question,

01:54:47.810 --> 01:54:49.900
is how often do they have to be applied?

01:54:49.900 --> 01:54:51.870
And then is there any other consideration

01:54:51.870 --> 01:54:55.833
for long-term solutions, such as replacing

01:54:57.030 --> 01:55:00.403
with low growth or native species?

01:55:07.895 --> 01:55:09.230
<v Peter>This is Peter with Liberty.</v>

01:55:09.230 --> 01:55:11.690
I'll start on that one.

01:55:11.690 --> 01:55:14.830
So we don't use herbicide currently

01:55:14.830 --> 01:55:17.770
for our vegetation management program.

01:55:17.770 --> 01:55:21.330
And we haven't used tree
growth regulators in the past.

01:55:21.330 --> 01:55:26.290
However, we have reached
out to some contractors

01:55:26.290 --> 01:55:28.150
that perform that services and have been

01:55:28.150 --> 01:55:30.230
in discussion with using that.

01:55:30.230 --> 01:55:34.880
We do have a couple outlying
portions of our service areas

01:55:34.880 --> 01:55:38.771
where we do see faster growing species

01:55:38.771 --> 01:55:43.660
that require more frequent maintenance.

01:55:43.660 --> 01:55:45.810
And so, we are considering that use

01:55:45.810 --> 01:55:49.170
of tree growth regulators in those instances.

01:55:49.170 --> 01:55:52.653
We haven't implemented
any of that type of work yet.

01:55:56.850 --> 01:56:00.030
Oh, and as the other one, as far as planting

01:56:00.030 --> 01:56:02.470
or following up with low growing shrubs

01:56:02.470 --> 01:56:05.230
and things like that, that's something where

01:56:06.750 --> 01:56:08.893
we're not currently doing.

01:56:10.310 --> 01:56:13.010
It's something that we'd consider long-term,

01:56:13.010 --> 01:56:17.930
especially on some of our larger projects

01:56:17.930 --> 01:56:19.590
where we're really just trying to promote

01:56:19.590 --> 01:56:22.320
the lower growing species
that would occur naturally,

01:56:22.320 --> 01:56:26.790
and managing to remove
those incompatible species,

01:56:26.790 --> 01:56:31.543
while promoting the naturally
occurring compatible species.

01:56:36.300 --> 01:56:37.133
<v Zoe>Thanks.</v>

01:56:37.133 --> 01:56:39.233
Maybe a quick follow-up
question for Liberty there.

01:56:40.690 --> 01:56:42.840
Is the decision to move to herbicides,

01:56:42.840 --> 01:56:45.190
is that partly a cost-based decision?

01:56:45.190 --> 01:56:49.300
So having to inspect
less and do less trimming?

01:56:49.300 --> 01:56:53.923
Or is it a wildfire
mitigation aspect as well?

01:56:55.840 --> 01:56:58.970
<v Peter>Honestly, it really has to do</v>

01:56:58.970 --> 01:57:00.770
with the permissioning.

01:57:00.770 --> 01:57:04.450
And in the Lake Tahoe Basin, there's a lot

01:57:04.450 --> 01:57:07.670
of additional regulations and restrictions

01:57:07.670 --> 01:57:11.997
on what we can do to prevent any pollution

01:57:11.997 --> 01:57:16.997
or discharge from activities that may create

01:57:17.010 --> 01:57:18.710
ground disturbance going into the lake.

01:57:18.710 --> 01:57:22.820
So the Tahoe Regional Planning Agency

01:57:22.820 --> 01:57:25.750
has additional rules for permitting.

01:57:25.750 --> 01:57:27.950
And so it's just something
that we haven't really

01:57:27.950 --> 01:57:30.973
pursued due to that reason.

01:57:34.370 --> 01:57:35.620
<v Zoe>Great. Thank you.</v>

01:57:38.690 --> 01:57:40.813
<v Brian>And this is Pacific Power.</v>

01:57:40.813 --> 01:57:42.180
So, we are, as you mentioned,

01:57:42.180 --> 01:57:45.160
utilizing tree growth regulator herbicides.

01:57:45.160 --> 01:57:48.500
We utilize that where we
have permission to do so.

01:57:48.500 --> 01:57:50.900
So it can be hit and miss in areas.

01:57:50.900 --> 01:57:55.010
There could be some prime
areas of prime candidacy,

01:57:55.010 --> 01:57:58.280
to utilize herbicides or
tree growth regulators,

01:57:58.280 --> 01:58:00.600
but we don't have permission
to do so, so we don't,

01:58:00.600 --> 01:58:04.503
due to environmental
concerns or landowner concerns,

01:58:04.503 --> 01:58:06.973
With respect to tree growth regulators,

01:58:08.171 --> 01:58:13.171
it's new in our veg management tool box,

01:58:14.640 --> 01:58:19.640
and we've been utilizing it
for a couple of years now.

01:58:19.760 --> 01:58:24.010
And as far as the reapplication,

01:58:24.010 --> 01:58:27.377
it is dependent upon species and so forth

01:58:27.377 --> 01:58:29.860
and the efficacy of the product.

01:58:29.860 --> 01:58:34.860
But it can be reapplied generally during

01:58:34.860 --> 01:58:38.410
either the cycle and or interim maintenance.

01:58:38.410 --> 01:58:40.240
So either once every four years

01:58:40.240 --> 01:58:43.993
or every two years there
may be an application.

01:58:45.500 --> 01:58:47.610
But again, tree growth regulator is

01:58:47.610 --> 01:58:49.450
something new that we are utilizing

01:58:49.450 --> 01:58:51.790
and we have to look into a little bit more

01:58:51.790 --> 01:58:55.540
as far as what our overall
plan and approach would be

01:58:55.540 --> 01:59:00.540
for reapplication on what
frequency, based on the tree.

01:59:00.660 --> 01:59:03.880
As far as promoting the low growing species,

01:59:03.880 --> 01:59:08.810
similar to what was said,
we're not actively planting,

01:59:08.810 --> 01:59:11.620
proactively doing
plantings, but we're utilizing

01:59:11.620 --> 01:59:13.610
herbicides and tree growth regulators

01:59:13.610 --> 01:59:17.246
to try to target those incompatible species.

01:59:17.246 --> 01:59:20.610
And then through integrated
vegetation management

01:59:20.610 --> 01:59:23.490
to promote those lower growing species

01:59:23.490 --> 01:59:24.743
within our rights-of-way.

01:59:34.580 --> 01:59:35.681
<v Zoe>Thanks.</v>

01:59:35.681 --> 01:59:38.843
And then Bear Valley, are
you using similar techniques?

01:59:40.580 --> 01:59:41.750
<v ->Oh, no.</v>

01:59:41.750 --> 01:59:46.750
We're not using any vegetation
inhibitors or regulators.

01:59:50.310 --> 01:59:54.090
We have similar issues
with it that Liberty raised

01:59:55.072 --> 01:59:59.370
as far as with what the
requirements would be.

01:59:59.370 --> 02:00:04.123
And it's not necessarily that
practical to our service area.

02:00:06.540 --> 02:00:11.540
And as far as replacement,
we haven't engaged in that.

02:00:12.300 --> 02:00:14.223
We did do some tree removal.

02:00:16.360 --> 02:00:21.360
But we really don't encounter
a lot of people introducing

02:00:21.769 --> 02:00:25.981
species that aren't indigenous to the area.

02:00:25.981 --> 02:00:29.463
That isn't a big issue for us.

02:00:38.090 --> 02:00:39.690
<v Zoe>Great. Thanks, everyone.</v>

02:00:43.640 --> 02:00:45.080
<v Colin>As a followup to that,</v>

02:00:45.080 --> 02:00:47.680
I apologize, I'm gonna
break the cycle a little bit.

02:00:50.594 --> 02:00:54.860
PacifiCorp mentioned
targeting specific species

02:00:54.860 --> 02:00:58.560
based on growth rates, and I was wondering,

02:00:58.560 --> 02:01:00.600
and Liberty mentioned that as well,

02:01:00.600 --> 02:01:05.590
and I was wondering if this
targeting of specific species

02:01:05.590 --> 02:01:09.120
kind of went beyond anything qualitative

02:01:09.120 --> 02:01:11.830
that the foresters are
doing based on experience,

02:01:11.830 --> 02:01:14.838
that is, is there data to support,

02:01:14.838 --> 02:01:19.156
slow, medium, fast growing species?

02:01:19.156 --> 02:01:23.940
And in addition to that,
are there any other factors

02:01:25.310 --> 02:01:30.310
that the utility uses to
target specific species,

02:01:31.270 --> 02:01:35.049
like for instance, limb failure rates

02:01:35.049 --> 02:01:40.049
or likelihood to fall in storms, et cetera?

02:01:45.660 --> 02:01:47.326
<v Brian>So, this is Pacific Power.</v>

02:01:47.326 --> 02:01:52.326
As far as we do, currently, we are relying on

02:01:52.950 --> 02:01:57.950
that qualitative information
based on experience

02:02:00.627 --> 02:02:04.330
and knowledge of our
pre-inspectors, our foresters,

02:02:04.330 --> 02:02:08.530
and so forth, to help target those areas

02:02:08.530 --> 02:02:10.450
where there are faster growth species

02:02:10.450 --> 02:02:14.370
or species that may be more susceptible

02:02:14.370 --> 02:02:16.360
to failure, as you mentioned.

02:02:16.360 --> 02:02:20.166
There is qualitative data out there.

02:02:20.166 --> 02:02:23.440
Currently, we are, Pacific Power

02:02:23.440 --> 02:02:25.970
is more currently in
the state of relying upon

02:02:25.970 --> 02:02:28.000
more of that qualitative information.

02:02:28.000 --> 02:02:29.163
As I mentioned earlier,

02:02:30.350 --> 02:02:34.320
we are modifying the data that we collect,

02:02:34.320 --> 02:02:37.095
when we're out in the
field conducting our work,

02:02:37.095 --> 02:02:42.058
through the tools we have
now in place since last year,

02:02:42.058 --> 02:02:46.320
such as collecting information
on those cycle busters,

02:02:46.320 --> 02:02:49.581
those faster growing species, to allow us

02:02:49.581 --> 02:02:53.884
to analyze that information at a later date

02:02:53.884 --> 02:02:57.083
to help inform our decision making process.

02:03:04.200 --> 02:03:06.986
<v Peter>So yeah, at Liberty, our pre-inspectors,</v>

02:03:06.986 --> 02:03:10.370
they're looking at previous years' growth

02:03:10.370 --> 02:03:12.960
to help determine future growth rate

02:03:12.960 --> 02:03:15.804
of individual trees as
they're inspecting them.

02:03:15.804 --> 02:03:20.804
And there is a lot of data
out there that has been done

02:03:24.370 --> 02:03:27.510
to quantify growth rates by species.

02:03:27.510 --> 02:03:29.830
And so that's another thing that we use.

02:03:29.830 --> 02:03:34.230
And sometimes when treating
different species on our system,

02:03:34.230 --> 02:03:39.230
we may target more clearance
or work with the customer

02:03:40.440 --> 02:03:42.670
to try and remove those species

02:03:42.670 --> 02:03:45.360
that we know are gonna be fast growers.

02:03:45.360 --> 02:03:49.930
But overall, our species
composition is pretty predictable.

02:03:49.930 --> 02:03:53.884
We don't have a lot of
that, other than the outliers.

02:03:53.884 --> 02:03:58.740
So we have a pretty good
handle, based on experience

02:03:58.740 --> 02:04:03.230
and industry research that's
been done to help guide us

02:04:03.230 --> 02:04:06.830
when determining growth
rates of individual species.

02:04:06.830 --> 02:04:10.810
But with switching to
these LiDAR inspections,

02:04:10.810 --> 02:04:15.514
that's one thing that we
will be able to quantify more

02:04:15.514 --> 02:04:19.120
by using change detection year over year,

02:04:19.120 --> 02:04:22.810
to show us exactly where
species are growing faster

02:04:22.810 --> 02:04:27.810
or at different rates and
need increased mitigation

02:04:28.610 --> 02:04:32.086
or more frequent pruning at that time.

02:04:32.086 --> 02:04:35.327
So, I think it's a combination of looking at

02:04:37.020 --> 02:04:39.690
each individual tree's previous growth rate

02:04:39.690 --> 02:04:42.105
to determine future growth rate using

02:04:42.105 --> 02:04:47.105
industry available research
on growth rate by species.

02:04:47.230 --> 02:04:49.500
And then integrating that future data

02:04:49.500 --> 02:04:52.410
that we're gonna be getting
from the LiDAR surveys

02:04:52.410 --> 02:04:55.950
to do change detection
to see if there are outliers

02:04:55.950 --> 02:04:58.410
or those cycle buster trees that maybe

02:04:58.410 --> 02:05:00.893
we're not currently targeting.

02:05:09.750 --> 02:05:11.220
<v Colin>Great, thank you.</v>

02:05:11.220 --> 02:05:13.370
Does Bear Valley target trees

02:05:13.370 --> 02:05:16.653
based on growth rates or other factors?

02:05:18.090 --> 02:05:20.720
<v ->Well, we track the species.</v>

02:05:20.720 --> 02:05:25.720
So when we do trim trees, we
document in our GIS the species

02:05:26.153 --> 02:05:29.183
so that we can keep track
of which are fast growers.

02:05:30.220 --> 02:05:33.920
Our contractor also keeps track of them too.

02:05:33.920 --> 02:05:37.990
So they import that into our
system so we can evaluate it.

02:05:37.990 --> 02:05:40.933
They also have their own
slightly different system.

02:05:41.830 --> 02:05:43.996
It's basically just uploading the files

02:05:43.996 --> 02:05:47.590
between the two systems,
but they also keep track

02:05:47.590 --> 02:05:52.240
of fast growers so that they can make sure

02:05:52.240 --> 02:05:54.483
the revisit rate is appropriate.

02:06:00.180 --> 02:06:01.180
<v Colin>Thank you.</v>

02:06:02.360 --> 02:06:04.663
Okay. I just want to make sure,

02:06:06.150 --> 02:06:08.613
Mr. Abrams, do you have a question?

02:06:09.754 --> 02:06:11.454
I see your hand isn't raised, but?

02:06:23.350 --> 02:06:24.183
Okay.

02:06:24.183 --> 02:06:25.908
In light of the silence.

02:06:25.908 --> 02:06:30.370
Hey, Ryan, are there any questions

02:06:30.370 --> 02:06:32.883
in the chat or in the Q and A?

02:06:34.330 --> 02:06:36.973
<v Ryan>Hey, Colin, nothing coming from the chat.</v>

02:06:37.970 --> 02:06:39.193
<v Colin>No. Okay.</v>

02:06:40.529 --> 02:06:44.370
Then I will throw it back to Henry Burton

02:06:44.370 --> 02:06:45.413
with Cal Advocates.

02:06:47.870 --> 02:06:48.743
<v ->Okay, thanks.</v>

02:06:49.670 --> 02:06:52.880
So, next question is,
can each of the utilities

02:06:52.880 --> 02:06:57.510
talk about how you do hazard
tree assessment and removal?

02:06:57.510 --> 02:07:02.330
Do you have a particular
tool that you use to assess

02:07:03.560 --> 02:07:07.261
whether a tree is hazardous
and needs to be removed?

02:07:07.261 --> 02:07:12.261
Whose judgment are you
relying on for those assessments?

02:07:13.611 --> 02:07:18.230
How far out from the wires are you looking

02:07:18.230 --> 02:07:20.900
when you're making hazard tree assessments?

02:07:20.900 --> 02:07:22.700
Let's start with PacifiCorp I guess.

02:07:25.140 --> 02:07:27.840
<v Brian>Yes, so with respect
to hazard tree assessments,</v>

02:07:27.840 --> 02:07:30.120
when our pre-inspector goes out

02:07:31.120 --> 02:07:34.620
to look at the vegetation along the line,

02:07:34.620 --> 02:07:39.030
in general, if you visualize
they're walking along

02:07:39.030 --> 02:07:41.730
the middle of the corridor
underneath the line,

02:07:41.730 --> 02:07:43.801
looking off from either side,

02:07:43.801 --> 02:07:47.640
to either side of the right-of-way,

02:07:47.640 --> 02:07:52.140
and looking for vegetation
encroachment or hazard trees.

02:07:52.140 --> 02:07:54.883
and with respect to hazard trees, generally,

02:07:57.210 --> 02:07:59.730
in accordance with industry standards,

02:07:59.730 --> 02:08:01.510
they're conducting a visual assessment,

02:08:01.510 --> 02:08:03.440
a level one assessment.

02:08:03.440 --> 02:08:05.000
And if there aren't any,

02:08:05.000 --> 02:08:09.510
they're looking for visual
indicators of tree health,

02:08:09.510 --> 02:08:12.186
for example, if there are any defects,

02:08:12.186 --> 02:08:15.770
other environmental factors as well.

02:08:15.770 --> 02:08:17.860
Is the tree leaning?

02:08:17.860 --> 02:08:22.102
Does it appear to, the root,

02:08:22.102 --> 02:08:27.102
or erosion around the base
of the tree for soil instability?

02:08:27.530 --> 02:08:29.180
So they're looking at various factors.

02:08:29.180 --> 02:08:32.174
But they're, in general, in order for them

02:08:32.174 --> 02:08:36.480
to do, potentially, do conduct
any more detailed assessment,

02:08:36.480 --> 02:08:41.429
there would need to be some visual indicator

02:08:41.429 --> 02:08:43.860
that would draw their eye to that tree,

02:08:43.860 --> 02:08:46.150
to indicate that as a hazard tree.

02:08:46.150 --> 02:08:49.200
And in general, if there
is a visual indication

02:08:49.200 --> 02:08:52.528
that it's a hazard tree it's
treated as a hazard tree

02:08:52.528 --> 02:08:57.528
and identified for removal
or pruning or be addressed.

02:09:00.180 --> 02:09:03.980
And so that's the general process.

02:09:03.980 --> 02:09:08.381
And in general, they do take
into account other factors.

02:09:08.381 --> 02:09:11.544
Prevailing wind directions.

02:09:11.544 --> 02:09:16.406
Has there been, for example,
some recent logging activity

02:09:16.406 --> 02:09:20.740
in the area, which now
opens up area and makes,

02:09:20.740 --> 02:09:23.800
and some trees may be susceptible

02:09:23.800 --> 02:09:28.800
to windthrow, et cetera,
or erosion in that area.

02:09:28.910 --> 02:09:33.000
So, they do look at wind
patterns, soil structure

02:09:33.000 --> 02:09:36.680
to a degree, slope, et
cetera, and all that plays into

02:09:36.680 --> 02:09:39.823
their visual assessment
of identifying hazard trees.

02:09:41.770 --> 02:09:45.530
Was there a second
point to the question there?

02:09:45.530 --> 02:09:46.630
Or did I capture that?

02:09:49.776 --> 02:09:50.940
<v ->I think that's mostly it.</v>

02:09:50.940 --> 02:09:53.490
I guess how far away from the wires

02:09:53.490 --> 02:09:56.373
are you looking when you
make those assessments?

02:09:57.390 --> 02:09:59.300
<v Brian>Well, they're looking</v>

02:09:59.300 --> 02:10:03.180
as far as they can see
into the tree canopy there,

02:10:03.180 --> 02:10:07.410
and for trees that are within
strike distance of a line.

02:10:07.410 --> 02:10:09.630
So if there's a tree outside
of the strike distance

02:10:09.630 --> 02:10:11.710
from the line, that won't be looked out,

02:10:11.710 --> 02:10:14.460
even if it was a dead, dying tree.

02:10:14.460 --> 02:10:18.180
So they're looking at trees within

02:10:18.180 --> 02:10:21.253
strike distance of a line, in general.

02:10:23.270 --> 02:10:25.513
<v ->Great, thanks. Liberty.</v>

02:10:27.720 --> 02:10:28.553
<v Peter>Yeah.</v>

02:10:28.553 --> 02:10:32.340
So at Liberty we have a
couple of different approaches

02:10:32.340 --> 02:10:34.330
to hazard tree mitigation.

02:10:34.330 --> 02:10:38.370
One of them is a program specifically focused

02:10:38.370 --> 02:10:40.380
on dead and dying tree removals.

02:10:40.380 --> 02:10:43.440
So we'll have inspectors patrol the lines

02:10:43.440 --> 02:10:47.855
and look for any tree
that's dead or declining

02:10:47.855 --> 02:10:52.740
and is able to strike the facilities.

02:10:52.740 --> 02:10:56.830
So, in some instances,
on our service territory,

02:10:56.830 --> 02:11:00.070
they may be looking at trees 200 feet away

02:11:00.070 --> 02:11:03.710
from our power lines, due
to the tall trees that we have

02:11:03.710 --> 02:11:08.209
in our service territory and
the slope that can occur.

02:11:08.209 --> 02:11:11.390
So, they're looking pretty
far off right away, again,

02:11:11.390 --> 02:11:14.110
towards anything that
can strike the facilities

02:11:14.110 --> 02:11:16.430
and looking for those obvious defects.

02:11:16.430 --> 02:11:19.330
So that's kind of, we follow as far as tools.

02:11:19.330 --> 02:11:22.070
Typically we follow industry standards.

02:11:22.070 --> 02:11:27.070
So there's the ANSI A 300
Part 9 Tree Risk Assessment

02:11:27.160 --> 02:11:30.310
Standards that we
typically use as a guideline

02:11:30.310 --> 02:11:32.413
for performing hazard tree assessments.

02:11:33.430 --> 02:11:36.810
So that and dying tree inspection,

02:11:36.810 --> 02:11:39.890
typically what would fall
into the level one inspection

02:11:39.890 --> 02:11:42.280
where you're just patrolling the line

02:11:42.280 --> 02:11:44.840
and looking for those obvious defects

02:11:44.840 --> 02:11:47.790
or the dead and dying trees from one angle.

02:11:47.790 --> 02:11:50.520
We also do detailed inspections of our lines.

02:11:50.520 --> 02:11:55.130
And that's where we have tree inspectors,

02:11:55.130 --> 02:11:57.130
typically they're inspectors that have

02:11:57.130 --> 02:12:01.029
a little bit more experience
and they're looking for, again,

02:12:01.029 --> 02:12:04.360
obvious defects, dead, dying
trees, and things like that.

02:12:04.360 --> 02:12:07.716
But they're also looking
for green hazard trees

02:12:07.716 --> 02:12:11.196
with the capability of
striking our facilities.

02:12:11.196 --> 02:12:15.940
And if they see something that
would draw them to that tree,

02:12:15.940 --> 02:12:18.710
like was mentioned
before, then they'll perform

02:12:18.710 --> 02:12:21.130
what would be considered
a level two inspection,

02:12:21.130 --> 02:12:23.480
where they're walking
completely around that tree

02:12:23.480 --> 02:12:26.500
looking for any other
defects, the capability of it

02:12:26.500 --> 02:12:29.610
to strike the facilities,
the likelihood of it,

02:12:29.610 --> 02:12:32.440
factoring environmental
considerations and things like that.

02:12:32.440 --> 02:12:37.110
So, that's typically the
tools that we're using.

02:12:37.110 --> 02:12:40.120
There's also a Utility Tree Risk Assessment

02:12:40.120 --> 02:12:42.150
Best Management Practices publication

02:12:42.150 --> 02:12:46.490
that was recently put
out, so we incorporate that,

02:12:46.490 --> 02:12:50.830
and we recently drafted a
hazard tree management plan

02:12:50.830 --> 02:12:52.709
that really outlines all this.

02:12:52.709 --> 02:12:57.120
And it is alluded to in our WMP.

02:12:57.120 --> 02:12:59.230
It's drafted, it's not finalized yet,

02:12:59.230 --> 02:13:03.022
but we're really drawing from those resources

02:13:03.022 --> 02:13:06.148
provided by the industry to help guide

02:13:06.148 --> 02:13:08.523
our hazard tree management plan.

02:13:22.720 --> 02:13:25.610
<v ->So similarly, we're looking at, Bear Valley,</v>

02:13:25.610 --> 02:13:30.610
at removal of dead or diseased trees

02:13:33.030 --> 02:13:36.853
that could fall into the line,

02:13:38.200 --> 02:13:41.483
is basically the distance that we look.

02:13:43.320 --> 02:13:47.743
And we also look at trees
under the drip line that are just,

02:13:48.600 --> 02:13:51.420
it's just it's too hard to manage them.

02:13:51.420 --> 02:13:55.922
You're gonna be revisiting
them very quick, too often.

02:13:55.922 --> 02:14:00.033
And then making those assessments,

02:14:00.033 --> 02:14:02.340
there's a couple of processes.

02:14:02.340 --> 02:14:04.460
One, the contractors' general foreman

02:14:04.460 --> 02:14:06.570
got a sense of experience.

02:14:06.570 --> 02:14:10.450
The contractor has an
arborist who they leverage.

02:14:10.450 --> 02:14:14.200
Our inspector has an enormous amount

02:14:14.200 --> 02:14:17.340
of experience in tree-trimming.

02:14:17.340 --> 02:14:20.300
And then we also now incorporate

02:14:20.300 --> 02:14:23.308
a forester into our process.

02:14:23.308 --> 02:14:28.308
As with most tree removals,
in our service area at least,

02:14:28.423 --> 02:14:31.880
there is a permitting requirement.

02:14:31.880 --> 02:14:34.740
So you just don't go chop down a tree.

02:14:34.740 --> 02:14:36.990
So there's an outside agency also

02:14:36.990 --> 02:14:41.990
that reviews our decisions in
making those tree removals.

02:14:53.200 --> 02:14:54.550
<v ->All right, thank you all.</v>

02:14:57.280 --> 02:14:59.930
<v Colin>Great. Thank you, Henry, for that question.</v>

02:15:01.770 --> 02:15:06.423
GPI, Zoe Harrold, do you
have another question?

02:15:08.270 --> 02:15:09.920
<v Zoe>Sure, I'll ask something.</v>

02:15:10.810 --> 02:15:13.670
Do any of the SMJUs have programs

02:15:13.670 --> 02:15:18.670
that basically route the
VM product or biomass

02:15:18.720 --> 02:15:21.950
to different end use applications?

02:15:21.950 --> 02:15:26.950
So either, pellet production
or particle board production

02:15:27.080 --> 02:15:30.893
or firewood for community
members, things like that?

02:15:36.619 --> 02:15:38.300
(radio beeping)

02:15:38.300 --> 02:15:39.363
<v Man>This is Britt.</v>

02:15:40.629 --> 02:15:42.850
<v Peter>Hi, this is Peter with Liberty.</v>

02:15:42.850 --> 02:15:46.490
I'll take the first stab at that question.

02:15:46.490 --> 02:15:51.490
Typically we don't direct
where the biomass goes.

02:15:52.960 --> 02:15:55.530
On those neighborhood or community projects

02:15:55.530 --> 02:15:58.716
that I had mentioned, the contractor,

02:15:58.716 --> 02:16:01.570
it's up to them where they take it.

02:16:01.570 --> 02:16:06.320
We do have one contractor
that was hauling all the biomass

02:16:06.320 --> 02:16:09.457
to a cogen plant where it's being,

02:16:09.457 --> 02:16:14.457
intended use to generate
energy from the biomass.

02:16:16.010 --> 02:16:21.010
We also had a contractor
take it to a similar facility to,

02:16:22.930 --> 02:16:27.930
actually it was one of the prisons over here,

02:16:28.410 --> 02:16:32.470
over in Nevada that uses
biomass to generate power,

02:16:32.470 --> 02:16:34.300
and so they brought it there.

02:16:34.300 --> 02:16:37.020
So I guess we don't typically dictate

02:16:37.020 --> 02:16:38.320
where the biomass goes.

02:16:38.320 --> 02:16:43.320
That's historically been
up to our contractors.

02:16:43.970 --> 02:16:47.210
But we're looking for ways to improve

02:16:47.210 --> 02:16:50.230
the utilization of biomass.

02:16:50.230 --> 02:16:51.770
When it comes to firewood,

02:16:51.770 --> 02:16:54.320
all of the work that we're typically doing

02:16:54.320 --> 02:16:58.750
on the California Tahoe Conservancy land is

02:16:58.750 --> 02:17:01.650
putting together, is having hand crews go in

02:17:01.650 --> 02:17:04.470
after our routine work
and bucking up that wood

02:17:04.470 --> 02:17:06.640
into firewood and stacking it.

02:17:06.640 --> 02:17:10.100
And then the Conservancy has
a firewood collection program.

02:17:10.100 --> 02:17:12.920
So we'll send that information back to them

02:17:12.920 --> 02:17:15.820
so they'll know exactly what
parcels we've completed.

02:17:15.820 --> 02:17:17.960
And it goes onto a map on their website.

02:17:17.960 --> 02:17:20.560
So people who have
permits to collect firewood

02:17:20.560 --> 02:17:22.560
know where they can go and collect firewood.

02:17:22.560 --> 02:17:25.310
So that's a really successful program.

02:17:25.310 --> 02:17:29.680
And then we also advertise internally

02:17:29.680 --> 02:17:31.440
to employees and things like that,

02:17:31.440 --> 02:17:34.854
where there's firewood
available to get picked up.

02:17:34.854 --> 02:17:39.854
But that's about the extent of the use

02:17:40.480 --> 02:17:43.363
I could think of at this point in time.

02:17:45.330 --> 02:17:47.180
<v Zoe>Thanks. That's helpful.</v>

02:17:47.180 --> 02:17:49.113
PacifiCorp and Bear Valley.

02:17:50.240 --> 02:17:52.128
<v Brian>Yes. Sorry, this is PacifiCorp.</v>

02:17:52.128 --> 02:17:56.170
My phone turned off in
the middle of the question,

02:17:56.170 --> 02:17:58.440
but based on the answer there it sounds like

02:17:58.440 --> 02:18:02.775
we're talking about slash and the end use

02:18:02.775 --> 02:18:07.775
of slash and wood chips and
programs associated with that.

02:18:08.490 --> 02:18:12.940
So Pacific Power, we do similar to Liberty.

02:18:12.940 --> 02:18:16.670
We don't dictate the end use per se,

02:18:16.670 --> 02:18:20.800
with respect to that
material with our contractor.

02:18:20.800 --> 02:18:24.450
In general, we do leave
a lot of the larger wood

02:18:24.450 --> 02:18:26.651
for the landowner that they can use

02:18:26.651 --> 02:18:28.880
for firewood and so forth.

02:18:28.880 --> 02:18:31.130
On some of our larger projects,

02:18:31.130 --> 02:18:34.910
large removal projects
that we have on going on,

02:18:34.910 --> 02:18:39.910
we have taken a lot of slash
to biomass energy producers,

02:18:41.080 --> 02:18:45.177
which has been fairly successful there.

02:18:45.177 --> 02:18:47.840
It's looking to be somewhat cost neutral

02:18:47.840 --> 02:18:50.767
as far as them purchasing the material

02:18:50.767 --> 02:18:54.240
to cover our transportation costs.

02:18:54.240 --> 02:18:59.240
And in general, we look
for ways and encourage

02:18:59.828 --> 02:19:03.550
the recycling of our wood chips

02:19:03.550 --> 02:19:07.080
in every opportunity that we can.

02:19:07.080 --> 02:19:10.320
But our tree contractor in large part

02:19:10.320 --> 02:19:13.383
will manage that process.

02:19:22.090 --> 02:19:27.090
<v ->So at Bear Valley, the contractor overall</v>

02:19:28.130 --> 02:19:33.130
is responsible per the
contract to remove the waste

02:19:33.253 --> 02:19:38.253
and dispose of them
properly in a legal manner.

02:19:40.370 --> 02:19:44.571
That's contractually our main requirement,

02:19:44.571 --> 02:19:47.820
and not leave anything behind.

02:19:47.820 --> 02:19:51.040
However, the contractor does, is allowed to,

02:19:51.040 --> 02:19:52.680
and they do work with customers.

02:19:52.680 --> 02:19:55.510
So if it's a tree that belonged to a customer

02:19:55.510 --> 02:19:57.233
and the customer wants the wood,

02:19:57.233 --> 02:20:00.740
then the customer gets the wood.

02:20:00.740 --> 02:20:03.900
We do work with the city
and provide them wood chips

02:20:06.161 --> 02:20:10.387
and also the water
company, if they want them,

02:20:11.340 --> 02:20:16.340
we provide them the wood
chips, or our contractor does.

02:20:16.410 --> 02:20:20.770
We also allow, the county
has a program to have wood

02:20:20.770 --> 02:20:24.473
for elderly and low-income folks.

02:20:25.618 --> 02:20:27.520
And so we do allow the contractor

02:20:27.520 --> 02:20:30.683
to provide that supply there too.

02:20:40.770 --> 02:20:42.320
<v Zoe>Great. Thanks everyone.</v>

02:20:46.233 --> 02:20:49.180
<v Colin>I see that we are running short on time,</v>

02:20:49.180 --> 02:20:52.220
but I do think we have
time for one more question.

02:20:52.220 --> 02:20:54.470
Henry, if you have another question,

02:20:54.470 --> 02:20:55.957
you are welcome to ask it.

02:20:59.390 --> 02:21:02.130
<v ->Sure. I guess this might be quick,</v>

02:21:02.130 --> 02:21:07.130
but do you keep track of the
performance of your contractor

02:21:08.400 --> 02:21:13.380
in things like how many errors or missed tree

02:21:13.380 --> 02:21:15.693
each contractor is responsible for?

02:21:19.138 --> 02:21:20.280
<v Brian>This is Pacific Power.</v>

02:21:20.280 --> 02:21:25.280
With the implementation of
our new electronic tracking,

02:21:26.310 --> 02:21:29.600
planning system that we rolled out last year,

02:21:29.600 --> 02:21:31.640
when our foresters conduct audits,

02:21:31.640 --> 02:21:35.760
we are tracking exceptions,
those audit findings.

02:21:35.760 --> 02:21:39.930
And so as of now, yes, we are
tracking those moving forward.

02:21:39.930 --> 02:21:44.620
And our foresters can,
based on those results,

02:21:44.620 --> 02:21:46.900
prompt discussions with our contractors,

02:21:46.900 --> 02:21:48.570
whether it be positive or negative,

02:21:48.570 --> 02:21:52.590
based on the number
of findings they're seeing.

02:21:52.590 --> 02:21:57.511
So we can course correct
and address any issues.

02:21:57.511 --> 02:22:01.650
As far as in the past,
we were also collecting

02:22:01.650 --> 02:22:04.070
that information, but it
was more paper-based.

02:22:04.070 --> 02:22:06.640
So moving forward, we'll
have an electronic database

02:22:06.640 --> 02:22:08.253
that we can build on.

02:22:10.480 --> 02:22:11.313
<v ->Great.</v>

02:22:11.313 --> 02:22:13.230
And you can link it back
to individual contractors

02:22:14.280 --> 02:22:16.143
or suppliers?
<v ->Correct.</v>

02:22:17.320 --> 02:22:18.153
<v ->Great.</v>

02:22:21.720 --> 02:22:26.480
<v Peter>Yeah. So at Liberty,
previously our audit process</v>

02:22:26.480 --> 02:22:29.830
was a little bit more ad hoc.

02:22:29.830 --> 02:22:33.810
Last year, we did a more formal audit

02:22:33.810 --> 02:22:37.780
of 15% of work that was performed for us.

02:22:37.780 --> 02:22:41.640
And so, with that data,
we're able to quantify

02:22:41.640 --> 02:22:46.320
which contractors were performing well,

02:22:46.320 --> 02:22:49.140
and with work orders
and everything like that,

02:22:49.140 --> 02:22:51.970
we could narrow it down to crew foreman

02:22:51.970 --> 02:22:54.163
if we wanted to and get pretty granular,

02:22:55.055 --> 02:22:58.879
if we saw a really consistent pattern

02:22:58.879 --> 02:23:03.879
of work failures that
wasn't meeting our criteria.

02:23:06.640 --> 02:23:10.614
And moving forward, we're developing

02:23:10.614 --> 02:23:15.614
a more robust quality
assurance, quality control plan,

02:23:15.810 --> 02:23:18.690
that we'll be rolling out to have

02:23:21.188 --> 02:23:24.540
a larger sample size and more data,

02:23:25.380 --> 02:23:27.600
more frequent inspections and audits,

02:23:27.600 --> 02:23:30.900
and also closer to the time
of work being performed,

02:23:30.900 --> 02:23:34.140
so that we can continue finding

02:23:34.140 --> 02:23:36.650
and fixing any issues that are out there.

02:23:36.650 --> 02:23:41.650
And again, with our
database, being able to go back

02:23:42.020 --> 02:23:45.030
to those work orders and determine do we have

02:23:46.689 --> 02:23:51.250
any patterns and that'll
help inform future training

02:23:51.250 --> 02:23:54.070
for contractors or future
work with contractors

02:23:54.070 --> 02:23:56.653
to continually improve our program.

02:24:04.280 --> 02:24:06.800
<v Paul>So, Bear Valley typically only has</v>

02:24:06.800 --> 02:24:10.853
one contracted company performing the work.

02:24:15.730 --> 02:24:18.800
Our veg management program, QC program,

02:24:18.800 --> 02:24:21.490
does have the ability and we do track

02:24:22.508 --> 02:24:27.508
the number of vegetational
orders resulting from QCs.

02:24:29.820 --> 02:24:32.260
Back in 2018, at the very beginning,

02:24:32.260 --> 02:24:34.917
when we implemented that program

02:24:34.917 --> 02:24:37.270
and really had metrics to it,

02:24:37.270 --> 02:24:42.270
we discovered our previous
contractor was not performing

02:24:42.370 --> 02:24:44.753
to the level that we needed.