WEBVTT

00:00:00.420 --> 00:00:01.873
<v Man>Thank you for your patience.</v>

00:00:21.404 --> 00:00:22.550
<v Melissa>Taking a look,
looks like we have folks on,</v>

00:00:22.550 --> 00:00:26.722
we have let's see, the
webcast also available

00:00:26.722 --> 00:00:28.172
for people just to listen in.

00:00:29.160 --> 00:00:30.370
So we'll get started.

00:00:30.370 --> 00:00:31.830
So good morning, everyone.

00:00:31.830 --> 00:00:35.830
On behalf of Director
Caroline Thomas Jacob,

00:00:35.830 --> 00:00:38.200
is the Director of the
Wildfire Safety Division.

00:00:38.200 --> 00:00:41.960
Thank you for joining us today
for our technical workshops

00:00:41.960 --> 00:00:45.940
on the 2021 Wildfire
Mitigation Plan Updates.

00:00:45.940 --> 00:00:49.230
My name is Melissa Semcer
and I'm the Program Manager

00:00:49.230 --> 00:00:50.600
in the Mitigation Branch,

00:00:50.600 --> 00:00:54.035
which houses the team of
experts undertaking review

00:00:54.035 --> 00:00:58.660
of the 2021 Wildfire
Mitigation Plan Updates.

00:00:58.660 --> 00:01:02.720
Our team along with the team
from CAL FIRE are responsible

00:01:02.720 --> 00:01:06.130
for evaluating the update
in support of a final decision

00:01:06.130 --> 00:01:08.733
on approval or denial of each plan.

00:01:09.790 --> 00:01:12.500
The goal of our workshops
over the next two days is

00:01:12.500 --> 00:01:16.330
to allow PG and E, SCE, and SEC and E

00:01:16.330 --> 00:01:20.390
to present and explain
their 2021 plan updates,

00:01:20.390 --> 00:01:23.500
focusing on specific areas
and to allow stakeholders

00:01:23.500 --> 00:01:26.350
and the general public to
ask questions of the utilities.

00:01:27.630 --> 00:01:30.650
As opposed to last year where
we had each utility present

00:01:30.650 --> 00:01:33.040
an overview of their entire plan

00:01:33.040 --> 00:01:35.640
this year effort to
streamline our process

00:01:35.640 --> 00:01:37.900
and in recognition of the
challenges of conducting

00:01:37.900 --> 00:01:39.878
a workshop in a remote environment,

00:01:39.878 --> 00:01:42.750
we sought to have utilities
hone in their presentations

00:01:42.750 --> 00:01:46.290
on four key areas, and
that is risk assessment,

00:01:46.290 --> 00:01:48.470
mapping and resource allocation,

00:01:48.470 --> 00:01:52.290
vegetation management, grid,
design, and system hardening,

00:01:52.290 --> 00:01:55.428
including inspections and
public safety, power shutoffs,

00:01:55.428 --> 00:01:57.095
or the energization.

00:01:58.703 --> 00:01:59.610
A note about today?

00:01:59.610 --> 00:02:04.110
The review of the WNT's
pursuant to Assembly Bill 10 64

00:02:04.110 --> 00:02:07.830
happened outside of a
formal Commission proceeding.

00:02:07.830 --> 00:02:10.380
However, the Commission
will take an action

00:02:10.380 --> 00:02:14.320
to ratify or not the Wildfire
Safety Division's actions

00:02:14.320 --> 00:02:16.650
on the Wildfire Mitigation Plans.

00:02:16.650 --> 00:02:19.090
So please be informed of
all communication practices

00:02:19.090 --> 00:02:22.203
involving discussion with
Commissioners or decision-makers.

00:02:24.021 --> 00:02:27.360
If we could just switch to
the next slide before I go on,

00:02:27.360 --> 00:02:29.330
I'll go through a brief safety message.

00:02:29.330 --> 00:02:32.980
So in these virtual times,
we're all in different locations.

00:02:32.980 --> 00:02:34.870
The please be aware of your surroundings

00:02:34.870 --> 00:02:37.070
and know two evacuation routes.

00:02:37.070 --> 00:02:39.470
Please have those mapped
out from your location.

00:02:40.350 --> 00:02:42.030
If you are alone and you
feel comfortable doing so,

00:02:42.030 --> 00:02:44.740
please make sure someone
is aware of your location

00:02:44.740 --> 00:02:47.096
in the event of an emergency.

00:02:47.096 --> 00:02:50.000
These workshops are
all day and require us to sit

00:02:50.000 --> 00:02:51.370
in front of the computer.

00:02:51.370 --> 00:02:53.360
We have built-in breaks.

00:02:53.360 --> 00:02:55.120
Please be sure to get up and move around

00:02:55.120 --> 00:02:57.193
the day and take
breaks as you need them.

00:03:00.350 --> 00:03:01.870
Also, please be aware to take care of

00:03:01.870 --> 00:03:03.460
your mental health during these times,

00:03:03.460 --> 00:03:05.633
including again, taking
breaks as needed.

00:03:06.550 --> 00:03:09.160
Please also practice any
public health guidelines regarding

00:03:09.160 --> 00:03:11.745
COVID-19 if you are around other people.

00:03:11.745 --> 00:03:14.425
And finally, if you see
something, say something,

00:03:14.425 --> 00:03:17.030
if you need immediate assistance,

00:03:17.030 --> 00:03:19.660
in addition to having
someone know your location,

00:03:19.660 --> 00:03:23.520
you're welcome to ping us in the chat.

00:03:23.520 --> 00:03:25.290
We'll be monitoring the chat throughout.

00:03:25.290 --> 00:03:26.340
So if you need assistance,

00:03:26.340 --> 00:03:28.853
please make sure that you let us know.

00:03:30.920 --> 00:03:32.843
If we move on to the next slide, please.

00:03:36.390 --> 00:03:37.560
All right, so I'll quickly run through

00:03:37.560 --> 00:03:38.840
the schedule for today.

00:03:38.840 --> 00:03:40.678
We're a little bit behind.

00:03:40.678 --> 00:03:43.720
So I'm going to just
go over this quickly.

00:03:43.720 --> 00:03:46.130
The general cadence of the
workshop is to allow a period of

00:03:46.130 --> 00:03:48.880
time for each of the three
large utilities to present

00:03:48.880 --> 00:03:50.430
on their designated topic.

00:03:50.430 --> 00:03:53.510
Then we take a break and
then we enter into a Q and A,

00:03:53.510 --> 00:03:55.390
question and answer session.

00:03:55.390 --> 00:03:58.490
So first up today is the risk
management mapping and

00:03:59.412 --> 00:04:00.740
resource allocation methodology.

00:04:00.740 --> 00:04:03.995
And after a break, we'll begin
our Q and A on that topic.

00:04:03.995 --> 00:04:08.230
Then we'll go to lunch at
12:30, and then we will go

00:04:08.230 --> 00:04:10.923
into vegetation management
inspection strategy.

00:04:12.230 --> 00:04:15.608
Take another break in the
afternoon and then finish with

00:04:15.608 --> 00:04:19.630
vegetation management
question and answer sessions,

00:04:19.630 --> 00:04:20.734
the brief discussion on next steps list

00:04:20.734 --> 00:04:23.930
the comparing us for tomorrow.

00:04:23.930 --> 00:04:25.500
And then we will adjourn.

00:04:26.810 --> 00:04:28.260
Go to the next slide, please.

00:04:31.940 --> 00:04:35.389
Okay, so in framing our
discussion over the next two days,

00:04:35.389 --> 00:04:37.960
the Wildfire Safety
Division asked the utility

00:04:37.960 --> 00:04:41.530
to focus on each of the
five questions listed below.

00:04:41.530 --> 00:04:44.180
What progress have you
achieved over the past year?

00:04:44.180 --> 00:04:47.510
And how does that progress
impact your anticipated work

00:04:47.510 --> 00:04:49.593
in 2021 and 2022?

00:04:50.450 --> 00:04:54.040
How do you understand your
risk and how does risk factor

00:04:54.040 --> 00:04:55.840
into decision-making?

00:04:55.840 --> 00:04:57.090
Here, we want to emphasize

00:04:57.090 --> 00:04:59.180
that utility mitigation initiatives

00:04:59.180 --> 00:05:03.130
should be priority prioritized
based on the reduction of

00:05:03.130 --> 00:05:06.730
wildfire, ignitions and public
safety power shut off events.

00:05:06.730 --> 00:05:09.800
It is imperative that the
utilities move towards a model

00:05:09.800 --> 00:05:12.580
where mitigation activities
are justified and risk reduction

00:05:12.580 --> 00:05:14.423
can be modeled and quantified.

00:05:16.200 --> 00:05:17.590
Based on that, the third question

00:05:17.590 --> 00:05:19.580
based on the modeling described above,

00:05:19.580 --> 00:05:22.500
we're asking utilities to
discuss what are their priority

00:05:22.500 --> 00:05:25.410
mitigation activities in the next year,

00:05:25.410 --> 00:05:27.710
and where are those
activities being targeted?

00:05:28.640 --> 00:05:31.000
And what is the
anticipated reduction in risk

00:05:31.000 --> 00:05:33.500
as a result of these actions?

00:05:33.500 --> 00:05:36.280
The question four, how
will mitigation initiatives,

00:05:36.280 --> 00:05:39.630
in addition to reducing
ignition risks also reduce

00:05:39.630 --> 00:05:42.150
the scale, scope and,
frequency, a public place,

00:05:42.150 --> 00:05:44.343
public safety power shutoff events.

00:05:45.773 --> 00:05:47.263
And finally, question five.

00:05:48.198 --> 00:05:50.280
How will initiatives to
reduce the risk of ignition

00:05:51.119 --> 00:05:53.303
wildfire spread and impact the decision

00:05:53.303 --> 00:05:55.470
to use public safety power shutoff?

00:05:55.470 --> 00:05:56.450
So the fifth question is
essentially embedded in the

00:05:56.450 --> 00:05:57.693
previous four questions.

00:05:59.194 --> 00:06:00.433
Can we go to the next slide, please?

00:06:04.962 --> 00:06:06.563
All right, and we can
actually move on from there.

00:06:07.645 --> 00:06:10.003
So going to go through
some meeting logistics,

00:06:10.003 --> 00:06:12.477
so bear with me, and if
you have any questions,

00:06:12.477 --> 00:06:13.767
you can ask them in the chat,

00:06:13.767 --> 00:06:14.663
which I'll go through in a second.

00:06:16.510 --> 00:06:19.250
The main form of communication
for most people who are

00:06:20.399 --> 00:06:21.960
joining us today is going
to be through the chat

00:06:23.557 --> 00:06:25.600
and the chat can be down
in the lower right-hand corner

00:06:26.994 --> 00:06:27.827
of your WebEx screen.

00:06:30.167 --> 00:06:31.000
I don't think you can see my screen.

00:06:31.000 --> 00:06:32.860
So yeah, just, just this in
the lower right-hand corner

00:06:32.860 --> 00:06:34.360
as participants and then chat.

00:06:35.740 --> 00:06:37.430
When asking questions in the chat,

00:06:37.430 --> 00:06:40.573
you must choose who you're
sending your questions to.

00:06:42.004 --> 00:06:45.090
So as a note, the designated,

00:06:45.090 --> 00:06:48.790
WebEx host is the technical resource.

00:06:48.790 --> 00:06:50.726
So they're not actually a member of

00:06:50.726 --> 00:06:52.140
the Wildfire Safety Division Team.

00:06:52.140 --> 00:06:54.650
We're getting some
background noise coming in,

00:06:54.650 --> 00:06:56.443
so please mute mute yourself.

00:06:59.003 --> 00:07:02.690
So please only chat
with the host directly.

00:07:02.690 --> 00:07:05.713
If you have a question about
a technical WebEx issue,

00:07:07.100 --> 00:07:09.670
otherwise, questions directly
to the host will likely not

00:07:09.670 --> 00:07:12.560
be addressed in any
of our panel discussions.

00:07:12.560 --> 00:07:16.370
If you, if you wish to ask
questions to the presenters,

00:07:16.370 --> 00:07:20.650
please select "all panelists"
in the chat function.

00:07:20.650 --> 00:07:23.270
Someone from the Wildfire
Safety Division will be monitoring

00:07:23.270 --> 00:07:25.989
all the posts directed to all panelists.

00:07:25.989 --> 00:07:29.520
Again, please do not
use the Q and A feature

00:07:29.520 --> 00:07:32.690
which comes in under the
chat that is we're not going

00:07:32.690 --> 00:07:34.330
to be monitoring the Q and A feature.

00:07:34.330 --> 00:07:37.519
We're only going to be
monitoring the chat today.

00:07:37.519 --> 00:07:42.519
And we will route the questions
to the appropriate panelists

00:07:42.760 --> 00:07:45.210
or just present them to
the panelists themselves.

00:07:46.104 --> 00:07:50.660
Just the final note is that
in addition to the panelists,

00:07:50.660 --> 00:07:52.530
the utility representative,

00:07:52.530 --> 00:07:55.210
we've also asked several
stakeholder organizations

00:07:55.210 --> 00:07:56.645
to serve as panelists.

00:07:56.645 --> 00:07:59.620
So they will be able
to have an opportunity

00:07:59.620 --> 00:08:02.743
to ask questions
directly of the utilities.

00:08:04.330 --> 00:08:06.073
Can we go to the next slide, please?

00:08:09.840 --> 00:08:11.980
Okay, so as an example,

00:08:11.980 --> 00:08:15.799
when we go into the risk
mapping and assessment portion,

00:08:15.799 --> 00:08:17.500
stakeholders that are designated

00:08:17.500 --> 00:08:20.000
as panelists may ask questions.

00:08:20.000 --> 00:08:22.480
So in order to ensure
an orderly discussion,

00:08:22.480 --> 00:08:24.075
we ask that the panelists,

00:08:24.075 --> 00:08:26.380
please use the "raise hand" function

00:08:26.380 --> 00:08:28.370
in order to ask questions.

00:08:28.370 --> 00:08:31.720
The raise hand function is
found in the participant list.

00:08:31.720 --> 00:08:34.370
So if you open the participant
list and get that on the

00:08:34.370 --> 00:08:37.963
right hand side of your
screen, it's next to your name.

00:08:38.940 --> 00:08:41.510
The moderator will coordinate
those stakeholder panelist

00:08:41.510 --> 00:08:44.380
questions in the order
of the hands are raised.

00:08:44.380 --> 00:08:46.600
Once the stakeholder
panelists asked her questions,

00:08:46.600 --> 00:08:48.280
we ask that you lower your hands,

00:08:48.280 --> 00:08:51.040
by clicking the same
button to clear the queue.

00:08:51.040 --> 00:08:53.400
For everyone else who
does not have panelist status,

00:08:53.400 --> 00:08:56.263
again, please use the chat as described.

00:08:57.990 --> 00:08:59.690
Depending on the number
of questions received,

00:08:59.690 --> 00:09:01.477
we may not be able to
get through all of them,

00:09:01.477 --> 00:09:04.140
but we will definitely give it our best

00:09:04.140 --> 00:09:05.553
and try to get through them.

00:09:06.540 --> 00:09:10.120
So before I hand it over
for our first panel discussion,

00:09:10.120 --> 00:09:12.330
which we're actually a
little bit ahead of time,

00:09:12.330 --> 00:09:16.490
are there any questions
that anyone has is so feel free

00:09:16.490 --> 00:09:18.900
to please put those into the chat

00:09:18.900 --> 00:09:20.700
and I can do my best to answer them.

00:09:31.520 --> 00:09:33.130
Okay, so I'm not seeing any questions.

00:09:33.130 --> 00:09:37.010
So with that, I'm going
to hand it over to Alan Wu,

00:09:37.010 --> 00:09:38.680
and he's going to
moderate the first portion

00:09:38.680 --> 00:09:39.640
of our workshop.

00:09:39.640 --> 00:09:41.380
Thank you again, everyone for joining,

00:09:41.380 --> 00:09:43.330
looking forward to a fruitful two days.

00:09:45.900 --> 00:09:47.710
<v ->Thank you, Melissa.</v>

00:09:47.710 --> 00:09:50.020
Hi everyone, my name is Alan Wu,

00:09:50.020 --> 00:09:52.220
and then will Wildfire
Safety Analyst with

00:09:52.220 --> 00:09:55.550
the Mitigation Branch of
the Wildfire Safety Division.

00:09:55.550 --> 00:09:58.350
I'll be your moderator coming session.

00:09:58.350 --> 00:10:01.520
Wildfires continue to be a
big threat to the environmental,

00:10:01.520 --> 00:10:05.080
economical, and social
wellbeing for the State of California

00:10:05.080 --> 00:10:08.550
and Wildfire Risk Models will
play an important part of this

00:10:08.550 --> 00:10:10.610
battle by being the thread that holds

00:10:10.610 --> 00:10:14.300
the entire Wildfire
Mitigation Plans together.

00:10:14.300 --> 00:10:17.350
Risk models should show
the utilities where their risks

00:10:17.350 --> 00:10:20.670
lie now, where their
risks will be in the future,

00:10:20.670 --> 00:10:23.900
and also act as a guiding
compass to pinpoint

00:10:23.900 --> 00:10:26.890
where resources should be distributed.

00:10:26.890 --> 00:10:31.000
For the next hour, we will
focus on risk assessments, map,

00:10:31.000 --> 00:10:33.560
and resource allocation methodology,

00:10:33.560 --> 00:10:35.540
and listening to the
three utility companies

00:10:35.540 --> 00:10:38.190
explain their Wildfire Risk Models

00:10:38.190 --> 00:10:42.157
and how they're incorporated
into the 2021 (indistinct).

00:10:43.540 --> 00:10:46.430
The utilities will present in
the order of PG and E, SCE,

00:10:47.440 --> 00:10:49.110
and SDG and E.

00:10:49.110 --> 00:10:50.850
Members of the audience and panel,

00:10:50.850 --> 00:10:52.810
please remember to
reserve all questions until

00:10:52.810 --> 00:10:55.520
the Q and A portions
of today's schedule.

00:10:55.520 --> 00:10:57.553
PG and E, we'll welcome you first.

00:10:58.760 --> 00:10:59.890
<v ->Good morning, everyone.</v>

00:10:59.890 --> 00:11:01.540
Just a quick sound to video chat.

00:11:05.030 --> 00:11:07.550
I'll take that as affirmative.

00:11:07.550 --> 00:11:08.980
I'll introduce myself. First of all,

00:11:08.980 --> 00:11:10.670
my name is Paul McGregor.

00:11:10.670 --> 00:11:13.220
I'm the Director of Electric Operations,

00:11:13.220 --> 00:11:16.143
Risk Management, and
Analytics at PG and E.

00:11:17.180 --> 00:11:20.670
I'm new to PG and E
having joined them in 2021.

00:11:20.670 --> 00:11:22.190
So I think it's important
that I take a minute just

00:11:22.190 --> 00:11:24.420
to explain my background.

00:11:24.420 --> 00:11:27.850
Previously, I led the enterprise
risk management function

00:11:27.850 --> 00:11:32.270
at Southern California
Edison, 2019 to 2020,

00:11:32.270 --> 00:11:37.270
where I developed the Wildfire
Risk Model for SCE as well

00:11:38.420 --> 00:11:40.910
as participated in the general rate case

00:11:40.910 --> 00:11:43.080
for the 2021 filing.

00:11:43.080 --> 00:11:44.680
Along the way, we developed

00:11:44.680 --> 00:11:47.917
the Wildfire Mitigation Plan for 2020.

00:11:47.917 --> 00:11:50.140
And I initiated as part of the team for

00:11:50.140 --> 00:11:52.150
the 2021 filing.

00:11:52.150 --> 00:11:54.150
Prior to that, I started as a consultant

00:11:54.150 --> 00:11:55.680
to the electric utilities industry,

00:11:55.680 --> 00:11:59.730
primarily California, 2017 through 2019,

00:11:59.730 --> 00:12:03.800
where I assisted PG and E
with their 2017 route filing,

00:12:03.800 --> 00:12:08.800
SCE in their 2018 round
trialing, and PG and E

00:12:09.050 --> 00:12:12.070
with their 2020 general rate case.

00:12:12.070 --> 00:12:14.060
So being a mineral out in California

00:12:14.060 --> 00:12:15.750
and pretty familiar with wildfire.

00:12:15.750 --> 00:12:18.300
Prior to that, I've spent about 25 years

00:12:18.300 --> 00:12:20.400
in the electric utilities industry

00:12:20.400 --> 00:12:23.580
and a number of
operational and financial

00:12:23.580 --> 00:12:25.400
and risk management roles.

00:12:25.400 --> 00:12:27.451
So that's a little bit about me.

00:12:27.451 --> 00:12:28.390
We'll jump to the next page.

00:12:28.390 --> 00:12:30.060
I have the pleasure of this morning,

00:12:30.060 --> 00:12:32.650
folks of introducing you to

00:12:32.650 --> 00:12:36.380
PG and E's Wildfire
Mitigation Plan for year 2021.

00:12:36.380 --> 00:12:38.900
And we can go to the next page as well.

00:12:38.900 --> 00:12:40.260
And then I've just got a couple of pages

00:12:40.260 --> 00:12:42.980
to lay the landscape.

00:12:42.980 --> 00:12:44.360
Basically P and E has

00:12:44.360 --> 00:12:47.350
a 70,000 square mile service territory.

00:12:47.350 --> 00:12:48.960
I want to go to the next page, please.

00:12:48.960 --> 00:12:50.213
Isn't turning one lane.

00:12:51.540 --> 00:12:53.910
About half of our service territory

00:12:53.910 --> 00:12:56.160
lies within the high
fire threat districts,

00:12:56.160 --> 00:12:58.280
tier two and tier three,

00:12:58.280 --> 00:13:01.880
and nearly one third of
our overhead lines are

00:13:01.880 --> 00:13:04.660
in the high fire threat history areas.

00:13:04.660 --> 00:13:08.710
And we power our customers
and communities, as you can see,

00:13:08.710 --> 00:13:11.370
about 10% of our
customer communities are

00:13:11.370 --> 00:13:14.163
in those high fire districts as well.

00:13:15.600 --> 00:13:19.210
In recent years, we've
seen a high temperatures,

00:13:19.210 --> 00:13:23.930
extreme dryness, and very high winds,

00:13:23.930 --> 00:13:26.900
in our service territory,
again across California,

00:13:26.900 --> 00:13:28.280
also in PG and E.

00:13:28.280 --> 00:13:32.339
2020, I was another year
of unprecedented fires,

00:13:32.339 --> 00:13:36.070
five of the six largest fires reported.

00:13:36.070 --> 00:13:39.510
Five of them were in PG
and E's service territory.

00:13:39.510 --> 00:13:41.200
And then for 2021,

00:13:41.200 --> 00:13:45.950
we've kicked off with a red
flag warning and a PSPS event

00:13:45.950 --> 00:13:48.100
in January of 2021.

00:13:48.100 --> 00:13:51.440
So the environment doesn't
seem to be letting up there.

00:13:51.440 --> 00:13:53.871
If we can jump to the next page.

00:13:53.871 --> 00:13:57.170
PG and E's 2021 Wildfire Mitigation Plan

00:13:57.170 --> 00:13:59.980
continues many of the
actions from the 2019

00:13:59.980 --> 00:14:01.583
and 2020 WMT's.

00:14:03.420 --> 00:14:06.850
It reflects our evolution, embracing,

00:14:06.850 --> 00:14:08.570
and advancing of technologies both

00:14:08.570 --> 00:14:12.090
in risk assessment
and in risk mitigation.

00:14:12.090 --> 00:14:14.490
We apply a number of the lessons learned

00:14:14.490 --> 00:14:18.260
from the 2020 WMP process
and incorporate with feedback

00:14:18.260 --> 00:14:20.350
from the Wildfire Safety Division.

00:14:20.350 --> 00:14:22.450
PG and E has a federal monitor

00:14:22.450 --> 00:14:25.218
and several other industry partners.

00:14:25.218 --> 00:14:28.710
Their Wildfire Mitigation
Plan has basically three goals,

00:14:28.710 --> 00:14:33.090
the reduction of wildfire
increasing risk by inspections,

00:14:33.090 --> 00:14:35.880
vegetation management, and hardening.

00:14:35.880 --> 00:14:38.530
Yes, yes, we're required.

00:14:38.530 --> 00:14:41.220
The enhancement of situational awareness

00:14:41.220 --> 00:14:45.960
with weather stations, cameras,
and advanced meteorology.

00:14:45.960 --> 00:14:48.940
And finally, to reduce
the impact of PSPS

00:14:48.940 --> 00:14:52.720
on our customers by reducing
the number customers impacted,

00:14:52.720 --> 00:14:55.037
the duration of those
customers impacted,

00:14:55.037 --> 00:14:57.130
and improved timeliness and accuracy

00:14:57.130 --> 00:14:58.780
of information to communicate

00:14:58.780 --> 00:15:01.180
to those customers and communities.

00:15:01.180 --> 00:15:06.180
All of this is supported by
our Wildfire Risk Models,

00:15:06.590 --> 00:15:08.480
and we have significantly
enhanced those.

00:15:08.480 --> 00:15:10.800
And that's really what we
want to talk about today.

00:15:10.800 --> 00:15:13.870
So if I could ask you to
advance, eh, it's two pages, Alan,

00:15:13.870 --> 00:15:16.120
actually, because
there's a slide in between.

00:15:17.060 --> 00:15:20.070
This gives you an
overview of our evolution.

00:15:20.070 --> 00:15:22.300
And as I explained
through my background,

00:15:22.300 --> 00:15:26.010
I've actually had the experience
of working with PG and E

00:15:26.010 --> 00:15:28.900
through a number of
these stages along the way.

00:15:28.900 --> 00:15:32.720
We started in 2017,
with our first round report,

00:15:32.720 --> 00:15:35.230
which was a first-generation
set of models using

00:15:35.230 --> 00:15:38.570
probabilistic modeling
and Monte Carlo simulation,

00:15:38.570 --> 00:15:42.210
the implementation of our
risks and efficiency metric.

00:15:42.210 --> 00:15:47.210
And again, first
first-mover step forward.

00:15:47.400 --> 00:15:50.020
In 2019, for our WMP,

00:15:50.020 --> 00:15:52.863
we developed the Community
Wildfire Safety Program,

00:15:53.770 --> 00:15:55.630
and again, implemented first of

00:15:55.630 --> 00:15:59.570
a kind probabilistic
prioritization models

00:15:59.570 --> 00:16:01.523
using fire spread modeling.

00:16:02.620 --> 00:16:06.850
For 2020, again,
continuation of these programs

00:16:06.850 --> 00:16:11.140
as we moved to the
Technosylva Wildfire Propagation

00:16:11.140 --> 00:16:13.910
and Consequence Modeling.

00:16:13.910 --> 00:16:17.800
And then in 2020, we filed
our second RAMP filing,

00:16:17.800 --> 00:16:21.169
which again was a second
generation set of RAMP models.

00:16:21.169 --> 00:16:24.750
This time we moved to Python
Interface and we enhanced our

00:16:24.750 --> 00:16:29.230
multi attribute value function
in accordance with the 2018

00:16:29.230 --> 00:16:31.300
S-map settlement agreement.

00:16:31.300 --> 00:16:34.720
For 2021, I'm offering
you our next generation

00:16:34.720 --> 00:16:36.570
of risk models, where we adopt

00:16:36.570 --> 00:16:39.360
that maximum entropy modeling approach,

00:16:39.360 --> 00:16:42.350
as well as marrying that
up to the Technosylva

00:16:42.350 --> 00:16:46.260
consequence and propagation modeling.

00:16:46.260 --> 00:16:47.810
So it's been quite a journey.

00:16:47.810 --> 00:16:50.940
I think the words of David
Soldcall captures this best,

00:16:50.940 --> 00:16:53.453
where I would see, I
pleased the progress,

00:16:54.422 --> 00:16:55.255
but not satisfying.

00:16:55.255 --> 00:16:56.180
So we have a long way to go.

00:16:57.409 --> 00:16:59.170
To the next page, please.

00:16:59.170 --> 00:17:03.060
All right, 2021 Wildfire
Risk Modeling Approach,

00:17:03.060 --> 00:17:06.210
very much supports and
aligns with our RAMP.

00:17:06.210 --> 00:17:10.600
It also endorses the
probability of ignition component

00:17:10.600 --> 00:17:13.890
upfront or likelihood of risk
event will work as we call it,

00:17:13.890 --> 00:17:17.520
as well as that core of the
consequence of a risk event.

00:17:17.520 --> 00:17:21.080
The model is driven predominantly
by our vegetation ignition

00:17:21.080 --> 00:17:25.360
model and our equipment
ignition model coming together

00:17:25.360 --> 00:17:28.750
and combining with the
techniques over consequence model

00:17:28.750 --> 00:17:30.630
to produce our output.

00:17:30.630 --> 00:17:33.800
Our equation is simple,
wildfire risk equals ignition

00:17:33.800 --> 00:17:37.490
probability, multiplied
by wildfire consequence.

00:17:37.490 --> 00:17:40.070
As we discussed before
mitigation programs,

00:17:40.070 --> 00:17:43.550
focus on system hardening,
enhanced vegetation,

00:17:43.550 --> 00:17:45.680
inspection and repairs,

00:17:45.680 --> 00:17:47.650
and each of these are prioritized

00:17:47.650 --> 00:17:50.023
using the outputs of this risk model.

00:17:51.280 --> 00:17:52.860
Moving onto the next page.

00:17:52.860 --> 00:17:55.700
I would like to talk a little
bit about our enhancements

00:17:55.700 --> 00:17:57.700
from previous models.

00:17:57.700 --> 00:17:59.270
So there's a lot going on in next slide.

00:17:59.270 --> 00:18:00.790
So I'll take a second.

00:18:00.790 --> 00:18:05.300
When we started this journey,
we used our 2019 risk models,

00:18:05.300 --> 00:18:07.860
which were built at
the tail end of 2018,

00:18:07.860 --> 00:18:10.580
using a regression-type approach.

00:18:10.580 --> 00:18:12.120
And we matted that up with

00:18:12.120 --> 00:18:16.030
the Reax propagation and consequence.

00:18:16.030 --> 00:18:17.590
And we also had some other features

00:18:17.590 --> 00:18:20.652
in there to assume egress.

00:18:20.652 --> 00:18:24.000
For 2021, we made a
number of enhancements,

00:18:24.000 --> 00:18:25.280
the first major one being,

00:18:25.280 --> 00:18:27.920
replacing the
regression-based vegetation,

00:18:27.920 --> 00:18:31.820
ignition likelihood model
with the maximum entropy

00:18:32.844 --> 00:18:34.730
machine learning
ignition probability model

00:18:34.730 --> 00:18:37.350
and unexpanded covariate too.

00:18:37.350 --> 00:18:41.337
We did a very similar
thing with our ignition

00:18:41.337 --> 00:18:43.390
and our equipment ignition model,

00:18:43.390 --> 00:18:45.630
which focuses on conductor failures.

00:18:45.630 --> 00:18:48.280
Again, it utilizes the maximum entropy

00:18:48.280 --> 00:18:50.000
machine learning approach,

00:18:50.000 --> 00:18:54.853
and also has a wider
span of co-vary approved.

00:18:56.470 --> 00:18:57.570
These are married together

00:18:57.570 --> 00:18:59.910
with our Technosylva Consequence Model.

00:18:59.910 --> 00:19:03.200
So Technosylva uses a more advanced set

00:19:03.200 --> 00:19:06.120
of data layers than we
previously used in Reax

00:19:06.120 --> 00:19:10.540
is an updated fuels data
using LANDFIRE 2016,

00:19:10.540 --> 00:19:12.800
with which is enhanced for disturbances

00:19:13.755 --> 00:19:16.780
through 2020, disturbances
mean fire events.

00:19:16.780 --> 00:19:20.900
It also sits on top of updated
population information

00:19:20.900 --> 00:19:23.620
and updated structures information.

00:19:23.620 --> 00:19:25.930
When we look at
consequence coming out of

00:19:25.930 --> 00:19:29.450
the consequence model,
we're looking at acres,

00:19:29.450 --> 00:19:33.440
we're looking at buildings
impacted and population impacted

00:19:33.440 --> 00:19:36.650
and also a feature
called Fire Behavior Index,

00:19:36.650 --> 00:19:39.350
which gives us an estimation
of where that fire is going

00:19:39.350 --> 00:19:41.583
to go and at what kind of intensity.

00:19:42.870 --> 00:19:44.700
If I can jump to the next page.

00:19:44.700 --> 00:19:46.240
I want to talk a little bit about

00:19:46.240 --> 00:19:48.447
this maximum entropy approach,

00:19:48.447 --> 00:19:50.100
and I think it's important to,

00:19:50.100 --> 00:19:52.730
to set out what this is exactly.

00:19:52.730 --> 00:19:54.883
It's basically a logistic regression.

00:19:56.413 --> 00:19:57.246
Alan, I believe there's a delay,

00:19:57.246 --> 00:19:59.830
if you could maybe move
that slight forward along one.

00:20:02.090 --> 00:20:03.710
Thank you, that's great.

00:20:03.710 --> 00:20:05.330
So what does maximum entropy do?

00:20:05.330 --> 00:20:07.610
Maximum entropy is an algorithm

00:20:07.610 --> 00:20:11.680
that was developed on a
logistic regression perspective.

00:20:11.680 --> 00:20:14.480
And it's particularly
good for identifying

00:20:14.480 --> 00:20:18.603
where a species maybe
found based on the habitat.

00:20:19.582 --> 00:20:20.500
So how does that translate?

00:20:20.500 --> 00:20:22.908
Quite simply, what
we're looking for is that

00:20:22.908 --> 00:20:27.350
where can I expect
something to occur based

00:20:27.350 --> 00:20:32.350
on the co-variants or
variables around the area?

00:20:32.350 --> 00:20:33.240
So what I'm looking at,

00:20:33.240 --> 00:20:35.540
is I'm looking at a
set of asset variables,

00:20:35.540 --> 00:20:39.130
namely conductor size, conductor age,

00:20:39.130 --> 00:20:41.760
are there splices in
that conductor, et cetera,

00:20:41.760 --> 00:20:44.740
so specific to the assets themselves.

00:20:44.740 --> 00:20:47.417
And then we're looking at
a number of environmental

00:20:47.417 --> 00:20:49.580
variables also.

00:20:49.580 --> 00:20:50.920
So when I say environmental,

00:20:50.920 --> 00:20:54.440
I'm talking about vegetation
and precipitation, the dryness,

00:20:54.440 --> 00:20:57.380
the amount of fuel, is it grown fuels,

00:20:57.380 --> 00:21:02.130
is it ladder fuels or is it
high burning Crown fuels?

00:21:02.130 --> 00:21:04.777
And finally the weather co-variate.

00:21:04.777 --> 00:21:06.270
So we're looking at
the weather conditions.

00:21:06.270 --> 00:21:09.080
We have wind, we're
looking at precipitation,

00:21:09.080 --> 00:21:11.890
we're looking at
temperature, and also applying

00:21:11.890 --> 00:21:13.920
a temporal perspective to this.

00:21:13.920 --> 00:21:18.760
In other words, when
co-variates come together

00:21:18.760 --> 00:21:22.090
and produce the ignition effect?

00:21:22.090 --> 00:21:23.360
So that's a basic introduction.

00:21:23.360 --> 00:21:26.620
We try to keep this
simple and basically seeing

00:21:26.620 --> 00:21:29.230
where can we expect this to occur.

00:21:29.230 --> 00:21:32.710
So once we generate
our probability of ignition,

00:21:32.710 --> 00:21:34.550
I can jump to the next
stage and show you

00:21:34.550 --> 00:21:39.550
the progression on one
second, thanks you, Sir.

00:21:39.620 --> 00:21:42.200
So again, we developed
the probability of ignition

00:21:42.200 --> 00:21:45.050
using this maximum entropy approach.

00:21:45.050 --> 00:21:46.730
And from that, we marry that

00:21:46.730 --> 00:21:51.190
to Technosylva propagation
and consequence model.

00:21:51.190 --> 00:21:53.022
As a discuss profit,

00:21:53.022 --> 00:21:55.010
it gives us our outputs
and natural units.

00:21:55.010 --> 00:21:57.780
They are acres, structures, and people,

00:21:57.780 --> 00:22:00.790
as well as fire behavior index.

00:22:00.790 --> 00:22:05.790
We also convert this to what
PG and E calls its core MAVF,

00:22:06.080 --> 00:22:08.440
so that's a consequence of risk event,

00:22:08.440 --> 00:22:10.967
multi attribute value function.

00:22:10.967 --> 00:22:12.860
And we use those particular points

00:22:12.860 --> 00:22:15.243
for internal discussion
when we're ranking this.

00:22:15.243 --> 00:22:18.250
When we have ignition
probability multiplied

00:22:18.250 --> 00:22:22.467
by consequence coming
together, providing us our risk score,

00:22:22.467 --> 00:22:25.830
and we can see this in
a geographical interface.

00:22:25.830 --> 00:22:29.010
So just moving onto
the next slide, again,

00:22:29.010 --> 00:22:32.862
I want to emphasize how do
we operationalize this model

00:22:32.862 --> 00:22:33.880
because we've got a lot of data,

00:22:33.880 --> 00:22:35.670
it's a machine learning interface.

00:22:35.670 --> 00:22:38.250
So as lots and lots of TSB files,

00:22:38.250 --> 00:22:42.070
and then we're overlaying
that on top of a GIS data set.

00:22:42.070 --> 00:22:45.360
So we take the outputs of
the risk model and we have to

00:22:45.360 --> 00:22:50.270
consider additional factors
and updated language

00:22:51.666 --> 00:22:55.570
(muffled speaking) were
all built in the 2015 to 2019

00:22:55.570 --> 00:22:59.590
set of data, 2015 to 2018
was our training datasets.

00:22:59.590 --> 00:23:04.590
And '19 was our testing
or verification datasets.

00:23:04.760 --> 00:23:07.140
We apply from 2020 findings,

00:23:07.140 --> 00:23:11.864
whether they be in our updated
LIDAR on strike treats within

00:23:11.864 --> 00:23:13.605
the higher price right districts

00:23:13.605 --> 00:23:15.690
or from our public
safety specialist expertise

00:23:15.690 --> 00:23:18.590
in the area, knowing
these particular areas,

00:23:18.590 --> 00:23:23.590
knowing the patterns,
egress at the terrain, et cetera.

00:23:23.809 --> 00:23:26.730
A lot of these people
are ex fire service,

00:23:26.730 --> 00:23:29.130
local and Statewide.

00:23:29.130 --> 00:23:31.550
So it gives us a good
insight to fire behavior

00:23:31.550 --> 00:23:33.330
in that particular area.

00:23:33.330 --> 00:23:35.880
And then we want to consider
additional system hardening

00:23:35.880 --> 00:23:37.540
projects that have gone on,

00:23:37.540 --> 00:23:39.790
and particularly fire builds
two weeks, you know,

00:23:39.790 --> 00:23:41.543
fire in recent years.

00:23:42.730 --> 00:23:45.680
And also to consider PSPSD

00:23:45.680 --> 00:23:50.390
energization impacts from
our 2019 and 2020 seasons.

00:23:50.390 --> 00:23:51.630
These come together,

00:23:51.630 --> 00:23:55.970
they inform our work plans
for vegetation management,

00:23:55.970 --> 00:23:59.240
for system hardening,
and also our metrics,

00:23:59.240 --> 00:24:02.800
which are in our Wildfire
Mitigation Plan and also part of

00:24:02.800 --> 00:24:04.603
the company's compensation plan.

00:24:05.863 --> 00:24:07.260
So to give you guys an example here,

00:24:07.260 --> 00:24:10.483
I'll take you through one
example on the next page, please.

00:24:15.040 --> 00:24:16.490
This is an example of a system,

00:24:16.490 --> 00:24:19.140
a circuit that we call Keswick 1101,

00:24:19.140 --> 00:24:21.920
it's in the Whiskeytown area of Shasta.

00:24:21.920 --> 00:24:25.150
So anybody that knows that
area, it's a very beautiful area,

00:24:25.150 --> 00:24:26.820
large recreational area,

00:24:26.820 --> 00:24:29.610
a beautiful lake surrounded by trees.

00:24:29.610 --> 00:24:33.580
So on this particular
circuit, we've got the risk,

00:24:33.580 --> 00:24:36.840
the risk model identifies this as a,

00:24:36.840 --> 00:24:38.490
as a high priority circuit,

00:24:38.490 --> 00:24:41.280
based on the co-variates
that we talked about,

00:24:41.280 --> 00:24:43.790
the age of conductor
or the size of conductor,

00:24:43.790 --> 00:24:45.810
the proximity to drive agitation,

00:24:45.810 --> 00:24:49.790
to strike trees and applying
weather variables also.

00:24:49.790 --> 00:24:52.040
So this particular
segment, so it's called,

00:24:52.040 --> 00:24:53.740
we call it a structure protection,

00:24:54.750 --> 00:24:56.540
which is an isolatable
section of a circuit.

00:24:56.540 --> 00:24:58.750
Simply a circuit segment,

00:24:58.750 --> 00:25:02.050
this pops out as one
of our top 50 miles.

00:25:02.050 --> 00:25:04.790
It's about 6.6 miles in length.

00:25:04.790 --> 00:25:06.290
When we build our risk model,

00:25:06.290 --> 00:25:10.710
we're building this at 100
meters by 100 meter grid squares,

00:25:10.710 --> 00:25:14.340
and then we aggregate
it with red square pixels

00:25:14.340 --> 00:25:16.890
to the particular six circuit segment

00:25:16.890 --> 00:25:19.460
or circuit protection zone.

00:25:19.460 --> 00:25:22.100
So the score for this
one and our language

00:25:22.100 --> 00:25:25.620
is 48.8 M MAVF units.

00:25:25.620 --> 00:25:28.230
Our total land MAVF
units just coincidentally are

00:25:28.230 --> 00:25:32.810
about 25,000, which is a
similar amount of distribution,

00:25:32.810 --> 00:25:36.270
overhead lanes we have
in the high fire districts.

00:25:36.270 --> 00:25:39.010
So it's forcing nine points effectively.

00:25:39.010 --> 00:25:41.870
And the average risk score
on this particular segment is

00:25:41.870 --> 00:25:43.650
about 1.25 units.

00:25:43.650 --> 00:25:45.740
So it's relatively high risk.

00:25:45.740 --> 00:25:48.410
And again, we consider this circuit

00:25:48.410 --> 00:25:51.050
for various system hardening activities.

00:25:51.050 --> 00:25:52.960
We consider undergrounding,

00:25:52.960 --> 00:25:56.130
we consider traditional hardening,

00:25:56.130 --> 00:25:58.117
such as cupboard conductor,

00:25:58.117 --> 00:26:01.200
and we also consider
moving parts of the circuit.

00:26:01.200 --> 00:26:02.980
Are we moving parts of this circuit

00:26:02.980 --> 00:26:04.650
if we can do so?

00:26:04.650 --> 00:26:06.270
For this particular example,

00:26:06.270 --> 00:26:08.410
I believe the final solution was

00:26:08.410 --> 00:26:10.820
a hybrid of both undergrounding

00:26:10.820 --> 00:26:14.053
and Covered Conductor
system hardening type activity.

00:26:15.590 --> 00:26:19.246
So moving onto the final page
from my presentation is really

00:26:19.246 --> 00:26:20.079
what are we doing next?

00:26:20.079 --> 00:26:23.570
What does '21 look like for PGAD?

00:26:23.570 --> 00:26:27.060
And so for me, there's a
lot of work in advancing

00:26:27.060 --> 00:26:30.440
and evolving our Wildfire
Mitigation Programs

00:26:30.440 --> 00:26:32.670
and also understanding our risks.

00:26:32.670 --> 00:26:34.190
So for our nomenclature,

00:26:34.190 --> 00:26:35.640
we call this current model

00:26:35.640 --> 00:26:38.807
or 2021 Wildfire
Distribution Risk Model.

00:26:38.807 --> 00:26:41.950
And we will enhance some
of the capabilities for that

00:26:41.950 --> 00:26:46.270
to build that our 2022
Wildfire Distribution Risk Model.

00:26:46.270 --> 00:26:47.990
Some of the things we'll be doing there

00:26:47.990 --> 00:26:50.560
is adding additional asset classes,

00:26:50.560 --> 00:26:53.350
including transformers and poles,

00:26:53.350 --> 00:26:56.340
and also breaking down
that granularity to help us look

00:26:56.340 --> 00:27:01.340
at the RSE at a localized
circuit segment type level.

00:27:02.090 --> 00:27:03.360
Also in development is

00:27:03.360 --> 00:27:07.386
the 2022 Wildfire
Transmission Risk Model.

00:27:07.386 --> 00:27:09.900
Again, slightly different set of data

00:27:09.900 --> 00:27:10.970
will be used for that one.

00:27:10.970 --> 00:27:13.160
We're looking at different asset classes

00:27:13.160 --> 00:27:16.900
that are lesser ignitions at
the transmission voltage class.

00:27:16.900 --> 00:27:19.420
So we need to be specific
when we're training our models

00:27:19.420 --> 00:27:21.230
and what to look for.

00:27:21.230 --> 00:27:23.210
And finally, we're building out

00:27:23.210 --> 00:27:26.470
a future state PSPS Consequence Model.

00:27:26.470 --> 00:27:30.140
PG and E has built a
consequence model for the,

00:27:30.140 --> 00:27:33.160
at the enterprise or portfolio level.

00:27:33.160 --> 00:27:36.070
What we're doing now
for '20 and 2021 is building

00:27:36.070 --> 00:27:40.216
that out to a circuit level
to allow us to forecast

00:27:40.216 --> 00:27:44.670
a probability of de-energization
and the potential impact

00:27:44.670 --> 00:27:47.790
in the cost on the
customers and communities

00:27:47.790 --> 00:27:50.573
within that particular
segment of the circuit.

00:27:52.010 --> 00:27:54.780
So that ends my presentation
as far as the formal,

00:27:54.780 --> 00:27:57.350
I know we have a Q and A session.

00:27:57.350 --> 00:27:59.270
I see there's a couple of questions

00:27:59.270 --> 00:28:01.780
in the, in the, in the chat.

00:28:01.780 --> 00:28:03.040
I'm happy to answer those.

00:28:03.040 --> 00:28:05.232
No, but I'll upload to the moderator.

00:28:05.232 --> 00:28:07.630
If you want to hold to
those now or move those

00:28:08.707 --> 00:28:11.057
on to the Q and A
session for later in the day.

00:28:12.050 --> 00:28:13.590
<v ->Yep, thank you so much, Paul.</v>

00:28:13.590 --> 00:28:14.970
We're going to reserve all the questions

00:28:14.970 --> 00:28:16.360
until the Q and A section,

00:28:16.360 --> 00:28:19.570
so we'll get to them there.

00:28:19.570 --> 00:28:21.130
Yeah, thank you so
much for the presentation

00:28:21.130 --> 00:28:24.830
and we have Southern
California Edison coming up next.

00:28:24.830 --> 00:28:25.663
Thank you.

00:28:27.887 --> 00:28:29.970
Hey bud, what's going on?

00:28:33.350 --> 00:28:35.060
<v ->Okay, good morning, everyone.</v>

00:28:35.060 --> 00:28:36.340
My name is Robert LeMoine,

00:28:36.340 --> 00:28:38.530
I'm Director of Enterprise
Risk Management

00:28:38.530 --> 00:28:40.710
for Southern California Edison.

00:28:40.710 --> 00:28:43.853
And can we go to the next slide please?

00:28:45.630 --> 00:28:48.390
I want to first thank the
Commission and the Wildfire Safety

00:28:48.390 --> 00:28:51.290
Division staff for inviting
us today here today,

00:28:51.290 --> 00:28:54.610
and also recognize Paul
McGregor as well as for setting

00:28:54.610 --> 00:28:56.910
the stage for us, really
appreciate that Paul.

00:28:58.310 --> 00:29:00.470
I'll be taking the first
two slides that you'll see,

00:29:00.470 --> 00:29:02.470
and then in this presentation,

00:29:02.470 --> 00:29:04.500
and there'll be handing it over to Joe,

00:29:04.500 --> 00:29:07.704
our Director in T and
D who is responsible

00:29:07.704 --> 00:29:09.260
for their Wildfire Risk Model.

00:29:09.260 --> 00:29:11.010
Can we go to the next slide please?

00:29:12.700 --> 00:29:14.960
Okay, so what I want to talk to you

00:29:14.960 --> 00:29:17.090
about today is how we have evolved

00:29:17.090 --> 00:29:19.270
our risk-modeling capabilities.

00:29:19.270 --> 00:29:21.550
Since we did have an
attorney back in 2018,

00:29:21.550 --> 00:29:26.193
with our grid safety and
resiliency plan, back in 2018.

00:29:27.060 --> 00:29:30.300
We've evolved our risk
models significantly since then.

00:29:30.300 --> 00:29:33.990
Back in 2018, when we
first started this journey,

00:29:33.990 --> 00:29:38.253
our our process was
to take a look at the,

00:29:39.270 --> 00:29:44.270
the exposure of our
lines in high fire risk areas.

00:29:44.680 --> 00:29:47.550
So this was at a very
early stage portion of,

00:29:47.550 --> 00:29:50.630
of determining risk and the, the,

00:29:50.630 --> 00:29:54.470
the most important characteristic
in our GSRP plan was how,

00:29:54.470 --> 00:29:57.330
how, how much mile of
conductor was contained

00:29:57.330 --> 00:30:00.120
in the defined high
fire threat districts,

00:30:00.120 --> 00:30:02.063
tier two and tier three,

00:30:02.063 --> 00:30:06.410
that that was married up
with some other probability

00:30:06.410 --> 00:30:09.630
ignition models that allowed us
to determine where we wanted

00:30:09.630 --> 00:30:13.036
to target our initial
grid hardening efforts.

00:30:13.036 --> 00:30:17.070
Those grid hardening
efforts led to significant work

00:30:17.070 --> 00:30:20.412
that was performed
throughout 2019 and 2020.

00:30:20.412 --> 00:30:24.260
And, and then we continued

00:30:24.260 --> 00:30:25.740
to evolve those programs.

00:30:25.740 --> 00:30:30.740
Starting in 2019, we, we
evolved our, our capabilities

00:30:31.340 --> 00:30:36.340
to first first by looking at a
much better consequence model

00:30:38.120 --> 00:30:41.700
that Reax engineering
provided to us in early 2019.

00:30:41.700 --> 00:30:44.550
That consequence model
was a static model that looked

00:30:44.550 --> 00:30:48.800
at fire spread based on location

00:30:48.800 --> 00:30:49.930
throughout our service territory,

00:30:49.930 --> 00:30:53.740
in the high fire threat district,
and modeled structures

00:30:53.740 --> 00:30:57.030
impacted, population impacted,

00:30:57.030 --> 00:31:00.710
and did so using worst weather days

00:31:00.710 --> 00:31:03.563
from the previous
20-year, 20-year dataset.

00:31:05.180 --> 00:31:08.040
That that model married up

00:31:08.040 --> 00:31:10.890
with our probability ignition
model allowed us to, again,

00:31:12.380 --> 00:31:16.500
begin to target our, begin
to target our grid hardening

00:31:16.500 --> 00:31:19.670
efforts on a much more granular levels.

00:31:19.670 --> 00:31:21.390
Starting this year,

00:31:22.605 --> 00:31:24.380
what we're able to do was, was take,

00:31:24.380 --> 00:31:26.890
take those models that
were based on with tiers,

00:31:26.890 --> 00:31:29.510
high fire threat tiers two and three,

00:31:29.510 --> 00:31:33.080
and begin to traunch our
consequence in (indistinct)

00:31:33.080 --> 00:31:37.530
ignition down to the circuit
segment and acid sample.

00:31:37.530 --> 00:31:41.550
We did that by first
contracting with Technosylva,

00:31:41.550 --> 00:31:43.534
the same company that was mentioned

00:31:43.534 --> 00:31:45.245
in the PG and E presentation,

00:31:45.245 --> 00:31:48.690
which gave us real time capabilities to,

00:31:48.690 --> 00:31:51.323
and much more updated
data for consequence.

00:31:52.640 --> 00:31:57.120
Taking that down to, to a
circuit and segment level

00:31:57.120 --> 00:32:00.990
allows us to really model the
areas of our service territory

00:32:00.990 --> 00:32:04.010
that are the highest risk
and to rank those areas

00:32:04.010 --> 00:32:05.633
for grid hardening efforts.

00:32:07.260 --> 00:32:10.000
In addition, in this
part this past year,

00:32:10.000 --> 00:32:13.580
we developed an approach
to estimating PSPS risk.

00:32:13.580 --> 00:32:16.303
If we can go to the next
slide, I'll go over how we did it.

00:32:18.210 --> 00:32:23.061
Okay, so in '20, in, in mid 2020,

00:32:23.061 --> 00:32:26.000
we began developing
what we call our MARS 2.0.

00:32:26.000 --> 00:32:29.140
It's the extension of our
multi attribute value function

00:32:29.140 --> 00:32:33.280
from our 2018 RAMP
Proceeding, and to conform

00:32:33.280 --> 00:32:35.830
with the 2018 S-map settlement.

00:32:35.830 --> 00:32:38.660
In evolving to MARS 2.0,

00:32:38.660 --> 00:32:40.550
again, of the main features of this was

00:32:40.550 --> 00:32:43.200
to be able to traunch our work from what

00:32:43.200 --> 00:32:48.011
in the last year WMT
was a very high level

00:32:48.011 --> 00:32:49.737
at system level
framework down to a circuit

00:32:49.737 --> 00:32:51.890
and segment level framework.

00:32:51.890 --> 00:32:53.910
So we did that with two different

00:32:55.562 --> 00:32:56.770
what we call risk stacks.

00:32:56.770 --> 00:32:58.880
The first on the left on this slide

00:32:58.880 --> 00:33:01.140
is our wildfire risk stack.

00:33:01.140 --> 00:33:03.530
What, what this does
is it takes the output

00:33:03.530 --> 00:33:05.520
from our Wildfire Risk Model,

00:33:05.520 --> 00:33:08.870
the probability of ignition,
and the consequence provided

00:33:08.870 --> 00:33:12.830
by Technosylva, and
translate that into a multi,

00:33:12.830 --> 00:33:15.740
multi attribute risk score
using the dimensions,

00:33:15.740 --> 00:33:18.915
safety, reliability, and financial.

00:33:18.915 --> 00:33:22.570
Those are calculated using the outputs

00:33:22.570 --> 00:33:25.260
in the Technosylva model
based on population impacted

00:33:25.260 --> 00:33:29.830
by the fire, the amount
of reliability impacts,

00:33:29.830 --> 00:33:34.560
and financial impact based on
amount of structures impacted.

00:33:34.560 --> 00:33:38.034
That gives us one
score for each location

00:33:38.034 --> 00:33:40.480
for the Wildfire Risk Score.

00:33:40.480 --> 00:33:42.440
We've also developed a second risk stack

00:33:42.440 --> 00:33:44.290
for public safety, power shutoff.

00:33:44.290 --> 00:33:49.230
That is a combination of
probability of de-energization

00:33:49.230 --> 00:33:51.490
with the same dimensions,
safety, reliability,

00:33:51.490 --> 00:33:52.363
and financial.

00:33:53.275 --> 00:33:55.240
The probability of de-energization

00:33:55.240 --> 00:33:57.150
it's calculated looking back

00:33:57.150 --> 00:33:59.900
doing a back cast of 10, 10 years,

00:33:59.900 --> 00:34:02.550
a looked back to determine how a,

00:34:02.550 --> 00:34:04.250
which circuits and how
long those circuits would

00:34:04.250 --> 00:34:06.820
be energized based on current approaches

00:34:06.820 --> 00:34:08.170
and the weather that occurred back

00:34:08.170 --> 00:34:10.151
in those timeframes.

00:34:10.151 --> 00:34:13.450
On the, on the consequence side,

00:34:13.450 --> 00:34:17.145
safety, reliability, and
financial are calculated

00:34:17.145 --> 00:34:19.640
based on the number of
customers that are impacted

00:34:19.640 --> 00:34:22.180
by the de-energization
event, the length of that,

00:34:22.180 --> 00:34:25.530
that de-energization and a
framework for understanding

00:34:25.530 --> 00:34:28.442
the financial impact of the
customers from a PSPS event.

00:34:28.442 --> 00:34:32.470
What these w doing it
this way allows us to look at

00:34:32.470 --> 00:34:34.760
a combination of both the wildfire

00:34:34.760 --> 00:34:37.760
and the PSPS restore
risk scores allows us

00:34:37.760 --> 00:34:39.550
to add them up and, allows us

00:34:40.614 --> 00:34:42.080
to provide mitigation effectiveness

00:34:42.080 --> 00:34:44.800
against these different dimensions,

00:34:44.800 --> 00:34:46.910
so that we can understand how something

00:34:46.910 --> 00:34:50.410
like Covered Conductor
can reduce both wildfire risk

00:34:50.410 --> 00:34:53.070
and the risk of PSPS to customers.

00:34:53.070 --> 00:34:56.230
By doing that, we can
understand where it's best

00:34:56.230 --> 00:34:58.573
to deploy those mitigations.

00:35:00.153 --> 00:35:04.240
So I would like to close with
before I sent it over to Joe,

00:35:04.240 --> 00:35:06.310
is that most of what I'm talking about,

00:35:06.310 --> 00:35:07.780
what we're talking
about today is covered

00:35:07.780 --> 00:35:09.200
in our Wildfire Mitigation Plans,

00:35:09.200 --> 00:35:11.430
majority of it is in chapter four.

00:35:11.430 --> 00:35:13.140
I encourage everyone
to take a look at that

00:35:13.140 --> 00:35:15.520
where we describe in detail,

00:35:15.520 --> 00:35:17.330
how we come up with these metrics,

00:35:17.330 --> 00:35:19.780
and we'll be happy to answer questions

00:35:19.780 --> 00:35:22.040
at the end of the presentation.

00:35:22.040 --> 00:35:24.556
With that, I'm going to let
you advance the next slide

00:35:24.556 --> 00:35:25.593
and I'll turn it over to Joe.

00:35:27.010 --> 00:35:27.843
<v ->Thanks Robert.</v>

00:35:27.843 --> 00:35:29.280
Hi, I'm Joe Goizueta,

00:35:29.280 --> 00:35:32.310
I'm Director of Advanced
Analytics and Process Improvement

00:35:32.310 --> 00:35:34.103
here at Southern California Edison.

00:35:34.940 --> 00:35:36.420
Good morning.

00:35:36.420 --> 00:35:39.090
So Robert described these two stacks

00:35:39.090 --> 00:35:41.240
and I'll go into them a
little in a little bit more detail.

00:35:41.240 --> 00:35:44.287
So you understand how they're created.

00:35:44.287 --> 00:35:48.453
When we talk about our
Wildfire Risk Reduction Model,

00:35:49.700 --> 00:35:52.060
we actually describe it as a framework

00:35:52.060 --> 00:35:54.881
because it's a collection
of many, many models.

00:35:54.881 --> 00:35:57.130
We built it that way intentionally,

00:35:57.130 --> 00:36:00.010
so that we'd have a lot of
flexibility to analyze problems

00:36:00.010 --> 00:36:01.360
in a lot of different ways.

00:36:02.390 --> 00:36:06.930
Both the wildfire and the
PSPS risk components of

00:36:06.930 --> 00:36:10.140
the Wildfire Risk Reduction Model follow

00:36:10.140 --> 00:36:12.780
the same bow-tie approach.

00:36:12.780 --> 00:36:16.350
And I'll, I'll walk you
through each of these stacks,

00:36:16.350 --> 00:36:19.430
the wildfire stack, which
is the bow tie at the top,

00:36:19.430 --> 00:36:23.890
and then the PSPS stack,
which is the bow tie at the bottom.

00:36:23.890 --> 00:36:24.860
So if we start with

00:36:25.852 --> 00:36:28.052
the upper left box,
probability of ignition.

00:36:29.350 --> 00:36:32.970
We chose to, to take a
machine-learning approach

00:36:32.970 --> 00:36:35.250
at the asset level
for building of models,

00:36:35.250 --> 00:36:38.170
mainly because we
wanted enough granularity

00:36:38.170 --> 00:36:42.380
to understand each potential mitigation

00:36:42.380 --> 00:36:45.300
in as much detail as possible.

00:36:45.300 --> 00:36:50.300
And we also chose to
focus on outages as a proxy

00:36:50.980 --> 00:36:55.100
for ignitions rather than
using ignitions themselves.

00:36:55.100 --> 00:36:58.630
And then the main reason
is because fortunately,

00:36:58.630 --> 00:37:00.480
we don't have a lot of ignitions,

00:37:00.480 --> 00:37:04.540
at least not the number of
ignitions that you'd really need

00:37:04.540 --> 00:37:08.030
to build a robust
machine-learning model.

00:37:08.030 --> 00:37:11.230
Any of these big data models
really require thousands

00:37:11.230 --> 00:37:13.220
and thousands of data points.

00:37:13.220 --> 00:37:17.460
So the approach we took
was to look at our outage data

00:37:17.460 --> 00:37:19.560
and look at the categories of outages,

00:37:19.560 --> 00:37:22.900
the classifications of
outages, and identify

00:37:22.900 --> 00:37:27.063
which type of outages
could have led to a spark.

00:37:27.940 --> 00:37:30.930
So certainly like a wire
down could lead to a spark.

00:37:30.930 --> 00:37:35.930
A transformer could lead to a spark.

00:37:36.230 --> 00:37:37.810
And we, and we chose that,

00:37:37.810 --> 00:37:42.060
which gave us upwards of
a hundred thousand outages

00:37:42.060 --> 00:37:43.320
in our database.

00:37:43.320 --> 00:37:45.690
I think over 85,000
outages in our database

00:37:46.800 --> 00:37:49.310
to build these machine
learning models from

00:37:49.310 --> 00:37:52.020
which now gave us enough data

00:37:52.020 --> 00:37:54.660
to really hone in on these.

00:37:54.660 --> 00:37:58.810
So, like I said, we built
them at the asset level.

00:37:58.810 --> 00:38:03.110
We started with the conductor
model and built a conductor

00:38:03.110 --> 00:38:07.260
at the segment level,
probability of ignitions

00:38:07.260 --> 00:38:10.230
for any kind of conductor failures.

00:38:10.230 --> 00:38:15.230
Then we moved on to
capacitors, transformers, switches.

00:38:15.250 --> 00:38:19.070
And so for each, each individual asset

00:38:19.070 --> 00:38:23.203
has its own machine-learning
model to predict failures.

00:38:24.080 --> 00:38:27.490
Then we created a set of Contact

00:38:27.490 --> 00:38:30.680
with Foreign Objects Models.

00:38:30.680 --> 00:38:34.180
Those as well are show
up in our outage data.

00:38:34.180 --> 00:38:36.480
So we know if we had balloon outage or

00:38:36.480 --> 00:38:39.390
a vegetation related
outage or a car hit a pole,

00:38:39.390 --> 00:38:40.730
for example.

00:38:40.730 --> 00:38:43.520
So we built individual
machine-learning models for each

00:38:43.520 --> 00:38:46.460
of these different types of
contacts with foreign objects,

00:38:46.460 --> 00:38:49.913
vegetation, animal balloon vehicles.

00:38:51.470 --> 00:38:54.260
And, and then from that,

00:38:54.260 --> 00:38:56.980
the way we approach it is we run each of

00:38:56.980 --> 00:39:00.280
the models at the asset location.

00:39:00.280 --> 00:39:02.870
So typically since we're really dealing

00:39:02.870 --> 00:39:06.780
with mostly overhead areas,

00:39:06.780 --> 00:39:08.950
we're really talking
about that at the pole level,

00:39:08.950 --> 00:39:11.873
we call them a flock, a
functional location area.

00:39:13.370 --> 00:39:16.210
And what it does is we are not, we,

00:39:16.210 --> 00:39:19.030
we calculate the probability
of admission at each pole

00:39:21.080 --> 00:39:22.380
for everything outside of conductor,

00:39:22.380 --> 00:39:24.790
which we do at the segment level.

00:39:24.790 --> 00:39:27.380
And then we aggregate
those probabilities.

00:39:27.380 --> 00:39:30.570
So a pole that has
multiple pieces of equipment

00:39:30.570 --> 00:39:32.110
will aggregate those probabilities

00:39:32.110 --> 00:39:33.987
because each one of those assets

00:39:33.987 --> 00:39:38.433
has a potential of, of creating a spark.

00:39:40.470 --> 00:39:45.470
From there, we then multiply
that, our consequence score,

00:39:45.970 --> 00:39:47.670
as Robert mentioned,

00:39:47.670 --> 00:39:50.700
one of the advancements
we made last year was moving

00:39:50.700 --> 00:39:53.300
from our Reax consequent scores

00:39:53.300 --> 00:39:56.493
to the new Technosylva
consequence scores.

00:39:57.480 --> 00:40:01.200
That gives us our
risk score for a wildfire.

00:40:01.200 --> 00:40:03.970
And then, like I said, we,
we, it, depending on the,

00:40:03.970 --> 00:40:05.840
the analysis we're doing or the problem

00:40:05.840 --> 00:40:07.310
we're trying to solve,

00:40:07.310 --> 00:40:10.260
we can either use the
full wildfire component

00:40:10.260 --> 00:40:14.550
or we can use an individual
wildfire component.

00:40:14.550 --> 00:40:16.040
So for example, when we,

00:40:16.040 --> 00:40:18.456
when we're scoping
our Covered Conductor,

00:40:18.456 --> 00:40:23.456
the way we'll approach
that is by looking at the,

00:40:24.060 --> 00:40:28.110
the total segment risk,
creating a, a risk curve,

00:40:28.110 --> 00:40:33.010
similar to what you saw in
the PG and E presentation.

00:40:33.010 --> 00:40:36.740
And then we, we will, we
will take out the traunches

00:40:36.740 --> 00:40:39.170
from the highest risk to lowest risk

00:40:39.170 --> 00:40:42.450
based on how much
scope we want to target.

00:40:42.450 --> 00:40:45.610
So for example, when we're ready

00:40:45.610 --> 00:40:48.680
to go after the next 500 miles,

00:40:48.680 --> 00:40:51.740
we go down that curve
to the next 500 miles worth

00:40:51.740 --> 00:40:55.000
of segments that are the highest risk.

00:40:55.000 --> 00:40:57.060
That's what goes over to engineering.

00:40:57.060 --> 00:40:59.040
And then engineering will sort through

00:40:59.040 --> 00:41:02.740
the operational
components of it to figure out

00:41:02.740 --> 00:41:05.453
the best way to operationally
get it constructed.

00:41:06.860 --> 00:41:09.870
We could do that for
various other things.

00:41:09.870 --> 00:41:13.300
So for example, for
our inspection programs,

00:41:13.300 --> 00:41:17.420
the inspection programs
will look at both the probability

00:41:17.420 --> 00:41:20.970
of ignition along with the consequence

00:41:20.970 --> 00:41:24.250
as two different dynamics,
because what we,

00:41:24.250 --> 00:41:26.950
what we've been targeting
with our inspection programs

00:41:27.821 --> 00:41:29.200
is making sure that our accelerated,

00:41:29.200 --> 00:41:33.362
our enhanced inspections,
accelerated inspections

00:41:33.362 --> 00:41:37.080
are looking at both the
highest consequence

00:41:37.080 --> 00:41:39.483
and the highest probabilities.

00:41:41.180 --> 00:41:46.180
For vegetation, vegetation
may only look at consequence

00:41:47.570 --> 00:41:50.400
and, and prioritize their
work based on consequence

00:41:50.400 --> 00:41:52.183
where it's, where it's appropriate.

00:41:53.030 --> 00:41:55.903
One of the, one of the
main things that we're,

00:41:57.070 --> 00:42:02.070
that the reason we wanted
this extra flexibility is because

00:42:02.540 --> 00:42:06.450
we always have to balance
the operational efficiencies

00:42:06.450 --> 00:42:09.550
that you gain by approaching things

00:42:10.560 --> 00:42:14.330
by area versus things
where you want to go after

00:42:14.330 --> 00:42:18.020
in order the highest
risk, the lowest risk,

00:42:18.020 --> 00:42:21.820
because there's always that
time component of how much risk

00:42:21.820 --> 00:42:24.750
can you buy down if
you work more efficiently

00:42:24.750 --> 00:42:27.253
versus purely based on risk?

00:42:29.200 --> 00:42:32.200
On the, on the bottom bow tie,

00:42:32.200 --> 00:42:34.030
you see our probability, I mean,

00:42:34.030 --> 00:42:38.921
our PSPS component of the
Wildfire Risk Reduction Model,

00:42:38.921 --> 00:42:40.688
and Rob, as Robert mentioned,

00:42:40.688 --> 00:42:44.150
essentially what we did
to establish our probability

00:42:44.150 --> 00:42:48.720
of de-energization was to
go back through 10 years

00:42:48.720 --> 00:42:52.610
of weather data, both wind and FPI data,

00:42:52.610 --> 00:42:55.860
and then calculate based
on our current protocols

00:42:55.860 --> 00:42:57.909
for PSPS de-energizations.

00:42:57.909 --> 00:43:00.150
Each time we would have,

00:43:00.150 --> 00:43:03.923
if the PSPS program
was in place in the past,

00:43:05.020 --> 00:43:06.210
how many times we would have,

00:43:06.210 --> 00:43:09.560
or what the frequency of
de-energizations would have been

00:43:10.670 --> 00:43:12.510
for each isolatable segment,

00:43:12.510 --> 00:43:14.830
that basically then
gives us a probability,

00:43:14.830 --> 00:43:17.270
assuming that those same patterns are

00:43:17.270 --> 00:43:20.940
the same moving forward,
gives us our probability

00:43:20.940 --> 00:43:23.113
of future PSPS events.

00:43:23.980 --> 00:43:28.980
Those are then connected
to PSPS consequences,

00:43:29.420 --> 00:43:33.415
which use components of the,
some data from the Technosylva

00:43:33.415 --> 00:43:38.123
and then implemented through
our MARS risk framework.

00:43:39.750 --> 00:43:42.140
Both of these streams together,

00:43:42.140 --> 00:43:45.230
that's why we recently we
call them stacks is that we,

00:43:45.230 --> 00:43:50.100
we can add the wildfire
risk along with the PSPS risk

00:43:50.100 --> 00:43:52.750
to calculate a total risk figure,

00:43:52.750 --> 00:43:57.120
or we can look at just
wildfire risk or just PSPS risk,

00:43:57.120 --> 00:44:02.120
depending on what the, what
the problem is to be solved.

00:44:02.450 --> 00:44:04.098
It also gives us a sense for

00:44:04.098 --> 00:44:08.653
how does PSPS risk
compared to wildfire risk?

00:44:08.653 --> 00:44:11.770
When we, when we
compare those two, there,

00:44:11.770 --> 00:44:15.760
we find certainly much
higher wildfire risks

00:44:15.760 --> 00:44:17.798
than PSPS risks.

00:44:17.798 --> 00:44:20.943
Really an order of
magnitude are 10 times more.

00:44:21.803 --> 00:44:25.300
And on average, in
general, wildfire risk

00:44:25.300 --> 00:44:29.120
over PSPS risk, which,
which isn't surprising

00:44:29.120 --> 00:44:31.730
considering what happens
when a wildfire starts

00:44:31.730 --> 00:44:36.730
versus certainly not a,
not an insignificant risk

00:44:38.100 --> 00:44:42.053
of what happens when we
have to de-energize a circuit.

00:44:43.530 --> 00:44:47.000
If we can go to the
next slide, this next slide,

00:44:47.000 --> 00:44:49.560
basically just, just gives
you a sense for, you know,

00:44:49.560 --> 00:44:51.540
how we, how we operationalize it,

00:44:51.540 --> 00:44:55.130
or how we manage the
data behind the models.

00:44:55.130 --> 00:44:57.680
There really are two,
two components to it.

00:44:57.680 --> 00:45:01.990
One way we manage
the data is by bringing it in,

00:45:01.990 --> 00:45:04.160
into our Technosylva viewer.

00:45:04.160 --> 00:45:07.960
Technosylva from a consequence

00:45:07.960 --> 00:45:12.760
perspective, but they
also provide a GIS viewer,

00:45:12.760 --> 00:45:14.283
which stores their values.

00:45:15.288 --> 00:45:16.410
What we've done with, with Technosylva

00:45:16.410 --> 00:45:19.990
is that we also have arranged with them

00:45:19.990 --> 00:45:23.350
that we can provide them our
probability of ignition values,

00:45:23.350 --> 00:45:27.330
which they upload into their
system so that we have access

00:45:27.330 --> 00:45:29.920
in this GIS viewer.

00:45:29.920 --> 00:45:33.120
So we can go to, we w we, we didn't,

00:45:33.120 --> 00:45:37.170
we just try not to do a full
demo of it because of the time,

00:45:37.170 --> 00:45:38.106
but essentially we provide them updates

00:45:38.106 --> 00:45:42.100
that were probability ignition data.

00:45:42.100 --> 00:45:45.210
They allow us to visualize that along

00:45:45.210 --> 00:45:47.740
with their consequence data.

00:45:47.740 --> 00:45:49.720
And they also give
us a lot of granularity

00:45:49.720 --> 00:45:52.320
around their consequence
data, so we have options.

00:45:52.320 --> 00:45:54.070
One of the, one of the advancements

00:45:54.990 --> 00:45:57.230
we've been able to
make using Technosylva

00:45:57.230 --> 00:45:59.800
over Reax is that Technosylva gives us

00:45:59.800 --> 00:46:01.938
a lot of different options,

00:46:01.938 --> 00:46:04.680
whether we want to see a
max value or 90 percentile value

00:46:04.680 --> 00:46:09.460
or average value at
each specific location.

00:46:09.460 --> 00:46:10.510
The other advancement,

00:46:10.510 --> 00:46:13.900
which was a really important
advancement over Reax was

00:46:13.900 --> 00:46:18.445
that Reax provided data
in a raster format with that.

00:46:18.445 --> 00:46:22.030
But because we are at an
asset level with our probability

00:46:22.030 --> 00:46:24.890
of ignitions that
required a data scientist

00:46:24.890 --> 00:46:28.970
to basically extrapolate
or interpolate the,

00:46:28.970 --> 00:46:32.117
the value from the
raster to the nearest,

00:46:32.117 --> 00:46:33.943
to the nearest asset,

00:46:34.789 --> 00:46:39.410
Technosylva overcomes
that by providing us the values

00:46:39.410 --> 00:46:42.263
at the specific asset level.

00:46:43.810 --> 00:46:44.860
If you go to the next slide,

00:46:44.860 --> 00:46:47.097
I'll just talk a little bit about the,

00:46:48.094 --> 00:46:49.294
the future improvements.

00:46:50.448 --> 00:46:52.553
So prior prioritization of mitigation.

00:46:53.960 --> 00:46:57.913
One of the things that
we haven't gotten to yet,

00:46:59.500 --> 00:47:01.627
mainly, one reason using this is

00:47:01.627 --> 00:47:02.810
because it hasn't, it hasn't been

00:47:02.810 --> 00:47:04.790
as critical yet, but
it is going to start

00:47:04.790 --> 00:47:07.640
becoming more critical
as we move forward.

00:47:07.640 --> 00:47:10.180
Is that is that as, as I explained,

00:47:10.180 --> 00:47:13.550
we have each asset
has occurred, risk curve.

00:47:13.550 --> 00:47:17.070
So we had, we know for all
of the independent assets,

00:47:17.070 --> 00:47:20.203
how their risk pro what
their risk profile looks like.

00:47:21.180 --> 00:47:25.080
Covered Conductor
in general has provide,

00:47:25.080 --> 00:47:28.320
provides the most risk buy down for,

00:47:28.320 --> 00:47:30.540
in our service territory.

00:47:30.540 --> 00:47:33.586
But because it's a
curve, you get a lot of,

00:47:33.586 --> 00:47:37.610
a lot higher risk buy down
in the highest risk segments.

00:47:37.610 --> 00:47:40.519
And then they start to
taper off very much like

00:47:40.519 --> 00:47:43.120
the curve you saw
on Paul's presentation.

00:47:43.120 --> 00:47:44.310
So there becomes a point

00:47:44.310 --> 00:47:49.310
where various assets,
risk curves start to cross.

00:47:49.630 --> 00:47:53.640
So you get to a point where
maybe installing a spacer

00:47:53.640 --> 00:47:58.640
between a line becomes
a better mitigation option

00:47:59.400 --> 00:48:04.150
than going to the next
segment of Covered Conductor.

00:48:04.150 --> 00:48:07.920
So one of the things we're
working on moving forward is,

00:48:07.920 --> 00:48:09.470
is how do we know when these,

00:48:09.470 --> 00:48:13.440
these risks inflection
points take place?

00:48:13.440 --> 00:48:16.470
So when do we know where
at what points do we know

00:48:16.470 --> 00:48:20.100
it's better to now move
to a different mitigation

00:48:20.100 --> 00:48:22.920
versus Covered Conductor?

00:48:22.920 --> 00:48:26.910
And how do you, how do you
combine various mitigations

00:48:26.910 --> 00:48:31.830
at a location to get
the most risk buy down

00:48:31.830 --> 00:48:35.283
at that location for the cost involved?

00:48:36.420 --> 00:48:40.470
In general, particularly
air in a highest risk areas,

00:48:40.470 --> 00:48:43.390
there aren't, we haven't
found any combinations

00:48:43.390 --> 00:48:48.330
of mitigations that will
actually be bias more,

00:48:48.330 --> 00:48:51.350
buy down more risks
than Covered Conductor,

00:48:51.350 --> 00:48:53.360
particularly because Covered Conductor

00:48:53.360 --> 00:48:55.460
has the unique ability

00:48:55.460 --> 00:48:59.390
to mitigate both
equipment failure risks,

00:48:59.390 --> 00:49:02.560
along with the contact
with foreign object.

00:49:02.560 --> 00:49:07.560
So other mitigations that
we have, like spacers don't,

00:49:09.070 --> 00:49:12.370
don't take, don't mitigate that contact

00:49:12.370 --> 00:49:14.150
with foreign object risk.

00:49:14.150 --> 00:49:15.510
So particularly in areas where

00:49:15.510 --> 00:49:17.790
the consequences are very high and the,

00:49:17.790 --> 00:49:22.440
and the chance of an
equipment failure is also very high,

00:49:22.440 --> 00:49:24.640
doing these alternative mitigations

00:49:25.690 --> 00:49:29.440
don't really get you anywhere
near the amount of risk

00:49:29.440 --> 00:49:31.613
you get with with the Covered Conductor.

00:49:33.363 --> 00:49:36.180
Another, the other thing is that's

00:49:36.180 --> 00:49:39.292
on our plate for this year
is really understanding

00:49:39.292 --> 00:49:41.760
how Covered Conductor
in other mitigations

00:49:41.760 --> 00:49:45.454
will impact our PSPS thresholds.

00:49:45.454 --> 00:49:49.420
That's something that we've
been studying for a while.

00:49:49.420 --> 00:49:52.380
And and you'll hear more about that

00:49:52.380 --> 00:49:56.250
I think tomorrow during the PSPS panel,

00:49:56.250 --> 00:49:59.850
but understanding exactly
how comfortable we can be

00:49:59.850 --> 00:50:02.500
raising PSPS, wind thresholds,

00:50:02.500 --> 00:50:07.070
as new mitigations are put in
place is something that we're,

00:50:07.070 --> 00:50:10.940
that we're studying
very deeply right now.

00:50:10.940 --> 00:50:11.860
And then as I mentioned,

00:50:11.860 --> 00:50:14.220
the sequential
evaluation and mitigations,

00:50:14.220 --> 00:50:18.630
how to various combinations
of mitigations help?

00:50:18.630 --> 00:50:22.620
So for example, and, and
what impact do, do mitigations,

00:50:22.620 --> 00:50:25.253
particularly around
vegetation and inspection,

00:50:26.380 --> 00:50:29.941
what impacts do our mitigations
have on those programs?

00:50:29.941 --> 00:50:34.260
So for example, once we cover a segment,

00:50:34.260 --> 00:50:37.670
how confident can
we be in adjusting our,

00:50:37.670 --> 00:50:41.320
our inspection or vegetation
programs, meaning do,

00:50:41.320 --> 00:50:46.120
will we still need enhanced
trimming on a circuit

00:50:46.120 --> 00:50:48.400
that has Covered Conductor?

00:50:48.400 --> 00:50:51.870
We wanna make sure we
understand that very carefully

00:50:51.870 --> 00:50:54.323
before making changes to the program.

00:50:56.120 --> 00:50:58.690
So with that, I think,
I think that brings us

00:50:58.690 --> 00:51:01.230
to the end of, of our presentation.

00:51:01.230 --> 00:51:05.113
Look forward to the questions
during the Q and A session.

00:51:14.059 --> 00:51:14.892
<v ->All right, good
morning, everyone.</v>

00:51:14.892 --> 00:51:16.590
My name is Sarah Almujahed.

00:51:16.590 --> 00:51:18.273
Just checking my audio.

00:51:21.810 --> 00:51:22.643
<v ->Sounds good.</v>

00:51:23.748 --> 00:51:24.635
<v ->All right, thank you.</v>

00:51:24.635 --> 00:51:25.907
So I'm Sarah Almujahed.

00:51:25.907 --> 00:51:27.450
I'm the Strategy Manager in STG and E's

00:51:27.450 --> 00:51:29.610
Wildfire Mitigation Department.

00:51:29.610 --> 00:51:33.010
I'm joined by Mason
Withers our risk expert

00:51:33.010 --> 00:51:35.500
from the Enterprise Risk
Management Department.

00:51:35.500 --> 00:51:37.830
And together we'll walk
you through our evolution

00:51:37.830 --> 00:51:41.130
of risk modeling, starting back in 2010,

00:51:41.130 --> 00:51:44.090
where we implemented the
first version of the WRRM Model,

00:51:44.090 --> 00:51:46.180
the Wildfire Risk Reduction Model,

00:51:46.180 --> 00:51:49.830
working with Technosylva
and where we've come today

00:51:49.830 --> 00:51:51.840
with our WINGS Model.

00:51:51.840 --> 00:51:55.720
So back in 2010, we developed
the WRRM model to understand

00:51:55.720 --> 00:51:59.890
the wildfire risk on an
asset-by-asset level.

00:51:59.890 --> 00:52:03.820
In 2014, we operationalized this model

00:52:03.820 --> 00:52:08.180
to give us an understanding
of the fire risk potential

00:52:08.180 --> 00:52:09.430
as weather evolved.

00:52:09.430 --> 00:52:12.540
So during emergencies,
during fire season,

00:52:12.540 --> 00:52:16.440
we're able to see the dynamic
changes in risk modeling using

00:52:16.440 --> 00:52:18.970
the WRRM ops version of the model.

00:52:18.970 --> 00:52:22.970
In 2017, we made updates
to the WRRM model itself

00:52:22.970 --> 00:52:27.720
to continue to help us inform
our grid-hardening priorities,

00:52:27.720 --> 00:52:29.590
using different factors.

00:52:29.590 --> 00:52:32.420
And it's important to note
that during this timeframe,

00:52:32.420 --> 00:52:35.300
there was a lot of changes
also in the regulatory world

00:52:35.300 --> 00:52:38.810
with the risk OIR decision
coming out in 2014,

00:52:38.810 --> 00:52:43.120
our filing of the first
RAMP in 2016 and in 2018,

00:52:43.120 --> 00:52:46.040
the first S-map settlement
agreement that established

00:52:46.040 --> 00:52:48.810
the latest standard for building

00:52:48.810 --> 00:52:50.980
our risk quantification framework.

00:52:50.980 --> 00:52:53.550
In 2019, we filed the first RAMP

00:52:53.550 --> 00:52:57.040
using this new risk
quantification framework.

00:52:57.040 --> 00:52:59.250
And in 2020, we developed WINGS,

00:52:59.250 --> 00:53:01.870
building on all these milestones

00:53:01.870 --> 00:53:06.580
that we've, we've come
across over the past decade.

00:53:06.580 --> 00:53:07.713
Next slide please.

00:53:11.180 --> 00:53:12.872
So at a high level,

00:53:12.872 --> 00:53:14.590
we thought it would be helpful to just

00:53:14.590 --> 00:53:17.070
to give you an understanding of

00:53:17.070 --> 00:53:18.710
our risk-informed
decision-making approach

00:53:18.710 --> 00:53:20.550
and highlight the
three topics we're going

00:53:20.550 --> 00:53:23.153
to get into in today's presentation.

00:53:24.220 --> 00:53:25.730
The first part of the is really

00:53:25.730 --> 00:53:28.341
to understand the baseline risk.

00:53:28.341 --> 00:53:31.120
And that is basically based on using

00:53:31.120 --> 00:53:33.150
our risk quantification
framework to understand

00:53:33.150 --> 00:53:35.557
the likelihood and
consequence of a fire risk

00:53:35.557 --> 00:53:37.600
and a PSPS risk.

00:53:37.600 --> 00:53:39.470
The next step is to
identify the mitigation.

00:53:39.470 --> 00:53:42.600
So we catalog the mitigations
that we have and ones

00:53:42.600 --> 00:53:45.550
that we are planning to
implement as we get ready

00:53:45.550 --> 00:53:49.020
to put together our
Wildfire Mitigation Plan.

00:53:49.020 --> 00:53:52.120
And then we evaluate the
mitigation by calculating risks,

00:53:52.120 --> 00:53:55.030
spend efficiencies that
give us an indication

00:53:55.030 --> 00:53:58.480
of the cost effectiveness
of our programs.

00:53:58.480 --> 00:54:01.180
And the last step
here is really dynamic,

00:54:01.180 --> 00:54:05.131
meaning that it really helps
feed into the prior steps.

00:54:05.131 --> 00:54:07.610
It applies to the baseline risk.

00:54:07.610 --> 00:54:09.521
It helps us understand
the mitigations better,

00:54:09.521 --> 00:54:14.130
but really this initiative
level prioritization is a refined

00:54:14.130 --> 00:54:17.400
and deeper dive into specific
programs that are so large,

00:54:17.400 --> 00:54:19.100
that we need to have a refined approach

00:54:19.100 --> 00:54:21.150
to really prioritize the work within.

00:54:21.150 --> 00:54:24.200
And this is really an example of that is

00:54:24.200 --> 00:54:26.832
our grid-hardening
efforts, where we needed

00:54:26.832 --> 00:54:29.270
to come up with specific
models to prioritize

00:54:29.270 --> 00:54:34.200
our targeting and which
assets we want to replace first.

00:54:34.200 --> 00:54:35.540
The key models at the bottom

00:54:35.540 --> 00:54:38.580
and frameworks that we'll
touch on today are three.

00:54:38.580 --> 00:54:41.310
We're going to talk about the
risk quantification framework.

00:54:41.310 --> 00:54:43.130
This is really the
foundational framework

00:54:43.130 --> 00:54:45.440
that we use to understand
the baseline risk

00:54:45.440 --> 00:54:48.460
and we use to calculate
the risks, spend efficiencies,

00:54:48.460 --> 00:54:51.433
we'll touch on the Wildfire
Risk Reduction Model.

00:54:51.433 --> 00:54:54.610
And this is what we've
used historically to prioritize

00:54:54.610 --> 00:54:56.580
our traditional hardening efforts

00:54:56.580 --> 00:54:59.130
or what we call bare
conductor hardening,

00:54:59.130 --> 00:55:01.440
and we'll touch on our future model,

00:55:01.440 --> 00:55:04.250
the WINGS model that we
developed in 2020 and how it's going

00:55:04.250 --> 00:55:08.890
to help us optimize grid
hardening solutions in the future.

00:55:08.890 --> 00:55:10.740
And with that, I'll
turn it over to Mason

00:55:10.740 --> 00:55:13.230
to walk you through
the first two models,

00:55:13.230 --> 00:55:15.100
and then I'll take
over for the last piece

00:55:15.100 --> 00:55:16.400
to walk you through WINGS.

00:55:20.820 --> 00:55:21.863
Next slide.

00:55:25.360 --> 00:55:27.160
Let's skip two slides.

00:55:27.160 --> 00:55:28.360
Go ahead, Mason.

00:55:28.360 --> 00:55:30.117
<v Mason>Good morning, my
name is Mason Weathers,</v>

00:55:30.117 --> 00:55:32.590
I'm with the Enterprise
Risk Management Team.

00:55:32.590 --> 00:55:35.220
We thought we would cover
the risk quantification framework

00:55:35.220 --> 00:55:37.700
a little bit, just so that
everybody understands

00:55:37.700 --> 00:55:38.863
how it's being applied.

00:55:39.830 --> 00:55:42.900
In the RAMP proceeding
and they S NAFTA precedes it,

00:55:42.900 --> 00:55:46.900
we were asked to create a
risk quantification framework

00:55:46.900 --> 00:55:49.616
using a multi attribute value function

00:55:49.616 --> 00:55:53.150
at SDG and E and SoCalGas,
this is the one on the left.

00:55:53.150 --> 00:55:55.660
You see the, at the
top, you see attributes,

00:55:55.660 --> 00:55:57.660
health and safety,
reliability, financial,

00:55:57.660 --> 00:55:59.330
and stakeholder impact.

00:55:59.330 --> 00:56:01.460
We're not going to dive
into all the details of it,

00:56:01.460 --> 00:56:04.839
but essentially it's a
tool that we use to identify

00:56:04.839 --> 00:56:08.980
how to quantify risks
at the enterprise level.

00:56:08.980 --> 00:56:12.610
So each enterprise has a
Enterprise Risk Register,

00:56:12.610 --> 00:56:14.926
and one of those risk
registry items as wildfire.

00:56:14.926 --> 00:56:18.630
And so we basically figure
out what's the likelihood

00:56:18.630 --> 00:56:22.060
and consequence of the
wildfire risk on an annual basis,

00:56:22.060 --> 00:56:23.810
run it through this framework,

00:56:23.810 --> 00:56:26.880
try to understand the health
and safety implications,

00:56:26.880 --> 00:56:29.640
the impact of stakeholders,
how it affects reliability,

00:56:29.640 --> 00:56:31.290
financial, and so forth,

00:56:31.290 --> 00:56:35.660
and create a single
number from that process.

00:56:35.660 --> 00:56:38.470
Over on the right, you
can see our top five risks

00:56:38.470 --> 00:56:43.060
at SDG and E ranked one
through five by the risk score.

00:56:43.060 --> 00:56:45.970
So you see wildfire involving
SDG equipment is ranked

00:56:45.970 --> 00:56:48.300
as number one and then
electric infrastructure integrity,

00:56:48.300 --> 00:56:49.710
and so on.

00:56:49.710 --> 00:56:51.400
The lower is the concept of

00:56:51.400 --> 00:56:54.300
how likely is the event to happen?

00:56:54.300 --> 00:56:58.590
SDG and E is using the
likelihood of an ignition

00:56:58.590 --> 00:56:59.860
as its risk event.

00:56:59.860 --> 00:57:02.580
So lower stands for
likelihood of risk event.

00:57:02.580 --> 00:57:05.197
So our, our risk event is the ignition,

00:57:05.197 --> 00:57:07.464
and we get about 22 ignitions on it.

00:57:07.464 --> 00:57:10.400
That's our five-year
average per year ignitions.

00:57:10.400 --> 00:57:12.630
The core is the concept
of where on the left.

00:57:12.630 --> 00:57:15.260
If an event were to happen,
how bad would it be?

00:57:15.260 --> 00:57:16.730
How much safety viability,

00:57:16.730 --> 00:57:19.820
financial implications would
it have, and that's the core.

00:57:19.820 --> 00:57:22.590
So you run those assumptions
through the risk quantification

00:57:22.590 --> 00:57:24.550
framework and you get a core value.

00:57:24.550 --> 00:57:27.490
The risk score is the
lower times the core.

00:57:27.490 --> 00:57:30.550
What we're showing this
year is because PSPS is such

00:57:30.550 --> 00:57:34.350
a big impact to the
entire wildfire risk,

00:57:34.350 --> 00:57:38.490
we're showing both the wildfire
score and the PSPS score.

00:57:38.490 --> 00:57:41.590
So on the left of that slash
is the wildfire score or the

00:57:41.590 --> 00:57:44.580
wildfire lower and the wildfire
core and the right side of

00:57:44.580 --> 00:57:47.520
the slash is the PSPS lower end core.

00:57:47.520 --> 00:57:50.890
And you can see the
total score is 18,000.

00:57:50.890 --> 00:57:54.690
So for example, the way you
can read it as PSPS on average,

00:57:54.690 --> 00:57:59.690
we expect about four PSPS
events per year for PSPS.

00:58:00.970 --> 00:58:04.490
So that's essentially how
we calculate the risk scores.

00:58:04.490 --> 00:58:06.100
And that risk score is important,

00:58:06.100 --> 00:58:09.210
not just to show like how it
ranks amongst other risks of

00:58:09.210 --> 00:58:12.470
the company, but that is the
risk score that we say, hey,

00:58:12.470 --> 00:58:14.230
if we were going to do an activity

00:58:14.230 --> 00:58:17.270
of some sort of mitigation,
an asset replacement,

00:58:17.270 --> 00:58:19.240
how much does it move that risk score?

00:58:19.240 --> 00:58:22.300
So when we do a new
mitigation or proposed mitigation,

00:58:22.300 --> 00:58:24.650
we recalculate what the
lower and the core would be

00:58:24.650 --> 00:58:27.580
if those were in place and
we would get a new risk score.

00:58:27.580 --> 00:58:29.160
And that's how you develop the RSCs,

00:58:29.160 --> 00:58:31.530
which we'll get into in just a second.

00:58:31.530 --> 00:58:33.390
Down the bottom right,
you can see a breakdown

00:58:33.390 --> 00:58:37.124
between the tier two
tier three concepts.

00:58:37.124 --> 00:58:38.810
If there's any questions on that,

00:58:38.810 --> 00:58:39.800
we can go into that.

00:58:39.800 --> 00:58:41.150
For the purpose of saving time,

00:58:41.150 --> 00:58:43.300
I'd like to move to
the next slide, please.

00:58:45.850 --> 00:58:47.730
And here we have an example of

00:58:47.730 --> 00:58:50.130
how the risk quantification has worked.

00:58:50.130 --> 00:58:52.558
Again, I'm not going to go
through every single detail,

00:58:52.558 --> 00:58:55.750
but essentially what
you do is you say there's

00:58:55.750 --> 00:58:58.130
a pre mitigation score, and then there's

00:58:58.130 --> 00:58:59.630
a post mitigation score.

00:58:59.630 --> 00:59:01.900
So in this case for Hot Line Clamps,

00:59:01.900 --> 00:59:05.090
that's those connectors between
some of the overhead system

00:59:05.090 --> 00:59:07.690
that they have a certain
likelihood of failure.

00:59:07.690 --> 00:59:09.760
And if we replace those Hot Line Clamps,

00:59:09.760 --> 00:59:12.780
how many ignitions could be
reduced if we were to do that?

00:59:12.780 --> 00:59:15.366
So in this case, we're
saying for $2 million,

00:59:15.366 --> 00:59:17.160
we could reduce 0.008,

00:59:17.160 --> 00:59:20.010
and we would get 25
years of benefit for doing so.

00:59:20.010 --> 00:59:22.860
So that would be, we would
apply those assumptions

00:59:22.860 --> 00:59:24.700
to the post mitigation work,

00:59:24.700 --> 00:59:26.620
and we would in the
end, generate an RSP.

00:59:26.620 --> 00:59:28.740
At the very bottom you see it's 58,

00:59:28.740 --> 00:59:31.760
which is the change in the risk
score multiplied by how many

00:59:31.760 --> 00:59:33.400
years we get the benefit divided

00:59:34.444 --> 00:59:35.277
by the cost of doing the project.

00:59:35.277 --> 00:59:36.730
So we would say at the minute,

00:59:36.730 --> 00:59:40.310
the RSC for Hot Line Clamp
replacement is a score of 58.

00:59:40.310 --> 00:59:42.720
I know it's pretty quick,
pretty quick run through,

00:59:42.720 --> 00:59:44.870
but hopefully you'll see in
the slides that you'll be able

00:59:44.870 --> 00:59:46.320
to learn from how we do that.

00:59:48.240 --> 00:59:50.973
Let's move to the next slide, please.

00:59:54.360 --> 00:59:57.410
Okay, so before we,
yeah, okay, that's fine.

00:59:57.410 --> 00:59:59.700
So Sarah was talking
about how we have a current

00:59:59.700 --> 01:00:01.060
and we have a future.

01:00:01.060 --> 01:00:03.300
So we want to make sure
everybody doesn't confuse the two,

01:00:03.300 --> 01:00:05.250
but we're sort of, we've
got one leg in the past

01:00:05.250 --> 01:00:06.300
and one leg going forward.

01:00:06.300 --> 01:00:08.420
So we want to show both sides.

01:00:08.420 --> 01:00:09.810
The WRRM is sort of our,

01:00:09.810 --> 01:00:12.280
where we stand right now
and we're building upon it.

01:00:12.280 --> 01:00:15.370
And as the other utilities
I've mentioned, and it sounds,

01:00:15.370 --> 01:00:17.030
it's going to sound very similar.

01:00:17.030 --> 01:00:20.810
We essentially look at
the likelihood of ignition

01:00:20.810 --> 01:00:22.120
occurring at each asset.

01:00:22.120 --> 01:00:23.590
So we look at each pole

01:00:23.590 --> 01:00:26.340
and poles have
conductors attached to them.

01:00:26.340 --> 01:00:28.550
We're saying, what's
the likelihood of a failure,

01:00:28.550 --> 01:00:31.260
which would lead to
an ignition on each pole.

01:00:31.260 --> 01:00:34.194
Then we say, well, how bad
would the consequence be

01:00:34.194 --> 01:00:37.440
if we were inefficient
were to occur there?

01:00:37.440 --> 01:00:39.150
And just like, I think it was Paul said,

01:00:39.150 --> 01:00:42.208
it's simply the likelihood
is times the consequence.

01:00:42.208 --> 01:00:45.470
And that gives you your risk
score at each pole location.

01:00:45.470 --> 01:00:46.303
So in the past,

01:00:46.303 --> 01:00:48.630
what we would do is we
would take that risk score.

01:00:48.630 --> 01:00:50.902
And we would say,
based upon that risk score,

01:00:50.902 --> 01:00:52.552
we can evaluate the,

01:00:52.552 --> 01:00:55.761
how proposed projects
would look if we were to do so.

01:00:55.761 --> 01:00:57.820
So just like everybody else was saying,

01:00:57.820 --> 01:01:00.075
we use different
inputs to try to figure out

01:01:00.075 --> 01:01:02.551
what the likelihood we
were using Technosylva

01:01:02.551 --> 01:01:05.150
that we are using Technosylva
to come up with a consequence.

01:01:05.150 --> 01:01:06.670
And we marry those two together

01:01:06.670 --> 01:01:08.740
to figure out where
we should do projects.

01:01:08.740 --> 01:01:09.830
Let's move to the next slide.

01:01:09.830 --> 01:01:12.014
You see an example of
how we've been using that

01:01:12.014 --> 01:01:14.283
for a few years.

01:01:15.200 --> 01:01:18.360
Here's a visual and,
I'll give a little feedback.

01:01:18.360 --> 01:01:21.020
Here's the visual of the word outfits.

01:01:21.020 --> 01:01:22.890
Each pole on the right,

01:01:22.890 --> 01:01:25.970
the graphic on the right
each dot represents a pole.

01:01:25.970 --> 01:01:28.830
And it's already had its
likelihood and consequences

01:01:28.830 --> 01:01:31.170
sort of determined or
estimated, I should say.

01:01:31.170 --> 01:01:34.300
All models are estimates, estimated,

01:01:34.300 --> 01:01:35.430
and then we're color coding

01:01:35.430 --> 01:01:37.080
in such a way that the high risk ones

01:01:37.080 --> 01:01:39.590
are colored red, the lower are yellow.

01:01:39.590 --> 01:01:42.290
So what we would have
done with this in the past is

01:01:42.290 --> 01:01:44.080
we would give this to some engineers

01:01:44.080 --> 01:01:47.430
and some project managers,
designers to say, hey,

01:01:47.430 --> 01:01:49.060
what can you do on these areas

01:01:49.060 --> 01:01:51.220
that could make the likelihood go down?

01:01:51.220 --> 01:01:53.590
Typically, these jobs are not
reducing the consequences.

01:01:53.590 --> 01:01:55.750
If the fire did start, it was
probably burned the same.

01:01:55.750 --> 01:01:57.020
So it's focusing on the likelihood.

01:01:57.020 --> 01:01:59.590
And so we would give it
to some project managers,

01:01:59.590 --> 01:02:02.040
they'd figure out an area
of lots of red dots and say,

01:02:02.040 --> 01:02:03.790
we can do the following in this area,

01:02:03.790 --> 01:02:07.640
which was typically hardening
and maybe putting some

01:02:07.640 --> 01:02:09.500
improved infrastructure in there.

01:02:09.500 --> 01:02:12.330
And so we would go through
that process of trying to reduce

01:02:12.330 --> 01:02:15.210
the risk at the best
usage of our dollar based

01:02:15.210 --> 01:02:16.373
upon the word model.

01:02:17.400 --> 01:02:19.950
Again, so that's, that's
where we are as to right now,

01:02:19.950 --> 01:02:23.780
Sarah is going to talk about
where it's going in the future.

01:02:23.780 --> 01:02:26.330
I think that covers my
slides, thank you very much.

01:02:29.525 --> 01:02:30.358
<v ->All right, thank you, Mason,</v>

01:02:30.358 --> 01:02:33.100
let's jump to the next
portion of the presentation

01:02:33.100 --> 01:02:34.363
to talk about WINGS.

01:02:35.240 --> 01:02:36.663
Let's go to the next slide.

01:02:39.560 --> 01:02:42.350
Okay, so before we dive into WINGS,

01:02:42.350 --> 01:02:44.847
we thought it would be
helpful to just kind of level set

01:02:44.847 --> 01:02:48.750
and just understand this
concept of different levels

01:02:48.750 --> 01:02:50.330
of granularity for models.

01:02:50.330 --> 01:02:53.810
And if you think of the
spectrum of granularity

01:02:53.810 --> 01:02:55.400
on the one side on the left,

01:02:55.400 --> 01:02:57.510
you might have modeling approaches

01:02:57.510 --> 01:03:00.200
and analysis happening
on an asset level.

01:03:00.200 --> 01:03:01.100
And on the far right,

01:03:01.100 --> 01:03:04.240
you might have analysis
happening at an enterprise level.

01:03:04.240 --> 01:03:06.910
What Mason presented
really covers those two ends of

01:03:06.910 --> 01:03:09.132
the spectrum, where he talked about

01:03:09.132 --> 01:03:10.640
the enterprise risk assessments using

01:03:10.640 --> 01:03:12.440
our risk quantification framework.

01:03:12.440 --> 01:03:14.840
That what's, that's what
goes into our RAMP.

01:03:14.840 --> 01:03:17.280
On the other end is
the asset level analysis

01:03:17.280 --> 01:03:18.950
that we've been doing through WRRM

01:03:18.950 --> 01:03:22.120
to quantify grid hardening projects

01:03:22.120 --> 01:03:24.190
and, and prioritize those.

01:03:24.190 --> 01:03:26.970
Now with the heightened focus on PSPS,

01:03:26.970 --> 01:03:31.440
we found a need to come
up with a layer of granularity

01:03:31.440 --> 01:03:33.970
between those two opposite ends.

01:03:33.970 --> 01:03:36.500
And we defined this layer

01:03:36.500 --> 01:03:40.040
as the segment level of granularity.

01:03:40.040 --> 01:03:43.440
And the segment is defined
as a collection of spans

01:03:43.440 --> 01:03:46.100
and structures between
two isolation points

01:03:46.100 --> 01:03:50.350
or two skated devices that
we operate during PSPS.

01:03:50.350 --> 01:03:55.040
We had to look at the system
as a grouping of these assets

01:03:55.040 --> 01:03:56.810
between isolation points,

01:03:56.810 --> 01:03:59.980
because when we look at
PSPS and when we de-energize,

01:03:59.980 --> 01:04:01.870
we don't, de-energize an asset, we don't

01:04:01.870 --> 01:04:04.320
de-energize a pole or a wire.

01:04:04.320 --> 01:04:06.780
We isolate portions of a circuit

01:04:06.780 --> 01:04:11.680
where we see high wind
conditions, risky situations.

01:04:11.680 --> 01:04:14.480
And so we had to
understand the PSPS risk

01:04:14.480 --> 01:04:17.500
from a segment standpoint,
and be able to compare it

01:04:17.500 --> 01:04:20.270
to the fire risk at a
segment standpoint.

01:04:20.270 --> 01:04:22.620
Now, one point I'll make here is just

01:04:22.620 --> 01:04:26.570
because we created
this layer of granularity.

01:04:26.570 --> 01:04:28.520
Doesn't mean we're
going to stop doing things

01:04:28.520 --> 01:04:31.710
on the asset level or the system level.

01:04:31.710 --> 01:04:34.050
All of these layers
feed into each other.

01:04:34.050 --> 01:04:38.070
We actually use the asset
level information to inform

01:04:38.070 --> 01:04:41.290
how we come up with the
assessment for the segment levels.

01:04:41.290 --> 01:04:44.210
And that's where we came
up with WINGS in 2020

01:04:44.210 --> 01:04:47.020
to specifically do
this type of analysis.

01:04:47.020 --> 01:04:48.380
The one thing I'll mention

01:04:48.380 --> 01:04:51.260
about WINGS is that
it's a modular model,

01:04:51.260 --> 01:04:52.920
meaning that it can take inputs

01:04:52.920 --> 01:04:55.210
from various sources and models,

01:04:55.210 --> 01:04:58.900
and we can continue to improve
those modeling approaches

01:04:58.900 --> 01:05:00.550
outside of it and feed into it.

01:05:00.550 --> 01:05:01.994
So it's really flexible.

01:05:01.994 --> 01:05:05.510
It's not, you know, set
in stone and it's can,

01:05:05.510 --> 01:05:07.810
it can take what we've
done from the asset level,

01:05:07.810 --> 01:05:09.530
and it can take what we're going to do

01:05:09.530 --> 01:05:11.460
with independent studies as we continue

01:05:11.460 --> 01:05:15.130
to evolve our modeling capabilities.

01:05:15.130 --> 01:05:16.323
Next slide please.

01:05:20.080 --> 01:05:22.813
Okay, so with WINGS,

01:05:22.813 --> 01:05:26.730
what it really leads to
is a shift in strategies

01:05:26.730 --> 01:05:29.580
for how we want to
mitigate our segments.

01:05:29.580 --> 01:05:31.700
Because as I mentioned,

01:05:31.700 --> 01:05:35.840
PSPS is, is a risk that
we want to account for

01:05:35.840 --> 01:05:37.870
with the development of WINGS.

01:05:37.870 --> 01:05:40.800
And as I mentioned previously,

01:05:40.800 --> 01:05:43.970
looking at things from an
asset standpoint is good,

01:05:43.970 --> 01:05:48.040
but in the context of PSPS,
doesn't help us a whole lot.

01:05:48.040 --> 01:05:50.120
And that's why we created
WINGS to really shift

01:05:50.120 --> 01:05:52.110
from an asset level approach

01:05:52.110 --> 01:05:55.640
to a comprehensive
segment level approach.

01:05:55.640 --> 01:05:57.610
And what we're
showing on the left here is

01:05:57.610 --> 01:05:59.860
a visual to give you a bit
more of an understanding

01:05:59.860 --> 01:06:01.550
of what that really means.

01:06:01.550 --> 01:06:06.260
So the first graphic on the
left is a geospatial mapping

01:06:06.260 --> 01:06:09.560
for one segment prior to using WINGS.

01:06:09.560 --> 01:06:11.470
So you'll see this one segment has

01:06:11.470 --> 01:06:14.790
a mix of wood poles and steel poles.

01:06:14.790 --> 01:06:17.230
And so in extreme situations,

01:06:17.230 --> 01:06:19.850
when the fire risk is heightened,

01:06:19.850 --> 01:06:22.180
we err on the conservative side,

01:06:22.180 --> 01:06:25.140
we know the segment hasn't
been completely hardened,

01:06:25.140 --> 01:06:26.820
so we may not feel comfortable enough

01:06:26.820 --> 01:06:29.980
to operate it under
high weather conditions.

01:06:29.980 --> 01:06:31.070
On the right-hand side,

01:06:31.070 --> 01:06:32.430
we're transitioning towards

01:06:32.430 --> 01:06:34.750
this whole segment solution approach

01:06:34.750 --> 01:06:37.140
so that we can account for things

01:06:37.140 --> 01:06:40.002
like objects flying into the line,

01:06:40.002 --> 01:06:42.840
really mitigating the
entire segment based

01:06:42.840 --> 01:06:44.653
on the situation of that segment.

01:06:45.540 --> 01:06:46.810
Again, as I mentioned,

01:06:46.810 --> 01:06:48.940
our asset level analysis really feeds

01:06:48.940 --> 01:06:51.280
into this and informs it.

01:06:51.280 --> 01:06:53.640
It doesn't take the, you know, the,

01:06:53.640 --> 01:06:54.840
the segment level analysis

01:06:54.840 --> 01:06:56.950
doesn't get rid of that granularity.

01:06:56.950 --> 01:06:59.100
And that's what I'm
highlighting on the right

01:06:59.100 --> 01:07:04.100
where I'm showing the
WRRM simulated asset analysis

01:07:04.480 --> 01:07:05.620
feeding into WINGS.

01:07:05.620 --> 01:07:08.940
So every poll on this chart essentially

01:07:08.940 --> 01:07:10.760
has a WRRM risk score.

01:07:10.760 --> 01:07:13.720
And we use the
components of that risk score

01:07:13.720 --> 01:07:17.950
to really aggregate the
assessment at a segment level.

01:07:17.950 --> 01:07:19.680
Now, quick facts about WINGS

01:07:20.709 --> 01:07:21.542
and this will continue to evolve,

01:07:21.542 --> 01:07:23.010
but where it stands today is we have

01:07:23.010 --> 01:07:27.740
over 600 distribution segments
being assessed in WINGS,

01:07:27.740 --> 01:07:32.280
comprised of 90,000 poles,
poles across the HFTD

01:07:32.280 --> 01:07:34.980
and a little bit outside the HFTD with

01:07:34.980 --> 01:07:38.340
around 3,600 miles of
distribution overhead.

01:07:38.340 --> 01:07:42.460
And the average length of a
segment is around six miles.

01:07:42.460 --> 01:07:44.090
The benefits of WINGS, as I mentioned,

01:07:44.090 --> 01:07:46.580
is it helps us reduce the PSPS impact

01:07:46.580 --> 01:07:49.090
by identifying whole segment solutions.

01:07:49.090 --> 01:07:52.590
It builds on prior models
and integrates their outputs,

01:07:52.590 --> 01:07:54.960
and it utilizes the same MAVF

01:07:54.960 --> 01:07:56.610
or the risk quantification framework

01:07:56.610 --> 01:07:59.990
that Mason walked us
through that we used for RAMP.

01:07:59.990 --> 01:08:01.113
and the WMP.

01:08:02.120 --> 01:08:03.433
Next slide, please.

01:08:06.450 --> 01:08:11.400
So what WINGS helps us
answer is really three key questions.

01:08:11.400 --> 01:08:14.160
It helps us understand
the current risk level today,

01:08:14.160 --> 01:08:16.188
the baseline risk for every segment,

01:08:16.188 --> 01:08:20.340
it helps us do this alternatives
analysis, using the risk,

01:08:20.340 --> 01:08:23.190
spend efficiency to
calculate risk scores

01:08:23.190 --> 01:08:24.950
for different types of mitigations.

01:08:24.950 --> 01:08:27.620
And as of right now in 2020,

01:08:27.620 --> 01:08:31.300
we used it to look at
what a segment, how,

01:08:31.300 --> 01:08:34.170
how the benefit could look like
if we underground a segment,

01:08:34.170 --> 01:08:36.350
if we applied Covered Conductor,

01:08:36.350 --> 01:08:38.271
if we gave customers generators,

01:08:38.271 --> 01:08:41.943
or if we continued our traditional
bare conductor hardening

01:08:41.943 --> 01:08:46.343
with each alternative
risk spent efficiency score,

01:08:46.343 --> 01:08:50.603
and we're using that to inform
our approaches in the future.

01:08:52.480 --> 01:08:55.023
I'm hearing somebody in the background.

01:08:56.533 --> 01:08:58.280
<v Man>(muffled speaking).</v>

01:08:58.280 --> 01:09:00.893
Yeah, (indistinct), yeah.

01:09:03.530 --> 01:09:04.363
Thank you.

01:09:06.022 --> 01:09:07.750
And then the last question
that it helps us answer is

01:09:07.750 --> 01:09:09.780
really, it helps us to play
out different scenarios

01:09:09.780 --> 01:09:12.300
in a top-down fashion,
meaning we might have,

01:09:12.300 --> 01:09:15.210
SMEE's want to play
out a different scenario,

01:09:15.210 --> 01:09:16.980
and then we can go
back to the model and see

01:09:16.980 --> 01:09:19.465
what that scenario could look like.

01:09:19.465 --> 01:09:20.298
Scenarios could be, you know,

01:09:20.298 --> 01:09:23.586
significant hardening in
certain areas of the territory,

01:09:23.586 --> 01:09:27.838
limited hardening, focusing
on one type of mitigation,

01:09:27.838 --> 01:09:29.540
giving customers generators.

01:09:29.540 --> 01:09:31.610
And we're able to go back into the model

01:09:31.610 --> 01:09:33.230
and actually quantify the cost

01:09:33.230 --> 01:09:35.960
and the benefit of
these different portfolios

01:09:35.960 --> 01:09:38.534
and, and see where we get the most,

01:09:38.534 --> 01:09:41.630
the biggest bang for buck essentially.

01:09:41.630 --> 01:09:42.783
Next slide please.

01:09:45.110 --> 01:09:47.760
All right, so inputs and
outputs of the model.

01:09:47.760 --> 01:09:52.290
So as many of my colleagues
today in the prior sessions

01:09:52.290 --> 01:09:53.870
talked about risk is comprised

01:09:53.870 --> 01:09:55.890
of likelihood and consequence.

01:09:55.890 --> 01:09:58.280
And WINGS helps us
understand both the fire risk

01:09:58.280 --> 01:09:59.860
and the PSPS risks.

01:09:59.860 --> 01:10:02.840
For each of those, we
have different data points

01:10:02.840 --> 01:10:05.840
to quantify the likelihood
and the consequence.

01:10:05.840 --> 01:10:09.110
For the wildfire risk,
we're really tailoring

01:10:09.110 --> 01:10:12.110
the risk assessment
to the unique conditions

01:10:12.110 --> 01:10:14.390
and the characteristics of the segment.

01:10:14.390 --> 01:10:16.280
So we're looking at historic conditions.

01:10:16.280 --> 01:10:17.560
We're looking at wind speeds

01:10:17.560 --> 01:10:20.170
because we have weather stations mapped

01:10:20.170 --> 01:10:24.150
to skated to devices or
segments in the, in our situation.

01:10:24.150 --> 01:10:27.080
We have an understanding
of the length of the tree strikes.

01:10:27.080 --> 01:10:29.310
So out of the entire
length of the segment,

01:10:29.310 --> 01:10:33.130
how much of it is really
at more risk of hitting a tree

01:10:33.130 --> 01:10:34.950
or being struck by a tree?

01:10:34.950 --> 01:10:36.610
We know the hardening status,

01:10:36.610 --> 01:10:38.310
'cause we've done a
lot of hardening work

01:10:38.310 --> 01:10:39.800
that really lowers the risk,

01:10:39.800 --> 01:10:42.470
but some segments are not
that significantly hardened

01:10:42.470 --> 01:10:45.773
because we've been focusing
on specific assets at risk.

01:10:45.773 --> 01:10:49.810
And the three last bullet
points under the likelihood

01:10:49.810 --> 01:10:53.890
for wildfire are three
new items that we added

01:10:53.890 --> 01:10:55.030
towards the end of last year,

01:10:55.030 --> 01:10:57.620
which is understanding
the vegetation density

01:10:57.620 --> 01:11:00.440
on that segment, taking into account

01:11:00.440 --> 01:11:03.020
the circuit health index,

01:11:03.020 --> 01:11:05.170
which gives us a little
bit more information

01:11:05.170 --> 01:11:07.760
about the specific
assets in that segment,

01:11:07.760 --> 01:11:09.760
as well as the conductor age.

01:11:09.760 --> 01:11:13.010
And then from a consequence
standpoint, as I mentioned,

01:11:13.010 --> 01:11:15.480
we're building on what we've
done in the WRRM model.

01:11:15.480 --> 01:11:19.230
So we're using the WRRM
conditional impacts that tell us

01:11:19.230 --> 01:11:22.820
at every pole, what is the
potential consequence of a flyer,

01:11:22.820 --> 01:11:24.160
where to start there?

01:11:24.160 --> 01:11:27.350
So we took every poll on a
segment and we aggregated it

01:11:27.350 --> 01:11:28.720
for this assessment to come up

01:11:28.720 --> 01:11:31.560
with the overall
consequence of a fire risk

01:11:31.560 --> 01:11:34.520
if something were to
happen on that segment.

01:11:34.520 --> 01:11:36.080
From a PSPS standpoint,

01:11:36.080 --> 01:11:39.170
we're looking at the
annual red flag warning data.

01:11:39.170 --> 01:11:42.000
We're looking at historical
wind speed patterns.

01:11:42.000 --> 01:11:42.930
For every segment,

01:11:42.930 --> 01:11:46.390
we have a probability
of shutoff that is based

01:11:46.390 --> 01:11:49.730
on the unique conditions, as
I mentioned of each segment,

01:11:49.730 --> 01:11:51.791
whether it's the wind or the vegetation,

01:11:51.791 --> 01:11:53.731
the level of hardening.

01:11:53.731 --> 01:11:57.680
And then one of the things
that we added most recently is

01:11:57.680 --> 01:11:59.930
this concept of circuit connectivity,

01:11:59.930 --> 01:12:02.610
which was really complicated at first.

01:12:02.610 --> 01:12:05.700
When in our first iteration
of the WINGS model,

01:12:05.700 --> 01:12:09.040
we were looking at segments
in isolation of each other,

01:12:09.040 --> 01:12:11.960
and that resulted in really
suboptimal mitigations.

01:12:11.960 --> 01:12:15.260
When we looked at the outcomes
and we looked at the segments

01:12:15.260 --> 01:12:17.110
in the context of a circuit,

01:12:17.110 --> 01:12:20.360
we would have solutions that
were pointing us, for example,

01:12:20.360 --> 01:12:23.680
to underground the most
downstream part of a circuit

01:12:23.680 --> 01:12:25.385
without mitigating the upstream risk.

01:12:25.385 --> 01:12:27.360
Well, that's great for that segment.

01:12:27.360 --> 01:12:29.680
But if a shutoff happens upstream,

01:12:29.680 --> 01:12:32.420
the customers don't get the
benefit of that underground.

01:12:32.420 --> 01:12:36.590
So we've updated this so
that the model now actually

01:12:36.590 --> 01:12:41.100
will run a combination of
scenarios and mitigations

01:12:41.100 --> 01:12:43.770
for every segment in
a circuit and come up

01:12:43.770 --> 01:12:46.260
with the right mix of
solutions that maximizes

01:12:46.260 --> 01:12:48.190
the benefit for the customers

01:12:48.190 --> 01:12:51.260
and from a fire risk
reduction standpoint.

01:12:51.260 --> 01:12:54.530
For the consequence of
PSPS, it's pretty straightforward

01:12:54.530 --> 01:12:56.270
to some extent.

01:12:56.270 --> 01:12:58.540
We're looking at the number
of customers that could

01:12:58.540 --> 01:13:01.330
be impacted by a shutoff
in any given segment.

01:13:01.330 --> 01:13:03.160
And we're looking at
different customer types.

01:13:03.160 --> 01:13:05.630
This is something that
we're continuing to evolve,

01:13:05.630 --> 01:13:09.090
but our latest update
on it is we've dissected

01:13:09.090 --> 01:13:11.930
the types of customers
into three categories.

01:13:11.930 --> 01:13:14.280
The first category
is critical customers.

01:13:14.280 --> 01:13:17.929
This is our urgent and
essential customers, hospitals,

01:13:17.929 --> 01:13:22.760
fire stations, police stations,
communication towers.

01:13:22.760 --> 01:13:25.020
The second category is medical baseline.

01:13:25.020 --> 01:13:26.390
That's pretty self-explanatory.

01:13:26.390 --> 01:13:29.720
And the third category is a
catch-all for any customers

01:13:29.720 --> 01:13:31.690
that don't fall in the
first two categories.

01:13:31.690 --> 01:13:35.100
And we call that the
non-critical customers category.

01:13:35.100 --> 01:13:38.358
But that said, we are
continuing to refine this

01:13:38.358 --> 01:13:40.760
and we'll have more
granularity with with regard

01:13:40.760 --> 01:13:42.227
to the customer types.

01:13:42.227 --> 01:13:43.960
We're looking at divvying up

01:13:43.960 --> 01:13:46.370
the residential, commercial, industrial,

01:13:46.370 --> 01:13:49.670
we're looking at better understanding

01:13:49.670 --> 01:13:51.710
the AFN population impact.

01:13:51.710 --> 01:13:54.680
So this is a continuing work
in progress that we're going

01:13:54.680 --> 01:13:56.900
to update this year.

01:13:56.900 --> 01:13:57.970
The outputs of the model.

01:13:57.970 --> 01:13:59.320
This is a bit of an eye chart,

01:13:59.320 --> 01:14:01.010
but just to give you
an idea of what comes

01:14:01.010 --> 01:14:02.170
out of this model.

01:14:02.170 --> 01:14:04.280
We, using the WINGS model,

01:14:04.280 --> 01:14:08.090
we can look at the ranking
of segments based on risk.

01:14:08.090 --> 01:14:10.960
We can look at the ranking
based on risk, spend efficiency.

01:14:10.960 --> 01:14:13.840
That'll tell us where we
can start the work to get

01:14:13.840 --> 01:14:16.930
the most benefit out of our projects.

01:14:16.930 --> 01:14:20.010
We can look at the RSC
analysis, as I mentioned earlier,

01:14:20.010 --> 01:14:22.330
to understand the different
alternatives and the cost

01:14:22.330 --> 01:14:25.710
benefit of those and inform
our decision-making that way.

01:14:25.710 --> 01:14:28.130
And we can also look
at the portfolio analysis,

01:14:28.130 --> 01:14:32.270
which really aggregates the
outcomes from every segment,

01:14:32.270 --> 01:14:35.730
adds it all up and gives us
these curves that really tell us

01:14:35.730 --> 01:14:39.860
and help us understand
how good is the risk reduction

01:14:39.860 --> 01:14:41.630
on a per dollar basis.

01:14:41.630 --> 01:14:43.690
You'll see examples of portfolios

01:14:43.690 --> 01:14:45.230
that have diminishing returns,

01:14:45.230 --> 01:14:47.780
but it's just being able
to visualize it this way.

01:14:47.780 --> 01:14:51.373
That really helps guide
our strategies in the future.

01:14:52.380 --> 01:14:53.503
Next slide please.

01:14:57.310 --> 01:15:02.310
So some quick applications
of the WINGS model in 2020.

01:15:02.797 --> 01:15:06.610
We were able to pivot some
of our mitigation strategies

01:15:06.610 --> 01:15:11.610
in the 2020 WMP, meaning
the timeframe of the 2020 WMP,

01:15:11.943 --> 01:15:13.958
2020 through 2022,

01:15:13.958 --> 01:15:16.780
but really pivoting and
flight work is not that easy.

01:15:16.780 --> 01:15:21.170
It takes about 12 to 18
months to go through a project

01:15:21.170 --> 01:15:23.370
from scoping to design and construction.

01:15:23.370 --> 01:15:26.610
And so really a lot of the work
that we're doing with WINGS

01:15:26.610 --> 01:15:30.120
is not going to be
implemented until later in 2022,

01:15:30.120 --> 01:15:34.000
to some extent, but
mostly in 2023 and beyond.

01:15:34.000 --> 01:15:36.420
That said, we were able to pivot some of

01:15:36.420 --> 01:15:39.810
the work depending on where
it was in the design phase.

01:15:39.810 --> 01:15:42.630
So we're showing an example
of an output from WINGS

01:15:42.630 --> 01:15:44.490
for one circuit on the left side,

01:15:44.490 --> 01:15:46.390
that's circuit 448,

01:15:46.390 --> 01:15:49.320
and all of the segments
within that circuit.

01:15:49.320 --> 01:15:51.900
And we looked at the
different alternatives.

01:15:51.900 --> 01:15:55.700
So Covered Conductor, that's
the CC risk spent efficiency.

01:15:55.700 --> 01:15:57.490
We looked at undergrounding and that's

01:15:57.490 --> 01:15:59.810
the risk spent efficiency
for undergrounding.

01:15:59.810 --> 01:16:02.130
We'll look at continuing
traditional hardening and there's

01:16:02.130 --> 01:16:04.170
the risks beneficent see for that.

01:16:04.170 --> 01:16:06.430
And then the recommended
mitigation is where we landed.

01:16:06.430 --> 01:16:10.010
And the reason for deviating
from the highest RSE.

01:16:10.010 --> 01:16:11.830
Generally speaking, the higher RSE,

01:16:11.830 --> 01:16:13.560
the better is the project.

01:16:13.560 --> 01:16:16.670
In some cases, as you'll
see here for some segments,

01:16:16.670 --> 01:16:18.450
we weren't able to pivot,

01:16:18.450 --> 01:16:20.817
but we wanted to validate
that we were still doing

01:16:20.817 --> 01:16:24.240
good projects in terms
of their risk scores.

01:16:24.240 --> 01:16:25.580
And that was really validated

01:16:25.580 --> 01:16:28.610
by the risks spent
inefficiencies that you see.

01:16:28.610 --> 01:16:31.530
However, for some, for
about three of these segments

01:16:31.530 --> 01:16:33.310
on this circuit, we were able to pivot

01:16:33.310 --> 01:16:36.470
because we weren't that
far in the design phase,

01:16:36.470 --> 01:16:37.990
and we're actually now designing them

01:16:37.990 --> 01:16:40.530
for the implementation
of Covered Conductor

01:16:40.530 --> 01:16:43.530
based on being the
highest risk spent efficiency

01:16:43.530 --> 01:16:45.390
for these segments.

01:16:45.390 --> 01:16:46.870
On the right hand side,

01:16:46.870 --> 01:16:51.870
we also did this validation
just to kind of, you know,

01:16:52.070 --> 01:16:53.480
WINGS is an improved model,

01:16:53.480 --> 01:16:55.970
it has a lot more
elements than what we use

01:16:55.970 --> 01:16:59.280
to look at in WRRM, but
it was really comforting

01:16:59.280 --> 01:17:01.820
to see that the
highest risk circuits are

01:17:01.820 --> 01:17:04.490
the same ones that
we had been targeting.

01:17:04.490 --> 01:17:05.840
But as I mentioned with WINGS,

01:17:05.840 --> 01:17:09.010
we're going to be gaining more
benefit because we're looking

01:17:09.010 --> 01:17:11.840
at the combination of PSPS and fire risk

01:17:11.840 --> 01:17:14.483
and we're using more
up-to-date information.

01:17:15.440 --> 01:17:16.823
Next slide please.

01:17:20.460 --> 01:17:23.050
So just some closing thoughts for today.

01:17:23.050 --> 01:17:26.949
We based on the discussion
today and our timelines,

01:17:26.949 --> 01:17:29.250
we have a history of using risk models

01:17:29.250 --> 01:17:31.770
to inform our mitigation efforts.

01:17:31.770 --> 01:17:33.990
We think risk modeling should continue

01:17:33.990 --> 01:17:36.450
to evolve based on emerging challenges.

01:17:36.450 --> 01:17:38.680
And there needs to be
a flexibility to determine

01:17:38.680 --> 01:17:41.430
the appropriate models
to use for various fun trips.

01:17:41.430 --> 01:17:44.010
It's really not a one size fits all.

01:17:44.010 --> 01:17:47.700
SMI input remains crucial
to making the final decision.

01:17:47.700 --> 01:17:50.860
There are things such
as feasibility analysis,

01:17:50.860 --> 01:17:53.370
land permitting, and other constraints

01:17:53.370 --> 01:17:55.780
that may lead us to
select different mitigations

01:17:55.780 --> 01:17:58.470
from what the model may point to.

01:17:58.470 --> 01:17:59.303
And as I mentioned,

01:17:59.303 --> 01:18:01.580
it takes time to transition
to new frameworks

01:18:01.580 --> 01:18:05.130
and shift operations and
decision-making to new standards.

01:18:05.130 --> 01:18:06.920
Our next steps is
we're going to continue

01:18:06.920 --> 01:18:09.660
to update WINGS in this year.

01:18:09.660 --> 01:18:11.580
We're going to continue
to refresh our assessments

01:18:11.580 --> 01:18:14.310
and continue to inform
the grid hardening in 2023

01:18:14.310 --> 01:18:16.700
and beyond, using this WINGS model,

01:18:16.700 --> 01:18:20.120
we're going to use WINGS
to explore the potential

01:18:20.120 --> 01:18:23.150
application of evaluating
vegetation management

01:18:23.150 --> 01:18:25.150
on a segment-by-segment basis.

01:18:25.150 --> 01:18:27.508
And we'll see where that takes us.

01:18:27.508 --> 01:18:28.700
And there will be additional
enhancements that we're going

01:18:28.700 --> 01:18:30.840
to identify this year
and develop a roadmap

01:18:30.840 --> 01:18:32.207
to continue to improve it.

01:18:32.207 --> 01:18:34.740
And as I mentioned,
WINGS is really going

01:18:34.740 --> 01:18:39.054
to primarily informed the scope
of work in 2023 and beyond.

01:18:39.054 --> 01:18:42.180
And with that, I will
end my presentation.

01:18:42.180 --> 01:18:43.013
Thank you.

01:18:48.930 --> 01:18:50.933
<v ->Thank you for
all the presenters.</v>

01:18:50.933 --> 01:18:55.650
So now we are going
to move into a break.

01:18:55.650 --> 01:19:00.040
So we are going to resume the
question and answer segment

01:19:00.040 --> 01:19:04.940
of, of this here starting at 11:15.

01:19:04.940 --> 01:19:08.450
So we will all be back here at 11:15.

01:19:08.450 --> 01:19:10.480
I will also post that in chat.

01:19:10.480 --> 01:19:12.760
And then that's when we'll
receive the question and answers.

01:19:12.760 --> 01:19:14.660
Thank you to all the presenters again.

01:21:49.267 --> 01:21:53.540
All right, everyone, my
clock is reading 11:15.

01:21:53.540 --> 01:21:56.650
So let's go ahead and get started

01:21:56.650 --> 01:21:59.863
with the question and
answers section of,

01:22:00.810 --> 01:22:02.400
of the risk assessment mapping

01:22:02.400 --> 01:22:05.353
and resource allocation
methodology portion.

01:22:07.650 --> 01:22:10.460
All right, so just a really quick note

01:22:10.460 --> 01:22:12.140
as we start the question and answer,

01:22:12.140 --> 01:22:14.280
there's going to be a
lot of active discussions.

01:22:14.280 --> 01:22:17.030
So participants and
people in the audience,

01:22:17.030 --> 01:22:19.150
please be aware of your mute button,

01:22:19.150 --> 01:22:20.940
just so we don't have
a lot of feedback going

01:22:20.940 --> 01:22:22.123
into the conversations.

01:22:23.410 --> 01:22:26.060
Joining us with the enter NS

01:22:26.060 --> 01:22:27.900
and D question and answers section,

01:22:27.900 --> 01:22:32.341
we have a few stake holder parties here.

01:22:32.341 --> 01:22:36.260
The representatives we have
representatives from the URN,

01:22:36.260 --> 01:22:39.580
which is the Utility Reform Network.

01:22:39.580 --> 01:22:41.630
We also have representatives

01:22:41.630 --> 01:22:43.800
from Mussey Grade Road Alliance.

01:22:43.800 --> 01:22:47.670
We also have representatives
from Bring Power Institute.

01:22:47.670 --> 01:22:50.687
And when we also
have Mr. Abrams and the,

01:22:50.687 --> 01:22:52.450
and the panelists as well.

01:22:52.450 --> 01:22:55.280
So stakeholder participants,

01:22:55.280 --> 01:22:57.970
what we'll do is before
you ask your question,

01:22:57.970 --> 01:22:59.938
go ahead and say your name and what,

01:22:59.938 --> 01:23:03.400
and what party you're associated with,

01:23:03.400 --> 01:23:06.893
and then we will, we will
have the question started.

01:23:09.130 --> 01:23:14.040
And then joining me as well
is going to be Melissa Semcer.

01:23:14.040 --> 01:23:17.420
She's going to be moderating
the chat and let us know

01:23:17.420 --> 01:23:20.373
the questions that have been
coming through through chat.

01:23:23.037 --> 01:23:26.170
Cool, so let's get started here.

01:23:26.170 --> 01:23:29.270
The I'll go ahead with the
first question and then I will go

01:23:29.270 --> 01:23:34.240
ahead and let the analysts
know who is, who is the next.

01:23:34.240 --> 01:23:36.240
The first question is coming from WSD,

01:23:36.240 --> 01:23:39.630
and this is just to set the
stage with this next question,

01:23:39.630 --> 01:23:41.640
question and answers section.

01:23:41.640 --> 01:23:46.640
We've all seeing an overview
of the risk models we wanted

01:23:48.100 --> 01:23:50.760
to just have the utilities highlight

01:23:50.760 --> 01:23:53.100
the specific changes that have been made

01:23:53.100 --> 01:23:58.100
since the 2020 WMP,
and how those updates

01:23:58.190 --> 01:24:02.510
will results in improved
ability to model ignition, risk,

01:24:02.510 --> 01:24:03.903
and wildfire spread?

01:24:04.930 --> 01:24:06.950
So it's a two-part question,

01:24:06.950 --> 01:24:10.552
the subsequent changes
and also how those changes

01:24:10.552 --> 01:24:14.308
will improve in the, the
ability to model ignitions risk

01:24:14.308 --> 01:24:15.141
and wildfire spread?

01:24:15.141 --> 01:24:17.490
And then the order
that will go is PG and E,

01:24:17.490 --> 01:24:18.363
SEN, STG and E.

01:24:26.530 --> 01:24:28.200
<v ->Hi, thank you
for that question.</v>

01:24:28.200 --> 01:24:29.536
I think that really gets to the crux

01:24:29.536 --> 01:24:31.927
of why we're meeting today.

01:24:31.927 --> 01:24:36.752
From PG and E's perspective,
the initial risk models

01:24:36.752 --> 01:24:39.640
were built in the late 2018, 2019.

01:24:39.640 --> 01:24:42.950
And we have changed
absolutely everything

01:24:42.950 --> 01:24:46.460
in those models where it, since the,

01:24:46.460 --> 01:24:50.787
during the 2020 period to
be in production for 2021.

01:24:50.787 --> 01:24:53.040
In my presentation, I discussed it

01:24:53.040 --> 01:24:55.570
and we, I think we did
quite a good job of discussing

01:24:55.570 --> 01:24:59.700
that in our Fire Mitigation
Plan, it's in section four,

01:24:59.700 --> 01:25:02.690
I commented the other utilities as well.

01:25:02.690 --> 01:25:05.457
The main things that we've
done is that we changed out

01:25:05.457 --> 01:25:08.840
the initial probability component and,

01:25:08.840 --> 01:25:12.193
and we've utilized this
maximum entropy approach using

01:25:12.193 --> 01:25:15.896
a machine-learning type analysis,

01:25:15.896 --> 01:25:18.470
a lot more data that
went into it this year.

01:25:18.470 --> 01:25:23.470
We used the 2018 to
20, sorry, 2015 to 2018

01:25:23.540 --> 01:25:25.890
CPUSA ignition dataset

01:25:25.890 --> 01:25:29.640
as the, as the, as the learning module.

01:25:29.640 --> 01:25:32.530
And then the treat that
the testing component of it,

01:25:32.530 --> 01:25:35.159
we use the 2019 ignitions.

01:25:35.159 --> 01:25:37.930
So we're predicting using
one set and then testing it

01:25:37.930 --> 01:25:40.180
against reality using the other.

01:25:40.180 --> 01:25:41.900
What does that allow us to do?

01:25:41.900 --> 01:25:43.850
We've got bigger (indistinct) approved.

01:25:45.028 --> 01:25:47.560
Our focus is on vegetation
and on conductor

01:25:47.560 --> 01:25:49.490
for the two main failure modes.

01:25:49.490 --> 01:25:51.088
I did see a question on that,

01:25:51.088 --> 01:25:52.240
and I think we'll
probably get to that one

01:25:52.240 --> 01:25:53.770
a little bit later.

01:25:53.770 --> 01:25:55.480
What this modeling approach allows us

01:25:55.480 --> 01:25:57.810
to do is make a better,

01:25:57.810 --> 01:26:00.820
accurate prediction of
where and when such

01:26:00.820 --> 01:26:04.120
an ignition may occur
and then us to pull

01:26:04.120 --> 01:26:06.370
in the various co-variates together

01:26:06.370 --> 01:26:11.023
and have a look at was, eh,
in, in, in, in a mixed setting.

01:26:13.410 --> 01:26:16.750
The second half of our model
that changed was that movement

01:26:16.750 --> 01:26:21.130
from the Reax fire propagation
and consequence module

01:26:21.130 --> 01:26:23.680
to the Technosylva Fire Propagation

01:26:23.680 --> 01:26:25.234
and Consequence Module.

01:26:25.234 --> 01:26:27.495
And there's a lot of
changes in that itself.

01:26:27.495 --> 01:26:30.800
Technosylva sits on a
more updated platform

01:26:30.800 --> 01:26:32.160
than the Reax Model did.

01:26:32.160 --> 01:26:33.886
I'm not saying it's better,

01:26:33.886 --> 01:26:34.910
I'm just saying that it's different.

01:26:34.910 --> 01:26:39.800
Reax was constructed using
a 2014 LANDFIRE dataset,

01:26:39.800 --> 01:26:43.000
which is the ground fuels from 2014.

01:26:43.000 --> 01:26:46.230
But those images were
actually from like 2011 or 2012,

01:26:46.230 --> 01:26:47.800
so slightly older,

01:26:47.800 --> 01:26:52.680
Technosylva sits upon a
2016 LANDFIRE dataset

01:26:52.680 --> 01:26:56.420
and has been updated
to include all disturbances

01:26:56.420 --> 01:26:57.630
through 2020.

01:26:57.630 --> 01:26:58.750
So when I say disturbances,

01:26:58.750 --> 01:27:01.823
I mean fires so, updates
to the fire module.

01:27:02.860 --> 01:27:07.860
The building structure, and
the population data insight,

01:27:08.530 --> 01:27:12.247
Technosylva is an updated layer to Reax.

01:27:12.247 --> 01:27:14.750
Technosylva is using
a 2018 Microsoft update

01:27:15.640 --> 01:27:19.160
Reax to engineering,
use the 2010 Census data.

01:27:19.160 --> 01:27:21.260
So again, we're
seeing (indistinct) there,

01:27:22.691 --> 01:27:24.329
so when we put these two together,

01:27:24.329 --> 01:27:26.050
we're seeing a lot of
changes between our model.

01:27:26.050 --> 01:27:31.050
The third part was CG and E
endeavored in 2019 to use it,

01:27:32.590 --> 01:27:34.800
the version of it regress model.

01:27:34.800 --> 01:27:37.003
That was included in it's 2018

01:27:38.804 --> 01:27:41.670
and 2020 Wildfire
Mitigation Plans to prioritize.

01:27:41.670 --> 01:27:44.943
It is not something
where you for the 2021,

01:27:44.943 --> 01:27:47.910
it's something that we'd like
to develop in partnership with

01:27:47.910 --> 01:27:52.910
the WSD and the other utilities
as we go forward in 2021.

01:27:53.250 --> 01:27:55.660
Now coming back to key points,

01:27:55.660 --> 01:27:59.800
we changed out the probability
model from the components of

01:27:59.800 --> 01:28:01.960
conductor and the vegetation.

01:28:01.960 --> 01:28:04.010
And we changed that
the consequence model

01:28:04.955 --> 01:28:06.710
for an updated dataset.

01:28:06.710 --> 01:28:08.260
And we also changed the algorithm.

01:28:08.260 --> 01:28:11.130
So everything in PG and
E's model has changed,

01:28:11.130 --> 01:28:12.840
we are seeing differences.

01:28:12.840 --> 01:28:17.540
Those differences are mostly
attributed to the fuels layers

01:28:17.540 --> 01:28:21.880
with regards to what we
call surface fuels, ladder fuels,

01:28:21.880 --> 01:28:24.670
then Crown fuels, Crown
fuels over the tops of the trees,

01:28:24.670 --> 01:28:26.450
which have the highest heat rate.

01:28:26.450 --> 01:28:29.731
So we saw a lot of progression
of change attributed to that.

01:28:29.731 --> 01:28:33.370
What it's allowing us to
do is it's allowing us to focus

01:28:33.370 --> 01:28:35.760
on areas where we
would expect an ignition

01:28:35.760 --> 01:28:39.370
to the curve based on the
attributes of the environment

01:28:39.370 --> 01:28:43.150
and the asset, as well as forecasting,

01:28:43.150 --> 01:28:46.530
where that fire would go
based on surface fuels,

01:28:46.530 --> 01:28:49.413
moving to ladder fuels,
moving to Crown fuels.

01:28:53.890 --> 01:28:56.940
<v ->So for, for STE, I won't
try and repeat everything</v>

01:28:56.940 --> 01:28:58.540
that Paul said, because
some of the changes

01:28:58.540 --> 01:28:59.423
are very similar.

01:29:00.280 --> 01:29:01.170
Our major changes,

01:29:01.170 --> 01:29:03.588
we're moving from Reax to Technosylva

01:29:03.588 --> 01:29:04.970
and it has the same benefits that,

01:29:04.970 --> 01:29:06.390
that Paul mentioned.

01:29:06.390 --> 01:29:09.050
We were also able to, a big change

01:29:09.050 --> 01:29:12.580
that we made was in our 2020 WMP,

01:29:12.580 --> 01:29:16.280
we did all of our RSC
calculations on our system level.

01:29:16.280 --> 01:29:18.110
Basically, there was one RSE calculation

01:29:18.110 --> 01:29:19.193
for each mitigation.

01:29:20.329 --> 01:29:21.190
This year, we're able
to get all the way down

01:29:21.190 --> 01:29:25.557
to a much more granular
set of RSC's as well.

01:29:25.557 --> 01:29:27.160
And what that allowed us to do from

01:29:27.160 --> 01:29:31.020
an operational perspective
is to sort of reorder

01:29:31.020 --> 01:29:33.130
the risk methodology to, to see

01:29:33.130 --> 01:29:36.728
where each segment (indistinct)

01:29:36.728 --> 01:29:39.290
and what that does is gives
us a better way targeting

01:29:39.290 --> 01:29:41.880
our mitigation specific segments
that have the highest risk

01:29:41.880 --> 01:29:43.750
based on the new methodology.

01:29:43.750 --> 01:29:46.220
And the last thing is, as I
mentioned in my presentation

01:29:46.220 --> 01:29:48.393
is we've created the PSPS risk stack,

01:29:49.240 --> 01:29:51.760
which is brand new
from the 2020 didn't exist

01:29:51.760 --> 01:29:54.413
in the 2020 (indistinct)
Mitigation Plan.

01:29:55.380 --> 01:29:58.940
And that, that gives us
more visibility to where the,

01:29:58.940 --> 01:30:02.940
where the PSPS risk exists on our system

01:30:02.940 --> 01:30:05.140
in terms of impacts to customers.

01:30:05.140 --> 01:30:06.550
And one thing I neglected to mention

01:30:06.550 --> 01:30:09.950
during my presentation
is part of that risk stack,

01:30:09.950 --> 01:30:13.280
we've created an access
and functional needs

01:30:13.280 --> 01:30:16.713
and a critical infrastructure adder

01:30:16.713 --> 01:30:19.260
that we use in a formula, which is,

01:30:19.260 --> 01:30:22.170
which enables us to
identify certain circuits

01:30:22.170 --> 01:30:25.680
and have have higher
impact to those populations,

01:30:25.680 --> 01:30:28.900
and it elevates those circuits
on the PSPS risk stack.

01:30:28.900 --> 01:30:33.058
So there's several, we
made several major changes

01:30:33.058 --> 01:30:34.993
that have a lot of
look at risk differently.

01:30:38.240 --> 01:30:40.251
<v ->And for SDG and E, I'll
highlight three key changes</v>

01:30:40.251 --> 01:30:44.301
that took place in 2020.

01:30:44.301 --> 01:30:47.120
The first one is the movement
from an asset level assessment

01:30:47.120 --> 01:30:48.320
to a second level assessment.

01:30:48.320 --> 01:30:49.780
As I mentioned earlier,

01:30:49.780 --> 01:30:51.700
and a big part of that
is taking into account

01:30:51.700 --> 01:30:54.910
the PSPS risks so that we
can hit two birds with one stone,

01:30:54.910 --> 01:30:57.380
for lack of a better explanation,

01:30:57.380 --> 01:30:59.610
but it helps us really
optimize our mitigations

01:30:59.610 --> 01:31:01.710
to reduce both risks.

01:31:01.710 --> 01:31:04.810
The second thing is we improve
the inputs to the likelihood.

01:31:04.810 --> 01:31:08.360
So we're WRRM was really
focused on likelihood assets

01:31:08.360 --> 01:31:11.250
failing, WINGS really takes into account

01:31:11.250 --> 01:31:14.520
a lot more data points
to look at the likelihood

01:31:14.520 --> 01:31:17.430
of ignitions from vegetation,
the wind conditions.

01:31:17.430 --> 01:31:21.340
And one of the biggest things
we also improved in 2020 is

01:31:21.340 --> 01:31:25.240
we went back and conducted
efficacy studies on our grid,

01:31:25.240 --> 01:31:28.200
hardening efforts to
date actually incorporated

01:31:28.200 --> 01:31:31.130
those estimates in our
analysis and WINGS

01:31:31.130 --> 01:31:35.380
to determine the effectiveness
or estimate, better estimate

01:31:35.380 --> 01:31:37.420
the effectiveness of mitigation.

01:31:37.420 --> 01:31:38.890
And then the last thing is really using

01:31:38.890 --> 01:31:42.190
an updated multi
attribute value framework.

01:31:42.190 --> 01:31:44.590
That's the latest implementation of

01:31:44.590 --> 01:31:47.710
the risk quantification
framework that Mason described.

01:31:47.710 --> 01:31:50.054
And in 2020, the work will continue.

01:31:50.054 --> 01:31:51.560
We're continuing to update it.

01:31:51.560 --> 01:31:53.700
We're continuing,
continuing to analyze the risk.

01:31:53.700 --> 01:31:55.590
And as new information comes in,

01:31:55.590 --> 01:31:58.283
we'll be able to better
refine that model.

01:32:02.440 --> 01:32:03.840
<v ->Great, thank you so much.</v>

01:32:04.930 --> 01:32:06.280
And then I did want
to also say that earlier

01:32:06.280 --> 01:32:07.700
when I was going
through the stakeholders,

01:32:07.700 --> 01:32:11.320
I did forget to include, we
also have a representative

01:32:11.320 --> 01:32:13.500
from Cal Advocates as well.

01:32:13.500 --> 01:32:15.990
So let, let's go through some,

01:32:15.990 --> 01:32:17.160
some of the other questions here.

01:32:17.160 --> 01:32:21.500
So the utility reform
reform network turn,

01:32:21.500 --> 01:32:23.660
go ahead and unmute,
introduce yourselves

01:32:23.660 --> 01:32:24.970
and then ask the question.

01:32:24.970 --> 01:32:26.120
Thank you.

01:32:26.120 --> 01:32:26.953
<v Katie>Great.</v>

01:32:27.800 --> 01:32:29.620
This is Katie Morsani from TURN.

01:32:29.620 --> 01:32:32.250
Before I get started, I'd like to raise

01:32:32.250 --> 01:32:34.500
the same port of order that Joseph did,

01:32:34.500 --> 01:32:36.450
I have a variety of questions.

01:32:36.450 --> 01:32:38.680
Should I run through all of them?

01:32:38.680 --> 01:32:40.823
Or just go one by one?

01:32:42.910 --> 01:32:44.110
Which would you prefer?

01:32:44.110 --> 01:32:46.570
<v ->Yeah, thank you
for that question.</v>

01:32:46.570 --> 01:32:50.070
So go for all the stakeholders.

01:32:50.070 --> 01:32:53.520
Let's keep the questions to
one at a time and then we'll go

01:32:53.520 --> 01:32:54.810
around in circle.

01:32:54.810 --> 01:32:57.340
Totally fine if your one
question has multi parts,

01:32:57.340 --> 01:33:00.070
but let's try to just
tackle it one at a time

01:33:00.070 --> 01:33:01.820
and then we'll make our way around.

01:33:02.980 --> 01:33:07.400
<v Katie>Okay, I, I have
a question I got to start</v>

01:33:07.400 --> 01:33:11.530
with PG and E and that is,

01:33:11.530 --> 01:33:15.440
this is a fairly simple
question, is my understanding

01:33:15.440 --> 01:33:17.750
correct that you're
using a different process

01:33:17.750 --> 01:33:22.030
for risk assessment
than we recently have

01:33:22.030 --> 01:33:24.103
been discussing in your RAMP filing?

01:33:31.260 --> 01:33:33.683
<v ->Is this for SDG
and E or all utilities?</v>

01:33:35.163 --> 01:33:37.080
<v Katie>For PG and E?</v>

01:33:38.958 --> 01:33:40.894
<v ->So the simple
answer to that is no</v>

01:33:40.894 --> 01:33:44.870
for the 2020 RAMP piling PG and E users

01:33:44.870 --> 01:33:47.380
on enterprise level risk model,

01:33:47.380 --> 01:33:49.597
which looks at risk at appropriate level

01:33:49.597 --> 01:33:51.733
to the highest level in the company.

01:33:52.948 --> 01:33:56.270
And we developed the multi
attribute value framework

01:33:56.270 --> 01:33:59.690
to be used at that level.

01:33:59.690 --> 01:34:03.480
For wildfire risk, we're
following that process,

01:34:03.480 --> 01:34:05.930
using the core and the lore,

01:34:05.930 --> 01:34:10.107
and we have the risk equals
probability times consequences,

01:34:10.107 --> 01:34:11.790
a very similar process.

01:34:11.790 --> 01:34:14.960
What we're doing at the
wildfire model is we can take this

01:34:14.960 --> 01:34:17.800
down to the circuit segment level.

01:34:17.800 --> 01:34:19.720
And then on the output side,

01:34:19.720 --> 01:34:22.870
we can use the outputs
that are either natural units

01:34:22.870 --> 01:34:24.850
that come from Technosylva,

01:34:24.850 --> 01:34:28.050
or we can convert
those back to our NABF,

01:34:28.050 --> 01:34:30.773
which is aligned with
our enterprise risk model.

01:34:31.778 --> 01:34:33.263
Did that answer your question, Katie?

01:34:40.930 --> 01:34:43.110
<v Katie>So you, okay.</v>

01:34:43.110 --> 01:34:45.500
Sorry, I'm I'm thinking and
talking at the same time,

01:34:45.500 --> 01:34:46.853
which is always dangerous.

01:34:49.380 --> 01:34:53.050
So you aren't using the same
model because in the RAMP you

01:34:53.050 --> 01:34:56.790
were looking at an enterprise
level and here in wildfire,

01:34:56.790 --> 01:34:58.993
you're looking at any
more granular level?

01:35:00.380 --> 01:35:01.230
<v ->That's correct.</v>

01:35:02.220 --> 01:35:05.560
At the RAMP level it's it's enterprise.

01:35:05.560 --> 01:35:08.130
So we're looking at
wildfire as the risk.

01:35:08.130 --> 01:35:11.590
There's a number of
drivers feeding a risk event

01:35:11.590 --> 01:35:13.460
with a number of potential outcomes.

01:35:13.460 --> 01:35:15.590
And then we're summing
all of those together

01:35:15.590 --> 01:35:18.350
to get our total MABS score.

01:35:18.350 --> 01:35:20.370
And that is for the risk.

01:35:20.370 --> 01:35:24.190
What we're doing in our
Wildfire Mitigation Plan

01:35:24.190 --> 01:35:28.010
using our Wildfire Risk
Model is to take that risk event

01:35:28.010 --> 01:35:32.150
and break it down to
specific circuit segment levels.

01:35:32.150 --> 01:35:34.570
And let me define what
a circuit segment is.

01:35:34.570 --> 01:35:37.560
A circuit segment is as
a component or a part,

01:35:37.560 --> 01:35:39.500
a subset of a circuit.

01:35:39.500 --> 01:35:43.960
They range from about,
you know, 0.02 miles,

01:35:43.960 --> 01:35:46.870
to about 12 miles long in land.

01:35:46.870 --> 01:35:49.540
The average is about six miles long,

01:35:49.540 --> 01:35:51.870
and we can tend to be able to control

01:35:51.870 --> 01:35:54.410
the advice actualization devices.

01:35:54.410 --> 01:35:56.700
So when we're looking at wildfire risk

01:35:56.700 --> 01:35:58.490
in the Wildfire Mitigation Plan,

01:35:58.490 --> 01:36:01.463
we're looking at at a
circuit segment level,

01:36:02.312 --> 01:36:03.463
not an enterprise level.

01:36:07.010 --> 01:36:08.390
<v Katie>Okay, thank you.</v>

01:36:08.390 --> 01:36:10.210
I, I have other
questions, so I'll, I'll wait

01:36:10.210 --> 01:36:11.110
for my turn again.

01:36:15.520 --> 01:36:16.600
<v ->Thank you, Katie.</v>

01:36:16.600 --> 01:36:18.423
Next let's go with Lucy Grade.

01:36:20.020 --> 01:36:21.690
<v Joe>Hi, this is Joseph Mitchell</v>

01:36:21.690 --> 01:36:23.313
from Mussey Grid Road Alliance.

01:36:24.450 --> 01:36:28.270
This question is for all the utilities,

01:36:28.270 --> 01:36:32.620
but I'm gonna start with
framing up PG and E

01:36:32.620 --> 01:36:37.620
because I heard Paul say
is that they do have sort of

01:36:39.690 --> 01:36:44.690
a time dependency in their
probability of ignition function.

01:36:45.010 --> 01:36:50.010
But what I read in the
WMP is that their probability

01:36:53.500 --> 01:36:56.700
of ignition function
was location dependent

01:36:56.700 --> 01:37:00.840
and not so much
specifically time dependent.

01:37:00.840 --> 01:37:05.840
So to be specific, do your
probability of ignition models

01:37:09.510 --> 01:37:13.540
take into account the
contingent weather conditions

01:37:13.540 --> 01:37:15.243
at the time of the risk event?

01:37:16.570 --> 01:37:21.570
Or do they, for instance,
take into account the peak wind

01:37:23.670 --> 01:37:28.670
or peak weather
conditions at that location?

01:37:29.810 --> 01:37:34.810
Or do they use an
average weather condition?

01:37:35.600 --> 01:37:39.440
Because I, what I had read
in the PG and E's WMP is

01:37:39.440 --> 01:37:42.440
that they're using averages
and that doesn't seem right

01:37:42.440 --> 01:37:45.560
to me because wildfires don't occur

01:37:45.560 --> 01:37:47.900
under average weather conditions,

01:37:47.900 --> 01:37:51.160
they occur under extreme
and peak weather conditions.

01:37:51.160 --> 01:37:53.690
So how do you take into account

01:37:53.690 --> 01:37:55.891
with probability of ignition,

01:37:55.891 --> 01:37:59.410
these, the weather contingencies

01:37:59.410 --> 01:38:01.950
on a specific event by event basis

01:38:01.950 --> 01:38:06.950
on a peak overall peak for
a location, or as an average?

01:38:09.680 --> 01:38:12.760
<v ->Okay, thank you
for that question, Joe.</v>

01:38:12.760 --> 01:38:14.470
There's a, there's a
lot to unpack there,

01:38:14.470 --> 01:38:17.113
so let me, let me try
and unwind some of that.

01:38:18.630 --> 01:38:23.630
Our modeling is based on
asset data, environmental data,

01:38:24.500 --> 01:38:26.140
and weather data,

01:38:26.140 --> 01:38:28.840
all of which has a
temporal component to it.

01:38:28.840 --> 01:38:30.350
There's age of the asset,

01:38:30.350 --> 01:38:32.060
there's age of particular upgrades,

01:38:32.060 --> 01:38:36.050
or changes out with regard
to environmental information.

01:38:36.050 --> 01:38:38.350
It changes across
the course of the year.

01:38:38.350 --> 01:38:41.001
So we're using different time periods

01:38:41.001 --> 01:38:42.040
when we're assessing that.

01:38:42.040 --> 01:38:43.270
And for weather conditions,

01:38:43.270 --> 01:38:47.230
I could correctly say weather
changes and wildfires tend

01:38:47.230 --> 01:38:52.230
to occur during our high
fire threat wind type periods.

01:38:52.530 --> 01:38:54.970
So that is in the model.

01:38:54.970 --> 01:38:59.330
With regard to the
prediction themselves,

01:38:59.330 --> 01:39:01.870
we're using the training set of data,

01:39:01.870 --> 01:39:06.870
which looks at historical
PUC reportable ignitions,

01:39:08.384 --> 01:39:10.510
and they have a temporal flavor to them

01:39:10.510 --> 01:39:14.410
in that we can look at the
distribution of those ignitions

01:39:14.410 --> 01:39:16.000
over the course of the year.

01:39:16.000 --> 01:39:19.410
The majority of them happen
in what we call IR season,

01:39:19.410 --> 01:39:21.825
which tends to be
between the PDL, late May,

01:39:21.825 --> 01:39:24.930
early June through the end of November.

01:39:24.930 --> 01:39:26.730
That doesn't mean they
don't happen outside of that.

01:39:26.730 --> 01:39:30.430
That tends to be when the
majority of those ignitions occur.

01:39:30.430 --> 01:39:32.830
So when we're looking at these ignitions

01:39:32.830 --> 01:39:34.240
and we're making these predictions

01:39:34.240 --> 01:39:36.740
there is a temporal component to it,

01:39:36.740 --> 01:39:38.000
but there's also that location

01:39:38.000 --> 01:39:40.687
or specific component as well,

01:39:40.687 --> 01:39:42.160
based on the environmental conditions

01:39:42.160 --> 01:39:43.910
at that particular place.

01:39:43.910 --> 01:39:45.960
And there's a lot of things going on,

01:39:45.960 --> 01:39:48.230
the particular algorithm
that we're doing,

01:39:48.230 --> 01:39:50.540
doesn't rank them in rank order,

01:39:50.540 --> 01:39:52.790
but more of a permutation type part.

01:39:52.790 --> 01:39:56.790
And in other words, if we
get a small bore conductor

01:39:56.790 --> 01:40:01.400
with splices on it in an
area with high grasses,

01:40:01.400 --> 01:40:03.430
high winds that are dried out,

01:40:03.430 --> 01:40:06.240
there is a more likelihood
of an ignition occurring

01:40:06.240 --> 01:40:08.580
in that particular geographical location

01:40:08.580 --> 01:40:10.203
at a particular point in time.

01:40:11.302 --> 01:40:12.410
<v Joe>Yes, I, I
looked at your, your,</v>

01:40:12.410 --> 01:40:14.160
the variables that were used

01:40:14.160 --> 01:40:17.630
and I saw average wind condition.

01:40:17.630 --> 01:40:21.310
I did not see peak wind
conditions in the list.

01:40:21.310 --> 01:40:23.310
<v ->Let me verify that
for you, thank you.</v>

01:40:27.794 --> 01:40:29.010
<v Joe>We can take
that answer offline or,</v>

01:40:29.010 --> 01:40:31.330
you know, handle it separately

01:40:31.330 --> 01:40:33.383
if you don't know off
the top of your head.

01:40:36.450 --> 01:40:38.754
<v ->I don't know it off
the top of my head,</v>

01:40:38.754 --> 01:40:42.084
but I can get back to
you looking at the list of all

01:40:42.084 --> 01:40:46.853
the topic near the top,
co-variates were conducted.

01:40:48.350 --> 01:40:50.680
Let me get back to you on that.

01:40:50.680 --> 01:40:51.623
<v ->Okay, thanks.</v>

01:40:57.306 --> 01:40:58.856
(indistinct) utilities as well.

01:41:00.220 --> 01:41:01.370
I can go next if you want,

01:41:01.370 --> 01:41:03.923
this is Joe Boycewater from
Southern California Edison.

01:41:05.040 --> 01:41:07.520
So let me break it into two, two parts.

01:41:07.520 --> 01:41:10.370
The consequences and
the probability ignition.

01:41:10.370 --> 01:41:12.210
We mentioned earlier with when we went

01:41:12.210 --> 01:41:16.330
to Technosylva, gave us,
gave us a few more options

01:41:16.330 --> 01:41:18.610
for consequence, specifically,

01:41:18.610 --> 01:41:20.870
whether we want to use the max,

01:41:20.870 --> 01:41:23.103
the 90 percentile or the average.

01:41:24.340 --> 01:41:27.710
So in general, we
have the ability to look

01:41:27.710 --> 01:41:31.770
at these two components
in different ways,

01:41:31.770 --> 01:41:34.540
and we're gonna usually choose
what makes the most sense

01:41:34.540 --> 01:41:36.760
for the particular problems.

01:41:36.760 --> 01:41:40.530
So for example, for
planning mitigation work

01:41:40.530 --> 01:41:43.630
that may take a year
or a year and a half

01:41:43.630 --> 01:41:46.980
before we can actually
complete the work,

01:41:46.980 --> 01:41:49.636
we're likely to use the max consequence.

01:41:49.636 --> 01:41:53.590
That ensures that we're,
we're going after the areas

01:41:53.590 --> 01:41:57.790
with the highest consequence in general.

01:41:57.790 --> 01:41:59.350
On the probability of ignition side,

01:41:59.350 --> 01:42:01.663
we looked at it a few different ways.

01:42:02.500 --> 01:42:06.151
First, we did correlation
analysis at the circuit level

01:42:06.151 --> 01:42:08.760
with outages and wind.

01:42:08.760 --> 01:42:11.270
So we, we originally
thinking that, you know,

01:42:11.270 --> 01:42:14.130
do we really want to build
our model off of, you know,

01:42:14.130 --> 01:42:17.070
to avoid high wind situations?

01:42:17.070 --> 01:42:20.860
The challenge was that the correlation

01:42:20.860 --> 01:42:25.260
between actual wind
speed and when faults occur

01:42:26.110 --> 01:42:29.690
is fairly loose, it's not a
very strong correlation,

01:42:29.690 --> 01:42:31.400
particularly when you start getting down

01:42:31.400 --> 01:42:34.860
to the asset level circuit level.

01:42:34.860 --> 01:42:37.270
When you start bringing it up into zones

01:42:37.270 --> 01:42:38.860
or districts or regions,

01:42:38.860 --> 01:42:40.990
you start seeing a
little bit more correlation

01:42:40.990 --> 01:42:45.830
between outages and, and wind speeds,

01:42:45.830 --> 01:42:49.430
but the correlation isn't super strong.

01:42:49.430 --> 01:42:51.570
Plus if, if we started limiting

01:42:51.570 --> 01:42:53.130
the development of our development

01:42:53.130 --> 01:42:56.320
of our models to specific
weather scenarios,

01:42:56.320 --> 01:43:01.320
like only data that occurs
on high wind, high FPI days,

01:43:01.430 --> 01:43:04.790
we start making this trade-off
between model accuracy

01:43:04.790 --> 01:43:08.210
that you get from
having lots of data and,

01:43:08.210 --> 01:43:11.140
and less accuracy
because you're using smaller

01:43:11.140 --> 01:43:14.460
and smaller sets of data.

01:43:14.460 --> 01:43:18.240
Also, because again, we
we're, we're building mostly,

01:43:18.240 --> 01:43:20.780
we're building these
models for the purposes of

01:43:20.780 --> 01:43:22.610
prioritizing mitigations,
which are going

01:43:22.610 --> 01:43:27.050
to take some time to, to advance.

01:43:27.050 --> 01:43:28.890
And also because, you know,

01:43:28.890 --> 01:43:32.930
we've now seen that you
can have very large fires even

01:43:32.930 --> 01:43:37.930
on relatively low wind days
from these fuel driven fires.

01:43:38.410 --> 01:43:40.970
The, the idea that
you only get the fires

01:43:40.970 --> 01:43:43.610
when the wind is very strong, last year,

01:43:43.610 --> 01:43:46.885
I think was proven not to be correct.

01:43:46.885 --> 01:43:48.510
So what we do is we build our,

01:43:48.510 --> 01:43:51.810
we do want to get at the
asset level and we want

01:43:51.810 --> 01:43:54.090
that model to be as
accurate as possible.

01:43:54.090 --> 01:43:55.790
And so that, which means we have to use

01:43:55.790 --> 01:43:57.490
as much data as possible.

01:43:57.490 --> 01:43:59.320
We built our app, we built our models,

01:43:59.320 --> 01:44:01.955
our probability of
ignition models using,

01:44:01.955 --> 01:44:03.420
like I said earlier,

01:44:03.420 --> 01:44:06.870
outages that could lead to a
spark and using all outages.

01:44:06.870 --> 01:44:08.880
So in practice,

01:44:08.880 --> 01:44:10.790
what that actually ends up meaning is

01:44:10.790 --> 01:44:13.930
that our probabilities
of ignition, aren't only,

01:44:13.930 --> 01:44:18.713
aren't specific to just
the highest wind days.

01:44:18.713 --> 01:44:21.000
They, they basically are.

01:44:21.000 --> 01:44:25.587
They represent what is the
current probability of ignition

01:44:25.587 --> 01:44:28.800
for each asset in our, in our system.

01:44:28.800 --> 01:44:30.830
And then the way we do a time component

01:44:30.830 --> 01:44:32.710
to that is through some calibration,

01:44:32.710 --> 01:44:35.230
which if you were
interested in the details,

01:44:35.230 --> 01:44:39.462
data scientists could,
could tell you how that works,

01:44:39.462 --> 01:44:43.940
but we calibrate it to
get a sense for based

01:44:43.940 --> 01:44:45.460
on our system and our probabilities,

01:44:45.460 --> 01:44:48.180
how many ignitions would
we expect in the next year,

01:44:48.180 --> 01:44:49.093
for example?

01:44:50.900 --> 01:44:52.003
Did I get to your question, Joe?

01:44:52.003 --> 01:44:55.087
<v Joe>Yeah, that was
good, thank you.</v>

01:44:57.490 --> 01:44:58.917
<v Man>Hi, Joe,
this is (indistinct).</v>

01:45:00.950 --> 01:45:02.080
I'll try to make this brief.

01:45:02.080 --> 01:45:03.690
I think we're pretty similar
to what you've heard

01:45:03.690 --> 01:45:06.510
from the others, because it
is a long-term planning model,

01:45:06.510 --> 01:45:10.800
which is different than what
we do in operational modes,

01:45:10.800 --> 01:45:11.953
we're looking at the
max and we're looking

01:45:11.953 --> 01:45:16.953
at the max wind speed and
the max consequence right now.

01:45:17.730 --> 01:45:18.660
We know in a perfect world,

01:45:18.660 --> 01:45:22.270
we want to extend out like
an 87 60 view of the year

01:45:23.264 --> 01:45:24.680
and have the lesser
events included as well.

01:45:24.680 --> 01:45:26.170
But right now we're looking at the max.

01:45:26.170 --> 01:45:29.035
So the roadmap has to have
a better view, excuse me.

01:45:29.035 --> 01:45:31.483
But right now we are looking at max.

01:45:33.600 --> 01:45:36.080
<v Man>Okay, so
that's, that's not on</v>

01:45:36.080 --> 01:45:37.240
an event-by-event level.

01:45:37.240 --> 01:45:39.620
That's sort of like an annual max

01:45:39.620 --> 01:45:41.173
or something like that?

01:45:42.090 --> 01:45:42.980
<v ->Correct?</v>

01:45:42.980 --> 01:45:47.130
For the time being, in 2021,
it may no longer be that way,

01:45:47.130 --> 01:45:48.930
but that's how it is at this moment.

01:45:49.887 --> 01:45:51.220
[Man] Thank you.

01:45:55.230 --> 01:45:57.090
<v ->Great, thank you, Joseph.</v>

01:45:57.090 --> 01:45:59.993
Yeah, let's move over to
a Green Power Institute.

01:46:04.140 --> 01:46:06.540
<v Zoey>Hi, this is Zoey Harold</v>

01:46:06.540 --> 01:46:07.950
with Green Power Institute.

01:46:07.950 --> 01:46:10.080
My question is for PG and E.

01:46:10.080 --> 01:46:13.660
So as has been mentioned,
a couple of times already,

01:46:13.660 --> 01:46:15.850
the machine-learning models that train

01:46:15.850 --> 01:46:19.020
on relatively large
datasets are more accurate.

01:46:19.020 --> 01:46:21.850
And so see is using the
outage data set to increase

01:46:21.850 --> 01:46:25.700
the number of events in
their data training input.

01:46:25.700 --> 01:46:28.940
In contrast, we see PG
and E's using ignitions,

01:46:28.940 --> 01:46:31.250
which actually has one
to two orders of magnitude

01:46:31.250 --> 01:46:34.230
less data than the outage event data.

01:46:34.230 --> 01:46:35.940
And then two to three
orders of magnitude,

01:46:35.940 --> 01:46:39.160
fewer events than the
total risk event dataset.

01:46:39.160 --> 01:46:42.520
So my question is why is PG and E

01:46:42.520 --> 01:46:45.048
using the ignition dataset?

01:46:45.048 --> 01:46:47.770
It only has tens of
thousands of events inputs

01:46:47.770 --> 01:46:51.820
versus risk or event risk datasets.

01:46:51.820 --> 01:46:52.653
Thank you.

01:46:54.850 --> 01:46:57.130
Hi Zoey, thank you for that
question, that's a good one.

01:46:57.130 --> 01:46:58.630
And thanks for bringing it up.

01:46:59.510 --> 01:47:04.510
In the 2019 and 2020 models
that PG and E presented,

01:47:04.520 --> 01:47:09.520
we also use outages as
the dependent variable

01:47:11.130 --> 01:47:12.420
in our regression,

01:47:12.420 --> 01:47:14.680
the independent radio variables being

01:47:15.836 --> 01:47:17.950
the actual passive asset
attributes, et cetera, et cetera.

01:47:17.950 --> 01:47:22.950
And we were using that as
our teachers, what we find.

01:47:23.330 --> 01:47:24.990
And again, this is related to the data

01:47:24.990 --> 01:47:26.750
as you correctly say, when we,

01:47:26.750 --> 01:47:30.233
when we analyze and examine
the particular outage data,

01:47:31.067 --> 01:47:33.380
the OTG data tends to be collected

01:47:33.380 --> 01:47:35.560
by the neatest piece
of recording equipment,

01:47:35.560 --> 01:47:38.870
as opposed to where the
particular risk event occurred.

01:47:38.870 --> 01:47:41.870
So when we repent ignitions,

01:47:41.870 --> 01:47:45.300
we tend to have the
lat-long of those ignitions

01:47:45.300 --> 01:47:49.340
because we had a trouble
man or utility personnel

01:47:49.340 --> 01:47:50.670
in that particular area.

01:47:50.670 --> 01:47:54.874
So we can be more
specific to our actual EDR

01:47:54.874 --> 01:47:56.950
or where the risk event
the ignition occurred.

01:47:56.950 --> 01:47:58.600
PG and E did make that movement.

01:47:58.600 --> 01:48:01.787
We went from outages to ignitions,

01:48:03.510 --> 01:48:05.740
predominantly around identification of

01:48:05.740 --> 01:48:08.504
the specific location
of where it occurred,

01:48:08.504 --> 01:48:11.957
our particular granularity
from this latest model,

01:48:11.957 --> 01:48:16.400
the 2021 Wildfire Distribution
Risk Model as at 100-meter

01:48:16.400 --> 01:48:18.260
by 100-meter resolution.

01:48:18.260 --> 01:48:19.990
If we went back to outages,

01:48:19.990 --> 01:48:24.090
we would be moving that
to a lesser pixel granularity,

01:48:24.090 --> 01:48:25.890
and it would be at
the piece of equipment.

01:48:25.890 --> 01:48:27.440
That's picking up that voltage.

01:48:35.200 --> 01:48:36.750
<v Zoey>Great, thanks so much.</v>

01:48:42.184 --> 01:48:43.070
<v ->All right, thank you, Zoey.</v>

01:48:43.070 --> 01:48:45.213
Next let's do Cal Advocates please.

01:48:50.810 --> 01:48:52.490
<v ->Hi, this is Henry Burton</v>

01:48:52.490 --> 01:48:54.770
with the Public Advocate's Office.

01:48:54.770 --> 01:48:57.520
I just want to follow up back
on Joe Mitchell's question

01:48:57.520 --> 01:49:00.743
about whether scenarios
and the risk modeling.

01:49:03.028 --> 01:49:05.210
So in a previous workshop at a firm said

01:49:05.210 --> 01:49:08.020
they have 41 weather
scenarios and they picked

01:49:08.020 --> 01:49:11.373
the scenario with the
maximum consequence.

01:49:12.570 --> 01:49:16.550
And so the question for
Edison and also STG and E,

01:49:16.550 --> 01:49:18.380
when you say you picked
the maximum consequences,

01:49:18.380 --> 01:49:22.750
do you mean the scenario that
has the greatest consequences

01:49:22.750 --> 01:49:24.610
across your entire service territory?

01:49:24.610 --> 01:49:28.140
Or do you pick the maximum
that the scenario that yields

01:49:28.140 --> 01:49:31.213
the greatest consequences
at each asset level?

01:49:33.660 --> 01:49:35.660
Do you understand what I'm asking there?

01:49:38.740 --> 01:49:40.470
<v ->Yeah, I think
so, this is Robert.</v>

01:49:40.470 --> 01:49:42.390
And Joe can chime in and correct me

01:49:42.390 --> 01:49:46.277
if I get this wrong, but
my understanding is our,

01:49:46.277 --> 01:49:50.060
the 40 weather scenarios are
actually put into an algorithm

01:49:50.060 --> 01:49:53.200
that want to come Monte
Carlo-type simulation.

01:49:53.200 --> 01:49:56.340
And so it's not just pick the max,

01:49:56.340 --> 01:49:59.830
but we picked the max 41
days for a particular location

01:49:59.830 --> 01:50:01.910
and then run that through the simulation

01:50:01.910 --> 01:50:03.220
right, to generate the score.

01:50:03.220 --> 01:50:07.170
So it's, I don't believe that it is

01:50:07.170 --> 01:50:09.495
instead of thinking just one number,

01:50:09.495 --> 01:50:10.746
but if you have a different response,

01:50:10.746 --> 01:50:11.843
you could correct
me if I got that wrong.

01:50:12.980 --> 01:50:14.420
<v Joe>Yeah, I would just add to it.</v>

01:50:14.420 --> 01:50:16.160
So if you remember, we,

01:50:16.160 --> 01:50:19.050
we mentioned that
Technosylva is providing us

01:50:19.050 --> 01:50:22.510
consequence values
at the asset location.

01:50:22.510 --> 01:50:25.520
So that means a simulation
is run at each asset location

01:50:25.520 --> 01:50:28.743
and we take the max
consequently at each location.

01:50:30.300 --> 01:50:32.454
<v ->Okay, so that
means you could have</v>

01:50:32.454 --> 01:50:33.780
different weather scenarios

01:50:33.780 --> 01:50:36.220
being employed for different assets.

01:50:36.220 --> 01:50:37.690
<v Man>Yes.</v>

01:50:37.690 --> 01:50:38.555
<v Henry>Okay.</v>

01:50:38.555 --> 01:50:40.005
And SDG and E, same question.

01:50:41.000 --> 01:50:43.180
<v ->Yeah, so currently
what we're using is</v>

01:50:43.180 --> 01:50:44.600
the max at the location.

01:50:44.600 --> 01:50:48.290
So there'll be different wind
patterns and kind of patterns

01:50:48.290 --> 01:50:50.863
at each pole, and we're
taking the max as the pole.

01:50:51.880 --> 01:50:52.870
As I mentioned to Joe though,

01:50:52.870 --> 01:50:54.990
that's changing and
we're going to be taking

01:50:54.990 --> 01:50:56.697
into account more, but
right now we're taking

01:50:56.697 --> 01:50:59.973
the max at each location,
not, not a system wide map.

01:51:01.480 --> 01:51:02.330
<v Henry>Got it.</v>

01:51:08.550 --> 01:51:11.500
Okay, and PG and E, do you
have an answer to that question?

01:51:12.826 --> 01:51:14.130
It wasn't clear to me that
you were using the same

01:51:14.130 --> 01:51:15.103
type of approach.

01:51:16.330 --> 01:51:18.490
We're using a similar approach, Henry.

01:51:18.490 --> 01:51:22.910
So again, on our probability model,

01:51:22.910 --> 01:51:24.790
and this is the question that the answer

01:51:24.790 --> 01:51:25.870
that I will draw back,

01:51:25.870 --> 01:51:29.560
I believe we use both average
and max for the wind speeds

01:51:29.560 --> 01:51:32.630
and the inputs to
generate the probability.

01:51:32.630 --> 01:51:34.850
On the output, we all, we all use

01:51:34.850 --> 01:51:37.360
the Technosylva
application, and Technosylva.

01:51:37.360 --> 01:51:40.840
can give us those answers
at the maximum consequence,

01:51:40.840 --> 01:51:45.450
the P 90, or also the, the mean.

01:51:45.450 --> 01:51:46.960
It's my understanding PGD is using

01:51:46.960 --> 01:51:49.609
the P 90 when we look at that.

01:51:49.609 --> 01:51:52.057
So it was slightly different
approach, but again,

01:51:52.057 --> 01:51:53.510
it's just a flavor of which we can take.

01:51:53.510 --> 01:51:55.600
We can see all of the results,

01:51:55.600 --> 01:51:57.480
but what we're using in our modeling.

01:51:57.480 --> 01:51:59.552
And again, Mason actually said

01:51:59.552 --> 01:52:00.800
that's really nicely earlier on is

01:52:00.800 --> 01:52:04.030
all of our wildfire models
are for system planning

01:52:04.030 --> 01:52:05.820
and mitigation-type activities.

01:52:05.820 --> 01:52:08.470
These are not real
time, operational models,

01:52:08.470 --> 01:52:11.277
real time operational
models that are being used

01:52:11.277 --> 01:52:15.810
for PSPS-type activities are
looking at the actual weather

01:52:15.810 --> 01:52:17.920
versus historical weather patterns.

01:52:17.920 --> 01:52:19.310
So I think that was worthy of noting.

01:52:19.310 --> 01:52:21.533
And thank you Mason
for making that clear.

01:52:24.970 --> 01:52:26.220
<v Man>Great, thank you.</v>

01:52:31.444 --> 01:52:32.277
<v ->Thank you, Henry.</v>

01:52:32.277 --> 01:52:33.670
Let's go right to Mr. Rayburn.

01:52:36.570 --> 01:52:38.438
<v ->Thanks very much
great to see progress</v>

01:52:38.438 --> 01:52:41.663
in the Wildfire Mitigation Plans.

01:52:42.958 --> 01:52:46.260
I, I have a broad question before

01:52:46.260 --> 01:52:50.340
I get into further questions
around methodology.

01:52:50.340 --> 01:52:54.610
The broader question
that I have is I sort of see

01:52:54.610 --> 01:52:57.020
a big gaping hole in these plans,

01:52:57.020 --> 01:53:00.730
and I'm hoping that
folks can either fill the hole

01:53:00.730 --> 01:53:03.550
or identify that it's not a hole.

01:53:03.550 --> 01:53:06.660
So specifically sort of
tying the assessments

01:53:06.660 --> 01:53:10.240
to our catastrophic wildfires.

01:53:10.240 --> 01:53:15.240
So, you know, as an example,
sort of an analogy, you know,

01:53:16.140 --> 01:53:21.140
if the Airbus went down
with Boeing and Boeing went

01:53:22.610 --> 01:53:27.610
to the FAA to explain why
these catastrophic wildfires

01:53:27.700 --> 01:53:31.680
occurred and built
into their risk modeling

01:53:31.680 --> 01:53:34.860
and the risk assessment
improvements based on that,

01:53:34.860 --> 01:53:36.920
you know, they would identify, you know,

01:53:36.920 --> 01:53:41.920
perhaps where the fan that
was at fault was incorporated

01:53:42.380 --> 01:53:47.340
to within their
assessment, or the air inlet,

01:53:47.340 --> 01:53:50.990
or the electrical coupler or
whatever those components are

01:53:50.990 --> 01:53:55.210
within that airplane that
failed, that caused that accident,

01:53:55.210 --> 01:53:57.660
they will report how
they incorporated that

01:53:57.660 --> 01:54:00.480
into their methodology in assessment.

01:54:00.480 --> 01:54:05.190
I have not seen in any of
the presentations thus far

01:54:05.190 --> 01:54:09.700
that specifics about here's
where we incorporated

01:54:09.700 --> 01:54:13.280
the learnings, as an
example from the Kincade Fire,

01:54:13.280 --> 01:54:16.970
this jumper failed, this is
where infrastructure needed

01:54:16.970 --> 01:54:19.010
to be de-energized and wasn't,

01:54:19.010 --> 01:54:23.290
and it is represented in our
Wildfire Mitigation Plan here,

01:54:23.290 --> 01:54:24.820
here, and here.

01:54:24.820 --> 01:54:28.950
And so I guess that's
sort of the big gaping hole

01:54:28.950 --> 01:54:33.351
that I see is tying recent
catastrophic wildfires,

01:54:33.351 --> 01:54:36.350
very specifically to how
you've addressed them.

01:54:36.350 --> 01:54:38.900
So I guess my question
would sort of be two part,

01:54:38.900 --> 01:54:43.880
one would be, you know,
can you please, I guess,

01:54:43.880 --> 01:54:47.160
state to me that you don't
see that as a big gaping hole,

01:54:47.160 --> 01:54:50.530
in which case I understand
that's your position,

01:54:50.530 --> 01:54:53.120
or if you filled that hole,

01:54:53.120 --> 01:54:56.280
if you can be more specific
and sort of go through

01:54:56.280 --> 01:54:58.560
the catastrophic wildfires
that have occurred

01:54:58.560 --> 01:55:00.970
in recent years within your territory

01:55:00.970 --> 01:55:04.749
and explain where specifically
that has been incorporated

01:55:04.749 --> 01:55:07.003
into your Wildfire Mitigation Plan.

01:55:07.950 --> 01:55:08.783
Thank you.

01:55:09.960 --> 01:55:10.920
<v ->This is Mason.</v>

01:55:10.920 --> 01:55:12.970
I'll take that one
first, if that's okay?

01:55:14.940 --> 01:55:18.080
First of all, Mr. Abrams,
nice to see you again.

01:55:18.080 --> 01:55:19.880
I wouldn't say that we are trying to do

01:55:19.880 --> 01:55:21.270
exactly what you're talking about,

01:55:21.270 --> 01:55:24.840
and maybe we need to
communicate it a little more clearly.

01:55:24.840 --> 01:55:26.790
SDG and E and I
believe the other utilities

01:55:26.790 --> 01:55:29.040
have done a very good job at researching

01:55:29.040 --> 01:55:30.740
what the circumstances were that led

01:55:30.740 --> 01:55:34.670
to large fires and try to understand,

01:55:34.670 --> 01:55:36.250
was it, was it an acid issue?

01:55:36.250 --> 01:55:38.250
Was it an outside contact issue?

01:55:38.250 --> 01:55:40.090
What could have at that fire?

01:55:40.090 --> 01:55:43.291
What were the circumstances
environmentally, the vegetation,

01:55:43.291 --> 01:55:45.260
the engineering conditions,

01:55:45.260 --> 01:55:47.310
what were the inspection
records on everything,

01:55:47.310 --> 01:55:51.670
we've been studying wildfire
pretty intensely since 2003,

01:55:51.670 --> 01:55:54.310
when we had some local fires
that were not associated STG

01:55:54.310 --> 01:55:57.630
and E but then, I mean,
literally for 17 years,

01:55:57.630 --> 01:56:00.330
we've been tracking ignitions
and trying to understand

01:56:00.330 --> 01:56:02.370
the conditions that lead
to those catastrophic ones

01:56:02.370 --> 01:56:04.328
that you're talking about.

01:56:04.328 --> 01:56:05.161
And we've done research,

01:56:05.161 --> 01:56:06.530
we have a fire potential index,

01:56:06.530 --> 01:56:08.300
and that was created
for the specific purpose.

01:56:08.300 --> 01:56:09.450
I think what you're talking about,

01:56:09.450 --> 01:56:11.540
which is in extreme conditions,

01:56:11.540 --> 01:56:14.310
extreme conditions are
probably over 90% of

01:56:14.310 --> 01:56:15.810
where wildfire risk is.

01:56:15.810 --> 01:56:17.598
There's an elevated piece, which is

01:56:17.598 --> 01:56:20.460
a little bit of fire risk and
the normal conditions.

01:56:20.460 --> 01:56:22.550
There's not much
wildfire risk to speak of.

01:56:22.550 --> 01:56:25.260
So we've been doing that
kind of analysis for quite awhile.

01:56:25.260 --> 01:56:28.680
The tier system of tier
two, tier three is also driving

01:56:28.680 --> 01:56:31.350
towards that, of doing the
work on these focused areas,

01:56:31.350 --> 01:56:33.820
where if the fire started
in those locations,

01:56:33.820 --> 01:56:35.460
they would be larger than if they happen

01:56:35.460 --> 01:56:36.860
in other situations.

01:56:36.860 --> 01:56:38.568
So we're trying to look at it

01:56:38.568 --> 01:56:39.440
from an environmental perspective,

01:56:39.440 --> 01:56:41.280
from a geographical perspective.

01:56:41.280 --> 01:56:43.460
And now we've done ignition
management to figure out

01:56:43.460 --> 01:56:45.820
what is the, what are
causing the outages?

01:56:45.820 --> 01:56:48.560
So we looked at, is
there a piece of equipment

01:56:48.560 --> 01:56:50.030
or was it outside contact?

01:56:50.030 --> 01:56:52.130
And we we've gone
through that for years now.

01:56:52.130 --> 01:56:55.340
And every time ignition
comes up, we try to review,

01:56:55.340 --> 01:56:57.490
is there something more
we could be doing about that?

01:56:57.490 --> 01:56:58.810
So, for example, back in the day,

01:56:58.810 --> 01:57:00.410
we had a lot of capacitor failures

01:57:00.410 --> 01:57:01.720
that were causing ignitions.

01:57:01.720 --> 01:57:04.910
We tackled those, we,
we placed all old capacitors

01:57:04.910 --> 01:57:06.900
in our back country
because we didn't want those

01:57:06.900 --> 01:57:08.190
to be a fire source.

01:57:08.190 --> 01:57:10.000
You know, we go through asset-by-asset,

01:57:10.000 --> 01:57:12.470
trying to figure out what
circumstances would

01:57:12.470 --> 01:57:13.970
a catastrophic fire occur

01:57:13.970 --> 01:57:16.110
and what can we do to mitigate those?

01:57:16.110 --> 01:57:18.400
PSPS's, this is the final straw

01:57:18.400 --> 01:57:19.640
along that where we can say,

01:57:19.640 --> 01:57:23.090
look with this given equipment
with these wind conditions,

01:57:23.090 --> 01:57:27.130
we think there is a chance
that an ignition could occur.

01:57:27.130 --> 01:57:29.760
And so PSPS is the last resort,

01:57:29.760 --> 01:57:32.880
but all that is to
prevent catastrophic fire.

01:57:32.880 --> 01:57:35.003
I, I hope I've made my case.

01:57:36.343 --> 01:57:37.176
<v ->I, I appreciate that.</v>

01:57:37.176 --> 01:57:38.810
And just, just to clarify,

01:57:38.810 --> 01:57:42.110
I think part of this just has
to do with the audience and

01:57:42.110 --> 01:57:44.960
the consumers of the
Wildfire Mitigation Plan.

01:57:44.960 --> 01:57:47.340
And so I think that part of the,

01:57:47.340 --> 01:57:49.950
the folks who are the consumers of

01:57:49.950 --> 01:57:54.950
the Wildfire Mitigation
Plan are our rate payers,

01:57:54.970 --> 01:57:59.970
our residents, who, who
lost their home in 2017,

01:58:00.990 --> 01:58:02.750
due to a catastrophic wildfire,

01:58:02.750 --> 01:58:06.100
who evacuated from their home in 2018,

01:58:06.100 --> 01:58:10.430
who again, had a close
call in 2019, and so on.

01:58:10.430 --> 01:58:13.800
So, you know, part
of what those residents

01:58:13.800 --> 01:58:18.500
I imagined would need
to see and ambitions see

01:58:18.500 --> 01:58:20.340
in a Wildfire Mitigation Plan

01:58:20.340 --> 01:58:24.130
so that I can breathe
easier if I live in these areas

01:58:24.130 --> 01:58:29.130
is to say, okay, great, PG
and E has the Kincade Fire.

01:58:29.130 --> 01:58:32.630
They identified these three things.

01:58:32.630 --> 01:58:35.000
They addressed it here, here,

01:58:35.000 --> 01:58:38.060
and here in their
Wildfire Mitigation Plan.

01:58:38.060 --> 01:58:42.860
Now I can breathe easy
because I know incorporated that

01:58:42.860 --> 01:58:46.660
into exactly where they need to do it

01:58:46.660 --> 01:58:48.850
so that we're safer moving forward.

01:58:48.850 --> 01:58:52.860
So it's, it's that level, again,

01:58:52.860 --> 01:58:56.860
for that audience that,
that really needs that.

01:58:56.860 --> 01:58:59.940
And I understand the
high-level presentation

01:58:59.940 --> 01:59:02.030
and walking through the methodology,

01:59:02.030 --> 01:59:05.200
but unless we get to the specific level,

01:59:05.200 --> 01:59:06.900
particularly around what caused

01:59:06.900 --> 01:59:10.170
these catastrophic
wildfires, I think we,

01:59:10.170 --> 01:59:14.560
we missed the mark with who
our audiences and we missed

01:59:14.560 --> 01:59:18.290
the mark in terms of
really being more proactive.

01:59:18.290 --> 01:59:22.180
And if we wait on the CAL
FIRE reports as an example

01:59:22.180 --> 01:59:26.040
that still hasn't come
out yet from Kincade,

01:59:26.040 --> 01:59:30.560
then it again is not really
providing assurances

01:59:30.560 --> 01:59:32.240
that we've addressed those things.

01:59:32.240 --> 01:59:35.810
And that's the, again,
this whole that I see

01:59:35.810 --> 01:59:38.320
that really needs to be addressed.

01:59:38.320 --> 01:59:41.881
So if we can, I guess
be specific about that,

01:59:41.881 --> 01:59:42.790
that would be fantastic.

01:59:42.790 --> 01:59:43.623
Thank you.

01:59:44.600 --> 01:59:46.320
<v ->Well, I I'd like to take a shot</v>

01:59:46.320 --> 01:59:47.774
at answering your question

01:59:47.774 --> 01:59:51.180
because I think a lot of that
was put toward PG and E,

01:59:51.180 --> 01:59:54.360
and I appreciate those
questions with regards

01:59:54.360 --> 01:59:57.470
to our Wildfire
Mitigation Plan for 2021,

01:59:57.470 --> 02:00:00.740
it is very distribution
voltage class focused,

02:00:00.740 --> 02:00:02.560
as I'm sure you've observed.

02:00:02.560 --> 02:00:07.030
The thing about distribution
voltage ignitions is there are

02:00:07.030 --> 02:00:11.300
a lot more audible for PG
and E, off the top of my head,

02:00:11.300 --> 02:00:13.740
it's about 90% per year.

02:00:13.740 --> 02:00:16.840
So it's about 90 over
100 ignitions per year.

02:00:16.840 --> 02:00:18.770
And from my time at the other utilities,

02:00:18.770 --> 02:00:21.310
it's probably a very similar ratio.

02:00:21.310 --> 02:00:23.820
So we have a lot more
thought on the distribution site.

02:00:23.820 --> 02:00:25.350
And that's the first order of business

02:00:25.350 --> 02:00:27.000
that we've gone after.

02:00:27.000 --> 02:00:32.000
as part of our Wildfire Mitigation
Plan and our model build,

02:00:32.160 --> 02:00:33.860
there is a number of failure,

02:00:33.860 --> 02:00:38.750
modes, effects, and analysis
FMI that goes on and gets done.

02:00:38.750 --> 02:00:42.193
So we're looking at components
that we need to mitigate,

02:00:43.060 --> 02:00:44.420
for example, and again,

02:00:44.420 --> 02:00:48.040
I speak about this only
generally that we've seen failures

02:00:48.040 --> 02:00:50.960
related to particular types
of connectors or clamps,

02:00:50.960 --> 02:00:53.530
or what have you, and
then we analyze the list.

02:00:53.530 --> 02:00:55.890
And then we look at
taking them out of service,

02:00:55.890 --> 02:01:00.680
whether it be expulsion,
fuses that when we go out,

02:01:00.680 --> 02:01:04.090
we've got the reaction
that causes the fuse to expel

02:01:04.090 --> 02:01:05.350
their spark and there's heat,

02:01:05.350 --> 02:01:06.730
and they can be a source of ignition

02:01:06.730 --> 02:01:08.570
as well as protecting the fault.

02:01:08.570 --> 02:01:11.610
Well then know not to
climb those in certain areas,

02:01:11.610 --> 02:01:14.140
so that's how learning
We tend to be writing that

02:01:14.140 --> 02:01:16.613
into the mitigation-type discussion.

02:01:17.480 --> 02:01:21.370
Also, as you said, with
regards to the Kincade Fire,

02:01:21.370 --> 02:01:22.770
and I remember reading about this

02:01:22.770 --> 02:01:25.150
before I became a PG and E employee,

02:01:25.150 --> 02:01:28.810
the particular piece of
equipment that was expected

02:01:28.810 --> 02:01:32.810
of being part of this
was, was a jumper cable.

02:01:32.810 --> 02:01:36.550
And that particular piece
of analysis is not discussed

02:01:36.550 --> 02:01:40.450
in our Wildfire Mitigation
Plan because our transmission,

02:01:40.450 --> 02:01:43.270
distribution, sorry, our
Transmission Wildfire Risk Model

02:01:43.270 --> 02:01:45.000
is currently in development.

02:01:45.000 --> 02:01:48.260
What is discussed is what
we call the whole each model

02:01:48.260 --> 02:01:49.650
or the TOA model is

02:01:49.650 --> 02:01:53.020
the Transmission Operability
Assessment model.

02:01:53.020 --> 02:01:53.930
And you can find a little bit more

02:01:53.930 --> 02:01:57.120
about that in section 4.3,

02:01:57.120 --> 02:02:00.260
where we discussed PSPS de-energizations

02:02:00.260 --> 02:02:02.230
of the transmission level.

02:02:02.230 --> 02:02:04.630
And again, just to hit on
something Mason said,

02:02:04.630 --> 02:02:05.900
what we're doing is we're looking

02:02:05.900 --> 02:02:09.500
at real life system conditions,
what's on those assets.

02:02:09.500 --> 02:02:12.390
What's being identified
as a potential problem

02:02:12.390 --> 02:02:15.740
on the operability
assessment side of the metric.

02:02:15.740 --> 02:02:18.920
And then on the, the X-axis,

02:02:18.920 --> 02:02:21.950
we're looking at FPI
Fire Potential Index.

02:02:21.950 --> 02:02:25.430
If something were to fail,
what is the outcome of that?

02:02:25.430 --> 02:02:28.690
That is in our view infighting
decision making for making

02:02:28.690 --> 02:02:32.820
de-energization decisions
around a transmission circuit

02:02:32.820 --> 02:02:36.530
with regards to our planning models,

02:02:36.530 --> 02:02:40.060
our Transmission
Wildfire Risk Assessment,

02:02:40.060 --> 02:02:42.620
we're still building
that process in there.

02:02:42.620 --> 02:02:44.870
So we've got a ways to go
on that as I acknowledged

02:02:44.870 --> 02:02:48.670
that one, it's one of the things
we're working on in 2021.

02:02:48.670 --> 02:02:51.890
Unfortunately, we are
struggling with data on that one.

02:02:51.890 --> 02:02:53.430
It's something that all the utilities

02:02:53.430 --> 02:02:56.650
could potentially work
together and pool their data.

02:02:56.650 --> 02:02:58.800
We all have similar types of equipment,

02:02:58.800 --> 02:03:01.190
and we can use that larger data set.

02:03:01.190 --> 02:03:03.890
As I said, for PG and E,
for transmission voltage,

02:03:03.890 --> 02:03:07.100
it's about nine events per
year and subject to check

02:03:07.100 --> 02:03:08.480
with my STE colleagues,

02:03:08.480 --> 02:03:11.563
if I recall it's about
four events per year.

02:03:11.563 --> 02:03:14.980
So it's a very small amount
to do that analysis on,

02:03:14.980 --> 02:03:16.280
but we're making progress.

02:03:21.900 --> 02:03:23.887
<v ->Yeah, and I'll,
I'll add for SCE.</v>

02:03:26.120 --> 02:03:29.220
Similar to what Mason described,

02:03:29.220 --> 02:03:32.080
we have a process to
do root cause analysis

02:03:32.080 --> 02:03:35.900
on every ignition, whether
they're CPC reportable,

02:03:35.900 --> 02:03:38.091
or not reportable ignitions.

02:03:38.091 --> 02:03:40.710
So each time ignition takes place,

02:03:40.710 --> 02:03:43.870
we have a process where
we collect information

02:03:43.870 --> 02:03:46.040
on the circuit of circuit's history,

02:03:46.040 --> 02:03:48.430
reliability, inspection,

02:03:48.430 --> 02:03:51.630
maintenance has been
down on the circuit.

02:03:51.630 --> 02:03:53.980
And we also send
engineers out into the field

02:03:53.980 --> 02:03:57.970
to actually look at the,
the equipment that failed or,

02:03:57.970 --> 02:04:01.036
or try to figure out what caused it

02:04:01.036 --> 02:04:03.727
from an engineering perspective.

02:04:03.727 --> 02:04:06.850
What they gather from that gets fed back

02:04:06.850 --> 02:04:11.150
to us in the modeling
area to enhance models.

02:04:11.150 --> 02:04:14.433
So for example, about a year ago,

02:04:15.450 --> 02:04:19.420
we, we, they started to
understand the impact of wind

02:04:19.420 --> 02:04:22.450
on the lines and how
wind and the direction

02:04:22.450 --> 02:04:25.440
that the wind was hitting the lines

02:04:25.440 --> 02:04:30.240
could influence failures
in multiple different ways.

02:04:30.240 --> 02:04:32.390
So one of the things we created for our,

02:04:32.390 --> 02:04:36.210
our Wildfire Risk Model was
the cumulative wind force.

02:04:36.210 --> 02:04:39.960
We went back hourly
data over the last 10 years,

02:04:39.960 --> 02:04:44.960
and then using basically
your basic physics

02:04:45.319 --> 02:04:49.400
wind force equations,
calculated the cumulative wind

02:04:49.400 --> 02:04:51.530
that every piece of
equipment is experienced

02:04:51.530 --> 02:04:54.810
based on not just the speed of the wind,

02:04:54.810 --> 02:04:57.633
but the direction that the
wind was hitting the lines.

02:04:58.734 --> 02:05:00.170
We found that was that,

02:05:00.170 --> 02:05:03.490
that improved the model
accuracy by about 15%.

02:05:03.490 --> 02:05:04.850
So that's something that we brought in

02:05:04.850 --> 02:05:07.690
from an engineering
analysis, but on top of that,

02:05:07.690 --> 02:05:11.452
sometimes the
engineers find things that,

02:05:11.452 --> 02:05:14.170
that you can't pick
up in a model just yet.

02:05:14.170 --> 02:05:17.760
So for example, when you
read this, the WMP this year,

02:05:17.760 --> 02:05:20.693
you'll see there's two
activities that we put in there,

02:05:22.200 --> 02:05:23.620
I'll, I'll hit on one of them.

02:05:23.620 --> 02:05:25.610
It's called the vertical switches,

02:05:25.610 --> 02:05:29.010
a certain type of switch that overall

02:05:29.010 --> 02:05:32.370
the models tell us that
switches themselves

02:05:33.250 --> 02:05:37.350
aren't large, large drivers of ignitions

02:05:37.350 --> 02:05:39.740
when compared to other
things like conductor.

02:05:39.740 --> 02:05:41.870
Conductors create
many more opportunities

02:05:41.870 --> 02:05:43.570
for ignitions and our switches do.

02:05:44.510 --> 02:05:47.330
However, when the engineers went out

02:05:47.330 --> 02:05:50.350
to evaluate these switches,

02:05:50.350 --> 02:05:53.080
they found evidence of
incandescent particles

02:05:53.080 --> 02:05:54.978
on the, on the poles.

02:05:54.978 --> 02:05:59.978
So even though the, the
model itself didn't suggest that,

02:06:00.500 --> 02:06:04.365
that we should prioritize those,

02:06:04.365 --> 02:06:07.750
we also listened to the engineer
judgment and considered

02:06:07.750 --> 02:06:10.850
the cost versus benefit
of replacing this switch is,

02:06:10.850 --> 02:06:12.360
and how many were out there?

02:06:12.360 --> 02:06:15.484
And we put it in into
the WMP as a program,

02:06:15.484 --> 02:06:17.550
even though the RST might be,

02:06:17.550 --> 02:06:20.170
might look small compared
to the other things.

02:06:20.170 --> 02:06:23.270
So these, this engineering process,

02:06:23.270 --> 02:06:26.290
a root cause process that
we go through on every ignition

02:06:26.290 --> 02:06:28.610
provides a lot of value.

02:06:28.610 --> 02:06:30.080
I think to the broader question,

02:06:30.080 --> 02:06:32.280
you're asking if you're
a customer, you know,

02:06:32.280 --> 02:06:33.693
how do you feel confident?

02:06:34.620 --> 02:06:36.790
I think the main way
you feel confident is

02:06:36.790 --> 02:06:38.817
that when you read our MP,

02:06:38.817 --> 02:06:43.460
it's very clear that we're
taking a risk-informed approach

02:06:43.460 --> 02:06:45.200
on everything that we're doing.

02:06:45.200 --> 02:06:49.750
So if you live in a high fire
area, you're on our radar,

02:06:49.750 --> 02:06:52.690
because we're, we're, we're putting our,

02:06:52.690 --> 02:06:55.280
our resources at the locations

02:06:55.280 --> 02:06:56.683
where we see the most fires.

02:07:02.650 --> 02:07:04.116
<v Man>Thanks very much.</v>

02:07:04.116 --> 02:07:05.280
I'll hold off on other questions,

02:07:05.280 --> 02:07:08.770
but I would just say, hey,
just in terms of feedback,

02:07:08.770 --> 02:07:10.400
take it for what it's worth.

02:07:10.400 --> 02:07:15.400
If I lost my home,
because a C-hook failed,

02:07:16.220 --> 02:07:21.220
I would want to read in
this Wildfire Mitigation Plan

02:07:21.541 --> 02:07:26.541
where (indistinct) was addressed

02:07:26.570 --> 02:07:30.172
and where it is
accounted for in the plan,

02:07:30.172 --> 02:07:31.983
and then the assessment methodology.

02:07:33.005 --> 02:07:37.040
(muffled speaking), whatever that was,

02:07:37.040 --> 02:07:38.860
if I'm in that area,

02:07:38.860 --> 02:07:42.240
I would want to know where
that has been incorporated

02:07:42.240 --> 02:07:46.690
very specifically, mapped
exactly to where that is

02:07:46.690 --> 02:07:50.840
within the process and
where all of the causes

02:07:50.840 --> 02:07:54.670
of those catastrophic wildfires
have been incorporated

02:07:54.670 --> 02:07:56.132
into what you do.

02:07:56.132 --> 02:07:56.965
But with that all, I'll leave it there.

02:07:56.965 --> 02:07:57.920
Thank you very much.

02:07:58.860 --> 02:07:59.693
<v ->Let me, can I just,</v>

02:07:59.693 --> 02:08:02.900
I'll just throw one in the
C-hooks and C-hooks

02:08:02.900 --> 02:08:05.680
are, are what we found.

02:08:05.680 --> 02:08:09.310
We haven't, he hasn't
actually had a C-hook failure yet

02:08:09.310 --> 02:08:13.720
and cause a fire, but we
still went out and studied it.

02:08:13.720 --> 02:08:17.360
We did aerial inspections,
grabbed inspections.

02:08:17.360 --> 02:08:21.270
And what we found was
that this is another situation

02:08:21.270 --> 02:08:25.203
where the model wouldn't
suggest that C-hooks pose

02:08:25.203 --> 02:08:28.080
a large risk because
remember models are,

02:08:28.080 --> 02:08:30.040
are designed using historical data.

02:08:30.040 --> 02:08:32.155
So things haven't happened in the past,

02:08:32.155 --> 02:08:34.010
they're invisible to the model,

02:08:34.010 --> 02:08:35.530
the models can't predict something

02:08:35.530 --> 02:08:37.180
that hasn't happened in the past.

02:08:38.529 --> 02:08:40.610
But what, but what we
did do is we went out there

02:08:40.610 --> 02:08:43.630
and we looked at every
C-hook in our system

02:08:43.630 --> 02:08:46.190
and we realized that
because of the way C-hooks

02:08:46.190 --> 02:08:47.900
are designed and where they are,

02:08:47.900 --> 02:08:51.480
you really can't tell, you
can't get a good sense

02:08:51.480 --> 02:08:52.810
for when they're wearing out.

02:08:52.810 --> 02:08:57.800
It's really hard to see,
see visually where they are.

02:08:57.800 --> 02:09:01.230
But recognizing that, that, you know,

02:09:01.230 --> 02:09:04.019
there's evidence that
C-hooks can cause fires.

02:09:04.019 --> 02:09:06.920
We decided to put that into
the WMP and we're going to

02:09:06.920 --> 02:09:08.313
change out all our C-hooks.

02:09:11.290 --> 02:09:13.640
Joe, do you want to
comment on that one as well

02:09:15.254 --> 02:09:17.433
and just to uplift the
cause with, well, again,

02:09:17.433 --> 02:09:21.310
referring to something that
happened in PG and E system.

02:09:21.310 --> 02:09:23.758
C-hooks were something
that were on the radar

02:09:23.758 --> 02:09:27.361
and caused a catastrophic fire.

02:09:27.361 --> 02:09:30.820
What we've done is
incorporated that specific piece

02:09:30.820 --> 02:09:34.000
of equipment into our
inspection programs.

02:09:34.000 --> 02:09:35.530
And you can read about that.

02:09:35.530 --> 02:09:37.900
They are mentioned in
our Wildfire Mitigation Plan

02:09:37.900 --> 02:09:42.640
under these sections on
latter steel type structures

02:09:42.640 --> 02:09:44.810
that can utilize that piece of equipment

02:09:44.810 --> 02:09:48.010
is something that we're
looking at and examining

02:09:48.010 --> 02:09:49.973
our failure before it pers.

02:09:58.720 --> 02:10:00.853
<v ->Great, thank you for
that question wheel,</v>

02:10:00.853 --> 02:10:02.973
and thank you for the discussion.

02:10:03.830 --> 02:10:06.200
<v ->Next let's go to Melissa.</v>

02:10:06.200 --> 02:10:08.010
Do we have some questions from chat

02:10:08.010 --> 02:10:11.070
that we would like to bring forward?

02:10:11.070 --> 02:10:12.400
<v Melissa>We do.</v>

02:10:12.400 --> 02:10:13.940
I'll, I'll just respond briefly to that,

02:10:13.940 --> 02:10:17.250
to say that the WOC
we'll note that as well,

02:10:17.250 --> 02:10:19.840
in terms of how
information gets presented

02:10:19.840 --> 02:10:21.260
to the WMP is going further.

02:10:21.260 --> 02:10:23.263
So we'll take note of the comment.

02:10:24.620 --> 02:10:29.133
The first question
that I see is it's for SCE

02:10:30.030 --> 02:10:32.863
and it's for mild or Mel Gordon,

02:10:34.580 --> 02:10:36.932
a framework for
understanding financial impacts

02:10:36.932 --> 02:10:40.830
of PSPS to customers as mentioned,

02:10:40.830 --> 02:10:42.940
could you elaborate on that framework?

02:10:42.940 --> 02:10:44.930
And I'll add that if that's better held

02:10:44.930 --> 02:10:49.163
for the PSTs conversation,
we can wait until then.

02:10:50.480 --> 02:10:53.530
<v ->So this is Robert
that that is part of this,</v>

02:10:53.530 --> 02:10:58.250
this presentation, as I
said, we have, we built up

02:10:58.250 --> 02:11:00.430
the MARS-like framework for PSPS

02:11:00.430 --> 02:11:03.900
for so that it could be
stacked up with wildfire risk.

02:11:03.900 --> 02:11:06.060
And I'll just start by saying,

02:11:06.060 --> 02:11:09.320
we put out a metrics there
in the Wildfire Mitigation Plan.

02:11:09.320 --> 02:11:11.464
So I'm not saying
anything that's not already

02:11:11.464 --> 02:11:12.430
in the Wildfire Mitigation Plan,

02:11:12.430 --> 02:11:16.830
and that we intend to evolve
this significantly this year,

02:11:16.830 --> 02:11:18.470
as we prepare for, for both

02:11:18.470 --> 02:11:20.350
the 2022 Wildfire Mitigation Plan

02:11:20.350 --> 02:11:23.585
and the 2022 RAMP
filing that SEC has to file.

02:11:23.585 --> 02:11:27.480
So, as I mentioned, we
have safety, reliability,

02:11:27.480 --> 02:11:29.460
and financial, on financial side,

02:11:29.460 --> 02:11:34.053
we used a metric of $250
per customer meter per event.

02:11:34.960 --> 02:11:38.870
And that of course has been
married up with reliability,

02:11:38.870 --> 02:11:41.742
which is a metric of number
of minutes of interruption

02:11:41.742 --> 02:11:45.110
for each customer based
on how many customers are,

02:11:45.110 --> 02:11:47.890
are out for the
particular amount of time

02:11:47.890 --> 02:11:50.030
that is predicted, and then safety,

02:11:50.030 --> 02:11:52.665
which is a metric that is developed both

02:11:52.665 --> 02:11:54.090
for the X's functional needs adder

02:11:54.090 --> 02:11:56.120
and critical in structure
for adder, I mentioned,

02:11:56.120 --> 02:11:59.720
but also a, a look
back at historic outages,

02:11:59.720 --> 02:12:01.760
most particularly the Northeast blackout

02:12:01.760 --> 02:12:04.130
and the safety consequences permitted

02:12:04.130 --> 02:12:06.440
with interruption from that event.

02:12:06.440 --> 02:12:08.510
So hope that helps answer the question.

02:12:08.510 --> 02:12:10.783
All this is also described in our WMP.

02:12:13.720 --> 02:12:14.620
<v ->Okay, thank you.</v>

02:12:14.620 --> 02:12:15.520
Alan, back to you.

02:12:18.215 --> 02:12:19.330
<v ->Perfect, thanks, Melissa.</v>

02:12:19.330 --> 02:12:22.373
Next question here is
going to come from WST.

02:12:24.290 --> 02:12:27.153
Let's see here, do we
have any questions?

02:12:28.330 --> 02:12:30.270
All right, so this question is going

02:12:30.270 --> 02:12:32.490
to go for all three utilities here.

02:12:32.490 --> 02:12:36.160
So how are are different risk models

02:12:36.160 --> 02:12:39.420
used two different types of initiatives?

02:12:39.420 --> 02:12:43.100
So grid hardening versus
bench management?

02:12:43.100 --> 02:12:45.410
How is this implemented and how are

02:12:45.410 --> 02:12:47.223
the different risks aggregated?

02:12:53.620 --> 02:12:55.190
<v ->Assuming we're
following protocol</v>

02:12:55.190 --> 02:12:57.290
and PG and E goes
first on that one, Alan?

02:12:59.170 --> 02:13:00.290
<v ->Thanks, (indistinct).</v>

02:13:01.220 --> 02:13:02.490
<v ->I think that's a
great question.</v>

02:13:02.490 --> 02:13:04.099
And I think it deserves some,

02:13:04.099 --> 02:13:04.980
a little bit of discussion here.

02:13:04.980 --> 02:13:07.900
I'll try and be brief so that
I'm not monopolizing this

02:13:07.900 --> 02:13:09.760
conversation and allow my,

02:13:09.760 --> 02:13:12.163
my peers to give me
their point of view as well.

02:13:13.120 --> 02:13:15.393
As I described in in our presentation

02:13:15.393 --> 02:13:17.920
earlier this morning, and
I think we've done quite

02:13:17.920 --> 02:13:22.470
a good job in our WMP of
talking about this as well.

02:13:22.470 --> 02:13:26.930
We use the risk model to
examine historical events

02:13:26.930 --> 02:13:28.960
and predict future events.

02:13:28.960 --> 02:13:32.410
And from those
productions, we are looking

02:13:32.410 --> 02:13:34.509
at applying up-to-date knowledge.

02:13:34.509 --> 02:13:36.590
So when we build our risk models,

02:13:36.590 --> 02:13:41.590
we're looking at history
2015 to 2018 training data,

02:13:42.700 --> 02:13:45.400
2019, test data,
because this is all done

02:13:45.400 --> 02:13:48.590
in 2020 as 2020 was going on.

02:13:48.590 --> 02:13:50.860
And then what we want
to do is to start to pool

02:13:50.860 --> 02:13:55.710
in what happened in 2020
into that decision-making?

02:13:55.710 --> 02:13:59.450
So for example, and I know
my team later on tomorrow,

02:13:59.450 --> 02:14:02.100
we'll discuss system harming
and vegetation management

02:14:02.100 --> 02:14:03.480
in more detail.

02:14:03.480 --> 02:14:05.790
I'll let them handle
the specific questions,

02:14:05.790 --> 02:14:07.470
but at a high level.

02:14:07.470 --> 02:14:10.750
What we're doing at PG and
E is we're using the risk model

02:14:10.750 --> 02:14:14.010
to form where we should
be doing what we call

02:14:14.010 --> 02:14:15.700
enhanced vegetation management

02:14:15.700 --> 02:14:18.660
or system hardening projects

02:14:19.840 --> 02:14:23.010
to each of those,
we're adding the reality

02:14:23.010 --> 02:14:25.175
of what happens in 2020,

02:14:25.175 --> 02:14:29.830
whether that be rebuilds
at circuit modifications

02:14:29.830 --> 02:14:34.648
that were conducted, fire
rebuild for fires that occurred,

02:14:34.648 --> 02:14:38.570
or PSPS's de-energization
event and were included

02:14:38.570 --> 02:14:41.030
in the decision as to
what the best mitigation

02:14:41.030 --> 02:14:42.640
is going forward.

02:14:42.640 --> 02:14:45.440
We also prove that pool of our team

02:14:45.440 --> 02:14:47.400
called public safety specialists.

02:14:47.400 --> 02:14:52.260
These tend to be at fire
marshals, fire captain,

02:14:52.260 --> 02:14:54.980
people that have been
involved in the fire service

02:14:54.980 --> 02:14:57.330
at a local or a state level,

02:14:57.330 --> 02:15:00.470
and can help us advise
based on what they know of

02:15:00.470 --> 02:15:02.930
that particular area
and the consequences

02:15:02.930 --> 02:15:06.589
associated if a fire
were to start in that area.

02:15:06.589 --> 02:15:08.090
So we're using the model to inform

02:15:08.090 --> 02:15:09.680
and reinforcing it's practice

02:15:09.680 --> 02:15:12.163
based on subject matter expertise.

02:15:13.120 --> 02:15:16.630
On the vegetation side, we
do something very similar also,

02:15:16.630 --> 02:15:20.789
we also use the most recent LIDAR data

02:15:20.789 --> 02:15:22.860
that we collected in 2020, and use that

02:15:22.860 --> 02:15:25.130
to identify straight potential trees,

02:15:25.130 --> 02:15:28.929
which was the definition
that MRT asked for earlier on.

02:15:28.929 --> 02:15:30.824
That's basically actually that can,

02:15:30.824 --> 02:15:34.330
can fall in or limbs detach and blow in

02:15:34.330 --> 02:15:37.480
to one of our lines, either
distribution or transmission,

02:15:37.480 --> 02:15:39.390
we identify those trees.

02:15:39.390 --> 02:15:41.510
So the order of execution of

02:15:41.510 --> 02:15:44.670
some of our vegetation
management activities

02:15:44.670 --> 02:15:46.520
may be slightly different from the order

02:15:46.520 --> 02:15:48.840
in which is coming up
the risk model to take

02:15:48.840 --> 02:15:52.160
into account the most recent LIDAR data,

02:15:52.160 --> 02:15:56.003
identifying these hazard
trees or strike potential trees.

02:16:01.020 --> 02:16:01.900
<v ->I guess I'll go next.</v>

02:16:01.900 --> 02:16:03.353
I'll I'll give you there's,

02:16:03.353 --> 02:16:06.760
I'll give you three different
flavors of how the risk model

02:16:08.110 --> 02:16:10.513
influences where we do mitigations.

02:16:11.666 --> 02:16:14.480
So I'll start with Covered Conductor.

02:16:14.480 --> 02:16:18.973
Covered Conductor,
obviously it's, it's a,

02:16:19.955 --> 02:16:22.410
a fairly expensive mitigation that takes

02:16:22.410 --> 02:16:23.820
a lot of time for planning.

02:16:23.820 --> 02:16:27.840
It takes a long time
to construct, but it has,

02:16:27.840 --> 02:16:30.503
it has a bites down a lot of risks.

02:16:31.690 --> 02:16:36.690
It's something that
will be done by, by a,

02:16:37.021 --> 02:16:41.710
a crew or a set of crews over
the course of weeks or months

02:16:41.710 --> 02:16:44.670
to cover many miles at a time.

02:16:44.670 --> 02:16:49.350
For those, we would use
basically straight risk reduction

02:16:49.350 --> 02:16:50.350
out of the model.

02:16:50.350 --> 02:16:54.460
So we would rank every segment and, and,

02:16:54.460 --> 02:16:57.250
and for us a segment
is, is a piece of is a,

02:16:57.250 --> 02:17:01.190
as a section of a circuit
that can be isolated,

02:17:01.190 --> 02:17:04.557
typically, it's between two
pieces yeah, of equipment.

02:17:05.440 --> 02:17:09.650
The reason you do that
versus a span per span,

02:17:09.650 --> 02:17:12.990
and just go after the
highest risk spans is

02:17:12.990 --> 02:17:15.210
because that's not really
operationally feasible,

02:17:15.210 --> 02:17:16.530
just the way you construct it.

02:17:16.530 --> 02:17:19.110
When you build con Covered
Conductor, you go through many,

02:17:19.110 --> 02:17:22.083
many spans before you cut the conductor.

02:17:23.620 --> 02:17:24.790
So when something like that,

02:17:24.790 --> 02:17:28.235
we'll follow as close as
operationally feasible,

02:17:28.235 --> 02:17:31.233
the ranking of risk by segment.

02:17:32.511 --> 02:17:33.900
Another example though,

02:17:33.900 --> 02:17:37.010
would be something like
inspection, inspection is something

02:17:37.010 --> 02:17:41.847
that we, we we're gonna,
we're gonna in an accelerated

02:17:41.847 --> 02:17:44.770
and accelerated inspections
where we're doing it

02:17:44.770 --> 02:17:49.120
more frequently than as per compliance.

02:17:51.520 --> 02:17:52.450
We're going to look at it

02:17:52.450 --> 02:17:55.860
because it's less
expensive per inspection.

02:17:55.860 --> 02:17:58.890
We're going to look at it in terms of

02:17:58.890 --> 02:18:00.730
not just straight risk,

02:18:00.730 --> 02:18:03.337
but really making sure that weather

02:18:04.587 --> 02:18:06.780
and location is high consequence

02:18:06.780 --> 02:18:11.600
or high in probability, or
both, that we make sure

02:18:11.600 --> 02:18:14.040
we capture that every year, because,

02:18:14.040 --> 02:18:16.000
because it's less expensive.

02:18:16.000 --> 02:18:18.541
So you, you actually
get a better chance of,

02:18:18.541 --> 02:18:22.650
of going to every
asset that could either

02:18:22.650 --> 02:18:24.790
have high consequence
or high probability.

02:18:24.790 --> 02:18:27.870
So we designed, so the
values from the risk model go

02:18:27.870 --> 02:18:31.280
into a matrix and it's, and
different areas are broken

02:18:31.280 --> 02:18:35.600
down based on where
you sit in that matrix.

02:18:35.600 --> 02:18:38.730
So that's a different way
they use the risk model.

02:18:38.730 --> 02:18:42.674
A third way would be something
like removing hazard trees.

02:18:42.674 --> 02:18:43.520
Then it gets a little trickier

02:18:43.520 --> 02:18:48.520
because in something
that you do fairly regularly,

02:18:49.020 --> 02:18:53.090
you always have to
make that decision on.

02:18:53.090 --> 02:18:55.890
Can you cover, can you get more done

02:18:55.890 --> 02:18:57.630
even if the risk, the risk score

02:18:57.630 --> 02:19:00.930
isn't perfectly ranked
by grouping things

02:19:00.930 --> 02:19:04.000
in different areas for
operational reasons?

02:19:04.000 --> 02:19:06.830
So can you actually,
over a period of time,

02:19:06.830 --> 02:19:08.403
buy down more risk,

02:19:10.101 --> 02:19:13.445
by attacking things
locations versus bouncing

02:19:13.445 --> 02:19:15.650
around the highest risk tree,

02:19:15.650 --> 02:19:18.070
then the next highest risk tree,

02:19:18.070 --> 02:19:20.280
and then the next
highest risk risk tree.

02:19:20.280 --> 02:19:22.010
So in those cases, you would take the,

02:19:22.010 --> 02:19:23.908
the output of the risk model,

02:19:23.908 --> 02:19:27.420
and then you would
sort of figure it out really

02:19:27.420 --> 02:19:29.050
from an operational perspective,

02:19:29.050 --> 02:19:31.682
what's the best way
to bundle this work over

02:19:31.682 --> 02:19:33.810
the course of the year, to basically get

02:19:33.810 --> 02:19:37.760
as many of these trees done as possible.

02:19:37.760 --> 02:19:41.660
Even if say early in
the year, you're doing,

02:19:41.660 --> 02:19:43.910
you're removing a tree
that has a little bit lower risk

02:19:43.910 --> 02:19:46.440
than something you would
have done later in the year.

02:19:46.440 --> 02:19:48.590
And then there's other, other programs

02:19:48.590 --> 02:19:50.890
that are very important in vegetation

02:19:50.890 --> 02:19:55.080
where you do it, you
do it every year anyway,

02:19:55.080 --> 02:19:57.240
so any program where we're going

02:19:57.240 --> 02:20:00.763
to cover the whole territory,

02:20:01.850 --> 02:20:04.830
there's you, you
really don't pick up any,

02:20:04.830 --> 02:20:09.830
any value by trying to
fine tune that year schedule

02:20:10.760 --> 02:20:13.583
into a highest to lowest risk.

02:20:14.470 --> 02:20:17.410
It's better to do it in
the most efficient way,

02:20:17.410 --> 02:20:20.240
which is typically like
for trimming going straight

02:20:20.240 --> 02:20:22.210
down a circuit and
trimming, trimming, trimming,

02:20:22.210 --> 02:20:23.550
trimming like that,

02:20:23.550 --> 02:20:25.610
rather than trying to get so specific

02:20:25.610 --> 02:20:29.350
where you're going to do
this piece of it this week,

02:20:29.350 --> 02:20:31.203
and then that piece of it next week.

02:20:32.200 --> 02:20:33.730
So hopefully that answered the question.

02:20:33.730 --> 02:20:36.100
So essentially that, and
that's why I, you know,

02:20:36.100 --> 02:20:38.640
what I was saying is
why we built our model

02:20:38.640 --> 02:20:40.890
in a, in a very component fashion,

02:20:40.890 --> 02:20:44.300
because we realized that
every type of mitigation problem

02:20:44.300 --> 02:20:47.060
out there may need
to take a different angle

02:20:47.060 --> 02:20:48.983
at how to use, how to use a model.

02:20:53.380 --> 02:20:55.930
<v ->I'll take this one
for SDG and E.</v>

02:20:55.930 --> 02:20:57.910
So just bigger picture.

02:20:57.910 --> 02:21:00.980
We use the same multi
attribute value framework

02:21:00.980 --> 02:21:03.000
to evaluate all our programs.

02:21:03.000 --> 02:21:04.260
That's at a high level.

02:21:04.260 --> 02:21:06.040
And then as I mentioned
in our presentation,

02:21:06.040 --> 02:21:08.950
sometimes we'll come up
with more refined methodologies

02:21:08.950 --> 02:21:12.290
to help us prioritize
day-to-day activities

02:21:12.290 --> 02:21:14.919
and specific projects within programs.

02:21:14.919 --> 02:21:17.270
The information coming
out of those programs

02:21:17.270 --> 02:21:18.730
is fed back into the model.

02:21:18.730 --> 02:21:21.800
So for example, with
vegetation management,

02:21:21.800 --> 02:21:25.170
we have to look at little
more detail and specifics

02:21:25.170 --> 02:21:28.873
around a tree species
analysis to help us identify

02:21:28.873 --> 02:21:30.760
what the highest risk areas might be,

02:21:30.760 --> 02:21:32.260
and we go out and do the inspections

02:21:32.260 --> 02:21:33.940
and mitigations.

02:21:33.940 --> 02:21:36.060
Findings from vegetation management,

02:21:36.060 --> 02:21:38.820
such as identification of trees

02:21:38.820 --> 02:21:41.130
that have a potential
to strike our lines

02:21:41.130 --> 02:21:43.860
are fed back into our overall model

02:21:43.860 --> 02:21:45.720
to assess the segment level risk.

02:21:45.720 --> 02:21:48.620
Another example is the
WRRM model that we talked

02:21:48.620 --> 02:21:52.620
about where specific
asset risk is evaluated

02:21:52.620 --> 02:21:55.130
at an asset level, but
then it's also aggregated

02:21:55.130 --> 02:21:57.803
into this overall
segment level analysis.

02:21:58.770 --> 02:22:00.490
The last thing I wanted to just touch

02:22:00.490 --> 02:22:02.800
on is just emphasize
that we're continuing

02:22:02.800 --> 02:22:06.010
to evolve and looking
for better ways to do this.

02:22:06.010 --> 02:22:08.040
And I'll just re-emphasize
what I mentioned

02:22:08.040 --> 02:22:10.360
about WINGS being a modular model.

02:22:10.360 --> 02:22:13.470
So although we might
have specific models applied

02:22:13.470 --> 02:22:15.040
to address specific problems

02:22:15.040 --> 02:22:17.650
or help us target specific programs,

02:22:17.650 --> 02:22:20.580
the idea is that we can
feed that information

02:22:20.580 --> 02:22:22.850
back into WINGS
and continue to refine it

02:22:22.850 --> 02:22:26.300
so that it's taking into
account all these data points

02:22:26.300 --> 02:22:27.400
as we go through them.

02:22:32.340 --> 02:22:34.880
<v ->Great, thank you so
much for the answers.</v>

02:22:34.880 --> 02:22:36.423
Next, let's go to TURN.

02:22:39.070 --> 02:22:42.017
<v ->Hi, yes, this is Katie
Morsani from TURN,</v>

02:22:42.017 --> 02:22:44.223
and I have a question
for all the utilities.

02:22:45.519 --> 02:22:48.480
I think as the, the numbers attached

02:22:48.480 --> 02:22:51.590
to the Wildfire Mitigation
Plans demonstrate there's

02:22:51.590 --> 02:22:56.470
a lot of potential for rate
impacts coming out of

02:22:56.470 --> 02:22:59.720
the Wildfire Mitigation Plan approaches

02:22:59.720 --> 02:23:04.430
and did, did each of
the utilities and, and how,

02:23:04.430 --> 02:23:07.780
if you did include
constraints like affordability

02:23:07.780 --> 02:23:12.400
and eliminating cost
increases in their risk models,

02:23:12.400 --> 02:23:14.133
as they determined a plan.

02:23:23.150 --> 02:23:24.556
<v ->Hi Katie.</v>

02:23:24.556 --> 02:23:25.389
(crosstalk)

02:23:25.389 --> 02:23:26.550
<v Katie>I mean
affordability problems,</v>

02:23:26.550 --> 02:23:29.923
the rate payer perspective,
not the utility perspective.

02:23:32.580 --> 02:23:35.230
<v ->Hi, Katie, I think I
understand your question there</v>

02:23:36.964 --> 02:23:38.680
and I think, and please, excuse me,

02:23:38.680 --> 02:23:40.380
I'm relatively new to PG and E,

02:23:40.380 --> 02:23:43.070
so if I, if I don't get the
mission statement correct,

02:23:43.070 --> 02:23:45.070
and I may be merged
with another employer

02:23:45.070 --> 02:23:47.100
that I've worked
for, I think you'll find

02:23:47.100 --> 02:23:50.410
that each of the
utilities have a mission

02:23:50.410 --> 02:23:53.180
that incorporates the
word safe, reliable,

02:23:53.180 --> 02:23:57.460
and affordable power for its
customers and communities.

02:23:57.460 --> 02:24:00.220
And I believe that's something
that we are standing behind

02:24:00.220 --> 02:24:02.860
is something that we're
trying to make sure we do.

02:24:02.860 --> 02:24:05.120
However, in my current role,

02:24:05.120 --> 02:24:09.550
as the Electric Operations
Risk Management Director,

02:24:09.550 --> 02:24:14.550
my objective is in buying
down risk of wildfire and other

02:24:15.490 --> 02:24:19.720
public safety related issues associated

02:24:19.720 --> 02:24:22.620
with the public and our electric assets.

02:24:22.620 --> 02:24:25.660
So that doesn't mean I'm
not focusing on the dollars,

02:24:25.660 --> 02:24:29.400
but the focus for what we're
trying to do here is to reduce

02:24:29.400 --> 02:24:32.860
consequential ignitions from our system.

02:24:32.860 --> 02:24:35.990
Unfortunately, it does come
with a price, the system,

02:24:35.990 --> 02:24:39.000
hardening activities, whether
it be Covered Conductor,

02:24:39.000 --> 02:24:42.690
whether it be moving a
circuit to a different path,

02:24:42.690 --> 02:24:45.147
to feed a set of communities,

02:24:45.147 --> 02:24:48.890
it comes with a particular
cost, and those costs are

02:24:48.890 --> 02:24:52.220
spread across our
entire service territory.

02:24:52.220 --> 02:24:55.230
So the people in those
communities are not hitting,

02:24:55.230 --> 02:24:57.415
you know, being hit
with a premium for it.

02:24:57.415 --> 02:25:02.415
Our objective is public safety
and buying down that risk.

02:25:03.470 --> 02:25:05.960
And we are aware that
it comes with a price.

02:25:05.960 --> 02:25:09.810
We are doing our fiduciary
duty to our constituents and

02:25:09.810 --> 02:25:12.017
our rate payers to minimize that,

02:25:12.017 --> 02:25:15.317
but also to focus on
making our systems safe

02:25:15.317 --> 02:25:16.873
and reliable for the future.

02:25:21.760 --> 02:25:24.250
<v ->This is Robert from
SCE, very similar</v>

02:25:24.250 --> 02:25:25.653
to, to Paul's response.

02:25:25.653 --> 02:25:28.390
I'll just add that obviously,

02:25:28.390 --> 02:25:30.433
affordability is a very
important consideration

02:25:30.433 --> 02:25:33.610
for SCE generally, and
there's actually a non-bach

02:25:33.610 --> 02:25:35.340
I think coming up in
the next couple of days

02:25:35.340 --> 02:25:37.320
on this exact topic.

02:25:37.320 --> 02:25:40.440
For us, we do ensure
that what we're proposing is

02:25:40.440 --> 02:25:43.790
in line with our already
previously forecasted capital plans

02:25:43.790 --> 02:25:45.102
and spending plans.

02:25:45.102 --> 02:25:47.350
And of course, everything that we put

02:25:47.350 --> 02:25:49.280
in our Wildfire Mitigation Plan will

02:25:49.280 --> 02:25:53.680
be reviewed in a, in a
subsequent general rate case.

02:25:53.680 --> 02:25:56.040
All those are, are, I would say,

02:25:56.040 --> 02:25:57.900
are constraints that we're focused on,

02:25:57.900 --> 02:26:00.890
but like Paul we're primarily
focused on coming up

02:26:00.890 --> 02:26:04.363
with plans that will mitigate
risk efficiently and quickly.

02:26:10.430 --> 02:26:11.920
<v ->Echoing what Robert mentioned,</v>

02:26:11.920 --> 02:26:15.460
I think the application
of risks spend efficiencies

02:26:15.460 --> 02:26:18.880
to really inform our future
work inherently takes

02:26:18.880 --> 02:26:21.183
into account the issue of affordability.

02:26:21.183 --> 02:26:23.270
'Cause if we didn't have that capability

02:26:23.270 --> 02:26:26.120
to really target our projects,

02:26:26.120 --> 02:26:29.660
we might end up casting
a broad net where we want

02:26:29.660 --> 02:26:32.360
to mitigate things
based on the uncertainty.

02:26:32.360 --> 02:26:34.760
But I think just being able
to refine our methodology is

02:26:34.760 --> 02:26:36.760
really takes that into consideration.

02:26:36.760 --> 02:26:39.420
We're looking at good
projects to implement.

02:26:39.420 --> 02:26:41.700
And as I mentioned in my presentation,

02:26:41.700 --> 02:26:45.740
we even go back to see how
the new model validates things

02:26:45.740 --> 02:26:46.573
we've already done.

02:26:46.573 --> 02:26:49.740
And we do the efficacy
studies to make sure that that's

02:26:49.740 --> 02:26:51.200
driving us in the right direction.

02:26:51.200 --> 02:26:54.410
And just like the other
utilities mentioned,

02:26:54.410 --> 02:26:56.920
just echoing the
notion of public safety,

02:26:56.920 --> 02:26:58.650
being a priority for us.

02:26:58.650 --> 02:27:01.530
But again, RFCs are
really inherently helping us

02:27:01.530 --> 02:27:03.480
make sure that the projects we do

02:27:03.480 --> 02:27:05.033
maintain that affordability.

02:27:14.900 --> 02:27:17.630
<v Katie>I'll hold on my
next question until,</v>

02:27:17.630 --> 02:27:20.430
and the chance that I have
another chance to answer,

02:27:20.430 --> 02:27:21.273
ask questions.

02:27:23.930 --> 02:27:24.800
<v ->Thank you, Katie.</v>

02:27:24.800 --> 02:27:27.933
Let's go to Mussey Grade Road Alliance.

02:27:29.116 --> 02:27:31.553
<v ->Okay, this is Joseph Mitchell,
Mussey Grade Road Alliance.</v>

02:27:32.950 --> 02:27:37.950
You're everybody is training
on an analyzing risk events.

02:27:41.810 --> 02:27:46.810
The question it is for
data after 29th, 2019,

02:27:48.530 --> 02:27:53.530
and after, PSPS became
widespread for all utilities.

02:27:56.330 --> 02:28:01.330
So the data for ignitions
and to some extent,

02:28:02.310 --> 02:28:06.930
outages as well is highly
biased and have a different

02:28:06.930 --> 02:28:11.930
character for 2019 and
2020 versus what it was

02:28:12.370 --> 02:28:15.193
for 2015 through 2018.

02:28:16.750 --> 02:28:21.510
I noticed that PG and E
for instance is using 2019

02:28:21.510 --> 02:28:24.730
as it's a test data set,

02:28:24.730 --> 02:28:29.730
whereas it used 2015 through
2018 as its training data set.

02:28:29.940 --> 02:28:33.300
So this is going to
introduce some systematics.

02:28:33.300 --> 02:28:38.300
How far all utilities
adjusting for the bias

02:28:41.420 --> 02:28:46.420
that's being put into their
risk events sample by PSPS?

02:28:52.790 --> 02:28:54.680
<v ->Thank you, Joseph,
for that question.</v>

02:28:54.680 --> 02:28:57.198
I think that's, I think
that's a great question

02:28:57.198 --> 02:29:00.610
in that we have in our actions,

02:29:00.610 --> 02:29:04.090
we have changed the
landscape looking forward.

02:29:04.090 --> 02:29:06.140
And as each of the utilities goes

02:29:06.140 --> 02:29:08.620
through some hardening type activities,

02:29:08.620 --> 02:29:11.380
we're changing the existing landscape.

02:29:11.380 --> 02:29:13.380
We don't have a hardened system.

02:29:13.380 --> 02:29:15.970
It's something that PGD is incorporating

02:29:15.970 --> 02:29:17.690
into the human component,

02:29:17.690 --> 02:29:21.800
but we also have a plan to
update our models each year

02:29:21.800 --> 02:29:23.650
with more recent ignition data,

02:29:23.650 --> 02:29:25.143
as it becomes available.

02:29:26.150 --> 02:29:29.410
To talk about your
specific point, about PSPS.

02:29:29.410 --> 02:29:32.120
One of the things that
PG and E has been doing

02:29:32.120 --> 02:29:37.120
is collecting near or near data
with regard to PSPS events.

02:29:38.050 --> 02:29:40.100
So we had the most recently,

02:29:40.100 --> 02:29:41.730
and this is something I worked on,

02:29:41.730 --> 02:29:46.600
is we had the PSPS's
outage on January, 2021.

02:29:46.600 --> 02:29:50.060
And we had a number of
events on a number of circuits

02:29:50.060 --> 02:29:53.600
that were de-energized
for public safety.

02:29:53.600 --> 02:29:57.520
That then had strikes
from vegetation fly-ins

02:29:57.520 --> 02:30:00.087
or equipment damages, or what have you.

02:30:00.087 --> 02:30:02.350
And we collected those and treated those

02:30:02.350 --> 02:30:05.580
as near hit near miss type data

02:30:05.580 --> 02:30:09.230
for future inclusion
into our risk models.

02:30:09.230 --> 02:30:13.950
Because system harming
takes it time to, to be deployed,

02:30:13.950 --> 02:30:16.140
we are building our data set on that,

02:30:16.140 --> 02:30:18.310
on that type of that
failure of those type

02:30:18.310 --> 02:30:20.910
of failures are near misses, let's say,

02:30:20.910 --> 02:30:25.310
for the PSPS, we've got
a good data set from 2019

02:30:25.310 --> 02:30:26.800
and for 2020.

02:30:26.800 --> 02:30:28.500
I would like to go on record

02:30:28.500 --> 02:30:31.890
and say that we we'd like to
get a better data set for 2021.

02:30:31.890 --> 02:30:35.300
Our objective is to reduce PSPS events

02:30:35.300 --> 02:30:38.460
and reduce PSPS duration as well,

02:30:38.460 --> 02:30:43.170
but definitely by learning
from those near hit events

02:30:43.170 --> 02:30:44.500
and bringing them into our models

02:30:44.500 --> 02:30:46.003
as we go forward with updates.

02:30:54.640 --> 02:30:56.040
<v ->Joe, I think you're muted.</v>

02:31:00.030 --> 02:31:01.258
<v ->Sorry about that.</v>

02:31:01.258 --> 02:31:05.050
I wanted a clarification
on the question.

02:31:05.050 --> 02:31:09.190
When you said bias in
the model due to PSPS,

02:31:11.100 --> 02:31:13.270
is that because you're
saying that ignitions

02:31:13.270 --> 02:31:15.750
were avoided doing PSPS events,

02:31:15.750 --> 02:31:19.190
so they wouldn't be
captured in the model?

02:31:19.190 --> 02:31:21.610
<v Man>It's more biased
data, not bias model.</v>

02:31:21.610 --> 02:31:25.760
So the data is biased, your outages.

02:31:25.760 --> 02:31:26.833
Yeah, I think, okay.

02:31:26.833 --> 02:31:29.360
That's what I was saying,
I thought you meant by,

02:31:29.360 --> 02:31:30.680
so, so for our model,

02:31:30.680 --> 02:31:33.890
remember our model
is based off of outages

02:31:33.890 --> 02:31:35.360
that could create a spark.

02:31:35.360 --> 02:31:39.400
So the number of outages
that would take place

02:31:39.400 --> 02:31:42.110
during a PSPS event
in a short period of time

02:31:42.110 --> 02:31:45.770
on a limited number of
circuits is really dwarfed

02:31:45.770 --> 02:31:49.483
by the outages that we see
across our whole system.

02:31:50.450 --> 02:31:52.220
So we don't think that
it's going to have a,

02:31:52.220 --> 02:31:54.937
it would have what we lose in that,

02:31:54.937 --> 02:31:56.620
in those short time
periods, during PSPS events,

02:31:56.620 --> 02:32:00.450
we don't think it would have
very much impact on the output

02:32:00.450 --> 02:32:01.853
of the model in general.

02:32:02.850 --> 02:32:04.800
Does that, does that make sense to you?

02:32:06.640 --> 02:32:09.533
<v Joe>I'm skeptical, but I
understand what you're saying.</v>

02:32:13.150 --> 02:32:16.050
Hey Joe, this is a Mason with SDG and E,

02:32:16.050 --> 02:32:18.000
I obviously appreciate the question.

02:32:18.000 --> 02:32:20.830
That's something
that's been on our minds.

02:32:20.830 --> 02:32:22.640
For the general audience,

02:32:22.640 --> 02:32:23.950
maybe a, another way of saying it

02:32:23.950 --> 02:32:26.150
is if you're always
turning the power off

02:32:26.150 --> 02:32:28.440
when the wind is above 50 miles an hour,

02:32:28.440 --> 02:32:29.650
how do you know what's going to happen

02:32:29.650 --> 02:32:32.630
to your system if the wind
is about 50 miles an hour?

02:32:32.630 --> 02:32:34.390
So we're just trying to be smart

02:32:34.390 --> 02:32:35.430
about how to incorporate that.

02:32:35.430 --> 02:32:38.950
We obviously collect after
action reports after PSPS events

02:32:38.950 --> 02:32:42.690
to see if there was known
or suspected incidents

02:32:42.690 --> 02:32:44.777
that would have led to
an outage or technician.

02:32:44.777 --> 02:32:47.180
And we try to take that into account.

02:32:47.180 --> 02:32:49.190
I will say we were trying
to be smart about this,

02:32:49.190 --> 02:32:51.810
and I don't think we have an
exact answer of how to update

02:32:51.810 --> 02:32:54.070
the models, given
that we're working on it

02:32:54.070 --> 02:32:55.907
as we speak to try to make sure that

02:32:55.907 --> 02:32:58.390
the bias doesn't lead
us down the wrong path,

02:32:58.390 --> 02:33:01.530
which so often with
statistics biases do that.

02:33:01.530 --> 02:33:03.960
So we're just trying to be smart.

02:33:03.960 --> 02:33:06.630
And in fact, if anybody's
got any great ideas,

02:33:06.630 --> 02:33:08.800
I'd love to hear him
share with utilities

02:33:08.800 --> 02:33:10.903
and figure out what's
the best way forward.

02:33:13.753 --> 02:33:17.826
Thank you, everybody.

02:33:17.826 --> 02:33:18.659
<v ->Thank you, Joseph,</v>

02:33:18.659 --> 02:33:20.200
and we just have a few
more minutes left here.

02:33:20.200 --> 02:33:23.420
So do you think you'll
be asking the last question

02:33:23.420 --> 02:33:25.603
during this question and answer section?

02:33:28.915 --> 02:33:29.748
[Henry] Okay, thank you.

02:33:29.748 --> 02:33:31.860
This is Henry Burton with
Public Advocate's Office.

02:33:33.000 --> 02:33:35.590
We probably don't have
time for a long discussion,

02:33:35.590 --> 02:33:38.670
but hopefully we can
discuss this briefly.

02:33:38.670 --> 02:33:42.290
You've all talked about data
use and the methods you use

02:33:42.290 --> 02:33:45.803
to model wildfire probability
and consequences.

02:33:47.680 --> 02:33:51.260
Can you talk briefly about
how you are validating the model

02:33:51.260 --> 02:33:55.640
outputs to ensure that
the models are producing

02:33:55.640 --> 02:33:58.270
information that's really,
really a reliable guide

02:33:58.270 --> 02:33:59.533
to real world events.

02:34:01.750 --> 02:34:04.650
I know PG and E has talked
about testing with 2019 data.

02:34:04.650 --> 02:34:09.650
And one question I have there
is why 2019 and not also 2020,

02:34:10.090 --> 02:34:10.923
but more generally,

02:34:10.923 --> 02:34:14.120
I would like each of them
to tell you is to tell me just

02:34:14.120 --> 02:34:18.180
why, why we should have
confidence that the models

02:34:18.180 --> 02:34:21.863
are a reliable guide
to real-world events?

02:34:24.610 --> 02:34:25.443
<v ->Thank you, Henry.</v>

02:34:25.443 --> 02:34:27.033
I think that's a great question.

02:34:28.200 --> 02:34:30.750
Let me, let me first of all
handle the data question

02:34:30.750 --> 02:34:31.640
that you asked about,

02:34:31.640 --> 02:34:32.873
and then I'll go back
to the validation that.

02:34:32.873 --> 02:34:37.130
The data that we use
to, to train our models

02:34:37.130 --> 02:34:39.290
was 2015 to 2018.

02:34:39.290 --> 02:34:41.180
So that was observed data.

02:34:41.180 --> 02:34:44.820
And then we run the
simulations and after the model

02:34:44.820 --> 02:34:48.910
was trained and test it
on the 29 model a year

02:34:48.910 --> 02:34:52.127
where we had a full year
of observed outcomes.

02:34:52.127 --> 02:34:54.020
And we look at the combat that,

02:34:54.020 --> 02:34:57.295
and we look at the comparison
of prediction versus actual

02:34:57.295 --> 02:35:00.150
and develop our area
under the curve to test

02:35:00.150 --> 02:35:02.820
the effectiveness of our modeling.

02:35:02.820 --> 02:35:06.810
This was done in the year
2020, while 2020 was occurring,

02:35:06.810 --> 02:35:09.910
so we didn't have the
benefit of the 2020 data set.

02:35:09.910 --> 02:35:12.610
What we can do as we
go back as we start to give

02:35:12.610 --> 02:35:14.910
the model more information and we would

02:35:14.910 --> 02:35:19.820
then test them on, say
on 15, 16, 17, 18, and 19

02:35:19.820 --> 02:35:21.520
against the year 2020.

02:35:21.520 --> 02:35:23.750
2020 was an exceptional
year in that school.

02:35:23.750 --> 02:35:26.690
And so we might see some
deviations there, but again,

02:35:26.690 --> 02:35:29.420
we do have that capability to do so.

02:35:29.420 --> 02:35:32.140
With regards to
verification of the model,

02:35:32.140 --> 02:35:33.690
because this was a new model,

02:35:33.690 --> 02:35:36.930
it was something that PG
and E took very seriously.

02:35:36.930 --> 02:35:41.510
We worked with a number
of very smart people.

02:35:41.510 --> 02:35:44.640
PhD's from very good
universities, et cetera,

02:35:44.640 --> 02:35:48.010
to independently build
components of the model and then to

02:35:48.010 --> 02:35:50.760
test and verify parts of that model.

02:35:50.760 --> 02:35:54.630
And also, I believe it
was a condition of our,

02:35:54.630 --> 02:35:57.900
of our probation, in our WMP,

02:35:57.900 --> 02:36:01.223
we talk about independent
third party validation of

02:36:01.223 --> 02:36:03.310
a particular modeling approach.

02:36:03.310 --> 02:36:04.684
The company is called E3.

02:36:04.684 --> 02:36:08.190
I think it's environmental engineering,

02:36:08.190 --> 02:36:10.270
and I believe it's
something that's somebody

02:36:10.270 --> 02:36:12.730
that's familiar with the CPUC.

02:36:12.730 --> 02:36:15.430
I apologize for not having
the full name of their title,

02:36:15.430 --> 02:36:18.160
but it's something that we
committed to in our WMP

02:36:18.160 --> 02:36:20.940
for third party,
independent verification of

02:36:20.940 --> 02:36:22.190
how our model is working.

02:36:26.550 --> 02:36:28.860
<v ->And then for, for Edison,</v>

02:36:28.860 --> 02:36:31.653
very similar to the
way Paul described it.

02:36:33.090 --> 02:36:34.240
But when we build our models,

02:36:34.240 --> 02:36:37.720
we use five years of outage
data and the data is broken

02:36:37.720 --> 02:36:41.910
into test sets and training
sets, 80% for building

02:36:41.910 --> 02:36:44.970
the model, and then 20% for testing it.

02:36:44.970 --> 02:36:49.010
And these, these data
points are selected randomly.

02:36:49.010 --> 02:36:51.020
So you have, you have, you know,

02:36:51.020 --> 02:36:54.350
basically random
selection to create each,

02:36:54.350 --> 02:36:56.300
each of these buckets.

02:36:56.300 --> 02:36:58.980
The models go, and
then it's tested, you know,

02:36:58.980 --> 02:37:03.530
tested against that test set
and there's measurements

02:37:03.530 --> 02:37:08.520
that are machine-learning
models use to determine

02:37:08.520 --> 02:37:10.870
how accurate they are
and they give you values

02:37:10.870 --> 02:37:13.790
like you're familiar with,
with R squared values

02:37:13.790 --> 02:37:15.924
and regressions and things like that.

02:37:15.924 --> 02:37:17.860
They have those values as well,

02:37:17.860 --> 02:37:20.400
which give you a sense to start.

02:37:20.400 --> 02:37:22.070
Then what we do is we take that,

02:37:22.070 --> 02:37:24.650
that model that we built and,

02:37:24.650 --> 02:37:27.670
and trained against the test set,

02:37:27.670 --> 02:37:30.270
and we test it against a
full year of data as well.

02:37:30.270 --> 02:37:32.660
That that was completely
left out of building

02:37:32.660 --> 02:37:35.524
the model, to see how well it's done.

02:37:35.524 --> 02:37:38.450
Then on top of that, what we do is we,

02:37:38.450 --> 02:37:41.483
now that we've been using
the model for a couple of years,

02:37:42.570 --> 02:37:44.910
we can now look at actual events.

02:37:44.910 --> 02:37:46.910
So actual ignition events.

02:37:46.910 --> 02:37:51.910
So remember I was explaining
that that fire incident process

02:37:52.020 --> 02:37:53.570
where every time there's ignition,

02:37:53.570 --> 02:37:54.910
we record in the database,

02:37:54.910 --> 02:37:57.464
we gather information
engineer goes out there.

02:37:57.464 --> 02:38:01.130
So what we do is now we
have a database full of ignitions,

02:38:01.130 --> 02:38:03.110
recordables, and non recordables.

02:38:03.110 --> 02:38:06.339
And we've been able now to
test what was the probability of

02:38:06.339 --> 02:38:11.339
an ignition at each of those
locations to see where to check

02:38:11.890 --> 02:38:14.907
that the model is basically
directionally correct,

02:38:14.907 --> 02:38:16.203
and it's, and it's move,

02:38:17.099 --> 02:38:18.130
and it's identifying the areas

02:38:18.130 --> 02:38:19.630
that have the most likelihood.

02:38:25.426 --> 02:38:26.259
<v ->So for SDG and E,</v>

02:38:26.259 --> 02:38:28.783
there's a couple of things that we do

02:38:28.783 --> 02:38:30.723
to validate the models.

02:38:30.723 --> 02:38:31.556
The first thing that we do,

02:38:31.556 --> 02:38:33.260
there's kind of a
forward-looking validation

02:38:33.260 --> 02:38:34.470
versus a backward looking

02:38:34.470 --> 02:38:36.300
and I'll explain each of those.

02:38:36.300 --> 02:38:38.990
Forward-looking is when
we construct the model

02:38:38.990 --> 02:38:40.650
and we have our results.

02:38:40.650 --> 02:38:43.090
We go through multiple
sessions with our SMEEs

02:38:43.090 --> 02:38:44.650
to kind of look through the rankings,

02:38:44.650 --> 02:38:46.470
look through the areas of concern

02:38:46.470 --> 02:38:48.120
that the model is pointing us to.

02:38:48.120 --> 02:38:50.040
And based on their
knowledge of the outages,

02:38:50.040 --> 02:38:52.870
things that are happening
on the ground, they're,

02:38:52.870 --> 02:38:54.640
they're real knowledge of

02:38:54.640 --> 02:38:57.160
where the weather
patterns are more severe,

02:38:57.160 --> 02:38:59.570
they help us validate
and calibrate the model,

02:38:59.570 --> 02:39:03.070
And often we've found that we
were missing some data points

02:39:03.070 --> 02:39:06.250
that we then went back and
added and cleaned up the model.

02:39:06.250 --> 02:39:10.170
The other aspect of backward
looking this really comes

02:39:10.170 --> 02:39:12.580
into play when we're evaluating

02:39:12.580 --> 02:39:14.310
the effectiveness of mitigations.

02:39:14.310 --> 02:39:16.850
We haven't applied in
the past and may not have

02:39:16.850 --> 02:39:19.450
a lot of data around whether
or not they're effective

02:39:19.450 --> 02:39:22.055
or to what extent they're effective.

02:39:22.055 --> 02:39:26.210
So prior to conducting
our efficacy studies in 2020,

02:39:26.210 --> 02:39:29.770
we had estimated
effectiveness percentages

02:39:29.770 --> 02:39:32.280
for traditional hardening, for example.

02:39:32.280 --> 02:39:34.330
And now that we've had many years

02:39:34.330 --> 02:39:36.670
under our belt conducting the program,

02:39:36.670 --> 02:39:39.700
we're able to look
back at the ignition rates

02:39:39.700 --> 02:39:42.030
before and the ignition rates after,

02:39:42.030 --> 02:39:44.760
and we've actually adjusted
our estimates and calibrated

02:39:44.760 --> 02:39:47.810
the model to take into
account those actuals

02:39:47.810 --> 02:39:49.667
and findings from those studies.

02:39:49.667 --> 02:39:52.840
Tyson will go over that
study in a little bit more detail

02:39:52.840 --> 02:39:54.930
in the grid hardening panel.

02:39:54.930 --> 02:39:56.430
Amazing, anything else to add?

02:40:08.010 --> 02:40:08.843
<v ->No.</v>

02:40:13.340 --> 02:40:15.540
Great, thank you so
much for all the questions

02:40:15.540 --> 02:40:18.930
and, and the discussions
that we, that we just had.

02:40:18.930 --> 02:40:21.490
So now we will be taking lunch.

02:40:21.490 --> 02:40:26.490
We are going to resume at
1:30 PM and the next session

02:40:26.860 --> 02:40:28.780
is going to be vegetation management

02:40:28.780 --> 02:40:32.520
and Paula will be the
moderator for that session.

02:40:32.520 --> 02:40:36.120
So thank you everyone, and
have been the panelists, please,

02:40:36.120 --> 02:40:38.095
let's lower our hands and to,

02:40:38.095 --> 02:40:40.710
to prepare for the next next session.

02:40:40.710 --> 02:40:43.980
So we will resume at 1:30 PM.

02:40:43.980 --> 02:40:44.930
Thank you everyone.

02:40:46.110 --> 02:40:46.943
<v ->Thank you.</v>

02:40:51.440 --> 02:40:53.610
<v ->Okay, hello everyone.</v>

02:40:53.610 --> 02:40:58.253
I am reading 1:30,
so it is time to resume.

02:40:59.400 --> 02:41:00.890
My name is Colin Lang.

02:41:00.890 --> 02:41:04.420
I'm the Environmental
Scientist at the WSD.

02:41:04.420 --> 02:41:06.060
And today I have the pleasure

02:41:06.060 --> 02:41:08.263
of moderating 21 WMP updates.

02:41:15.080 --> 02:41:18.190
Vegetation management
can reduce both wildfire ignition

02:41:18.190 --> 02:41:19.990
and consequence risks.

02:41:19.990 --> 02:41:23.360
It involves planning for
both the canopy surrounding

02:41:23.360 --> 02:41:25.910
overhead lines and the understory

02:41:25.910 --> 02:41:28.250
in and around the right of way.

02:41:28.250 --> 02:41:30.970
Landscape structures
modified by colonization

02:41:30.970 --> 02:41:33.610
and our changing climate have
made vegetation management

02:41:33.610 --> 02:41:36.930
efforts challenging and
require land managers

02:41:36.930 --> 02:41:41.230
and utilities to constantly
adjust to the present,

02:41:41.230 --> 02:41:43.603
sometimes unprecedented conditions.

02:41:44.710 --> 02:41:46.810
Over the past few years,

02:41:46.810 --> 02:41:49.270
all of the utilities present
here today have increased

02:41:49.270 --> 02:41:53.080
the scale and scope of their
vegetation management programs

02:41:53.080 --> 02:41:55.523
to address these issues and many more.

02:41:57.430 --> 02:42:01.758
In the next hour, we'll hear
from PG and E and then FCE,

02:42:01.758 --> 02:42:02.591
and then SDG and E.

02:42:02.591 --> 02:42:05.520
So the order, seems to
be the order of the day

02:42:05.520 --> 02:42:08.062
about their vegetation management plans.

02:42:08.062 --> 02:42:12.107
This will be followed by a
short break and then a question

02:42:12.107 --> 02:42:16.150
and answer session panel this
afternoon with our presenters

02:42:16.150 --> 02:42:18.877
as well as key
stakeholders, and the WSD.

02:42:20.890 --> 02:42:23.890
First up, we have Steven
Fischer from PG and E,

02:42:23.890 --> 02:42:26.573
if you are ready, you can take it away.

02:42:31.650 --> 02:42:32.990
<v ->Yes, good afternoon, everyone.</v>

02:42:32.990 --> 02:42:34.600
My name is Steven Fischer.

02:42:34.600 --> 02:42:36.000
I'm a Director for PG and E,

02:42:36.000 --> 02:42:39.497
responsible for the execution
of our veg management grants.

02:42:39.497 --> 02:42:42.860
I actually participated
last year as a panelist

02:42:42.860 --> 02:42:45.573
representing PG and E for this panel.

02:42:50.548 --> 02:42:55.548
So, sorry, just let me get
used to this, how this looks.

02:42:55.946 --> 02:42:56.779
Can I...

02:42:59.370 --> 02:43:00.458
There we go, all right.

02:43:00.458 --> 02:43:01.291
Can we go to the first side of

02:43:01.291 --> 02:43:02.550
the presentation then, please?

02:43:03.890 --> 02:43:08.890
All right, so let me walk
through this presentation.

02:43:08.890 --> 02:43:12.350
So the first part of the is about

02:43:14.106 --> 02:43:18.610
the 2021 Wildfire Distribution
Risk Model and how we applied

02:43:18.610 --> 02:43:21.953
that to our enhanced
vegetation management program.

02:43:23.930 --> 02:43:26.940
In 2021, PCO will be using

02:43:26.940 --> 02:43:29.480
the 2021 Wildfire
Risk Distribution Model

02:43:30.379 --> 02:43:31.379
for its EVM program.

02:43:33.130 --> 02:43:38.130
We then enhanced this model
by overlaying existing LIDAR

02:43:38.270 --> 02:43:41.590
data that we've have as
well as the completed work

02:43:41.590 --> 02:43:45.308
from the past two years of
our completed EBM program to,

02:43:45.308 --> 02:43:50.253
to target the work in
the highest risk circuits.

02:43:51.860 --> 02:43:55.030
This risk model is based on 100-meter

02:43:55.030 --> 02:43:58.063
by a 100-meter risk
pixels that were generated.

02:43:59.960 --> 02:44:02.829
And each one has a risk
score associated to them

02:44:02.829 --> 02:44:07.829
due to the way the EBM
tool is that we use internally

02:44:07.960 --> 02:44:11.770
is run, those programs,
those pixels were reaggregated

02:44:11.770 --> 02:44:15.053
into approximately one
kilometer by one kilometer grid.

02:44:16.268 --> 02:44:18.660
That's a standard grid
used within PG and E

02:44:19.630 --> 02:44:22.093
for our tracking of our
completed EVM work.

02:44:25.100 --> 02:44:27.320
Any changes to the work plan this year,

02:44:27.320 --> 02:44:28.730
will need to go through a newly stood

02:44:28.730 --> 02:44:31.173
up Wildfire Risk Governance
Steering Committee.

02:44:32.470 --> 02:44:33.303
Throughout the year,

02:44:33.303 --> 02:44:36.223
there may be some
needs to change the risk,

02:44:37.326 --> 02:44:38.340
the targeted circuits that we're working

02:44:38.340 --> 02:44:40.953
for a variety of variety
of operational reasons.

02:44:42.560 --> 02:44:45.290
Prior to doing so, any changes will need

02:44:45.290 --> 02:44:48.590
to be approved by this
new Risk Governance

02:44:48.590 --> 02:44:52.350
Steering Committee that was
stood up at the end of 2020,

02:44:52.350 --> 02:44:54.500
and we'll govern all
our work through 2021.

02:44:55.876 --> 02:44:59.099
The EVM team within
PG and E is targeting

02:44:59.099 --> 02:45:02.480
to complete 80% of the
miles from the top 20%

02:45:02.480 --> 02:45:05.390
of the high-risk CPZ's, which stands for

02:45:05.390 --> 02:45:06.923
our Circuit Protection Zones.

02:45:08.086 --> 02:45:10.250
Basically the, the areas where a circuit

02:45:10.250 --> 02:45:11.763
can be switched on and off.

02:45:13.660 --> 02:45:16.700
So that's how we plan
on using the model and,

02:45:16.700 --> 02:45:18.250
and our ABM programs here.

02:45:18.250 --> 02:45:19.650
We can go to the next slide.

02:45:26.230 --> 02:45:29.360
Another pretty significant
change that we made

02:45:29.360 --> 02:45:32.240
that PG and E made this past year

02:45:32.240 --> 02:45:34.013
and we'll be seeing the impacts of,

02:45:35.174 --> 02:45:37.040
is our change to our
three contractor resources

02:45:37.040 --> 02:45:39.063
and the contract model we use with them.

02:45:40.630 --> 02:45:42.540
In the past few years,

02:45:42.540 --> 02:45:44.910
resources have been a major challenge.

02:45:44.910 --> 02:45:49.545
There's just not enough
qualified tree crews out there

02:45:49.545 --> 02:45:52.560
to perform the sheer amount
of work being performed

02:45:52.560 --> 02:45:53.940
in the state, not just at Fiji,

02:45:53.940 --> 02:45:56.841
but I think also at some
of the other utilities as well.

02:45:56.841 --> 02:46:00.320
And so we've been really
focusing on how to improve

02:46:00.320 --> 02:46:04.160
that workflow or that flow
of treat crew rock resources.

02:46:04.160 --> 02:46:08.887
So in 2021, we started
this in October of 2020.

02:46:08.887 --> 02:46:12.090
We shifted to what we call a
Defined Scope Contract Model,

02:46:12.090 --> 02:46:15.890
where instead of in the past PG and E

02:46:15.890 --> 02:46:17.967
would identify individual trees

02:46:17.967 --> 02:46:20.270
and then hand it
over to the contractors,

02:46:20.270 --> 02:46:23.680
what that led to who were
peaks and valleys in their work,

02:46:23.680 --> 02:46:26.010
which made it difficult
for them to maintain

02:46:26.010 --> 02:46:27.693
a consistent level of staffing.

02:46:28.700 --> 02:46:33.490
In this new model, the
contractors control the patrol cycle

02:46:33.490 --> 02:46:36.330
so that they can help to levelize their,

02:46:36.330 --> 02:46:38.600
their own workforce throughout the year.

02:46:38.600 --> 02:46:41.463
So it helps to avoid a lot
of those peaks and valleys.

02:46:42.720 --> 02:46:45.260
It also helps to give the contractor,

02:46:45.260 --> 02:46:48.385
the contractor aligned with
what PG and E's goals are

02:46:48.385 --> 02:46:52.440
by having them focus on, on
the compliance of the circuit,

02:46:52.440 --> 02:46:54.493
not just completing so many units.

02:46:55.340 --> 02:46:58.030
It was one of the things we
saw was as possible in the past

02:46:58.030 --> 02:46:59.930
that they completed their units,

02:46:59.930 --> 02:47:04.110
but the work wasn't done
successfully and didn't align well.

02:47:04.110 --> 02:47:05.410
So in this new model,

02:47:05.410 --> 02:47:09.750
it's more about ensuring
that the circuits are compliant

02:47:09.750 --> 02:47:12.890
with all the applicable
rules and regulations,

02:47:12.890 --> 02:47:16.820
so that if the contractor
is truly successful,

02:47:16.820 --> 02:47:20.090
it also translates to PG
and E being successful

02:47:20.090 --> 02:47:22.690
and also improve safety overall

02:47:22.690 --> 02:47:25.510
for the, the people of California.

02:47:25.510 --> 02:47:30.250
So this is going into effect
on our routine program,

02:47:30.250 --> 02:47:32.870
primarily, it doesn't have any impact

02:47:32.870 --> 02:47:35.863
on our EDM scope of work.

02:47:37.970 --> 02:47:38.920
Next slide, please.

02:47:42.010 --> 02:47:44.687
Another area of
improvement that PhDs made

02:47:44.687 --> 02:47:47.320
in the last year is the rollout

02:47:47.320 --> 02:47:49.720
of our tree assessment tool.

02:47:49.720 --> 02:47:51.400
The past, we used a different tool

02:47:51.400 --> 02:47:55.650
called the Hazard Tree Assessment Tool.

02:47:55.650 --> 02:47:57.150
We've updated that tool.

02:47:57.150 --> 02:48:00.140
We've made it simpler,
easier to understand.

02:48:00.140 --> 02:48:03.240
And also it's now
digital so that we collect

02:48:03.240 --> 02:48:06.390
the data as the program is going.

02:48:06.390 --> 02:48:09.480
So as part of our EDM program,

02:48:09.480 --> 02:48:11.600
we perform an inventory of all the trees

02:48:11.600 --> 02:48:13.696
that have striped potential
to a PG and E facility

02:48:13.696 --> 02:48:18.696
and each tree we'll get
a tree assessment tool.

02:48:19.990 --> 02:48:21.473
So a assessment of it.

02:48:22.350 --> 02:48:26.130
So what happens is our
pre inspectors are going out,

02:48:26.130 --> 02:48:29.563
they look at a tree, they're
asked a series of questions.

02:48:30.700 --> 02:48:35.110
If that question results in
a severe enough defect,

02:48:35.110 --> 02:48:37.690
that it results that it
removals part of the tool,

02:48:37.690 --> 02:48:42.500
instruct them, excuse me,
to remove the tool, the tree,

02:48:42.500 --> 02:48:44.343
or to market for removal.

02:48:45.500 --> 02:48:48.250
This tool takes into consideration

02:48:48.250 --> 02:48:51.440
tree species data based
on previous outages.

02:48:51.440 --> 02:48:54.520
So we, we are constantly looking,

02:48:54.520 --> 02:48:56.060
refreshing it with outage data.

02:48:56.060 --> 02:48:59.090
So as the, as we learn more from

02:48:59.090 --> 02:49:02.120
what causes a drives outages,
the tool is updated as well,

02:49:02.120 --> 02:49:04.240
so that those impacts are seen.

02:49:04.240 --> 02:49:07.220
So trees that are of
a higher risk species,

02:49:07.220 --> 02:49:11.990
get a higher rating
for removal than a tree

02:49:11.990 --> 02:49:16.990
that's less likely to be cause
of an ignition or an outage.

02:49:17.220 --> 02:49:19.600
Additionally, what
this tool does is take

02:49:19.600 --> 02:49:22.950
into consideration
weather patterns for the,

02:49:22.950 --> 02:49:25.610
the area that the work is being done in,

02:49:25.610 --> 02:49:27.400
specifically wind speed.

02:49:27.400 --> 02:49:30.740
We're looking to, it looks
to what environmental data

02:49:30.740 --> 02:49:34.820
we have on that area that
the person is working in

02:49:34.820 --> 02:49:38.540
and pulls in a wind
speed data for that way

02:49:38.540 --> 02:49:41.350
into the consideration
for potential removals

02:49:41.350 --> 02:49:43.730
of certain types of species.

02:49:43.730 --> 02:49:47.069
It also takes into
consideration terrain and slope,

02:49:47.069 --> 02:49:51.070
overall tree health, leave species.

02:49:51.070 --> 02:49:54.230
Those kinds of contributing
factors all drive this.

02:49:54.230 --> 02:49:59.230
And so this went into
effect in March of 2020,

02:49:59.450 --> 02:50:01.060
and will continue to be used

02:50:01.060 --> 02:50:03.630
in our Enhanced Vegetation
Management Program

02:50:04.510 --> 02:50:05.663
throughout 2021.

02:50:08.480 --> 02:50:09.380
Next slide please.

02:50:13.510 --> 02:50:18.510
So another area that we've
significantly expanded in going

02:50:19.180 --> 02:50:23.420
into 2021, is our Enhanced
Work Verification Program.

02:50:23.420 --> 02:50:28.420
So previously our we'd
sent out work verifiers.

02:50:28.440 --> 02:50:30.410
Those are kind of like a
quality assurance team,

02:50:30.410 --> 02:50:33.220
if you will, or a quality control team

02:50:33.220 --> 02:50:37.310
to check on the work being performed in

02:50:38.460 --> 02:50:41.120
by our contractors out in the field.

02:50:41.120 --> 02:50:43.500
We've increased the scope into 2021

02:50:43.500 --> 02:50:45.240
for Enhanced Vegetation Program.

02:50:45.240 --> 02:50:48.630
Now our inspectors will also fill out

02:50:48.630 --> 02:50:51.750
their own separate tree assessment tool

02:50:51.750 --> 02:50:54.740
on all the trees along our corridors

02:50:54.740 --> 02:50:56.560
that have strike potential.

02:50:56.560 --> 02:50:58.500
The idea behind this
is to make sure that

02:50:58.500 --> 02:51:03.500
we're getting consistent
data on the removal of trees.

02:51:03.600 --> 02:51:05.695
It's an area we've
gotten a lot of feedback,

02:51:05.695 --> 02:51:07.710
a lot of questions about.

02:51:07.710 --> 02:51:09.360
People, some people are concerned

02:51:10.633 --> 02:51:11.466
we're removing too many trees,

02:51:11.466 --> 02:51:13.840
others are not, or thinking
we're not removing enough.

02:51:13.840 --> 02:51:16.130
So by having a second set of eyes

02:51:16.130 --> 02:51:19.501
or second individual
perform the assessment,

02:51:19.501 --> 02:51:24.010
it'll drive to increase
level of consistency

02:51:24.010 --> 02:51:25.273
between those programs.

02:51:26.650 --> 02:51:31.270
Additionally, we're
expanding our work verification

02:51:31.270 --> 02:51:33.640
to our Routine Program as well.

02:51:33.640 --> 02:51:36.380
In the past I Routine Program had only

02:51:36.380 --> 02:51:38.263
a statistical sampling done,

02:51:39.410 --> 02:51:42.351
the high fire threat districts,

02:51:42.351 --> 02:51:46.160
now for all we'll be doing
100% work verification

02:51:46.160 --> 02:51:50.040
of all completed work and
all, all conductors in that,

02:51:50.040 --> 02:51:52.750
in that area, again,
with the ultimate goal

02:51:52.750 --> 02:51:56.780
of improving the overall
quality and consistency

02:51:56.780 --> 02:52:00.363
of the work as we see it
across the service territory.

02:52:03.920 --> 02:52:04.753
Next slide.

02:52:10.654 --> 02:52:13.890
Okay, so another thing that we realized,

02:52:13.890 --> 02:52:16.740
and we've had this in place since 2019,

02:52:16.740 --> 02:52:19.950
but we, we made some
streamlining effects to this

02:52:19.950 --> 02:52:24.290
is what we call our Priority
Tag Process, formerly

02:52:24.290 --> 02:52:29.290
it was known as a Hazard
Notification Procedure,

02:52:29.400 --> 02:52:31.750
and now we call these Priority Tags.

02:52:31.750 --> 02:52:33.840
And basically there's a Priority One

02:52:33.840 --> 02:52:36.070
and Priority Two type tags.

02:52:36.070 --> 02:52:39.840
Priority One tags are
reserved for tags that need

02:52:39.840 --> 02:52:42.390
to be mitigated
mitigated within 24 hours.

02:52:42.390 --> 02:52:47.070
So these an example
of this would be a tree

02:52:47.070 --> 02:52:50.020
that showed previous
contact with a conductor

02:52:50.020 --> 02:52:53.250
or a tree that in the
opinion of the individual

02:52:53.250 --> 02:52:56.390
who's out there
performing the work is in

02:52:56.390 --> 02:53:00.560
a state of actively failing
and could strike our facilities.

02:53:00.560 --> 02:53:02.480
This accelerated, these tags are done

02:53:02.480 --> 02:53:04.600
on their accelerated timeline.

02:53:04.600 --> 02:53:08.793
The tags are done within
24 hours of being identified,

02:53:11.314 --> 02:53:15.040
and we manage those to
completion with on a daily basis.

02:53:15.040 --> 02:53:16.140
The idea here is,

02:53:16.140 --> 02:53:20.280
is to put the highest risk trees
or the most dangerous trees

02:53:20.280 --> 02:53:23.250
up to the front of the queue constantly,

02:53:23.250 --> 02:53:28.080
so that they get worked
before they become a danger

02:53:28.080 --> 02:53:30.530
to, to people of California.

02:53:30.530 --> 02:53:34.640
So it's an accelerated
timeline, 24 hours.

02:53:34.640 --> 02:53:36.000
And they're identified

02:53:36.000 --> 02:53:38.450
by the, the veg management personnel

02:53:38.450 --> 02:53:39.983
who are working in the field.

02:53:41.320 --> 02:53:43.693
We also have a Priority Two tag.

02:53:44.530 --> 02:53:48.793
These are tags that are need
to be mitigated within 30 days.

02:53:49.920 --> 02:53:52.080
Most common occurrence
of these are instances

02:53:52.080 --> 02:53:56.040
where the vegetation is
within that four foot requirement

02:53:57.030 --> 02:54:00.860
for high fire threats or
18 inches for other areas.

02:54:00.860 --> 02:54:03.420
So if we're inside that compliance zone,

02:54:03.420 --> 02:54:05.520
we move these to the
front of the line as well,

02:54:05.520 --> 02:54:07.623
so that they get done
in accelerated pace.

02:54:09.107 --> 02:54:11.540
It's also possible for this type of tag

02:54:11.540 --> 02:54:15.840
to include trees that the,
the inspector has a concern.

02:54:15.840 --> 02:54:19.160
They may not last until a normal cycle

02:54:19.160 --> 02:54:21.904
for when our tree crews would get there.

02:54:21.904 --> 02:54:24.920
And so these are to be
done in an accelerated basis

02:54:24.920 --> 02:54:27.740
with a similar concept
of the Priority One's,

02:54:27.740 --> 02:54:31.640
with the emphasis on bringing
the most dangerous trees

02:54:31.640 --> 02:54:32.960
to the front of the line,

02:54:32.960 --> 02:54:34.960
so that they're getting worked actively.

02:54:37.010 --> 02:54:40.610
In the past, we had different timelines

02:54:40.610 --> 02:54:42.760
for in and out of fire season.

02:54:42.760 --> 02:54:44.690
We felt that that created
additional confusion,

02:54:44.690 --> 02:54:49.690
so we just aligned everything
to that same timeline,

02:54:49.960 --> 02:54:53.000
the goal being to make consistent.

02:54:53.000 --> 02:54:55.860
And the reality is, is
from our perspective,

02:54:55.860 --> 02:54:58.890
you know, if we think
the trees in risk of failure,

02:54:58.890 --> 02:55:01.880
we want to work at
sooner rather than later,

02:55:01.880 --> 02:55:04.383
regardless of whether
in high fire threat or not.

02:55:05.877 --> 02:55:09.960
So this is another area of
improvement to accelerate

02:55:09.960 --> 02:55:12.653
the work we do on
certain high-risk trees.

02:55:14.380 --> 02:55:15.330
Next slide, please.

02:55:18.960 --> 02:55:21.510
So another program
that we've been working

02:55:21.510 --> 02:55:23.787
on a little over a year now,

02:55:23.787 --> 02:55:28.080
and we're going to probably
do the most work here

02:55:28.080 --> 02:55:32.750
in 2021, is around our Utility
Defensible Space Program.

02:55:33.840 --> 02:55:37.310
This is very similar to the
kind of defensible space

02:55:37.310 --> 02:55:40.260
that CAL FIRE asks homeowners to do

02:55:40.260 --> 02:55:42.310
around their, their houses.

02:55:42.310 --> 02:55:44.430
We're looking to do something similar

02:55:45.270 --> 02:55:48.450
around our, our power
lines, with the idea,

02:55:48.450 --> 02:55:51.340
being that in the event of a failure,

02:55:51.340 --> 02:55:54.370
the line is more likely to
fail into a safe situation.

02:55:54.370 --> 02:55:57.670
So instead of falling on a underbrush,

02:55:57.670 --> 02:56:02.414
it'll fall onto more
maintained right away

02:56:02.414 --> 02:56:06.710
with the likelihood of either
preventing an ignition at all,

02:56:06.710 --> 02:56:10.000
or limiting the spread
or the rate of spread,

02:56:10.000 --> 02:56:13.400
allowing time for emergency,

02:56:13.400 --> 02:56:17.810
emergency personnel to
respond and be able to put out

02:56:17.810 --> 02:56:20.953
the, the fire before
it turns into a wildfire.

02:56:23.355 --> 02:56:25.380
As I said, it's, it's mirrored after

02:56:25.380 --> 02:56:27.490
the same kind of defensible
space requirements

02:56:27.490 --> 02:56:30.270
that you'll see around homes.

02:56:30.270 --> 02:56:35.270
So we're looking to remove
brush fuel underneath the lines,

02:56:36.580 --> 02:56:40.543
remove ladder fuels,
adjacent to the lines as well,

02:56:41.890 --> 02:56:44.570
and also remove some of
those higher risk vegetation

02:56:44.570 --> 02:56:49.090
that we know increase the spread of fire

02:56:49.090 --> 02:56:52.663
or very likely to, to
ignite in certain situations.

02:56:54.490 --> 02:56:56.360
Want to note that this is not

02:56:56.360 --> 02:56:59.530
a complete bare soil removal process.

02:56:59.530 --> 02:57:01.490
That's something PG
and E had tried in the past

02:57:01.490 --> 02:57:03.520
and met with quite a bit of resistance.

02:57:03.520 --> 02:57:05.120
It also has some negative impacts

02:57:05.120 --> 02:57:06.590
from an environmental standpoint.

02:57:06.590 --> 02:57:09.460
So we're looking at this from a,

02:57:09.460 --> 02:57:12.360
what is a sustainable
balance, if you will,

02:57:12.360 --> 02:57:15.660
between, you know,
going to the extreme of say,

02:57:15.660 --> 02:57:20.150
bare mineral soil to a more
of balanced approach of

02:57:20.150 --> 02:57:24.800
a more like a manicured
park style that would allow

02:57:24.800 --> 02:57:28.483
for still good environmental conditions?

02:57:30.330 --> 02:57:32.077
One thing we're still looking into,

02:57:32.077 --> 02:57:36.390
and we are working with our
internal environmental team,

02:57:36.390 --> 02:57:38.720
others outside would
be the application of

02:57:38.720 --> 02:57:41.963
a flame-retardant and or herbicides.

02:57:43.070 --> 02:57:44.970
The idea with the
flame retardant is kind of

02:57:44.970 --> 02:57:46.420
a proactive approach

02:57:46.420 --> 02:57:49.633
to prevent the fire from
igniting on the vegetation.

02:57:50.526 --> 02:57:52.770
We've seen this used quite successfully

02:57:52.770 --> 02:57:55.000
in various environment,

02:57:55.000 --> 02:57:59.360
in various fire situations
where flame-retardant is applied

02:57:59.360 --> 02:58:03.000
along poles and that
are in the potential path.

02:58:03.000 --> 02:58:05.150
And we've seen that
that works quite well.

02:58:05.150 --> 02:58:07.479
It's very effective to have it perfect,

02:58:07.479 --> 02:58:08.870
protecting the infrastructure.

02:58:08.870 --> 02:58:13.330
So we'd like to see the
same concept applied here,

02:58:13.330 --> 02:58:16.940
where the flame retardants
applied on the vegetation under

02:58:16.940 --> 02:58:21.540
or around the lines, preventing
them from igniting in a,

02:58:21.540 --> 02:58:24.190
in an event where wires are sparking

02:58:24.190 --> 02:58:26.607
to help prevent those ignitions.

02:58:28.280 --> 02:58:32.080
We're looking to do
some miles here in 2021.

02:58:32.080 --> 02:58:34.190
We're gonna model use the same

02:58:34.190 --> 02:58:36.150
Wildfire Distribution Risk Model

02:58:36.150 --> 02:58:38.500
that we are using for our
Enhanced Vegetation Program

02:58:38.500 --> 02:58:40.883
to target mileage.

02:58:41.990 --> 02:58:44.280
The amount of mileage done
is still going to be relatively

02:58:44.280 --> 02:58:46.790
small compared to some
of our other programs

02:58:46.790 --> 02:58:50.263
as we continue to test out
the feasibility of this program.

02:58:51.270 --> 02:58:54.070
We're also using this
program to work in combination

02:58:54.070 --> 02:58:57.900
with some local agencies,
including CAL FIRE,

02:58:57.900 --> 02:59:00.340
U.S. Forest Service,
and other municipalities

02:59:00.340 --> 02:59:03.750
for targeted fuel reduction programs

02:59:03.750 --> 02:59:05.913
in various communities around the state.

02:59:09.230 --> 02:59:11.730
So that's it for the
utility defensible space.

02:59:11.730 --> 02:59:13.433
We could go to the next slide.

02:59:24.150 --> 02:59:26.400
Actually, I think
that is the last slide.

02:59:26.400 --> 02:59:30.150
So with that, I think
that concludes the,

02:59:30.150 --> 02:59:31.530
my presentation for today.

02:59:31.530 --> 02:59:33.830
And I'll be available
for the Q and A portion.

02:59:36.560 --> 02:59:37.560
<v ->Thank you, Steven.</v>

02:59:39.110 --> 02:59:41.150
Next up we have Melanie Jocelyn

02:59:41.150 --> 02:59:42.650
of Southern California Edison.

02:59:57.160 --> 03:00:00.273
<v Colin>Melanie, if you were
speaking, you are on mute.</v>

03:00:05.870 --> 03:00:06.703
There we go.

03:00:09.813 --> 03:00:11.900
<v ->That's speaking button to tape.</v>

03:00:22.690 --> 03:00:24.550
<v Colin>Melanie, I heard
you there for a moment,</v>

03:00:24.550 --> 03:00:25.750
but you were very faint.

03:00:27.428 --> 03:00:28.261
<v Melanie>How about now?</v>

03:00:29.340 --> 03:00:31.990
<v Colin>That is, that
is a little better.</v>

03:00:31.990 --> 03:00:34.890
<v Melanie>Okay, I will also
try to speak up, that works.</v>

03:00:36.000 --> 03:00:37.560
<v Colin>Yes, thank you.</v>

03:00:37.560 --> 03:00:39.510
<v Melanie>Camera
button work as well.</v>

03:00:41.413 --> 03:00:43.093
Technology is not my friend today,

03:00:44.170 --> 03:00:45.470
but see me, you can hear me now.

03:00:45.470 --> 03:00:49.520
We can go ahead and
start off and move to the,

03:00:49.520 --> 03:00:52.770
the first content slide,
which is really orientation

03:00:52.770 --> 03:00:53.875
in review here are in terms of

03:00:53.875 --> 03:00:56.673
the topics we're going to review.

03:00:57.710 --> 03:01:01.290
High level high level review
of kind of the major categories

03:01:01.290 --> 03:01:06.290
of SCE's approach and
goals, some key changes,

03:01:06.400 --> 03:01:08.100
and then we'll go through

03:01:08.100 --> 03:01:11.030
a few more specific topics in detail.

03:01:11.030 --> 03:01:13.580
So with that, we can move
to the category overview.

03:01:17.460 --> 03:01:20.790
Okay, so, you know, fundamentally,

03:01:20.790 --> 03:01:22.640
I think we all understand
what we're trying to do here

03:01:22.640 --> 03:01:26.840
in terms of supporting
public safety and reliability

03:01:26.840 --> 03:01:28.573
by managing the vegetation,

03:01:29.720 --> 03:01:32.890
we're going to really
continue on a similar path,

03:01:32.890 --> 03:01:36.030
expanding some programs and initiatives.

03:01:36.030 --> 03:01:40.800
And then the specific
activities that we do in the field,

03:01:40.800 --> 03:01:44.150
include our Hazard Tree
Program and where we're planning

03:01:44.150 --> 03:01:48.040
to assess between
150,000 and 200,000 trees

03:01:48.040 --> 03:01:52.600
for 2021, and thereafter.

03:01:52.600 --> 03:01:55.590
And then we are performing
the timely mitigation associated

03:01:55.590 --> 03:01:59.540
with those, which are
typically within 180 days,

03:01:59.540 --> 03:02:01.160
Once we have the access and authority

03:02:01.160 --> 03:02:04.765
to remove or perform the mitigation.

03:02:04.765 --> 03:02:07.270
For our Dead and Dying
Tree Removal Program,

03:02:07.270 --> 03:02:09.940
we'll continue to do
patrols in that space.

03:02:09.940 --> 03:02:12.290
And similarly, we
have a similar structure

03:02:12.290 --> 03:02:14.760
for timely mitigation in that space.

03:02:14.760 --> 03:02:17.300
And then we're planning
to do our pole clearing

03:02:17.300 --> 03:02:20.030
or brushing around the base of

03:02:21.300 --> 03:02:23.680
between 200,000 and
300,000 district poles,

03:02:23.680 --> 03:02:26.260
distribution poles working our way up to

03:02:26.260 --> 03:02:29.763
the entirety of the
distribution poll population.

03:02:34.090 --> 03:02:35.890
When you can move to the next slide.

03:02:43.565 --> 03:02:44.720
Okay, apologies.

03:02:44.720 --> 03:02:47.470
The camera just really will
not let me hit that button.

03:02:48.790 --> 03:02:52.060
So some key program
changes here include are,

03:02:52.060 --> 03:02:54.767
are something that was
probably discussed this morning

03:02:54.767 --> 03:02:57.650
regarding risk overall,

03:02:57.650 --> 03:03:02.650
which is the companies move
from Reax to Technosylva.

03:03:04.200 --> 03:03:08.040
So the way that that takes
shape is by leveraging

03:03:08.040 --> 03:03:10.320
our Wildfire Risk Reduction Model,

03:03:10.320 --> 03:03:13.670
where we are applying risk
informed decision-making.

03:03:13.670 --> 03:03:15.410
So I am aware,

03:03:15.410 --> 03:03:19.420
I think there was an example
earlier regarding, you know,

03:03:19.420 --> 03:03:21.910
for work that we're
doing within the course of

03:03:21.910 --> 03:03:25.920
a single calendar year,
we still consider risk,

03:03:25.920 --> 03:03:30.450
but it's less necessary to, you know,

03:03:30.450 --> 03:03:33.590
because you're not excluding
anything from the population,

03:03:33.590 --> 03:03:36.530
the risk factors really come into timing

03:03:36.530 --> 03:03:38.360
within the course of the year.

03:03:38.360 --> 03:03:40.980
So where we are not actually looking

03:03:40.980 --> 03:03:44.340
or working everything
within a single calendar year,

03:03:44.340 --> 03:03:46.810
that would be hazard tree assessments.

03:03:46.810 --> 03:03:50.290
Our QC sampling
methodology is also dependent

03:03:51.160 --> 03:03:54.960
on risk modeling as well
as supplemental patrols,

03:03:54.960 --> 03:03:58.640
which are sometimes
called summer patrols

03:03:58.640 --> 03:04:00.850
where we're going getting one more look

03:04:00.850 --> 03:04:03.373
at an area before the time of the year

03:04:03.373 --> 03:04:05.273
when we have the most heightened risk,

03:04:06.817 --> 03:04:09.250
some other things that
we're doing this year

03:04:09.250 --> 03:04:12.450
that were not entertained
at the 2020 timeframe,

03:04:12.450 --> 03:04:16.603
we're developing an initial
Tree Risk Index Model.

03:04:17.450 --> 03:04:20.533
So that will be something
that's really tied to the WRRM.

03:04:21.826 --> 03:04:24.626
But we're looking for an
opportunity here where to apply

03:04:25.490 --> 03:04:28.580
tree-specific information
and basically marry up

03:04:28.580 --> 03:04:33.110
the information and our
tree database with the WRRM

03:04:33.110 --> 03:04:36.780
in a way that will help us better inform

03:04:36.780 --> 03:04:37.930
if there are opportunities

03:04:37.930 --> 03:04:41.260
to do inspection at different cycles

03:04:41.260 --> 03:04:45.154
or to adjust our trimming
distances accordingly.

03:04:45.154 --> 03:04:48.163
We're doing some
work on at-risk species.

03:04:49.530 --> 03:04:51.160
Specifically for 2021,

03:04:51.160 --> 03:04:56.160
we're focused on
palms of the top species

03:04:56.920 --> 03:05:00.830
that we have issues with,
palms are way up there.

03:05:00.830 --> 03:05:05.830
And so, because they
often require maintenance,

03:05:05.940 --> 03:05:08.210
three or even four times a year,

03:05:08.210 --> 03:05:10.670
in order to maintain public safety,

03:05:10.670 --> 03:05:13.660
we're looking to increase
the number of removals

03:05:13.660 --> 03:05:16.943
that we get for those
particular species.

03:05:18.380 --> 03:05:22.543
Something we started in
20, in fourth quarter of 2020.

03:05:23.500 --> 03:05:26.850
So it wasn't at the WMP
last year is an increased focus

03:05:26.850 --> 03:05:31.420
on quality and engaging with
our contractors accordingly.

03:05:31.420 --> 03:05:33.760
So we're feeding them
detailed information

03:05:33.760 --> 03:05:36.080
on their overall
performance that applies

03:05:36.080 --> 03:05:38.440
to both inspectors, as well as the folks

03:05:38.440 --> 03:05:40.330
performing the mitigation.

03:05:40.330 --> 03:05:42.810
And then we're giving, you know,

03:05:42.810 --> 03:05:45.430
having deep dives with
them regarding the state of

03:05:45.430 --> 03:05:48.520
that quality and working
with them on corrective actions

03:05:48.520 --> 03:05:52.263
on how they can do it or job
in either side of the equation.

03:05:54.470 --> 03:05:56.450
We're looking to explore,

03:05:56.450 --> 03:05:59.690
continue exploring
distribution LIDAR in a way

03:05:59.690 --> 03:06:02.169
that would align with trim cycles.

03:06:02.169 --> 03:06:06.170
So we had an opportunity in
2020 to do some experimentation

03:06:06.170 --> 03:06:07.200
with distribution LINAR,

03:06:07.200 --> 03:06:10.051
and leverage some data
that had been collected,

03:06:10.051 --> 03:06:13.900
but for a variety of reasons, it,

03:06:13.900 --> 03:06:17.960
it was challenging to do
the work in accordance

03:06:17.960 --> 03:06:21.100
with that our normal planned work.

03:06:21.100 --> 03:06:23.850
And so we're, we're trying
to see if we can come up

03:06:23.850 --> 03:06:27.030
with a way to advance that area

03:06:27.030 --> 03:06:29.570
and see if we can do a cost benefit,

03:06:29.570 --> 03:06:31.750
if it makes sense to keep pushing

03:06:31.750 --> 03:06:33.333
on the distribution LIDAR side.

03:06:34.440 --> 03:06:37.840
The final two items are
to an increase of public

03:06:37.840 --> 03:06:40.450
and agency engagement
regarding notification

03:06:40.450 --> 03:06:42.550
and trimming practices.

03:06:42.550 --> 03:06:47.020
That is really to speak
to a lot of customer angst

03:06:47.020 --> 03:06:48.633
about the work that we do.

03:06:49.620 --> 03:06:52.910
And COVID certainly COVID-19
has certainly heightened

03:06:52.910 --> 03:06:55.270
that experience for us in 2020.

03:06:55.270 --> 03:06:58.020
And we want to be working
more closely with the agencies

03:06:58.020 --> 03:07:00.620
so that when they hear
something from their customers,

03:07:00.620 --> 03:07:03.800
they have a solid foundation
in what we're doing,

03:07:03.800 --> 03:07:06.560
why we're doing it, how we're doing it,

03:07:06.560 --> 03:07:09.500
and so that they can help
back us up in convincing

03:07:09.500 --> 03:07:12.113
those customers to do
what's best for public safety.

03:07:13.100 --> 03:07:15.600
The final thing that we'll
are going to be doing is

03:07:15.600 --> 03:07:19.410
the implementation of our
work management system,

03:07:19.410 --> 03:07:24.000
which we should get
through significantly in 2021.

03:07:24.000 --> 03:07:25.970
And hopefully if all goes well,

03:07:25.970 --> 03:07:29.200
get that implemented
for all vegetation work

03:07:29.200 --> 03:07:31.283
in early 2022.

03:07:34.699 --> 03:07:35.749
Can you move on then?

03:07:39.770 --> 03:07:42.719
Okay, here's the overall strategy

03:07:42.719 --> 03:07:47.010
to put everything
into context, you know,

03:07:47.010 --> 03:07:49.630
fundamentally we're
trying to reduce or eliminate

03:07:49.630 --> 03:07:51.980
the risk of vegetation
to conduct your contact.

03:07:53.870 --> 03:07:58.300
And so the way that that
breaks down is that we want

03:07:58.300 --> 03:08:01.563
to keep working on
achieving enhanced clearance.

03:08:03.890 --> 03:08:06.160
Based on contractor data,

03:08:06.160 --> 03:08:11.114
we're getting that about
80% of the time right now.

03:08:11.114 --> 03:08:13.890
And so we want to keep
pushing the envelope on that and

03:08:13.890 --> 03:08:17.720
doing what we can to
work with all of the various

03:08:17.720 --> 03:08:20.200
constraints that that may apply to

03:08:20.200 --> 03:08:22.290
why we don't have that to date.

03:08:22.290 --> 03:08:26.550
The main reason for that
has to do with maintaining

03:08:26.550 --> 03:08:29.590
the distance for a full annual cycle.

03:08:29.590 --> 03:08:32.073
And this feeds into the next one

03:08:32.073 --> 03:08:35.120
where we can't maintain that clearance,

03:08:35.120 --> 03:08:37.300
we really want to focus on removals.

03:08:37.300 --> 03:08:39.522
So these are not,

03:08:39.522 --> 03:08:41.960
these are not changes
to the program per se.

03:08:41.960 --> 03:08:44.490
These are things that we're
continuing to push through

03:08:44.490 --> 03:08:47.580
and try to raise the
bar so that we actually

03:08:47.580 --> 03:08:52.070
are achieving this for more
and more trees every year.

03:08:52.070 --> 03:08:54.960
If we remove a tree
that can't maintain cycle

03:08:54.960 --> 03:08:59.250
for a full year, like
a palm, for example,

03:08:59.250 --> 03:09:01.180
that reduces the number
of visits we have to make

03:09:01.180 --> 03:09:02.970
to that customer's property.

03:09:02.970 --> 03:09:04.570
And, you know, hopefully also,

03:09:04.570 --> 03:09:06.270
even if they're not
happy about not having

03:09:06.270 --> 03:09:08.100
the tree at least, you know,

03:09:08.100 --> 03:09:11.610
provides them with some
increased customer service

03:09:11.610 --> 03:09:14.650
just by not having to
engage in that process

03:09:14.650 --> 03:09:16.890
with us multiple times.

03:09:16.890 --> 03:09:19.270
Finally, we want to remove trees

03:09:19.270 --> 03:09:21.580
that are fallen and blown and risks.

03:09:21.580 --> 03:09:24.544
And that is typically
characterized by our hazard tree

03:09:24.544 --> 03:09:29.288
and Dead and Dying Tree
Programs, those are the,

03:09:29.288 --> 03:09:32.033
it's not to say that we
don't ever remove a tree

03:09:32.033 --> 03:09:35.540
that would be a fallen risk
or an at-risk species closer

03:09:35.540 --> 03:09:37.860
to the right of way under
our routine program.

03:09:37.860 --> 03:09:41.550
But these two programs
are specifically inspecting

03:09:41.550 --> 03:09:43.920
for these characteristics where the tree

03:09:43.920 --> 03:09:45.910
is farther outside the right of way,

03:09:45.910 --> 03:09:49.533
and may not be caught
in our routine inspection.

03:09:51.680 --> 03:09:54.480
Okay, next in terms strategy,

03:09:54.480 --> 03:09:57.173
it goes back to that use of the WRRM.

03:09:58.100 --> 03:10:02.360
And as I already alluded
to in the previous slide,

03:10:02.360 --> 03:10:05.460
what we're trying to do is marry up the,

03:10:05.460 --> 03:10:09.540
the tree characteristics that
we already have knowledge of

03:10:09.540 --> 03:10:14.010
with the equipment and
risk consequence modeling

03:10:14.010 --> 03:10:17.680
so that we can put all
those pieces together

03:10:17.680 --> 03:10:22.680
and really drive to where
we have an opportunity

03:10:23.250 --> 03:10:28.023
to adjust our approach in
one area versus another.

03:10:29.550 --> 03:10:34.550
And then on the customer
side, we are really looking to,

03:10:34.590 --> 03:10:38.180
again, speak to that agency engagement,

03:10:38.180 --> 03:10:42.825
but also some direct customer outreach

03:10:42.825 --> 03:10:47.825
evaluating, hey, is our
process good enough?

03:10:48.250 --> 03:10:50.170
We know it's not always reaching folks.

03:10:50.170 --> 03:10:52.090
Is that just because they,

03:10:52.090 --> 03:10:54.707
they really don't believe in the risk?

03:10:54.707 --> 03:10:57.970
And is there anything else
that we can do to convince them,

03:10:57.970 --> 03:11:00.520
or are we failing in some capacity

03:11:00.520 --> 03:11:02.210
to make a compelling argument?

03:11:02.210 --> 03:11:04.130
And do we need to adjust that?

03:11:04.130 --> 03:11:09.130
Likewise, we're also looking
at expanding SCE's Voice

03:11:09.680 --> 03:11:13.280
of the Customer Survey
process to include vegetation

03:11:13.280 --> 03:11:17.150
so that we can create a
baseline of understanding of

03:11:17.150 --> 03:11:19.343
how most of our customers view our work.

03:11:22.660 --> 03:11:24.033
And we can move to the next slide then.

03:11:28.516 --> 03:11:31.016
Okay, in terms of inspections,

03:11:36.422 --> 03:11:39.100
we're doing the following activities.

03:11:39.100 --> 03:11:42.900
So these are very, very,
again, very much kind of factual.

03:11:42.900 --> 03:11:45.103
We have our routine line clearing.

03:11:46.200 --> 03:11:49.830
We're looking for
encroachments in this case,

03:11:49.830 --> 03:11:54.180
focusing on distribution
in our high fire areas,

03:11:54.180 --> 03:11:56.380
that would be anything that encroaches

03:11:56.380 --> 03:11:59.700
on that four foot minimum clearance.

03:11:59.700 --> 03:12:02.600
Then we have pole brushing
where we're inspecting

03:12:02.600 --> 03:12:04.510
the base of the poles, right?

03:12:04.510 --> 03:12:07.702
So it line clearing those
trees can be anywhere

03:12:07.702 --> 03:12:08.535
along the span.

03:12:08.535 --> 03:12:11.930
It's not tied to a specific
pole, so pole brushing,

03:12:11.930 --> 03:12:15.180
we're actually looking
at the equipment itself

03:12:15.180 --> 03:12:17.950
and we're clearing the vegetation really

03:12:17.950 --> 03:12:22.950
at the base in order to
reduce livable objects

03:12:23.060 --> 03:12:25.460
underneath in the event
of an equipment failure.

03:12:28.290 --> 03:12:31.530
Hazard Tree really looks,
as I already mentioned,

03:12:31.530 --> 03:12:34.110
further away from the right of way.

03:12:34.110 --> 03:12:38.900
And it is using a detailed process to

03:12:38.900 --> 03:12:42.816
score risk from certified arborists

03:12:42.816 --> 03:12:45.210
in their professional judgment,

03:12:45.210 --> 03:12:48.610
and look to what can
we do to mitigate that,

03:12:48.610 --> 03:12:51.570
that typically that
fall in or blow in risk

03:12:51.570 --> 03:12:55.083
from a large tree lands or palm prawns.

03:12:56.090 --> 03:12:58.840
The Dead and Dying Tree Program inspects

03:12:58.840 --> 03:13:02.929
a very specific subset of Hazard Tree.

03:13:02.929 --> 03:13:04.620
And this is the long standing one where

03:13:04.620 --> 03:13:07.840
the tree represents a
hazard because it has been,

03:13:07.840 --> 03:13:11.810
it's really so compromised
and its health it's going to die.

03:13:11.810 --> 03:13:14.000
And that, that increases the risk

03:13:14.000 --> 03:13:15.893
of that fall in or blow in.

03:13:17.490 --> 03:13:21.210
So LIDAR is really our
preference for transmission.

03:13:21.210 --> 03:13:24.090
That's been well
encapsulated in our program

03:13:24.930 --> 03:13:28.290
in terms of using that as
a primary reference point

03:13:28.290 --> 03:13:32.590
for determining what
represents an encroachment on.

03:13:32.590 --> 03:13:37.280
So we use the LIDAR to model
out maximum sag and sway,

03:13:37.280 --> 03:13:40.040
and clear accordingly
on transmission lines.

03:13:40.040 --> 03:13:44.807
And then I already addressed
LIDAR for distribution and,

03:13:44.807 --> 03:13:46.323
and how we're trying to evaluate that.

03:13:52.090 --> 03:13:54.363
Okay, you mentioned
the next slide, please.

03:13:58.870 --> 03:14:01.423
Finally, on our work management system.

03:14:02.450 --> 03:14:04.590
So this is a really key effort for us,

03:14:04.590 --> 03:14:08.080
and I think foundational
to the improvements

03:14:08.080 --> 03:14:10.660
that we'll make in ensuing years.

03:14:10.660 --> 03:14:13.890
We're trying to take numerous
digital tools and put them

03:14:13.890 --> 03:14:16.650
into a single platform
it's called our ARBORA.

03:14:16.650 --> 03:14:21.010
And really there's a lot
of benefits to it in terms of

03:14:21.010 --> 03:14:24.730
the efficiency, ability
to apply risk modeling,

03:14:24.730 --> 03:14:25.793
communication.

03:14:27.040 --> 03:14:28.880
And I won't read through all of them.

03:14:28.880 --> 03:14:30.923
Scheduling is a big one.

03:14:31.950 --> 03:14:35.640
And I'll just pause here
just to highlight a little bit,

03:14:35.640 --> 03:14:38.450
trying to manage the work as we do today

03:14:38.450 --> 03:14:41.080
in different tools is, you know,

03:14:41.080 --> 03:14:43.563
it allows us to get the
work done, no question.

03:14:44.510 --> 03:14:48.750
What it does not do is
allow us to optimize it,

03:14:48.750 --> 03:14:52.960
such that we can see all
of the various types of work

03:14:52.960 --> 03:14:55.650
that may be happening in if you want

03:14:55.650 --> 03:14:57.920
to imagine a given
neighborhood block, right?

03:14:57.920 --> 03:15:00.170
So if you have a hazard tree
that needs to be removed there,

03:15:00.170 --> 03:15:02.830
maybe you have a dead and dying tree.

03:15:02.830 --> 03:15:05.120
Maybe you have some routine line work.

03:15:05.120 --> 03:15:09.341
Maybe you have an emergent
work to address an encroachment,

03:15:09.341 --> 03:15:11.210
each of those things today,

03:15:11.210 --> 03:15:13.400
is maybe a pole to be brushed, right?

03:15:13.400 --> 03:15:15.980
Each of those things
today is in its own system.

03:15:15.980 --> 03:15:19.260
And so they are managed simultaneously

03:15:19.260 --> 03:15:21.560
and linearly linearly.

03:15:21.560 --> 03:15:24.910
And so we are anticipating
the ability to see all of

03:15:24.910 --> 03:15:29.210
that work in one system
will drive a lot of efficiency

03:15:29.210 --> 03:15:33.069
as well as better data
analytics and understanding

03:15:33.069 --> 03:15:38.069
of what's happening to those
trees, so that we can again,

03:15:38.720 --> 03:15:40.470
use that information to drive

03:15:40.470 --> 03:15:43.230
the program forward in its maturity.

03:15:43.230 --> 03:15:48.080
So this platform that our BORE
is based on is cloud-based,

03:15:48.080 --> 03:15:51.632
it's got it orchestrates, the processes,

03:15:51.632 --> 03:15:56.632
automates things on a, in a mobile tool,

03:15:56.960 --> 03:16:00.420
and then puts everything
into a single repository.

03:16:00.420 --> 03:16:03.130
And so that's also going to
help with that engagement

03:16:03.130 --> 03:16:04.270
with the customer.

03:16:04.270 --> 03:16:08.670
I heard about the efficiency,
but we also see, you know,

03:16:08.670 --> 03:16:10.930
it'll be ultimately a better way

03:16:10.930 --> 03:16:12.540
to able to communicate to a customer.

03:16:12.540 --> 03:16:14.610
Here's all the things
that's happening here,

03:16:14.610 --> 03:16:18.160
as well as our agencies
on the regulatory side,

03:16:18.160 --> 03:16:20.690
as well as the CPUC, you know, hey,

03:16:20.690 --> 03:16:23.000
here's all the work in one location.

03:16:23.000 --> 03:16:26.355
And so we're doing this
as a phased approach.

03:16:26.355 --> 03:16:30.160
And, you know, the
idea is to get significantly

03:16:30.160 --> 03:16:35.160
through the work of
implementation by the end of this year

03:16:35.341 --> 03:16:39.320
and wrap up in the
first half of next year,

03:16:39.320 --> 03:16:42.560
but we are doing it as this
phased approach so that we

03:16:42.560 --> 03:16:46.530
can prove it out for successive
programs and functionality

03:16:46.530 --> 03:16:47.940
before we push to the next one,

03:16:47.940 --> 03:16:51.910
because it's so critical that each,

03:16:51.910 --> 03:16:53.510
that the whole thing
is successful, right?

03:16:53.510 --> 03:16:56.063
And we need to make sure that our, what,

03:16:56.063 --> 03:16:59.320
1,500-plus users in the field, you know,

03:16:59.320 --> 03:17:02.070
really kind of embrace and
use this tool appropriately.

03:17:04.020 --> 03:17:07.417
So, it's being started in our
Dead and Dying Tree Program,

03:17:07.417 --> 03:17:12.417
and we are going to be
pushing that through and testing it

03:17:13.250 --> 03:17:15.113
in our Hazard Tree Program next.

03:17:18.943 --> 03:17:19.776
And this may well be the last slide.

03:17:19.776 --> 03:17:20.853
Is there one more?

03:17:23.753 --> 03:17:24.586
Okay, thank you.

03:17:28.220 --> 03:17:29.100
<v Colin>Thank you, Melanie.</v>

03:17:29.100 --> 03:17:31.310
You came in loud and
clear the entire presentation.

03:17:31.310 --> 03:17:32.893
So appreciate you speaking up.

03:17:33.810 --> 03:17:35.240
Next, last but not least,

03:17:35.240 --> 03:17:39.293
we have Michael and Tyson
from San Diego Gas and Electric.

03:17:43.426 --> 03:17:44.320
<v Michael>Good
afternoon, thank you.</v>

03:17:44.320 --> 03:17:47.730
My name is Michael (indistinct) or SDG,

03:17:47.730 --> 03:17:51.510
and I'll be taking you through
SDG and E's approach,

03:17:51.510 --> 03:17:55.570
risk mitigation, as it pertains
to vegetation management.

03:17:55.570 --> 03:18:00.516
We'll be joined on the last
slide with Tyson Swedek,

03:18:00.516 --> 03:18:03.184
who was our Director of Operations.

03:18:03.184 --> 03:18:06.590
And they'll give you more
detail about one of the analysis

03:18:06.590 --> 03:18:09.290
that we did in conjunction
with our risk mitigation

03:18:09.290 --> 03:18:13.788
that are having to use to are.

03:18:13.788 --> 03:18:18.121
So without going to get
started, next slide, please.

03:18:20.670 --> 03:18:24.290
Contextual slides and put us
in perspective as SDG and E.

03:18:24.290 --> 03:18:28.260
We track about 457,000
of inventory trees

03:18:28.260 --> 03:18:30.924
within our, our system.

03:18:30.924 --> 03:18:34.000
And by tracking, we
mean, we actually document

03:18:34.000 --> 03:18:37.250
and keep records of all of those trees.

03:18:37.250 --> 03:18:40.580
Every single time a
tree is either inspected

03:18:40.580 --> 03:18:43.090
or trimmed or audited.

03:18:43.090 --> 03:18:47.160
Rich, robust data set allows

03:18:47.160 --> 03:18:49.791
to look historically what's found

03:18:49.791 --> 03:18:51.480
and what we may have to do,

03:18:51.480 --> 03:18:53.680
make sure until
mitigating any (indistinct).

03:18:55.340 --> 03:18:58.750
Just geographically, we
divide our service territory,

03:18:58.750 --> 03:19:03.750
vegetation management
areas, which are 133 of those.

03:19:03.750 --> 03:19:07.130
And we obviously can
maintain compliancy around it

03:19:07.130 --> 03:19:09.690
to avoid any outages or fires.

03:19:09.690 --> 03:19:13.673
We have to follow a very
specific, specific master schedule.

03:19:14.510 --> 03:19:16.230
So this is an activity schedule.

03:19:16.230 --> 03:19:19.190
All of our activities are contingent

03:19:19.190 --> 03:19:20.580
on the one that proceeds it.

03:19:20.580 --> 03:19:24.400
So inspection, auditing,
trimming, auditing,

03:19:24.400 --> 03:19:25.956
and pole brushing.

03:19:25.956 --> 03:19:27.246
These all together,

03:19:27.246 --> 03:19:29.373
make up all of our
vegetation management.

03:19:31.790 --> 03:19:35.170
And overall about 54% of our,

03:19:35.170 --> 03:19:39.440
some of our overhead
total system line miles

03:19:39.440 --> 03:19:41.520
are within the HR 2D.

03:19:41.520 --> 03:19:45.323
That's about 60% of our
geographical territory is

03:19:45.323 --> 03:19:47.053
with the nature of today.

03:19:47.991 --> 03:19:49.900
So we are obviously
pretty challenged to ensure

03:19:49.900 --> 03:19:52.560
that we are mitigating those hazards.

03:19:52.560 --> 03:19:56.447
We are enabling the front
end to assuming we're not going

03:19:56.447 --> 03:19:59.047
to have any trees or be
contacting our (indistinct).

03:20:00.450 --> 03:20:01.380
Like the other two utilities,

03:20:01.380 --> 03:20:04.470
we have engaged trying to adopt

03:20:04.470 --> 03:20:07.670
and adapt maximum
clearances, maximum clearances

03:20:07.670 --> 03:20:08.660
wherever possible.

03:20:08.660 --> 03:20:11.780
So we defined as enhanced clearances

03:20:11.780 --> 03:20:15.330
or anything that's
greater than 12 feet up to,

03:20:15.330 --> 03:20:18.060
and including a clearance
that basically mitigate

03:20:18.060 --> 03:20:20.883
any tree regardless
of where it is relative.

03:20:22.410 --> 03:20:24.770
And then that last graphic
is just give you an example,

03:20:24.770 --> 03:20:28.340
how many trees in 2020
that we trim and the HFTD,

03:20:29.191 --> 03:20:30.273
and without the outage?

03:20:31.950 --> 03:20:33.077
Next slide please.

03:20:38.458 --> 03:20:40.880
Well with regard to
our inspection activities,

03:20:40.880 --> 03:20:43.074
they do have other utilities.

03:20:43.074 --> 03:20:45.293
We have a specific contractor
who performs this function.

03:20:45.293 --> 03:20:47.460
We have one trained special contractor

03:20:47.460 --> 03:20:50.103
who does our risk faction activity.

03:20:51.030 --> 03:20:56.030
We in 2020, have added on
four new internal SDG inspectors.

03:20:56.410 --> 03:20:58.390
So this is brand new for the company.

03:20:58.390 --> 03:21:00.780
You actually bring on employees,

03:21:00.780 --> 03:21:03.350
employees who are
performing this function,

03:21:03.350 --> 03:21:07.630
like our inspectors, who
do our HWD inspection,

03:21:07.630 --> 03:21:10.670
using individuals are
also certified our risks.

03:21:10.670 --> 03:21:13.630
So they will be
engaged to do all of our,

03:21:13.630 --> 03:21:16.060
we call our off cycle inspections

03:21:16.060 --> 03:21:20.060
in the age of 2D and our special patrols

03:21:20.060 --> 03:21:23.223
would our palm and our bamboo patrol.

03:21:24.074 --> 03:21:26.150
So these are, these are
trees along with central plant,

03:21:26.150 --> 03:21:29.390
these are species that
we have difficulty managing

03:21:29.390 --> 03:21:32.890
because of their unpredictable
nature, road pattern,

03:21:32.890 --> 03:21:35.123
and also they just posted fast.

03:21:36.219 --> 03:21:38.520
So we do actually off cycle inspections.

03:21:38.520 --> 03:21:41.573
And the HFPV when
these, these specialties.

03:21:44.920 --> 03:21:49.060
Look at our entire HF to
be at least twice a year,

03:21:49.060 --> 03:21:52.927
that's just to ensure that
we've looked at the HF today,

03:21:52.927 --> 03:21:54.940
and if anything's changed since

03:21:54.940 --> 03:21:57.340
the routine inspection activity,

03:21:57.340 --> 03:22:00.150
then we can mitigate that before

03:22:00.150 --> 03:22:02.246
the (indistinct) fire season.

03:22:02.246 --> 03:22:04.170
And for us, obviously
fire seasons year round,

03:22:04.170 --> 03:22:07.430
but the most critical
time is in the fall through

03:22:07.430 --> 03:22:11.033
the winter time, which we
have our static condition.

03:22:12.720 --> 03:22:15.530
We're going to continue
these post-term clearances.

03:22:15.530 --> 03:22:18.050
We find that as the most effective

03:22:18.050 --> 03:22:22.310
and our application of
that consists of blindness

03:22:22.310 --> 03:22:24.170
or will be called targeted species.

03:22:24.170 --> 03:22:27.960
So we have five targeted
species that based

03:22:27.960 --> 03:22:30.770
on historical contacts,

03:22:30.770 --> 03:22:34.260
known propensity for species failure,

03:22:34.260 --> 03:22:36.570
growth potential, and outage history

03:22:36.570 --> 03:22:39.323
that these trees are the
most difficult to manage.

03:22:39.323 --> 03:22:43.580
So really trying to focus our
enhanced clearances that is up

03:22:43.580 --> 03:22:47.520
to, and including those
20 to 25 feet and greater,

03:22:47.520 --> 03:22:50.070
those trees with the
known history of (indistinct).

03:22:52.494 --> 03:22:55.660
We also last year immigrated
and inspection and our agent

03:22:55.660 --> 03:22:59.648
to view, to look at all
secondary facilities.

03:22:59.648 --> 03:23:02.958
So that includes not
only open wire secondary,

03:23:02.958 --> 03:23:05.040
but also triplex construction,

03:23:05.040 --> 03:23:08.373
do not the propofol HFTD portion.

03:23:10.700 --> 03:23:12.520
Lastly, last year, we,

03:23:12.520 --> 03:23:16.087
we began an integration
with working with some of

03:23:16.087 --> 03:23:19.900
the local colleges to develop
some curriculum specific,

03:23:19.900 --> 03:23:24.310
to live a life learns, tree
trimming contractors,

03:23:24.310 --> 03:23:26.840
and all sorts of
pre-inspection contractors.

03:23:26.840 --> 03:23:30.640
We built more professionalism
and to these careers

03:23:30.640 --> 03:23:34.210
where folks can actually
go to these colleges and get

03:23:34.210 --> 03:23:37.770
a certification that again,
could help them with their,

03:23:37.770 --> 03:23:42.130
their ability to work in these fields.

03:23:42.130 --> 03:23:44.850
But also it makes them
well-positioned to sort of hit

03:23:44.850 --> 03:23:47.450
the ground running when
they start these activities.

03:23:51.622 --> 03:23:54.039
(indistinct)

03:23:57.060 --> 03:24:01.230
So more specifically, how
do we track all of these trees?

03:24:01.230 --> 03:24:04.028
Again, we mentioned you have about four

03:24:04.028 --> 03:24:06.153
to 57,000 trees in our inventory.

03:24:06.153 --> 03:24:10.340
That number changes
every day as trees are added

03:24:10.340 --> 03:24:12.860
and are removed from the system.

03:24:12.860 --> 03:24:15.207
So this database that we currently have,

03:24:15.207 --> 03:24:19.110
our work management system,
very robust, as I mentioned,

03:24:19.110 --> 03:24:22.910
every single tree record
is mapped electronically.

03:24:22.910 --> 03:24:24.330
And that true record,

03:24:24.330 --> 03:24:27.520
houses all of the activity
history from that tree.

03:24:27.520 --> 03:24:30.440
We know at any, any
given time, for example,

03:24:30.440 --> 03:24:32.650
but a tree was inspected,

03:24:32.650 --> 03:24:36.892
what the clearance was during
that day and the same work

03:24:36.892 --> 03:24:37.863
for trimming and auditing.

03:24:39.154 --> 03:24:42.130
You can obviously run
copious reports on us.

03:24:42.130 --> 03:24:44.580
So we always know the
of our system, if you will,

03:24:44.580 --> 03:24:45.673
at any given time.

03:24:47.210 --> 03:24:51.600
All the data that's captured
daily from our contractors is

03:24:51.600 --> 03:24:54.160
uploaded electronically
to the master servers.

03:24:54.160 --> 03:24:57.010
So all of the contractors
are in the system,

03:24:57.010 --> 03:24:59.263
including our tree-trimming contractor.

03:25:00.710 --> 03:25:04.000
In 2020, we started the development

03:25:04.000 --> 03:25:05.920
of our new work management system

03:25:05.920 --> 03:25:10.630
with the next generation
or our mobile application

03:25:10.630 --> 03:25:12.120
for our database.

03:25:12.120 --> 03:25:14.250
So this system is called EPOCH,

03:25:14.250 --> 03:25:15.820
and it's going to give us improvements

03:25:15.820 --> 03:25:19.920
in data gathering work
deficiencies, we'll have,

03:25:19.920 --> 03:25:24.920
again, robust asset history,
better report capabilities,

03:25:26.400 --> 03:25:29.704
and much better mapping
capability will increase

03:25:29.704 --> 03:25:34.704
the productivity and the
efficiency of our contractors,

03:25:34.800 --> 03:25:37.530
and also our ability to capture data

03:25:37.530 --> 03:25:40.417
that we can use for
some of our analytics.

03:25:41.864 --> 03:25:43.170
We'll also have the
ability with this new system

03:25:43.170 --> 03:25:48.170
to get geolocate by GPS,
every single tree in our system.

03:25:48.650 --> 03:25:52.340
So all every single
limitory tree that we map

03:25:52.340 --> 03:25:54.790
will have a specific location.

03:25:54.790 --> 03:25:57.400
And just a quick definition
of what constitutes

03:25:57.400 --> 03:26:02.360
a inventory tree,
that has the capability

03:26:02.360 --> 03:26:06.270
to impact the power lines
either why encroachment

03:26:06.270 --> 03:26:08.657
and growth, or could otherwise fall

03:26:08.657 --> 03:26:13.650
and strike (indistinct)
ranch on the power lines.

03:26:13.650 --> 03:26:17.140
So we'll have information
for every one of those trees

03:26:17.140 --> 03:26:19.310
within the spikes
that meet that criteria

03:26:22.100 --> 03:26:27.100
We'll also have more updated
customer information and which

03:26:27.510 --> 03:26:30.760
will improve our ability to
engage with our customers.

03:26:30.760 --> 03:26:33.500
Right now, we have all of
our customer information

03:26:33.500 --> 03:26:37.890
within those tree records
for our contractors to use.

03:26:37.890 --> 03:26:39.900
And we also have, for example,

03:26:39.900 --> 03:26:43.947
specific on notification
or access instructions.

03:26:46.670 --> 03:26:47.970
Next slide, please.

03:26:53.160 --> 03:26:57.520
So regarding the technologies, in 2020,

03:26:57.520 --> 03:27:02.465
we continue one of our
pilot projects with LIDAR.

03:27:02.465 --> 03:27:05.570
And this is our more of our
deep dive into determining

03:27:05.570 --> 03:27:09.230
whether and how effectively
we can utilize LIDAR.

03:27:09.230 --> 03:27:10.750
It's typically to integrated within

03:27:10.750 --> 03:27:14.510
our routine pre-inspection actions,

03:27:14.510 --> 03:27:17.530
which we are currently looking at that.

03:27:17.530 --> 03:27:21.530
We piloted a circuit in one
of our highest risk circuits

03:27:21.530 --> 03:27:24.729
where we have relative high tree density

03:27:24.729 --> 03:27:28.277
and where we've had outages in the past.

03:27:28.277 --> 03:27:30.580
One of the drawbacks, if you will,

03:27:30.580 --> 03:27:32.470
for LIDAR is the frequency with

03:27:32.470 --> 03:27:34.640
which we get the data, right?

03:27:34.640 --> 03:27:37.200
It's subject to our flights,

03:27:37.200 --> 03:27:39.300
but we have to have the LIDAR flight.

03:27:39.300 --> 03:27:42.810
And then you have to
produce the data in a fashion

03:27:42.810 --> 03:27:46.823
that it's usable, readily
usable or a, the department.

03:27:47.860 --> 03:27:52.460
So right now we are, we're
currently using LIDAR or similar,

03:27:52.460 --> 03:27:54.700
I think to SDG and E and PG and E

03:27:54.700 --> 03:27:57.170
on most of our transmission lines,

03:27:57.170 --> 03:28:00.910
we could build in
(indistinct) CAD information,

03:28:00.910 --> 03:28:03.700
and we can drive, for
example, the blow outs

03:28:03.700 --> 03:28:05.893
in the sack of our transmission.

03:28:06.930 --> 03:28:09.445
We're looking to apply that to some of

03:28:09.445 --> 03:28:11.610
our distribution circuits as well, too,

03:28:11.610 --> 03:28:15.753
so we can further capitalize
on not the use of LIDAR.

03:28:16.890 --> 03:28:19.173
Well, the other proof of concept.

03:28:21.850 --> 03:28:24.550
Issues that we looked
at last year in 2020,

03:28:24.550 --> 03:28:26.220
was satellite imagery.

03:28:26.220 --> 03:28:29.270
So we're, we're
currently doing a use case

03:28:29.270 --> 03:28:32.530
to look at this technology
to see its value.

03:28:32.530 --> 03:28:35.420
And again, whether it
has incremental value

03:28:35.420 --> 03:28:37.690
to the Vegetation Management Program.

03:28:37.690 --> 03:28:40.470
Initially, what we find
when you compare LIDAR

03:28:40.470 --> 03:28:43.710
with satellite imagery
is that satellite imagery,

03:28:43.710 --> 03:28:47.145
you can get much more
frequent data, right?

03:28:47.145 --> 03:28:49.260
And you can get, this is often as,

03:28:49.260 --> 03:28:52.330
as the satellites circles
the Earth, we can get that,

03:28:52.330 --> 03:28:56.860
that data, so it can help
us formulate and verify,

03:28:56.860 --> 03:28:58.853
for example, our tree height data.

03:28:59.860 --> 03:29:04.070
It doesn't give us the
specific official accuracy

03:29:04.070 --> 03:29:06.823
that LIDAR can give us,
but we think we can be,

03:29:06.823 --> 03:29:10.450
we will be able to use it in
conjunction with LIDAR is

03:29:10.450 --> 03:29:14.280
to help finesse and
give us a more finite look

03:29:14.280 --> 03:29:15.950
at our system.

03:29:15.950 --> 03:29:18.080
Because we do, because we're required

03:29:18.080 --> 03:29:20.300
to maintain compliance a year round,

03:29:20.300 --> 03:29:24.420
we really have to rely
on our field inspectors,

03:29:24.420 --> 03:29:29.420
not only to assess clearances
at a high degree of frequency,

03:29:29.760 --> 03:29:32.130
but also we need their
skill set as arborists

03:29:32.130 --> 03:29:36.590
to determine not just
clearances, but also looking at risk,

03:29:38.120 --> 03:29:40.807
the hazard that those trees.

03:29:40.807 --> 03:29:45.440
That requires for us, in the
HFTD, a 360-degree look

03:29:45.440 --> 03:29:48.970
at all of those trees are
within the strike zone.

03:29:48.970 --> 03:29:51.950
It could potentially hit
the power lines if they were

03:29:51.950 --> 03:29:53.993
to fall from the ground.

03:29:55.650 --> 03:29:57.840
And lastly we continue to build

03:29:57.840 --> 03:30:00.100
on our Vegetation Risk Index,

03:30:00.100 --> 03:30:03.390
where we're merging our meteorology data

03:30:03.390 --> 03:30:06.290
with our tree outage data.

03:30:06.290 --> 03:30:08.650
Every time we have
a tree-related outage,

03:30:08.650 --> 03:30:11.730
our foresters will do
a field investigation

03:30:11.730 --> 03:30:14.550
and will capture all
the information relative

03:30:14.550 --> 03:30:18.480
to that, that outage, which
gives us a rich outage history

03:30:18.480 --> 03:30:22.620
going for us, going back to 2000.

03:30:22.620 --> 03:30:25.400
And we can mine that data and use that

03:30:25.400 --> 03:30:27.980
in conjunction with
our meteorology history,

03:30:27.980 --> 03:30:30.616
you see where we might have higher risk.

03:30:30.616 --> 03:30:35.616
And as Sarah mentioned
earlier with our WINGS model,

03:30:36.183 --> 03:30:39.750
one of the inputs we can
use is the vegetation index,

03:30:39.750 --> 03:30:43.780
see where we may have
higher risks on a given circuit,

03:30:43.780 --> 03:30:45.080
on a segment (indistinct).

03:30:46.510 --> 03:30:51.150
And then we are also as of last year,

03:30:51.150 --> 03:30:53.807
we have engaged with in
vegetation management,

03:30:53.807 --> 03:30:57.800
the use of a University
of California at San Diego,

03:30:57.800 --> 03:31:00.785
super, super convenient modeling team.

03:31:00.785 --> 03:31:03.990
We're actually taking all this data

03:31:03.990 --> 03:31:05.600
that I've just described,

03:31:05.600 --> 03:31:08.830
and they're trying to
help us build Risk Analysis

03:31:08.830 --> 03:31:11.240
and Predictive Modeling Tool.

03:31:11.240 --> 03:31:13.960
And one of the ways that
we're going to help that along is

03:31:13.960 --> 03:31:17.220
to capture even more refined data

03:31:17.220 --> 03:31:20.160
at the tree's specific asset level.

03:31:20.160 --> 03:31:22.240
That would incline, for example,

03:31:22.240 --> 03:31:23.890
what is the soil moisture content

03:31:25.167 --> 03:31:27.000
or the given area of
the trees located on?

03:31:27.000 --> 03:31:29.730
What is the soil type?

03:31:29.730 --> 03:31:31.870
What is the slope?

03:31:31.870 --> 03:31:36.730
And what is the history
of meteorology data?

03:31:36.730 --> 03:31:39.989
So we're looking at sort of
tying all of these technologies,

03:31:39.989 --> 03:31:43.000
give us the most informed information,

03:31:43.000 --> 03:31:46.970
but incorporated in it being integrated

03:31:46.970 --> 03:31:50.700
into improving our field
inspections, which again,

03:31:50.700 --> 03:31:53.050
you're doing at least
twice a year with the HA.

03:32:03.806 --> 03:32:05.389
Next slide, please.

03:32:10.702 --> 03:32:13.340
And another thing we started last year

03:32:13.340 --> 03:32:15.350
with vegetation
management was really to take

03:32:15.350 --> 03:32:18.070
a closer look at our
sustainability initiative

03:32:18.070 --> 03:32:20.270
and SDG and E, like
all the other utilities

03:32:20.270 --> 03:32:22.920
is committed to
environmental stewardship.

03:32:22.920 --> 03:32:26.890
Our contractors are trained
each year on the rules

03:32:26.890 --> 03:32:30.730
and regulations as they pertain
to environmental compliance.

03:32:30.730 --> 03:32:35.050
We currently in regards
to our tree removal

03:32:35.050 --> 03:32:36.820
and tree trimming operations,

03:32:36.820 --> 03:32:39.870
we removed all of the
vegetation trail off sites

03:32:39.870 --> 03:32:43.580
with the exception of larger material

03:32:43.580 --> 03:32:45.320
that we leave for customers.

03:32:45.320 --> 03:32:49.463
We also upon request, we'll
leave material with customers.

03:32:50.322 --> 03:32:54.270
And then also what we've
done in 2020, is we've added

03:32:54.270 --> 03:32:58.060
on a second vendor
that processes all material

03:32:58.060 --> 03:33:02.856
that is brought to their
facility and to 100% recycling

03:33:02.856 --> 03:33:03.689
(indistinct).

03:33:03.689 --> 03:33:06.040
So we're looking for an increase in

03:33:06.040 --> 03:33:09.162
the amount of green waste
that we divert away from

03:33:09.162 --> 03:33:12.780
our local landfills in 2021.

03:33:12.780 --> 03:33:14.784
And that little graphic right there,

03:33:14.784 --> 03:33:16.030
you can see how much tonnage we deliver

03:33:16.030 --> 03:33:19.780
to recyclable facilities in 2019,

03:33:19.780 --> 03:33:22.610
compared to the (indistinct)

03:33:22.610 --> 03:33:23.940
Next slide, please.

03:33:28.274 --> 03:33:29.350
Okay, with that, I'm going
to turn it over to Tyson,

03:33:29.350 --> 03:33:32.483
who's going to talk about our
vegetation clearance analysis.

03:33:34.050 --> 03:33:35.240
<v Tyson>Thank you, Michael.</v>

03:33:35.240 --> 03:33:36.797
So I'm Tyson Swedek,

03:33:40.118 --> 03:33:43.453
Director of our Partitioners
Operations Unit for SDG and E,

03:33:43.453 --> 03:33:45.563
and I'll be discussing the
vegetation clearance studies

03:33:45.563 --> 03:33:48.473
that we've been conducting.

03:33:48.473 --> 03:33:50.793
As you know, we have a
goal to reduce risk events

03:33:50.793 --> 03:33:52.400
and ignitions and
meditation contexts continues

03:33:52.400 --> 03:33:54.612
to represent one of the higher risks

03:33:54.612 --> 03:33:55.720
for SDG and E.

03:33:55.720 --> 03:33:57.590
From 2015 to 2019,

03:33:57.590 --> 03:34:00.700
we've averaged about
two ignitions per year

03:34:00.700 --> 03:34:03.760
in HFTD due to vegetation contacts,

03:34:03.760 --> 03:34:06.600
which is second from
a risk driver standpoint,

03:34:06.600 --> 03:34:08.193
only two vehicle contacts.

03:34:09.050 --> 03:34:12.510
In the 2019 WMP, SDG and E moved forward

03:34:12.510 --> 03:34:15.370
with a solution to increase
post-trim clearances.

03:34:15.370 --> 03:34:19.425
Based on this different success
we've had had historically,

03:34:19.425 --> 03:34:23.260
we're using vegetation
contacts from over 400 per year

03:34:23.260 --> 03:34:26.560
to under 100 per year
when we moved from two

03:34:26.560 --> 03:34:30.973
to four foot clearances to
10 to 12 foot clearances.

03:34:32.060 --> 03:34:35.240
So I've teamed up with
arbitration management teams

03:34:35.240 --> 03:34:37.160
to analyze the data
from our tree database

03:34:37.160 --> 03:34:38.670
to see if we could gain some insights

03:34:38.670 --> 03:34:41.430
into the impacts of clearance from trees

03:34:41.430 --> 03:34:43.827
to electric conductors on vegetation

03:34:43.827 --> 03:34:46.980
and risk events and admissions.

03:34:46.980 --> 03:34:48.610
So to accomplish this,

03:34:48.610 --> 03:34:51.930
we looked at tree-trimming
data and vegetation contact data

03:34:51.930 --> 03:34:55.620
from 2002 through 2019.

03:34:55.620 --> 03:34:58.070
2002 was selected
because this is the year

03:34:58.070 --> 03:35:00.340
that we consistently started reporting

03:35:00.340 --> 03:35:04.740
post trend clearance
values for inventory trees.

03:35:04.740 --> 03:35:07.470
We looked at both the
vegetation contacts that occurred

03:35:07.470 --> 03:35:09.420
at a certain post-term
clearance distance

03:35:09.420 --> 03:35:13.340
and the number of trees
trimmed in a year at this,

03:35:13.340 --> 03:35:14.860
at those distances.

03:35:14.860 --> 03:35:18.610
So this data combined allowed
us to determine a contact rate

03:35:18.610 --> 03:35:20.380
or a number of vegetation,

03:35:20.380 --> 03:35:23.180
risk events over the
number of opportunities

03:35:23.180 --> 03:35:25.320
or risks to occur.

03:35:25.320 --> 03:35:29.100
We then normalize the
data per 1,000 trees trimmed.

03:35:30.100 --> 03:35:32.320
We did begin with a
system-wide look looking

03:35:32.320 --> 03:35:33.870
at every vegetation contact

03:35:33.870 --> 03:35:36.230
on the system overall three's trends.

03:35:36.230 --> 03:35:39.370
And then in this latest study
that we have displayed here,

03:35:39.370 --> 03:35:41.140
we zoom in on the specifics of

03:35:41.140 --> 03:35:43.590
the Enhanced Vegetation
Management Program,

03:35:43.590 --> 03:35:46.130
which is the filter of the
original data set to just

03:35:46.130 --> 03:35:49.730
the five targeted species
and only trees located

03:35:49.730 --> 03:35:51.440
within the HFTD.

03:35:51.440 --> 03:35:54.010
Again, the shape of the
curve remains the same

03:35:54.010 --> 03:35:58.240
and does indicate or relationship that

03:35:58.240 --> 03:36:02.747
as clearances are
increased from trees to lines,

03:36:02.747 --> 03:36:07.083
we do have less risk events that occur.

03:36:12.479 --> 03:36:15.323
And I think that's the
end of our presentation.

03:36:23.290 --> 03:36:25.030
<v Colin>Thank you, Michael.</v>

03:36:25.030 --> 03:36:25.863
Thank you Tyson.

03:36:27.400 --> 03:36:29.360
Now we have an opportunity for a break

03:36:29.360 --> 03:36:33.620
before our Q and A
session we will resume at,

03:36:33.620 --> 03:36:35.780
let me just double check.

03:36:35.780 --> 03:36:38.530
I believe it's 2:45.

03:36:38.530 --> 03:36:39.720
Yes, 2:45.

03:36:39.720 --> 03:36:43.243
So will we see you all back at 2:45?

03:37:04.170 --> 03:37:06.660
Okay, I have 2:45.

03:37:06.660 --> 03:37:08.250
So welcome back everybody.

03:37:08.250 --> 03:37:11.040
I hope that you all got
a chance to step outside

03:37:11.040 --> 03:37:15.260
and maybe some trees in
preparation for this Q and A.

03:37:16.825 --> 03:37:18.660
During this Q and A,

03:37:18.660 --> 03:37:22.330
we will have the speakers
who gave their presentations

03:37:22.330 --> 03:37:24.500
just a few moments ago.

03:37:24.500 --> 03:37:27.060
We'll also have, we'll also hear,

03:37:27.060 --> 03:37:29.220
be able to hear from stakeholders such

03:37:29.220 --> 03:37:33.680
as the Utility Reform Network,
Mussey Grade Road Alliance,

03:37:33.680 --> 03:37:37.830
the Public Advocate's Office,
and Green Power Institute.

03:37:37.830 --> 03:37:40.270
We'll do the same thing
that we did this morning.

03:37:40.270 --> 03:37:41.890
We'll do a round robin.

03:37:41.890 --> 03:37:44.310
I will start with one question from WSC,

03:37:44.310 --> 03:37:47.270
and then we will go around
to the various stakeholders

03:37:47.270 --> 03:37:51.150
and include people who are listening

03:37:51.150 --> 03:37:53.640
and putting their questions in the chat

03:37:53.640 --> 03:37:55.713
and the Q and A function in WebEx.

03:37:57.310 --> 03:38:00.230
Ryan Arba will be monitoring the chat.

03:38:00.230 --> 03:38:03.170
Please make sure when you are submitting

03:38:03.170 --> 03:38:04.920
a question via chat,

03:38:04.920 --> 03:38:07.740
that you use that down
menu and make sure

03:38:07.740 --> 03:38:09.827
that you select "all panelists,"

03:38:10.668 --> 03:38:12.345
so all of us can see the chat.

03:38:12.345 --> 03:38:15.573
The host is in an IT role.

03:38:16.900 --> 03:38:18.757
Please, select "all panelists."

03:38:24.882 --> 03:38:28.680
<v Ryan>Okay, to
start out, first of all,</v>

03:38:28.680 --> 03:38:31.030
thank you for answering the
first couple of my questions

03:38:31.030 --> 03:38:33.080
on my list already.

03:38:33.080 --> 03:38:37.100
So we'll start in with going
a little further down the list.

03:38:37.100 --> 03:38:38.900
You all, all of the utilities

03:38:38.900 --> 03:38:40.970
have increased their clearances over

03:38:40.970 --> 03:38:43.970
the past couple of years in response

03:38:43.970 --> 03:38:48.970
to increased vegetation
management and wildfire mitigation.

03:38:50.090 --> 03:38:55.090
And a few of you touched
upon fuels management,

03:38:55.970 --> 03:38:58.360
but I would like to hear
a little bit more about

03:38:58.360 --> 03:39:01.660
how the increased scale
of vegetation management

03:39:01.660 --> 03:39:06.660
has affected biomass
management and fuels management

03:39:07.640 --> 03:39:08.667
in the field.

03:39:19.529 --> 03:39:21.100
<v ->So Colin, I'm not sure if
you're going to call on us</v>

03:39:21.100 --> 03:39:23.240
or it's just going to start
with PG and E's time,

03:39:23.240 --> 03:39:27.630
but I'll go ahead and talk
about how it's impacted us.

03:39:27.630 --> 03:39:32.630
So this number fluctuates a fair amount,

03:39:33.800 --> 03:39:38.190
but I would say somewhere
between 70 and 99%

03:39:39.650 --> 03:39:44.650
of our bio waste
generated from our activities

03:39:44.670 --> 03:39:48.030
goes to region plants.

03:39:48.030 --> 03:39:51.853
It depends on a variety
of factors, location.

03:39:53.080 --> 03:39:54.900
Also, if the plants are
even taking anything,

03:39:54.900 --> 03:39:58.197
unfortunately what we saw in 2020,

03:39:58.197 --> 03:40:00.290
with the large number
of fires that occurred,

03:40:00.290 --> 03:40:03.003
many of the plants were
overwhelmed because there was just

03:40:03.003 --> 03:40:05.220
so much available material
for them to be taking.

03:40:05.220 --> 03:40:06.713
And so they got to a place.

03:40:07.930 --> 03:40:09.270
We do tend to work though,

03:40:09.270 --> 03:40:11.370
even if it doesn't go
to one of those plants,

03:40:11.370 --> 03:40:16.370
the landfills we go to, we
make sure that they are re there,

03:40:16.840 --> 03:40:20.840
that they do treat the wood
environmentally friendly means

03:40:20.840 --> 03:40:23.280
that they don't just
let it build up in places.

03:40:23.280 --> 03:40:26.000
So we try and work with
folks to make sure that it gets to

03:40:26.000 --> 03:40:27.653
a, a reasonable place,

03:40:28.990 --> 03:40:30.860
but we have seen that it has overwhelmed

03:40:30.860 --> 03:40:35.043
at times some of the, the
systems that are available to us,

03:40:36.510 --> 03:40:39.720
specifically with the
wood that is we haul off.

03:40:39.720 --> 03:40:41.960
We tend to only haul off a wood

03:40:41.960 --> 03:40:45.200
that's less than four inches in diameter

03:40:45.200 --> 03:40:47.210
and the larger diameter wood

03:40:47.210 --> 03:40:50.480
we tend to leave in a location,
that can vary depending

03:40:50.480 --> 03:40:53.240
on the situation pretty drastically,

03:40:53.240 --> 03:40:54.950
but that's our general policy.

03:40:54.950 --> 03:40:58.890
And we remove that
smaller diameter material

03:41:00.450 --> 03:41:02.883
from most locations that we do work on.

03:41:04.460 --> 03:41:06.520
From a fuel reduction standpoint,

03:41:06.520 --> 03:41:07.840
a targeted floor reduction,

03:41:07.840 --> 03:41:11.260
I briefly mentioned in my
presentation, you know,

03:41:11.260 --> 03:41:12.860
the last few years we've done

03:41:12.860 --> 03:41:14.620
some targeted fuel reduction projects.

03:41:14.620 --> 03:41:16.960
Usually those are in, in partnership

03:41:16.960 --> 03:41:20.810
with a local agency, typically
to establish fuel breaks

03:41:20.810 --> 03:41:25.810
around cities or
other critical locations.

03:41:26.100 --> 03:41:29.740
In 2021, we're going to
be targeting a, a more,

03:41:29.740 --> 03:41:34.597
a larger fuel defensible space
program that I mentioned.

03:41:34.597 --> 03:41:37.853
And we'll be, that'll be
along our right of ways.

03:41:41.520 --> 03:41:43.693
<v ->Quick follow up
question for you, Steven.</v>

03:41:43.693 --> 03:41:48.530
Does PG and E have any
programs to help increase

03:41:48.530 --> 03:41:51.770
the number of pathways
for biomass waste when

03:41:51.770 --> 03:41:54.820
the system is overwhelmed,
or do you see that as more,

03:41:54.820 --> 03:41:58.150
the overwhelming volume
of biomass is more of

03:41:58.150 --> 03:41:59.463
a temporary problem?

03:42:01.160 --> 03:42:05.870
<v ->So the first time I really
saw that issue was in 2020,</v>

03:42:05.870 --> 03:42:08.059
and that was really, you know,

03:42:08.059 --> 03:42:11.510
when over 4 million
acres burned in the state.

03:42:11.510 --> 03:42:13.980
Prior to that, we haven't
really seen that (indistinct).

03:42:13.980 --> 03:42:16.100
I don't know of any
plans to increase that

03:42:16.100 --> 03:42:17.850
at PGS is involved with right now,

03:42:17.850 --> 03:42:22.200
but we do work in support
those different agencies.

03:42:22.200 --> 03:42:26.370
Often, I think the
majority of our waste,

03:42:26.370 --> 03:42:27.670
we give to them as at no cost,

03:42:27.670 --> 03:42:29.550
we don't usually ask
for anything in return

03:42:29.550 --> 03:42:31.369
for it in most instances.

03:42:31.369 --> 03:42:33.840
So we try and make
it as beneficial to them

03:42:33.840 --> 03:42:37.250
as we can in our practice
of giving it to them.

03:42:40.373 --> 03:42:42.803
<v ->Thank you, Steven, Melanie?</v>

03:42:48.380 --> 03:42:49.280
<v Melanie>Hello.</v>

03:42:51.020 --> 03:42:54.590
So I can address this one as well.

03:42:54.590 --> 03:42:59.183
So I, in some ways we're
similar to what Steven described,

03:43:00.965 --> 03:43:04.500
basically, except we don't
distinguish on debris size.

03:43:04.500 --> 03:43:08.470
The work that we do is
generally always hauled away

03:43:08.470 --> 03:43:13.210
and disposed of and or
recycled by our contractors.

03:43:13.210 --> 03:43:16.046
We don't track closely
the amount that's recycled,

03:43:16.046 --> 03:43:19.690
but typically from a
financial perspective,

03:43:19.690 --> 03:43:24.130
as long as there is a center
in the vicinity that is willing

03:43:24.130 --> 03:43:29.130
to accept the debris the
fences, recycle, recycle recycling,

03:43:29.470 --> 03:43:32.290
simply because it's affordable that way.

03:43:32.290 --> 03:43:35.330
And the only tree debris
that I'm aware of that cannot

03:43:35.330 --> 03:43:37.210
be recycled is those from palms

03:43:37.210 --> 03:43:39.423
because it's not actually a tree.

03:43:41.220 --> 03:43:44.380
And so, as I mentioned,
the debris of whatever size is,

03:43:44.380 --> 03:43:47.526
is removed, that is there are there,

03:43:47.526 --> 03:43:50.860
there are certain
exceptions in that case.

03:43:50.860 --> 03:43:54.070
The major exception is remote areas

03:43:54.070 --> 03:43:56.008
on U.S. Forest Service land,

03:43:56.008 --> 03:43:59.350
where the rules permit is permit it,

03:43:59.350 --> 03:44:02.320
where more than 100 feet from the road,

03:44:02.320 --> 03:44:04.050
the roadways we'll cut.

03:44:04.050 --> 03:44:06.250
And then we scatter it
up to a certain height,

03:44:06.250 --> 03:44:10.350
so it doesn't create too
much of a fire concern there.

03:44:10.350 --> 03:44:14.270
We are actually also I'm
undertaking a fuel study with

03:44:14.270 --> 03:44:17.670
the Edison Power
Research Institute through

03:44:17.670 --> 03:44:18.980
the remainder of this year,

03:44:18.980 --> 03:44:20.890
and hoping to get
some further insight there

03:44:20.890 --> 03:44:22.870
on best practices.

03:44:22.870 --> 03:44:25.550
And then just to
anticipate your question,

03:44:25.550 --> 03:44:28.480
in terms of bio-mass,
we are aware that again,

03:44:28.480 --> 03:44:33.480
in terms of use of
bio-mass plants for energy,

03:44:35.400 --> 03:44:39.110
that is also sometimes
an option in the vicinity

03:44:39.110 --> 03:44:41.433
of where the work is taking place.

03:44:42.440 --> 03:44:44.047
But part of the challenge there,

03:44:44.047 --> 03:44:45.950
and our ability to support that effort,

03:44:45.950 --> 03:44:47.680
which is something we've looked at,

03:44:47.680 --> 03:44:51.980
has to do with the
continuity of the work, right?

03:44:51.980 --> 03:44:54.060
Meaning if somebody is going to set up

03:44:54.060 --> 03:44:55.930
a biomass generation plant,

03:44:55.930 --> 03:44:59.380
they need to be able to
assure a consistent fuel supply.

03:44:59.380 --> 03:45:02.750
And that's not the way
that we plan our work, right?

03:45:02.750 --> 03:45:05.540
We're not that that is
not our core purpose.

03:45:05.540 --> 03:45:07.360
And so it tends to be based

03:45:07.360 --> 03:45:09.870
on economic factors for the region.

03:45:09.870 --> 03:45:11.870
And it's something that
we can take advantage of

03:45:11.870 --> 03:45:15.850
rather than something
that we can explicitly pursue

03:45:15.850 --> 03:45:17.423
or drive independently.

03:45:26.070 --> 03:45:27.120
<v ->Thank you, Melanie.</v>

03:45:29.690 --> 03:45:31.756
Can we get a response
from Michael or Tyson

03:45:31.756 --> 03:45:33.401
at SDG and E?

03:45:33.401 --> 03:45:34.570
There you are Michael.

03:45:34.570 --> 03:45:35.996
<v ->Hi, Michael, thank you.</v>

03:45:35.996 --> 03:45:37.596
Thank you for that question too.

03:45:39.177 --> 03:45:41.650
So we'll just reiterate
for our routine registration

03:45:41.650 --> 03:45:45.233
management operations,
all the way an exception of

03:45:48.009 --> 03:45:49.920
the larger margin degree would be,

03:45:49.920 --> 03:45:53.501
for example, if we're taking
arts diameter trees down,

03:45:53.501 --> 03:45:57.710
that is customers' properties
that we do (indistinct)

03:45:57.710 --> 03:46:00.410
and leave it at
de-manageable lengths quality.

03:46:02.465 --> 03:46:04.910
When it comes to agency
lands like forest service

03:46:04.910 --> 03:46:09.350
or state parks, we follow
better specific guidance

03:46:09.350 --> 03:46:11.810
and requirements pre-disposal.

03:46:11.810 --> 03:46:14.430
So as Melanie mentioned,
for example, Forest Service,

03:46:14.430 --> 03:46:18.120
we would lop and scatter while
there are some communities

03:46:18.120 --> 03:46:20.869
where we have turned into agreement

03:46:20.869 --> 03:46:22.310
to remove most of the material,

03:46:22.310 --> 03:46:26.060
even though larger
material offsite in conjunction

03:46:26.060 --> 03:46:28.880
with our reaching global operations.

03:46:28.880 --> 03:46:33.880
But majority of the
debris is chipped off site.

03:46:34.338 --> 03:46:35.820
And as I mentioned last year,

03:46:35.820 --> 03:46:40.820
we were able to divert
4,500 tons of material

03:46:41.050 --> 03:46:43.730
otherwise have gone to landfill into

03:46:43.730 --> 03:46:44.930
a recycled (indistinct).

03:46:47.205 --> 03:46:49.190
Back to our Fuels Management Program,

03:46:49.190 --> 03:46:52.480
one of the initiatives that
we can use last year was

03:46:52.480 --> 03:46:56.530
what we call are all fuels
modification treatments,

03:46:56.530 --> 03:47:01.530
where we're reducing fuels
around the base poles to try

03:47:01.930 --> 03:47:05.340
to prevent ignition if
there were to be either

03:47:05.340 --> 03:47:08.420
an equipment failure or a pole failure.

03:47:08.420 --> 03:47:10.090
And what we're doing
in those instances is

03:47:10.090 --> 03:47:13.070
we're removing all of
the flashy finer fuels,

03:47:13.070 --> 03:47:16.127
about 50 feet from the pole

03:47:16.127 --> 03:47:19.260
to avoid an ignition in those instances,

03:47:19.260 --> 03:47:23.760
all the material that we
generated was actually donated

03:47:23.760 --> 03:47:27.573
to parties that wanted
to use that (indistinct)

03:47:27.573 --> 03:47:29.960
for ground cover or whatnot.

03:47:35.400 --> 03:47:36.747
<v ->Thank you, Michael.</v>

03:47:37.765 --> 03:47:38.598
For our next question,

03:47:38.598 --> 03:47:40.530
we'll go to the rest of the panelists.

03:47:40.530 --> 03:47:43.740
Marcel from TURN.

03:47:43.740 --> 03:47:46.240
You want to unmute yourself
and ask your question?

03:47:53.160 --> 03:47:54.460
<v Marcel>Okay, sorry about that.</v>

03:47:54.460 --> 03:47:55.930
Thank you very much.

03:47:55.930 --> 03:47:58.073
This is Marcel Hopper from TURN.

03:47:59.990 --> 03:48:04.392
I have two questions
really about benchmarking

03:48:04.392 --> 03:48:06.623
for all of the utilities.

03:48:08.004 --> 03:48:11.249
So the first is I think
all of you described

03:48:11.249 --> 03:48:14.457
that you have some
sort of program to remove

03:48:14.457 --> 03:48:17.640
what you might be calling hazard trees

03:48:17.640 --> 03:48:21.970
or target trees or target tree species.

03:48:21.970 --> 03:48:25.993
And I'm just wondering
if you can, if you have,

03:48:27.370 --> 03:48:29.660
if the utilities have gotten together

03:48:29.660 --> 03:48:32.960
to discuss the criteria they use

03:48:32.960 --> 03:48:35.470
to identify such trees and
that whether you've done

03:48:35.470 --> 03:48:40.290
any benchmarking concerning
your Hazard Tree Programs.

03:48:40.290 --> 03:48:43.023
And if so, what's the outcome of that?

03:48:44.160 --> 03:48:45.067
And let's see,

03:48:45.067 --> 03:48:47.823
may I ask my second
benchmarking question right now?

03:48:51.090 --> 03:48:53.316
All right, I'm going
to take that as a yes.

03:48:53.316 --> 03:48:54.149
(crosstalk)

03:48:54.149 --> 03:48:55.037
<v ->Yeah, go ahead.</v>

03:48:55.923 --> 03:48:58.020
<v Marcel>It's a different
it's benchmarking,</v>

03:48:58.020 --> 03:49:01.793
but a different topic in
vegetation management.

03:49:01.793 --> 03:49:05.590
And that is you've you all saw
all described sort of systems

03:49:05.590 --> 03:49:08.620
you're implementing or had
used for work management.

03:49:08.620 --> 03:49:11.620
And I know the whole
issue of quality assurance,

03:49:11.620 --> 03:49:16.620
quality control is a
very kind of critical issue

03:49:16.670 --> 03:49:19.160
in the area of vegetation management.

03:49:19.160 --> 03:49:20.260
And I'm just curious,

03:49:20.260 --> 03:49:24.680
it sounded like Edison
was discussed describing

03:49:24.680 --> 03:49:27.120
the our ARBORA mobile tool

03:49:27.120 --> 03:49:30.555
and SDG and E described its EPIC tool.

03:49:30.555 --> 03:49:35.555
And I didn't quite understand
whether PG and E's statement

03:49:37.360 --> 03:49:40.010
that it's moving to defined scope,

03:49:40.010 --> 03:49:43.740
contracting constitutes
something similar

03:49:43.740 --> 03:49:44.980
in terms of work management.

03:49:44.980 --> 03:49:49.020
I guess what I'm really
trying to ask is PG and E

03:49:49.020 --> 03:49:51.440
sounded like it's doing
going a different direction

03:49:51.440 --> 03:49:55.210
from internalizing work management

03:49:55.210 --> 03:49:59.010
through centralized databases
to kind of outsourcing it

03:49:59.010 --> 03:50:00.769
a little bit more to the contractors.

03:50:00.769 --> 03:50:04.320
Let me know if that's totally,
if I'm misunderstanding

03:50:04.320 --> 03:50:06.610
and my question is whether
you all have benchmarked

03:50:06.610 --> 03:50:10.010
any of these work
management tools and I do they,

03:50:10.010 --> 03:50:12.920
I'm assuming they
include quality assurance,

03:50:12.920 --> 03:50:14.113
quality control.

03:50:15.040 --> 03:50:16.700
But these tell me if I'm wrong.

03:50:16.700 --> 03:50:17.700
Thank you very much.

03:50:20.870 --> 03:50:22.063
<v ->I'm happy to start.</v>

03:50:24.067 --> 03:50:29.067
So I can tell you that in terms
of hazard tree discussions,

03:50:30.540 --> 03:50:33.250
it's been some months
since we got together,

03:50:33.250 --> 03:50:37.290
but all three of the IOU's
are presented on this call have

03:50:37.290 --> 03:50:40.632
had benchmarking discussions
regarding Hazard Tree,

03:50:40.632 --> 03:50:43.920
going back to at least early 2020.

03:50:43.920 --> 03:50:47.500
And my memory is failing as
to what about extended is 2019.

03:50:47.500 --> 03:50:51.120
And I believe that our
fundamental approach is the same

03:50:51.120 --> 03:50:54.090
in terms of evaluating
the risk characteristics

03:50:54.090 --> 03:50:56.950
of each individual tree

03:50:56.950 --> 03:51:01.200
and then acting accordingly
associated with that tree.

03:51:01.200 --> 03:51:04.307
But rather than letting it stop there,

03:51:04.307 --> 03:51:06.607
I'll let my colleagues
weigh in on that point.

03:51:13.246 --> 03:51:15.269
<v ->This is Michael with SDG and E.</v>

03:51:15.269 --> 03:51:17.734
What we're looking for
is what Melanie just said.

03:51:17.734 --> 03:51:18.567
Thank you, Marcel for those questions.

03:51:18.567 --> 03:51:21.291
(indistinct) hazard trees.

03:51:21.291 --> 03:51:25.313
So just to reiterate.

03:51:26.530 --> 03:51:29.687
The individuals that do
our hazard tree inspection

03:51:29.687 --> 03:51:31.960
within the HFTD to be, and again,

03:51:31.960 --> 03:51:35.037
we do two separate
inspections within the HFTD

03:51:35.037 --> 03:51:37.330
and these folks are qualified

03:51:37.330 --> 03:51:39.980
to perform these self assessments.

03:51:39.980 --> 03:51:43.230
That is, they are certified arborists.

03:51:43.230 --> 03:51:45.500
So they're trained and they're educated,

03:51:45.500 --> 03:51:49.930
and for example, tree
growth, trees (indistinct)

03:51:50.960 --> 03:51:52.523
have the propensity to fail.

03:51:53.690 --> 03:51:55.940
But I think, while there
was some commonality

03:51:55.940 --> 03:51:57.920
with all the utilities.

03:51:57.920 --> 03:51:58.990
Obviously, you know,

03:51:58.990 --> 03:52:01.580
we live in different parts of the state.

03:52:01.580 --> 03:52:04.500
There are some common
species and common attributes

03:52:04.500 --> 03:52:06.490
that are required to assess

03:52:06.490 --> 03:52:08.860
when you're doing hazard tree valuation.

03:52:08.860 --> 03:52:10.670
We are a little unique that

03:52:10.670 --> 03:52:13.990
we do not have nearly the density,

03:52:13.990 --> 03:52:17.553
tree density, nor species diversity.

03:52:18.500 --> 03:52:23.282
We have what we call
five targeted tree species

03:52:23.282 --> 03:52:27.480
that are known to grow
fast or the sparkly cause

03:52:27.480 --> 03:52:30.580
the highest frequency
outages that it's those trees

03:52:30.580 --> 03:52:34.760
we're really focusing on our
enhanced operation function

03:52:34.760 --> 03:52:36.310
with how's the tree evaluation.

03:52:37.596 --> 03:52:39.150
By the way, those species are

03:52:39.150 --> 03:52:43.133
oak, bark, pine, palm, and eucalyptus.

03:52:44.500 --> 03:52:47.750
The eucalyptus is
non native to California,

03:52:47.750 --> 03:52:50.990
there's hundreds of
species of eucalyptus trees.

03:52:50.990 --> 03:52:53.986
Unfortunately how few
of them that are notorious,

03:52:53.986 --> 03:52:57.240
for failing, where they grow fast,

03:52:57.240 --> 03:53:00.300
but they are also what's
called Lockwood species.

03:53:00.300 --> 03:53:01.920
So they can handle for,

03:53:01.920 --> 03:53:03.830
especially during windy conditions

03:53:03.830 --> 03:53:07.143
or when the soils are saturated.

03:53:08.059 --> 03:53:12.610
We were also looking at
the frequency of our outages

03:53:12.610 --> 03:53:16.810
to help inform us and drive
those trees of really trying

03:53:16.810 --> 03:53:18.643
to practically mitigate.

03:53:19.677 --> 03:53:23.550
It really comes down to the
completeness and the accuracy

03:53:23.550 --> 03:53:26.450
of hazard tree assessments
and the individual

03:53:26.450 --> 03:53:28.520
that is trained to do that,

03:53:28.520 --> 03:53:30.850
where you're going to
see the highest success

03:53:30.850 --> 03:53:33.960
in identifying hazard rates.

03:53:33.960 --> 03:53:36.017
LIDAR and other
technologies can inform you,

03:53:36.017 --> 03:53:38.670
but really requires those people frown

03:53:38.670 --> 03:53:40.770
on their professional knowledge.

03:53:40.770 --> 03:53:45.350
How's it, as it, as it relates
to the second question,

03:53:45.350 --> 03:53:47.790
we'll go about work management.

03:53:47.790 --> 03:53:50.860
One more detail about
our specific system,

03:53:50.860 --> 03:53:54.900
but what we're striving
to do is track our trees

03:53:54.900 --> 03:53:56.700
at the asset level.

03:53:56.700 --> 03:53:59.120
So we know at any given time again,

03:53:59.120 --> 03:54:02.850
when a tree has been
inspected and how much it had

03:54:02.850 --> 03:54:05.410
at that time, so it
could better inform us

03:54:05.410 --> 03:54:06.840
what actions to take.

03:54:06.840 --> 03:54:11.840
And we do have a specific
third party quality activity

03:54:12.380 --> 03:54:15.610
at the conclusion of all of

03:54:16.779 --> 03:54:18.760
our vegetation management actions,

03:54:18.760 --> 03:54:20.060
action (muffled speaking).

03:54:48.290 --> 03:54:50.366
<v ->I'm not sure did
we lose Michael?</v>

03:54:50.366 --> 03:54:52.013
I'm not sure if others
can still hear him.

03:54:55.220 --> 03:54:57.260
<v Michael>Okay, well, yeah,</v>

03:54:57.260 --> 03:55:00.430
I concluded all of what
we heard everything.

03:55:03.510 --> 03:55:07.150
<v ->All right, well, I'll just add
on, I, I, as you heard, we,</v>

03:55:07.150 --> 03:55:09.850
we have met together to
talk about different trees,

03:55:09.850 --> 03:55:11.310
targeted tree species rule.

03:55:11.310 --> 03:55:16.310
But again, it's not so much
the species, like for example,

03:55:16.610 --> 03:55:20.330
both you heard Edison and
San Diego mentioned palm trees.

03:55:20.330 --> 03:55:22.870
I don't really worry too much
about palm trees up here

03:55:22.870 --> 03:55:24.570
in the Northern half of the state.

03:55:26.097 --> 03:55:27.410
So it's not a major concern.

03:55:27.410 --> 03:55:30.500
Gray pines are a tree that
I have a lot of concern with.

03:55:30.500 --> 03:55:34.000
And while I wish we were doing

03:55:34.000 --> 03:55:36.100
some targeted species removals,

03:55:36.100 --> 03:55:38.364
that's not the approach we've taken.

03:55:38.364 --> 03:55:40.533
What we've we've done is

03:55:40.533 --> 03:55:41.980
we've developed our
tree assessment tool.

03:55:41.980 --> 03:55:43.740
And what that tool does is takes

03:55:43.740 --> 03:55:45.810
into consideration outage data,

03:55:45.810 --> 03:55:48.260
as well as other, as
I mentioned earlier,

03:55:48.260 --> 03:55:51.270
I won't rehash it here, but
basically looking for factors,

03:55:51.270 --> 03:55:54.020
what are factors that make
a tree more likely to fail,

03:55:54.020 --> 03:55:55.850
then it's the tree adjacent to it

03:55:55.850 --> 03:55:59.017
would be likely to fail
under certain conditions?

03:55:59.017 --> 03:56:02.500
And so that's what we, we look at.

03:56:02.500 --> 03:56:05.450
And I, and we've met
with the other utilities

03:56:05.450 --> 03:56:07.440
and talked about what are some,

03:56:07.440 --> 03:56:09.960
some characteristics that
we should be looking for

03:56:09.960 --> 03:56:12.510
that helps drive those discussions.

03:56:12.510 --> 03:56:13.343
And I think as you heard,

03:56:13.343 --> 03:56:15.710
we also all use our outage data

03:56:15.710 --> 03:56:18.193
where we've had failures
in the past, have shown,

03:56:20.190 --> 03:56:21.960
give us an indication
where we'll have failures

03:56:21.960 --> 03:56:24.210
in the future, both in location,

03:56:24.210 --> 03:56:26.930
but also in, in, in tree species.

03:56:26.930 --> 03:56:28.620
And then ask for your second question

03:56:28.620 --> 03:56:32.380
about the, the, the technology we use.

03:56:32.380 --> 03:56:36.210
So I think like the other utilities,

03:56:36.210 --> 03:56:41.210
we've been looking at a
new tool to oversee our,

03:56:42.520 --> 03:56:45.670
our veg management program,
PG and E is also undergoing

03:56:45.670 --> 03:56:48.380
that same process,
hoping to have something

03:56:48.380 --> 03:56:49.640
in place for 2021.

03:56:51.410 --> 03:56:55.530
We are, to your question
specifically about defined scope,

03:56:55.530 --> 03:56:57.750
we are looking to take a step back

03:56:57.750 --> 03:57:00.380
and not be in the way, if you will,

03:57:00.380 --> 03:57:03.713
of our contractors and
their ability to be efficient.

03:57:04.702 --> 03:57:05.990
You know, our old models,

03:57:05.990 --> 03:57:08.630
our pre inspectors
would give us the work

03:57:08.630 --> 03:57:11.078
and then we would
turn around and give it

03:57:11.078 --> 03:57:15.000
to the tree contractors that
created a middleman step.

03:57:15.000 --> 03:57:17.280
So what we're looking
into with our defined scope,

03:57:17.280 --> 03:57:21.840
which is limited just to
our routine program is that

03:57:21.840 --> 03:57:24.690
the tree contractors
are working directly

03:57:24.690 --> 03:57:27.980
with the tree inspectors
so that they control

03:57:27.980 --> 03:57:29.570
that, that flow of work.

03:57:29.570 --> 03:57:31.500
And we started this in October

03:57:31.500 --> 03:57:35.010
and already we've seen
improvements in that,

03:57:35.010 --> 03:57:39.080
especially that communication
between the two, two groups,

03:57:39.080 --> 03:57:41.763
the tree contractors
and the tree inspectors,

03:57:41.763 --> 03:57:42.596
allowing them to be more efficient.

03:57:42.596 --> 03:57:45.470
But in terms of the
data that we collect,

03:57:45.470 --> 03:57:48.640
PG and E will still
have all the, all the data

03:57:48.640 --> 03:57:51.197
will still be the
repository for that data.

03:57:51.197 --> 03:57:53.644
And so we are in the
process of developing a,

03:57:53.644 --> 03:57:56.550
a work management
tool, as well as a database,

03:57:56.550 --> 03:57:59.460
a new one to replace
some of our older systems

03:58:01.190 --> 03:58:03.760
that they can, all those
different groups can use

03:58:03.760 --> 03:58:07.210
to store their data across
that we contract with.

03:58:11.880 --> 03:58:13.520
<v ->Thank you, Steven.</v>

03:58:13.520 --> 03:58:16.660
Just a quick clarifying
question for you.

03:58:16.660 --> 03:58:18.990
I think you mentioned
that you may not target

03:58:18.990 --> 03:58:22.980
specific tree species,
but correct me if I'm wrong,

03:58:22.980 --> 03:58:26.340
the tree assessment
tool does include species

03:58:26.340 --> 03:58:28.637
as a risk attribute.

03:58:29.666 --> 03:58:31.840
<v ->It is a risk attribute, but
it's not an automatic, right?</v>

03:58:31.840 --> 03:58:32.960
So I mentioned we'll just go

03:58:32.960 --> 03:58:34.160
with the grapevine that I mentioned,

03:58:34.160 --> 03:58:36.360
just because you're a
grapevine doesn't mean

03:58:37.363 --> 03:58:39.290
you're automatically going
to be targeted for removal,

03:58:39.290 --> 03:58:42.240
but the scoring system
that works in the back end of

03:58:42.240 --> 03:58:46.470
that tool will make it more
likely that your pet tree itself

03:58:46.470 --> 03:58:49.270
will be targeted for removal,
but it's not an automatic.

03:58:50.670 --> 03:58:52.100
<v ->Great, thank you.</v>

03:58:52.100 --> 03:58:54.781
<v ->Yeah, Colin, if I, if
I could add to that.</v>

03:58:54.781 --> 03:58:57.650
(muffled speaking)

03:58:57.650 --> 03:59:00.920
Sorry, I just wanted
to make that distinction.

03:59:00.920 --> 03:59:03.420
I think one tree that's
probably consistent

03:59:03.420 --> 03:59:07.220
amongst all three utilities
areas is the eucalyptus.

03:59:07.220 --> 03:59:09.860
So similar to what Steven described,

03:59:09.860 --> 03:59:13.160
we're not going to unilaterally
remove all eucalyptus,

03:59:13.160 --> 03:59:15.350
but because we know that eucalyptus tend

03:59:15.350 --> 03:59:17.830
to shed limbs more easily,

03:59:17.830 --> 03:59:19.810
it's more likely that a
eucalyptus would reach

03:59:19.810 --> 03:59:22.330
a threshold that requires mitigation.

03:59:22.330 --> 03:59:25.260
It's going to depend on
how far it is from the line,

03:59:25.260 --> 03:59:26.580
a direction of lean,

03:59:26.580 --> 03:59:30.326
various health factors
that were our base.

03:59:30.326 --> 03:59:31.909
And that's where I started
with in terms of doing

03:59:31.909 --> 03:59:33.940
an individual assessment
on that particular tree.

03:59:33.940 --> 03:59:35.080
And then, and then just because

03:59:35.080 --> 03:59:37.680
I didn't address Marcel's
second question initially,

03:59:37.680 --> 03:59:40.160
I just wanted to add there that yes,

03:59:40.160 --> 03:59:41.970
both the tool that we use today and the,

03:59:41.970 --> 03:59:44.060
our ARBORA tool that
we're working to implement

03:59:44.060 --> 03:59:47.573
to incorporate QPC as
part of that functionality.

03:59:48.610 --> 03:59:51.890
And we have had extensive
benchmarking with our colleagues

03:59:51.890 --> 03:59:53.190
and discussing options before

03:59:53.190 --> 03:59:54.840
we pursued the path of that tool.

04:00:01.210 --> 04:00:04.106
<v ->Thank you for that
clarification, Melanie.</v>

04:00:04.106 --> 04:00:07.883
Next on my list is Will Averil.

04:00:11.630 --> 04:00:12.463
<v ->Thank you.</v>

04:00:13.357 --> 04:00:17.774
I just had a question on
some proceed disconnects

04:00:17.774 --> 04:00:20.240
with the vegetation management approach.

04:00:20.240 --> 04:00:24.078
One of these was touched
on in the morning part of the,

04:00:24.078 --> 04:00:28.480
of the discussion around
the bow tie methodology.

04:00:28.480 --> 04:00:31.640
So part of what I see
sort of missing there

04:00:31.640 --> 04:00:34.947
on the far right-hand
side of that bow tie

04:00:34.947 --> 04:00:38.380
are the mitigation efforts.

04:00:38.380 --> 04:00:41.840
So specifically around
vegetation management, you know,

04:00:41.840 --> 04:00:46.840
wildfire occurs, and then
we have MTTR dictating

04:00:47.020 --> 04:00:50.670
how quickly we can restore power, right?

04:00:50.670 --> 04:00:54.020
And so part of what I
don't see in the plans,

04:00:54.020 --> 04:00:55.617
and maybe you can speak to this,

04:00:55.617 --> 04:00:59.960
is here's how we're here
are the plans to address

04:00:59.960 --> 04:01:03.850
vegetation management,
post catastrophic wildfire.

04:01:03.850 --> 04:01:06.100
Here's where we intend to underground

04:01:06.100 --> 04:01:08.801
in this high fire threat district.

04:01:08.801 --> 04:01:12.950
Here's where we intend to
do fuel breaks, firebreaks.

04:01:12.950 --> 04:01:16.100
When that limited window
of opportunity arises,

04:01:16.100 --> 04:01:17.970
post-fire where you can do some things

04:01:17.970 --> 04:01:20.730
that are different rather
than just sort of putting lines

04:01:20.730 --> 04:01:21.913
right back where they are.

04:01:21.913 --> 04:01:26.010
Similarly, you know, a disconnect with

04:01:26.010 --> 04:01:29.580
the other wildfire mitigation plans

04:01:29.580 --> 04:01:33.530
or community wildfire
protection plans that exist.

04:01:33.530 --> 04:01:37.450
So what I don't see as sort of
a systemic or integrated way

04:01:37.450 --> 04:01:41.050
where the Wildfire
Mitigation Plan is talking

04:01:41.050 --> 04:01:44.370
to the community
wildfire protection plans

04:01:44.370 --> 04:01:46.410
and other Statewide efforts

04:01:46.410 --> 04:01:49.820
like Governor Newsome's 30 by 30 effort

04:01:49.820 --> 04:01:54.000
to restore the wild lands
and seeing that integration.

04:01:54.000 --> 04:01:55.350
'Cause obviously, you know,

04:01:55.350 --> 04:01:57.750
these plans don't exist in a vacuum

04:01:57.750 --> 04:02:01.070
and while I've heard
some sort of anecdotal, hey,

04:02:01.070 --> 04:02:03.830
we work with the city
when they reach out to us,

04:02:03.830 --> 04:02:07.320
I wanted to see where as
part of the planning effort,

04:02:07.320 --> 04:02:10.060
these things are more
systematically incorporated.

04:02:10.060 --> 04:02:13.710
And the last point in terms
of a disconnect is really trying

04:02:13.710 --> 04:02:17.840
to understand what are
the external variables

04:02:17.840 --> 04:02:21.010
and what do you have
as sort of a plan B,

04:02:21.010 --> 04:02:23.700
plan C to respond to that?

04:02:23.700 --> 04:02:27.290
So those things might be
things like COVID where,

04:02:27.290 --> 04:02:32.110
how are you going to address
depending on that, or if you,

04:02:32.110 --> 04:02:34.763
you know, your tree
trimmers or contractors,

04:02:35.640 --> 04:02:38.130
you sort of stop their tree
trimming and you have

04:02:38.130 --> 04:02:41.180
to find other available contractors.

04:02:41.180 --> 04:02:42.450
Just trying to understand

04:02:42.450 --> 04:02:45.070
where you have built into those plans,

04:02:45.070 --> 04:02:49.190
that type of integration and
where you can fill those gaps.

04:02:49.190 --> 04:02:50.023
Thank you.

04:03:00.380 --> 04:03:03.120
<v ->Well, I'll, I'll take a stab
at trying to answer that.</v>

04:03:03.120 --> 04:03:08.120
So, so first off, let me start by...

04:03:08.170 --> 04:03:11.040
I don't know that I necessarily
agree that I see a benefit

04:03:11.040 --> 04:03:14.583
in a, in a post fire or situation to,

04:03:16.220 --> 04:03:18.827
to do things different than
what we currently doing.

04:03:18.827 --> 04:03:19.940
And the reason I say that is,

04:03:19.940 --> 04:03:23.710
is it's seldom in a situation
after fire that there's,

04:03:23.710 --> 04:03:25.480
there's no customers left, right?

04:03:25.480 --> 04:03:28.740
W what I've my experience
has been over the last few years

04:03:28.740 --> 04:03:31.720
is that while there's a
considerable amount of destruction,

04:03:31.720 --> 04:03:34.410
there's still some surviving
homes and people in those

04:03:34.410 --> 04:03:38.961
communities who want their
power restored and are not always

04:03:38.961 --> 04:03:43.330
able to wait for say an
undergrounding project to occur

04:03:43.330 --> 04:03:45.180
or the lines to be relocated.

04:03:45.180 --> 04:03:49.100
And so that is something
though that we do look into,

04:03:49.100 --> 04:03:53.720
I know PG and E has
worked to identify situations

04:03:53.720 --> 04:03:56.733
where it makes sense to underground,

04:03:57.710 --> 04:04:01.990
but undergrounding is a very
long process to, to undergo.

04:04:01.990 --> 04:04:05.900
And it's when you still have
surviving houses and customers

04:04:05.900 --> 04:04:09.993
who want power and need
power to, to resume their lives,

04:04:11.020 --> 04:04:14.090
being able to stop and just do
undergrounding is not always

04:04:14.090 --> 04:04:15.764
a viable solution.

04:04:15.764 --> 04:04:18.040
We do have some situations

04:04:18.040 --> 04:04:21.840
where we've done
alternate generation means.

04:04:21.840 --> 04:04:25.860
So I know we have quite
a few system locations

04:04:25.860 --> 04:04:27.570
where it's basically,

04:04:27.570 --> 04:04:31.160
we've got miles of one line
feeding a single customer,

04:04:31.160 --> 04:04:33.220
and we use these opportunities both

04:04:33.220 --> 04:04:34.804
after a wildfire or during,

04:04:34.804 --> 04:04:36.770
or during our normal course of business

04:04:36.770 --> 04:04:40.370
to target those individuals
and either convert them

04:04:40.370 --> 04:04:43.470
to solar or convert them
to some other means of,

04:04:43.470 --> 04:04:48.470
of generation so that they
can get off of the normal grid.

04:04:48.880 --> 04:04:51.249
And then we don't have to continue,

04:04:51.249 --> 04:04:52.082
we don't have to rebuild the line,

04:04:52.082 --> 04:04:54.963
or we don't have to continue
to maintain that existing line.

04:04:57.540 --> 04:04:59.150
And then for your second question,

04:04:59.150 --> 04:05:00.530
and I wasn't totally clear on this.

04:05:00.530 --> 04:05:04.840
So you're asking about how
we have contingency plans

04:05:04.840 --> 04:05:07.350
for the unexpected things that can occur

04:05:07.350 --> 04:05:11.700
like such as COVID was that
where you were going with that?

04:05:11.700 --> 04:05:14.653
<v ->Yeah, so the other
two areas are integration</v>

04:05:14.653 --> 04:05:17.510
with other wildfire mitigation plans,

04:05:17.510 --> 04:05:19.680
like community wildfire protection plan.

04:05:19.680 --> 04:05:21.730
So as an example, I was
on the Steering Committee

04:05:21.730 --> 04:05:25.190
for the Santa Rosa and the county has

04:05:25.190 --> 04:05:28.130
another community
wildfire protection plan.

04:05:28.130 --> 04:05:31.870
And what I don't see within
those and others is here's

04:05:31.870 --> 04:05:36.870
where PG and E or other
utilities tie into those plans.

04:05:36.870 --> 04:05:40.200
That's where your
vegetation management is,

04:05:40.200 --> 04:05:42.970
is within their strategic plan

04:05:42.970 --> 04:05:46.470
and their efforts are
embedded with your plan.

04:05:46.470 --> 04:05:49.400
And yes, those external
variables are important

04:05:49.400 --> 04:05:52.180
because part of what I
gather from what you said,

04:05:52.180 --> 04:05:54.720
which is a disconnect for me is every

04:05:55.690 --> 04:05:57.730
wildfire professional that I've spoken

04:05:57.730 --> 04:06:00.690
to is that there is this
unique opportunity

04:06:00.690 --> 04:06:03.410
when a wildfire hits to turn a burn scar

04:06:03.410 --> 04:06:05.600
into a firebreak or a fuel break,

04:06:05.600 --> 04:06:07.420
or to think about undergrounding.

04:06:07.420 --> 04:06:10.810
I think PG and E actually
looked at the situation

04:06:10.810 --> 04:06:13.100
in Paradise as an
example, and said, look,

04:06:13.100 --> 04:06:15.024
that's where we need to undergrounds

04:06:15.024 --> 04:06:16.710
to sort of from their mistakes.

04:06:16.710 --> 04:06:20.090
In 2017, with just putting
it right back where it was,

04:06:20.090 --> 04:06:22.110
even though there's
a lot of pressure there

04:06:22.110 --> 04:06:24.690
to have that strategy in place,

04:06:24.690 --> 04:06:25.860
so that you're ready to go.

04:06:25.860 --> 04:06:28.880
So just trying to understand
what you've developed

04:06:28.880 --> 04:06:31.120
since that time to
have it more ingrained

04:06:31.120 --> 04:06:33.380
in your wildfire mitigation plan.

04:06:33.380 --> 04:06:34.530
That makes sense?

04:06:34.530 --> 04:06:35.620
<v ->Right?</v>

04:06:35.620 --> 04:06:36.780
Well, as I said, we do,

04:06:36.780 --> 04:06:39.890
we do try and target areas
for another approach in you.

04:06:39.890 --> 04:06:42.230
But I would say what the other piece is,

04:06:42.230 --> 04:06:46.250
is that utility's responsibility is,

04:06:46.250 --> 04:06:47.920
is to its infrastructure.

04:06:47.920 --> 04:06:50.600
You know, that's our
core responsibility there.

04:06:50.600 --> 04:06:53.510
And of course we want to be
partners with the communities,

04:06:53.510 --> 04:06:55.487
and that's why we do work
with the different communities

04:06:55.487 --> 04:06:58.538
and what they're trying to accomplish.

04:06:58.538 --> 04:07:01.550
But eight, and, and you'll see that

04:07:01.550 --> 04:07:03.730
there are examples where
PG and E's right away,

04:07:03.730 --> 04:07:05.750
especially our transmission
right-of-ways are used

04:07:05.750 --> 04:07:08.250
as natural fuel breaks or not natural,

04:07:08.250 --> 04:07:11.420
but newly created fuel
breaks to protect certain cities,

04:07:11.420 --> 04:07:14.060
but it doesn't always work out that way.

04:07:14.060 --> 04:07:18.430
And so the location
may not be ideal for,

04:07:18.430 --> 04:07:21.830
for a fuel break or may not be included

04:07:21.830 --> 04:07:23.160
in the local community's plan

04:07:23.160 --> 04:07:25.660
for where the established break is.

04:07:25.660 --> 04:07:28.847
And so, while we're certainly
willing to work locally, I,

04:07:28.847 --> 04:07:31.650
if there are additional
steps and requirements

04:07:31.650 --> 04:07:33.960
that kind of make that difficult,

04:07:33.960 --> 04:07:37.320
but I'd like to think, and
if, if this isn't the case,

04:07:37.320 --> 04:07:38.480
I certainly will take this back.

04:07:38.480 --> 04:07:40.320
But I'd like to think that PG
and E is always willing to be

04:07:40.320 --> 04:07:43.683
at the table during those
discussions to be part of that.

04:07:44.620 --> 04:07:48.670
As I mentioned in our Defensible
Space Presentation earlier,

04:07:48.670 --> 04:07:51.270
we are working with those
communities when they do reach out

04:07:51.270 --> 04:07:54.310
and we're happy to be at the
table during those discussions,

04:07:54.310 --> 04:07:58.550
and look for opportunities
to, to collaborate.

04:07:58.550 --> 04:08:03.550
But, you know, my job is
to make sure that the, the,

04:08:03.670 --> 04:08:06.430
the overhead lines
are clear of vegetation.

04:08:06.430 --> 04:08:08.460
And when I can find
opportunities to overlap

04:08:08.460 --> 04:08:10.320
with local community, I'm
more than happy to do it,

04:08:10.320 --> 04:08:14.220
but I'm not going to create a firebreak

04:08:14.220 --> 04:08:16.120
that's outside of my easement.

04:08:16.120 --> 04:08:19.530
That's just not what my
responsibility is as a utility.

04:08:19.530 --> 04:08:22.623
And, but I'm happy to partner
when they do line up well.

04:08:31.462 --> 04:08:33.050
I don't know if any of the other folks

04:08:33.050 --> 04:08:34.160
have anything to add.

04:08:34.160 --> 04:08:35.681
<v ->Yeah, sure, Steven.</v>

04:08:35.681 --> 04:08:39.470
<v ->Thank you.</v>
<v ->So, in terms of speaking</v>

04:08:39.470 --> 04:08:42.310
on fire restorations specifically,

04:08:42.310 --> 04:08:45.210
I think Steven raised a couple
of good points in terms of

04:08:45.210 --> 04:08:48.850
the urgency of restoring
power in the moment.

04:08:48.850 --> 04:08:51.140
For SCE, we had a significant fire

04:08:51.140 --> 04:08:52.380
in our territory last year,

04:08:52.380 --> 04:08:55.610
which was the Creek Fire, and required

04:08:55.610 --> 04:08:59.670
over 1,000 vegetation
management personnel,

04:08:59.670 --> 04:09:02.200
mostly contractor in order to support

04:09:02.200 --> 04:09:04.270
the restoration activities up there.

04:09:04.270 --> 04:09:07.900
So I, you know, certainly
when the moment arrives

04:09:07.900 --> 04:09:11.470
and we're trying to clear
trees that have been damaged

04:09:11.470 --> 04:09:14.040
from the fire are, you know, are our,

04:09:14.040 --> 04:09:16.620
we're trying to protect the,
not just the infrastructure,

04:09:16.620 --> 04:09:18.410
that's going to be built
and create enough room

04:09:18.410 --> 04:09:20.013
to build the infrastructure,

04:09:20.013 --> 04:09:23.650
but we're trying to
actually create the space

04:09:23.650 --> 04:09:25.930
around the infrastructure that we need

04:09:25.930 --> 04:09:28.870
to maintain on an ongoing basis.

04:09:28.870 --> 04:09:30.510
And, and I make that distinction

04:09:30.510 --> 04:09:33.740
because I didn't want folks on this call

04:09:33.740 --> 04:09:35.594
to walk away with the idea that it's,

04:09:35.594 --> 04:09:39.140
it's always really easy to
keep that, that clearance, right?

04:09:39.140 --> 04:09:42.810
We have a lot of barriers
that come up from the people

04:09:42.810 --> 04:09:45.800
who own the property, who
own the trees in many cases.

04:09:45.800 --> 04:09:49.560
And so what we can do in
a situation of fire restoration

04:09:49.560 --> 04:09:52.460
is talk to the property
owners to the extent

04:09:52.460 --> 04:09:56.130
that they're there, or
the fire or the agency,

04:09:56.130 --> 04:09:59.690
if it's a federal or state
agency, local government land,

04:09:59.690 --> 04:10:03.280
and talk to them about
expanding the opportunity for us to,

04:10:03.280 --> 04:10:06.650
to create that pole
clearance, and in the process

04:10:06.650 --> 04:10:08.400
that may well create a fire break.

04:10:08.400 --> 04:10:11.330
So I think, you
know, it is, it is in fact,

04:10:11.330 --> 04:10:13.860
an opportunity that
we're seizing on to say,

04:10:13.860 --> 04:10:18.130
okay, not only do we want
to get, you know, just get the,

04:10:18.130 --> 04:10:19.570
get the facility, you know,

04:10:19.570 --> 04:10:22.900
get the trucks and the equipment
in and out of here, but no,

04:10:22.900 --> 04:10:25.500
we actually want to set this
up in a sustainable manner.

04:10:25.500 --> 04:10:26.970
And I can tell you from the Creek Fire,

04:10:26.970 --> 04:10:29.040
one of the other things
we're doing is we're using this

04:10:29.040 --> 04:10:31.410
as an opportunity to do a pilot

04:10:31.410 --> 04:10:33.640
on some integrated veg management

04:10:33.640 --> 04:10:37.390
where we're at a very small scale.

04:10:37.390 --> 04:10:39.480
So it's not highlighted in the WMP,

04:10:39.480 --> 04:10:43.600
but we're looking for
opportunity to see if we can foster

04:10:43.600 --> 04:10:47.070
the growth of more low growing species,

04:10:47.070 --> 04:10:49.270
which are more compatible
with our right of ways

04:10:49.270 --> 04:10:51.090
and not something that
would require a maintenance

04:10:51.090 --> 04:10:51.923
in the future.

04:10:53.380 --> 04:10:56.180
In terms of integrating with, you know,

04:10:56.180 --> 04:10:57.610
or dealing with contingency plans

04:10:57.610 --> 04:11:01.310
in terms of local communities
and their planning,

04:11:01.310 --> 04:11:03.570
the major area of
intersection for us seems

04:11:03.570 --> 04:11:07.620
to be with leveraging
local fire councils

04:11:07.620 --> 04:11:09.549
to support our efforts.

04:11:09.549 --> 04:11:12.640
And so while it may not be
integrated at the plan level,

04:11:12.640 --> 04:11:14.830
and I think that that's
something worth pursuing,

04:11:14.830 --> 04:11:17.690
because if we can integrate
our work into their plans,

04:11:17.690 --> 04:11:20.500
that would certainly bolster
our position and making

04:11:20.500 --> 04:11:24.237
the argument that we need
to trim X-tree, remove Y-tree.

04:11:24.237 --> 04:11:27.575
And so I will take that back
is something we can consider

04:11:27.575 --> 04:11:29.913
to more to formalize that.

04:11:30.750 --> 04:11:33.040
Right now, what we tend
to do today is we're having,

04:11:33.040 --> 04:11:34.970
when we're having
conversations with a community,

04:11:34.970 --> 04:11:39.970
let's say it's a, a city,
you know, mayor or board,

04:11:41.750 --> 04:11:44.610
or dealing with individual
homeowners associations

04:11:44.610 --> 04:11:49.300
will try to generate support
from that local fire chief

04:11:49.300 --> 04:11:52.170
or the fire agency,

04:11:52.170 --> 04:11:55.880
and just get them to
understand what our plan is

04:11:55.880 --> 04:11:57.980
and how that does
integrate with their desires.

04:11:57.980 --> 04:12:01.480
And in some cases that is
effective at overcoming resistance

04:12:01.480 --> 04:12:04.760
regarding the work that
we're trying to accomplish,

04:12:04.760 --> 04:12:07.363
and maybe not always
as easily as we would like.

04:12:10.300 --> 04:12:12.330
And I think one final
point you mentioned

04:12:12.330 --> 04:12:14.380
was around COVID-19 and contingency.

04:12:14.380 --> 04:12:18.160
So I will just add there,
will that be, you know,

04:12:18.160 --> 04:12:21.130
internally we have a pretty
strong matrix approach

04:12:21.130 --> 04:12:23.761
to see what happens if
we're unable to complete

04:12:23.761 --> 04:12:26.940
all of the work we have
planned under the circumstances

04:12:26.940 --> 04:12:29.810
and what are the thresholds
that would require us

04:12:29.810 --> 04:12:34.103
to reconsider various actions
under those circumstances?

04:12:37.630 --> 04:12:40.530
<v ->Yeah, and just to add
a few more things to this,</v>

04:12:40.530 --> 04:12:43.820
I PG and E and shouldn't
have answered it very well,

04:12:43.820 --> 04:12:48.806
but I would just say to you
on kind of the context from,

04:12:48.806 --> 04:12:52.630
can you like go in and underground,

04:12:52.630 --> 04:12:54.614
like a whole system on something

04:12:54.614 --> 04:12:55.447
that burned down afterwards?

04:12:55.447 --> 04:12:56.980
Now our OPER mitigation
funds are very focused

04:12:56.980 --> 04:13:00.200
on preventing the, the
catastrophic ignition.

04:13:00.200 --> 04:13:03.400
So preventing all
risk events at ignitions,

04:13:03.400 --> 04:13:06.500
but I would agree with, with,
what's been, what's been said,

04:13:06.500 --> 04:13:11.100
and there's usually still some
customers that are, that you,

04:13:11.100 --> 04:13:13.934
you know, do have homes
that are not from down.

04:13:13.934 --> 04:13:14.767
And we're trying to
restore service as quickly

04:13:14.767 --> 04:13:17.343
as possible and to restore service,

04:13:18.200 --> 04:13:20.300
there's a lot of engineering involved,

04:13:20.300 --> 04:13:21.350
no matter what you're doing.

04:13:21.350 --> 04:13:23.070
A lot of the reason
restoration is fast is

04:13:23.070 --> 04:13:24.870
because we're going back with

04:13:24.870 --> 04:13:27.185
the exact same
structure, types, locations,

04:13:27.185 --> 04:13:30.510
so that we know in
attachments, it was there before,

04:13:30.510 --> 04:13:34.387
so that your, so that your, you know,

04:13:34.387 --> 04:13:35.730
the engineering's already been done

04:13:35.730 --> 04:13:37.107
to know that that's
going to work, right?

04:13:37.107 --> 04:13:39.979
You have the right
clearances, you have the right a,

04:13:39.979 --> 04:13:41.080
you have an a right structure.

04:13:41.080 --> 04:13:43.149
If you were to say, hey,

04:13:43.149 --> 04:13:45.043
we're just going to go ahead
and underground this well,

04:13:45.043 --> 04:13:46.290
you haven't done any conflict studies.

04:13:46.290 --> 04:13:48.840
You don't know if you're
gonna hit a water pipe, gas lines,

04:13:48.840 --> 04:13:51.510
all the things that are
doing under, underground,

04:13:51.510 --> 04:13:53.420
it takes, you know,

04:13:53.420 --> 04:13:56.850
about a year typically
to do a pole design.

04:13:56.850 --> 04:13:57.880
You need to get your cut lines,

04:13:57.880 --> 04:14:01.270
your cable pulling tensions
site, your manholes.

04:14:01.270 --> 04:14:02.130
There's a lot,

04:14:02.130 --> 04:14:04.630
I would say there's a lot
that goes into planning,

04:14:06.010 --> 04:14:08.590
the design engineering
and construction of aligned

04:14:08.590 --> 04:14:10.660
to be reliable over the long term.

04:14:10.660 --> 04:14:12.630
And then when we get
into emergency planning,

04:14:12.630 --> 04:14:14.130
we really are typically just going back

04:14:14.130 --> 04:14:16.193
with what was there before,

04:14:17.530 --> 04:14:19.670
because we know there's a design

04:14:19.670 --> 04:14:22.390
that didn't work reliably before.

04:14:22.390 --> 04:14:25.610
So it, it, again, I think in the plan,

04:14:25.610 --> 04:14:27.589
the focus really is on prevention.

04:14:27.589 --> 04:14:30.833
That that is the goal
to not start those fires.

04:14:32.420 --> 04:14:33.253
Thanks.

04:14:33.253 --> 04:14:34.200
<v ->Thanks for that answer.</v>

04:14:34.200 --> 04:14:37.330
I just guess what, just
something to take back.

04:14:37.330 --> 04:14:40.880
It really is this unique window
of opportunity to do things

04:14:40.880 --> 04:14:42.915
at a much lower cost cost.

04:14:42.915 --> 04:14:45.070
You know, roads are, are, are,

04:14:45.070 --> 04:14:47.694
are already going to be rebuilt.

04:14:47.694 --> 04:14:49.270
People's homes are destroyed,

04:14:49.270 --> 04:14:51.240
so you can underground more easily,

04:14:51.240 --> 04:14:52.370
there's opportunities there.

04:14:52.370 --> 04:14:55.210
So some of the things that
you just talked about and touring

04:14:55.210 --> 04:14:58.200
in terms of doing that
strategic work upfront,

04:14:58.200 --> 04:15:01.250
so that you have a plan in
higher fire threat districts,

04:15:01.250 --> 04:15:05.380
so that you can both do
the short-term, restore power,

04:15:05.380 --> 04:15:10.040
and improve the, you know,
longer term mitigation efforts.

04:15:10.040 --> 04:15:11.900
<v ->I think, you know,</v>

04:15:11.900 --> 04:15:14.330
seems to me like an
area that we should all

04:15:14.330 --> 04:15:16.810
be focused on, not just the utilities,

04:15:16.810 --> 04:15:19.970
but all of us coordinating
together so that we can use

04:15:19.970 --> 04:15:22.020
these opportunities
to really work together

04:15:22.020 --> 04:15:23.930
towards common interests.

04:15:23.930 --> 04:15:24.763
But thank you.

04:15:31.170 --> 04:15:33.660
<v ->Thank you Will,
for your question.</v>

04:15:33.660 --> 04:15:37.193
Next, Zoey Harold from
the Green Power Institute.

04:15:39.500 --> 04:15:40.560
<v Zoey>Hello everyone.</v>

04:15:40.560 --> 04:15:42.510
Zoey Harold from Green Power Institute.

04:15:43.718 --> 04:15:47.350
So our question is
essentially a continuation of

04:15:47.350 --> 04:15:52.350
the WSD question on fuel load
and then VM and EVM residues.

04:15:52.400 --> 04:15:54.463
And I'll ask it in two parts.

04:15:55.640 --> 04:15:59.617
There was a mention that
palm has limited use pathways,

04:15:59.617 --> 04:16:02.290
but we know some biomass facilities,

04:16:02.290 --> 04:16:06.350
for example, the 50
megawatt desert view facility

04:16:06.350 --> 04:16:09.340
in Mecca can actually
utilize palm residues.

04:16:09.340 --> 04:16:12.960
And so our question
was have the utilities

04:16:12.960 --> 04:16:15.373
with palm residues actually explore

04:16:15.373 --> 04:16:18.217
these biomass facilities
and residue pathways?

04:16:18.217 --> 04:16:22.070
And then the second part
of that was for PG and E.

04:16:22.070 --> 04:16:27.020
So we are curious as to whether

04:16:27.020 --> 04:16:30.972
the residue removal process
and incomplete removal of

04:16:30.972 --> 04:16:35.650
those residues is leading to the need

04:16:35.650 --> 04:16:38.280
and consideration of
using fire retardants?

04:16:38.280 --> 04:16:42.380
And so if there was more
complete removal of those residues,

04:16:42.380 --> 04:16:44.880
would that reduce the
need to use fire retardants?

04:16:45.859 --> 04:16:46.692
Thanks.

04:16:53.232 --> 04:16:54.690
<v ->Okay, well, I'll, I'll answer.</v>

04:16:54.690 --> 04:16:59.690
So palms make up such a
small percentage of our, our trims.

04:17:00.130 --> 04:17:01.930
I don't think we've
looked into that at all.

04:17:01.930 --> 04:17:05.870
I don't even think it's,
but I'll follow up on that,

04:17:05.870 --> 04:17:07.410
but I don't think there's
much in the palms,

04:17:07.410 --> 04:17:10.230
but specifically to the reason behind

04:17:10.230 --> 04:17:12.790
the fire retardant, again
goes back to prevention.

04:17:12.790 --> 04:17:14.290
It hasn't, it doesn't have anything

04:17:14.290 --> 04:17:17.260
to do with the loading of the fuel.

04:17:17.260 --> 04:17:18.800
What we're looking to do is

04:17:20.760 --> 04:17:24.720
you can have a wire down
event for a variety of reasons,

04:17:24.720 --> 04:17:27.140
you know, a bird
strike, equipment failure,

04:17:27.140 --> 04:17:31.339
or vegetation strike, a
carpool, the list goes on.

04:17:31.339 --> 04:17:35.180
And in all cases, what
typically causes the fire

04:17:35.180 --> 04:17:37.580
to spread is that flashy
fuel, that brush that's

04:17:37.580 --> 04:17:40.757
underneath the, the conductors.

04:17:40.757 --> 04:17:44.190
I've been out to multiple
sites where trees fell

04:17:44.190 --> 04:17:46.040
on the line and the
tree, which is still alive,

04:17:46.040 --> 04:17:48.560
tends to not burn, but
it's all the dead brush

04:17:48.560 --> 04:17:49.393
on the ground.

04:17:49.393 --> 04:17:52.850
And so the concept behind
applying that flame retardant

04:17:52.850 --> 04:17:57.850
would be that if the wire does
break and has a down event,

04:17:57.925 --> 04:18:00.680
it doesn't have anything
on the ground that can ignite.

04:18:00.680 --> 04:18:03.810
And we've tried in the
past, PG and E is trying

04:18:03.810 --> 04:18:06.490
to pass of going to
bare minimal soil that met

04:18:06.490 --> 04:18:09.180
with some pretty stiff
resistance from the communities.

04:18:09.180 --> 04:18:11.340
And also just, you know,

04:18:11.340 --> 04:18:13.820
has issues with this sustainability.

04:18:13.820 --> 04:18:17.320
But the flame-retardant is
something that we're looking into

04:18:17.320 --> 04:18:21.080
because you can still have
some vegetation on the ground

04:18:21.080 --> 04:18:22.920
with that flame retardant applied to it.

04:18:22.920 --> 04:18:27.788
And in some of our laboratory
tests that we've done,

04:18:27.788 --> 04:18:31.600
it reduces the likelihood
pretty substantially of

04:18:31.600 --> 04:18:33.223
a mission breaking out.

04:18:34.680 --> 04:18:38.680
And so in we're looking
to do prevention, that's,

04:18:38.680 --> 04:18:40.810
that's our primary
focus here, and in this,

04:18:40.810 --> 04:18:42.290
what we've seen just in,

04:18:42.290 --> 04:18:46.720
in laboratory tests is that
the application that flight

04:18:46.720 --> 04:18:50.690
a flame retardant significantly
reduces the likelihood of

04:18:50.690 --> 04:18:54.060
a spark breaking out,
turning it into a fire.

04:18:54.060 --> 04:18:58.310
And then it also has the added
benefit that it prevents that

04:18:58.310 --> 04:19:01.320
or slows that fire from
turning into a wildfire.

04:19:01.320 --> 04:19:04.470
And that spread is so much reduced

04:19:04.470 --> 04:19:06.660
that local emergency
personnel can get out there

04:19:06.660 --> 04:19:10.050
and put the fire out
before it gets out of control.

04:19:10.050 --> 04:19:10.980
So that's why we're doing it.

04:19:10.980 --> 04:19:13.077
It doesn't have anything to do with the,

04:19:13.077 --> 04:19:16.520
the fuel loading left by our work

04:19:16.520 --> 04:19:21.520
or by other existing
vegetation that's out there.

04:19:25.670 --> 04:19:27.420
<v ->And this is
Michael (indistinct),</v>

04:19:31.207 --> 04:19:32.040
just concur with BJ's.

04:19:32.040 --> 04:19:36.170
And similarly, we try to
a pilot project last year

04:19:36.170 --> 04:19:38.140
of use of where to fly,

04:19:38.140 --> 04:19:41.430
which is a it's tough
requirement on a communion.

04:19:41.430 --> 04:19:46.090
And we've piloted it on
about a two-mile stretch of

04:19:46.090 --> 04:19:48.067
our facilities of 100 (indistinct).

04:19:49.610 --> 04:19:52.600
And we were just looking,
just ask to see again,

04:19:52.600 --> 04:19:54.060
if incrementally what's,

04:19:54.060 --> 04:19:58.323
what added benefit can we
get as to reduce our ignition?

04:19:58.323 --> 04:20:00.730
What we're finding out
though, is that it comes

04:20:01.636 --> 04:20:03.780
at a very high cost, especially Harrison

04:20:03.780 --> 04:20:07.840
between traditional rushing
or mechanically removing

04:20:07.840 --> 04:20:10.020
all of the vegetation.

04:20:10.020 --> 04:20:13.570
We're going to continue looking
at that and use that product

04:20:13.570 --> 04:20:17.140
this year, again, to, to
negative comparative analysis,

04:20:17.140 --> 04:20:19.420
whether it makes sense to continue this

04:20:19.420 --> 04:20:23.994
from an efficacy standpoint
and an efficiency standpoint.

04:20:23.994 --> 04:20:28.380
Where we differ with Eugenia
obviously is with regard

04:20:28.380 --> 04:20:30.100
to palms, you know, San Diego,

04:20:30.100 --> 04:20:35.100
obviously would be a
premier signature EC's,

04:20:35.910 --> 04:20:40.490
so most of the palms
that we have are non emic,

04:20:42.340 --> 04:20:43.393
they don't grow here,

04:20:44.486 --> 04:20:46.030
and they don't originate
here at San Diego.

04:20:46.030 --> 04:20:48.570
So we are really challenged with palms

04:20:48.570 --> 04:20:49.710
as a space investment.

04:20:49.710 --> 04:20:52.750
That's why it was most of
our top (indistinct) species,

04:20:52.750 --> 04:20:56.373
really practically trying to
remove palms whenever we can.

04:20:57.220 --> 04:21:00.630
We do that with very lasting engagement

04:21:00.630 --> 04:21:02.800
with customers, explaining to them

04:21:02.800 --> 04:21:05.640
the reasons why it's
beneficial to cut the palm out

04:21:05.640 --> 04:21:08.000
and so unlike other species,

04:21:08.000 --> 04:21:11.010
palm is not even a tree species.

04:21:11.010 --> 04:21:12.590
It's a member the grass family,

04:21:12.590 --> 04:21:14.250
we cannot direct it's growth,

04:21:14.250 --> 04:21:16.426
all the way to the power line.

04:21:16.426 --> 04:21:18.160
And so once it reached high,

04:21:18.160 --> 04:21:20.190
we have to remove it completely.

04:21:21.078 --> 04:21:23.703
And then we're left with a residual.

04:21:24.890 --> 04:21:28.899
A lot of our, most of our
landfills do take palm debris

04:21:28.899 --> 04:21:31.293
as far as a higher
(muffled speaking) here,

04:21:32.710 --> 04:21:34.350
our Rosette Recycling Facility,

04:21:34.350 --> 04:21:38.080
one of our recycling
facilities does take palms,

04:21:38.080 --> 04:21:39.963
but it is of a limited use,

04:21:40.808 --> 04:21:44.490
or there is not as much
of a hierarchy if you will,

04:21:44.490 --> 04:21:47.730
as a recyclable material, but we,

04:21:47.730 --> 04:21:50.885
we are interested in
investigating different options

04:21:50.885 --> 04:21:53.370
for utilization of palm matures,

04:21:53.370 --> 04:21:55.680
especially given that we do generate

04:21:55.680 --> 04:21:59.323
a relatively high number
of palm residue here.

04:22:05.950 --> 04:22:08.190
<v ->Yeah, I'll, I'll start
off with palms as well,</v>

04:22:08.190 --> 04:22:11.153
just going on from Michael's response.

04:22:12.100 --> 04:22:14.780
So I think we've heard in
the prior two responses,

04:22:14.780 --> 04:22:17.820
some reference to economics and the fact

04:22:17.820 --> 04:22:20.320
that we are stewards of our rate payers

04:22:20.320 --> 04:22:22.940
and need to keep rates
affordable for them.

04:22:22.940 --> 04:22:25.720
So I heard you on the, on the location

04:22:25.720 --> 04:22:28.080
in Mecca that would be
interested in palm waste.

04:22:28.080 --> 04:22:30.420
And so I think to the
extent that we have qualms

04:22:30.420 --> 04:22:32.630
in that vicinity of our territory,

04:22:32.630 --> 04:22:34.260
at least leading out in that direction,

04:22:34.260 --> 04:22:35.450
'cause that's is outside of,

04:22:35.450 --> 04:22:38.156
I think all three of
the utilities territories,

04:22:38.156 --> 04:22:40.380
where it becomes economically feasible

04:22:40.380 --> 04:22:42.767
to transport to that location.

04:22:42.767 --> 04:22:44.770
And that definitely seems feasible.

04:22:44.770 --> 04:22:47.280
I think what we would
find is that in a situation

04:22:47.280 --> 04:22:49.860
where many of our
palms are actually located

04:22:49.860 --> 04:22:53.624
in coastal areas, so up
near Santa Barbara for us.

04:22:53.624 --> 04:22:57.000
And so that you're contrasting
the option to take that

04:22:57.000 --> 04:22:58.790
to a local landfill that would accept

04:22:58.790 --> 04:23:03.790
the palm versus a much
farther in, in interior location

04:23:05.320 --> 04:23:08.060
that might have a higher and better use.

04:23:08.060 --> 04:23:09.960
It would come down to is the,

04:23:09.960 --> 04:23:13.670
is the economic cost or additional rate

04:23:13.670 --> 04:23:15.950
that that would create
for the customers,

04:23:15.950 --> 04:23:20.130
then a benefit that for which
the environmental benefit

04:23:20.130 --> 04:23:21.370
outweighs that?

04:23:21.370 --> 04:23:26.040
And so I think that is something
that we take very seriously

04:23:26.040 --> 04:23:29.450
and we need to look carefully
at what the impacts would be

04:23:29.450 --> 04:23:33.500
for extensive transit of
that kind of waste material.

04:23:33.500 --> 04:23:36.850
And I don't know that there's
a lot more to add with regard

04:23:36.850 --> 04:23:40.910
to the idea of the product fortify,

04:23:40.910 --> 04:23:42.840
which Michael specifically identified,

04:23:42.840 --> 04:23:46.380
but we are also taking a look at that.

04:23:46.380 --> 04:23:50.323
I'm trying to see if that in
any way fits into our future.

04:23:59.050 --> 04:23:59.917
<v ->Thank you for
that question, Zoey.</v>

04:23:59.917 --> 04:24:02.400
And I have a quick follow up question

04:24:02.400 --> 04:24:03.780
for Michael and Steven.

04:24:03.780 --> 04:24:07.130
You both talked about
piloting fire retardants

04:24:08.640 --> 04:24:09.650
in your right of ways.

04:24:09.650 --> 04:24:13.960
And I was just curious
about the length of efficacy of

04:24:13.960 --> 04:24:17.870
that fire retardant and
whether like when it's applied

04:24:17.870 --> 04:24:21.377
and how often it needs to
be reapplied to be effective?

04:24:24.200 --> 04:24:28.293
<v ->So in our initial
laboratory tests,</v>

04:24:29.571 --> 04:24:32.890
we actually haven't done
much out in the field aside

04:24:32.890 --> 04:24:35.260
from planning a fire response.

04:24:35.260 --> 04:24:37.861
But during our laboratory tests,

04:24:37.861 --> 04:24:40.190
we were told that
basically it's good for a year.

04:24:40.190 --> 04:24:42.440
So it has to be reapplied annually

04:24:42.440 --> 04:24:47.440
or after I believe it
was two inches of rain,

04:24:47.540 --> 04:24:49.660
which if we got two inches of rain,

04:24:49.660 --> 04:24:52.020
we would be extremely
happy and wouldn't be worried

04:24:52.020 --> 04:24:54.540
too much anymore
about the fire retardant.

04:24:54.540 --> 04:24:58.150
So that seemed to, I mean, it'd be nice.

04:24:58.150 --> 04:25:02.339
It was better than
annually, but it seems to,

04:25:02.339 --> 04:25:04.090
it, it seemed like it would last

04:25:04.090 --> 04:25:06.240
during fire season
is our initial reaction.

04:25:09.650 --> 04:25:11.290
<v ->I think we'd all rather it rain</v>

04:25:11.290 --> 04:25:14.500
than it would be effective
for multiple fire seasons.

04:25:16.413 --> 04:25:18.050
(crosstalk)

04:25:18.050 --> 04:25:19.520
<v ->Sorry, one of the
things I'll just add is</v>

04:25:19.520 --> 04:25:22.810
we did also see a drop-off in efficiency

04:25:22.810 --> 04:25:24.760
for areas that were prone to high wind.

04:25:27.090 --> 04:25:27.923
Doesn't go to zero,

04:25:27.923 --> 04:25:31.200
but it does have an
impact, sustained wind,

04:25:31.200 --> 04:25:33.113
which again was done in a laboratory,

04:25:34.050 --> 04:25:35.540
did seem to have an impact.

04:25:35.540 --> 04:25:37.340
That was the only factor we noticed.

04:25:39.200 --> 04:25:40.490
Sorry Mike, didn't mean to cut you off.

04:25:40.490 --> 04:25:41.663
<v ->Oh no, no worries.</v>

04:25:42.970 --> 04:25:47.043
Similar for us at PG and E,
assessment of pilot project,

04:25:48.169 --> 04:25:53.169
a relatively small area that
we treated looks like we can,

04:25:54.142 --> 04:25:56.836
we can get one, maybe
two years out of this,

04:25:56.836 --> 04:25:58.920
but it all depends on hormonal factors.

04:25:58.920 --> 04:26:03.410
Like (muffled speaking)
at this juncture,

04:26:03.410 --> 04:26:07.740
we don't think it's necessarily
(muffled speaking) activity

04:26:07.740 --> 04:26:11.732
an augmenting activity in
conjunction with article rushing

04:26:11.732 --> 04:26:14.570
our enhancements tissue for instance,

04:26:14.570 --> 04:26:16.930
and reducing some of those finer fuels

04:26:16.930 --> 04:26:21.267
at specific holes that we
have within our operation.

04:26:27.620 --> 04:26:29.490
<v ->Great, thank you, Paul.</v>

04:26:31.377 --> 04:26:33.027
Next, I want to move to the chat.

04:26:33.880 --> 04:26:37.210
Ryan, are there any
lingering questions in the chat?

04:26:43.890 --> 04:26:44.723
<v Ryan>Hey, Colin,</v>

04:26:44.723 --> 04:26:47.280
Yep, we've got two
questions here in the chat.

04:26:47.280 --> 04:26:52.140
The first one is for
Steven and PG and E.

04:26:52.140 --> 04:26:55.290
Is the tree assessment
tool a proprietary program,

04:26:55.290 --> 04:26:58.920
or is it based on the
RGAs collector app?

04:26:58.920 --> 04:27:00.950
Where does it pull the
wind gust data from?

04:27:00.950 --> 04:27:04.963
Does this have to be entered
manually by the inspector?

04:27:07.750 --> 04:27:11.330
<v ->So the tool
itself is actually a,</v>

04:27:11.330 --> 04:27:13.430
I believe a certain when
you survey one, two, three,

04:27:13.430 --> 04:27:17.690
which is an add-on to
the RHS collector app.

04:27:17.690 --> 04:27:21.180
So the program itself,
I guess, is, I mean,

04:27:21.180 --> 04:27:22.270
it's not PD proprietary.

04:27:22.270 --> 04:27:26.368
You'd have to have
access to our GIS to use it,

04:27:26.368 --> 04:27:28.310
which we've bought a license for.

04:27:28.310 --> 04:27:31.020
It's more the, the questions,
a series of questions,

04:27:31.020 --> 04:27:33.550
which I, I try to get an answer on this.

04:27:33.550 --> 04:27:36.229
And I think the general
response from PG and E

04:27:36.229 --> 04:27:39.370
is it's not proprietary, it's
just a series of questions.

04:27:39.370 --> 04:27:42.410
And I, I believe we
probably disclosed it certainly

04:27:42.410 --> 04:27:45.700
to some of the regulatory agencies,

04:27:45.700 --> 04:27:47.890
the, the series of questions,

04:27:47.890 --> 04:27:52.890
the wind data comes from
PG and E's meteorology team,

04:27:53.511 --> 04:27:56.550
and they don't have
to enter it, what the,

04:27:56.550 --> 04:28:00.820
the way the system is set
up is that when they create

04:28:00.820 --> 04:28:03.130
the inventory point, when
they're out in the field,

04:28:03.130 --> 04:28:06.230
it takes a GPS
coordinator where they're at

04:28:06.230 --> 04:28:10.289
and pulls the relevant wind data.

04:28:10.289 --> 04:28:14.613
It's not real-time wind its
average wind speed for that,

04:28:14.613 --> 04:28:17.430
that area that they're in.
So that, that is a factor.

04:28:17.430 --> 04:28:20.640
So on the simplest of terms,

04:28:20.640 --> 04:28:23.810
it basically would put
in an added factor, says,

04:28:23.810 --> 04:28:26.000
this area is gets higher wind speeds,

04:28:26.000 --> 04:28:28.440
which would increase
the likelihood of a failure,

04:28:28.440 --> 04:28:31.170
which would increase the
likelihood of the tree needing

04:28:31.170 --> 04:28:33.480
to be, or being removed,

04:28:33.480 --> 04:28:37.670
if it has additional defects
that might make it weakened

04:28:37.670 --> 04:28:38.933
in a wind type event.

04:28:40.720 --> 04:28:43.487
So I think that's all the
questions for that one.

04:28:46.080 --> 04:28:47.740
<v Ryan>Got it.</v>

04:28:47.740 --> 04:28:49.174
All right, thank you.

04:28:49.174 --> 04:28:50.710
And calling there's one more for Edison.

04:28:50.710 --> 04:28:53.083
If you'd like, I could
read that one off now?

04:28:54.260 --> 04:28:56.020
<v ->Yes, go ahead.</v>

04:28:56.020 --> 04:29:01.020
<v Ryan>Great, purposes in 2005 051</v>

04:29:01.040 --> 04:29:02.560
utilities are supposed to provide

04:29:02.560 --> 04:29:05.250
a customer friendly
portal that allows the public

04:29:05.250 --> 04:29:08.103
to view clear and
comprehensive information

04:29:08.103 --> 04:29:10.480
on their specific vegetation
management activities

04:29:10.480 --> 04:29:13.307
that are ongoing, the
progress that has been made,

04:29:13.307 --> 04:29:15.940
and the expected completion dates.

04:29:15.940 --> 04:29:18.300
As SG and E's website just
provides a general statement

04:29:18.300 --> 04:29:21.320
that 1.1 million trees
are inspected annually

04:29:21.320 --> 04:29:24.800
and 750,000 are pruned.

04:29:24.800 --> 04:29:26.010
From the presentation today,

04:29:26.010 --> 04:29:28.820
it appears that SCE is able to provide

04:29:28.820 --> 04:29:31.020
the type of location-specific,

04:29:31.020 --> 04:29:33.290
comprehensive vegetation
management information

04:29:33.290 --> 04:29:37.483
that is called for by
decision 20 05 051.

04:29:38.350 --> 04:29:41.200
So when is that information
going to be made available

04:29:41.200 --> 04:29:42.733
on a customer-friendly portal?

04:29:48.060 --> 04:29:50.420
<v ->I don't have an
immediate information</v>

04:29:50.420 --> 04:29:52.270
on a, on date of availability.

04:29:52.270 --> 04:29:54.410
I think we're going to need to see the,

04:29:54.410 --> 04:29:57.162
our ARBORA tool that we've
been discussing implemented

04:29:57.162 --> 04:30:01.589
in order to translate data
to something that would be

04:30:01.589 --> 04:30:04.700
a comprehensive view
for the customer base.

04:30:04.700 --> 04:30:08.683
And so we would need to be
looking ahead to 2022 for that.

04:30:13.015 --> 04:30:14.110
<v Ryan>Okay, thank you.</v>

04:30:14.110 --> 04:30:15.873
That's it from the chat box, Colin.

04:30:17.700 --> 04:30:18.600
<v ->Thank you, Ryan.</v>

04:30:19.830 --> 04:30:23.080
Next, we will move to
Joseph Mitchell, Mitchell

04:30:23.080 --> 04:30:25.880
of Mussey Grade Road Alliance.

04:30:25.880 --> 04:30:27.953
<v Joe>Hi, this is Joe Mitchell,</v>

04:30:28.958 --> 04:30:33.958
I had a question on the
classifications of at-risk species.

04:30:34.460 --> 04:30:35.960
This is for all the utilities.

04:30:37.170 --> 04:30:42.170
In the past WMT's at-risk
species were determined as,

04:30:45.510 --> 04:30:50.510
as far as outage data informed
at-risk species determination

04:30:51.210 --> 04:30:53.700
just by the sheer number of outages.

04:30:53.700 --> 04:30:58.700
And as a result, the, the
top at-risk trees tended

04:30:59.770 --> 04:31:02.750
to be just the top
threes in the population

04:31:04.770 --> 04:31:09.720
rather than normalizing
as the tree frequency

04:31:09.720 --> 04:31:11.300
in the utility area.

04:31:11.300 --> 04:31:14.730
I know that we did
some analysis on some of

04:31:14.730 --> 04:31:18.242
the quarterly updates with SDG and E

04:31:18.242 --> 04:31:23.242
and saw that some of the, the weights

04:31:23.610 --> 04:31:27.030
for some of these at-risk species

04:31:27.030 --> 04:31:30.400
were greatly different from each other.

04:31:30.400 --> 04:31:33.610
Palm of course, always being really bad,

04:31:33.610 --> 04:31:37.060
but certain things not
making the top of the list,

04:31:37.060 --> 04:31:39.654
like cypress and century plants,

04:31:39.654 --> 04:31:42.354
just because there aren't
that many of them out there.

04:31:43.825 --> 04:31:46.700
The question is, as you're maturing,

04:31:46.700 --> 04:31:51.700
these risk determination
models, are you,

04:31:51.910 --> 04:31:54.730
and you're incorporating
outage information,

04:31:54.730 --> 04:31:59.100
are you normalizing that
outage information per tree

04:32:01.410 --> 04:32:04.640
per you know, per outages
per a thousand trees per year,

04:32:04.640 --> 04:32:08.600
for instance, or are
you still using just

04:32:08.600 --> 04:32:11.233
the sheer number of outages
from your service areas?

04:32:14.870 --> 04:32:16.355
<v ->This is Michael.</v>

04:32:16.355 --> 04:32:17.480
I'll go ahead and (indistinct).

04:32:18.410 --> 04:32:22.140
Hi Joe, thank you for the,
for the questions, so I'll,

04:32:22.140 --> 04:32:27.140
I'll reiterate just for context
are our top five species

04:32:27.370 --> 04:32:32.370
Sycamore, pine,
eucalyptus, palm, and oak.

04:32:33.500 --> 04:32:36.850
And Joe, Joe brings up a valid point.

04:32:36.850 --> 04:32:39.203
Well, there's the relative frequency

04:32:39.203 --> 04:32:41.470
that these trees cause outages.

04:32:41.470 --> 04:32:44.330
And then there is
the less specific trees,

04:32:44.330 --> 04:32:47.030
species propensity to cause an outage.

04:32:47.030 --> 04:32:49.790
Well, that can certainly
change year to year.

04:32:49.790 --> 04:32:51.430
I think what's important and critical

04:32:51.430 --> 04:32:55.200
for us every time that
we have an outage,

04:32:55.200 --> 04:32:58.650
we do a very detailed analysis

04:32:58.650 --> 04:33:02.270
and investigation of
not only the species,

04:33:02.270 --> 04:33:06.070
but what were the mechanics
that cause that outage,

04:33:06.070 --> 04:33:09.190
if it was a branch
breakout there, for example,

04:33:09.190 --> 04:33:12.380
included bark, was there a severe lean?

04:33:12.380 --> 04:33:14.880
There are other environmental
factors that lead us

04:33:16.122 --> 04:33:18.360
to thinking could have been
a contributing factor to that

04:33:18.360 --> 04:33:21.110
being an outage, even though

04:33:21.110 --> 04:33:25.657
we consider those five
species be our quote,

04:33:25.657 --> 04:33:28.297
"top five species,"

04:33:28.297 --> 04:33:32.680
there are, for example, some
species where we are going

04:33:32.680 --> 04:33:35.139
to nuance it a little bit further,

04:33:35.139 --> 04:33:37.100
and I'll illustrate that with thereby

04:33:37.100 --> 04:33:38.743
by bringing up pine species.

04:33:39.617 --> 04:33:43.870
So SDG and E does not
have a very large diversity

04:33:43.870 --> 04:33:46.983
or number of different pine species,

04:33:46.983 --> 04:33:48.523
but there are a couple of pine species

04:33:48.523 --> 04:33:51.687
that are especially problematic for us.

04:33:51.687 --> 04:33:56.210
They are, are non-native
on sorry, high wind speed,

04:33:56.210 --> 04:33:59.253
the Aleppo pine and
the Canary Island pine.

04:34:00.320 --> 04:34:04.350
Most of our outages that
are caused by pines are one of

04:34:04.350 --> 04:34:05.673
those two species.

04:34:06.843 --> 04:34:10.140
One, that they have propensity no year.

04:34:10.140 --> 04:34:14.510
We ironically do not find a
lot of outages, for example,

04:34:14.510 --> 04:34:16.759
in our higher elevations,

04:34:16.759 --> 04:34:19.380
where pine species are usually found.

04:34:19.380 --> 04:34:24.100
So one way that we are
getting even more detailed

04:34:24.100 --> 04:34:26.680
in the application of our target species

04:34:26.680 --> 04:34:29.960
and where we in turn get
our greatest clearances is

04:34:29.960 --> 04:34:32.220
to focus those greater clearances

04:34:32.220 --> 04:34:35.400
on those specific three species.

04:34:35.400 --> 04:34:39.900
That is the Aleppo pine
and the Canary Island pine.

04:34:39.900 --> 04:34:43.820
Similarly for, oak, we
like most in California have

04:34:43.820 --> 04:34:47.040
a lot of oak species, nowhere near what

04:34:47.040 --> 04:34:48.713
our counterparts have up North.

04:34:49.602 --> 04:34:51.790
There are a couple of
species that are, for example,

04:34:51.790 --> 04:34:55.980
are subject to pest invasion.

04:34:55.980 --> 04:34:59.830
We have pretty random in
case of blow-potted oak wart

04:34:59.830 --> 04:35:02.190
in Southern California
that have decimated

04:35:02.190 --> 04:35:04.040
a lot of our location.

04:35:04.040 --> 04:35:06.120
So we are targeting those trees,

04:35:06.120 --> 04:35:09.170
obviously that are
showing signs of mortality

04:35:09.170 --> 04:35:10.680
or structural impact.

04:35:10.680 --> 04:35:15.680
It will likely be one of those
trees that cause our outages.

04:35:15.791 --> 04:35:19.110
So all that to say is that
we are not trying to target all

04:35:19.110 --> 04:35:22.620
of those tough five species
for complete removal,

04:35:22.620 --> 04:35:25.760
or are we looking to
target all of those species

04:35:25.760 --> 04:35:28.149
with those enhanced clearances?

04:35:28.149 --> 04:35:31.075
You're looking at every
tree, not just the species,

04:35:31.075 --> 04:35:32.414
looking at all of its site-specific
environmental factors,

04:35:32.414 --> 04:35:36.348
determine where we
need to remove a tree,

04:35:36.348 --> 04:35:40.373
or get greater clearance.

04:35:48.444 --> 04:35:49.277
<v Joe>Yeah, yeah.</v>

04:35:49.277 --> 04:35:50.160
Thanks, Mike.

04:35:50.160 --> 04:35:55.160
I was just wondering, just
back to the specific question,

04:35:55.800 --> 04:36:00.800
you are looking at the
frequency that as well,

04:36:01.320 --> 04:36:02.153
is that correct?

04:36:04.570 --> 04:36:07.150
<v ->Yeah, mind if I
jumped in on this one?</v>

04:36:07.150 --> 04:36:09.070
Yeah, we, we did.

04:36:09.070 --> 04:36:10.770
We do look at the frequency.

04:36:10.770 --> 04:36:14.363
We look at, we look at both, but again,

04:36:16.420 --> 04:36:19.630
the goal that we're trying to
do here is reduce risk events.

04:36:19.630 --> 04:36:23.070
So not only is the frequency important,

04:36:23.070 --> 04:36:24.860
like if there isn't a
volume of those trees,

04:36:24.860 --> 04:36:28.390
like you mentioned
cypress and century plants,

04:36:28.390 --> 04:36:31.497
and I know Mike can speak to that.

04:36:31.497 --> 04:36:32.330
We do have an actual plan,

04:36:32.330 --> 04:36:33.810
additional inspections
that are done for cypress

04:36:33.810 --> 04:36:37.580
and century, given that they
are a high risk for our system,

04:36:37.580 --> 04:36:40.140
but there's just not enough
volume of them to make them one

04:36:40.140 --> 04:36:42.600
of the targeted species
because they only contribute to,

04:36:42.600 --> 04:36:46.503
I think maybe like less than
half a risk event per year.

04:36:47.480 --> 04:36:51.571
So, you know, to
your point, you're right.

04:36:51.571 --> 04:36:53.693
Some of these species
that we targeted high risk,

04:36:54.659 --> 04:36:57.580
it's both from the frequency
standpoint like palm,

04:36:57.580 --> 04:37:00.300
but also from a volume standpoint,

04:37:00.300 --> 04:37:05.300
because ultimately we are
trying to reduce risk events

04:37:05.480 --> 04:37:07.010
to reduce ignitions.

04:37:07.010 --> 04:37:10.220
And so we need to target that the trees

04:37:10.220 --> 04:37:12.320
and there's five species that make up

04:37:12.320 --> 04:37:14.290
the most risk events on our system.

04:37:14.290 --> 04:37:16.010
To actually do something that's going

04:37:16.010 --> 04:37:18.010
to reduce risk events on the system,

04:37:18.010 --> 04:37:21.040
we have to target, target those species.

04:37:21.040 --> 04:37:24.130
But no, you're, you're
right in the analysis you did

04:37:24.130 --> 04:37:28.270
from a pure (indistinct) opportunity.

04:37:28.270 --> 04:37:31.373
You know, there, there are
some distinctions between,

04:37:33.220 --> 04:37:36.730
you know, actual what
we would normally call risk

04:37:36.730 --> 04:37:39.840
in an effort to, to actually
bring down risk events

04:37:39.840 --> 04:37:40.710
on the system.

04:37:40.710 --> 04:37:41.773
Does that make sense?

04:37:44.180 --> 04:37:49.180
<v Joe>Yes, that's
open to other utilities</v>

04:37:49.710 --> 04:37:50.610
to answer as well.

04:37:52.690 --> 04:37:55.173
<v ->Sure, I can speak
on behalf of SCE here.</v>

04:37:56.200 --> 04:37:59.070
I want to draw a distinction
between what we consider to be

04:37:59.070 --> 04:38:01.660
at risk and what we consider to be

04:38:01.660 --> 04:38:05.790
a major contributor to outages
because you're right on point

04:38:05.790 --> 04:38:07.660
that they are there either is

04:38:07.660 --> 04:38:11.890
a factor of simple volume
of population in this case.

04:38:11.890 --> 04:38:15.700
So for us, we have
identified our outage drivers

04:38:15.700 --> 04:38:19.740
to the pine, oak, eucalyptus and palm.

04:38:19.740 --> 04:38:22.300
So it's a bunch of
runners up for fifth place.

04:38:22.300 --> 04:38:24.600
So we'll keep it at the top four.

04:38:24.600 --> 04:38:28.680
And really, in fact, I've
asked numerous times

04:38:28.680 --> 04:38:31.540
our arborist team about
oaks and pines in particular.

04:38:31.540 --> 04:38:33.640
And are we missing something here?

04:38:33.640 --> 04:38:36.700
Why are they, why
are they driving outages

04:38:36.700 --> 04:38:38.083
in the way they are,

04:38:39.035 --> 04:38:40.120
do we need to be
treating them differently?

04:38:40.120 --> 04:38:42.400
And we continue to
investigate that a question, right?

04:38:42.400 --> 04:38:44.753
It certainly suggests if we
have outages from them,

04:38:44.753 --> 04:38:46.970
there's something
to be doing differently,

04:38:46.970 --> 04:38:48.900
gaining more clearance for example,

04:38:48.900 --> 04:38:52.140
but we don't inherently consider
them to be at-risk species.

04:38:52.140 --> 04:38:55.647
We have a top 10 of
at-risk species and on it,

04:38:55.647 --> 04:38:57.440
are palm and eucalyptus.

04:38:57.440 --> 04:39:01.557
So you can see the alignment
between the outages and the,

04:39:02.420 --> 04:39:04.430
and the at-risk in that component.

04:39:04.430 --> 04:39:07.390
But as I mentioned, oak
and pine are not on that list.

04:39:07.390 --> 04:39:11.460
And so when it comes to
marrying up the difference,

04:39:11.460 --> 04:39:14.540
but the, the, the volume of the outages

04:39:14.540 --> 04:39:17.530
and your ability to impact
that versus you're at-risk,

04:39:17.530 --> 04:39:20.150
it does require different
treatment and analysis

04:39:20.150 --> 04:39:23.823
to understand how to adjust
your program appropriately.

04:39:29.260 --> 04:39:31.110
<v ->And I'll, I'll just
add for PG and E.</v>

04:39:31.110 --> 04:39:36.110
So the simple answer is
yes, we do normalize for,

04:39:37.470 --> 04:39:39.920
for the, the size of the population.

04:39:39.920 --> 04:39:42.220
We've actually, we
we've also looked at it

04:39:42.220 --> 04:39:43.470
by geographical area.

04:39:43.470 --> 04:39:45.390
So like, you've heard
some of the other utilities

04:39:45.390 --> 04:39:49.200
have like their top
10 species, or top five,

04:39:49.200 --> 04:39:50.860
we've actually done the same thing,

04:39:50.860 --> 04:39:52.860
but we've broken up
into smaller regions, right?

04:39:52.860 --> 04:39:55.800
So our, our coastal
area has a different list

04:39:55.800 --> 04:40:00.397
of tops high-risk species
than our, in the Sierras do.

04:40:00.397 --> 04:40:01.540
And so we've broken up

04:40:01.540 --> 04:40:03.750
into our six regional
areas that we have.

04:40:03.750 --> 04:40:07.510
So basically it's the North coast, the,

04:40:07.510 --> 04:40:11.740
what we call the central
coast, the Bay area,

04:40:11.740 --> 04:40:13.117
the central valley, the Sierras,

04:40:13.117 --> 04:40:17.270
and then the Northern
Sierras, Sierra North Valley,

04:40:17.270 --> 04:40:19.020
is what we call it.

04:40:19.020 --> 04:40:20.570
Each has their own targeted or,

04:40:20.570 --> 04:40:23.980
or lists based on the
outage data for their area,

04:40:23.980 --> 04:40:27.530
as well as the species
population in that area.

04:40:27.530 --> 04:40:30.423
We also actually have even
normalized for time of year.

04:40:31.830 --> 04:40:33.810
We see different kinds of outages

04:40:33.810 --> 04:40:35.890
being caused during winter,

04:40:35.890 --> 04:40:39.080
which are less than a
factor for wildfire prevention.

04:40:39.080 --> 04:40:42.430
So snow loading will cost
certain trees to fail, fail.

04:40:42.430 --> 04:40:45.143
So like a Ponderosa pine, for example,

04:40:46.050 --> 04:40:47.750
is subject to snow loading failures

04:40:47.750 --> 04:40:48.720
during the winter months.

04:40:48.720 --> 04:40:50.040
But during the summer months,

04:40:50.040 --> 04:40:54.450
typically doesn't have
a lot of failures cause.

04:40:54.450 --> 04:40:57.563
We've also been looking into
breaking up and having these,

04:40:57.563 --> 04:41:01.660
these top 10 species for
different types of causes

04:41:01.660 --> 04:41:02.493
for outage, right?

04:41:02.493 --> 04:41:05.990
So a, a redwood tree for example,

04:41:05.990 --> 04:41:10.440
will shed branches
where other species won't.

04:41:10.440 --> 04:41:13.130
So those are higher risk for an overhang

04:41:13.130 --> 04:41:14.310
than for a fall enrich.

04:41:14.310 --> 04:41:18.780
So we've been looking at the
data from that perspective too,

04:41:18.780 --> 04:41:23.750
but I do want to go back to
what SDG and E said, which is,

04:41:23.750 --> 04:41:26.530
you know, part of this for
us is, is driving down risk.

04:41:26.530 --> 04:41:28.930
And so, although we
do see that the outages

04:41:28.930 --> 04:41:31.363
are caused can be normalized.

04:41:32.490 --> 04:41:34.070
There still is that risk there.

04:41:34.070 --> 04:41:36.480
And so I might have a circuit

04:41:36.480 --> 04:41:39.440
that has 1,000 Ponderosa pines

04:41:39.440 --> 04:41:40.720
that have striped potential on it.

04:41:40.720 --> 04:41:43.360
And while there's a
likelihood of only ignition,

04:41:43.360 --> 04:41:45.970
say once every a thousand trees, well,

04:41:45.970 --> 04:41:48.230
I can still have a chance
for ignition on there.

04:41:48.230 --> 04:41:52.910
So the risk impact plays a role there

04:41:52.910 --> 04:41:56.980
and how that mostly materializes
for us is basically in our,

04:41:56.980 --> 04:41:59.200
in that tree assessment
tool that I mentioned earlier,

04:41:59.200 --> 04:42:01.520
we put that at waiting in there

04:42:01.520 --> 04:42:03.250
to help inform the decisions.

04:42:03.250 --> 04:42:05.727
We're looking at some other
ways of potentially doing,

04:42:05.727 --> 04:42:08.760
of expanding that in the
future to maybe accelerate

04:42:08.760 --> 04:42:10.617
or do more targeted approaches.

04:42:10.617 --> 04:42:11.800
But for right now,

04:42:11.800 --> 04:42:14.560
those are still kind of
in the concept phase.

04:42:14.560 --> 04:42:18.287
But I agree, we do look at
the species population and,

04:42:18.287 --> 04:42:19.760
and a bunch of other factors,

04:42:19.760 --> 04:42:22.130
and we don't limit it to
just one type of failure.

04:42:22.130 --> 04:42:23.620
We live when we are looking at it

04:42:23.620 --> 04:42:25.730
from different type types of failures.

04:42:25.730 --> 04:42:29.290
So fall in overhang and then grow in

04:42:29.290 --> 04:42:30.590
is another factor as well.

04:42:31.940 --> 04:42:32.840
<v Joe>Thank you.</v>

04:42:37.150 --> 04:42:37.983
<v ->Thank you all.</v>

04:42:37.983 --> 04:42:40.240
Thank you, Joseph, for your question,

04:42:40.240 --> 04:42:43.307
Henry Burton from the
Public Advocate's Office.

04:42:47.720 --> 04:42:49.460
<v ->Okay, thanks.</v>

04:42:49.460 --> 04:42:52.850
My question is about how
the utilities are targeting

04:42:52.850 --> 04:42:55.310
their enhanced vegetation
management programs

04:42:55.310 --> 04:42:58.350
to address the highest
risk circuit segments

04:42:58.350 --> 04:43:00.570
in their HTD areas.

04:43:00.570 --> 04:43:05.570
So your risk models are telling
us that a very small number

04:43:06.530 --> 04:43:10.173
of circuit segments and
circuit miles are resulting

04:43:11.810 --> 04:43:16.700
in a disproportionate
amount of the total wildfire risk.

04:43:16.700 --> 04:43:17.630
Just as an example,

04:43:17.630 --> 04:43:20.320
I think I haven't looked
at all the utilities yet,

04:43:20.320 --> 04:43:21.593
but just as an example,

04:43:22.500 --> 04:43:25.030
six of Edison's
distribution circuits account

04:43:25.030 --> 04:43:27.960
for 25% of the total wildfire risk

04:43:27.960 --> 04:43:31.500
on the distribution
system, and 24 circuits

04:43:31.500 --> 04:43:33.340
out of thousands address account

04:43:33.340 --> 04:43:36.523
for half of the total wildfire risk.

04:43:37.780 --> 04:43:40.110
So my question is how you're targeting

04:43:40.110 --> 04:43:41.640
your enhanced vegetation management

04:43:41.640 --> 04:43:42.950
to the high risk circuit segments.

04:43:42.950 --> 04:43:45.897
I know PGD had said that they're setting

04:43:45.897 --> 04:43:50.897
a goal of doing 80% of that
work in 20% of the circuits

04:43:52.770 --> 04:43:53.760
or circuit segments.

04:43:53.760 --> 04:43:57.900
But since you're only doing EVM on

04:43:57.900 --> 04:44:01.160
about 7% of your HTD miles per year,

04:44:01.160 --> 04:44:04.013
can you explain why
that's an appropriate target?

04:44:10.620 --> 04:44:15.350
<v ->So, to explain where the 80%,</v>

04:44:15.350 --> 04:44:18.420
so there are other
operational challenges

04:44:18.420 --> 04:44:19.960
that we need to contend with.

04:44:19.960 --> 04:44:23.010
I think we'd all like it
to be as close to 100%

04:44:23.010 --> 04:44:27.380
as possible, but there's
other operational challenges.

04:44:27.380 --> 04:44:30.633
Permitting is certainly
one, you know, customers,

04:44:30.633 --> 04:44:32.880
some other environmental factors,

04:44:32.880 --> 04:44:35.830
all of those weigh in some
of these also existing projects

04:44:35.830 --> 04:44:38.730
that we're carrying
over from, from last year.

04:44:38.730 --> 04:44:43.300
PG and E's risk model
has changed three times,

04:44:43.300 --> 04:44:45.667
one each year as we
continue to learn more.

04:44:45.667 --> 04:44:48.000
And so we update the
model and circuits that were

04:44:48.000 --> 04:44:50.279
in the higher risk categories year,

04:44:50.279 --> 04:44:51.373
it may not be this year.

04:44:52.320 --> 04:44:56.610
The other piece is, is that
the next step in our planning

04:44:56.610 --> 04:45:00.810
is that we also take
into consideration work

04:45:00.810 --> 04:45:01.920
that's already been completed.

04:45:01.920 --> 04:45:06.330
So a circuit that is
high-risk, if we've addressed,

04:45:06.330 --> 04:45:08.830
you know, the majority of the circuit,

04:45:08.830 --> 04:45:13.430
the remaining risk may no
longer keep it in that top 20%.

04:45:13.430 --> 04:45:16.555
So we might move to another area

04:45:16.555 --> 04:45:20.283
where we can get the
most, most impact if you will.

04:45:21.320 --> 04:45:25.100
So that's how we we've
targeted, you know,

04:45:25.100 --> 04:45:30.100
80% is going to be, I
think, a challenge for us.

04:45:30.100 --> 04:45:32.150
To be honest, it was kind of a,

04:45:32.150 --> 04:45:35.653
a balancing act between
wanting to do everything there.

04:45:36.820 --> 04:45:38.146
And then what's also feasible.

04:45:38.146 --> 04:45:39.600
And, and I'll just remind

04:45:39.600 --> 04:45:42.200
that all of this circuits
that we're working,

04:45:42.200 --> 04:45:46.180
100% of the circuits
are all in HFTD's, right?

04:45:46.180 --> 04:45:47.410
So they're in the high fire threat.

04:45:47.410 --> 04:45:50.540
So the reality is, is
that there's that potential

04:45:50.540 --> 04:45:52.600
to have an ignition anywhere.

04:45:52.600 --> 04:45:57.450
And so we're trying to go
for the places where it's the,

04:45:57.450 --> 04:45:59.590
the impact of the
ignition will be greatest.

04:45:59.590 --> 04:46:00.920
And that's where we
see the highest risk,

04:46:00.920 --> 04:46:02.290
so we're trying to work there first,

04:46:02.290 --> 04:46:05.527
but it is possible to
having anywhere in,

04:46:05.527 --> 04:46:09.370
and we're only working in a
high fire threat district area.

04:46:09.370 --> 04:46:13.703
So even that other 20% is
in that, that high-risk area.

04:46:16.650 --> 04:46:19.950
<v ->I would just echo and thank
you, Henry, for that question.</v>

04:46:19.950 --> 04:46:23.500
So, as we mentioned in
our presentation or over half,

04:46:23.500 --> 04:46:27.603
of our overhead sort of miles
off exists within the HF TV.

04:46:28.545 --> 04:46:30.770
So certainly from a
privatization standpoint,

04:46:30.770 --> 04:46:35.770
we why some of the tools
that risk models form us,

04:46:35.860 --> 04:46:37.280
where we may prioritize

04:46:37.280 --> 04:46:39.520
our enhancement
agitation management work.

04:46:39.520 --> 04:46:41.150
For example, looking at our,

04:46:41.150 --> 04:46:46.150
our segments in our SMRVRI
modeling, make that decision.

04:46:47.640 --> 04:46:50.800
I think it's, it's
important to kind of state

04:46:50.800 --> 04:46:55.520
the premise that, that any
part of our service territory

04:46:55.520 --> 04:47:00.063
that exists within VHF
TV, all it takes is one tree,

04:47:00.063 --> 04:47:04.590
either shut a branch
or onto the power lines

04:47:04.590 --> 04:47:06.466
to cause any condition.

04:47:06.466 --> 04:47:09.150
So, so no, we have to be judicious

04:47:09.150 --> 04:47:12.320
in the application of our
enhancement station management,

04:47:12.320 --> 04:47:14.690
we have to be extremely prudent.

04:47:14.690 --> 04:47:17.350
And one, one could
argue that we have to err,

04:47:17.350 --> 04:47:22.090
on the side of caution
where we are engaging lies

04:47:22.090 --> 04:47:24.693
in our UVM are on
those targeted species.

04:47:24.693 --> 04:47:28.623
We are not ready to
arbitrary clearances,

04:47:29.701 --> 04:47:33.233
in clearances based on
what the specific tree tells us.

04:47:34.390 --> 04:47:35.910
What is the structure of the tree?

04:47:35.910 --> 04:47:39.120
Where is it located
adjacent to the power lines?

04:47:39.120 --> 04:47:41.108
Is it (indistinct)

04:47:41.108 --> 04:47:42.190
what is the PRI?

04:47:42.190 --> 04:47:44.760
Really from a prioritization standpoint,

04:47:44.760 --> 04:47:47.440
we use some of the risk models, but we,

04:47:47.440 --> 04:47:49.803
we have to be extremely
diligent and make sure

04:47:49.803 --> 04:47:52.030
that we are addressing it no matter

04:47:52.030 --> 04:47:56.600
where the fire potential lies.

04:47:56.600 --> 04:47:59.590
We, for example, we could have a tree

04:47:59.590 --> 04:48:04.590
that fails outside of BHFTD
and under the right conditions

04:48:04.910 --> 04:48:09.910
fairly quickly be with
an HMT to corroboration.

04:48:10.340 --> 04:48:15.340
So we we're, we're going to
stand by our, our operations.

04:48:15.810 --> 04:48:20.810
So being extremely prudent,

04:48:21.160 --> 04:48:24.250
but also extremely thorough in

04:48:24.250 --> 04:48:27.520
where we are applying
these greater clearances.

04:48:27.520 --> 04:48:31.316
Three, let the data
for us going to do it.

04:48:31.316 --> 04:48:34.750
We would argue that
mitigation efforts are taking

04:48:34.750 --> 04:48:37.590
and our data is
showing that as resulting

04:48:37.590 --> 04:48:40.550
in reduction of outages and thus...

04:48:51.060 --> 04:48:53.170
<v ->Yeah, in terms of SCE,</v>

04:48:53.170 --> 04:48:55.440
I think a lot of good
points there that I,

04:48:55.440 --> 04:48:58.228
I don't need to say repeat.

04:48:58.228 --> 04:49:02.750
A couple points I would make,
have to do with, you know,

04:49:02.750 --> 04:49:05.390
specifically your
question and the reference

04:49:05.390 --> 04:49:07.260
to certain distribution circuits,

04:49:07.260 --> 04:49:10.010
being the majority driver of risk.

04:49:10.010 --> 04:49:14.310
And you see that come in in
terms of risk-informed planning

04:49:14.310 --> 04:49:16.550
with regard to the Hazard Tree Program,

04:49:16.550 --> 04:49:21.070
which really seeks to work
down and evaluate the tree

04:49:21.070 --> 04:49:24.220
as along those circuits
in just that fashion, right?

04:49:24.220 --> 04:49:25.680
There, there is a component

04:49:25.680 --> 04:49:29.700
for operationalizing the work, right,

04:49:29.700 --> 04:49:32.370
and the need to not
be hither and thither all

04:49:32.370 --> 04:49:34.320
over the territory with a segment of

04:49:34.320 --> 04:49:36.240
a line here and a segment of line there,

04:49:36.240 --> 04:49:39.230
because then you quickly
spiral you toss out of control

04:49:39.230 --> 04:49:41.730
and really find it difficult

04:49:41.730 --> 04:49:44.080
to maintain momentum in the work.

04:49:44.080 --> 04:49:47.330
But by and large, the
approach is to work down

04:49:47.330 --> 04:49:50.300
in terms of risk severity.

04:49:50.300 --> 04:49:55.300
And then the other nuance
there relates to things like our,

04:49:55.580 --> 04:49:56.420
our line clearing,

04:49:56.420 --> 04:49:58.980
where we're doing
enhanced clearances, right?

04:49:58.980 --> 04:50:01.220
Which is that, that 12-foot clearance

04:50:01.220 --> 04:50:04.050
at time of trim that has
been discussed extensively

04:50:04.050 --> 04:50:06.263
over the past a year plus.

04:50:07.364 --> 04:50:10.820
And really we do that in all locations

04:50:10.820 --> 04:50:13.210
in the high fire risk areas.

04:50:13.210 --> 04:50:15.620
And that's because
it, it not only reduces

04:50:15.620 --> 04:50:20.090
the wildfire potential,
but it also, you know,

04:50:20.090 --> 04:50:23.810
is supportive of the
compliance obligation to not have

04:50:23.810 --> 04:50:27.460
the tree encroach on the
minimum clearance distance.

04:50:27.460 --> 04:50:32.220
And so there there's a
component of risk-informed points

04:50:32.220 --> 04:50:35.450
there that I don't, again,
I'm not trying to repeat

04:50:35.450 --> 04:50:38.380
or belabor points, but
there may be variations

04:50:38.380 --> 04:50:41.520
in trees in terms of their growth cycle

04:50:41.520 --> 04:50:45.150
and our ability to obtain
a, a lesser distance

04:50:45.150 --> 04:50:46.450
in some cases.

04:50:46.450 --> 04:50:48.650
But we anchor on a standard in order

04:50:48.650 --> 04:50:51.660
to provide consistency in the direction

04:50:51.660 --> 04:50:54.570
to our workforce so that
they know what's expected.

04:50:54.570 --> 04:50:58.170
And because we're going to
those locations every single year

04:50:58.170 --> 04:51:01.350
and evaluating the
condition of individual trees,

04:51:01.350 --> 04:51:06.350
the risk associated with
that particular circuit today

04:51:06.350 --> 04:51:08.670
in the world, as we have,
it is less consequential.

04:51:08.670 --> 04:51:10.770
Now, as we mature our risk modeling,

04:51:10.770 --> 04:51:15.770
we may move to a place
where that is more informed

04:51:15.920 --> 04:51:18.660
and that's something
we're trying to get to,

04:51:18.660 --> 04:51:21.580
but right now we're not quite there.

04:51:21.580 --> 04:51:23.750
And so that point is not as relevant

04:51:23.750 --> 04:51:25.150
for that particular program.

04:51:28.320 --> 04:51:30.250
<v ->I'd also like to just echo
something Melanie said</v>

04:51:30.250 --> 04:51:32.282
is so PG and E as well,

04:51:32.282 --> 04:51:34.160
our high fire threat districts

04:51:34.160 --> 04:51:37.790
get patrolled twice a year, every year.

04:51:37.790 --> 04:51:41.580
So we are still making
sure that we're working

04:51:41.580 --> 04:51:44.062
on our tuning, our radio clearance,

04:51:44.062 --> 04:51:45.410
removing dead and
dying trees and other trees

04:51:45.410 --> 04:51:49.120
that we think are
defective and need to go.

04:51:49.120 --> 04:51:52.280
The, when the enhanced EBM program,

04:51:52.280 --> 04:51:54.570
Enhanced Vegetation
Management Program gets there,

04:51:54.570 --> 04:51:57.240
that program is going above
and beyond the requirements

04:51:57.240 --> 04:51:59.810
and attempting to get
a greater clearance,

04:51:59.810 --> 04:52:03.530
establish a bigger right
away inventory, all the trees.

04:52:03.530 --> 04:52:05.300
And so, you know, we are,

04:52:05.300 --> 04:52:07.370
it's not that the rest of the system

04:52:07.370 --> 04:52:09.170
isn't getting attention from us.

04:52:09.170 --> 04:52:13.050
It's just, it's just not getting
that enhanced program yet,

04:52:13.050 --> 04:52:14.470
because to your point,

04:52:14.470 --> 04:52:17.770
we're only able to do so
many of those models annually,

04:52:17.770 --> 04:52:20.640
but we do still patrol
those other, the rest of the,

04:52:20.640 --> 04:52:23.413
the system twice a year, every year.

04:52:37.400 --> 04:52:38.703
<v Henry>Great, thank you.</v>

04:52:43.086 --> 04:52:43.919
<v ->Go ahead, Henry.</v>

04:52:43.919 --> 04:52:44.752
I have other questions,

04:52:44.752 --> 04:52:46.770
but it looks like we're at
time and I'm sure other people

04:52:46.770 --> 04:52:48.220
have other questions as well.

04:52:50.280 --> 04:52:52.890
<v ->We are, we are a
time and I would like</v>

04:52:52.890 --> 04:52:55.930
to elevate one more person
before we are for the day

04:52:55.930 --> 04:52:57.173
if that is all right?

04:53:00.380 --> 04:53:03.000
Megan, from the Joint
Local Governments Coalition.

04:53:03.000 --> 04:53:04.800
I see your question in the chat.

04:53:04.800 --> 04:53:06.820
And if you would like to unmute yourself

04:53:06.820 --> 04:53:08.920
and ask your question,
you are welcome to.

04:53:10.670 --> 04:53:12.170
<v Megan>Yes, thank you.</v>

04:53:12.170 --> 04:53:13.710
This is Megan Smoggy for

04:53:13.710 --> 04:53:16.330
the Joint Local Government Coalition.

04:53:16.330 --> 04:53:19.100
And this question is
primarily for PG and E,

04:53:19.100 --> 04:53:24.100
although there, there's
some things that SCE

04:53:24.550 --> 04:53:27.370
and SDG and E could speak to as well.

04:53:27.370 --> 04:53:31.653
I want to follow up about
the fire retardant again.

04:53:33.000 --> 04:53:37.200
Now your Wildfire Mitigation Plan speaks

04:53:37.200 --> 04:53:40.140
to getting pesticide use permits

04:53:40.140 --> 04:53:44.100
and undertaking SEPA and NEPA review

04:53:44.100 --> 04:53:48.320
on state and federal
lands for your rights of way,

04:53:48.320 --> 04:53:51.410
where you're looking
to potentially deploy

04:53:51.410 --> 04:53:55.922
this fire retardant, but for
work on private property,

04:53:55.922 --> 04:54:00.922
you only mentioned a
land's right assessment.

04:54:01.260 --> 04:54:05.410
And so in light of the fact
that in your service territory,

04:54:05.410 --> 04:54:09.630
you have significant
private agricultural property

04:54:10.640 --> 04:54:13.510
that your equipment runs through,

04:54:13.510 --> 04:54:18.510
you have coastal property
in the high fire threat area,

04:54:19.060 --> 04:54:22.410
and you have a large
number of customers who rely

04:54:22.410 --> 04:54:26.092
on the groundwater
table for their well water,

04:54:26.092 --> 04:54:29.520
I'd like to know what PG and E's plan is

04:54:29.520 --> 04:54:32.150
at a programmatic level

04:54:32.150 --> 04:54:34.990
for comprehensive environmental review

04:54:34.990 --> 04:54:37.743
and permitting for this fire retardants.

04:54:39.730 --> 04:54:40.980
<v ->No, thank you,
it's a great question.</v>

04:54:40.980 --> 04:54:43.710
And I just want to clarify, I, I,

04:54:43.710 --> 04:54:46.987
you said pesticide, it
should be herbicide.

04:54:46.987 --> 04:54:49.140
Hopefully, it says that in
the Wildfire Mitigation Plan,

04:54:49.140 --> 04:54:52.150
it should say herbicide, not pesticide,

04:54:52.150 --> 04:54:56.620
but so what you mentioned there is

04:54:56.620 --> 04:54:59.380
why we haven't started yet.

04:54:59.380 --> 04:55:03.130
We are currently going
through an environmental review.

04:55:03.130 --> 04:55:07.873
We've been working with
several suppliers of the,

04:55:09.000 --> 04:55:13.257
the flame-retardant to understand

04:55:13.257 --> 04:55:15.463
what its environmental impacts are.

04:55:16.450 --> 04:55:19.463
And we still going
through that practice.

04:55:20.300 --> 04:55:23.581
Certainly one of the thing
that initially came out is,

04:55:23.581 --> 04:55:28.581
you know, that some of
these fire retardants, if not all,

04:55:29.020 --> 04:55:33.980
do have a very negative
impact on, on the, on the,

04:55:33.980 --> 04:55:35.330
the water streams.

04:55:35.330 --> 04:55:38.410
And so that's certainly
something that we've already made

04:55:38.410 --> 04:55:41.815
note of, but that environmental
review is still undergoing,

04:55:41.815 --> 04:55:44.960
and we certainly don't
want to do anything

04:55:44.960 --> 04:55:48.240
that's going to damage the
environment, make things worse.

04:55:48.240 --> 04:55:50.931
I personally live off
of a well water system,

04:55:50.931 --> 04:55:53.450
so I definitely can
relate to that as well

04:55:56.064 --> 04:55:57.040
As for what the plan is,

04:55:57.040 --> 04:55:59.400
we're still waiting the
results of that review

04:55:59.400 --> 04:56:02.333
and understanding
what the impacts will be.

04:56:03.510 --> 04:56:08.190
We're looking at six that are
used already in the process

04:56:08.190 --> 04:56:10.570
of, of fire prevention.

04:56:10.570 --> 04:56:13.180
So a lot of the samples,

04:56:13.180 --> 04:56:15.390
or at least one of them is
actually the same product that

04:56:15.390 --> 04:56:19.410
CAL FIRE uses in their
fire pretension activities.

04:56:19.410 --> 04:56:20.793
But I don't have the
details of the answer

04:56:20.793 --> 04:56:23.650
to answer your question,

04:56:23.650 --> 04:56:25.320
because we're still
trying to understand that,

04:56:25.320 --> 04:56:28.280
and we're not gonna
apply this these products

04:56:28.280 --> 04:56:32.530
until we have that understood and make,

04:56:32.530 --> 04:56:34.770
make sure that it's
not causing more harm

04:56:34.770 --> 04:56:35.820
than it's preventing.

04:56:37.370 --> 04:56:38.884
<v Megan>Thank you.</v>

04:56:38.884 --> 04:56:41.937
And just very brief up, once you do have

04:56:41.937 --> 04:56:45.030
the environmental work done and have

04:56:45.030 --> 04:56:46.530
a better understanding
of what this might do

04:56:46.530 --> 04:56:49.890
to the environment, do
you plan to make that work?

04:56:51.570 --> 04:56:55.490
Are those studies publicly
available to the stakeholders

04:56:55.490 --> 04:57:00.410
at the Commission and also
directly to the impacted cities,

04:57:00.410 --> 04:57:02.333
counties, and state agencies?

04:57:06.130 --> 04:57:08.830
<v ->Barring some unknown
legal requirements</v>

04:57:08.830 --> 04:57:10.450
that I'm not aware of, I would say yes.

04:57:10.450 --> 04:57:12.280
I mean, we, we make,

04:57:12.280 --> 04:57:14.300
I think all of that
information available,

04:57:14.300 --> 04:57:16.310
but barring some legal requirement

04:57:16.310 --> 04:57:18.480
that I'm not personally
aware of right now,

04:57:18.480 --> 04:57:20.724
I would say the answer
to that is, yes, I'm sure.

04:57:20.724 --> 04:57:24.120
I know we've already
talked about internally

04:57:24.120 --> 04:57:28.100
what the outreach would
look like in terms of talking

04:57:28.100 --> 04:57:30.875
with communities and
allowing communities

04:57:30.875 --> 04:57:33.280
to weigh in on this.

04:57:33.280 --> 04:57:35.380
But before we go to that step,

04:57:35.380 --> 04:57:36.973
we wanted to have the results.

04:57:38.520 --> 04:57:41.180
You know, I mean, if I'd like to think

04:57:41.180 --> 04:57:43.110
that if we find that
this stuff is damaging

04:57:43.110 --> 04:57:45.340
to the environment, we're
just not going to use it.

04:57:45.340 --> 04:57:50.340
So I don't, I know work
with the local communities

04:57:50.670 --> 04:57:51.700
and I'm sure it will make

04:57:51.700 --> 04:57:54.090
all of our information
available to them.

04:57:54.090 --> 04:57:55.250
As we progress through this.

04:57:55.250 --> 04:57:58.640
We want people to feel
confident that this is a good choice

04:57:58.640 --> 04:58:02.040
that we're making and
that it actually helps

04:58:02.040 --> 04:58:04.480
to prevent wildfires while also helping

04:58:04.480 --> 04:58:08.533
to keep this state as
beautiful and healthy as it is.

04:58:12.759 --> 04:58:13.592
<v ->I wonder if I could,</v>

04:58:13.592 --> 04:58:17.070
I'll just speak to SDG and E's staffers

04:58:17.070 --> 04:58:18.440
regards to (indistinct) and reviews.

04:58:18.440 --> 04:58:20.680
So as mentioned earlier, our,

04:58:20.680 --> 04:58:24.820
our pilot project with
the use of our turn area

04:58:24.820 --> 04:58:27.108
was about 25 acres.

04:58:27.108 --> 04:58:30.750
It goes through every year
from our safety department,

04:58:30.750 --> 04:58:33.400
as well as our environmental
(indistinct) department.

04:58:34.980 --> 04:58:38.977
Anytime we do any activities,
especially new activities,

04:58:38.977 --> 04:58:41.320
our General Informal
Services Department,

04:58:41.320 --> 04:58:43.240
reviews that to make sure that those

04:58:43.240 --> 04:58:46.773
within guidelines of our
natural communities, culture,

04:58:47.760 --> 04:58:51.230
which is essentially
landscape level habitat

04:58:51.230 --> 04:58:53.810
conservation plan that SDG and E has

04:58:53.810 --> 04:58:56.700
with the wildlife agency.

04:58:56.700 --> 04:59:01.620
This particular pilot, we
did limit the scope areas

04:59:01.620 --> 04:59:04.600
where we did not see
environmental damage

04:59:04.600 --> 04:59:06.163
or negative negative impact,

04:59:07.455 --> 04:59:09.350
but it did go through
that environment review

04:59:09.350 --> 04:59:13.860
in advance of this
action of that product,

04:59:13.860 --> 04:59:16.447
and that that can be made available.

04:59:26.490 --> 04:59:28.780
<v ->Thank you for your
question, Megan.</v>

04:59:28.780 --> 04:59:32.620
It seems that Melanie from
SCE has having computer issues.

04:59:32.620 --> 04:59:33.990
And so I think with that,

04:59:33.990 --> 04:59:37.350
we will conclude for the
day as we are at time.

04:59:37.350 --> 04:59:40.620
Thank you to all our
accounts for answering

04:59:40.620 --> 04:59:42.270
various questions from our stakeholders

04:59:42.270 --> 04:59:45.790
and from the public, and some final,

04:59:45.790 --> 04:59:48.860
there are some final
words from Melissa Semcer

04:59:48.860 --> 04:59:50.443
to send us off for the day.

04:59:56.332 --> 04:59:59.467
<v ->Get my video on here,
hopefully in a second.</v>

04:59:59.467 --> 05:00:00.300
I'm not sure if I'm showing up.

05:00:00.300 --> 05:00:01.433
Okay, there we go.

05:00:02.650 --> 05:00:03.943
Yeah, I don't have much
more to add than that.

05:00:03.943 --> 05:00:06.550
Just thank you to everyone who,

05:00:06.550 --> 05:00:08.600
who participated
today for the utilities,

05:00:08.600 --> 05:00:12.130
preparing their
presentations, for the panelists

05:00:12.130 --> 05:00:14.840
that joined in and asked the questions.

05:00:14.840 --> 05:00:17.370
We have tried to capture
the questions in the chat

05:00:17.370 --> 05:00:20.560
that have not been answered
mainly from this morning,

05:00:20.560 --> 05:00:22.930
so that we can follow up on those.

05:00:22.930 --> 05:00:26.820
For the stakeholders who
did not get all of your questions

05:00:26.820 --> 05:00:28.310
answered, which I
know is the case for just

05:00:28.310 --> 05:00:30.360
about all of you,

05:00:30.360 --> 05:00:32.137
feel free to follow up
with those questions

05:00:32.137 --> 05:00:34.173
and data requests to the utilities.

05:00:35.350 --> 05:00:36.600
And other than that,

05:00:36.600 --> 05:00:40.887
we are back on at 9:30
again tomorrow morning and,

05:00:43.896 --> 05:00:45.240
and will use the same
procedures as we did today.

05:00:45.240 --> 05:00:47.650
So thank you for
everyone for showing up,

05:00:47.650 --> 05:00:49.480
and we will see you tomorrow.

05:00:49.480 --> 05:00:50.313
Thank you.